Last modified by Xiaoling on 2025/04/24 10:00
<
From version < 2.1 >
edited by Edwin Chen
on 2023/04/09 00:08
To version < 6.1 >
edited by Edwin Chen
on 2023/04/09 00:33
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -35,28 +35,23 @@
35 35  
36 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 -**The actual battery life depends on how often to send data, please see battery analyzer chapter.
39 39  
39 +**~*~***The actual battery life depends on how often to send data, please see battery analyzer chapter.
40 40  
41 41  
42 42  == 1.2 Features ==
43 43  
44 -
45 45  * LoRaWAN v1.0.3 Class A protocol
46 46  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915
47 47  * AT Commands to change parameters
48 48  * Remote configure parameters via LoRaWAN Downlink
48 +* Support wireless OTA update firmware
49 49  * Firmware upgradeable via program port
50 -* Built-in 2400mAh battery for up to 10 years of use.
50 +* Built-in 2400mAh battery for up to 5 years of use.
51 51  * Built-in Temperature & Humidity sensor
52 -* External Illuminance Sensor
53 -* Tri-color LED to indicate working status
54 -* 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" %)
55 55  
56 -(% style="display:none" %)
57 -
58 -
59 -
60 60  == 1.3 Specification ==
61 61  
62 62  
... ... @@ -74,52 +74,39 @@
74 74  * Long Term Drift: < 0.02 °C/yr
75 75  * Operating Range: 0 ~~ 96 %RH
76 76  
77 -(% style="color:#037691" %)**External IIIuminace Sensor:**
72 +(% class="mark" style="color:#037691" %)**External PIR Sensor:**
78 78  
79 -* Base on BH1750 Illumination Sensor
80 -* Cable Length : 50cm
81 -* Resolution: 1 lx
82 -* Range: 0-65535 lx
83 -* 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
84 84  
85 -= 2. Connect LHT65N-E5 to IoT Server =
80 += 2. Connect LHT65N-PIR to IoT Server =
86 86  
87 -== 2.1 How does LHT65N-E5 work? ==
82 +== 2.1 How does LHT65N-PIR work? ==
88 88  
84 +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.
89 89  
90 -(((
91 -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.
92 -)))
86 +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.
93 93  
94 -(((
95 -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.
96 -)))
97 97  
89 +== 2.2 How to Activate LHT65N-PIR? ==
98 98  
99 -== 2.2 How to Activate LHT65N-E5? ==
91 +The LHT65N-PIR has two working modes:
100 100  
93 +* (% 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.
101 101  
102 -(((
103 -The LHT65N-E5 has two working modes:
104 -)))
95 +* (% 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.
105 105  
106 -* (((
107 -(% 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.
108 -)))
109 -* (((
110 -(% 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. 
111 -)))
97 +The LHT65N-PIR is set in deep sleep mode by default; The ACT button on the front is to switch to different modes:
112 112  
113 -(((
114 -The LHT65N-E5 is set in deep sleep mode by default; The ACT button on the front is to switch to different modes:
115 -)))
116 116  
100 +[[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"]]
117 117  
118 -[[image:image-20220515123819-1.png||_mstalt="430742" height="379" width="317"]]
102 +[[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-20220525110604-2.png||_mstalt="427531"]]
121 121  
122 -
123 123  == 2.3 Example to join LoRaWAN network ==
124 124  
125 125  
... ... @@ -131,21 +131,15 @@
131 131  [[image:image-20221224101636-1.png||height="435" width="715"]]
132 132  
133 133  
134 -(((
135 -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:
136 -)))
116 +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:
137 137  
138 138  
139 139  === 2.3.1 Step 1: Create Device n TTN ===
140 140  
141 141  
142 -(((
143 -Create a device in TTN V3 with the OTAA keys from LHT65N-E5.
144 -)))
122 +Create a device in TTN V3 with the OTAA keys from LHT65N-PIR.
145 145  
146 -(((
147 -Each LHT65N-E5 is shipped with a sticker with its device EUI, APP Key and APP EUI as below:
148 -)))
124 +Each LHT65N-PIR is shipped with a sticker with its device EUI, APP Key and APP EUI as below:
149 149  
150 150  [[image:image-20220617150003-1.jpeg||_mstalt="5426434"]]
151 151  
... ... @@ -164,12 +164,9 @@
164 164  
165 165  
166 166  
167 -(% style="color:red" %)**Note: LHT65N-E5 use same payload decoder as LHT65.**
143 +(% style="color:red" %)**Note: LHT65N-PIR use same payload decoder as LHT65.**
168 168  
169 169  
170 -[[image:image-20220522233026-6.png||_mstalt="429403"]]
171 -
172 -
173 173  Input APP EUI,  APP KEY and DEV EUI:
174 174  
175 175  
... ... @@ -176,26 +176,17 @@
176 176  [[image:image-20220522233118-7.png||_mstalt="430430"]]
177 177  
178 178  
179 -=== 2.3.2 Step 2: Activate LHT65N-E5 by pressing the ACT button for more than 5 seconds. ===
152 +=== 2.3.2 Step 2: Activate LHT65N-PIR by pressing the ACT button for more than 5 seconds. ===
180 180  
181 -
182 -(((
183 -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.
184 -)))
185 -
154 +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.
186 186  [[image:image-20220522233300-8.png||_mstalt="428389" height="219" width="722"]]
187 187  
188 188  
189 189  == 2.4 Uplink Payload   ( Fport~=2) ==
190 190  
191 -
192 -(((
193 193  The uplink payload includes totally 11 bytes. Uplink packets use FPORT=2 and (% style="color:#4f81bd" %)**every 20 minutes**(%%) send one uplink by default.
194 -)))
195 195  
196 -(((
197 197  After each uplink, the (% style="color:blue" %)**BLUE LED**(%%) will blink once.
198 -)))
199 199  
200 200  (% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:390px" %)
201 201  |=(% style="width: 60px;" %)(((
... ... @@ -229,17 +229,17 @@
229 229  [[Ext value>>||anchor="H2.4.6Extvalue"]]
230 230  )))
231 231  
232 -* The First 6 bytes: has fix meanings for every LHT65N-E5.
233 -* The 7th byte (EXT #): defines the external sensor model. It can be 0x05 or 0x09 for LHT65N-E5
234 -* The 8^^th^^ ~~ 9^^th^^ byte: Illuminance. Range: 0-65535 lx.
235 -* The 10th ~~ 11th byte: Reserve, always 0xFFFF
196 +* The First 6 bytes: has fix meanings for every LHT65N-PIR.
197 +* The 7th byte (EXT #): defines the external sensor model. It can be (% class="mark" %)0x05 or 0x09(%%) for LHT65N-PIR
198 +* The 7^^th^^ byte: Alarm Bit (if this uplink is from periodically or movement)
199 +* The 8^^th^^ ~~ 11st  byte: Movement Detect Count.
236 236  
237 237  === 2.4.1 Decoder in TTN V3 ===
238 238  
239 239  
240 -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.
204 +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.
241 241  
242 -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]]
206 +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]]
243 243  
244 244  
245 245  [[image:image-20220522234118-10.png||_mstalt="451464" height="353" width="729"]]
... ... @@ -256,11 +256,12 @@
256 256  [[image:image-20220522235639-1.png||_mstalt="431392" height="139" width="727"]]
257 257  
258 258  
259 -Check the battery voltage for LHT65N-E5.
223 +Check the battery voltage for LHT65N-PIR.
260 260  
261 -* BAT status=(0Xcba4>>14)&0xFF=11(B)，very good
225 +* BAT status=(0xcba4>>14)&0xFF=11(B)，very good
262 262  * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV
263 263  
228 +
264 264  === 2.4.3 Built-in Temperature ===
265 265  
266 266  
... ... @@ -298,71 +298,6 @@
298 298   The last 2 bytes of data are meaningless
299 299  
300 300  
301 -
302 -==== 2.4.5.2 Ext~=0x85, E5 sensor with Unix Timestamp ====
303 -
304 -
305 -(((
306 -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:
307 -)))
308 -
309 -(((
310 -
311 -)))
312 -
313 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:535px" %)
314 -|=(% style="width: 88px;" %)(((
315 -**Size(bytes)**
316 -)))|=(% style="width: 93px;" %)(((
317 -**2**
318 -)))|=(% style="width: 94px;" %)(((
319 -**2**
320 -)))|=(% style="width: 117px;" %)(((
321 -**2**
322 -)))|=(% style="width: 54px;" %)(((
323 -**1**
324 -)))|=(% style="width: 79px;" %)(((
325 -**4**
326 -)))
327 -|(% style="width:88px" %)(((
328 -**Value**
329 -)))|(% style="width:93px" %)(((
330 -[[External temperature>>||anchor="H4.2SetExternalSensorMode"]]
331 -)))|(% style="width:94px" %)(((
332 -[[Built-In Temperature>>||anchor="H2.4.3Built-inTemperature"]]
333 -)))|(% style="width:117px" %)(((
334 -BAT Status &
335 -Illumination
336 -)))|(% style="width:54px" %)(((
337 -Status & Ext
338 -)))|(% style="width:79px" %)(((
339 -[[Unix Time Stamp>>||anchor="H2.6.2UnixTimeStamp"]]
340 -)))
341 -
342 -* **Battery status & Built-in Humidity**
343 -
344 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:461px" %)
345 -|=(% style="width: 67px;" %)Bit(bit)|=(% style="width: 256px;" %)[15:14]|=(% style="width: 132px;" %)[11:0]
346 -|(% style="width:67px" %)Value|(% style="width:256px" %)(((
347 -BAT Status
348 -00(b): Ultra Low ( BAT <= 2.50v)
349 -01(b): Low  (2.50v <=BAT <= 2.55v)
350 -10(b): OK   (2.55v <= BAT <=2.65v)
351 -11(b): Good   (BAT >= 2.65v)
352 -)))|(% style="width:132px" %)(((
353 -Illumination
354 -)))
355 -
356 -* **Status & Ext Byte**
357 -
358 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:500px" %)
359 -|=(% 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]**
360 -|=(% 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)
361 -
362 -* (% style="color:blue" %)**Poll Message Flag**:(%%)  1: This message is a poll message reply, 0: means this is a normal uplink.
363 -* (% 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.
364 -* (% 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)
365 -
366 366  == 2.5 Show data on Datacake ==
367 367  
368 368  
... ... @@ -408,239 +408,11 @@
408 408  [[image:image-20221224161957-6.png||height="306" width="852"]]
409 409  
410 410  
411 -== 2.6 Datalog Feature ==
412 412  
413 -
414 -(((
415 -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.
416 -)))
417 -
418 -
419 -=== 2.6.1 Ways to get datalog via LoRaWAN ===
420 -
421 -
422 -There are two methods:
423 -
424 -(% style="color:blue" %)**Method 1:** (%%)IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specified time range.
425 -
426 -
427 -(% 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.
428 -
429 -
430 -(% style="color:red" %)**Note for method 2:**
431 -
432 -* a) LHT65N-E5 will do an ACK check for data records sending to make sure every data arrive server.
433 -* 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.
434 -
435 -Below is the typical case for the auto-update datalog feature (Set PNACKMD=1)
436 -
437 -
438 -[[image:image-20220703111700-2.png||_mstalt="426244" height="381" width="1119"]]
439 -
440 -
441 -=== 2.6.2 Unix TimeStamp ===
442 -
443 -
444 -LHT65N-E5 uses Unix TimeStamp format based on
445 -
446 -
447 -[[image:image-20220523001219-11.png||_mstalt="450450" height="97" width="627"]]
448 -
449 -
450 -
451 -User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
452 -
453 -Below is the converter example
454 -
455 -[[image:image-20220523001219-12.png||_mstalt="450827" height="298" width="720"]]
456 -
457 -
458 -So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
459 -
460 -
461 -=== 2.6.3 Set Device Time ===
462 -
463 -
464 -(((
465 -(% style="color:blue" %)**There are two ways to set device's time:**
466 -)))
467 -
468 -(((
469 -**1.  Through LoRaWAN MAC Command (Default settings)**
470 -)))
471 -
472 -(((
473 -User need to set SYNCMOD=1 to enable sync time via MAC command.
474 -)))
475 -
476 -(((
477 -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).
478 -)))
479 -
480 -(((
481 -(% 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.**
482 -)))
483 -
484 -
485 -(((
486 -**2. Manually Set Time**
487 -)))
488 -
489 -(((
490 -User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
491 -)))
492 -
493 -
494 -=== 2.6.4 Poll sensor value ===
495 -
496 -
497 -User can poll sensor value based on timestamps from the server. Below is the downlink command.
498 -
499 -[[image:image-20220523152302-15.png||_mstalt="451581"]]
500 -
501 -
502 -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.
503 -
504 -For example, downlink command (% _mstmutation="1" %)**31 5FC5F350 5FC6 0160 05**(%%)
505 -
506 -Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00’s data
507 -
508 -Uplink Internal =5s，means LHT65N-E5 will send one packet every 5s. range 5~~255s.
509 -
510 -
511 -=== 2.6.5 Datalog Uplink payload ===
512 -
513 -
514 -The Datalog poll reply uplink will use below payload format.
515 -
516 -**Retrieval data payload:**
517 -
518 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:480px" %)
519 -|=(% style="width: 60px;" %)(((
520 -**Size(bytes)**
521 -)))|=(% style="width: 90px;" %)**2**|=(% style="width: 90px;" %)**2**|=(% style="width: 70px;" %)**2**|=(% style="width: 100px;" %)**1**|=(% style="width: 70px;" %)**4**
522 -|(% 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"]]
523 -
524 -**Poll message flag & Ext:**
525 -
526 -[[image:image-20221006192726-1.png||_mstalt="430508" height="112" width="754"]]
527 -
528 -(% 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)
529 -
530 -(% style="color:blue" %)**Poll Message Flag**(%%): 1: This message is a poll message reply.
531 -
532 -* Poll Message Flag is set to 1.
533 -
534 -* Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands.
535 -
536 -For example, in US915 band, the max payload for different DR is:
537 -
538 -(% style="color:blue" %)**a) DR0:** (%%)max is 11 bytes so one entry of data
539 -
540 -(% style="color:blue" %)**b) DR1:**(%%) max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
541 -
542 -(% style="color:blue" %)**c) DR2:**(%%) total payload includes 11 entries of data
543 -
544 -(% style="color:blue" %)**d) DR3: **(%%)total payload includes 22 entries of data.
545 -
546 -If devise doesn't have any data in the polling time. Device will uplink 11 bytes of 0   
547 -
548 -
549 -**Example:**
550 -
551 -If LHT65N-E5 has below data inside Flash:
552 -
553 -[[image:image-20220523144455-1.png||_mstalt="430040" height="335" width="735"]]
554 -
555 -
556 -If user sends below downlink command: (% style="background-color:yellow" %)3160065F9760066DA705
557 -
558 -Where : Start time: 60065F97 = time 21/1/19 04:27:03
559 -
560 - Stop time: 60066DA7= time 21/1/19 05:27:03
561 -
562 -
563 -**LHT65N-E5 will uplink this payload.**
564 -
565 -[[image:image-20220523001219-13.png||_mstalt="451204" height="421" style="text-align:left" width="727"]]
566 -
567 -
568 -__**7FFF089801464160065F97**__ **__7FFF__ __088E__ __014B__ __41__ __60066009__** 7FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E
569 -
570 -Where the first 11 bytes is for the first entry:
571 -
572 -7FFF089801464160065F97
573 -
574 -Ext sensor data=0x7FFF/100=327.67
575 -
576 -Temp=0x088E/100=22.00
577 -
578 -Hum=0x014B/10=32.6
579 -
580 -poll message flag & Ext=0x41,means reply data,Ext=1
581 -
582 -Unix time is 0x60066009=1611030423s=21/1/19 04:27:03
583 -
584 -
585 -== 2.7 Alarm Mode ==
586 -
587 -(((
588 -
589 -
590 -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.
591 -)))
592 -
593 -(((
594 -(% style="color:red" %)**Note: alarm mode adds a little power consumption, and we recommend extending the normal read time when this feature is enabled.**
595 -
596 -
597 -)))
598 -
599 -=== 2.7.1 ALARM MODE ===
600 -
601 -
602 -(% class="box infomessage" %)
603 -(((
604 -(((
605 -**AT+WMOD=1**:  Enable/disable alarm mode. (0: Disabled, 1: Enabled Temperature Alarm for onboard temperature sensor)
606 -)))
607 -
608 -(((
609 -**AT+CITEMP=1**:  The interval between checking the alarm temperature. (In minutes)
610 -)))
611 -
612 -(((
613 -**AT+ARTEMP**:  Gets or sets the alarm range of the internal temperature sensor
614 -)))
615 -
616 -(((
617 -(% _mstmutation="1" %)**AT+ARTEMP=？ **(%%):  Gets the alarm range of the internal temperature sensor(% style="display:none" %)
618 -)))
619 -
620 -(((
621 -**AT+ARTEMP=45,105**:  Set the internal temperature sensor alarm range from 45 to 105.
622 -)))
623 -)))
624 -
625 -(% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX**
626 -
627 -Total bytes: 8 bytes
628 -
629 -**Example:**AA0100010001003C
630 -
631 -WMOD=01
632 -
633 -CITEMP=0001
634 -
635 -TEMPlow=0001
636 -
637 -TEMPhigh=003C
638 -
639 -
640 640  == 2.8 LED Indicator ==
641 641  
642 642  
643 -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 .
644 644  
645 645  While user press ACT button, the LED will work as per LED status with ACT button.
646 646  
... ... @@ -651,6 +651,7 @@
651 651  * RED LED when external sensor is not connected
652 652  * For each success downlink, the PURPLE LED will blink once
653 653  
326 +
654 654  == 2.9 installation ==
655 655  
656 656  
... ... @@ -671,19 +671,13 @@
671 671  Use for AT Command
672 672  )))
673 673  * (((
674 -Update firmware for LHT65N-E5
347 +Update firmware for LHT65N-PIR
675 675  )))
676 -* (((
677 -Exposed All pins from the LHT65N Type-C connector.
678 678  
679 -
680 -
681 -)))
682 -
683 683  [[image:image-20220619092421-3.png||_mstalt="430547" height="371" width="529"]]
684 684  
685 685  
686 -= 4. Configure LHT65N-E5 via AT command or LoRaWAN downlink =
353 += 4. Configure LHT65N-PIR via AT command or LoRaWAN downlink =
687 687  
688 688  
689 689  (((
... ... @@ -794,127 +794,8 @@
794 794  
795 795  * There is no downlink command to set to Sleep mode.
796 796  
797 -== 4.4 Set system time ==
798 -
799 -
800 -Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]]
801 -
802 -
803 -(% style="color:#4f81bd" %)**AT Command:**
804 -
805 -[[image:image-20220523151253-8.png||_mstalt="430677"]]
806 -
807 -
808 -(% style="color:#4f81bd" %)**Downlink Command:**
809 -
810 -0x306007806000  ~/~/  Set timestamp to 0x(6007806000),Same as AT+TIMESTAMP=1611104352
811 -
812 -
813 -== 4.5 Set Time Sync Mode ==
814 -
815 -
816 -(((
817 -Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply this command.
818 -)))
819 -
820 -(((
821 -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.
822 -
823 823  
824 -)))
825 825  
826 -(% style="color:#4f81bd" %)**AT Command:**
827 -
828 -[[image:image-20220523151336-9.png||_mstalt="431717"]]
829 -
830 -
831 -(% style="color:#4f81bd" %)**Downlink Command:**
832 -
833 -0x28 01  ~/~/  Same As AT+SYNCMOD=1
834 -0x28 00  ~/~/  Same As AT+SYNCMOD=0
835 -
836 -
837 -== 4.6 Set Time Sync Interval ==
838 -
839 -
840 -Feature: Define System time sync interval. SYNCTDC default value: 10 days.
841 -
842 -
843 -(% style="color:#4f81bd" %)**AT Command:**
844 -
845 -[[image:image-20220523151411-10.png||_mstalt="449696"]]
846 -
847 -
848 -(% style="color:#4f81bd" %)**Downlink Command:**
849 -
850 -**0x29 0A**  ~/~/ Same as AT+SYNCTDC=0x0A
851 -
852 -
853 -== 4.7 Print data entries base on page. ==
854 -
855 -
856 -Feature: Print the sector data from start page to stop page (max is 416 pages).
857 -
858 -
859 -(% style="color:#4f81bd" %)**AT Command: AT+PDTA**
860 -
861 -[[image:image-20220523151450-11.png||_mstalt="451035"]]
862 -
863 -
864 -(% style="color:#4f81bd" %)**Downlink Command:**
865 -
866 -No downlink commands for feature
867 -
868 -
869 -== 4.8 Print last few data entries. ==
870 -
871 -
872 -Feature: Print the last few data entries
873 -
874 -
875 -(% style="color:#4f81bd" %)**AT Command: AT+PLDTA**
876 -
877 -[[image:image-20220523151524-12.png||_mstalt="452101"]]
878 -
879 -
880 -(% style="color:#4f81bd" %)**Downlink Command:**
881 -
882 -No downlink commands for feature
883 -
884 -
885 -== 4.9 Clear Flash Record ==
886 -
887 -
888 -Feature: Clear flash storage for data log feature.
889 -
890 -
891 -(% style="color:#4f81bd" %)**AT Command: AT+CLRDTA**
892 -
893 -[[image:image-20220523151556-13.png||_mstalt="454129"]]
894 -
895 -
896 -(% style="color:#4f81bd" %)**Downlink Command: 0xA3**
897 -
898 -* Example: 0xA301  ~/~/  Same as AT+CLRDTA
899 -
900 -== 4.10 Auto Send None-ACK messages ==
901 -
902 -
903 -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.
904 -
905 -
906 -(% style="color:#4f81bd" %)**AT Command: AT+PNACKMD**
907 -
908 -The default factory setting is 0
909 -
910 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:367px" %)
911 -|=(% style="width: 158px;" %)**Command Example**|=(% style="width: 118px;" %)**Function**|=(% style="width: 87px;" %)**Response**
912 -|(% style="width:158px" %)AT+PNACKMD=1|(% style="width:118px" %)Poll None-ACK message|(% style="width:87px" %)OK
913 -
914 -(% style="color:#4f81bd" %)**Downlink Command: 0x34**
915 -
916 -* Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
917 -
918 918  = 5. Battery & How to replace =
919 919  
920 920  == 5.1 Battery Type ==

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0