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
-
... ... @@ -22,20 +22,34 @@ 22 22 23 23 24 24 ((( 25 +((( 25 25 The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data. 26 -\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network. 27 -\\NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage. 28 -\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 29 -\\NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 30 -\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection. 31 31 ))) 32 32 33 - 29 +((( 30 +The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network. 34 34 ))) 35 35 36 -[[image:1654503236291-817.png]] 33 +((( 34 +NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage. 35 +))) 37 37 37 +((( 38 +NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 39 +))) 38 38 41 +((( 42 +NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 43 +))) 44 + 45 +((( 46 +To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection. 47 +))) 48 +))) 49 + 50 + 51 +))) 52 + 39 39 [[image:1657327959271-447.png]] 40 40 41 41 ... ... @@ -86,12 +86,13 @@ 86 86 (% style="color:#037691" %)**Power Consumption** 87 87 88 88 * STOP Mode: 10uA @ 3.3v 89 -* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]103 +* Max transmit power: 350mA@3.3v 90 90 91 91 92 92 93 93 == 1.4 Applications == 94 94 109 + 95 95 * Smart Buildings & Home Automation 96 96 * Logistics and Supply Chain Management 97 97 * Smart Metering ... ... @@ -114,6 +114,7 @@ 114 114 115 115 == 2.1 How it works == 116 116 132 + 117 117 ((( 118 118 The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75. 119 119 ))) ... ... @@ -139,16 +139,17 @@ 139 139 140 140 === 2.2.1 Test Requirement === 141 141 158 + 142 142 ((( 143 143 To use NDDS75 in your city, make sure meet below requirements: 144 144 ))) 145 145 146 146 * Your local operator has already distributed a NB-IoT Network there. 147 -* The local NB-IoT network used the band that NS E01supports.164 +* The local NB-IoT network used the band that NDDS75 supports. 148 148 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 149 149 150 150 ((( 151 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server 168 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server. 152 152 ))) 153 153 154 154 ... ... @@ -158,6 +158,7 @@ 158 158 159 159 === 2.2.2 Insert SIM card === 160 160 178 + 161 161 ((( 162 162 Insert the NB-IoT Card get from your provider. 163 163 ))) ... ... @@ -173,6 +173,7 @@ 173 173 174 174 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 175 175 194 + 176 176 ((( 177 177 ((( 178 178 User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below. ... ... @@ -212,21 +212,34 @@ 212 212 213 213 === 2.2.4 Use CoAP protocol to uplink data === 214 214 215 -(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 216 216 235 +(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]** 217 217 237 + 238 +((( 218 218 **Use below commands:** 240 +))) 219 219 220 -* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 221 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 222 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 242 +* ((( 243 +(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 244 +))) 245 +* ((( 246 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 247 +))) 248 +* ((( 249 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 250 +))) 223 223 252 +((( 224 224 For parameter description, please refer to AT command set 254 +))) 225 225 226 226 [[image:1657330452568-615.png]] 227 227 228 228 259 +((( 229 229 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. 261 +))) 230 230 231 231 [[image:1657330472797-498.png]] 232 232 ... ... @@ -235,9 +235,9 @@ 235 235 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 236 236 237 237 238 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 270 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 239 239 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 240 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 272 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 241 241 242 242 [[image:1657330501006-241.png]] 243 243 ... ... @@ -249,11 +249,11 @@ 249 249 === 2.2.6 Use MQTT protocol to uplink data === 250 250 251 251 252 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 253 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 254 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 255 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 256 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 284 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 285 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 286 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 287 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 288 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 257 257 * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 258 258 * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 259 259 ... ... @@ -284,6 +284,7 @@ 284 284 285 285 === 2.2.8 Change Update Interval === 286 286 319 + 287 287 User can use below command to change the (% style="color:green" %)**uplink interval**. 288 288 289 289 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -293,7 +293,7 @@ 293 293 ))) 294 294 295 295 ((( 296 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 329 +(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** 297 297 ))) 298 298 299 299 ... ... @@ -300,13 +300,14 @@ 300 300 301 301 == 2.3 Uplink Payload == 302 302 336 + 303 303 In this mode, uplink payload includes in total 14 bytes 304 304 305 305 306 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width: 510px" %)307 -|=(% style="width: 80px;" %)(((340 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 341 +|=(% style="width: 60px;" %)((( 308 308 **Size(bytes)** 309 -)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width:110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width:70px;" %)**1**343 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 310 310 |(% 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"]] 311 311 312 312 ((( ... ... @@ -353,6 +353,7 @@ 353 353 354 354 === 2.4.1 Device ID === 355 355 390 + 356 356 ((( 357 357 By default, the Device ID equal to the last 6 bytes of IMEI. 358 358 ))) ... ... @@ -377,6 +377,7 @@ 377 377 378 378 === 2.4.2 Version Info === 379 379 415 + 380 380 ((( 381 381 Specify the software version: 0x64=100, means firmware version 1.00. 382 382 ))) ... ... @@ -389,9 +389,6 @@ 389 389 390 390 === 2.4.3 Battery Info === 391 391 392 -((( 393 -Check the battery voltage for LSE01. 394 -))) 395 395 396 396 ((( 397 397 Ex1: 0x0B45 = 2885mV ... ... @@ -405,6 +405,7 @@ 405 405 406 406 === 2.4.4 Signal Strength === 407 407 441 + 408 408 ((( 409 409 NB-IoT Network signal Strength. 410 410 ))) ... ... @@ -437,9 +437,12 @@ 437 437 438 438 === 2.4.5 Distance === 439 439 474 + 440 440 Get the distance. Flat object range 280mm - 7500mm. 441 441 477 +((( 442 442 For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 479 +))) 443 443 444 444 ((( 445 445 ((( ... ... @@ -457,6 +457,7 @@ 457 457 458 458 === 2.4.6 Digital Interrupt === 459 459 497 + 460 460 ((( 461 461 Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server. 462 462 ))) ... ... @@ -491,6 +491,7 @@ 491 491 492 492 === 2.4.7 +5V Output === 493 493 532 + 494 494 ((( 495 495 NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 496 496 ))) ... ... @@ -512,6 +512,7 @@ 512 512 513 513 == 2.5 Downlink Payload == 514 514 554 + 515 515 By default, NDDS75 prints the downlink payload to console port. 516 516 517 517 [[image:image-20220709100028-1.png]] ... ... @@ -582,7 +582,9 @@ 582 582 == 2.7 Firmware Change Log == 583 583 584 584 625 +((( 585 585 Download URL & Firmware Change log 627 +))) 586 586 587 587 ((( 588 588 [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]] ... ... @@ -589,7 +589,9 @@ 589 589 ))) 590 590 591 591 634 +((( 592 592 Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 636 +))) 593 593 594 594 595 595 ... ... @@ -622,6 +622,7 @@ 622 622 623 623 === 2.8.2 Power consumption Analyze === 624 624 669 + 625 625 ((( 626 626 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. 627 627 ))) ... ... @@ -660,6 +660,7 @@ 660 660 661 661 === 2.8.3 Battery Note === 662 662 708 + 663 663 ((( 664 664 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. 665 665 ))) ... ... @@ -668,6 +668,7 @@ 668 668 669 669 === 2.8.4 Replace the battery === 670 670 717 + 671 671 ((( 672 672 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). 673 673 ))) ... ... @@ -676,6 +676,7 @@ 676 676 677 677 = 3. Access NB-IoT Module = 678 678 726 + 679 679 ((( 680 680 Users can directly access the AT command set of the NB-IoT module. 681 681 ))) ... ... @@ -692,6 +692,7 @@ 692 692 693 693 == 4.1 Access AT Commands == 694 694 743 + 695 695 See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 696 696 697 697 ... ... @@ -780,7 +780,7 @@ 780 780 ))) 781 781 782 782 ((( 783 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 832 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.** 784 784 ))) 785 785 786 786 ... ... @@ -802,6 +802,7 @@ 802 802 803 803 == 6.2 AT Command input doesn't work == 804 804 854 + 805 805 ((( 806 806 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. 807 807 ... ... @@ -827,7 +827,7 @@ 827 827 828 828 (% style="color:#037691" %)**Package Includes**: 829 829 830 -* NS E01NB-IoT Distance Detect Sensor Node x 1880 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1 831 831 * External antenna x 1 832 832 ))) 833 833 ... ... @@ -836,7 +836,6 @@ 836 836 837 837 (% style="color:#037691" %)**Dimension and weight**: 838 838 839 - 840 840 * Device Size: 13.0 x 5 x 4.5 cm 841 841 * Device Weight: 150g 842 842 * Package Size / pcs : 15 x 12x 5.5 cm ... ... @@ -852,5 +852,6 @@ 852 852 853 853 = 9. Support = 854 854 904 + 855 855 * 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. 856 856 * 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]]