Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 3 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. David1 +XWiki.Xiaoling - 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 ... ... @@ -70,7 +70,6 @@ 70 70 71 71 72 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 77 + 97 97 * Li/SOCI2 un-chargeable battery 98 98 * Capacity: 8500mAh 99 99 * Self Discharge: <1% / Year @ 25°C ... ... @@ -102,10 +102,8 @@ 102 102 103 103 104 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 99 +== 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]]151 +[[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 -))) 172 +* Your local operator has already distributed a NB-IoT Network there. 173 +* The local NB-IoT network used the band that N95S31B supports. 174 +* 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 -))) 181 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 182 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 183 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 184 +* 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]]**244 +(% 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 251 +(% 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 ))) ... ... @@ -356,8 +356,6 @@ 356 356 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 357 357 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 358 358 359 - 360 - 361 361 [[image:1657352391268-297.png]] 362 362 363 363 ... ... @@ -367,7 +367,6 @@ 367 367 368 368 === 2.2.7 Use MQTT protocol to uplink data === 369 369 370 - 371 371 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 372 372 373 373 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink ... ... @@ -378,14 +378,11 @@ 378 378 * (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 379 379 * (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 380 380 381 - 382 - 383 383 [[image:1657352634421-276.png]] 384 384 385 385 386 386 [[image:1657352645687-385.png]] 387 387 388 - 389 389 ((( 390 390 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. 391 391 ))) ... ... @@ -399,14 +399,11 @@ 399 399 400 400 === 2.2.8 Use TCP protocol to uplink data === 401 401 402 - 403 403 This feature is supported since firmware version v110 404 404 405 405 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 406 406 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 407 407 408 - 409 - 410 410 [[image:1657352898400-901.png]] 411 411 412 412 ... ... @@ -416,7 +416,6 @@ 416 416 417 417 === 2.2.9 Change Update Interval === 418 418 419 - 420 420 User can use below command to change the (% style="color:green" %)**uplink interval**. 421 421 422 422 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -430,88 +430,52 @@ 430 430 == 2.3 Uplink Payload == 431 431 432 432 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 -))) 356 +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. 436 436 437 437 438 -((( 439 439 For example: 440 -))) 441 441 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 -))) 361 + (% 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. 445 445 446 446 447 -((( 448 448 The uplink payloads are composed in ASCII String. For example: 449 -))) 450 450 451 -((( 452 452 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 453 -))) 454 454 455 -((( 456 456 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 457 -))) 458 458 459 459 460 -((( 461 461 (% style="color:red" %)**NOTE:** 462 -))) 463 463 464 464 (% style="color:red" %) 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.** 374 +1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 375 +1. By default, the device will send an uplink message every 1 hour. 470 470 471 471 472 - 473 - 474 -))) 475 - 476 476 === 2.3.1 Payload Analyze === 477 477 478 - 479 479 N95S31B uplink payload includes in total 21 bytes 480 480 481 481 482 482 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 483 -|=(% style="width: 60px;" %)(((384 +|=(% style="width: 50px;" %)((( 484 484 **Size(bytes)** 485 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width:55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width:60px;" %)**2**386 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 60px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 50px;" %)**2** 486 486 |(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)((( 487 -((( 488 488 Reserve/ Same as NBSN95 CFGMOD=1 489 -))) 490 490 491 -((( 492 492 No function here. 493 -))) 494 494 )))|(% style="width:77px" %)((( 495 -((( 496 496 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 497 -))) 498 498 499 -((( 500 500 By SHT31 501 -))) 502 502 )))|(% style="width:80px" %)((( 503 -((( 504 504 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 505 -))) 506 506 507 -((( 508 508 By SHT31 509 509 ))) 510 -))) 511 511 512 512 ((( 513 - 514 - 515 515 ((( 516 516 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 517 517 ))) ... ... @@ -544,7 +544,6 @@ 544 544 545 545 === 2.3.2 Device ID === 546 546 547 - 548 548 ((( 549 549 By default, the Device ID equal to the last 6 bytes of IMEI. 550 550 ))) ... ... @@ -570,25 +570,14 @@ 570 570 === 2.3.3 Version Info === 571 571 572 572 573 -((( 574 574 These bytes include the hardware and software version. 575 -))) 576 576 577 -((( 578 578 Higher byte: Specify hardware version: always 0x00 for N95S31B 579 -))) 580 580 581 -((( 582 582 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 583 -))) 584 584 585 -((( 586 - 587 -))) 588 588 589 -((( 590 590 For example: 0x00 6E: this device is N95S31B with firmware version 110. 591 -))) 592 592 593 593 ((( 594 594 ... ... @@ -597,7 +597,6 @@ 597 597 598 598 === 2.3.4 Battery Info === 599 599 600 - 601 601 ((( 602 602 Ex1: 0x0B45 = 2885mV 603 603 ))) ... ... @@ -610,7 +610,6 @@ 610 610 611 611 === 2.3.5 Signal Strength === 612 612 613 - 614 614 ((( 615 615 NB-IoT Network signal Strength. 616 616 ))) ... ... @@ -643,7 +643,6 @@ 643 643 644 644 === 2.3.6 Temperature & Humidity === 645 645 646 - 647 647 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 648 648 649 649 [[image:image-20220709161741-3.png]] ... ... @@ -662,9 +662,8 @@ 662 662 663 663 == 2.4 Downlink Payload == 664 664 537 +By default, NDDS75 prints the downlink payload to console port. 665 665 666 -By default, N95S31B prints the downlink payload to console port. 667 - 668 668 [[image:image-20220709100028-1.png]] 669 669 670 670 ... ... @@ -701,7 +701,7 @@ 701 701 ))) 702 702 703 703 ((( 704 -If payload = 0x04FF, it will reset the 95S31B575 +If payload = 0x04FF, it will reset the NDDS75 705 705 ))) 706 706 707 707 ... ... @@ -715,7 +715,6 @@ 715 715 716 716 == 2.5 Battery Analysis == 717 717 718 - 719 719 === 2.5.1 Battery Type === 720 720 721 721 ... ... @@ -743,9 +743,8 @@ 743 743 744 744 === 2.5.2 Power consumption Analyze === 745 745 746 - 747 747 ((( 748 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dro pbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]617 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project. 749 749 ))) 750 750 751 751 ((( ... ... @@ -755,7 +755,6 @@ 755 755 756 756 === 2.5.3 Battery Note === 757 757 758 - 759 759 ((( 760 760 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. 761 761 ))) ... ... @@ -778,7 +778,6 @@ 778 778 779 779 = 3. Access NB-IoT Module = 780 780 781 - 782 782 ((( 783 783 Users can directly access the AT command set of the NB-IoT module. 784 784 ))) ... ... @@ -785,8 +785,6 @@ 785 785 786 786 ((( 787 787 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 - 790 790 ))) 791 791 792 792 [[image:1657333200519-600.png]] ... ... @@ -795,13 +795,11 @@ 795 795 796 796 = 4. Using the AT Commands = 797 797 798 - 799 799 == 4.1 Access AT Commands == 800 800 665 +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/]] 801 801 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]] 803 803 804 - 805 805 AT+<CMD>? : Help on <CMD> 806 806 807 807 AT+<CMD> : Run <CMD> ... ... @@ -875,7 +875,6 @@ 875 875 876 876 = 5. FAQ = 877 877 878 - 879 879 == 5.1 How to Upgrade Firmware == 880 880 881 881 ... ... @@ -890,16 +890,13 @@ 890 890 ((( 891 891 892 892 893 -((( 894 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 755 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 895 895 ))) 896 -))) 897 897 898 898 899 899 900 900 = 6. Trouble Shooting = 901 901 902 - 903 903 == 6.1 Connection problem when uploading firmware == 904 904 905 905 ... ... @@ -915,7 +915,6 @@ 915 915 916 916 == 6.2 AT Command input doesn't work == 917 917 918 - 919 919 ((( 920 920 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. 921 921 ... ... @@ -965,9 +965,5 @@ 965 965 966 966 = 9. Support = 967 967 968 - 969 969 * 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. 970 970 * 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,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- image-20220908154949-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -58.5 KB - Content
- image-20220908163102-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -29.7 KB - Content