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, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -66,6 +66,8 @@ 66 66 * Micro SIM card slot for NB-IoT SIM 67 67 * 8500mAh Battery for long term use 68 68 69 + 70 + 69 69 == 1.3 Specification == 70 70 71 71 ... ... @@ -85,7 +85,6 @@ 85 85 86 86 (% style="color:#037691" %)**Battery:** 87 87 88 - 89 89 * Li/SOCI2 un-chargeable battery 90 90 * Capacity: 8500mAh 91 91 * Self Discharge: <1% / Year @ 25°C ... ... @@ -92,6 +92,8 @@ 92 92 * Max continuously current: 130mA 93 93 * Max boost current: 2A, 1 second 94 94 96 + 97 + 95 95 == 1.4 Applications == 96 96 97 97 * Smart Buildings & Home Automation ... ... @@ -105,7 +105,7 @@ 105 105 106 106 107 107 108 -== 1.5 Pin Definitions == 111 +== 1.5 Pin Definitions & Switch == 109 109 110 110 N95S31B use the mother board from NBSN95 which as below. 111 111 ... ... @@ -120,9 +120,13 @@ 120 120 121 121 === 1.5.2 BOOT MODE / SW1 === 122 122 126 +((( 123 123 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. 128 +))) 124 124 130 +((( 125 125 2) Flash: work mode, device starts to work and send out console output for further debug 132 +))) 126 126 127 127 128 128 ... ... @@ -139,6 +139,8 @@ 139 139 1. When boot the device in flash mode 140 140 1. Send an uplink packet 141 141 149 + 150 + 142 142 = 2. Use N95S31B to communicate with IoT Server = 143 143 144 144 == 2.1 How it works == ... ... @@ -157,7 +157,7 @@ 157 157 158 158 ))) 159 159 160 -[[image:1657 350248151-650.png]]169 +[[image:1657520100595-569.png]] 161 161 162 162 ((( 163 163 ... ... @@ -176,23 +176,45 @@ 176 176 === 2.2.1 Test Requirement === 177 177 178 178 188 +((( 179 179 To use N95S31B in your city, make sure meet below requirements: 190 +))) 180 180 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. 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 +))) 184 184 202 +((( 185 185 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 204 +))) 186 186 206 +((( 187 187 N95S31B supports different communication protocol such as : 208 +))) 188 188 189 189 ((( 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(%%)) 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 +))) 194 194 224 +((( 195 195 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 +))) 196 196 197 197 198 198 ))) ... ... @@ -362,28 +362,45 @@ 362 362 == 2.3 Uplink Payload == 363 363 364 364 396 +((( 365 365 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 +))) 366 366 367 367 401 +((( 368 368 For example: 403 +))) 369 369 405 +((( 370 370 (% 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 +))) 371 371 372 372 410 +((( 373 373 The uplink payloads are composed in ASCII String. For example: 412 +))) 374 374 414 +((( 375 375 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 416 +))) 376 376 418 +((( 377 377 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 420 +))) 378 378 379 379 423 +((( 380 380 (% style="color:red" %)**NOTE:** 425 +))) 381 381 382 382 (% style="color:red" %) 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. 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 +))) 385 385 386 - 387 387 === 2.3.1 Payload Analyze === 388 388 389 389 N95S31B uplink payload includes in total 21 bytes ... ... @@ -476,15 +476,25 @@ 476 476 477 477 === 2.3.3 Version Info === 478 478 479 - 527 +((( 480 480 These bytes include the hardware and software version. 529 +))) 481 481 531 +((( 482 482 Higher byte: Specify hardware version: always 0x00 for N95S31B 533 +))) 483 483 535 +((( 484 484 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 537 +))) 485 485 539 +((( 540 + 541 +))) 486 486 543 +((( 487 487 For example: 0x00 6E: this device is N95S31B with firmware version 110. 545 +))) 488 488 489 489 ((( 490 490 ... ... @@ -773,8 +773,10 @@ 773 773 ((( 774 774 775 775 834 +((( 776 776 (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 777 777 ))) 837 +))) 778 778 779 779 780 780
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content