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
-
... ... @@ -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 ))) ... ... @@ -54,7 +54,6 @@ 54 54 55 55 56 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 ... ... @@ -83,7 +83,6 @@ 83 83 84 84 85 85 86 - 87 87 == 1.4 Applications == 88 88 89 89 * Smart Buildings & Home Automation ... ... @@ -112,9 +112,13 @@ 112 112 113 113 === 1.5.2 BOOT MODE / SW1 === 114 114 126 +((( 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. 128 +))) 116 116 130 +((( 117 117 2) Flash: work mode, device starts to work and send out console output for further debug 132 +))) 118 118 119 119 120 120 ... ... @@ -132,6 +132,7 @@ 132 132 1. Send an uplink packet 133 133 134 134 150 + 135 135 = 2. Use N95S31B to communicate with IoT Server = 136 136 137 137 == 2.1 How it works == ... ... @@ -169,23 +169,45 @@ 169 169 === 2.2.1 Test Requirement === 170 170 171 171 188 +((( 172 172 To use N95S31B in your city, make sure meet below requirements: 190 +))) 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. 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 +))) 177 177 202 +((( 178 178 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 204 +))) 179 179 206 +((( 180 180 N95S31B supports different communication protocol such as : 208 +))) 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(%%)) 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 +))) 187 187 224 +((( 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. 226 +))) 189 189 190 190 191 191 ))) ... ... @@ -355,26 +355,44 @@ 355 355 == 2.3 Uplink Payload == 356 356 357 357 396 +((( 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. 398 +))) 359 359 360 360 401 +((( 361 361 For example: 403 +))) 362 362 405 +((( 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. 407 +))) 364 364 365 365 410 +((( 366 366 The uplink payloads are composed in ASCII String. For example: 412 +))) 367 367 414 +((( 368 368 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 416 +))) 369 369 418 +((( 370 370 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 420 +))) 371 371 372 372 423 +((( 373 373 (% style="color:red" %)**NOTE:** 425 +))) 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. 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 +))) 378 378 379 379 380 380 ... ... @@ -383,23 +383,35 @@ 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" %)442 +(% 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" %)((( 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** 446 +|(% 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 +((( 391 391 Reserve/ Same as NBSN95 CFGMOD=1 449 +))) 392 392 451 +((( 393 393 No function here. 453 +))) 394 394 )))|(% style="width:77px" %)((( 395 -[[Temperature >>||anchor="H2.4.5A0Distance"]] 455 +((( 456 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 457 +))) 396 396 459 +((( 397 397 By SHT31 461 +))) 398 398 )))|(% style="width:80px" %)((( 399 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 463 +((( 464 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 465 +))) 400 400 467 +((( 401 401 By SHT31 402 402 ))) 470 +))) 403 403 404 404 ((( 405 405 ((( ... ... @@ -458,15 +458,25 @@ 458 458 459 459 === 2.3.3 Version Info === 460 460 461 - 529 +((( 462 462 These bytes include the hardware and software version. 531 +))) 463 463 533 +((( 464 464 Higher byte: Specify hardware version: always 0x00 for N95S31B 535 +))) 465 465 537 +((( 466 466 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 539 +))) 467 467 541 +((( 542 + 543 +))) 468 468 545 +((( 469 469 For example: 0x00 6E: this device is N95S31B with firmware version 110. 547 +))) 470 470 471 471 ((( 472 472 ... ... @@ -535,7 +535,7 @@ 535 535 536 536 537 537 538 -== 2. 5Downlink Payload ==616 +== 2.4 Downlink Payload == 539 539 540 540 By default, NDDS75 prints the downlink payload to console port. 541 541 ... ... @@ -753,8 +753,12 @@ 753 753 ))) 754 754 755 755 ((( 756 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 834 + 835 + 836 +((( 837 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 757 757 ))) 839 +))) 758 758 759 759 760 760 ... ... @@ -785,7 +785,7 @@ 785 785 = 7. Order Info = 786 786 787 787 788 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**870 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 789 789 790 790 791 791 (% class="wikigeneratedid" %) ... ... @@ -800,7 +800,7 @@ 800 800 801 801 (% style="color:#037691" %)**Package Includes**: 802 802 803 -* NS E01DistanceDetectSensorNode x 1885 +* N95S31B NB-IoT Temperature and Humidity Sensor 804 804 * External antenna x 1 805 805 ))) 806 806 ... ... @@ -809,11 +809,10 @@ 809 809 810 810 (% style="color:#037691" %)**Dimension and weight**: 811 811 812 - 813 813 * Device Size: 13.0 x 5 x 4.5 cm 814 814 * Device Weight: 150g 815 -* Package Size / pcs : 1 5x12x 5.5cm816 -* Weight / pcs : 220g896 +* Package Size / pcs : 14.0 x 8x 5 cm 897 +* Weight / pcs : 180g 817 817 ))) 818 818 819 819 (((