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,68 +1,57 @@ 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 ... ... @@ -92,7 +92,13 @@ 92 92 * Max continuously current: 130mA 93 93 * Max boost current: 2A, 1 second 94 94 84 +(% style="color:#037691" %)**Power Consumption** 95 95 86 +* STOP Mode: 10uA @ 3.3v 87 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 88 + 89 + 90 + 96 96 == 1.4 Applications == 97 97 98 98 * Smart Buildings & Home Automation ... ... @@ -106,57 +106,25 @@ 106 106 107 107 108 108 109 -== 1.5 Pin Definitions & Switch == 110 110 111 - N95S31Busethemother boardfrom NBSN95 which asbelow.105 +== 1.5 Pin Definitions == 112 112 113 -[[image:image-20220709144723-1.png]] 114 114 108 +[[image:1657328609906-564.png]] 115 115 116 -=== 1.5.1 Jumper JP2 === 117 117 118 -Power on Device when put this jumper. 119 119 112 += 2. Use NDDS75 to communicate with IoT Server = 120 120 121 - 122 -=== 1.5.2 BOOT MODE / SW1 === 123 - 124 -((( 125 -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. 126 -))) 127 - 128 -((( 129 -2) Flash: work mode, device starts to work and send out console output for further debug 130 -))) 131 - 132 - 133 - 134 -=== 1.5.3 Reset Button === 135 - 136 -Press to reboot the device. 137 - 138 - 139 - 140 -=== 1.5.4 LED === 141 - 142 -It will flash: 143 - 144 -1. When boot the device in flash mode 145 -1. Send an uplink packet 146 - 147 - 148 -= 2. Use N95S31B to communicate with IoT Server = 149 - 150 150 == 2.1 How it works == 151 151 152 - 153 153 ((( 154 -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. 155 155 ))) 156 156 157 157 158 158 ((( 159 -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: 160 160 ))) 161 161 162 162 ((( ... ... @@ -163,7 +163,7 @@ 163 163 164 164 ))) 165 165 166 -[[image:16573 50248151-650.png]]129 +[[image:1657328659945-416.png]] 167 167 168 168 ((( 169 169 ... ... @@ -170,67 +170,30 @@ 170 170 ))) 171 171 172 172 173 -== 2.2 Configure the N 95S31B==136 +== 2.2 Configure the NDDS75 == 174 174 175 175 176 -=== 2.2.1 Power On N95S31B === 177 - 178 - 179 -[[image:image-20220709150546-2.png]] 180 - 181 - 182 182 === 2.2.1 Test Requirement === 183 183 184 - 185 185 ((( 186 -To use N 95S31Bin your city, make sure meet below requirements:142 +To use NDDS75 in your city, make sure meet below requirements: 187 187 ))) 188 188 189 -* ((( 190 -Your local operator has already distributed a NB-IoT Network there. 191 -))) 192 -* ((( 193 -The local NB-IoT network used the band that N95S31B supports. 194 -))) 195 -* ((( 196 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 197 -))) 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. 198 198 199 199 ((( 200 -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 201 201 ))) 202 202 203 -((( 204 -N95S31B supports different communication protocol such as : 205 -))) 206 206 207 -((( 208 -* ((( 209 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 210 -))) 211 -* ((( 212 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 213 -))) 214 -* ((( 215 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 216 -))) 217 -* ((( 218 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 219 -))) 154 +[[image:1657328756309-230.png]] 220 220 221 -((( 222 -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. 223 -))) 224 224 225 - 226 -))) 227 227 228 - [[image:1657350625843-586.png]]158 +=== 2.2.2 Insert SIM card === 229 229 230 - 231 - 232 -=== 2.2.3 Insert SIM card === 233 - 234 234 ((( 235 235 Insert the NB-IoT Card get from your provider. 236 236 ))) ... ... @@ -240,19 +240,19 @@ 240 240 ))) 241 241 242 242 243 -[[image:16573 51240556-536.png]]169 +[[image:1657328884227-504.png]] 244 244 245 245 246 246 247 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===173 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 248 248 249 249 ((( 250 250 ((( 251 -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. 252 252 ))) 253 253 ))) 254 254 255 -[[image: 1657351312545-300.png]]181 +[[image:image-20220709092052-2.png]] 256 256 257 257 **Connection:** 258 258 ... ... @@ -272,110 +272,90 @@ 272 272 * Flow Control: (% style="color:green" %)**None** 273 273 274 274 ((( 275 -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. 276 276 ))) 277 277 278 278 [[image:1657329814315-101.png]] 279 279 280 280 ((( 281 -(% 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/]] 282 282 ))) 283 283 284 284 285 285 286 -=== 2.2. 5Use CoAP protocol to uplink data ===212 +=== 2.2.4 Use CoAP protocol to uplink data === 287 287 288 288 (% 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/]] 289 289 290 290 291 -((( 292 292 **Use below commands:** 293 -))) 294 294 295 -* ((( 296 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 297 -))) 298 -* ((( 299 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 300 -))) 301 -* ((( 302 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 303 -))) 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 304 304 305 -((( 306 - 307 - 308 308 For parameter description, please refer to AT command set 309 -))) 310 310 311 -[[image:1657352 146020-183.png]]225 +[[image:1657330452568-615.png]] 312 312 313 313 314 -((( 315 315 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. 316 -))) 317 317 318 -[[image:16573 52185396-303.png]]230 +[[image:1657330472797-498.png]] 319 319 320 320 321 321 322 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===234 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 323 323 324 324 325 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) 237 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 326 326 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 327 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 239 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 328 328 329 -[[image:16573 52391268-297.png]]241 +[[image:1657330501006-241.png]] 330 330 331 331 332 -[[image:16573 52403317-397.png]]244 +[[image:1657330533775-472.png]] 333 333 334 334 335 335 336 -=== 2.2. 7Use MQTT protocol to uplink data ===248 +=== 2.2.6 Use MQTT protocol to uplink data === 337 337 338 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 339 339 340 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) 341 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) 342 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** 343 -* (% style="color:blue" %)**AT+UNAME=UNAME 344 -* (% style="color:blue" %)**AT+PWD=PWD 345 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527346 -* (% 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 347 347 348 -[[image:1657 352634421-276.png]]259 +[[image:1657249978444-674.png]] 349 349 350 350 351 -[[image:16573 52645687-385.png]]262 +[[image:1657330723006-866.png]] 352 352 353 -((( 354 -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. 355 -))) 356 356 357 - 358 358 ((( 359 -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. 360 360 ))) 361 361 362 362 363 363 364 -=== 2.2. 8Use TCP protocol to uplink data ===271 +=== 2.2.7 Use TCP protocol to uplink data === 365 365 366 -This feature is supported since firmware version v110 367 367 368 368 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 369 369 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 370 370 371 -[[image: 1657352898400-901.png]]277 +[[image:image-20220709093918-1.png]] 372 372 373 373 374 -[[image: 1657352914475-252.png]]280 +[[image:image-20220709093918-2.png]] 375 375 376 376 377 377 378 -=== 2.2. 9Change Update Interval ===284 +=== 2.2.8 Change Update Interval === 379 379 380 380 User can use below command to change the (% style="color:green" %)**uplink interval**. 381 381 ... ... @@ -382,235 +382,226 @@ 382 382 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 383 383 384 384 ((( 385 - 291 +(% style="color:red" %)**NOTE:** 386 386 ))) 387 387 294 +((( 295 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 296 +))) 388 388 389 389 299 + 390 390 == 2.3 Uplink Payload == 391 391 302 +In this mode, uplink payload includes in total 14 bytes 392 392 393 -((( 394 -NBSN95 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. 395 -))) 396 396 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"]] 397 397 398 398 ((( 399 - 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. 400 400 ))) 401 401 402 -((( 403 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 404 -))) 405 405 316 +[[image:1657331036973-987.png]] 406 406 407 407 ((( 408 -The uplink payloadsare composedinASCIIString.Forxample:319 +The payload is ASCII string, representative same HEX: 409 409 ))) 410 410 411 411 ((( 412 -0 a cd00ed0acc0ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:323 +0x72403155615900640c6c19029200 where: 413 413 ))) 414 414 415 -((( 416 - 0x 0acd 00ed0acc0000ef 02d21d Total12 bytes326 +* ((( 327 +Device ID: 0x724031556159 = 724031556159 417 417 ))) 418 - 419 - 420 -((( 421 -(% style="color:red" %)**NOTE:** 329 +* ((( 330 +Version: 0x0064=100=1.0.0 422 422 ))) 423 423 424 -(% style="color:red" %) 425 -1. ((( 426 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 333 +* ((( 334 +BAT: 0x0c6c = 3180 mV = 3.180V 427 427 ))) 428 - 1.(((429 - By default, the device will sendan uplinkmessage every1hour.336 +* ((( 337 +Signal: 0x19 = 25 430 430 ))) 339 +* ((( 340 +Distance: 0x0292= 658 mm 341 +))) 342 +* ((( 343 +Interrupt: 0x00 = 0 344 +))) 431 431 432 432 433 -== =2.3.1PayloadAnalyze ===347 +== 2.4 Payload Explanation and Sensor Interface == 434 434 435 -N95S31B uplink payload includes in total 21 bytes 436 436 350 +=== 2.4.1 Device ID === 437 437 438 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 439 -|=(% style="width: 60px;" %)((( 440 -**Size(bytes)** 441 -)))|=(% 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** 442 -|(% 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" %)((( 443 443 ((( 444 - Reserve/Same asNBSN95CFGMOD=1353 +By default, the Device ID equal to the last 6 bytes of IMEI. 445 445 ))) 446 446 447 447 ((( 448 - Nofunctionhere.357 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 449 449 ))) 450 -)))|(% style="width:77px" %)((( 451 -((( 452 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 453 -))) 454 454 455 455 ((( 456 - By SHT31361 +**Example:** 457 457 ))) 458 -)))|(% style="width:80px" %)((( 459 -((( 460 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 461 -))) 462 462 463 463 ((( 464 - By SHT31365 +AT+DEUI=A84041F15612 465 465 ))) 466 -))) 467 467 468 468 ((( 469 -((( 470 -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. 471 471 ))) 472 -))) 473 473 474 474 475 -[[image:1657354294009-643.png]] 476 476 374 +=== 2.4.2 Version Info === 477 477 478 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 479 - 480 -* Device ID: 0x724031607457 = 724031607457 481 -* Version: 0x006e=110=1.1.0 482 - 483 -* BAT: 0x0ccd = 3277 mV = 3.277V 484 -* Signal: 0x1b = 27 485 -* Model: 0x01 = 1 486 -* 0x00dc000ccc= reserve, ignore in N95S31B 487 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 488 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 489 - 490 490 ((( 491 - 377 +Specify the software version: 0x64=100, means firmware version 1.00. 492 492 ))) 493 493 494 494 ((( 495 - 381 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 496 496 ))) 497 497 498 498 499 -=== 2.3.2 Device ID === 500 500 501 -((( 502 -By default, the Device ID equal to the last 6 bytes of IMEI. 503 -))) 386 +=== 2.4.3 Battery Info === 504 504 505 505 ((( 506 - Usercanuse(% style="color:blue"%)**AT+DEUI**(%%) tosetDeviceID389 +Check the battery voltage for LSE01. 507 507 ))) 508 508 509 509 ((( 510 - **Example:**393 +Ex1: 0x0B45 = 2885mV 511 511 ))) 512 512 513 513 ((( 514 - AT+DEUI=A84041F15612397 +Ex2: 0x0B49 = 2889mV 515 515 ))) 516 516 517 -((( 518 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 519 -))) 520 520 521 521 402 +=== 2.4.4 Signal Strength === 522 522 523 -=== 2.3.3 Version Info === 404 +((( 405 +NB-IoT Network signal Strength. 406 +))) 524 524 525 525 ((( 526 - Thesebytes includethehardware and software version.409 +**Ex1: 0x1d = 29** 527 527 ))) 528 528 529 529 ((( 530 - Higherbyte: Specifyhardwareversion:always0x00forN95S31B413 +(% style="color:blue" %)**0**(%%) -113dBm or less 531 531 ))) 532 532 533 533 ((( 534 - Lowerbyte: Specifythesoftwareversion: 0x6E=110,meansfirmwareversion110417 +(% style="color:blue" %)**1**(%%) -111dBm 535 535 ))) 536 536 537 537 ((( 538 - 421 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 539 539 ))) 540 540 541 541 ((( 542 - Forexample:0x006E:thisdeviceisN95S31Bwithfirmwareversion 110.425 +(% style="color:blue" %)**31** (%%) -51dBm or greater 543 543 ))) 544 544 545 545 ((( 546 - 429 +(% style="color:blue" %)**99** (%%) Not known or not detectable 547 547 ))) 548 548 549 549 550 -=== 2.3.4 Battery Info === 551 551 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 + 552 552 ((( 553 -Ex1: 0x0B45 = 2885mV 441 +((( 442 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 554 554 ))) 444 +))) 555 555 556 556 ((( 557 - Ex2:0x0B49 = 2889mV447 + 558 558 ))) 559 559 450 +((( 451 + 452 +))) 560 560 454 +=== 2.4.6 Digital Interrupt === 561 561 562 -=== 2.3.5 Signal Strength === 563 - 564 564 ((( 565 - 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. 566 566 ))) 567 567 568 568 ((( 569 - **Ex1:0x1d= 29**461 +The command is: 570 570 ))) 571 571 572 572 ((( 573 -(% 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]])**.** 574 574 ))) 575 575 468 + 576 576 ((( 577 - (%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. 578 578 ))) 579 579 473 + 580 580 ((( 581 - (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm475 +Example: 582 582 ))) 583 583 584 584 ((( 585 -( %style="color:blue"%)**31** (%%) -51dBm or greater479 +0x(00): Normal uplink packet. 586 586 ))) 587 587 588 588 ((( 589 -( %style="color:blue" %)**99** (%%) Notknownor not detectable483 +0x(01): Interrupt Uplink Packet. 590 590 ))) 591 591 592 592 593 593 594 -=== 2. 3.6Temperature& Humidity===488 +=== 2.4.7 +5V Output === 595 595 596 -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 +))) 597 597 598 -[[image:image-20220709161741-3.png]] 599 599 495 +((( 496 +The 5V output time can be controlled by AT Command. 497 +))) 600 600 601 -Convert the read byte to decimal and divide it by ten. 499 +((( 500 +(% style="color:blue" %)**AT+5VT=1000** 501 +))) 602 602 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 +))) 603 603 604 -**Example:** 605 605 606 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 607 607 608 - Humidity:Read:0295(H)=661(D)Value:661 / 10=66.1, So66.1%509 +== 2.5 Downlink Payload == 609 609 610 - 611 - 612 -== 2.4 Downlink Payload == 613 - 614 614 By default, NDDS75 prints the downlink payload to console port. 615 615 616 616 [[image:image-20220709100028-1.png]] ... ... @@ -661,19 +661,80 @@ 661 661 662 662 663 663 664 -== 2. 5BatteryAnalysis==561 +== 2.6 LED Indicator == 665 665 666 -=== 2.5.1 Battery Type === 667 667 564 +The NDDS75 has an internal LED which is to show the status of different state. 668 668 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 + 669 669 ((( 670 - 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 + 671 671 ))) 672 672 576 + 577 + 578 +== 2.7 Installation in Soil == 579 + 580 +__**Measurement the soil surface**__ 581 + 673 673 ((( 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 +((( 674 674 The battery is designed to last for several years depends on the actually use environment and update interval. 675 675 ))) 676 676 634 + 677 677 ((( 678 678 The battery related documents as below: 679 679 ))) ... ... @@ -683,40 +683,61 @@ 683 683 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 684 684 685 685 ((( 686 -[[image:image-2022070 9101450-2.png]]644 +[[image:image-20220708140453-6.png]] 687 687 ))) 688 688 689 689 690 690 691 -=== 2. 5.2 Power consumption Analyze ===649 +=== 2.9.2 Power consumption Analyze === 692 692 693 693 ((( 694 - 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. 695 695 ))) 696 696 655 + 697 697 ((( 698 - 657 +Instruction to use as below: 699 699 ))) 700 700 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 +))) 701 701 702 -=== 2.5.3 Battery Note === 703 703 704 704 ((( 705 - 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 706 706 ))) 707 707 669 +* ((( 670 +Product Model 671 +))) 672 +* ((( 673 +Uplink Interval 674 +))) 675 +* ((( 676 +Working Mode 677 +))) 708 708 679 +((( 680 +And the Life expectation in difference case will be shown on the right. 681 +))) 709 709 710 - ===2.5.4 Replacethe battery ===683 +[[image:image-20220708141352-7.jpeg]] 711 711 712 712 686 + 687 +=== 2.9.3 Battery Note === 688 + 713 713 ((( 714 - 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. 715 715 ))) 716 716 717 717 694 + 695 +=== 2.9.4 Replace the battery === 696 + 718 718 ((( 719 -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). 720 720 ))) 721 721 722 722 ... ... @@ -731,7 +731,7 @@ 731 731 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/]] 732 732 ))) 733 733 734 -[[image:1657 333200519-600.png]]713 +[[image:1657261278785-153.png]] 735 735 736 736 737 737 ... ... @@ -739,7 +739,7 @@ 739 739 740 740 == 4.1 Access AT Commands == 741 741 742 -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/]] 743 743 744 744 745 745 AT+<CMD>? : Help on <CMD> ... ... @@ -827,15 +827,18 @@ 827 827 ))) 828 828 829 829 ((( 830 - 809 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update. 810 +))) 831 831 812 + 813 + 814 +== 5.2 Can I calibrate NSE01 to different soil types? == 815 + 832 832 ((( 833 - (%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]]. 834 834 ))) 835 -))) 836 836 837 837 838 - 839 839 = 6. Trouble Shooting = 840 840 841 841 == 6.1 Connection problem when uploading firmware == ... ... @@ -863,7 +863,7 @@ 863 863 = 7. Order Info = 864 864 865 865 866 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**848 +Part Number**:** (% style="color:#4f81bd" %)**NSE01** 867 867 868 868 869 869 (% class="wikigeneratedid" %) ... ... @@ -878,7 +878,7 @@ 878 878 879 879 (% style="color:#037691" %)**Package Includes**: 880 880 881 -* N 95S31BNB-IoTTemperatureandHumiditySensor863 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1 882 882 * External antenna x 1 883 883 ))) 884 884 ... ... @@ -887,10 +887,8 @@ 887 887 888 888 (% style="color:#037691" %)**Dimension and weight**: 889 889 890 -* Device Size: 13.0 x 5 x 4.5 cm 891 -* Device Weight: 150g 892 -* Package Size / pcs : 14.0 x 8x 5 cm 893 -* Weight / pcs : 180g 872 +* Size: 195 x 125 x 55 mm 873 +* Weight: 420g 894 894 ))) 895 895 896 896 (((
- 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