Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 102.1 >
edited by David Huang
on 2022/09/08 17:53
To version < 108.9 >
edited by Xiaoling
on 2023/04/04 12:01
>
Change comment: There is no comment for this version

Summary

Details

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