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