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,14 +22,31 @@ 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 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. 31 +))) 32 + 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 +))) 36 + 37 +((( 38 +NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 39 +))) 40 + 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 + 33 33 34 34 ))) 35 35 ... ... @@ -89,6 +89,7 @@ 89 89 90 90 == 1.4 Applications == 91 91 109 + 92 92 * Smart Buildings & Home Automation 93 93 * Logistics and Supply Chain Management 94 94 * Smart Metering ... ... @@ -111,6 +111,7 @@ 111 111 112 112 == 2.1 How it works == 113 113 132 + 114 114 ((( 115 115 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. 116 116 ))) ... ... @@ -136,16 +136,17 @@ 136 136 137 137 === 2.2.1 Test Requirement === 138 138 158 + 139 139 ((( 140 140 To use NDDS75 in your city, make sure meet below requirements: 141 141 ))) 142 142 143 143 * Your local operator has already distributed a NB-IoT Network there. 144 -* The local NB-IoT network used the band that NS E01supports.164 +* The local NB-IoT network used the band that NDDS75 supports. 145 145 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 146 146 147 147 ((( 148 -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. 149 149 ))) 150 150 151 151 ... ... @@ -155,6 +155,7 @@ 155 155 156 156 === 2.2.2 Insert SIM card === 157 157 178 + 158 158 ((( 159 159 Insert the NB-IoT Card get from your provider. 160 160 ))) ... ... @@ -170,6 +170,7 @@ 170 170 171 171 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 172 172 194 + 173 173 ((( 174 174 ((( 175 175 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. ... ... @@ -209,21 +209,34 @@ 209 209 210 210 === 2.2.4 Use CoAP protocol to uplink data === 211 211 212 -(% 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/]] 213 213 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/]]** 214 214 237 + 238 +((( 215 215 **Use below commands:** 240 +))) 216 216 217 -* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 218 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 219 -* (% 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 +))) 220 220 252 +((( 221 221 For parameter description, please refer to AT command set 254 +))) 222 222 223 223 [[image:1657330452568-615.png]] 224 224 225 225 259 +((( 226 226 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 +))) 227 227 228 228 [[image:1657330472797-498.png]] 229 229 ... ... @@ -246,11 +246,11 @@ 246 246 === 2.2.6 Use MQTT protocol to uplink data === 247 247 248 248 249 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 250 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 251 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 252 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 253 -* (% 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 254 254 * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 255 255 * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 256 256 ... ... @@ -281,6 +281,7 @@ 281 281 282 282 === 2.2.8 Change Update Interval === 283 283 319 + 284 284 User can use below command to change the (% style="color:green" %)**uplink interval**. 285 285 286 286 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -290,7 +290,7 @@ 290 290 ))) 291 291 292 292 ((( 293 -(% 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.** 294 294 ))) 295 295 296 296 ... ... @@ -297,13 +297,14 @@ 297 297 298 298 == 2.3 Uplink Payload == 299 299 336 + 300 300 In this mode, uplink payload includes in total 14 bytes 301 301 302 302 303 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width: 510px" %)304 -|=(% style="width: 80px;" %)(((340 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 341 +|=(% style="width: 60px;" %)((( 305 305 **Size(bytes)** 306 -)))|=(% 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** 307 307 |(% 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"]] 308 308 309 309 ((( ... ... @@ -350,6 +350,7 @@ 350 350 351 351 === 2.4.1 Device ID === 352 352 390 + 353 353 ((( 354 354 By default, the Device ID equal to the last 6 bytes of IMEI. 355 355 ))) ... ... @@ -374,6 +374,7 @@ 374 374 375 375 === 2.4.2 Version Info === 376 376 415 + 377 377 ((( 378 378 Specify the software version: 0x64=100, means firmware version 1.00. 379 379 ))) ... ... @@ -386,6 +386,7 @@ 386 386 387 387 === 2.4.3 Battery Info === 388 388 428 + 389 389 ((( 390 390 Ex1: 0x0B45 = 2885mV 391 391 ))) ... ... @@ -398,6 +398,7 @@ 398 398 399 399 === 2.4.4 Signal Strength === 400 400 441 + 401 401 ((( 402 402 NB-IoT Network signal Strength. 403 403 ))) ... ... @@ -430,9 +430,12 @@ 430 430 431 431 === 2.4.5 Distance === 432 432 474 + 433 433 Get the distance. Flat object range 280mm - 7500mm. 434 434 477 +((( 435 435 For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 479 +))) 436 436 437 437 ((( 438 438 ((( ... ... @@ -450,6 +450,7 @@ 450 450 451 451 === 2.4.6 Digital Interrupt === 452 452 497 + 453 453 ((( 454 454 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. 455 455 ))) ... ... @@ -484,6 +484,7 @@ 484 484 485 485 === 2.4.7 +5V Output === 486 486 532 + 487 487 ((( 488 488 NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 489 489 ))) ... ... @@ -505,6 +505,7 @@ 505 505 506 506 == 2.5 Downlink Payload == 507 507 554 + 508 508 By default, NDDS75 prints the downlink payload to console port. 509 509 510 510 [[image:image-20220709100028-1.png]] ... ... @@ -575,7 +575,9 @@ 575 575 == 2.7 Firmware Change Log == 576 576 577 577 625 +((( 578 578 Download URL & Firmware Change log 627 +))) 579 579 580 580 ((( 581 581 [[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/]] ... ... @@ -582,7 +582,9 @@ 582 582 ))) 583 583 584 584 634 +((( 585 585 Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 636 +))) 586 586 587 587 588 588 ... ... @@ -615,6 +615,7 @@ 615 615 616 616 === 2.8.2 Power consumption Analyze === 617 617 669 + 618 618 ((( 619 619 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. 620 620 ))) ... ... @@ -653,6 +653,7 @@ 653 653 654 654 === 2.8.3 Battery Note === 655 655 708 + 656 656 ((( 657 657 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. 658 658 ))) ... ... @@ -661,6 +661,7 @@ 661 661 662 662 === 2.8.4 Replace the battery === 663 663 717 + 664 664 ((( 665 665 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). 666 666 ))) ... ... @@ -669,6 +669,7 @@ 669 669 670 670 = 3. Access NB-IoT Module = 671 671 726 + 672 672 ((( 673 673 Users can directly access the AT command set of the NB-IoT module. 674 674 ))) ... ... @@ -685,6 +685,7 @@ 685 685 686 686 == 4.1 Access AT Commands == 687 687 743 + 688 688 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/]] 689 689 690 690 ... ... @@ -773,7 +773,7 @@ 773 773 ))) 774 774 775 775 ((( 776 -(% 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.** 777 777 ))) 778 778 779 779 ... ... @@ -795,6 +795,7 @@ 795 795 796 796 == 6.2 AT Command input doesn't work == 797 797 854 + 798 798 ((( 799 799 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. 800 800 ... ... @@ -820,7 +820,7 @@ 820 820 821 821 (% style="color:#037691" %)**Package Includes**: 822 822 823 -* NS E01NB-IoT Distance Detect Sensor Node x 1880 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1 824 824 * External antenna x 1 825 825 ))) 826 826 ... ... @@ -829,7 +829,6 @@ 829 829 830 830 (% style="color:#037691" %)**Dimension and weight**: 831 831 832 - 833 833 * Device Size: 13.0 x 5 x 4.5 cm 834 834 * Device Weight: 150g 835 835 * Package Size / pcs : 15 x 12x 5.5 cm ... ... @@ -845,5 +845,6 @@ 845 845 846 846 = 9. Support = 847 847 904 + 848 848 * 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. 849 849 * 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]]