Changes for page LHT65N-PIR Temperature/Humidity/PIR Motion Sensor User Manual
Last modified by Xiaoling on 2025/04/24 10:00
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -52,7 +52,6 @@ 52 52 * External PIR Sensor 53 53 * Tri-color LED to indicate working status(% style="display:none" %) 54 54 55 - 56 56 == 1.3 Specification == 57 57 58 58 ... ... @@ -78,7 +78,6 @@ 78 78 * (% class="mark" %)Range: 0-65535 lx 79 79 * (% class="mark" %)Operating Range: -40 °C ~~ 85 °C 80 80 81 - 82 82 = 2. Connect LHT65N-PIR to IoT Server = 83 83 84 84 == 2.1 How does LHT65N-PIR work? == ... ... @@ -90,20 +90,18 @@ 90 90 91 91 == 2.2 How to Activate LHT65N-PIR? == 92 92 93 -The LHT65N- E5has two working modes:91 +The LHT65N-PIR has two working modes: 94 94 95 -* 96 -(% 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. 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. 97 97 98 -* 99 -(% 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. 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. 100 100 101 -The LHT65N- E5is set in deep sleep mode by default; The ACT button on the front is to switch to different modes:97 +The LHT65N-PIR is set in deep sleep mode by default; The ACT button on the front is to switch to different modes: 102 102 103 103 104 -[[image:image-20220515123819-1.png|| _mstalt="430742" height="379" width="317"]]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"]] 105 105 106 -[[image:image-20220525110604-2.png|| _mstalt="427531"]]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"]] 107 107 108 108 109 109 == 2.3 Example to join LoRaWAN network == ... ... @@ -117,21 +117,15 @@ 117 117 [[image:image-20221224101636-1.png||height="435" width="715"]] 118 118 119 119 120 -((( 121 -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: 122 -))) 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: 123 123 124 124 125 125 === 2.3.1 Step 1: Create Device n TTN === 126 126 127 127 128 -((( 129 -Create a device in TTN V3 with the OTAA keys from LHT65N-E5. 130 -))) 122 +Create a device in TTN V3 with the OTAA keys from LHT65N-PIR. 131 131 132 -((( 133 -Each LHT65N-E5 is shipped with a sticker with its device EUI, APP Key and APP EUI as below: 134 -))) 124 +Each LHT65N-PIR is shipped with a sticker with its device EUI, APP Key and APP EUI as below: 135 135 136 136 [[image:image-20220617150003-1.jpeg||_mstalt="5426434"]] 137 137 ... ... @@ -150,12 +150,9 @@ 150 150 151 151 152 152 153 -(% style="color:red" %)**Note: LHT65N- E5use same payload decoder as LHT65.**143 +(% style="color:red" %)**Note: LHT65N-PIR use same payload decoder as LHT65.** 154 154 155 155 156 -[[image:image-20220522233026-6.png||_mstalt="429403"]] 157 - 158 - 159 159 Input APP EUI, APP KEY and DEV EUI: 160 160 161 161 ... ... @@ -162,26 +162,17 @@ 162 162 [[image:image-20220522233118-7.png||_mstalt="430430"]] 163 163 164 164 165 -=== 2.3.2 Step 2: Activate LHT65N- E5by 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. === 166 166 167 - 168 -((( 169 -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. 170 -))) 171 - 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. 172 172 [[image:image-20220522233300-8.png||_mstalt="428389" height="219" width="722"]] 173 173 174 174 175 175 == 2.4 Uplink Payload ( Fport~=2) == 176 176 177 - 178 -((( 179 179 The uplink payload includes totally 11 bytes. Uplink packets use FPORT=2 and (% style="color:#4f81bd" %)**every 20 minutes**(%%) send one uplink by default. 180 -))) 181 181 182 -((( 183 183 After each uplink, the (% style="color:blue" %)**BLUE LED**(%%) will blink once. 184 -))) 185 185 186 186 (% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:390px" %) 187 187 |=(% style="width: 60px;" %)((( ... ... @@ -215,17 +215,17 @@ 215 215 [[Ext value>>||anchor="H2.4.6Extvalue"]] 216 216 ))) 217 217 218 -* The First 6 bytes: has fix meanings for every LHT65N- E5.219 -* The 7th byte (EXT #): defines the external sensor model. It can be 0x05 or 0x09 for LHT65N- E5220 -* The 8^^th^^~~ 9^^th^^byte:Illuminance. Range:0-65535lx.221 -* The 10th ~~ 11thbyte:Reserve,always 0xFFFF196 +* 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. 222 222 223 223 === 2.4.1 Decoder in TTN V3 === 224 224 225 225 226 -When the uplink payload arrives TTNv3, it shows HEX format and not friendly to read. We can add LHT65N- E5decoder 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. 227 227 228 -Below is the position to put the decoder and LHT65N- E5decoder 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]] 229 229 230 230 231 231 [[image:image-20220522234118-10.png||_mstalt="451464" height="353" width="729"]] ... ... @@ -242,11 +242,12 @@ 242 242 [[image:image-20220522235639-1.png||_mstalt="431392" height="139" width="727"]] 243 243 244 244 245 -Check the battery voltage for LHT65N- E5.223 +Check the battery voltage for LHT65N-PIR. 246 246 247 -* BAT status=(0 Xcba4>>14)&0xFF=11(B),very good225 +* BAT status=(0xcba4>>14)&0xFF=11(B),very good 248 248 * Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV 249 249 228 + 250 250 === 2.4.3 Built-in Temperature === 251 251 252 252 ... ... @@ -284,71 +284,6 @@ 284 284 The last 2 bytes of data are meaningless 285 285 286 286 287 - 288 -==== 2.4.5.2 Ext~=0x85, E5 sensor with Unix Timestamp ==== 289 - 290 - 291 -((( 292 -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: 293 -))) 294 - 295 -((( 296 - 297 -))) 298 - 299 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:535px" %) 300 -|=(% style="width: 88px;" %)((( 301 -**Size(bytes)** 302 -)))|=(% style="width: 93px;" %)((( 303 -**2** 304 -)))|=(% style="width: 94px;" %)((( 305 -**2** 306 -)))|=(% style="width: 117px;" %)((( 307 -**2** 308 -)))|=(% style="width: 54px;" %)((( 309 -**1** 310 -)))|=(% style="width: 79px;" %)((( 311 -**4** 312 -))) 313 -|(% style="width:88px" %)((( 314 -**Value** 315 -)))|(% style="width:93px" %)((( 316 -[[External temperature>>||anchor="H4.2SetExternalSensorMode"]] 317 -)))|(% style="width:94px" %)((( 318 -[[Built-In Temperature>>||anchor="H2.4.3Built-inTemperature"]] 319 -)))|(% style="width:117px" %)((( 320 -BAT Status & 321 -Illumination 322 -)))|(% style="width:54px" %)((( 323 -Status & Ext 324 -)))|(% style="width:79px" %)((( 325 -[[Unix Time Stamp>>||anchor="H2.6.2UnixTimeStamp"]] 326 -))) 327 - 328 -* **Battery status & Built-in Humidity** 329 - 330 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:461px" %) 331 -|=(% style="width: 67px;" %)Bit(bit)|=(% style="width: 256px;" %)[15:14]|=(% style="width: 132px;" %)[11:0] 332 -|(% style="width:67px" %)Value|(% style="width:256px" %)((( 333 -BAT Status 334 -00(b): Ultra Low ( BAT <= 2.50v) 335 -01(b): Low (2.50v <=BAT <= 2.55v) 336 -10(b): OK (2.55v <= BAT <=2.65v) 337 -11(b): Good (BAT >= 2.65v) 338 -)))|(% style="width:132px" %)((( 339 -Illumination 340 -))) 341 - 342 -* **Status & Ext Byte** 343 - 344 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:500px" %) 345 -|=(% 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]** 346 -|=(% 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) 347 - 348 -* (% style="color:blue" %)**Poll Message Flag**:(%%) 1: This message is a poll message reply, 0: means this is a normal uplink. 349 -* (% 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. 350 -* (% 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) 351 - 352 352 == 2.5 Show data on Datacake == 353 353 354 354 ... ... @@ -394,239 +394,11 @@ 394 394 [[image:image-20221224161957-6.png||height="306" width="852"]] 395 395 396 396 397 -== 2.6 Datalog Feature == 398 398 399 - 400 -((( 401 -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. 402 -))) 403 - 404 - 405 -=== 2.6.1 Ways to get datalog via LoRaWAN === 406 - 407 - 408 -There are two methods: 409 - 410 -(% style="color:blue" %)**Method 1:** (%%)IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specified time range. 411 - 412 - 413 -(% 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. 414 - 415 - 416 -(% style="color:red" %)**Note for method 2:** 417 - 418 -* a) LHT65N-E5 will do an ACK check for data records sending to make sure every data arrive server. 419 -* 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. 420 - 421 -Below is the typical case for the auto-update datalog feature (Set PNACKMD=1) 422 - 423 - 424 -[[image:image-20220703111700-2.png||_mstalt="426244" height="381" width="1119"]] 425 - 426 - 427 -=== 2.6.2 Unix TimeStamp === 428 - 429 - 430 -LHT65N-E5 uses Unix TimeStamp format based on 431 - 432 - 433 -[[image:image-20220523001219-11.png||_mstalt="450450" height="97" width="627"]] 434 - 435 - 436 - 437 -User can get this time from link: [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] : 438 - 439 -Below is the converter example 440 - 441 -[[image:image-20220523001219-12.png||_mstalt="450827" height="298" width="720"]] 442 - 443 - 444 -So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25 445 - 446 - 447 -=== 2.6.3 Set Device Time === 448 - 449 - 450 -((( 451 -(% style="color:blue" %)**There are two ways to set device's time:** 452 -))) 453 - 454 -((( 455 -**1. Through LoRaWAN MAC Command (Default settings)** 456 -))) 457 - 458 -((( 459 -User need to set SYNCMOD=1 to enable sync time via MAC command. 460 -))) 461 - 462 -((( 463 -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). 464 -))) 465 - 466 -((( 467 -(% 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.** 468 -))) 469 - 470 - 471 -((( 472 -**2. Manually Set Time** 473 -))) 474 - 475 -((( 476 -User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server. 477 -))) 478 - 479 - 480 -=== 2.6.4 Poll sensor value === 481 - 482 - 483 -User can poll sensor value based on timestamps from the server. Below is the downlink command. 484 - 485 -[[image:image-20220523152302-15.png||_mstalt="451581"]] 486 - 487 - 488 -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. 489 - 490 -For example, downlink command (% _mstmutation="1" %)**31 5FC5F350 5FC6 0160 05**(%%) 491 - 492 -Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00’s data 493 - 494 -Uplink Internal =5s,means LHT65N-E5 will send one packet every 5s. range 5~~255s. 495 - 496 - 497 -=== 2.6.5 Datalog Uplink payload === 498 - 499 - 500 -The Datalog poll reply uplink will use below payload format. 501 - 502 -**Retrieval data payload:** 503 - 504 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:480px" %) 505 -|=(% style="width: 60px;" %)((( 506 -**Size(bytes)** 507 -)))|=(% style="width: 90px;" %)**2**|=(% style="width: 90px;" %)**2**|=(% style="width: 70px;" %)**2**|=(% style="width: 100px;" %)**1**|=(% style="width: 70px;" %)**4** 508 -|(% 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"]] 509 - 510 -**Poll message flag & Ext:** 511 - 512 -[[image:image-20221006192726-1.png||_mstalt="430508" height="112" width="754"]] 513 - 514 -(% 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) 515 - 516 -(% style="color:blue" %)**Poll Message Flag**(%%): 1: This message is a poll message reply. 517 - 518 -* Poll Message Flag is set to 1. 519 - 520 -* Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands. 521 - 522 -For example, in US915 band, the max payload for different DR is: 523 - 524 -(% style="color:blue" %)**a) DR0:** (%%)max is 11 bytes so one entry of data 525 - 526 -(% style="color:blue" %)**b) DR1:**(%%) max is 53 bytes so devices will upload 4 entries of data (total 44 bytes) 527 - 528 -(% style="color:blue" %)**c) DR2:**(%%) total payload includes 11 entries of data 529 - 530 -(% style="color:blue" %)**d) DR3: **(%%)total payload includes 22 entries of data. 531 - 532 -If devise doesn't have any data in the polling time. Device will uplink 11 bytes of 0 533 - 534 - 535 -**Example:** 536 - 537 -If LHT65N-E5 has below data inside Flash: 538 - 539 -[[image:image-20220523144455-1.png||_mstalt="430040" height="335" width="735"]] 540 - 541 - 542 -If user sends below downlink command: (% style="background-color:yellow" %)3160065F9760066DA705 543 - 544 -Where : Start time: 60065F97 = time 21/1/19 04:27:03 545 - 546 - Stop time: 60066DA7= time 21/1/19 05:27:03 547 - 548 - 549 -**LHT65N-E5 will uplink this payload.** 550 - 551 -[[image:image-20220523001219-13.png||_mstalt="451204" height="421" style="text-align:left" width="727"]] 552 - 553 - 554 -__**7FFF089801464160065F97**__ **__7FFF__ __088E__ __014B__ __41__ __60066009__** 7FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E 555 - 556 -Where the first 11 bytes is for the first entry: 557 - 558 -7FFF089801464160065F97 559 - 560 -Ext sensor data=0x7FFF/100=327.67 561 - 562 -Temp=0x088E/100=22.00 563 - 564 -Hum=0x014B/10=32.6 565 - 566 -poll message flag & Ext=0x41,means reply data,Ext=1 567 - 568 -Unix time is 0x60066009=1611030423s=21/1/19 04:27:03 569 - 570 - 571 -== 2.7 Alarm Mode == 572 - 573 -((( 574 - 575 - 576 -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. 577 -))) 578 - 579 -((( 580 -(% style="color:red" %)**Note: alarm mode adds a little power consumption, and we recommend extending the normal read time when this feature is enabled.** 581 - 582 - 583 -))) 584 - 585 -=== 2.7.1 ALARM MODE === 586 - 587 - 588 -(% class="box infomessage" %) 589 -((( 590 -((( 591 -**AT+WMOD=1**: Enable/disable alarm mode. (0: Disabled, 1: Enabled Temperature Alarm for onboard temperature sensor) 592 -))) 593 - 594 -((( 595 -**AT+CITEMP=1**: The interval between checking the alarm temperature. (In minutes) 596 -))) 597 - 598 -((( 599 -**AT+ARTEMP**: Gets or sets the alarm range of the internal temperature sensor 600 -))) 601 - 602 -((( 603 -(% _mstmutation="1" %)**AT+ARTEMP=? **(%%): Gets the alarm range of the internal temperature sensor(% style="display:none" %) 604 -))) 605 - 606 -((( 607 -**AT+ARTEMP=45,105**: Set the internal temperature sensor alarm range from 45 to 105. 608 -))) 609 -))) 610 - 611 -(% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX** 612 - 613 -Total bytes: 8 bytes 614 - 615 -**Example:**AA0100010001003C 616 - 617 -WMOD=01 618 - 619 -CITEMP=0001 620 - 621 -TEMPlow=0001 622 - 623 -TEMPhigh=003C 624 - 625 - 626 626 == 2.8 LED Indicator == 627 627 628 628 629 -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 . 630 630 631 631 While user press ACT button, the LED will work as per LED status with ACT button. 632 632 ... ... @@ -637,6 +637,7 @@ 637 637 * RED LED when external sensor is not connected 638 638 * For each success downlink, the PURPLE LED will blink once 639 639 326 + 640 640 == 2.9 installation == 641 641 642 642 ... ... @@ -657,19 +657,13 @@ 657 657 Use for AT Command 658 658 ))) 659 659 * ((( 660 -Update firmware for LHT65N- E5347 +Update firmware for LHT65N-PIR 661 661 ))) 662 -* ((( 663 -Exposed All pins from the LHT65N Type-C connector. 664 664 665 - 666 - 667 -))) 668 - 669 669 [[image:image-20220619092421-3.png||_mstalt="430547" height="371" width="529"]] 670 670 671 671 672 -= 4. Configure LHT65N- E5via AT command or LoRaWAN downlink =353 += 4. Configure LHT65N-PIR via AT command or LoRaWAN downlink = 673 673 674 674 675 675 ((( ... ... @@ -780,127 +780,8 @@ 780 780 781 781 * There is no downlink command to set to Sleep mode. 782 782 783 -== 4.4 Set system time == 784 - 785 - 786 -Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]] 787 - 788 - 789 -(% style="color:#4f81bd" %)**AT Command:** 790 - 791 -[[image:image-20220523151253-8.png||_mstalt="430677"]] 792 - 793 - 794 -(% style="color:#4f81bd" %)**Downlink Command:** 795 - 796 -0x306007806000 ~/~/ Set timestamp to 0x(6007806000),Same as AT+TIMESTAMP=1611104352 797 - 798 - 799 -== 4.5 Set Time Sync Mode == 800 - 801 - 802 -((( 803 -Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply this command. 804 -))) 805 - 806 -((( 807 -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. 808 - 809 809 810 -))) 811 811 812 -(% style="color:#4f81bd" %)**AT Command:** 813 - 814 -[[image:image-20220523151336-9.png||_mstalt="431717"]] 815 - 816 - 817 -(% style="color:#4f81bd" %)**Downlink Command:** 818 - 819 -0x28 01 ~/~/ Same As AT+SYNCMOD=1 820 -0x28 00 ~/~/ Same As AT+SYNCMOD=0 821 - 822 - 823 -== 4.6 Set Time Sync Interval == 824 - 825 - 826 -Feature: Define System time sync interval. SYNCTDC default value: 10 days. 827 - 828 - 829 -(% style="color:#4f81bd" %)**AT Command:** 830 - 831 -[[image:image-20220523151411-10.png||_mstalt="449696"]] 832 - 833 - 834 -(% style="color:#4f81bd" %)**Downlink Command:** 835 - 836 -**0x29 0A** ~/~/ Same as AT+SYNCTDC=0x0A 837 - 838 - 839 -== 4.7 Print data entries base on page. == 840 - 841 - 842 -Feature: Print the sector data from start page to stop page (max is 416 pages). 843 - 844 - 845 -(% style="color:#4f81bd" %)**AT Command: AT+PDTA** 846 - 847 -[[image:image-20220523151450-11.png||_mstalt="451035"]] 848 - 849 - 850 -(% style="color:#4f81bd" %)**Downlink Command:** 851 - 852 -No downlink commands for feature 853 - 854 - 855 -== 4.8 Print last few data entries. == 856 - 857 - 858 -Feature: Print the last few data entries 859 - 860 - 861 -(% style="color:#4f81bd" %)**AT Command: AT+PLDTA** 862 - 863 -[[image:image-20220523151524-12.png||_mstalt="452101"]] 864 - 865 - 866 -(% style="color:#4f81bd" %)**Downlink Command:** 867 - 868 -No downlink commands for feature 869 - 870 - 871 -== 4.9 Clear Flash Record == 872 - 873 - 874 -Feature: Clear flash storage for data log feature. 875 - 876 - 877 -(% style="color:#4f81bd" %)**AT Command: AT+CLRDTA** 878 - 879 -[[image:image-20220523151556-13.png||_mstalt="454129"]] 880 - 881 - 882 -(% style="color:#4f81bd" %)**Downlink Command: 0xA3** 883 - 884 -* Example: 0xA301 ~/~/ Same as AT+CLRDTA 885 - 886 -== 4.10 Auto Send None-ACK messages == 887 - 888 - 889 -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. 890 - 891 - 892 -(% style="color:#4f81bd" %)**AT Command: AT+PNACKMD** 893 - 894 -The default factory setting is 0 895 - 896 -(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:367px" %) 897 -|=(% style="width: 158px;" %)**Command Example**|=(% style="width: 118px;" %)**Function**|=(% style="width: 87px;" %)**Response** 898 -|(% style="width:158px" %)AT+PNACKMD=1|(% style="width:118px" %)Poll None-ACK message|(% style="width:87px" %)OK 899 - 900 -(% style="color:#4f81bd" %)**Downlink Command: 0x34** 901 - 902 -* Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 903 - 904 904 = 5. Battery & How to replace = 905 905 906 906 == 5.1 Battery Type ==