Skip to Content
Last modified by BoYang Xie on 2025/07/24 16:47
From version 188.2
edited by Xiaoling
on 2025/06/10 17:55
Change comment: There is no comment for this version
To version 73.1
edited by BoYang Xie
on 2024/11/21 18:19
Change comment: Uploaded new attachment "image-20241121181957-17.png", version {1}

Summary

Details

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