<
From version < 95.3 >
edited by Xiaoling
on 2022/07/09 10:35
To version < 104.1 >
edited by Edwin Chen
on 2022/09/08 23:13
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -7,6 +7,7 @@
7 7  
8 8  **Table of Contents:**
9 9  
10 +{{toc/}}
10 10  
11 11  
12 12  
... ... @@ -15,6 +15,7 @@
15 15  
16 16  = 1.  Introduction =
17 17  
19 +
18 18  == 1.1 ​ What is NDDS75 Distance Detection Sensor ==
19 19  
20 20  (((
... ... @@ -21,20 +21,34 @@
21 21  
22 22  
23 23  (((
26 +(((
24 24  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.
25 -\\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.
26 -\\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.
27 -\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
28 -\\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)
29 -\\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.
30 30  )))
31 31  
32 -
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.
33 33  )))
34 34  
35 -[[image:1654503236291-817.png]]
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 +)))
36 36  
38 +(((
39 +NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
40 +)))
37 37  
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 +
38 38  [[image:1657327959271-447.png]]
39 39  
40 40  
... ... @@ -55,7 +55,6 @@
55 55  * Micro SIM card slot for NB-IoT SIM
56 56  * 8500mAh Battery for long term use
57 57  
58 -
59 59  == 1.3  Specification ==
60 60  
61 61  
... ... @@ -84,12 +84,11 @@
84 84  (% style="color:#037691" %)**Power Consumption**
85 85  
86 86  * STOP Mode: 10uA @ 3.3v
87 -* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
102 +* Max transmit power: 350mA@3.3v
88 88  
89 -
90 -
91 91  == ​1.4  Applications ==
92 92  
106 +
93 93  * Smart Buildings & Home Automation
94 94  * Logistics and Supply Chain Management
95 95  * Smart Metering
... ... @@ -102,6 +102,7 @@
102 102  
103 103  
104 104  
119 +
105 105  == 1.5  Pin Definitions ==
106 106  
107 107  
... ... @@ -111,8 +111,10 @@
111 111  
112 112  = 2.  Use NDDS75 to communicate with IoT Server =
113 113  
129 +
114 114  == 2.1  How it works ==
115 115  
132 +
116 116  (((
117 117  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.
118 118  )))
... ... @@ -138,16 +138,17 @@
138 138  
139 139  === 2.2.1 Test Requirement ===
140 140  
158 +
141 141  (((
142 142  To use NDDS75 in your city, make sure meet below requirements:
143 143  )))
144 144  
145 145  * Your local operator has already distributed a NB-IoT Network there.
146 -* The local NB-IoT network used the band that NSE01 supports.
164 +* The local NB-IoT network used the band that NDDS75 supports.
147 147  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
148 148  
149 149  (((
150 -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
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.
151 151  )))
152 152  
153 153  
... ... @@ -157,6 +157,7 @@
157 157  
158 158  === 2.2.2 Insert SIM card ===
159 159  
178 +
160 160  (((
161 161  Insert the NB-IoT Card get from your provider.
162 162  )))
... ... @@ -172,6 +172,7 @@
172 172  
173 173  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
174 174  
194 +
175 175  (((
176 176  (((
177 177  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.
... ... @@ -180,6 +180,7 @@
180 180  
181 181  [[image:image-20220709092052-2.png]]
182 182  
203 +
183 183  **Connection:**
184 184  
185 185   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -203,8 +203,9 @@
203 203  
204 204  [[image:1657329814315-101.png]]
205 205  
227 +
206 206  (((
207 -(% 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/]]
229 +(% 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]]**
208 208  )))
209 209  
210 210  
... ... @@ -211,21 +211,38 @@
211 211  
212 212  === 2.2.4 Use CoAP protocol to uplink data ===
213 213  
214 -(% 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/]]
215 215  
237 +(% 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/]]**
216 216  
239 +
240 +(((
217 217  **Use below commands:**
242 +)))
218 218  
219 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
220 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
221 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
244 +* (((
245 +(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
246 +)))
247 +* (((
248 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
249 +)))
250 +* (((
251 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
222 222  
253 +
254 +
255 +)))
256 +
257 +(((
223 223  For parameter description, please refer to AT command set
259 +)))
224 224  
225 225  [[image:1657330452568-615.png]]
226 226  
227 227  
264 +
265 +(((
228 228  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.
267 +)))
229 229  
230 230  [[image:1657330472797-498.png]]
231 231  
... ... @@ -234,9 +234,9 @@
234 234  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
235 235  
236 236  
237 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
276 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
238 238  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
239 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
278 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
240 240  
241 241  [[image:1657330501006-241.png]]
242 242  
... ... @@ -248,11 +248,11 @@
248 248  === 2.2.6 Use MQTT protocol to uplink data ===
249 249  
250 250  
251 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
252 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
253 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
254 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
255 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
290 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
291 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
292 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
293 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
294 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
256 256  * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
257 257  * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
258 258  
... ... @@ -283,30 +283,34 @@
283 283  
284 284  === 2.2.8 Change Update Interval ===
285 285  
325 +
286 286  User can use below command to change the (% style="color:green" %)**uplink interval**.
287 287  
288 288  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
289 289  
290 290  (((
291 -(% style="color:red" %)**NOTE:**
292 -)))
331 +(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.**
293 293  
294 -(((
295 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
333 +
296 296  )))
297 297  
336 +**NOTE:When the firmware version is v1.3.2 and later firmware:**
298 298  
338 +**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
299 299  
340 +
300 300  == 2.3  Uplink Payload ==
301 301  
302 -In this mode, uplink payload includes in total 14 bytes
303 303  
344 +=== 2.3.1 Before Firmware 1.3.2 ===
304 304  
305 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
346 +In this mode, uplink payload includes in total 14 bytes
347 +
348 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
306 306  |=(% style="width: 60px;" %)(((
307 307  **Size(bytes)**
308 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 50px;" %)**1**
309 -|(% 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:108px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]]
351 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
352 +|(% 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"]]
310 310  
311 311  (((
312 312  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
... ... @@ -315,6 +315,7 @@
315 315  
316 316  [[image:1657331036973-987.png]]
317 317  
361 +
318 318  (((
319 319  The payload is ASCII string, representative same HEX:
320 320  )))
... ... @@ -341,14 +341,44 @@
341 341  )))
342 342  * (((
343 343  Interrupt: 0x00 = 0
388 +
389 +
344 344  )))
345 345  
392 +=== **2.3.2 Since firmware v1.3.2** ===
346 346  
394 +In this mode, uplink payload includes 69 bytes in total by default.
395 +
396 +Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
397 +
398 +|**Size(bytes)**|**8**|2|2|1|1|1|2|4|2|4
399 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Distance|Timestamp|Distance|Timestamp.......
400 +
401 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
402 +
403 +[[image:image-20220908175246-1.png]]
404 +
405 +The payload is ASCII string, representative same HEX:
406 +
407 +0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%) where:
408 +
409 +* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
410 +* (% style="color:red" %)Version: 0x0084=132=1.3.2
411 +* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
412 +* (% style="color:blue" %)Singal: 0x1e = 30
413 +* (% style="color:red" %)Mod: 0x01 = 1
414 +* Interrupt: 0x00= 0
415 +* Distance: 0x0039= 57 = 57
416 +* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
417 +* Distance,Time stamp : 00396319baf0
418 +* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
419 +
347 347  == 2.4  Payload Explanation and Sensor Interface ==
348 348  
349 349  
350 350  === 2.4.1  Device ID ===
351 351  
425 +
352 352  (((
353 353  By default, the Device ID equal to the last 6 bytes of IMEI.
354 354  )))
... ... @@ -355,6 +355,8 @@
355 355  
356 356  (((
357 357  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
432 +
433 +
358 358  )))
359 359  
360 360  (((
... ... @@ -370,9 +370,19 @@
370 370  )))
371 371  
372 372  
449 +**NOTE:When the firmware version is v1.3.2 and later firmware:**
373 373  
451 +By default, the Device ID equal to the last 15 bits of IMEI.
452 +
453 +User can use **AT+DEUI** to set Device ID
454 +
455 +**Example:**
456 +
457 +AT+DEUI=868411056754138
458 +
374 374  === 2.4.2  Version Info ===
375 375  
461 +
376 376  (((
377 377  Specify the software version: 0x64=100, means firmware version 1.00.
378 378  )))
... ... @@ -385,9 +385,6 @@
385 385  
386 386  === 2.4.3  Battery Info ===
387 387  
388 -(((
389 -Check the battery voltage for LSE01.
390 -)))
391 391  
392 392  (((
393 393  Ex1: 0x0B45 = 2885mV
... ... @@ -401,6 +401,7 @@
401 401  
402 402  === 2.4.4  Signal Strength ===
403 403  
487 +
404 404  (((
405 405  NB-IoT Network signal Strength.
406 406  )))
... ... @@ -431,11 +431,14 @@
431 431  
432 432  
433 433  
434 -=== 2.4.5  Soil Moisture ===
518 +=== 2.4.5  Distance ===
435 435  
520 +
436 436  Get the distance. Flat object range 280mm - 7500mm.
437 437  
523 +(((
438 438  For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
525 +)))
439 439  
440 440  (((
441 441  (((
... ... @@ -453,6 +453,7 @@
453 453  
454 454  === 2.4.6  Digital Interrupt ===
455 455  
543 +
456 456  (((
457 457  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.
458 458  )))
... ... @@ -487,6 +487,7 @@
487 487  
488 488  === 2.4.7  ​+5V Output ===
489 489  
578 +
490 490  (((
491 491  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
492 492  )))
... ... @@ -494,10 +494,14 @@
494 494  
495 495  (((
496 496  The 5V output time can be controlled by AT Command.
586 +
587 +
497 497  )))
498 498  
499 499  (((
500 500  (% style="color:blue" %)**AT+5VT=1000**
592 +
593 +
501 501  )))
502 502  
503 503  (((
... ... @@ -508,6 +508,7 @@
508 508  
509 509  == 2.5  Downlink Payload ==
510 510  
604 +
511 511  By default, NDDS75 prints the downlink payload to console port.
512 512  
513 513  [[image:image-20220709100028-1.png]]
... ... @@ -557,10 +557,44 @@
557 557  )))
558 558  
559 559  
654 +== 2.6 Distance alarm function(Since firmware v1.3.2) ==
560 560  
561 -== 2.6  ​LED Indicator ==
656 + AT Command:
562 562  
658 +AT+ LDDSALARM=min,max
563 563  
660 +² When min=0, and max≠0, Alarm higher than max
661 +
662 +² When min≠0, and max=0, Alarm lower than min
663 +
664 +² When min≠0 and max≠0, Alarm higher than max or lower than min
665 +
666 +Example:
667 +
668 +AT+ LDDSALARM=260,2000 ~/~/ Alarm when distance lower than 260.
669 +
670 +
671 +== 2.7 Set the number of data to be uploaded and the recording time ==
672 +
673 +➢ AT Command:
674 +
675 +AT+TR=900  ~/~/The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
676 +
677 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
678 +
679 +== 2.8 Read or Clear cached data ==
680 +
681 +➢ AT Command:
682 +
683 +AT+CDP ~/~/ Read cached data
684 +
685 +[[image:image-20220908175333-2.png]]
686 +
687 +AT+CDP=0 ~/~/ Clear cached data
688 +
689 +== 2.9  ​LED Indicator ==
690 +
691 +
564 564  The NDDS75 has an internal LED which is to show the status of different state.
565 565  
566 566  
... ... @@ -575,23 +575,27 @@
575 575  
576 576  
577 577  
578 -== 2.7  ​Firmware Change Log ==
706 +== 2.10  ​Firmware Change Log ==
579 579  
580 580  
581 -Download URL & Firmware Change log
709 +(((
710 +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]]
711 +)))
582 582  
583 583  (((
584 -[[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/]]
714 +
585 585  )))
586 586  
717 +(((
718 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
719 +)))
587 587  
588 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
589 589  
590 590  
723 +== 2.11  ​Battery Analysis ==
591 591  
592 -== 2.8  ​Battery Analysis ==
593 593  
594 -=== 2.8.1  ​Battery Type ===
726 +=== 2.11.1  ​Battery Type ===
595 595  
596 596  
597 597  (((
... ... @@ -616,8 +616,9 @@
616 616  
617 617  
618 618  
619 -=== 2.8.2  Power consumption Analyze ===
751 +=== 2.11.2  Power consumption Analyze ===
620 620  
753 +
621 621  (((
622 622  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.
623 623  )))
... ... @@ -650,12 +650,13 @@
650 650  And the Life expectation in difference case will be shown on the right.
651 651  )))
652 652  
653 -[[image:image-20220708141352-7.jpeg]]
786 +[[image:image-20220709110451-3.png]]
654 654  
655 655  
656 656  
657 -=== 2.8.3  ​Battery Note ===
790 +=== 2.11.3  ​Battery Note ===
658 658  
792 +
659 659  (((
660 660  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.
661 661  )))
... ... @@ -662,8 +662,9 @@
662 662  
663 663  
664 664  
665 -=== 2.8.4  Replace the battery ===
799 +=== 2.11.4  Replace the battery ===
666 666  
801 +
667 667  (((
668 668  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).
669 669  )))
... ... @@ -672,6 +672,7 @@
672 672  
673 673  = 3. ​ Access NB-IoT Module =
674 674  
810 +
675 675  (((
676 676  Users can directly access the AT command set of the NB-IoT module.
677 677  )))
... ... @@ -678,6 +678,8 @@
678 678  
679 679  (((
680 680  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/]] 
817 +
818 +
681 681  )))
682 682  
683 683  [[image:1657333200519-600.png]]
... ... @@ -686,11 +686,13 @@
686 686  
687 687  = 4.  Using the AT Commands =
688 688  
827 +
689 689  == 4.1  Access AT Commands ==
690 690  
691 -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/]]
692 692  
831 +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]]
693 693  
833 +
694 694  AT+<CMD>?  : Help on <CMD>
695 695  
696 696  AT+<CMD>         : Run <CMD>
... ... @@ -730,7 +730,23 @@
730 730  
731 731  AT+SERVADDR  : Server Address
732 732  
873 +AT+TR      : Get or Set record time"
733 733  
875 +AT+APN     : Get or set the APN
876 +
877 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
878 +
879 +AT+DNSCFG  : Get or Set DNS Server
880 +
881 +AT+GETSENSORVALUE   : Returns the current sensor measurement
882 +
883 +AT+NOUD      : Get or Set the number of data to be uploaded
884 +
885 +AT+CDP     : Read or Clear cached data
886 +
887 +AT+LDDSALARM : Get or Set alarm of distance
888 +
889 +
734 734  (% style="color:#037691" %)**COAP Management**      
735 735  
736 736  AT+URI            : Resource parameters
... ... @@ -764,6 +764,7 @@
764 764  
765 765  = ​5.  FAQ =
766 766  
923 +
767 767  == 5.1 ​ How to Upgrade Firmware ==
768 768  
769 769  
... ... @@ -776,7 +776,7 @@
776 776  )))
777 777  
778 778  (((
779 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
936 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
780 780  )))
781 781  
782 782  
... ... @@ -783,6 +783,7 @@
783 783  
784 784  = 6.  Trouble Shooting =
785 785  
943 +
786 786  == 6.1  ​Connection problem when uploading firmware ==
787 787  
788 788  
... ... @@ -798,6 +798,7 @@
798 798  
799 799  == 6.2  AT Command input doesn't work ==
800 800  
959 +
801 801  (((
802 802  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.
803 803  
... ... @@ -823,7 +823,7 @@
823 823  
824 824  (% style="color:#037691" %)**Package Includes**:
825 825  
826 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
985 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1
827 827  * External antenna x 1
828 828  )))
829 829  
... ... @@ -830,9 +830,9 @@
830 830  (((
831 831  
832 832  
992 +
833 833  (% style="color:#037691" %)**Dimension and weight**:
834 834  
835 -
836 836  * Device Size: 13.0 x 5 x 4.5 cm
837 837  * Device Weight: 150g
838 838  * Package Size / pcs : 15 x 12x 5.5 cm
... ... @@ -848,5 +848,6 @@
848 848  
849 849  = 9.  Support =
850 850  
1010 +
851 851  * 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.
852 852  * 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]]
image-20220709110451-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +611.5 KB
Content
image-20220908175246-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +55.7 KB
Content
image-20220908175333-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +31.1 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0