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