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)
-
Attachments (0 modified, 19 added, 0 removed)
- 1657327959271-447.png
- 1657328609906-564.png
- 1657328659945-416.png
- 1657328756309-230.png
- 1657328884227-504.png
- 1657329814315-101.png
- 1657330452568-615.png
- 1657330472797-498.png
- 1657330501006-241.png
- 1657330533775-472.png
- 1657330723006-866.png
- 1657331036973-987.png
- image-20220709084137-2.jpeg
- image-20220709084207-3.jpeg
- image-20220709084458-4.png
- image-20220709085040-1.png
- image-20220709092052-2.png
- image-20220709093918-1.png
- image-20220709093918-2.png
Details
- Page properties
-
- Content
-
... ... @@ -1,15 +1,10 @@ 1 1 (% style="text-align:center" %) 2 -[[image: 1657271519014-786.png]]2 +[[image:image-20220709085040-1.png||height="542" width="524"]] 3 3 4 4 5 5 6 6 7 7 8 - 9 - 10 - 11 - 12 - 13 13 **Table of Contents:** 14 14 15 15 ... ... @@ -25,18 +25,13 @@ 25 25 ((( 26 26 27 27 28 -The Dragino NDDS75 is a **NB-IOT Distance Detection Sensor** for Internet of Things solution. It is used 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. 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. 29 - 30 -It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server. 31 - 32 -**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. 33 - 34 -NDDS75 is powered by 8**500mA Li-SOCI2 battery**; It is designed for long term use up to 5 years*. 35 - 36 -~* Actually lifetime depends on network coverage and uplink interval and other factors 37 - 38 38 ((( 39 - 24 +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. 25 +\\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. 26 +\\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. 27 +\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 28 +\\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) 29 +\\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. 40 40 ))) 41 41 42 42 ... ... @@ -45,27 +45,26 @@ 45 45 [[image:1654503236291-817.png]] 46 46 47 47 48 -[[image:16572 45163077-232.png]]38 +[[image:1657327959271-447.png]] 49 49 50 50 51 51 52 52 == 1.2 Features == 53 53 44 + 54 54 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 55 -* Monitor Soil Moisture 56 -* Monitor Soil Temperature 57 -* Monitor Soil Conductivity 46 +* Ultra low power consumption 47 +* Distance Detection by Ultrasonic technology 48 +* Flat object range 280mm - 7500mm 49 +* Accuracy: ±(1cm+S*0.3%) (S: Distance) 50 +* Cable Length: 25cm 58 58 * AT Commands to change parameters 59 59 * Uplink on periodically 60 60 * Downlink to change configure 61 61 * IP66 Waterproof Enclosure 62 -* Ultra-Low Power consumption 63 -* AT Commands to change parameters 64 64 * Micro SIM card slot for NB-IoT SIM 65 65 * 8500mAh Battery for long term use 66 66 67 - 68 - 69 69 == 1.3 Specification == 70 70 71 71 ... ... @@ -83,58 +83,72 @@ 83 83 * - B20 @H-FDD: 800MHz 84 84 * - B28 @H-FDD: 700MHz 85 85 86 - Probe(% style="color:#037691" %)**Specification:**75 +(% style="color:#037691" %)**Battery:** 87 87 88 -Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height. 77 +* Li/SOCI2 un-chargeable battery 78 +* Capacity: 8500mAh 79 +* Self Discharge: <1% / Year @ 25°C 80 +* Max continuously current: 130mA 81 +* Max boost current: 2A, 1 second 89 89 90 - [[image:image-20220708101224-1.png]]83 +(% style="color:#037691" %)**Power Consumption** 91 91 85 +* STOP Mode: 10uA @ 3.3v 86 +* Max transmit power: 350mA@3.3v 92 92 93 93 94 94 == 1.4 Applications == 95 95 91 +* Smart Buildings & Home Automation 92 +* Logistics and Supply Chain Management 93 +* Smart Metering 96 96 * Smart Agriculture 95 +* Smart Cities 96 +* Smart Factory 97 97 98 98 (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %) 99 99 100 100 101 + 102 + 101 101 == 1.5 Pin Definitions == 102 102 103 103 104 -[[image:16572 46476176-652.png]]106 +[[image:1657328609906-564.png]] 105 105 106 106 107 107 108 -= 2. Use NS E01to communicate with IoT Server =110 += 2. Use NDDS75 to communicate with IoT Server = 109 109 110 110 == 2.1 How it works == 111 111 112 - 113 113 ((( 114 -The NS E01is equipped with a NB-IoT module, the pre-loaded firmware in NSE01will 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 NSE01.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. 115 115 ))) 116 116 117 117 118 118 ((( 119 -The diagram below shows the working flow in default firmware of NS E01:120 +The diagram below shows the working flow in default firmware of NDDS75: 120 120 ))) 121 121 122 -[[image:image-20220708101605-2.png]] 123 - 124 124 ((( 125 125 126 126 ))) 127 127 127 +[[image:1657328659945-416.png]] 128 128 129 +((( 130 + 131 +))) 129 129 130 -== 2.2 Configure the NSE01 == 131 131 134 +== 2.2 Configure the NDDS75 == 132 132 136 + 133 133 === 2.2.1 Test Requirement === 134 134 135 - 136 136 ((( 137 -To use NS E01in your city, make sure meet below requirements:140 +To use NDDS75 in your city, make sure meet below requirements: 138 138 ))) 139 139 140 140 * Your local operator has already distributed a NB-IoT Network there. ... ... @@ -142,11 +142,11 @@ 142 142 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 143 143 144 144 ((( 145 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The E01will 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 server148 +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 146 146 ))) 147 147 148 148 149 -[[image:16572 49419225-449.png]]152 +[[image:1657328756309-230.png]] 150 150 151 151 152 152 ... ... @@ -161,18 +161,19 @@ 161 161 ))) 162 162 163 163 164 -[[image:16572 49468462-536.png]]167 +[[image:1657328884227-504.png]] 165 165 166 166 167 167 168 -=== 2.2.3 Connect USB – TTL to NS E01to configure it ===171 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 169 169 170 170 ((( 171 171 ((( 172 -User need to configure NS E01via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01support AT Commands, user can use a USB to TTL adapter to connect to NSE01and use AT Commands to configure it, as below.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. 173 173 ))) 174 174 ))) 175 175 179 +[[image:image-20220709092052-2.png]] 176 176 177 177 **Connection:** 178 178 ... ... @@ -192,13 +192,13 @@ 192 192 * Flow Control: (% style="color:green" %)**None** 193 193 194 194 ((( 195 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NS E01. NSE01will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.199 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input. 196 196 ))) 197 197 198 -[[image: image-20220708110657-3.png]]202 +[[image:1657329814315-101.png]] 199 199 200 200 ((( 201 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NS E01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]205 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]] 202 202 ))) 203 203 204 204 ... ... @@ -216,48 +216,44 @@ 216 216 217 217 For parameter description, please refer to AT command set 218 218 219 -[[image:1657 249793983-486.png]]223 +[[image:1657330452568-615.png]] 220 220 221 221 222 -After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NS E01will start to uplink sensor values to CoAP server.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. 223 223 224 -[[image:1657 249831934-534.png]]228 +[[image:1657330472797-498.png]] 225 225 226 226 227 227 228 228 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 229 229 230 -This feature is supported since firmware version v1.0.1 231 231 232 - 233 233 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 234 234 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 235 235 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 236 236 237 -[[image:1657 249864775-321.png]]239 +[[image:1657330501006-241.png]] 238 238 239 239 240 -[[image:1657 249930215-289.png]]242 +[[image:1657330533775-472.png]] 241 241 242 242 243 243 244 244 === 2.2.6 Use MQTT protocol to uplink data === 245 245 246 -This feature is supported since firmware version v110 247 247 248 - 249 249 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 250 250 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 251 251 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 252 252 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 253 253 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 254 -* (% style="color:blue" %)**AT+PUBTOPIC=NS E01_PUB255 -* (% style="color:blue" %)**AT+SUBTOPIC=NS E01_SUB **(%%)254 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 255 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 256 256 257 257 [[image:1657249978444-674.png]] 258 258 259 259 260 -[[image:16572 49990869-686.png]]260 +[[image:1657330723006-866.png]] 261 261 262 262 263 263 ((( ... ... @@ -268,16 +268,14 @@ 268 268 269 269 === 2.2.7 Use TCP protocol to uplink data === 270 270 271 -This feature is supported since firmware version v110 272 272 273 - 274 274 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 275 275 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 276 276 277 -[[image: 1657250217799-140.png]]275 +[[image:image-20220709093918-1.png]] 278 278 279 279 280 -[[image: 1657250255956-604.png]]278 +[[image:image-20220709093918-2.png]] 281 281 282 282 283 283 ... ... @@ -299,38 +299,53 @@ 299 299 300 300 == 2.3 Uplink Payload == 301 301 302 -In this mode, uplink payload includes in total 1 8bytes300 +In this mode, uplink payload includes in total 14 bytes 303 303 302 + 304 304 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 305 305 |=(% style="width: 60px;" %)((( 306 306 **Size(bytes)** 307 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 90px;" %)**2**|=(% style="width:50px;" %)**1**308 -|(% 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:108px" %)[[ Soil Moisture>>||anchor="H2.4.5A0SoilMoisture"]]|(%style="width:133px" %)[[Soil Temperature>>||anchor="H2.4.6A0SoilTemperature"]]|(% style="width:159px"%)[[Soil Conductivity(EC)>>||anchor="H2.4.7A0SoilConductivity28EC29"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]]306 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 50px;" %)**1** 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:108px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]] 309 309 310 310 ((( 311 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NS E01 uplink data.310 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 312 312 ))) 313 313 314 314 315 -[[image: image-20220708111918-4.png]]314 +[[image:1657331036973-987.png]] 316 316 317 - 316 +((( 318 318 The payload is ASCII string, representative same HEX: 318 +))) 319 319 320 -0x72403155615900640c7817075e0a8c02f900 where: 320 +((( 321 +0x72403155615900640c6c19029200 where: 322 +))) 321 321 322 -* Device ID: 0x 724031556159 = 724031556159 323 -* Version: 0x0064=100=1.0.0 324 +* ((( 325 +Device ID: 0x724031556159 = 724031556159 326 +))) 327 +* ((( 328 +Version: 0x0064=100=1.0.0 329 +))) 324 324 325 -* BAT: 0x0c78 = 3192 mV = 3.192V 326 -* Singal: 0x17 = 23 327 -* Soil Moisture: 0x075e= 1886 = 18.86 % 328 -* Soil Temperature:0x0a8c =2700=27 °C 329 -* Soil Conductivity(EC) = 0x02f9 =761 uS /cm 330 -* Interrupt: 0x00 = 0 331 +* ((( 332 +BAT: 0x0c6c = 3180 mV = 3.180V 333 +))) 334 +* ((( 335 +Signal: 0x19 = 25 336 +))) 337 +* ((( 338 +Distance: 0x0292= 658 mm 339 +))) 340 +* ((( 341 +Interrupt: 0x00 = 0 342 +))) 331 331 332 332 333 333 346 + 334 334 == 2.4 Payload Explanation and Sensor Interface == 335 335 336 336
- 1657327959271-447.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +78.3 KB - Content
- 1657328609906-564.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +492.6 KB - Content
- 1657328659945-416.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +78.8 KB - Content
- 1657328756309-230.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +78.5 KB - Content
- 1657328884227-504.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +483.6 KB - Content
- 1657329814315-101.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +85.3 KB - Content
- 1657330452568-615.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +71.3 KB - Content
- 1657330472797-498.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +68.9 KB - Content
- 1657330501006-241.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +119.2 KB - Content
- 1657330533775-472.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +74.9 KB - Content
- 1657330723006-866.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +74.1 KB - Content
- 1657331036973-987.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +83.8 KB - Content
- image-20220709084137-2.jpeg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +72.0 KB - Content
- image-20220709084207-3.jpeg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +72.0 KB - Content
- image-20220709084458-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +199.5 KB - Content
- image-20220709085040-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +200.4 KB - Content
- image-20220709092052-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +247.3 KB - Content
- image-20220709093918-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +42.2 KB - Content
- image-20220709093918-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +61.9 KB - Content