Skip to Content
Last modified by BoYang Xie on 2025/07/09 11:46
From version 55.1
edited by Edwin Chen
on 2024/10/09 10:25
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.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -1,9 +1,13 @@
1 -
2 -[[image:image-20240915231842-1.png]]
1 +
3 3  
3 +(% style="text-align:center" %)
4 +[[image:image-20241226135550-1.png]]
4 4  
6 +
7 +
8 +
5 5  (% _mstvisible="1" %)
6 -(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents：**
10 +(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:**
7 7  
8 8  {{toc/}}
9 9  
... ... @@ -16,19 +16,20 @@
16 16  
17 17  = 1.  Introduction =
18 18  
19 -== 1.1  What is LTS5 LoRa HMI touch screen ==
23 +== 1.1  What is the LTS5 LoRa HMI Touch Screen? ==
20 20  
21 -LTS5 is a (% style="color:blue" %)LoRa / LoRaWAN HMI Touch Screen(%%) designed for display purpose of IoT project. It have a 5.0" HMI touch screen, and support WiFi, Bluetooch, LoRa wireless protocol.
22 22  
23 -LTS5 is an Open Source software project. The MCU is ESP32 and Dragino LA66 LoRa module. There are lots of development source for ESP32 which can greatly reduce the development time.
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.
24 24  
25 -The HMI touch screen of LTS5 supports drap & drop design. Developer can use SquareLine to easily customize the display UI for different application.
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.
26 26  
27 -LTS5 use LA66 LoRa module, this module can be program to support private LoRa protocol or LoRaWAN protocol.
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.
28 28  
32 +The LA66 LoRa module can be programmed to support either private LoRa protocols or the LoRaWAN protocol.
29 29  
30 30  == 1.2  Features ==
31 31  
36 +
32 32  * ESP32-WROOM MCU: 8MB RAM & 16MB ROM
33 33  * Dragino LA66 LoRa Module
34 34  * Support Private LoRa protocol or LoRaWAN protocol
... ... @@ -41,8 +41,9 @@
41 41  * 5V DC power
42 42  * IP Rating: IP52
43 43  
44 -== 1.3  Specification ==
49 +== 1.3  Specifications ==
45 45  
51 +
46 46  **LoRa**:
47 47  
48 48  * Frequency Range: 870 MHz ~~ 960 MHz
... ... @@ -76,15 +76,18 @@
76 76  
77 77  == 1.4  Power Consumption ==
78 78  
85 +
79 79  * External 5V DC power adapter
80 80  
81 81  == 1.5  Storage & Operation Temperature ==
82 82  
90 +
83 83  * Operation Temperature: -20 ~~ 70°C  (No Dew)
84 84  * Storage Temperature: -30 ~~ 70°C  (No Dew)
85 85  
86 86  == 1.6  Applications ==
87 87  
96 +
88 88  * Smart Buildings & Home Automation
89 89  * Logistics and Supply Chain Management
90 90  * Smart Metering
... ... @@ -92,132 +92,202 @@
92 92  * Smart Cities
93 93  * Smart Factory
94 94  
95 -= 2.  Getting Started with Hello World =
104 += 2.  Getting Started with 'Hello World' =
96 96  
97 97  == 2.1  About this demo ==
98 98  
99 -In this Getting Started Example, we will show how to design a simple Display UI and upload it to LTS5. This UI has  a button , when user click the button. The Web UI will jump to a new page.
100 100  
109 +This getting started example demonstrates how to design and deploy a simple display UI for the LTS5 device. The example includes:
110 +
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.
114 +
115 +By completing this demo, you will gain foundational knowledge for customizing the LTS5 interface and building more advanced IoT applications.
116 +
117 +
101 101  == 2.2  Install Software Running Environment ==
102 102  
103 -The ESP MCU can be developed using ESP-IDF, Arduino, or MicroPython. For this project, we utilize ESP-IDF for compilation and Visual Studio Code (VSCode) for editing.
104 104  
105 -=== 2.2.1 Install VSCode and ESP-IDF extension ===
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.
106 106  
107 -Firstly, download and install VSCode for your computer's operating system from the official website: [[Download Visual Studio Code - Mac, Linux, Windows>>url:https://code.visualstudio.com/download]].
108 108  
109 -Next, you need to install the ESP-IDF extension within VSCode. The detailed operation steps are illustrated in image 1.
124 +=== 2.2.1 Install VS Code and ESP-IDF extension ===
110 110  
126 +
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]].
128 +
129 +Next, install the **ESP-IDF** extension within **VS Code**. Detailed steps for this process are shown in Image 1.
130 +
131 +
111 111  [[image:image-20240928110211-5.png||height="508" width="866"]]
112 112  
113 - image 1 ESP-IDF extension install
134 + Image 1: ESP-IDF extension install
114 114  
115 115  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]]
116 116  
138 +
117 117  === 2.2.2 Install SquareLine Studio ===
118 118  
119 -The version we are utilizing for this software is 1.4.2. You can download it from the official link: [[SquareLine Studio - Download the current version of SquareLine Studio>>url:https://squareline.io/downloads#lastRelease]].
120 120  
121 -Please note that this software necessitates the registration of a license prior to usage, and various licenses come with distinct limitations. For instance, the free version imposes restrictions such as a limit of 1 component, 150 widgets, and 10 screens. However, for first-time downloads, you are granted unrestricted access for a period of 30 days without the need for immediate registration.
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.
122 122  
123 -== 2.3 Simple usage of SquareLine Studio and export UI code ==
144 +[[image:squareline.io_downloads.png||height="888" width="1294"]]
124 124  
125 -After launching and logging in to this software, create a project as shown in the following image 2. The version of LVGL is 8.3.11.
126 126  
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:
127 127  
128 -[[image:image-20240928103357-2.png||height="680" width="708"]]
149 +* Max. 10 screens
150 +* Max. 150 widgets
151 +* Max. 5 global colors
152 +* Max. 2 themes
153 +* Max. 1 component
129 129  
130 - image 2 create a SquareLine project
155 +== 2.3 Simple usage of SquareLine Studio and exporting UI code ==
131 131  
132 -Next, we need to make some settings for this project. By clicking in the specified order on image 3, we can see the page as shown in image 4.
133 133  
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**.
159 +
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.
162 +
163 +[[image:squareline-studio-launcher-screen.png||height="752" width="1415"]]
164 +
165 +
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 +
134 134  [[image:1727229582471-566.png]]
135 135  
136 - image 3 project settings
137 137  
171 +In the **PROJECT SETTINGS** dialog box, configure/modify the project settings as shown in the image below.
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**
175 +* Click on the **APPLY CHANGES** button.
176 +
138 138  [[image:image-20240928105309-4.png||height="526" width="556"]]
139 139  
140 - image 4 modify project settings
141 141  
142 -Now we can start to use this software. Here are some usage information for this software.
180 +Now you can start building the user interface. Follow the steps below:
143 143  
144 -**1.add widget**
145 145  
146 -To add a widget, you should click a widget you want to add at the area entitled “Widgets”. In image , demonstrate a add process of label, button, and image 5.
183 +=== **Add widgets** ===
147 147  
185 +
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.
187 +
148 148  [[image:image-20240928111412-6.png||height="526" width="864"]]
149 149  
150 - image 5 add widgets
151 151  
152 -**2.modify widget**
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**.
153 153  
154 -The area for modifying widgets is called "Inspector". There are four parts in the "Inspector" tab. We use three of them more frequently, excluding "COMPONENT". The second part is aimed at adjusting the layout, size, position, alignment, flags, and states, etc. of widgets. The name of the second part indicates the type of widget it is representing, and in image 6, it is "BUTTON".
193 +[[image:Screenshot 2024-12-24 140459.png||height="278" width="290"]]
155 155  
195 +=== **Modify widget properties** ===
196 +
197 +
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.
199 +
156 156  [[image:1727485118799-984.png]]
157 157  
158 - image 6 the button widget's "Inspector" tab
159 159  
160 -Second part: "Layout" means a auto position-management for widgets contained in the parent widget. "Transform" includes size, position and align modification.
203 +==== **Changing the Button properties** ====
161 161  
205 +
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:
207 +
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
215 +
162 162  [[image:1727485251053-655.png]]
163 163  
164 -image 7 the button widget's "BUTTON" tab
165 165  
166 -Third part: It is an area of style setting.
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.
167 167  
168 -Fourth part: It is an area for adding events. In image 8, it is adding a click event to a button. If the button is clicked after the click event is added as shown in image 8, the current screen will fade into another specified screen, and the switching process will last 500ms.
221 +* Click **ADD EVENT** button. A new section will appear to configure this event.
169 169  
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 +
170 170  [[image:1727485480434-713.png||height="395" width="290"]]
171 171  
172 - image 8 add event for button
234 + Image 8: Add an event for the button
173 173  
174 -**3.change label widget content**
175 175  
176 -Modify the content in text as shown in image 9, the text content of label widget will be changed accordingly.
237 +==== **Changing the label properties** ====
177 177  
239 +
240 +Click the Label you have added to the screen. Under the **Label** section, type "**Click for Detail**" in the **Text** textbox.
241 +
178 178  [[image:image-20240928090825-1.png||height="327" width="391"]]
179 179  
180 - image 9 modify text content of label widget
181 181  
182 -**4.Add image into project**
245 +Once you enter the text, it will immediately appear on the label.
183 183  
184 -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. One way is to move your image into the folder "…/squareline project/assets/", as shown in image 10. 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" area in SquareLine Studio, as demonstrated in image 11.
185 185  
248 +==== **Changing image properties** ====
249 +
250 +
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.
252 +
253 +One way is to move your image into the folder "…/squareline project/assets/", as shown in the image below.
254 +
186 186  [[image:image-20240928113424-9.png||height="355" width="505"]]
187 187  
188 - image 10 add image file into SquareLine Studio project
189 189  
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 +
190 190  [[image:image-20240928114139-10.png||height="559" width="810"]]
191 191  
192 - image 11 use image widget in SquareLine Studio
193 193  
194 -**5.The relationship between widgets**
263 +==== **The relationship between widgets** ====
195 195  
196 -There are two common relationships between widgets: one is parallel, the other is parent-child. The parallel relationship means that widgets' relative position is based on a collective object of reference. In parent-child relationship, the parts of the child object that are outside the boundaries of the parent object are not visible by default. Therefore, we need to adjust the position of the child object so that it falls within the range of the parent object, allowing it to be seen as illustrated in image 13.
197 197  
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.
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.
270 +
198 198  [[image:1727486567182-334.png||height="318" width="278"]]
199 199  
200 -image 12 move label1 to make label1 widget be a child of button1 widget(1)
201 201  
274 +Move the label, **Label1** to make it a child of **Button1** as shown in the image below.
275 +
202 202  [[image:image-20240928112001-8.png||height="431" width="796"]]
203 203  
204 - image 13 move label1 to make label1 widget be a child of button1 widget(2)
205 205  
206 -**6.Preview the final effect**
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.
207 207  
208 -An advantage of this kind of software is that you can edit the UI with quick previews. In other words, it provides a way of combining graphical programming with simulation immediately.
281 +[[image:Screenshot 2024-12-24 144005.png||height="360" width="290"]]
209 209  
283 +
284 +==== **Preview the screen** ====
285 +
286 +
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.
288 +
210 210  [[image:1727487368023-281.png]]
211 211  
212 - image 14 click on the triangle icon to start or end the simulation
213 213  
214 -For more detailed usage, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
292 +For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
215 215  
216 216  
217 217  == 2.4 Integrate UI Code to ESP-IDF Project ==
218 218  
219 -To achieve the integrating, we first need to export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
220 220  
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.
299 +
221 221  [[image:1727229798126-306.png]]
222 222  
223 223   image 15 export UI file
... ... @@ -236,6 +236,7 @@
236 236  
237 237   image 18 modify CMakeLists.txt
238 238  
318 +
239 239  The last step of integrating is adding two lines of code in main.c file.
240 240  
241 241  [[image:1727229926561-300.png]]
... ... @@ -246,12 +246,16 @@
246 246  
247 247   image 20 add "ui_init()"
248 248  
329 +
249 249  == 2.5 Brief introduction of hello world project ==
250 250  
332 +
251 251  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.
252 252  
335 +
253 253  == 2.6 Test Result ==
254 254  
338 +
255 255  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.
256 256  
257 257  [[image:1727488067077-684.png||height="402" width="574"]]
... ... @@ -262,15 +262,265 @@
262 262  
263 263   image 22 screen2
264 264  
349 +
265 265  = 3. Example Project 1: LoRa Central Display =
266 266  
267 267  [[image:image-20240916101737-1.png||height="468" width="683"]]
268 268  
269 269  
270 -
271 271  = 4. Example Project 2: LoRaWAN RS485 Alarm =
272 272  
357 += 5. The way to add a new panel to project =
273 273  
359 +
360 +**~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.**
361 +
362 +[[image:image-20241121113445-1.png||height="584" width="934"]]
363 +
364 + image 5.1 a panel about water_leak
365 +
366 +
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.
368 +
369 +[[image:image-20241121141120-4.png||height="383" width="795"]]
370 +
371 + image 5.2 ui files exported
372 +
373 +
374 +**3. Delete or rename some file.** Here are the steps:
375 +
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'.
381 +
382 +[[image:image-20241121151934-10.png||height="303" width="792"]]
383 +
384 + image 5.3 rest file (1)
385 +
386 +[[image:image-20241121142925-7.png||height="141" width="793"]]
387 +
388 + image 5.4 rest file (2)
389 +
390 +**4. Open this project in vscode.**
391 +
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.
393 +
394 +[[image:image-20241121181957-17.png||height="438" width="516"]]
395 +
396 + image 5.5 extra_lib/CMakeLists.txt before add
397 +
398 +[[image:image-20241121182239-18.png||height="520" width="518"]]
399 +
400 + image 5.6 extra_lib/CMakeLists.txt after add
401 +
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.
403 +
404 +[[image:image-20241121171629-11.png]]
405 +
406 + image 5.7 before-modified font file
407 +
408 +[[image:image-20241121171901-12.png]]
409 +
410 + image 5.8 modified font file
411 +
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.
413 +
414 +[[image:image-20241121172714-13.png]]
415 +
416 + image 5.9 before-modified image file
417 +
418 +[[image:image-20241121172908-14.png]]
419 +
420 + image 5.10 modified image file
421 +
422 +**7. Modify the ui_water_leak/CMakeLists.txt.** Open this file, and modify it from image 5.11 to image 5.12.
423 +
424 +[[image:image-20241121180030-15.png]]
425 +
426 + image 5.11 ui_water_leak/CMakeLists.txt before modification
427 +
428 +[[image:image-20241121180517-16.png]]
429 +
430 + image 5.12 ui_water_leak/CMakeLists.txt after modification
431 +
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.
433 +
434 +[[image:image-20241122094200-23.png]]
435 +
436 + image 5.13 ui_water_leak.h (1) before modification
437 +
438 +[[image:image-20241122094320-24.png||height="852" width="554"]]
439 +
440 + image 5.14 ui_water_leak.h (2) before modification
441 +
442 +[[image:image-20241122094600-25.png||height="1078" width="554"]]
443 +
444 + image 5.15 ui_water_leak.h (1) after modification
445 +
446 +[[image:image-20241122094719-26.png||height="941" width="583"]]
447 +
448 + image 5.16 ui_water_leak.h (2) before modification
449 +
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.
451 +
452 +_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.
453 +
454 +[[image:image-20241122102929-27.png||height="619" width="426"]]
455 +
456 + image 5.17 ui_water_leak.c (1) before modification
457 +
458 +[[image:image-20241122112838-30.png||height="551" width="628"]]
459 +
460 + image 5.18 ui_water_leak.c (2) before modification
461 +
462 +[[image:image-20241122110815-29.png||height="725" width="712"]]
463 +
464 + image 5.19 ui_water_leak.c (3) before modification
465 +
466 +[[image:image-20241122113158-31.png||height="872" width="677"]]
467 +
468 + image 5.20 ui_water_leak.c (1) after modification
469 +
470 +[[image:image-20241122113259-33.png||height="874" width="724"]]
471 +
472 + image 5.21 ui_water_leak.c (2) after modification
473 +
474 +[[image:image-20241122113359-34.png||height="804" width="746"]]
475 +
476 + image 5.22 ui_water_leak.c (3) after modification
477 +
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.
479 +
480 +[[image:image-20241122134113-35.png||height="380" width="421"]]
481 +
482 + image 5.23 ui_water_leak_events_.h before modification
483 +
484 +[[image:image-20241122134420-37.png||height="201" width="283"]]
485 +
486 +image 5.24 ui_water_leak_events_.h after modification
487 +
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.
489 +
490 +Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
491 +
492 +Step2. add code  below in delete_object() function definition.
493 +
494 + panel_all * panel = find_upper_by_SensorPanel(&arr,((lv_obj_t *)(e->user_data~)~)~);
495 +
496 + size_t index = panel->panel_obj_index;
497 +
498 + deleteElement(&arr, index);
499 +
500 +[[image:image-20241122135023-38.png||height="358" width="372"]]
501 +
502 + image 5.25 ui_water_leak_events_.c before modification
503 +
504 +[[image:image-20241122135258-39.png||height="403" width="559"]]
505 +
506 + image 5.26 ui_water_leak_events_.c after modification
507 +
508 +
509 +**12. Modify ui_water_leak_style.c file.**
510 +
511 +Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
512 +
513 + add '#include "../../sort.h"'
514 +
515 + add '#include "ui.h"'
516 +
517 +[[image:image-20241122141536-41.png||height="361" width="612"]]
518 +
519 + image 5.27 ui_water_leak_style.c (1) before modification
520 +
521 +[[image:image-20241122142129-42.png||height="386" width="613"]]
522 +
523 + image 5.28 ui_water_leak_style.c (1) after modification
524 +
525 +
526 +Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
527 +
528 + delete code as shown in image 5.29
529 +
530 +[[image:image-20241122145620-44.png||height="757" width="671"]]
531 +
532 + image 5.29 ui_water_leak_style.c (2)
533 +
534 +
535 +Step3. The image 5.30, 5.31 show the change.
536 +
537 +[[image:image-20241122152026-45.png||height="277" width="828"]]
538 +
539 + image 5.30 ui_water_leak_style.c (3) before modification
540 +
541 +[[image:image-20241122152542-46.png||height="293" width="830"]]
542 +
543 + image 5.31 ui_water_leak_style.c (3) after modification
544 +
545 +
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).
547 +
548 +[[image:image-20241122153958-47.png]]
549 +
550 + image 5.32 ui_water_leak_style.c (4)
551 +
552 +[[image:image-20241122154755-49.png||height="864" width="513"]]
553 +
554 + image 5.33 ui_water_leak_style.c (4)
555 +
556 +
557 +Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
558 +
559 +[[image:image-20241122155650-50.png||height="922" width="513"]]
560 +
561 + image 5.34 ui_water_leak_style.c (5)
562 +
563 +
564 +Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
565 +
566 +[[image:image-20241122161934-51.png]]
567 +
568 + image 5.35
569 +
570 +
571 +Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
572 +
573 +[[image:image-20241122162852-53.png||height="330" width="529"]]
574 +
575 + image 5.37
576 +
577 +
578 +Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
579 +
580 +panel_with_type union_sensor;
581 +
582 +union_sensor.panel_type = WATER_LEAK_TYPE;
583 +
584 +......
585 +
586 +lv_obj_set_x(union_sensor.panel_union.door.ui_PanelSensorDoor, x_by_index(index));
587 +
588 +lv_obj_set_y(union_sensor.panel_union.door.ui_PanelSensorDoor, y_by_index(index));
589 +
590 +return union_sensor;
591 +
592 +[[image:image-20241122171211-54.png||height="635" width="792"]]
593 +
594 + image 5.38
595 +
596 +
597 +**13. Modify sort.c file.**
598 +
599 +Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
600 +
601 +[[image:image-20241122173718-56.png||height="378" width="579"]]
602 +
603 + image 5.39 sort.c (1)
604 +
605 +There are still some changes need to be done in sort.c, and omit here for the moment.
606 +
607 +
274 274  = 6. FAQ =
275 275  
276 276  == 6.1 ==
... ... @@ -280,11 +280,13 @@
280 280  
281 281  == 7.1  Part Number ==
282 282  
617 +
283 283  Part Number: (% style="color:#4472c4" %)LTS5
284 284  
285 285  
286 286  == 7.2  Packing Info ==
287 287  
623 +
288 288  **Package Includes**:
289 289  
290 290  * LTS5 HMI Touch Screen
... ... @@ -293,11 +293,13 @@
293 293  
294 294  = 8. Support =
295 295  
632 +
296 296  * 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.
297 297  * 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]].
298 298  
299 299  = 9.  Reference material =
300 300  
638 +
301 301  * Datasheet
302 302  * Source Code
303 303  * Mechinical
Screenshot 2024-12-24 134818.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +15.0 KB
Content
Screenshot 2024-12-24 134937.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +3.6 KB
Content
Screenshot 2024-12-24 140459.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +12.0 KB
Content
Screenshot 2024-12-24 144005.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +28.0 KB
Content
image-20241121113445-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +250.0 KB
Content
image-20241121120222-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +44.8 KB
Content
image-20241121120830-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +42.6 KB
Content
image-20241121141120-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +41.7 KB
Content
image-20241121141315-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +29.4 KB
Content
image-20241121141329-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +29.4 KB
Content
image-20241121142925-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +14.8 KB
Content
image-20241121145915-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +61.0 KB
Content
image-20241121150911-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +73.0 KB
Content
image-20241121151934-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +32.9 KB
Content
image-20241121171629-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +16.9 KB
Content
image-20241121171901-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +17.2 KB
Content
image-20241121172714-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +26.4 KB
Content
image-20241121172908-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +27.1 KB
Content
image-20241121180030-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +27.7 KB
Content
image-20241121180517-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +26.5 KB
Content
image-20241121181957-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +59.3 KB
Content
image-20241121182239-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +71.3 KB
Content
image-20241122092239-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +270.9 KB
Content
image-20241122092655-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +251.6 KB
Content
image-20241122093445-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +128.9 KB
Content
image-20241122093601-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +120.0 KB
Content
image-20241122094200-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +289.2 KB
Content
image-20241122094320-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +182.4 KB
Content
image-20241122094600-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +136.0 KB
Content
image-20241122094719-26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +129.5 KB
Content
image-20241122102929-27.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +219.9 KB
Content
image-20241122104344-28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +257.1 KB
Content
image-20241122110815-29.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +246.1 KB
Content
image-20241122112838-30.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +263.9 KB
Content
image-20241122113158-31.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +133.7 KB
Content
image-20241122113252-32.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +152.3 KB
Content
image-20241122113259-33.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +152.3 KB
Content
image-20241122113359-34.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +126.5 KB
Content
image-20241122134113-35.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +69.3 KB
Content
image-20241122134412-36.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +14.9 KB
Content
image-20241122134420-37.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +14.9 KB
Content
image-20241122135023-38.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +28.7 KB
Content
image-20241122135258-39.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +40.3 KB
Content
image-20241122141526-40.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +78.8 KB
Content
image-20241122141536-41.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +78.8 KB
Content
image-20241122142129-42.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +85.1 KB
Content
image-20241122143105-43.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +60.2 KB
Content
image-20241122145620-44.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +394.0 KB
Content
image-20241122152026-45.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +201.6 KB
Content
image-20241122152542-46.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +95.3 KB
Content
image-20241122153958-47.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +241.1 KB
Content
image-20241122154745-48.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +135.7 KB
Content
image-20241122154755-49.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +135.7 KB
Content
image-20241122155650-50.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +104.4 KB
Content
image-20241122161934-51.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +230.3 KB
Content
image-20241122162612-52.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +58.7 KB
Content
image-20241122162852-53.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +125.5 KB
Content
image-20241122171211-54.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +173.3 KB
Content
image-20241122173706-55.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +37.6 KB
Content
image-20241122173718-56.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +37.6 KB
Content
image-20241226135550-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +293.3 KB
Content
squalreline-trial.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +60.4 KB
Content
squareline-studio-launcher-screen.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +203.4 KB
Content
squareline.io_downloads.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +1.5 MB
Content