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