Skip to Content
Version 104.6 by Xiaoling on 2022/09/09 13:35
Show last authors
1 (% style="text-align:center" %)
2 [[image:image-20220709085040-1.png||height="542" width="524"]]
3
4
5
6
7
8 **Table of Contents:**
9
10 {{toc/}}
11
12
13
14
15
16
17 = 1.  Introduction =
18
19
20 == 1.1 ​ What is NDDS75 Distance Detection Sensor ==
21
22 (((
23
24
25 (((
26 (((
27 The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
28 )))
29
30 (((
31 The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
32 )))
33
34 (((
35 NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
36 )))
37
38 (((
39 NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
40 )))
41
42 (((
43 NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
44 )))
45
46 (((
47 To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
48 )))
49 )))
50
51
52 )))
53
54 [[image:1657327959271-447.png]]
55
56
57
58 == 1.2 ​ Features ==
59
60
61 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
62 * Ultra low power consumption
63 * Distance Detection by Ultrasonic technology
64 * Flat object range 280mm - 7500mm
65 * Accuracy: ±(1cm+S*0.3%) (S: Distance)
66 * Cable Length: 25cm
67 * AT Commands to change parameters
68 * Uplink on periodically
69 * Downlink to change configure
70 * IP66 Waterproof Enclosure
71 * Micro SIM card slot for NB-IoT SIM
72 * 8500mAh Battery for long term use
73
74
75
76
77
78 == 1.3  Specification ==
79
80
81 (% style="color:#037691" %)**Common DC Characteristics:**
82
83 * Supply Voltage: 2.1v ~~ 3.6v
84 * Operating Temperature: -40 ~~ 85°C
85
86 (% style="color:#037691" %)**NB-IoT Spec:**
87
88 * - B1 @H-FDD: 2100MHz
89 * - B3 @H-FDD: 1800MHz
90 * - B8 @H-FDD: 900MHz
91 * - B5 @H-FDD: 850MHz
92 * - B20 @H-FDD: 800MHz
93 * - B28 @H-FDD: 700MHz
94
95 (% style="color:#037691" %)**Battery:**
96
97 * Li/SOCI2 un-chargeable battery
98 * Capacity: 8500mAh
99 * Self Discharge: <1% / Year @ 25°C
100 * Max continuously current: 130mA
101 * Max boost current: 2A, 1 second
102
103 (% style="color:#037691" %)**Power Consumption**
104
105 * STOP Mode: 10uA @ 3.3v
106 * Max transmit power: 350mA@3.3v
107
108
109
110
111
112 == ​1.4  Applications ==
113
114
115 * Smart Buildings & Home Automation
116 * Logistics and Supply Chain Management
117 * Smart Metering
118 * Smart Agriculture
119 * Smart Cities
120 * Smart Factory
121
122 (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
123 ​
124
125
126
127
128 == 1.5  Pin Definitions ==
129
130
131 [[image:1657328609906-564.png]]
132
133
134
135 = 2.  Use NDDS75 to communicate with IoT Server =
136
137
138 == 2.1  How it works ==
139
140
141 (((
142 The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.
143 )))
144
145
146 (((
147 The diagram below shows the working flow in default firmware of NDDS75:
148 )))
149
150 (((
151
152 )))
153
154 [[image:1657328659945-416.png]]
155
156 (((
157
158 )))
159
160
161 == 2.2 ​ Configure the NDDS75 ==
162
163
164 === 2.2.1 Test Requirement ===
165
166
167 (((
168 To use NDDS75 in your city, make sure meet below requirements:
169 )))
170
171 * Your local operator has already distributed a NB-IoT Network there.
172 * The local NB-IoT network used the band that NDDS75 supports.
173 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
174
175 (((
176 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server.
177 )))
178
179
180 [[image:1657328756309-230.png]]
181
182
183
184 === 2.2.2 Insert SIM card ===
185
186
187 (((
188 Insert the NB-IoT Card get from your provider.
189 )))
190
191 (((
192 User need to take out the NB-IoT module and insert the SIM card like below:
193 )))
194
195
196 [[image:1657328884227-504.png]]
197
198
199
200 === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
201
202
203 (((
204 (((
205 User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
206 )))
207 )))
208
209 [[image:image-20220709092052-2.png]]
210
211
212 **Connection:**
213
214 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
215
216 (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
217
218 (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
219
220
221 In the PC, use below serial tool settings:
222
223 * Baud:  (% style="color:green" %)**9600**
224 * Data bits:** (% style="color:green" %)8(%%)**
225 * Stop bits: (% style="color:green" %)**1**
226 * Parity:  (% style="color:green" %)**None**
227 * Flow Control: (% style="color:green" %)**None**
228
229 (((
230 Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
231 )))
232
233 [[image:1657329814315-101.png]]
234
235
236 (((
237 (% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)**[[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]**
238 )))
239
240
241
242 === 2.2.4 Use CoAP protocol to uplink data ===
243
244
245 (% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]**
246
247
248 (((
249 **Use below commands:**
250 )))
251
252 * (((
253 (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
254 )))
255 * (((
256 (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
257 )))
258 * (((
259 (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
260
261
262
263 )))
264
265 (((
266 For parameter description, please refer to AT command set
267
268
269 )))
270
271 [[image:1657330452568-615.png]]
272
273
274
275 (((
276 After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
277
278
279 )))
280
281 [[image:1657330472797-498.png]]
282
283
284
285 === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
286
287
288 * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
289 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
290 * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
291
292 [[image:1657330501006-241.png]]
293
294
295 [[image:1657330533775-472.png]]
296
297
298
299 === 2.2.6 Use MQTT protocol to uplink data ===
300
301
302 * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
303 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
304 * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
305 * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
306 * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
307 * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
308 * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
309
310 [[image:1657249978444-674.png]]
311
312
313 [[image:1657330723006-866.png]]
314
315
316 (((
317 MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
318 )))
319
320
321
322 === 2.2.7 Use TCP protocol to uplink data ===
323
324
325 * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
326 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
327
328 [[image:image-20220709093918-1.png]]
329
330
331 [[image:image-20220709093918-2.png]]
332
333
334
335 === 2.2.8 Change Update Interval ===
336
337
338 User can use below command to change the (% style="color:green" %)**uplink interval**.
339
340 * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
341
342 (((
343
344
345
346 (% style="color:red" %)**NOTE:**
347
348 (% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
349
350 (% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
351 )))
352
353 (% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
354
355
356
357 == 2.3  Uplink Payload ==
358
359
360 === 2.3.1  Before Firmware 1.3.2 ===
361
362
363 In this mode, uplink payload includes in total 14 bytes
364
365 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
366 |=(% style="width: 60px;" %)(((
367 **Size(bytes)**
368 )))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
369 |(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
370
371 (((
372 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
373 )))
374
375
376 [[image:1657331036973-987.png]]
377
378
379 (((
380 The payload is **ASCII** string, representative same HEX:
381 )))
382
383 (((
384 0x72403155615900640c6c19029200 where:
385 )))
386
387 * (((
388 Device ID: 0x724031556159 = 724031556159
389 )))
390 * (((
391 Version:  0x0064=100=1.0.0
392 )))
393
394 * (((
395 BAT:  0x0c6c = 3180 mV = 3.180V
396 )))
397 * (((
398 Signal: 0x19 = 25
399 )))
400 * (((
401 Distance: 0x0292= 658 mm
402 )))
403 * (((
404 Interrupt: 0x00 = 0
405
406
407
408
409
410 )))
411
412 === **2.3.2  Since firmware v1.3.2** ===
413
414
415 In this mode, uplink payload includes 69 bytes in total by default.
416
417 Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
418
419 (% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
420 |(% style="width:95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)4
421 |(% style="width:95px" %)**Value**|(% style="width:84px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:48px" %)BAT|(% style="width:123px" %)Signal Strength|(% style="width:55px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:77px" %)Distance|(% style="width:94px" %)Timestamp|(% style="width:77px" %)Distance|(% style="width:116px" %)Timestamp.......
422
423 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
424
425 [[image:image-20220908175246-1.png]]
426
427
428 The payload is ASCII string, representative same HEX:
429
430 0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%) where:
431
432 * (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
433 * (% style="color:red" %)Version: 0x0084=132=1.3.2
434 * (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
435 * (% style="color:blue" %)Singal: 0x1e = 30
436 * (% style="color:red" %)Mod: 0x01 = 1
437 * Interrupt: 0x00= 0
438 * Distance: 0x0039= 57 = 57
439 * Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
440 * Distance,Time stamp : 00396319baf0
441 * (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
442
443
444
445
446
447 == 2.4  Payload Explanation and Sensor Interface ==
448
449
450 === 2.4.1  Device ID ===
451
452
453 (((
454 By default, the Device ID equal to the last 6 bytes of IMEI.
455 )))
456
457 (((
458 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
459
460
461 )))
462
463 (((
464 (% style="color:blue" %)**Example :**
465 )))
466
467 (((
468 AT+DEUI=A84041F15612
469 )))
470
471 (((
472 The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
473 )))
474
475
476 (% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
477
478 (% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
479
480 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
481
482
483 (% style="color:blue" %)**Example :**
484
485 AT+DEUI=868411056754138
486
487
488
489 === 2.4.2  Version Info ===
490
491
492 (((
493 Specify the software version: 0x64=100, means firmware version 1.00.
494 )))
495
496 (((
497 For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
498 )))
499
500
501
502 === 2.4.3  Battery Info ===
503
504
505 (((
506 Ex1: 0x0B45 = 2885mV
507 )))
508
509 (((
510 Ex2: 0x0B49 = 2889mV
511 )))
512
513
514
515 === 2.4.4  Signal Strength ===
516
517
518 (((
519 NB-IoT Network signal Strength.
520 )))
521
522 (((
523 **Ex1: 0x1d = 29**
524 )))
525
526 (((
527 (% style="color:blue" %)**0**(%%)  -113dBm or less
528 )))
529
530 (((
531 (% style="color:blue" %)**1**(%%)  -111dBm
532 )))
533
534 (((
535 (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
536 )))
537
538 (((
539 (% style="color:blue" %)**31**  (%%) -51dBm or greater
540 )))
541
542 (((
543 (% style="color:blue" %)**99**   (%%) Not known or not detectable
544 )))
545
546
547
548 === 2.4.5  Distance ===
549
550
551 Get the distance. Flat object range 280mm - 7500mm.
552
553 (((
554 For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
555 )))
556
557 (((
558 (((
559 (% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
560 )))
561 )))
562
563 (((
564
565 )))
566
567 (((
568
569 )))
570
571 === 2.4.6  Digital Interrupt ===
572
573
574 (((
575 Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
576 )))
577
578 (((
579 The command is:
580 )))
581
582 (((
583 (% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
584 )))
585
586
587 (((
588 The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
589 )))
590
591
592 (((
593 Example:
594 )))
595
596 (((
597 0x(00): Normal uplink packet.
598 )))
599
600 (((
601 0x(01): Interrupt Uplink Packet.
602 )))
603
604
605
606 === 2.4.7  ​+5V Output ===
607
608
609 (((
610 NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
611 )))
612
613
614 (((
615 The 5V output time can be controlled by AT Command.
616
617
618 )))
619
620 (((
621 (% style="color:blue" %)**AT+5VT=1000**
622
623
624 )))
625
626 (((
627 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
628 )))
629
630
631
632 == 2.5  Downlink Payload ==
633
634
635 By default, NDDS75 prints the downlink payload to console port.
636
637 [[image:image-20220709100028-1.png]]
638
639
640 (((
641 (% style="color:blue" %)**Examples:**
642 )))
643
644 (((
645
646 )))
647
648 * (((
649 (% style="color:blue" %)**Set TDC**
650 )))
651
652 (((
653 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
654 )))
655
656 (((
657 Payload:    01 00 00 1E    TDC=30S
658 )))
659
660 (((
661 Payload:    01 00 00 3C    TDC=60S
662 )))
663
664 (((
665
666 )))
667
668 * (((
669 (% style="color:blue" %)**Reset**
670 )))
671
672 (((
673 If payload = 0x04FF, it will reset the NDDS75
674 )))
675
676
677 * (% style="color:blue" %)**INTMOD**
678
679 (((
680 Downlink Payload: 06000003, Set AT+INTMOD=3
681 )))
682
683
684
685 == 2.6  Distance alarm function(Since firmware v1.3.2) ==
686
687
688 (% style="color:blue" %)** ➢ AT Command:**
689
690 (% style="color:#037691" %)** AT+ LDDSALARM=min,max**
691
692 ² When min=0, and max≠0, Alarm higher than max
693
694 ² When min≠0, and max=0, Alarm lower than min
695
696 ² When min≠0 and max≠0, Alarm higher than max or lower than min
697
698
699 (% style="color:blue" %)** Example:**
700
701 **AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
702
703
704
705 == 2.7  Set the number of data to be uploaded and the recording time ==
706
707
708 (% style="color:blue" %)** ➢ AT Command:**
709
710 * (% style="color:#037691" %)** AT+TR=900** (%%) ~/~/ The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
711 * (% style="color:#037691" %)** AT+NOUD=8** (%%) ~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
712
713
714
715
716 == 2.8  Read or Clear cached data ==
717
718
719 (% style="color:blue" %)** ➢ AT Command:**
720
721 * (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data
722 * (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
723
724
725
726 [[image:image-20220908175333-2.png]]
727
728
729
730 == 2.9  ​LED Indicator ==
731
732
733 The NDDS75 has an internal LED which is to show the status of different state.
734
735
736 * When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
737 * Then the LED will be on for 1 second means device is boot normally.
738 * After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
739 * For each uplink probe, LED will be on for 500ms.
740
741 (((
742
743 )))
744
745
746
747 == 2.10  ​Firmware Change Log ==
748
749
750 (((
751 Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]]
752 )))
753
754 (((
755
756 )))
757
758 (((
759 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
760 )))
761
762
763
764 == 2.11  ​Battery Analysis ==
765
766
767 === 2.11.1  ​Battery Type ===
768
769
770 (((
771 The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
772 )))
773
774 (((
775 The battery is designed to last for several years depends on the actually use environment and update interval. 
776 )))
777
778 (((
779 The battery related documents as below:
780 )))
781
782 * [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
783 * [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
784 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
785
786 (((
787 [[image:image-20220709101450-2.png]]
788 )))
789
790
791
792 === 2.11.2  Power consumption Analyze ===
793
794
795 (((
796 Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
797 )))
798
799
800 (((
801 Instruction to use as below:
802 )))
803
804 (((
805 (% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
806 )))
807
808
809 (((
810 (% style="color:blue" %)**Step 2: **(%%) Open it and choose
811 )))
812
813 * (((
814 Product Model
815 )))
816 * (((
817 Uplink Interval
818 )))
819 * (((
820 Working Mode
821 )))
822
823 (((
824 And the Life expectation in difference case will be shown on the right.
825 )))
826
827 [[image:image-20220709110451-3.png]]
828
829
830
831 === 2.11.3  ​Battery Note ===
832
833
834 (((
835 The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
836 )))
837
838
839
840 === 2.11.4  Replace the battery ===
841
842
843 (((
844 The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
845 )))
846
847
848
849 = 3. ​ Access NB-IoT Module =
850
851
852 (((
853 Users can directly access the AT command set of the NB-IoT module.
854 )))
855
856 (((
857 The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 
858
859
860 )))
861
862 [[image:1657333200519-600.png]]
863
864
865
866 = 4.  Using the AT Commands =
867
868
869 == 4.1  Access AT Commands ==
870
871
872 See this link for detail:  [[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]
873
874
875 AT+<CMD>?  : Help on <CMD>
876
877 AT+<CMD>         : Run <CMD>
878
879 AT+<CMD>=<value> : Set the value
880
881 AT+<CMD>=?  : Get the value
882
883
884 (% style="color:#037691" %)**General Commands**(%%)      
885
886 AT  : Attention       
887
888 AT?  : Short Help     
889
890 ATZ  : MCU Reset    
891
892 AT+TDC  : Application Data Transmission Interval
893
894 AT+CFG  : Print all configurations
895
896 AT+CFGMOD           : Working mode selection
897
898 AT+INTMOD            : Set the trigger interrupt mode
899
900 AT+5VT  : Set extend the time of 5V power  
901
902 AT+PRO  : Choose agreement
903
904 AT+WEIGRE  : Get weight or set weight to 0
905
906 AT+WEIGAP  : Get or Set the GapValue of weight
907
908 AT+RXDL  : Extend the sending and receiving time
909
910 AT+CNTFAC  : Get or set counting parameters
911
912 AT+SERVADDR  : Server Address
913
914 AT+TR      : Get or Set record time"
915
916 AT+APN     : Get or set the APN
917
918 AT+FBAND   : Get or Set whether to automatically modify the frequency band
919
920 AT+DNSCFG  : Get or Set DNS Server
921
922 AT+GETSENSORVALUE   : Returns the current sensor measurement
923
924 AT+NOUD      : Get or Set the number of data to be uploaded
925
926 AT+CDP     : Read or Clear cached data
927
928 AT+LDDSALARM : Get or Set alarm of distance
929
930
931 (% style="color:#037691" %)**COAP Management**      
932
933 AT+URI            : Resource parameters
934
935
936 (% style="color:#037691" %)**UDP Management**
937
938 AT+CFM          : Upload confirmation mode (only valid for UDP)
939
940
941 (% style="color:#037691" %)**MQTT Management**
942
943 AT+CLIENT               : Get or Set MQTT client
944
945 AT+UNAME  : Get or Set MQTT Username
946
947 AT+PWD                  : Get or Set MQTT password
948
949 AT+PUBTOPIC  : Get or Set MQTT publish topic
950
951 AT+SUBTOPIC  : Get or Set MQTT subscription topic
952
953
954 (% style="color:#037691" %)**Information**          
955
956 AT+FDR  : Factory Data Reset
957
958 AT+PWORD  : Serial Access Password
959
960
961
962 = ​5.  FAQ =
963
964
965 == 5.1 ​ How to Upgrade Firmware ==
966
967
968 (((
969 User can upgrade the firmware for 1) bug fix, 2) new feature release.
970 )))
971
972 (((
973 Please see this link for how to upgrade:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
974 )))
975
976 (((
977 (% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
978 )))
979
980
981
982 = 6.  Trouble Shooting =
983
984
985 == 6.1  ​Connection problem when uploading firmware ==
986
987
988 (((
989 **Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
990 )))
991
992 (% class="wikigeneratedid" %)
993 (((
994
995 )))
996
997
998 == 6.2  AT Command input doesn't work ==
999
1000
1001 (((
1002 In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
1003
1004
1005 )))
1006
1007
1008 = 7. ​ Order Info =
1009
1010
1011 Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
1012
1013
1014 (% class="wikigeneratedid" %)
1015 (((
1016
1017 )))
1018
1019 = 8.  Packing Info =
1020
1021 (((
1022
1023
1024 (% style="color:#037691" %)**Package Includes**:
1025
1026 * NDDS75 NB-IoT Distance Detect Sensor Node x 1
1027 * External antenna x 1
1028 )))
1029
1030 (((
1031
1032
1033
1034 (% style="color:#037691" %)**Dimension and weight**:
1035
1036 * Device Size: 13.0 x 5 x 4.5 cm
1037 * Device Weight: 150g
1038 * Package Size / pcs : 15 x 12x 5.5 cm
1039 * Weight / pcs : 220g
1040 )))
1041
1042 (((
1043
1044
1045
1046
1047 )))
1048
1049 = 9.  Support =
1050
1051
1052 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1053 * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]