Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
<
edited by Mengting Qiu
on 2024/04/02 16:44
on 2024/04/02 16:44
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -N95S31B --NB-IoT Temperature & Humidity Sensor User Manual1 +N95S31B NB-IoT Temperature & Humidity Sensor User Manual - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ting1 +XWiki.Xiaoling - Content
-
... ... @@ -17,8 +17,11 @@ 17 17 18 18 = 1. Introduction = 19 19 20 + 20 20 == 1.1 What is N95S31B NB-IoT Sensor Node == 21 21 23 +((( 24 + 22 22 23 23 ((( 24 24 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*. ... ... @@ -37,13 +37,20 @@ 37 37 ))) 38 38 39 39 ((( 43 + 44 +))) 45 + 46 +((( 40 40 ~* make sure you have NB-IoT coverage locally. 41 41 ))) 42 42 50 + 51 +))) 43 43 44 44 [[image:1657348284168-431.png]] 45 45 46 46 56 + 47 47 == 1.2 Features == 48 48 49 49 ... ... @@ -68,12 +68,12 @@ 68 68 69 69 (% style="color:#037691" %)**NB-IoT Spec:** 70 70 71 -* B1 @H-FDD: 2100MHz 72 -* B3 @H-FDD: 1800MHz 73 -* B8 @H-FDD: 900MHz 74 -* B5 @H-FDD: 850MHz 75 -* B20 @H-FDD: 800MHz 76 -* B28 @H-FDD: 700MHz 81 +* - B1 @H-FDD: 2100MHz 82 +* - B3 @H-FDD: 1800MHz 83 +* - B8 @H-FDD: 900MHz 84 +* - B5 @H-FDD: 850MHz 85 +* - B20 @H-FDD: 800MHz 86 +* - B28 @H-FDD: 700MHz 77 77 78 78 (% style="color:#037691" %)**Battery:** 79 79 ... ... @@ -97,6 +97,7 @@ 97 97 98 98 99 99 110 + 100 100 == 1.5 Pin Definitions & Switch == 101 101 102 102 ... ... @@ -106,6 +106,7 @@ 106 106 [[image:image-20220709144723-1.png]] 107 107 108 108 120 + 109 109 === 1.5.1 Jumper JP2 === 110 110 111 111 ... ... @@ -112,6 +112,7 @@ 112 112 Power on Device when put this jumper. 113 113 114 114 127 + 115 115 === 1.5.2 BOOT MODE / SW1 === 116 116 117 117 ... ... @@ -124,6 +124,7 @@ 124 124 ))) 125 125 126 126 140 + 127 127 === 1.5.3 Reset Button === 128 128 129 129 ... ... @@ -130,6 +130,7 @@ 130 130 Press to reboot the device. 131 131 132 132 147 + 133 133 === 1.5.4 LED === 134 134 135 135 ... ... @@ -140,8 +140,10 @@ 140 140 2. Send an uplink packet 141 141 142 142 158 + 143 143 = 2. Use N95S31B to communicate with IoT Server = 144 144 161 + 145 145 == 2.1 How it works == 146 146 147 147 ... ... @@ -164,8 +164,10 @@ 164 164 165 165 ))) 166 166 184 + 167 167 == 2.2 Configure the N95S31B == 168 168 187 + 169 169 === 2.2.1 Power On N95S31B === 170 170 171 171 ... ... @@ -172,9 +172,10 @@ 172 172 [[image:image-20220709150546-2.png]] 173 173 174 174 175 -=== 2.2.2 Test Requirement === 176 176 195 +=== 2.2.1 Test Requirement === 177 177 197 + 178 178 ((( 179 179 To use N95S31B in your city, make sure meet below requirements: 180 180 ))) ... ... @@ -221,6 +221,7 @@ 221 221 [[image:1657350625843-586.png]] 222 222 223 223 244 + 224 224 === 2.2.3 Insert SIM card === 225 225 226 226 ... ... @@ -236,6 +236,7 @@ 236 236 [[image:1657351240556-536.png]] 237 237 238 238 260 + 239 239 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 240 240 241 241 ... ... @@ -279,6 +279,7 @@ 279 279 ))) 280 280 281 281 304 + 282 282 === 2.2.5 Use CoAP protocol to uplink data === 283 283 284 284 ... ... @@ -315,11 +315,13 @@ 315 315 [[image:1657352185396-303.png]] 316 316 317 317 341 + 318 318 === 2.2.6 Use UDP protocol to uplink data(Default protocol) === 319 319 320 320 321 321 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 322 322 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 347 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 323 323 324 324 [[image:1657352391268-297.png]] 325 325 ... ... @@ -327,6 +327,7 @@ 327 327 [[image:1657352403317-397.png]] 328 328 329 329 355 + 330 330 === 2.2.7 Use MQTT protocol to uplink data === 331 331 332 332 ... ... @@ -350,11 +350,13 @@ 350 350 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. 351 351 ))) 352 352 379 + 353 353 ((( 354 354 MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 355 355 ))) 356 356 357 357 385 + 358 358 === 2.2.8 Use TCP protocol to uplink data === 359 359 360 360 ... ... @@ -369,6 +369,7 @@ 369 369 [[image:1657352914475-252.png]] 370 370 371 371 400 + 372 372 === 2.2.9 Change Update Interval === 373 373 374 374 ... ... @@ -389,6 +389,7 @@ 389 389 ))) 390 390 391 391 421 + 392 392 == 2.3 Uplink Payload == 393 393 394 394 ... ... @@ -402,7 +402,7 @@ 402 402 ))) 403 403 404 404 ((( 405 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/ 435 + (% 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. 406 406 ))) 407 407 408 408 ... ... @@ -431,19 +431,22 @@ 431 431 **By default, the device will send an uplink message every 1 hour.** 432 432 433 433 464 + 434 434 435 435 ))) 436 436 437 437 === 2.3.1 Payload Analyze === 438 438 470 + 439 439 ==== 2.3.1.1 Before Firmware v1.2 ==== 440 440 441 441 442 -N95S31B uplink payload includes in total 21 bytes .474 +N95S31B uplink payload includes in total 21 bytes 443 443 444 -(% border="1" style="background-color:#f2f2f2; width:520px" %) 445 -|=(% style="width: 50px;background-color:#D9E2F3" %)**Size(bytes)**|=(% style="width: 45px;background-color:#D9E2F3" %)**6**|=(% style="width: 25px;background-color:#D9E2F3" %)2|=(% style="width: 25px;background-color:#D9E2F3" %)**2**|=(% style="width: 65px;background-color:#D9E2F3" %)**1**|=(% style="width: 50px;background-color:#D9E2F3" %)1|=(% style="width: 120px;background-color:#D9E2F3" %)5|=(% style="width: 70px;background-color:#D9E2F3" %)**2**|=(% style="width: 70px;background-color:#D9E2F3" %)**2** 446 -|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:162px" %)((( 476 + 477 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 478 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|=(% style="width: 40px;" %)**6**|=(% style="width: 20px;" %)2|=(% style="width: 20px;" %)**2**|=(% style="width: 60px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 100px;" %)5|=(% style="width: 50px;" %)**2**|=(% style="width: 50px;" %)**2** 479 +|=(% style="width: 97px;" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:162px" %)((( 447 447 ((( 448 448 Reserve/ Same as NBSN95 CFGMOD=1 449 449 ))) ... ... @@ -504,6 +504,7 @@ 504 504 ((( 505 505 506 506 540 + 507 507 508 508 ))) 509 509 ... ... @@ -514,10 +514,11 @@ 514 514 515 515 Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded. 516 516 517 -(% border="1" style="background-color:#f2f2f2; width:520px" %) 518 -|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**Size(bytes)**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**8**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:30px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:55px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:35px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:30px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**4** 519 -|(% style="width:95px" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:47px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:56px" %)MOD|(% style="width:109px" %)TemDS18B20|(% style="width:80px" %)Interrupt|(% style="width:51px" %)ADC|(% style="width:79px" %)SHTTEM|(% style="width:84px" %)SHTHUM|(% style="width:100px" %)Time stamp |(% style="width:76px" %)SHTTEM|(% style="width:81px" %)SHTHUM|(% style="width:121px" %)Time stamp ..... 520 520 552 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 553 +|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:30px" %)**1**|(% style="width:20px" %)**1**|(% style="width:50px" %)**2**|(% style="width:30px" %)**1**|(% style="width:20px" %)**2**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:40px" %)**4**|(% style="width:35px" %)**2**|(% style="width:35px" %)**2**|(% style="width:35px" %)**4** 554 +|=(% style="width: 95px;" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:47px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:56px" %)MOD|(% style="width:109px" %)TemDS18B20|(% style="width:80px" %)Interrupt|(% style="width:51px" %)ADC|(% style="width:79px" %)SHTTEM|(% style="width:84px" %)SHTHUM|(% style="width:100px" %)Time stamp |(% style="width:76px" %)SHTTEM|(% style="width:81px" %)SHTHUM|(% style="width:121px" %)Time stamp ..... 555 + 521 521 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 522 522 523 523 ... ... @@ -598,6 +598,7 @@ 598 598 AT+DEUI=868411056754138 599 599 600 600 636 + 601 601 === 2.3.3 Version Info === 602 602 603 603 ... ... @@ -606,11 +606,11 @@ 606 606 ))) 607 607 608 608 ((( 609 - **Higher byte:**Specify hardware version: always 0x00 for N95S31B645 +Higher byte: Specify hardware version: always 0x00 for N95S31B 610 610 ))) 611 611 612 612 ((( 613 - **Lower byte:**Specify the software version: 0x6E=110, means firmware version 110649 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 614 614 ))) 615 615 616 616 ((( ... ... @@ -625,6 +625,7 @@ 625 625 626 626 ))) 627 627 664 + 628 628 === 2.3.4 Battery Info === 629 629 630 630 ... ... @@ -637,6 +637,7 @@ 637 637 ))) 638 638 639 639 677 + 640 640 === 2.3.5 Signal Strength === 641 641 642 642 ... ... @@ -669,6 +669,7 @@ 669 669 ))) 670 670 671 671 710 + 672 672 === 2.3.6 Temperature & Humidity === 673 673 674 674 ... ... @@ -687,17 +687,15 @@ 687 687 Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 688 688 689 689 729 + 690 690 == 2.4 Downlink Payload == 691 691 692 692 693 693 By default, N95S31B prints the downlink payload to console port. 694 694 695 -(% border="1" style="background-color:#f2f2f2; width:520px" %) 696 -|(% style="background-color:#d9e2f3; color:#0070c0; width:200px" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:100px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; width:170px" %)**Downlink payload size(bytes)** 697 -|(% style="width:204px" %)TDC(Transmit Time Interval)|(% style="width:80px" %)Any|(% style="width:94px" %)01|(% style="width:150px" %)4 698 -|(% style="width:204px" %)RESET|(% style="width:80px" %)Any|(% style="width:94px" %)04|(% style="width:150px" %)2 699 -|(% style="width:204px" %)INTMOD|(% style="width:80px" %)Any|(% style="width:94px" %)06|(% style="width:150px" %)4 735 +[[image:image-20220709100028-1.png]] 700 700 737 + 701 701 ((( 702 702 (% style="color:blue" %)**Examples:** 703 703 ))) ... ... @@ -742,6 +742,7 @@ 742 742 ))) 743 743 744 744 782 + 745 745 == 2.5 Humidity and Temperature alarm function == 746 746 747 747 ... ... @@ -777,6 +777,7 @@ 777 777 AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 778 778 779 779 818 + 780 780 == 2.6 Set the number of data to be uploaded and the recording time == 781 781 782 782 ... ... @@ -790,6 +790,7 @@ 790 790 [[image:image-20221009001045-1.png||height="726" width="1009"]] 791 791 792 792 832 + 793 793 == 2.7 Read or Clear cached data == 794 794 795 795 ... ... @@ -801,14 +801,70 @@ 801 801 [[image:image-20220908163102-2.png]] 802 802 803 803 804 -== 2.8 Battery & Power Consumption == 805 805 845 +== 2.8 Battery Analysis == 806 806 807 -N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 808 808 809 - [[**BatteryInfo & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]].848 +=== 2.8.1 Battery Type === 810 810 811 811 851 +((( 852 +The N95S31B battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter. 853 +))) 854 + 855 +((( 856 +The battery is designed to last for several years depends on the actually use environment and update interval. 857 +))) 858 + 859 +((( 860 +The battery related documents as below: 861 +))) 862 + 863 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 864 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 865 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 866 + 867 +((( 868 +[[image:image-20220709101450-2.png]] 869 +))) 870 + 871 + 872 + 873 +=== 2.8.2 Power consumption Analyze === 874 + 875 + 876 +((( 877 +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. 878 +))) 879 + 880 +((( 881 + 882 +))) 883 + 884 + 885 +=== 2.8.3 Battery Note === 886 + 887 + 888 +((( 889 +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. 890 +))) 891 + 892 + 893 + 894 +=== 2.8.4 Replace the battery === 895 + 896 + 897 +((( 898 +You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board. 899 +))) 900 + 901 + 902 +((( 903 +The default battery pack of N95S31B includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes). 904 +))) 905 + 906 + 907 + 812 812 = 3. Access NB-IoT Module = 813 813 814 814 ... ... @@ -825,8 +825,10 @@ 825 825 [[image:1657333200519-600.png]] 826 826 827 827 924 + 828 828 = 4. Using the AT Commands = 829 829 927 + 830 830 == 4.1 Access AT Commands == 831 831 832 832 ... ... @@ -895,6 +895,11 @@ 895 895 AT+URI : Resource parameters 896 896 897 897 996 +(% style="color:#037691" %)**UDP Management** 997 + 998 +AT+CFM : Upload confirmation mode (only valid for UDP) 999 + 1000 + 898 898 (% style="color:#037691" %)**MQTT Management** 899 899 900 900 AT+CLIENT : Get or Set MQTT client ... ... @@ -915,8 +915,10 @@ 915 915 AT+PWORD : Serial Access Password 916 916 917 917 1021 + 918 918 = 5. FAQ = 919 919 1024 + 920 920 == 5.1 How to Upgrade Firmware == 921 921 922 922 ... ... @@ -929,14 +929,18 @@ 929 929 ))) 930 930 931 931 ((( 932 - FirmwareDownload:[[https:~~/~~/www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0>>https://www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0]]1037 + 933 933 1039 +((( 934 934 (% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 935 935 ))) 1042 +))) 936 936 937 937 1045 + 938 938 = 6. Trouble Shooting = 939 939 1048 + 940 940 == 6.1 Connection problem when uploading firmware == 941 941 942 942 ... ... @@ -944,7 +944,12 @@ 944 944 **Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]] 945 945 ))) 946 946 1056 +(% class="wikigeneratedid" %) 1057 +((( 1058 + 1059 +))) 947 947 1061 + 948 948 == 6.2 AT Command input doesn't work == 949 949 950 950 ... ... @@ -954,12 +954,7 @@ 954 954 955 955 ))) 956 956 957 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 958 958 959 - 960 -This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**. 961 - 962 - 963 963 = 7. Order Info = 964 964 965 965 ... ... @@ -966,6 +966,11 @@ 966 966 Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 967 967 968 968 1078 +(% class="wikigeneratedid" %) 1079 +((( 1080 + 1081 +))) 1082 + 969 969 = 8. Packing Info = 970 970 971 971 ((( ... ... @@ -988,11 +988,15 @@ 988 988 * Weight / pcs : 180g 989 989 ))) 990 990 1105 +((( 1106 + 991 991 992 992 1109 + 1110 +))) 1111 + 993 993 = 9. Support = 994 994 995 995 996 996 * 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. 997 - 998 998 * 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]]