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 ... ... @@ -150,6 +150,8 @@ 150 150 1. When boot the device in flash mode 151 151 1. Send an uplink packet 152 152 149 + 150 + 153 153 = 2. Use N95S31B to communicate with IoT Server = 154 154 155 155 == 2.1 How it works == ... ... @@ -187,23 +187,45 @@ 187 187 === 2.2.1 Test Requirement === 188 188 189 189 188 +((( 190 190 To use N95S31B in your city, make sure meet below requirements: 190 +))) 191 191 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. 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 +))) 195 195 202 +((( 196 196 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 204 +))) 197 197 206 +((( 198 198 N95S31B supports different communication protocol such as : 208 +))) 199 199 200 200 ((( 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(%%)) 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 +))) 205 205 224 +((( 206 206 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 +))) 207 207 208 208 209 209 ))) ... ... @@ -373,28 +373,47 @@ 373 373 == 2.3 Uplink Payload == 374 374 375 375 396 +((( 376 376 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 +))) 377 377 378 378 401 +((( 379 379 For example: 403 +))) 380 380 405 +((( 381 381 (% 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 +))) 382 382 383 383 410 +((( 384 384 The uplink payloads are composed in ASCII String. For example: 412 +))) 385 385 414 +((( 386 386 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 416 +))) 387 387 418 +((( 388 388 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 420 +))) 389 389 390 390 423 +((( 391 391 (% style="color:red" %)**NOTE:** 425 +))) 392 392 393 393 (% style="color:red" %) 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. 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 +))) 396 396 397 397 436 + 398 398 === 2.3.1 Payload Analyze === 399 399 400 400 N95S31B uplink payload includes in total 21 bytes ... ... @@ -487,15 +487,25 @@ 487 487 488 488 === 2.3.3 Version Info === 489 489 490 - 529 +((( 491 491 These bytes include the hardware and software version. 531 +))) 492 492 533 +((( 493 493 Higher byte: Specify hardware version: always 0x00 for N95S31B 535 +))) 494 494 537 +((( 495 495 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 539 +))) 496 496 541 +((( 542 + 543 +))) 497 497 545 +((( 498 498 For example: 0x00 6E: this device is N95S31B with firmware version 110. 547 +))) 499 499 500 500 ((( 501 501 ... ... @@ -784,8 +784,10 @@ 784 784 ((( 785 785 786 786 836 +((( 787 787 (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 788 788 ))) 839 +))) 789 789 790 790 791 791