Last modified by Xiaoling on 2023/07/18 10:12

From version 189.5
edited by Xiaoling
on 2022/07/22 10:34
Change comment: There is no comment for this version
To version 189.8
edited by Xiaoling
on 2022/08/08 16:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20220613162008-1.png||_mstalt="428142" height="579" 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
... ... @@ -60,7 +60,6 @@
60 60  
61 61  
62 62  
63 -
64 64  == 1.3 Specification ==
65 65  
66 66  
... ... @@ -71,6 +71,8 @@
71 71  * Long Term Drift: < 0.02 °C/yr
72 72  * Operating Range: -40 ~~ 85 °C
73 73  
74 +
75 +
74 74  **Built-in Humidity Sensor:**
75 75  
76 76  * Resolution: 0.04 %RH
... ... @@ -78,6 +78,8 @@
78 78  * Long Term Drift: < 0.02 °C/yr
79 79  * Operating Range: 0 ~~ 96 %RH
80 80  
83 +
84 +
81 81  **External Temperature Sensor:**
82 82  
83 83  * Resolution: 0.0625 °C
... ... @@ -87,11 +87,11 @@
87 87  
88 88  
89 89  
90 -
91 91  = 2. Connect LHT65N to IoT Server =
92 92  
93 93  == 2.1 How does LHT65N work? ==
94 94  
98 +
95 95  (((
96 96  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.
97 97  )))
... ... @@ -101,8 +101,10 @@
101 101  )))
102 102  
103 103  
108 +
104 104  == 2.2 How to Activate LHT65N? ==
105 105  
111 +
106 106  (((
107 107  The LHT65N has two working modes:
108 108  )))
... ... @@ -127,6 +127,7 @@
127 127  
128 128  == 2.3 Example to join LoRaWAN network ==
129 129  
136 +
130 130  (% _msthash="315240" _msttexthash="9205482" _mstvisible="1" class="wikigeneratedid" %)
131 131  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.
132 132  
... ... @@ -142,6 +142,7 @@
142 142  
143 143  === 2.3.1 Step 1: Create Device n TTN ===
144 144  
152 +
145 145  (((
146 146  Create a device in TTN V3 with the OTAA keys from LHT65N.
147 147  )))
... ... @@ -183,6 +183,7 @@
183 183  
184 184  === 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. ===
185 185  
194 +
186 186  (((
187 187  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.
188 188  )))
... ... @@ -194,6 +194,7 @@
194 194  
195 195  == 2.4 Uplink Payload ==
196 196  
206 +
197 197  (((
198 198  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.
199 199  )))
... ... @@ -268,12 +268,13 @@
268 268  
269 269  * The First 6 bytes: has fix meanings for every LHT65N.
270 270  * The 7th byte (EXT #): defines the external sensor model.
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 wont 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.)
272 272  
273 273  
274 274  
275 275  === 2.4.1 Decoder in TTN V3 ===
276 276  
287 +
277 277  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.
278 278  
279 279  Below is the position to put the decoder and LHT65N decoder can be download from here:
... ... @@ -289,6 +289,7 @@
289 289  
290 290  === 2.4.2 BAT-Battery Info ===
291 291  
303 +
292 292  These two bytes of BAT include the battery state and the actually voltage
293 293  
294 294  [[image:image-20220523152839-18.png||_mstalt="457613" _mstvisible="3"]]
... ... @@ -306,6 +306,7 @@
306 306  
307 307  === 2.4.3 Built-in Temperature ===
308 308  
321 +
309 309  [[image:image-20220522235639-2.png||_mstalt="431756" _mstvisible="3" height="138" width="722"]]
310 310  
311 311  * Temperature:  0x0ABB/100=27.47℃
... ... @@ -318,6 +318,7 @@
318 318  
319 319  === 2.4.4 Built-in Humidity ===
320 320  
334 +
321 321  [[image:image-20220522235639-4.png||_mstalt="432484" _mstvisible="3" height="138" width="722"]]
322 322  
323 323  * Humidity:    0x025C/10=60.4%
... ... @@ -326,6 +326,7 @@
326 326  
327 327  === 2.4.5 Ext # ===
328 328  
343 +
329 329  Bytes for External Sensor:
330 330  
331 331  [[image:image-20220523152822-17.png||_mstalt="454545" _mstvisible="3"]]
... ... @@ -357,6 +357,7 @@
357 357  
358 358  ==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ====
359 359  
375 +
360 360  (((
361 361  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:
362 362  )))
... ... @@ -479,8 +479,10 @@
479 479  * (% 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)
480 480  
481 481  
498 +
482 482  ==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ====
483 483  
501 +
484 484  In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can
485 485  
486 486  be used to power the external ADC sensor; user can control the power on time for this
... ... @@ -528,6 +528,7 @@
528 528  
529 529  == 2.5 Show data on Datacake ==
530 530  
549 +
531 531  (((
532 532  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:
533 533  )))
... ... @@ -575,6 +575,7 @@
575 575  
576 576  == 2.6 Datalog Feature ==
577 577  
597 +
578 578  (((
579 579  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.
580 580  )))
... ... @@ -583,6 +583,7 @@
583 583  
584 584  === 2.6.1 Ways to get datalog via LoRaWAN ===
585 585  
606 +
586 586  There are two methods:
587 587  
588 588  1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specifying time range.
... ... @@ -615,6 +615,7 @@
615 615  
616 616  === 2.6.3 Set Device Time ===
617 617  
639 +
618 618  (((
619 619  There are two ways to set device's time:
620 620  )))
... ... @@ -632,7 +632,7 @@
632 632  )))
633 633  
634 634  (((
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 doesnt support. If server doesnt 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.**
636 636  )))
637 637  
638 638  (((
... ... @@ -651,6 +651,7 @@
651 651  
652 652  === 2.6.4 Poll sensor value ===
653 653  
676 +
654 654  User can poll sensor value based on timestamps from the server. Below is the downlink command.
655 655  
656 656  [[image:image-20220523152302-15.png||_mstalt="451581" _mstvisible="3"]]
... ... @@ -668,6 +668,7 @@
668 668  
669 669  === 2.6.5 Datalog Uplink payload ===
670 670  
694 +
671 671  (% _msthash="315267" _msttexthash="2245087" _mstvisible="1" %)
672 672  The Datalog poll reply uplink will use below payload format.
673 673  
... ... @@ -674,6 +674,9 @@
674 674  (% _mstvisible="1" %)
675 675  (((
676 676  (% _mstvisible="2" %)
701 +
702 +
703 +(% _mstvisible="2" %)
677 677  (% _msthash="506080" _msttexthash="451581" _mstvisible="4" %)**Retrieval data payload**
678 678  )))
679 679  
... ... @@ -801,6 +801,7 @@
801 801  )))
802 802  )))
803 803  
831 +
804 804  (% _mstvisible="1" %)
805 805  (% _msthash="315268" _msttexthash="390390" _mstvisible="3" %)**Poll message flag & Ext**
806 806  
... ... @@ -936,7 +936,7 @@
936 936  (% _mstvisible="1" %)
937 937  (((
938 938  (% _msthash="506083" _msttexthash="737269" _mstvisible="2" style="text-align: left;" %)
939 - 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
940 940  )))
941 941  
942 942  (% _mstvisible="1" %)
... ... @@ -1061,6 +1061,7 @@
1061 1061  * RED LED when external sensor is not connected
1062 1062  * For each success downlink, the PURPLE LED will blink once
1063 1063  
1092 +
1064 1064  == 2.9 installation ==
1065 1065  
1066 1066  (% _mstvisible="1" %)
... ... @@ -1111,6 +1111,7 @@
1111 1111  * Operating Range: -40 ~~ 125 °C
1112 1112  * Working voltage 2.35v ~~ 5v
1113 1113  
1143 +
1114 1114  = 4. Configure LHT65N via AT command or LoRaWAN downlink =
1115 1115  
1116 1116  (((
... ... @@ -1176,6 +1176,7 @@
1176 1176  
1177 1177  * **Example 2**: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
1178 1178  
1209 +
1179 1179  == 4.2 Set External Sensor Mode ==
1180 1180  
1181 1181  Feature: Change External Sensor Mode.
... ... @@ -1197,6 +1197,7 @@
1197 1197  
1198 1198  * 0xA20702003c: Same as AT+SETCNT=60
1199 1199  
1231 +
1200 1200  == 4.3 Enable/Disable uplink Temperature probe ID ==
1201 1201  
1202 1202  (((
... ... @@ -1224,6 +1224,7 @@
1224 1224  * **0xA800**  **~-~->** AT+PID=0
1225 1225  * **0xA801**     **~-~->** AT+PID=1
1226 1226  
1259 +
1227 1227  == 4.4 Set Password ==
1228 1228  
1229 1229  Feature: Set device password, max 9 digits
... ... @@ -1270,6 +1270,7 @@
1270 1270  
1271 1271  * There is no downlink command to set to Sleep mode.
1272 1272  
1306 +
1273 1273  == 4.7 Set system time ==
1274 1274  
1275 1275  Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]]
... ... @@ -1366,6 +1366,7 @@
1366 1366  
1367 1367  * Example: 0xA301 ~/~/Same as AT+CLRDTA
1368 1368  
1403 +
1369 1369  == 4.13 Auto Send None-ACK messages ==
1370 1370  
1371 1371  (% _msthash="315394" _msttexthash="51837149" _mstvisible="1" %)
... ... @@ -1384,6 +1384,7 @@
1384 1384  
1385 1385  * Example: 0x3401 ~/~/Same as AT+PNACKMD=1
1386 1386  
1422 +
1387 1387  = 5. Battery & How to replace =
1388 1388  
1389 1389  == 5.1 Battery Type ==
... ... @@ -1836,6 +1836,7 @@
1836 1836  
1837 1837  * (% style="color:red" %)**E3**(%%): External Temperature Probe
1838 1838  
1875 +
1839 1839  = 8. Packing Info =
1840 1840  
1841 1841  
... ... @@ -1849,10 +1849,12 @@
1849 1849  * Device Size:  10 x 10 x 3.5 cm
1850 1850  * Device Weight: 120.5g
1851 1851  
1889 +
1852 1852  = 9. Reference material =
1853 1853  
1854 1854  * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0||_msthash="504975" _msttexthash="51420512"]]
1855 1855  
1894 +
1856 1856  = 10. FCC Warning =
1857 1857  
1858 1858  This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions: