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