Skip to Content
Last modified by BoYang Xie on 2025/07/17 15:54
From version 189.4
edited by BoYang Xie
on 2025/07/09 11:41
Change comment: There is no comment for this version
To version 112.1
edited by BoYang Xie
on 2024/11/22 17:37
Change comment: Uploaded new attachment "image-20241122173706-55.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,10 +1,12 @@
1 -
1 +(% style="text-align:center" %)
2 +[[image:image-20240915231842-1.png]]
2 2  
3 -[[image:image-20241226135550-1.png||data-xwiki-image-style-alignment="center"]]
4 4  
5 5  
6 6  
7 7  
8 +
9 +
8 8  (% _mstvisible="1" %)
9 9  (% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:**
10 10  
... ... @@ -19,23 +19,20 @@
19 19  
20 20  = 1.  Introduction =
21 21  
22 -== 1.1  What is the LTS5 LoRa HMI Touch Screen? ==
24 +== 1.1  What is LTS5 LoRa HMI touch screen ==
23 23  
24 24  
25 -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.
26 26  
27 -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.
28 28  
29 -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.
30 30  
31 -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.
32 32  
33 33  
34 -**//Note: Due to the current incomplete functionality, it is not recommended to purchase at this time.//**
35 -
36 36  == 1.2  Features ==
37 37  
38 -
39 39  * ESP32-WROOM MCU: 8MB RAM & 16MB ROM
40 40  * Dragino LA66 LoRa Module
41 41  * Support Private LoRa protocol or LoRaWAN protocol
... ... @@ -48,7 +48,7 @@
48 48  * 5V DC power
49 49  * IP Rating: IP52
50 50  
51 -== 1.3  Specifications ==
50 +== 1.3  Specification ==
52 52  
53 53  
54 54  **LoRa**:
... ... @@ -103,37 +103,28 @@
103 103  * Smart Cities
104 104  * Smart Factory
105 105  
106 -= 2.  Getting Started with 'Hello World' =
105 += 2.  Getting Started with Hello World =
107 107  
108 108  == 2.1  About this demo ==
109 109  
110 110  
111 -This getting started example demonstrates how to design and deploy a simple display UI for the LTS5 device. The example includes:
110 +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.
112 112  
113 -* Creating a basic UI with a single button.
114 -* Implementing functionality to navigate the Web UI to a new page when the button is clicked.
115 -* Uploading the UI to the LTS5 device.
116 116  
117 -By completing this demo, you will gain foundational knowledge for customizing the LTS5 interface and building more advanced IoT applications.
118 -
119 -
120 120  == 2.2  Install Software Running Environment ==
121 121  
115 +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.
122 122  
123 -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.
117 +=== 2.2.1 Install VSCode and ESP-IDF extension ===
124 124  
125 125  
126 -=== 2.2.1 Install VS Code and ESP-IDF extension ===
120 +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]].
127 127  
122 +Next, you need to install the ESP-IDF extension within VSCode. The detailed operation steps are illustrated in image 1.
128 128  
129 -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]].
130 -
131 -Next, install the **ESP-IDF** extension within **VS Code**. Detailed steps for this process are shown in Image 1.
132 -
133 -
134 134  [[image:image-20240928110211-5.png||height="508" width="866"]]
135 135  
136 - Image 1: ESP-IDF extension install
126 + image 1 ESP-IDF extension install
137 137  
138 138  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]]
139 139  
... ... @@ -141,220 +141,159 @@
141 141  === 2.2.2 Install SquareLine Studio ===
142 142  
143 143  
144 -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.
134 +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]].
145 145  
146 -[[image:squareline.io_downloads.png||height="888" width="1294"]]
136 +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.
147 147  
148 148  
149 -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:
139 +== 2.3 Simple usage of SquareLine Studio and export UI code ==
150 150  
151 -* Max. 10 screens
152 -* Max. 150 widgets
153 -* Max. 5 global colors
154 -* Max. 2 themes
155 -* Max. 1 component
156 156  
157 -== 2.3 Simple usage of SquareLine Studio and exporting UI code ==
142 +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.
158 158  
144 +[[image:image-20240928103357-2.png||height="680" width="708"]]
159 159  
160 -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**.
146 + image 2 create a SquareLine project
161 161  
162 -* In the **PROJECT SETTINGS**, select **LVGL version **as **8.3.11** and **Resolution** as **800** x **480**.
163 -* Select the **CREATE **button to create the new project with the selected settings.
148 +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.
164 164  
165 -[[image:squareline-studio-launcher-screen.png||height="752" width="1415"]]
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  
152 + 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 Path**: 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  
156 + image 4 modify project settings
181 181  
182 -Now you can start building the user interface. Follow the steps below:
158 +Now we can start to use this software. Here are some usage information for this software.
183 183  
160 +**~1. add widget**
184 184  
185 -=== **Add widgets** ===
162 +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 -After creating a project, a **Screen** will be automatically added. Its name is **Screen1** by default.
189 -
190 -To add a widget, navigate to the **Widgets** panel, and then click on the widget you want to add to the screen. You can reposition the widgets in the screen area by clicking and dragging them. Now add a **Label**, **Button**, and **Image** as shown in the image below. The added widgets are also displayed in the **Hierarchy **panel.
191 -
192 192  [[image:image-20240928111412-6.png||height="526" width="864"]]
193 193  
166 + image 5 add widgets
194 194  
195 -Then click the **Screen **widget to add the second screen. After adding the second screen, it will appear in the Screens panel as **Screen2**.
168 +**2. modify widget**
196 196  
197 -[[image:Screenshot 2024-12-24 140459.png||height="278" width="290"]]
170 +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".
198 198  
199 -=== **Modify widget properties** ===
200 -
201 -
202 -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.
203 -
204 204  [[image:1727485118799-984.png]]
205 205  
174 + image 6 the button widget's "Inspector" tab
206 206  
207 -==== **Changing the Button properties** ====
176 +Second part: "Layout" means a auto position-management for widgets contained in the parent widget. "Transform" includes size, position and align modification.
208 208  
209 -
210 -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:
211 -
212 -* **Flex Flow**: No Layout
213 -* **Transform**:
214 -** **X**: 331 px
215 -** **Y**: 203 px
216 -** **Width**: 100 px
217 -** **Height**: 50 px
218 -** **Align**: CENTER
219 -
220 220  [[image:1727485251053-655.png]]
221 221  
180 +image 7 the button widget's "BUTTON" tab
222 222  
223 -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.
182 +Third part: It is an area of style setting.
224 224  
225 -* Click **ADD EVENT** button. A new section will appear to configure this event.
184 +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.
226 226  
227 -[[image:Screenshot 2024-12-24 134937.png||height="80" width="290"]]
228 -
229 -* 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.
230 -
231 -[[image:Screenshot 2024-12-24 134818.png||height="222" width="290"]]
232 -
233 -* 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.
234 -* Finally, click the **ADD** button.
235 -
236 236  [[image:1727485480434-713.png||height="395" width="290"]]
237 237  
238 - Image 8: Add an event for the button
188 + image 8 add event for button
239 239  
190 +**3. change label widget content**
240 240  
241 -==== **Changing the label properties** ====
192 +Modify the content in text as shown in image 9, the text content of label widget will be changed accordingly.
242 242  
243 -
244 -Click the Label you have added to the screen. Under the **Label** section, type "**Click for Detail**" in the **Text** textbox.
245 -
246 246  [[image:image-20240928090825-1.png||height="327" width="391"]]
247 247  
196 + image 9 modify text content of label widget
248 248  
249 -Once you enter the text, it will immediately appear on the label.
198 +**4. Add image into project**
250 250  
200 +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.
251 251  
252 -==== **Changing image properties** ====
253 -
254 -
255 -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.
256 -
257 -One way is to move your image into the folder "…/squareline project/assets/", as shown in the image below.
258 -
259 259  [[image:image-20240928113424-9.png||height="355" width="505"]]
260 260  
204 + image 10 add image file into SquareLine Studio project
261 261  
262 -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.
263 -
264 264  [[image:image-20240928114139-10.png||height="559" width="810"]]
265 265  
208 + image 11 use image widget in SquareLine Studio
266 266  
267 -==== **The relationship between widgets** ====
210 +**5. The relationship between widgets**
268 268  
212 +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.
269 269  
270 -Widgets commonly have two types of relationships: **parallel** and **parent-child**.
271 -
272 -* In a **parallel relationship**, widgets' positions are determined relative to a shared reference object.
273 -* 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.
274 -
275 275  [[image:1727486567182-334.png||height="318" width="278"]]
276 276  
216 +image 12 move label1 to make label1 widget be a child of button1 widget(1)
277 277  
278 -Move the label, **Label1** to make it a child of **Button1** as shown in the image below.
279 -
280 280  [[image:image-20240928112001-8.png||height="431" width="796"]]
281 281  
220 + image 13 move label1 to make label1 widget be a child of button1 widget(2)
282 282  
283 -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.
222 +**6. Preview the final effect**
284 284  
285 -[[image:Screenshot 2024-12-24 144005.png||height="360" width="290"]]
224 +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.
286 286  
287 -
288 -==== **Preview the screen** ====
289 -
290 -
291 -You can test the result by clicking on the **PLAY** button as shown in the image below. The screen will change into play mode.
292 -
293 293  [[image:1727487368023-281.png]]
294 294  
228 + image 14 click on the triangle icon to start or end the simulation
295 295  
296 -For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
230 +For more detailed usage, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
297 297  
298 298  
299 -== 2.4 Integrate UI Code into an ESP-IDF Project ==
233 +== 2.4 Integrate UI Code to ESP-IDF Project ==
300 300  
301 301  
302 -To integrate, first export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
236 +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.
303 303  
304 -On the  menubar, click **Export -> Export UI** Files as shown in the image below.
305 -
306 306  [[image:1727229798126-306.png]]
307 307  
240 + image 15 export UI file
308 308  
309 -The exported UI files can be found in your SquareLine project folder as shown in the image below.
310 -
311 -
312 312  [[image:1727229821582-258.png||height="333" width="662"]]
313 313  
244 + image 16 exported UI file
314 314  
315 -Create a new folder named "**ui**" at path "**basic_prj/app_components/ui/**", and copy all the exported UI code into it as shown in the image below.
246 +Create a empty directory entitled "ui" in path "basic_prj/app_components/ui/", and then copy all UI code exported to this directory.
316 316  
317 317  [[image:image-20240928144830-11.png]]
318 318  
250 + image 17 open CMakeLists.txt
319 319  
320 -Open the **CMakeLists.txt** file and edit it as ahown below.
321 -
322 322  [[image:1727229892636-154.png||height="521" width="407"]]
323 323  
254 + image 18 modify CMakeLists.txt
324 324  
325 -Open the main.c file and  add two lines of code as shown in the below images.
256 +The last step of integrating is adding two lines of code in main.c file.
326 326  
327 -Add **#include "ui.h"**
328 -
329 329  [[image:1727229926561-300.png]]
330 330  
260 + image 19 add "ui.h"
331 331  
332 -Add **ui_init();**
333 -
334 334  [[image:1727229955611-607.png]]
335 335  
264 + image 20 add "ui_init()"
336 336  
337 -== 2.5 Brief introduction to the Hello World project ==
338 338  
267 +== 2.5 Brief introduction of hello world project ==
339 339  
340 -The project consists of two screens. The first screen displays the company's logo, the project name, and a button to navigate to the next screen. The second screen provides information about the HMI screen product through an image and includes a button to return to the previous screen.
341 341  
270 +The project consists of two screens. The first screen displays the company's logo, the project name, and a button to navigate to the next screen. The second screen presents some information about this HMI screen product through an image and includes a button to return to the previous screen.
342 342  
272 +
343 343  == 2.6 Test Result ==
344 344  
345 345  
346 -By pressing the button located at the bottom right, the screen switches to the next one as expected. This confirms that the UI file has been successfully integrated into the project and is functioning correctly.
276 +By pressing the button lying bottom right, the screen can switch to another as expected. This indicates that the UI file has been successfully integrated into the project and is now effective.
347 347  
348 -Screen 1:
349 -
350 350  [[image:1727488067077-684.png||height="402" width="574"]]
351 351  
280 + image 21 screen1
352 352  
353 -Screen 2:
354 -
355 355  [[image:1727488157579-949.png||height="397" width="572"]]
356 356  
284 + image 22 screen2
357 357  
286 +
358 358  = 3. Example Project 1: LoRa Central Display =
359 359  
360 360  [[image:image-20240916101737-1.png||height="468" width="683"]]
... ... @@ -362,490 +362,105 @@
362 362  
363 363  = 4. Example Project 2: LoRaWAN RS485 Alarm =
364 364  
365 -= 5. Example Project 3: P2P =
366 -
367 -The project achieves the function of receiving LoRa P2P messages and displaying them on the screen. The workflow is as follows: A LA66, running a P2P program, sends a message in a particular format via an AT command. Then, the LTS5 receives the message and displays it on the screen.
368 -
369 -The project can be found at [[this link>>url:https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/P2P]].
370 -
371 -== 5.1 Firmware Flashing ==
372 -
373 -
374 -The following software tools are required to flash firmware to the ESP32 and LA66.
375 -
376 -* Download the ESP32 firmware flash tool from [[this link>>https://docs.espressif.com/projects/esp-test-tools/en/latest/esp32/production_stage/tools/flash_download_tool.html]].
377 -* Download the LA66 firmware flash tool from [[this link>>https://www.dropbox.com/scl/fo/9kqeqf6wmet10o9hgxuwa/h?rlkey=4ikrg6kg5v0yjxwhp0i37wrv7&e=1&dl=0]].
378 -
379 -=== 5.1.1 Upload the Firmware to the ESP32 ===
380 -
381 -Open //**flash_download_tool.exe**// and follow the steps below.
382 -
383 -* **Chip Type**: ESP32-S3
384 -* **WorkMode**: Develop
385 -* **LoadMode**: UART
386 -* Click on the **OK** button.
387 -
388 -[[image:1738893226894-758.png||height="170" width="176"]]
389 -
390 -
391 -In the **SPIDownload** tab,
392 -
393 -* Select the checkboxes for ESP32_LoRaC-P2P_CommonFW_v1.0.0.bin.
394 -* SPI Flashing Config(default configuration):
395 -** **SPI SPEED**: 40MHz
396 -** **SPI MODE**: DIO
397 -** Check **DoNotChgBin** option.
398 -* **COM**: Select the correct COM port.
399 -* **BAUD**: 1152000
400 -* Click on the **START** button.
401 -
402 -[[image:image-20250505122103-4.png||height="551" width="705"]]
403 -
404 -The progress bar will indicate the firmware update progress and display a **FINISH** message once the update is complete.
405 -
406 -
407 -=== 5.1.2 Upload the Firmware to the LA66 ===
408 -
409 -Open **Dragino_Sensor_Manager_Utility.exe**, and then follow the steps below.
410 -
411 -* Click on the UART Update Firmware tab.
412 -* Select the correct COM port.
413 -* Click on the Upload_File button and select the LA66_P2P_FW_v1.0.0.bin file.
414 -* Click on the Start button.
415 -
416 -
417 -
418 -[[image:image-20250505121328-2.png]]
419 -
420 -
421 -[[image:image-20250505121531-3.png]]
422 -
423 423  (% class="wikigeneratedid" %)
424 -The progress bar will indicate the firmware update progress.
295 += 5.  The way to add a new panel to project =
425 425  
297 +~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.
426 426  
427 -== 5.2 AT commands and LTS5 Panel Data Formats ==
428 -
429 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**01**A4CBBB0A8E085C02,0,3
430 -
431 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**02**A4CB00,0,3
432 -
433 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**03**A4CB00,0,3
434 -
435 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**04**A4CB00,0,3
436 -
437 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**05**A4CB00,0,3
438 -
439 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**06**A4CB00,0,3
440 -
441 -**LTS5 panel data format**:
442 -
443 -~1. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF  A84041000181D4A8  01  A4CB  BB0A  8E08  5C02**,0,3
444 -
445 -**01:** encrypt. 1 Byte. 01 ~-~-> no encryption. This 1-byte information is now invalid; simply write 0x01 instead.
446 -
447 -**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.
448 -
449 -**A84041000181D4A8:** Device EUI. 8 Bytes. The last three Bytes will be extracted by the ESP32-S3 and displayed on the screen.
450 -
451 -**01: **Panel Type. 1 Byte. 0x01~-~->Tem & Hum,
452 -
453 - 0x02~-~->Door,
454 -
455 - 0x03~-~->Water Leak,
456 -
457 - 0x04~-~->Occupied,
458 -
459 - 0x05~-~->Button,
460 -
461 - 0x06~-~->Alarm,
462 -
463 -**A4CB: **Battery level//. //2 Bytes. Battery Voltage =0xCBA4&0x3FFF=0x0BA4=2980mV
464 -
465 -**BB0A: **The temperature of the built-in sensor in LHT65N.// //2 Bytes. Temperature:  0x0ABB/100=27.47℃
466 -
467 -**8E08: **The temperature of the External temperature sensor.// //2 Bytes. Temperature:  0x088E/100=21.90℃
468 -
469 -**5C02：**The humidity of the built-in sensor in LHT65N. 2 Bytes. Humidity: 0x025C/10=60.4%
470 -
471 -2. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF**  **A84041000181D4A8**  **02  A4CB  00**,0,3
472 -
473 -Specific sections of the data share the same function.
474 -
475 -**00: Status. **1 Byte//. //If Panel Type is 0x02, **Status: 00~-~->Open; 01~-~->Close.**
476 -
477 - If Panel Type is 0x03, **Status: 00~-~->Normal; 01~-~->Water Leaking.**
478 -
479 - If Panel Type is 0x04, **Status: 00~-~->Free; 01~-~->Occupied.**
480 -
481 - If Panel Type is 0x05, **Status: 00~-~->OFF; 01~-~->ON.**
482 -
483 - If Panel Type is 0x06, **Status: 00~-~->OFF; 01~-~->Alarm.**
484 -
485 -== 5.3 Usage ==
486 -
487 -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.
488 -
489 -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.
490 -
491 -[[image:image-20250207143131-11.png||height="527" width="547"]]
492 -
493 -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.
494 -
495 -[[image:image-20250207144605-12.png||height="634" width="548"]]
496 -
497 -LTS5 receives this message and displays it on its screen as the image below shows.
498 -
499 -[[image:image-20250208181700-8.jpeg||height="528" width="704"]]
500 -
501 -= 6. Example Project 4: LoRaWAN_CLASS_C =
502 -
503 -
504 -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.
505 -
506 -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.
507 -
508 -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).
509 -
510 -The project can be found at [[this link>>https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/LoRaWAN_CLASS_C]].
511 -
512 -== 6.1 firmware flashing approach ==
513 -
514 -The firmware flashing approach is the same as described in section 5.1.
515 -
516 -== 6.2 flowchart ==
517 -
518 -[[image:image-20250207164320-13.png||height="696" width="1344"]]
519 -
520 -== 6.3 Usage ==
521 -
522 -This section now describes a process involving TTN downlink panel data that is to be displayed on the LTS5 screen.
523 -
524 -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.
525 -
526 -[[image:image-20250207165702-14.png||height="830" width="563"]]
527 -
528 -6.3.2 Switch to Class C using "AT+CLASS=C", and check the class with "AT+CLASS=?".
529 -
530 -[[image:image-20250207173212-27.png]]
531 -
532 -[[image:image-20250207172246-20.png]]
533 -
534 -6.3.3 Verify LA66's join status (in LTS5) with "AT+NJS=?". If not joined, connect manually to LoRaWAN with "AT+JOIN".
535 -
536 -[[image:image-20250207172010-19.png]]
537 -
538 -[[image:image-20250207171650-17.png]]
539 -
540 -6.3.4 After joining, send a message to TTN, such as "AT+SENDB=01,02,8,05820802581ea0a5", to activate communication.
541 -
542 -[[image:image-20250207192107-28.png]]
543 -
544 -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.
545 -
546 -There is an example for TTN downlink.
547 -
548 -1. downlink DEUI F1A84041000181D4A8
549 -1. downlink Dev Name F24B69746368656E2D467269676531FFFF
550 -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.
551 -
552 -[[image:image-20250208175819-1.png||height="503" width="502"]]
553 -
554 -
555 -[[image:image-20250208175918-2.png||height="505" width="502"]]
556 -
557 -
558 -[[image:image-20250208180010-3.png||height="507" width="503"]]
559 -
560 -
561 -[[image:image-20250208181019-4.jpeg||height="592" width="790"]]
562 -
563 -
564 -[[image:image-20250208181328-7.png||height="505" width="504"]]
565 -
566 -
567 -[[image:image-20250208181139-5.jpeg||height="594" width="792"]]
568 -
569 -
570 -= 7. The method for adding a new type of panel to the project =
571 -
572 -If you don't have this need, then this part of the content can be ignored.
573 -
574 -1. Design a panel in SquareLine Studio, as shown in Image 7.1 below for reference.
575 -
576 576  [[image:image-20241121113445-1.png||height="584" width="934"]]
577 577  
578 - Image 7.1: a panel about water_leak
301 + image 5.1 a panel about water_leak
579 579  
303 +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.
580 580  
581 -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.
582 -
583 583  [[image:image-20241121141120-4.png||height="383" width="795"]]
584 584  
585 - Image 7.2: Exported UI files
307 + image 5.2 ui files exported
586 586  
309 +3. Delete or rename some file. Here are the steps:
587 587  
588 -3. **Delete and rename some file.** Here are the steps:
311 + 3.1 Delete the 'components' directory.
312 + 3.2 Delete 'filelist.txt'.
313 + 3.3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
314 + 3.4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
315 + 3.5 Rename the 'screens' directory to 'styles'.
589 589  
590 - Step 1: Delete the 'components' directory.
591 - Step 2: Delete 'filelist.txt'.
592 - Step 3: Delete 'ui_helpers.c' and 'ui_helpers.h'.
593 - Step 4: Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
594 - Step 5: Rename the 'screens' directory to 'styles'.
595 -
596 596  [[image:image-20241121151934-10.png||height="303" width="792"]]
597 597  
598 - image 7.3 rest file (1)
319 + image 5.3 rest file 1
599 599  
600 600  [[image:image-20241121142925-7.png||height="141" width="793"]]
601 601  
602 - image 7.4 rest file (2)
323 + image 5.4 rest file 2
603 603  
604 -4. Open the project in VS Code.
325 +4. Open this project in vscode.
605 605  
606 -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**."
327 +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.
607 607  
608 608  [[image:image-20241121181957-17.png||height="438" width="516"]]
609 609  
610 - image 7.5 extra_lib/CMakeLists.txt before adding
331 + image 5.5 before add
611 611  
612 612  [[image:image-20241121182239-18.png||height="520" width="518"]]
613 613  
614 - image 7.6 extra_lib/CMakeLists.txt after adding
335 + image 5.6 after add
615 615  
616 -6.  **Modify the header files included in the fonts and images directories**.
337 +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.
617 617  
618 -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.
619 -
620 620  [[image:image-20241121171629-11.png]]
621 621  
622 - image 7.7 unmodified font file
341 + image 5.7 before-modified font file
623 623  
624 624  [[image:image-20241121171901-12.png]]
625 625  
626 - image 7.8 modified font file
345 + image 5.8 modified font file
627 627  
628 -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.
347 +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.
629 629  
630 630  [[image:image-20241121172714-13.png]]
631 631  
632 - image 7.9 unmodified image file
351 + image 5.9 before-modified image file
633 633  
634 634  [[image:image-20241121172908-14.png]]
635 635  
636 - image 7.10 modified image file
355 + image 5.10 modified image file
637 637  
638 -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).
357 +7. Modify the ui_water_leak/CMakeLists.txt. Open this file, and modify it from image 5.11 to image 5.12.
639 639  
640 640  [[image:image-20241121180030-15.png]]
641 641  
642 - image 7.11 ui_water_leak/CMakeLists.txt before modification
361 + image 5.11 before modification
643 643  
644 644  [[image:image-20241121180517-16.png]]
645 645  
646 - image 7.12 ui_water_leak/CMakeLists.txt after modification
365 + image 5.12 after modification
647 647  
367 +8.
648 648  
649 -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.
650 650  
651 -[[image:image-20241122094200-23.png]]
652 652  
653 - image 7.13 ui_water_leak.h (1) before modification
654 654  
655 -[[image:image-20241122094320-24.png||height="852" width="554"]]
656 656  
657 - image 7.14 ui_water_leak.h (2) before modification
658 658  
659 -[[image:image-20241122094600-25.png||height="1078" width="554"]]
660 660  
661 - image 7.15 ui_water_leak.h (1) after modification
662 662  
663 -[[image:image-20241122094719-26.png||height="941" width="583"]]
664 664  
665 - image 7.16 ui_water_leak.h (2) before modification
666 666  
667 -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.
668 668  
669 -_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.
379 += 6. FAQ =
670 670  
671 -[[image:image-20241122102929-27.png||height="619" width="426"]]
381 +== 6.1 ==
672 672  
673 - image 7.17 ui_water_leak.c (1) before modification
674 674  
675 -[[image:image-20241122112838-30.png||height="551" width="628"]]
384 += 7. Order Info =
676 676  
677 - image 7.18 ui_water_leak.c (2) before modification
386 +== 7.1  Part Number ==
678 678  
679 -[[image:image-20241122110815-29.png||height="725" width="712"]]
680 680  
681 - image 7.19 ui_water_leak.c (3) before modification
682 -
683 -[[image:image-20241122113158-31.png||height="872" width="677"]]
684 -
685 - image 7.20 ui_water_leak.c (1) after modification
686 -
687 -[[image:image-20241122113259-33.png||height="874" width="724"]]
688 -
689 - image 7.21 ui_water_leak.c (2) after modification
690 -
691 -[[image:image-20241122113359-34.png||height="804" width="746"]]
692 -
693 - image 7.22 ui_water_leak.c (3) after modification
694 -
695 -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.
696 -
697 -[[image:image-20241122134113-35.png||height="380" width="421"]]
698 -
699 - image 7.23 ui_water_leak_events_.h before modification
700 -
701 -[[image:image-20241122134420-37.png||height="201" width="283"]]
702 -
703 -image 7.24 ui_water_leak_events_.h after modification
704 -
705 -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.
706 -
707 -Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
708 -
709 -Step2. add code  below in delete_object() function definition.
710 -
711 - panel_all * panel = find_upper_by_SensorPanel(&arr,((lv_obj_t *)(e->user_data~)~)~);
712 -
713 - size_t index = panel->panel_obj_index;
714 -
715 - deleteElement(&arr, index);
716 -
717 -[[image:image-20241122135023-38.png||height="358" width="372"]]
718 -
719 - image 7.25 ui_water_leak_events_.c before modification
720 -
721 -[[image:image-20241122135258-39.png||height="403" width="559"]]
722 -
723 - image 7.26 ui_water_leak_events_.c after modification
724 -
725 -
726 -12. **Modify ui_water_leak_style.c file.**
727 -
728 -Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
729 -
730 - add '#include "../../sort.h"'
731 -
732 - add '#include "ui.h"'
733 -
734 -[[image:image-20241122141536-41.png||height="361" width="612"]]
735 -
736 - image 7.27 ui_water_leak_style.c (1) before modification
737 -
738 -[[image:image-20241122142129-42.png||height="386" width="613"]]
739 -
740 - image 7.28 ui_water_leak_style.c (1) after modification
741 -
742 -
743 -Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
744 -
745 - delete code as shown in image 7.29
746 -
747 -[[image:image-20241122145620-44.png||height="757" width="671"]]
748 -
749 - image 7.29 ui_water_leak_style.c (2)
750 -
751 -
752 -Step3. The image 7.30, 7.31 show the change.
753 -
754 -[[image:image-20241122152026-45.png||height="277" width="828"]]
755 -
756 - image 7.30 ui_water_leak_style.c (3) before modification
757 -
758 -[[image:image-20241122152542-46.png||height="293" width="830"]]
759 -
760 - image 7.31 ui_water_leak_style.c (3) after modification
761 -
762 -
763 -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).
764 -
765 -[[image:image-20241122153958-47.png]]
766 -
767 - image 7.32 ui_water_leak_style.c (4)
768 -
769 -
770 -[[image:image-20241122154755-49.png||height="864" width="513"]]
771 -
772 - image 7.33 ui_water_leak_style.c (4)
773 -
774 -
775 -Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 7.34).
776 -
777 -[[image:image-20241122155650-50.png||height="922" width="513"]]
778 -
779 - image 7.34 ui_water_leak_style.c (5)
780 -
781 -
782 -Step6. Add some lines of code in extra_lib/sort.h as shown in image 7.35.
783 -
784 -[[image:image-20241122161934-51.png]]
785 -
786 - image 7.35
787 -
788 -
789 -Step7. Add a line of code in extra_lib/sort.h as shown in image 7.36.
790 -
791 -[[image:image-20241122162852-53.png||height="330" width="529"]]
792 -
793 - image 7.37
794 -
795 -
796 -Step8. Add some code in ui_water_leak_style.c as shown in image 7.38 from line534 to line 576 in detail.
797 -
798 -panel_with_type union_sensor;
799 -
800 -union_sensor.panel_type = WATER_LEAK_TYPE;
801 -
802 -......
803 -
804 -lv_obj_set_x(union_sensor.panel_union.door.ui_PanelSensorDoor, x_by_index(index));
805 -
806 -lv_obj_set_y(union_sensor.panel_union.door.ui_PanelSensorDoor, y_by_index(index));
807 -
808 -return union_sensor;
809 -
810 -[[image:image-20250122173546-6.png||height="777" width="922"]]
811 -
812 - image 7.38
813 -
814 -
815 -13. Rest midification in sort.h file.
816 -
817 -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.
818 -
819 -[[image:image-20250122170230-1.png||height="580" width="513"]]
820 -
821 - image 7.39 sort.h
822 -
823 -13. **Modify sort.c file.**
824 -
825 -Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 26.
826 -
827 -[[image:image-20250122171910-5.png||height="524" width="510"]]
828 -
829 - image 7.40 sort.c (1)
830 -
831 -There are still some changes need to be done in sort.c, and omit here for the moment.
832 -
833 -
834 -
835 -= 8. FAQ =
836 -
837 -== 8.1 ==
838 -
839 -
840 -= 9. Order Info =
841 -
842 -== 9.1  Part Number ==
843 -
844 -
845 845  Part Number: (% style="color:#4472c4" %)LTS5
846 846  
847 847  
848 -== 9.2  Packing Info ==
392 +== 7.2  Packing Info ==
849 849  
850 850  
851 851  **Package Includes**:
... ... @@ -854,21 +854,20 @@
854 854  * 5V,2A DC Power Adapter.
855 855  * USB Type C Program Cable
856 856  
857 -= 10. Support =
401 += 8. Support =
858 858  
859 859  
860 860  * 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.
861 861  * 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]].
862 862  
863 -= 11.  Reference material =
407 += 9.  Reference material =
864 864  
865 865  
866 -* Datasheet: [[https:~~/~~/www.dropbox.com/scl/fo/fr7wjsdfh9huchg59p7bv/APASCR0elWtp_EbUZ1W9K-A?rlkey=pcuptw3dtg5pw9vgt4ag6hs9z&st=ds6hdztg&dl=0>>https://www.dropbox.com/scl/fo/fr7wjsdfh9huchg59p7bv/APASCR0elWtp_EbUZ1W9K-A?rlkey=pcuptw3dtg5pw9vgt4ag6hs9z&st=ds6hdztg&dl=0]]
867 -* schematic: [[LTS5-V1>>https://www.dropbox.com/scl/fo/grwr5b4x1tk2omyjwg06y/ACleSdi5f7p5zRB2mfPH7CE?rlkey=vhcs83jrj9tkmw8wa9m9wo5rx&st=hkhe3bbj&dl=0]]
868 -* 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]]
410 +* Datasheet
411 +* Source Code
869 869  * Mechinical
870 870  
871 -= 12. FCC Warning =
414 += 10. FCC Warning =
872 872  
873 873  
874 874  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-20241122173718-56.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -37.6 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
image-20250505121531-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -21.3 KB
Content
image-20250505122103-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -46.1 KB
Content
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