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 (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -22,16 +22,29 @@ 22 22 ((( 23 23 24 24 25 +((( 25 25 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*. 27 +))) 26 26 29 +((( 27 27 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 +))) 28 28 33 +((( 29 29 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 35 +))) 30 30 37 +((( 31 31 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 +))) 32 32 41 +((( 42 + 43 +))) 33 33 45 +((( 34 34 ~* make sure you have NB-IoT coverage locally. 47 +))) 35 35 36 36 37 37 ))) ... ... @@ -74,7 +74,6 @@ 74 74 75 75 (% style="color:#037691" %)**Battery:** 76 76 77 - 78 78 * Li/SOCI2 un-chargeable battery 79 79 * Capacity: 8500mAh 80 80 * Self Discharge: <1% / Year @ 25°C ... ... @@ -111,9 +111,13 @@ 111 111 112 112 === 1.5.2 BOOT MODE / SW1 === 113 113 126 +((( 114 114 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 +))) 115 115 130 +((( 116 116 2) Flash: work mode, device starts to work and send out console output for further debug 132 +))) 117 117 118 118 119 119 ... ... @@ -130,6 +130,8 @@ 130 130 1. When boot the device in flash mode 131 131 1. Send an uplink packet 132 132 149 + 150 + 133 133 = 2. Use N95S31B to communicate with IoT Server = 134 134 135 135 == 2.1 How it works == ... ... @@ -167,23 +167,45 @@ 167 167 === 2.2.1 Test Requirement === 168 168 169 169 188 +((( 170 170 To use N95S31B in your city, make sure meet below requirements: 190 +))) 171 171 172 -* Your local operator has already distributed a NB-IoT Network there. 173 -* The local NB-IoT network used the band that N95S31B supports. 174 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 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 +))) 175 175 202 +((( 176 176 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 204 +))) 177 177 206 +((( 178 178 N95S31B supports different communication protocol such as : 208 +))) 179 179 180 180 ((( 181 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 182 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 183 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 184 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 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 +))) 185 185 224 +((( 186 186 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 +))) 187 187 188 188 189 189 ))) ... ... @@ -353,50 +353,81 @@ 353 353 == 2.3 Uplink Payload == 354 354 355 355 396 +((( 356 356 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. 398 +))) 357 357 358 358 401 +((( 359 359 For example: 403 +))) 360 360 405 +((( 361 361 (% 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. 407 +))) 362 362 363 363 410 +((( 364 364 The uplink payloads are composed in ASCII String. For example: 412 +))) 365 365 414 +((( 366 366 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 416 +))) 367 367 418 +((( 368 368 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 420 +))) 369 369 370 370 423 +((( 371 371 (% style="color:red" %)**NOTE:** 425 +))) 372 372 373 373 (% style="color:red" %) 374 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 375 -1. By default, the device will send an uplink message every 1 hour. 428 +1. ((( 429 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 430 +))) 431 +1. ((( 432 +By default, the device will send an uplink message every 1 hour. 433 +))) 376 376 377 377 436 + 378 378 === 2.3.1 Payload Analyze === 379 379 380 380 N95S31B uplink payload includes in total 21 bytes 381 381 382 382 383 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width: 440px" %)442 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 384 384 |=(% style="width: 60px;" %)((( 385 385 **Size(bytes)** 386 -)))|=(% style="width: 60px;" %)**6**|=(% style="width:35px;" %)2|=(% style="width:35px;" %)**2**|=(% style="width:80px;" %)**1**|=(% style="width:80px;" %)1|=(% style="width:99px;" %)5|=(% style="width:77px;" %)**2**|=(% style="width: 60px;" %)**2**445 +)))|=(% 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** 387 387 |(% 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" %)((( 447 +((( 388 388 Reserve/ Same as NBSN95 CFGMOD=1 449 +))) 389 389 451 +((( 390 390 No function here. 453 +))) 391 391 )))|(% style="width:77px" %)((( 455 +((( 392 392 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 457 +))) 393 393 459 +((( 394 394 By SHT31 461 +))) 395 395 )))|(% style="width:80px" %)((( 463 +((( 396 396 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 465 +))) 397 397 467 +((( 398 398 By SHT31 399 399 ))) 470 +))) 400 400 401 401 ((( 402 402 ((( ... ... @@ -455,15 +455,25 @@ 455 455 456 456 === 2.3.3 Version Info === 457 457 458 - 529 +((( 459 459 These bytes include the hardware and software version. 531 +))) 460 460 533 +((( 461 461 Higher byte: Specify hardware version: always 0x00 for N95S31B 535 +))) 462 462 537 +((( 463 463 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 539 +))) 464 464 541 +((( 542 + 543 +))) 465 465 545 +((( 466 466 For example: 0x00 6E: this device is N95S31B with firmware version 110. 547 +))) 467 467 468 468 ((( 469 469 ... ... @@ -752,8 +752,10 @@ 752 752 ((( 753 753 754 754 836 +((( 755 755 (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 756 756 ))) 839 +))) 757 757 758 758 759 759