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
-
... ... @@ -22,29 +22,16 @@ 22 22 ((( 23 23 24 24 25 -((( 26 26 The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*. 27 -))) 28 28 29 -((( 30 30 The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use. 31 -))) 32 32 33 -((( 34 34 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 35 -))) 36 36 37 -((( 38 38 N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report). 39 -))) 40 40 41 -((( 42 - 43 -))) 44 44 45 -((( 46 46 ~* make sure you have NB-IoT coverage locally. 47 -))) 48 48 49 49 50 50 ))) ... ... @@ -66,8 +66,6 @@ 66 66 * Micro SIM card slot for NB-IoT SIM 67 67 * 8500mAh Battery for long term use 68 68 69 - 70 - 71 71 == 1.3 Specification == 72 72 73 73 ... ... @@ -87,6 +87,7 @@ 87 87 88 88 (% style="color:#037691" %)**Battery:** 89 89 75 + 90 90 * Li/SOCI2 un-chargeable battery 91 91 * Capacity: 8500mAh 92 92 * Self Discharge: <1% / Year @ 25°C ... ... @@ -93,8 +93,6 @@ 93 93 * Max continuously current: 130mA 94 94 * Max boost current: 2A, 1 second 95 95 96 - 97 - 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==95 +== 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]]147 +[[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 -))) 168 +* Your local operator has already distributed a NB-IoT Network there. 169 +* The local NB-IoT network used the band that N95S31B supports. 170 +* 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 -))) 177 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 178 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 179 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 180 +* 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,48 +392,29 @@ 392 392 == 2.3 Uplink Payload == 393 393 394 394 395 -((( 396 396 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. 397 -))) 398 398 399 399 400 -((( 401 401 For example: 402 -))) 403 403 404 -((( 405 405 (% 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. 406 -))) 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. 370 +1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 371 +1. By default, the device will send an uplink message every 1 hour. 432 432 433 433 434 434 435 - 436 -))) 437 437 438 438 === 2.3.1 Payload Analyze === 439 439 ... ... @@ -527,25 +527,15 @@ 527 527 528 528 === 2.3.3 Version Info === 529 529 530 - (((468 + 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.547 +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 95S31B585 +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