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,6 +17,7 @@ 17 17 18 18 = 1. Introduction = 19 19 20 + 20 20 == 1.1 What is N95S31B NB-IoT Sensor Node == 21 21 22 22 ((( ... ... @@ -55,6 +55,7 @@ 55 55 56 56 == 1.2 Features == 57 57 59 + 58 58 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 59 59 * Monitor Temperature & Humidity via SHT31 60 60 * AT Commands to change parameters ... ... @@ -66,6 +66,9 @@ 66 66 * Micro SIM card slot for NB-IoT SIM 67 67 * 8500mAh Battery for long term use 68 68 71 + 72 + 73 + 69 69 == 1.3 Specification == 70 70 71 71 ... ... @@ -74,6 +74,8 @@ 74 74 * Supply Voltage: 2.1v ~~ 3.6v 75 75 * Operating Temperature: -40 ~~ 85°C 76 76 82 + 83 + 77 77 (% style="color:#037691" %)**NB-IoT Spec:** 78 78 79 79 * - B1 @H-FDD: 2100MHz ... ... @@ -83,9 +83,10 @@ 83 83 * - B20 @H-FDD: 800MHz 84 84 * - B28 @H-FDD: 700MHz 85 85 86 -(% style="color:#037691" %)**Battery:** 87 87 88 88 95 +(% style="color:#037691" %)**Battery:** 96 + 89 89 * Li/SOCI2 un-chargeable battery 90 90 * Capacity: 8500mAh 91 91 * Self Discharge: <1% / Year @ 25°C ... ... @@ -92,8 +92,12 @@ 92 92 * Max continuously current: 130mA 93 93 * Max boost current: 2A, 1 second 94 94 103 + 104 + 105 + 95 95 == 1.4 Applications == 96 96 108 + 97 97 * Smart Buildings & Home Automation 98 98 * Logistics and Supply Chain Management 99 99 * Smart Metering ... ... @@ -105,15 +105,20 @@ 105 105 106 106 107 107 108 -== 1.5 Pin Definitions == 109 109 121 +== 1.5 Pin Definitions & Switch == 122 + 123 + 110 110 N95S31B use the mother board from NBSN95 which as below. 111 111 126 + 112 112 [[image:image-20220709144723-1.png]] 113 113 114 114 130 + 115 115 === 1.5.1 Jumper JP2 === 116 116 133 + 117 117 Power on Device when put this jumper. 118 118 119 119 ... ... @@ -120,14 +120,20 @@ 120 120 121 121 === 1.5.2 BOOT MODE / SW1 === 122 122 140 + 141 +((( 123 123 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 +))) 124 124 145 +((( 125 125 2) Flash: work mode, device starts to work and send out console output for further debug 147 +))) 126 126 127 127 128 128 129 129 === 1.5.3 Reset Button === 130 130 153 + 131 131 Press to reboot the device. 132 132 133 133 ... ... @@ -134,13 +134,18 @@ 134 134 135 135 === 1.5.4 LED === 136 136 160 + 137 137 It will flash: 138 138 139 139 1. When boot the device in flash mode 140 140 1. Send an uplink packet 141 141 166 + 167 + 168 + 142 142 = 2. Use N95S31B to communicate with IoT Server = 143 143 171 + 144 144 == 2.1 How it works == 145 145 146 146 ... ... @@ -157,7 +157,7 @@ 157 157 158 158 ))) 159 159 160 -[[image:1657 350248151-650.png]]188 +[[image:1657520100595-569.png]] 161 161 162 162 ((( 163 163 ... ... @@ -173,26 +173,49 @@ 173 173 [[image:image-20220709150546-2.png]] 174 174 175 175 204 + 176 176 === 2.2.1 Test Requirement === 177 177 178 178 208 +((( 179 179 To use N95S31B in your city, make sure meet below requirements: 210 +))) 180 180 181 -* Your local operator has already distributed a NB-IoT Network there. 182 -* The local NB-IoT network used the band that N95S31B supports. 183 -* 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 +))) 184 184 222 +((( 185 185 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 224 +))) 186 186 226 +((( 187 187 N95S31B supports different communication protocol such as : 228 +))) 188 188 189 189 ((( 190 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 191 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 192 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 193 -* 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 +))) 194 194 244 +((( 195 195 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 +))) 196 196 197 197 198 198 ))) ... ... @@ -203,6 +203,7 @@ 203 203 204 204 === 2.2.3 Insert SIM card === 205 205 257 + 206 206 ((( 207 207 Insert the NB-IoT Card get from your provider. 208 208 ))) ... ... @@ -218,14 +218,18 @@ 218 218 219 219 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 220 220 273 + 221 221 ((( 222 222 ((( 223 223 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 + 224 224 ))) 225 225 ))) 226 226 227 227 [[image:1657351312545-300.png]] 228 228 284 + 229 229 **Connection:** 230 230 231 231 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -249,8 +249,9 @@ 249 249 250 250 [[image:1657329814315-101.png]] 251 251 308 + 252 252 ((( 253 -(% 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]]** 254 254 ))) 255 255 256 256 ... ... @@ -257,9 +257,10 @@ 257 257 258 258 === 2.2.5 Use CoAP protocol to uplink data === 259 259 260 -(% 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/]] 261 261 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/]]** 262 262 320 + 263 263 ((( 264 264 **Use below commands:** 265 265 ))) ... ... @@ -362,28 +362,49 @@ 362 362 == 2.3 Uplink Payload == 363 363 364 364 365 -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 +))) 366 366 367 367 428 +((( 368 368 For example: 430 +))) 369 369 370 - (% 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 +))) 371 371 372 372 437 +((( 373 373 The uplink payloads are composed in ASCII String. For example: 439 +))) 374 374 441 +((( 375 375 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 443 +))) 376 376 445 +((( 377 377 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 447 +))) 378 378 379 379 450 +((( 380 380 (% style="color:red" %)**NOTE:** 452 +))) 381 381 382 382 (% style="color:red" %) 383 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 384 -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. 385 385 386 386 462 + 463 + 464 +))) 465 + 387 387 === 2.3.1 Payload Analyze === 388 388 389 389 N95S31B uplink payload includes in total 21 bytes ... ... @@ -476,15 +476,25 @@ 476 476 477 477 === 2.3.3 Version Info === 478 478 479 - 558 +((( 480 480 These bytes include the hardware and software version. 560 +))) 481 481 562 +((( 482 482 Higher byte: Specify hardware version: always 0x00 for N95S31B 564 +))) 483 483 566 +((( 484 484 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 568 +))) 485 485 570 +((( 571 + 572 +))) 486 486 574 +((( 487 487 For example: 0x00 6E: this device is N95S31B with firmware version 110. 576 +))) 488 488 489 489 ((( 490 490 ... ... @@ -555,7 +555,7 @@ 555 555 556 556 == 2.4 Downlink Payload == 557 557 558 -By default, DDS75 prints the downlink payload to console port.647 +By default, N95S31B prints the downlink payload to console port. 559 559 560 560 [[image:image-20220709100028-1.png]] 561 561 ... ... @@ -593,7 +593,7 @@ 593 593 ))) 594 594 595 595 ((( 596 -If payload = 0x04FF, it will reset the DDS75685 +If payload = 0x04FF, it will reset the N95S31B 597 597 ))) 598 598 599 599 ... ... @@ -773,8 +773,10 @@ 773 773 ((( 774 774 775 775 865 +((( 776 776 (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 777 777 ))) 868 +))) 778 778 779 779 780 780
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content