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,29 +22,16 @@ 22 22 ((( 23 23 24 24 25 -((( 26 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*. 27 -))) 28 28 29 -((( 30 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 32 33 -((( 34 34 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 35 -))) 36 36 37 -((( 38 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 40 41 -((( 42 - 43 -))) 44 44 45 -((( 46 46 ~* make sure you have NB-IoT coverage locally. 47 -))) 48 48 49 49 50 50 ))) ... ... @@ -67,8 +67,6 @@ 67 67 * 8500mAh Battery for long term use 68 68 69 69 70 - 71 - 72 72 == 1.3 Specification == 73 73 74 74 ... ... @@ -77,7 +77,6 @@ 77 77 * Supply Voltage: 2.1v ~~ 3.6v 78 78 * Operating Temperature: -40 ~~ 85°C 79 79 80 - 81 81 (% style="color:#037691" %)**NB-IoT Spec:** 82 82 83 83 * - B1 @H-FDD: 2100MHz ... ... @@ -87,9 +87,9 @@ 87 87 * - B20 @H-FDD: 800MHz 88 88 * - B28 @H-FDD: 700MHz 89 89 90 - 91 91 (% style="color:#037691" %)**Battery:** 92 92 76 + 93 93 * Li/SOCI2 un-chargeable battery 94 94 * Capacity: 8500mAh 95 95 * Self Discharge: <1% / Year @ 25°C ... ... @@ -97,8 +97,6 @@ 97 97 * Max boost current: 2A, 1 second 98 98 99 99 100 - 101 - 102 102 == 1.4 Applications == 103 103 104 104 * Smart Buildings & Home Automation ... ... @@ -127,13 +127,9 @@ 127 127 128 128 === 1.5.2 BOOT MODE / SW1 === 129 129 130 -((( 131 131 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. 132 -))) 133 133 134 -((( 135 135 2) Flash: work mode, device starts to work and send out console output for further debug 136 -))) 137 137 138 138 139 139 ... ... @@ -150,9 +150,6 @@ 150 150 1. When boot the device in flash mode 151 151 1. Send an uplink packet 152 152 153 - 154 - 155 - 156 156 = 2. Use N95S31B to communicate with IoT Server = 157 157 158 158 == 2.1 How it works == ... ... @@ -190,45 +190,23 @@ 190 190 === 2.2.1 Test Requirement === 191 191 192 192 193 -((( 194 194 To use N95S31B in your city, make sure meet below requirements: 195 -))) 196 196 197 -* ((( 198 -Your local operator has already distributed a NB-IoT Network there. 199 -))) 200 -* ((( 201 -The local NB-IoT network used the band that N95S31B supports. 202 -))) 203 -* ((( 204 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 205 -))) 170 +* Your local operator has already distributed a NB-IoT Network there. 171 +* The local NB-IoT network used the band that N95S31B supports. 172 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 206 206 207 -((( 208 208 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 209 -))) 210 210 211 -((( 212 212 N95S31B supports different communication protocol such as : 213 -))) 214 214 215 215 ((( 216 -* ((( 217 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 218 -))) 219 -* ((( 220 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 221 -))) 222 -* ((( 223 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 224 -))) 225 -* ((( 226 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 227 -))) 179 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 180 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 181 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 182 +* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 228 228 229 -((( 230 230 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. 231 -))) 232 232 233 233 234 234 ))) ... ... @@ -398,48 +398,27 @@ 398 398 == 2.3 Uplink Payload == 399 399 400 400 401 -((( 402 402 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. 403 -))) 404 404 405 405 406 -((( 407 407 For example: 408 -))) 409 409 410 -((( 411 411 (% 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. 412 -))) 413 413 414 414 415 -((( 416 416 The uplink payloads are composed in ASCII String. For example: 417 -))) 418 418 419 -((( 420 420 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 421 -))) 422 422 423 -((( 424 424 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 425 -))) 426 426 427 427 428 -((( 429 429 (% style="color:red" %)**NOTE:** 430 -))) 431 431 432 432 (% style="color:red" %) 433 -1. ((( 434 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 435 -))) 436 -1. ((( 437 -By default, the device will send an uplink message every 1 hour. 438 -))) 372 +1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 373 +1. By default, the device will send an uplink message every 1 hour. 439 439 440 - 441 - 442 - 443 443 === 2.3.1 Payload Analyze === 444 444 445 445 N95S31B uplink payload includes in total 21 bytes ... ... @@ -448,32 +448,20 @@ 448 448 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 449 449 |=(% style="width: 60px;" %)((( 450 450 **Size(bytes)** 451 -)))|=(% style="width: 5 0px;" %)**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**383 +)))|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2** 452 452 |(% 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" %)((( 453 -((( 454 454 Reserve/ Same as NBSN95 CFGMOD=1 455 -))) 456 456 457 -((( 458 458 No function here. 459 -))) 460 460 )))|(% style="width:77px" %)((( 461 -((( 462 462 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 463 -))) 464 464 465 -((( 466 466 By SHT31 467 -))) 468 468 )))|(% style="width:80px" %)((( 469 -((( 470 470 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 471 -))) 472 472 473 -((( 474 474 By SHT31 475 475 ))) 476 -))) 477 477 478 478 ((( 479 479 ((( ... ... @@ -829,10 +829,8 @@ 829 829 ((( 830 830 831 831 832 -((( 833 833 (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 834 834 ))) 835 -))) 836 836 837 837 838 838