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

From version 189.4
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
... ... @@ -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  )))
... ... @@ -177,6 +177,7 @@
177 177  
178 178  === 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. ===
179 179  
194 +
180 180  (((
181 181  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.
182 182  )))
... ... @@ -188,6 +188,7 @@
188 188  
189 189  == 2.4 Uplink Payload ==
190 190  
206 +
191 191  (((
192 192  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.
193 193  )))
... ... @@ -262,12 +262,13 @@
262 262  
263 263  * The First 6 bytes: has fix meanings for every LHT65N.
264 264  * The 7th byte (EXT #): defines the external sensor model.
265 -* 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.)
266 266  
267 267  
268 268  
269 269  === 2.4.1 Decoder in TTN V3 ===
270 270  
287 +
271 271  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.
272 272  
273 273  Below is the position to put the decoder and LHT65N decoder can be download from here:
... ... @@ -283,6 +283,7 @@
283 283  
284 284  === 2.4.2 BAT-Battery Info ===
285 285  
303 +
286 286  These two bytes of BAT include the battery state and the actually voltage
287 287  
288 288  [[image:image-20220523152839-18.png||_mstalt="457613" _mstvisible="3"]]
... ... @@ -300,6 +300,7 @@
300 300  
301 301  === 2.4.3 Built-in Temperature ===
302 302  
321 +
303 303  [[image:image-20220522235639-2.png||_mstalt="431756" _mstvisible="3" height="138" width="722"]]
304 304  
305 305  * Temperature:  0x0ABB/100=27.47℃
... ... @@ -312,6 +312,7 @@
312 312  
313 313  === 2.4.4 Built-in Humidity ===
314 314  
334 +
315 315  [[image:image-20220522235639-4.png||_mstalt="432484" _mstvisible="3" height="138" width="722"]]
316 316  
317 317  * Humidity:    0x025C/10=60.4%
... ... @@ -320,6 +320,7 @@
320 320  
321 321  === 2.4.5 Ext # ===
322 322  
343 +
323 323  Bytes for External Sensor:
324 324  
325 325  [[image:image-20220523152822-17.png||_mstalt="454545" _mstvisible="3"]]
... ... @@ -351,6 +351,7 @@
351 351  
352 352  ==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ====
353 353  
375 +
354 354  (((
355 355  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:
356 356  )))
... ... @@ -473,8 +473,10 @@
473 473  * (% 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)
474 474  
475 475  
498 +
476 476  ==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ====
477 477  
501 +
478 478  In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can
479 479  
480 480  be used to power the external ADC sensor; user can control the power on time for this
... ... @@ -522,6 +522,7 @@
522 522  
523 523  == 2.5 Show data on Datacake ==
524 524  
549 +
525 525  (((
526 526  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:
527 527  )))
... ... @@ -569,6 +569,7 @@
569 569  
570 570  == 2.6 Datalog Feature ==
571 571  
597 +
572 572  (((
573 573  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.
574 574  )))
... ... @@ -577,6 +577,7 @@
577 577  
578 578  === 2.6.1 Ways to get datalog via LoRaWAN ===
579 579  
606 +
580 580  There are two methods:
581 581  
582 582  1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specifying time range.
... ... @@ -609,6 +609,7 @@
609 609  
610 610  === 2.6.3 Set Device Time ===
611 611  
639 +
612 612  (((
613 613  There are two ways to set device's time:
614 614  )))
... ... @@ -626,7 +626,7 @@
626 626  )))
627 627  
628 628  (((
629 -(% 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.**
630 630  )))
631 631  
632 632  (((
... ... @@ -645,6 +645,7 @@
645 645  
646 646  === 2.6.4 Poll sensor value ===
647 647  
676 +
648 648  User can poll sensor value based on timestamps from the server. Below is the downlink command.
649 649  
650 650  [[image:image-20220523152302-15.png||_mstalt="451581" _mstvisible="3"]]
... ... @@ -662,6 +662,7 @@
662 662  
663 663  === 2.6.5 Datalog Uplink payload ===
664 664  
694 +
665 665  (% _msthash="315267" _msttexthash="2245087" _mstvisible="1" %)
666 666  The Datalog poll reply uplink will use below payload format.
667 667  
... ... @@ -668,6 +668,9 @@
668 668  (% _mstvisible="1" %)
669 669  (((
670 670  (% _mstvisible="2" %)
701 +
702 +
703 +(% _mstvisible="2" %)
671 671  (% _msthash="506080" _msttexthash="451581" _mstvisible="4" %)**Retrieval data payload**
672 672  )))
673 673  
... ... @@ -795,6 +795,7 @@
795 795  )))
796 796  )))
797 797  
831 +
798 798  (% _mstvisible="1" %)
799 799  (% _msthash="315268" _msttexthash="390390" _mstvisible="3" %)**Poll message flag & Ext**
800 800  
... ... @@ -930,7 +930,7 @@
930 930  (% _mstvisible="1" %)
931 931  (((
932 932  (% _msthash="506083" _msttexthash="737269" _mstvisible="2" style="text-align: left;" %)
933 - 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
934 934  )))
935 935  
936 936  (% _mstvisible="1" %)
... ... @@ -1055,6 +1055,7 @@
1055 1055  * RED LED when external sensor is not connected
1056 1056  * For each success downlink, the PURPLE LED will blink once
1057 1057  
1092 +
1058 1058  == 2.9 installation ==
1059 1059  
1060 1060  (% _mstvisible="1" %)
... ... @@ -1105,6 +1105,7 @@
1105 1105  * Operating Range: -40 ~~ 125 °C
1106 1106  * Working voltage 2.35v ~~ 5v
1107 1107  
1143 +
1108 1108  = 4. Configure LHT65N via AT command or LoRaWAN downlink =
1109 1109  
1110 1110  (((
... ... @@ -1170,6 +1170,7 @@
1170 1170  
1171 1171  * **Example 2**: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
1172 1172  
1209 +
1173 1173  == 4.2 Set External Sensor Mode ==
1174 1174  
1175 1175  Feature: Change External Sensor Mode.
... ... @@ -1191,6 +1191,7 @@
1191 1191  
1192 1192  * 0xA20702003c: Same as AT+SETCNT=60
1193 1193  
1231 +
1194 1194  == 4.3 Enable/Disable uplink Temperature probe ID ==
1195 1195  
1196 1196  (((
... ... @@ -1218,6 +1218,7 @@
1218 1218  * **0xA800**  **~-~->** AT+PID=0
1219 1219  * **0xA801**     **~-~->** AT+PID=1
1220 1220  
1259 +
1221 1221  == 4.4 Set Password ==
1222 1222  
1223 1223  Feature: Set device password, max 9 digits
... ... @@ -1264,6 +1264,7 @@
1264 1264  
1265 1265  * There is no downlink command to set to Sleep mode.
1266 1266  
1306 +
1267 1267  == 4.7 Set system time ==
1268 1268  
1269 1269  Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]]
... ... @@ -1360,6 +1360,7 @@
1360 1360  
1361 1361  * Example: 0xA301 ~/~/Same as AT+CLRDTA
1362 1362  
1403 +
1363 1363  == 4.13 Auto Send None-ACK messages ==
1364 1364  
1365 1365  (% _msthash="315394" _msttexthash="51837149" _mstvisible="1" %)
... ... @@ -1378,6 +1378,7 @@
1378 1378  
1379 1379  * Example: 0x3401 ~/~/Same as AT+PNACKMD=1
1380 1380  
1422 +
1381 1381  = 5. Battery & How to replace =
1382 1382  
1383 1383  == 5.1 Battery Type ==
... ... @@ -1830,6 +1830,7 @@
1830 1830  
1831 1831  * (% style="color:red" %)**E3**(%%): External Temperature Probe
1832 1832  
1875 +
1833 1833  = 8. Packing Info =
1834 1834  
1835 1835  
... ... @@ -1843,10 +1843,12 @@
1843 1843  * Device Size:  10 x 10 x 3.5 cm
1844 1844  * Device Weight: 120.5g
1845 1845  
1889 +
1846 1846  = 9. Reference material =
1847 1847  
1848 1848  * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0||_msthash="504975" _msttexthash="51420512"]]
1849 1849  
1894 +
1850 1850  = 10. FCC Warning =
1851 1851  
1852 1852  This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions: