Skip to Content
Last modified by BoYang Xie on 2025/07/24 16:47
From version 180.1
edited by Dilisi S
on 2025/02/18 01:33
Change comment: Feb 17 edits - typo
To version 70.1
edited by BoYang Xie
on 2024/11/21 17:29
Change comment: Uploaded new attachment "image-20241121172908-14.png", version {1}

Summary

Details

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