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