Changes for page NDDS75 -- NB-IoT Distance Detect Sensor User Manual
Last modified by Bei Jinggeng on 2024/05/31 09:53
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. David1 +XWiki.Xiaoling - Content
-
... ... @@ -16,7 +16,6 @@ 16 16 17 17 = 1. Introduction = 18 18 19 - 20 20 == 1.1 What is NDDS75 Distance Detection Sensor == 21 21 22 22 ((( ... ... @@ -54,7 +54,6 @@ 54 54 [[image:1657327959271-447.png]] 55 55 56 56 57 - 58 58 == 1.2 Features == 59 59 60 60 ... ... @@ -72,6 +72,7 @@ 72 72 * 8500mAh Battery for long term use 73 73 74 74 73 + 75 75 == 1.3 Specification == 76 76 77 77 ... ... @@ -82,12 +82,12 @@ 82 82 83 83 (% style="color:#037691" %)**NB-IoT Spec:** 84 84 85 -* -B1 @H-FDD: 2100MHz86 -* -B3 @H-FDD: 1800MHz87 -* -B8 @H-FDD: 900MHz88 -* -B5 @H-FDD: 850MHz89 -* -B20 @H-FDD: 800MHz90 -* -B28 @H-FDD: 700MHz84 +* 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 91 91 92 92 (% style="color:#037691" %)**Battery:** 93 93 ... ... @@ -100,9 +100,10 @@ 100 100 (% style="color:#037691" %)**Power Consumption** 101 101 102 102 * STOP Mode: 10uA @ 3.3v 103 -* Max transmit power: 350mA@3.3v 102 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 104 104 105 105 105 + 106 106 == 1.4 Applications == 107 107 108 108 ... ... @@ -117,8 +117,6 @@ 117 117 118 118 119 119 120 - 121 - 122 122 == 1.5 Pin Definitions == 123 123 124 124 ... ... @@ -125,10 +125,8 @@ 125 125 [[image:1657328609906-564.png]] 126 126 127 127 128 - 129 129 = 2. Use NDDS75 to communicate with IoT Server = 130 130 131 - 132 132 == 2.1 How it works == 133 133 134 134 ... ... @@ -151,10 +151,8 @@ 151 151 152 152 ))) 153 153 154 - 155 155 == 2.2 Configure the NDDS75 == 156 156 157 - 158 158 === 2.2.1 Test Requirement === 159 159 160 160 ... ... @@ -174,7 +174,6 @@ 174 174 [[image:1657328756309-230.png]] 175 175 176 176 177 - 178 178 === 2.2.2 Insert SIM card === 179 179 180 180 ... ... @@ -190,7 +190,6 @@ 190 190 [[image:1657328884227-504.png]] 191 191 192 192 193 - 194 194 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 195 195 196 196 ... ... @@ -232,7 +232,6 @@ 232 232 ))) 233 233 234 234 235 - 236 236 === 2.2.4 Use CoAP protocol to uplink data === 237 237 238 238 ... ... @@ -275,7 +275,6 @@ 275 275 [[image:1657330472797-498.png]] 276 276 277 277 278 - 279 279 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 280 280 281 281 ... ... @@ -283,7 +283,6 @@ 283 283 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 284 284 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 285 285 286 - 287 287 [[image:1657330501006-241.png]] 288 288 289 289 ... ... @@ -290,7 +290,6 @@ 290 290 [[image:1657330533775-472.png]] 291 291 292 292 293 - 294 294 === 2.2.6 Use MQTT protocol to uplink data === 295 295 296 296 ... ... @@ -313,7 +313,6 @@ 313 313 ))) 314 314 315 315 316 - 317 317 === 2.2.7 Use TCP protocol to uplink data === 318 318 319 319 ... ... @@ -326,7 +326,6 @@ 326 326 [[image:image-20220709093918-2.png]] 327 327 328 328 329 - 330 330 === 2.2.8 Change Update Interval === 331 331 332 332 ... ... @@ -348,10 +348,8 @@ 348 348 (% 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).** 349 349 350 350 351 - 352 352 == 2.3 Uplink Payload == 353 353 354 - 355 355 === 2.3.1 Before Firmware v1.3.2 === 356 356 357 357 ... ... @@ -364,7 +364,7 @@ 364 364 |(% 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"]] 365 365 366 366 ((( 367 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 1uplink data.351 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 368 368 ))) 369 369 370 370 ... ... @@ -371,49 +371,36 @@ 371 371 [[image:1657331036973-987.png]] 372 372 373 373 374 -((( 375 375 The payload is **ASCII** string, representative same HEX: 376 -))) 377 377 378 -((( 379 -0x72403155615900640c6c19029200 where: 380 -))) 360 +(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 ** 381 381 382 -* ((( 383 -Device ID: 0x724031556159 = 724031556159 384 -))) 385 -* ((( 386 -Version: 0x0064=100=1.0.0 387 -))) 362 +**where :** 388 388 389 -* ((( 390 -BAT: 0x0c6c = 3180 mV = 3.180V 391 -))) 392 -* ((( 393 -Signal: 0x19 = 25 394 -))) 395 -* ((( 396 -Distance: 0x0292= 658 mm 397 -))) 398 -* ((( 399 -Interrupt: 0x00 = 0 364 +* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159 400 400 366 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 401 401 368 +* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V 402 402 370 +* (% style="color:#037691" %)**Signal:**(%%) 0x19 = 25 403 403 404 - 405 -))) 372 +* (% style="color:#037691" %)**Distance:** (%%)0x0292= 658 mm 406 406 407 -= ==**2.3.2 Sincefirmware v1.3.2** ===374 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0 408 408 409 409 377 + 378 +=== 2.3.2 Since firmware v1.3.2 === 379 + 380 + 410 410 In this mode, uplink payload includes 69 bytes in total by default. 411 411 412 412 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. 413 413 414 -(% border=" 2" style="background-color:#ffffcc; color:green; width:896px" %)415 -|(% 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" %)4416 -|(% 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....... 385 +(% border="1" style="background-color:#ffffcc; color:green; width:490px" %) 386 +|=(% 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** 387 +|=(% 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....... 417 417 418 418 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 419 419 ... ... @@ -422,23 +422,34 @@ 422 422 423 423 The payload is ASCII string, representative same HEX: 424 424 425 -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:396 +**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 (%%)** 426 426 427 -* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317 428 -* (% style="color:red" %)Version: 0x0084=132=1.3.2 429 -* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V 430 -* (% style="color:blue" %)Singal: 0x1e = 30 431 -* (% style="color:red" %)Mod: 0x01 = 1 432 -* Interrupt: 0x00= 0 433 -* Distance: 0x0039= 57 = 57 434 -* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 435 -* Distance,Time stamp : 00396319baf0 436 -* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,....... 398 +**where:** 437 437 400 +* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317 438 438 439 - ==2.4Payload Explanationand Sensor Interface==402 +* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2 440 440 404 +* (% style="color:#037691" %)**BAT:**(%%) 0x0cf4 = 3316 mV = 3.316V 441 441 406 +* (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 407 + 408 +* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 409 + 410 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 411 + 412 +* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57 413 + 414 +* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 415 + 416 +* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0 417 + 418 +* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 419 + 420 + 421 + 422 +== 2.4 Payload Explanation and Sensor Interface == 423 + 442 442 === 2.4.1 Device ID === 443 443 444 444 ... ... @@ -477,7 +477,6 @@ 477 477 AT+DEUI=868411056754138 478 478 479 479 480 - 481 481 === 2.4.2 Version Info === 482 482 483 483 ... ... @@ -490,7 +490,6 @@ 490 490 ))) 491 491 492 492 493 - 494 494 === 2.4.3 Battery Info === 495 495 496 496 ... ... @@ -503,7 +503,6 @@ 503 503 ))) 504 504 505 505 506 - 507 507 === 2.4.4 Signal Strength === 508 508 509 509 ... ... @@ -536,7 +536,6 @@ 536 536 ))) 537 537 538 538 539 - 540 540 === 2.4.5 Distance === 541 541 542 542 ... ... @@ -556,10 +556,6 @@ 556 556 557 557 ))) 558 558 559 -((( 560 - 561 -))) 562 - 563 563 === 2.4.6 Digital Interrupt === 564 564 565 565 ... ... @@ -594,7 +594,6 @@ 594 594 ))) 595 595 596 596 597 - 598 598 === 2.4.7 +5V Output === 599 599 600 600 ... ... @@ -620,7 +620,6 @@ 620 620 ))) 621 621 622 622 623 - 624 624 == 2.5 Downlink Payload == 625 625 626 626 ... ... @@ -673,7 +673,6 @@ 673 673 ))) 674 674 675 675 676 - 677 677 == 2.6 Distance alarm function(Since firmware v1.3.2) == 678 678 679 679 ... ... @@ -693,7 +693,6 @@ 693 693 **AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 694 694 695 695 696 - 697 697 == 2.7 Set the number of data to be uploaded and the recording time == 698 698 699 699 ... ... @@ -702,8 +702,11 @@ 702 702 * (% 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) 703 703 * (% 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. 704 704 705 -Thi slinkexplains the relationship between TR, NOUD and TDC more clearly[[https:~~/~~/www.processon.com/view/link/6340e606e401fd390891af87>>url:https://www.processon.com/view/link/6340e606e401fd390891af87]]675 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 706 706 677 +[[image:image-20221009001114-1.png||height="687" width="955"]] 678 + 679 + 707 707 == 2.8 Read or Clear cached data == 708 708 709 709 ... ... @@ -715,7 +715,6 @@ 715 715 [[image:image-20220908175333-2.png]] 716 716 717 717 718 - 719 719 == 2.9 LED Indicator == 720 720 721 721 ... ... @@ -732,7 +732,6 @@ 732 732 ))) 733 733 734 734 735 - 736 736 == 2.10 Firmware Change Log == 737 737 738 738 ... ... @@ -741,100 +741,18 @@ 741 741 ))) 742 742 743 743 ((( 744 - 745 -))) 746 - 747 -((( 748 748 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 749 749 ))) 750 750 751 751 719 +== 2.11 Battery & Power Consumption == 752 752 753 -== 2.11 Battery Analysis == 754 754 722 +NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 755 755 756 - === 2.11.1 BatteryType===724 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 757 757 758 758 759 -((( 760 -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. 761 -))) 762 - 763 -((( 764 -The battery is designed to last for several years depends on the actually use environment and update interval. 765 -))) 766 - 767 -((( 768 -The battery related documents as below: 769 -))) 770 - 771 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 772 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 773 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 774 - 775 -((( 776 -[[image:image-20220709101450-2.png]] 777 -))) 778 - 779 - 780 - 781 -=== 2.11.2 Power consumption Analyze === 782 - 783 - 784 -((( 785 -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. 786 -))) 787 - 788 - 789 -((( 790 -Instruction to use as below: 791 -))) 792 - 793 -((( 794 -(% 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/]] 795 -))) 796 - 797 - 798 -((( 799 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose 800 -))) 801 - 802 -* ((( 803 -Product Model 804 -))) 805 -* ((( 806 -Uplink Interval 807 -))) 808 -* ((( 809 -Working Mode 810 -))) 811 - 812 -((( 813 -And the Life expectation in difference case will be shown on the right. 814 -))) 815 - 816 -[[image:image-20220709110451-3.png]] 817 - 818 - 819 - 820 -=== 2.11.3 Battery Note === 821 - 822 - 823 -((( 824 -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. 825 -))) 826 - 827 - 828 - 829 -=== 2.11.4 Replace the battery === 830 - 831 - 832 -((( 833 -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). 834 -))) 835 - 836 - 837 - 838 838 = 3. Access NB-IoT Module = 839 839 840 840 ... ... @@ -851,10 +851,8 @@ 851 851 [[image:1657333200519-600.png]] 852 852 853 853 854 - 855 855 = 4. Using the AT Commands = 856 856 857 - 858 858 == 4.1 Access AT Commands == 859 859 860 860 ... ... @@ -947,10 +947,8 @@ 947 947 AT+PWORD : Serial Access Password 948 948 949 949 950 - 951 951 = 5. FAQ = 952 952 953 - 954 954 == 5.1 How to Upgrade Firmware == 955 955 956 956 ... ... @@ -967,10 +967,8 @@ 967 967 ))) 968 968 969 969 970 - 971 971 = 6. Trouble Shooting = 972 972 973 - 974 974 == 6.1 Connection problem when uploading firmware == 975 975 976 976 ... ... @@ -983,14 +983,11 @@ 983 983 984 984 ))) 985 985 986 - 987 987 == 6.2 AT Command input doesn't work == 988 988 989 989 990 990 ((( 991 991 In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string. 992 - 993 - 994 994 ))) 995 995 996 996 ... ... @@ -1000,11 +1000,6 @@ 1000 1000 Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 1001 1001 1002 1002 1003 -(% class="wikigeneratedid" %) 1004 -((( 1005 - 1006 -))) 1007 - 1008 1008 = 8. Packing Info = 1009 1009 1010 1010 ((( ... ... @@ -1019,7 +1019,6 @@ 1019 1019 ((( 1020 1020 1021 1021 1022 - 1023 1023 (% style="color:#037691" %)**Dimension and weight**: 1024 1024 1025 1025 * Device Size: 13.0 x 5 x 4.5 cm ... ... @@ -1031,7 +1031,6 @@ 1031 1031 ((( 1032 1032 1033 1033 1034 - 1035 1035 1036 1036 ))) 1037 1037
- image-20221009001114-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +282.9 KB - Content