Skip to Content
Last modified by BoYang Xie on 2025/07/09 11:46
From version 188.2
edited by Xiaoling
on 2025/06/10 17:55
Change comment: There is no comment for this version
To version 133.1
edited by Xiaoling
on 2024/12/26 13:55
Change comment: Uploaded new attachment "image-20241226135550-1.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,10 +1,12 @@
1 -
1 +(% style="text-align:center" %)
2 +[[image:image-20240915231842-1.png]]
2 2  
3 -[[image:image-20241226135550-1.png||data-xwiki-image-style-alignment="center"]]
4 4  
5 5  
6 6  
7 7  
8 +
9 +
8 8  (% _mstvisible="1" %)
9 9  (% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:**
10 10  
... ... @@ -140,7 +140,7 @@
140 140  
141 141  Download and install the latest version of [[SquareLine Studio>>https://squareline.io/downloads#lastRelease]] on your computer. It supports Windows, Linux, and Mac OS. The software version we are using here is 1.5.0. See the image below.
142 142  
143 -[[image:squareline.io_downloads.png||height="888" width="1294"]]
145 +[[image:squareline.io_downloads.png]]
144 144  
145 145  
146 146  After installation, you can use SquareLine Studio with a **PERSONAL license plan**. Click **LOG IN** and create a free account using your email address. Then activate your PERSONAL license plan for free. You don’t need to provide any credit card information. However, the PERSONAL license plan has the following limitations:
... ... @@ -159,9 +159,10 @@
159 159  * In the **PROJECT SETTINGS**, select **LVGL version **as **8.3.11** and **Resolution** as **800** x **480**.
160 160  * Select the **CREATE **button to create the new project with the selected settings.
161 161  
162 -[[image:squareline-studio-launcher-screen.png||height="752" width="1415"]]
164 +[[image:squareline-studio-launcher-screen.png]]
163 163  
164 164  
167 +
165 165  Next, you need to configure some additional settings for this project. To do so, select** File  -> Project Settings** as shown in the image below.
166 166  
167 167  [[image:1727229582471-566.png]]
... ... @@ -169,7 +169,7 @@
169 169  
170 170  In the **PROJECT SETTINGS** dialog box, configure/modify the project settings as shown in the image below.
171 171  
172 -* **UI Files Export Path**: Select a **folder** on your computer to store the **UI files**.
175 +* **UI Files Export Root**: Select a folder on your computer to store the UI files.
173 173  * **LVGL Include Path**: Set this to **lvgl.h**
174 174  * Click on the **APPLY CHANGES** button.
175 175  
... ... @@ -182,8 +182,6 @@
182 182  === **Add widgets** ===
183 183  
184 184  
185 -After creating a project, a **Screen** will be automatically added. Its name is **Screen1** by default.
186 -
187 187  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.
188 188  
189 189  [[image:image-20240928111412-6.png||height="526" width="864"]]
... ... @@ -293,65 +293,61 @@
293 293  For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
294 294  
295 295  
296 -== 2.4 Integrate UI Code into an ESP-IDF Project ==
297 +== 2.4 Integrate UI Code to ESP-IDF Project ==
297 297  
298 298  
299 299  To integrate, first export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
300 300  
301 -On the  menubar, click **Export -> Export UI** Files as shown in the image below.
302 -
303 303  [[image:1727229798126-306.png]]
304 304  
304 + image 15 export UI file
305 305  
306 -The exported UI files can be found in your SquareLine project folder as shown in the image below.
307 -
308 -
309 309  [[image:1727229821582-258.png||height="333" width="662"]]
310 310  
308 + image 16 exported UI file
311 311  
312 -Create a new folder named "**ui**" at path "**basic_prj/app_components/ui/**", and copy all the exported UI code into it as shown in the image below.
310 +Create a empty directory entitled "ui" in path "basic_prj/app_components/ui/", and then copy all UI code exported to this directory.
313 313  
314 314  [[image:image-20240928144830-11.png]]
315 315  
314 + image 17 open CMakeLists.txt
316 316  
317 -Open the **CMakeLists.txt** file and edit it as ahown below.
318 -
319 319  [[image:1727229892636-154.png||height="521" width="407"]]
320 320  
318 + image 18 modify CMakeLists.txt
321 321  
322 -Open the main.c file and  add two lines of code as shown in the below images.
323 323  
324 -Add **#include "ui.h"**
321 +The last step of integrating is adding two lines of code in main.c file.
325 325  
326 326  [[image:1727229926561-300.png]]
327 327  
325 + image 19 add "ui.h"
328 328  
329 -Add **ui_init();**
330 -
331 331  [[image:1727229955611-607.png]]
332 332  
329 + image 20 add "ui_init()"
333 333  
334 -== 2.5 Brief introduction to the Hello World project ==
335 335  
332 +== 2.5 Brief introduction of hello world project ==
336 336  
337 -The project consists of two screens. The first screen displays the company's logo, the project name, and a button to navigate to the next screen. The second screen provides information about the HMI screen product through an image and includes a button to return to the previous screen.
338 338  
335 +The project consists of two screens. The first screen displays the company's logo, the project name, and a button to navigate to the next screen. The second screen presents some information about this HMI screen product through an image and includes a button to return to the previous screen.
339 339  
337 +
340 340  == 2.6 Test Result ==
341 341  
342 342  
343 -By pressing the button located at the bottom right, the screen switches to the next one as expected. This confirms that the UI file has been successfully integrated into the project and is functioning correctly.
341 +By pressing the button lying bottom right, the screen can switch to another as expected. This indicates that the UI file has been successfully integrated into the project and is now effective.
344 344  
345 -Screen 1:
346 -
347 347  [[image:1727488067077-684.png||height="402" width="574"]]
348 348  
345 + image 21 screen1
349 349  
350 -Screen 2:
351 -
352 352  [[image:1727488157579-949.png||height="397" width="572"]]
353 353  
349 + image 22 screen2
354 354  
351 +
355 355  = 3. Example Project 1: LoRa Central Display =
356 356  
357 357  [[image:image-20240916101737-1.png||height="468" width="683"]]
... ... @@ -359,347 +359,138 @@
359 359  
360 360  = 4. Example Project 2: LoRaWAN RS485 Alarm =
361 361  
362 -= 5. Example Project 3: P2P =
359 += 5. The way to add a new panel to project =
363 363  
364 -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.
365 365  
366 -The project can be found at [[this link>>url:https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/P2P]].
362 +**~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.**
367 367  
368 -== 5.1 Firmware Flashing ==
369 -
370 -
371 -The following software tools are required to flash firmware to the ESP32 and LA66.
372 -
373 -* 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]].
374 -* Download the LA66 firmware flash tool from [[this link>>https://www.dropbox.com/scl/fo/9kqeqf6wmet10o9hgxuwa/h?rlkey=4ikrg6kg5v0yjxwhp0i37wrv7&e=1&dl=0]].
375 -
376 -=== 5.1.1 Upload the Firmware to the ESP32 ===
377 -
378 -Open //**flash_download_tool.exe**// and follow the steps below.
379 -
380 -* **Chip Type**: ESP32-S3
381 -* **WorkMode**: Develop
382 -* **LoadMode**: UART
383 -* Click on the **OK** button.
384 -
385 -[[image:1738893226894-758.png||height="170" width="176"]]
386 -
387 -
388 -In the **SPIDownload** tab,
389 -
390 -* Select the checkboxes for ESP32_LoRaC-P2P_CommonFW_v1.0.0.bin.
391 -* SPI Flashing Config(default configuration):
392 -** **SPI SPEED**: 40MHz
393 -** **SPI MODE**: DIO
394 -** Check **DoNotChgBin** option.
395 -* **COM**: Select the correct COM port.
396 -* **BAUD**: 1152000
397 -* Click on the **START** button.
398 -
399 -[[image:image-20250505122103-4.png||height="551" width="705"]]
400 -
401 -The progress bar will indicate the firmware update progress and display a **FINISH** message once the update is complete.
402 -
403 -
404 -=== 5.1.2 Upload the Firmware to the LA66 ===
405 -
406 -Open **Dragino_Sensor_Manager_Utility.exe**, and then follow the steps below.
407 -
408 -* Click on the UART Update Firmware tab.
409 -* Select the correct COM port.
410 -* Click on the Upload_File button and select the LA66_P2P_FW_v1.0.0.bin file.
411 -* Click on the Start button.
412 -
413 -
414 -
415 -[[image:image-20250505121328-2.png]]
416 -
417 -
418 -[[image:image-20250505121531-3.png]]
419 -
420 -(% class="wikigeneratedid" %)
421 -The progress bar will indicate the firmware update progress.
422 -
423 -
424 -== 5.2 AT commands and LTS5 Panel Data Formats ==
425 -
426 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**01**A4CBBB0A8E085C02,0,3
427 -
428 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**02**A4CB00,0,3
429 -
430 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**03**A4CB00,0,3
431 -
432 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**04**A4CB00,0,3
433 -
434 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**05**A4CB00,0,3
435 -
436 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**06**A4CB00,0,3
437 -
438 -**LTS5 panel data format**:
439 -
440 -~1. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF  A84041000181D4A8  01  A4CB  BB0A  8E08  5C02**,0,3
441 -
442 -**01:** encrypt. 1 Byte. 01 ~-~-> no encryption. This 1-byte information is now invalid; simply write 0x01 instead.
443 -
444 -**4b69746368656e2d467269676531FFFF: **Device Name. 16 Bytes. The Device Name for this piece of information is "Kitchen-Frige1," and the subsequent "FFFF" is intended to pad it up to 16 Bytes. The Device Name for this piece of information is 'Kitchen-Frige1,' and the subsequent 'FFFF' is intended to pad it up to 16 Bytes, but it is not necessary as the system can handle shorter names as well.
445 -
446 -**A84041000181D4A8:** Device EUI. 8 Bytes. The last three Bytes will be extracted by the ESP32-S3 and displayed on the screen.
447 -
448 -**01: **Panel Type. 1 Byte. 0x01~-~->Tem & Hum,
449 -
450 - 0x02~-~->Door,
451 -
452 - 0x03~-~->Water Leak,
453 -
454 - 0x04~-~->Occupied,
455 -
456 - 0x05~-~->Button,
457 -
458 - 0x06~-~->Alarm,
459 -
460 -**A4CB: **Battery level//. //2 Bytes. Battery Voltage =0xCBA4&0x3FFF=0x0BA4=2980mV
461 -
462 -**BB0A: **The temperature of the built-in sensor in LHT65N.// //2 Bytes. Temperature:  0x0ABB/100=27.47℃
463 -
464 -**8E08: **The temperature of the External temperature sensor.// //2 Bytes. Temperature:  0x088E/100=21.90℃
465 -
466 -**5C02：**The humidity of the built-in sensor in LHT65N. 2 Bytes. Humidity: 0x025C/10=60.4%
467 -
468 -2. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF**  **A84041000181D4A8**  **02  A4CB  00**,0,3
469 -
470 -Specific sections of the data share the same function.
471 -
472 -**00: Status. **1 Byte//. //If Panel Type is 0x02, **Status: 00~-~->Open; 01~-~->Close.**
473 -
474 - If Panel Type is 0x03, **Status: 00~-~->Normal; 01~-~->Water Leaking.**
475 -
476 - If Panel Type is 0x04, **Status: 00~-~->Free; 01~-~->Occupied.**
477 -
478 - If Panel Type is 0x05, **Status: 00~-~->OFF; 01~-~->ON.**
479 -
480 - If Panel Type is 0x06, **Status: 00~-~->OFF; 01~-~->Alarm.**
481 -
482 -== 5.3 Usage ==
483 -
484 -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.
485 -
486 -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.
487 -
488 -[[image:image-20250207143131-11.png||height="527" width="547"]]
489 -
490 -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.
491 -
492 -[[image:image-20250207144605-12.png||height="634" width="548"]]
493 -
494 -LTS5 receives this message and displays it on its screen as the image below shows.
495 -
496 -[[image:image-20250208181700-8.jpeg||height="528" width="704"]]
497 -
498 -= 6. Example Project 4: LoRaWAN_CLASS_C =
499 -
500 -
501 -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.
502 -
503 -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.
504 -
505 -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).
506 -
507 -The project can be found at [[this link>>https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/LoRaWAN_CLASS_C]].
508 -
509 -== 6.1 firmware flashing approach ==
510 -
511 -The firmware flashing approach is the same as described in section 5.1.
512 -
513 -== 6.2 flowchart ==
514 -
515 -[[image:image-20250207164320-13.png||height="696" width="1344"]]
516 -
517 -== 6.3 Usage ==
518 -
519 -This section now describes a process involving TTN downlink panel data that is to be displayed on the LTS5 screen.
520 -
521 -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.
522 -
523 -[[image:image-20250207165702-14.png||height="830" width="563"]]
524 -
525 -6.3.2 Switch to Class C using "AT+CLASS=C", and check the class with "AT+CLASS=?".
526 -
527 -[[image:image-20250207173212-27.png]]
528 -
529 -[[image:image-20250207172246-20.png]]
530 -
531 -6.3.3 Verify LA66's join status (in LTS5) with "AT+NJS=?". If not joined, connect manually to LoRaWAN with "AT+JOIN".
532 -
533 -[[image:image-20250207172010-19.png]]
534 -
535 -[[image:image-20250207171650-17.png]]
536 -
537 -6.3.4 After joining, send a message to TTN, such as "AT+SENDB=01,02,8,05820802581ea0a5", to activate communication.
538 -
539 -[[image:image-20250207192107-28.png]]
540 -
541 -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.
542 -
543 -There is an example for TTN downlink.
544 -
545 -1. downlink DEUI F1A84041000181D4A8
546 -1. downlink Dev Name F24B69746368656E2D467269676531FFFF
547 -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.
548 -
549 -[[image:image-20250208175819-1.png||height="503" width="502"]]
550 -
551 -
552 -[[image:image-20250208175918-2.png||height="505" width="502"]]
553 -
554 -
555 -[[image:image-20250208180010-3.png||height="507" width="503"]]
556 -
557 -
558 -[[image:image-20250208181019-4.jpeg||height="592" width="790"]]
559 -
560 -
561 -[[image:image-20250208181328-7.png||height="505" width="504"]]
562 -
563 -
564 -[[image:image-20250208181139-5.jpeg||height="594" width="792"]]
565 -
566 -
567 -= 7. The method for adding a new type of panel to the project =
568 -
569 -If you don't have this need, then this part of the content can be ignored.
570 -
571 -1. Design a panel in SquareLine Studio, as shown in Image 7.1 below for reference.
572 -
573 573  [[image:image-20241121113445-1.png||height="584" width="934"]]
574 574  
575 - Image 7.1: a panel about water_leak
366 + image 5.1 a panel about water_leak
576 576  
577 577  
578 -2. **Export the UI file: **You need to adjust the export path first, then click '**Export -> Export UI Files**' on the menu bar. This step was introduced earlier. After that, you can get the UI files as shown in Image 7.2.
369 +**2. Export the ui file.** You need  to adjust the export path first, then click "Export->Export UI Files". This step had been introduced before. Then you can get the ui files as shown in image 5.2.
579 579  
580 580  [[image:image-20241121141120-4.png||height="383" width="795"]]
581 581  
582 - Image 7.2: Exported UI files
373 + image 5.2 ui files exported
583 583  
584 584  
585 -3. **Delete and rename some file.** Here are the steps:
376 +**3. Delete or rename some file.** Here are the steps:
586 586  
587 - Step 1: Delete the 'components' directory.
588 - Step 2: Delete 'filelist.txt'.
589 - Step 3: Delete 'ui_helpers.c' and 'ui_helpers.h'.
590 - Step 4: Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
591 - Step 5: Rename the 'screens' directory to 'styles'.
378 + Step1 Delete the 'components' directory.
379 + Step2 Delete 'filelist.txt'.
380 + Step3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
381 + Step4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
382 + Step5 Rename the 'screens' directory to 'styles'.
592 592  
593 593  [[image:image-20241121151934-10.png||height="303" width="792"]]
594 594  
595 - image 7.3 rest file (1)
386 + image 5.3 rest file (1)
596 596  
597 597  [[image:image-20241121142925-7.png||height="141" width="793"]]
598 598  
599 - image 7.4 rest file (2)
390 + image 5.4 rest file (2)
600 600  
601 -4. Open the project in VS Code.
392 +**4. Open this project in vscode.**
602 602  
603 -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**."
394 +5. Add file include path about water_leak in extra_lib/CMakeLists.txt as shown in image 5.5, 5.6, and its format is similar to the tem_hum or door.
604 604  
605 605  [[image:image-20241121181957-17.png||height="438" width="516"]]
606 606  
607 - image 7.5 extra_lib/CMakeLists.txt before adding
398 + image 5.5 extra_lib/CMakeLists.txt before add
608 608  
609 609  [[image:image-20241121182239-18.png||height="520" width="518"]]
610 610  
611 - image 7.6 extra_lib/CMakeLists.txt after adding
402 + image 5.6 extra_lib/CMakeLists.txt after add
612 612  
613 -6.  **Modify the header files included in the fonts and images directories**.
404 +**6. Modify header file include in fonts and images directory.** Open the fonts/ui_font_Font12.c file, as shown in image 5.7, then modify the '#include "../ui.h"' to '#include "../ui_water_leak.h"', the image 5.8 is the modified image. Other font file need to be modified in same way.
614 614  
615 -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.
616 -
617 617  [[image:image-20241121171629-11.png]]
618 618  
619 - image 7.7 unmodified font file
408 + image 5.7 before-modified font file
620 620  
621 621  [[image:image-20241121171901-12.png]]
622 622  
623 - image 7.8 modified font file
412 + image 5.8 modified font file
624 624  
625 -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.
414 +Open the images/ui_img_battery_empty_png.c file, as shown in image 5.9, then modify the '#include "../ui.h"' to '#include "../ui_water_leak.h"', the image 5.10 is the modified image. Other image file need to be modified in same way.
626 626  
627 627  [[image:image-20241121172714-13.png]]
628 628  
629 - image 7.9 unmodified image file
418 + image 5.9 before-modified image file
630 630  
631 631  [[image:image-20241121172908-14.png]]
632 632  
633 - image 7.10 modified image file
422 + image 5.10 modified image file
634 634  
635 -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).
424 +**7. Modify the ui_water_leak/CMakeLists.txt.** Open this file, and modify it from image 5.11 to image 5.12.
636 636  
637 637  [[image:image-20241121180030-15.png]]
638 638  
639 - image 7.11 ui_water_leak/CMakeLists.txt before modification
428 + image 5.11 ui_water_leak/CMakeLists.txt before modification
640 640  
641 641  [[image:image-20241121180517-16.png]]
642 642  
643 - image 7.12 ui_water_leak/CMakeLists.txt after modification
432 + image 5.12 ui_water_leak/CMakeLists.txt after modification
644 644  
434 +**8. Modify ui_water_leak.h file.** The image 5.13, 5.14 show the code before modification, and the image 5.15, 5.16 show the code after modification.
645 645  
646 -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.
647 -
648 648  [[image:image-20241122094200-23.png]]
649 649  
650 - image 7.13 ui_water_leak.h (1) before modification
438 + image 5.13 ui_water_leak.h (1) before modification
651 651  
652 652  [[image:image-20241122094320-24.png||height="852" width="554"]]
653 653  
654 - image 7.14 ui_water_leak.h (2) before modification
442 + image 5.14 ui_water_leak.h (2) before modification
655 655  
656 656  [[image:image-20241122094600-25.png||height="1078" width="554"]]
657 657  
658 - image 7.15 ui_water_leak.h (1) after modification
446 + image 5.15 ui_water_leak.h (1) after modification
659 659  
660 660  [[image:image-20241122094719-26.png||height="941" width="583"]]
661 661  
662 - image 7.16 ui_water_leak.h (2) before modification
450 + image 5.16 ui_water_leak.h (2) before modification
663 663  
664 -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.
452 +**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.
665 665  
666 666  _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.
667 667  
668 668  [[image:image-20241122102929-27.png||height="619" width="426"]]
669 669  
670 - image 7.17 ui_water_leak.c (1) before modification
458 + image 5.17 ui_water_leak.c (1) before modification
671 671  
672 672  [[image:image-20241122112838-30.png||height="551" width="628"]]
673 673  
674 - image 7.18 ui_water_leak.c (2) before modification
462 + image 5.18 ui_water_leak.c (2) before modification
675 675  
676 676  [[image:image-20241122110815-29.png||height="725" width="712"]]
677 677  
678 - image 7.19 ui_water_leak.c (3) before modification
466 + image 5.19 ui_water_leak.c (3) before modification
679 679  
680 680  [[image:image-20241122113158-31.png||height="872" width="677"]]
681 681  
682 - image 7.20 ui_water_leak.c (1) after modification
470 + image 5.20 ui_water_leak.c (1) after modification
683 683  
684 684  [[image:image-20241122113259-33.png||height="874" width="724"]]
685 685  
686 - image 7.21 ui_water_leak.c (2) after modification
474 + image 5.21 ui_water_leak.c (2) after modification
687 687  
688 688  [[image:image-20241122113359-34.png||height="804" width="746"]]
689 689  
690 - image 7.22 ui_water_leak.c (3) after modification
478 + image 5.22 ui_water_leak.c (3) after modification
691 691  
692 -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.
480 +**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.
693 693  
694 694  [[image:image-20241122134113-35.png||height="380" width="421"]]
695 695  
696 - image 7.23 ui_water_leak_events_.h before modification
484 + image 5.23 ui_water_leak_events_.h before modification
697 697  
698 698  [[image:image-20241122134420-37.png||height="201" width="283"]]
699 699  
700 -image 7.24 ui_water_leak_events_.h after modification
488 +image 5.24 ui_water_leak_events_.h after modification
701 701  
702 -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.
490 +**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.
703 703  
704 704  Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
705 705  
... ... @@ -713,14 +713,14 @@
713 713  
714 714  [[image:image-20241122135023-38.png||height="358" width="372"]]
715 715  
716 - image 7.25 ui_water_leak_events_.c before modification
504 + image 5.25 ui_water_leak_events_.c before modification
717 717  
718 718  [[image:image-20241122135258-39.png||height="403" width="559"]]
719 719  
720 - image 7.26 ui_water_leak_events_.c after modification
508 + image 5.26 ui_water_leak_events_.c after modification
721 721  
722 722  
723 -12. **Modify ui_water_leak_style.c file.**
511 +**12. Modify ui_water_leak_style.c file.**
724 724  
725 725  Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
726 726  
... ... @@ -730,67 +730,66 @@
730 730  
731 731  [[image:image-20241122141536-41.png||height="361" width="612"]]
732 732  
733 - image 7.27 ui_water_leak_style.c (1) before modification
521 + image 5.27 ui_water_leak_style.c (1) before modification
734 734  
735 735  [[image:image-20241122142129-42.png||height="386" width="613"]]
736 736  
737 - image 7.28 ui_water_leak_style.c (1) after modification
525 + image 5.28 ui_water_leak_style.c (1) after modification
738 738  
739 739  
740 740  Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
741 741  
742 - delete code as shown in image 7.29
530 + delete code as shown in image 5.29
743 743  
744 744  [[image:image-20241122145620-44.png||height="757" width="671"]]
745 745  
746 - image 7.29 ui_water_leak_style.c (2)
534 + image 5.29 ui_water_leak_style.c (2)
747 747  
748 748  
749 -Step3. The image 7.30, 7.31 show the change.
537 +Step3. The image 5.30, 5.31 show the change.
750 750  
751 751  [[image:image-20241122152026-45.png||height="277" width="828"]]
752 752  
753 - image 7.30 ui_water_leak_style.c (3) before modification
541 + image 5.30 ui_water_leak_style.c (3) before modification
754 754  
755 755  [[image:image-20241122152542-46.png||height="293" width="830"]]
756 756  
757 - image 7.31 ui_water_leak_style.c (3) after modification
545 + image 5.31 ui_water_leak_style.c (3) after modification
758 758  
759 759  
760 -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).
548 +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).
761 761  
762 762  [[image:image-20241122153958-47.png]]
763 763  
764 - image 7.32 ui_water_leak_style.c (4)
552 + image 5.32 ui_water_leak_style.c (4)
765 765  
766 -
767 767  [[image:image-20241122154755-49.png||height="864" width="513"]]
768 768  
769 - image 7.33 ui_water_leak_style.c (4)
556 + image 5.33 ui_water_leak_style.c (4)
770 770  
771 771  
772 -Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 7.34).
559 +Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
773 773  
774 774  [[image:image-20241122155650-50.png||height="922" width="513"]]
775 775  
776 - image 7.34 ui_water_leak_style.c (5)
563 + image 5.34 ui_water_leak_style.c (5)
777 777  
778 778  
779 -Step6. Add some lines of code in extra_lib/sort.h as shown in image 7.35.
566 +Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
780 780  
781 781  [[image:image-20241122161934-51.png]]
782 782  
783 - image 7.35
570 + image 5.35
784 784  
785 785  
786 -Step7. Add a line of code in extra_lib/sort.h as shown in image 7.36.
573 +Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
787 787  
788 788  [[image:image-20241122162852-53.png||height="330" width="529"]]
789 789  
790 - image 7.37
577 + image 5.37
791 791  
792 792  
793 -Step8. Add some code in ui_water_leak_style.c as shown in image 7.38 from line534 to line 576 in detail.
580 +Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
794 794  
795 795  panel_with_type union_sensor;
796 796  
... ... @@ -804,45 +804,36 @@
804 804  
805 805  return union_sensor;
806 806  
807 -[[image:image-20250122173546-6.png||height="777" width="922"]]
594 +[[image:image-20241122171211-54.png||height="635" width="792"]]
808 808  
809 - image 7.38
596 + image 5.38
810 810  
811 811  
812 -13. Rest midification in sort.h file.
599 +**13. Modify sort.c file.**
813 813  
814 -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.
601 +Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
815 815  
816 -[[image:image-20250122170230-1.png||height="580" width="513"]]
603 +[[image:image-20241122173718-56.png||height="378" width="579"]]
817 817  
818 - image 7.39 sort.h
605 + image 5.39 sort.c (1)
819 819  
820 -13. **Modify sort.c file.**
821 -
822 -Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 26.
823 -
824 -[[image:image-20250122171910-5.png||height="524" width="510"]]
825 -
826 - image 7.40 sort.c (1)
827 -
828 828  There are still some changes need to be done in sort.c, and omit here for the moment.
829 829  
830 830  
610 += 6. FAQ =
831 831  
832 -= 8. FAQ =
612 +== 6.1 ==
833 833  
834 -== 8.1 ==
835 835  
615 += 7. Order Info =
836 836  
837 -= 9. Order Info =
617 +== 7.1  Part Number ==
838 838  
839 -== 9.1  Part Number ==
840 840  
841 -
842 842  Part Number: (% style="color:#4472c4" %)LTS5
843 843  
844 844  
845 -== 9.2  Packing Info ==
623 +== 7.2  Packing Info ==
846 846  
847 847  
848 848  **Package Includes**:
... ... @@ -851,21 +851,20 @@
851 851  * 5V,2A DC Power Adapter.
852 852  * USB Type C Program Cable
853 853  
854 -= 10. Support =
632 += 8. Support =
855 855  
856 856  
857 857  * 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.
858 858  * 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]].
859 859  
860 -= 11.  Reference material =
638 += 9.  Reference material =
861 861  
862 862  
863 -* 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]]
864 -* schematic: [[LTS5-V1>>attach:LTS5-V1.pdf]]
865 -* 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]]
641 +* Datasheet
642 +* Source Code
866 866  * Mechinical
867 867  
868 -= 12. FCC Warning =
645 += 10. FCC Warning =
869 869  
870 870  
871 871  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-20250122170230-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -77.3 KB
Content
image-20250122171809-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20250122171825-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20250122171832-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 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