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