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