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
-
... ... @@ -17,21 +17,35 @@ 17 17 18 18 = 1. Introduction = 19 19 20 + 20 20 == 1.1 What is N95S31B NB-IoT Sensor Node == 21 21 22 22 ((( 23 23 24 24 26 +((( 25 25 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*. 28 +))) 26 26 30 +((( 27 27 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. 32 +))) 28 28 34 +((( 29 29 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 36 +))) 30 30 38 +((( 31 31 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). 40 +))) 32 32 42 +((( 43 + 44 +))) 33 33 46 +((( 34 34 ~* make sure you have NB-IoT coverage locally. 48 +))) 35 35 36 36 37 37 ))) ... ... @@ -42,6 +42,7 @@ 42 42 43 43 == 1.2 Features == 44 44 59 + 45 45 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 46 46 * Monitor Temperature & Humidity via SHT31 47 47 * AT Commands to change parameters ... ... @@ -55,6 +55,7 @@ 55 55 56 56 57 57 73 + 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -63,6 +63,8 @@ 63 63 * Supply Voltage: 2.1v ~~ 3.6v 64 64 * Operating Temperature: -40 ~~ 85°C 65 65 82 + 83 + 66 66 (% style="color:#037691" %)**NB-IoT Spec:** 67 67 68 68 * - B1 @H-FDD: 2100MHz ... ... @@ -72,9 +72,10 @@ 72 72 * - B20 @H-FDD: 800MHz 73 73 * - B28 @H-FDD: 700MHz 74 74 75 -(% style="color:#037691" %)**Battery:** 76 76 77 77 95 +(% style="color:#037691" %)**Battery:** 96 + 78 78 * Li/SOCI2 un-chargeable battery 79 79 * Capacity: 8500mAh 80 80 * Self Discharge: <1% / Year @ 25°C ... ... @@ -83,8 +83,10 @@ 83 83 84 84 85 85 105 + 86 86 == 1.4 Applications == 87 87 108 + 88 88 * Smart Buildings & Home Automation 89 89 * Logistics and Supply Chain Management 90 90 * Smart Metering ... ... @@ -96,15 +96,20 @@ 96 96 97 97 98 98 99 -== 1.5 Pin Definitions == 100 100 121 +== 1.5 Pin Definitions & Switch == 122 + 123 + 101 101 N95S31B use the mother board from NBSN95 which as below. 102 102 126 + 103 103 [[image:image-20220709144723-1.png]] 104 104 105 105 130 + 106 106 === 1.5.1 Jumper JP2 === 107 107 133 + 108 108 Power on Device when put this jumper. 109 109 110 110 ... ... @@ -111,14 +111,20 @@ 111 111 112 112 === 1.5.2 BOOT MODE / SW1 === 113 113 140 + 141 +((( 114 114 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. 143 +))) 115 115 145 +((( 116 116 2) Flash: work mode, device starts to work and send out console output for further debug 147 +))) 117 117 118 118 119 119 120 120 === 1.5.3 Reset Button === 121 121 153 + 122 122 Press to reboot the device. 123 123 124 124 ... ... @@ -125,13 +125,18 @@ 125 125 126 126 === 1.5.4 LED === 127 127 160 + 128 128 It will flash: 129 129 130 130 1. When boot the device in flash mode 131 131 1. Send an uplink packet 132 132 166 + 167 + 168 + 133 133 = 2. Use N95S31B to communicate with IoT Server = 134 134 171 + 135 135 == 2.1 How it works == 136 136 137 137 ... ... @@ -148,7 +148,7 @@ 148 148 149 149 ))) 150 150 151 -[[image:1657 350248151-650.png]]188 +[[image:1657520100595-569.png]] 152 152 153 153 ((( 154 154 ... ... @@ -164,26 +164,49 @@ 164 164 [[image:image-20220709150546-2.png]] 165 165 166 166 204 + 167 167 === 2.2.1 Test Requirement === 168 168 169 169 208 +((( 170 170 To use N95S31B in your city, make sure meet below requirements: 210 +))) 171 171 172 -* Your local operator has already distributed a NB-IoT Network there. 173 -* The local NB-IoT network used the band that N95S31B supports. 174 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 212 +* ((( 213 +Your local operator has already distributed a NB-IoT Network there. 214 +))) 215 +* ((( 216 +The local NB-IoT network used the band that N95S31B supports. 217 +))) 218 +* ((( 219 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 220 +))) 175 175 222 +((( 176 176 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 224 +))) 177 177 226 +((( 178 178 N95S31B supports different communication protocol such as : 228 +))) 179 179 180 180 ((( 181 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 182 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 183 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 184 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 231 +* ((( 232 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 233 +))) 234 +* ((( 235 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 236 +))) 237 +* ((( 238 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 239 +))) 240 +* ((( 241 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 242 +))) 185 185 244 +((( 186 186 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. 246 +))) 187 187 188 188 189 189 ))) ... ... @@ -194,6 +194,7 @@ 194 194 195 195 === 2.2.3 Insert SIM card === 196 196 257 + 197 197 ((( 198 198 Insert the NB-IoT Card get from your provider. 199 199 ))) ... ... @@ -209,14 +209,18 @@ 209 209 210 210 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 211 211 273 + 212 212 ((( 213 213 ((( 214 214 User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below. 277 + 278 + 215 215 ))) 216 216 ))) 217 217 218 218 [[image:1657351312545-300.png]] 219 219 284 + 220 220 **Connection:** 221 221 222 222 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -240,8 +240,9 @@ 240 240 241 241 [[image:1657329814315-101.png]] 242 242 308 + 243 243 ((( 244 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]310 +(% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]** 245 245 ))) 246 246 247 247 ... ... @@ -248,9 +248,10 @@ 248 248 249 249 === 2.2.5 Use CoAP protocol to uplink data === 250 250 251 -(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 252 252 318 +(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]** 253 253 320 + 254 254 ((( 255 255 **Use below commands:** 256 256 ))) ... ... @@ -353,50 +353,83 @@ 353 353 == 2.3 Uplink Payload == 354 354 355 355 356 -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. 423 +((( 424 +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. 425 +))) 357 357 358 358 428 +((( 359 359 For example: 430 +))) 360 360 361 - (% 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. 432 +((( 433 + (% 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. 434 +))) 362 362 363 363 437 +((( 364 364 The uplink payloads are composed in ASCII String. For example: 439 +))) 365 365 441 +((( 366 366 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 443 +))) 367 367 445 +((( 368 368 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 447 +))) 369 369 370 370 450 +((( 371 371 (% style="color:red" %)**NOTE:** 452 +))) 372 372 373 373 (% style="color:red" %) 374 -1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]]. 375 -1. By default, the device will send an uplink message every 1 hour. 455 +1. ((( 456 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 457 +))) 458 +1. ((( 459 +By default, the device will send an uplink message every 1 hour. 376 376 377 377 462 + 463 + 464 +))) 465 + 378 378 === 2.3.1 Payload Analyze === 379 379 380 380 N95S31B uplink payload includes in total 21 bytes 381 381 382 382 383 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width: 440px" %)471 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 384 384 |=(% style="width: 60px;" %)((( 385 385 **Size(bytes)** 386 -)))|=(% style="width: 60px;" %)**6**|=(% style="width:35px;" %)2|=(% style="width:35px;" %)**2**|=(% style="width:80px;" %)**1**|=(% style="width:80px;" %)1|=(% style="width:99px;" %)5|=(% style="width:77px;" %)**2**|=(% style="width: 60px;" %)**2**474 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2** 387 387 |(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)((( 476 +((( 388 388 Reserve/ Same as NBSN95 CFGMOD=1 478 +))) 389 389 480 +((( 390 390 No function here. 482 +))) 391 391 )))|(% style="width:77px" %)((( 484 +((( 392 392 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 486 +))) 393 393 488 +((( 394 394 By SHT31 490 +))) 395 395 )))|(% style="width:80px" %)((( 492 +((( 396 396 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 494 +))) 397 397 496 +((( 398 398 By SHT31 399 399 ))) 499 +))) 400 400 401 401 ((( 402 402 ((( ... ... @@ -455,15 +455,25 @@ 455 455 456 456 === 2.3.3 Version Info === 457 457 458 - 558 +((( 459 459 These bytes include the hardware and software version. 560 +))) 460 460 562 +((( 461 461 Higher byte: Specify hardware version: always 0x00 for N95S31B 564 +))) 462 462 566 +((( 463 463 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 568 +))) 464 464 570 +((( 571 + 572 +))) 465 465 574 +((( 466 466 For example: 0x00 6E: this device is N95S31B with firmware version 110. 576 +))) 467 467 468 468 ((( 469 469 ... ... @@ -534,7 +534,7 @@ 534 534 535 535 == 2.4 Downlink Payload == 536 536 537 -By default, DDS75 prints the downlink payload to console port.647 +By default, N95S31B prints the downlink payload to console port. 538 538 539 539 [[image:image-20220709100028-1.png]] 540 540 ... ... @@ -572,7 +572,7 @@ 572 572 ))) 573 573 574 574 ((( 575 -If payload = 0x04FF, it will reset the DDS75685 +If payload = 0x04FF, it will reset the N95S31B 576 576 ))) 577 577 578 578 ... ... @@ -752,8 +752,10 @@ 752 752 ((( 753 753 754 754 865 +((( 755 755 (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 756 756 ))) 868 +))) 757 757 758 758 759 759
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content