Last modified by Dilisi S on 2025/02/26 19:24
<
From version < 132.1 >
edited by Dilisi S
on 2024/12/25 01:39
To version < 74.1 >
edited by BoYang Xie
on 2024/11/21 18:22
>
Change comment: Uploaded new attachment "image-20241121182239-18.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.pradeeka
1 +XWiki.xieby
Content
... ... @@ -21,20 +21,20 @@
21 21  
22 22  = 1.  Introduction =
23 23  
24 -== 1.1  What is the LTS5 LoRa HMI Touch Screen? ==
24 +== 1.1  What is LTS5 LoRa HMI touch screen ==
25 25  
26 26  
27 -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.
27 +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.
28 28  
29 -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.
29 +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.
30 30  
31 -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.
31 +The HMI touch screen of LTS5 supports drap & drop design. Developer can use SquareLine to easily customize the display UI for different application.
32 32  
33 -The LA66 LoRa module can be programmed to support either private LoRa protocols or the LoRaWAN protocol.
33 +LTS5 use LA66 LoRa module, this module can be program to support private LoRa protocol or LoRaWAN protocol.
34 34  
35 +
35 35  == 1.2  Features ==
36 36  
37 -
38 38  * ESP32-WROOM MCU: 8MB RAM & 16MB ROM
39 39  * Dragino LA66 LoRa Module
40 40  * Support Private LoRa protocol or LoRaWAN protocol
... ... @@ -47,9 +47,10 @@
47 47  * 5V DC power
48 48  * IP Rating: IP52
49 49  
50 -== 1.3  Specifications ==
51 51  
51 +== 1.3  Specification ==
52 52  
53 +
53 53  **LoRa**:
54 54  
55 55  * Frequency Range: 870 MHz ~~ 960 MHz
... ... @@ -86,6 +86,7 @@
86 86  
87 87  * External 5V DC power adapter
88 88  
90 +
89 89  == 1.5  Storage & Operation Temperature ==
90 90  
91 91  
... ... @@ -92,6 +92,7 @@
92 92  * Operation Temperature: -20 ~~ 70°C  (No Dew)
93 93  * Storage Temperature: -30 ~~ 70°C  (No Dew)
94 94  
97 +
95 95  == 1.6  Applications ==
96 96  
97 97  
... ... @@ -102,37 +102,29 @@
102 102  * Smart Cities
103 103  * Smart Factory
104 104  
105 -= 2.  Getting Started with 'Hello World' =
106 106  
109 += 2.  Getting Started with Hello World =
110 +
107 107  == 2.1  About this demo ==
108 108  
109 109  
110 -This getting started example demonstrates how to design and deploy a simple display UI for the LTS5 device. The example includes:
114 +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.
111 111  
112 -* Creating a basic UI with a single button.
113 -* Implementing functionality to navigate the Web UI to a new page when the button is clicked.
114 -* Uploading the UI to the LTS5 device.
115 115  
116 -By completing this demo, you will gain foundational knowledge for customizing the LTS5 interface and building more advanced IoT applications.
117 -
118 -
119 119  == 2.2  Install Software Running Environment ==
120 120  
119 +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.
121 121  
122 -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.
121 +=== 2.2.1 Install VSCode and ESP-IDF extension ===
123 123  
124 124  
125 -=== 2.2.1 Install VS Code and ESP-IDF extension ===
124 +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]].
126 126  
126 +Next, you need to install the ESP-IDF extension within VSCode. The detailed operation steps are illustrated in image 1.
127 127  
128 -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]].
129 -
130 -Next, install the **ESP-IDF** extension within **VS Code**. Detailed steps for this process are shown in Image 1.
131 -
132 -
133 133  [[image:image-20240928110211-5.png||height="508" width="866"]]
134 134  
135 - Image 1: ESP-IDF extension install
130 + image 1 ESP-IDF extension install
136 136  
137 137  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]]
138 138  
... ... @@ -140,164 +140,109 @@
140 140  === 2.2.2 Install SquareLine Studio ===
141 141  
142 142  
143 -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.
138 +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]].
144 144  
145 -[[image:squareline.io_downloads.png]]
140 +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.
146 146  
147 147  
148 -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:
143 +== 2.3 Simple usage of SquareLine Studio and export UI code ==
149 149  
150 -* Max. 10 screens
151 -* Max. 150 widgets
152 -* Max. 5 global colors
153 -* Max. 2 themes
154 -* Max. 1 component
155 155  
156 -== 2.3 Simple usage of SquareLine Studio and exporting UI code ==
146 +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.
157 157  
148 +[[image:image-20240928103357-2.png||height="680" width="708"]]
158 158  
159 -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**.
150 + image 2 create a SquareLine project
160 160  
161 -* In the **PROJECT SETTINGS**, select **LVGL version **as **8.3.11** and **Resolution** as **800** x **480**.
162 -* Select the **CREATE **button to create the new project with the selected settings.
152 +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.
163 163  
164 -[[image:squareline-studio-launcher-screen.png]]
165 -
166 -
167 -
168 -Next, you need to configure some additional settings for this project. To do so, select** File  -> Project Settings** as shown in the image below.
169 -
170 170  [[image:1727229582471-566.png]]
171 171  
156 + image 3 project settings
172 172  
173 -In the **PROJECT SETTINGS** dialog box, configure/modify the project settings as shown in the image below.
174 -
175 -* **UI Files Export Root**: Select a folder on your computer to store the UI files.
176 -* **LVGL Include Path**: Set this to **lvgl.h**
177 -* Click on the **APPLY CHANGES** button.
178 -
179 179  [[image:image-20240928105309-4.png||height="526" width="556"]]
180 180  
160 + image 4 modify project settings
181 181  
182 -Now you can start building the user interface. Follow the steps below:
162 +Now we can start to use this software. Here are some usage information for this software.
183 183  
164 +**~1. add widget**
184 184  
185 -=== **Add widgets** ===
166 +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.
186 186  
187 -
188 -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.
189 -
190 190  [[image:image-20240928111412-6.png||height="526" width="864"]]
191 191  
170 + image 5 add widgets
192 192  
193 -Then click the **Screen **widget to add the second screen. After adding the second screen, it will appear in the Screens panel as **Screen2**.
172 +**2. modify widget**
194 194  
195 -[[image:Screenshot 2024-12-24 140459.png||height="278" width="290"]]
174 +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".
196 196  
197 -=== **Modify widget properties** ===
198 -
199 -
200 -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.
201 -
202 202  [[image:1727485118799-984.png]]
203 203  
178 + image 6 the button widget's "Inspector" tab
204 204  
205 -==== **Changing the Button properties** ====
180 +Second part: "Layout" means a auto position-management for widgets contained in the parent widget. "Transform" includes size, position and align modification.
206 206  
207 -
208 -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:
209 -
210 -* **Flex Flow**: No Layout
211 -* **Transform**:
212 -** **X**: 331 px
213 -** **Y**: 203 px
214 -** **Width**: 100 px
215 -** **Height**: 50 px
216 -** **Align**: CENTER
217 -
218 218  [[image:1727485251053-655.png]]
219 219  
184 +image 7 the button widget's "BUTTON" tab
220 220  
221 -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.
186 +Third part: It is an area of style setting.
222 222  
223 -* Click **ADD EVENT** button. A new section will appear to configure this event.
188 +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.
224 224  
225 -[[image:Screenshot 2024-12-24 134937.png||height="80" width="290"]]
226 -
227 -* 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.
228 -
229 -[[image:Screenshot 2024-12-24 134818.png||height="222" width="290"]]
230 -
231 -* 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.
232 -* Finally, click the **ADD** button.
233 -
234 234  [[image:1727485480434-713.png||height="395" width="290"]]
235 235  
236 - Image 8: Add an event for the button
192 + image 8 add event for button
237 237  
194 +**3. change label widget content**
238 238  
239 -==== **Changing the label properties** ====
196 +Modify the content in text as shown in image 9, the text content of label widget will be changed accordingly.
240 240  
241 -
242 -Click the Label you have added to the screen. Under the **Label** section, type "**Click for Detail**" in the **Text** textbox.
243 -
244 244  [[image:image-20240928090825-1.png||height="327" width="391"]]
245 245  
200 + image 9 modify text content of label widget
246 246  
247 -Once you enter the text, it will immediately appear on the label.
202 +**4. Add image into project**
248 248  
204 +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.
249 249  
250 -==== **Changing image properties** ====
251 -
252 -
253 -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.
254 -
255 -One way is to move your image into the folder "…/squareline project/assets/", as shown in the image below.
256 -
257 257  [[image:image-20240928113424-9.png||height="355" width="505"]]
258 258  
208 + image 10 add image file into SquareLine Studio project
259 259  
260 -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.
261 -
262 262  [[image:image-20240928114139-10.png||height="559" width="810"]]
263 263  
212 + image 11 use image widget in SquareLine Studio
264 264  
265 -==== **The relationship between widgets** ====
214 +**5. The relationship between widgets**
266 266  
216 +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.
267 267  
268 -Widgets commonly have two types of relationships: **parallel** and **parent-child**.
269 -
270 -* In a **parallel relationship**, widgets' positions are determined relative to a shared reference object.
271 -* 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.
272 -
273 273  [[image:1727486567182-334.png||height="318" width="278"]]
274 274  
220 +image 12 move label1 to make label1 widget be a child of button1 widget(1)
275 275  
276 -Move the label, **Label1** to make it a child of **Button1** as shown in the image below.
277 -
278 278  [[image:image-20240928112001-8.png||height="431" width="796"]]
279 279  
224 + image 13 move label1 to make label1 widget be a child of button1 widget(2)
280 280  
281 -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.
226 +**6. Preview the final effect**
282 282  
283 -[[image:Screenshot 2024-12-24 144005.png||height="360" width="290"]]
228 +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.
284 284  
285 -
286 -==== **Preview the screen** ====
287 -
288 -
289 -You can test the result by clicking on the **PLAY** button as shown in the image below. The screen will change into play mode.
290 -
291 291  [[image:1727487368023-281.png]]
292 292  
232 + image 14 click on the triangle icon to start or end the simulation
293 293  
294 -For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
234 +For more detailed usage, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
295 295  
296 296  
297 297  == 2.4 Integrate UI Code to ESP-IDF Project ==
298 298  
299 299  
300 -To integrate, first export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
240 +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.
301 301  
302 302  [[image:1727229798126-306.png]]
303 303  
... ... @@ -317,7 +317,6 @@
317 317  
318 318   image 18 modify CMakeLists.txt
319 319  
320 -
321 321  The last step of integrating is adding two lines of code in main.c file.
322 322  
323 323  [[image:1727229926561-300.png]]
... ... @@ -356,257 +356,7 @@
356 356  
357 357  = 4. Example Project 2: LoRaWAN RS485 Alarm =
358 358  
359 -= 5. The way to add a new panel to project =
360 360  
361 -
362 -**~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.**
363 -
364 -[[image:image-20241121113445-1.png||height="584" width="934"]]
365 -
366 - image 5.1 a panel about water_leak
367 -
368 -
369 -**2. Export the ui file.** You need  to adjust the export path first, then click "Export->Export UI Files". This step had been introduced before. Then you can get the ui files as shown in image 5.2.
370 -
371 -[[image:image-20241121141120-4.png||height="383" width="795"]]
372 -
373 - image 5.2 ui files exported
374 -
375 -
376 -**3. Delete or rename some file.** Here are the steps:
377 -
378 - Step1 Delete the 'components' directory.
379 - Step2 Delete 'filelist.txt'.
380 - Step3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
381 - Step4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
382 - Step5 Rename the 'screens' directory to 'styles'.
383 -
384 -[[image:image-20241121151934-10.png||height="303" width="792"]]
385 -
386 - image 5.3 rest file (1)
387 -
388 -[[image:image-20241121142925-7.png||height="141" width="793"]]
389 -
390 - image 5.4 rest file (2)
391 -
392 -**4. Open this project in vscode.**
393 -
394 -5. Add file include path about water_leak in extra_lib/CMakeLists.txt as shown in image 5.5, 5.6, and its format is similar to the tem_hum or door.
395 -
396 -[[image:image-20241121181957-17.png||height="438" width="516"]]
397 -
398 - image 5.5 extra_lib/CMakeLists.txt before add
399 -
400 -[[image:image-20241121182239-18.png||height="520" width="518"]]
401 -
402 - image 5.6 extra_lib/CMakeLists.txt after add
403 -
404 -**6. Modify header file include in fonts and images directory.** Open the fonts/ui_font_Font12.c file, as shown in image 5.7, then modify the '#include "../ui.h"' to '#include "../ui_water_leak.h"', the image 5.8 is the modified image. Other font file need to be modified in same way.
405 -
406 -[[image:image-20241121171629-11.png]]
407 -
408 - image 5.7 before-modified font file
409 -
410 -[[image:image-20241121171901-12.png]]
411 -
412 - image 5.8 modified font file
413 -
414 -Open the images/ui_img_battery_empty_png.c file, as shown in image 5.9, then modify the '#include "../ui.h"' to '#include "../ui_water_leak.h"', the image 5.10 is the modified image. Other image file need to be modified in same way.
415 -
416 -[[image:image-20241121172714-13.png]]
417 -
418 - image 5.9 before-modified image file
419 -
420 -[[image:image-20241121172908-14.png]]
421 -
422 - image 5.10 modified image file
423 -
424 -**7. Modify the ui_water_leak/CMakeLists.txt.** Open this file, and modify it from image 5.11 to image 5.12.
425 -
426 -[[image:image-20241121180030-15.png]]
427 -
428 - image 5.11 ui_water_leak/CMakeLists.txt before modification
429 -
430 -[[image:image-20241121180517-16.png]]
431 -
432 - image 5.12 ui_water_leak/CMakeLists.txt after modification
433 -
434 -**8. Modify ui_water_leak.h file.** The image 5.13, 5.14 show the code before modification, and the image 5.15, 5.16 show the code after modification.
435 -
436 -[[image:image-20241122094200-23.png]]
437 -
438 - image 5.13 ui_water_leak.h (1) before modification
439 -
440 -[[image:image-20241122094320-24.png||height="852" width="554"]]
441 -
442 - image 5.14 ui_water_leak.h (2) before modification
443 -
444 -[[image:image-20241122094600-25.png||height="1078" width="554"]]
445 -
446 - image 5.15 ui_water_leak.h (1) after modification
447 -
448 -[[image:image-20241122094719-26.png||height="941" width="583"]]
449 -
450 - image 5.16 ui_water_leak.h (2) before modification
451 -
452 -**9. Modify ui_water_leak.c file.** The image 5.17, 5.18, 5.19 show the code before modification, and the image 5.20, 5.21, 5.22 show the code after modification.
453 -
454 -_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.
455 -
456 -[[image:image-20241122102929-27.png||height="619" width="426"]]
457 -
458 - image 5.17 ui_water_leak.c (1) before modification
459 -
460 -[[image:image-20241122112838-30.png||height="551" width="628"]]
461 -
462 - image 5.18 ui_water_leak.c (2) before modification
463 -
464 -[[image:image-20241122110815-29.png||height="725" width="712"]]
465 -
466 - image 5.19 ui_water_leak.c (3) before modification
467 -
468 -[[image:image-20241122113158-31.png||height="872" width="677"]]
469 -
470 - image 5.20 ui_water_leak.c (1) after modification
471 -
472 -[[image:image-20241122113259-33.png||height="874" width="724"]]
473 -
474 - image 5.21 ui_water_leak.c (2) after modification
475 -
476 -[[image:image-20241122113359-34.png||height="804" width="746"]]
477 -
478 - image 5.22 ui_water_leak.c (3) after modification
479 -
480 -**10. Modify ui_water_leak_events.h file.** The image 5.23 show the code before modification, and the image 5.24 show the code after modification.
481 -
482 -[[image:image-20241122134113-35.png||height="380" width="421"]]
483 -
484 - image 5.23 ui_water_leak_events_.h before modification
485 -
486 -[[image:image-20241122134420-37.png||height="201" width="283"]]
487 -
488 -image 5.24 ui_water_leak_events_.h after modification
489 -
490 -**11. Modify ui_water_leak_events.c file.** The image 5.25 show the code before modification, and the image 5.26 show the code after modification.
491 -
492 -Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
493 -
494 -Step2. add code  below in delete_object() function definition.
495 -
496 - panel_all * panel = find_upper_by_SensorPanel(&arr,((lv_obj_t *)(e->user_data~)~)~);
497 -
498 - size_t index = panel->panel_obj_index;
499 -
500 - deleteElement(&arr, index);
501 -
502 -[[image:image-20241122135023-38.png||height="358" width="372"]]
503 -
504 - image 5.25 ui_water_leak_events_.c before modification
505 -
506 -[[image:image-20241122135258-39.png||height="403" width="559"]]
507 -
508 - image 5.26 ui_water_leak_events_.c after modification
509 -
510 -
511 -**12. Modify ui_water_leak_style.c file.**
512 -
513 -Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
514 -
515 - add '#include "../../sort.h"'
516 -
517 - add '#include "ui.h"'
518 -
519 -[[image:image-20241122141536-41.png||height="361" width="612"]]
520 -
521 - image 5.27 ui_water_leak_style.c (1) before modification
522 -
523 -[[image:image-20241122142129-42.png||height="386" width="613"]]
524 -
525 - image 5.28 ui_water_leak_style.c (1) after modification
526 -
527 -
528 -Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
529 -
530 - delete code as shown in image 5.29
531 -
532 -[[image:image-20241122145620-44.png||height="757" width="671"]]
533 -
534 - image 5.29 ui_water_leak_style.c (2)
535 -
536 -
537 -Step3. The image 5.30, 5.31 show the change.
538 -
539 -[[image:image-20241122152026-45.png||height="277" width="828"]]
540 -
541 - image 5.30 ui_water_leak_style.c (3) before modification
542 -
543 -[[image:image-20241122152542-46.png||height="293" width="830"]]
544 -
545 - image 5.31 ui_water_leak_style.c (3) after modification
546 -
547 -
548 -Step4. Copy partly the code in ui_water_leak.c, paste at extra_lib/sort.h(The process is shown in image 5.32, 5.33).
549 -
550 -[[image:image-20241122153958-47.png]]
551 -
552 - image 5.32 ui_water_leak_style.c (4)
553 -
554 -[[image:image-20241122154755-49.png||height="864" width="513"]]
555 -
556 - image 5.33 ui_water_leak_style.c (4)
557 -
558 -
559 -Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
560 -
561 -[[image:image-20241122155650-50.png||height="922" width="513"]]
562 -
563 - image 5.34 ui_water_leak_style.c (5)
564 -
565 -
566 -Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
567 -
568 -[[image:image-20241122161934-51.png]]
569 -
570 - image 5.35
571 -
572 -
573 -Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
574 -
575 -[[image:image-20241122162852-53.png||height="330" width="529"]]
576 -
577 - image 5.37
578 -
579 -
580 -Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
581 -
582 -panel_with_type union_sensor;
583 -
584 -union_sensor.panel_type = WATER_LEAK_TYPE;
585 -
586 -......
587 -
588 -lv_obj_set_x(union_sensor.panel_union.door.ui_PanelSensorDoor, x_by_index(index));
589 -
590 -lv_obj_set_y(union_sensor.panel_union.door.ui_PanelSensorDoor, y_by_index(index));
591 -
592 -return union_sensor;
593 -
594 -[[image:image-20241122171211-54.png||height="635" width="792"]]
595 -
596 - image 5.38
597 -
598 -
599 -**13. Modify sort.c file.**
600 -
601 -Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
602 -
603 -[[image:image-20241122173718-56.png||height="378" width="579"]]
604 -
605 - image 5.39 sort.c (1)
606 -
607 -There are still some changes need to be done in sort.c, and omit here for the moment.
608 -
609 -
610 610  = 6. FAQ =
611 611  
612 612  == 6.1 ==
... ... @@ -629,6 +629,7 @@
629 629  * 5V,2A DC Power Adapter.
630 630  * USB Type C Program Cable
631 631  
321 +
632 632  = 8. Support =
633 633  
634 634  
... ... @@ -635,6 +635,7 @@
635 635  * 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.
636 636  * 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]].
637 637  
328 +
638 638  = 9.  Reference material =
639 639  
640 640  
... ... @@ -642,6 +642,7 @@
642 642  * Source Code
643 643  * Mechinical
644 644  
336 +
645 645  = 10. FCC Warning =
646 646  
647 647  
Screenshot 2024-12-24 134818.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -15.0 KB
Content
Screenshot 2024-12-24 134937.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -3.6 KB
Content
Screenshot 2024-12-24 140459.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -12.0 KB
Content
Screenshot 2024-12-24 144005.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -28.0 KB
Content
image-20241122092239-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -270.9 KB
Content
image-20241122092655-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -251.6 KB
Content
image-20241122093445-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -128.9 KB
Content
image-20241122093601-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -120.0 KB
Content
image-20241122094200-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -289.2 KB
Content
image-20241122094320-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -182.4 KB
Content
image-20241122094600-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -136.0 KB
Content
image-20241122094719-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -129.5 KB
Content
image-20241122102929-27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -219.9 KB
Content
image-20241122104344-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -257.1 KB
Content
image-20241122110815-29.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -246.1 KB
Content
image-20241122112838-30.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -263.9 KB
Content
image-20241122113158-31.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -133.7 KB
Content
image-20241122113252-32.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -152.3 KB
Content
image-20241122113259-33.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -152.3 KB
Content
image-20241122113359-34.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -126.5 KB
Content
image-20241122134113-35.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -69.3 KB
Content
image-20241122134412-36.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
image-20241122134420-37.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
image-20241122135023-38.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -28.7 KB
Content
image-20241122135258-39.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -40.3 KB
Content
image-20241122141526-40.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
image-20241122141536-41.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
image-20241122142129-42.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -85.1 KB
Content
image-20241122143105-43.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -60.2 KB
Content
image-20241122145620-44.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -394.0 KB
Content
image-20241122152026-45.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -201.6 KB
Content
image-20241122152542-46.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -95.3 KB
Content
image-20241122153958-47.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -241.1 KB
Content
image-20241122154745-48.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -135.7 KB
Content
image-20241122154755-49.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -135.7 KB
Content
image-20241122155650-50.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -104.4 KB
Content
image-20241122161934-51.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -230.3 KB
Content
image-20241122162612-52.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -58.7 KB
Content
image-20241122162852-53.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -125.5 KB
Content
image-20241122171211-54.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -173.3 KB
Content
image-20241122173706-55.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -37.6 KB
Content
image-20241122173718-56.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -37.6 KB
Content
squalreline-trial.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -60.4 KB
Content
squareline-studio-launcher-screen.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -203.4 KB
Content
squareline.io_downloads.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -1.5 MB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0