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
-
... ... @@ -68,7 +68,6 @@ 68 68 69 69 70 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,7 +87,6 @@ 87 87 * - B20 @H-FDD: 800MHz 88 88 * - B28 @H-FDD: 700MHz 89 89 90 - 91 91 (% style="color:#037691" %)**Battery:** 92 92 93 93 * Li/SOCI2 un-chargeable battery ... ... @@ -98,7 +98,6 @@ 98 98 99 99 100 100 101 - 102 102 == 1.4 Applications == 103 103 104 104 * Smart Buildings & Home Automation ... ... @@ -152,7 +152,6 @@ 152 152 153 153 154 154 155 - 156 156 = 2. Use N95S31B to communicate with IoT Server = 157 157 158 158 == 2.1 How it works == ... ... @@ -190,23 +190,45 @@ 190 190 === 2.2.1 Test Requirement === 191 191 192 192 188 +((( 193 193 To use N95S31B in your city, make sure meet below requirements: 190 +))) 194 194 195 -* Your local operator has already distributed a NB-IoT Network there. 196 -* The local NB-IoT network used the band that N95S31B supports. 197 -* 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 +))) 198 198 202 +((( 199 199 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 204 +))) 200 200 206 +((( 201 201 N95S31B supports different communication protocol such as : 208 +))) 202 202 203 203 ((( 204 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 205 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 206 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 207 -* 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 +))) 208 208 224 +((( 209 209 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 +))) 210 210 211 211 212 212 ))) ... ... @@ -376,28 +376,47 @@ 376 376 == 2.3 Uplink Payload == 377 377 378 378 396 +((( 379 379 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 +))) 380 380 381 381 401 +((( 382 382 For example: 403 +))) 383 383 405 +((( 384 384 (% 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 +))) 385 385 386 386 410 +((( 387 387 The uplink payloads are composed in ASCII String. For example: 412 +))) 388 388 414 +((( 389 389 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 416 +))) 390 390 418 +((( 391 391 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 420 +))) 392 392 393 393 423 +((( 394 394 (% style="color:red" %)**NOTE:** 425 +))) 395 395 396 396 (% style="color:red" %) 397 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 398 -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 +))) 399 399 400 400 436 + 401 401 === 2.3.1 Payload Analyze === 402 402 403 403 N95S31B uplink payload includes in total 21 bytes ... ... @@ -490,15 +490,25 @@ 490 490 491 491 === 2.3.3 Version Info === 492 492 493 - 529 +((( 494 494 These bytes include the hardware and software version. 531 +))) 495 495 533 +((( 496 496 Higher byte: Specify hardware version: always 0x00 for N95S31B 535 +))) 497 497 537 +((( 498 498 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 539 +))) 499 499 541 +((( 542 + 543 +))) 500 500 545 +((( 501 501 For example: 0x00 6E: this device is N95S31B with firmware version 110. 547 +))) 502 502 503 503 ((( 504 504 ... ... @@ -787,8 +787,10 @@ 787 787 ((( 788 788 789 789 836 +((( 790 790 (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 791 791 ))) 839 +))) 792 792 793 793 794 794