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 ... ... @@ -69,6 +69,8 @@ 69 69 * Micro SIM card slot for NB-IoT SIM 70 70 * 8500mAh Battery for long term use 71 71 74 + 75 + 72 72 == 1.3 Specification == 73 73 74 74 ... ... @@ -79,12 +79,12 @@ 79 79 80 80 (% style="color:#037691" %)**NB-IoT Spec:** 81 81 82 -* B1 @H-FDD: 2100MHz 83 -* B3 @H-FDD: 1800MHz 84 -* B8 @H-FDD: 900MHz 85 -* B5 @H-FDD: 850MHz 86 -* B20 @H-FDD: 800MHz 87 -* 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 88 88 89 89 (% style="color:#037691" %)**Battery:** 90 90 ... ... @@ -99,6 +99,8 @@ 99 99 * STOP Mode: 10uA @ 3.3v 100 100 * Max transmit power: 350mA@3.3v 101 101 106 + 107 + 102 102 == 1.4 Applications == 103 103 104 104 ... ... @@ -113,6 +113,7 @@ 113 113 114 114 115 115 122 + 116 116 == 1.5 Pin Definitions == 117 117 118 118 ... ... @@ -119,8 +119,10 @@ 119 119 [[image:1657328609906-564.png]] 120 120 121 121 129 + 122 122 = 2. Use NDDS75 to communicate with IoT Server = 123 123 132 + 124 124 == 2.1 How it works == 125 125 126 126 ... ... @@ -143,8 +143,10 @@ 143 143 144 144 ))) 145 145 155 + 146 146 == 2.2 Configure the NDDS75 == 147 147 158 + 148 148 === 2.2.1 Test Requirement === 149 149 150 150 ... ... @@ -164,6 +164,7 @@ 164 164 [[image:1657328756309-230.png]] 165 165 166 166 178 + 167 167 === 2.2.2 Insert SIM card === 168 168 169 169 ... ... @@ -179,6 +179,7 @@ 179 179 [[image:1657328884227-504.png]] 180 180 181 181 194 + 182 182 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 183 183 184 184 ... ... @@ -220,6 +220,7 @@ 220 220 ))) 221 221 222 222 236 + 223 223 === 2.2.4 Use CoAP protocol to uplink data === 224 224 225 225 ... ... @@ -262,6 +262,7 @@ 262 262 [[image:1657330472797-498.png]] 263 263 264 264 279 + 265 265 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 266 266 267 267 ... ... @@ -275,6 +275,7 @@ 275 275 [[image:1657330533775-472.png]] 276 276 277 277 293 + 278 278 === 2.2.6 Use MQTT protocol to uplink data === 279 279 280 280 ... ... @@ -297,6 +297,7 @@ 297 297 ))) 298 298 299 299 316 + 300 300 === 2.2.7 Use TCP protocol to uplink data === 301 301 302 302 ... ... @@ -309,6 +309,7 @@ 309 309 [[image:image-20220709093918-2.png]] 310 310 311 311 329 + 312 312 === 2.2.8 Change Update Interval === 313 313 314 314 ... ... @@ -330,21 +330,23 @@ 330 330 (% 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).** 331 331 332 332 351 + 333 333 == 2.3 Uplink Payload == 334 334 354 + 335 335 === 2.3.1 Before Firmware v1.3.2 === 336 336 337 337 338 338 In this mode, uplink payload includes in total 14 bytes 339 339 340 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:440px" %)341 -|=(% style="width: 60px; background-color:#D9E2F3;color:#0070C0" %)(((360 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 361 +|=(% style="width: 60px;" %)((( 342 342 **Size(bytes)** 343 -)))|=(% style="width: 60px; background-color:#D9E2F3;color:#0070C0" %)**6**|=(% style="width: 35px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 35px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 80px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 100px;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** 344 344 |(% 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"]] 345 345 346 346 ((( 347 -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. 348 348 ))) 349 349 350 350 ... ... @@ -351,6 +351,7 @@ 351 351 [[image:1657331036973-987.png]] 352 352 353 353 374 + 354 354 The payload is **ASCII** string, representative same HEX: 355 355 356 356 (% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 ** ... ... @@ -369,6 +369,8 @@ 369 369 370 370 * (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0 371 371 393 + 394 + 372 372 === 2.3.2 Since firmware v1.3.2 === 373 373 374 374 ... ... @@ -376,8 +376,8 @@ 376 376 377 377 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. 378 378 379 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:490px" %)380 -|=(% 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** 381 381 |=(% 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....... 382 382 383 383 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. ... ... @@ -399,7 +399,7 @@ 399 399 400 400 * (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 401 401 402 -* (% style="color:#037691" %)**Mod:**(%%)** 425 +* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 403 403 404 404 * (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 405 405 ... ... @@ -411,8 +411,11 @@ 411 411 412 412 * (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 413 413 437 + 438 + 414 414 == 2.4 Payload Explanation and Sensor Interface == 415 415 441 + 416 416 === 2.4.1 Device ID === 417 417 418 418 ... ... @@ -451,6 +451,7 @@ 451 451 AT+DEUI=868411056754138 452 452 453 453 480 + 454 454 === 2.4.2 Version Info === 455 455 456 456 ... ... @@ -463,6 +463,7 @@ 463 463 ))) 464 464 465 465 493 + 466 466 === 2.4.3 Battery Info === 467 467 468 468 ... ... @@ -475,6 +475,7 @@ 475 475 ))) 476 476 477 477 506 + 478 478 === 2.4.4 Signal Strength === 479 479 480 480 ... ... @@ -507,6 +507,7 @@ 507 507 ))) 508 508 509 509 539 + 510 510 === 2.4.5 Distance === 511 511 512 512 ... ... @@ -526,6 +526,10 @@ 526 526 527 527 ))) 528 528 559 +((( 560 + 561 +))) 562 + 529 529 === 2.4.6 Digital Interrupt === 530 530 531 531 ... ... @@ -560,6 +560,7 @@ 560 560 ))) 561 561 562 562 597 + 563 563 === 2.4.7 +5V Output === 564 564 565 565 ... ... @@ -585,19 +585,15 @@ 585 585 ))) 586 586 587 587 623 + 588 588 == 2.5 Downlink Payload == 589 589 590 590 591 591 By default, NDDS75 prints the downlink payload to console port. 592 592 593 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %) 594 -|(% style="width:208px;background-color:#D9E2F3;color:#0070C0" %)**Downlink Control Type**|(% style="width:56px;background-color:#D9E2F3;color:#0070C0" %)**FPort**|(% style="width:100px;background-color:#D9E2F3;color:#0070C0" %)**Type Code**|(% style="width:154px;background-color:#D9E2F3;color:#0070C0" %)**Downlink payload size(bytes)** 595 -|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4 596 -|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2 597 -|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4 629 +[[image:image-20220709100028-1.png]] 598 598 599 599 600 - 601 601 ((( 602 602 (% style="color:blue" %)**Examples:** 603 603 ))) ... ... @@ -642,6 +642,7 @@ 642 642 ))) 643 643 644 644 676 + 645 645 == 2.6 Distance alarm function(Since firmware v1.3.2) == 646 646 647 647 ... ... @@ -661,6 +661,7 @@ 661 661 **AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 662 662 663 663 696 + 664 664 == 2.7 Set the number of data to be uploaded and the recording time == 665 665 666 666 ... ... @@ -674,6 +674,7 @@ 674 674 [[image:image-20221009001114-1.png||height="687" width="955"]] 675 675 676 676 710 + 677 677 == 2.8 Read or Clear cached data == 678 678 679 679 ... ... @@ -685,6 +685,7 @@ 685 685 [[image:image-20220908175333-2.png]] 686 686 687 687 722 + 688 688 == 2.9 LED Indicator == 689 689 690 690 ... ... @@ -701,6 +701,7 @@ 701 701 ))) 702 702 703 703 739 + 704 704 == 2.10 Firmware Change Log == 705 705 706 706 ... ... @@ -709,18 +709,100 @@ 709 709 ))) 710 710 711 711 ((( 748 + 749 +))) 750 + 751 +((( 712 712 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 713 713 ))) 714 714 715 715 716 -== 2.11 Battery & Power Consumption == 717 717 757 +== 2.11 Battery Analysis == 718 718 719 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 720 720 721 - [[**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 === 722 722 723 723 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 + 724 724 = 3. Access NB-IoT Module = 725 725 726 726 ... ... @@ -737,8 +737,10 @@ 737 737 [[image:1657333200519-600.png]] 738 738 739 739 858 + 740 740 = 4. Using the AT Commands = 741 741 861 + 742 742 == 4.1 Access AT Commands == 743 743 744 744 ... ... @@ -831,8 +831,10 @@ 831 831 AT+PWORD : Serial Access Password 832 832 833 833 954 + 834 834 = 5. FAQ = 835 835 957 + 836 836 == 5.1 How to Upgrade Firmware == 837 837 838 838 ... ... @@ -849,8 +849,10 @@ 849 849 ))) 850 850 851 851 974 + 852 852 = 6. Trouble Shooting = 853 853 977 + 854 854 == 6.1 Connection problem when uploading firmware == 855 855 856 856 ... ... @@ -863,20 +863,17 @@ 863 863 864 864 ))) 865 865 990 + 866 866 == 6.2 AT Command input doesn't work == 867 867 868 868 869 869 ((( 870 870 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 + 871 871 ))) 872 872 873 873 874 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 875 - 876 - 877 -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]]//**. 878 - 879 - 880 880 = 7. Order Info = 881 881 882 882 ... ... @@ -883,6 +883,11 @@ 883 883 Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 884 884 885 885 1007 +(% class="wikigeneratedid" %) 1008 +((( 1009 + 1010 +))) 1011 + 886 886 = 8. Packing Info = 887 887 888 888 ((( ... ... @@ -897,6 +897,7 @@ 897 897 ((( 898 898 899 899 1026 + 900 900 (% style="color:#037691" %)**Dimension and weight**: 901 901 902 902 * Device Size: 13.0 x 5 x 4.5 cm ... ... @@ -908,6 +908,7 @@ 908 908 ((( 909 909 910 910 1038 + 911 911 912 912 ))) 913 913 ... ... @@ -915,5 +915,4 @@ 915 915 916 916 917 917 * 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. 918 - 919 919 * 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]]