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
-
... ... @@ -9,6 +9,7 @@ 9 9 10 10 **Table of Contents:** 11 11 12 +{{toc/}} 12 12 13 13 14 14 ... ... @@ -21,16 +21,29 @@ 21 21 ((( 22 22 23 23 25 +((( 24 24 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 +))) 25 25 29 +((( 26 26 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 +))) 27 27 33 +((( 28 28 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 35 +))) 29 29 37 +((( 30 30 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 +))) 31 31 41 +((( 42 + 43 +))) 32 32 45 +((( 33 33 ~* make sure you have NB-IoT coverage locally. 47 +))) 34 34 35 35 36 36 ))) ... ... @@ -53,8 +53,6 @@ 53 53 * 8500mAh Battery for long term use 54 54 55 55 56 - 57 - 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -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 ... ... @@ -82,8 +82,6 @@ 82 82 * Max boost current: 2A, 1 second 83 83 84 84 85 - 86 - 87 87 == 1.4 Applications == 88 88 89 89 * Smart Buildings & Home Automation ... ... @@ -97,7 +97,7 @@ 97 97 98 98 99 99 100 -== 1.5 Pin Definitions == 109 +== 1.5 Pin Definitions & Switch == 101 101 102 102 N95S31B use the mother board from NBSN95 which as below. 103 103 ... ... @@ -112,9 +112,13 @@ 112 112 113 113 === 1.5.2 BOOT MODE / SW1 === 114 114 124 +((( 115 115 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 +))) 116 116 128 +((( 117 117 2) Flash: work mode, device starts to work and send out console output for further debug 130 +))) 118 118 119 119 120 120 ... ... @@ -169,23 +169,45 @@ 169 169 === 2.2.1 Test Requirement === 170 170 171 171 185 +((( 172 172 To use N95S31B in your city, make sure meet below requirements: 187 +))) 173 173 174 -* Your local operator has already distributed a NB-IoT Network there. 175 -* The local NB-IoT network used the band that N95S31B supports. 176 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 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 +))) 177 177 199 +((( 178 178 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 201 +))) 179 179 203 +((( 180 180 N95S31B supports different communication protocol such as : 205 +))) 181 181 182 182 ((( 183 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 184 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 185 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 186 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 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 +))) 187 187 221 +((( 188 188 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 +))) 189 189 190 190 191 191 ))) ... ... @@ -355,51 +355,80 @@ 355 355 == 2.3 Uplink Payload == 356 356 357 357 393 +((( 358 358 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 +))) 359 359 360 360 398 +((( 361 361 For example: 400 +))) 362 362 402 +((( 363 363 (% 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 +))) 364 364 365 365 407 +((( 366 366 The uplink payloads are composed in ASCII String. For example: 409 +))) 367 367 411 +((( 368 368 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 413 +))) 369 369 415 +((( 370 370 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 417 +))) 371 371 372 372 420 +((( 373 373 (% style="color:red" %)**NOTE:** 422 +))) 374 374 375 375 (% style="color:red" %) 376 -1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]]. 377 -1. By default, the device will send an uplink message every 1 hour. 425 +1. ((( 426 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 427 +))) 428 +1. ((( 429 +By default, the device will send an uplink message every 1 hour. 430 +))) 378 378 379 379 380 - 381 381 === 2.3.1 Payload Analyze === 382 382 383 383 N95S31B uplink payload includes in total 21 bytes 384 384 385 385 386 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width: 440px" %)438 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 387 387 |=(% style="width: 60px;" %)((( 388 388 **Size(bytes)** 389 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1** 390 -|(% 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:123px" %)MOD 0X01|(% style="width:99px" %)((( 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 +((( 391 391 Reserve/ Same as NBSN95 CFGMOD=1 445 +))) 392 392 447 +((( 393 393 No function here. 449 +))) 394 394 )))|(% style="width:77px" %)((( 395 -[[Temperature >>||anchor="H2.4.5A0Distance"]] 451 +((( 452 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 453 +))) 396 396 455 +((( 397 397 By SHT31 457 +))) 398 398 )))|(% style="width:80px" %)((( 399 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 459 +((( 460 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 461 +))) 400 400 463 +((( 401 401 By SHT31 402 402 ))) 466 +))) 403 403 404 404 ((( 405 405 ((( ... ... @@ -458,15 +458,25 @@ 458 458 459 459 === 2.3.3 Version Info === 460 460 461 - 525 +((( 462 462 These bytes include the hardware and software version. 527 +))) 463 463 529 +((( 464 464 Higher byte: Specify hardware version: always 0x00 for N95S31B 531 +))) 465 465 533 +((( 466 466 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 535 +))) 467 467 537 +((( 538 + 539 +))) 468 468 541 +((( 469 469 For example: 0x00 6E: this device is N95S31B with firmware version 110. 543 +))) 470 470 471 471 ((( 472 472 ... ... @@ -535,7 +535,7 @@ 535 535 536 536 537 537 538 -== 2. 5Downlink Payload ==612 +== 2.4 Downlink Payload == 539 539 540 540 By default, NDDS75 prints the downlink payload to console port. 541 541 ... ... @@ -755,8 +755,10 @@ 755 755 ((( 756 756 757 757 832 +((( 758 758 (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 759 759 ))) 835 +))) 760 760 761 761 762 762
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content