Changes for page LTS5 LoRa HMI Touch Screen
Last modified by BoYang Xie on 2025/07/24 16:47
From version 195.11
edited by BoYang Xie
on 2025/07/24 16:38
on 2025/07/24 16:38
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 3 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. xieby1 +XWiki.Xiaoling - Content
-
... ... @@ -30,9 +30,6 @@ 30 30 31 31 The LA66 LoRa module can be programmed to support either private LoRa protocols or the LoRaWAN protocol. 32 32 33 - 34 -**//Note: Due to the current incomplete functionality, it is not recommended to purchase at this time.//** 35 - 36 36 == 1.2 Features == 37 37 38 38 ... ... @@ -404,19 +404,6 @@ 404 404 The progress bar will indicate the firmware update progress and display a **FINISH** message once the update is complete. 405 405 406 406 407 -If you want to compile your own ESP32 project and burn the firmware instead of using the pre-provided firmware in the Firmware folder, please use the following method. 408 - 409 -~1. The first method is to use the IDF plugin in VSCode for flashing. Just click the button circled in red in the picture. 410 - 411 -[[image:1752737375843-555.png]] 412 - 413 -2. The second method is to use the FLASH DOWNLOAD TOOL. Select the 4 bin files under the build folder in the project as shown in the following figure. 414 - 415 -Click the "CombineBin" button (indicated by the red box) in the following figure to combine the selected 4 bin files. The combined firmware can be found in the "flash_download_tool_3.9.7/combine/" directory of this software. The ESP32_LoRaC-P2P_CommonFW_v1.0.0.bin firmware is a combined firmware. 416 - 417 -[[image:1752738269428-241.png||height="574" width="674"]] 418 - 419 - 420 420 === 5.1.2 Upload the Firmware to the LA66 === 421 421 422 422 Open **Dragino_Sensor_Manager_Utility.exe**, and then follow the steps below. ... ... @@ -451,28 +451,27 @@ 451 451 452 452 AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**06**A4CB00,0,3 453 453 438 +**LTS5 panel data format**: 454 454 455 -**Currently, there are two types of panel data formats in LTS5. One is the temperature and humidity type, and the other is the "switch" type. Here is the detailed introduction.** 456 - 457 457 ~1. AT+SEND=1,**01** **4b69746368656e2d467269676531FFFF A84041000181D4A8 01 A4CB BB0A 8E08 5C02**,0,3 458 458 459 459 **01:** encrypt. 1 Byte. 01 ~-~-> no encryption. This 1-byte information is now invalid; simply write 0x01 instead. 460 460 461 -**4b69746368656e2d467269676531FFFF: **Device Name. 16 Bytes. The Device Name for this piece of information is "Kitchen-Frige1", and the subsequent 'FFFF' is intended to pad it up to 16 Bytes, but it is not necessary as the LTS5can handle shorter names as well.444 +**4b69746368656e2d467269676531FFFF: **Device Name. 16 Bytes. The Device Name for this piece of information is "Kitchen-Frige1," and the subsequent "FFFF" is intended to pad it up to 16 Bytes. The Device Name for this piece of information is 'Kitchen-Frige1,' and the subsequent 'FFFF' is intended to pad it up to 16 Bytes, but it is not necessary as the system can handle shorter names as well. 462 462 463 463 **A84041000181D4A8:** Device EUI. 8 Bytes. The last three Bytes will be extracted by the ESP32-S3 and displayed on the screen. 464 464 465 465 **01: **Panel Type. 1 Byte. 0x01~-~->Tem & Hum, 466 466 467 - 450 + 0x02~-~->Door, 468 468 469 - 452 + 0x03~-~->Water Leak, 470 470 471 - 454 + 0x04~-~->Occupied, 472 472 473 - 456 + 0x05~-~->Button, 474 474 475 - 458 + 0x06~-~->Alarm, 476 476 477 477 **A4CB: **Battery level//. //2 Bytes. Battery Voltage =0xCBA4&0x3FFF=0x0BA4=2980mV 478 478 ... ... @@ -482,7 +482,6 @@ 482 482 483 483 **5C02:**The humidity of the built-in sensor in LHT65N. 2 Bytes. Humidity: 0x025C/10=60.4% 484 484 485 - 486 486 2. AT+SEND=1,**01** **4b69746368656e2d467269676531FFFF** **A84041000181D4A8** **02 A4CB 00**,0,3 487 487 488 488 Specific sections of the data share the same function. ... ... @@ -489,15 +489,14 @@ 489 489 490 490 **00: Status. **1 Byte//. //If Panel Type is 0x02, **Status: 00~-~->Open; 01~-~->Close.** 491 491 492 - 474 + If Panel Type is 0x03, **Status: 00~-~->Normal; 01~-~->Water Leaking.** 493 493 494 - 476 + If Panel Type is 0x04, **Status: 00~-~->Free; 01~-~->Occupied.** 495 495 496 - 478 + If Panel Type is 0x05, **Status: 00~-~->OFF; 01~-~->ON.** 497 497 498 - 480 + If Panel Type is 0x06, **Status: 00~-~->OFF; 01~-~->Alarm.** 499 499 500 - 501 501 == 5.3 Usage == 502 502 503 503 After burning the firmware into LTS5, you can use an LA66 equipped with peer-to-peer firmware to send data to LTS5 via AT commands. ... ... @@ -594,14 +594,8 @@ 594 594 Image 7.1: a panel about water_leak 595 595 596 596 597 -2. **Export the UI file .**578 +2. **Export the UI file: **You need to adjust the export path first, then click '**Export -> Export UI Files**' on the menu bar. This step was introduced earlier. After that, you can get the UI files as shown in Image 7.2. 598 598 599 -You need to adjust the export path first, then click '**Export -> Export UI Files**' on the menu bar. The method for exporting UI files using the SquareLine software has already been described earlier. 600 - 601 -Next, create a new folder named "ui_water_leak" under "app_components/extra_lib/", and then cut all the UI files you just exported into this newly created folder. 602 - 603 -Image 7.2 shows the result of the operation. 604 - 605 605 [[image:image-20241121141120-4.png||height="383" width="795"]] 606 606 607 607 Image 7.2: Exported UI files
- 1752737128542-192.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.xieby - Size
-
... ... @@ -1,1 +1,0 @@ 1 -52.4 KB - Content
- 1752737375843-555.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.xieby - Size
-
... ... @@ -1,1 +1,0 @@ 1 -9.4 KB - Content
- 1752738269428-241.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.xieby - Size
-
... ... @@ -1,1 +1,0 @@ 1 -52.7 KB - Content