Last modified by Xiaoling on 2025/06/10 09:17

From version 1.1
edited by Edwin Chen
on 2023/04/08 23:59
Change comment: There is no comment for this version
To version 8.1
edited by Edwin Chen
on 2023/04/09 08:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -23,41 +23,35 @@
23 23  
24 24  = 1. Introduction =
25 25  
26 -== 1.1 What is LHT65N-E5 Temperature,Humidity&Illuminance Sensor ==
26 +== 1.1 What is LHT65N-PIR Temperature,Humidity & PIR Sensor ==
27 27  
28 +The Dragino (% style="color:blue" %)**LHT65N-PIR Temperature, Humidity & PIR sensor**(%%) is a Long Range LoRaWAN Sensor.It includes a (% style="color:blue" %)**built-in Temperature & Humidity sensor**(%%) and has an (% style="color:blue" %)**external PIR Probe**(%%)**.** LHT65N-PIR can detect environment Temperature & Humdity, it also detects (% style="color:blue" %)**People Activity**(%%) via PIR probe and them send these info to LoRaWAN IoT Server.
28 28  
29 -(((
30 -The Dragino (% style="color:blue" %)**LHT65N-E5 Temperature, Humidity & Illuminance sensor**(%%) is a Long Range LoRaWAN Sensor.It includes a (% style="color:blue" %)**built-in Temperature & Humidity sensor**(%%) and has an (% style="color:blue" %)**external Illuminance **(%%)** (% style="color:blue" %)sensor(%%).**
30 +The LHT65N-PIR allows users to send data and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, building automation, and so on.
31 31  
32 -The LHT65N-E5 allows users to send data and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, building automation, and so on.
32 +LHT65N-PIR has a (% style="color:blue" %)**built-in 2400mAh non-chargeable battery**(%%) which can be used for more than 5 years*.
33 33  
34 -LHT65N-E5 has a (% style="color:blue" %)**built-in 2400mAh non-chargeable battery**(%%) which can be used for more than 10 years*.
34 +LHT65N-PIR supports (% style="color:blue" %)**wireless configure & OTA update**(%%) which make user easy to use.
35 35  
36 -LHT65N-E5 is fully compatible with (% style="color:blue" %)**LoRaWAN v1.0.3 Class A protocol**(%%), it can work with a standard LoRaWAN gateway.
36 +LHT65N-PIR is fully compatible with (% style="color:blue" %)**LoRaWAN v1.0.3 Class A protocol**(%%), it can work with a standard LoRaWAN gateway.
37 37  
38 -(% style="color:blue" %)*(%%)** **The actual battery life depends on how often to send data, please see battery analyzer chapter.
39 -)))
40 40  
41 -(% style="display:none" %) (%%)
39 +**~*~***The actual battery life depends on how often to send data, please see battery analyzer chapter.
42 42  
41 +
43 43  == 1.2 Features ==
44 44  
45 -
46 46  * LoRaWAN v1.0.3 Class A protocol
47 47  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915
48 48  * AT Commands to change parameters
49 49  * Remote configure parameters via LoRaWAN Downlink
48 +* Support wireless OTA update firmware
50 50  * Firmware upgradeable via program port
51 -* Built-in 2400mAh battery for up to 10 years of use.
50 +* Built-in 2400mAh battery for up to 5 years of use.
52 52  * Built-in Temperature & Humidity sensor
53 -* External Illuminance Sensor
54 -* Tri-color LED to indicate working status
55 -* Datalog feature to save sensor data when no LoRaWAN network
52 +* External PIR Sensor
53 +* Tri-color LED to indicate working status(% style="display:none" %)
56 56  
57 -(% style="display:none" %)
58 -
59 -
60 -
61 61  == 1.3 Specification ==
62 62  
63 63  
... ... @@ -75,53 +75,40 @@
75 75  * Long Term Drift: < 0.02 °C/yr
76 76  * Operating Range: 0 ~~ 96 %RH
77 77  
78 -(% style="color:#037691" %)**External IIIuminace Sensor:**
72 +(% class="mark" style="color:#037691" %)**External PIR Sensor:**
79 79  
80 -* Base on BH1750 Illumination Sensor
81 -* Cable Length : 50cm
82 -* Resolution: 1 lx
83 -* Range: 0-65535 lx
84 -* Operating Range: -40 °C ~~ 85 °C
74 +* (% class="mark" %)Base on BH1750 Illumination Sensor
75 +* (% class="mark" %)Cable Length : 50cm
76 +* (% class="mark" %)Resolution: 1 lx
77 +* (% class="mark" %)Range: 0-65535 lx
78 +* (% class="mark" %)Operating Range: -40 °C ~~ 85 °C
79 +*
85 85  
81 += 2. Connect LHT65N-PIR to IoT Server =
86 86  
87 -= 2. Connect LHT65N-E5 to IoT Server =
83 +== 2.1 How does LHT65N-PIR work? ==
88 88  
89 -== 2.1 How does LHT65N-E5 work? ==
85 +LHT65N-PIR is configured as LoRaWAN OTAA Class A sensor by default. Each LHT65N-PIR is shipped with a worldwide unique set of OTAA keys. To use LHT65N-PIR in a LoRaWAN network, first, we need to put the OTAA keys in LoRaWAN Network Server and then activate LHT65N-PIR.
90 90  
87 +If LHT65N-PIR is within the coverage of this LoRaWAN network. LHT65N-PIR can join the LoRaWAN network automatically. After successfully joining, LHT65N-PIR will start to measure environment temperature, humidity & people activity, and start to transmit sensor data to the LoRaWAN server. The default period for each uplink is 20 minutes.
91 91  
92 -(((
93 -LHT65N-E5 is configured as LoRaWAN OTAA Class A sensor by default. Each LHT65N-E5 is shipped with a worldwide unique set of OTAA keys. To use LHT65N-E5 in a LoRaWAN network, first, we need to put the OTAA keys in LoRaWAN Network Server and then activate LHT65N-E5.
94 -)))
95 95  
96 -(((
97 -If LHT65N-E5 is within the coverage of this LoRaWAN network. LHT65N-E5 can join the LoRaWAN network automatically. After successfully joining, LHT65N-E5 will start to measure environment temperature, humidity & illumination, and start to transmit sensor data to the LoRaWAN server. The default period for each uplink is 20 minutes.
98 -)))
90 +== 2.2 How to Activate LHT65N-PIR? ==
99 99  
92 +The LHT65N-PIR has two working modes:
100 100  
101 -== 2.2 How to Activate LHT65N-E5? ==
94 +* (% style="color:blue" %)**Deep Sleep Mode**(%%): LHT65N-PIR doesn't have any LoRaWAN activation. This mode is used for storage and shipping to save battery life.
102 102  
96 +* (% style="color:blue" %)**Working Mode**(%%):  In this mode, LHT65N-PIR works as LoRaWAN Sensor mode to Join LoRaWAN network and send out the sensor data to the server. Between each sampling/tx/rx periodically, LHT65N-PIR will be in STOP mode (IDLE mode), in STOP mode, the PIR sensor is still working to detect people activity in low power consumption.
103 103  
104 -(((
105 -The LHT65N-E5 has two working modes:
106 -)))
98 +The LHT65N-PIR is set in deep sleep mode by default; The ACT button on the front is to switch to different modes:
107 107  
108 -* (((
109 -(% style="color:blue" %)**Deep Sleep Mode**(%%): LHT65N-E5 doesn't have any LoRaWAN activation. This mode is used for storage and shipping to save battery life.
110 -)))
111 -* (((
112 -(% style="color:blue" %)**Working Mode**(%%):  In this mode, LHT65N-E5 works as LoRaWAN Sensor mode to Join LoRaWAN network and send out the sensor data to the server. Between each sampling/tx/rx periodically, LHT65N-E5 will be in STOP mode (IDLE mode), in STOP mode, LHT65N-E5 has the same power consumption as Deep Sleep mode. 
113 -)))
114 114  
115 -(((
116 -The LHT65N-E5 is set in deep sleep mode by default; The ACT button on the front is to switch to different modes:
117 -)))
101 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N-E5%20LoRaWAN%20Temperature_Humidity%20%26%20Illuminance%20Sensor%20User%20Manual/WebHome/image-20220515123819-1.png?width=317&height=379&rev=1.1||alt="image-20220515123819-1.png" height="379" width="317"]]
118 118  
103 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N-E5%20LoRaWAN%20Temperature_Humidity%20%26%20Illuminance%20Sensor%20User%20Manual/WebHome/image-20220525110604-2.png?rev=1.1||alt="image-20220525110604-2.png"]]
119 119  
120 -[[image:image-20220515123819-1.png||_mstalt="430742" height="379" width="317"]]
121 121  
122 -[[image:image-20220525110604-2.png||_mstalt="427531"]]
123 -
124 -
125 125  == 2.3 Example to join LoRaWAN network ==
126 126  
127 127  
... ... @@ -130,24 +130,18 @@
130 130  
131 131  
132 132  (% class="wikigeneratedid" %)
133 -[[image:image-20221224101636-1.png||height="435" width="715"]]
114 +[[image:image-20230409080812-1.png||height="487" width="785"]]
134 134  
135 135  
136 -(((
137 -Assume the LPS8v2 is already set to connect to [[TTN V3 network>>url:https://eu1.cloud.thethings.network||_mstvisible="2"]], So it provides network coverage for LHT65N-E5. Next we need to add the LHT65N-E5 device in TTN V3:
138 -)))
117 +Assume the LPS8v2 is already set to connect to [[TTN V3 network>>url:https://eu1.cloud.thethings.network||_mstvisible="2"]], So it provides network coverage for LHT65N-PIR. Next we need to add the LHT65N-PIR device in TTN V3:
139 139  
140 140  
141 141  === 2.3.1 Step 1: Create Device n TTN ===
142 142  
143 143  
144 -(((
145 -Create a device in TTN V3 with the OTAA keys from LHT65N-E5.
146 -)))
123 +Create a device in TTN V3 with the OTAA keys from LHT65N-PIR.
147 147  
148 -(((
149 -Each LHT65N-E5 is shipped with a sticker with its device EUI, APP Key and APP EUI as below:
150 -)))
125 +Each LHT65N-PIR is shipped with a sticker with its device EUI, APP Key and APP EUI as below:
151 151  
152 152  [[image:image-20220617150003-1.jpeg||_mstalt="5426434"]]
153 153  
... ... @@ -156,7 +156,7 @@
156 156  Add APP EUI in the application.
157 157  
158 158  
159 -[[image:image-20220522232916-3.png||_mstalt="430495"]]
134 +[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522232916-3.png||_mstalt="430495" alt="image-20220522232916-3.png"]]
160 160  
161 161  
162 162  [[image:image-20220522232932-4.png||_mstalt="430157"]]
... ... @@ -166,12 +166,9 @@
166 166  
167 167  
168 168  
169 -(% style="color:red" %)**Note: LHT65N-E5 use same payload decoder as LHT65.**
144 +(% style="color:red" %)**Note: LHT65N-PIR use same payload decoder as LHT65.**
170 170  
171 171  
172 -[[image:image-20220522233026-6.png||_mstalt="429403"]]
173 -
174 -
175 175  Input APP EUI,  APP KEY and DEV EUI:
176 176  
177 177  
... ... @@ -178,26 +178,17 @@
178 178  [[image:image-20220522233118-7.png||_mstalt="430430"]]
179 179  
180 180  
181 -=== 2.3.2 Step 2: Activate LHT65N-E5 by pressing the ACT button for more than 5 seconds. ===
153 +=== 2.3.2 Step 2: Activate LHT65N-PIR by pressing the ACT button for more than 5 seconds. ===
182 182  
183 -
184 -(((
185 -Use ACT button to activate LHT65N-E5 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.
186 -)))
187 -
155 +Use ACT button to activate LHT65N-PIR 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  [[image:image-20220522233300-8.png||_mstalt="428389" height="219" width="722"]]
189 189  
190 190  
191 191  == 2.4 Uplink Payload   ( Fport~=2) ==
192 192  
193 -
194 -(((
195 195  The uplink payload includes totally 11 bytes. Uplink packets use FPORT=2 and (% style="color:#4f81bd" %)**every 20 minutes**(%%) send one uplink by default.
196 -)))
197 197  
198 -(((
199 199  After each uplink, the (% style="color:blue" %)**BLUE LED**(%%) will blink once.
200 -)))
201 201  
202 202  (% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:390px" %)
203 203  |=(% style="width: 60px;" %)(((
... ... @@ -231,18 +231,17 @@
231 231  [[Ext value>>||anchor="H2.4.6Extvalue"]]
232 232  )))
233 233  
234 -* The First 6 bytes: has fix meanings for every LHT65N-E5.
235 -* The 7th byte (EXT #): defines the external sensor model. It can be 0x05 or 0x09 for LHT65N-E5
236 -* The 8^^th^^ ~~ 9^^th^^ byte: Illuminance. Range: 0-65535 lx.
237 -* The 10th ~~ 11th byte: Reserve, always 0xFFFF
197 +* The First 6 bytes: has fix meanings for every LHT65N-PIR.
198 +* The 7th byte (EXT #): defines the external sensor model. It can be (% class="mark" %)0x05 or 0x09(%%) for LHT65N-PIR
199 +* The 7^^th^^ byte: Alarm Bit (if this uplink is from periodically or movement)
200 +* The 8^^th^^ ~~ 11st  byte: Movement Detect Count.
238 238  
239 -
240 240  === 2.4.1 Decoder in TTN V3 ===
241 241  
242 242  
243 -When the uplink payload arrives TTNv3, it shows HEX format and not friendly to read. We can add LHT65N-E5 decoder in TTNv3 for friendly reading.
205 +When the uplink payload arrives TTNv3, it shows HEX format and not friendly to read. We can add LHT65N-PIR decoder in TTNv3 for friendly reading.
244 244  
245 -Below is the position to put the decoder and LHT65N-E5 decoder can be download from here: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]
207 +Below is the position to put the decoder and LHT65N-PIR decoder can be download from here: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]
246 246  
247 247  
248 248  [[image:image-20220522234118-10.png||_mstalt="451464" height="353" width="729"]]
... ... @@ -259,12 +259,11 @@
259 259  [[image:image-20220522235639-1.png||_mstalt="431392" height="139" width="727"]]
260 260  
261 261  
262 -Check the battery voltage for LHT65N-E5.
224 +Check the battery voltage for LHT65N-PIR.
263 263  
264 -* BAT status=(0Xcba4>>14)&0xFF=11(B),very good
226 +* BAT status=(0xcba4>>14)&0xFF=11(B),very good
265 265  * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV
266 266  
267 -
268 268  === 2.4.3 Built-in Temperature ===
269 269  
270 270  
... ... @@ -276,7 +276,6 @@
276 276  
277 277  * Temperature:  (0xF5C6-65536)/100=-26.18℃
278 278  
279 -
280 280  === 2.4.4 Built-in Humidity ===
281 281  
282 282  
... ... @@ -284,7 +284,6 @@
284 284  
285 285  * Humidity:    0x025C/10=60.4%
286 286  
287 -
288 288  === 2.4.5 Ext value ===
289 289  
290 290  ==== 2.4.5.1 Ext~=0x05, Illuminance Sensor ====
... ... @@ -304,72 +304,6 @@
304 304   The last 2 bytes of data are meaningless
305 305  
306 306  
307 -
308 -==== 2.4.5.2 Ext~=0x85, E5 sensor with Unix Timestamp ====
309 -
310 -
311 -(((
312 -Timestamp mode is designed for LHT65N-E5 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:
313 -)))
314 -
315 -(((
316 -
317 -)))
318 -
319 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:535px" %)
320 -|=(% style="width: 88px;" %)(((
321 -**Size(bytes)**
322 -)))|=(% style="width: 93px;" %)(((
323 -**2**
324 -)))|=(% style="width: 94px;" %)(((
325 -**2**
326 -)))|=(% style="width: 117px;" %)(((
327 -**2**
328 -)))|=(% style="width: 54px;" %)(((
329 -**1**
330 -)))|=(% style="width: 79px;" %)(((
331 -**4**
332 -)))
333 -|(% style="width:88px" %)(((
334 -**Value**
335 -)))|(% style="width:93px" %)(((
336 -[[External temperature>>||anchor="H4.2SetExternalSensorMode"]]
337 -)))|(% style="width:94px" %)(((
338 -[[Built-In Temperature>>||anchor="H2.4.3Built-inTemperature"]]
339 -)))|(% style="width:117px" %)(((
340 -BAT Status &
341 -Illumination
342 -)))|(% style="width:54px" %)(((
343 -Status & Ext
344 -)))|(% style="width:79px" %)(((
345 -[[Unix Time Stamp>>||anchor="H2.6.2UnixTimeStamp"]]
346 -)))
347 -
348 -* **Battery status & Built-in Humidity**
349 -
350 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:461px" %)
351 -|=(% style="width: 67px;" %)Bit(bit)|=(% style="width: 256px;" %)[15:14]|=(% style="width: 132px;" %)[11:0]
352 -|(% style="width:67px" %)Value|(% style="width:256px" %)(((
353 -BAT Status
354 -00(b): Ultra Low ( BAT <= 2.50v)
355 -01(b): Low  (2.50v <=BAT <= 2.55v)
356 -10(b): OK   (2.55v <= BAT <=2.65v)
357 -11(b): Good   (BAT >= 2.65v)
358 -)))|(% style="width:132px" %)(((
359 -Illumination
360 -)))
361 -
362 -* **Status & Ext Byte**
363 -
364 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:500px" %)
365 -|=(% scope="row" 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]**
366 -|=(% 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)
367 -
368 -* (% style="color:blue" %)**Poll Message Flag**:(%%)  1: This message is a poll message reply, 0: means this is a normal uplink.
369 -* (% style="color:blue" %)**Sync time OK**: (%%) 1: Set time ok,0: N/A. After time SYNC request is sent, LHT65N-E5 will set this bit to 0 until got the time stamp from the application server.
370 -* (% style="color:blue" %)**Unix Time Request**:(%%)  1: Request server downlink Unix time, 0 : N/A. In this mode, LHT65N-E5 will set this bit to 1 every 10 days to request a time SYNC. (AT+SYNCMOD to set this)
371 -
372 -
373 373  == 2.5 Show data on Datacake ==
374 374  
375 375  
... ... @@ -415,239 +415,11 @@
415 415  [[image:image-20221224161957-6.png||height="306" width="852"]]
416 416  
417 417  
418 -== 2.6 Datalog Feature ==
419 419  
420 -
421 -(((
422 -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-E5 will store the reading for future retrieving purposes. There are two ways for IoT servers to get datalog from LHT65N-E5.
423 -)))
424 -
425 -
426 -=== 2.6.1 Ways to get datalog via LoRaWAN ===
427 -
428 -
429 -There are two methods:
430 -
431 -(% style="color:blue" %)**Method 1:** (%%)IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specified time range.
432 -
433 -
434 -(% style="color:blue" %)**Method 2: **(%%)Set [[PNACKMD=1>>||anchor="H4.13AutoSendNone-ACKmessages"]], LHT65N-E5 will wait for ACK for every uplink, when there is no LoRaWAN network, LHT65N-E5 will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
435 -
436 -
437 -(% style="color:red" %)**Note for method 2:**
438 -
439 -* a) LHT65N-E5 will do an ACK check for data records sending to make sure every data arrive server.
440 -* b) LHT65N-E5 will send data in **CONFIRMED Mode** when PNACKMD=1, but LHT65N-E5 won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink if LHT65N-E5 gets a ACK, LHT65N-E5 will consider there is a network connection and resend all NONE-ACK Message.
441 -
442 -Below is the typical case for the auto-update datalog feature (Set PNACKMD=1)
443 -
444 -
445 -[[image:image-20220703111700-2.png||_mstalt="426244" height="381" width="1119"]]
446 -
447 -
448 -=== 2.6.2 Unix TimeStamp ===
449 -
450 -
451 -LHT65N-E5 uses Unix TimeStamp format based on
452 -
453 -
454 -[[image:image-20220523001219-11.png||_mstalt="450450" height="97" width="627"]]
455 -
456 -
457 -
458 -User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
459 -
460 -Below is the converter example
461 -
462 -[[image:image-20220523001219-12.png||_mstalt="450827" height="298" width="720"]]
463 -
464 -
465 -So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
466 -
467 -
468 -=== 2.6.3 Set Device Time ===
469 -
470 -
471 -(((
472 -(% style="color:blue" %)**There are two ways to set device's time:**
473 -)))
474 -
475 -(((
476 -**1.  Through LoRaWAN MAC Command (Default settings)**
477 -)))
478 -
479 -(((
480 -User need to set SYNCMOD=1 to enable sync time via MAC command.
481 -)))
482 -
483 -(((
484 -Once LHT65N-E5 Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to LHT65N-E5. If LHT65N-E5 fails to get the time from the server, LHT65N-E5 will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
485 -)))
486 -
487 -(((
488 -(% 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.**
489 -)))
490 -
491 -
492 -(((
493 -**2. Manually Set Time**
494 -)))
495 -
496 -(((
497 -User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
498 -)))
499 -
500 -
501 -=== 2.6.4 Poll sensor value ===
502 -
503 -
504 -User can poll sensor value based on timestamps from the server. Below is the downlink command.
505 -
506 -[[image:image-20220523152302-15.png||_mstalt="451581"]]
507 -
508 -
509 -Timestamp start and Timestamp end use Unix TimeStamp format as mentioned above. Devices will reply with all data log during this time period, use the uplink interval.
510 -
511 -For example, downlink command (% _mstmutation="1" %)**31 5FC5F350 5FC6 0160 05**(%%)
512 -
513 -Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00’s data
514 -
515 -Uplink Internal =5s,means LHT65N-E5 will send one packet every 5s. range 5~~255s.
516 -
517 -
518 -=== 2.6.5 Datalog Uplink payload ===
519 -
520 -
521 -The Datalog poll reply uplink will use below payload format.
522 -
523 -**Retrieval data payload:**
524 -
525 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:480px" %)
526 -|=(% style="width: 60px;" %)(((
527 -**Size(bytes)**
528 -)))|=(% style="width: 90px;" %)**2**|=(% style="width: 90px;" %)**2**|=(% style="width: 70px;" %)**2**|=(% style="width: 100px;" %)**1**|=(% style="width: 70px;" %)**4**
529 -|(% style="width:97px" %)**Value**|(% style="width:123px" %)[[External sensor data>>||anchor="H2.4.6Extvalue"]]|(% style="width:108px" %)[[Built In Temperature>>||anchor="H2.4.3Built-inTemperature"]]|(% style="width:133px" %)[[Built-in Humidity>>||anchor="H2.4.4Built-inHumidity"]]|(% style="width:159px" %)Poll message flag & Ext|(% style="width:80px" %)[[Unix Time Stamp>>||anchor="H2.6.2UnixTimeStamp"]]
530 -
531 -**Poll message flag & Ext:**
532 -
533 -[[image:image-20221006192726-1.png||_mstalt="430508" height="112" width="754"]]
534 -
535 -(% style="color:blue" %)**No ACK Message**(%%):  1: This message means this payload is fromn Uplink Message which doesn't get ACK from the server before ( for [[PNACKMD=1>>||anchor="H4.13AutoSendNone-ACKmessages"]] feature)
536 -
537 -(% style="color:blue" %)**Poll Message Flag**(%%): 1: This message is a poll message reply.
538 -
539 -* Poll Message Flag is set to 1.
540 -
541 -* Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands.
542 -
543 -For example, in US915 band, the max payload for different DR is:
544 -
545 -(% style="color:blue" %)**a) DR0:** (%%)max is 11 bytes so one entry of data
546 -
547 -(% style="color:blue" %)**b) DR1:**(%%) max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
548 -
549 -(% style="color:blue" %)**c) DR2:**(%%) total payload includes 11 entries of data
550 -
551 -(% style="color:blue" %)**d) DR3: **(%%)total payload includes 22 entries of data.
552 -
553 -If devise doesn't have any data in the polling time. Device will uplink 11 bytes of 0   
554 -
555 -
556 -**Example:**
557 -
558 -If LHT65N-E5 has below data inside Flash:
559 -
560 -[[image:image-20220523144455-1.png||_mstalt="430040" height="335" width="735"]]
561 -
562 -
563 -If user sends below downlink command: (% style="background-color:yellow" %)3160065F9760066DA705
564 -
565 -Where : Start time: 60065F97 = time 21/1/19 04:27:03
566 -
567 - Stop time: 60066DA7= time 21/1/19 05:27:03
568 -
569 -
570 -**LHT65N-E5 will uplink this payload.**
571 -
572 -[[image:image-20220523001219-13.png||_mstalt="451204" height="421" style="text-align:left" width="727"]]
573 -
574 -
575 -__**7FFF089801464160065F97**__ **__7FFF__ __088E__ __014B__ __41__ __60066009__** 7FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E
576 -
577 -Where the first 11 bytes is for the first entry:
578 -
579 -7FFF089801464160065F97
580 -
581 -Ext sensor data=0x7FFF/100=327.67
582 -
583 -Temp=0x088E/100=22.00
584 -
585 -Hum=0x014B/10=32.6
586 -
587 -poll message flag & Ext=0x41,means reply data,Ext=1
588 -
589 -Unix time is 0x60066009=1611030423s=21/1/19 04:27:03
590 -
591 -
592 -== 2.7 Alarm Mode ==
593 -
594 -(((
595 -
596 -
597 -when the device is in alarm mode, it checks the built-in sensor temperature for a short time. if the temperature exceeds the preconfigured range, it sends an uplink immediately.
598 -)))
599 -
600 -(((
601 -(% style="color:red" %)**Note: alarm mode adds a little power consumption, and we recommend extending the normal read time when this feature is enabled.**
602 -
603 -
604 -)))
605 -
606 -=== 2.7.1 ALARM MODE ===
607 -
608 -
609 -(% class="box infomessage" %)
610 -(((
611 -(((
612 -**AT+WMOD=1**:  Enable/disable alarm mode. (0: Disabled, 1: Enabled Temperature Alarm for onboard temperature sensor)
613 -)))
614 -
615 -(((
616 -**AT+CITEMP=1**:  The interval between checking the alarm temperature. (In minutes)
617 -)))
618 -
619 -(((
620 -**AT+ARTEMP**:  Gets or sets the alarm range of the internal temperature sensor
621 -)))
622 -
623 -(((
624 -(% _mstmutation="1" %)**AT+ARTEMP=? **(%%):  Gets the alarm range of the internal temperature sensor(% style="display:none" %)
625 -)))
626 -
627 -(((
628 -**AT+ARTEMP=45,105**:  Set the internal temperature sensor alarm range from 45 to 105.
629 -)))
630 -)))
631 -
632 -(% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX**
633 -
634 -Total bytes: 8 bytes
635 -
636 -**Example:**AA0100010001003C
637 -
638 -WMOD=01
639 -
640 -CITEMP=0001
641 -
642 -TEMPlow=0001
643 -
644 -TEMPhigh=003C
645 -
646 -
647 647  == 2.8 LED Indicator ==
648 648  
649 649  
650 -The LHT65 has a triple color LED which for easy showing different stage .
315 +The LHT65N-PIR has a triple color LED which for easy showing different stage .
651 651  
652 652  While user press ACT button, the LED will work as per LED status with ACT button.
653 653  
... ... @@ -658,7 +658,6 @@
658 658  * RED LED when external sensor is not connected
659 659  * For each success downlink, the PURPLE LED will blink once
660 660  
661 -
662 662  == 2.9 installation ==
663 663  
664 664  
... ... @@ -679,19 +679,13 @@
679 679  Use for AT Command
680 680  )))
681 681  * (((
682 -Update firmware for LHT65N-E5
346 +Update firmware for LHT65N-PIR
683 683  )))
684 -* (((
685 -Exposed All pins from the LHT65N Type-C connector.
686 686  
687 -
688 -
689 -)))
690 -
691 691  [[image:image-20220619092421-3.png||_mstalt="430547" height="371" width="529"]]
692 692  
693 693  
694 -= 4. Configure LHT65N-E5 via AT command or LoRaWAN downlink =
352 += 4. Configure LHT65N-PIR via AT command or LoRaWAN downlink =
695 695  
696 696  
697 697  (((
... ... @@ -759,7 +759,6 @@
759 759  
760 760  * **Example 2**: Downlink Payload: 0100003C  ~/~/ Set Transmit Interval (TDC) = 60 seconds
761 761  
762 -
763 763  == 4.2 Currently only supports E5 ==
764 764  
765 765  
... ... @@ -786,7 +786,6 @@
786 786  
787 787  * 0xA205: Set external sensor type to E5
788 788  
789 -
790 790  == 4.3 Set to sleep mode ==
791 791  
792 792  
... ... @@ -805,129 +805,6 @@
805 805  * There is no downlink command to set to Sleep mode.
806 806  
807 807  
808 -== 4.4 Set system time ==
809 -
810 -
811 -Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]]
812 -
813 -
814 -(% style="color:#4f81bd" %)**AT Command:**
815 -
816 -[[image:image-20220523151253-8.png||_mstalt="430677"]]
817 -
818 -
819 -(% style="color:#4f81bd" %)**Downlink Command:**
820 -
821 -0x306007806000  ~/~/  Set timestamp to 0x(6007806000),Same as AT+TIMESTAMP=1611104352
822 -
823 -
824 -== 4.5 Set Time Sync Mode ==
825 -
826 -
827 -(((
828 -Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply this command.
829 -)))
830 -
831 -(((
832 -SYNCMOD is set to 1 by default. If user want to set a different time from LoRaWAN server, user need to set this to 0.
833 -
834 -
835 -)))
836 -
837 -(% style="color:#4f81bd" %)**AT Command:**
838 -
839 -[[image:image-20220523151336-9.png||_mstalt="431717"]]
840 -
841 -
842 -(% style="color:#4f81bd" %)**Downlink Command:**
843 -
844 -0x28 01  ~/~/  Same As AT+SYNCMOD=1
845 -0x28 00  ~/~/  Same As AT+SYNCMOD=0
846 -
847 -
848 -== 4.6 Set Time Sync Interval ==
849 -
850 -
851 -Feature: Define System time sync interval. SYNCTDC default value: 10 days.
852 -
853 -
854 -(% style="color:#4f81bd" %)**AT Command:**
855 -
856 -[[image:image-20220523151411-10.png||_mstalt="449696"]]
857 -
858 -
859 -(% style="color:#4f81bd" %)**Downlink Command:**
860 -
861 -**0x29 0A**  ~/~/ Same as AT+SYNCTDC=0x0A
862 -
863 -
864 -== 4.7 Print data entries base on page. ==
865 -
866 -
867 -Feature: Print the sector data from start page to stop page (max is 416 pages).
868 -
869 -
870 -(% style="color:#4f81bd" %)**AT Command: AT+PDTA**
871 -
872 -[[image:image-20220523151450-11.png||_mstalt="451035"]]
873 -
874 -
875 -(% style="color:#4f81bd" %)**Downlink Command:**
876 -
877 -No downlink commands for feature
878 -
879 -
880 -== 4.8 Print last few data entries. ==
881 -
882 -
883 -Feature: Print the last few data entries
884 -
885 -
886 -(% style="color:#4f81bd" %)**AT Command: AT+PLDTA**
887 -
888 -[[image:image-20220523151524-12.png||_mstalt="452101"]]
889 -
890 -
891 -(% style="color:#4f81bd" %)**Downlink Command:**
892 -
893 -No downlink commands for feature
894 -
895 -
896 -== 4.9 Clear Flash Record ==
897 -
898 -
899 -Feature: Clear flash storage for data log feature.
900 -
901 -
902 -(% style="color:#4f81bd" %)**AT Command: AT+CLRDTA**
903 -
904 -[[image:image-20220523151556-13.png||_mstalt="454129"]]
905 -
906 -
907 -(% style="color:#4f81bd" %)**Downlink Command: 0xA3**
908 -
909 -* Example: 0xA301  ~/~/  Same as AT+CLRDTA
910 -
911 -
912 -== 4.10 Auto Send None-ACK messages ==
913 -
914 -
915 -Feature: LHT65N-E5 will wait for ACK for each uplink, If LHT65N-E5 doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. LHT65N-E5 keeps sending messages in normal periodically. Once LHT65N-E5 gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
916 -
917 -
918 -(% style="color:#4f81bd" %)**AT Command: AT+PNACKMD**
919 -
920 -The default factory setting is 0
921 -
922 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:367px" %)
923 -|=(% style="width: 158px;" %)**Command Example**|=(% style="width: 118px;" %)**Function**|=(% style="width: 87px;" %)**Response**
924 -|(% style="width:158px" %)AT+PNACKMD=1|(% style="width:118px" %)Poll None-ACK message|(% style="width:87px" %)OK
925 -
926 -(% style="color:#4f81bd" %)**Downlink Command: 0x34**
927 -
928 -* Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
929 -
930 -
931 931  = 5. Battery & How to replace =
932 932  
933 933  == 5.1 Battery Type ==
... ... @@ -1232,7 +1232,6 @@
1232 1232  * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**IN865**(%%): LoRaWAN IN865 band
1233 1233  * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1234 1234  
1235 -
1236 1236  = 8. Packing Info =
1237 1237  
1238 1238  
... ... @@ -1245,13 +1245,11 @@
1245 1245  * Device Size:  10 x 10 x 3.5 mm
1246 1246  * Device Weight: 120.5g
1247 1247  
1248 -
1249 1249  = 9. Reference material =
1250 1250  
1251 1251  
1252 1252  * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0]]
1253 1253  
1254 -
1255 1255  = 10. FCC Warning =
1256 1256  
1257 1257  
... ... @@ -1260,5 +1260,3 @@
1260 1260  (1) This device may not cause harmful interference;
1261 1261  
1262 1262  (2) this device must accept any interference received, including interference that may cause undesired operation.
1263 -
1264 -
image-20230409080812-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +249.6 KB
Content