Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 23 removed)
- 1657332990863-496.png
- 1657333200519-600.png
- 1657348034241-728.png
- 1657348284168-431.png
- 1657350248151-650.png
- 1657350625843-586.png
- 1657351240556-536.png
- 1657351312545-300.png
- 1657352146020-183.png
- 1657352185396-303.png
- 1657352391268-297.png
- 1657352403317-397.png
- 1657352634421-276.png
- 1657352645687-385.png
- 1657352898400-901.png
- 1657352914475-252.png
- 1657354294009-643.png
- 1657520100595-569.png
- image-20220709101450-2.png
- image-20220709110451-3.png
- image-20220709144723-1.png
- image-20220709150546-2.png
- image-20220709161741-3.png
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -N 95S31BNB-IoTTemperature& HumiditySensor User Manual1 +NDDS75 NB-IoT Distance Detect Sensor User Manual - Content
-
... ... @@ -1,73 +1,61 @@ 1 1 (% style="text-align:center" %) 2 -[[image: 1657348034241-728.png||height="470" width="470"]]2 +[[image:image-20220709085040-1.png||height="542" width="524"]] 3 3 4 4 5 5 6 6 7 7 8 - 9 - 10 10 **Table of Contents:** 11 11 12 -{{toc/}} 13 13 14 14 15 15 16 16 17 17 15 + 18 18 = 1. Introduction = 19 19 20 -== 1.1 What is N 95S31BNB-IoTSensorNode==18 +== 1.1 What is NDDS75 Distance Detection Sensor == 21 21 22 22 ((( 23 23 24 24 25 25 ((( 26 -The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*. 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. 27 27 ))) 28 28 29 -((( 30 -The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use. 31 -))) 32 - 33 -((( 34 -N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 35 -))) 36 - 37 -((( 38 -N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report). 39 -))) 40 - 41 -((( 42 42 43 43 ))) 44 44 45 -((( 46 -~* make sure you have NB-IoT coverage locally. 47 -))) 35 +[[image:1654503236291-817.png]] 48 48 49 - 50 -))) 51 51 52 -[[image:16573 48284168-431.png]]38 +[[image:1657327959271-447.png]] 53 53 54 54 55 55 56 56 == 1.2 Features == 57 57 44 + 58 58 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 59 -* Monitor Temperature & Humidity via SHT31 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 60 60 * AT Commands to change parameters 61 61 * Uplink on periodically 62 62 * Downlink to change configure 63 63 * IP66 Waterproof Enclosure 64 -* Ultra-Low Power consumption 65 -* AT Commands to change parameters 66 66 * Micro SIM card slot for NB-IoT SIM 67 67 * 8500mAh Battery for long term use 68 68 69 69 70 - 71 71 == 1.3 Specification == 72 72 73 73 ... ... @@ -93,8 +93,13 @@ 93 93 * Max continuously current: 130mA 94 94 * Max boost current: 2A, 1 second 95 95 84 +(% style="color:#037691" %)**Power Consumption** 96 96 86 +* STOP Mode: 10uA @ 3.3v 87 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 97 97 89 + 90 + 98 98 == 1.4 Applications == 99 99 100 100 * Smart Buildings & Home Automation ... ... @@ -108,58 +108,25 @@ 108 108 109 109 110 110 111 -== 1.5 Pin Definitions & Switch == 112 112 113 - N95S31Busethemother boardfrom NBSN95 which asbelow.105 +== 1.5 Pin Definitions == 114 114 115 -[[image:image-20220709144723-1.png]] 116 116 108 +[[image:1657328609906-564.png]] 117 117 118 -=== 1.5.1 Jumper JP2 === 119 119 120 -Power on Device when put this jumper. 121 121 112 += 2. Use NDDS75 to communicate with IoT Server = 122 122 123 - 124 -=== 1.5.2 BOOT MODE / SW1 === 125 - 126 -((( 127 -1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. 128 -))) 129 - 130 -((( 131 -2) Flash: work mode, device starts to work and send out console output for further debug 132 -))) 133 - 134 - 135 - 136 -=== 1.5.3 Reset Button === 137 - 138 -Press to reboot the device. 139 - 140 - 141 - 142 -=== 1.5.4 LED === 143 - 144 -It will flash: 145 - 146 -1. When boot the device in flash mode 147 -1. Send an uplink packet 148 - 149 - 150 - 151 -= 2. Use N95S31B to communicate with IoT Server = 152 - 153 153 == 2.1 How it works == 154 154 155 - 156 156 ((( 157 -The N 95S31Bis equipped with a NB-IoT module, the pre-loaded firmware in N95S31Bwill 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 N95S31B.117 +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. 158 158 ))) 159 159 160 160 161 161 ((( 162 -The diagram below shows the working flow in default firmware of N 95S31B:122 +The diagram below shows the working flow in default firmware of NDDS75: 163 163 ))) 164 164 165 165 ((( ... ... @@ -166,7 +166,7 @@ 166 166 167 167 ))) 168 168 169 -[[image:1657 520100595-569.png]]129 +[[image:1657328659945-416.png]] 170 170 171 171 ((( 172 172 ... ... @@ -173,67 +173,30 @@ 173 173 ))) 174 174 175 175 176 -== 2.2 Configure the N 95S31B==136 +== 2.2 Configure the NDDS75 == 177 177 178 178 179 -=== 2.2.1 Power On N95S31B === 180 - 181 - 182 -[[image:image-20220709150546-2.png]] 183 - 184 - 185 185 === 2.2.1 Test Requirement === 186 186 187 - 188 188 ((( 189 -To use N 95S31Bin your city, make sure meet below requirements:142 +To use NDDS75 in your city, make sure meet below requirements: 190 190 ))) 191 191 192 -* ((( 193 -Your local operator has already distributed a NB-IoT Network there. 194 -))) 195 -* ((( 196 -The local NB-IoT network used the band that N95S31B supports. 197 -))) 198 -* ((( 199 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 200 -))) 145 +* Your local operator has already distributed a NB-IoT Network there. 146 +* The local NB-IoT network used the band that NSE01 supports. 147 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 201 201 202 202 ((( 203 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 150 +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 204 204 ))) 205 205 206 -((( 207 -N95S31B supports different communication protocol such as : 208 -))) 209 209 210 -((( 211 -* ((( 212 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 213 -))) 214 -* ((( 215 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 216 -))) 217 -* ((( 218 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 219 -))) 220 -* ((( 221 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 222 -))) 154 +[[image:1657328756309-230.png]] 223 223 224 -((( 225 -We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server. 226 -))) 227 227 228 - 229 -))) 230 230 231 - [[image:1657350625843-586.png]]158 +=== 2.2.2 Insert SIM card === 232 232 233 - 234 - 235 -=== 2.2.3 Insert SIM card === 236 - 237 237 ((( 238 238 Insert the NB-IoT Card get from your provider. 239 239 ))) ... ... @@ -243,19 +243,19 @@ 243 243 ))) 244 244 245 245 246 -[[image:16573 51240556-536.png]]169 +[[image:1657328884227-504.png]] 247 247 248 248 249 249 250 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===173 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 251 251 252 252 ((( 253 253 ((( 254 -User need to configure 95S31Bvia serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31Bsupport AT Commands, user can use a USB to TTL adapter to connect to95S31Band use AT Commands to configure it, as below.177 +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. 255 255 ))) 256 256 ))) 257 257 258 -[[image: 1657351312545-300.png]]181 +[[image:image-20220709092052-2.png]] 259 259 260 260 **Connection:** 261 261 ... ... @@ -275,110 +275,90 @@ 275 275 * Flow Control: (% style="color:green" %)**None** 276 276 277 277 ((( 278 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N 95S31B.95S31Bwill output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.201 +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. 279 279 ))) 280 280 281 281 [[image:1657329814315-101.png]] 282 282 283 283 ((( 284 -(% style="color:red" %)Note: the valid AT Commands can be found at: 95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]207 +(% 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/]] 285 285 ))) 286 286 287 287 288 288 289 -=== 2.2. 5Use CoAP protocol to uplink data ===212 +=== 2.2.4 Use CoAP protocol to uplink data === 290 290 291 291 (% 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/]] 292 292 293 293 294 -((( 295 295 **Use below commands:** 296 -))) 297 297 298 -* ((( 299 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 300 -))) 301 -* ((( 302 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 303 -))) 304 -* ((( 305 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 306 -))) 219 +* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 220 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 221 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 307 307 308 -((( 309 - 310 - 311 311 For parameter description, please refer to AT command set 312 -))) 313 313 314 -[[image:1657352 146020-183.png]]225 +[[image:1657330452568-615.png]] 315 315 316 316 317 -((( 318 318 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. 319 -))) 320 320 321 -[[image:16573 52185396-303.png]]230 +[[image:1657330472797-498.png]] 322 322 323 323 324 324 325 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===234 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 326 326 327 327 328 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) 237 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 329 329 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 330 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 239 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 331 331 332 -[[image:16573 52391268-297.png]]241 +[[image:1657330501006-241.png]] 333 333 334 334 335 -[[image:16573 52403317-397.png]]244 +[[image:1657330533775-472.png]] 336 336 337 337 338 338 339 -=== 2.2. 7Use MQTT protocol to uplink data ===248 +=== 2.2.6 Use MQTT protocol to uplink data === 340 340 341 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 342 342 343 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) 344 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) 345 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** 346 -* (% style="color:blue" %)**AT+UNAME=UNAME 347 -* (% style="color:blue" %)**AT+PWD=PWD 348 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527349 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)251 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 252 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 253 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 254 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 255 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 256 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 257 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 350 350 351 -[[image:1657 352634421-276.png]]259 +[[image:1657249978444-674.png]] 352 352 353 353 354 -[[image:16573 52645687-385.png]]262 +[[image:1657330723006-866.png]] 355 355 356 -((( 357 -To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period. 358 -))) 359 359 360 - 361 361 ((( 362 -MQTT protocol has a much high -power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.266 +MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 363 363 ))) 364 364 365 365 366 366 367 -=== 2.2. 8Use TCP protocol to uplink data ===271 +=== 2.2.7 Use TCP protocol to uplink data === 368 368 369 -This feature is supported since firmware version v110 370 370 371 371 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 372 372 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 373 373 374 -[[image: 1657352898400-901.png]]277 +[[image:image-20220709093918-1.png]] 375 375 376 376 377 -[[image: 1657352914475-252.png]]280 +[[image:image-20220709093918-2.png]] 378 378 379 379 380 380 381 -=== 2.2. 9Change Update Interval ===284 +=== 2.2.8 Change Update Interval === 382 382 383 383 User can use below command to change the (% style="color:green" %)**uplink interval**. 384 384 ... ... @@ -385,240 +385,228 @@ 385 385 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 386 386 387 387 ((( 388 - 291 +(% style="color:red" %)**NOTE:** 389 389 ))) 390 390 294 +((( 295 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 296 +))) 391 391 392 392 299 + 393 393 == 2.3 Uplink Payload == 394 394 302 +In this mode, uplink payload includes in total 14 bytes 395 395 396 -((( 397 -N95S31B has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes. 398 -))) 399 399 305 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 306 +|=(% style="width: 60px;" %)((( 307 +**Size(bytes)** 308 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 50px;" %)**1** 309 +|(% 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"]] 400 400 401 401 ((( 402 - For example:312 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 403 403 ))) 404 404 405 -((( 406 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 407 -))) 408 408 316 +[[image:1657331036973-987.png]] 409 409 410 410 ((( 411 -The uplink payloadsare composedinASCIIString.Forxample:319 +The payload is ASCII string, representative same HEX: 412 412 ))) 413 413 414 414 ((( 415 -0 a cd00ed0acc0ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:323 +0x72403155615900640c6c19029200 where: 416 416 ))) 417 417 418 -((( 419 - 0x 0acd 00ed0acc0000ef 02d21d Total12 bytes326 +* ((( 327 +Device ID: 0x724031556159 = 724031556159 420 420 ))) 421 - 422 - 423 -((( 424 -(% style="color:red" %)**NOTE:** 329 +* ((( 330 +Version: 0x0064=100=1.0.0 425 425 ))) 426 426 427 -(% style="color:red" %) 428 -1. ((( 429 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 333 +* ((( 334 +BAT: 0x0c6c = 3180 mV = 3.180V 430 430 ))) 431 -1. ((( 432 -By default, the device will send an uplink message every 1 hour. 433 - 434 - 435 - 436 - 336 +* ((( 337 +Signal: 0x19 = 25 437 437 ))) 339 +* ((( 340 +Distance: 0x0292= 658 mm 341 +))) 342 +* ((( 343 +Interrupt: 0x00 = 0 344 +))) 438 438 439 -=== 2.3.1 Payload Analyze === 440 440 441 - N95S31Buplinkpayload includesinotal 21 bytes347 +== 2.4 Payload Explanation and Sensor Interface == 442 442 443 443 444 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 445 -|=(% style="width: 60px;" %)((( 446 -**Size(bytes)** 447 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2** 448 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)((( 350 +=== 2.4.1 Device ID === 351 + 449 449 ((( 450 - Reserve/Same asNBSN95CFGMOD=1353 +By default, the Device ID equal to the last 6 bytes of IMEI. 451 451 ))) 452 452 453 453 ((( 454 - Nofunctionhere.357 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 455 455 ))) 456 -)))|(% style="width:77px" %)((( 457 -((( 458 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 459 -))) 460 460 461 461 ((( 462 - By SHT31361 +**Example:** 463 463 ))) 464 -)))|(% style="width:80px" %)((( 465 -((( 466 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 467 -))) 468 468 469 469 ((( 470 - By SHT31365 +AT+DEUI=A84041F15612 471 471 ))) 472 -))) 473 473 474 474 ((( 475 -((( 476 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 369 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 477 477 ))) 478 -))) 479 479 480 480 481 -[[image:1657354294009-643.png]] 482 482 374 +=== 2.4.2 Version Info === 483 483 484 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 485 - 486 -* Device ID: 0x724031607457 = 724031607457 487 -* Version: 0x006e=110=1.1.0 488 - 489 -* BAT: 0x0ccd = 3277 mV = 3.277V 490 -* Signal: 0x1b = 27 491 -* Model: 0x01 = 1 492 -* 0x00dc000ccc= reserve, ignore in N95S31B 493 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 494 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 495 - 496 496 ((( 497 - 377 +Specify the software version: 0x64=100, means firmware version 1.00. 498 498 ))) 499 499 500 500 ((( 501 - 381 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 502 502 ))) 503 503 504 504 505 -=== 2.3.2 Device ID === 506 506 507 -((( 508 -By default, the Device ID equal to the last 6 bytes of IMEI. 509 -))) 386 +=== 2.4.3 Battery Info === 510 510 511 511 ((( 512 - Usercanuse(% style="color:blue"%)**AT+DEUI**(%%) tosetDeviceID389 +Check the battery voltage for LSE01. 513 513 ))) 514 514 515 515 ((( 516 - **Example:**393 +Ex1: 0x0B45 = 2885mV 517 517 ))) 518 518 519 519 ((( 520 - AT+DEUI=A84041F15612397 +Ex2: 0x0B49 = 2889mV 521 521 ))) 522 522 523 -((( 524 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 525 -))) 526 526 527 527 402 +=== 2.4.4 Signal Strength === 528 528 529 -=== 2.3.3 Version Info === 404 +((( 405 +NB-IoT Network signal Strength. 406 +))) 530 530 531 531 ((( 532 - Thesebytes includethehardware and software version.409 +**Ex1: 0x1d = 29** 533 533 ))) 534 534 535 535 ((( 536 - Higherbyte: Specifyhardwareversion:always0x00forN95S31B413 +(% style="color:blue" %)**0**(%%) -113dBm or less 537 537 ))) 538 538 539 539 ((( 540 - Lowerbyte: Specifythesoftwareversion: 0x6E=110,meansfirmwareversion110417 +(% style="color:blue" %)**1**(%%) -111dBm 541 541 ))) 542 542 543 543 ((( 544 - 421 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 545 545 ))) 546 546 547 547 ((( 548 - Forexample:0x006E:thisdeviceisN95S31Bwithfirmwareversion 110.425 +(% style="color:blue" %)**31** (%%) -51dBm or greater 549 549 ))) 550 550 551 551 ((( 552 - 429 +(% style="color:blue" %)**99** (%%) Not known or not detectable 553 553 ))) 554 554 555 555 556 -=== 2.3.4 Battery Info === 557 557 434 +=== 2.4.5 Soil Moisture === 435 + 436 +Get the distance. Flat object range 280mm - 7500mm. 437 + 438 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 439 + 558 558 ((( 559 -Ex1: 0x0B45 = 2885mV 441 +((( 442 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 560 560 ))) 444 +))) 561 561 562 562 ((( 563 - Ex2:0x0B49 = 2889mV447 + 564 564 ))) 565 565 450 +((( 451 + 452 +))) 566 566 454 +=== 2.4.6 Digital Interrupt === 567 567 568 -=== 2.3.5 Signal Strength === 569 - 570 570 ((( 571 - NB-IoTNetworksignalStrength.457 +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. 572 572 ))) 573 573 574 574 ((( 575 - **Ex1:0x1d= 29**461 +The command is: 576 576 ))) 577 577 578 578 ((( 579 -(% style="color:blue" %)** 0**(%%)-113dBmor less465 +(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.** 580 580 ))) 581 581 468 + 582 582 ((( 583 - (%style="color:blue"%)**1**(%%)-111dBm470 +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. 584 584 ))) 585 585 473 + 586 586 ((( 587 - (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm475 +Example: 588 588 ))) 589 589 590 590 ((( 591 -( %style="color:blue"%)**31** (%%) -51dBm or greater479 +0x(00): Normal uplink packet. 592 592 ))) 593 593 594 594 ((( 595 -( %style="color:blue" %)**99** (%%) Notknownor not detectable483 +0x(01): Interrupt Uplink Packet. 596 596 ))) 597 597 598 598 599 599 600 -=== 2. 3.6Temperature& Humidity===488 +=== 2.4.7 +5V Output === 601 601 602 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 490 +((( 491 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 492 +))) 603 603 604 -[[image:image-20220709161741-3.png]] 605 605 495 +((( 496 +The 5V output time can be controlled by AT Command. 497 +))) 606 606 607 -Convert the read byte to decimal and divide it by ten. 499 +((( 500 +(% style="color:blue" %)**AT+5VT=1000** 501 +))) 608 608 503 +((( 504 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 505 +))) 609 609 610 -**Example:** 611 611 612 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 613 613 614 - Humidity:Read:0295(H)=661(D)Value:661 / 10=66.1, So66.1%509 +== 2.5 Downlink Payload == 615 615 511 +By default, NDDS75 prints the downlink payload to console port. 616 616 617 - 618 -== 2.4 Downlink Payload == 619 - 620 -By default, N95S31B prints the downlink payload to console port. 621 - 622 622 [[image:image-20220709100028-1.png]] 623 623 624 624 ... ... @@ -655,7 +655,7 @@ 655 655 ))) 656 656 657 657 ((( 658 -If payload = 0x04FF, it will reset the 95S31B549 +If payload = 0x04FF, it will reset the NDDS75 659 659 ))) 660 660 661 661 ... ... @@ -667,19 +667,80 @@ 667 667 668 668 669 669 670 -== 2. 5BatteryAnalysis==561 +== 2.6 LED Indicator == 671 671 672 -=== 2.5.1 Battery Type === 673 673 564 +The NDDS75 has an internal LED which is to show the status of different state. 674 674 566 + 567 +* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 568 +* Then the LED will be on for 1 second means device is boot normally. 569 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 570 +* For each uplink probe, LED will be on for 500ms. 571 + 675 675 ((( 676 - TheN95S31B 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.573 + 677 677 ))) 678 678 576 + 577 + 578 +== 2.7 Installation in Soil == 579 + 580 +__**Measurement the soil surface**__ 581 + 679 679 ((( 583 +Choose the proper measuring position. Avoid the probe to touch rocks or hard things. Split the surface soil according to the measured deep. Keep the measured as original density. Vertical insert the probe into the soil to be measured. Make sure not shake when inserting. [[https:~~/~~/img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg>>url:https://img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg]] 584 +))) 585 + 586 +[[image:1657259653666-883.png]] 587 + 588 + 589 +((( 590 + 591 + 592 +((( 593 +Dig a hole with diameter > 20CM. 594 +))) 595 + 596 +((( 597 +Horizontal insert the probe to the soil and fill the hole for long term measurement. 598 +))) 599 +))) 600 + 601 +[[image:1654506665940-119.png]] 602 + 603 +((( 604 + 605 +))) 606 + 607 + 608 +== 2.8 Firmware Change Log == 609 + 610 + 611 +Download URL & Firmware Change log 612 + 613 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]] 614 + 615 + 616 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 617 + 618 + 619 + 620 +== 2.9 Battery Analysis == 621 + 622 +=== 2.9.1 Battery Type === 623 + 624 + 625 +((( 626 +The NSE01 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. 627 +))) 628 + 629 + 630 +((( 680 680 The battery is designed to last for several years depends on the actually use environment and update interval. 681 681 ))) 682 682 634 + 683 683 ((( 684 684 The battery related documents as below: 685 685 ))) ... ... @@ -689,40 +689,61 @@ 689 689 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 690 690 691 691 ((( 692 -[[image:image-2022070 9101450-2.png]]644 +[[image:image-20220708140453-6.png]] 693 693 ))) 694 694 695 695 696 696 697 -=== 2. 5.2 Power consumption Analyze ===649 +=== 2.9.2 Power consumption Analyze === 698 698 699 699 ((( 700 - The file**DRAGINO_N95S31B-Power-Analyzer.pdf**from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describesadetailmeasurementtoanalyzethepowerconsumption indifferentcase. User can useitfordesignguideline fortheirproject.652 +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. 701 701 ))) 702 702 655 + 703 703 ((( 704 - 657 +Instruction to use as below: 705 705 ))) 706 706 660 +((( 661 +(% 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/]] 662 +))) 707 707 708 -=== 2.5.3 Battery Note === 709 709 710 710 ((( 711 - TheLi-SICO batteryis designed for small current / long period application. It is not good tousea high current, short periodtransmitmethod.Therecommendedminimum period for use ofthisbattery is 5 minutes.If you use a shorter period time to uplink data, then the battery life may be decreased.666 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 712 712 ))) 713 713 669 +* ((( 670 +Product Model 671 +))) 672 +* ((( 673 +Uplink Interval 674 +))) 675 +* ((( 676 +Working Mode 677 +))) 714 714 679 +((( 680 +And the Life expectation in difference case will be shown on the right. 681 +))) 715 715 716 - ===2.5.4 Replacethe battery ===683 +[[image:image-20220708141352-7.jpeg]] 717 717 718 718 686 + 687 +=== 2.9.3 Battery Note === 688 + 719 719 ((( 720 - You can changethebattery intheN95S31B.Thetype ofbatteryis notlimitedaslongas theutput isbetween3vto3.6v.Onthemainboard,there isa diode(D1)betweenthebatteryandthemaincircuit. If youneed touse abatterywith less than 3.3v,pleaseremove the D1 andshortcut the twopadsofitso there won'tbe voltagedropbetween batteryandmainboard.690 +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. 721 721 ))) 722 722 723 723 694 + 695 +=== 2.9.4 Replace the battery === 696 + 724 724 ((( 725 -The default battery pack of N 95S31Bincludes 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).698 +The default battery pack of NSE01 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). 726 726 ))) 727 727 728 728 ... ... @@ -737,7 +737,7 @@ 737 737 The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 738 738 ))) 739 739 740 -[[image:1657 333200519-600.png]]713 +[[image:1657261278785-153.png]] 741 741 742 742 743 743 ... ... @@ -745,7 +745,7 @@ 745 745 746 746 == 4.1 Access AT Commands == 747 747 748 -See NBSN95 AT Command inthis link for detail:s:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]721 +See this link for detail: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 749 749 750 750 751 751 AT+<CMD>? : Help on <CMD> ... ... @@ -833,15 +833,18 @@ 833 833 ))) 834 834 835 835 ((( 836 - 809 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update. 810 +))) 837 837 812 + 813 + 814 +== 5.2 Can I calibrate NSE01 to different soil types? == 815 + 838 838 ((( 839 - (%style="color:red"%)Notice,N95S31BandLSN50v2share thesamemotherboard.Theyuse thesameconnectionand method toupdate.817 +NSE01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]]. 840 840 ))) 841 -))) 842 842 843 843 844 - 845 845 = 6. Trouble Shooting = 846 846 847 847 == 6.1 Connection problem when uploading firmware == ... ... @@ -869,7 +869,7 @@ 869 869 = 7. Order Info = 870 870 871 871 872 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**848 +Part Number**:** (% style="color:#4f81bd" %)**NSE01** 873 873 874 874 875 875 (% class="wikigeneratedid" %) ... ... @@ -884,7 +884,7 @@ 884 884 885 885 (% style="color:#037691" %)**Package Includes**: 886 886 887 -* N 95S31BNB-IoTTemperatureandHumiditySensor863 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1 888 888 * External antenna x 1 889 889 ))) 890 890 ... ... @@ -893,10 +893,8 @@ 893 893 894 894 (% style="color:#037691" %)**Dimension and weight**: 895 895 896 -* Device Size: 13.0 x 5 x 4.5 cm 897 -* Device Weight: 150g 898 -* Package Size / pcs : 14.0 x 8x 5 cm 899 -* Weight / pcs : 180g 872 +* Size: 195 x 125 x 55 mm 873 +* Weight: 420g 900 900 ))) 901 901 902 902 (((
- 1657332990863-496.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.2 KB - Content
- 1657333200519-600.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- 1657348034241-728.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -127.8 KB - Content
- 1657348284168-431.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -93.5 KB - Content
- 1657350248151-650.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- 1657350625843-586.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -93.3 KB - Content
- 1657351240556-536.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -483.6 KB - Content
- 1657351312545-300.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -675.8 KB - Content
- 1657352146020-183.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -264.0 KB - Content
- 1657352185396-303.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -98.3 KB - Content
- 1657352391268-297.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -238.0 KB - Content
- 1657352403317-397.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -547.7 KB - Content
- 1657352634421-276.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -163.6 KB - Content
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -144.8 KB - Content
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -157.0 KB - Content
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- image-20220709101450-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.5 KB - Content
- image-20220709110451-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -611.5 KB - Content
- image-20220709144723-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -413.1 KB - Content
- image-20220709150546-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -333.5 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.2 KB - Content