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 ))) ... ... @@ -53,6 +53,9 @@ 53 53 * Micro SIM card slot for NB-IoT SIM 54 54 * 8500mAh Battery for long term use 55 55 69 + 70 + 71 + 56 56 == 1.3 Specification == 57 57 58 58 ... ... @@ -61,6 +61,7 @@ 61 61 * Supply Voltage: 2.1v ~~ 3.6v 62 62 * Operating Temperature: -40 ~~ 85°C 63 63 80 + 64 64 (% style="color:#037691" %)**NB-IoT Spec:** 65 65 66 66 * - B1 @H-FDD: 2100MHz ... ... @@ -70,9 +70,9 @@ 70 70 * - B20 @H-FDD: 800MHz 71 71 * - B28 @H-FDD: 700MHz 72 72 90 + 73 73 (% style="color:#037691" %)**Battery:** 74 74 75 - 76 76 * Li/SOCI2 un-chargeable battery 77 77 * Capacity: 8500mAh 78 78 * Self Discharge: <1% / Year @ 25°C ... ... @@ -79,6 +79,9 @@ 79 79 * Max continuously current: 130mA 80 80 * Max boost current: 2A, 1 second 81 81 99 + 100 + 101 + 82 82 == 1.4 Applications == 83 83 84 84 * Smart Buildings & Home Automation ... ... @@ -107,9 +107,13 @@ 107 107 108 108 === 1.5.2 BOOT MODE / SW1 === 109 109 130 +((( 110 110 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 +))) 111 111 134 +((( 112 112 2) Flash: work mode, device starts to work and send out console output for further debug 136 +))) 113 113 114 114 115 115 ... ... @@ -126,6 +126,9 @@ 126 126 1. When boot the device in flash mode 127 127 1. Send an uplink packet 128 128 153 + 154 + 155 + 129 129 = 2. Use N95S31B to communicate with IoT Server = 130 130 131 131 == 2.1 How it works == ... ... @@ -163,23 +163,45 @@ 163 163 === 2.2.1 Test Requirement === 164 164 165 165 193 +((( 166 166 To use N95S31B in your city, make sure meet below requirements: 195 +))) 167 167 168 -* Your local operator has already distributed a NB-IoT Network there. 169 -* The local NB-IoT network used the band that N95S31B supports. 170 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 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 +))) 171 171 207 +((( 172 172 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 209 +))) 173 173 211 +((( 174 174 N95S31B supports different communication protocol such as : 213 +))) 175 175 176 176 ((( 177 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 178 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 179 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 180 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 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 +))) 181 181 229 +((( 182 182 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 +))) 183 183 184 184 185 185 ))) ... ... @@ -371,8 +371,6 @@ 371 371 1. By default, the device will send an uplink message every 1 hour. 372 372 373 373 374 - 375 - 376 376 === 2.3.1 Payload Analyze === 377 377 378 378 N95S31B uplink payload includes in total 21 bytes ... ... @@ -381,7 +381,7 @@ 381 381 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 382 382 |=(% style="width: 60px;" %)((( 383 383 **Size(bytes)** 384 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 1 20px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2**431 +)))|=(% 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** 385 385 |(% 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" %)((( 386 386 ((( 387 387 Reserve/ Same as NBSN95 CFGMOD=1