Skip to Content
Last modified by Xiaoling on 2023/07/18 10:12
From version 187.1
edited by Edwin Chen
on 2022/07/03 11:17
Change comment: Uploaded new attachment "image-20220703111700-2.png", version {1}
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
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,8 +60,6 @@
60 60  
61 61  
62 62  
63 -
64 -
65 65  == 1.3 Specification ==
66 66  
67 67  
... ... @@ -72,6 +72,8 @@
72 72  * Long Term Drift: < 0.02 °C/yr
73 73  * Operating Range: -40 ~~ 85 °C
74 74  
74 +
75 +
75 75  **Built-in Humidity Sensor:**
76 76  
77 77  * Resolution: 0.04 %RH
... ... @@ -79,6 +79,8 @@
79 79  * Long Term Drift: < 0.02 °C/yr
80 80  * Operating Range: 0 ~~ 96 %RH
81 81  
83 +
84 +
82 82  **External Temperature Sensor:**
83 83  
84 84  * Resolution: 0.0625 °C
... ... @@ -88,12 +88,11 @@
88 88  
89 89  
90 90  
91 -
92 -
93 93  = 2. Connect LHT65N to IoT Server =
94 94  
95 95  == 2.1 How does LHT65N work? ==
96 96  
98 +
97 97  (((
98 98  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.
99 99  )))
... ... @@ -103,8 +103,10 @@
103 103  )))
104 104  
105 105  
108 +
106 106  == 2.2 How to Activate LHT65N? ==
107 107  
111 +
108 108  (((
109 109  The LHT65N has two working modes:
110 110  )))
... ... @@ -129,6 +129,7 @@
129 129  
130 130  == 2.3 Example to join LoRaWAN network ==
131 131  
136 +
132 132  (% _msthash="315240" _msttexthash="9205482" _mstvisible="1" class="wikigeneratedid" %)
133 133  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.
134 134  
... ... @@ -144,6 +144,7 @@
144 144  
145 145  === 2.3.1 Step 1: Create Device n TTN ===
146 146  
152 +
147 147  (((
148 148  Create a device in TTN V3 with the OTAA keys from LHT65N.
149 149  )))
... ... @@ -168,9 +168,10 @@
168 168  [[image:image-20220522232954-5.png||_mstalt="431847" _mstvisible="3"]]
169 169  
170 170  
171 -Note: LHT65N use same payload as LHT65.
172 172  
178 +(% style="color:red" %)**Note: LHT65N use same payload as LHT65.**
173 173  
180 +
174 174  [[image:image-20220522233026-6.png||_mstalt="429403" _mstvisible="3"]]
175 175  
176 176  
... ... @@ -184,6 +184,7 @@
184 184  
185 185  === 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. ===
186 186  
194 +
187 187  (((
188 188  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.
189 189  )))
... ... @@ -195,6 +195,7 @@
195 195  
196 196  == 2.4 Uplink Payload ==
197 197  
206 +
198 198  (((
199 199  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.
200 200  )))
... ... @@ -269,14 +269,13 @@
269 269  
270 270  * The First 6 bytes: has fix meanings for every LHT65N.
271 271  * The 7th byte (EXT #): defines the external sensor model.
272 -* 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.)
273 273  
274 274  
275 275  
276 -
277 -
278 278  === 2.4.1 Decoder in TTN V3 ===
279 279  
287 +
280 280  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.
281 281  
282 282  Below is the position to put the decoder and LHT65N decoder can be download from here:
... ... @@ -292,6 +292,7 @@
292 292  
293 293  === 2.4.2 BAT-Battery Info ===
294 294  
303 +
295 295  These two bytes of BAT include the battery state and the actually voltage
296 296  
297 297  [[image:image-20220523152839-18.png||_mstalt="457613" _mstvisible="3"]]
... ... @@ -307,10 +307,9 @@
307 307  
308 308  
309 309  
310 -
311 -
312 312  === 2.4.3 Built-in Temperature ===
313 313  
321 +
314 314  [[image:image-20220522235639-2.png||_mstalt="431756" _mstvisible="3" height="138" width="722"]]
315 315  
316 316  * Temperature:  0x0ABB/100=27.47℃
... ... @@ -321,10 +321,9 @@
321 321  
322 322  
323 323  
324 -
325 -
326 326  === 2.4.4 Built-in Humidity ===
327 327  
334 +
328 328  [[image:image-20220522235639-4.png||_mstalt="432484" _mstvisible="3" height="138" width="722"]]
329 329  
330 330  * Humidity:    0x025C/10=60.4%
... ... @@ -331,10 +331,9 @@
331 331  
332 332  
333 333  
334 -
335 -
336 336  === 2.4.5 Ext # ===
337 337  
343 +
338 338  Bytes for External Sensor:
339 339  
340 340  [[image:image-20220523152822-17.png||_mstalt="454545" _mstvisible="3"]]
... ... @@ -366,6 +366,7 @@
366 366  
367 367  ==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ====
368 368  
375 +
369 369  (((
370 370  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:
371 371  )))
... ... @@ -479,18 +479,19 @@
479 479  
480 480  * (% _msthash="504956" _msttexthash="245037" _mstvisible="4" %)**Status & Ext Byte**
481 481  
482 -[[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)
483 483  
484 -* Poll Message Flag:  1: This message is a poll message reply, 0: means this is a normal uplink.
485 -* 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.
486 -* 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)
487 487  
488 488  
489 489  
490 -
491 -
492 492  ==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ====
493 493  
501 +
494 494  In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can
495 495  
496 496  be used to power the external ADC sensor; user can control the power on time for this
... ... @@ -538,6 +538,7 @@
538 538  
539 539  == 2.5 Show data on Datacake ==
540 540  
549 +
541 541  (((
542 542  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:
543 543  )))
... ... @@ -585,6 +585,7 @@
585 585  
586 586  == 2.6 Datalog Feature ==
587 587  
597 +
588 588  (((
589 589  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.
590 590  )))
... ... @@ -593,15 +593,17 @@
593 593  
594 594  === 2.6.1 Ways to get datalog via LoRaWAN ===
595 595  
606 +
596 596  There are two methods:
597 597  
598 -1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specify time range.
599 -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.
600 600  
612 +Below is the typical case for the auto-update datalog feature (Set PNACKMD=1)
601 601  
614 +[[image:image-20220703111700-2.png||height="381" width="1119"]]
602 602  
603 603  
604 -
605 605  === 2.6.2 Unix TimeStamp ===
606 606  
607 607  
... ... @@ -624,6 +624,7 @@
624 624  
625 625  === 2.6.3 Set Device Time ===
626 626  
639 +
627 627  (((
628 628  There are two ways to set device's time:
629 629  )))
... ... @@ -641,7 +641,7 @@
641 641  )))
642 642  
643 643  (((
644 -(% 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.**
645 645  )))
646 646  
647 647  (((
... ... @@ -660,6 +660,7 @@
660 660  
661 661  === 2.6.4 Poll sensor value ===
662 662  
676 +
663 663  User can poll sensor value based on timestamps from the server. Below is the downlink command.
664 664  
665 665  [[image:image-20220523152302-15.png||_mstalt="451581" _mstvisible="3"]]
... ... @@ -677,6 +677,7 @@
677 677  
678 678  === 2.6.5 Datalog Uplink payload ===
679 679  
694 +
680 680  (% _msthash="315267" _msttexthash="2245087" _mstvisible="1" %)
681 681  The Datalog poll reply uplink will use below payload format.
682 682  
... ... @@ -683,6 +683,9 @@
683 683  (% _mstvisible="1" %)
684 684  (((
685 685  (% _mstvisible="2" %)
701 +
702 +
703 +(% _mstvisible="2" %)
686 686  (% _msthash="506080" _msttexthash="451581" _mstvisible="4" %)**Retrieval data payload**
687 687  )))
688 688  
... ... @@ -810,6 +810,7 @@
810 810  )))
811 811  )))
812 812  
831 +
813 813  (% _mstvisible="1" %)
814 814  (% _msthash="315268" _msttexthash="390390" _mstvisible="3" %)**Poll message flag & Ext**
815 815  
... ... @@ -945,7 +945,7 @@
945 945  (% _mstvisible="1" %)
946 946  (((
947 947  (% _msthash="506083" _msttexthash="737269" _mstvisible="2" style="text-align: left;" %)
948 - 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
949 949  )))
950 950  
951 951  (% _mstvisible="1" %)
... ... @@ -1042,8 +1042,21 @@
1042 1042  )))
1043 1043  )))
1044 1044  
1064 +(% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX**
1045 1045  
1066 +Total bytes: 8 bytes
1046 1046  
1068 +**Example:**AA0100010001003C
1069 +
1070 +WMOD=01
1071 +
1072 +CITEMP=0001
1073 +
1074 +TEMPlow=0001
1075 +
1076 +TEMPhigh=003C
1077 +
1078 +
1047 1047  == 2.8 LED Indicator ==
1048 1048  
1049 1049  The LHT65 has a triple color LED which for easy showing different stage .
... ... @@ -1058,9 +1058,6 @@
1058 1058  * For each success downlink, the PURPLE LED will blink once
1059 1059  
1060 1060  
1061 -
1062 -
1063 -
1064 1064  == 2.9 installation ==
1065 1065  
1066 1066  (% _mstvisible="1" %)
... ... @@ -1112,9 +1112,6 @@
1112 1112  * Working voltage 2.35v ~~ 5v
1113 1113  
1114 1114  
1115 -
1116 -
1117 -
1118 1118  = 4. Configure LHT65N via AT command or LoRaWAN downlink =
1119 1119  
1120 1120  (((
... ... @@ -1181,9 +1181,6 @@
1181 1181  * **Example 2**: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
1182 1182  
1183 1183  
1184 -
1185 -
1186 -
1187 1187  == 4.2 Set External Sensor Mode ==
1188 1188  
1189 1189  Feature: Change External Sensor Mode.
... ... @@ -1206,9 +1206,6 @@
1206 1206  * 0xA20702003c: Same as AT+SETCNT=60
1207 1207  
1208 1208  
1209 -
1210 -
1211 -
1212 1212  == 4.3 Enable/Disable uplink Temperature probe ID ==
1213 1213  
1214 1214  (((
... ... @@ -1237,9 +1237,6 @@
1237 1237  * **0xA801**     **~-~->** AT+PID=1
1238 1238  
1239 1239  
1240 -
1241 -
1242 -
1243 1243  == 4.4 Set Password ==
1244 1244  
1245 1245  Feature: Set device password, max 9 digits
... ... @@ -1287,9 +1287,6 @@
1287 1287  * There is no downlink command to set to Sleep mode.
1288 1288  
1289 1289  
1290 -
1291 -
1292 -
1293 1293  == 4.7 Set system time ==
1294 1294  
1295 1295  Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]]
... ... @@ -1387,9 +1387,6 @@
1387 1387  * Example: 0xA301 ~/~/Same as AT+CLRDTA
1388 1388  
1389 1389  
1390 -
1391 -
1392 -
1393 1393  == 4.13 Auto Send None-ACK messages ==
1394 1394  
1395 1395  (% _msthash="315394" _msttexthash="51837149" _mstvisible="1" %)
... ... @@ -1409,9 +1409,6 @@
1409 1409  * Example: 0x3401 ~/~/Same as AT+PNACKMD=1
1410 1410  
1411 1411  
1412 -
1413 -
1414 -
1415 1415  = 5. Battery & How to replace =
1416 1416  
1417 1417  == 5.1 Battery Type ==
... ... @@ -1865,9 +1865,6 @@
1865 1865  * (% style="color:red" %)**E3**(%%): External Temperature Probe
1866 1866  
1867 1867  
1868 -
1869 -
1870 -
1871 1871  = 8. Packing Info =
1872 1872  
1873 1873  
... ... @@ -1882,17 +1882,11 @@
1882 1882  * Device Weight: 120.5g
1883 1883  
1884 1884  
1885 -
1886 -
1887 -
1888 1888  = 9. Reference material =
1889 1889  
1890 1890  * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0||_msthash="504975" _msttexthash="51420512"]]
1891 1891  
1892 1892  
1893 -
1894 -
1895 -
1896 1896  = 10. FCC Warning =
1897 1897  
1898 1898  This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions: