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 ... ... @@ -70,6 +70,7 @@ 70 70 * 8500mAh Battery for long term use 71 71 72 72 75 + 73 73 == 1.3 Specification == 74 74 75 75 ... ... @@ -80,12 +80,12 @@ 80 80 81 81 (% style="color:#037691" %)**NB-IoT Spec:** 82 82 83 -* B1 @H-FDD: 2100MHz 84 -* B3 @H-FDD: 1800MHz 85 -* B8 @H-FDD: 900MHz 86 -* B5 @H-FDD: 850MHz 87 -* B20 @H-FDD: 800MHz 88 -* 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 89 89 90 90 (% style="color:#037691" %)**Battery:** 91 91 ... ... @@ -101,6 +101,7 @@ 101 101 * Max transmit power: 350mA@3.3v 102 102 103 103 107 + 104 104 == 1.4 Applications == 105 105 106 106 ... ... @@ -115,6 +115,7 @@ 115 115 116 116 117 117 122 + 118 118 == 1.5 Pin Definitions == 119 119 120 120 ... ... @@ -121,8 +121,10 @@ 121 121 [[image:1657328609906-564.png]] 122 122 123 123 129 + 124 124 = 2. Use NDDS75 to communicate with IoT Server = 125 125 132 + 126 126 == 2.1 How it works == 127 127 128 128 ... ... @@ -145,8 +145,10 @@ 145 145 146 146 ))) 147 147 155 + 148 148 == 2.2 Configure the NDDS75 == 149 149 158 + 150 150 === 2.2.1 Test Requirement === 151 151 152 152 ... ... @@ -166,6 +166,7 @@ 166 166 [[image:1657328756309-230.png]] 167 167 168 168 178 + 169 169 === 2.2.2 Insert SIM card === 170 170 171 171 ... ... @@ -181,6 +181,7 @@ 181 181 [[image:1657328884227-504.png]] 182 182 183 183 194 + 184 184 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 185 185 186 186 ... ... @@ -222,6 +222,7 @@ 222 222 ))) 223 223 224 224 236 + 225 225 === 2.2.4 Use CoAP protocol to uplink data === 226 226 227 227 ... ... @@ -264,6 +264,7 @@ 264 264 [[image:1657330472797-498.png]] 265 265 266 266 279 + 267 267 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 268 268 269 269 ... ... @@ -277,6 +277,7 @@ 277 277 [[image:1657330533775-472.png]] 278 278 279 279 293 + 280 280 === 2.2.6 Use MQTT protocol to uplink data === 281 281 282 282 ... ... @@ -299,6 +299,7 @@ 299 299 ))) 300 300 301 301 316 + 302 302 === 2.2.7 Use TCP protocol to uplink data === 303 303 304 304 ... ... @@ -311,6 +311,7 @@ 311 311 [[image:image-20220709093918-2.png]] 312 312 313 313 329 + 314 314 === 2.2.8 Change Update Interval === 315 315 316 316 ... ... @@ -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 ** ... ... @@ -372,6 +372,7 @@ 372 372 * (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0 373 373 374 374 394 + 375 375 === 2.3.2 Since firmware v1.3.2 === 376 376 377 377 ... ... @@ -379,8 +379,8 @@ 379 379 380 380 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. 381 381 382 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:490px" %)383 -|=(% style="width: 60px; background-color:#D9E2F3;color:#0070C0" %)**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**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** 384 384 |=(% 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 385 386 386 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. ... ... @@ -402,7 +402,7 @@ 402 402 403 403 * (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 404 404 405 -* (% style="color:#037691" %)**Mod:**(%%)** 425 +* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 406 406 407 407 * (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 408 408 ... ... @@ -415,8 +415,10 @@ 415 415 * (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 416 416 417 417 438 + 418 418 == 2.4 Payload Explanation and Sensor Interface == 419 419 441 + 420 420 === 2.4.1 Device ID === 421 421 422 422 ... ... @@ -455,6 +455,7 @@ 455 455 AT+DEUI=868411056754138 456 456 457 457 480 + 458 458 === 2.4.2 Version Info === 459 459 460 460 ... ... @@ -467,6 +467,7 @@ 467 467 ))) 468 468 469 469 493 + 470 470 === 2.4.3 Battery Info === 471 471 472 472 ... ... @@ -479,6 +479,7 @@ 479 479 ))) 480 480 481 481 506 + 482 482 === 2.4.4 Signal Strength === 483 483 484 484 ... ... @@ -511,6 +511,7 @@ 511 511 ))) 512 512 513 513 539 + 514 514 === 2.4.5 Distance === 515 515 516 516 ... ... @@ -530,6 +530,10 @@ 530 530 531 531 ))) 532 532 559 +((( 560 + 561 +))) 562 + 533 533 === 2.4.6 Digital Interrupt === 534 534 535 535 ... ... @@ -564,6 +564,7 @@ 564 564 ))) 565 565 566 566 597 + 567 567 === 2.4.7 +5V Output === 568 568 569 569 ... ... @@ -589,17 +589,15 @@ 589 589 ))) 590 590 591 591 623 + 592 592 == 2.5 Downlink Payload == 593 593 594 594 595 595 By default, NDDS75 prints the downlink payload to console port. 596 596 597 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %) 598 -|(% 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)** 599 -|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4 600 -|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2 601 -|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4 629 +[[image:image-20220709100028-1.png]] 602 602 631 + 603 603 ((( 604 604 (% style="color:blue" %)**Examples:** 605 605 ))) ... ... @@ -644,6 +644,7 @@ 644 644 ))) 645 645 646 646 676 + 647 647 == 2.6 Distance alarm function(Since firmware v1.3.2) == 648 648 649 649 ... ... @@ -663,6 +663,7 @@ 663 663 **AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 664 664 665 665 696 + 666 666 == 2.7 Set the number of data to be uploaded and the recording time == 667 667 668 668 ... ... @@ -676,6 +676,7 @@ 676 676 [[image:image-20221009001114-1.png||height="687" width="955"]] 677 677 678 678 710 + 679 679 == 2.8 Read or Clear cached data == 680 680 681 681 ... ... @@ -687,6 +687,7 @@ 687 687 [[image:image-20220908175333-2.png]] 688 688 689 689 722 + 690 690 == 2.9 LED Indicator == 691 691 692 692 ... ... @@ -703,6 +703,7 @@ 703 703 ))) 704 704 705 705 739 + 706 706 == 2.10 Firmware Change Log == 707 707 708 708 ... ... @@ -711,18 +711,100 @@ 711 711 ))) 712 712 713 713 ((( 748 + 749 +))) 750 + 751 +((( 714 714 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 715 715 ))) 716 716 717 717 718 -== 2.11 Battery & Power Consumption == 719 719 757 +== 2.11 Battery Analysis == 720 720 721 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 722 722 723 - [[**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 === 724 724 725 725 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 + 726 726 = 3. Access NB-IoT Module = 727 727 728 728 ... ... @@ -739,8 +739,10 @@ 739 739 [[image:1657333200519-600.png]] 740 740 741 741 858 + 742 742 = 4. Using the AT Commands = 743 743 861 + 744 744 == 4.1 Access AT Commands == 745 745 746 746 ... ... @@ -833,8 +833,10 @@ 833 833 AT+PWORD : Serial Access Password 834 834 835 835 954 + 836 836 = 5. FAQ = 837 837 957 + 838 838 == 5.1 How to Upgrade Firmware == 839 839 840 840 ... ... @@ -851,8 +851,10 @@ 851 851 ))) 852 852 853 853 974 + 854 854 = 6. Trouble Shooting = 855 855 977 + 856 856 == 6.1 Connection problem when uploading firmware == 857 857 858 858 ... ... @@ -865,20 +865,17 @@ 865 865 866 866 ))) 867 867 990 + 868 868 == 6.2 AT Command input doesn't work == 869 869 870 870 871 871 ((( 872 872 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 + 873 873 ))) 874 874 875 875 876 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 877 - 878 - 879 -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]]//**. 880 - 881 - 882 882 = 7. Order Info = 883 883 884 884 ... ... @@ -885,6 +885,11 @@ 885 885 Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 886 886 887 887 1007 +(% class="wikigeneratedid" %) 1008 +((( 1009 + 1010 +))) 1011 + 888 888 = 8. Packing Info = 889 889 890 890 ((( ... ... @@ -899,6 +899,7 @@ 899 899 ((( 900 900 901 901 1026 + 902 902 (% style="color:#037691" %)**Dimension and weight**: 903 903 904 904 * Device Size: 13.0 x 5 x 4.5 cm ... ... @@ -910,6 +910,7 @@ 910 910 ((( 911 911 912 912 1038 + 913 913 914 914 ))) 915 915 ... ... @@ -917,5 +917,4 @@ 917 917 918 918 919 919 * 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. 920 - 921 921 * 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]]