Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 97.4 >
edited by Xiaoling
on 2022/07/09 11:10
To version < 104.3 >
edited by Xiaoling
on 2022/09/09 11:50
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,6 +16,7 @@
16 16  
17 17  = 1.  Introduction =
18 18  
19 +
19 19  == 1.1 ​ What is NDDS75 Distance Detection Sensor ==
20 20  
21 21  (((
... ... @@ -22,14 +22,31 @@
22 22  
23 23  
24 24  (((
26 +(((
25 25  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.
26 -\\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.
27 -\\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.
28 -\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
29 -\\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)
30 -\\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.
31 31  )))
32 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.
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 +
33 33  
34 34  )))
35 35  
... ... @@ -53,8 +53,6 @@
53 53  * Micro SIM card slot for NB-IoT SIM
54 54  * 8500mAh Battery for long term use
55 55  
56 -
57 -
58 58  == 1.3  Specification ==
59 59  
60 60  
... ... @@ -83,12 +83,11 @@
83 83  (% style="color:#037691" %)**Power Consumption**
84 84  
85 85  * STOP Mode: 10uA @ 3.3v
86 -* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
102 +* Max transmit power: 350mA@3.3v
87 87  
88 -
89 -
90 90  == ​1.4  Applications ==
91 91  
106 +
92 92  * Smart Buildings & Home Automation
93 93  * Logistics and Supply Chain Management
94 94  * Smart Metering
... ... @@ -100,6 +100,8 @@
100 100  ​
101 101  
102 102  
118 +
119 +
103 103  == 1.5  Pin Definitions ==
104 104  
105 105  
... ... @@ -109,8 +109,10 @@
109 109  
110 110  = 2.  Use NDDS75 to communicate with IoT Server =
111 111  
129 +
112 112  == 2.1  How it works ==
113 113  
132 +
114 114  (((
115 115  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.
116 116  )))
... ... @@ -136,16 +136,17 @@
136 136  
137 137  === 2.2.1 Test Requirement ===
138 138  
158 +
139 139  (((
140 140  To use NDDS75 in your city, make sure meet below requirements:
141 141  )))
142 142  
143 143  * Your local operator has already distributed a NB-IoT Network there.
144 -* The local NB-IoT network used the band that NSE01 supports.
164 +* The local NB-IoT network used the band that NDDS75 supports.
145 145  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
146 146  
147 147  (((
148 -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.
149 149  )))
150 150  
151 151  
... ... @@ -155,6 +155,7 @@
155 155  
156 156  === 2.2.2 Insert SIM card ===
157 157  
178 +
158 158  (((
159 159  Insert the NB-IoT Card get from your provider.
160 160  )))
... ... @@ -170,6 +170,7 @@
170 170  
171 171  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
172 172  
194 +
173 173  (((
174 174  (((
175 175  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.
... ... @@ -178,6 +178,7 @@
178 178  
179 179  [[image:image-20220709092052-2.png]]
180 180  
203 +
181 181  **Connection:**
182 182  
183 183   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -201,8 +201,9 @@
201 201  
202 202  [[image:1657329814315-101.png]]
203 203  
227 +
204 204  (((
205 -(% 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]]**
206 206  )))
207 207  
208 208  
... ... @@ -209,22 +209,43 @@
209 209  
210 210  === 2.2.4 Use CoAP protocol to uplink data ===
211 211  
212 -(% 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/]]
213 213  
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/]]**
214 214  
239 +
240 +(((
215 215  **Use below commands:**
242 +)))
216 216  
217 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
218 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
219 -* (% 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
220 220  
253 +
254 +
255 +)))
256 +
257 +(((
221 221  For parameter description, please refer to AT command set
222 222  
260 +
261 +)))
262 +
223 223  [[image:1657330452568-615.png]]
224 224  
225 225  
266 +
267 +(((
226 226  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.
227 227  
270 +
271 +)))
272 +
228 228  [[image:1657330472797-498.png]]
229 229  
230 230  
... ... @@ -232,9 +232,9 @@
232 232  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
233 233  
234 234  
235 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
280 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
236 236  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
237 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
282 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
238 238  
239 239  [[image:1657330501006-241.png]]
240 240  
... ... @@ -246,11 +246,11 @@
246 246  === 2.2.6 Use MQTT protocol to uplink data ===
247 247  
248 248  
249 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
250 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
251 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
252 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
253 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
294 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
295 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
296 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
297 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
298 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
254 254  * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
255 255  * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
256 256  
... ... @@ -281,29 +281,35 @@
281 281  
282 282  === 2.2.8 Change Update Interval ===
283 283  
329 +
284 284  User can use below command to change the (% style="color:green" %)**uplink interval**.
285 285  
286 286  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
287 287  
288 288  (((
289 -(% style="color:red" %)**NOTE:**
290 -)))
335 +(% style="color:red" %)**NOTE 1: By default, the device will send an uplink message every 1 hour.**
291 291  
292 -(((
293 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
337 +
294 294  )))
295 295  
340 +(% style="color:red" %)**NOTE 2: When the firmware version is v1.3.2 and later firmware:**
296 296  
342 +(% style="color:red" %)**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).**
297 297  
344 +
345 +
298 298  == 2.3  Uplink Payload ==
299 299  
300 -In this mode, uplink payload includes in total 14 bytes
301 301  
349 +=== 2.3.1  Before Firmware 1.3.2 ===
302 302  
303 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
304 -|=(% style="width: 80px;" %)(((
351 +
352 +In this mode, uplink payload includes in total 14 bytes
353 +
354 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
355 +|=(% style="width: 60px;" %)(((
305 305  **Size(bytes)**
306 -)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1**
357 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
307 307  |(% 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"]]
308 308  
309 309  (((
... ... @@ -313,8 +313,9 @@
313 313  
314 314  [[image:1657331036973-987.png]]
315 315  
367 +
316 316  (((
317 -The payload is ASCII string, representative same HEX:
369 +The payload is **ASCII** string, representative same HEX:
318 318  )))
319 319  
320 320  (((
... ... @@ -325,11 +325,11 @@
325 325  Device ID: 0x724031556159 = 724031556159
326 326  )))
327 327  * (((
328 -Version: 0x0064=100=1.0.0
380 +Version:  0x0064=100=1.0.0
329 329  )))
330 330  
331 331  * (((
332 -BAT: 0x0c6c = 3180 mV = 3.180V
384 +BAT:  0x0c6c = 3180 mV = 3.180V
333 333  )))
334 334  * (((
335 335  Signal: 0x19 = 25
... ... @@ -342,14 +342,51 @@
342 342  
343 343  
344 344  
397 +
345 345  
346 346  )))
347 347  
401 +=== **2.3.2  Since firmware v1.3.2** ===
402 +
403 +
404 +In this mode, uplink payload includes 69 bytes in total by default.
405 +
406 +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.
407 +
408 +(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
409 +|(% style="width:95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)4
410 +|(% style="width:95px" %)**Value**|(% style="width:84px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:48px" %)BAT|(% style="width:123px" %)Signal Strength|(% style="width:55px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:77px" %)Distance|(% style="width:94px" %)Timestamp|(% style="width:77px" %)Distance|(% style="width:116px" %)Timestamp.......
411 +
412 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
413 +
414 +[[image:image-20220908175246-1.png]]
415 +
416 +
417 +The payload is ASCII string, representative same HEX:
418 +
419 +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:
420 +
421 +* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
422 +* (% style="color:red" %)Version: 0x0084=132=1.3.2
423 +* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
424 +* (% style="color:blue" %)Singal: 0x1e = 30
425 +* (% style="color:red" %)Mod: 0x01 = 1
426 +* Interrupt: 0x00= 0
427 +* Distance: 0x0039= 57 = 57
428 +* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
429 +* Distance,Time stamp : 00396319baf0
430 +* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
431 +
432 +
433 +
434 +
435 +
348 348  == 2.4  Payload Explanation and Sensor Interface ==
349 349  
350 350  
351 351  === 2.4.1  Device ID ===
352 352  
441 +
353 353  (((
354 354  By default, the Device ID equal to the last 6 bytes of IMEI.
355 355  )))
... ... @@ -356,10 +356,12 @@
356 356  
357 357  (((
358 358  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
448 +
449 +
359 359  )))
360 360  
361 361  (((
362 -**Example:**
453 +(% style="color:blue" %)**Example :**
363 363  )))
364 364  
365 365  (((
... ... @@ -367,13 +367,26 @@
367 367  )))
368 368  
369 369  (((
370 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
461 +The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
371 371  )))
372 372  
373 373  
465 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
374 374  
467 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
468 +
469 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
470 +
471 +
472 +(% style="color:blue" %)**Example :**
473 +
474 +AT+DEUI=868411056754138
475 +
476 +
477 +
375 375  === 2.4.2  Version Info ===
376 376  
480 +
377 377  (((
378 378  Specify the software version: 0x64=100, means firmware version 1.00.
379 379  )))
... ... @@ -386,9 +386,6 @@
386 386  
387 387  === 2.4.3  Battery Info ===
388 388  
389 -(((
390 -Check the battery voltage for LSE01.
391 -)))
392 392  
393 393  (((
394 394  Ex1: 0x0B45 = 2885mV
... ... @@ -402,6 +402,7 @@
402 402  
403 403  === 2.4.4  Signal Strength ===
404 404  
506 +
405 405  (((
406 406  NB-IoT Network signal Strength.
407 407  )))
... ... @@ -434,9 +434,12 @@
434 434  
435 435  === 2.4.5  Distance ===
436 436  
539 +
437 437  Get the distance. Flat object range 280mm - 7500mm.
438 438  
542 +(((
439 439  For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
544 +)))
440 440  
441 441  (((
442 442  (((
... ... @@ -454,6 +454,7 @@
454 454  
455 455  === 2.4.6  Digital Interrupt ===
456 456  
562 +
457 457  (((
458 458  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.
459 459  )))
... ... @@ -488,6 +488,7 @@
488 488  
489 489  === 2.4.7  ​+5V Output ===
490 490  
597 +
491 491  (((
492 492  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
493 493  )))
... ... @@ -495,10 +495,14 @@
495 495  
496 496  (((
497 497  The 5V output time can be controlled by AT Command.
605 +
606 +
498 498  )))
499 499  
500 500  (((
501 501  (% style="color:blue" %)**AT+5VT=1000**
611 +
612 +
502 502  )))
503 503  
504 504  (((
... ... @@ -509,6 +509,7 @@
509 509  
510 510  == 2.5  Downlink Payload ==
511 511  
623 +
512 512  By default, NDDS75 prints the downlink payload to console port.
513 513  
514 514  [[image:image-20220709100028-1.png]]
... ... @@ -559,9 +559,55 @@
559 559  
560 560  
561 561  
562 -== 2.6  ​LED Indicator ==
674 +== 2.6  Distance alarm function(Since firmware v1.3.2) ==
563 563  
564 564  
677 +(% style="color:blue" %)** ➢ AT Command:**
678 +
679 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
680 +
681 +² When min=0, and max≠0, Alarm higher than max
682 +
683 +² When min≠0, and max=0, Alarm lower than min
684 +
685 +² When min≠0 and max≠0, Alarm higher than max or lower than min
686 +
687 +
688 +(% style="color:blue" %)** Example:**
689 +
690 +**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
691 +
692 +
693 +
694 +== 2.7  Set the number of data to be uploaded and the recording time ==
695 +
696 +
697 +(% style="color:blue" %)** ➢ AT Command:**
698 +
699 +(% style="color:#037691" %)** 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)
700 +
701 +(% style="color:#037691" %)** AT+NOUD=8** (%%) ~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
702 +
703 +
704 +
705 +== 2.8  Read or Clear cached data ==
706 +
707 +
708 +(% style="color:blue" %)** ➢ AT Command:**
709 +
710 +(% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data
711 +
712 +
713 +[[image:image-20220908175333-2.png]]
714 +
715 +
716 +(% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/ Clear cached data
717 +
718 +
719 +
720 +== 2.9  ​LED Indicator ==
721 +
722 +
565 565  The NDDS75 has an internal LED which is to show the status of different state.
566 566  
567 567  
... ... @@ -576,23 +576,27 @@
576 576  
577 577  
578 578  
579 -== 2.7  ​Firmware Change Log ==
737 +== 2.10  ​Firmware Change Log ==
580 580  
581 581  
582 -Download URL & Firmware Change log
740 +(((
741 +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]]
742 +)))
583 583  
584 584  (((
585 -[[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/]]
745 +
586 586  )))
587 587  
748 +(((
749 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
750 +)))
588 588  
589 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
590 590  
591 591  
754 +== 2.11  ​Battery Analysis ==
592 592  
593 -== 2.8  ​Battery Analysis ==
594 594  
595 -=== 2.8.1  ​Battery Type ===
757 +=== 2.11.1  ​Battery Type ===
596 596  
597 597  
598 598  (((
... ... @@ -617,8 +617,9 @@
617 617  
618 618  
619 619  
620 -=== 2.8.2  Power consumption Analyze ===
782 +=== 2.11.2  Power consumption Analyze ===
621 621  
784 +
622 622  (((
623 623  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.
624 624  )))
... ... @@ -655,8 +655,9 @@
655 655  
656 656  
657 657  
658 -=== 2.8.3  ​Battery Note ===
821 +=== 2.11.3  ​Battery Note ===
659 659  
823 +
660 660  (((
661 661  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.
662 662  )))
... ... @@ -663,8 +663,9 @@
663 663  
664 664  
665 665  
666 -=== 2.8.4  Replace the battery ===
830 +=== 2.11.4  Replace the battery ===
667 667  
832 +
668 668  (((
669 669  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).
670 670  )))
... ... @@ -673,6 +673,7 @@
673 673  
674 674  = 3. ​ Access NB-IoT Module =
675 675  
841 +
676 676  (((
677 677  Users can directly access the AT command set of the NB-IoT module.
678 678  )))
... ... @@ -679,6 +679,8 @@
679 679  
680 680  (((
681 681  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/]] 
848 +
849 +
682 682  )))
683 683  
684 684  [[image:1657333200519-600.png]]
... ... @@ -687,11 +687,13 @@
687 687  
688 688  = 4.  Using the AT Commands =
689 689  
858 +
690 690  == 4.1  Access AT Commands ==
691 691  
692 -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/]]
693 693  
862 +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]]
694 694  
864 +
695 695  AT+<CMD>?  : Help on <CMD>
696 696  
697 697  AT+<CMD>         : Run <CMD>
... ... @@ -731,7 +731,23 @@
731 731  
732 732  AT+SERVADDR  : Server Address
733 733  
904 +AT+TR      : Get or Set record time"
734 734  
906 +AT+APN     : Get or set the APN
907 +
908 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
909 +
910 +AT+DNSCFG  : Get or Set DNS Server
911 +
912 +AT+GETSENSORVALUE   : Returns the current sensor measurement
913 +
914 +AT+NOUD      : Get or Set the number of data to be uploaded
915 +
916 +AT+CDP     : Read or Clear cached data
917 +
918 +AT+LDDSALARM : Get or Set alarm of distance
919 +
920 +
735 735  (% style="color:#037691" %)**COAP Management**      
736 736  
737 737  AT+URI            : Resource parameters
... ... @@ -765,6 +765,7 @@
765 765  
766 766  = ​5.  FAQ =
767 767  
954 +
768 768  == 5.1 ​ How to Upgrade Firmware ==
769 769  
770 770  
... ... @@ -777,7 +777,7 @@
777 777  )))
778 778  
779 779  (((
780 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
967 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
781 781  )))
782 782  
783 783  
... ... @@ -784,6 +784,7 @@
784 784  
785 785  = 6.  Trouble Shooting =
786 786  
974 +
787 787  == 6.1  ​Connection problem when uploading firmware ==
788 788  
789 789  
... ... @@ -799,6 +799,7 @@
799 799  
800 800  == 6.2  AT Command input doesn't work ==
801 801  
990 +
802 802  (((
803 803  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.
804 804  
... ... @@ -824,7 +824,7 @@
824 824  
825 825  (% style="color:#037691" %)**Package Includes**:
826 826  
827 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
1016 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1
828 828  * External antenna x 1
829 829  )))
830 830  
... ... @@ -831,9 +831,9 @@
831 831  (((
832 832  
833 833  
1023 +
834 834  (% style="color:#037691" %)**Dimension and weight**:
835 835  
836 -
837 837  * Device Size: 13.0 x 5 x 4.5 cm
838 838  * Device Weight: 150g
839 839  * Package Size / pcs : 15 x 12x 5.5 cm
... ... @@ -849,5 +849,6 @@
849 849  
850 850  = 9.  Support =
851 851  
1041 +
852 852  * 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.
853 853  * 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-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

Applications

Navigation

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