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