Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 100.4 >
edited by Xiaoling
on 2022/08/22 14:38
To version < 108.10 >
edited by Xiaoling
on 2023/04/04 12:01
>
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  (((
... ... @@ -70,9 +70,6 @@
70 70  * Micro SIM card slot for NB-IoT SIM
71 71  * 8500mAh Battery for long term use
72 72  
73 -
74 -
75 -
76 76  == 1.3  Specification ==
77 77  
78 78  
... ... @@ -81,19 +81,15 @@
81 81  * Supply Voltage: 2.1v ~~ 3.6v
82 82  * Operating Temperature: -40 ~~ 85°C
83 83  
84 -
85 -
86 86  (% style="color:#037691" %)**NB-IoT Spec:**
87 87  
88 -* - B1 @H-FDD: 2100MHz
89 -* - B3 @H-FDD: 1800MHz
90 -* - B8 @H-FDD: 900MHz
91 -* - B5 @H-FDD: 850MHz
92 -* - B20 @H-FDD: 800MHz
93 -* - B28 @H-FDD: 700MHz
84 +* B1 @H-FDD: 2100MHz
85 +* B3 @H-FDD: 1800MHz
86 +* B8 @H-FDD: 900MHz
87 +* B5 @H-FDD: 850MHz
88 +* B20 @H-FDD: 800MHz
89 +* B28 @H-FDD: 700MHz
94 94  
95 -
96 -
97 97  (% style="color:#037691" %)**Battery:**
98 98  
99 99  * Li/SOCI2 un-chargeable battery
... ... @@ -102,17 +102,11 @@
102 102  * Max continuously current: 130mA
103 103  * Max boost current: 2A, 1 second
104 104  
105 -
106 -
107 107  (% style="color:#037691" %)**Power Consumption**
108 108  
109 109  * STOP Mode: 10uA @ 3.3v
110 110  * Max transmit power: 350mA@3.3v
111 111  
112 -
113 -
114 -
115 -
116 116  == ​1.4  Applications ==
117 117  
118 118  
... ... @@ -128,7 +128,6 @@
128 128  
129 129  
130 130  
131 -
132 132  == 1.5  Pin Definitions ==
133 133  
134 134  
... ... @@ -213,13 +213,13 @@
213 213  [[image:image-20220709092052-2.png]]
214 214  
215 215  
216 -**Connection:**
203 +(% style="color:blue" %)**Connection:**
217 217  
218 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
205 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
219 219  
220 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
207 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
221 221  
222 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
209 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
223 223  
224 224  
225 225  In the PC, use below serial tool settings:
... ... @@ -257,14 +257,19 @@
257 257  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
258 258  )))
259 259  * (((
260 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
247 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
261 261  )))
262 262  * (((
263 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
250 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
251 +
252 +
253 +
264 264  )))
265 265  
266 266  (((
267 267  For parameter description, please refer to AT command set
258 +
259 +
268 268  )))
269 269  
270 270  [[image:1657330452568-615.png]]
... ... @@ -273,6 +273,8 @@
273 273  
274 274  (((
275 275  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.
268 +
269 +
276 276  )))
277 277  
278 278  [[image:1657330472797-498.png]]
... ... @@ -282,12 +282,10 @@
282 282  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
283 283  
284 284  
285 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
286 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
287 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
279 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
280 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
281 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
288 288  
289 -
290 -
291 291  [[image:1657330501006-241.png]]
292 292  
293 293  
... ... @@ -298,16 +298,14 @@
298 298  === 2.2.6 Use MQTT protocol to uplink data ===
299 299  
300 300  
301 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
302 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
303 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
304 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
305 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
306 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
307 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
293 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
294 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
295 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
296 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
297 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
298 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
299 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
308 308  
309 -
310 -
311 311  [[image:1657249978444-674.png]]
312 312  
313 313  
... ... @@ -323,11 +323,9 @@
323 323  === 2.2.7 Use TCP protocol to uplink data ===
324 324  
325 325  
326 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
327 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
316 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
317 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
328 328  
329 -
330 -
331 331  [[image:image-20220709093918-1.png]]
332 332  
333 333  
... ... @@ -340,24 +340,31 @@
340 340  
341 341  User can use below command to change the (% style="color:green" %)**uplink interval**.
342 342  
343 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
331 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
344 344  
345 345  (((
334 +
335 +
336 +
346 346  (% style="color:red" %)**NOTE:**
347 -)))
348 348  
349 -(((
350 350  (% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
340 +
341 +(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
351 351  )))
352 352  
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).**
353 353  
354 354  
347 +
355 355  == 2.3  Uplink Payload ==
356 356  
357 357  
358 -In this mode, uplink payload includes in total 14 bytes
351 +=== 2.3.1  Before Firmware v1.3.2 ===
359 359  
360 360  
354 +In this mode, uplink payload includes in total 14 bytes
355 +
361 361  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
362 362  |=(% style="width: 60px;" %)(((
363 363  **Size(bytes)**
... ... @@ -365,7 +365,7 @@
365 365  |(% 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"]]
366 366  
367 367  (((
368 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
363 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
369 369  )))
370 370  
371 371  
... ... @@ -372,38 +372,67 @@
372 372  [[image:1657331036973-987.png]]
373 373  
374 374  
375 -(((
370 +
371 +The payload is **ASCII** string, representative same HEX:
372 +
373 +(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
374 +
375 +**where :**
376 +
377 +* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
378 +
379 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
380 +
381 +* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
382 +
383 +* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
384 +
385 +* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
386 +
387 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
388 +
389 +=== 2.3.2  Since firmware v1.3.2 ===
390 +
391 +
392 +In this mode, uplink payload includes 69 bytes in total by default.
393 +
394 +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.
395 +
396 +(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
397 +|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:70px" %)**4**|(% style="width:40px" %)**2**|(% style="width:60px" %)**4**
398 +|=(% 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.......
399 +
400 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
401 +
402 +[[image:image-20220908175246-1.png]]
403 +
404 +
376 376  The payload is ASCII string, representative same HEX:
377 -)))
378 378  
379 -(((
380 -0x72403155615900640c6c19029200 where:
381 -)))
407 +**0x (% style="color:red" %)f867787050213317 (% style="color:blue" %)0084 (% style="color:green" %)0cf4 (% style="color:#00b0f0" %)1e (% style="color:#7030a0" %)01 (% style="color:#d60093" %)00(% style="color:#a14d07" %) 0039 (% style="color:#0020b0" %)6315537b (% style="color:#663300" %)00396319baf0 00396319ba3c 00396319b988 00396319b8d4 00396319b820 00396319b76c 00396319b6b8 00396319b604 (%%)**
382 382  
383 -* (((
384 -Device ID: 0x724031556159 = 724031556159
385 -)))
386 -* (((
387 -Version: 0x0064=100=1.0.0
388 -)))
409 +**where:**
389 389  
390 -* (((
391 -BAT: 0x0c6c = 3180 mV = 3.180V
392 -)))
393 -* (((
394 -Signal: 0x19 = 25
395 -)))
396 -* (((
397 -Distance: 0x0292= 658 mm
398 -)))
399 -* (((
400 -Interrupt: 0x00 = 0
411 +* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
401 401  
413 +* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
402 402  
415 +* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
403 403  
404 -
405 -)))
417 +* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
406 406  
419 +* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
420 +
421 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
422 +
423 +* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
424 +
425 +* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
426 +
427 +* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
428 +
429 +* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
430 +
407 407  == 2.4  Payload Explanation and Sensor Interface ==
408 408  
409 409  
... ... @@ -421,7 +421,7 @@
421 421  )))
422 422  
423 423  (((
424 -**Example:**
448 +(% style="color:blue" %)**Example :**
425 425  )))
426 426  
427 427  (((
... ... @@ -429,11 +429,23 @@
429 429  )))
430 430  
431 431  (((
432 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
456 +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.
433 433  )))
434 434  
435 435  
460 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
436 436  
462 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
463 +
464 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
465 +
466 +
467 +(% style="color:blue" %)**Example :**
468 +
469 +AT+DEUI=868411056754138
470 +
471 +
472 +
437 437  === 2.4.2  Version Info ===
438 438  
439 439  
... ... @@ -528,7 +528,7 @@
528 528  )))
529 529  
530 530  (((
531 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
567 +(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/  (more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
532 532  )))
533 533  
534 534  
... ... @@ -630,125 +630,93 @@
630 630  
631 631  
632 632  
633 -== 2.6  ​LED Indicator ==
669 +== 2.6  Distance alarm function(Since firmware v1.3.2) ==
634 634  
635 635  
636 -The NDDS75 has an internal LED which is to show the status of different state.
672 +(% style="color:blue" %)** ➢ AT Command:**
637 637  
674 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
638 638  
639 -* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
640 -* Then the LED will be on for 1 second means device is boot normally.
641 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
642 -* For each uplink probe, LED will be on for 500ms.
676 +² When min=0, and max≠0, Alarm higher than max
643 643  
644 -(((
645 -
646 -)))
678 +² When min≠0, and max=0, Alarm lower than min
647 647  
680 +² When min≠0 and max≠0, Alarm higher than max or lower than min
648 648  
649 649  
650 -== 2.7  ​Firmware Change Log ==
683 +(% style="color:blue" %)** Example:**
651 651  
685 +**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
652 652  
653 -(((
654 -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]]
655 -)))
656 656  
657 -(((
658 -
659 -)))
660 660  
661 -(((
662 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
663 -)))
689 +== 2.7  Set the number of data to be uploaded and the recording time ==
664 664  
665 665  
692 +(% style="color:blue" %)** ➢ AT Command:**
666 666  
667 -== 2.8  ​Battery Analysis ==
694 +* (% 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)
695 +* (% 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.
668 668  
697 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
669 669  
670 -=== 2.8.1  ​Battery Type ===
699 +[[image:image-20221009001114-1.png||height="687" width="955"]]
671 671  
672 672  
673 -(((
674 -The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
675 -)))
676 676  
677 -(((
678 -The battery is designed to last for several years depends on the actually use environment and update interval. 
679 -)))
703 +== 2.8  Read or Clear cached data ==
680 680  
681 -(((
682 -The battery related documents as below:
683 -)))
684 684  
685 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
686 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
687 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
706 +(% style="color:blue" %)** ➢ AT Command:**
688 688  
689 -(((
690 -[[image:image-20220709101450-2.png]]
691 -)))
708 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
709 +* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
692 692  
711 +[[image:image-20220908175333-2.png]]
693 693  
694 694  
695 -=== 2.8.2  Power consumption Analyze ===
696 696  
715 +== 2.9  ​LED Indicator ==
697 697  
698 -(((
699 -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.
700 -)))
701 701  
718 +The NDDS75 has an internal LED which is to show the status of different state.
702 702  
703 -(((
704 -Instruction to use as below:
705 -)))
706 706  
721 +* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
722 +* Then the LED will be on for 1 second means device is boot normally.
723 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
724 +* For each uplink probe, LED will be on for 500ms.
725 +
707 707  (((
708 -(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
727 +
709 709  )))
710 710  
711 711  
731 +
732 +== 2.10  ​Firmware Change Log ==
733 +
734 +
712 712  (((
713 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
736 +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]]
714 714  )))
715 715  
716 -* (((
717 -Product Model
718 -)))
719 -* (((
720 -Uplink Interval
721 -)))
722 -* (((
723 -Working Mode
724 -)))
725 -
726 726  (((
727 -And the Life expectation in difference case will be shown on the right.
740 +
728 728  )))
729 729  
730 -[[image:image-20220709110451-3.png]]
731 -
732 -
733 -
734 -=== 2.8.3  ​Battery Note ===
735 -
736 -
737 737  (((
738 -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.
744 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
739 739  )))
740 740  
741 741  
742 742  
743 -=== 2.8.4  Replace the battery ===
749 +== 2.11 Battery & Power Consumption ==
744 744  
745 745  
746 -(((
747 -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).
748 -)))
752 +PS-LB-NA uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
749 749  
754 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
750 750  
751 -
752 752  = 3. ​ Access NB-IoT Module =
753 753  
754 754  
... ... @@ -775,74 +775,90 @@
775 775  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]]
776 776  
777 777  
778 -AT+<CMD>?  : Help on <CMD>
782 +AT+<CMD>?  :  Help on <CMD>
779 779  
780 -AT+<CMD>         : Run <CMD>
784 +AT+<CMD>         :  Run <CMD>
781 781  
782 -AT+<CMD>=<value> : Set the value
786 +AT+<CMD>=<value> :  Set the value
783 783  
784 -AT+<CMD>=?  : Get the value
788 +AT+<CMD>=?  :  Get the value
785 785  
786 786  
787 787  (% style="color:#037691" %)**General Commands**(%%)      
788 788  
789 -AT  : Attention       
793 +AT  :  Attention       
790 790  
791 -AT?  : Short Help     
795 +AT?  :  Short Help     
792 792  
793 -ATZ  : MCU Reset    
797 +ATZ  :  MCU Reset    
794 794  
795 -AT+TDC  : Application Data Transmission Interval
799 +AT+TDC  :  Application Data Transmission Interval
796 796  
797 -AT+CFG  : Print all configurations
801 +AT+CFG  :  Print all configurations
798 798  
799 -AT+CFGMOD           : Working mode selection
803 +AT+CFGMOD           :  Working mode selection
800 800  
801 -AT+INTMOD            : Set the trigger interrupt mode
805 +AT+INTMOD            :  Set the trigger interrupt mode
802 802  
803 -AT+5VT  : Set extend the time of 5V power  
807 +AT+5VT  :  Set extend the time of 5V power  
804 804  
805 -AT+PRO  : Choose agreement
809 +AT+PRO  :  Choose agreement
806 806  
807 -AT+WEIGRE  : Get weight or set weight to 0
811 +AT+WEIGRE  :  Get weight or set weight to 0
808 808  
809 -AT+WEIGAP  : Get or Set the GapValue of weight
813 +AT+WEIGAP  :  Get or Set the GapValue of weight
810 810  
811 -AT+RXDL  : Extend the sending and receiving time
815 +AT+RXDL  :  Extend the sending and receiving time
812 812  
813 -AT+CNTFAC  : Get or set counting parameters
817 +AT+CNTFAC  :  Get or set counting parameters
814 814  
815 -AT+SERVADDR  : Server Address
819 +AT+SERVADDR  :  Server Address
816 816  
821 +AT+TR  :  Get or Set record time"
817 817  
823 +AT+APN     :  Get or set the APN
824 +
825 +AT+FBAND  :  Get or Set whether to automatically modify the frequency band
826 +
827 +AT+DNSCFG  : Get or Set DNS Server
828 +
829 +AT+GETSENSORVALUE   :  Returns the current sensor measurement
830 +
831 +AT+NOUD  :  Get or Set the number of data to be uploaded
832 +
833 +AT+CDP     :  Read or Clear cached data
834 +
835 +AT+LDDSALARM :  Get or Set alarm of distance
836 +
837 +
818 818  (% style="color:#037691" %)**COAP Management**      
819 819  
820 -AT+URI            : Resource parameters
840 +AT+URI            :  Resource parameters
821 821  
822 822  
823 823  (% style="color:#037691" %)**UDP Management**
824 824  
825 -AT+CFM          : Upload confirmation mode (only valid for UDP)
845 +AT+CFM          :  Upload confirmation mode (only valid for UDP)
826 826  
827 827  
828 828  (% style="color:#037691" %)**MQTT Management**
829 829  
830 -AT+CLIENT               : Get or Set MQTT client
850 +AT+CLIENT  :  Get or Set MQTT client
831 831  
832 -AT+UNAME  : Get or Set MQTT Username
852 +AT+UNAME  :  Get or Set MQTT Username
833 833  
834 -AT+PWD                  : Get or Set MQTT password
854 +AT+PWD  :  Get or Set MQTT password
835 835  
836 -AT+PUBTOPIC  : Get or Set MQTT publish topic
856 +AT+PUBTOPIC  :  Get or Set MQTT publish topic
837 837  
838 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
858 +AT+SUBTOPIC  :  Get or Set MQTT subscription topic
839 839  
840 840  
841 841  (% style="color:#037691" %)**Information**          
842 842  
843 -AT+FDR  : Factory Data Reset
863 +AT+FDR  :  Factory Data Reset
844 844  
845 -AT+PWORD  : Serial Access Password
865 +AT+PWORD  :  Serial Access Password
846 846  
847 847  
848 848  
... ... @@ -917,6 +917,7 @@
917 917  (((
918 918  
919 919  
940 +
920 920  (% style="color:#037691" %)**Dimension and weight**:
921 921  
922 922  * Device Size: 13.0 x 5 x 4.5 cm
... ... @@ -937,6 +937,3 @@
937 937  
938 938  * 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.
939 939  * 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]]
940 -
941 -
942 -
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
image-20221009001114-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +282.9 KB
Content

Applications

Navigation

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