Changes for page LHT65N -- Manual do sensor de temperatura e umidade LoRaWAN
Last modified by Xiaoling on 2023/07/18 10:12
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,5 +1,5 @@ 1 1 (% style="text-align:center" %) 2 -[[image:image-20220613162008-1.png||_mstalt="428142" height="5 10" width="334"]]2 +[[image:image-20220613162008-1.png||_mstalt="428142" height="579" width="379"]] 3 3 4 4 5 5 ... ... @@ -46,7 +46,6 @@ 46 46 47 47 == 1.2 Features == 48 48 49 - 50 50 * Wall mountable 51 51 * LoRaWAN v1.0.3 Class A protocol 52 52 * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915 ... ... @@ -61,6 +61,7 @@ 61 61 62 62 63 63 63 + 64 64 == 1.3 Specification == 65 65 66 66 ... ... @@ -71,8 +71,6 @@ 71 71 * Long Term Drift: < 0.02 °C/yr 72 72 * Operating Range: -40 ~~ 85 °C 73 73 74 - 75 - 76 76 **Built-in Humidity Sensor:** 77 77 78 78 * Resolution: 0.04 %RH ... ... @@ -80,8 +80,6 @@ 80 80 * Long Term Drift: < 0.02 °C/yr 81 81 * Operating Range: 0 ~~ 96 %RH 82 82 83 - 84 - 85 85 **External Temperature Sensor:** 86 86 87 87 * Resolution: 0.0625 °C ... ... @@ -91,11 +91,11 @@ 91 91 92 92 93 93 90 + 94 94 = 2. Connect LHT65N to IoT Server = 95 95 96 96 == 2.1 How does LHT65N work? == 97 97 98 - 99 99 ((( 100 100 LHT65N is configured as LoRaWAN OTAA Class A mode by default. Each LHT65N is shipped with a worldwide unique set of OTAA keys. To use LHT65N in a LoRaWAN network, first, we need to put the OTAA keys in LoRaWAN Network Server and then activate LHT65N. 101 101 ))) ... ... @@ -105,10 +105,8 @@ 105 105 ))) 106 106 107 107 108 - 109 109 == 2.2 How to Activate LHT65N? == 110 110 111 - 112 112 ((( 113 113 The LHT65N has two working modes: 114 114 ))) ... ... @@ -133,7 +133,6 @@ 133 133 134 134 == 2.3 Example to join LoRaWAN network == 135 135 136 - 137 137 (% _msthash="315240" _msttexthash="9205482" _mstvisible="1" class="wikigeneratedid" %) 138 138 This section shows an example of how to join the TTN V3 LoRaWAN IoT server. Use with other LoRaWAN IoT servers is of a similar procedure. 139 139 ... ... @@ -149,7 +149,6 @@ 149 149 150 150 === 2.3.1 Step 1: Create Device n TTN === 151 151 152 - 153 153 ((( 154 154 Create a device in TTN V3 with the OTAA keys from LHT65N. 155 155 ))) ... ... @@ -191,7 +191,6 @@ 191 191 192 192 === 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. === 193 193 194 - 195 195 ((( 196 196 Use ACT button to activate LHT65N and it will auto-join to the TTN V3 network. After join success, it will start to upload sensor data to TTN V3 and user can see in the panel. 197 197 ))) ... ... @@ -203,7 +203,6 @@ 203 203 204 204 == 2.4 Uplink Payload == 205 205 206 - 207 207 ((( 208 208 The uplink payload includes totally 11 bytes. Uplink packets use FPORT=2 and (% _mstvisible="3" style="color:#4f81bd" %)**every 20 minutes**(%%) send one uplink by default. 209 209 ))) ... ... @@ -278,13 +278,12 @@ 278 278 279 279 * The First 6 bytes: has fix meanings for every LHT65N. 280 280 * The 7th byte (EXT #): defines the external sensor model. 281 -* The 8(% _msthash="734578" _msttexthash="21372" _mstvisible="4" %)^^th^^(%%) ~~ 11(% _msthash="734579" _msttexthash="21372" _mstvisible="4" %)^^th^^(%%) byte: the value for external sensor value. The definition is based on external sensor type. (If EXT=0, there won 't be these four bytes.)271 +* The 8(% _msthash="734578" _msttexthash="21372" _mstvisible="4" %)^^th^^(%%) ~~ 11(% _msthash="734579" _msttexthash="21372" _mstvisible="4" %)^^th^^(%%) byte: the value for external sensor value. The definition is based on external sensor type. (If EXT=0, there won’t be these four bytes.) 282 282 283 283 284 284 285 285 === 2.4.1 Decoder in TTN V3 === 286 286 287 - 288 288 When the uplink payload arrives TTNv3, it shows HEX format and not friendly to read. We can add LHT65N decoder in TTNv3 for friendly reading. 289 289 290 290 Below is the position to put the decoder and LHT65N decoder can be download from here: ... ... @@ -300,7 +300,6 @@ 300 300 301 301 === 2.4.2 BAT-Battery Info === 302 302 303 - 304 304 These two bytes of BAT include the battery state and the actually voltage 305 305 306 306 [[image:image-20220523152839-18.png||_mstalt="457613" _mstvisible="3"]] ... ... @@ -318,7 +318,6 @@ 318 318 319 319 === 2.4.3 Built-in Temperature === 320 320 321 - 322 322 [[image:image-20220522235639-2.png||_mstalt="431756" _mstvisible="3" height="138" width="722"]] 323 323 324 324 * Temperature: 0x0ABB/100=27.47℃ ... ... @@ -331,7 +331,6 @@ 331 331 332 332 === 2.4.4 Built-in Humidity === 333 333 334 - 335 335 [[image:image-20220522235639-4.png||_mstalt="432484" _mstvisible="3" height="138" width="722"]] 336 336 337 337 * Humidity: 0x025C/10=60.4% ... ... @@ -340,7 +340,6 @@ 340 340 341 341 === 2.4.5 Ext # === 342 342 343 - 344 344 Bytes for External Sensor: 345 345 346 346 [[image:image-20220523152822-17.png||_mstalt="454545" _mstvisible="3"]] ... ... @@ -372,7 +372,6 @@ 372 372 373 373 ==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ==== 374 374 375 - 376 376 ((( 377 377 Timestamp mode is designed for LHT65N with E3 probe, it will send the uplink payload with Unix timestamp. With the limitation of 11 bytes (max distance of AU915/US915/AS923 band), the time stamp mode will be lack of BAT voltage field, instead, it shows the battery status. The payload is as below: 378 378 ))) ... ... @@ -495,10 +495,8 @@ 495 495 * (% style="color:blue" %)**Unix Time Request**:(%%) 1: Request server downlink Unix time, 0 : N/A. In this mode, LHT65N will set this bit to 1 every 10 days to request a time SYNC. (AT+SYNCMOD to set this) 496 496 497 497 498 - 499 499 ==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ==== 500 500 501 - 502 502 In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can 503 503 504 504 be used to power the external ADC sensor; user can control the power on time for this ... ... @@ -546,7 +546,6 @@ 546 546 547 547 == 2.5 Show data on Datacake == 548 548 549 - 550 550 ((( 551 551 Datacake IoT platform provides a human-friendly interface to show the sensor data, once we have sensor data in TTN V3, we can use Datacake to connect to TTN V3 and see the data in Datacake. Below are the steps: 552 552 ))) ... ... @@ -594,7 +594,6 @@ 594 594 595 595 == 2.6 Datalog Feature == 596 596 597 - 598 598 ((( 599 599 Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, LHT65N will store the reading for future retrieving purposes. There are two ways for IoT servers to get datalog from LHT65N. 600 600 ))) ... ... @@ -603,7 +603,6 @@ 603 603 604 604 === 2.6.1 Ways to get datalog via LoRaWAN === 605 605 606 - 607 607 There are two methods: 608 608 609 609 1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specifying time range. ... ... @@ -636,7 +636,6 @@ 636 636 637 637 === 2.6.3 Set Device Time === 638 638 639 - 640 640 ((( 641 641 There are two ways to set device's time: 642 642 ))) ... ... @@ -654,7 +654,7 @@ 654 654 ))) 655 655 656 656 ((( 657 -(% style="color:red" %) **Note: LoRaWAN Server need to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature, Chirpstack,TTN V3 v3 and loriot support but TTN V3 v2 doesn't support. If server doesn't support this command, it will through away uplink packet with this command, so user will lose the packet with time request for TTN V3 v2 if SYNCMOD=1.**635 +(% style="color:red" %)Note: LoRaWAN Server need to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature, Chirpstack,TTN V3 v3 and loriot support but TTN V3 v2 doesn’t support. If server doesn’t support this command, it will through away uplink packet with this command, so user will lose the packet with time request for TTN V3 v2 if SYNCMOD=1. 658 658 ))) 659 659 660 660 ((( ... ... @@ -673,7 +673,6 @@ 673 673 674 674 === 2.6.4 Poll sensor value === 675 675 676 - 677 677 User can poll sensor value based on timestamps from the server. Below is the downlink command. 678 678 679 679 [[image:image-20220523152302-15.png||_mstalt="451581" _mstvisible="3"]] ... ... @@ -691,7 +691,6 @@ 691 691 692 692 === 2.6.5 Datalog Uplink payload === 693 693 694 - 695 695 (% _msthash="315267" _msttexthash="2245087" _mstvisible="1" %) 696 696 The Datalog poll reply uplink will use below payload format. 697 697 ... ... @@ -698,9 +698,6 @@ 698 698 (% _mstvisible="1" %) 699 699 ((( 700 700 (% _mstvisible="2" %) 701 - 702 - 703 -(% _mstvisible="2" %) 704 704 (% _msthash="506080" _msttexthash="451581" _mstvisible="4" %)**Retrieval data payload** 705 705 ))) 706 706 ... ... @@ -828,7 +828,6 @@ 828 828 ))) 829 829 ))) 830 830 831 - 832 832 (% _mstvisible="1" %) 833 833 (% _msthash="315268" _msttexthash="390390" _mstvisible="3" %)**Poll message flag & Ext** 834 834 ... ... @@ -964,7 +964,7 @@ 964 964 (% _mstvisible="1" %) 965 965 ((( 966 966 (% _msthash="506083" _msttexthash="737269" _mstvisible="2" style="text-align: left;" %) 967 - 939 + Stop time 60066DA7= time 21/1/19 05:27:(% _msthash="903005" _msttexthash="9672" _mstvisible="2" %)03 968 968 ))) 969 969 970 970 (% _mstvisible="1" %) ... ... @@ -1090,6 +1090,8 @@ 1090 1090 * For each success downlink, the PURPLE LED will blink once 1091 1091 1092 1092 1065 + 1066 + 1093 1093 == 2.9 installation == 1094 1094 1095 1095 (% _mstvisible="1" %) ... ... @@ -1141,6 +1141,8 @@ 1141 1141 * Working voltage 2.35v ~~ 5v 1142 1142 1143 1143 1118 + 1119 + 1144 1144 = 4. Configure LHT65N via AT command or LoRaWAN downlink = 1145 1145 1146 1146 ((( ... ... @@ -1207,6 +1207,8 @@ 1207 1207 * **Example 2**: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds 1208 1208 1209 1209 1186 + 1187 + 1210 1210 == 4.2 Set External Sensor Mode == 1211 1211 1212 1212 Feature: Change External Sensor Mode. ... ... @@ -1229,6 +1229,8 @@ 1229 1229 * 0xA20702003c: Same as AT+SETCNT=60 1230 1230 1231 1231 1210 + 1211 + 1232 1232 == 4.3 Enable/Disable uplink Temperature probe ID == 1233 1233 1234 1234 ((( ... ... @@ -1257,6 +1257,8 @@ 1257 1257 * **0xA801** **~-~->** AT+PID=1 1258 1258 1259 1259 1240 + 1241 + 1260 1260 == 4.4 Set Password == 1261 1261 1262 1262 Feature: Set device password, max 9 digits ... ... @@ -1304,6 +1304,8 @@ 1304 1304 * There is no downlink command to set to Sleep mode. 1305 1305 1306 1306 1289 + 1290 + 1307 1307 == 4.7 Set system time == 1308 1308 1309 1309 Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]] ... ... @@ -1401,6 +1401,8 @@ 1401 1401 * Example: 0xA301 ~/~/Same as AT+CLRDTA 1402 1402 1403 1403 1388 + 1389 + 1404 1404 == 4.13 Auto Send None-ACK messages == 1405 1405 1406 1406 (% _msthash="315394" _msttexthash="51837149" _mstvisible="1" %) ... ... @@ -1420,6 +1420,8 @@ 1420 1420 * Example: 0x3401 ~/~/Same as AT+PNACKMD=1 1421 1421 1422 1422 1409 + 1410 + 1423 1423 = 5. Battery & How to replace = 1424 1424 1425 1425 == 5.1 Battery Type == ... ... @@ -1873,6 +1873,8 @@ 1873 1873 * (% style="color:red" %)**E3**(%%): External Temperature Probe 1874 1874 1875 1875 1864 + 1865 + 1876 1876 = 8. Packing Info = 1877 1877 1878 1878 ... ... @@ -1887,11 +1887,15 @@ 1887 1887 * Device Weight: 120.5g 1888 1888 1889 1889 1880 + 1881 + 1890 1890 = 9. Reference material = 1891 1891 1892 1892 * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0||_msthash="504975" _msttexthash="51420512"]] 1893 1893 1894 1894 1887 + 1888 + 1895 1895 = 10. FCC Warning = 1896 1896 1897 1897 This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions: