Changes for page LHT65N -- Manual do sensor de temperatura e umidade LoRaWAN
Last modified by Xiaoling on 2023/07/18 10:12
From version 185.1
edited by Bei Jinggeng
on 2022/06/28 15:12
on 2022/06/28 15:12
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 2 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Bei1 +XWiki.Xiaoling - 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 ... ... @@ -59,6 +59,7 @@ 59 59 * Datalog feature 60 60 61 61 63 + 62 62 == 1.3 Specification == 63 63 64 64 ... ... @@ -69,6 +69,8 @@ 69 69 * Long Term Drift: < 0.02 °C/yr 70 70 * Operating Range: -40 ~~ 85 °C 71 71 74 + 75 + 72 72 **Built-in Humidity Sensor:** 73 73 74 74 * Resolution: 0.04 %RH ... ... @@ -76,6 +76,8 @@ 76 76 * Long Term Drift: < 0.02 °C/yr 77 77 * Operating Range: 0 ~~ 96 %RH 78 78 83 + 84 + 79 79 **External Temperature Sensor:** 80 80 81 81 * Resolution: 0.0625 °C ... ... @@ -84,10 +84,12 @@ 84 84 * Operating Range: -55 °C ~~ 125 °C 85 85 86 86 93 + 87 87 = 2. Connect LHT65N to IoT Server = 88 88 89 89 == 2.1 How does LHT65N work? == 90 90 98 + 91 91 ((( 92 92 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. 93 93 ))) ... ... @@ -97,8 +97,10 @@ 97 97 ))) 98 98 99 99 108 + 100 100 == 2.2 How to Activate LHT65N? == 101 101 111 + 102 102 ((( 103 103 The LHT65N has two working modes: 104 104 ))) ... ... @@ -123,6 +123,7 @@ 123 123 124 124 == 2.3 Example to join LoRaWAN network == 125 125 136 + 126 126 (% _msthash="315240" _msttexthash="9205482" _mstvisible="1" class="wikigeneratedid" %) 127 127 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. 128 128 ... ... @@ -138,6 +138,7 @@ 138 138 139 139 === 2.3.1 Step 1: Create Device n TTN === 140 140 152 + 141 141 ((( 142 142 Create a device in TTN V3 with the OTAA keys from LHT65N. 143 143 ))) ... ... @@ -162,9 +162,10 @@ 162 162 [[image:image-20220522232954-5.png||_mstalt="431847" _mstvisible="3"]] 163 163 164 164 165 -Note: LHT65N use same payload as LHT65. 166 166 178 +(% style="color:red" %)**Note: LHT65N use same payload as LHT65.** 167 167 180 + 168 168 [[image:image-20220522233026-6.png||_mstalt="429403" _mstvisible="3"]] 169 169 170 170 ... ... @@ -178,6 +178,7 @@ 178 178 179 179 === 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. === 180 180 194 + 181 181 ((( 182 182 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. 183 183 ))) ... ... @@ -189,6 +189,7 @@ 189 189 190 190 == 2.4 Uplink Payload == 191 191 206 + 192 192 ((( 193 193 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. 194 194 ))) ... ... @@ -263,10 +263,13 @@ 263 263 264 264 * The First 6 bytes: has fix meanings for every LHT65N. 265 265 * The 7th byte (EXT #): defines the external sensor model. 266 -* 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.) 267 267 283 + 284 + 268 268 === 2.4.1 Decoder in TTN V3 === 269 269 287 + 270 270 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. 271 271 272 272 Below is the position to put the decoder and LHT65N decoder can be download from here: ... ... @@ -282,6 +282,7 @@ 282 282 283 283 === 2.4.2 BAT-Battery Info === 284 284 303 + 285 285 These two bytes of BAT include the battery state and the actually voltage 286 286 287 287 [[image:image-20220523152839-18.png||_mstalt="457613" _mstvisible="3"]] ... ... @@ -295,8 +295,11 @@ 295 295 * BAT status=(0Xcba4>>14)&0xFF=11(B),very good 296 296 * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV 297 297 317 + 318 + 298 298 === 2.4.3 Built-in Temperature === 299 299 321 + 300 300 [[image:image-20220522235639-2.png||_mstalt="431756" _mstvisible="3" height="138" width="722"]] 301 301 302 302 * Temperature: 0x0ABB/100=27.47℃ ... ... @@ -305,14 +305,20 @@ 305 305 306 306 * Temperature: (0xF5C6-65536)/100=-26.18℃ 307 307 330 + 331 + 308 308 === 2.4.4 Built-in Humidity === 309 309 334 + 310 310 [[image:image-20220522235639-4.png||_mstalt="432484" _mstvisible="3" height="138" width="722"]] 311 311 312 312 * Humidity: 0x025C/10=60.4% 313 313 339 + 340 + 314 314 === 2.4.5 Ext # === 315 315 343 + 316 316 Bytes for External Sensor: 317 317 318 318 [[image:image-20220523152822-17.png||_mstalt="454545" _mstvisible="3"]] ... ... @@ -344,6 +344,7 @@ 344 344 345 345 ==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ==== 346 346 375 + 347 347 ((( 348 348 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: 349 349 ))) ... ... @@ -457,14 +457,19 @@ 457 457 458 458 * (% _msthash="504956" _msttexthash="245037" _mstvisible="4" %)**Status & Ext Byte** 459 459 460 -[[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) 461 461 462 -* Poll Message Flag: 1: This message is a poll message reply, 0: means this is a normal uplink. 463 -* Sync time OK: 464 -* 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) 465 465 497 + 498 + 466 466 ==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ==== 467 467 501 + 468 468 In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can 469 469 470 470 be used to power the external ADC sensor; user can control the power on time for this ... ... @@ -509,8 +509,10 @@ 509 509 [[image:image-20220628151143-7.png]] 510 510 511 511 546 + 512 512 == 2.5 Show data on Datacake == 513 513 549 + 514 514 ((( 515 515 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: 516 516 ))) ... ... @@ -558,6 +558,7 @@ 558 558 559 559 == 2.6 Datalog Feature == 560 560 597 + 561 561 ((( 562 562 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. 563 563 ))) ... ... @@ -566,11 +566,17 @@ 566 566 567 567 === 2.6.1 Ways to get datalog via LoRaWAN === 568 568 606 + 569 569 There are two methods: 570 570 571 -1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specify time range. 572 -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. 573 573 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 + 574 574 === 2.6.2 Unix TimeStamp === 575 575 576 576 ... ... @@ -593,6 +593,7 @@ 593 593 594 594 === 2.6.3 Set Device Time === 595 595 639 + 596 596 ((( 597 597 There are two ways to set device's time: 598 598 ))) ... ... @@ -610,7 +610,7 @@ 610 610 ))) 611 611 612 612 ((( 613 -(% 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.** 614 614 ))) 615 615 616 616 ((( ... ... @@ -629,6 +629,7 @@ 629 629 630 630 === 2.6.4 Poll sensor value === 631 631 676 + 632 632 User can poll sensor value based on timestamps from the server. Below is the downlink command. 633 633 634 634 [[image:image-20220523152302-15.png||_mstalt="451581" _mstvisible="3"]] ... ... @@ -646,6 +646,7 @@ 646 646 647 647 === 2.6.5 Datalog Uplink payload === 648 648 694 + 649 649 (% _msthash="315267" _msttexthash="2245087" _mstvisible="1" %) 650 650 The Datalog poll reply uplink will use below payload format. 651 651 ... ... @@ -652,6 +652,9 @@ 652 652 (% _mstvisible="1" %) 653 653 ((( 654 654 (% _mstvisible="2" %) 701 + 702 + 703 +(% _mstvisible="2" %) 655 655 (% _msthash="506080" _msttexthash="451581" _mstvisible="4" %)**Retrieval data payload** 656 656 ))) 657 657 ... ... @@ -779,6 +779,7 @@ 779 779 ))) 780 780 ))) 781 781 831 + 782 782 (% _mstvisible="1" %) 783 783 (% _msthash="315268" _msttexthash="390390" _mstvisible="3" %)**Poll message flag & Ext** 784 784 ... ... @@ -914,7 +914,7 @@ 914 914 (% _mstvisible="1" %) 915 915 ((( 916 916 (% _msthash="506083" _msttexthash="737269" _mstvisible="2" style="text-align: left;" %) 917 - 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 918 918 ))) 919 919 920 920 (% _mstvisible="1" %) ... ... @@ -1011,8 +1011,21 @@ 1011 1011 ))) 1012 1012 ))) 1013 1013 1064 +(% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX** 1014 1014 1066 +Total bytes: 8 bytes 1015 1015 1068 +**Example:**AA0100010001003C 1069 + 1070 +WMOD=01 1071 + 1072 +CITEMP=0001 1073 + 1074 +TEMPlow=0001 1075 + 1076 +TEMPhigh=003C 1077 + 1078 + 1016 1016 == 2.8 LED Indicator == 1017 1017 1018 1018 The LHT65 has a triple color LED which for easy showing different stage . ... ... @@ -1026,6 +1026,7 @@ 1026 1026 * RED LED when external sensor is not connected 1027 1027 * For each success downlink, the PURPLE LED will blink once 1028 1028 1092 + 1029 1029 == 2.9 installation == 1030 1030 1031 1031 (% _mstvisible="1" %) ... ... @@ -1076,6 +1076,7 @@ 1076 1076 * Operating Range: -40 ~~ 125 °C 1077 1077 * Working voltage 2.35v ~~ 5v 1078 1078 1143 + 1079 1079 = 4. Configure LHT65N via AT command or LoRaWAN downlink = 1080 1080 1081 1081 ((( ... ... @@ -1141,6 +1141,7 @@ 1141 1141 1142 1142 * **Example 2**: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds 1143 1143 1209 + 1144 1144 == 4.2 Set External Sensor Mode == 1145 1145 1146 1146 Feature: Change External Sensor Mode. ... ... @@ -1162,6 +1162,7 @@ 1162 1162 1163 1163 * 0xA20702003c: Same as AT+SETCNT=60 1164 1164 1231 + 1165 1165 == 4.3 Enable/Disable uplink Temperature probe ID == 1166 1166 1167 1167 ((( ... ... @@ -1189,6 +1189,7 @@ 1189 1189 * **0xA800** **~-~->** AT+PID=0 1190 1190 * **0xA801** **~-~->** AT+PID=1 1191 1191 1259 + 1192 1192 == 4.4 Set Password == 1193 1193 1194 1194 Feature: Set device password, max 9 digits ... ... @@ -1235,6 +1235,7 @@ 1235 1235 1236 1236 * There is no downlink command to set to Sleep mode. 1237 1237 1306 + 1238 1238 == 4.7 Set system time == 1239 1239 1240 1240 Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]] ... ... @@ -1331,6 +1331,7 @@ 1331 1331 1332 1332 * Example: 0xA301 ~/~/Same as AT+CLRDTA 1333 1333 1403 + 1334 1334 == 4.13 Auto Send None-ACK messages == 1335 1335 1336 1336 (% _msthash="315394" _msttexthash="51837149" _mstvisible="1" %) ... ... @@ -1349,6 +1349,7 @@ 1349 1349 1350 1350 * Example: 0x3401 ~/~/Same as AT+PNACKMD=1 1351 1351 1422 + 1352 1352 = 5. Battery & How to replace = 1353 1353 1354 1354 == 5.1 Battery Type == ... ... @@ -1738,7 +1738,7 @@ 1738 1738 [[image:image-20220615154519-3.png||height="672" width="807"]] 1739 1739 1740 1740 1741 -== 6. 6How to use USB-TYPE-C to connect PC to upgrade firmware? ==1812 +== 6.7 How to use USB-TYPE-C to connect PC to upgrade firmware? == 1742 1742 1743 1743 [[image:image-20220623110706-1.png]] 1744 1744 ... ... @@ -1801,6 +1801,7 @@ 1801 1801 1802 1802 * (% style="color:red" %)**E3**(%%): External Temperature Probe 1803 1803 1875 + 1804 1804 = 8. Packing Info = 1805 1805 1806 1806 ... ... @@ -1814,10 +1814,12 @@ 1814 1814 * Device Size: 10 x 10 x 3.5 cm 1815 1815 * Device Weight: 120.5g 1816 1816 1889 + 1817 1817 = 9. Reference material = 1818 1818 1819 1819 * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0||_msthash="504975" _msttexthash="51420512"]] 1820 1820 1894 + 1821 1821 = 10. FCC Warning = 1822 1822 1823 1823 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