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