Skip to Content
Last modified by Xiaoling on 2023/07/18 10:12
From version 189.1
edited by Bei Jinggeng
on 2022/07/06 13:48
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.Bei
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
... ... @@ -70,6 +70,8 @@
70 70  * Long Term Drift: < 0.02 °C/yr
71 71  * Operating Range: -40 ~~ 85 °C
72 72  
74 +
75 +
73 73  **Built-in Humidity Sensor:**
74 74  
75 75  * Resolution: 0.04 %RH
... ... @@ -77,6 +77,8 @@
77 77  * Long Term Drift: < 0.02 °C/yr
78 78  * Operating Range: 0 ~~ 96 %RH
79 79  
83 +
84 +
80 80  **External Temperature Sensor:**
81 81  
82 82  * Resolution: 0.0625 °C
... ... @@ -90,6 +90,7 @@
90 90  
91 91  == 2.1 How does LHT65N work? ==
92 92  
98 +
93 93  (((
94 94  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.
95 95  )))
... ... @@ -99,8 +99,10 @@
99 99  )))
100 100  
101 101  
108 +
102 102  == 2.2 How to Activate LHT65N? ==
103 103  
111 +
104 104  (((
105 105  The LHT65N has two working modes:
106 106  )))
... ... @@ -125,6 +125,7 @@
125 125  
126 126  == 2.3 Example to join LoRaWAN network ==
127 127  
136 +
128 128  (% _msthash="315240" _msttexthash="9205482" _mstvisible="1" class="wikigeneratedid" %)
129 129  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.
130 130  
... ... @@ -140,6 +140,7 @@
140 140  
141 141  === 2.3.1 Step 1: Create Device n TTN ===
142 142  
152 +
143 143  (((
144 144  Create a device in TTN V3 with the OTAA keys from LHT65N.
145 145  )))
... ... @@ -164,9 +164,10 @@
164 164  [[image:image-20220522232954-5.png||_mstalt="431847" _mstvisible="3"]]
165 165  
166 166  
167 -Note: LHT65N use same payload as LHT65.
168 168  
178 +(% style="color:red" %)**Note: LHT65N use same payload as LHT65.**
169 169  
180 +
170 170  [[image:image-20220522233026-6.png||_mstalt="429403" _mstvisible="3"]]
171 171  
172 172  
... ... @@ -180,6 +180,7 @@
180 180  
181 181  === 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. ===
182 182  
194 +
183 183  (((
184 184  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.
185 185  )))
... ... @@ -191,6 +191,7 @@
191 191  
192 192  == 2.4 Uplink Payload ==
193 193  
206 +
194 194  (((
195 195  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.
196 196  )))
... ... @@ -265,12 +265,13 @@
265 265  
266 266  * The First 6 bytes: has fix meanings for every LHT65N.
267 267  * The 7th byte (EXT #): defines the external sensor model.
268 -* 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.)
269 269  
270 270  
271 271  
272 272  === 2.4.1 Decoder in TTN V3 ===
273 273  
287 +
274 274  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.
275 275  
276 276  Below is the position to put the decoder and LHT65N decoder can be download from here:
... ... @@ -286,6 +286,7 @@
286 286  
287 287  === 2.4.2 BAT-Battery Info ===
288 288  
303 +
289 289  These two bytes of BAT include the battery state and the actually voltage
290 290  
291 291  [[image:image-20220523152839-18.png||_mstalt="457613" _mstvisible="3"]]
... ... @@ -303,6 +303,7 @@
303 303  
304 304  === 2.4.3 Built-in Temperature ===
305 305  
321 +
306 306  [[image:image-20220522235639-2.png||_mstalt="431756" _mstvisible="3" height="138" width="722"]]
307 307  
308 308  * Temperature:  0x0ABB/100=27.47℃
... ... @@ -315,6 +315,7 @@
315 315  
316 316  === 2.4.4 Built-in Humidity ===
317 317  
334 +
318 318  [[image:image-20220522235639-4.png||_mstalt="432484" _mstvisible="3" height="138" width="722"]]
319 319  
320 320  * Humidity:    0x025C/10=60.4%
... ... @@ -323,6 +323,7 @@
323 323  
324 324  === 2.4.5 Ext # ===
325 325  
343 +
326 326  Bytes for External Sensor:
327 327  
328 328  [[image:image-20220523152822-17.png||_mstalt="454545" _mstvisible="3"]]
... ... @@ -354,6 +354,7 @@
354 354  
355 355  ==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ====
356 356  
375 +
357 357  (((
358 358  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:
359 359  )))
... ... @@ -467,16 +467,19 @@
467 467  
468 468  * (% _msthash="504956" _msttexthash="245037" _mstvisible="4" %)**Status & Ext Byte**
469 469  
470 -[[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)
471 471  
472 -* Poll Message Flag:  1: This message is a poll message reply, 0: means this is a normal uplink.
473 -* 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.
474 -* 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)
475 475  
476 476  
477 477  
478 478  ==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ====
479 479  
501 +
480 480  In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can
481 481  
482 482  be used to power the external ADC sensor; user can control the power on time for this
... ... @@ -524,6 +524,7 @@
524 524  
525 525  == 2.5 Show data on Datacake ==
526 526  
549 +
527 527  (((
528 528  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:
529 529  )))
... ... @@ -571,6 +571,7 @@
571 571  
572 572  == 2.6 Datalog Feature ==
573 573  
597 +
574 574  (((
575 575  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.
576 576  )))
... ... @@ -579,6 +579,7 @@
579 579  
580 580  === 2.6.1 Ways to get datalog via LoRaWAN ===
581 581  
606 +
582 582  There are two methods:
583 583  
584 584  1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specifying time range.
... ... @@ -611,6 +611,7 @@
611 611  
612 612  === 2.6.3 Set Device Time ===
613 613  
639 +
614 614  (((
615 615  There are two ways to set device's time:
616 616  )))
... ... @@ -628,7 +628,7 @@
628 628  )))
629 629  
630 630  (((
631 -(% 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.**
632 632  )))
633 633  
634 634  (((
... ... @@ -647,6 +647,7 @@
647 647  
648 648  === 2.6.4 Poll sensor value ===
649 649  
676 +
650 650  User can poll sensor value based on timestamps from the server. Below is the downlink command.
651 651  
652 652  [[image:image-20220523152302-15.png||_mstalt="451581" _mstvisible="3"]]
... ... @@ -664,6 +664,7 @@
664 664  
665 665  === 2.6.5 Datalog Uplink payload ===
666 666  
694 +
667 667  (% _msthash="315267" _msttexthash="2245087" _mstvisible="1" %)
668 668  The Datalog poll reply uplink will use below payload format.
669 669  
... ... @@ -670,6 +670,9 @@
670 670  (% _mstvisible="1" %)
671 671  (((
672 672  (% _mstvisible="2" %)
701 +
702 +
703 +(% _mstvisible="2" %)
673 673  (% _msthash="506080" _msttexthash="451581" _mstvisible="4" %)**Retrieval data payload**
674 674  )))
675 675  
... ... @@ -797,6 +797,7 @@
797 797  )))
798 798  )))
799 799  
831 +
800 800  (% _mstvisible="1" %)
801 801  (% _msthash="315268" _msttexthash="390390" _mstvisible="3" %)**Poll message flag & Ext**
802 802  
... ... @@ -932,7 +932,7 @@
932 932  (% _mstvisible="1" %)
933 933  (((
934 934  (% _msthash="506083" _msttexthash="737269" _mstvisible="2" style="text-align: left;" %)
935 - 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
936 936  )))
937 937  
938 938  (% _mstvisible="1" %)
... ... @@ -1058,7 +1058,6 @@
1058 1058  * For each success downlink, the PURPLE LED will blink once
1059 1059  
1060 1060  
1061 -
1062 1062  == 2.9 installation ==
1063 1063  
1064 1064  (% _mstvisible="1" %)
... ... @@ -1110,7 +1110,6 @@
1110 1110  * Working voltage 2.35v ~~ 5v
1111 1111  
1112 1112  
1113 -
1114 1114  = 4. Configure LHT65N via AT command or LoRaWAN downlink =
1115 1115  
1116 1116  (((
... ... @@ -1177,7 +1177,6 @@
1177 1177  * **Example 2**: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
1178 1178  
1179 1179  
1180 -
1181 1181  == 4.2 Set External Sensor Mode ==
1182 1182  
1183 1183  Feature: Change External Sensor Mode.
... ... @@ -1200,7 +1200,6 @@
1200 1200  * 0xA20702003c: Same as AT+SETCNT=60
1201 1201  
1202 1202  
1203 -
1204 1204  == 4.3 Enable/Disable uplink Temperature probe ID ==
1205 1205  
1206 1206  (((
... ... @@ -1229,7 +1229,6 @@
1229 1229  * **0xA801**     **~-~->** AT+PID=1
1230 1230  
1231 1231  
1232 -
1233 1233  == 4.4 Set Password ==
1234 1234  
1235 1235  Feature: Set device password, max 9 digits
... ... @@ -1277,7 +1277,6 @@
1277 1277  * There is no downlink command to set to Sleep mode.
1278 1278  
1279 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,7 +1375,6 @@
1375 1375  * Example: 0xA301 ~/~/Same as AT+CLRDTA
1376 1376  
1377 1377  
1378 -
1379 1379  == 4.13 Auto Send None-ACK messages ==
1380 1380  
1381 1381  (% _msthash="315394" _msttexthash="51837149" _mstvisible="1" %)
... ... @@ -1395,7 +1395,6 @@
1395 1395  * Example: 0x3401 ~/~/Same as AT+PNACKMD=1
1396 1396  
1397 1397  
1398 -
1399 1399  = 5. Battery & How to replace =
1400 1400  
1401 1401  == 5.1 Battery Type ==
... ... @@ -1849,7 +1849,6 @@
1849 1849  * (% style="color:red" %)**E3**(%%): External Temperature Probe
1850 1850  
1851 1851  
1852 -
1853 1853  = 8. Packing Info =
1854 1854  
1855 1855  
... ... @@ -1864,13 +1864,11 @@
1864 1864  * Device Weight: 120.5g
1865 1865  
1866 1866  
1867 -
1868 1868  = 9. Reference material =
1869 1869  
1870 1870  * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0||_msthash="504975" _msttexthash="51420512"]]
1871 1871  
1872 1872  
1873 -
1874 1874  = 10. FCC Warning =
1875 1875  
1876 1876  This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions: