<
From version < 108.9 >
edited by Xiaoling
on 2023/04/04 12:01
To version < 100.5 >
edited by Xiaoling
on 2022/08/22 14:39
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -72,6 +72,8 @@
72 72  * 8500mAh Battery for long term use
73 73  
74 74  
75 +
76 +
75 75  == 1.3  Specification ==
76 76  
77 77  
... ... @@ -80,15 +80,17 @@
80 80  * Supply Voltage: 2.1v ~~ 3.6v
81 81  * Operating Temperature: -40 ~~ 85°C
82 82  
85 +
83 83  (% style="color:#037691" %)**NB-IoT Spec:**
84 84  
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
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
91 91  
95 +
92 92  (% style="color:#037691" %)**Battery:**
93 93  
94 94  * Li/SOCI2 un-chargeable battery
... ... @@ -97,6 +97,7 @@
97 97  * Max continuously current: 130mA
98 98  * Max boost current: 2A, 1 second
99 99  
104 +
100 100  (% style="color:#037691" %)**Power Consumption**
101 101  
102 102  * STOP Mode: 10uA @ 3.3v
... ... @@ -103,6 +103,8 @@
103 103  * Max transmit power: 350mA@3.3v
104 104  
105 105  
111 +
112 +
106 106  == ​1.4  Applications ==
107 107  
108 108  
... ... @@ -118,6 +118,7 @@
118 118  
119 119  
120 120  
128 +
121 121  == 1.5  Pin Definitions ==
122 122  
123 123  
... ... @@ -202,13 +202,13 @@
202 202  [[image:image-20220709092052-2.png]]
203 203  
204 204  
205 -(% style="color:blue" %)**Connection:**
213 +**Connection:**
206 206  
207 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
215 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
208 208  
209 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
217 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
210 210  
211 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
219 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
212 212  
213 213  
214 214  In the PC, use below serial tool settings:
... ... @@ -246,19 +246,14 @@
246 246  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
247 247  )))
248 248  * (((
249 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
257 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
250 250  )))
251 251  * (((
252 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
253 -
254 -
255 -
260 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
256 256  )))
257 257  
258 258  (((
259 259  For parameter description, please refer to AT command set
260 -
261 -
262 262  )))
263 263  
264 264  [[image:1657330452568-615.png]]
... ... @@ -267,8 +267,6 @@
267 267  
268 268  (((
269 269  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 -
272 272  )))
273 273  
274 274  [[image:1657330472797-498.png]]
... ... @@ -278,10 +278,11 @@
278 278  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
279 279  
280 280  
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
282 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
283 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
284 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
284 284  
286 +
285 285  [[image:1657330501006-241.png]]
286 286  
287 287  
... ... @@ -292,14 +292,15 @@
292 292  === 2.2.6 Use MQTT protocol to uplink data ===
293 293  
294 294  
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
297 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
298 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
299 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
300 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
301 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
302 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
303 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
302 302  
305 +
303 303  [[image:1657249978444-674.png]]
304 304  
305 305  
... ... @@ -315,9 +315,10 @@
315 315  === 2.2.7 Use TCP protocol to uplink data ===
316 316  
317 317  
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
321 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
322 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
320 320  
324 +
321 321  [[image:image-20220709093918-1.png]]
322 322  
323 323  
... ... @@ -330,31 +330,24 @@
330 330  
331 331  User can use below command to change the (% style="color:green" %)**uplink interval**.
332 332  
333 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
337 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
334 334  
335 335  (((
336 -
337 -
338 -
339 339  (% style="color:red" %)**NOTE:**
341 +)))
340 340  
343 +(((
341 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:**
344 344  )))
345 345  
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).**
347 347  
348 348  
349 -
350 350  == 2.3  Uplink Payload ==
351 351  
352 352  
353 -=== 2.3.1  Before Firmware v1.3.2 ===
354 -
355 -
356 356  In this mode, uplink payload includes in total 14 bytes
357 357  
354 +
358 358  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
359 359  |=(% style="width: 60px;" %)(((
360 360  **Size(bytes)**
... ... @@ -362,7 +362,7 @@
362 362  |(% 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"]]
363 363  
364 364  (((
365 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
362 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
366 366  )))
367 367  
368 368  
... ... @@ -369,68 +369,38 @@
369 369  [[image:1657331036973-987.png]]
370 370  
371 371  
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 -
369 +(((
408 408  The payload is ASCII string, representative same HEX:
371 +)))
409 409  
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 (%%)**
373 +(((
374 +0x72403155615900640c6c19029200 where:
375 +)))
411 411  
412 -**where:**
377 +* (((
378 +Device ID: 0x724031556159 = 724031556159
379 +)))
380 +* (((
381 +Version: 0x0064=100=1.0.0
382 +)))
413 413  
414 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
384 +* (((
385 +BAT: 0x0c6c = 3180 mV = 3.180V
386 +)))
387 +* (((
388 +Signal: 0x19 = 25
389 +)))
390 +* (((
391 +Distance: 0x0292= 658 mm
392 +)))
393 +* (((
394 +Interrupt: 0x00 = 0
415 415  
416 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
417 417  
418 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
419 419  
420 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
398 +
399 +)))
421 421  
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 -
434 434  == 2.4  Payload Explanation and Sensor Interface ==
435 435  
436 436  
... ... @@ -448,7 +448,7 @@
448 448  )))
449 449  
450 450  (((
451 -(% style="color:blue" %)**Example :**
418 +**Example:**
452 452  )))
453 453  
454 454  (((
... ... @@ -456,23 +456,11 @@
456 456  )))
457 457  
458 458  (((
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.
426 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
460 460  )))
461 461  
462 462  
463 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
464 464  
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 -
476 476  === 2.4.2  Version Info ===
477 477  
478 478  
... ... @@ -567,7 +567,7 @@
567 567  )))
568 568  
569 569  (((
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]])**.**
525 +(% 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]])**.**
571 571  )))
572 572  
573 573  
... ... @@ -669,93 +669,125 @@
669 669  
670 670  
671 671  
672 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
627 +== 2.6  ​LED Indicator ==
673 673  
674 674  
675 -(% style="color:blue" %)** AT Command:**
630 +The NDDS75 has an internal LED which is to show the status of different state.
676 676  
677 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
678 678  
679 -² When min=0, and max≠0, Alarm higher than max
633 +* 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)
634 +* Then the LED will be on for 1 second means device is boot normally.
635 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
636 +* For each uplink probe, LED will be on for 500ms.
680 680  
681 -² When min≠0, and max=0, Alarm lower than min
638 +(((
639 +
640 +)))
682 682  
683 -² When min≠0 and max≠0, Alarm higher than max or lower than min
684 684  
685 685  
686 -(% style="color:blue" %)** Example:**
644 +== 2.7  ​Firmware Change Log ==
687 687  
688 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
689 689  
647 +(((
648 +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]]
649 +)))
690 690  
651 +(((
652 +
653 +)))
691 691  
692 -== 2.7  Set the number of data to be uploaded and the recording time ==
655 +(((
656 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
657 +)))
693 693  
694 694  
695 -(% style="color:blue" %)** ➢ AT Command:**
696 696  
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.
661 +== 2.8  ​Battery Analysis ==
699 699  
700 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
701 701  
702 -[[image:image-20221009001114-1.png||height="687" width="955"]]
664 +=== 2.8.1  ​Battery Type ===
703 703  
704 704  
667 +(((
668 +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.
669 +)))
705 705  
706 -== 2.8  Read or Clear cached data ==
671 +(((
672 +The battery is designed to last for several years depends on the actually use environment and update interval. 
673 +)))
707 707  
675 +(((
676 +The battery related documents as below:
677 +)))
708 708  
709 -(% style="color:blue" %)** ➢ AT Command:**
679 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
680 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
681 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
710 710  
711 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
712 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
683 +(((
684 +[[image:image-20220709101450-2.png]]
685 +)))
713 713  
714 -[[image:image-20220908175333-2.png]]
715 715  
716 716  
689 +=== 2.8.2  Power consumption Analyze ===
717 717  
718 -== 2.9  ​LED Indicator ==
719 719  
692 +(((
693 +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.
694 +)))
720 720  
721 -The NDDS75 has an internal LED which is to show the status of different state.
722 722  
697 +(((
698 +Instruction to use as below:
699 +)))
723 723  
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 -
729 729  (((
730 -
702 +(% 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/]]
731 731  )))
732 732  
733 733  
734 -
735 -== 2.10  ​Firmware Change Log ==
736 -
737 -
738 738  (((
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]]
707 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
740 740  )))
741 741  
710 +* (((
711 +Product Model
712 +)))
713 +* (((
714 +Uplink Interval
715 +)))
716 +* (((
717 +Working Mode
718 +)))
719 +
742 742  (((
743 -
721 +And the Life expectation in difference case will be shown on the right.
744 744  )))
745 745  
724 +[[image:image-20220709110451-3.png]]
725 +
726 +
727 +
728 +=== 2.8.3  ​Battery Note ===
729 +
730 +
746 746  (((
747 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
732 +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.
748 748  )))
749 749  
750 750  
751 751  
752 -== 2.11 Battery & Power Consumption ==
737 +=== 2.8.4  Replace the battery ===
753 753  
754 754  
755 -PS-LB-NA uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
740 +(((
741 +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).
742 +)))
756 756  
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/]] .
758 758  
745 +
759 759  = 3. ​ Access NB-IoT Module =
760 760  
761 761  
... ... @@ -782,90 +782,74 @@
782 782  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]]
783 783  
784 784  
785 -AT+<CMD>?  :  Help on <CMD>
772 +AT+<CMD>?  : Help on <CMD>
786 786  
787 -AT+<CMD>         :  Run <CMD>
774 +AT+<CMD>         : Run <CMD>
788 788  
789 -AT+<CMD>=<value> :  Set the value
776 +AT+<CMD>=<value> : Set the value
790 790  
791 -AT+<CMD>=?  :  Get the value
778 +AT+<CMD>=?  : Get the value
792 792  
793 793  
794 794  (% style="color:#037691" %)**General Commands**(%%)      
795 795  
796 -AT  :  Attention       
783 +AT  : Attention       
797 797  
798 -AT?  :  Short Help     
785 +AT?  : Short Help     
799 799  
800 -ATZ  :  MCU Reset    
787 +ATZ  : MCU Reset    
801 801  
802 -AT+TDC  :  Application Data Transmission Interval
789 +AT+TDC  : Application Data Transmission Interval
803 803  
804 -AT+CFG  :  Print all configurations
791 +AT+CFG  : Print all configurations
805 805  
806 -AT+CFGMOD           :  Working mode selection
793 +AT+CFGMOD           : Working mode selection
807 807  
808 -AT+INTMOD            :  Set the trigger interrupt mode
795 +AT+INTMOD            : Set the trigger interrupt mode
809 809  
810 -AT+5VT  :  Set extend the time of 5V power  
797 +AT+5VT  : Set extend the time of 5V power  
811 811  
812 -AT+PRO  :  Choose agreement
799 +AT+PRO  : Choose agreement
813 813  
814 -AT+WEIGRE  :  Get weight or set weight to 0
801 +AT+WEIGRE  : Get weight or set weight to 0
815 815  
816 -AT+WEIGAP  :  Get or Set the GapValue of weight
803 +AT+WEIGAP  : Get or Set the GapValue of weight
817 817  
818 -AT+RXDL  :  Extend the sending and receiving time
805 +AT+RXDL  : Extend the sending and receiving time
819 819  
820 -AT+CNTFAC  :  Get or set counting parameters
807 +AT+CNTFAC  : Get or set counting parameters
821 821  
822 -AT+SERVADDR  :  Server Address
809 +AT+SERVADDR  : Server Address
823 823  
824 -AT+TR  :  Get or Set record time"
825 825  
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 -
841 841  (% style="color:#037691" %)**COAP Management**      
842 842  
843 -AT+URI            :  Resource parameters
814 +AT+URI            : Resource parameters
844 844  
845 845  
846 846  (% style="color:#037691" %)**UDP Management**
847 847  
848 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
819 +AT+CFM          : Upload confirmation mode (only valid for UDP)
849 849  
850 850  
851 851  (% style="color:#037691" %)**MQTT Management**
852 852  
853 -AT+CLIENT  :  Get or Set MQTT client
824 +AT+CLIENT               : Get or Set MQTT client
854 854  
855 -AT+UNAME  Get or Set MQTT Username
826 +AT+UNAME  : Get or Set MQTT Username
856 856  
857 -AT+PWD  :  Get or Set MQTT password
828 +AT+PWD                  : Get or Set MQTT password
858 858  
859 -AT+PUBTOPIC  Get or Set MQTT publish topic
830 +AT+PUBTOPIC  : Get or Set MQTT publish topic
860 860  
861 -AT+SUBTOPIC  Get or Set MQTT subscription topic
832 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
862 862  
863 863  
864 864  (% style="color:#037691" %)**Information**          
865 865  
866 -AT+FDR  :  Factory Data Reset
837 +AT+FDR  : Factory Data Reset
867 867  
868 -AT+PWORD  :  Serial Access Password
839 +AT+PWORD  : Serial Access Password
869 869  
870 870  
871 871  
... ... @@ -940,7 +940,6 @@
940 940  (((
941 941  
942 942  
943 -
944 944  (% style="color:#037691" %)**Dimension and weight**:
945 945  
946 946  * Device Size: 13.0 x 5 x 4.5 cm
... ... @@ -961,3 +961,5 @@
961 961  
962 962  * 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.
963 963  * 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]]
934 +
935 +
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
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0