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 ))) ... ... @@ -285,6 +285,8 @@ 285 285 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 286 286 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 287 287 359 + 360 + 288 288 [[image:1657352391268-297.png]] 289 289 290 290 ... ... @@ -294,6 +294,7 @@ 294 294 295 295 === 2.2.7 Use MQTT protocol to uplink data === 296 296 370 + 297 297 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 298 298 299 299 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink ... ... @@ -304,11 +304,14 @@ 304 304 * (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 305 305 * (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 306 306 381 + 382 + 307 307 [[image:1657352634421-276.png]] 308 308 309 309 310 310 [[image:1657352645687-385.png]] 311 311 388 + 312 312 ((( 313 313 To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period. 314 314 ))) ... ... @@ -322,11 +322,14 @@ 322 322 323 323 === 2.2.8 Use TCP protocol to uplink data === 324 324 402 + 325 325 This feature is supported since firmware version v110 326 326 327 327 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 328 328 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 329 329 408 + 409 + 330 330 [[image:1657352898400-901.png]] 331 331 332 332 ... ... @@ -336,6 +336,7 @@ 336 336 337 337 === 2.2.9 Change Update Interval === 338 338 419 + 339 339 User can use below command to change the (% style="color:green" %)**uplink interval**. 340 340 341 341 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -349,32 +349,52 @@ 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. 433 +((( 434 +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. 435 +))) 353 353 354 354 438 +((( 355 355 For example: 440 +))) 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. 442 +((( 443 + (% 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. 444 +))) 358 358 359 359 447 +((( 360 360 The uplink payloads are composed in ASCII String. For example: 449 +))) 361 361 451 +((( 362 362 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 453 +))) 363 363 455 +((( 364 364 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 457 +))) 365 365 366 366 460 +((( 367 367 (% style="color:red" %)**NOTE:** 462 +))) 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. 465 +1. ((( 466 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 467 +))) 468 +1. ((( 469 +**By default, the device will send an uplink message every 1 hour.** 372 372 373 373 374 374 473 + 474 +))) 375 375 376 376 === 2.3.1 Payload Analyze === 377 377 478 + 378 378 N95S31B uplink payload includes in total 21 bytes 379 379 380 380 ... ... @@ -409,6 +409,8 @@ 409 409 ))) 410 410 411 411 ((( 513 + 514 + 412 412 ((( 413 413 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 414 414 ))) ... ... @@ -441,6 +441,7 @@ 441 441 442 442 === 2.3.2 Device ID === 443 443 547 + 444 444 ((( 445 445 By default, the Device ID equal to the last 6 bytes of IMEI. 446 446 ))) ... ... @@ -466,14 +466,25 @@ 466 466 === 2.3.3 Version Info === 467 467 468 468 573 +((( 469 469 These bytes include the hardware and software version. 575 +))) 470 470 577 +((( 471 471 Higher byte: Specify hardware version: always 0x00 for N95S31B 579 +))) 472 472 581 +((( 473 473 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 583 +))) 474 474 585 +((( 586 + 587 +))) 475 475 589 +((( 476 476 For example: 0x00 6E: this device is N95S31B with firmware version 110. 591 +))) 477 477 478 478 ((( 479 479 ... ... @@ -482,6 +482,7 @@ 482 482 483 483 === 2.3.4 Battery Info === 484 484 600 + 485 485 ((( 486 486 Ex1: 0x0B45 = 2885mV 487 487 ))) ... ... @@ -494,6 +494,7 @@ 494 494 495 495 === 2.3.5 Signal Strength === 496 496 613 + 497 497 ((( 498 498 NB-IoT Network signal Strength. 499 499 ))) ... ... @@ -526,6 +526,7 @@ 526 526 527 527 === 2.3.6 Temperature & Humidity === 528 528 646 + 529 529 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 530 530 531 531 [[image:image-20220709161741-3.png]] ... ... @@ -544,8 +544,9 @@ 544 544 545 545 == 2.4 Downlink Payload == 546 546 547 -By default, NDDS75 prints the downlink payload to console port. 548 548 666 +By default, N95S31B prints the downlink payload to console port. 667 + 549 549 [[image:image-20220709100028-1.png]] 550 550 551 551 ... ... @@ -582,7 +582,7 @@ 582 582 ))) 583 583 584 584 ((( 585 -If payload = 0x04FF, it will reset the DDS75704 +If payload = 0x04FF, it will reset the N95S31B 586 586 ))) 587 587 588 588 ... ... @@ -596,6 +596,7 @@ 596 596 597 597 == 2.5 Battery Analysis == 598 598 718 + 599 599 === 2.5.1 Battery Type === 600 600 601 601 ... ... @@ -623,8 +623,9 @@ 623 623 624 624 === 2.5.2 Power consumption Analyze === 625 625 746 + 626 626 ((( 627 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]748 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project. 628 628 ))) 629 629 630 630 ((( ... ... @@ -634,6 +634,7 @@ 634 634 635 635 === 2.5.3 Battery Note === 636 636 758 + 637 637 ((( 638 638 The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to uplink data, then the battery life may be decreased. 639 639 ))) ... ... @@ -656,6 +656,7 @@ 656 656 657 657 = 3. Access NB-IoT Module = 658 658 781 + 659 659 ((( 660 660 Users can directly access the AT command set of the NB-IoT module. 661 661 ))) ... ... @@ -662,6 +662,8 @@ 662 662 663 663 ((( 664 664 The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 788 + 789 + 665 665 ))) 666 666 667 667 [[image:1657333200519-600.png]] ... ... @@ -670,11 +670,13 @@ 670 670 671 671 = 4. Using the AT Commands = 672 672 798 + 673 673 == 4.1 Access AT Commands == 674 674 675 -See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]] 676 676 802 +See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]] 677 677 804 + 678 678 AT+<CMD>? : Help on <CMD> 679 679 680 680 AT+<CMD> : Run <CMD> ... ... @@ -748,6 +748,7 @@ 748 748 749 749 = 5. FAQ = 750 750 878 + 751 751 == 5.1 How to Upgrade Firmware == 752 752 753 753 ... ... @@ -762,13 +762,16 @@ 762 762 ((( 763 763 764 764 765 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 893 +((( 894 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 766 766 ))) 896 +))) 767 767 768 768 769 769 770 770 = 6. Trouble Shooting = 771 771 902 + 772 772 == 6.1 Connection problem when uploading firmware == 773 773 774 774 ... ... @@ -784,6 +784,7 @@ 784 784 785 785 == 6.2 AT Command input doesn't work == 786 786 918 + 787 787 ((( 788 788 In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string. 789 789 ... ... @@ -833,5 +833,9 @@ 833 833 834 834 = 9. Support = 835 835 968 + 836 836 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 837 837 * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]] 971 + 972 + 973 +
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content