Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 108.10 >
edited by Xiaoling
on 2023/04/04 12:01
To version < 100.6 >
edited by Xiaoling
on 2022/09/06 17:42
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -71,6 +71,9 @@
71 71  * Micro SIM card slot for NB-IoT SIM
72 72  * 8500mAh Battery for long term use
73 73  
74 +
75 +
76 +
74 74  == 1.3  Specification ==
75 75  
76 76  
... ... @@ -79,15 +79,19 @@
79 79  * Supply Voltage: 2.1v ~~ 3.6v
80 80  * Operating Temperature: -40 ~~ 85°C
81 81  
85 +
86 +
82 82  (% style="color:#037691" %)**NB-IoT Spec:**
83 83  
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
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
90 90  
96 +
97 +
91 91  (% style="color:#037691" %)**Battery:**
92 92  
93 93  * Li/SOCI2 un-chargeable battery
... ... @@ -96,11 +96,16 @@
96 96  * Max continuously current: 130mA
97 97  * Max boost current: 2A, 1 second
98 98  
106 +
107 +
99 99  (% style="color:#037691" %)**Power Consumption**
100 100  
101 101  * STOP Mode: 10uA @ 3.3v
102 102  * Max transmit power: 350mA@3.3v
103 103  
113 +
114 +
115 +
104 104  == ​1.4  Applications ==
105 105  
106 106  
... ... @@ -116,6 +116,7 @@
116 116  
117 117  
118 118  
131 +
119 119  == 1.5  Pin Definitions ==
120 120  
121 121  
... ... @@ -163,6 +163,8 @@
163 163  * The local NB-IoT network used the band that NDDS75 supports.
164 164  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
165 165  
179 +
180 +
166 166  (((
167 167  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server.
168 168  )))
... ... @@ -200,13 +200,13 @@
200 200  [[image:image-20220709092052-2.png]]
201 201  
202 202  
203 -(% style="color:blue" %)**Connection:**
218 +**Connection:**
204 204  
205 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
220 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
206 206  
207 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
222 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
208 208  
209 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
224 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
210 210  
211 211  
212 212  In the PC, use below serial tool settings:
... ... @@ -244,10 +244,10 @@
244 244  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
245 245  )))
246 246  * (((
247 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
262 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
248 248  )))
249 249  * (((
250 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
265 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
251 251  
252 252  
253 253  
... ... @@ -255,8 +255,6 @@
255 255  
256 256  (((
257 257  For parameter description, please refer to AT command set
258 -
259 -
260 260  )))
261 261  
262 262  [[image:1657330452568-615.png]]
... ... @@ -265,8 +265,6 @@
265 265  
266 266  (((
267 267  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 -
270 270  )))
271 271  
272 272  [[image:1657330472797-498.png]]
... ... @@ -276,10 +276,12 @@
276 276  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
277 277  
278 278  
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
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
282 282  
294 +
295 +
283 283  [[image:1657330501006-241.png]]
284 284  
285 285  
... ... @@ -290,14 +290,16 @@
290 290  === 2.2.6 Use MQTT protocol to uplink data ===
291 291  
292 292  
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
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
300 300  
314 +
315 +
301 301  [[image:1657249978444-674.png]]
302 302  
303 303  
... ... @@ -313,9 +313,11 @@
313 313  === 2.2.7 Use TCP protocol to uplink data ===
314 314  
315 315  
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
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 318  
334 +
335 +
319 319  [[image:image-20220709093918-1.png]]
320 320  
321 321  
... ... @@ -328,31 +328,22 @@
328 328  
329 329  User can use below command to change the (% style="color:green" %)**uplink interval**.
330 330  
331 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
348 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
332 332  
333 -(((
334 -
335 335  
336 336  
337 -(% style="color:red" %)**NOTE:**
338 -
339 -(% 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:**
352 +(((
353 +(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.**
342 342  )))
343 343  
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).**
345 345  
346 346  
347 -
348 348  == 2.3  Uplink Payload ==
349 349  
350 350  
351 -=== 2.3.1  Before Firmware v1.3.2 ===
352 -
353 -
354 354  In this mode, uplink payload includes in total 14 bytes
355 355  
363 +
356 356  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
357 357  |=(% style="width: 60px;" %)(((
358 358  **Size(bytes)**
... ... @@ -360,7 +360,7 @@
360 360  |(% 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"]]
361 361  
362 362  (((
363 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
371 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
364 364  )))
365 365  
366 366  
... ... @@ -367,67 +367,38 @@
367 367  [[image:1657331036973-987.png]]
368 368  
369 369  
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 -
378 +(((
405 405  The payload is ASCII string, representative same HEX:
380 +)))
406 406  
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 +(((
383 +0x72403155615900640c6c19029200 where:
384 +)))
408 408  
409 -**where:**
386 +* (((
387 +Device ID: 0x724031556159 = 724031556159
388 +)))
389 +* (((
390 +Version: 0x0064=100=1.0.0
391 +)))
410 410  
411 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
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
412 412  
413 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
414 414  
415 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
416 416  
417 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
407 +
408 +)))
418 418  
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 -
431 431  == 2.4  Payload Explanation and Sensor Interface ==
432 432  
433 433  
... ... @@ -445,7 +445,7 @@
445 445  )))
446 446  
447 447  (((
448 -(% style="color:blue" %)**Example :**
427 +**Example:**
449 449  )))
450 450  
451 451  (((
... ... @@ -453,23 +453,11 @@
453 453  )))
454 454  
455 455  (((
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.
435 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
457 457  )))
458 458  
459 459  
460 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
461 461  
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 -
473 473  === 2.4.2  Version Info ===
474 474  
475 475  
... ... @@ -564,7 +564,7 @@
564 564  )))
565 565  
566 566  (((
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]])**.**
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]])**.**
568 568  )))
569 569  
570 570  
... ... @@ -666,93 +666,125 @@
666 666  
667 667  
668 668  
669 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
636 +== 2.6  ​LED Indicator ==
670 670  
671 671  
672 -(% style="color:blue" %)** ➢ AT Command:**
639 +The NDDS75 has an internal LED which is to show the status of different state.
673 673  
674 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
675 675  
676 -² When min=0, and max≠0, Alarm higher than max
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.
677 677  
678 -² When min≠0, and max=0, Alarm lower than min
647 +(((
648 +
649 +)))
679 679  
680 -² When min≠0 and max≠0, Alarm higher than max or lower than min
681 681  
682 682  
683 -(% style="color:blue" %)** Example:**
653 +== 2.7  ​Firmware Change Log ==
684 684  
685 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
686 686  
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 +)))
687 687  
660 +(((
661 +
662 +)))
688 688  
689 -== 2.7  Set the number of data to be uploaded and the recording time ==
664 +(((
665 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
666 +)))
690 690  
691 691  
692 -(% style="color:blue" %)** ➢ AT Command:**
693 693  
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.
670 +== 2.8  ​Battery Analysis ==
696 696  
697 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
698 698  
699 -[[image:image-20221009001114-1.png||height="687" width="955"]]
673 +=== 2.8.1  ​Battery Type ===
700 700  
701 701  
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 +)))
702 702  
703 -== 2.8  Read or Clear cached data ==
680 +(((
681 +The battery is designed to last for several years depends on the actually use environment and update interval. 
682 +)))
704 704  
684 +(((
685 +The battery related documents as below:
686 +)))
705 705  
706 -(% style="color:blue" %)** ➢ AT Command:**
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/]]
707 707  
708 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
709 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
692 +(((
693 +[[image:image-20220709101450-2.png]]
694 +)))
710 710  
711 -[[image:image-20220908175333-2.png]]
712 712  
713 713  
698 +=== 2.8.2  Power consumption Analyze ===
714 714  
715 -== 2.9  ​LED Indicator ==
716 716  
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 +)))
717 717  
718 -The NDDS75 has an internal LED which is to show the status of different state.
719 719  
706 +(((
707 +Instruction to use as below:
708 +)))
720 720  
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 -
726 726  (((
727 -
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/]]
728 728  )))
729 729  
730 730  
731 -
732 -== 2.10  ​Firmware Change Log ==
733 -
734 -
735 735  (((
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]]
716 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
737 737  )))
738 738  
719 +* (((
720 +Product Model
721 +)))
722 +* (((
723 +Uplink Interval
724 +)))
725 +* (((
726 +Working Mode
727 +)))
728 +
739 739  (((
740 -
730 +And the Life expectation in difference case will be shown on the right.
741 741  )))
742 742  
733 +[[image:image-20220709110451-3.png]]
734 +
735 +
736 +
737 +=== 2.8.3  ​Battery Note ===
738 +
739 +
743 743  (((
744 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
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.
745 745  )))
746 746  
747 747  
748 748  
749 -== 2.11 Battery & Power Consumption ==
746 +=== 2.8.4  Replace the battery ===
750 750  
751 751  
752 -PS-LB-NA uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
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 +)))
753 753  
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/]] .
755 755  
754 +
756 756  = 3. ​ Access NB-IoT Module =
757 757  
758 758  
... ... @@ -779,90 +779,74 @@
779 779  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]]
780 780  
781 781  
782 -AT+<CMD>?  :  Help on <CMD>
781 +AT+<CMD>?  : Help on <CMD>
783 783  
784 -AT+<CMD>         :  Run <CMD>
783 +AT+<CMD>         : Run <CMD>
785 785  
786 -AT+<CMD>=<value> :  Set the value
785 +AT+<CMD>=<value> : Set the value
787 787  
788 -AT+<CMD>=?  :  Get the value
787 +AT+<CMD>=?  : Get the value
789 789  
790 790  
791 791  (% style="color:#037691" %)**General Commands**(%%)      
792 792  
793 -AT  :  Attention       
792 +AT  : Attention       
794 794  
795 -AT?  :  Short Help     
794 +AT?  : Short Help     
796 796  
797 -ATZ  :  MCU Reset    
796 +ATZ  : MCU Reset    
798 798  
799 -AT+TDC  :  Application Data Transmission Interval
798 +AT+TDC  : Application Data Transmission Interval
800 800  
801 -AT+CFG  :  Print all configurations
800 +AT+CFG  : Print all configurations
802 802  
803 -AT+CFGMOD           :  Working mode selection
802 +AT+CFGMOD           : Working mode selection
804 804  
805 -AT+INTMOD            :  Set the trigger interrupt mode
804 +AT+INTMOD            : Set the trigger interrupt mode
806 806  
807 -AT+5VT  :  Set extend the time of 5V power  
806 +AT+5VT  : Set extend the time of 5V power  
808 808  
809 -AT+PRO  :  Choose agreement
808 +AT+PRO  : Choose agreement
810 810  
811 -AT+WEIGRE  :  Get weight or set weight to 0
810 +AT+WEIGRE  : Get weight or set weight to 0
812 812  
813 -AT+WEIGAP  :  Get or Set the GapValue of weight
812 +AT+WEIGAP  : Get or Set the GapValue of weight
814 814  
815 -AT+RXDL  :  Extend the sending and receiving time
814 +AT+RXDL  : Extend the sending and receiving time
816 816  
817 -AT+CNTFAC  :  Get or set counting parameters
816 +AT+CNTFAC  : Get or set counting parameters
818 818  
819 -AT+SERVADDR  :  Server Address
818 +AT+SERVADDR  : Server Address
820 820  
821 -AT+TR  :  Get or Set record time"
822 822  
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 -
838 838  (% style="color:#037691" %)**COAP Management**      
839 839  
840 -AT+URI            :  Resource parameters
823 +AT+URI            : Resource parameters
841 841  
842 842  
843 843  (% style="color:#037691" %)**UDP Management**
844 844  
845 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
828 +AT+CFM          : Upload confirmation mode (only valid for UDP)
846 846  
847 847  
848 848  (% style="color:#037691" %)**MQTT Management**
849 849  
850 -AT+CLIENT  :  Get or Set MQTT client
833 +AT+CLIENT               : Get or Set MQTT client
851 851  
852 -AT+UNAME  :  Get or Set MQTT Username
835 +AT+UNAME  : Get or Set MQTT Username
853 853  
854 -AT+PWD  :  Get or Set MQTT password
837 +AT+PWD                  : Get or Set MQTT password
855 855  
856 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
839 +AT+PUBTOPIC  : Get or Set MQTT publish topic
857 857  
858 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
841 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
859 859  
860 860  
861 861  (% style="color:#037691" %)**Information**          
862 862  
863 -AT+FDR  :  Factory Data Reset
846 +AT+FDR  : Factory Data Reset
864 864  
865 -AT+PWORD  :  Serial Access Password
848 +AT+PWORD  : Serial Access Password
866 866  
867 867  
868 868  
... ... @@ -958,3 +958,5 @@
958 958  
959 959  * 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.
960 960  * 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-20220908175246-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -55.7 KB
Content
image-20220908175333-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -31.1 KB
Content
image-20221009001114-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -282.9 KB
Content

Applications

Navigation

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