Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 97.2 >
edited by Xiaoling
on 2022/07/09 11:09
To version < 104.2 >
edited by Xiaoling
on 2022/09/09 10:26
>
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,20 +22,34 @@
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  
33 -
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.
34 34  )))
35 35  
36 -[[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 +)))
37 37  
38 +(((
39 +NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
40 +)))
38 38  
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 +
39 39  [[image:1657327959271-447.png]]
40 40  
41 41  
... ... @@ -57,7 +57,6 @@
57 57  * 8500mAh Battery for long term use
58 58  
59 59  
60 -
61 61  == 1.3  Specification ==
62 62  
63 63  
... ... @@ -86,12 +86,12 @@
86 86  (% style="color:#037691" %)**Power Consumption**
87 87  
88 88  * STOP Mode: 10uA @ 3.3v
89 -* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
103 +* Max transmit power: 350mA@3.3v
90 90  
91 91  
92 -
93 93  == ​1.4  Applications ==
94 94  
108 +
95 95  * Smart Buildings & Home Automation
96 96  * Logistics and Supply Chain Management
97 97  * Smart Metering
... ... @@ -104,6 +104,7 @@
104 104  
105 105  
106 106  
121 +
107 107  == 1.5  Pin Definitions ==
108 108  
109 109  
... ... @@ -113,8 +113,10 @@
113 113  
114 114  = 2.  Use NDDS75 to communicate with IoT Server =
115 115  
131 +
116 116  == 2.1  How it works ==
117 117  
134 +
118 118  (((
119 119  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.
120 120  )))
... ... @@ -140,16 +140,17 @@
140 140  
141 141  === 2.2.1 Test Requirement ===
142 142  
160 +
143 143  (((
144 144  To use NDDS75 in your city, make sure meet below requirements:
145 145  )))
146 146  
147 147  * Your local operator has already distributed a NB-IoT Network there.
148 -* The local NB-IoT network used the band that NSE01 supports.
166 +* The local NB-IoT network used the band that NDDS75 supports.
149 149  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
150 150  
151 151  (((
152 -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
170 +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.
153 153  )))
154 154  
155 155  
... ... @@ -159,6 +159,7 @@
159 159  
160 160  === 2.2.2 Insert SIM card ===
161 161  
180 +
162 162  (((
163 163  Insert the NB-IoT Card get from your provider.
164 164  )))
... ... @@ -174,6 +174,7 @@
174 174  
175 175  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
176 176  
196 +
177 177  (((
178 178  (((
179 179  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.
... ... @@ -182,6 +182,7 @@
182 182  
183 183  [[image:image-20220709092052-2.png]]
184 184  
205 +
185 185  **Connection:**
186 186  
187 187   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -205,8 +205,9 @@
205 205  
206 206  [[image:1657329814315-101.png]]
207 207  
229 +
208 208  (((
209 -(% 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/]]
231 +(% 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]]**
210 210  )))
211 211  
212 212  
... ... @@ -213,22 +213,43 @@
213 213  
214 214  === 2.2.4 Use CoAP protocol to uplink data ===
215 215  
216 -(% 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/]]
217 217  
239 +(% 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/]]**
218 218  
241 +
242 +(((
219 219  **Use below commands:**
244 +)))
220 220  
221 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
222 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
223 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
246 +* (((
247 +(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
248 +)))
249 +* (((
250 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
251 +)))
252 +* (((
253 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
224 224  
255 +
256 +
257 +)))
258 +
259 +(((
225 225  For parameter description, please refer to AT command set
226 226  
262 +
263 +)))
264 +
227 227  [[image:1657330452568-615.png]]
228 228  
229 229  
268 +
269 +(((
230 230  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.
231 231  
272 +
273 +)))
274 +
232 232  [[image:1657330472797-498.png]]
233 233  
234 234  
... ... @@ -236,9 +236,9 @@
236 236  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
237 237  
238 238  
239 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
282 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
240 240  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
241 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
284 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
242 242  
243 243  [[image:1657330501006-241.png]]
244 244  
... ... @@ -250,11 +250,11 @@
250 250  === 2.2.6 Use MQTT protocol to uplink data ===
251 251  
252 252  
253 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
254 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
255 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
256 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
257 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
296 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
297 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
298 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
299 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
300 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
258 258  * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
259 259  * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
260 260  
... ... @@ -285,29 +285,35 @@
285 285  
286 286  === 2.2.8 Change Update Interval ===
287 287  
331 +
288 288  User can use below command to change the (% style="color:green" %)**uplink interval**.
289 289  
290 290  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
291 291  
292 292  (((
293 -(% style="color:red" %)**NOTE:**
294 -)))
337 +(% style="color:red" %)**NOTE 1: By default, the device will send an uplink message every 1 hour.**
295 295  
296 -(((
297 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
339 +
298 298  )))
299 299  
342 +(% style="color:red" %)**NOTE 2: When the firmware version is v1.3.2 and later firmware:**
300 300  
344 +(% 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).**
301 301  
346 +
347 +
302 302  == 2.3  Uplink Payload ==
303 303  
304 -In this mode, uplink payload includes in total 14 bytes
305 305  
351 +=== 2.3.1  Before Firmware 1.3.2 ===
306 306  
307 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
308 -|=(% style="width: 80px;" %)(((
353 +
354 +In this mode, uplink payload includes in total 14 bytes
355 +
356 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
357 +|=(% style="width: 60px;" %)(((
309 309  **Size(bytes)**
310 -)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1**
359 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
311 311  |(% 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"]]
312 312  
313 313  (((
... ... @@ -317,8 +317,9 @@
317 317  
318 318  [[image:1657331036973-987.png]]
319 319  
369 +
320 320  (((
321 -The payload is ASCII string, representative same HEX:
371 +The payload is **ASCII** string, representative same HEX:
322 322  )))
323 323  
324 324  (((
... ... @@ -329,11 +329,11 @@
329 329  Device ID: 0x724031556159 = 724031556159
330 330  )))
331 331  * (((
332 -Version: 0x0064=100=1.0.0
382 +Version:  0x0064=100=1.0.0
333 333  )))
334 334  
335 335  * (((
336 -BAT: 0x0c6c = 3180 mV = 3.180V
386 +BAT:  0x0c6c = 3180 mV = 3.180V
337 337  )))
338 338  * (((
339 339  Signal: 0x19 = 25
... ... @@ -346,14 +346,48 @@
346 346  
347 347  
348 348  
399 +
349 349  
350 350  )))
351 351  
403 +=== **2.3.2  Since firmware v1.3.2** ===
404 +
405 +
406 +In this mode, uplink payload includes 69 bytes in total by default.
407 +
408 +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.
409 +
410 +(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
411 +|(% 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
412 +|(% 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.......
413 +
414 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
415 +
416 +[[image:image-20220908175246-1.png]]
417 +
418 +
419 +The payload is ASCII string, representative same HEX:
420 +
421 +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:
422 +
423 +* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
424 +* (% style="color:red" %)Version: 0x0084=132=1.3.2
425 +* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
426 +* (% style="color:blue" %)Singal: 0x1e = 30
427 +* (% style="color:red" %)Mod: 0x01 = 1
428 +* Interrupt: 0x00= 0
429 +* Distance: 0x0039= 57 = 57
430 +* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
431 +* Distance,Time stamp : 00396319baf0
432 +* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
433 +
434 +
352 352  == 2.4  Payload Explanation and Sensor Interface ==
353 353  
354 354  
355 355  === 2.4.1  Device ID ===
356 356  
440 +
357 357  (((
358 358  By default, the Device ID equal to the last 6 bytes of IMEI.
359 359  )))
... ... @@ -360,10 +360,12 @@
360 360  
361 361  (((
362 362  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
447 +
448 +
363 363  )))
364 364  
365 365  (((
366 -**Example:**
452 +(% style="color:blue" %)**Example :**
367 367  )))
368 368  
369 369  (((
... ... @@ -371,13 +371,26 @@
371 371  )))
372 372  
373 373  (((
374 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
460 +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.
375 375  )))
376 376  
377 377  
464 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
378 378  
466 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
467 +
468 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
469 +
470 +
471 +(% style="color:blue" %)**Example :**
472 +
473 +AT+DEUI=868411056754138
474 +
475 +
476 +
379 379  === 2.4.2  Version Info ===
380 380  
479 +
381 381  (((
382 382  Specify the software version: 0x64=100, means firmware version 1.00.
383 383  )))
... ... @@ -390,9 +390,6 @@
390 390  
391 391  === 2.4.3  Battery Info ===
392 392  
393 -(((
394 -Check the battery voltage for LSE01.
395 -)))
396 396  
397 397  (((
398 398  Ex1: 0x0B45 = 2885mV
... ... @@ -406,6 +406,7 @@
406 406  
407 407  === 2.4.4  Signal Strength ===
408 408  
505 +
409 409  (((
410 410  NB-IoT Network signal Strength.
411 411  )))
... ... @@ -438,9 +438,12 @@
438 438  
439 439  === 2.4.5  Distance ===
440 440  
538 +
441 441  Get the distance. Flat object range 280mm - 7500mm.
442 442  
541 +(((
443 443  For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
543 +)))
444 444  
445 445  (((
446 446  (((
... ... @@ -458,6 +458,7 @@
458 458  
459 459  === 2.4.6  Digital Interrupt ===
460 460  
561 +
461 461  (((
462 462  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.
463 463  )))
... ... @@ -492,6 +492,7 @@
492 492  
493 493  === 2.4.7  ​+5V Output ===
494 494  
596 +
495 495  (((
496 496  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
497 497  )))
... ... @@ -499,10 +499,14 @@
499 499  
500 500  (((
501 501  The 5V output time can be controlled by AT Command.
604 +
605 +
502 502  )))
503 503  
504 504  (((
505 505  (% style="color:blue" %)**AT+5VT=1000**
610 +
611 +
506 506  )))
507 507  
508 508  (((
... ... @@ -513,6 +513,7 @@
513 513  
514 514  == 2.5  Downlink Payload ==
515 515  
622 +
516 516  By default, NDDS75 prints the downlink payload to console port.
517 517  
518 518  [[image:image-20220709100028-1.png]]
... ... @@ -563,9 +563,55 @@
563 563  
564 564  
565 565  
566 -== 2.6  ​LED Indicator ==
673 +== 2.6  Distance alarm function(Since firmware v1.3.2) ==
567 567  
568 568  
676 +(% style="color:blue" %)** ➢ AT Command:**
677 +
678 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
679 +
680 +² When min=0, and max≠0, Alarm higher than max
681 +
682 +² When min≠0, and max=0, Alarm lower than min
683 +
684 +² When min≠0 and max≠0, Alarm higher than max or lower than min
685 +
686 +
687 +(% style="color:blue" %)** Example:**
688 +
689 +**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
690 +
691 +
692 +
693 +== 2.7  Set the number of data to be uploaded and the recording time ==
694 +
695 +
696 +(% style="color:blue" %)** ➢ AT Command:**
697 +
698 +(% 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)
699 +
700 +(% 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.
701 +
702 +
703 +
704 +== 2.8  Read or Clear cached data ==
705 +
706 +
707 +(% style="color:blue" %)** ➢ AT Command:**
708 +
709 +(% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data
710 +
711 +
712 +[[image:image-20220908175333-2.png]]
713 +
714 +
715 +(% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/ Clear cached data
716 +
717 +
718 +
719 +== 2.9  ​LED Indicator ==
720 +
721 +
569 569  The NDDS75 has an internal LED which is to show the status of different state.
570 570  
571 571  
... ... @@ -580,23 +580,27 @@
580 580  
581 581  
582 582  
583 -== 2.7  ​Firmware Change Log ==
736 +== 2.10  ​Firmware Change Log ==
584 584  
585 585  
586 -Download URL & Firmware Change log
739 +(((
740 +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]]
741 +)))
587 587  
588 588  (((
589 -[[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/]]
744 +
590 590  )))
591 591  
747 +(((
748 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
749 +)))
592 592  
593 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
594 594  
595 595  
753 +== 2.11  ​Battery Analysis ==
596 596  
597 -== 2.8  ​Battery Analysis ==
598 598  
599 -=== 2.8.1  ​Battery Type ===
756 +=== 2.11.1  ​Battery Type ===
600 600  
601 601  
602 602  (((
... ... @@ -621,8 +621,9 @@
621 621  
622 622  
623 623  
624 -=== 2.8.2  Power consumption Analyze ===
781 +=== 2.11.2  Power consumption Analyze ===
625 625  
783 +
626 626  (((
627 627  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.
628 628  )))
... ... @@ -659,8 +659,9 @@
659 659  
660 660  
661 661  
662 -=== 2.8.3  ​Battery Note ===
820 +=== 2.11.3  ​Battery Note ===
663 663  
822 +
664 664  (((
665 665  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.
666 666  )))
... ... @@ -667,8 +667,9 @@
667 667  
668 668  
669 669  
670 -=== 2.8.4  Replace the battery ===
829 +=== 2.11.4  Replace the battery ===
671 671  
831 +
672 672  (((
673 673  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).
674 674  )))
... ... @@ -677,6 +677,7 @@
677 677  
678 678  = 3. ​ Access NB-IoT Module =
679 679  
840 +
680 680  (((
681 681  Users can directly access the AT command set of the NB-IoT module.
682 682  )))
... ... @@ -683,6 +683,8 @@
683 683  
684 684  (((
685 685  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/]] 
847 +
848 +
686 686  )))
687 687  
688 688  [[image:1657333200519-600.png]]
... ... @@ -691,11 +691,13 @@
691 691  
692 692  = 4.  Using the AT Commands =
693 693  
857 +
694 694  == 4.1  Access AT Commands ==
695 695  
696 -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/]]
697 697  
861 +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]]
698 698  
863 +
699 699  AT+<CMD>?  : Help on <CMD>
700 700  
701 701  AT+<CMD>         : Run <CMD>
... ... @@ -735,7 +735,23 @@
735 735  
736 736  AT+SERVADDR  : Server Address
737 737  
903 +AT+TR      : Get or Set record time"
738 738  
905 +AT+APN     : Get or set the APN
906 +
907 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
908 +
909 +AT+DNSCFG  : Get or Set DNS Server
910 +
911 +AT+GETSENSORVALUE   : Returns the current sensor measurement
912 +
913 +AT+NOUD      : Get or Set the number of data to be uploaded
914 +
915 +AT+CDP     : Read or Clear cached data
916 +
917 +AT+LDDSALARM : Get or Set alarm of distance
918 +
919 +
739 739  (% style="color:#037691" %)**COAP Management**      
740 740  
741 741  AT+URI            : Resource parameters
... ... @@ -769,6 +769,7 @@
769 769  
770 770  = ​5.  FAQ =
771 771  
953 +
772 772  == 5.1 ​ How to Upgrade Firmware ==
773 773  
774 774  
... ... @@ -781,7 +781,7 @@
781 781  )))
782 782  
783 783  (((
784 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
966 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
785 785  )))
786 786  
787 787  
... ... @@ -788,6 +788,7 @@
788 788  
789 789  = 6.  Trouble Shooting =
790 790  
973 +
791 791  == 6.1  ​Connection problem when uploading firmware ==
792 792  
793 793  
... ... @@ -803,6 +803,7 @@
803 803  
804 804  == 6.2  AT Command input doesn't work ==
805 805  
989 +
806 806  (((
807 807  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.
808 808  
... ... @@ -828,7 +828,7 @@
828 828  
829 829  (% style="color:#037691" %)**Package Includes**:
830 830  
831 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
1015 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1
832 832  * External antenna x 1
833 833  )))
834 834  
... ... @@ -835,9 +835,9 @@
835 835  (((
836 836  
837 837  
1022 +
838 838  (% style="color:#037691" %)**Dimension and weight**:
839 839  
840 -
841 841  * Device Size: 13.0 x 5 x 4.5 cm
842 842  * Device Weight: 150g
843 843  * Package Size / pcs : 15 x 12x 5.5 cm
... ... @@ -853,5 +853,6 @@
853 853  
854 854  = 9.  Support =
855 855  
1040 +
856 856  * 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.
857 857  * 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