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

Applications

Navigation

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