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)
Details
- Page properties
-
- Content
-
... ... @@ -16,6 +16,7 @@ 16 16 17 17 = 1. Introduction = 18 18 19 + 19 19 == 1.1 What is NDDS75 Distance Detection Sensor == 20 20 21 21 ((( ... ... @@ -53,6 +53,7 @@ 53 53 [[image:1657327959271-447.png]] 54 54 55 55 57 + 56 56 == 1.2 Features == 57 57 58 58 ... ... @@ -81,12 +81,12 @@ 81 81 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 86 +* - B1 @H-FDD: 2100MHz 87 +* - B3 @H-FDD: 1800MHz 88 +* - B8 @H-FDD: 900MHz 89 +* - B5 @H-FDD: 850MHz 90 +* - B20 @H-FDD: 800MHz 91 +* - B28 @H-FDD: 700MHz 90 90 91 91 (% style="color:#037691" %)**Battery:** 92 92 ... ... @@ -117,6 +117,7 @@ 117 117 118 118 119 119 122 + 120 120 == 1.5 Pin Definitions == 121 121 122 122 ... ... @@ -123,8 +123,10 @@ 123 123 [[image:1657328609906-564.png]] 124 124 125 125 129 + 126 126 = 2. Use NDDS75 to communicate with IoT Server = 127 127 132 + 128 128 == 2.1 How it works == 129 129 130 130 ... ... @@ -147,8 +147,10 @@ 147 147 148 148 ))) 149 149 155 + 150 150 == 2.2 Configure the NDDS75 == 151 151 158 + 152 152 === 2.2.1 Test Requirement === 153 153 154 154 ... ... @@ -168,6 +168,7 @@ 168 168 [[image:1657328756309-230.png]] 169 169 170 170 178 + 171 171 === 2.2.2 Insert SIM card === 172 172 173 173 ... ... @@ -183,6 +183,7 @@ 183 183 [[image:1657328884227-504.png]] 184 184 185 185 194 + 186 186 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 187 187 188 188 ... ... @@ -224,6 +224,7 @@ 224 224 ))) 225 225 226 226 236 + 227 227 === 2.2.4 Use CoAP protocol to uplink data === 228 228 229 229 ... ... @@ -243,6 +243,7 @@ 243 243 * ((( 244 244 (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 245 245 256 + 246 246 247 247 ))) 248 248 ... ... @@ -265,6 +265,7 @@ 265 265 [[image:1657330472797-498.png]] 266 266 267 267 279 + 268 268 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 269 269 270 270 ... ... @@ -278,6 +278,7 @@ 278 278 [[image:1657330533775-472.png]] 279 279 280 280 293 + 281 281 === 2.2.6 Use MQTT protocol to uplink data === 282 282 283 283 ... ... @@ -300,6 +300,7 @@ 300 300 ))) 301 301 302 302 316 + 303 303 === 2.2.7 Use TCP protocol to uplink data === 304 304 305 305 ... ... @@ -312,6 +312,7 @@ 312 312 [[image:image-20220709093918-2.png]] 313 313 314 314 329 + 315 315 === 2.2.8 Change Update Interval === 316 316 317 317 ... ... @@ -322,6 +322,7 @@ 322 322 ((( 323 323 324 324 340 + 325 325 (% style="color:red" %)**NOTE:** 326 326 327 327 (% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** ... ... @@ -332,21 +332,23 @@ 332 332 (% 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).** 333 333 334 334 351 + 335 335 == 2.3 Uplink Payload == 336 336 354 + 337 337 === 2.3.1 Before Firmware v1.3.2 === 338 338 339 339 340 340 In this mode, uplink payload includes in total 14 bytes 341 341 342 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:440px" %)343 -|=(% style="width: 6 1px;background-color:#D9E2F3;color:#0070C0" %)(((360 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 361 +|=(% style="width: 60px;" %)((( 344 344 **Size(bytes)** 345 -)))|=(% style="width: 6 1px;background-color:#D9E2F3;color:#0070C0" %)**6**|=(% style="width: 37px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 37px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 82px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 102px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**1**363 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 346 346 |(% 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"]] 347 347 348 348 ((( 349 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 367 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 350 350 ))) 351 351 352 352 ... ... @@ -353,6 +353,7 @@ 353 353 [[image:1657331036973-987.png]] 354 354 355 355 374 + 356 356 The payload is **ASCII** string, representative same HEX: 357 357 358 358 (% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 ** ... ... @@ -380,9 +380,9 @@ 380 380 381 381 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. 382 382 383 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:490px" %)384 -|(% s tyle="background-color:#d9e2f3;color:#0070c0;width:60px" %)**Size(bytes)**|(% style="background-color:#d9e2f3; color:#0070c0;width:40px" %)**8**|(% style="background-color:#d9e2f3; color:#0070c0;width:25px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0;width:25px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0;width:60px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0;width:25px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0;width:40px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0;width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0;width:70px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0;width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0;width:60px" %)**4**385 -|(% 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 +(% border="1" style="background-color:#ffffcc; color:green; width:490px" %) 403 +|=(% 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** 404 +|=(% 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....... 386 386 387 387 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 388 388 ... ... @@ -403,7 +403,7 @@ 403 403 404 404 * (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 405 405 406 -* (% style="color:#037691" %)**Mod:**(%%)** 425 +* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 407 407 408 408 * (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 409 409 ... ... @@ -419,6 +419,7 @@ 419 419 420 420 == 2.4 Payload Explanation and Sensor Interface == 421 421 441 + 422 422 === 2.4.1 Device ID === 423 423 424 424 ... ... @@ -457,6 +457,7 @@ 457 457 AT+DEUI=868411056754138 458 458 459 459 480 + 460 460 === 2.4.2 Version Info === 461 461 462 462 ... ... @@ -469,6 +469,7 @@ 469 469 ))) 470 470 471 471 493 + 472 472 === 2.4.3 Battery Info === 473 473 474 474 ... ... @@ -481,6 +481,7 @@ 481 481 ))) 482 482 483 483 506 + 484 484 === 2.4.4 Signal Strength === 485 485 486 486 ... ... @@ -513,6 +513,7 @@ 513 513 ))) 514 514 515 515 539 + 516 516 === 2.4.5 Distance === 517 517 518 518 ... ... @@ -519,13 +519,23 @@ 519 519 Get the distance. Flat object range 280mm - 7500mm. 520 520 521 521 ((( 522 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is (% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**546 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 523 523 ))) 524 524 525 525 ((( 550 +((( 551 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 552 +))) 553 +))) 554 + 555 +((( 526 526 527 527 ))) 528 528 559 +((( 560 + 561 +))) 562 + 529 529 === 2.4.6 Digital Interrupt === 530 530 531 531 ... ... @@ -546,8 +546,9 @@ 546 546 The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up. 547 547 ))) 548 548 583 + 549 549 ((( 550 - **Example:**585 +Example: 551 551 ))) 552 552 553 553 ((( ... ... @@ -559,6 +559,7 @@ 559 559 ))) 560 560 561 561 597 + 562 562 === 2.4.7 +5V Output === 563 563 564 564 ... ... @@ -566,12 +566,17 @@ 566 566 NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 567 567 ))) 568 568 605 + 569 569 ((( 570 570 The 5V output time can be controlled by AT Command. 608 + 609 + 571 571 ))) 572 572 573 573 ((( 574 574 (% style="color:blue" %)**AT+5VT=1000** 614 + 615 + 575 575 ))) 576 576 577 577 ((( ... ... @@ -579,17 +579,15 @@ 579 579 ))) 580 580 581 581 623 + 582 582 == 2.5 Downlink Payload == 583 583 584 584 585 585 By default, NDDS75 prints the downlink payload to console port. 586 586 587 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %) 588 -|(% style="background-color:#d9e2f3; color:#0070c0; width:208px" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0; width:56px" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:100px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; width:154px" %)**Downlink payload size(bytes)** 589 -|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4 590 -|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2 591 -|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4 629 +[[image:image-20220709100028-1.png]] 592 592 631 + 593 593 ((( 594 594 (% style="color:blue" %)**Examples:** 595 595 ))) ... ... @@ -634,6 +634,7 @@ 634 634 ))) 635 635 636 636 676 + 637 637 == 2.6 Distance alarm function(Since firmware v1.3.2) == 638 638 639 639 ... ... @@ -653,6 +653,7 @@ 653 653 **AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 654 654 655 655 696 + 656 656 == 2.7 Set the number of data to be uploaded and the recording time == 657 657 658 658 ... ... @@ -666,6 +666,7 @@ 666 666 [[image:image-20221009001114-1.png||height="687" width="955"]] 667 667 668 668 710 + 669 669 == 2.8 Read or Clear cached data == 670 670 671 671 ... ... @@ -677,6 +677,7 @@ 677 677 [[image:image-20220908175333-2.png]] 678 678 679 679 722 + 680 680 == 2.9 LED Indicator == 681 681 682 682 ... ... @@ -693,6 +693,7 @@ 693 693 ))) 694 694 695 695 739 + 696 696 == 2.10 Firmware Change Log == 697 697 698 698 ... ... @@ -701,18 +701,100 @@ 701 701 ))) 702 702 703 703 ((( 748 + 749 +))) 750 + 751 +((( 704 704 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 705 705 ))) 706 706 707 707 708 -== 2.11 Battery & Power Consumption == 709 709 757 +== 2.11 Battery Analysis == 710 710 711 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 712 712 713 - [[**BatteryInfo & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]].760 +=== 2.11.1 Battery Type === 714 714 715 715 763 +((( 764 +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. 765 +))) 766 + 767 +((( 768 +The battery is designed to last for several years depends on the actually use environment and update interval. 769 +))) 770 + 771 +((( 772 +The battery related documents as below: 773 +))) 774 + 775 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 776 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 777 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 778 + 779 +((( 780 +[[image:image-20220709101450-2.png]] 781 +))) 782 + 783 + 784 + 785 +=== 2.11.2 Power consumption Analyze === 786 + 787 + 788 +((( 789 +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. 790 +))) 791 + 792 + 793 +((( 794 +Instruction to use as below: 795 +))) 796 + 797 +((( 798 +(% 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/]] 799 +))) 800 + 801 + 802 +((( 803 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 804 +))) 805 + 806 +* ((( 807 +Product Model 808 +))) 809 +* ((( 810 +Uplink Interval 811 +))) 812 +* ((( 813 +Working Mode 814 +))) 815 + 816 +((( 817 +And the Life expectation in difference case will be shown on the right. 818 +))) 819 + 820 +[[image:image-20220709110451-3.png]] 821 + 822 + 823 + 824 +=== 2.11.3 Battery Note === 825 + 826 + 827 +((( 828 +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. 829 +))) 830 + 831 + 832 + 833 +=== 2.11.4 Replace the battery === 834 + 835 + 836 +((( 837 +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). 838 +))) 839 + 840 + 841 + 716 716 = 3. Access NB-IoT Module = 717 717 718 718 ... ... @@ -729,8 +729,10 @@ 729 729 [[image:1657333200519-600.png]] 730 730 731 731 858 + 732 732 = 4. Using the AT Commands = 733 733 861 + 734 734 == 4.1 Access AT Commands == 735 735 736 736 ... ... @@ -823,8 +823,10 @@ 823 823 AT+PWORD : Serial Access Password 824 824 825 825 954 + 826 826 = 5. FAQ = 827 827 957 + 828 828 == 5.1 How to Upgrade Firmware == 829 829 830 830 ... ... @@ -841,8 +841,10 @@ 841 841 ))) 842 842 843 843 974 + 844 844 = 6. Trouble Shooting = 845 845 977 + 846 846 == 6.1 Connection problem when uploading firmware == 847 847 848 848 ... ... @@ -855,20 +855,17 @@ 855 855 856 856 ))) 857 857 990 + 858 858 == 6.2 AT Command input doesn't work == 859 859 860 860 861 861 ((( 862 862 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. 996 + 997 + 863 863 ))) 864 864 865 865 866 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 867 - 868 - 869 -This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**. 870 - 871 - 872 872 = 7. Order Info = 873 873 874 874 ... ... @@ -875,6 +875,11 @@ 875 875 Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 876 876 877 877 1007 +(% class="wikigeneratedid" %) 1008 +((( 1009 + 1010 +))) 1011 + 878 878 = 8. Packing Info = 879 879 880 880 ((( ... ... @@ -889,6 +889,7 @@ 889 889 ((( 890 890 891 891 1026 + 892 892 (% style="color:#037691" %)**Dimension and weight**: 893 893 894 894 * Device Size: 13.0 x 5 x 4.5 cm ... ... @@ -900,6 +900,7 @@ 900 900 ((( 901 901 902 902 1038 + 903 903 904 904 ))) 905 905 ... ... @@ -907,5 +907,4 @@ 907 907 908 908 909 909 * 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. 910 - 911 911 * 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]]