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
-
... ... @@ -66,9 +66,6 @@ 66 66 * Micro SIM card slot for NB-IoT SIM 67 67 * 8500mAh Battery for long term use 68 68 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 88 + 93 93 * Li/SOCI2 un-chargeable battery 94 94 * Capacity: 8500mAh 95 95 * Self Discharge: <1% / Year @ 25°C ... ... @@ -96,9 +96,6 @@ 96 96 * Max continuously current: 130mA 97 97 * Max boost current: 2A, 1 second 98 98 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 -))) 181 +* Your local operator has already distributed a NB-IoT Network there. 182 +* The local NB-IoT network used the band that N95S31B supports. 183 +* 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 -))) 190 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 191 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 192 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 193 +* 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,28 @@ 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 -))) 383 +1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 384 +1. By default, the device will send an uplink message every 1 hour. 439 439 440 440 441 - 442 - 443 443 === 2.3.1 Payload Analyze === 444 444 445 445 N95S31B uplink payload includes in total 21 bytes ... ... @@ -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