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 (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -NDDS75 --NB-IoT Distance Detect Sensor User Manual1 +NDDS75 NB-IoT Distance Detect Sensor User Manual - 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 ... ... @@ -175,9 +175,11 @@ 175 175 User need to take out the NB-IoT module and insert the SIM card like below: 176 176 ))) 177 177 190 + 178 178 [[image:1657328884227-504.png]] 179 179 180 180 194 + 181 181 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 182 182 183 183 ... ... @@ -219,6 +219,7 @@ 219 219 ))) 220 220 221 221 236 + 222 222 === 2.2.4 Use CoAP protocol to uplink data === 223 223 224 224 ... ... @@ -238,6 +238,7 @@ 238 238 * ((( 239 239 (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 240 240 256 + 241 241 242 242 ))) 243 243 ... ... @@ -250,13 +250,17 @@ 250 250 [[image:1657330452568-615.png]] 251 251 252 252 269 + 253 253 ((( 254 254 After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server. 272 + 273 + 255 255 ))) 256 256 257 257 [[image:1657330472797-498.png]] 258 258 259 259 279 + 260 260 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 261 261 262 262 ... ... @@ -270,6 +270,7 @@ 270 270 [[image:1657330533775-472.png]] 271 271 272 272 293 + 273 273 === 2.2.6 Use MQTT protocol to uplink data === 274 274 275 275 ... ... @@ -292,6 +292,7 @@ 292 292 ))) 293 293 294 294 316 + 295 295 === 2.2.7 Use TCP protocol to uplink data === 296 296 297 297 ... ... @@ -304,6 +304,7 @@ 304 304 [[image:image-20220709093918-2.png]] 305 305 306 306 329 + 307 307 === 2.2.8 Change Update Interval === 308 308 309 309 ... ... @@ -314,6 +314,7 @@ 314 314 ((( 315 315 316 316 340 + 317 317 (% style="color:red" %)**NOTE:** 318 318 319 319 (% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** ... ... @@ -324,21 +324,23 @@ 324 324 (% 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).** 325 325 326 326 351 + 327 327 == 2.3 Uplink Payload == 328 328 354 + 329 329 === 2.3.1 Before Firmware v1.3.2 === 330 330 331 331 332 332 In this mode, uplink payload includes in total 14 bytes 333 333 334 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:440px" %)335 -|=(% style="width: 6 1px;background-color:#4F81BD;color:white" %)(((360 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 361 +|=(% style="width: 60px;" %)((( 336 336 **Size(bytes)** 337 -)))|=(% style="width: 6 1px;background-color:#4F81BD;color:white" %)**6**|=(% style="width: 37px;background-color:#4F81BD;color:white" %)2|=(% style="width: 37px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 82px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 102px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**1**338 -|(% 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"]] 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** 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"]] 339 339 340 340 ((( 341 -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. 342 342 ))) 343 343 344 344 ... ... @@ -345,6 +345,7 @@ 345 345 [[image:1657331036973-987.png]] 346 346 347 347 374 + 348 348 The payload is **ASCII** string, representative same HEX: 349 349 350 350 (% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 ** ... ... @@ -363,6 +363,8 @@ 363 363 364 364 * (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0 365 365 393 + 394 + 366 366 === 2.3.2 Since firmware v1.3.2 === 367 367 368 368 ... ... @@ -370,9 +370,9 @@ 370 370 371 371 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. 372 372 373 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:490px" %)374 -|(% s tyle="background-color:#4F81BD;color:white;width:60px" %)**Size(bytes)**|(% style="background-color:#4F81BD;color:white; width:40px" %)**8**|(% style="background-color:#4F81BD;color:white; width:25px" %)**2**|(% style="background-color:#4F81BD;color:white; width:25px" %)**2**|(% style="background-color:#4F81BD;color:white; width:60px" %)**1**|(% style="background-color:#4F81BD;color:white; width:25px" %)**1**|(% style="background-color:#4F81BD;color:white; width:40px" %)**1**|(% style="background-color:#4F81BD;color:white; width:40px" %)**2**|(% style="background-color:#4F81BD;color:white; width:70px" %)**4**|(% style="background-color:#4F81BD;color:white; width:40px" %)**2**|(% style="background-color:#4F81BD;color:white; width:60px" %)**4**375 -|(% 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....... 376 376 377 377 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 378 378 ... ... @@ -393,7 +393,7 @@ 393 393 394 394 * (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 395 395 396 -* (% style="color:#037691" %)**Mod:**(%%)** 425 +* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 397 397 398 398 * (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 399 399 ... ... @@ -405,8 +405,11 @@ 405 405 406 406 * (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 407 407 437 + 438 + 408 408 == 2.4 Payload Explanation and Sensor Interface == 409 409 441 + 410 410 === 2.4.1 Device ID === 411 411 412 412 ... ... @@ -445,6 +445,7 @@ 445 445 AT+DEUI=868411056754138 446 446 447 447 480 + 448 448 === 2.4.2 Version Info === 449 449 450 450 ... ... @@ -457,6 +457,7 @@ 457 457 ))) 458 458 459 459 493 + 460 460 === 2.4.3 Battery Info === 461 461 462 462 ... ... @@ -469,6 +469,7 @@ 469 469 ))) 470 470 471 471 506 + 472 472 === 2.4.4 Signal Strength === 473 473 474 474 ... ... @@ -501,6 +501,7 @@ 501 501 ))) 502 502 503 503 539 + 504 504 === 2.4.5 Distance === 505 505 506 506 ... ... @@ -507,13 +507,23 @@ 507 507 Get the distance. Flat object range 280mm - 7500mm. 508 508 509 509 ((( 510 -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 511 511 ))) 512 512 513 513 ((( 550 +((( 551 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 552 +))) 553 +))) 554 + 555 +((( 514 514 515 515 ))) 516 516 559 +((( 560 + 561 +))) 562 + 517 517 === 2.4.6 Digital Interrupt === 518 518 519 519 ... ... @@ -534,8 +534,9 @@ 534 534 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. 535 535 ))) 536 536 583 + 537 537 ((( 538 - **Example:**585 +Example: 539 539 ))) 540 540 541 541 ((( ... ... @@ -547,6 +547,7 @@ 547 547 ))) 548 548 549 549 597 + 550 550 === 2.4.7 +5V Output === 551 551 552 552 ... ... @@ -554,12 +554,17 @@ 554 554 NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 555 555 ))) 556 556 605 + 557 557 ((( 558 558 The 5V output time can be controlled by AT Command. 608 + 609 + 559 559 ))) 560 560 561 561 ((( 562 562 (% style="color:blue" %)**AT+5VT=1000** 614 + 615 + 563 563 ))) 564 564 565 565 ((( ... ... @@ -567,17 +567,15 @@ 567 567 ))) 568 568 569 569 623 + 570 570 == 2.5 Downlink Payload == 571 571 572 572 573 573 By default, NDDS75 prints the downlink payload to console port. 574 574 575 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:520px" %) 576 -|(% style="background-color:#4F81BD;color:white; width:208px" %)**Downlink Control Type**|(% style="background-color:#4F81BD;color:white; width:56px" %)**FPort**|(% style="background-color:#4F81BD;color:white; width:100px" %)**Type Code**|(% style="background-color:#4F81BD;color:white; width:154px" %)**Downlink payload size(bytes)** 577 -|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4 578 -|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2 579 -|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4 629 +[[image:image-20220709100028-1.png]] 580 580 631 + 581 581 ((( 582 582 (% style="color:blue" %)**Examples:** 583 583 ))) ... ... @@ -622,6 +622,7 @@ 622 622 ))) 623 623 624 624 676 + 625 625 == 2.6 Distance alarm function(Since firmware v1.3.2) == 626 626 627 627 ... ... @@ -641,6 +641,7 @@ 641 641 **AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 642 642 643 643 696 + 644 644 == 2.7 Set the number of data to be uploaded and the recording time == 645 645 646 646 ... ... @@ -654,6 +654,7 @@ 654 654 [[image:image-20221009001114-1.png||height="687" width="955"]] 655 655 656 656 710 + 657 657 == 2.8 Read or Clear cached data == 658 658 659 659 ... ... @@ -665,6 +665,7 @@ 665 665 [[image:image-20220908175333-2.png]] 666 666 667 667 722 + 668 668 == 2.9 LED Indicator == 669 669 670 670 ... ... @@ -681,6 +681,7 @@ 681 681 ))) 682 682 683 683 739 + 684 684 == 2.10 Firmware Change Log == 685 685 686 686 ... ... @@ -689,18 +689,100 @@ 689 689 ))) 690 690 691 691 ((( 748 + 749 +))) 750 + 751 +((( 692 692 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 693 693 ))) 694 694 695 695 696 -== 2.11 Battery & Power Consumption == 697 697 757 +== 2.11 Battery Analysis == 698 698 699 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 700 700 701 - [[**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 === 702 702 703 703 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 + 704 704 = 3. Access NB-IoT Module = 705 705 706 706 ... ... @@ -717,8 +717,10 @@ 717 717 [[image:1657333200519-600.png]] 718 718 719 719 858 + 720 720 = 4. Using the AT Commands = 721 721 861 + 722 722 == 4.1 Access AT Commands == 723 723 724 724 ... ... @@ -811,8 +811,10 @@ 811 811 AT+PWORD : Serial Access Password 812 812 813 813 954 + 814 814 = 5. FAQ = 815 815 957 + 816 816 == 5.1 How to Upgrade Firmware == 817 817 818 818 ... ... @@ -829,8 +829,10 @@ 829 829 ))) 830 830 831 831 974 + 832 832 = 6. Trouble Shooting = 833 833 977 + 834 834 == 6.1 Connection problem when uploading firmware == 835 835 836 836 ... ... @@ -843,20 +843,17 @@ 843 843 844 844 ))) 845 845 990 + 846 846 == 6.2 AT Command input doesn't work == 847 847 848 848 849 849 ((( 850 850 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 + 851 851 ))) 852 852 853 853 854 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 855 - 856 - 857 -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]]//**. 858 - 859 - 860 860 = 7. Order Info = 861 861 862 862 ... ... @@ -863,6 +863,11 @@ 863 863 Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 864 864 865 865 1007 +(% class="wikigeneratedid" %) 1008 +((( 1009 + 1010 +))) 1011 + 866 866 = 8. Packing Info = 867 867 868 868 ((( ... ... @@ -877,6 +877,7 @@ 877 877 ((( 878 878 879 879 1026 + 880 880 (% style="color:#037691" %)**Dimension and weight**: 881 881 882 882 * Device Size: 13.0 x 5 x 4.5 cm ... ... @@ -888,6 +888,7 @@ 888 888 ((( 889 889 890 890 1038 + 891 891 892 892 ))) 893 893 ... ... @@ -895,5 +895,4 @@ 895 895 896 896 897 897 * 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. 898 - 899 899 * 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]]