Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 97.11 >
edited by Xiaoling
on 2022/07/09 11:31
To version < 104.6 >
edited by Xiaoling
on 2022/09/09 13:35
>
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  
... ... @@ -55,6 +55,8 @@
55 55  
56 56  
57 57  
76 +
77 +
58 58  == 1.3  Specification ==
59 59  
60 60  
... ... @@ -87,8 +87,11 @@
87 87  
88 88  
89 89  
110 +
111 +
90 90  == ​1.4  Applications ==
91 91  
114 +
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  
126 +
127 +
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  
137 +
112 112  == 2.1  How it works ==
113 113  
140 +
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  
166 +
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.
172 +* 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
176 +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  
186 +
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  
202 +
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  
211 +
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  
235 +
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/]]
237 +(% 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,9 +209,10 @@
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  
245 +(% 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  
247 +
215 215  (((
216 216  **Use below commands:**
217 217  )))
... ... @@ -224,17 +224,25 @@
224 224  )))
225 225  * (((
226 226  (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
260 +
261 +
262 +
227 227  )))
228 228  
229 229  (((
230 230  For parameter description, please refer to AT command set
267 +
268 +
231 231  )))
232 232  
233 233  [[image:1657330452568-615.png]]
234 234  
235 235  
274 +
236 236  (((
237 237  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.
277 +
278 +
238 238  )))
239 239  
240 240  [[image:1657330472797-498.png]]
... ... @@ -261,8 +261,8 @@
261 261  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
262 262  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
263 263  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
264 -* (% style="color:blue" %)**AT+UNAME=UNAME  **(%%)~/~/Set the username of MQTT
265 -* (% style="color:blue" %)**AT+PWD=PWD  **(%%)~/~/Set the password of MQTT
305 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
306 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
266 266  * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
267 267  * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
268 268  
... ... @@ -293,29 +293,38 @@
293 293  
294 294  === 2.2.8 Change Update Interval ===
295 295  
337 +
296 296  User can use below command to change the (% style="color:green" %)**uplink interval**.
297 297  
298 298  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
299 299  
300 300  (((
343 +
344 +
345 +
301 301  (% style="color:red" %)**NOTE:**
302 -)))
303 303  
304 -(((
305 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
348 +(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
349 +
350 +(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
306 306  )))
307 307  
353 +(% 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).**
308 308  
309 309  
356 +
310 310  == 2.3  Uplink Payload ==
311 311  
312 -In this mode, uplink payload includes in total 14 bytes
313 313  
360 +=== 2.3.1  Before Firmware 1.3.2 ===
314 314  
315 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
316 -|=(% style="width: 80px;" %)(((
362 +
363 +In this mode, uplink payload includes in total 14 bytes
364 +
365 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
366 +|=(% style="width: 60px;" %)(((
317 317  **Size(bytes)**
318 -)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1**
368 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
319 319  |(% 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"]]
320 320  
321 321  (((
... ... @@ -325,8 +325,9 @@
325 325  
326 326  [[image:1657331036973-987.png]]
327 327  
378 +
328 328  (((
329 -The payload is ASCII string, representative same HEX:
380 +The payload is **ASCII** string, representative same HEX:
330 330  )))
331 331  
332 332  (((
... ... @@ -337,11 +337,11 @@
337 337  Device ID: 0x724031556159 = 724031556159
338 338  )))
339 339  * (((
340 -Version: 0x0064=100=1.0.0
391 +Version:  0x0064=100=1.0.0
341 341  )))
342 342  
343 343  * (((
344 -BAT: 0x0c6c = 3180 mV = 3.180V
395 +BAT:  0x0c6c = 3180 mV = 3.180V
345 345  )))
346 346  * (((
347 347  Signal: 0x19 = 25
... ... @@ -354,14 +354,51 @@
354 354  
355 355  
356 356  
408 +
357 357  
358 358  )))
359 359  
412 +=== **2.3.2  Since firmware v1.3.2** ===
413 +
414 +
415 +In this mode, uplink payload includes 69 bytes in total by default.
416 +
417 +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.
418 +
419 +(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
420 +|(% 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
421 +|(% 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.......
422 +
423 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
424 +
425 +[[image:image-20220908175246-1.png]]
426 +
427 +
428 +The payload is ASCII string, representative same HEX:
429 +
430 +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:
431 +
432 +* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
433 +* (% style="color:red" %)Version: 0x0084=132=1.3.2
434 +* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
435 +* (% style="color:blue" %)Singal: 0x1e = 30
436 +* (% style="color:red" %)Mod: 0x01 = 1
437 +* Interrupt: 0x00= 0
438 +* Distance: 0x0039= 57 = 57
439 +* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
440 +* Distance,Time stamp : 00396319baf0
441 +* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
442 +
443 +
444 +
445 +
446 +
360 360  == 2.4  Payload Explanation and Sensor Interface ==
361 361  
362 362  
363 363  === 2.4.1  Device ID ===
364 364  
452 +
365 365  (((
366 366  By default, the Device ID equal to the last 6 bytes of IMEI.
367 367  )))
... ... @@ -368,10 +368,12 @@
368 368  
369 369  (((
370 370  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
459 +
460 +
371 371  )))
372 372  
373 373  (((
374 -**Example:**
464 +(% style="color:blue" %)**Example :**
375 375  )))
376 376  
377 377  (((
... ... @@ -379,13 +379,26 @@
379 379  )))
380 380  
381 381  (((
382 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
472 +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.
383 383  )))
384 384  
385 385  
476 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
386 386  
478 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
479 +
480 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
481 +
482 +
483 +(% style="color:blue" %)**Example :**
484 +
485 +AT+DEUI=868411056754138
486 +
487 +
488 +
387 387  === 2.4.2  Version Info ===
388 388  
491 +
389 389  (((
390 390  Specify the software version: 0x64=100, means firmware version 1.00.
391 391  )))
... ... @@ -398,6 +398,7 @@
398 398  
399 399  === 2.4.3  Battery Info ===
400 400  
504 +
401 401  (((
402 402  Ex1: 0x0B45 = 2885mV
403 403  )))
... ... @@ -410,6 +410,7 @@
410 410  
411 411  === 2.4.4  Signal Strength ===
412 412  
517 +
413 413  (((
414 414  NB-IoT Network signal Strength.
415 415  )))
... ... @@ -442,9 +442,12 @@
442 442  
443 443  === 2.4.5  Distance ===
444 444  
550 +
445 445  Get the distance. Flat object range 280mm - 7500mm.
446 446  
553 +(((
447 447  For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
555 +)))
448 448  
449 449  (((
450 450  (((
... ... @@ -462,6 +462,7 @@
462 462  
463 463  === 2.4.6  Digital Interrupt ===
464 464  
573 +
465 465  (((
466 466  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.
467 467  )))
... ... @@ -496,6 +496,7 @@
496 496  
497 497  === 2.4.7  ​+5V Output ===
498 498  
608 +
499 499  (((
500 500  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
501 501  )))
... ... @@ -503,10 +503,14 @@
503 503  
504 504  (((
505 505  The 5V output time can be controlled by AT Command.
616 +
617 +
506 506  )))
507 507  
508 508  (((
509 509  (% style="color:blue" %)**AT+5VT=1000**
622 +
623 +
510 510  )))
511 511  
512 512  (((
... ... @@ -517,6 +517,7 @@
517 517  
518 518  == 2.5  Downlink Payload ==
519 519  
634 +
520 520  By default, NDDS75 prints the downlink payload to console port.
521 521  
522 522  [[image:image-20220709100028-1.png]]
... ... @@ -567,9 +567,54 @@
567 567  
568 568  
569 569  
570 -== 2.6  ​LED Indicator ==
685 +== 2.6  Distance alarm function(Since firmware v1.3.2) ==
571 571  
572 572  
688 +(% style="color:blue" %)** ➢ AT Command:**
689 +
690 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
691 +
692 +² When min=0, and max≠0, Alarm higher than max
693 +
694 +² When min≠0, and max=0, Alarm lower than min
695 +
696 +² When min≠0 and max≠0, Alarm higher than max or lower than min
697 +
698 +
699 +(% style="color:blue" %)** Example:**
700 +
701 +**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
702 +
703 +
704 +
705 +== 2.7  Set the number of data to be uploaded and the recording time ==
706 +
707 +
708 +(% style="color:blue" %)** ➢ AT Command:**
709 +
710 +* (% 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)
711 +* (% 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.
712 +
713 +
714 +
715 +
716 +== 2.8  Read or Clear cached data ==
717 +
718 +
719 +(% style="color:blue" %)** ➢ AT Command:**
720 +
721 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data
722 +* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
723 +
724 +
725 +
726 +[[image:image-20220908175333-2.png]]
727 +
728 +
729 +
730 +== 2.9  ​LED Indicator ==
731 +
732 +
573 573  The NDDS75 has an internal LED which is to show the status of different state.
574 574  
575 575  
... ... @@ -584,23 +584,27 @@
584 584  
585 585  
586 586  
587 -== 2.7  ​Firmware Change Log ==
747 +== 2.10  ​Firmware Change Log ==
588 588  
589 589  
590 -Download URL & Firmware Change log
750 +(((
751 +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]]
752 +)))
591 591  
592 592  (((
593 -[[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/]]
755 +
594 594  )))
595 595  
758 +(((
759 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
760 +)))
596 596  
597 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
598 598  
599 599  
764 +== 2.11  ​Battery Analysis ==
600 600  
601 -== 2.8  ​Battery Analysis ==
602 602  
603 -=== 2.8.1  ​Battery Type ===
767 +=== 2.11.1  ​Battery Type ===
604 604  
605 605  
606 606  (((
... ... @@ -625,8 +625,9 @@
625 625  
626 626  
627 627  
628 -=== 2.8.2  Power consumption Analyze ===
792 +=== 2.11.2  Power consumption Analyze ===
629 629  
794 +
630 630  (((
631 631  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.
632 632  )))
... ... @@ -663,8 +663,9 @@
663 663  
664 664  
665 665  
666 -=== 2.8.3  ​Battery Note ===
831 +=== 2.11.3  ​Battery Note ===
667 667  
833 +
668 668  (((
669 669  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.
670 670  )))
... ... @@ -671,8 +671,9 @@
671 671  
672 672  
673 673  
674 -=== 2.8.4  Replace the battery ===
840 +=== 2.11.4  Replace the battery ===
675 675  
842 +
676 676  (((
677 677  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).
678 678  )))
... ... @@ -681,6 +681,7 @@
681 681  
682 682  = 3. ​ Access NB-IoT Module =
683 683  
851 +
684 684  (((
685 685  Users can directly access the AT command set of the NB-IoT module.
686 686  )))
... ... @@ -687,6 +687,8 @@
687 687  
688 688  (((
689 689  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/]] 
858 +
859 +
690 690  )))
691 691  
692 692  [[image:1657333200519-600.png]]
... ... @@ -695,11 +695,13 @@
695 695  
696 696  = 4.  Using the AT Commands =
697 697  
868 +
698 698  == 4.1  Access AT Commands ==
699 699  
700 -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/]]
701 701  
872 +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]]
702 702  
874 +
703 703  AT+<CMD>?  : Help on <CMD>
704 704  
705 705  AT+<CMD>         : Run <CMD>
... ... @@ -739,7 +739,23 @@
739 739  
740 740  AT+SERVADDR  : Server Address
741 741  
914 +AT+TR      : Get or Set record time"
742 742  
916 +AT+APN     : Get or set the APN
917 +
918 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
919 +
920 +AT+DNSCFG  : Get or Set DNS Server
921 +
922 +AT+GETSENSORVALUE   : Returns the current sensor measurement
923 +
924 +AT+NOUD      : Get or Set the number of data to be uploaded
925 +
926 +AT+CDP     : Read or Clear cached data
927 +
928 +AT+LDDSALARM : Get or Set alarm of distance
929 +
930 +
743 743  (% style="color:#037691" %)**COAP Management**      
744 744  
745 745  AT+URI            : Resource parameters
... ... @@ -773,6 +773,7 @@
773 773  
774 774  = ​5.  FAQ =
775 775  
964 +
776 776  == 5.1 ​ How to Upgrade Firmware ==
777 777  
778 778  
... ... @@ -785,7 +785,7 @@
785 785  )))
786 786  
787 787  (((
788 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
977 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
789 789  )))
790 790  
791 791  
... ... @@ -792,6 +792,7 @@
792 792  
793 793  = 6.  Trouble Shooting =
794 794  
984 +
795 795  == 6.1  ​Connection problem when uploading firmware ==
796 796  
797 797  
... ... @@ -807,6 +807,7 @@
807 807  
808 808  == 6.2  AT Command input doesn't work ==
809 809  
1000 +
810 810  (((
811 811  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.
812 812  
... ... @@ -832,7 +832,7 @@
832 832  
833 833  (% style="color:#037691" %)**Package Includes**:
834 834  
835 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
1026 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1
836 836  * External antenna x 1
837 837  )))
838 838  
... ... @@ -839,9 +839,9 @@
839 839  (((
840 840  
841 841  
1033 +
842 842  (% style="color:#037691" %)**Dimension and weight**:
843 843  
844 -
845 845  * Device Size: 13.0 x 5 x 4.5 cm
846 846  * Device Weight: 150g
847 847  * Package Size / pcs : 15 x 12x 5.5 cm
... ... @@ -857,5 +857,6 @@
857 857  
858 858  = 9.  Support =
859 859  
1051 +
860 860  * 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.
861 861  * 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