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