Skip to Content
Last modified by Xiaoling on 2025/06/10 18:03
From version 181.1
edited by Dilisi S
on 2025/02/18 01:36
Change comment: Feb 17 edits - typo
To version 140.1
edited by BoYang Xie
on 2025/01/22 17:19
Change comment: Uploaded new attachment "image-20250122171910-5.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.pradeeka
1 +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 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,198 +360,24 @@
360 360  
361 361  = 4. Example Project 2: LoRaWAN RS485 Alarm =
362 362  
363 -= 5. Example Project 3: P2P =
361 += 5. Adding new 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 366  
367 -The project can be found at [[this link>>url:https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/P2P]].
364 +**~1. **Design a panel in SquareLine Studio, as shown in Image 5.1 below for reference.
368 368  
369 -== 5.1 firmware flashing approach. ==
370 -
371 -5.1.1 Download this project
372 -
373 -5.1.2 Download esp32 firmware flash tool in [[this link>>https://docs.espressif.com/projects/esp-test-tools/en/latest/esp32/production_stage/tools/flash_download_tool.html]].
374 -
375 -5.1.3 Download la66 firmware flash tool in [[this link>>https://www.dropbox.com/scl/fo/9kqeqf6wmet10o9hgxuwa/h?rlkey=4ikrg6kg5v0yjxwhp0i37wrv7&e=1&dl=0]].
376 -
377 -5.1.4 Upload firmware to esp32
378 -
379 -Open flash_download_tool.exe, and then follow the steps below.
380 -
381 -[[image:1738893226894-758.png||height="170" width="176"]]
382 -
383 -[[image:image-20250207100150-7.png||height="476" width="538"]]
384 -
385 -5.1.5 Upload firmware to la66
386 -
387 -Open Dragino_Sensor_Manager_Utility.exe, and then follow the steps below.
388 -
389 -[[image:image-20250207101415-8.png||height="522" width="618"]]
390 -
391 -[[image:image-20250207101515-9.png||height="522" width="618"]]
392 -
393 -== 5.2 AT command and LTS5 panel data format ==
394 -
395 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**01**A4CBBB0A8E085C02,0,3
396 -
397 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**02**A4CB00,0,3
398 -
399 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**03**A4CB00,0,3
400 -
401 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**04**A4CB00,0,3
402 -
403 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**05**A4CB00,0,3
404 -
405 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**06**A4CB00,0,3
406 -
407 -**LTS5 panel data format**:
408 -
409 -~1. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF  A84041000181D4A8  01  A4CB  BB0A  8E08  5C02**,0,3
410 -
411 -**01:** encrypt. 1 Byte. 01 ~-~-> no encryption. This 1-byte information is now invalid; simply write 0x01 instead.
412 -
413 -**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.
414 -
415 -**A84041000181D4A8:** Device EUI. 8 Bytes. The last three Bytes will be extracted by the ESP32-S3 and displayed on the screen.
416 -
417 -**01: **Panel Type. 1 Byte. 0x01~-~->Tem & Hum,
418 -
419 - 0x02~-~->Door,
420 -
421 - 0x03~-~->Water Leak,
422 -
423 - 0x04~-~->Occupied,
424 -
425 - 0x05~-~->Button,
426 -
427 - 0x06~-~->Alarm,
428 -
429 -**A4CB: **Battery level//. //2 Bytes. Battery Voltage =0xCBA4&0x3FFF=0x0BA4=2980mV
430 -
431 -**BB0A: **The temperature of the built-in sensor in LHT65N.// //2 Bytes. Temperature:  0x0ABB/100=27.47℃
432 -
433 -**8E08: **The temperature of the External temperature sensor.// //2 Bytes. Temperature:  0x088E/100=21.90℃
434 -
435 -**5C02：**The humidity of the built-in sensor in LHT65N. 2 Bytes. Humidity: 0x025C/10=60.4%
436 -
437 -2. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF**  **A84041000181D4A8**  **02  A4CB  00**,0,3
438 -
439 -Specific sections of the data share the same function.
440 -
441 -**00: Status. **1 Byte//. //If Panel Type is 0x02, **Status: 00~-~->Open; 01~-~->Close.**
442 -
443 - If Panel Type is 0x03, **Status: 00~-~->Normal; 01~-~->Water Leaking.**
444 -
445 - If Panel Type is 0x04, **Status: 00~-~->Free; 01~-~->Occupied.**
446 -
447 - If Panel Type is 0x05, **Status: 00~-~->OFF; 01~-~->ON.**
448 -
449 - If Panel Type is 0x06, **Status: 00~-~->OFF; 01~-~->Alarm.**
450 -
451 -== 5.3 Usage ==
452 -
453 -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.
454 -
455 -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.
456 -
457 -[[image:image-20250207143131-11.png||height="527" width="547"]]
458 -
459 -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.
460 -
461 -[[image:image-20250207144605-12.png||height="634" width="548"]]
462 -
463 -LTS5 receives this message and displays it on its screen as the image below shows.
464 -
465 -[[image:image-20250208181700-8.jpeg||height="528" width="704"]]
466 -
467 -= 6. Example Project 4: LoRaWAN_CLASS_C =
468 -
469 -
470 -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.
471 -
472 -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.
473 -
474 -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).
475 -
476 -The project can be found at [[this link>>https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/LoRaWAN_CLASS_C]].
477 -
478 -== 6.1 firmware flashing approach ==
479 -
480 -The firmware flashing approach is the same as described in section 5.1.
481 -
482 -== 6.2 flowchart ==
483 -
484 -[[image:image-20250207164320-13.png||height="696" width="1344"]]
485 -
486 -== 6.3 Usage ==
487 -
488 -This section now describes a process involving TTN downlink panel data that is to be displayed on the LTS5 screen.
489 -
490 -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.
491 -
492 -[[image:image-20250207165702-14.png||height="830" width="563"]]
493 -
494 -6.3.2 Switch to Class C using "AT+CLASS=C", and check the class with "AT+CLASS=?".
495 -
496 -[[image:image-20250207173212-27.png]]
497 -
498 -[[image:image-20250207172246-20.png]]
499 -
500 -6.3.3 Verify LA66's join status (in LTS5) with "AT+NJS=?". If not joined, connect manually to LoRaWAN with "AT+JOIN".
501 -
502 -[[image:image-20250207172010-19.png]]
503 -
504 -[[image:image-20250207171650-17.png]]
505 -
506 -6.3.4 After joining, send a message to TTN, such as "AT+SENDB=01,02,8,05820802581ea0a5", to activate communication.
507 -
508 -[[image:image-20250207192107-28.png]]
509 -
510 -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.
511 -
512 -There is an example for TTN downlink.
513 -
514 -1. downlink DEUI F1A84041000181D4A8
515 -1. downlink Dev Name F24B69746368656E2D467269676531FFFF
516 -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.
517 -
518 -[[image:image-20250208175819-1.png||height="503" width="502"]]
519 -
520 -
521 -[[image:image-20250208175918-2.png||height="505" width="502"]]
522 -
523 -
524 -[[image:image-20250208180010-3.png||height="507" width="503"]]
525 -
526 -
527 -[[image:image-20250208181019-4.jpeg||height="592" width="790"]]
528 -
529 -
530 -[[image:image-20250208181328-7.png||height="505" width="504"]]
531 -
532 -
533 -[[image:image-20250208181139-5.jpeg||height="594" width="792"]]
534 -
535 -
536 -= 7. The method for adding a new type of panel to the project =
537 -
538 -If you don't have this need, then this part of the content can be ignored.
539 -
540 -1. Design a panel in SquareLine Studio, as shown in Image 7.1 below for reference.
541 -
542 542  [[image:image-20241121113445-1.png||height="584" width="934"]]
543 543  
544 - Image 7.1: a panel about water_leak
368 + Image 5.1: a panel about water_leak
545 545  
546 546  
547 -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.
371 +**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.
548 548  
549 549  [[image:image-20241121141120-4.png||height="383" width="795"]]
550 550  
551 - Image 7.2: Exported UI files
375 + Image 5.2: Exported UI files
552 552  
553 553  
554 -3. **Delete and rename some file.** Here are the steps:
378 +**3. Delete and rename some file.** Here are the steps:
555 555  
556 556   Step 1: Delete the 'components' directory.
557 557   Step 2: Delete 'filelist.txt'.
... ... @@ -561,114 +561,114 @@
561 561  
562 562  [[image:image-20241121151934-10.png||height="303" width="792"]]
563 563  
564 - image 7.3 rest file (1)
388 + image 5.3 rest file (1)
565 565  
566 566  [[image:image-20241121142925-7.png||height="141" width="793"]]
567 567  
568 - image 7.4 rest file (2)
392 + image 5.4 rest file (2)
569 569  
570 -4. Open the project in VS Code.
394 +4. Open the project in **VS Code**.
571 571  
572 -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**."
396 +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**."
573 573  
574 574  [[image:image-20241121181957-17.png||height="438" width="516"]]
575 575  
576 - image 7.5 extra_lib/CMakeLists.txt before adding
400 + image 5.5 extra_lib/CMakeLists.txt before add
577 577  
578 578  [[image:image-20241121182239-18.png||height="520" width="518"]]
579 579  
580 - image 7.6 extra_lib/CMakeLists.txt after adding
404 + image 5.6 extra_lib/CMakeLists.txt after add
581 581  
582 -6.  **Modify the header files included in the fonts and images directories**.
406 +**6. ** **Modify the header files included in the fonts and images directories**.
583 583  
584 -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.
408 +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.
585 585  
586 586  [[image:image-20241121171629-11.png]]
587 587  
588 - image 7.7 unmodified font file
412 + image 5.7 before-modified font file
589 589  
590 590  [[image:image-20241121171901-12.png]]
591 591  
592 - image 7.8 modified font file
416 + image 5.8 modified font file
593 593  
594 -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.
418 +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.
595 595  
596 596  [[image:image-20241121172714-13.png]]
597 597  
598 - image 7.9 unmodified image file
422 + image 5.9 before-modified image file
599 599  
600 600  [[image:image-20241121172908-14.png]]
601 601  
602 - image 7.10 modified image file
426 + image 5.10 modified image file
603 603  
604 -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).
428 +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).
605 605  
606 606  [[image:image-20241121180030-15.png]]
607 607  
608 - image 7.11 ui_water_leak/CMakeLists.txt before modification
432 + image 5.11 ui_water_leak/CMakeLists.txt before modification
609 609  
610 610  [[image:image-20241121180517-16.png]]
611 611  
612 - image 7.12 ui_water_leak/CMakeLists.txt after modification
436 + image 5.12 ui_water_leak/CMakeLists.txt after modification
613 613  
614 614  
615 -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.
439 +**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.
616 616  
617 617  [[image:image-20241122094200-23.png]]
618 618  
619 - image 7.13 ui_water_leak.h (1) before modification
443 + image 5.13 ui_water_leak.h (1) before modification
620 620  
621 621  [[image:image-20241122094320-24.png||height="852" width="554"]]
622 622  
623 - image 7.14 ui_water_leak.h (2) before modification
447 + image 5.14 ui_water_leak.h (2) before modification
624 624  
625 625  [[image:image-20241122094600-25.png||height="1078" width="554"]]
626 626  
627 - image 7.15 ui_water_leak.h (1) after modification
451 + image 5.15 ui_water_leak.h (1) after modification
628 628  
629 629  [[image:image-20241122094719-26.png||height="941" width="583"]]
630 630  
631 - image 7.16 ui_water_leak.h (2) before modification
455 + image 5.16 ui_water_leak.h (2) before modification
632 632  
633 -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.
457 +**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.
634 634  
635 635  _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.
636 636  
637 637  [[image:image-20241122102929-27.png||height="619" width="426"]]
638 638  
639 - image 7.17 ui_water_leak.c (1) before modification
463 + image 5.17 ui_water_leak.c (1) before modification
640 640  
641 641  [[image:image-20241122112838-30.png||height="551" width="628"]]
642 642  
643 - image 7.18 ui_water_leak.c (2) before modification
467 + image 5.18 ui_water_leak.c (2) before modification
644 644  
645 645  [[image:image-20241122110815-29.png||height="725" width="712"]]
646 646  
647 - image 7.19 ui_water_leak.c (3) before modification
471 + image 5.19 ui_water_leak.c (3) before modification
648 648  
649 649  [[image:image-20241122113158-31.png||height="872" width="677"]]
650 650  
651 - image 7.20 ui_water_leak.c (1) after modification
475 + image 5.20 ui_water_leak.c (1) after modification
652 652  
653 653  [[image:image-20241122113259-33.png||height="874" width="724"]]
654 654  
655 - image 7.21 ui_water_leak.c (2) after modification
479 + image 5.21 ui_water_leak.c (2) after modification
656 656  
657 657  [[image:image-20241122113359-34.png||height="804" width="746"]]
658 658  
659 - image 7.22 ui_water_leak.c (3) after modification
483 + image 5.22 ui_water_leak.c (3) after modification
660 660  
661 -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.
485 +**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.
662 662  
663 663  [[image:image-20241122134113-35.png||height="380" width="421"]]
664 664  
665 - image 7.23 ui_water_leak_events_.h before modification
489 + image 5.23 ui_water_leak_events_.h before modification
666 666  
667 667  [[image:image-20241122134420-37.png||height="201" width="283"]]
668 668  
669 -image 7.24 ui_water_leak_events_.h after modification
493 +image 5.24 ui_water_leak_events_.h after modification
670 670  
671 -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.
495 +**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.
672 672  
673 673  Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
674 674  
... ... @@ -682,14 +682,14 @@
682 682  
683 683  [[image:image-20241122135023-38.png||height="358" width="372"]]
684 684  
685 - image 7.25 ui_water_leak_events_.c before modification
509 + image 5.25 ui_water_leak_events_.c before modification
686 686  
687 687  [[image:image-20241122135258-39.png||height="403" width="559"]]
688 688  
689 - image 7.26 ui_water_leak_events_.c after modification
513 + image 5.26 ui_water_leak_events_.c after modification
690 690  
691 691  
692 -12. **Modify ui_water_leak_style.c file.**
516 +**12. Modify ui_water_leak_style.c file.**
693 693  
694 694  Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
695 695  
... ... @@ -699,67 +699,66 @@
699 699  
700 700  [[image:image-20241122141536-41.png||height="361" width="612"]]
701 701  
702 - image 7.27 ui_water_leak_style.c (1) before modification
526 + image 5.27 ui_water_leak_style.c (1) before modification
703 703  
704 704  [[image:image-20241122142129-42.png||height="386" width="613"]]
705 705  
706 - image 7.28 ui_water_leak_style.c (1) after modification
530 + image 5.28 ui_water_leak_style.c (1) after modification
707 707  
708 708  
709 709  Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
710 710  
711 - delete code as shown in image 7.29
535 + delete code as shown in image 5.29
712 712  
713 713  [[image:image-20241122145620-44.png||height="757" width="671"]]
714 714  
715 - image 7.29 ui_water_leak_style.c (2)
539 + image 5.29 ui_water_leak_style.c (2)
716 716  
717 717  
718 -Step3. The image 7.30, 7.31 show the change.
542 +Step3. The image 5.30, 5.31 show the change.
719 719  
720 720  [[image:image-20241122152026-45.png||height="277" width="828"]]
721 721  
722 - image 7.30 ui_water_leak_style.c (3) before modification
546 + image 5.30 ui_water_leak_style.c (3) before modification
723 723  
724 724  [[image:image-20241122152542-46.png||height="293" width="830"]]
725 725  
726 - image 7.31 ui_water_leak_style.c (3) after modification
550 + image 5.31 ui_water_leak_style.c (3) after modification
727 727  
728 728  
729 -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).
553 +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).
730 730  
731 731  [[image:image-20241122153958-47.png]]
732 732  
733 - image 7.32 ui_water_leak_style.c (4)
557 + image 5.32 ui_water_leak_style.c (4)
734 734  
735 -
736 736  [[image:image-20241122154755-49.png||height="864" width="513"]]
737 737  
738 - image 7.33 ui_water_leak_style.c (4)
561 + image 5.33 ui_water_leak_style.c (4)
739 739  
740 740  
741 -Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 7.34).
564 +Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
742 742  
743 743  [[image:image-20241122155650-50.png||height="922" width="513"]]
744 744  
745 - image 7.34 ui_water_leak_style.c (5)
568 + image 5.34 ui_water_leak_style.c (5)
746 746  
747 747  
748 -Step6. Add some lines of code in extra_lib/sort.h as shown in image 7.35.
571 +Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
749 749  
750 750  [[image:image-20241122161934-51.png]]
751 751  
752 - image 7.35
575 + image 5.35
753 753  
754 754  
755 -Step7. Add a line of code in extra_lib/sort.h as shown in image 7.36.
578 +Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
756 756  
757 757  [[image:image-20241122162852-53.png||height="330" width="529"]]
758 758  
759 - image 7.37
582 + image 5.37
760 760  
761 761  
762 -Step8. Add some code in ui_water_leak_style.c as shown in image 7.38 from line534 to line 576 in detail.
585 +Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
763 763  
764 764  panel_with_type union_sensor;
765 765  
... ... @@ -773,45 +773,36 @@
773 773  
774 774  return union_sensor;
775 775  
776 -[[image:image-20250122173546-6.png||height="777" width="922"]]
599 +[[image:image-20241122171211-54.png||height="635" width="792"]]
777 777  
778 - image 7.38
601 + image 5.38
779 779  
780 780  
781 -13. Rest midification in sort.h file.
604 +**13. Modify sort.c file.**
782 782  
783 -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.
606 +Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
784 784  
785 -[[image:image-20250122170230-1.png||height="580" width="513"]]
608 +[[image:image-20241122173718-56.png||height="378" width="579"]]
786 786  
787 - image 7.39 sort.h
610 + image 5.39 sort.c (1)
788 788  
789 -13. **Modify sort.c file.**
790 -
791 -Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 26.
792 -
793 -[[image:image-20250122171910-5.png||height="524" width="510"]]
794 -
795 - image 7.40 sort.c (1)
796 -
797 797  There are still some changes need to be done in sort.c, and omit here for the moment.
798 798  
799 799  
615 += 6. FAQ =
800 800  
801 -= 8. FAQ =
617 +== 6.1 ==
802 802  
803 -== 8.1 ==
804 804  
620 += 7. Order Info =
805 805  
806 -= 9. Order Info =
622 +== 7.1  Part Number ==
807 807  
808 -== 9.1  Part Number ==
809 809  
810 -
811 811  Part Number: (% style="color:#4472c4" %)LTS5
812 812  
813 813  
814 -== 9.2  Packing Info ==
628 +== 7.2  Packing Info ==
815 815  
816 816  
817 817  **Package Includes**:
... ... @@ -820,21 +820,20 @@
820 820  * 5V,2A DC Power Adapter.
821 821  * USB Type C Program Cable
822 822  
823 -= 10. Support =
637 += 8. Support =
824 824  
825 825  
826 826  * 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.
827 827  * 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]].
828 828  
829 -= 11.  Reference material =
643 += 9.  Reference material =
830 830  
831 831  
832 832  * Datasheet
833 -* schematic: [[LTS5-V1>>attach:LTS5-V1.pdf]]
834 -* 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]]
647 +* Source Code
835 835  * Mechinical
836 836  
837 -= 12. FCC Warning =
650 += 10. FCC Warning =
838 838  
839 839  
840 840  This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
1738893226894-758.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -25.6 KB
Content
LTS5-V1.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -661.6 KB
Content
image-20250122173546-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -200.4 KB
Content
image-20250207100150-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -54.1 KB
Content
image-20250207101415-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -17.6 KB
Content
image-20250207101515-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -24.1 KB
Content
image-20250207142334-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -62.0 KB
Content
image-20250207143131-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -48.7 KB
Content
image-20250207144605-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -58.1 KB
Content
image-20250207164320-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -194.5 KB
Content
image-20250207165702-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -78.1 KB
Content
image-20250207170215-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.6 KB
Content
image-20250207170307-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.2 KB
Content
image-20250207171650-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -11.0 KB
Content
image-20250207171851-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.5 KB
Content
image-20250207172010-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.5 KB
Content
image-20250207172246-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.5 KB
Content
image-20250207172443-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207172821-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -0 bytes
Content
image-20250207172834-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -0 bytes
Content
image-20250207173152-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207173159-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207173206-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207173212-27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 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