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