Skip to Content
Version 104.1 by Edwin Chen on 2022/09/08 23:13
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 == 1.3  Specification ==
75
76
77 (% style="color:#037691" %)**Common DC Characteristics:**
78
79 * Supply Voltage: 2.1v ~~ 3.6v
80 * Operating Temperature: -40 ~~ 85°C
81
82 (% style="color:#037691" %)**NB-IoT Spec:**
83
84 * - B1 @H-FDD: 2100MHz
85 * - B3 @H-FDD: 1800MHz
86 * - B8 @H-FDD: 900MHz
87 * - B5 @H-FDD: 850MHz
88 * - B20 @H-FDD: 800MHz
89 * - B28 @H-FDD: 700MHz
90
91 (% style="color:#037691" %)**Battery:**
92
93 * Li/SOCI2 un-chargeable battery
94 * Capacity: 8500mAh
95 * Self Discharge: <1% / Year @ 25°C
96 * Max continuously current: 130mA
97 * Max boost current: 2A, 1 second
98
99 (% style="color:#037691" %)**Power Consumption**
100
101 * STOP Mode: 10uA @ 3.3v
102 * Max transmit power: 350mA@3.3v
103
104 == ​1.4  Applications ==
105
106
107 * Smart Buildings & Home Automation
108 * Logistics and Supply Chain Management
109 * Smart Metering
110 * Smart Agriculture
111 * Smart Cities
112 * Smart Factory
113
114 (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
115 ​
116
117
118
119
120 == 1.5  Pin Definitions ==
121
122
123 [[image:1657328609906-564.png]]
124
125
126
127 = 2.  Use NDDS75 to communicate with IoT Server =
128
129
130 == 2.1  How it works ==
131
132
133 (((
134 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.
135 )))
136
137
138 (((
139 The diagram below shows the working flow in default firmware of NDDS75:
140 )))
141
142 (((
143
144 )))
145
146 [[image:1657328659945-416.png]]
147
148 (((
149
150 )))
151
152
153 == 2.2 ​ Configure the NDDS75 ==
154
155
156 === 2.2.1 Test Requirement ===
157
158
159 (((
160 To use NDDS75 in your city, make sure meet below requirements:
161 )))
162
163 * Your local operator has already distributed a NB-IoT Network there.
164 * The local NB-IoT network used the band that NDDS75 supports.
165 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
166
167 (((
168 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.
169 )))
170
171
172 [[image:1657328756309-230.png]]
173
174
175
176 === 2.2.2 Insert SIM card ===
177
178
179 (((
180 Insert the NB-IoT Card get from your provider.
181 )))
182
183 (((
184 User need to take out the NB-IoT module and insert the SIM card like below:
185 )))
186
187
188 [[image:1657328884227-504.png]]
189
190
191
192 === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
193
194
195 (((
196 (((
197 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.
198 )))
199 )))
200
201 [[image:image-20220709092052-2.png]]
202
203
204 **Connection:**
205
206 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
207
208 (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
209
210 (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
211
212
213 In the PC, use below serial tool settings:
214
215 * Baud:  (% style="color:green" %)**9600**
216 * Data bits:** (% style="color:green" %)8(%%)**
217 * Stop bits: (% style="color:green" %)**1**
218 * Parity:  (% style="color:green" %)**None**
219 * Flow Control: (% style="color:green" %)**None**
220
221 (((
222 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.
223 )))
224
225 [[image:1657329814315-101.png]]
226
227
228 (((
229 (% 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]]**
230 )))
231
232
233
234 === 2.2.4 Use CoAP protocol to uplink data ===
235
236
237 (% 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/]]**
238
239
240 (((
241 **Use below commands:**
242 )))
243
244 * (((
245 (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
246 )))
247 * (((
248 (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
249 )))
250 * (((
251 (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
252
253
254
255 )))
256
257 (((
258 For parameter description, please refer to AT command set
259 )))
260
261 [[image:1657330452568-615.png]]
262
263
264
265 (((
266 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.
267 )))
268
269 [[image:1657330472797-498.png]]
270
271
272
273 === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
274
275
276 * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
277 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
278 * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
279
280 [[image:1657330501006-241.png]]
281
282
283 [[image:1657330533775-472.png]]
284
285
286
287 === 2.2.6 Use MQTT protocol to uplink data ===
288
289
290 * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
291 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
292 * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
293 * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
294 * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
295 * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
296 * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
297
298 [[image:1657249978444-674.png]]
299
300
301 [[image:1657330723006-866.png]]
302
303
304 (((
305 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.
306 )))
307
308
309
310 === 2.2.7 Use TCP protocol to uplink data ===
311
312
313 * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
314 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
315
316 [[image:image-20220709093918-1.png]]
317
318
319 [[image:image-20220709093918-2.png]]
320
321
322
323 === 2.2.8 Change Update Interval ===
324
325
326 User can use below command to change the (% style="color:green" %)**uplink interval**.
327
328 * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
329
330 (((
331 (% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.**
332
333
334 )))
335
336 **NOTE:When the firmware version is v1.3.2 and later firmware:**
337
338 **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).**
339
340
341 == 2.3  Uplink Payload ==
342
343
344 === 2.3.1 Before Firmware 1.3.2 ===
345
346 In this mode, uplink payload includes in total 14 bytes
347
348 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
349 |=(% style="width: 60px;" %)(((
350 **Size(bytes)**
351 )))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
352 |(% 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"]]
353
354 (((
355 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
356 )))
357
358
359 [[image:1657331036973-987.png]]
360
361
362 (((
363 The payload is ASCII string, representative same HEX:
364 )))
365
366 (((
367 0x72403155615900640c6c19029200 where:
368 )))
369
370 * (((
371 Device ID: 0x724031556159 = 724031556159
372 )))
373 * (((
374 Version: 0x0064=100=1.0.0
375 )))
376
377 * (((
378 BAT: 0x0c6c = 3180 mV = 3.180V
379 )))
380 * (((
381 Signal: 0x19 = 25
382 )))
383 * (((
384 Distance: 0x0292= 658 mm
385 )))
386 * (((
387 Interrupt: 0x00 = 0
388
389
390 )))
391
392 === **2.3.2 Since firmware v1.3.2** ===
393
394 In this mode, uplink payload includes 69 bytes in total by default.
395
396 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.
397
398 |**Size(bytes)**|**8**|2|2|1|1|1|2|4|2|4
399 |**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Distance|Timestamp|Distance|Timestamp.......
400
401 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
402
403 [[image:image-20220908175246-1.png]]
404
405 The payload is ASCII string, representative same HEX:
406
407 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:
408
409 * (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
410 * (% style="color:red" %)Version: 0x0084=132=1.3.2
411 * (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
412 * (% style="color:blue" %)Singal: 0x1e = 30
413 * (% style="color:red" %)Mod: 0x01 = 1
414 * Interrupt: 0x00= 0
415 * Distance: 0x0039= 57 = 57
416 * Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
417 * Distance,Time stamp : 00396319baf0
418 * (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
419
420 == 2.4  Payload Explanation and Sensor Interface ==
421
422
423 === 2.4.1  Device ID ===
424
425
426 (((
427 By default, the Device ID equal to the last 6 bytes of IMEI.
428 )))
429
430 (((
431 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
432
433
434 )))
435
436 (((
437 **Example:**
438 )))
439
440 (((
441 AT+DEUI=A84041F15612
442 )))
443
444 (((
445 The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
446 )))
447
448
449 **NOTE:When the firmware version is v1.3.2 and later firmware:**
450
451 By default, the Device ID equal to the last 15 bits of IMEI.
452
453 User can use **AT+DEUI** to set Device ID
454
455 **Example:**
456
457 AT+DEUI=868411056754138
458
459 === 2.4.2  Version Info ===
460
461
462 (((
463 Specify the software version: 0x64=100, means firmware version 1.00.
464 )))
465
466 (((
467 For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
468 )))
469
470
471
472 === 2.4.3  Battery Info ===
473
474
475 (((
476 Ex1: 0x0B45 = 2885mV
477 )))
478
479 (((
480 Ex2: 0x0B49 = 2889mV
481 )))
482
483
484
485 === 2.4.4  Signal Strength ===
486
487
488 (((
489 NB-IoT Network signal Strength.
490 )))
491
492 (((
493 **Ex1: 0x1d = 29**
494 )))
495
496 (((
497 (% style="color:blue" %)**0**(%%)  -113dBm or less
498 )))
499
500 (((
501 (% style="color:blue" %)**1**(%%)  -111dBm
502 )))
503
504 (((
505 (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
506 )))
507
508 (((
509 (% style="color:blue" %)**31**  (%%) -51dBm or greater
510 )))
511
512 (((
513 (% style="color:blue" %)**99**   (%%) Not known or not detectable
514 )))
515
516
517
518 === 2.4.5  Distance ===
519
520
521 Get the distance. Flat object range 280mm - 7500mm.
522
523 (((
524 For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
525 )))
526
527 (((
528 (((
529 (% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
530 )))
531 )))
532
533 (((
534
535 )))
536
537 (((
538
539 )))
540
541 === 2.4.6  Digital Interrupt ===
542
543
544 (((
545 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.
546 )))
547
548 (((
549 The command is:
550 )))
551
552 (((
553 (% 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]])**.**
554 )))
555
556
557 (((
558 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.
559 )))
560
561
562 (((
563 Example:
564 )))
565
566 (((
567 0x(00): Normal uplink packet.
568 )))
569
570 (((
571 0x(01): Interrupt Uplink Packet.
572 )))
573
574
575
576 === 2.4.7  ​+5V Output ===
577
578
579 (((
580 NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
581 )))
582
583
584 (((
585 The 5V output time can be controlled by AT Command.
586
587
588 )))
589
590 (((
591 (% style="color:blue" %)**AT+5VT=1000**
592
593
594 )))
595
596 (((
597 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
598 )))
599
600
601
602 == 2.5  Downlink Payload ==
603
604
605 By default, NDDS75 prints the downlink payload to console port.
606
607 [[image:image-20220709100028-1.png]]
608
609
610 (((
611 (% style="color:blue" %)**Examples:**
612 )))
613
614 (((
615
616 )))
617
618 * (((
619 (% style="color:blue" %)**Set TDC**
620 )))
621
622 (((
623 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
624 )))
625
626 (((
627 Payload:    01 00 00 1E    TDC=30S
628 )))
629
630 (((
631 Payload:    01 00 00 3C    TDC=60S
632 )))
633
634 (((
635
636 )))
637
638 * (((
639 (% style="color:blue" %)**Reset**
640 )))
641
642 (((
643 If payload = 0x04FF, it will reset the NDDS75
644 )))
645
646
647 * (% style="color:blue" %)**INTMOD**
648
649 (((
650 Downlink Payload: 06000003, Set AT+INTMOD=3
651 )))
652
653
654 == 2.6 Distance alarm function(Since firmware v1.3.2) ==
655
656 ➢ AT Command:
657
658 AT+ LDDSALARM=min,max
659
660 ² When min=0, and max≠0, Alarm higher than max
661
662 ² When min≠0, and max=0, Alarm lower than min
663
664 ² When min≠0 and max≠0, Alarm higher than max or lower than min
665
666 Example:
667
668 AT+ LDDSALARM=260,2000 ~/~/ Alarm when distance lower than 260.
669
670
671 == 2.7 Set the number of data to be uploaded and the recording time ==
672
673 ➢ AT Command:
674
675 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)
676
677 AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
678
679 == 2.8 Read or Clear cached data ==
680
681 ➢ AT Command:
682
683 AT+CDP ~/~/ Read cached data
684
685 [[image:image-20220908175333-2.png]]
686
687 AT+CDP=0 ~/~/ Clear cached data
688
689 == 2.9  ​LED Indicator ==
690
691
692 The NDDS75 has an internal LED which is to show the status of different state.
693
694
695 * 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)
696 * Then the LED will be on for 1 second means device is boot normally.
697 * After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
698 * For each uplink probe, LED will be on for 500ms.
699
700 (((
701
702 )))
703
704
705
706 == 2.10  ​Firmware Change Log ==
707
708
709 (((
710 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]]
711 )))
712
713 (((
714
715 )))
716
717 (((
718 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
719 )))
720
721
722
723 == 2.11  ​Battery Analysis ==
724
725
726 === 2.11.1  ​Battery Type ===
727
728
729 (((
730 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.
731 )))
732
733 (((
734 The battery is designed to last for several years depends on the actually use environment and update interval. 
735 )))
736
737 (((
738 The battery related documents as below:
739 )))
740
741 * [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
742 * [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
743 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
744
745 (((
746 [[image:image-20220709101450-2.png]]
747 )))
748
749
750
751 === 2.11.2  Power consumption Analyze ===
752
753
754 (((
755 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.
756 )))
757
758
759 (((
760 Instruction to use as below:
761 )))
762
763 (((
764 (% 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/]]
765 )))
766
767
768 (((
769 (% style="color:blue" %)**Step 2: **(%%) Open it and choose
770 )))
771
772 * (((
773 Product Model
774 )))
775 * (((
776 Uplink Interval
777 )))
778 * (((
779 Working Mode
780 )))
781
782 (((
783 And the Life expectation in difference case will be shown on the right.
784 )))
785
786 [[image:image-20220709110451-3.png]]
787
788
789
790 === 2.11.3  ​Battery Note ===
791
792
793 (((
794 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.
795 )))
796
797
798
799 === 2.11.4  Replace the battery ===
800
801
802 (((
803 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).
804 )))
805
806
807
808 = 3. ​ Access NB-IoT Module =
809
810
811 (((
812 Users can directly access the AT command set of the NB-IoT module.
813 )))
814
815 (((
816 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/]] 
817
818
819 )))
820
821 [[image:1657333200519-600.png]]
822
823
824
825 = 4.  Using the AT Commands =
826
827
828 == 4.1  Access AT Commands ==
829
830
831 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]]
832
833
834 AT+<CMD>?  : Help on <CMD>
835
836 AT+<CMD>         : Run <CMD>
837
838 AT+<CMD>=<value> : Set the value
839
840 AT+<CMD>=?  : Get the value
841
842
843 (% style="color:#037691" %)**General Commands**(%%)      
844
845 AT  : Attention       
846
847 AT?  : Short Help     
848
849 ATZ  : MCU Reset    
850
851 AT+TDC  : Application Data Transmission Interval
852
853 AT+CFG  : Print all configurations
854
855 AT+CFGMOD           : Working mode selection
856
857 AT+INTMOD            : Set the trigger interrupt mode
858
859 AT+5VT  : Set extend the time of 5V power  
860
861 AT+PRO  : Choose agreement
862
863 AT+WEIGRE  : Get weight or set weight to 0
864
865 AT+WEIGAP  : Get or Set the GapValue of weight
866
867 AT+RXDL  : Extend the sending and receiving time
868
869 AT+CNTFAC  : Get or set counting parameters
870
871 AT+SERVADDR  : Server Address
872
873 AT+TR      : Get or Set record time"
874
875 AT+APN     : Get or set the APN
876
877 AT+FBAND   : Get or Set whether to automatically modify the frequency band
878
879 AT+DNSCFG  : Get or Set DNS Server
880
881 AT+GETSENSORVALUE   : Returns the current sensor measurement
882
883 AT+NOUD      : Get or Set the number of data to be uploaded
884
885 AT+CDP     : Read or Clear cached data
886
887 AT+LDDSALARM : Get or Set alarm of distance
888
889
890 (% style="color:#037691" %)**COAP Management**      
891
892 AT+URI            : Resource parameters
893
894
895 (% style="color:#037691" %)**UDP Management**
896
897 AT+CFM          : Upload confirmation mode (only valid for UDP)
898
899
900 (% style="color:#037691" %)**MQTT Management**
901
902 AT+CLIENT               : Get or Set MQTT client
903
904 AT+UNAME  : Get or Set MQTT Username
905
906 AT+PWD                  : Get or Set MQTT password
907
908 AT+PUBTOPIC  : Get or Set MQTT publish topic
909
910 AT+SUBTOPIC  : Get or Set MQTT subscription topic
911
912
913 (% style="color:#037691" %)**Information**          
914
915 AT+FDR  : Factory Data Reset
916
917 AT+PWORD  : Serial Access Password
918
919
920
921 = ​5.  FAQ =
922
923
924 == 5.1 ​ How to Upgrade Firmware ==
925
926
927 (((
928 User can upgrade the firmware for 1) bug fix, 2) new feature release.
929 )))
930
931 (((
932 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]]
933 )))
934
935 (((
936 (% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
937 )))
938
939
940
941 = 6.  Trouble Shooting =
942
943
944 == 6.1  ​Connection problem when uploading firmware ==
945
946
947 (((
948 **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]]
949 )))
950
951 (% class="wikigeneratedid" %)
952 (((
953
954 )))
955
956
957 == 6.2  AT Command input doesn't work ==
958
959
960 (((
961 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.
962
963
964 )))
965
966
967 = 7. ​ Order Info =
968
969
970 Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
971
972
973 (% class="wikigeneratedid" %)
974 (((
975
976 )))
977
978 = 8.  Packing Info =
979
980 (((
981
982
983 (% style="color:#037691" %)**Package Includes**:
984
985 * NDDS75 NB-IoT Distance Detect Sensor Node x 1
986 * External antenna x 1
987 )))
988
989 (((
990
991
992
993 (% style="color:#037691" %)**Dimension and weight**:
994
995 * Device Size: 13.0 x 5 x 4.5 cm
996 * Device Weight: 150g
997 * Package Size / pcs : 15 x 12x 5.5 cm
998 * Weight / pcs : 220g
999 )))
1000
1001 (((
1002
1003
1004
1005
1006 )))
1007
1008 = 9.  Support =
1009
1010
1011 * 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.
1012 * 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]]