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 ... ... @@ -53,6 +53,9 @@ 53 53 * Micro SIM card slot for NB-IoT SIM 54 54 * 8500mAh Battery for long term use 55 55 71 + 72 + 73 + 56 56 == 1.3 Specification == 57 57 58 58 ... ... @@ -61,6 +61,8 @@ 61 61 * Supply Voltage: 2.1v ~~ 3.6v 62 62 * Operating Temperature: -40 ~~ 85°C 63 63 82 + 83 + 64 64 (% style="color:#037691" %)**NB-IoT Spec:** 65 65 66 66 * - B1 @H-FDD: 2100MHz ... ... @@ -70,9 +70,10 @@ 70 70 * - B20 @H-FDD: 800MHz 71 71 * - B28 @H-FDD: 700MHz 72 72 73 -(% style="color:#037691" %)**Battery:** 74 74 75 75 95 +(% style="color:#037691" %)**Battery:** 96 + 76 76 * Li/SOCI2 un-chargeable battery 77 77 * Capacity: 8500mAh 78 78 * Self Discharge: <1% / Year @ 25°C ... ... @@ -79,8 +79,12 @@ 79 79 * Max continuously current: 130mA 80 80 * Max boost current: 2A, 1 second 81 81 103 + 104 + 105 + 82 82 == 1.4 Applications == 83 83 108 + 84 84 * Smart Buildings & Home Automation 85 85 * Logistics and Supply Chain Management 86 86 * Smart Metering ... ... @@ -92,15 +92,20 @@ 92 92 93 93 94 94 95 -== 1.5 Pin Definitions == 96 96 121 +== 1.5 Pin Definitions & Switch == 122 + 123 + 97 97 N95S31B use the mother board from NBSN95 which as below. 98 98 126 + 99 99 [[image:image-20220709144723-1.png]] 100 100 101 101 130 + 102 102 === 1.5.1 Jumper JP2 === 103 103 133 + 104 104 Power on Device when put this jumper. 105 105 106 106 ... ... @@ -107,14 +107,20 @@ 107 107 108 108 === 1.5.2 BOOT MODE / SW1 === 109 109 140 + 141 +((( 110 110 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 +))) 111 111 145 +((( 112 112 2) Flash: work mode, device starts to work and send out console output for further debug 147 +))) 113 113 114 114 115 115 116 116 === 1.5.3 Reset Button === 117 117 153 + 118 118 Press to reboot the device. 119 119 120 120 ... ... @@ -121,13 +121,18 @@ 121 121 122 122 === 1.5.4 LED === 123 123 160 + 124 124 It will flash: 125 125 126 126 1. When boot the device in flash mode 127 127 1. Send an uplink packet 128 128 166 + 167 + 168 + 129 129 = 2. Use N95S31B to communicate with IoT Server = 130 130 171 + 131 131 == 2.1 How it works == 132 132 133 133 ... ... @@ -144,7 +144,7 @@ 144 144 145 145 ))) 146 146 147 -[[image:1657 350248151-650.png]]188 +[[image:1657520100595-569.png]] 148 148 149 149 ((( 150 150 ... ... @@ -160,26 +160,49 @@ 160 160 [[image:image-20220709150546-2.png]] 161 161 162 162 204 + 163 163 === 2.2.1 Test Requirement === 164 164 165 165 208 +((( 166 166 To use N95S31B in your city, make sure meet below requirements: 210 +))) 167 167 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. 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 +))) 171 171 222 +((( 172 172 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 224 +))) 173 173 226 +((( 174 174 N95S31B supports different communication protocol such as : 228 +))) 175 175 176 176 ((( 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(%%)) 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 +))) 181 181 244 +((( 182 182 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 +))) 183 183 184 184 185 185 ))) ... ... @@ -190,6 +190,7 @@ 190 190 191 191 === 2.2.3 Insert SIM card === 192 192 257 + 193 193 ((( 194 194 Insert the NB-IoT Card get from your provider. 195 195 ))) ... ... @@ -205,14 +205,18 @@ 205 205 206 206 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 207 207 273 + 208 208 ((( 209 209 ((( 210 210 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 + 211 211 ))) 212 212 ))) 213 213 214 214 [[image:1657351312545-300.png]] 215 215 284 + 216 216 **Connection:** 217 217 218 218 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -236,8 +236,9 @@ 236 236 237 237 [[image:1657329814315-101.png]] 238 238 308 + 239 239 ((( 240 -(% 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]]** 241 241 ))) 242 242 243 243 ... ... @@ -244,9 +244,10 @@ 244 244 245 245 === 2.2.5 Use CoAP protocol to uplink data === 246 246 247 -(% 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/]] 248 248 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/]]** 249 249 320 + 250 250 ((( 251 251 **Use below commands:** 252 252 ))) ... ... @@ -349,29 +349,48 @@ 349 349 == 2.3 Uplink Payload == 350 350 351 351 352 -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 +))) 353 353 354 354 428 +((( 355 355 For example: 430 +))) 356 356 357 - (% 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 +))) 358 358 359 359 437 +((( 360 360 The uplink payloads are composed in ASCII String. For example: 439 +))) 361 361 441 +((( 362 362 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 443 +))) 363 363 445 +((( 364 364 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 447 +))) 365 365 366 366 450 +((( 367 367 (% style="color:red" %)**NOTE:** 452 +))) 368 368 369 369 (% style="color:red" %) 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. 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. 372 372 373 373 374 374 463 + 464 +))) 375 375 376 376 === 2.3.1 Payload Analyze === 377 377 ... ... @@ -465,15 +465,25 @@ 465 465 466 466 === 2.3.3 Version Info === 467 467 468 - 558 +((( 469 469 These bytes include the hardware and software version. 560 +))) 470 470 562 +((( 471 471 Higher byte: Specify hardware version: always 0x00 for N95S31B 564 +))) 472 472 566 +((( 473 473 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 568 +))) 474 474 570 +((( 571 + 572 +))) 475 475 574 +((( 476 476 For example: 0x00 6E: this device is N95S31B with firmware version 110. 576 +))) 477 477 478 478 ((( 479 479 ... ... @@ -544,7 +544,7 @@ 544 544 545 545 == 2.4 Downlink Payload == 546 546 547 -By default, DDS75 prints the downlink payload to console port.647 +By default, N95S31B prints the downlink payload to console port. 548 548 549 549 [[image:image-20220709100028-1.png]] 550 550 ... ... @@ -582,7 +582,7 @@ 582 582 ))) 583 583 584 584 ((( 585 -If payload = 0x04FF, it will reset the DDS75685 +If payload = 0x04FF, it will reset the N95S31B 586 586 ))) 587 587 588 588 ... ... @@ -762,8 +762,10 @@ 762 762 ((( 763 763 764 764 865 +((( 765 765 (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 766 766 ))) 868 +))) 767 767 768 768 769 769
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content