Skip to Content
Last modified by BoYang Xie on 2025/07/24 16:47
From version 193.5
edited by BoYang Xie
on 2025/07/17 15:42
Change comment: There is no comment for this version
To version 133.2
edited by Xiaoling
on 2024/12/26 14:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.xieby
1 +XWiki.Xiaoling
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,65 +296,61 @@
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.
303 303  
304 -On the  menubar, click **Export -> Export UI** Files as shown in the image below.
305 -
306 306  [[image:1727229798126-306.png]]
307 307  
302 + image 15 export UI file
308 308  
309 -The exported UI files can be found in your SquareLine project folder as shown in the image below.
310 -
311 -
312 312  [[image:1727229821582-258.png||height="333" width="662"]]
313 313  
306 + image 16 exported UI file
314 314  
315 -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.
308 +Create a empty directory entitled "ui" in path "basic_prj/app_components/ui/", and then copy all UI code exported to this directory.
316 316  
317 317  [[image:image-20240928144830-11.png]]
318 318  
312 + image 17 open CMakeLists.txt
319 319  
320 -Open the **CMakeLists.txt** file and edit it as ahown below.
321 -
322 322  [[image:1727229892636-154.png||height="521" width="407"]]
323 323  
316 + image 18 modify CMakeLists.txt
324 324  
325 -Open the main.c file and  add two lines of code as shown in the below images.
326 326  
327 -Add **#include "ui.h"**
319 +The last step of integrating is adding two lines of code in main.c file.
328 328  
329 329  [[image:1727229926561-300.png]]
330 330  
323 + image 19 add "ui.h"
331 331  
332 -Add **ui_init();**
333 -
334 334  [[image:1727229955611-607.png]]
335 335  
327 + image 20 add "ui_init()"
336 336  
337 -== 2.5 Brief introduction to the Hello World project ==
338 338  
330 +== 2.5 Brief introduction of hello world project ==
339 339  
340 -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.
341 341  
333 +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.
342 342  
335 +
343 343  == 2.6 Test Result ==
344 344  
345 345  
346 -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.
339 +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.
347 347  
348 -Screen 1:
349 -
350 350  [[image:1727488067077-684.png||height="402" width="574"]]
351 351  
343 + image 21 screen1
352 352  
353 -Screen 2:
354 -
355 355  [[image:1727488157579-949.png||height="397" width="572"]]
356 356  
347 + image 22 screen2
357 357  
349 +
358 358  = 3. Example Project 1: LoRa Central Display =
359 359  
360 360  [[image:image-20240916101737-1.png||height="468" width="683"]]
... ... @@ -362,366 +362,138 @@
362 362  
363 363  = 4. Example Project 2: LoRaWAN RS485 Alarm =
364 364  
365 -= 5. Example Project 3: P2P =
357 += 5. The way to add a new panel to 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]].
360 +**~1. Design a panel in SquareLine Studio, using image 5.1 below as a 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 in the figure below to combine the selected firmware. The combined firmware can be found in the "flash_download_tool_3.9.7/combine/" directory of this software.
416 -
417 -[[image:1752737128542-192.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 -**LTS5 panel data format**:
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. 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.
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 -2. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF**  **A84041000181D4A8**  **02  A4CB  00**,0,3
485 -
486 -Specific sections of the data share the same function.
487 -
488 -**00: Status. **1 Byte//. //If Panel Type is 0x02, **Status: 00~-~->Open; 01~-~->Close.**
489 -
490 - If Panel Type is 0x03, **Status: 00~-~->Normal; 01~-~->Water Leaking.**
491 -
492 - If Panel Type is 0x04, **Status: 00~-~->Free; 01~-~->Occupied.**
493 -
494 - If Panel Type is 0x05, **Status: 00~-~->OFF; 01~-~->ON.**
495 -
496 - If Panel Type is 0x06, **Status: 00~-~->OFF; 01~-~->Alarm.**
497 -
498 -== 5.3 Usage ==
499 -
500 -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.
501 -
502 -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.
503 -
504 -[[image:image-20250207143131-11.png||height="527" width="547"]]
505 -
506 -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.
507 -
508 -[[image:image-20250207144605-12.png||height="634" width="548"]]
509 -
510 -LTS5 receives this message and displays it on its screen as the image below shows.
511 -
512 -[[image:image-20250208181700-8.jpeg||height="528" width="704"]]
513 -
514 -= 6. Example Project 4: LoRaWAN_CLASS_C =
515 -
516 -
517 -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.
518 -
519 -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.
520 -
521 -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).
522 -
523 -The project can be found at [[this link>>https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/LoRaWAN_CLASS_C]].
524 -
525 -== 6.1 firmware flashing approach ==
526 -
527 -The firmware flashing approach is the same as described in section 5.1.
528 -
529 -== 6.2 flowchart ==
530 -
531 -[[image:image-20250207164320-13.png||height="696" width="1344"]]
532 -
533 -== 6.3 Usage ==
534 -
535 -This section now describes a process involving TTN downlink panel data that is to be displayed on the LTS5 screen.
536 -
537 -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.
538 -
539 -[[image:image-20250207165702-14.png||height="830" width="563"]]
540 -
541 -6.3.2 Switch to Class C using "AT+CLASS=C", and check the class with "AT+CLASS=?".
542 -
543 -[[image:image-20250207173212-27.png]]
544 -
545 -[[image:image-20250207172246-20.png]]
546 -
547 -6.3.3 Verify LA66's join status (in LTS5) with "AT+NJS=?". If not joined, connect manually to LoRaWAN with "AT+JOIN".
548 -
549 -[[image:image-20250207172010-19.png]]
550 -
551 -[[image:image-20250207171650-17.png]]
552 -
553 -6.3.4 After joining, send a message to TTN, such as "AT+SENDB=01,02,8,05820802581ea0a5", to activate communication.
554 -
555 -[[image:image-20250207192107-28.png]]
556 -
557 -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.
558 -
559 -There is an example for TTN downlink.
560 -
561 -1. downlink DEUI F1A84041000181D4A8
562 -1. downlink Dev Name F24B69746368656E2D467269676531FFFF
563 -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.
564 -
565 -[[image:image-20250208175819-1.png||height="503" width="502"]]
566 -
567 -
568 -[[image:image-20250208175918-2.png||height="505" width="502"]]
569 -
570 -
571 -[[image:image-20250208180010-3.png||height="507" width="503"]]
572 -
573 -
574 -[[image:image-20250208181019-4.jpeg||height="592" width="790"]]
575 -
576 -
577 -[[image:image-20250208181328-7.png||height="505" width="504"]]
578 -
579 -
580 -[[image:image-20250208181139-5.jpeg||height="594" width="792"]]
581 -
582 -
583 -= 7. The method for adding a new type of panel to the project =
584 -
585 -If you don't have this need, then this part of the content can be ignored.
586 -
587 -1. Design a panel in SquareLine Studio, as shown in Image 7.1 below for reference.
588 -
589 589  [[image:image-20241121113445-1.png||height="584" width="934"]]
590 590  
591 - Image 7.1: a panel about water_leak
364 + image 5.1 a panel about water_leak
592 592  
593 593  
594 -2. **Export the UI file. **
367 +**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.
595 595  
596 -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.
597 -
598 -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.
599 -
600 -Image 7.2 shows the result of the operation.
601 -
602 602  [[image:image-20241121141120-4.png||height="383" width="795"]]
603 603  
604 - Image 7.2: Exported UI files
371 + image 5.2 ui files exported
605 605  
606 606  
607 -3. **Delete and rename some file.** Here are the steps:
374 +**3. Delete or rename some file.** Here are the steps:
608 608  
609 - Step 1: Delete the 'components' directory.
610 - Step 2: Delete 'filelist.txt'.
611 - Step 3: Delete 'ui_helpers.c' and 'ui_helpers.h'.
612 - Step 4: Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
613 - Step 5: Rename the 'screens' directory to 'styles'.
376 + Step1 Delete the 'components' directory.
377 + Step2 Delete 'filelist.txt'.
378 + Step3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
379 + Step4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
380 + Step5 Rename the 'screens' directory to 'styles'.
614 614  
615 615  [[image:image-20241121151934-10.png||height="303" width="792"]]
616 616  
617 - image 7.3 rest file (1)
384 + image 5.3 rest file (1)
618 618  
619 619  [[image:image-20241121142925-7.png||height="141" width="793"]]
620 620  
621 - image 7.4 rest file (2)
388 + image 5.4 rest file (2)
622 622  
623 -4. Open the project in VS Code.
390 +**4. Open this project in vscode.**
624 624  
625 -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**."
392 +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.
626 626  
627 627  [[image:image-20241121181957-17.png||height="438" width="516"]]
628 628  
629 - image 7.5 extra_lib/CMakeLists.txt before adding
396 + image 5.5 extra_lib/CMakeLists.txt before add
630 630  
631 631  [[image:image-20241121182239-18.png||height="520" width="518"]]
632 632  
633 - image 7.6 extra_lib/CMakeLists.txt after adding
400 + image 5.6 extra_lib/CMakeLists.txt after add
634 634  
635 -6.  **Modify the header files included in the fonts and images directories**.
402 +**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.
636 636  
637 -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.
638 -
639 639  [[image:image-20241121171629-11.png]]
640 640  
641 - image 7.7 unmodified font file
406 + image 5.7 before-modified font file
642 642  
643 643  [[image:image-20241121171901-12.png]]
644 644  
645 - image 7.8 modified font file
410 + image 5.8 modified font file
646 646  
647 -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.
412 +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.
648 648  
649 649  [[image:image-20241121172714-13.png]]
650 650  
651 - image 7.9 unmodified image file
416 + image 5.9 before-modified image file
652 652  
653 653  [[image:image-20241121172908-14.png]]
654 654  
655 - image 7.10 modified image file
420 + image 5.10 modified image file
656 656  
657 -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).
422 +**7. Modify the ui_water_leak/CMakeLists.txt.** Open this file, and modify it from image 5.11 to image 5.12.
658 658  
659 659  [[image:image-20241121180030-15.png]]
660 660  
661 - image 7.11 ui_water_leak/CMakeLists.txt before modification
426 + image 5.11 ui_water_leak/CMakeLists.txt before modification
662 662  
663 663  [[image:image-20241121180517-16.png]]
664 664  
665 - image 7.12 ui_water_leak/CMakeLists.txt after modification
430 + image 5.12 ui_water_leak/CMakeLists.txt after modification
666 666  
432 +**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.
667 667  
668 -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.
669 -
670 670  [[image:image-20241122094200-23.png]]
671 671  
672 - image 7.13 ui_water_leak.h (1) before modification
436 + image 5.13 ui_water_leak.h (1) before modification
673 673  
674 674  [[image:image-20241122094320-24.png||height="852" width="554"]]
675 675  
676 - image 7.14 ui_water_leak.h (2) before modification
440 + image 5.14 ui_water_leak.h (2) before modification
677 677  
678 678  [[image:image-20241122094600-25.png||height="1078" width="554"]]
679 679  
680 - image 7.15 ui_water_leak.h (1) after modification
444 + image 5.15 ui_water_leak.h (1) after modification
681 681  
682 682  [[image:image-20241122094719-26.png||height="941" width="583"]]
683 683  
684 - image 7.16 ui_water_leak.h (2) before modification
448 + image 5.16 ui_water_leak.h (2) before modification
685 685  
686 -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.
450 +**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.
687 687  
688 688  _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.
689 689  
690 690  [[image:image-20241122102929-27.png||height="619" width="426"]]
691 691  
692 - image 7.17 ui_water_leak.c (1) before modification
456 + image 5.17 ui_water_leak.c (1) before modification
693 693  
694 694  [[image:image-20241122112838-30.png||height="551" width="628"]]
695 695  
696 - image 7.18 ui_water_leak.c (2) before modification
460 + image 5.18 ui_water_leak.c (2) before modification
697 697  
698 698  [[image:image-20241122110815-29.png||height="725" width="712"]]
699 699  
700 - image 7.19 ui_water_leak.c (3) before modification
464 + image 5.19 ui_water_leak.c (3) before modification
701 701  
702 702  [[image:image-20241122113158-31.png||height="872" width="677"]]
703 703  
704 - image 7.20 ui_water_leak.c (1) after modification
468 + image 5.20 ui_water_leak.c (1) after modification
705 705  
706 706  [[image:image-20241122113259-33.png||height="874" width="724"]]
707 707  
708 - image 7.21 ui_water_leak.c (2) after modification
472 + image 5.21 ui_water_leak.c (2) after modification
709 709  
710 710  [[image:image-20241122113359-34.png||height="804" width="746"]]
711 711  
712 - image 7.22 ui_water_leak.c (3) after modification
476 + image 5.22 ui_water_leak.c (3) after modification
713 713  
714 -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.
478 +**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.
715 715  
716 716  [[image:image-20241122134113-35.png||height="380" width="421"]]
717 717  
718 - image 7.23 ui_water_leak_events_.h before modification
482 + image 5.23 ui_water_leak_events_.h before modification
719 719  
720 720  [[image:image-20241122134420-37.png||height="201" width="283"]]
721 721  
722 -image 7.24 ui_water_leak_events_.h after modification
486 +image 5.24 ui_water_leak_events_.h after modification
723 723  
724 -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.
488 +**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.
725 725  
726 726  Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
727 727  
... ... @@ -735,14 +735,14 @@
735 735  
736 736  [[image:image-20241122135023-38.png||height="358" width="372"]]
737 737  
738 - image 7.25 ui_water_leak_events_.c before modification
502 + image 5.25 ui_water_leak_events_.c before modification
739 739  
740 740  [[image:image-20241122135258-39.png||height="403" width="559"]]
741 741  
742 - image 7.26 ui_water_leak_events_.c after modification
506 + image 5.26 ui_water_leak_events_.c after modification
743 743  
744 744  
745 -12. **Modify ui_water_leak_style.c file.**
509 +**12. Modify ui_water_leak_style.c file.**
746 746  
747 747  Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
748 748  
... ... @@ -752,67 +752,66 @@
752 752  
753 753  [[image:image-20241122141536-41.png||height="361" width="612"]]
754 754  
755 - image 7.27 ui_water_leak_style.c (1) before modification
519 + image 5.27 ui_water_leak_style.c (1) before modification
756 756  
757 757  [[image:image-20241122142129-42.png||height="386" width="613"]]
758 758  
759 - image 7.28 ui_water_leak_style.c (1) after modification
523 + image 5.28 ui_water_leak_style.c (1) after modification
760 760  
761 761  
762 762  Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
763 763  
764 - delete code as shown in image 7.29
528 + delete code as shown in image 5.29
765 765  
766 766  [[image:image-20241122145620-44.png||height="757" width="671"]]
767 767  
768 - image 7.29 ui_water_leak_style.c (2)
532 + image 5.29 ui_water_leak_style.c (2)
769 769  
770 770  
771 -Step3. The image 7.30, 7.31 show the change.
535 +Step3. The image 5.30, 5.31 show the change.
772 772  
773 773  [[image:image-20241122152026-45.png||height="277" width="828"]]
774 774  
775 - image 7.30 ui_water_leak_style.c (3) before modification
539 + image 5.30 ui_water_leak_style.c (3) before modification
776 776  
777 777  [[image:image-20241122152542-46.png||height="293" width="830"]]
778 778  
779 - image 7.31 ui_water_leak_style.c (3) after modification
543 + image 5.31 ui_water_leak_style.c (3) after modification
780 780  
781 781  
782 -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).
546 +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).
783 783  
784 784  [[image:image-20241122153958-47.png]]
785 785  
786 - image 7.32 ui_water_leak_style.c (4)
550 + image 5.32 ui_water_leak_style.c (4)
787 787  
788 -
789 789  [[image:image-20241122154755-49.png||height="864" width="513"]]
790 790  
791 - image 7.33 ui_water_leak_style.c (4)
554 + image 5.33 ui_water_leak_style.c (4)
792 792  
793 793  
794 -Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 7.34).
557 +Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
795 795  
796 796  [[image:image-20241122155650-50.png||height="922" width="513"]]
797 797  
798 - image 7.34 ui_water_leak_style.c (5)
561 + image 5.34 ui_water_leak_style.c (5)
799 799  
800 800  
801 -Step6. Add some lines of code in extra_lib/sort.h as shown in image 7.35.
564 +Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
802 802  
803 803  [[image:image-20241122161934-51.png]]
804 804  
805 - image 7.35
568 + image 5.35
806 806  
807 807  
808 -Step7. Add a line of code in extra_lib/sort.h as shown in image 7.36.
571 +Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
809 809  
810 810  [[image:image-20241122162852-53.png||height="330" width="529"]]
811 811  
812 - image 7.37
575 + image 5.37
813 813  
814 814  
815 -Step8. Add some code in ui_water_leak_style.c as shown in image 7.38 from line534 to line 576 in detail.
578 +Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
816 816  
817 817  panel_with_type union_sensor;
818 818  
... ... @@ -826,45 +826,36 @@
826 826  
827 827  return union_sensor;
828 828  
829 -[[image:image-20250122173546-6.png||height="777" width="922"]]
592 +[[image:image-20241122171211-54.png||height="635" width="792"]]
830 830  
831 - image 7.38
594 + image 5.38
832 832  
833 833  
834 -13. Rest midification in sort.h file.
597 +**13. Modify sort.c file.**
835 835  
836 -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.
599 +Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
837 837  
838 -[[image:image-20250122170230-1.png||height="580" width="513"]]
601 +[[image:image-20241122173718-56.png||height="378" width="579"]]
839 839  
840 - image 7.39 sort.h
603 + image 5.39 sort.c (1)
841 841  
842 -13. **Modify sort.c file.**
843 -
844 -Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 26.
845 -
846 -[[image:image-20250122171910-5.png||height="524" width="510"]]
847 -
848 - image 7.40 sort.c (1)
849 -
850 850  There are still some changes need to be done in sort.c, and omit here for the moment.
851 851  
852 852  
608 += 6. FAQ =
853 853  
854 -= 8. FAQ =
610 +== 6.1 ==
855 855  
856 -== 8.1 ==
857 857  
613 += 7. Order Info =
858 858  
859 -= 9. Order Info =
615 +== 7.1  Part Number ==
860 860  
861 -== 9.1  Part Number ==
862 862  
863 -
864 864  Part Number: (% style="color:#4472c4" %)LTS5
865 865  
866 866  
867 -== 9.2  Packing Info ==
621 +== 7.2  Packing Info ==
868 868  
869 869  
870 870  **Package Includes**:
... ... @@ -873,21 +873,20 @@
873 873  * 5V,2A DC Power Adapter.
874 874  * USB Type C Program Cable
875 875  
876 -= 10. Support =
630 += 8. Support =
877 877  
878 878  
879 879  * 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.
880 880  * 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]].
881 881  
882 -= 11.  Reference material =
636 += 9.  Reference material =
883 883  
884 884  
885 -* 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]]
886 -* schematic: [[LTS5-V1>>https://www.dropbox.com/scl/fo/grwr5b4x1tk2omyjwg06y/ACleSdi5f7p5zRB2mfPH7CE?rlkey=vhcs83jrj9tkmw8wa9m9wo5rx&st=hkhe3bbj&dl=0]]
887 -* 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]]
639 +* Datasheet
640 +* Source Code
888 888  * Mechinical
889 889  
890 -= 12. FCC Warning =
643 += 10. FCC Warning =
891 891  
892 892  
893 893  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
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