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
-
... ... @@ -19,6 +19,8 @@ 19 19 20 20 == 1.1 What is N95S31B NB-IoT Sensor Node == 21 21 22 +((( 23 + 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 ((( 42 + 43 +))) 44 + 45 +((( 40 40 ~* make sure you have NB-IoT coverage locally. 41 41 ))) 42 42 49 + 50 +))) 43 43 44 44 [[image:1657348284168-431.png]] 45 45 46 46 55 + 47 47 == 1.2 Features == 48 48 49 49 ... ... @@ -58,6 +58,7 @@ 58 58 * Micro SIM card slot for NB-IoT SIM 59 59 * 8500mAh Battery for long term use 60 60 70 + 61 61 == 1.3 Specification == 62 62 63 63 ... ... @@ -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 ... ... @@ -83,6 +83,7 @@ 83 83 * Max continuously current: 130mA 84 84 * Max boost current: 2A, 1 second 85 85 96 + 86 86 == 1.4 Applications == 87 87 88 88 ... ... @@ -164,6 +164,7 @@ 164 164 165 165 ))) 166 166 178 + 167 167 == 2.2 Configure the N95S31B == 168 168 169 169 === 2.2.1 Power On N95S31B === ... ... @@ -320,6 +320,7 @@ 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 335 +* (% 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 ... ... @@ -350,6 +350,7 @@ 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 366 + 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 ))) ... ... @@ -402,7 +402,7 @@ 402 402 ))) 403 403 404 404 ((( 405 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/ 419 + (% 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 ... ... @@ -439,10 +439,11 @@ 439 439 ==== 2.3.1.1 Before Firmware v1.2 ==== 440 440 441 441 442 -N95S31B uplink payload includes in total 21 bytes .456 +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** 458 + 459 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 460 +|=(% style="width: 50px;" %)**Size(bytes)**|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 65px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**2** 446 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" %)((( 447 447 ((( 448 448 Reserve/ Same as NBSN95 CFGMOD=1 ... ... @@ -504,6 +504,7 @@ 504 504 ((( 505 505 506 506 522 + 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 534 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 535 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:30px" %)**1**|(% style="width:20px" %)**1**|(% style="width:55px" %)**2**|(% style="width:35px" %)**1**|(% style="width:20px" %)**2**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:30px" %)**4**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:35px" %)**4** 536 +|=(% 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 ..... 537 + 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 ... ... @@ -558,6 +558,7 @@ 558 558 559 559 * (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 560 560 578 + 561 561 === 2.3.2 Device ID === 562 562 563 563 ... ... @@ -606,11 +606,11 @@ 606 606 ))) 607 607 608 608 ((( 609 - **Higher byte:**Specify hardware version: always 0x00 for N95S31B627 +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 110631 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 614 614 ))) 615 615 616 616 ((( ... ... @@ -692,12 +692,9 @@ 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 713 +[[image:image-20220709100028-1.png]] 700 700 715 + 701 701 ((( 702 702 (% style="color:blue" %)**Examples:** 703 703 ))) ... ... @@ -801,7 +801,7 @@ 801 801 [[image:image-20220908163102-2.png]] 802 802 803 803 804 -= =2.8 Battery & Power Consumption ==819 += 2.8 Battery & Power Consumption = 805 805 806 806 807 807 N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. ... ... @@ -809,6 +809,8 @@ 809 809 [[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 810 810 811 811 827 + 828 + 812 812 = 3. Access NB-IoT Module = 813 813 814 814 ... ... @@ -895,6 +895,11 @@ 895 895 AT+URI : Resource parameters 896 896 897 897 915 +(% style="color:#037691" %)**UDP Management** 916 + 917 +AT+CFM : Upload confirmation mode (only valid for UDP) 918 + 919 + 898 898 (% style="color:#037691" %)**MQTT Management** 899 899 900 900 AT+CLIENT : Get or Set MQTT client ... ... @@ -929,10 +929,12 @@ 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]]954 + 933 933 956 +((( 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 ))) 959 +))) 936 936 937 937 938 938 = 6. Trouble Shooting = ... ... @@ -944,6 +944,10 @@ 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 971 +(% class="wikigeneratedid" %) 972 +((( 973 + 974 +))) 947 947 948 948 == 6.2 AT Command input doesn't work == 949 949 ... ... @@ -954,12 +954,6 @@ 954 954 955 955 ))) 956 956 957 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 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 ... ... @@ -988,11 +988,18 @@ 988 988 * Weight / pcs : 180g 989 989 ))) 990 990 1013 +((( 1014 + 991 991 1016 + 1017 +))) 992 992 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]] 1024 + 1025 + 1026 + 1027 +