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, 0 added, 1 removed)
Details
- Page properties
-
- Content
-
... ... @@ -67,6 +67,8 @@ 67 67 * 8500mAh Battery for long term use 68 68 69 69 70 + 71 + 70 70 == 1.3 Specification == 71 71 72 72 ... ... @@ -75,6 +75,7 @@ 75 75 * Supply Voltage: 2.1v ~~ 3.6v 76 76 * Operating Temperature: -40 ~~ 85°C 77 77 80 + 78 78 (% style="color:#037691" %)**NB-IoT Spec:** 79 79 80 80 * - B1 @H-FDD: 2100MHz ... ... @@ -84,6 +84,7 @@ 84 84 * - B20 @H-FDD: 800MHz 85 85 * - B28 @H-FDD: 700MHz 86 86 90 + 87 87 (% style="color:#037691" %)**Battery:** 88 88 89 89 * Li/SOCI2 un-chargeable battery ... ... @@ -93,6 +93,8 @@ 93 93 * Max boost current: 2A, 1 second 94 94 95 95 100 + 101 + 96 96 == 1.4 Applications == 97 97 98 98 * Smart Buildings & Home Automation ... ... @@ -106,7 +106,7 @@ 106 106 107 107 108 108 109 -== 1.5 Pin Definitions & Switch==115 +== 1.5 Pin Definitions == 110 110 111 111 N95S31B use the mother board from NBSN95 which as below. 112 112 ... ... @@ -144,7 +144,6 @@ 144 144 1. When boot the device in flash mode 145 145 1. Send an uplink packet 146 146 147 - 148 148 = 2. Use N95S31B to communicate with IoT Server = 149 149 150 150 == 2.1 How it works == ... ... @@ -182,45 +182,23 @@ 182 182 === 2.2.1 Test Requirement === 183 183 184 184 185 -((( 186 186 To use N95S31B in your city, make sure meet below requirements: 187 -))) 188 188 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 -))) 192 +* Your local operator has already distributed a NB-IoT Network there. 193 +* The local NB-IoT network used the band that N95S31B supports. 194 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 198 198 199 -((( 200 200 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 201 -))) 202 202 203 -((( 204 204 N95S31B supports different communication protocol such as : 205 -))) 206 206 207 207 ((( 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 -))) 201 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 202 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 203 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 204 +* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 220 220 221 -((( 222 222 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 -))) 224 224 225 225 226 226 ))) ... ... @@ -390,44 +390,26 @@ 390 390 == 2.3 Uplink Payload == 391 391 392 392 393 -((( 394 394 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 -))) 396 396 397 397 398 -((( 399 399 For example: 400 -))) 401 401 402 -((( 403 403 (% 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 -))) 405 405 406 406 407 -((( 408 408 The uplink payloads are composed in ASCII String. For example: 409 -))) 410 410 411 -((( 412 412 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 413 -))) 414 414 415 -((( 416 416 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 417 -))) 418 418 419 419 420 -((( 421 421 (% style="color:red" %)**NOTE:** 422 -))) 423 423 424 424 (% style="color:red" %) 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 -))) 394 +1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 395 +1. By default, the device will send an uplink message every 1 hour. 431 431 432 432 433 433 === 2.3.1 Payload Analyze === ... ... @@ -522,25 +522,15 @@ 522 522 523 523 === 2.3.3 Version Info === 524 524 525 - (((490 + 526 526 These bytes include the hardware and software version. 527 -))) 528 528 529 -((( 530 530 Higher byte: Specify hardware version: always 0x00 for N95S31B 531 -))) 532 532 533 -((( 534 534 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 535 -))) 536 536 537 -((( 538 - 539 -))) 540 540 541 -((( 542 542 For example: 0x00 6E: this device is N95S31B with firmware version 110. 543 -))) 544 544 545 545 ((( 546 546 ... ... @@ -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
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content