Wiki source code of LTS5 LoRa HMI Touch Screen

Version 135.1 by Dilisi S on 2024/12/26 18:50

version	line-number	content
133.2	1
	2
56.1	3	(% style="text-align:center" %)
133.2	4	[[image:image-20241226135550-1.png]]
2.1	5
	6
56.1	7
	8
2.1	9	(% _mstvisible="1" %)
56.1	10	(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)Table of Contents:
2.1	11
	12	{{toc/}}
	13
	14
	15
	16
	17
	18
	19
	20
	21	= 1. Introduction =
	22
116.1	23	== 1.1 What is the LTS5 LoRa HMI Touch Screen? ==
2.1	24
56.1	25
116.1	26	The LTS5 is a (% style="color:blue" %)LoRa / LoRaWAN HMI Touch Screen(%%) designed for displaying information in IoT projects. It features a 5.0-inch HMI touch screen and supports Wi-Fi, Bluetooth, and LoRa wireless protocols.
2.1	27
116.1	28	The LTS5 is an open-source software project powered by an ESP32 MCU and a Dragino LA66 LoRa module. The extensive development resources available for ESP32 can significantly reduce development time.
2.1	29
116.1	30	The LTS5's HMI touch screen supports drag-and-drop design, allowing developers to use SquareLine to easily customize the display UI for various applications.
2.1	31
116.1	32	The LA66 LoRa module can be programmed to support either private LoRa protocols or the LoRaWAN protocol.
2.1	33
	34	== 1.2 Features ==
	35
115.1	36
55.1	37	* ESP32-WROOM MCU: 8MB RAM & 16MB ROM
	38	* Dragino LA66 LoRa Module
4.2	39	* Support Private LoRa protocol or LoRaWAN protocol
	40	* Support WiFi & BLE wireless protocol
	41	* 5.0" HMI touch screen
4.6	42	* Support LVGL case. SquareLine program.
4.2	43	* Support RS485 Interface
	44	* Open Source Project
2.1	45	* Wall Attachable.
4.2	46	* 5V DC power
2.1	47	* IP Rating: IP52
	48
116.1	49	== 1.3 Specifications ==
2.1	50
56.1	51
4.9	52	LoRa:
	53
55.1	54	* Frequency Range: 870 MHz ~~ 960 MHz
	55	* TCXO crystal to ensure RF performance on low temperature
	56	* Maximum Power +22 dBm constant RF output
	57	* High sensitivity: -148 dBm
	58	* LoRa Tx Current: <90 mA at +17 dBm, 108 mA at +22 dBm
	59	* LoRa Rx current: <9 mA
4.9	60
4.7	61	WiFi:
	62
	63	* 802.11b/g/n
	64	* Up to 150 Mbps data rate in 802.11n mode
	65	* Support A-MPDU and A-MSDU aggregation
	66	* zero point four μ S protection interval
	67	* Working channel center frequency range: 2412~~2484 MHz
	68
	69	Bluetooth:
	70
	71	* Bluetooth V4.2 BR/EDR and Bluetooth LE standard
	72	* Class-1, Class-2, and Class-3 transmitters.
	73	* AFH
	74	* CVSD and SBC
	75
4.2	76	Display:
2.1	77
4.9	78	* 5.0 Inch , 800 x 480
	79	* IPS Capacitive Touch SCreen
4.11	80	* RGB color.
	81	* Display Area: 120.7*75.80 mm
2.1	82
	83	== 1.4 Power Consumption ==
	84
56.1	85
4.5	86	* External 5V DC power adapter
2.1	87
	88	== 1.5 Storage & Operation Temperature ==
	89
56.1	90
4.10	91	* Operation Temperature: -20 ~~ 70°C (No Dew)
	92	* Storage Temperature: -30 ~~ 70°C (No Dew)
2.1	93
	94	== 1.6 Applications ==
	95
56.1	96
2.1	97	* Smart Buildings & Home Automation
	98	* Logistics and Supply Chain Management
	99	* Smart Metering
	100	* Smart Agriculture
	101	* Smart Cities
	102	* Smart Factory
	103
122.1	104	= 2. Getting Started with 'Hello World' =
2.1	105
5.1	106	== 2.1 About this demo ==
2.1	107
56.1	108
117.1	109	This getting started example demonstrates how to design and deploy a simple display UI for the LTS5 device. The example includes:
2.1	110
117.1	111	* Creating a basic UI with a single button.
	112	* Implementing functionality to navigate the Web UI to a new page when the button is clicked.
	113	* Uploading the UI to the LTS5 device.
56.1	114
117.1	115	By completing this demo, you will gain foundational knowledge for customizing the LTS5 interface and building more advanced IoT applications.
	116
	117
5.1	118	== 2.2 Install Software Running Environment ==
2.1	119
115.1	120
120.1	121	The ESP MCU supports development with ESP-IDF, Arduino, or MicroPython. We use ESP-IDF for compilation and Visual Studio Code (VS Code) as the development environment for this project.
2.1	122
115.1	123
120.1	124	=== 2.2.1 Install VS Code and ESP-IDF extension ===
26.2	125
56.1	126
120.1	127	First, download and install VS Code for your operating system from the Visual Studio Code website: [[Visual Studio Code - Mac, Linux, Windows>>https://code.visualstudio.com/download]].
26.2	128
120.1	129	Next, install the ESP-IDF extension within VS Code. Detailed steps for this process are shown in Image 1.
26.2	130
120.1	131
51.2	132	[[image:image-20240928110211-5.png\|\|height="508" width="866"]]
	133
120.1	134	Image 1: ESP-IDF extension install
26.2	135
	136	Links for reference: [[Install ESP32 ESP-IDF on Windows and Integrate with VS code (esp32tutorials.com)>>url:https://esp32tutorials.com/install-esp32-esp-idf-windows-integrate-vs-code/#:~~:text=In%20this%20tutorial,%20we%20will%20show%20you%20how%20to%20install]]
	137
56.1	138
5.1	139	=== 2.2.2 Install SquareLine Studio ===
2.1	140
56.1	141
125.1	142	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.
2.1	143
133.2	144	[[image:squareline.io_downloads.png\|\|height="888" width="1294"]]
2.1	145
56.1	146
121.1	147	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:
120.1	148
121.1	149	* Max. 10 screens
	150	* Max. 150 widgets
	151	* Max. 5 global colors
	152	* Max. 2 themes
	153	* Max. 1 component
120.1	154
121.1	155	== 2.3 Simple usage of SquareLine Studio and exporting UI code ==
2.1	156
56.1	157
131.1	158	Start the SquareLine Studio. The launcher screen appears as shown in the below image. You can create a new project by clicking Create in the top menu. Then select the Desktop tab. Select the development platform, Eclipse with SDL for development on PC.
2.1	159
125.1	160	* In the PROJECT SETTINGS, select LVGL version as 8.3.11 and Resolution as 800 x 480.
	161	* Select the CREATE button to create the new project with the selected settings.
121.1	162
133.2	163	[[image:squareline-studio-launcher-screen.png\|\|height="752" width="1415"]]
26.2	164
	165
131.1	166	Next, you need to configure some additional settings for this project. To do so, select File -> Project Settings as shown in the image below.
	167
26.2	168	[[image:1727229582471-566.png]]
	169
	170
131.1	171	In the PROJECT SETTINGS dialog box, configure/modify the project settings as shown in the image below.
121.1	172
	173	* UI Files Export Root: Select a folder on your computer to store the UI files.
	174	* LVGL Include Path: Set this to lvgl.h
131.1	175	* Click on the APPLY CHANGES button.
121.1	176
51.2	177	[[image:image-20240928105309-4.png\|\|height="526" width="556"]]
	178
26.2	179
131.1	180	Now you can start building the user interface. Follow the steps below:
26.2	181
121.1	182
123.2	183	=== Add widgets ===
26.2	184
123.2	185
131.1	186	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.
26.2	187
51.2	188	[[image:image-20240928111412-6.png\|\|height="526" width="864"]]
26.2	189
	190
131.1	191	Then click the Screen widget to add the second screen. After adding the second screen, it will appear in the Screens panel as Screen2.
26.2	192
131.1	193	[[image:Screenshot 2024-12-24 140459.png\|\|height="278" width="290"]]
	194
123.2	195	=== Modify widget properties ===
	196
	197
131.1	198	The area for modifying widgets is called the Inspector panel. The Inspector panel consists of four sections: COMPONENT, <WIDGET>, STYLE SETTINGS, and EVENTS, as shown in the image below. The second section allows you to adjust a widget's layout, size, position, alignment, flags, states, and more. When you select a widget on the screen, the name of this section changes to match the name of the selected widget.
26.2	199
51.2	200	[[image:1727485118799-984.png]]
26.2	201
	202
123.2	203	==== Changing the Button properties ====
122.1	204
123.2	205
131.1	206	Click the Button you have added to the screen. Under the Layout you can change the button's position and size. Use the following settings:
122.1	207
131.1	208	* Flex Flow: No Layout
	209	* Transform:
	210	X**: 331 px
	211	Y**: 203 px
	212	Width**: 100 px
	213	Height**: 50 px
	214	Align**: CENTER
122.1	215
51.2	216	[[image:1727485251053-655.png]]
26.2	217
	218
123.1	219	Next, add a click event to the button. When the button is clicked, an event should trigger to change the current screen (Screen1) to a new screen (Screen2) with a fade effect and the transition from Screen1 to Screen2 should take 500ms.
26.2	220
131.1	221	* Click ADD EVENT button. A new section will appear to configure this event.
26.2	222
131.1	223	[[image:Screenshot 2024-12-24 134937.png\|\|height="80" width="290"]]
	224
	225	* Select CLICKED from the dropdown under Trigger. Choose CHANGE SCREEN under Action, then click the ADD button. A new section will appear to configure the action.
	226
	227	[[image:Screenshot 2024-12-24 134818.png\|\|height="222" width="290"]]
	228
	229	* Select Screen2 under Screen to. Select FADE ON from Fade mode. The default value 500 means the transition takes 500 milliseconds to appear the Screen2.
	230	* Finally, click the ADD button.
	231
51.2	232	[[image:1727485480434-713.png\|\|height="395" width="290"]]
26.2	233
123.2	234	Image 8: Add an event for the button
51.2	235
	236
123.2	237	==== Changing the label properties ====
51.2	238
123.2	239
131.1	240	Click the Label you have added to the screen. Under the Label section, type "Click for Detail" in the Text textbox.
122.1	241
51.2	242	[[image:image-20240928090825-1.png\|\|height="327" width="391"]]
	243
	244
131.1	245	Once you enter the text, it will immediately appear on the label.
51.2	246
131.1	247
123.2	248	==== Changing image properties ====
122.1	249
123.2	250
131.1	251	To use the Image widget, you should first add an image to your project. The image format must be PNG, and its resolution should not exceed 800x480 pixels. There are two ways to add an image file.
51.2	252
131.1	253	One way is to move your image into the folder "…/squareline project/assets/", as shown in the image below.
	254
51.2	255	[[image:image-20240928113424-9.png\|\|height="355" width="505"]]
	256
	257
131.1	258	The other way is to click the "ADD FILE INTO ASSETS" button, then select an image from your computer to import. After adding, you can see the image in the "assets" panel in SquareLine Studio, as shown in the image below.
	259
51.2	260	[[image:image-20240928114139-10.png\|\|height="559" width="810"]]
	261
	262
123.2	263	==== The relationship between widgets ====
51.2	264
123.2	265
123.1	266	Widgets commonly have two types of relationships: parallel and parent-child.
	267
	268	* In a parallel relationship, widgets' positions are determined relative to a shared reference object.
132.1	269	* In a parent-child relationship, any part of the child object outside the parent's boundaries is hidden by default. To make the child object fully visible, you must adjust its position to fit within the parent's range.
123.1	270
51.2	271	[[image:1727486567182-334.png\|\|height="318" width="278"]]
	272
	273
131.1	274	Move the label, Label1 to make it a child of Button1 as shown in the image below.
123.1	275
51.2	276	[[image:image-20240928112001-8.png\|\|height="431" width="796"]]
	277
	278
131.1	279	Then set the X and Y position of the label to 0 as shown in the image below. The label will appear on the button. If you move the button on the screen, the label will move along with it as part of the button.
51.2	280
131.1	281	[[image:Screenshot 2024-12-24 144005.png\|\|height="360" width="290"]]
	282
	283
123.2	284	==== Preview the screen ====
51.2	285
123.2	286
132.1	287	You can test the result by clicking on the PLAY button as shown in the image below. The screen will change into play mode.
122.1	288
51.2	289	[[image:1727487368023-281.png]]
	290
	291
123.1	292	For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~\| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
51.2	293
123.1	294
26.2	295	== 2.4 Integrate UI Code to ESP-IDF Project ==
	296
56.1	297
132.1	298	To integrate, first export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
26.2	299
135.1	300	On the menubar, click Export -> Export UI Files as shown in the image below.
	301
26.2	302	[[image:1727229798126-306.png]]
	303
	304
135.1	305	The exported UI files can be found in your SquareLine project folder as shown in the image below.
	306
	307
51.2	308	[[image:1727229821582-258.png\|\|height="333" width="662"]]
26.2	309
	310
135.1	311	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.
26.2	312
54.1	313	[[image:image-20240928144830-11.png]]
26.2	314
	315
135.1	316	Open the CMakeLists.txt file and edit it as ahown below.
	317
51.2	318	[[image:1727229892636-154.png\|\|height="521" width="407"]]
26.2	319
	320
135.1	321	Open the main.c file and add two lines of code as shown in the below images.
132.1	322
135.1	323	Add #include "ui.h"
26.2	324
	325	[[image:1727229926561-300.png]]
	326
	327
135.1	328	Add ui_init();
	329
26.2	330	[[image:1727229955611-607.png]]
	331
	332
135.1	333	== 2.5 Brief introduction to the Hello World project ==
56.1	334
2.1	335
135.1	336	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.
56.1	337
51.2	338
	339	== 2.6 Test Result ==
	340
56.1	341
135.1	342	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.
2.1	343
135.1	344	Screen 1:
	345
51.2	346	[[image:1727488067077-684.png\|\|height="402" width="574"]]
26.2	347
	348
135.1	349	Screen 2:
	350
51.2	351	[[image:1727488157579-949.png\|\|height="397" width="572"]]
26.2	352
	353
5.1	354	= 3. Example Project 1: LoRa Central Display =
2.1	355
7.1	356	[[image:image-20240916101737-1.png\|\|height="468" width="683"]]
2.1	357
7.1	358
8.1	359	= 4. Example Project 2: LoRaWAN RS485 Alarm =
2.1	360
135.1	361	= 5. Adding new panel to the project =
2.1	362
123.2	363
135.1	364	~1. Design a panel in SquareLine Studio, as shown in Image 5.1 below for reference.
75.1	365
	366	[[image:image-20241121113445-1.png\|\|height="584" width="934"]]
	367
135.1	368	Image 5.1: a panel about water_leak
75.1	369
123.2	370
135.1	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.
75.1	372
	373	[[image:image-20241121141120-4.png\|\|height="383" width="795"]]
	374
135.1	375	Image 5.2: Exported UI files
75.1	376
123.2	377
135.1	378	3. Delete and rename some file. Here are the steps:
75.1	379
135.1	380	Step 1: Delete the 'components' directory.
	381	Step 2: Delete 'filelist.txt'.
	382	Step 3: Delete 'ui_helpers.c' and 'ui_helpers.h'.
	383	Step 4: Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
	384	Step 5: Rename the 'screens' directory to 'styles'.
75.1	385
	386	[[image:image-20241121151934-10.png\|\|height="303" width="792"]]
	387
113.2	388	image 5.3 rest file (1)
75.1	389
	390	[[image:image-20241121142925-7.png\|\|height="141" width="793"]]
	391
113.2	392	image 5.4 rest file (2)
75.1	393
135.1	394	4. Open the project in VS Code.
75.1	395
135.1	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."
75.1	397
	398	[[image:image-20241121181957-17.png\|\|height="438" width="516"]]
	399
113.2	400	image 5.5 extra_lib/CMakeLists.txt before add
75.1	401
	402	[[image:image-20241121182239-18.png\|\|height="520" width="518"]]
	403
113.2	404	image 5.6 extra_lib/CMakeLists.txt after add
75.1	405
135.1	406	6. Modify the header files included in the fonts and images directories.
75.1	407
135.1	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.
	409
75.1	410	[[image:image-20241121171629-11.png]]
	411
113.2	412	image 5.7 before-modified font file
75.1	413
	414	[[image:image-20241121171901-12.png]]
	415
	416	image 5.8 modified font file
	417
135.1	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.
75.1	419
	420	[[image:image-20241121172714-13.png]]
	421
	422	image 5.9 before-modified image file
	423
	424	[[image:image-20241121172908-14.png]]
	425
	426	image 5.10 modified image file
	427
135.1	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).
75.1	429
	430	[[image:image-20241121180030-15.png]]
	431
113.2	432	image 5.11 ui_water_leak/CMakeLists.txt before modification
75.1	433
	434	[[image:image-20241121180517-16.png]]
	435
113.2	436	image 5.12 ui_water_leak/CMakeLists.txt after modification
75.1	437
	438
135.1	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.
	440
113.2	441	[[image:image-20241122094200-23.png]]
75.1	442
113.2	443	image 5.13 ui_water_leak.h (1) before modification
75.1	444
113.2	445	[[image:image-20241122094320-24.png\|\|height="852" width="554"]]
75.1	446
113.2	447	image 5.14 ui_water_leak.h (2) before modification
75.1	448
113.2	449	[[image:image-20241122094600-25.png\|\|height="1078" width="554"]]
75.1	450
113.2	451	image 5.15 ui_water_leak.h (1) after modification
75.1	452
113.2	453	[[image:image-20241122094719-26.png\|\|height="941" width="583"]]
75.1	454
113.2	455	image 5.16 ui_water_leak.h (2) before modification
75.1	456
113.2	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.
75.1	458
113.2	459	_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.
75.1	460
113.2	461	[[image:image-20241122102929-27.png\|\|height="619" width="426"]]
	462
	463	image 5.17 ui_water_leak.c (1) before modification
	464
	465	[[image:image-20241122112838-30.png\|\|height="551" width="628"]]
	466
	467	image 5.18 ui_water_leak.c (2) before modification
	468
	469	[[image:image-20241122110815-29.png\|\|height="725" width="712"]]
	470
	471	image 5.19 ui_water_leak.c (3) before modification
	472
	473	[[image:image-20241122113158-31.png\|\|height="872" width="677"]]
	474
	475	image 5.20 ui_water_leak.c (1) after modification
	476
	477	[[image:image-20241122113259-33.png\|\|height="874" width="724"]]
	478
	479	image 5.21 ui_water_leak.c (2) after modification
	480
	481	[[image:image-20241122113359-34.png\|\|height="804" width="746"]]
	482
	483	image 5.22 ui_water_leak.c (3) after modification
	484
	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.
	486
	487	[[image:image-20241122134113-35.png\|\|height="380" width="421"]]
	488
	489	image 5.23 ui_water_leak_events_.h before modification
	490
	491	[[image:image-20241122134420-37.png\|\|height="201" width="283"]]
	492
	493	image 5.24 ui_water_leak_events_.h after modification
	494
	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.
	496
	497	Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
	498
	499	Step2. add code below in delete_object() function definition.
	500
	501	panel_all * panel = find_upper_by_SensorPanel(&arr,((lv_obj_t *)(e->user_data~)~)~);
	502
	503	size_t index = panel->panel_obj_index;
	504
	505	deleteElement(&arr, index);
	506
	507	[[image:image-20241122135023-38.png\|\|height="358" width="372"]]
	508
	509	image 5.25 ui_water_leak_events_.c before modification
	510
	511	[[image:image-20241122135258-39.png\|\|height="403" width="559"]]
	512
	513	image 5.26 ui_water_leak_events_.c after modification
	514
123.2	515
113.2	516	12. Modify ui_water_leak_style.c file.
	517
	518	Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
	519
	520	add '#include "../../sort.h"'
	521
	522	add '#include "ui.h"'
	523
	524	[[image:image-20241122141536-41.png\|\|height="361" width="612"]]
	525
	526	image 5.27 ui_water_leak_style.c (1) before modification
	527
	528	[[image:image-20241122142129-42.png\|\|height="386" width="613"]]
	529
	530	image 5.28 ui_water_leak_style.c (1) after modification
	531
123.2	532
113.2	533	Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
	534
	535	delete code as shown in image 5.29
	536
	537	[[image:image-20241122145620-44.png\|\|height="757" width="671"]]
	538
	539	image 5.29 ui_water_leak_style.c (2)
	540
123.2	541
113.2	542	Step3. The image 5.30, 5.31 show the change.
	543
	544	[[image:image-20241122152026-45.png\|\|height="277" width="828"]]
	545
	546	image 5.30 ui_water_leak_style.c (3) before modification
	547
	548	[[image:image-20241122152542-46.png\|\|height="293" width="830"]]
	549
	550	image 5.31 ui_water_leak_style.c (3) after modification
	551
123.2	552
113.2	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).
	554
	555	[[image:image-20241122153958-47.png]]
	556
	557	image 5.32 ui_water_leak_style.c (4)
	558
	559	[[image:image-20241122154755-49.png\|\|height="864" width="513"]]
	560
	561	image 5.33 ui_water_leak_style.c (4)
	562
123.2	563
113.2	564	Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
	565
	566	[[image:image-20241122155650-50.png\|\|height="922" width="513"]]
	567
	568	image 5.34 ui_water_leak_style.c (5)
	569
123.2	570
113.2	571	Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
	572
	573	[[image:image-20241122161934-51.png]]
	574
	575	image 5.35
	576
123.2	577
113.2	578	Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
	579
	580	[[image:image-20241122162852-53.png\|\|height="330" width="529"]]
	581
	582	image 5.37
	583
123.2	584
113.2	585	Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
	586
	587	panel_with_type union_sensor;
	588
	589	union_sensor.panel_type = WATER_LEAK_TYPE;
	590
	591	......
	592
	593	lv_obj_set_x(union_sensor.panel_union.door.ui_PanelSensorDoor, x_by_index(index));
	594
	595	lv_obj_set_y(union_sensor.panel_union.door.ui_PanelSensorDoor, y_by_index(index));
	596
	597	return union_sensor;
	598
	599	[[image:image-20241122171211-54.png\|\|height="635" width="792"]]
	600
	601	image 5.38
	602
123.2	603
113.2	604	13. Modify sort.c file.
	605
	606	Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
	607
	608	[[image:image-20241122173718-56.png\|\|height="378" width="579"]]
	609
	610	image 5.39 sort.c (1)
	611
	612	There are still some changes need to be done in sort.c, and omit here for the moment.
	613
	614
2.1	615	= 6. FAQ =
	616
7.1	617	== 6.1 ==
2.1	618
	619
	620	= 7. Order Info =
	621
4.4	622	== 7.1 Part Number ==
2.1	623
56.1	624
4.4	625	Part Number: (% style="color:#4472c4" %)LTS5
2.1	626
	627
4.4	628	== 7.2 Packing Info ==
2.1	629
56.1	630
4.4	631	Package Includes:
2.1	632
4.4	633	* LTS5 HMI Touch Screen
	634	* 5V,2A DC Power Adapter.
	635	* USB Type C Program Cable
2.1	636
	637	= 8. Support =
	638
56.1	639
2.1	640	* 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.
	641	* 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]].
	642
	643	= 9. Reference material =
	644
56.1	645
4.2	646	* Datasheet
	647	* Source Code
4.3	648	* Mechinical
2.1	649
	650	= 10. FCC Warning =
	651
	652
	653	This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
	654
	655	(1) This device may not cause harmful interference;
	656
	657	(2) this device must accept any interference received,including interference that may cause undesired operation.
	658

Wiki source code of LTS5 LoRa HMI Touch Screen

Applications

Navigation