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
-
... ... @@ -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 ... ... @@ -112,7 +112,7 @@ 112 112 113 113 114 114 115 -== 1.5 Pin Definitions == 111 +== 1.5 Pin Definitions & Switch == 116 116 117 117 N95S31B use the mother board from NBSN95 which as below. 118 118 ... ... @@ -127,9 +127,13 @@ 127 127 128 128 === 1.5.2 BOOT MODE / SW1 === 129 129 126 +((( 130 130 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 +))) 131 131 130 +((( 132 132 2) Flash: work mode, device starts to work and send out console output for further debug 132 +))) 133 133 134 134 135 135 ... ... @@ -146,6 +146,8 @@ 146 146 1. When boot the device in flash mode 147 147 1. Send an uplink packet 148 148 149 + 150 + 149 149 = 2. Use N95S31B to communicate with IoT Server = 150 150 151 151 == 2.1 How it works == ... ... @@ -164,7 +164,7 @@ 164 164 165 165 ))) 166 166 167 -[[image:1657 350248151-650.png]]169 +[[image:1657520100595-569.png]] 168 168 169 169 ((( 170 170 ... ... @@ -183,23 +183,45 @@ 183 183 === 2.2.1 Test Requirement === 184 184 185 185 188 +((( 186 186 To use N95S31B in your city, make sure meet below requirements: 190 +))) 187 187 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. 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 +))) 191 191 202 +((( 192 192 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 204 +))) 193 193 206 +((( 194 194 N95S31B supports different communication protocol such as : 208 +))) 195 195 196 196 ((( 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(%%)) 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 +))) 201 201 224 +((( 202 202 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 +))) 203 203 204 204 205 205 ))) ... ... @@ -369,28 +369,49 @@ 369 369 == 2.3 Uplink Payload == 370 370 371 371 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. 396 +((( 397 +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. 398 +))) 373 373 374 374 401 +((( 375 375 For example: 403 +))) 376 376 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. 405 +((( 406 + (% 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. 407 +))) 378 378 379 379 410 +((( 380 380 The uplink payloads are composed in ASCII String. For example: 412 +))) 381 381 414 +((( 382 382 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 416 +))) 383 383 418 +((( 384 384 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 420 +))) 385 385 386 386 423 +((( 387 387 (% style="color:red" %)**NOTE:** 425 +))) 388 388 389 389 (% style="color:red" %) 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. 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. 392 392 393 393 435 + 436 + 437 +))) 438 + 394 394 === 2.3.1 Payload Analyze === 395 395 396 396 N95S31B uplink payload includes in total 21 bytes ... ... @@ -483,15 +483,25 @@ 483 483 484 484 === 2.3.3 Version Info === 485 485 486 - 531 +((( 487 487 These bytes include the hardware and software version. 533 +))) 488 488 535 +((( 489 489 Higher byte: Specify hardware version: always 0x00 for N95S31B 537 +))) 490 490 539 +((( 491 491 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 541 +))) 492 492 543 +((( 544 + 545 +))) 493 493 547 +((( 494 494 For example: 0x00 6E: this device is N95S31B with firmware version 110. 549 +))) 495 495 496 496 ((( 497 497 ... ... @@ -562,7 +562,7 @@ 562 562 563 563 == 2.4 Downlink Payload == 564 564 565 -By default, DDS75 prints the downlink payload to console port.620 +By default, N95S31B prints the downlink payload to console port. 566 566 567 567 [[image:image-20220709100028-1.png]] 568 568 ... ... @@ -600,7 +600,7 @@ 600 600 ))) 601 601 602 602 ((( 603 -If payload = 0x04FF, it will reset the DDS75658 +If payload = 0x04FF, it will reset the N95S31B 604 604 ))) 605 605 606 606 ... ... @@ -780,8 +780,10 @@ 780 780 ((( 781 781 782 782 838 +((( 783 783 (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 784 784 ))) 841 +))) 785 785 786 786 787 787
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content