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
-
... ... @@ -77,6 +77,7 @@ 77 77 * Supply Voltage: 2.1v ~~ 3.6v 78 78 * Operating Temperature: -40 ~~ 85°C 79 79 80 + 80 80 (% style="color:#037691" %)**NB-IoT Spec:** 81 81 82 82 * - B1 @H-FDD: 2100MHz ... ... @@ -86,9 +86,9 @@ 86 86 * - B20 @H-FDD: 800MHz 87 87 * - B28 @H-FDD: 700MHz 88 88 90 + 89 89 (% style="color:#037691" %)**Battery:** 90 90 91 - 92 92 * Li/SOCI2 un-chargeable battery 93 93 * Capacity: 8500mAh 94 94 * Self Discharge: <1% / Year @ 25°C ... ... @@ -95,6 +95,9 @@ 95 95 * Max continuously current: 130mA 96 96 * Max boost current: 2A, 1 second 97 97 99 + 100 + 101 + 98 98 == 1.4 Applications == 99 99 100 100 * Smart Buildings & Home Automation ... ... @@ -123,9 +123,13 @@ 123 123 124 124 === 1.5.2 BOOT MODE / SW1 === 125 125 130 +((( 126 126 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 +))) 127 127 134 +((( 128 128 2) Flash: work mode, device starts to work and send out console output for further debug 136 +))) 129 129 130 130 131 131 ... ... @@ -142,6 +142,9 @@ 142 142 1. When boot the device in flash mode 143 143 1. Send an uplink packet 144 144 153 + 154 + 155 + 145 145 = 2. Use N95S31B to communicate with IoT Server = 146 146 147 147 == 2.1 How it works == ... ... @@ -179,23 +179,45 @@ 179 179 === 2.2.1 Test Requirement === 180 180 181 181 193 +((( 182 182 To use N95S31B in your city, make sure meet below requirements: 195 +))) 183 183 184 -* Your local operator has already distributed a NB-IoT Network there. 185 -* The local NB-IoT network used the band that N95S31B supports. 186 -* 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 +))) 187 187 207 +((( 188 188 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 209 +))) 189 189 211 +((( 190 190 N95S31B supports different communication protocol such as : 213 +))) 191 191 192 192 ((( 193 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 194 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 195 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 196 -* 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 +))) 197 197 229 +((( 198 198 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 +))) 199 199 200 200 201 201 ))) ... ... @@ -365,28 +365,48 @@ 365 365 == 2.3 Uplink Payload == 366 366 367 367 401 +((( 368 368 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 +))) 369 369 370 370 406 +((( 371 371 For example: 408 +))) 372 372 410 +((( 373 373 (% 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 +))) 374 374 375 375 415 +((( 376 376 The uplink payloads are composed in ASCII String. For example: 417 +))) 377 377 419 +((( 378 378 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 421 +))) 379 379 423 +((( 380 380 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 425 +))) 381 381 382 382 428 +((( 383 383 (% style="color:red" %)**NOTE:** 430 +))) 384 384 385 385 (% style="color:red" %) 386 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 387 -1. By default, the device will send an uplink message every 1 hour. 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 +))) 388 388 389 389 441 + 442 + 390 390 === 2.3.1 Payload Analyze === 391 391 392 392 N95S31B uplink payload includes in total 21 bytes ... ... @@ -776,8 +776,10 @@ 776 776 ((( 777 777 778 778 832 +((( 779 779 (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 780 780 ))) 835 +))) 781 781 782 782 783 783