Changes for page LTS5 LoRa HMI Touch Screen
Last modified by Dilisi S on 2025/02/26 19:24
<
edited by BoYang Xie
on 2025/02/07 19:21
on 2025/02/07 19:21
Change comment:
Uploaded new attachment "image-20250207192107-28.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 11 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. pradeeka1 +XWiki.xieby - Content
-
... ... @@ -170,7 +170,7 @@ 170 170 171 171 In the **PROJECT SETTINGS** dialog box, configure/modify the project settings as shown in the image below. 172 172 173 -* **UI Files Export Path**: Select a**folder**on your computer to store the**UI files**.173 +* **UI Files Export Root**: Select a folder on your computer to store the UI files. 174 174 * **LVGL Include Path**: Set this to **lvgl.h** 175 175 * Click on the **APPLY CHANGES** button. 176 176 ... ... @@ -183,8 +183,6 @@ 183 183 === **Add widgets** === 184 184 185 185 186 -After creating a project, a **Screen** will be automatically added. Its name is **Screen1** by default. 187 - 188 188 To add a widget, navigate to the **Widgets** panel, and then click on the widget you want to add to the screen. You can reposition the widgets in the screen area by clicking and dragging them. Now add a **Label**, **Button**, and **Image** as shown in the image below. The added widgets are also displayed in the **Hierarchy **panel. 189 189 190 190 [[image:image-20240928111412-6.png||height="526" width="864"]] ... ... @@ -294,7 +294,7 @@ 294 294 For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]]. 295 295 296 296 297 -== 2.4 Integrate UI Code intoanESP-IDF Project ==295 +== 2.4 Integrate UI Code to ESP-IDF Project == 298 298 299 299 300 300 To integrate, first export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project. ... ... @@ -360,227 +360,22 @@ 360 360 361 361 = 4. Example Project 2: LoRaWAN RS485 Alarm = 362 362 363 -= 5. ExampleProject3: P2P=361 += 5. The method for adding a new type of panel to the project = 364 364 365 -The project achieves the function of receiving LoRa P2P messages and displaying them on the screen. The workflow is as follows: A LA66, running a P2P program, sends a message in a particular format via an AT command. Then, the LTS5 receives the message and displays it on the screen. 366 - 367 -The project can be found at [[this link>>url:https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/P2P]]. 368 - 369 -== 5.1 Firmware Flashing == 370 - 371 - 372 -The following software tools are required to flash firmware to the ESP32 and LA66. 373 - 374 -* Download the ESP32 firmware flash tool from [[this link>>https://docs.espressif.com/projects/esp-test-tools/en/latest/esp32/production_stage/tools/flash_download_tool.html]]. 375 -* Download the LA66 firmware flash tool from [[this link>>https://www.dropbox.com/scl/fo/9kqeqf6wmet10o9hgxuwa/h?rlkey=4ikrg6kg5v0yjxwhp0i37wrv7&e=1&dl=0]]. 376 - 377 -=== 5.1.1 Upload the Firmware to the ESP32 === 378 - 379 -Open //**flash_download_tool.exe**// and follow the steps below. 380 - 381 -* **Chip Type**: ESP32-S3 382 -* **WorkMode**: Develop 383 -* **LoadMode**: UART 384 -* Click on the **OK** button. 385 - 386 -[[image:1738893226894-758.png||height="170" width="176"]] 387 - 388 - 389 -In the **SPIDownload** tab, 390 - 391 -* Select the checkboxes for //bootloader.bin, partition-table.bin, ota_data_initial.bin//, and //project.bin//. 392 -* SPI Flashing Config: 393 -** **SPI SPEED**: 40MHz 394 -** **SPI MODE**: DIO 395 -** Check **DoNotChgBin** option. 396 -* **COM**: Select the correct COM port. 397 -* **BAUD**: 1152000 398 -* Click on the **START** button. 399 - 400 -[[image:image-20250207100150-7.png||height="476" width="538"]] 401 - 402 - 403 -The progress bar will indicate the firmware update progress and display a **FINISH** message once the update is complete. 404 - 405 - 406 -=== 5.1.2 Upload the Firmware to the LA66 === 407 - 408 -Open **Dragino_Sensor_Manager_Utility.exe**, and then follow the steps below. 409 - 410 -* Click on the UART Update Firmware tab. 411 -* Select the correct COM port. 412 -* Click on the Upload_File button and select the DRAGINO-LRWAN-AT.bin file. 413 -* Click on the Start button. 414 - 415 -[[image:image-20250207101415-8.png||height="522" width="618"]] 416 - 417 - 418 -[[image:image-20250207101515-9.png||height="522" width="618"]] 419 - 420 - 421 -(% class="wikigeneratedid" %) 422 -The progress bar will indicate the firmware update progress. 423 - 424 - 425 -== 5.2 AT commands and LTS5 Panel Data Formats == 426 - 427 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**01**A4CBBB0A8E085C02,0,3 428 - 429 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**02**A4CB00,0,3 430 - 431 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**03**A4CB00,0,3 432 - 433 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**04**A4CB00,0,3 434 - 435 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**05**A4CB00,0,3 436 - 437 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**06**A4CB00,0,3 438 - 439 -**LTS5 panel data format**: 440 - 441 -~1. AT+SEND=1,**01** **4b69746368656e2d467269676531FFFF A84041000181D4A8 01 A4CB BB0A 8E08 5C02**,0,3 442 - 443 -**01:** encrypt. 1 Byte. 01 ~-~-> no encryption. This 1-byte information is now invalid; simply write 0x01 instead. 444 - 445 -**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. 446 - 447 -**A84041000181D4A8:** Device EUI. 8 Bytes. The last three Bytes will be extracted by the ESP32-S3 and displayed on the screen. 448 - 449 -**01: **Panel Type. 1 Byte. 0x01~-~->Tem & Hum, 450 - 451 - 0x02~-~->Door, 452 - 453 - 0x03~-~->Water Leak, 454 - 455 - 0x04~-~->Occupied, 456 - 457 - 0x05~-~->Button, 458 - 459 - 0x06~-~->Alarm, 460 - 461 -**A4CB: **Battery level//. //2 Bytes. Battery Voltage =0xCBA4&0x3FFF=0x0BA4=2980mV 462 - 463 -**BB0A: **The temperature of the built-in sensor in LHT65N.// //2 Bytes. Temperature: 0x0ABB/100=27.47℃ 464 - 465 -**8E08: **The temperature of the External temperature sensor.// //2 Bytes. Temperature: 0x088E/100=21.90℃ 466 - 467 -**5C02:**The humidity of the built-in sensor in LHT65N. 2 Bytes. Humidity: 0x025C/10=60.4% 468 - 469 -2. AT+SEND=1,**01** **4b69746368656e2d467269676531FFFF** **A84041000181D4A8** **02 A4CB 00**,0,3 470 - 471 -Specific sections of the data share the same function. 472 - 473 -**00: Status. **1 Byte//. //If Panel Type is 0x02, **Status: 00~-~->Open; 01~-~->Close.** 474 - 475 - If Panel Type is 0x03, **Status: 00~-~->Normal; 01~-~->Water Leaking.** 476 - 477 - If Panel Type is 0x04, **Status: 00~-~->Free; 01~-~->Occupied.** 478 - 479 - If Panel Type is 0x05, **Status: 00~-~->OFF; 01~-~->ON.** 480 - 481 - If Panel Type is 0x06, **Status: 00~-~->OFF; 01~-~->Alarm.** 482 - 483 -== 5.3 Usage == 484 - 485 -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. 486 - 487 -5.3.1 Connect LA66 to the computer, open Serial Port Utility, and send the AT+CFG instruction to check whether the LA66 has downloaded correct program. 488 - 489 -[[image:image-20250207143131-11.png||height="527" width="547"]] 490 - 491 -5.3.2 Copy an AT instruction example, click "Send" button, then the led in LA66 will flash and the LTS5 will display the LoRa information. 492 - 493 -[[image:image-20250207144605-12.png||height="634" width="548"]] 494 - 495 -LTS5 receives this message and displays it on its screen as the image below shows. 496 - 497 -[[image:image-20250208181700-8.jpeg||height="528" width="704"]] 498 - 499 -= 6. Example Project 4: LoRaWAN_CLASS_C = 500 - 501 - 502 -The project achieves the function of receiving LoRaWAN Class C messages and displaying them on the screen. Note: The Things Network (TTN) needs to enable Class C support, and the LA66 within the LTS5 needs to operate in Class C mode. 503 - 504 -The downlink workflow proceeds as follows: The Things Network (TTN) sends a message in a specific format via downlink. Then, a LoRaWAN gateway relays this message to the LTS5. Finally, the LTS5 receives the message and displays it on its screen. 505 - 506 -The uplink workflow is as follows: The LA66 within the LTS5 sends a LoRaWAN message, for some reason, to a LoRaWAN gateway, which then forwards it to The Things Network (TTN). 507 - 508 -The project can be found at [[this link>>https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/LoRaWAN_CLASS_C]]. 509 - 510 -== 6.1 firmware flashing approach == 511 - 512 -The firmware flashing approach is the same as described in section 5.1. 513 - 514 -== 6.2 flowchart == 515 - 516 -[[image:image-20250207164320-13.png||height="696" width="1344"]] 517 - 518 -== 6.3 Usage == 519 - 520 -This section now describes a process involving TTN downlink panel data that is to be displayed on the LTS5 screen. 521 - 522 -6.3.1 Connect LA66 to the computer, open Serial Port Utility, and send the AT+CFG instruction to check whether the LA66 has downloaded correct program. 523 - 524 -[[image:image-20250207165702-14.png||height="830" width="563"]] 525 - 526 -6.3.2 Switch to Class C using "AT+CLASS=C", and check the class with "AT+CLASS=?". 527 - 528 -[[image:image-20250207173212-27.png]] 529 - 530 -[[image:image-20250207172246-20.png]] 531 - 532 -6.3.3 Verify LA66's join status (in LTS5) with "AT+NJS=?". If not joined, connect manually to LoRaWAN with "AT+JOIN". 533 - 534 -[[image:image-20250207172010-19.png]] 535 - 536 -[[image:image-20250207171650-17.png]] 537 - 538 -6.3.4 After joining, send a message to TTN, such as "AT+SENDB=01,02,8,05820802581ea0a5", to activate communication. 539 - 540 -[[image:image-20250207192107-28.png]] 541 - 542 -6.3.5 TTN distributes panel data in three phases: DEUI, Dev Name, and Sensor Data. The Dev Name, the last three bytes of the DEUI, and the panel type union together ensure the identification of a panel. Data about the same panel type will update the existing panel display, while data about a different panel type will create a new panel display on the LTS5 screen. 543 - 544 -There is an example for TTN downlink. 545 - 546 -1. downlink DEUI F1A84041000181D4A8 547 -1. downlink Dev Name F24B69746368656E2D467269676531FFFF 548 -1. downlink Sensor Data 5501A4CBBB0A8E085C02 or 5504A4CB01. Both of them are vaild formats for LTS5. Note: 0x55 as prefix and any other prefix except 0xF1, 0xF2, 0xF3 means downlink is Sensor Data. 549 - 550 -[[image:image-20250208175819-1.png||height="503" width="502"]] 551 - 552 - 553 -[[image:image-20250208175918-2.png||height="505" width="502"]] 554 - 555 - 556 -[[image:image-20250208180010-3.png||height="507" width="503"]] 557 - 558 - 559 -[[image:image-20250208181019-4.jpeg||height="592" width="790"]] 560 - 561 - 562 -[[image:image-20250208181328-7.png||height="505" width="504"]] 563 - 564 - 565 -[[image:image-20250208181139-5.jpeg||height="594" width="792"]] 566 - 567 - 568 -= 7. The method for adding a new type of panel to the project = 569 - 570 570 If you don't have this need, then this part of the content can be ignored. 571 571 572 -1. Design a panel in SquareLine Studio, as shown in Image 7.1 below for reference.365 +1. Design a panel in SquareLine Studio, as shown in Image 5.1 below for reference. 573 573 574 574 [[image:image-20241121113445-1.png||height="584" width="934"]] 575 575 576 - Image 7.1: a panel about water_leak369 + Image 5.1: a panel about water_leak 577 577 578 578 579 -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.372 +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 5.2. 580 580 581 581 [[image:image-20241121141120-4.png||height="383" width="795"]] 582 582 583 - Image 7.2: Exported UI files376 + Image 5.2: Exported UI files 584 584 585 585 586 586 3. **Delete and rename some file.** Here are the steps: ... ... @@ -593,114 +593,114 @@ 593 593 594 594 [[image:image-20241121151934-10.png||height="303" width="792"]] 595 595 596 - image 7.3 rest file (1)389 + image 5.3 rest file (1) 597 597 598 598 [[image:image-20241121142925-7.png||height="141" width="793"]] 599 599 600 - image 7.4 rest file (2)393 + image 5.4 rest file (2) 601 601 602 -4. Open the project in VS Code. 395 +4. Open the project in **VS Code**. 603 603 604 -5. Add the file include path for **water_leak** in **extra_lib/CMakeLists.txt**, as shown in Images 7.5 and7.6. Its format is similar to that of **tem_hum** or **door**."397 +5. Add the file include path for **water_leak** in **extra_lib/CMakeLists.txt**, as shown in Images 5.5 and 5.6. Its format is similar to that of **tem_hum** or **door**." 605 605 606 606 [[image:image-20241121181957-17.png||height="438" width="516"]] 607 607 608 - image 7.5 extra_lib/CMakeLists.txt before adding401 + image 5.5 extra_lib/CMakeLists.txt before add 609 609 610 610 [[image:image-20241121182239-18.png||height="520" width="518"]] 611 611 612 - image 7.6 extra_lib/CMakeLists.txt after adding405 + image 5.6 extra_lib/CMakeLists.txt after add 613 613 614 614 6. **Modify the header files included in the fonts and images directories**. 615 615 616 -Open the **fonts/ui_font_Font12.c** file, as shown in Image 7.7, and change **#include "../ui.h"** to **#include "../ui_water_leak.h"**. The modified file is shown in Image7.8. Other font files need to be modified in the same way.409 +Open the **fonts/ui_font_Font12.c** file, as shown in Image 5.7, and change **#include "../ui.h"** to **#include "../ui_water_leak.h"**. The modified file is shown in Image 5.8. Other font files need to be modified in the same way. 617 617 618 618 [[image:image-20241121171629-11.png]] 619 619 620 - image 7.7unmodified font file413 + image 5.7 before-modified font file 621 621 622 622 [[image:image-20241121171901-12.png]] 623 623 624 - image 7.8 modified font file417 + image 5.8 modified font file 625 625 626 -Open the **images/ui_img_battery_empty_png.c** file, as shown in Image 7.9, and change **#include "../ui.h"** to **#include "../ui_water_leak.h"**. The modified file is shown in Image7.10. Other image files need to be modified in the same way.419 +Open the **images/ui_img_battery_empty_png.c** file, as shown in Image 5.9, and change **#include "../ui.h"** to **#include "../ui_water_leak.h"**. The modified file is shown in Image 5.10. Other image files need to be modified in the same way. 627 627 628 628 [[image:image-20241121172714-13.png]] 629 629 630 - 7.9unmodified image file423 + image 5.9 before-modified image file 631 631 632 632 [[image:image-20241121172908-14.png]] 633 633 634 - image 7.10 modified image file427 + image 5.10 modified image file 635 635 636 -7. Modify the **ui_water_leak/CMakeLists.txt**. Open this file, and modify it as shown in image 7.11 (before) and image7.12 (after).429 +7. Modify the **ui_water_leak/CMakeLists.txt**. Open this file, and modify it as shown in image 5.11 (before) and image 5.12 (after). 637 637 638 638 [[image:image-20241121180030-15.png]] 639 639 640 - image 7.11 ui_water_leak/CMakeLists.txt before modification433 + image 5.11 ui_water_leak/CMakeLists.txt before modification 641 641 642 642 [[image:image-20241121180517-16.png]] 643 643 644 - image 7.12 ui_water_leak/CMakeLists.txt after modification437 + image 5.12 ui_water_leak/CMakeLists.txt after modification 645 645 646 646 647 -8. Modify the **ui_water_leak.h** file. Images 7.13 and7.14 show the code before modification, while Images7.15 and7.16 show the code after modification.440 +8. Modify the **ui_water_leak.h** file. Images 5.13 and 5.14 show the code before modification, while Images 5.15 and 5.16 show the code after modification. 648 648 649 649 [[image:image-20241122094200-23.png]] 650 650 651 - image 7.13 ui_water_leak.h (1) before modification444 + image 5.13 ui_water_leak.h (1) before modification 652 652 653 653 [[image:image-20241122094320-24.png||height="852" width="554"]] 654 654 655 - image 7.14 ui_water_leak.h (2) before modification448 + image 5.14 ui_water_leak.h (2) before modification 656 656 657 657 [[image:image-20241122094600-25.png||height="1078" width="554"]] 658 658 659 - image 7.15 ui_water_leak.h (1) after modification452 + image 5.15 ui_water_leak.h (1) after modification 660 660 661 661 [[image:image-20241122094719-26.png||height="941" width="583"]] 662 662 663 - image 7.16 ui_water_leak.h (2) before modification456 + image 5.16 ui_water_leak.h (2) before modification 664 664 665 -9. **Modify ui_water_leak.c file.** The image 7.17,7.18,7.19 show the code before modification, and the image7.20,7.21,7.22 show the code after modification.458 +9. **Modify ui_water_leak.c file.** The image 5.17, 5.18, 5.19 show the code before modification, and the image 5.20, 5.21, 5.22 show the code after modification. 666 666 667 667 _ui_flag_modify( ((lv_obj_t *)(e->user_data)), LV_OBJ_FLAG_HIDDEN, _UI_MODIFY_FLAG_TOGGLE); This code replaces 4 lines of code in ui_water_leak.c, so it is pasted here for convenience. 668 668 669 669 [[image:image-20241122102929-27.png||height="619" width="426"]] 670 670 671 - image 7.17 ui_water_leak.c (1) before modification464 + image 5.17 ui_water_leak.c (1) before modification 672 672 673 673 [[image:image-20241122112838-30.png||height="551" width="628"]] 674 674 675 - image 7.18 ui_water_leak.c (2) before modification468 + image 5.18 ui_water_leak.c (2) before modification 676 676 677 677 [[image:image-20241122110815-29.png||height="725" width="712"]] 678 678 679 - image 7.19 ui_water_leak.c (3) before modification472 + image 5.19 ui_water_leak.c (3) before modification 680 680 681 681 [[image:image-20241122113158-31.png||height="872" width="677"]] 682 682 683 - image 7.20 ui_water_leak.c (1) after modification476 + image 5.20 ui_water_leak.c (1) after modification 684 684 685 685 [[image:image-20241122113259-33.png||height="874" width="724"]] 686 686 687 - image 7.21 ui_water_leak.c (2) after modification480 + image 5.21 ui_water_leak.c (2) after modification 688 688 689 689 [[image:image-20241122113359-34.png||height="804" width="746"]] 690 690 691 - image 7.22 ui_water_leak.c (3) after modification484 + image 5.22 ui_water_leak.c (3) after modification 692 692 693 -10. **Modify ui_water_leak_events.h file.** The image 7.23 show the code before modification, and the image7.24 show the code after modification.486 +10. **Modify ui_water_leak_events.h file.** The image 5.23 show the code before modification, and the image 5.24 show the code after modification. 694 694 695 695 [[image:image-20241122134113-35.png||height="380" width="421"]] 696 696 697 - image 7.23 ui_water_leak_events_.h before modification490 + image 5.23 ui_water_leak_events_.h before modification 698 698 699 699 [[image:image-20241122134420-37.png||height="201" width="283"]] 700 700 701 -image 7.24 ui_water_leak_events_.h after modification494 +image 5.24 ui_water_leak_events_.h after modification 702 702 703 -11.** Modify ui_water_leak_events.c file.** The image 7.25 show the code before modification, and the image7.26 show the code after modification.496 +11.** Modify ui_water_leak_events.c file.** The image 5.25 show the code before modification, and the image 5.26 show the code after modification. 704 704 705 705 Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"' 706 706 ... ... @@ -714,11 +714,11 @@ 714 714 715 715 [[image:image-20241122135023-38.png||height="358" width="372"]] 716 716 717 - image 7.25 ui_water_leak_events_.c before modification510 + image 5.25 ui_water_leak_events_.c before modification 718 718 719 719 [[image:image-20241122135258-39.png||height="403" width="559"]] 720 720 721 - image 7.26 ui_water_leak_events_.c after modification514 + image 5.26 ui_water_leak_events_.c after modification 722 722 723 723 724 724 12. **Modify ui_water_leak_style.c file.** ... ... @@ -731,67 +731,67 @@ 731 731 732 732 [[image:image-20241122141536-41.png||height="361" width="612"]] 733 733 734 - image 7.27 ui_water_leak_style.c (1) before modification527 + image 5.27 ui_water_leak_style.c (1) before modification 735 735 736 736 [[image:image-20241122142129-42.png||height="386" width="613"]] 737 737 738 - image 7.28 ui_water_leak_style.c (1) after modification531 + image 5.28 ui_water_leak_style.c (1) after modification 739 739 740 740 741 741 Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)' 742 742 743 - delete code as shown in image 7.29536 + delete code as shown in image 5.29 744 744 745 745 [[image:image-20241122145620-44.png||height="757" width="671"]] 746 746 747 - image 7.29 ui_water_leak_style.c (2)540 + image 5.29 ui_water_leak_style.c (2) 748 748 749 749 750 -Step3. The image 7.30,7.31 show the change.543 +Step3. The image 5.30, 5.31 show the change. 751 751 752 752 [[image:image-20241122152026-45.png||height="277" width="828"]] 753 753 754 - image 7.30 ui_water_leak_style.c (3) before modification547 + image 5.30 ui_water_leak_style.c (3) before modification 755 755 756 756 [[image:image-20241122152542-46.png||height="293" width="830"]] 757 757 758 - image 7.31 ui_water_leak_style.c (3) after modification551 + image 5.31 ui_water_leak_style.c (3) after modification 759 759 760 760 761 -Step4. Copy partly the code in ui_water_leak.c, paste at extra_lib/sort.h(The process is shown in image 7.32,7.33).554 +Step4. Copy partly the code in ui_water_leak.c, paste at extra_lib/sort.h(The process is shown in image 5.32, 5.33). 762 762 763 763 [[image:image-20241122153958-47.png]] 764 764 765 - image 7.32 ui_water_leak_style.c (4)558 + image 5.32 ui_water_leak_style.c (4) 766 766 767 767 768 768 [[image:image-20241122154755-49.png||height="864" width="513"]] 769 769 770 - image 7.33 ui_water_leak_style.c (4)563 + image 5.33 ui_water_leak_style.c (4) 771 771 772 772 773 -Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 7.34).566 +Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34). 774 774 775 775 [[image:image-20241122155650-50.png||height="922" width="513"]] 776 776 777 - image 7.34 ui_water_leak_style.c (5)570 + image 5.34 ui_water_leak_style.c (5) 778 778 779 779 780 -Step6. Add some lines of code in extra_lib/sort.h as shown in image 7.35.573 +Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35. 781 781 782 782 [[image:image-20241122161934-51.png]] 783 783 784 - image 7.35577 + image 5.35 785 785 786 786 787 -Step7. Add a line of code in extra_lib/sort.h as shown in image 7.36.580 +Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36. 788 788 789 789 [[image:image-20241122162852-53.png||height="330" width="529"]] 790 790 791 - image 7.37584 + image 5.37 792 792 793 793 794 -Step8. Add some code in ui_water_leak_style.c as shown in image 7.38 from line534 to line 576 in detail.587 +Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail. 795 795 796 796 panel_with_type union_sensor; 797 797 ... ... @@ -807,16 +807,16 @@ 807 807 808 808 [[image:image-20250122173546-6.png||height="777" width="922"]] 809 809 810 - image 7.38603 + image 5.38 811 811 812 812 813 813 13. Rest midification in sort.h file. 814 814 815 -In image 7.39 as below, we can see "WATER_LEAK_TYPE" at line 24 and water leak switch status definition at line 32,33, and these are what we need to add in sort.h.608 +In image 5.39 as below, we can see "WATER_LEAK_TYPE" at line 24 and water leak switch status definition at line 32,33, and these are what we need to add in sort. 816 816 817 817 [[image:image-20250122170230-1.png||height="580" width="513"]] 818 818 819 - image 7.39 sort.h612 + image 5.39 sort.h 820 820 821 821 13. **Modify sort.c file.** 822 822 ... ... @@ -824,26 +824,26 @@ 824 824 825 825 [[image:image-20250122171910-5.png||height="524" width="510"]] 826 826 827 - image 7.40 sort.c (1)620 + image 5.40 sort.c (1) 828 828 829 829 There are still some changes need to be done in sort.c, and omit here for the moment. 830 830 831 831 832 832 833 -= 8. FAQ =626 += 6. FAQ = 834 834 835 -== 8.1 ==628 +== 6.1 == 836 836 837 837 838 -= 9. Order Info =631 += 7. Order Info = 839 839 840 -== 9.1 Part Number ==633 +== 7.1 Part Number == 841 841 842 842 843 843 Part Number: (% style="color:#4472c4" %)LTS5 844 844 845 845 846 -== 9.2 Packing Info ==639 +== 7.2 Packing Info == 847 847 848 848 849 849 **Package Includes**: ... ... @@ -852,21 +852,20 @@ 852 852 * 5V,2A DC Power Adapter. 853 853 * USB Type C Program Cable 854 854 855 -= 10. Support =648 += 8. Support = 856 856 857 857 858 858 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 859 859 * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]. 860 860 861 -= 11. Reference material =654 += 9. Reference material = 862 862 863 863 864 864 * Datasheet 865 -* schematic: [[LTS5-V1>>attach:LTS5-V1.pdf]] 866 866 * Source Code: [[dragino/LoRa-HMI-Touch-Screen: Open Source LoRa / LoRaWAN HMI Touch Screen Project>>url:https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main]] 867 867 * Mechinical 868 868 869 -= 1 2. FCC Warning =661 += 10. FCC Warning = 870 870 871 871 872 872 This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
- LTS5-V1.pdf
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.xieby - Size
-
... ... @@ -1,1 +1,0 @@ 1 -661.6 KB - Content
- image-20250208170737-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.xieby - Size
-
... ... @@ -1,1 +1,0 @@ 1 -36.9 KB - Content
- image-20250208170758-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.xieby - Size
-
... ... @@ -1,1 +1,0 @@ 1 -36.9 KB - Content
- image-20250208175819-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.xieby - Size
-
... ... @@ -1,1 +1,0 @@ 1 -36.3 KB - Content
- image-20250208175918-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.xieby - Size
-
... ... @@ -1,1 +1,0 @@ 1 -37.8 KB - Content
- image-20250208180010-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.xieby - Size
-
... ... @@ -1,1 +1,0 @@ 1 -36.7 KB - Content
- image-20250208181019-4.jpeg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.xieby - Size
-
... ... @@ -1,1 +1,0 @@ 1 -546.8 KB - Content
- image-20250208181139-5.jpeg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.xieby - Size
-
... ... @@ -1,1 +1,0 @@ 1 -320.5 KB - Content
- image-20250208181317-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.xieby - Size
-
... ... @@ -1,1 +1,0 @@ 1 -34.8 KB - Content
- image-20250208181328-7.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.xieby - Size
-
... ... @@ -1,1 +1,0 @@ 1 -34.8 KB - Content
- image-20250208181700-8.jpeg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.xieby - Size
-
... ... @@ -1,1 +1,0 @@ 1 -526.4 KB - Content