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
-
... ... @@ -68,6 +68,7 @@ 68 68 69 69 70 70 71 + 71 71 == 1.3 Specification == 72 72 73 73 ... ... @@ -76,6 +76,7 @@ 76 76 * Supply Voltage: 2.1v ~~ 3.6v 77 77 * Operating Temperature: -40 ~~ 85°C 78 78 80 + 79 79 (% style="color:#037691" %)**NB-IoT Spec:** 80 80 81 81 * - B1 @H-FDD: 2100MHz ... ... @@ -85,6 +85,7 @@ 85 85 * - B20 @H-FDD: 800MHz 86 86 * - B28 @H-FDD: 700MHz 87 87 90 + 88 88 (% style="color:#037691" %)**Battery:** 89 89 90 90 * Li/SOCI2 un-chargeable battery ... ... @@ -95,6 +95,7 @@ 95 95 96 96 97 97 101 + 98 98 == 1.4 Applications == 99 99 100 100 * Smart Buildings & Home Automation ... ... @@ -108,7 +108,7 @@ 108 108 109 109 110 110 111 -== 1.5 Pin Definitions & Switch==115 +== 1.5 Pin Definitions == 112 112 113 113 N95S31B use the mother board from NBSN95 which as below. 114 114 ... ... @@ -123,13 +123,9 @@ 123 123 124 124 === 1.5.2 BOOT MODE / SW1 === 125 125 126 -((( 127 127 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 -))) 129 129 130 -((( 131 131 2) Flash: work mode, device starts to work and send out console output for further debug 132 -))) 133 133 134 134 135 135 ... ... @@ -146,7 +146,6 @@ 146 146 1. When boot the device in flash mode 147 147 1. Send an uplink packet 148 148 149 - 150 150 = 2. Use N95S31B to communicate with IoT Server = 151 151 152 152 == 2.1 How it works == ... ... @@ -165,7 +165,7 @@ 165 165 166 166 ))) 167 167 168 -[[image:16575 20100595-569.png]]167 +[[image:1657350248151-650.png]] 169 169 170 170 ((( 171 171 ... ... @@ -184,45 +184,23 @@ 184 184 === 2.2.1 Test Requirement === 185 185 186 186 187 -((( 188 188 To use N95S31B in your city, make sure meet below requirements: 189 -))) 190 190 191 -* ((( 192 -Your local operator has already distributed a NB-IoT Network there. 193 -))) 194 -* ((( 195 -The local NB-IoT network used the band that N95S31B supports. 196 -))) 197 -* ((( 198 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 199 -))) 188 +* Your local operator has already distributed a NB-IoT Network there. 189 +* The local NB-IoT network used the band that N95S31B supports. 190 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 200 200 201 -((( 202 202 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 203 -))) 204 204 205 -((( 206 206 N95S31B supports different communication protocol such as : 207 -))) 208 208 209 209 ((( 210 -* ((( 211 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 212 -))) 213 -* ((( 214 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 215 -))) 216 -* ((( 217 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 218 -))) 219 -* ((( 220 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 221 -))) 197 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 198 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 199 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 200 +* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 222 222 223 -((( 224 224 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. 225 -))) 226 226 227 227 228 228 ))) ... ... @@ -392,49 +392,28 @@ 392 392 == 2.3 Uplink Payload == 393 393 394 394 395 -((( 396 -N95S31B 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. 397 -))) 372 +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 398 399 399 400 -((( 401 401 For example: 402 -))) 403 403 404 -((( 405 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 406 -))) 377 + (% 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 407 408 408 409 -((( 410 410 The uplink payloads are composed in ASCII String. For example: 411 -))) 412 412 413 -((( 414 414 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 415 -))) 416 416 417 -((( 418 418 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 419 -))) 420 420 421 421 422 -((( 423 423 (% style="color:red" %)**NOTE:** 424 -))) 425 425 426 426 (% style="color:red" %) 427 -1. ((( 428 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 429 -))) 430 -1. ((( 431 -By default, the device will send an uplink message every 1 hour. 390 +1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 391 +1. By default, the device will send an uplink message every 1 hour. 432 432 433 433 434 - 435 - 436 -))) 437 - 438 438 === 2.3.1 Payload Analyze === 439 439 440 440 N95S31B uplink payload includes in total 21 bytes ... ... @@ -527,25 +527,15 @@ 527 527 528 528 === 2.3.3 Version Info === 529 529 530 - (((486 + 531 531 These bytes include the hardware and software version. 532 -))) 533 533 534 -((( 535 535 Higher byte: Specify hardware version: always 0x00 for N95S31B 536 -))) 537 537 538 -((( 539 539 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 540 -))) 541 541 542 -((( 543 - 544 -))) 545 545 546 -((( 547 547 For example: 0x00 6E: this device is N95S31B with firmware version 110. 548 -))) 549 549 550 550 ((( 551 551 ... ... @@ -616,7 +616,7 @@ 616 616 617 617 == 2.4 Downlink Payload == 618 618 619 -By default, 95S31Bprints the downlink payload to console port.565 +By default, NDDS75 prints the downlink payload to console port. 620 620 621 621 [[image:image-20220709100028-1.png]] 622 622 ... ... @@ -654,7 +654,7 @@ 654 654 ))) 655 655 656 656 ((( 657 -If payload = 0x04FF, it will reset the 95S31B603 +If payload = 0x04FF, it will reset the NDDS75 658 658 ))) 659 659 660 660 ... ... @@ -834,10 +834,8 @@ 834 834 ((( 835 835 836 836 837 -((( 838 838 (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 839 839 ))) 840 -))) 841 841 842 842 843 843
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content