Skip to Content
Last modified by Xiaoling on 2025/06/10 18:03
From version 188.1
edited by BoYang Xie
on 2025/05/05 12:26
Change comment: There is no comment for this version
To version 163.1
edited by BoYang Xie
on 2025/02/07 17:32
Change comment: Uploaded new attachment "image-20250207173212-27.png", version {1}

Summary

Details

Page properties
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 into an ESP-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,228 +360,22 @@
360 360  
361 361  = 4. Example Project 2: LoRaWAN RS485 Alarm =
362 362  
363 -= 5. Example Project 3: 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 ESP32_LoRaC-P2P_CommonFW_v1.0.0.bin.
392 -* SPI Flashing Config(default configuration):
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 -
401 -[[image:image-20250505122103-4.png||height="551" width="705"]]
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 LA66_P2P_FW_v1.0.0.bin file.
413 -* Click on the Start button.
414 -
415 -
416 -
417 -[[image:image-20250505121328-2.png]]
418 -
419 -
420 -[[image:image-20250505121531-3.png]]
421 -
422 -(% class="wikigeneratedid" %)
423 -The progress bar will indicate the firmware update progress.
424 -
425 -
426 -== 5.2 AT commands and LTS5 Panel Data Formats ==
427 -
428 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**01**A4CBBB0A8E085C02,0,3
429 -
430 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**02**A4CB00,0,3
431 -
432 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**03**A4CB00,0,3
433 -
434 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**04**A4CB00,0,3
435 -
436 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**05**A4CB00,0,3
437 -
438 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**06**A4CB00,0,3
439 -
440 -**LTS5 panel data format**:
441 -
442 -~1. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF  A84041000181D4A8  01  A4CB  BB0A  8E08  5C02**,0,3
443 -
444 -**01:** encrypt. 1 Byte. 01 ~-~-> no encryption. This 1-byte information is now invalid; simply write 0x01 instead.
445 -
446 -**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.
447 -
448 -**A84041000181D4A8:** Device EUI. 8 Bytes. The last three Bytes will be extracted by the ESP32-S3 and displayed on the screen.
449 -
450 -**01: **Panel Type. 1 Byte. 0x01~-~->Tem & Hum,
451 -
452 - 0x02~-~->Door,
453 -
454 - 0x03~-~->Water Leak,
455 -
456 - 0x04~-~->Occupied,
457 -
458 - 0x05~-~->Button,
459 -
460 - 0x06~-~->Alarm,
461 -
462 -**A4CB: **Battery level//. //2 Bytes. Battery Voltage =0xCBA4&0x3FFF=0x0BA4=2980mV
463 -
464 -**BB0A: **The temperature of the built-in sensor in LHT65N.// //2 Bytes. Temperature:  0x0ABB/100=27.47℃
465 -
466 -**8E08: **The temperature of the External temperature sensor.// //2 Bytes. Temperature:  0x088E/100=21.90℃
467 -
468 -**5C02：**The humidity of the built-in sensor in LHT65N. 2 Bytes. Humidity: 0x025C/10=60.4%
469 -
470 -2. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF**  **A84041000181D4A8**  **02  A4CB  00**,0,3
471 -
472 -Specific sections of the data share the same function.
473 -
474 -**00: Status. **1 Byte//. //If Panel Type is 0x02, **Status: 00~-~->Open; 01~-~->Close.**
475 -
476 - If Panel Type is 0x03, **Status: 00~-~->Normal; 01~-~->Water Leaking.**
477 -
478 - If Panel Type is 0x04, **Status: 00~-~->Free; 01~-~->Occupied.**
479 -
480 - If Panel Type is 0x05, **Status: 00~-~->OFF; 01~-~->ON.**
481 -
482 - If Panel Type is 0x06, **Status: 00~-~->OFF; 01~-~->Alarm.**
483 -
484 -== 5.3 Usage ==
485 -
486 -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.
487 -
488 -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.
489 -
490 -[[image:image-20250207143131-11.png||height="527" width="547"]]
491 -
492 -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.
493 -
494 -[[image:image-20250207144605-12.png||height="634" width="548"]]
495 -
496 -LTS5 receives this message and displays it on its screen as the image below shows.
497 -
498 -[[image:image-20250208181700-8.jpeg||height="528" width="704"]]
499 -
500 -= 6. Example Project 4: LoRaWAN_CLASS_C =
501 -
502 -
503 -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.
504 -
505 -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.
506 -
507 -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).
508 -
509 -The project can be found at [[this link>>https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/LoRaWAN_CLASS_C]].
510 -
511 -== 6.1 firmware flashing approach ==
512 -
513 -The firmware flashing approach is the same as described in section 5.1.
514 -
515 -== 6.2 flowchart ==
516 -
517 -[[image:image-20250207164320-13.png||height="696" width="1344"]]
518 -
519 -== 6.3 Usage ==
520 -
521 -This section now describes a process involving TTN downlink panel data that is to be displayed on the LTS5 screen.
522 -
523 -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.
524 -
525 -[[image:image-20250207165702-14.png||height="830" width="563"]]
526 -
527 -6.3.2 Switch to Class C using "AT+CLASS=C", and check the class with "AT+CLASS=?".
528 -
529 -[[image:image-20250207173212-27.png]]
530 -
531 -[[image:image-20250207172246-20.png]]
532 -
533 -6.3.3 Verify LA66's join status (in LTS5) with "AT+NJS=?". If not joined, connect manually to LoRaWAN with "AT+JOIN".
534 -
535 -[[image:image-20250207172010-19.png]]
536 -
537 -[[image:image-20250207171650-17.png]]
538 -
539 -6.3.4 After joining, send a message to TTN, such as "AT+SENDB=01,02,8,05820802581ea0a5", to activate communication.
540 -
541 -[[image:image-20250207192107-28.png]]
542 -
543 -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.
544 -
545 -There is an example for TTN downlink.
546 -
547 -1. downlink DEUI F1A84041000181D4A8
548 -1. downlink Dev Name F24B69746368656E2D467269676531FFFF
549 -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.
550 -
551 -[[image:image-20250208175819-1.png||height="503" width="502"]]
552 -
553 -
554 -[[image:image-20250208175918-2.png||height="505" width="502"]]
555 -
556 -
557 -[[image:image-20250208180010-3.png||height="507" width="503"]]
558 -
559 -
560 -[[image:image-20250208181019-4.jpeg||height="592" width="790"]]
561 -
562 -
563 -[[image:image-20250208181328-7.png||height="505" width="504"]]
564 -
565 -
566 -[[image:image-20250208181139-5.jpeg||height="594" width="792"]]
567 -
568 -
569 -= 7. The method for adding a new type of panel to the project =
570 -
571 571  If you don't have this need, then this part of the content can be ignored.
572 572  
573 -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.
574 574  
575 575  [[image:image-20241121113445-1.png||height="584" width="934"]]
576 576  
577 - Image 7.1: a panel about water_leak
369 + Image 5.1: a panel about water_leak
578 578  
579 579  
580 -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.
581 581  
582 582  [[image:image-20241121141120-4.png||height="383" width="795"]]
583 583  
584 - Image 7.2: Exported UI files
376 + Image 5.2: Exported UI files
585 585  
586 586  
587 587  3. **Delete and rename some file.** Here are the steps:
... ... @@ -594,114 +594,114 @@
594 594  
595 595  [[image:image-20241121151934-10.png||height="303" width="792"]]
596 596  
597 - image 7.3 rest file (1)
389 + image 5.3 rest file (1)
598 598  
599 599  [[image:image-20241121142925-7.png||height="141" width="793"]]
600 600  
601 - image 7.4 rest file (2)
393 + image 5.4 rest file (2)
602 602  
603 -4. Open the project in VS Code.
395 +4. Open the project in **VS Code**.
604 604  
605 -5. Add the file include path for **water_leak** in **extra_lib/CMakeLists.txt**, as shown in Images 7.5 and 7.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**."
606 606  
607 607  [[image:image-20241121181957-17.png||height="438" width="516"]]
608 608  
609 - image 7.5 extra_lib/CMakeLists.txt before adding
401 + image 5.5 extra_lib/CMakeLists.txt before add
610 610  
611 611  [[image:image-20241121182239-18.png||height="520" width="518"]]
612 612  
613 - image 7.6 extra_lib/CMakeLists.txt after adding
405 + image 5.6 extra_lib/CMakeLists.txt after add
614 614  
615 615  6.  **Modify the header files included in the fonts and images directories**.
616 616  
617 -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 Image 7.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.
618 618  
619 619  [[image:image-20241121171629-11.png]]
620 620  
621 - image 7.7 unmodified font file
413 + image 5.7 before-modified font file
622 622  
623 623  [[image:image-20241121171901-12.png]]
624 624  
625 - image 7.8 modified font file
417 + image 5.8 modified font file
626 626  
627 -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 Image 7.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.
628 628  
629 629  [[image:image-20241121172714-13.png]]
630 630  
631 - image 7.9 unmodified image file
423 + image 5.9 before-modified image file
632 632  
633 633  [[image:image-20241121172908-14.png]]
634 634  
635 - image 7.10 modified image file
427 + image 5.10 modified image file
636 636  
637 -7. Modify the **ui_water_leak/CMakeLists.txt**. Open this file, and modify it as shown in image 7.11 (before) and image 7.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).
638 638  
639 639  [[image:image-20241121180030-15.png]]
640 640  
641 - image 7.11 ui_water_leak/CMakeLists.txt before modification
433 + image 5.11 ui_water_leak/CMakeLists.txt before modification
642 642  
643 643  [[image:image-20241121180517-16.png]]
644 644  
645 - image 7.12 ui_water_leak/CMakeLists.txt after modification
437 + image 5.12 ui_water_leak/CMakeLists.txt after modification
646 646  
647 647  
648 -8. Modify the **ui_water_leak.h** file. Images 7.13 and 7.14 show the code before modification, while Images 7.15 and 7.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.
649 649  
650 650  [[image:image-20241122094200-23.png]]
651 651  
652 - image 7.13 ui_water_leak.h (1) before modification
444 + image 5.13 ui_water_leak.h (1) before modification
653 653  
654 654  [[image:image-20241122094320-24.png||height="852" width="554"]]
655 655  
656 - image 7.14 ui_water_leak.h (2) before modification
448 + image 5.14 ui_water_leak.h (2) before modification
657 657  
658 658  [[image:image-20241122094600-25.png||height="1078" width="554"]]
659 659  
660 - image 7.15 ui_water_leak.h (1) after modification
452 + image 5.15 ui_water_leak.h (1) after modification
661 661  
662 662  [[image:image-20241122094719-26.png||height="941" width="583"]]
663 663  
664 - image 7.16 ui_water_leak.h (2) before modification
456 + image 5.16 ui_water_leak.h (2) before modification
665 665  
666 -9. **Modify ui_water_leak.c file.** The image 7.17, 7.18, 7.19 show the code before modification, and the image 7.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.
667 667  
668 668  _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.
669 669  
670 670  [[image:image-20241122102929-27.png||height="619" width="426"]]
671 671  
672 - image 7.17 ui_water_leak.c (1) before modification
464 + image 5.17 ui_water_leak.c (1) before modification
673 673  
674 674  [[image:image-20241122112838-30.png||height="551" width="628"]]
675 675  
676 - image 7.18 ui_water_leak.c (2) before modification
468 + image 5.18 ui_water_leak.c (2) before modification
677 677  
678 678  [[image:image-20241122110815-29.png||height="725" width="712"]]
679 679  
680 - image 7.19 ui_water_leak.c (3) before modification
472 + image 5.19 ui_water_leak.c (3) before modification
681 681  
682 682  [[image:image-20241122113158-31.png||height="872" width="677"]]
683 683  
684 - image 7.20 ui_water_leak.c (1) after modification
476 + image 5.20 ui_water_leak.c (1) after modification
685 685  
686 686  [[image:image-20241122113259-33.png||height="874" width="724"]]
687 687  
688 - image 7.21 ui_water_leak.c (2) after modification
480 + image 5.21 ui_water_leak.c (2) after modification
689 689  
690 690  [[image:image-20241122113359-34.png||height="804" width="746"]]
691 691  
692 - image 7.22 ui_water_leak.c (3) after modification
484 + image 5.22 ui_water_leak.c (3) after modification
693 693  
694 -10. **Modify ui_water_leak_events.h file.** The image 7.23 show the code before modification, and the image 7.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.
695 695  
696 696  [[image:image-20241122134113-35.png||height="380" width="421"]]
697 697  
698 - image 7.23 ui_water_leak_events_.h before modification
490 + image 5.23 ui_water_leak_events_.h before modification
699 699  
700 700  [[image:image-20241122134420-37.png||height="201" width="283"]]
701 701  
702 -image 7.24 ui_water_leak_events_.h after modification
494 +image 5.24 ui_water_leak_events_.h after modification
703 703  
704 -11.** Modify ui_water_leak_events.c file.** The image 7.25 show the code before modification, and the image 7.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.
705 705  
706 706  Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
707 707  
... ... @@ -715,11 +715,11 @@
715 715  
716 716  [[image:image-20241122135023-38.png||height="358" width="372"]]
717 717  
718 - image 7.25 ui_water_leak_events_.c before modification
510 + image 5.25 ui_water_leak_events_.c before modification
719 719  
720 720  [[image:image-20241122135258-39.png||height="403" width="559"]]
721 721  
722 - image 7.26 ui_water_leak_events_.c after modification
514 + image 5.26 ui_water_leak_events_.c after modification
723 723  
724 724  
725 725  12. **Modify ui_water_leak_style.c file.**
... ... @@ -732,67 +732,67 @@
732 732  
733 733  [[image:image-20241122141536-41.png||height="361" width="612"]]
734 734  
735 - image 7.27 ui_water_leak_style.c (1) before modification
527 + image 5.27 ui_water_leak_style.c (1) before modification
736 736  
737 737  [[image:image-20241122142129-42.png||height="386" width="613"]]
738 738  
739 - image 7.28 ui_water_leak_style.c (1) after modification
531 + image 5.28 ui_water_leak_style.c (1) after modification
740 740  
741 741  
742 742  Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
743 743  
744 - delete code as shown in image 7.29
536 + delete code as shown in image 5.29
745 745  
746 746  [[image:image-20241122145620-44.png||height="757" width="671"]]
747 747  
748 - image 7.29 ui_water_leak_style.c (2)
540 + image 5.29 ui_water_leak_style.c (2)
749 749  
750 750  
751 -Step3. The image 7.30, 7.31 show the change.
543 +Step3. The image 5.30, 5.31 show the change.
752 752  
753 753  [[image:image-20241122152026-45.png||height="277" width="828"]]
754 754  
755 - image 7.30 ui_water_leak_style.c (3) before modification
547 + image 5.30 ui_water_leak_style.c (3) before modification
756 756  
757 757  [[image:image-20241122152542-46.png||height="293" width="830"]]
758 758  
759 - image 7.31 ui_water_leak_style.c (3) after modification
551 + image 5.31 ui_water_leak_style.c (3) after modification
760 760  
761 761  
762 -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).
763 763  
764 764  [[image:image-20241122153958-47.png]]
765 765  
766 - image 7.32 ui_water_leak_style.c (4)
558 + image 5.32 ui_water_leak_style.c (4)
767 767  
768 768  
769 769  [[image:image-20241122154755-49.png||height="864" width="513"]]
770 770  
771 - image 7.33 ui_water_leak_style.c (4)
563 + image 5.33 ui_water_leak_style.c (4)
772 772  
773 773  
774 -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).
775 775  
776 776  [[image:image-20241122155650-50.png||height="922" width="513"]]
777 777  
778 - image 7.34 ui_water_leak_style.c (5)
570 + image 5.34 ui_water_leak_style.c (5)
779 779  
780 780  
781 -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.
782 782  
783 783  [[image:image-20241122161934-51.png]]
784 784  
785 - image 7.35
577 + image 5.35
786 786  
787 787  
788 -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.
789 789  
790 790  [[image:image-20241122162852-53.png||height="330" width="529"]]
791 791  
792 - image 7.37
584 + image 5.37
793 793  
794 794  
795 -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.
796 796  
797 797  panel_with_type union_sensor;
798 798  
... ... @@ -808,16 +808,16 @@
808 808  
809 809  [[image:image-20250122173546-6.png||height="777" width="922"]]
810 810  
811 - image 7.38
603 + image 5.38
812 812  
813 813  
814 814  13. Rest midification in sort.h file.
815 815  
816 -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.
817 817  
818 818  [[image:image-20250122170230-1.png||height="580" width="513"]]
819 819  
820 - image 7.39 sort.h
612 + image 5.39 sort.h
821 821  
822 822  13. **Modify sort.c file.**
823 823  
... ... @@ -825,26 +825,26 @@
825 825  
826 826  [[image:image-20250122171910-5.png||height="524" width="510"]]
827 827  
828 - image 7.40 sort.c (1)
620 + image 5.40 sort.c (1)
829 829  
830 830  There are still some changes need to be done in sort.c, and omit here for the moment.
831 831  
832 832  
833 833  
834 -= 8. FAQ =
626 += 6. FAQ =
835 835  
836 -== 8.1 ==
628 +== 6.1 ==
837 837  
838 838  
839 -= 9. Order Info =
631 += 7. Order Info =
840 840  
841 -== 9.1  Part Number ==
633 +== 7.1  Part Number ==
842 842  
843 843  
844 844  Part Number: (% style="color:#4472c4" %)LTS5
845 845  
846 846  
847 -== 9.2  Packing Info ==
639 +== 7.2  Packing Info ==
848 848  
849 849  
850 850  **Package Includes**:
... ... @@ -853,21 +853,20 @@
853 853  * 5V,2A DC Power Adapter.
854 854  * USB Type C Program Cable
855 855  
856 -= 10. Support =
648 += 8. Support =
857 857  
858 858  
859 859  * 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.
860 860  * 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]].
861 861  
862 -= 11.  Reference material =
654 += 9.  Reference material =
863 863  
864 864  
865 865  * Datasheet
866 -* schematic: [[LTS5-V1>>attach:LTS5-V1.pdf]]
867 867  * 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]]
868 868  * Mechinical
869 869  
870 -= 12. FCC Warning =
661 += 10. FCC Warning =
871 871  
872 872  
873 873  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-20250207192107-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -14.3 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
image-20250505112032-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -43.9 KB
Content
image-20250505121328-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -12.2 KB
Content
image-20250505121531-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -21.3 KB
Content
image-20250505122103-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -46.1 KB
Content