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