Skip to Content
Last modified by BoYang Xie on 2025/07/24 16:47
From version 164.2
edited by BoYang Xie
on 2025/02/07 19:53
Change comment: There is no comment for this version
To version 49.1
edited by BoYang Xie
on 2024/09/28 11:20
Change comment: Uploaded new attachment "image-20240928112001-8.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,13 +1,9 @@
1 -
1 +
2 +[[image:image-20240915231842-1.png]]
2 2  
3 -(% style="text-align:center" %)
4 -[[image:image-20241226135550-1.png]]
5 5  
6 -
7 -
8 -
9 9  (% _mstvisible="1" %)
10 -(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:**
6 +(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents：**
11 11  
12 12  {{toc/}}
13 13  
... ... @@ -20,22 +20,20 @@
20 20  
21 21  = 1.  Introduction =
22 22  
23 -== 1.1  What is the LTS5 LoRa HMI Touch Screen? ==
19 +== 1.1  What is LTS5 LoRa HMI touch screen ==
24 24  
21 +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.
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.
23 +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.
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.
25 +The HMI touch screen of LTS5 supports drap & drop design. Developer can use SquareLine to easily customize the display UI for different application.
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.
27 +LTS5 use LA66 LoRa module, this module can be program to support private LoRa protocol or LoRaWAN protocol.
31 31  
32 -The LA66 LoRa module can be programmed to support either private LoRa protocols or the LoRaWAN protocol.
33 33  
34 34  == 1.2  Features ==
35 35  
36 -
37 -* ESP32-WROOM MCU: 8MB RAM & 16MB ROM
38 -* Dragino LA66 LoRa Module
32 +* ESP32-WROOM MCU + Dragino LA66 LoRa Module
39 39  * Support Private LoRa protocol or LoRaWAN protocol
40 40  * Support WiFi & BLE wireless protocol
41 41  * 5.0" HMI touch screen
... ... @@ -46,17 +46,10 @@
46 46  * 5V DC power
47 47  * IP Rating: IP52
48 48  
49 -== 1.3  Specifications ==
43 +== 1.3  Specification ==
50 50  
51 -
52 52  **LoRa**:
53 53  
54 -* Frequency Range: 870 MHz ~~ 960 MHz
55 -* TCXO crystal to ensure RF performance on low temperature
56 -* Maximum Power +22 dBm constant RF output
57 -* High sensitivity: -148 dBm
58 -* LoRa Tx Current: <90 mA at +17 dBm, 108 mA at +22 dBm
59 -* LoRa Rx current: <9 mA
60 60  
61 61  **WiFi:**
62 62  
... ... @@ -82,18 +82,15 @@
82 82  
83 83  == 1.4  Power Consumption ==
84 84  
85 -
86 86  * External 5V DC power adapter
87 87  
88 88  == 1.5  Storage & Operation Temperature ==
89 89  
90 -
91 91  * Operation Temperature: -20 ~~ 70°C  (No Dew)
92 92  * Storage Temperature: -30 ~~ 70°C  (No Dew)
93 93  
94 94  == 1.6  Applications ==
95 95  
96 -
97 97  * Smart Buildings & Home Automation
98 98  * Logistics and Supply Chain Management
99 99  * Smart Metering
... ... @@ -101,677 +101,138 @@
101 101  * Smart Cities
102 102  * Smart Factory
103 103  
104 -= 2.  Getting Started with 'Hello World' =
88 += 2.  Getting Start with Hello World =
105 105  
106 106  == 2.1  About this demo ==
107 107  
92 +In this Getting Start 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.
108 108  
109 -This getting started example demonstrates how to design and deploy a simple display UI for the LTS5 device. The example includes:
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 -
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  
96 +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.
98 +=== 2.2.1 Install VSCode and ESP-IDF extension ===
122 122  
100 +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]].
123 123  
124 -=== 2.2.1 Install VS Code and ESP-IDF extension ===
102 +Next, you need to install the ESP-IDF extension within VSCode. The detailed operation steps are illustrated in image 1.
125 125  
104 +[[image:1727229396732-319.png]]
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]].
106 + image 1 ESP-IDF extension install
128 128  
129 -Next, install the **ESP-IDF** extension within **VS Code**. Detailed steps for this process are shown in Image 1.
130 -
131 -
132 -[[image:image-20240928110211-5.png||height="508" width="866"]]
133 -
134 - Image 1: ESP-IDF extension install
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  
138 -
139 139  === 2.2.2 Install SquareLine Studio ===
140 140  
112 +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]].
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.
114 +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.
143 143  
144 -[[image:squareline.io_downloads.png||height="888" width="1294"]]
116 +== 2.3 Simple usage of SquareLine Studio and export UI code ==
145 145  
118 +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.
146 146  
147 -After installation, you can use SquareLine Studio with a **PERSONAL license plan**. Click **LOG IN** and create a free account using your email address. Then activate your PERSONAL license plan for free. You don’t need to provide any credit card information. However, the PERSONAL license plan has the following limitations:
148 148  
149 -* Max. 10 screens
150 -* Max. 150 widgets
151 -* Max. 5 global colors
152 -* Max. 2 themes
153 -* Max. 1 component
121 +[[image:1727233636007-933.png]]
154 154  
155 -== 2.3 Simple usage of SquareLine Studio and exporting UI code ==
123 + image 2 create a SquareLine project
156 156  
125 +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.
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**.
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.
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  
129 + image 3 project settings
170 170  
171 -In the **PROJECT SETTINGS** dialog box, configure/modify the project settings as shown in the image below.
131 +[[image:1727229618724-758.png]]
172 172  
173 -* **UI Files Export Root**: 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.
133 + image 4 modify project settings
176 176  
177 -[[image:image-20240928105309-4.png||height="526" width="556"]]
135 +Now we can start to use this software. The steps for creating this UI are shown in image 5-10.
178 178  
137 +[[image:1727229653254-680.png]]
179 179  
180 -Now you can start building the user interface. Follow the steps below:
139 + image 5 create a UI(1)
181 181  
141 +[[image:1727231038705-173.png]]
182 182  
183 -=== **Add widgets** ===
143 + image 6 create a UI(2)
184 184  
145 +[[image:1727229682537-381.png]]
185 185  
186 -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.
147 + image 7 create a UI(3)
187 187  
188 -[[image:image-20240928111412-6.png||height="526" width="864"]]
149 +We repeat the steps of screen1 in screen2. Then we get screen2 as shown in image 8.
189 189  
151 +[[image:1727229715361-392.png]]
190 190  
191 -Then click the **Screen **widget to add the second screen. After adding the second screen, it will appear in the Screens panel as **Screen2**.
153 + image 8 create a UI(4)
192 192  
193 -[[image:Screenshot 2024-12-24 140459.png||height="278" width="290"]]
155 +Finally, we add click event for screen change to button1 in screen1(shown in image 9) and button2 in screen2.
194 194  
195 -=== **Modify widget properties** ===
157 +[[image:1727229740592-843.png]]
196 196  
159 + image 9 create a UI(5)
197 197  
198 -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.
161 +The event settings of button1 are as image 10 shown. The event adding operation of button2 is similar to button1.
199 199  
200 -[[image:1727485118799-984.png]]
163 +[[image:1727229760857-521.png]]
201 201  
165 + image 10 create a UI(6)
202 202  
203 -==== **Changing the Button properties** ====
204 -
205 -
206 -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:
207 -
208 -* **Flex Flow**: No Layout
209 -* **Transform**:
210 -** **X**: 331 px
211 -** **Y**: 203 px
212 -** **Width**: 100 px
213 -** **Height**: 50 px
214 -** **Align**: CENTER
215 -
216 -[[image:1727485251053-655.png]]
217 -
218 -
219 -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.
220 -
221 -* Click **ADD EVENT** button. A new section will appear to configure this event.
222 -
223 -[[image:Screenshot 2024-12-24 134937.png||height="80" width="290"]]
224 -
225 -* 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.
226 -
227 -[[image:Screenshot 2024-12-24 134818.png||height="222" width="290"]]
228 -
229 -* 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.
230 -* Finally, click the **ADD** button.
231 -
232 -[[image:1727485480434-713.png||height="395" width="290"]]
233 -
234 - Image 8: Add an event for the button
235 -
236 -
237 -==== **Changing the label properties** ====
238 -
239 -
240 -Click the Label you have added to the screen. Under the **Label** section, type "**Click for Detail**" in the **Text** textbox.
241 -
242 -[[image:image-20240928090825-1.png||height="327" width="391"]]
243 -
244 -
245 -Once you enter the text, it will immediately appear on the label.
246 -
247 -
248 -==== **Changing image properties** ====
249 -
250 -
251 -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.
252 -
253 -One way is to move your image into the folder "…/squareline project/assets/", as shown in the image below.
254 -
255 -[[image:image-20240928113424-9.png||height="355" width="505"]]
256 -
257 -
258 -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.
259 -
260 -[[image:image-20240928114139-10.png||height="559" width="810"]]
261 -
262 -
263 -==== **The relationship between widgets** ====
264 -
265 -
266 -Widgets commonly have two types of relationships: **parallel** and **parent-child**.
267 -
268 -* In a **parallel relationship**, widgets' positions are determined relative to a shared reference object.
269 -* 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.
270 -
271 -[[image:1727486567182-334.png||height="318" width="278"]]
272 -
273 -
274 -Move the label, **Label1** to make it a child of **Button1** as shown in the image below.
275 -
276 -[[image:image-20240928112001-8.png||height="431" width="796"]]
277 -
278 -
279 -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.
280 -
281 -[[image:Screenshot 2024-12-24 144005.png||height="360" width="290"]]
282 -
283 -
284 -==== **Preview the screen** ====
285 -
286 -
287 -You can test the result by clicking on the **PLAY** button as shown in the image below. The screen will change into play mode.
288 -
289 -[[image:1727487368023-281.png]]
290 -
291 -
292 -For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
293 -
294 -
295 295  == 2.4 Integrate UI Code to ESP-IDF Project ==
296 296  
169 +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.
297 297  
298 -To integrate, first export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
299 -
300 -On the  menubar, click **Export -> Export UI** Files as shown in the image below.
301 -
302 302  [[image:1727229798126-306.png]]
303 303  
173 + image 11 export UI file
304 304  
305 -The exported UI files can be found in your SquareLine project folder as shown in the image below.
175 +[[image:1727229821582-258.png]]
306 306  
177 + image 12 exported UI file
307 307  
308 -[[image:1727229821582-258.png||height="333" width="662"]]
179 +Create a empty directory entitled ‘ui’ in path “basic_prj/app_components/ui/”, and then copy all UI code exported to this directory.
309 309  
181 +[[image:1727229845835-509.png]]
310 310  
311 -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.
183 + image 13 open CMakeLists.txt
312 312  
313 -[[image:image-20240928144830-11.png]]
185 +[[image:1727229892636-154.png]]
314 314  
187 + image 14 modify CMakeLists.txt
315 315  
316 -Open the **CMakeLists.txt** file and edit it as ahown below.
189 +The last step of integrating is adding two lines of code in main.c file.
317 317  
318 -[[image:1727229892636-154.png||height="521" width="407"]]
319 -
320 -
321 -Open the main.c file and  add two lines of code as shown in the below images.
322 -
323 -Add **#include "ui.h"**
324 -
325 325  [[image:1727229926561-300.png]]
326 326  
193 + image 15 add “ui.h”
327 327  
328 -Add **ui_init();**
329 -
330 330  [[image:1727229955611-607.png]]
331 331  
197 + image 16 add “ui_init()”
332 332  
333 -== 2.5 Brief introduction to the Hello World project ==
199 +== 2.5 Test Result ==
334 334  
201 +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.
335 335  
336 -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.
203 +[[image:1727229990795-405.png]]
337 337  
205 + image 17 screen1
338 338  
339 -== 2.6 Test Result ==
207 +[[image:1727230012478-930.png]]
340 340  
209 + image 18 screen2
341 341  
342 -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.
343 -
344 -Screen 1:
345 -
346 -[[image:1727488067077-684.png||height="402" width="574"]]
347 -
348 -
349 -Screen 2:
350 -
351 -[[image:1727488157579-949.png||height="397" width="572"]]
352 -
353 -
354 354  = 3. Example Project 1: LoRa Central Display =
355 355  
356 356  [[image:image-20240916101737-1.png||height="468" width="683"]]
357 357  
358 358  
216 +
359 359  = 4. Example Project 2: LoRaWAN RS485 Alarm =
360 360  
361 -= 5. Example Project 3: P2P =
362 362  
363 -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.
364 -
365 -The project can be found at [[this link>>url:https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/P2P]].
366 -
367 -== 5.1 firmware flashing approach. ==
368 -
369 -5.1.1 Download this project
370 -
371 -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]].
372 -
373 -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]].
374 -
375 -5.1.4 Upload firmware to esp32
376 -
377 -Open flash_download_tool.exe, and then follow the steps below.
378 -
379 -[[image:1738893226894-758.png||height="170" width="176"]]
380 -
381 -[[image:image-20250207100150-7.png||height="476" width="538"]]
382 -
383 -5.1.5 Upload firmware to la66
384 -
385 -Open Dragino_Sensor_Manager_Utility.exe, and then follow the steps below.
386 -
387 -[[image:image-20250207101415-8.png||height="522" width="618"]]
388 -
389 -[[image:image-20250207101515-9.png||height="522" width="618"]]
390 -
391 -== 5.2 AT command and P2P data format ==
392 -
393 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**01**A4CBBB0A8E085C02,0,3
394 -
395 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**02**A4CB00,0,3
396 -
397 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**03**A4CB00,0,3
398 -
399 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**04**A4CB00,0,3
400 -
401 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**05**A4CB00,0,3
402 -
403 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**06**A4CB00,0,3
404 -
405 -**Data format**:
406 -
407 -~1. AT+SEND=1,**01** **4b69746368656e2d467269676531FFFF A84041000181D4A8 01  A4CB  BB0A  8E08  5C02**,0,3
408 -
409 -**01:** encrypt. 1 Byte. 01 ~-~-> no encryption. This 1-byte information is now invalid; simply write 0x01 instead.
410 -
411 -**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.
412 -
413 -**A84041000181D4A8:** Device EUI. 8 Bytes. The last three Bytes will be extracted by the ESP32-S3 and displayed on the screen.
414 -
415 -**01: **Panel Type. 1 Byte. 0x01~-~->Tem & Hum,
416 -
417 - 0x02~-~->Door,
418 -
419 - 0x03~-~->Water Leak,
420 -
421 - 0x04~-~->Occupied,
422 -
423 - 0x05~-~->Button,
424 -
425 - 0x06~-~->Alarm,
426 -
427 -**A4CB: **Battery level//. //2 Bytes. Battery Voltage =0xCBA4&0x3FFF=0x0BA4=2980mV
428 -
429 -**BB0A: **The temperature of the built-in sensor in LHT65N.// //2 Bytes. Temperature:  0x0ABB/100=27.47℃
430 -
431 -**8E08: **The temperature of the External temperature sensor.// //2 Bytes. Temperature:  0x088E/100=21.90℃
432 -
433 -**5C02：**The humidity of the built-in sensor in LHT65N. 2 Bytes. Humidity: 0x025C/10=60.4%
434 -
435 -2. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF**  **A84041000181D4A8**  **02  A4CB  00**,0,3
436 -
437 -Specific sections of the data share the same function.
438 -
439 -**00: Status. **1 Byte//. //If Panel Type is 0x02, **Status: 00~-~->Open; 01~-~->Close.**
440 -
441 - If Panel Type is 0x03, **Status: 00~-~->Normal; 01~-~->Water Leaking.**
442 -
443 - If Panel Type is 0x04, **Status: 00~-~->Free; 01~-~->Occupied.**
444 -
445 - If Panel Type is 0x05, **Status: 00~-~->OFF; 01~-~->ON.**
446 -
447 - If Panel Type is 0x06, **Status: 00~-~->OFF; 01~-~->Alarm.**
448 -
449 -== 5.3 Usage ==
450 -
451 -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.
452 -
453 -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.
454 -
455 -[[image:image-20250207143131-11.png||height="527" width="547"]]
456 -
457 -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.
458 -
459 -[[image:image-20250207144605-12.png||height="634" width="548"]]
460 -
461 -= 6. Example Project 4: LoRaWAN_CLASS_C =
462 -
463 -
464 -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.
465 -
466 -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.
467 -
468 -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).
469 -
470 -The project can be found at [[this link>>https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/LoRaWAN_CLASS_C]].
471 -
472 -== 6.1 firmware flashing approach ==
473 -
474 -The firmware flashing approach is the same as described in section [[5.1>>5.1]].
475 -
476 -== 6.2 flowchart ==
477 -
478 -[[image:image-20250207164320-13.png||height="696" width="1344"]]
479 -
480 -== 6.3 Usage ==
481 -
482 -6.3.1 TTN downlink panel data to display in LTS5
483 -
484 -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.
485 -
486 -[[image:image-20250207165702-14.png||height="830" width="563"]]
487 -
488 -6.3.2 Switch to Class C using "AT+CLASS=C", and check the class with "AT+CLASS=?".
489 -
490 -[[image:image-20250207173212-27.png]]
491 -
492 -[[image:image-20250207172246-20.png]]
493 -
494 -6.3.3 Verify LA66's join status (in LTS5) with "AT+NJS=?". If not joined, connect manually to LoRaWAN with "AT+JOIN".
495 -
496 -[[image:image-20250207172010-19.png]]
497 -
498 -[[image:image-20250207171650-17.png]]
499 -
500 -6.3.4 After joining, send a message to TTN, such as "AT+SENDB=01,02,8,05820802581ea0a5", to activate communication.
501 -
502 -[[image:image-20250207192107-28.png]]
503 -
504 -6.3.5 TTN distributes panel data in three batches.
505 -
506 -1. downlink DEUI F1A84041000181D4A8
507 -1. downlink Dev Name F24B69746368656E2D467269676531FFFF
508 -1. downlink Sensor Data 5501A4CBBB0A8E085C02 或 5504A4CB01
509 -
510 -= 5. The method for adding a new type of panel to the project =
511 -
512 -If you don't have this need, then this part of the content can be ignored.
513 -
514 -1. Design a panel in SquareLine Studio, as shown in Image 5.1 below for reference.
515 -
516 -[[image:image-20241121113445-1.png||height="584" width="934"]]
517 -
518 - Image 5.1: a panel about water_leak
519 -
520 -
521 -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 5.2.
522 -
523 -[[image:image-20241121141120-4.png||height="383" width="795"]]
524 -
525 - Image 5.2: Exported UI files
526 -
527 -
528 -3. **Delete and rename some file.** Here are the steps:
529 -
530 - Step 1: Delete the 'components' directory.
531 - Step 2: Delete 'filelist.txt'.
532 - Step 3: Delete 'ui_helpers.c' and 'ui_helpers.h'.
533 - Step 4: Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
534 - Step 5: Rename the 'screens' directory to 'styles'.
535 -
536 -[[image:image-20241121151934-10.png||height="303" width="792"]]
537 -
538 - image 5.3 rest file (1)
539 -
540 -[[image:image-20241121142925-7.png||height="141" width="793"]]
541 -
542 - image 5.4 rest file (2)
543 -
544 -4. Open the project in **VS Code**.
545 -
546 -5. Add the file include path for **water_leak** in **extra_lib/CMakeLists.txt**, as shown in Images 5.5 and 5.6. Its format is similar to that of **tem_hum** or **door**."
547 -
548 -[[image:image-20241121181957-17.png||height="438" width="516"]]
549 -
550 - image 5.5 extra_lib/CMakeLists.txt before add
551 -
552 -[[image:image-20241121182239-18.png||height="520" width="518"]]
553 -
554 - image 5.6 extra_lib/CMakeLists.txt after add
555 -
556 -6.  **Modify the header files included in the fonts and images directories**.
557 -
558 -Open the **fonts/ui_font_Font12.c** file, as shown in Image 5.7, and change **#include "../ui.h"** to **#include "../ui_water_leak.h"**. The modified file is shown in Image 5.8. Other font files need to be modified in the same way.
559 -
560 -[[image:image-20241121171629-11.png]]
561 -
562 - image 5.7 before-modified font file
563 -
564 -[[image:image-20241121171901-12.png]]
565 -
566 - image 5.8 modified font file
567 -
568 -Open the **images/ui_img_battery_empty_png.c** file, as shown in Image 5.9, and change **#include "../ui.h"** to **#include "../ui_water_leak.h"**. The modified file is shown in Image 5.10. Other image files need to be modified in the same way.
569 -
570 -[[image:image-20241121172714-13.png]]
571 -
572 - image 5.9 before-modified image file
573 -
574 -[[image:image-20241121172908-14.png]]
575 -
576 - image 5.10 modified image file
577 -
578 -7. Modify the **ui_water_leak/CMakeLists.txt**. Open this file, and modify it as shown in image 5.11 (before) and image 5.12 (after).
579 -
580 -[[image:image-20241121180030-15.png]]
581 -
582 - image 5.11 ui_water_leak/CMakeLists.txt before modification
583 -
584 -[[image:image-20241121180517-16.png]]
585 -
586 - image 5.12 ui_water_leak/CMakeLists.txt after modification
587 -
588 -
589 -8. Modify the **ui_water_leak.h** file. Images 5.13 and 5.14 show the code before modification, while Images 5.15 and 5.16 show the code after modification.
590 -
591 -[[image:image-20241122094200-23.png]]
592 -
593 - image 5.13 ui_water_leak.h (1) before modification
594 -
595 -[[image:image-20241122094320-24.png||height="852" width="554"]]
596 -
597 - image 5.14 ui_water_leak.h (2) before modification
598 -
599 -[[image:image-20241122094600-25.png||height="1078" width="554"]]
600 -
601 - image 5.15 ui_water_leak.h (1) after modification
602 -
603 -[[image:image-20241122094719-26.png||height="941" width="583"]]
604 -
605 - image 5.16 ui_water_leak.h (2) before modification
606 -
607 -9. **Modify ui_water_leak.c file.** The image 5.17, 5.18, 5.19 show the code before modification, and the image 5.20, 5.21, 5.22 show the code after modification.
608 -
609 -_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.
610 -
611 -[[image:image-20241122102929-27.png||height="619" width="426"]]
612 -
613 - image 5.17 ui_water_leak.c (1) before modification
614 -
615 -[[image:image-20241122112838-30.png||height="551" width="628"]]
616 -
617 - image 5.18 ui_water_leak.c (2) before modification
618 -
619 -[[image:image-20241122110815-29.png||height="725" width="712"]]
620 -
621 - image 5.19 ui_water_leak.c (3) before modification
622 -
623 -[[image:image-20241122113158-31.png||height="872" width="677"]]
624 -
625 - image 5.20 ui_water_leak.c (1) after modification
626 -
627 -[[image:image-20241122113259-33.png||height="874" width="724"]]
628 -
629 - image 5.21 ui_water_leak.c (2) after modification
630 -
631 -[[image:image-20241122113359-34.png||height="804" width="746"]]
632 -
633 - image 5.22 ui_water_leak.c (3) after modification
634 -
635 -10. **Modify ui_water_leak_events.h file.** The image 5.23 show the code before modification, and the image 5.24 show the code after modification.
636 -
637 -[[image:image-20241122134113-35.png||height="380" width="421"]]
638 -
639 - image 5.23 ui_water_leak_events_.h before modification
640 -
641 -[[image:image-20241122134420-37.png||height="201" width="283"]]
642 -
643 -image 5.24 ui_water_leak_events_.h after modification
644 -
645 -11.** Modify ui_water_leak_events.c file.** The image 5.25 show the code before modification, and the image 5.26 show the code after modification.
646 -
647 -Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
648 -
649 -Step2. add code  below in delete_object() function definition.
650 -
651 - panel_all * panel = find_upper_by_SensorPanel(&arr,((lv_obj_t *)(e->user_data~)~)~);
652 -
653 - size_t index = panel->panel_obj_index;
654 -
655 - deleteElement(&arr, index);
656 -
657 -[[image:image-20241122135023-38.png||height="358" width="372"]]
658 -
659 - image 5.25 ui_water_leak_events_.c before modification
660 -
661 -[[image:image-20241122135258-39.png||height="403" width="559"]]
662 -
663 - image 5.26 ui_water_leak_events_.c after modification
664 -
665 -
666 -12. **Modify ui_water_leak_style.c file.**
667 -
668 -Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
669 -
670 - add '#include "../../sort.h"'
671 -
672 - add '#include "ui.h"'
673 -
674 -[[image:image-20241122141536-41.png||height="361" width="612"]]
675 -
676 - image 5.27 ui_water_leak_style.c (1) before modification
677 -
678 -[[image:image-20241122142129-42.png||height="386" width="613"]]
679 -
680 - image 5.28 ui_water_leak_style.c (1) after modification
681 -
682 -
683 -Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
684 -
685 - delete code as shown in image 5.29
686 -
687 -[[image:image-20241122145620-44.png||height="757" width="671"]]
688 -
689 - image 5.29 ui_water_leak_style.c (2)
690 -
691 -
692 -Step3. The image 5.30, 5.31 show the change.
693 -
694 -[[image:image-20241122152026-45.png||height="277" width="828"]]
695 -
696 - image 5.30 ui_water_leak_style.c (3) before modification
697 -
698 -[[image:image-20241122152542-46.png||height="293" width="830"]]
699 -
700 - image 5.31 ui_water_leak_style.c (3) after modification
701 -
702 -
703 -Step4. Copy partly the code in ui_water_leak.c, paste at extra_lib/sort.h(The process is shown in image 5.32, 5.33).
704 -
705 -[[image:image-20241122153958-47.png]]
706 -
707 - image 5.32 ui_water_leak_style.c (4)
708 -
709 -
710 -[[image:image-20241122154755-49.png||height="864" width="513"]]
711 -
712 - image 5.33 ui_water_leak_style.c (4)
713 -
714 -
715 -Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
716 -
717 -[[image:image-20241122155650-50.png||height="922" width="513"]]
718 -
719 - image 5.34 ui_water_leak_style.c (5)
720 -
721 -
722 -Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
723 -
724 -[[image:image-20241122161934-51.png]]
725 -
726 - image 5.35
727 -
728 -
729 -Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
730 -
731 -[[image:image-20241122162852-53.png||height="330" width="529"]]
732 -
733 - image 5.37
734 -
735 -
736 -Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
737 -
738 -panel_with_type union_sensor;
739 -
740 -union_sensor.panel_type = WATER_LEAK_TYPE;
741 -
742 -......
743 -
744 -lv_obj_set_x(union_sensor.panel_union.door.ui_PanelSensorDoor, x_by_index(index));
745 -
746 -lv_obj_set_y(union_sensor.panel_union.door.ui_PanelSensorDoor, y_by_index(index));
747 -
748 -return union_sensor;
749 -
750 -[[image:image-20250122173546-6.png||height="777" width="922"]]
751 -
752 - image 5.38
753 -
754 -
755 -13. Rest midification in sort.h file.
756 -
757 -In image 5.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.
758 -
759 -[[image:image-20250122170230-1.png||height="580" width="513"]]
760 -
761 - image 5.39 sort.h
762 -
763 -13. **Modify sort.c file.**
764 -
765 -Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 26.
766 -
767 -[[image:image-20250122171910-5.png||height="524" width="510"]]
768 -
769 - image 5.40 sort.c (1)
770 -
771 -There are still some changes need to be done in sort.c, and omit here for the moment.
772 -
773 -
774 -
775 775  = 6. FAQ =
776 776  
777 777  == 6.1 ==
... ... @@ -781,13 +781,11 @@
781 781  
782 782  == 7.1  Part Number ==
783 783  
784 -
785 785  Part Number: (% style="color:#4472c4" %)LTS5
786 786  
787 787  
788 788  == 7.2  Packing Info ==
789 789  
790 -
791 791  **Package Includes**:
792 792  
793 793  * LTS5 HMI Touch Screen
... ... @@ -796,15 +796,13 @@
796 796  
797 797  = 8. Support =
798 798  
799 -
800 800  * 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.
801 801  * 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]].
802 802  
803 803  = 9.  Reference material =
804 804  
805 -
806 806  * Datasheet
807 -* 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]]
248 +* Source Code
808 808  * Mechinical
809 809  
810 810  = 10. FCC Warning =
1738893226894-758.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -25.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-20240928113424-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -50.8 KB
Content
image-20240928114139-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -114.3 KB
Content
image-20240928144830-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -25.5 KB
Content
image-20241121113445-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -250.0 KB
Content
image-20241121120222-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -44.8 KB
Content
image-20241121120830-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -42.6 KB
Content
image-20241121141120-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -41.7 KB
Content
image-20241121141315-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -29.4 KB
Content
image-20241121141329-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -29.4 KB
Content
image-20241121142925-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -14.8 KB
Content
image-20241121145915-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -61.0 KB
Content
image-20241121150911-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -73.0 KB
Content
image-20241121151934-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -32.9 KB
Content
image-20241121171629-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -16.9 KB
Content
image-20241121171901-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -17.2 KB
Content
image-20241121172714-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -26.4 KB
Content
image-20241121172908-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -27.1 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
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