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)
-
Attachments (0 modified, 1 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 ))) ... ... @@ -54,6 +54,7 @@ 54 54 * 8500mAh Battery for long term use 55 55 56 56 70 + 57 57 == 1.3 Specification == 58 58 59 59 ... ... @@ -73,7 +73,6 @@ 73 73 74 74 (% style="color:#037691" %)**Battery:** 75 75 76 - 77 77 * Li/SOCI2 un-chargeable battery 78 78 * Capacity: 8500mAh 79 79 * Self Discharge: <1% / Year @ 25°C ... ... @@ -81,6 +81,7 @@ 81 81 * Max boost current: 2A, 1 second 82 82 83 83 97 + 84 84 == 1.4 Applications == 85 85 86 86 * Smart Buildings & Home Automation ... ... @@ -94,7 +94,7 @@ 94 94 95 95 96 96 97 -== 1.5 Pin Definitions == 111 +== 1.5 Pin Definitions & Switch == 98 98 99 99 N95S31B use the mother board from NBSN95 which as below. 100 100 ... ... @@ -109,9 +109,13 @@ 109 109 110 110 === 1.5.2 BOOT MODE / SW1 === 111 111 126 +((( 112 112 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 +))) 113 113 130 +((( 114 114 2) Flash: work mode, device starts to work and send out console output for further debug 132 +))) 115 115 116 116 117 117 ... ... @@ -128,6 +128,7 @@ 128 128 1. When boot the device in flash mode 129 129 1. Send an uplink packet 130 130 149 + 131 131 = 2. Use N95S31B to communicate with IoT Server = 132 132 133 133 == 2.1 How it works == ... ... @@ -146,7 +146,7 @@ 146 146 147 147 ))) 148 148 149 -[[image:1657 350248151-650.png]]168 +[[image:1657520100595-569.png]] 150 150 151 151 ((( 152 152 ... ... @@ -165,23 +165,45 @@ 165 165 === 2.2.1 Test Requirement === 166 166 167 167 187 +((( 168 168 To use N95S31B in your city, make sure meet below requirements: 189 +))) 169 169 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. 191 +* ((( 192 +Your local operator has already distributed a NB-IoT Network there. 193 +))) 194 +* ((( 195 +The local NB-IoT network used the band that N95S31B supports. 196 +))) 197 +* ((( 198 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 199 +))) 173 173 201 +((( 174 174 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 203 +))) 175 175 205 +((( 176 176 N95S31B supports different communication protocol such as : 207 +))) 177 177 178 178 ((( 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(%%)) 210 +* ((( 211 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 212 +))) 213 +* ((( 214 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 215 +))) 216 +* ((( 217 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 218 +))) 219 +* ((( 220 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 221 +))) 183 183 223 +((( 184 184 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. 225 +))) 185 185 186 186 187 187 ))) ... ... @@ -351,26 +351,44 @@ 351 351 == 2.3 Uplink Payload == 352 352 353 353 395 +((( 354 354 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. 397 +))) 355 355 356 356 400 +((( 357 357 For example: 402 +))) 358 358 404 +((( 359 359 (% 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. 406 +))) 360 360 361 361 409 +((( 362 362 The uplink payloads are composed in ASCII String. For example: 411 +))) 363 363 413 +((( 364 364 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 415 +))) 365 365 417 +((( 366 366 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 419 +))) 367 367 368 368 422 +((( 369 369 (% style="color:red" %)**NOTE:** 424 +))) 370 370 371 371 (% style="color:red" %) 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. 427 +1. ((( 428 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 429 +))) 430 +1. ((( 431 +By default, the device will send an uplink message every 1 hour. 432 +))) 374 374 375 375 === 2.3.1 Payload Analyze === 376 376 ... ... @@ -380,20 +380,32 @@ 380 380 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 381 381 |=(% style="width: 60px;" %)((( 382 382 **Size(bytes)** 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**442 +)))|=(% 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** 384 384 |(% 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" %)((( 444 +((( 385 385 Reserve/ Same as NBSN95 CFGMOD=1 446 +))) 386 386 448 +((( 387 387 No function here. 450 +))) 388 388 )))|(% style="width:77px" %)((( 452 +((( 389 389 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 454 +))) 390 390 456 +((( 391 391 By SHT31 458 +))) 392 392 )))|(% style="width:80px" %)((( 460 +((( 393 393 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 462 +))) 394 394 464 +((( 395 395 By SHT31 396 396 ))) 467 +))) 397 397 398 398 ((( 399 399 ((( ... ... @@ -452,15 +452,25 @@ 452 452 453 453 === 2.3.3 Version Info === 454 454 455 - 526 +((( 456 456 These bytes include the hardware and software version. 528 +))) 457 457 530 +((( 458 458 Higher byte: Specify hardware version: always 0x00 for N95S31B 532 +))) 459 459 534 +((( 460 460 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 536 +))) 461 461 538 +((( 539 + 540 +))) 462 462 542 +((( 463 463 For example: 0x00 6E: this device is N95S31B with firmware version 110. 544 +))) 464 464 465 465 ((( 466 466 ... ... @@ -749,8 +749,10 @@ 749 749 ((( 750 750 751 751 833 +((( 752 752 (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 753 753 ))) 836 +))) 754 754 755 755 756 756
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content