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
-
... ... @@ -17,35 +17,21 @@ 17 17 18 18 = 1. Introduction = 19 19 20 - 21 21 == 1.1 What is N95S31B NB-IoT Sensor Node == 22 22 23 23 ((( 24 24 25 25 26 -((( 27 27 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 -))) 29 29 30 -((( 31 31 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 -))) 33 33 34 -((( 35 35 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 36 -))) 37 37 38 -((( 39 39 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 -))) 41 41 42 -((( 43 - 44 -))) 45 45 46 -((( 47 47 ~* make sure you have NB-IoT coverage locally. 48 -))) 49 49 50 50 51 51 ))) ... ... @@ -56,7 +56,6 @@ 56 56 57 57 == 1.2 Features == 58 58 59 - 60 60 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 61 61 * Monitor Temperature & Humidity via SHT31 62 62 * AT Commands to change parameters ... ... @@ -68,9 +68,6 @@ 68 68 * Micro SIM card slot for NB-IoT SIM 69 69 * 8500mAh Battery for long term use 70 70 71 - 72 - 73 - 74 74 == 1.3 Specification == 75 75 76 76 ... ... @@ -79,8 +79,6 @@ 79 79 * Supply Voltage: 2.1v ~~ 3.6v 80 80 * Operating Temperature: -40 ~~ 85°C 81 81 82 - 83 - 84 84 (% style="color:#037691" %)**NB-IoT Spec:** 85 85 86 86 * - B1 @H-FDD: 2100MHz ... ... @@ -90,10 +90,9 @@ 90 90 * - B20 @H-FDD: 800MHz 91 91 * - B28 @H-FDD: 700MHz 92 92 93 - 94 - 95 95 (% style="color:#037691" %)**Battery:** 96 96 75 + 97 97 * Li/SOCI2 un-chargeable battery 98 98 * Capacity: 8500mAh 99 99 * Self Discharge: <1% / Year @ 25°C ... ... @@ -100,12 +100,8 @@ 100 100 * Max continuously current: 130mA 101 101 * Max boost current: 2A, 1 second 102 102 103 - 104 - 105 - 106 106 == 1.4 Applications == 107 107 108 - 109 109 * Smart Buildings & Home Automation 110 110 * Logistics and Supply Chain Management 111 111 * Smart Metering ... ... @@ -117,20 +117,15 @@ 117 117 118 118 119 119 95 +== 1.5 Pin Definitions == 120 120 121 -== 1.5 Pin Definitions & Switch == 122 - 123 - 124 124 N95S31B use the mother board from NBSN95 which as below. 125 125 126 - 127 127 [[image:image-20220709144723-1.png]] 128 128 129 129 130 - 131 131 === 1.5.1 Jumper JP2 === 132 132 133 - 134 134 Power on Device when put this jumper. 135 135 136 136 ... ... @@ -137,20 +137,14 @@ 137 137 138 138 === 1.5.2 BOOT MODE / SW1 === 139 139 140 - 141 -((( 142 142 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 -))) 144 144 145 -((( 146 146 2) Flash: work mode, device starts to work and send out console output for further debug 147 -))) 148 148 149 149 150 150 151 151 === 1.5.3 Reset Button === 152 152 153 - 154 154 Press to reboot the device. 155 155 156 156 ... ... @@ -157,18 +157,13 @@ 157 157 158 158 === 1.5.4 LED === 159 159 160 - 161 161 It will flash: 162 162 163 163 1. When boot the device in flash mode 164 164 1. Send an uplink packet 165 165 166 - 167 - 168 - 169 169 = 2. Use N95S31B to communicate with IoT Server = 170 170 171 - 172 172 == 2.1 How it works == 173 173 174 174 ... ... @@ -185,7 +185,7 @@ 185 185 186 186 ))) 187 187 188 -[[image:16575 20100595-569.png]]147 +[[image:1657350248151-650.png]] 189 189 190 190 ((( 191 191 ... ... @@ -201,49 +201,26 @@ 201 201 [[image:image-20220709150546-2.png]] 202 202 203 203 204 - 205 205 === 2.2.1 Test Requirement === 206 206 207 207 208 -((( 209 209 To use N95S31B in your city, make sure meet below requirements: 210 -))) 211 211 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 -))) 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. 221 221 222 -((( 223 223 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 224 -))) 225 225 226 -((( 227 227 N95S31B supports different communication protocol such as : 228 -))) 229 229 230 230 ((( 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 -))) 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(%%)) 243 243 244 -((( 245 245 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 -))) 247 247 248 248 249 249 ))) ... ... @@ -254,7 +254,6 @@ 254 254 255 255 === 2.2.3 Insert SIM card === 256 256 257 - 258 258 ((( 259 259 Insert the NB-IoT Card get from your provider. 260 260 ))) ... ... @@ -270,18 +270,14 @@ 270 270 271 271 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 272 272 273 - 274 274 ((( 275 275 ((( 276 276 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 - 279 279 ))) 280 280 ))) 281 281 282 282 [[image:1657351312545-300.png]] 283 283 284 - 285 285 **Connection:** 286 286 287 287 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -305,9 +305,8 @@ 305 305 306 306 [[image:1657329814315-101.png]] 307 307 308 - 309 309 ((( 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]]**240 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] 311 311 ))) 312 312 313 313 ... ... @@ -314,10 +314,9 @@ 314 314 315 315 === 2.2.5 Use CoAP protocol to uplink data === 316 316 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/]] 317 317 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/]]** 319 319 320 - 321 321 ((( 322 322 **Use below commands:** 323 323 ))) ... ... @@ -420,48 +420,29 @@ 420 420 == 2.3 Uplink Payload == 421 421 422 422 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 -))) 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. 426 426 427 427 428 -((( 429 429 For example: 430 -))) 431 431 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 -))) 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. 435 435 436 436 437 -((( 438 438 The uplink payloads are composed in ASCII String. For example: 439 -))) 440 440 441 -((( 442 442 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 443 -))) 444 444 445 -((( 446 446 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 447 -))) 448 448 449 449 450 -((( 451 451 (% style="color:red" %)**NOTE:** 452 -))) 453 453 454 454 (% style="color:red" %) 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. 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. 460 460 461 461 462 462 463 - 464 -))) 465 465 466 466 === 2.3.1 Payload Analyze === 467 467 ... ... @@ -555,25 +555,15 @@ 555 555 556 556 === 2.3.3 Version Info === 557 557 558 - (((468 + 559 559 These bytes include the hardware and software version. 560 -))) 561 561 562 -((( 563 563 Higher byte: Specify hardware version: always 0x00 for N95S31B 564 -))) 565 565 566 -((( 567 567 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 568 -))) 569 569 570 -((( 571 - 572 -))) 573 573 574 -((( 575 575 For example: 0x00 6E: this device is N95S31B with firmware version 110. 576 -))) 577 577 578 578 ((( 579 579 ... ... @@ -644,7 +644,7 @@ 644 644 645 645 == 2.4 Downlink Payload == 646 646 647 -By default, 95S31Bprints the downlink payload to console port.547 +By default, NDDS75 prints the downlink payload to console port. 648 648 649 649 [[image:image-20220709100028-1.png]] 650 650 ... ... @@ -682,7 +682,7 @@ 682 682 ))) 683 683 684 684 ((( 685 -If payload = 0x04FF, it will reset the 95S31B585 +If payload = 0x04FF, it will reset the NDDS75 686 686 ))) 687 687 688 688 ... ... @@ -862,10 +862,8 @@ 862 862 ((( 863 863 864 864 865 -((( 866 866 (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 867 867 ))) 868 -))) 869 869 870 870 871 871
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content