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

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0