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)
-
Attachments (0 modified, 2 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 79" width="379"]]2 +[[image:image-20220613162008-1.png||_mstalt="428142" height="510" width="334"]] 3 3 4 4 5 5 ... ... @@ -46,6 +46,7 @@ 46 46 47 47 == 1.2 Features == 48 48 49 + 49 49 * Wall mountable 50 50 * LoRaWAN v1.0.3 Class A protocol 51 51 * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915 ... ... @@ -58,6 +58,8 @@ 58 58 * Tri-color LED to indicate working status 59 59 * Datalog feature 60 60 62 + 63 + 61 61 == 1.3 Specification == 62 62 63 63 ... ... @@ -68,6 +68,8 @@ 68 68 * Long Term Drift: < 0.02 °C/yr 69 69 * Operating Range: -40 ~~ 85 °C 70 70 74 + 75 + 71 71 **Built-in Humidity Sensor:** 72 72 73 73 * Resolution: 0.04 %RH ... ... @@ -75,6 +75,8 @@ 75 75 * Long Term Drift: < 0.02 °C/yr 76 76 * Operating Range: 0 ~~ 96 %RH 77 77 83 + 84 + 78 78 **External Temperature Sensor:** 79 79 80 80 * Resolution: 0.0625 °C ... ... @@ -82,10 +82,13 @@ 82 82 * ±2°C accuracy from -55°C to +125°C 83 83 * Operating Range: -55 °C ~~ 125 °C 84 84 92 + 93 + 85 85 = 2. Connect LHT65N to IoT Server = 86 86 87 87 == 2.1 How does LHT65N work? == 88 88 98 + 89 89 ((( 90 90 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. 91 91 ))) ... ... @@ -95,8 +95,10 @@ 95 95 ))) 96 96 97 97 108 + 98 98 == 2.2 How to Activate LHT65N? == 99 99 111 + 100 100 ((( 101 101 The LHT65N has two working modes: 102 102 ))) ... ... @@ -121,6 +121,7 @@ 121 121 122 122 == 2.3 Example to join LoRaWAN network == 123 123 136 + 124 124 (% _msthash="315240" _msttexthash="9205482" _mstvisible="1" class="wikigeneratedid" %) 125 125 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. 126 126 ... ... @@ -136,6 +136,7 @@ 136 136 137 137 === 2.3.1 Step 1: Create Device n TTN === 138 138 152 + 139 139 ((( 140 140 Create a device in TTN V3 with the OTAA keys from LHT65N. 141 141 ))) ... ... @@ -160,9 +160,10 @@ 160 160 [[image:image-20220522232954-5.png||_mstalt="431847" _mstvisible="3"]] 161 161 162 162 163 -Note: LHT65N use same payload as LHT65. 164 164 178 +(% style="color:red" %)**Note: LHT65N use same payload as LHT65.** 165 165 180 + 166 166 [[image:image-20220522233026-6.png||_mstalt="429403" _mstvisible="3"]] 167 167 168 168 ... ... @@ -176,6 +176,7 @@ 176 176 177 177 === 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. === 178 178 194 + 179 179 ((( 180 180 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. 181 181 ))) ... ... @@ -187,6 +187,7 @@ 187 187 188 188 == 2.4 Uplink Payload == 189 189 206 + 190 190 ((( 191 191 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. 192 192 ))) ... ... @@ -261,10 +261,13 @@ 261 261 262 262 * The First 6 bytes: has fix meanings for every LHT65N. 263 263 * The 7th byte (EXT #): defines the external sensor model. 264 -* 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.)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.) 265 265 283 + 284 + 266 266 === 2.4.1 Decoder in TTN V3 === 267 267 287 + 268 268 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. 269 269 270 270 Below is the position to put the decoder and LHT65N decoder can be download from here: ... ... @@ -280,6 +280,7 @@ 280 280 281 281 === 2.4.2 BAT-Battery Info === 282 282 303 + 283 283 These two bytes of BAT include the battery state and the actually voltage 284 284 285 285 [[image:image-20220523152839-18.png||_mstalt="457613" _mstvisible="3"]] ... ... @@ -293,8 +293,11 @@ 293 293 * BAT status=(0Xcba4>>14)&0xFF=11(B),very good 294 294 * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV 295 295 317 + 318 + 296 296 === 2.4.3 Built-in Temperature === 297 297 321 + 298 298 [[image:image-20220522235639-2.png||_mstalt="431756" _mstvisible="3" height="138" width="722"]] 299 299 300 300 * Temperature: 0x0ABB/100=27.47℃ ... ... @@ -303,14 +303,20 @@ 303 303 304 304 * Temperature: (0xF5C6-65536)/100=-26.18℃ 305 305 330 + 331 + 306 306 === 2.4.4 Built-in Humidity === 307 307 334 + 308 308 [[image:image-20220522235639-4.png||_mstalt="432484" _mstvisible="3" height="138" width="722"]] 309 309 310 310 * Humidity: 0x025C/10=60.4% 311 311 339 + 340 + 312 312 === 2.4.5 Ext # === 313 313 343 + 314 314 Bytes for External Sensor: 315 315 316 316 [[image:image-20220523152822-17.png||_mstalt="454545" _mstvisible="3"]] ... ... @@ -342,6 +342,7 @@ 342 342 343 343 ==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ==== 344 344 375 + 345 345 ((( 346 346 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: 347 347 ))) ... ... @@ -455,14 +455,19 @@ 455 455 456 456 * (% _msthash="504956" _msttexthash="245037" _mstvisible="4" %)**Status & Ext Byte** 457 457 458 -[[image:image-20220523152434-16.png||_mstalt="453921" _mstvisible="3"]] 489 +(% border="1" cellspacing="8" style="background-color:#ffffcc; color:green; width:520px" %) 490 +|(% style="width:60px" %)**Bits**|(% style="width:90px" %)**7**|(% style="width:100px" %)**6**|(% style="width:90px" %)**5**|(% style="width:100px" %)**4**|(% style="width:60px" %)**[3:0]** 491 +|(% style="width:96px" %)**Status&Ext**|(% style="width:124px" %)None-ACK Flag|(% style="width:146px" %)Poll Message FLAG|(% style="width:109px" %)Sync time OK|(% style="width:143px" %)Unix Time Request|(% style="width:106px" %)Ext: 0b(1001) 459 459 460 -* Poll Message Flag: 1: This message is a poll message reply, 0: means this is a normal uplink. 461 -* Sync time OK: 462 -* 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) 493 +* (% style="color:blue" %)**Poll Message Flag**:(%%) 1: This message is a poll message reply, 0: means this is a normal uplink. 494 +* (% style="color:blue" %)**Sync time OK**: (%%) 1: Set time ok,0: N/A. After time SYNC request is sent, LHT65N will set this bit to 0 until got the time stamp from the application server. 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) 463 463 497 + 498 + 464 464 ==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ==== 465 465 501 + 466 466 In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can 467 467 468 468 be used to power the external ADC sensor; user can control the power on time for this ... ... @@ -507,8 +507,10 @@ 507 507 [[image:image-20220628151143-7.png]] 508 508 509 509 546 + 510 510 == 2.5 Show data on Datacake == 511 511 549 + 512 512 ((( 513 513 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: 514 514 ))) ... ... @@ -556,6 +556,7 @@ 556 556 557 557 == 2.6 Datalog Feature == 558 558 597 + 559 559 ((( 560 560 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. 561 561 ))) ... ... @@ -564,11 +564,17 @@ 564 564 565 565 === 2.6.1 Ways to get datalog via LoRaWAN === 566 566 606 + 567 567 There are two methods: 568 568 569 -1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specify time range. 570 -1. Set [[PNACKMD=1>>||anchor="H4.13AutoSendNone-ACKmessages"]], LHT65N will wait for ACK for every uplink, when there is no LoRaWAN network, LHT65N will store the sensor data, and it will send all messages after network recover. 609 +1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specifying time range. 610 +1. Set [[PNACKMD=1>>||anchor="H4.13AutoSendNone-ACKmessages"]], LHT65N will wait for ACK for every uplink, when there is no LoRaWAN network, LHT65N will store the sensor data, and it will send all messages after the network recovery. 571 571 612 +Below is the typical case for the auto-update datalog feature (Set PNACKMD=1) 613 + 614 +[[image:image-20220703111700-2.png||height="381" width="1119"]] 615 + 616 + 572 572 === 2.6.2 Unix TimeStamp === 573 573 574 574 ... ... @@ -591,6 +591,7 @@ 591 591 592 592 === 2.6.3 Set Device Time === 593 593 639 + 594 594 ((( 595 595 There are two ways to set device's time: 596 596 ))) ... ... @@ -608,7 +608,7 @@ 608 608 ))) 609 609 610 610 ((( 611 -(% 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.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.** 612 612 ))) 613 613 614 614 ((( ... ... @@ -627,6 +627,7 @@ 627 627 628 628 === 2.6.4 Poll sensor value === 629 629 676 + 630 630 User can poll sensor value based on timestamps from the server. Below is the downlink command. 631 631 632 632 [[image:image-20220523152302-15.png||_mstalt="451581" _mstvisible="3"]] ... ... @@ -644,6 +644,7 @@ 644 644 645 645 === 2.6.5 Datalog Uplink payload === 646 646 694 + 647 647 (% _msthash="315267" _msttexthash="2245087" _mstvisible="1" %) 648 648 The Datalog poll reply uplink will use below payload format. 649 649 ... ... @@ -650,6 +650,9 @@ 650 650 (% _mstvisible="1" %) 651 651 ((( 652 652 (% _mstvisible="2" %) 701 + 702 + 703 +(% _mstvisible="2" %) 653 653 (% _msthash="506080" _msttexthash="451581" _mstvisible="4" %)**Retrieval data payload** 654 654 ))) 655 655 ... ... @@ -777,6 +777,7 @@ 777 777 ))) 778 778 ))) 779 779 831 + 780 780 (% _mstvisible="1" %) 781 781 (% _msthash="315268" _msttexthash="390390" _mstvisible="3" %)**Poll message flag & Ext** 782 782 ... ... @@ -912,7 +912,7 @@ 912 912 (% _mstvisible="1" %) 913 913 ((( 914 914 (% _msthash="506083" _msttexthash="737269" _mstvisible="2" style="text-align: left;" %) 915 - Stop time 60066DA7= time 21/1/19 05:27:(% _msthash="903005" _msttexthash="9672" _mstvisible="2" %)03 967 + Stop time 60066DA7= time 21/1/19 05:27:(% _msthash="903005" _msttexthash="9672" _mstvisible="2" %)03 916 916 ))) 917 917 918 918 (% _mstvisible="1" %) ... ... @@ -1009,8 +1009,21 @@ 1009 1009 ))) 1010 1010 ))) 1011 1011 1064 +(% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX** 1012 1012 1066 +Total bytes: 8 bytes 1013 1013 1068 +**Example:**AA0100010001003C 1069 + 1070 +WMOD=01 1071 + 1072 +CITEMP=0001 1073 + 1074 +TEMPlow=0001 1075 + 1076 +TEMPhigh=003C 1077 + 1078 + 1014 1014 == 2.8 LED Indicator == 1015 1015 1016 1016 The LHT65 has a triple color LED which for easy showing different stage . ... ... @@ -1024,6 +1024,7 @@ 1024 1024 * RED LED when external sensor is not connected 1025 1025 * For each success downlink, the PURPLE LED will blink once 1026 1026 1092 + 1027 1027 == 2.9 installation == 1028 1028 1029 1029 (% _mstvisible="1" %) ... ... @@ -1074,6 +1074,7 @@ 1074 1074 * Operating Range: -40 ~~ 125 °C 1075 1075 * Working voltage 2.35v ~~ 5v 1076 1076 1143 + 1077 1077 = 4. Configure LHT65N via AT command or LoRaWAN downlink = 1078 1078 1079 1079 ((( ... ... @@ -1139,6 +1139,7 @@ 1139 1139 1140 1140 * **Example 2**: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds 1141 1141 1209 + 1142 1142 == 4.2 Set External Sensor Mode == 1143 1143 1144 1144 Feature: Change External Sensor Mode. ... ... @@ -1160,6 +1160,7 @@ 1160 1160 1161 1161 * 0xA20702003c: Same as AT+SETCNT=60 1162 1162 1231 + 1163 1163 == 4.3 Enable/Disable uplink Temperature probe ID == 1164 1164 1165 1165 ((( ... ... @@ -1187,6 +1187,7 @@ 1187 1187 * **0xA800** **~-~->** AT+PID=0 1188 1188 * **0xA801** **~-~->** AT+PID=1 1189 1189 1259 + 1190 1190 == 4.4 Set Password == 1191 1191 1192 1192 Feature: Set device password, max 9 digits ... ... @@ -1233,6 +1233,7 @@ 1233 1233 1234 1234 * There is no downlink command to set to Sleep mode. 1235 1235 1306 + 1236 1236 == 4.7 Set system time == 1237 1237 1238 1238 Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]] ... ... @@ -1329,6 +1329,7 @@ 1329 1329 1330 1330 * Example: 0xA301 ~/~/Same as AT+CLRDTA 1331 1331 1403 + 1332 1332 == 4.13 Auto Send None-ACK messages == 1333 1333 1334 1334 (% _msthash="315394" _msttexthash="51837149" _mstvisible="1" %) ... ... @@ -1347,6 +1347,7 @@ 1347 1347 1348 1348 * Example: 0x3401 ~/~/Same as AT+PNACKMD=1 1349 1349 1422 + 1350 1350 = 5. Battery & How to replace = 1351 1351 1352 1352 == 5.1 Battery Type == ... ... @@ -1800,9 +1800,6 @@ 1800 1800 * (% style="color:red" %)**E3**(%%): External Temperature Probe 1801 1801 1802 1802 1803 - 1804 - 1805 - 1806 1806 = 8. Packing Info = 1807 1807 1808 1808 ... ... @@ -1817,17 +1817,11 @@ 1817 1817 * Device Weight: 120.5g 1818 1818 1819 1819 1820 - 1821 - 1822 - 1823 1823 = 9. Reference material = 1824 1824 1825 1825 * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0||_msthash="504975" _msttexthash="51420512"]] 1826 1826 1827 1827 1828 - 1829 - 1830 - 1831 1831 = 10. FCC Warning = 1832 1832 1833 1833 This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
- image-20220703111533-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +694.5 KB - Content
- image-20220703111700-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +369.4 KB - Content