Last modified by BoYang Xie on 2025/05/05 12:26
<
From version < 123.1 >
edited by Dilisi S
on 2024/12/24 04:36
To version < 172.1 >
edited by BoYang Xie
on 2025/02/08 18:00
>
Change comment: Uploaded new attachment "image-20250208180010-3.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.pradeeka
1 +XWiki.xieby
Content
... ... @@ -1,12 +1,11 @@
1 +
2 +
1 1  (% style="text-align:center" %)
2 -[[image:image-20240915231842-1.png]]
4 +[[image:image-20241226135550-1.png]]
3 3  
4 4  
5 5  
6 6  
7 -
8 -
9 -
10 10  (% _mstvisible="1" %)
11 11  (% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:**
12 12  
... ... @@ -140,9 +140,9 @@
140 140  === 2.2.2 Install SquareLine Studio ===
141 141  
142 142  
143 -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.4.2.
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.
144 144  
145 -[[image:squareline.io_downloads.png]]
144 +[[image:squareline.io_downloads.png||height="888" width="1294"]]
146 146  
147 147  
148 148  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:
... ... @@ -156,137 +156,140 @@
156 156  == 2.3 Simple usage of SquareLine Studio and exporting UI code ==
157 157  
158 158  
159 -After launching and logging into the software, create a new project as shown in Image 2.
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**.
160 160  
161 -* Select the major **LVGL** version as **8.3**.
162 -* Select the **Desktop** tab.
163 -* Select  **Eclipse with  SDL for  development on PC**:
164 -* In the **PROJECT SETTINGS**, select **LVGL version** **8.3.11**
165 -* Select the **CREATE **button.
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.
166 166  
167 -[[image:image-20240928103357-2.png||height="680" width="708"]]
163 +[[image:squareline-studio-launcher-screen.png||height="752" width="1415"]]
168 168  
169 - Image 2: Creating a new SquareLine project
170 170  
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.
171 171  
172 -Next, you need to configure some settings for this project. By clicking in the specified order shown in Image 3, you will be directed to the page displayed in Image 4.
173 -
174 -* Select** File  -> Project Settings**
175 -
176 176  [[image:1727229582471-566.png]]
177 177  
178 - Image 3 accessing project settings
179 179  
171 +In the **PROJECT SETTINGS** dialog box, configure/modify the project settings as shown in the image below.
180 180  
181 -In the PROJECT SETTINGS dialog box, configure/modify the project settings:
182 -
183 183  * **UI Files Export Root**: Select a folder on your computer to store the UI files.
184 184  * **LVGL Include Path**: Set this to **lvgl.h**
185 -* **Click on the APPLY CHANGES button.**
175 +* Click on the **APPLY CHANGES** button.
186 186  
187 187  [[image:image-20240928105309-4.png||height="526" width="556"]]
188 188  
189 - Image 4 Configure/modify project settings
190 190  
180 +Now you can start building the user interface. Follow the steps below:
191 191  
192 -Now you can start building the sample UI. Follow the steps below:
193 193  
183 +=== **Add widgets** ===
194 194  
195 -=== Add widgets ===
196 196  
197 -To add widgets navigate to the **Widgets** area, then click on the widgets you want to add. The selected widgets will be added to the screen. You can reposition the widgets in the screen area by clicking and dragging them.
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.
198 198  
199 -Add a Label, Button, and Image to the screen as shown in **Image 5**.
200 -
201 201  [[image:image-20240928111412-6.png||height="526" width="864"]]
202 202  
203 - Image 5: Add widgets
204 204  
205 -=== Modify widget properties ===
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**.
206 206  
207 -The area for modifying widgets is called the **Inspector** tab. The Inspector tab consists of four sections: **COMPONENT**, **<WIDGET>**, **STYLE SETTINGS**, and **EVENTS**, as shown in Image 6.
193 +[[image:Screenshot 2024-12-24 140459.png||height="278" width="290"]]
208 208  
209 -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.
195 +=== **Modify widget properties** ===
210 210  
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.
199 +
211 211  [[image:1727485118799-984.png]]
212 212  
213 - Image 6: The button widget's "Inspector" tab
214 214  
203 +==== **Changing the Button properties** ====
215 215  
216 -==== Changing the Button properties ====
217 217  
218 -Click the Button.
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:
219 219  
220 -Under the "Layout" you can change the button's position and size.
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
221 221  
222 222  [[image:1727485251053-655.png]]
223 223  
224 -Image 7: The button widget's "BUTTON" tab
225 225  
226 -
227 227  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.
228 228  
229 -* Click **ADD EVENT** button.
230 -* Select **CLICKED** under the Trigger.
231 -* Select **Screen2** from **Screen to**.
232 -* Select **FADE ON** from **Fade mode**.
233 -* Enter **500** in the **Speed** text box.
234 -* Finally, click **ADD** button.
221 +* Click **ADD EVENT** button. A new section will appear to configure this event.
235 235  
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 +
236 236  [[image:1727485480434-713.png||height="395" width="290"]]
237 237  
238 - Image 8: Add an event for the button
234 + Image 8: Add an event for the button
239 239  
240 240  
241 -==== Changing the label properties ====
237 +==== **Changing the label properties** ====
242 242  
243 -Click the label. Under the **Label** section, type "Click For Detail" in the **Text** textbox.
244 244  
240 +Click the Label you have added to the screen. Under the **Label** section, type "**Click for Detail**" in the **Text** textbox.
245 245  
246 246  [[image:image-20240928090825-1.png||height="327" width="391"]]
247 247  
248 - Image 9:  Modify text of label widget
249 249  
245 +Once you enter the text, it will immediately appear on the label.
250 250  
251 -==== 4. Changing image properties ====
252 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. One way is to move your image into the folder "…/squareline project/assets/", as shown in image 10. The other way is to click the "ADD FILE INTO ASSETS" button, then select an image from your computer to import. After adding, you can see the image in the "assets" area in SquareLine Studio, as demonstrated in image 11.
248 +==== **Changing image properties** ====
254 254  
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 255  [[image:image-20240928113424-9.png||height="355" width="505"]]
256 256  
257 - image 10 add image file into SquareLine Studio project
258 258  
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 +
259 259  [[image:image-20240928114139-10.png||height="559" width="810"]]
260 260  
261 - image 11 use image widget in SquareLine Studio
262 262  
263 +==== **The relationship between widgets** ====
263 263  
264 -==== 5. The relationship between widgets ====
265 265  
266 266  Widgets commonly have two types of relationships: **parallel** and **parent-child**.
267 267  
268 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, as shown in Image 13.
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 270  
271 271  [[image:1727486567182-334.png||height="318" width="278"]]
272 272  
273 273  
274 -Move **Label1** to make it a child of **Button1**. See Image 13.
274 +Move the label, **Label1** to make it a child of **Button1** as shown in the image below.
275 275  
276 276  [[image:image-20240928112001-8.png||height="431" width="796"]]
277 277  
278 - Image 13: Move Label1 to make it a child of Button1.
279 279  
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 280  
281 -**6. Preview the screen**
281 +[[image:Screenshot 2024-12-24 144005.png||height="360" width="290"]]
282 282  
283 -You can test the result by clicking on the **PLAY** button. The screen will change into play mode. See Image 14.
284 284  
285 -[[image:1727487368023-281.png]]
284 +==== **Preview the screen** ====
286 286  
287 - Image 14: Simulating the project
288 288  
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.
289 289  
289 +[[image:1727487368023-281.png]]
290 +
291 +
290 290  For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
291 291  
292 292  
... ... @@ -293,57 +293,62 @@
293 293  == 2.4 Integrate UI Code to ESP-IDF Project ==
294 294  
295 295  
296 -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.
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.
297 297  
300 +On the  menubar, click **Export -> Export UI** Files as shown in the image below.
301 +
298 298  [[image:1727229798126-306.png]]
299 299  
300 - image 15 export UI file
301 301  
305 +The exported UI files can be found in your SquareLine project folder as shown in the image below.
306 +
307 +
302 302  [[image:1727229821582-258.png||height="333" width="662"]]
303 303  
304 - image 16 exported UI file
305 305  
306 -Create a empty directory entitled "ui" in path "basic_prj/app_components/ui/", and then copy all UI code exported to this directory.
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.
307 307  
308 308  [[image:image-20240928144830-11.png]]
309 309  
310 - image 17 open CMakeLists.txt
311 311  
316 +Open the **CMakeLists.txt** file and edit it as ahown below.
317 +
312 312  [[image:1727229892636-154.png||height="521" width="407"]]
313 313  
314 - image 18 modify CMakeLists.txt
315 315  
316 -The last step of integrating is adding two lines of code in main.c file.
321 +Open the main.c file and  add two lines of code as shown in the below images.
317 317  
323 +Add **#include "ui.h"**
324 +
318 318  [[image:1727229926561-300.png]]
319 319  
320 - image 19 add "ui.h"
321 321  
328 +Add **ui_init();**
329 +
322 322  [[image:1727229955611-607.png]]
323 323  
324 - image 20 add "ui_init()"
325 325  
333 +== 2.5 Brief introduction to the Hello World project ==
326 326  
327 -== 2.5 Brief introduction of hello world project ==
328 328  
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.
329 329  
330 -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.
331 331  
332 -
333 333  == 2.6 Test Result ==
334 334  
335 335  
336 -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.
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.
337 337  
344 +Screen 1:
345 +
338 338  [[image:1727488067077-684.png||height="402" width="574"]]
339 339  
340 - image 21 screen1
341 341  
349 +Screen 2:
350 +
342 342  [[image:1727488157579-949.png||height="397" width="572"]]
343 343  
344 - image 22 screen2
345 345  
346 -
347 347  = 3. Example Project 1: LoRa Central Display =
348 348  
349 349  [[image:image-20240916101737-1.png||height="468" width="683"]]
... ... @@ -351,135 +351,293 @@
351 351  
352 352  = 4. Example Project 2: LoRaWAN RS485 Alarm =
353 353  
354 -= 5.  The way to add a new panel to project =
361 += 5. Example Project 3: P2P =
355 355  
356 -**~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.**
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.
357 357  
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.
475 +
476 +== 6.2 flowchart ==
477 +
478 +[[image:image-20250207164320-13.png||height="696" width="1344"]]
479 +
480 +== 6.3 Usage ==
481 +
482 +This section now describes a process involving TTN downlink panel data that is to be displayed on the LTS5 screen.
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 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.
505 +
506 +There is an example for TTN downlink.
507 +
508 +1. downlink DEUI F1A84041000181D4A8
509 +1. downlink Dev Name F24B69746368656E2D467269676531FFFF
510 +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.
511 +
512 += 7. The method for adding a new type of panel to the project =
513 +
514 +If you don't have this need, then this part of the content can be ignored.
515 +
516 +1. Design a panel in SquareLine Studio, as shown in Image 7.1 below for reference.
517 +
358 358  [[image:image-20241121113445-1.png||height="584" width="934"]]
359 359  
360 - image 5.1 a panel about water_leak
520 + Image 7.1: a panel about water_leak
361 361  
362 -**2. Export the ui file.** You need  to adjust the export path first, then click "Export->Export UI Files". This step had been introduced before. Then you can get the ui files as shown in image 5.2.
363 363  
523 +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.
524 +
364 364  [[image:image-20241121141120-4.png||height="383" width="795"]]
365 365  
366 - image 5.2 ui files exported
527 + Image 7.2: Exported UI files
367 367  
368 -**3. Delete or rename some file.** Here are the steps:
369 369  
370 - Step1 Delete the 'components' directory.
371 - Step2 Delete 'filelist.txt'.
372 - Step3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
373 - Step4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
374 - Step5 Rename the 'screens' directory to 'styles'.
530 +3. **Delete and rename some file.** Here are the steps:
375 375  
532 + Step 1: Delete the 'components' directory.
533 + Step 2: Delete 'filelist.txt'.
534 + Step 3: Delete 'ui_helpers.c' and 'ui_helpers.h'.
535 + Step 4: Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
536 + Step 5: Rename the 'screens' directory to 'styles'.
537 +
376 376  [[image:image-20241121151934-10.png||height="303" width="792"]]
377 377  
378 - image 5.3 rest file (1)
540 + image 7.3 rest file (1)
379 379  
380 380  [[image:image-20241121142925-7.png||height="141" width="793"]]
381 381  
382 - image 5.4 rest file (2)
544 + image 7.4 rest file (2)
383 383  
384 -**4. Open this project in vscode.**
546 +4. Open the project in VS Code.
385 385  
386 -5. Add file include path about water_leak in extra_lib/CMakeLists.txt as shown in image 5.5, 5.6, and its format is similar to the tem_hum or door.
548 +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**."
387 387  
388 388  [[image:image-20241121181957-17.png||height="438" width="516"]]
389 389  
390 - image 5.5 extra_lib/CMakeLists.txt before add
552 + image 7.5 extra_lib/CMakeLists.txt before adding
391 391  
392 392  [[image:image-20241121182239-18.png||height="520" width="518"]]
393 393  
394 - image 5.6 extra_lib/CMakeLists.txt after add
556 + image 7.6 extra_lib/CMakeLists.txt after adding
395 395  
396 -**6. Modify header file include in fonts and images directory.** Open the fonts/ui_font_Font12.c file, as shown in image 5.7, then modify the '#include "../ui.h"' to '#include "../ui_water_leak.h"', the image 5.8 is the modified image. Other font file need to be modified in same way.
558 +6.  **Modify the header files included in the fonts and images directories**.
397 397  
560 +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.
561 +
398 398  [[image:image-20241121171629-11.png]]
399 399  
400 - image 5.7 before-modified font file
564 + image 7.7 unmodified font file
401 401  
402 402  [[image:image-20241121171901-12.png]]
403 403  
404 - image 5.8 modified font file
568 + image 7.8 modified font file
405 405  
406 -Open the images/ui_img_battery_empty_png.c file, as shown in image 5.9, then modify the '#include "../ui.h"' to '#include "../ui_water_leak.h"', the image 5.10 is the modified image. Other image file need to be modified in same way.
570 +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.
407 407  
408 408  [[image:image-20241121172714-13.png]]
409 409  
410 - image 5.9 before-modified image file
574 + image 7.9 unmodified image file
411 411  
412 412  [[image:image-20241121172908-14.png]]
413 413  
414 - image 5.10 modified image file
578 + image 7.10 modified image file
415 415  
416 -**7. Modify the ui_water_leak/CMakeLists.txt.** Open this file, and modify it from image 5.11 to image 5.12.
580 +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).
417 417  
418 418  [[image:image-20241121180030-15.png]]
419 419  
420 - image 5.11 ui_water_leak/CMakeLists.txt before modification
584 + image 7.11 ui_water_leak/CMakeLists.txt before modification
421 421  
422 422  [[image:image-20241121180517-16.png]]
423 423  
424 - image 5.12 ui_water_leak/CMakeLists.txt after modification
588 + image 7.12 ui_water_leak/CMakeLists.txt after modification
425 425  
426 -**8. Modify ui_water_leak.h file.** The image 5.13, 5.14 show the code before modification, and the image 5.15, 5.16 show the code after modification.
427 427  
591 +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.
592 +
428 428  [[image:image-20241122094200-23.png]]
429 429  
430 - image 5.13 ui_water_leak.h (1) before modification
595 + image 7.13 ui_water_leak.h (1) before modification
431 431  
432 432  [[image:image-20241122094320-24.png||height="852" width="554"]]
433 433  
434 - image 5.14 ui_water_leak.h (2) before modification
599 + image 7.14 ui_water_leak.h (2) before modification
435 435  
436 436  [[image:image-20241122094600-25.png||height="1078" width="554"]]
437 437  
438 - image 5.15 ui_water_leak.h (1) after modification
603 + image 7.15 ui_water_leak.h (1) after modification
439 439  
440 440  [[image:image-20241122094719-26.png||height="941" width="583"]]
441 441  
442 - image 5.16 ui_water_leak.h (2) before modification
607 + image 7.16 ui_water_leak.h (2) before modification
443 443  
444 -**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.
609 +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.
445 445  
446 446  _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.
447 447  
448 448  [[image:image-20241122102929-27.png||height="619" width="426"]]
449 449  
450 - image 5.17 ui_water_leak.c (1) before modification
615 + image 7.17 ui_water_leak.c (1) before modification
451 451  
452 452  [[image:image-20241122112838-30.png||height="551" width="628"]]
453 453  
454 - image 5.18 ui_water_leak.c (2) before modification
619 + image 7.18 ui_water_leak.c (2) before modification
455 455  
456 456  [[image:image-20241122110815-29.png||height="725" width="712"]]
457 457  
458 - image 5.19 ui_water_leak.c (3) before modification
623 + image 7.19 ui_water_leak.c (3) before modification
459 459  
460 460  [[image:image-20241122113158-31.png||height="872" width="677"]]
461 461  
462 - image 5.20 ui_water_leak.c (1) after modification
627 + image 7.20 ui_water_leak.c (1) after modification
463 463  
464 464  [[image:image-20241122113259-33.png||height="874" width="724"]]
465 465  
466 - image 5.21 ui_water_leak.c (2) after modification
631 + image 7.21 ui_water_leak.c (2) after modification
467 467  
468 468  [[image:image-20241122113359-34.png||height="804" width="746"]]
469 469  
470 - image 5.22 ui_water_leak.c (3) after modification
635 + image 7.22 ui_water_leak.c (3) after modification
471 471  
472 -**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.
637 +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.
473 473  
474 474  [[image:image-20241122134113-35.png||height="380" width="421"]]
475 475  
476 - image 5.23 ui_water_leak_events_.h before modification
641 + image 7.23 ui_water_leak_events_.h before modification
477 477  
478 478  [[image:image-20241122134420-37.png||height="201" width="283"]]
479 479  
480 -image 5.24 ui_water_leak_events_.h after modification
645 +image 7.24 ui_water_leak_events_.h after modification
481 481  
482 -**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.
647 +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.
483 483  
484 484  Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
485 485  
... ... @@ -493,14 +493,15 @@
493 493  
494 494  [[image:image-20241122135023-38.png||height="358" width="372"]]
495 495  
496 - image 5.25 ui_water_leak_events_.c before modification
661 + image 7.25 ui_water_leak_events_.c before modification
497 497  
498 498  [[image:image-20241122135258-39.png||height="403" width="559"]]
499 499  
500 - image 5.26 ui_water_leak_events_.c after modification
665 + image 7.26 ui_water_leak_events_.c after modification
501 501  
502 -**12. Modify ui_water_leak_style.c file.**
503 503  
668 +12. **Modify ui_water_leak_style.c file.**
669 +
504 504  Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
505 505  
506 506   add '#include "../../sort.h"'
... ... @@ -509,60 +509,68 @@
509 509  
510 510  [[image:image-20241122141536-41.png||height="361" width="612"]]
511 511  
512 - image 5.27 ui_water_leak_style.c (1) before modification
678 + image 7.27 ui_water_leak_style.c (1) before modification
513 513  
514 514  [[image:image-20241122142129-42.png||height="386" width="613"]]
515 515  
516 - image 5.28 ui_water_leak_style.c (1) after modification
682 + image 7.28 ui_water_leak_style.c (1) after modification
517 517  
684 +
518 518  Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
519 519  
520 - delete code as shown in image 5.29
687 + delete code as shown in image 7.29
521 521  
522 522  [[image:image-20241122145620-44.png||height="757" width="671"]]
523 523  
524 - image 5.29 ui_water_leak_style.c (2)
691 + image 7.29 ui_water_leak_style.c (2)
525 525  
526 -Step3. The image 5.30, 5.31 show the change.
527 527  
694 +Step3. The image 7.30, 7.31 show the change.
695 +
528 528  [[image:image-20241122152026-45.png||height="277" width="828"]]
529 529  
530 - image 5.30 ui_water_leak_style.c (3) before modification
698 + image 7.30 ui_water_leak_style.c (3) before modification
531 531  
532 532  [[image:image-20241122152542-46.png||height="293" width="830"]]
533 533  
534 - image 5.31 ui_water_leak_style.c (3) after modification
702 + image 7.31 ui_water_leak_style.c (3) after modification
535 535  
536 -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).
537 537  
705 +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).
706 +
538 538  [[image:image-20241122153958-47.png]]
539 539  
540 - image 5.32 ui_water_leak_style.c (4)
709 + image 7.32 ui_water_leak_style.c (4)
541 541  
711 +
542 542  [[image:image-20241122154755-49.png||height="864" width="513"]]
543 543  
544 - image 5.33 ui_water_leak_style.c (4)
714 + image 7.33 ui_water_leak_style.c (4)
545 545  
546 -Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
547 547  
717 +Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 7.34).
718 +
548 548  [[image:image-20241122155650-50.png||height="922" width="513"]]
549 549  
550 - image 5.34 ui_water_leak_style.c (5)
721 + image 7.34 ui_water_leak_style.c (5)
551 551  
552 -Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
553 553  
724 +Step6. Add some lines of code in extra_lib/sort.h as shown in image 7.35.
725 +
554 554  [[image:image-20241122161934-51.png]]
555 555  
556 - image 5.35
728 + image 7.35
557 557  
558 -Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
559 559  
731 +Step7. Add a line of code in extra_lib/sort.h as shown in image 7.36.
732 +
560 560  [[image:image-20241122162852-53.png||height="330" width="529"]]
561 561  
562 - image 5.37
735 + image 7.37
563 563  
564 -Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
565 565  
738 +Step8. Add some code in ui_water_leak_style.c as shown in image 7.38 from line534 to line 576 in detail.
739 +
566 566  panel_with_type union_sensor;
567 567  
568 568  union_sensor.panel_type = WATER_LEAK_TYPE;
... ... @@ -575,35 +575,45 @@
575 575  
576 576  return union_sensor;
577 577  
578 -[[image:image-20241122171211-54.png||height="635" width="792"]]
752 +[[image:image-20250122173546-6.png||height="777" width="922"]]
579 579  
580 - image 5.38
754 + image 7.38
581 581  
582 -**13. Modify sort.c file.**
583 583  
584 -Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
757 +13. Rest midification in sort.h file.
585 585  
586 -[[image:image-20241122173718-56.png||height="378" width="579"]]
759 +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.
587 587  
588 - image 5.39 sort.c (1)
761 +[[image:image-20250122170230-1.png||height="580" width="513"]]
589 589  
763 + image 7.39 sort.h
764 +
765 +13. **Modify sort.c file.**
766 +
767 +Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 26.
768 +
769 +[[image:image-20250122171910-5.png||height="524" width="510"]]
770 +
771 + image 7.40 sort.c (1)
772 +
590 590  There are still some changes need to be done in sort.c, and omit here for the moment.
591 591  
592 592  
593 -= 6. FAQ =
594 594  
595 -== 6.1 ==
777 += 8. FAQ =
596 596  
779 +== 8.1 ==
597 597  
598 -= 7. Order Info =
599 599  
600 -== 7.1  Part Number ==
782 += 9. Order Info =
601 601  
784 +== 9.1  Part Number ==
602 602  
786 +
603 603  Part Number: (% style="color:#4472c4" %)LTS5
604 604  
605 605  
606 -== 7.2  Packing Info ==
790 +== 9.2  Packing Info ==
607 607  
608 608  
609 609  **Package Includes**:
... ... @@ -612,20 +612,20 @@
612 612  * 5V,2A DC Power Adapter.
613 613  * USB Type C Program Cable
614 614  
615 -= 8. Support =
799 += 10. Support =
616 616  
617 617  
618 618  * 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.
619 619  * 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]].
620 620  
621 -= 9.  Reference material =
805 += 11.  Reference material =
622 622  
623 623  
624 624  * Datasheet
625 -* Source Code
809 +* 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]]
626 626  * Mechinical
627 627  
628 -= 10. FCC Warning =
812 += 12. FCC Warning =
629 629  
630 630  
631 631  This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
1738893226894-758.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +25.6 KB
Content
LTS5-V1.pdf
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +661.6 KB
Content
Screenshot 2024-12-24 134818.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +15.0 KB
Content
Screenshot 2024-12-24 134937.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +3.6 KB
Content
Screenshot 2024-12-24 140459.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +12.0 KB
Content
Screenshot 2024-12-24 144005.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +28.0 KB
Content
image-20241226135550-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +293.3 KB
Content
image-20250122170230-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +77.3 KB
Content
image-20250122171809-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +51.1 KB
Content
image-20250122171825-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +51.1 KB
Content
image-20250122171832-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +51.1 KB
Content
image-20250122171910-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +51.1 KB
Content
image-20250122173546-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +200.4 KB
Content
image-20250207100150-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +54.1 KB
Content
image-20250207101415-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +17.6 KB
Content
image-20250207101515-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +24.1 KB
Content
image-20250207142334-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +62.0 KB
Content
image-20250207143131-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +48.7 KB
Content
image-20250207144605-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +58.1 KB
Content
image-20250207164320-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +194.5 KB
Content
image-20250207165702-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +78.1 KB
Content
image-20250207170215-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.6 KB
Content
image-20250207170307-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.2 KB
Content
image-20250207171650-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +11.0 KB
Content
image-20250207171851-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.5 KB
Content
image-20250207172010-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.5 KB
Content
image-20250207172246-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.5 KB
Content
image-20250207172443-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207172821-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +0 bytes
Content
image-20250207172834-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +0 bytes
Content
image-20250207173152-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207173159-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207173206-26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207173212-27.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207192107-28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +14.3 KB
Content
image-20250208170737-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +36.9 KB
Content
image-20250208170758-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +36.9 KB
Content
image-20250208175819-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +36.3 KB
Content
image-20250208175918-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +37.8 KB
Content
image-20250208180010-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +36.7 KB
Content
squareline-studio-launcher-screen.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +203.4 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0