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