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

From version 188.1
edited by Edwin Chen
on 2022/07/03 11:17
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
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,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  )))
... ... @@ -166,9 +166,10 @@
166 166  [[image:image-20220522232954-5.png||_mstalt="431847" _mstvisible="3"]]
167 167  
168 168  
169 -Note: LHT65N use same payload as LHT65.
170 170  
178 +(% style="color:red" %)**Note: LHT65N use same payload as LHT65.**
171 171  
180 +
172 172  [[image:image-20220522233026-6.png||_mstalt="429403" _mstvisible="3"]]
173 173  
174 174  
... ... @@ -182,6 +182,7 @@
182 182  
183 183  === 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. ===
184 184  
194 +
185 185  (((
186 186  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.
187 187  )))
... ... @@ -193,6 +193,7 @@
193 193  
194 194  == 2.4 Uplink Payload ==
195 195  
206 +
196 196  (((
197 197  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.
198 198  )))
... ... @@ -267,13 +267,13 @@
267 267  
268 268  * The First 6 bytes: has fix meanings for every LHT65N.
269 269  * The 7th byte (EXT #): defines the external sensor model.
270 -* 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.)
271 271  
272 272  
273 273  
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"]]
... ... @@ -304,9 +304,9 @@
304 304  
305 305  
306 306  
307 -
308 308  === 2.4.3 Built-in Temperature ===
309 309  
321 +
310 310  [[image:image-20220522235639-2.png||_mstalt="431756" _mstvisible="3" height="138" width="722"]]
311 311  
312 312  * Temperature:  0x0ABB/100=27.47℃
... ... @@ -317,9 +317,9 @@
317 317  
318 318  
319 319  
320 -
321 321  === 2.4.4 Built-in Humidity ===
322 322  
334 +
323 323  [[image:image-20220522235639-4.png||_mstalt="432484" _mstvisible="3" height="138" width="722"]]
324 324  
325 325  * Humidity:    0x025C/10=60.4%
... ... @@ -326,9 +326,9 @@
326 326  
327 327  
328 328  
329 -
330 330  === 2.4.5 Ext # ===
331 331  
343 +
332 332  Bytes for External Sensor:
333 333  
334 334  [[image:image-20220523152822-17.png||_mstalt="454545" _mstvisible="3"]]
... ... @@ -360,6 +360,7 @@
360 360  
361 361  ==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ====
362 362  
375 +
363 363  (((
364 364  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:
365 365  )))
... ... @@ -473,17 +473,19 @@
473 473  
474 474  * (% _msthash="504956" _msttexthash="245037" _mstvisible="4" %)**Status & Ext Byte**
475 475  
476 -[[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)
477 477  
478 -* Poll Message Flag:  1: This message is a poll message reply, 0: means this is a normal uplink.
479 -* 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.
480 -* 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)
481 481  
482 482  
483 483  
484 -
485 485  ==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ====
486 486  
501 +
487 487  In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can
488 488  
489 489  be used to power the external ADC sensor; user can control the power on time for this
... ... @@ -531,6 +531,7 @@
531 531  
532 532  == 2.5 Show data on Datacake ==
533 533  
549 +
534 534  (((
535 535  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:
536 536  )))
... ... @@ -578,6 +578,7 @@
578 578  
579 579  == 2.6 Datalog Feature ==
580 580  
597 +
581 581  (((
582 582  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.
583 583  )))
... ... @@ -586,6 +586,7 @@
586 586  
587 587  === 2.6.1 Ways to get datalog via LoRaWAN ===
588 588  
606 +
589 589  There are two methods:
590 590  
591 591  1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specifying time range.
... ... @@ -618,6 +618,7 @@
618 618  
619 619  === 2.6.3 Set Device Time ===
620 620  
639 +
621 621  (((
622 622  There are two ways to set device's time:
623 623  )))
... ... @@ -635,7 +635,7 @@
635 635  )))
636 636  
637 637  (((
638 -(% 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.**
639 639  )))
640 640  
641 641  (((
... ... @@ -654,6 +654,7 @@
654 654  
655 655  === 2.6.4 Poll sensor value ===
656 656  
676 +
657 657  User can poll sensor value based on timestamps from the server. Below is the downlink command.
658 658  
659 659  [[image:image-20220523152302-15.png||_mstalt="451581" _mstvisible="3"]]
... ... @@ -671,6 +671,7 @@
671 671  
672 672  === 2.6.5 Datalog Uplink payload ===
673 673  
694 +
674 674  (% _msthash="315267" _msttexthash="2245087" _mstvisible="1" %)
675 675  The Datalog poll reply uplink will use below payload format.
676 676  
... ... @@ -677,6 +677,9 @@
677 677  (% _mstvisible="1" %)
678 678  (((
679 679  (% _mstvisible="2" %)
701 +
702 +
703 +(% _mstvisible="2" %)
680 680  (% _msthash="506080" _msttexthash="451581" _mstvisible="4" %)**Retrieval data payload**
681 681  )))
682 682  
... ... @@ -804,6 +804,7 @@
804 804  )))
805 805  )))
806 806  
831 +
807 807  (% _mstvisible="1" %)
808 808  (% _msthash="315268" _msttexthash="390390" _mstvisible="3" %)**Poll message flag & Ext**
809 809  
... ... @@ -939,7 +939,7 @@
939 939  (% _mstvisible="1" %)
940 940  (((
941 941  (% _msthash="506083" _msttexthash="737269" _mstvisible="2" style="text-align: left;" %)
942 - 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
943 943  )))
944 944  
945 945  (% _mstvisible="1" %)
... ... @@ -1036,8 +1036,21 @@
1036 1036  )))
1037 1037  )))
1038 1038  
1064 +(% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX**
1039 1039  
1066 +Total bytes: 8 bytes
1040 1040  
1068 +**Example:**AA0100010001003C
1069 +
1070 +WMOD=01
1071 +
1072 +CITEMP=0001
1073 +
1074 +TEMPlow=0001
1075 +
1076 +TEMPhigh=003C
1077 +
1078 +
1041 1041  == 2.8 LED Indicator ==
1042 1042  
1043 1043  The LHT65 has a triple color LED which for easy showing different stage .
... ... @@ -1052,8 +1052,6 @@
1052 1052  * For each success downlink, the PURPLE LED will blink once
1053 1053  
1054 1054  
1055 -
1056 -
1057 1057  == 2.9 installation ==
1058 1058  
1059 1059  (% _mstvisible="1" %)
... ... @@ -1105,8 +1105,6 @@
1105 1105  * Working voltage 2.35v ~~ 5v
1106 1106  
1107 1107  
1108 -
1109 -
1110 1110  = 4. Configure LHT65N via AT command or LoRaWAN downlink =
1111 1111  
1112 1112  (((
... ... @@ -1173,8 +1173,6 @@
1173 1173  * **Example 2**: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
1174 1174  
1175 1175  
1176 -
1177 -
1178 1178  == 4.2 Set External Sensor Mode ==
1179 1179  
1180 1180  Feature: Change External Sensor Mode.
... ... @@ -1197,8 +1197,6 @@
1197 1197  * 0xA20702003c: Same as AT+SETCNT=60
1198 1198  
1199 1199  
1200 -
1201 -
1202 1202  == 4.3 Enable/Disable uplink Temperature probe ID ==
1203 1203  
1204 1204  (((
... ... @@ -1227,8 +1227,6 @@
1227 1227  * **0xA801**     **~-~->** AT+PID=1
1228 1228  
1229 1229  
1230 -
1231 -
1232 1232  == 4.4 Set Password ==
1233 1233  
1234 1234  Feature: Set device password, max 9 digits
... ... @@ -1276,8 +1276,6 @@
1276 1276  * There is no downlink command to set to Sleep mode.
1277 1277  
1278 1278  
1279 -
1280 -
1281 1281  == 4.7 Set system time ==
1282 1282  
1283 1283  Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]]
... ... @@ -1375,8 +1375,6 @@
1375 1375  * Example: 0xA301 ~/~/Same as AT+CLRDTA
1376 1376  
1377 1377  
1378 -
1379 -
1380 1380  == 4.13 Auto Send None-ACK messages ==
1381 1381  
1382 1382  (% _msthash="315394" _msttexthash="51837149" _mstvisible="1" %)
... ... @@ -1396,8 +1396,6 @@
1396 1396  * Example: 0x3401 ~/~/Same as AT+PNACKMD=1
1397 1397  
1398 1398  
1399 -
1400 -
1401 1401  = 5. Battery & How to replace =
1402 1402  
1403 1403  == 5.1 Battery Type ==
... ... @@ -1851,8 +1851,6 @@
1851 1851  * (% style="color:red" %)**E3**(%%): External Temperature Probe
1852 1852  
1853 1853  
1854 -
1855 -
1856 1856  = 8. Packing Info =
1857 1857  
1858 1858  
... ... @@ -1867,15 +1867,11 @@
1867 1867  * Device Weight: 120.5g
1868 1868  
1869 1869  
1870 -
1871 -
1872 1872  = 9. Reference material =
1873 1873  
1874 1874  * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0||_msthash="504975" _msttexthash="51420512"]]
1875 1875  
1876 1876  
1877 -
1878 -
1879 1879  = 10. FCC Warning =
1880 1880  
1881 1881  This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions: