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