Skip to Content
Last modified by BoYang Xie on 2025/07/24 16:47
From version 195.9
edited by BoYang Xie
on 2025/07/24 16:27
Change comment: There is no comment for this version
To version 139.1
edited by BoYang Xie
on 2025/01/22 17:18
Change comment: Uploaded new attachment "image-20250122171832-4.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,7 @@
1 1  
2 2  
3 -[[image:image-20241226135550-1.png||data-xwiki-image-style-alignment="center"]]
3 +(% style="text-align:center" %)
4 +[[image:image-20241226135550-1.png]]
4 4  
5 5  
6 6  
... ... @@ -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  
... ... @@ -172,7 +172,7 @@
172 172  
173 173  In the **PROJECT SETTINGS** dialog box, configure/modify the project settings as shown in the image below.
174 174  
175 -* **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.
176 176  * **LVGL Include Path**: Set this to **lvgl.h**
177 177  * Click on the **APPLY CHANGES** button.
178 178  
... ... @@ -185,8 +185,6 @@
185 185  === **Add widgets** ===
186 186  
187 187  
188 -After creating a project, a **Screen** will be automatically added. Its name is **Screen1** by default.
189 -
190 190  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.
191 191  
192 192  [[image:image-20240928111412-6.png||height="526" width="864"]]
... ... @@ -296,7 +296,7 @@
296 296  For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
297 297  
298 298  
299 -== 2.4 Integrate UI Code into an ESP-IDF Project ==
295 +== 2.4 Integrate UI Code to ESP-IDF Project ==
300 300  
301 301  
302 302  To integrate, first export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
... ... @@ -362,250 +362,24 @@
362 362  
363 363  = 4. Example Project 2: LoRaWAN RS485 Alarm =
364 364  
365 -= 5. Example Project 3: P2P =
361 += 5. Adding new panel to the project =
366 366  
367 -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.
368 368  
369 -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.
370 370  
371 -== 5.1 Firmware Flashing ==
372 -
373 -
374 -The following software tools are required to flash firmware to the ESP32 and LA66.
375 -
376 -* 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]].
377 -* Download the LA66 firmware flash tool from [[this link>>https://www.dropbox.com/scl/fo/9kqeqf6wmet10o9hgxuwa/h?rlkey=4ikrg6kg5v0yjxwhp0i37wrv7&e=1&dl=0]].
378 -
379 -=== 5.1.1 Upload the Firmware to the ESP32 ===
380 -
381 -Open //**flash_download_tool.exe**// and follow the steps below.
382 -
383 -* **Chip Type**: ESP32-S3
384 -* **WorkMode**: Develop
385 -* **LoadMode**: UART
386 -* Click on the **OK** button.
387 -
388 -[[image:1738893226894-758.png||height="170" width="176"]]
389 -
390 -
391 -In the **SPIDownload** tab,
392 -
393 -* Select the checkboxes for ESP32_LoRaC-P2P_CommonFW_v1.0.0.bin.
394 -* SPI Flashing Config(default configuration):
395 -** **SPI SPEED**: 40MHz
396 -** **SPI MODE**: DIO
397 -** Check **DoNotChgBin** option.
398 -* **COM**: Select the correct COM port.
399 -* **BAUD**: 1152000
400 -* Click on the **START** button.
401 -
402 -[[image:image-20250505122103-4.png||height="551" width="705"]]
403 -
404 -The progress bar will indicate the firmware update progress and display a **FINISH** message once the update is complete.
405 -
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 -=== 5.1.2 Upload the Firmware to the LA66 ===
421 -
422 -Open **Dragino_Sensor_Manager_Utility.exe**, and then follow the steps below.
423 -
424 -* Click on the UART Update Firmware tab.
425 -* Select the correct COM port.
426 -* Click on the Upload_File button and select the LA66_P2P_FW_v1.0.0.bin file.
427 -* Click on the Start button.
428 -
429 -
430 -
431 -[[image:image-20250505121328-2.png]]
432 -
433 -
434 -[[image:image-20250505121531-3.png]]
435 -
436 -(% class="wikigeneratedid" %)
437 -The progress bar will indicate the firmware update progress.
438 -
439 -
440 -== 5.2 AT commands and LTS5 Panel Data Formats ==
441 -
442 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**01**A4CBBB0A8E085C02,0,3
443 -
444 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**02**A4CB00,0,3
445 -
446 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**03**A4CB00,0,3
447 -
448 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**04**A4CB00,0,3
449 -
450 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**05**A4CB00,0,3
451 -
452 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**06**A4CB00,0,3
453 -
454 -**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.**
455 -
456 -~1. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF  A84041000181D4A8  01  A4CB  BB0A  8E08  5C02**,0,3
457 -
458 -**01:** encrypt. 1 Byte. 01 ~-~-> no encryption. This 1-byte information is now invalid; simply write 0x01 instead.
459 -
460 -**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 LTS5 can handle shorter names as well.
461 -
462 -**A84041000181D4A8:** Device EUI. 8 Bytes. The last three Bytes will be extracted by the ESP32-S3 and displayed on the screen.
463 -
464 -**01: **Panel Type. 1 Byte. 0x01~-~->Tem & Hum,
465 -
466 - 0x02~-~->Door,
467 -
468 - 0x03~-~->Water Leak,
469 -
470 - 0x04~-~->Occupied,
471 -
472 - 0x05~-~->Button,
473 -
474 - 0x06~-~->Alarm,
475 -
476 -**A4CB: **Battery level//. //2 Bytes. Battery Voltage =0xCBA4&0x3FFF=0x0BA4=2980mV
477 -
478 -**BB0A: **The temperature of the built-in sensor in LHT65N.// //2 Bytes. Temperature:  0x0ABB/100=27.47℃
479 -
480 -**8E08: **The temperature of the External temperature sensor.// //2 Bytes. Temperature:  0x088E/100=21.90℃
481 -
482 -**5C02：**The humidity of the built-in sensor in LHT65N. 2 Bytes. Humidity: 0x025C/10=60.4%
483 -
484 -
485 -2. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF**  **A84041000181D4A8**  **02  A4CB  00**,0,3
486 -
487 -Specific sections of the data share the same function.
488 -
489 -**00: Status. **1 Byte//. //If Panel Type is 0x02, **Status: 00~-~->Open; 01~-~->Close.**
490 -
491 - If Panel Type is 0x03, **Status: 00~-~->Normal; 01~-~->Water Leaking.**
492 -
493 - If Panel Type is 0x04, **Status: 00~-~->Free; 01~-~->Occupied.**
494 -
495 - If Panel Type is 0x05, **Status: 00~-~->OFF; 01~-~->ON.**
496 -
497 - If Panel Type is 0x06, **Status: 00~-~->OFF; 01~-~->Alarm.**
498 -
499 -== 5.3 Usage ==
500 -
501 -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.
502 -
503 -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.
504 -
505 -[[image:image-20250207143131-11.png||height="527" width="547"]]
506 -
507 -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.
508 -
509 -[[image:image-20250207144605-12.png||height="634" width="548"]]
510 -
511 -LTS5 receives this message and displays it on its screen as the image below shows.
512 -
513 -[[image:image-20250208181700-8.jpeg||height="528" width="704"]]
514 -
515 -= 6. Example Project 4: LoRaWAN_CLASS_C =
516 -
517 -
518 -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.
519 -
520 -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.
521 -
522 -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).
523 -
524 -The project can be found at [[this link>>https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/LoRaWAN_CLASS_C]].
525 -
526 -== 6.1 firmware flashing approach ==
527 -
528 -The firmware flashing approach is the same as described in section 5.1.
529 -
530 -== 6.2 flowchart ==
531 -
532 -[[image:image-20250207164320-13.png||height="696" width="1344"]]
533 -
534 -== 6.3 Usage ==
535 -
536 -This section now describes a process involving TTN downlink panel data that is to be displayed on the LTS5 screen.
537 -
538 -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.
539 -
540 -[[image:image-20250207165702-14.png||height="830" width="563"]]
541 -
542 -6.3.2 Switch to Class C using "AT+CLASS=C", and check the class with "AT+CLASS=?".
543 -
544 -[[image:image-20250207173212-27.png]]
545 -
546 -[[image:image-20250207172246-20.png]]
547 -
548 -6.3.3 Verify LA66's join status (in LTS5) with "AT+NJS=?". If not joined, connect manually to LoRaWAN with "AT+JOIN".
549 -
550 -[[image:image-20250207172010-19.png]]
551 -
552 -[[image:image-20250207171650-17.png]]
553 -
554 -6.3.4 After joining, send a message to TTN, such as "AT+SENDB=01,02,8,05820802581ea0a5", to activate communication.
555 -
556 -[[image:image-20250207192107-28.png]]
557 -
558 -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.
559 -
560 -There is an example for TTN downlink.
561 -
562 -1. downlink DEUI F1A84041000181D4A8
563 -1. downlink Dev Name F24B69746368656E2D467269676531FFFF
564 -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.
565 -
566 -[[image:image-20250208175819-1.png||height="503" width="502"]]
567 -
568 -
569 -[[image:image-20250208175918-2.png||height="505" width="502"]]
570 -
571 -
572 -[[image:image-20250208180010-3.png||height="507" width="503"]]
573 -
574 -
575 -[[image:image-20250208181019-4.jpeg||height="592" width="790"]]
576 -
577 -
578 -[[image:image-20250208181328-7.png||height="505" width="504"]]
579 -
580 -
581 -[[image:image-20250208181139-5.jpeg||height="594" width="792"]]
582 -
583 -
584 -= 7. The method for adding a new type of panel to the project =
585 -
586 -If you don't have this need, then this part of the content can be ignored.
587 -
588 -1. Design a panel in SquareLine Studio, as shown in Image 7.1 below for reference.
589 -
590 590  [[image:image-20241121113445-1.png||height="584" width="934"]]
591 591  
592 - Image 7.1: a panel about water_leak
368 + Image 5.1: a panel about water_leak
593 593  
594 594  
595 -2. **Export the UI file. **
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.
596 596  
597 -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.
598 -
599 -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.
600 -
601 -Image 7.2 shows the result of the operation.
602 -
603 603  [[image:image-20241121141120-4.png||height="383" width="795"]]
604 604  
605 - Image 7.2: Exported UI files
375 + Image 5.2: Exported UI files
606 606  
607 607  
608 -3. **Delete and rename some file.** Here are the steps:
378 +**3. Delete and rename some file.** Here are the steps:
609 609  
610 610   Step 1: Delete the 'components' directory.
611 611   Step 2: Delete 'filelist.txt'.
... ... @@ -615,114 +615,114 @@
615 615  
616 616  [[image:image-20241121151934-10.png||height="303" width="792"]]
617 617  
618 - image 7.3 rest file (1)
388 + image 5.3 rest file (1)
619 619  
620 620  [[image:image-20241121142925-7.png||height="141" width="793"]]
621 621  
622 - image 7.4 rest file (2)
392 + image 5.4 rest file (2)
623 623  
624 -4. Open the project in VS Code.
394 +4. Open the project in **VS Code**.
625 625  
626 -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**."
627 627  
628 628  [[image:image-20241121181957-17.png||height="438" width="516"]]
629 629  
630 - image 7.5 extra_lib/CMakeLists.txt before adding
400 + image 5.5 extra_lib/CMakeLists.txt before add
631 631  
632 632  [[image:image-20241121182239-18.png||height="520" width="518"]]
633 633  
634 - image 7.6 extra_lib/CMakeLists.txt after adding
404 + image 5.6 extra_lib/CMakeLists.txt after add
635 635  
636 -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**.
637 637  
638 -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.
639 639  
640 640  [[image:image-20241121171629-11.png]]
641 641  
642 - image 7.7 unmodified font file
412 + image 5.7 before-modified font file
643 643  
644 644  [[image:image-20241121171901-12.png]]
645 645  
646 - image 7.8 modified font file
416 + image 5.8 modified font file
647 647  
648 -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.
649 649  
650 650  [[image:image-20241121172714-13.png]]
651 651  
652 - image 7.9 unmodified image file
422 + image 5.9 before-modified image file
653 653  
654 654  [[image:image-20241121172908-14.png]]
655 655  
656 - image 7.10 modified image file
426 + image 5.10 modified image file
657 657  
658 -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).
659 659  
660 660  [[image:image-20241121180030-15.png]]
661 661  
662 - image 7.11 ui_water_leak/CMakeLists.txt before modification
432 + image 5.11 ui_water_leak/CMakeLists.txt before modification
663 663  
664 664  [[image:image-20241121180517-16.png]]
665 665  
666 - image 7.12 ui_water_leak/CMakeLists.txt after modification
436 + image 5.12 ui_water_leak/CMakeLists.txt after modification
667 667  
668 668  
669 -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.
670 670  
671 671  [[image:image-20241122094200-23.png]]
672 672  
673 - image 7.13 ui_water_leak.h (1) before modification
443 + image 5.13 ui_water_leak.h (1) before modification
674 674  
675 675  [[image:image-20241122094320-24.png||height="852" width="554"]]
676 676  
677 - image 7.14 ui_water_leak.h (2) before modification
447 + image 5.14 ui_water_leak.h (2) before modification
678 678  
679 679  [[image:image-20241122094600-25.png||height="1078" width="554"]]
680 680  
681 - image 7.15 ui_water_leak.h (1) after modification
451 + image 5.15 ui_water_leak.h (1) after modification
682 682  
683 683  [[image:image-20241122094719-26.png||height="941" width="583"]]
684 684  
685 - image 7.16 ui_water_leak.h (2) before modification
455 + image 5.16 ui_water_leak.h (2) before modification
686 686  
687 -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.
688 688  
689 689  _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.
690 690  
691 691  [[image:image-20241122102929-27.png||height="619" width="426"]]
692 692  
693 - image 7.17 ui_water_leak.c (1) before modification
463 + image 5.17 ui_water_leak.c (1) before modification
694 694  
695 695  [[image:image-20241122112838-30.png||height="551" width="628"]]
696 696  
697 - image 7.18 ui_water_leak.c (2) before modification
467 + image 5.18 ui_water_leak.c (2) before modification
698 698  
699 699  [[image:image-20241122110815-29.png||height="725" width="712"]]
700 700  
701 - image 7.19 ui_water_leak.c (3) before modification
471 + image 5.19 ui_water_leak.c (3) before modification
702 702  
703 703  [[image:image-20241122113158-31.png||height="872" width="677"]]
704 704  
705 - image 7.20 ui_water_leak.c (1) after modification
475 + image 5.20 ui_water_leak.c (1) after modification
706 706  
707 707  [[image:image-20241122113259-33.png||height="874" width="724"]]
708 708  
709 - image 7.21 ui_water_leak.c (2) after modification
479 + image 5.21 ui_water_leak.c (2) after modification
710 710  
711 711  [[image:image-20241122113359-34.png||height="804" width="746"]]
712 712  
713 - image 7.22 ui_water_leak.c (3) after modification
483 + image 5.22 ui_water_leak.c (3) after modification
714 714  
715 -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.
716 716  
717 717  [[image:image-20241122134113-35.png||height="380" width="421"]]
718 718  
719 - image 7.23 ui_water_leak_events_.h before modification
489 + image 5.23 ui_water_leak_events_.h before modification
720 720  
721 721  [[image:image-20241122134420-37.png||height="201" width="283"]]
722 722  
723 -image 7.24 ui_water_leak_events_.h after modification
493 +image 5.24 ui_water_leak_events_.h after modification
724 724  
725 -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.
726 726  
727 727  Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
728 728  
... ... @@ -736,14 +736,14 @@
736 736  
737 737  [[image:image-20241122135023-38.png||height="358" width="372"]]
738 738  
739 - image 7.25 ui_water_leak_events_.c before modification
509 + image 5.25 ui_water_leak_events_.c before modification
740 740  
741 741  [[image:image-20241122135258-39.png||height="403" width="559"]]
742 742  
743 - image 7.26 ui_water_leak_events_.c after modification
513 + image 5.26 ui_water_leak_events_.c after modification
744 744  
745 745  
746 -12. **Modify ui_water_leak_style.c file.**
516 +**12. Modify ui_water_leak_style.c file.**
747 747  
748 748  Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
749 749  
... ... @@ -753,67 +753,66 @@
753 753  
754 754  [[image:image-20241122141536-41.png||height="361" width="612"]]
755 755  
756 - image 7.27 ui_water_leak_style.c (1) before modification
526 + image 5.27 ui_water_leak_style.c (1) before modification
757 757  
758 758  [[image:image-20241122142129-42.png||height="386" width="613"]]
759 759  
760 - image 7.28 ui_water_leak_style.c (1) after modification
530 + image 5.28 ui_water_leak_style.c (1) after modification
761 761  
762 762  
763 763  Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
764 764  
765 - delete code as shown in image 7.29
535 + delete code as shown in image 5.29
766 766  
767 767  [[image:image-20241122145620-44.png||height="757" width="671"]]
768 768  
769 - image 7.29 ui_water_leak_style.c (2)
539 + image 5.29 ui_water_leak_style.c (2)
770 770  
771 771  
772 -Step3. The image 7.30, 7.31 show the change.
542 +Step3. The image 5.30, 5.31 show the change.
773 773  
774 774  [[image:image-20241122152026-45.png||height="277" width="828"]]
775 775  
776 - image 7.30 ui_water_leak_style.c (3) before modification
546 + image 5.30 ui_water_leak_style.c (3) before modification
777 777  
778 778  [[image:image-20241122152542-46.png||height="293" width="830"]]
779 779  
780 - image 7.31 ui_water_leak_style.c (3) after modification
550 + image 5.31 ui_water_leak_style.c (3) after modification
781 781  
782 782  
783 -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).
784 784  
785 785  [[image:image-20241122153958-47.png]]
786 786  
787 - image 7.32 ui_water_leak_style.c (4)
557 + image 5.32 ui_water_leak_style.c (4)
788 788  
789 -
790 790  [[image:image-20241122154755-49.png||height="864" width="513"]]
791 791  
792 - image 7.33 ui_water_leak_style.c (4)
561 + image 5.33 ui_water_leak_style.c (4)
793 793  
794 794  
795 -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).
796 796  
797 797  [[image:image-20241122155650-50.png||height="922" width="513"]]
798 798  
799 - image 7.34 ui_water_leak_style.c (5)
568 + image 5.34 ui_water_leak_style.c (5)
800 800  
801 801  
802 -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.
803 803  
804 804  [[image:image-20241122161934-51.png]]
805 805  
806 - image 7.35
575 + image 5.35
807 807  
808 808  
809 -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.
810 810  
811 811  [[image:image-20241122162852-53.png||height="330" width="529"]]
812 812  
813 - image 7.37
582 + image 5.37
814 814  
815 815  
816 -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.
817 817  
818 818  panel_with_type union_sensor;
819 819  
... ... @@ -827,45 +827,36 @@
827 827  
828 828  return union_sensor;
829 829  
830 -[[image:image-20250122173546-6.png||height="777" width="922"]]
599 +[[image:image-20241122171211-54.png||height="635" width="792"]]
831 831  
832 - image 7.38
601 + image 5.38
833 833  
834 834  
835 -13. Rest midification in sort.h file.
604 +**13. Modify sort.c file.**
836 836  
837 -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.
838 838  
839 -[[image:image-20250122170230-1.png||height="580" width="513"]]
608 +[[image:image-20241122173718-56.png||height="378" width="579"]]
840 840  
841 - image 7.39 sort.h
610 + image 5.39 sort.c (1)
842 842  
843 -13. **Modify sort.c file.**
844 -
845 -Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 26.
846 -
847 -[[image:image-20250122171910-5.png||height="524" width="510"]]
848 -
849 - image 7.40 sort.c (1)
850 -
851 851  There are still some changes need to be done in sort.c, and omit here for the moment.
852 852  
853 853  
615 += 6. FAQ =
854 854  
855 -= 8. FAQ =
617 +== 6.1 ==
856 856  
857 -== 8.1 ==
858 858  
620 += 7. Order Info =
859 859  
860 -= 9. Order Info =
622 +== 7.1  Part Number ==
861 861  
862 -== 9.1  Part Number ==
863 863  
864 -
865 865  Part Number: (% style="color:#4472c4" %)LTS5
866 866  
867 867  
868 -== 9.2  Packing Info ==
628 +== 7.2  Packing Info ==
869 869  
870 870  
871 871  **Package Includes**:
... ... @@ -874,21 +874,20 @@
874 874  * 5V,2A DC Power Adapter.
875 875  * USB Type C Program Cable
876 876  
877 -= 10. Support =
637 += 8. Support =
878 878  
879 879  
880 880  * 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.
881 881  * 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]].
882 882  
883 -= 11.  Reference material =
643 += 9.  Reference material =
884 884  
885 885  
886 -* Datasheet: [[https:~~/~~/www.dropbox.com/scl/fo/fr7wjsdfh9huchg59p7bv/APASCR0elWtp_EbUZ1W9K-A?rlkey=pcuptw3dtg5pw9vgt4ag6hs9z&st=ds6hdztg&dl=0>>https://www.dropbox.com/scl/fo/fr7wjsdfh9huchg59p7bv/APASCR0elWtp_EbUZ1W9K-A?rlkey=pcuptw3dtg5pw9vgt4ag6hs9z&st=ds6hdztg&dl=0]]
887 -* schematic: [[LTS5-V1>>https://www.dropbox.com/scl/fo/grwr5b4x1tk2omyjwg06y/ACleSdi5f7p5zRB2mfPH7CE?rlkey=vhcs83jrj9tkmw8wa9m9wo5rx&st=hkhe3bbj&dl=0]]
888 -* 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]]
646 +* Datasheet
647 +* Source Code
889 889  * Mechinical
890 890  
891 -= 12. FCC Warning =
650 += 10. FCC Warning =
892 892  
893 893  
894 894  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
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
LTS5-V1.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -661.6 KB
Content
image-20250122171910-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 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
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