Skip to Content
Last modified by BoYang Xie on 2025/07/15 16:41
From version 185.1
edited by BoYang Xie
on 2025/05/05 12:13
Change comment: Uploaded new attachment "image-20250505121328-2.png", version {1}
To version 119.1
edited by Dilisi S
on 2024/12/22 15:26
Change comment: Uploaded new attachment "squalreline-trial.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.xieby
1 +XWiki.pradeeka
Content
... ... @@ -1,11 +3,12 @@
1 -
2 -
3 3  (% style="text-align:center" %)
4 -[[image:image-20241226135550-1.png]]
2 +[[image:image-20240915231842-1.png]]
5 5  
6 6  
7 7  
8 8  
7 +
8 +
9 +
9 9  (% _mstvisible="1" %)
10 10  (% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:**
11 11  
... ... @@ -101,7 +101,7 @@
101 101  * Smart Cities
102 102  * Smart Factory
103 103  
104 -= 2.  Getting Started with 'Hello World' =
105 += 2.  Getting Started with Hello World =
105 105  
106 106  == 2.1  About this demo ==
107 107  
... ... @@ -112,6 +112,7 @@
112 112  * Implementing functionality to navigate the Web UI to a new page when the button is clicked.
113 113  * Uploading the UI to the LTS5 device.
114 114  
116 +
115 115  By completing this demo, you will gain foundational knowledge for customizing the LTS5 interface and building more advanced IoT applications.
116 116  
117 117  
... ... @@ -118,20 +118,19 @@
118 118  == 2.2  Install Software Running Environment ==
119 119  
120 120  
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.
123 +The **ESP MCU** supports development using **ESP-IDF**, **Arduino**, or **MicroPython**. For this project, we use **ESP-IDF** for compilation and **Visual Studio Code (VS Code)** as the development environment.
122 122  
123 123  
124 -=== 2.2.1 Install VS Code and ESP-IDF extension ===
126 +=== 2.2.1 Install VSCode and ESP-IDF extension ===
125 125  
126 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]].
129 +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]].
128 128  
129 -Next, install the **ESP-IDF** extension within **VS Code**. Detailed steps for this process are shown in Image 1.
131 +Next, you need to install the ESP-IDF extension within VSCode. The detailed operation steps are illustrated in image 1.
130 130  
131 -
132 132  [[image:image-20240928110211-5.png||height="508" width="866"]]
133 133  
134 - Image 1: ESP-IDF extension install
135 + image 1 ESP-IDF extension install
135 135  
136 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 137  
... ... @@ -139,220 +139,159 @@
139 139  === 2.2.2 Install SquareLine Studio ===
140 140  
141 141  
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.
143 +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]].
143 143  
144 -[[image:squareline.io_downloads.png||height="888" width="1294"]]
145 +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.
145 145  
146 146  
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:
148 +== 2.3 Simple usage of SquareLine Studio and export UI code ==
148 148  
149 -* Max. 10 screens
150 -* Max. 150 widgets
151 -* Max. 5 global colors
152 -* Max. 2 themes
153 -* Max. 1 component
154 154  
155 -== 2.3 Simple usage of SquareLine Studio and exporting UI code ==
151 +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.
156 156  
153 +[[image:image-20240928103357-2.png||height="680" width="708"]]
157 157  
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**.
155 + image 2 create a SquareLine project
159 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.
157 +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.
162 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 -
168 168  [[image:1727229582471-566.png]]
169 169  
161 + image 3 project settings
170 170  
171 -In the **PROJECT SETTINGS** dialog box, configure/modify the project settings as shown in the image below.
172 -
173 -* **UI Files Export Path**: 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 -
177 177  [[image:image-20240928105309-4.png||height="526" width="556"]]
178 178  
165 + image 4 modify project settings
179 179  
180 -Now you can start building the user interface. Follow the steps below:
167 +Now we can start to use this software. Here are some usage information for this software.
181 181  
169 +**~1. add widget**
182 182  
183 -=== **Add widgets** ===
171 +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.
184 184  
185 -
186 -After creating a project, a **Screen** will be automatically added. Its name is **Screen1** by default.
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  
175 + 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**.
177 +**2. modify widget**
194 194  
195 -[[image:Screenshot 2024-12-24 140459.png||height="278" width="290"]]
179 +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  
183 + image 6 the button widget's "Inspector" tab
204 204  
205 -==== **Changing the Button properties** ====
185 +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  
189 +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.
191 +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.
193 +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
197 + image 8 add event for button
237 237  
199 +**3. change label widget content**
238 238  
239 -==== **Changing the label properties** ====
201 +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  
205 + image 9 modify text content of label widget
246 246  
247 -Once you enter the text, it will immediately appear on the label.
207 +**4. Add image into project**
248 248  
209 +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  
213 + 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  
217 + image 11 use image widget in SquareLine Studio
264 264  
265 -==== **The relationship between widgets** ====
219 +**5. The relationship between widgets**
266 266  
221 +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  
225 +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  
229 + 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.
231 +**6. Preview the final effect**
282 282  
283 -[[image:Screenshot 2024-12-24 144005.png||height="360" width="290"]]
233 +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  
237 + 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/]].
239 +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 -== 2.4 Integrate UI Code into an ESP-IDF Project ==
242 +== 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.
245 +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 -On the  menubar, click **Export -> Export UI** Files as shown in the image below.
303 -
304 304  [[image:1727229798126-306.png]]
305 305  
249 + image 15 export UI file
306 306  
307 -The exported UI files can be found in your SquareLine project folder as shown in the image below.
308 -
309 -
310 310  [[image:1727229821582-258.png||height="333" width="662"]]
311 311  
253 + image 16 exported UI file
312 312  
313 -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.
255 +Create a empty directory entitled "ui" in path "basic_prj/app_components/ui/", and then copy all UI code exported to this directory.
314 314  
315 315  [[image:image-20240928144830-11.png]]
316 316  
259 + image 17 open CMakeLists.txt
317 317  
318 -Open the **CMakeLists.txt** file and edit it as ahown below.
319 -
320 320  [[image:1727229892636-154.png||height="521" width="407"]]
321 321  
263 + image 18 modify CMakeLists.txt
322 322  
323 -Open the main.c file and  add two lines of code as shown in the below images.
265 +The last step of integrating is adding two lines of code in main.c file.
324 324  
325 -Add **#include "ui.h"**
326 -
327 327  [[image:1727229926561-300.png]]
328 328  
269 + image 19 add "ui.h"
329 329  
330 -Add **ui_init();**
331 -
332 332  [[image:1727229955611-607.png]]
333 333  
273 + image 20 add "ui_init()"
334 334  
335 -== 2.5 Brief introduction to the Hello World project ==
336 336  
276 +== 2.5 Brief introduction of hello world project ==
337 337  
338 -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.
339 339  
279 +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.
340 340  
281 +
341 341  == 2.6 Test Result ==
342 342  
343 343  
344 -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.
285 +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.
345 345  
346 -Screen 1:
347 -
348 348  [[image:1727488067077-684.png||height="402" width="574"]]
349 349  
289 + image 21 screen1
350 350  
351 -Screen 2:
352 -
353 353  [[image:1727488157579-949.png||height="397" width="572"]]
354 354  
293 + image 22 screen2
355 355  
295 +
356 356  = 3. Example Project 1: LoRa Central Display =
357 357  
358 358  [[image:image-20240916101737-1.png||height="468" width="683"]]
... ... @@ -360,347 +360,135 @@
360 360  
361 361  = 4. Example Project 2: LoRaWAN RS485 Alarm =
362 362  
363 -= 5. Example Project 3: P2P =
303 += 5.  The way to add a new panel to project =
364 364  
365 -The project achieves the function of receiving LoRa P2P messages and displaying them on the screen. The workflow is as follows: A LA66, running a P2P program, sends a message in a particular format via an AT command. Then, the LTS5 receives the message and displays it on the screen.
305 +**~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.**
366 366  
367 -The project can be found at [[this link>>url:https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/P2P]].
368 -
369 -== 5.1 Firmware Flashing ==
370 -
371 -
372 -The following software tools are required to flash firmware to the ESP32 and LA66.
373 -
374 -* Download the ESP32 firmware flash tool from [[this link>>https://docs.espressif.com/projects/esp-test-tools/en/latest/esp32/production_stage/tools/flash_download_tool.html]].
375 -* Download the LA66 firmware flash tool from [[this link>>https://www.dropbox.com/scl/fo/9kqeqf6wmet10o9hgxuwa/h?rlkey=4ikrg6kg5v0yjxwhp0i37wrv7&e=1&dl=0]].
376 -
377 -=== 5.1.1 Upload the Firmware to the ESP32 ===
378 -
379 -Open //**flash_download_tool.exe**// and follow the steps below.
380 -
381 -* **Chip Type**: ESP32-S3
382 -* **WorkMode**: Develop
383 -* **LoadMode**: UART
384 -* Click on the **OK** button.
385 -
386 -[[image:1738893226894-758.png||height="170" width="176"]]
387 -
388 -
389 -In the **SPIDownload** tab,
390 -
391 -* Select the checkboxes for //bootloader.bin, partition-table.bin, ota_data_initial.bin//, and //project.bin//.
392 -* SPI Flashing Config:
393 -** **SPI SPEED**: 40MHz
394 -** **SPI MODE**: DIO
395 -** Check **DoNotChgBin** option.
396 -* **COM**: Select the correct COM port.
397 -* **BAUD**: 1152000
398 -* Click on the **START** button.
399 -
400 -[[image:image-20250207100150-7.png||height="476" width="538"]]
401 -
402 -
403 -The progress bar will indicate the firmware update progress and display a **FINISH** message once the update is complete.
404 -
405 -
406 -=== 5.1.2 Upload the Firmware to the LA66 ===
407 -
408 -Open **Dragino_Sensor_Manager_Utility.exe**, and then follow the steps below.
409 -
410 -* Click on the UART Update Firmware tab.
411 -* Select the correct COM port.
412 -* Click on the Upload_File button and select the DRAGINO-LRWAN-AT.bin file.
413 -* Click on the Start button.
414 -
415 -[[image:image-20250207101415-8.png||height="522" width="618"]]
416 -
417 -
418 -[[image:image-20250207101515-9.png||height="522" width="618"]]
419 -
420 -
421 -(% class="wikigeneratedid" %)
422 -The progress bar will indicate the firmware update progress.
423 -
424 -
425 -== 5.2 AT commands and LTS5 Panel Data Formats ==
426 -
427 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**01**A4CBBB0A8E085C02,0,3
428 -
429 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**02**A4CB00,0,3
430 -
431 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**03**A4CB00,0,3
432 -
433 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**04**A4CB00,0,3
434 -
435 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**05**A4CB00,0,3
436 -
437 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**06**A4CB00,0,3
438 -
439 -**LTS5 panel data format**:
440 -
441 -~1. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF  A84041000181D4A8  01  A4CB  BB0A  8E08  5C02**,0,3
442 -
443 -**01:** encrypt. 1 Byte. 01 ~-~-> no encryption. This 1-byte information is now invalid; simply write 0x01 instead.
444 -
445 -**4b69746368656e2d467269676531FFFF: **Device Name. 16 Bytes. The Device Name for this piece of information is "Kitchen-Frige1," and the subsequent "FFFF" is intended to pad it up to 16 Bytes. The Device Name for this piece of information is 'Kitchen-Frige1,' and the subsequent 'FFFF' is intended to pad it up to 16 Bytes, but it is not necessary as the system can handle shorter names as well.
446 -
447 -**A84041000181D4A8:** Device EUI. 8 Bytes. The last three Bytes will be extracted by the ESP32-S3 and displayed on the screen.
448 -
449 -**01: **Panel Type. 1 Byte. 0x01~-~->Tem & Hum,
450 -
451 - 0x02~-~->Door,
452 -
453 - 0x03~-~->Water Leak,
454 -
455 - 0x04~-~->Occupied,
456 -
457 - 0x05~-~->Button,
458 -
459 - 0x06~-~->Alarm,
460 -
461 -**A4CB: **Battery level//. //2 Bytes. Battery Voltage =0xCBA4&0x3FFF=0x0BA4=2980mV
462 -
463 -**BB0A: **The temperature of the built-in sensor in LHT65N.// //2 Bytes. Temperature:  0x0ABB/100=27.47℃
464 -
465 -**8E08: **The temperature of the External temperature sensor.// //2 Bytes. Temperature:  0x088E/100=21.90℃
466 -
467 -**5C02：**The humidity of the built-in sensor in LHT65N. 2 Bytes. Humidity: 0x025C/10=60.4%
468 -
469 -2. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF**  **A84041000181D4A8**  **02  A4CB  00**,0,3
470 -
471 -Specific sections of the data share the same function.
472 -
473 -**00: Status. **1 Byte//. //If Panel Type is 0x02, **Status: 00~-~->Open; 01~-~->Close.**
474 -
475 - If Panel Type is 0x03, **Status: 00~-~->Normal; 01~-~->Water Leaking.**
476 -
477 - If Panel Type is 0x04, **Status: 00~-~->Free; 01~-~->Occupied.**
478 -
479 - If Panel Type is 0x05, **Status: 00~-~->OFF; 01~-~->ON.**
480 -
481 - If Panel Type is 0x06, **Status: 00~-~->OFF; 01~-~->Alarm.**
482 -
483 -== 5.3 Usage ==
484 -
485 -After burning the firmware into LTS5, you can use an LA66 equipped with peer-to-peer firmware to send data to LTS5 via AT commands.
486 -
487 -5.3.1 Connect LA66 to the computer, open Serial Port Utility, and send the AT+CFG instruction to check whether the LA66 has downloaded correct program.
488 -
489 -[[image:image-20250207143131-11.png||height="527" width="547"]]
490 -
491 -5.3.2 Copy an AT instruction example, click "Send" button, then the led in LA66 will flash and the LTS5 will display the LoRa information.
492 -
493 -[[image:image-20250207144605-12.png||height="634" width="548"]]
494 -
495 -LTS5 receives this message and displays it on its screen as the image below shows.
496 -
497 -[[image:image-20250208181700-8.jpeg||height="528" width="704"]]
498 -
499 -= 6. Example Project 4: LoRaWAN_CLASS_C =
500 -
501 -
502 -The project achieves the function of receiving LoRaWAN Class C messages and displaying them on the screen. Note: The Things Network (TTN) needs to enable Class C support, and the LA66 within the LTS5 needs to operate in Class C mode.
503 -
504 -The downlink workflow proceeds as follows: The Things Network (TTN) sends a message in a specific format via downlink. Then, a LoRaWAN gateway relays this message to the LTS5. Finally, the LTS5 receives the message and displays it on its screen.
505 -
506 -The uplink workflow is as follows: The LA66 within the LTS5 sends a LoRaWAN message, for some reason, to a LoRaWAN gateway, which then forwards it to The Things Network (TTN).
507 -
508 -The project can be found at [[this link>>https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/LoRaWAN_CLASS_C]].
509 -
510 -== 6.1 firmware flashing approach ==
511 -
512 -The firmware flashing approach is the same as described in section 5.1.
513 -
514 -== 6.2 flowchart ==
515 -
516 -[[image:image-20250207164320-13.png||height="696" width="1344"]]
517 -
518 -== 6.3 Usage ==
519 -
520 -This section now describes a process involving TTN downlink panel data that is to be displayed on the LTS5 screen.
521 -
522 -6.3.1 Connect LA66 to the computer, open Serial Port Utility, and send the AT+CFG instruction to check whether the LA66 has downloaded correct program.
523 -
524 -[[image:image-20250207165702-14.png||height="830" width="563"]]
525 -
526 -6.3.2 Switch to Class C using "AT+CLASS=C", and check the class with "AT+CLASS=?".
527 -
528 -[[image:image-20250207173212-27.png]]
529 -
530 -[[image:image-20250207172246-20.png]]
531 -
532 -6.3.3 Verify LA66's join status (in LTS5) with "AT+NJS=?". If not joined, connect manually to LoRaWAN with "AT+JOIN".
533 -
534 -[[image:image-20250207172010-19.png]]
535 -
536 -[[image:image-20250207171650-17.png]]
537 -
538 -6.3.4 After joining, send a message to TTN, such as "AT+SENDB=01,02,8,05820802581ea0a5", to activate communication.
539 -
540 -[[image:image-20250207192107-28.png]]
541 -
542 -6.3.5 TTN distributes panel data in three phases: DEUI, Dev Name, and Sensor Data. The Dev Name, the last three bytes of the DEUI, and the panel type union together ensure the identification of a panel. Data about the same panel type will update the existing panel display, while data about a different panel type will create a new panel display on the LTS5 screen.
543 -
544 -There is an example for TTN downlink.
545 -
546 -1. downlink DEUI F1A84041000181D4A8
547 -1. downlink Dev Name F24B69746368656E2D467269676531FFFF
548 -1. downlink Sensor Data 5501A4CBBB0A8E085C02 or 5504A4CB01. Both of them are vaild formats for LTS5. Note: 0x55 as prefix and any other prefix except 0xF1, 0xF2, 0xF3 means downlink is Sensor Data.
549 -
550 -[[image:image-20250208175819-1.png||height="503" width="502"]]
551 -
552 -
553 -[[image:image-20250208175918-2.png||height="505" width="502"]]
554 -
555 -
556 -[[image:image-20250208180010-3.png||height="507" width="503"]]
557 -
558 -
559 -[[image:image-20250208181019-4.jpeg||height="592" width="790"]]
560 -
561 -
562 -[[image:image-20250208181328-7.png||height="505" width="504"]]
563 -
564 -
565 -[[image:image-20250208181139-5.jpeg||height="594" width="792"]]
566 -
567 -
568 -= 7. The method for adding a new type of panel to the project =
569 -
570 -If you don't have this need, then this part of the content can be ignored.
571 -
572 -1. Design a panel in SquareLine Studio, as shown in Image 7.1 below for reference.
573 -
574 574  [[image:image-20241121113445-1.png||height="584" width="934"]]
575 575  
576 - Image 7.1: a panel about water_leak
309 + image 5.1 a panel about water_leak
577 577  
311 +**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.
578 578  
579 -2. **Export the UI file: **You need to adjust the export path first, then click '**Export -> Export UI Files**' on the menu bar. This step was introduced earlier. After that, you can get the UI files as shown in Image 7.2.
580 -
581 581  [[image:image-20241121141120-4.png||height="383" width="795"]]
582 582  
583 - Image 7.2: Exported UI files
315 + image 5.2 ui files exported
584 584  
317 +**3. Delete or rename some file.** Here are the steps:
585 585  
586 -3. **Delete and rename some file.** Here are the steps:
319 + Step1 Delete the 'components' directory.
320 + Step2 Delete 'filelist.txt'.
321 + Step3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
322 + Step4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
323 + Step5 Rename the 'screens' directory to 'styles'.
587 587  
588 - Step 1: Delete the 'components' directory.
589 - Step 2: Delete 'filelist.txt'.
590 - Step 3: Delete 'ui_helpers.c' and 'ui_helpers.h'.
591 - Step 4: Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
592 - Step 5: Rename the 'screens' directory to 'styles'.
593 -
594 594  [[image:image-20241121151934-10.png||height="303" width="792"]]
595 595  
596 - image 7.3 rest file (1)
327 + image 5.3 rest file (1)
597 597  
598 598  [[image:image-20241121142925-7.png||height="141" width="793"]]
599 599  
600 - image 7.4 rest file (2)
331 + image 5.4 rest file (2)
601 601  
602 -4. Open the project in VS Code.
333 +**4. Open this project in vscode.**
603 603  
604 -5. Add the file include path for **water_leak** in **extra_lib/CMakeLists.txt**, as shown in Images 7.5 and 7.6. Its format is similar to that of **tem_hum** or **door**."
335 +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.
605 605  
606 606  [[image:image-20241121181957-17.png||height="438" width="516"]]
607 607  
608 - image 7.5 extra_lib/CMakeLists.txt before adding
339 + image 5.5 extra_lib/CMakeLists.txt before add
609 609  
610 610  [[image:image-20241121182239-18.png||height="520" width="518"]]
611 611  
612 - image 7.6 extra_lib/CMakeLists.txt after adding
343 + image 5.6 extra_lib/CMakeLists.txt after add
613 613  
614 -6.  **Modify the header files included in the fonts and images directories**.
345 +**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.
615 615  
616 -Open the **fonts/ui_font_Font12.c** file, as shown in Image 7.7, and change **#include "../ui.h"** to **#include "../ui_water_leak.h"**. The modified file is shown in Image 7.8. Other font files need to be modified in the same way.
617 -
618 618  [[image:image-20241121171629-11.png]]
619 619  
620 - image 7.7 unmodified font file
349 + image 5.7 before-modified font file
621 621  
622 622  [[image:image-20241121171901-12.png]]
623 623  
624 - image 7.8 modified font file
353 + image 5.8 modified font file
625 625  
626 -Open the **images/ui_img_battery_empty_png.c** file, as shown in Image 7.9, and change **#include "../ui.h"** to **#include "../ui_water_leak.h"**. The modified file is shown in Image 7.10. Other image files need to be modified in the same way.
355 +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.
627 627  
628 628  [[image:image-20241121172714-13.png]]
629 629  
630 - image 7.9 unmodified image file
359 + image 5.9 before-modified image file
631 631  
632 632  [[image:image-20241121172908-14.png]]
633 633  
634 - image 7.10 modified image file
363 + image 5.10 modified image file
635 635  
636 -7. Modify the **ui_water_leak/CMakeLists.txt**. Open this file, and modify it as shown in image 7.11 (before) and image 7.12 (after).
365 +**7. Modify the ui_water_leak/CMakeLists.txt.** Open this file, and modify it from image 5.11 to image 5.12.
637 637  
638 638  [[image:image-20241121180030-15.png]]
639 639  
640 - image 7.11 ui_water_leak/CMakeLists.txt before modification
369 + image 5.11 ui_water_leak/CMakeLists.txt before modification
641 641  
642 642  [[image:image-20241121180517-16.png]]
643 643  
644 - image 7.12 ui_water_leak/CMakeLists.txt after modification
373 + image 5.12 ui_water_leak/CMakeLists.txt after modification
645 645  
375 +**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.
646 646  
647 -8. Modify the **ui_water_leak.h** file. Images 7.13 and 7.14 show the code before modification, while Images 7.15 and 7.16 show the code after modification.
648 -
649 649  [[image:image-20241122094200-23.png]]
650 650  
651 - image 7.13 ui_water_leak.h (1) before modification
379 + image 5.13 ui_water_leak.h (1) before modification
652 652  
653 653  [[image:image-20241122094320-24.png||height="852" width="554"]]
654 654  
655 - image 7.14 ui_water_leak.h (2) before modification
383 + image 5.14 ui_water_leak.h (2) before modification
656 656  
657 657  [[image:image-20241122094600-25.png||height="1078" width="554"]]
658 658  
659 - image 7.15 ui_water_leak.h (1) after modification
387 + image 5.15 ui_water_leak.h (1) after modification
660 660  
661 661  [[image:image-20241122094719-26.png||height="941" width="583"]]
662 662  
663 - image 7.16 ui_water_leak.h (2) before modification
391 + image 5.16 ui_water_leak.h (2) before modification
664 664  
665 -9. **Modify ui_water_leak.c file.** The image 7.17, 7.18, 7.19 show the code before modification, and the image 7.20, 7.21, 7.22 show the code after modification.
393 +**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.
666 666  
667 667  _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.
668 668  
669 669  [[image:image-20241122102929-27.png||height="619" width="426"]]
670 670  
671 - image 7.17 ui_water_leak.c (1) before modification
399 + image 5.17 ui_water_leak.c (1) before modification
672 672  
673 673  [[image:image-20241122112838-30.png||height="551" width="628"]]
674 674  
675 - image 7.18 ui_water_leak.c (2) before modification
403 + image 5.18 ui_water_leak.c (2) before modification
676 676  
677 677  [[image:image-20241122110815-29.png||height="725" width="712"]]
678 678  
679 - image 7.19 ui_water_leak.c (3) before modification
407 + image 5.19 ui_water_leak.c (3) before modification
680 680  
681 681  [[image:image-20241122113158-31.png||height="872" width="677"]]
682 682  
683 - image 7.20 ui_water_leak.c (1) after modification
411 + image 5.20 ui_water_leak.c (1) after modification
684 684  
685 685  [[image:image-20241122113259-33.png||height="874" width="724"]]
686 686  
687 - image 7.21 ui_water_leak.c (2) after modification
415 + image 5.21 ui_water_leak.c (2) after modification
688 688  
689 689  [[image:image-20241122113359-34.png||height="804" width="746"]]
690 690  
691 - image 7.22 ui_water_leak.c (3) after modification
419 + image 5.22 ui_water_leak.c (3) after modification
692 692  
693 -10. **Modify ui_water_leak_events.h file.** The image 7.23 show the code before modification, and the image 7.24 show the code after modification.
421 +**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.
694 694  
695 695  [[image:image-20241122134113-35.png||height="380" width="421"]]
696 696  
697 - image 7.23 ui_water_leak_events_.h before modification
425 + image 5.23 ui_water_leak_events_.h before modification
698 698  
699 699  [[image:image-20241122134420-37.png||height="201" width="283"]]
700 700  
701 -image 7.24 ui_water_leak_events_.h after modification
429 +image 5.24 ui_water_leak_events_.h after modification
702 702  
703 -11.** Modify ui_water_leak_events.c file.** The image 7.25 show the code before modification, and the image 7.26 show the code after modification.
431 +**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.
704 704  
705 705  Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
706 706  
... ... @@ -714,15 +714,14 @@
714 714  
715 715  [[image:image-20241122135023-38.png||height="358" width="372"]]
716 716  
717 - image 7.25 ui_water_leak_events_.c before modification
445 + image 5.25 ui_water_leak_events_.c before modification
718 718  
719 719  [[image:image-20241122135258-39.png||height="403" width="559"]]
720 720  
721 - image 7.26 ui_water_leak_events_.c after modification
449 + image 5.26 ui_water_leak_events_.c after modification
722 722  
451 +**12. Modify ui_water_leak_style.c file.**
723 723  
724 -12. **Modify ui_water_leak_style.c file.**
725 -
726 726  Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
727 727  
728 728   add '#include "../../sort.h"'
... ... @@ -731,68 +731,60 @@
731 731  
732 732  [[image:image-20241122141536-41.png||height="361" width="612"]]
733 733  
734 - image 7.27 ui_water_leak_style.c (1) before modification
461 + image 5.27 ui_water_leak_style.c (1) before modification
735 735  
736 736  [[image:image-20241122142129-42.png||height="386" width="613"]]
737 737  
738 - image 7.28 ui_water_leak_style.c (1) after modification
465 + image 5.28 ui_water_leak_style.c (1) after modification
739 739  
740 -
741 741  Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
742 742  
743 - delete code as shown in image 7.29
469 + delete code as shown in image 5.29
744 744  
745 745  [[image:image-20241122145620-44.png||height="757" width="671"]]
746 746  
747 - image 7.29 ui_water_leak_style.c (2)
473 + image 5.29 ui_water_leak_style.c (2)
748 748  
475 +Step3. The image 5.30, 5.31 show the change.
749 749  
750 -Step3. The image 7.30, 7.31 show the change.
751 -
752 752  [[image:image-20241122152026-45.png||height="277" width="828"]]
753 753  
754 - image 7.30 ui_water_leak_style.c (3) before modification
479 + image 5.30 ui_water_leak_style.c (3) before modification
755 755  
756 756  [[image:image-20241122152542-46.png||height="293" width="830"]]
757 757  
758 - image 7.31 ui_water_leak_style.c (3) after modification
483 + image 5.31 ui_water_leak_style.c (3) after modification
759 759  
485 +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).
760 760  
761 -Step4. Copy partly the code in ui_water_leak.c, paste at extra_lib/sort.h(The process is shown in image 7.32, 7.33).
762 -
763 763  [[image:image-20241122153958-47.png]]
764 764  
765 - image 7.32 ui_water_leak_style.c (4)
489 + image 5.32 ui_water_leak_style.c (4)
766 766  
767 -
768 768  [[image:image-20241122154755-49.png||height="864" width="513"]]
769 769  
770 - image 7.33 ui_water_leak_style.c (4)
493 + image 5.33 ui_water_leak_style.c (4)
771 771  
495 +Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
772 772  
773 -Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 7.34).
774 -
775 775  [[image:image-20241122155650-50.png||height="922" width="513"]]
776 776  
777 - image 7.34 ui_water_leak_style.c (5)
499 + image 5.34 ui_water_leak_style.c (5)
778 778  
501 +Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
779 779  
780 -Step6. Add some lines of code in extra_lib/sort.h as shown in image 7.35.
781 -
782 782  [[image:image-20241122161934-51.png]]
783 783  
784 - image 7.35
505 + image 5.35
785 785  
507 +Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
786 786  
787 -Step7. Add a line of code in extra_lib/sort.h as shown in image 7.36.
788 -
789 789  [[image:image-20241122162852-53.png||height="330" width="529"]]
790 790  
791 - image 7.37
511 + image 5.37
792 792  
513 +Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
793 793  
794 -Step8. Add some code in ui_water_leak_style.c as shown in image 7.38 from line534 to line 576 in detail.
795 -
796 796  panel_with_type union_sensor;
797 797  
798 798  union_sensor.panel_type = WATER_LEAK_TYPE;
... ... @@ -805,45 +805,35 @@
805 805  
806 806  return union_sensor;
807 807  
808 -[[image:image-20250122173546-6.png||height="777" width="922"]]
527 +[[image:image-20241122171211-54.png||height="635" width="792"]]
809 809  
810 - image 7.38
529 + image 5.38
811 811  
531 +**13. Modify sort.c file.**
812 812  
813 -13. Rest midification in sort.h file.
533 +Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
814 814  
815 -In image 7.39 as below, we can see "WATER_LEAK_TYPE" at line 24 and water leak switch status definition at line 32,33, and these are what we need to add in sort.h.
535 +[[image:image-20241122173718-56.png||height="378" width="579"]]
816 816  
817 -[[image:image-20250122170230-1.png||height="580" width="513"]]
537 + image 5.39 sort.c (1)
818 818  
819 - image 7.39 sort.h
820 -
821 -13. **Modify sort.c file.**
822 -
823 -Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 26.
824 -
825 -[[image:image-20250122171910-5.png||height="524" width="510"]]
826 -
827 - image 7.40 sort.c (1)
828 -
829 829  There are still some changes need to be done in sort.c, and omit here for the moment.
830 830  
831 831  
542 += 6. FAQ =
832 832  
833 -= 8. FAQ =
544 +== 6.1 ==
834 834  
835 -== 8.1 ==
836 836  
547 += 7. Order Info =
837 837  
838 -= 9. Order Info =
549 +== 7.1  Part Number ==
839 839  
840 -== 9.1  Part Number ==
841 841  
842 -
843 843  Part Number: (% style="color:#4472c4" %)LTS5
844 844  
845 845  
846 -== 9.2  Packing Info ==
555 +== 7.2  Packing Info ==
847 847  
848 848  
849 849  **Package Includes**:
... ... @@ -852,21 +852,20 @@
852 852  * 5V,2A DC Power Adapter.
853 853  * USB Type C Program Cable
854 854  
855 -= 10. Support =
564 += 8. Support =
856 856  
857 857  
858 858  * 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.
859 859  * 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]].
860 860  
861 -= 11.  Reference material =
570 += 9.  Reference material =
862 862  
863 863  
864 864  * Datasheet
865 -* schematic: [[LTS5-V1>>attach:LTS5-V1.pdf]]
866 -* Source Code: [[dragino/LoRa-HMI-Touch-Screen: Open Source LoRa / LoRaWAN HMI Touch Screen Project>>url:https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main]]
574 +* Source Code
867 867  * Mechinical
868 868  
869 -= 12. FCC Warning =
577 += 10. FCC Warning =
870 870  
871 871  
872 872  This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
1738893226894-758.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -25.6 KB
Content
LTS5-V1.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -661.6 KB
Content
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-20241226135550-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -293.3 KB
Content
image-20250122170230-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -77.3 KB
Content
image-20250122171809-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20250122171825-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20250122171832-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20250122171910-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20250122173546-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -200.4 KB
Content
image-20250207100150-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -54.1 KB
Content
image-20250207101415-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -17.6 KB
Content
image-20250207101515-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -24.1 KB
Content
image-20250207142334-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -62.0 KB
Content
image-20250207143131-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -48.7 KB
Content
image-20250207144605-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -58.1 KB
Content
image-20250207164320-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -194.5 KB
Content
image-20250207165702-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -78.1 KB
Content
image-20250207170215-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.6 KB
Content
image-20250207170307-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.2 KB
Content
image-20250207171650-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -11.0 KB
Content
image-20250207171851-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.5 KB
Content
image-20250207172010-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.5 KB
Content
image-20250207172246-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.5 KB
Content
image-20250207172443-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207172821-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -0 bytes
Content
image-20250207172834-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -0 bytes
Content
image-20250207173152-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207173159-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207173206-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207173212-27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207192107-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -14.3 KB
Content
image-20250208170737-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -36.9 KB
Content
image-20250208170758-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -36.9 KB
Content
image-20250208175819-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -36.3 KB
Content
image-20250208175918-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -37.8 KB
Content
image-20250208180010-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -36.7 KB
Content
image-20250208181019-4.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -546.8 KB
Content
image-20250208181139-5.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -320.5 KB
Content
image-20250208181317-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -34.8 KB
Content
image-20250208181328-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -34.8 KB
Content
image-20250208181700-8.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -526.4 KB
Content
image-20250505112032-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -43.9 KB
Content
image-20250505121328-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -12.2 KB
Content
squareline-studio-launcher-screen.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -203.4 KB
Content