Changes for page NDDS75 -- NB-IoT Distance Detect Sensor User Manual
Last modified by Bei Jinggeng on 2024/05/31 09:53
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -72,7 +72,6 @@ 72 72 * 8500mAh Battery for long term use 73 73 74 74 75 - 76 76 == 1.3 Specification == 77 77 78 78 ... ... @@ -83,12 +83,12 @@ 83 83 84 84 (% style="color:#037691" %)**NB-IoT Spec:** 85 85 86 -* -B1 @H-FDD: 2100MHz87 -* -B3 @H-FDD: 1800MHz88 -* -B8 @H-FDD: 900MHz89 -* -B5 @H-FDD: 850MHz90 -* -B20 @H-FDD: 800MHz91 -* -B28 @H-FDD: 700MHz85 +* 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 92 92 93 93 (% style="color:#037691" %)**Battery:** 94 94 ... ... @@ -104,7 +104,6 @@ 104 104 * Max transmit power: 350mA@3.3v 105 105 106 106 107 - 108 108 == 1.4 Applications == 109 109 110 110 ... ... @@ -120,7 +120,6 @@ 120 120 121 121 122 122 123 - 124 124 == 1.5 Pin Definitions == 125 125 126 126 ... ... @@ -285,8 +285,6 @@ 285 285 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 286 286 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 287 287 288 - 289 - 290 290 [[image:1657330501006-241.png]] 291 291 292 292 ... ... @@ -367,7 +367,7 @@ 367 367 |(% 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"]] 368 368 369 369 ((( 370 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 1uplink 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. 371 371 ))) 372 372 373 373 ... ... @@ -374,49 +374,36 @@ 374 374 [[image:1657331036973-987.png]] 375 375 376 376 377 - (((372 + 378 378 The payload is **ASCII** string, representative same HEX: 379 -))) 380 380 381 -((( 382 -0x72403155615900640c6c19029200 where: 383 -))) 375 +(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 ** 384 384 385 -* ((( 386 -Device ID: 0x724031556159 = 724031556159 387 -))) 388 -* ((( 389 -Version: 0x0064=100=1.0.0 390 -))) 377 +**where :** 391 391 392 -* ((( 393 -BAT: 0x0c6c = 3180 mV = 3.180V 394 -))) 395 -* ((( 396 -Signal: 0x19 = 25 397 -))) 398 -* ((( 399 -Distance: 0x0292= 658 mm 400 -))) 401 -* ((( 402 -Interrupt: 0x00 = 0 379 +* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159 403 403 381 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 404 404 383 +* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V 405 405 385 +* (% style="color:#037691" %)**Signal:**(%%) 0x19 = 25 406 406 407 - 408 -))) 387 +* (% style="color:#037691" %)**Distance:** (%%)0x0292= 658 mm 409 409 410 -= ==**2.3.2 Sincefirmware v1.3.2** ===389 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0 411 411 412 412 392 +=== 2.3.2 Since firmware v1.3.2 === 393 + 394 + 413 413 In this mode, uplink payload includes 69 bytes in total by default. 414 414 415 415 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. 416 416 417 -(% border=" 2" style="background-color:#ffffcc; color:green; width:896px" %)418 -|(% style="width: 95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)4419 -|(% 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 +(% 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....... 420 420 421 421 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 422 422 ... ... @@ -425,21 +425,30 @@ 425 425 426 426 The payload is ASCII string, representative same HEX: 427 427 428 -0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color: red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%)where: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 (%%)** 429 429 430 -* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317 431 -* (% style="color:red" %)Version: 0x0084=132=1.3.2 432 -* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V 433 -* (% style="color:blue" %)Singal: 0x1e = 30 434 -* (% style="color:red" %)Mod: 0x01 = 1 435 -* Interrupt: 0x00= 0 436 -* Distance: 0x0039= 57 = 57 437 -* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 438 -* Distance,Time stamp : 00396319baf0 439 -* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,....... 412 +**where:** 440 440 414 +* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317 441 441 416 +* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2 442 442 418 +* (% style="color:#037691" %)**BAT:**(%%) 0x0cf4 = 3316 mV = 3.316V 419 + 420 +* (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 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 + 443 443 == 2.4 Payload Explanation and Sensor Interface == 444 444 445 445 ... ... @@ -704,11 +704,14 @@ 704 704 (% style="color:blue" %)** ➢ AT Command:** 705 705 706 706 * (% 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) 707 -* (% style="color:#037691" %)** AT+NOUD=8** 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. 708 708 700 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 709 709 702 +[[image:image-20221009001114-1.png||height="687" width="955"]] 710 710 711 711 705 + 712 712 == 2.8 Read or Clear cached data == 713 713 714 714 ... ... @@ -755,91 +755,13 @@ 755 755 756 756 757 757 758 -== 2.11 BatteryAnalysis==752 +== 2.11 Battery & Power Consumption == 759 759 760 760 761 - ===2.11.1BatteryType===755 +PS-LB-NA uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 762 762 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/]] . 763 763 764 -((( 765 -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. 766 -))) 767 - 768 -((( 769 -The battery is designed to last for several years depends on the actually use environment and update interval. 770 -))) 771 - 772 -((( 773 -The battery related documents as below: 774 -))) 775 - 776 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 777 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 778 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 779 - 780 -((( 781 -[[image:image-20220709101450-2.png]] 782 -))) 783 - 784 - 785 - 786 -=== 2.11.2 Power consumption Analyze === 787 - 788 - 789 -((( 790 -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. 791 -))) 792 - 793 - 794 -((( 795 -Instruction to use as below: 796 -))) 797 - 798 -((( 799 -(% 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/]] 800 -))) 801 - 802 - 803 -((( 804 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose 805 -))) 806 - 807 -* ((( 808 -Product Model 809 -))) 810 -* ((( 811 -Uplink Interval 812 -))) 813 -* ((( 814 -Working Mode 815 -))) 816 - 817 -((( 818 -And the Life expectation in difference case will be shown on the right. 819 -))) 820 - 821 -[[image:image-20220709110451-3.png]] 822 - 823 - 824 - 825 -=== 2.11.3 Battery Note === 826 - 827 - 828 -((( 829 -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. 830 -))) 831 - 832 - 833 - 834 -=== 2.11.4 Replace the battery === 835 - 836 - 837 -((( 838 -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). 839 -))) 840 - 841 - 842 - 843 843 = 3. Access NB-IoT Module = 844 844 845 845
- image-20221009001114-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +282.9 KB - Content