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