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