Last modified by BoYang Xie on 2025/07/09 11:46

From version 179.1
edited by Dilisi S
on 2025/02/18 01:20
Change comment: Feb 17 edits
To version 130.1
edited by Dilisi S
on 2024/12/24 21:40
Change comment: Uploaded new attachment "Screenshot 2024-12-24 144005.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,11 +3,12 @@
1 -
2 -
3 3  (% style="text-align:center" %)
4 -[[image:image-20241226135550-1.png]]
2 +[[image:image-20240915231842-1.png]]
5 5  
6 6  
7 7  
8 8  
7 +
8 +
9 +
9 9  (% _mstvisible="1" %)
10 10  (% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:**
11 11  
... ... @@ -141,7 +141,7 @@
141 141  
142 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.
143 143  
144 -[[image:squareline.io_downloads.png||height="888" width="1294"]]
145 +[[image:squareline.io_downloads.png]]
145 145  
146 146  
147 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:
... ... @@ -155,80 +155,81 @@
155 155  == 2.3 Simple usage of SquareLine Studio and exporting UI code ==
156 156  
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 +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.
159 159  
161 +* Select major **LVGL** version: **8.3**.
162 +* Select the **Desktop** tab.
163 +* Select  **Eclipse with  SDL for  development on PC**:
160 160  * In the **PROJECT SETTINGS**, select **LVGL version **as **8.3.11** and **Resolution** as **800** x **480**.
161 161  * Select the **CREATE **button to create the new project with the selected settings.
162 162  
163 -[[image:squareline-studio-launcher-screen.png||height="752" width="1415"]]
167 +[[image:image-20240928103357-2.png||height="680" width="708"]]
164 164  
165 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.
170 +Next, you need to configure some additional settings for this project. Select** File  -> Project Settings** as shown in the image below.
167 167  
168 168  [[image:1727229582471-566.png]]
169 169  
170 170  
171 -In the **PROJECT SETTINGS** dialog box, configure/modify the project settings as shown in the image below.
175 +In the PROJECT SETTINGS dialog box, configure/modify the project settings:
172 172  
173 -* **UI Files Export Path**: Select a **folder** on your computer to store the **UI files**.
177 +* **UI Files Export Root**: Select a folder on your computer to store the UI files.
174 174  * **LVGL Include Path**: Set this to **lvgl.h**
175 -* Click on the **APPLY CHANGES** button.
179 +* **Click on the APPLY CHANGES button.**
176 176  
177 177  [[image:image-20240928105309-4.png||height="526" width="556"]]
178 178  
183 + Image 4 Configure/modify project settings
179 179  
180 -Now you can start building the user interface. Follow the steps below:
181 181  
186 +Now you can start building the sample UI. Follow the steps below:
182 182  
188 +
183 183  === **Add widgets** ===
184 184  
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.
192 +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.
187 187  
194 +Add a Label, Button, and Image to the screen as shown in **Image 5**.
195 +
188 188  [[image:image-20240928111412-6.png||height="526" width="864"]]
189 189  
198 + Image 5: Add widgets
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**.
192 192  
193 -[[image:Screenshot 2024-12-24 140459.png||height="278" width="290"]]
194 -
195 195  === **Modify widget properties** ===
196 196  
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.
204 +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.
199 199  
206 +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.
207 +
200 200  [[image:1727485118799-984.png]]
201 201  
210 + Image 6: The button widget's "Inspector" tab
202 202  
212 +
203 203  ==== **Changing the Button properties** ====
204 204  
205 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:
216 +Click the Button.
207 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
218 +Under the "Layout" you can change the button's position and size.
215 215  
216 216  [[image:1727485251053-655.png]]
217 217  
222 +Image 7: The button widget's "BUTTON" tab
218 218  
224 +
219 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 220  
221 -* Click **ADD EVENT** button. A new section will appear to configure this event.
227 +* Click **ADD EVENT** button.
228 +* Select **CLICKED** under the Trigger.
229 +* Select **Screen2** from **Screen to**.
230 +* Select **FADE ON** from **Fade mode**.
231 +* Enter **500** in the **Speed** text box.
232 +* Finally, click **ADD** button.
222 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 232  [[image:1727485480434-713.png||height="395" width="290"]]
233 233  
234 234   Image 8: Add an event for the button
... ... @@ -237,29 +237,27 @@
237 237  ==== **Changing the label properties** ====
238 238  
239 239  
240 -Click the Label you have added to the screen. Under the **Label** section, type "**Click for Detail**" in the **Text** textbox.
242 +Click the label. Under the **Label** section, type "Click For Detail" in the **Text** textbox.
241 241  
242 242  [[image:image-20240928090825-1.png||height="327" width="391"]]
243 243  
246 + Image 9:  Modify text of label widget
244 244  
245 -Once you enter the text, it will immediately appear on the label.
246 246  
247 -
248 248  ==== **Changing image properties** ====
249 249  
250 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 +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.
252 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  
256 + image 10 add image file into SquareLine Studio project
257 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 260  [[image:image-20240928114139-10.png||height="559" width="810"]]
261 261  
260 + image 11 use image widget in SquareLine Studio
262 262  
262 +
263 263  ==== **The relationship between widgets** ====
264 264  
265 265  
... ... @@ -266,29 +266,28 @@
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.
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.
270 270  
271 271  [[image:1727486567182-334.png||height="318" width="278"]]
272 272  
273 273  
274 -Move the label, **Label1** to make it a child of **Button1** as shown in the image below.
274 +Move **Label1** to make it a child of **Button1**. See Image 13.
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.
278 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 280  
281 -[[image:Screenshot 2024-12-24 144005.png||height="360" width="290"]]
282 -
283 -
284 284  ==== **Preview the screen** ====
285 285  
286 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.
284 +You can test the result by clicking on the **PLAY** button. The screen will change into play mode. See Image 14.
288 288  
289 289  [[image:1727487368023-281.png]]
290 290  
288 + Image 14: Simulating the project
291 291  
290 +
292 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 293  
294 294  
... ... @@ -295,62 +295,57 @@
295 295  == 2.4 Integrate UI Code to ESP-IDF Project ==
296 296  
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.
297 +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.
299 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  
301 + image 15 export UI file
304 304  
305 -The exported UI files can be found in your SquareLine project folder as shown in the image below.
306 -
307 -
308 308  [[image:1727229821582-258.png||height="333" width="662"]]
309 309  
305 + image 16 exported UI file
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.
307 +Create a empty directory entitled "ui" in path "basic_prj/app_components/ui/", and then copy all UI code exported to this directory.
312 312  
313 313  [[image:image-20240928144830-11.png]]
314 314  
311 + image 17 open CMakeLists.txt
315 315  
316 -Open the **CMakeLists.txt** file and edit it as ahown below.
317 -
318 318  [[image:1727229892636-154.png||height="521" width="407"]]
319 319  
315 + image 18 modify CMakeLists.txt
320 320  
321 -Open the main.c file and  add two lines of code as shown in the below images.
317 +The last step of integrating is adding two lines of code in main.c file.
322 322  
323 -Add **#include "ui.h"**
324 -
325 325  [[image:1727229926561-300.png]]
326 326  
321 + image 19 add "ui.h"
327 327  
328 -Add **ui_init();**
329 -
330 330  [[image:1727229955611-607.png]]
331 331  
325 + image 20 add "ui_init()"
332 332  
333 -== 2.5 Brief introduction to the Hello World project ==
334 334  
328 +== 2.5 Brief introduction of hello world project ==
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.
337 337  
331 +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.
338 338  
333 +
339 339  == 2.6 Test Result ==
340 340  
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.
337 +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.
343 343  
344 -Screen 1:
345 -
346 346  [[image:1727488067077-684.png||height="402" width="574"]]
347 347  
341 + image 21 screen1
348 348  
349 -Screen 2:
350 -
351 351  [[image:1727488157579-949.png||height="397" width="572"]]
352 352  
345 + image 22 screen2
353 353  
347 +
354 354  = 3. Example Project 1: LoRa Central Display =
355 355  
356 356  [[image:image-20240916101737-1.png||height="468" width="683"]]
... ... @@ -358,315 +358,138 @@
358 358  
359 359  = 4. Example Project 2: LoRaWAN RS485 Alarm =
360 360  
361 -= 5. Example Project 3: P2P =
355 += 5. The way to add a new panel to project =
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 364  
365 -The project can be found at [[this link>>url:https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/P2P]].
358 +**~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.**
366 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 LTS5 panel 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 -**LTS5 panel 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 -LTS5 receives this message and displays it on its screen as the image below shows.
462 -
463 -[[image:image-20250208181700-8.jpeg||height="528" width="704"]]
464 -
465 -= 6. Example Project 4: LoRaWAN_CLASS_C =
466 -
467 -
468 -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.
469 -
470 -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.
471 -
472 -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).
473 -
474 -The project can be found at [[this link>>https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/LoRaWAN_CLASS_C]].
475 -
476 -== 6.1 firmware flashing approach ==
477 -
478 -The firmware flashing approach is the same as described in section 5.1.
479 -
480 -== 6.2 flowchart ==
481 -
482 -[[image:image-20250207164320-13.png||height="696" width="1344"]]
483 -
484 -== 6.3 Usage ==
485 -
486 -This section now describes a process involving TTN downlink panel data that is to be displayed on the LTS5 screen.
487 -
488 -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.
489 -
490 -[[image:image-20250207165702-14.png||height="830" width="563"]]
491 -
492 -6.3.2 Switch to Class C using "AT+CLASS=C", and check the class with "AT+CLASS=?".
493 -
494 -[[image:image-20250207173212-27.png]]
495 -
496 -[[image:image-20250207172246-20.png]]
497 -
498 -6.3.3 Verify LA66's join status (in LTS5) with "AT+NJS=?". If not joined, connect manually to LoRaWAN with "AT+JOIN".
499 -
500 -[[image:image-20250207172010-19.png]]
501 -
502 -[[image:image-20250207171650-17.png]]
503 -
504 -6.3.4 After joining, send a message to TTN, such as "AT+SENDB=01,02,8,05820802581ea0a5", to activate communication.
505 -
506 -[[image:image-20250207192107-28.png]]
507 -
508 -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.
509 -
510 -There is an example for TTN downlink.
511 -
512 -1. downlink DEUI F1A84041000181D4A8
513 -1. downlink Dev Name F24B69746368656E2D467269676531FFFF
514 -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.
515 -
516 -[[image:image-20250208175819-1.png||height="503" width="502"]]
517 -
518 -
519 -[[image:image-20250208175918-2.png||height="505" width="502"]]
520 -
521 -
522 -[[image:image-20250208180010-3.png||height="507" width="503"]]
523 -
524 -
525 -[[image:image-20250208181019-4.jpeg||height="592" width="790"]]
526 -
527 -
528 -[[image:image-20250208181328-7.png||height="505" width="504"]]
529 -
530 -
531 -[[image:image-20250208181139-5.jpeg||height="594" width="792"]]
532 -
533 -
534 -= 7. The method for adding a new type of panel to the project =
535 -
536 -If you don't have this need, then this part of the content can be ignored.
537 -
538 -1. Design a panel in SquareLine Studio, as shown in Image 7.1 below for reference.
539 -
540 540  [[image:image-20241121113445-1.png||height="584" width="934"]]
541 541  
542 - Image 7.1: a panel about water_leak
362 + image 5.1 a panel about water_leak
543 543  
544 544  
545 -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.
365 +**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.
546 546  
547 547  [[image:image-20241121141120-4.png||height="383" width="795"]]
548 548  
549 - Image 7.2: Exported UI files
369 + image 5.2 ui files exported
550 550  
551 551  
552 -3. **Delete and rename some file.** Here are the steps:
372 +**3. Delete or rename some file.** Here are the steps:
553 553  
554 - Step 1: Delete the 'components' directory.
555 - Step 2: Delete 'filelist.txt'.
556 - Step 3: Delete 'ui_helpers.c' and 'ui_helpers.h'.
557 - Step 4: Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
558 - Step 5: Rename the 'screens' directory to 'styles'.
374 + Step1 Delete the 'components' directory.
375 + Step2 Delete 'filelist.txt'.
376 + Step3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
377 + Step4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
378 + Step5 Rename the 'screens' directory to 'styles'.
559 559  
560 560  [[image:image-20241121151934-10.png||height="303" width="792"]]
561 561  
562 - image 7.3 rest file (1)
382 + image 5.3 rest file (1)
563 563  
564 564  [[image:image-20241121142925-7.png||height="141" width="793"]]
565 565  
566 - image 7.4 rest file (2)
386 + image 5.4 rest file (2)
567 567  
568 -4. Open the project in VS Code.
388 +**4. Open this project in vscode.**
569 569  
570 -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**."
390 +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.
571 571  
572 572  [[image:image-20241121181957-17.png||height="438" width="516"]]
573 573  
574 - image 7.5 extra_lib/CMakeLists.txt before adding
394 + image 5.5 extra_lib/CMakeLists.txt before add
575 575  
576 576  [[image:image-20241121182239-18.png||height="520" width="518"]]
577 577  
578 - image 7.6 extra_lib/CMakeLists.txt after adding
398 + image 5.6 extra_lib/CMakeLists.txt after add
579 579  
580 -6.  **Modify the header files included in the fonts and images directories**.
400 +**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.
581 581  
582 -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.
583 -
584 584  [[image:image-20241121171629-11.png]]
585 585  
586 - image 7.7 unmodified font file
404 + image 5.7 before-modified font file
587 587  
588 588  [[image:image-20241121171901-12.png]]
589 589  
590 - image 7.8 modified font file
408 + image 5.8 modified font file
591 591  
592 -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.
410 +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.
593 593  
594 594  [[image:image-20241121172714-13.png]]
595 595  
596 - image 7.9 unmodified image file
414 + image 5.9 before-modified image file
597 597  
598 598  [[image:image-20241121172908-14.png]]
599 599  
600 - image 7.10 modified image file
418 + image 5.10 modified image file
601 601  
602 -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).
420 +**7. Modify the ui_water_leak/CMakeLists.txt.** Open this file, and modify it from image 5.11 to image 5.12.
603 603  
604 604  [[image:image-20241121180030-15.png]]
605 605  
606 - image 7.11 ui_water_leak/CMakeLists.txt before modification
424 + image 5.11 ui_water_leak/CMakeLists.txt before modification
607 607  
608 608  [[image:image-20241121180517-16.png]]
609 609  
610 - image 7.12 ui_water_leak/CMakeLists.txt after modification
428 + image 5.12 ui_water_leak/CMakeLists.txt after modification
611 611  
430 +**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.
612 612  
613 -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.
614 -
615 615  [[image:image-20241122094200-23.png]]
616 616  
617 - image 7.13 ui_water_leak.h (1) before modification
434 + image 5.13 ui_water_leak.h (1) before modification
618 618  
619 619  [[image:image-20241122094320-24.png||height="852" width="554"]]
620 620  
621 - image 7.14 ui_water_leak.h (2) before modification
438 + image 5.14 ui_water_leak.h (2) before modification
622 622  
623 623  [[image:image-20241122094600-25.png||height="1078" width="554"]]
624 624  
625 - image 7.15 ui_water_leak.h (1) after modification
442 + image 5.15 ui_water_leak.h (1) after modification
626 626  
627 627  [[image:image-20241122094719-26.png||height="941" width="583"]]
628 628  
629 - image 7.16 ui_water_leak.h (2) before modification
446 + image 5.16 ui_water_leak.h (2) before modification
630 630  
631 -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.
448 +**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.
632 632  
633 633  _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.
634 634  
635 635  [[image:image-20241122102929-27.png||height="619" width="426"]]
636 636  
637 - image 7.17 ui_water_leak.c (1) before modification
454 + image 5.17 ui_water_leak.c (1) before modification
638 638  
639 639  [[image:image-20241122112838-30.png||height="551" width="628"]]
640 640  
641 - image 7.18 ui_water_leak.c (2) before modification
458 + image 5.18 ui_water_leak.c (2) before modification
642 642  
643 643  [[image:image-20241122110815-29.png||height="725" width="712"]]
644 644  
645 - image 7.19 ui_water_leak.c (3) before modification
462 + image 5.19 ui_water_leak.c (3) before modification
646 646  
647 647  [[image:image-20241122113158-31.png||height="872" width="677"]]
648 648  
649 - image 7.20 ui_water_leak.c (1) after modification
466 + image 5.20 ui_water_leak.c (1) after modification
650 650  
651 651  [[image:image-20241122113259-33.png||height="874" width="724"]]
652 652  
653 - image 7.21 ui_water_leak.c (2) after modification
470 + image 5.21 ui_water_leak.c (2) after modification
654 654  
655 655  [[image:image-20241122113359-34.png||height="804" width="746"]]
656 656  
657 - image 7.22 ui_water_leak.c (3) after modification
474 + image 5.22 ui_water_leak.c (3) after modification
658 658  
659 -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.
476 +**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.
660 660  
661 661  [[image:image-20241122134113-35.png||height="380" width="421"]]
662 662  
663 - image 7.23 ui_water_leak_events_.h before modification
480 + image 5.23 ui_water_leak_events_.h before modification
664 664  
665 665  [[image:image-20241122134420-37.png||height="201" width="283"]]
666 666  
667 -image 7.24 ui_water_leak_events_.h after modification
484 +image 5.24 ui_water_leak_events_.h after modification
668 668  
669 -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.
486 +**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.
670 670  
671 671  Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
672 672  
... ... @@ -680,14 +680,14 @@
680 680  
681 681  [[image:image-20241122135023-38.png||height="358" width="372"]]
682 682  
683 - image 7.25 ui_water_leak_events_.c before modification
500 + image 5.25 ui_water_leak_events_.c before modification
684 684  
685 685  [[image:image-20241122135258-39.png||height="403" width="559"]]
686 686  
687 - image 7.26 ui_water_leak_events_.c after modification
504 + image 5.26 ui_water_leak_events_.c after modification
688 688  
689 689  
690 -12. **Modify ui_water_leak_style.c file.**
507 +**12. Modify ui_water_leak_style.c file.**
691 691  
692 692  Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
693 693  
... ... @@ -697,67 +697,66 @@
697 697  
698 698  [[image:image-20241122141536-41.png||height="361" width="612"]]
699 699  
700 - image 7.27 ui_water_leak_style.c (1) before modification
517 + image 5.27 ui_water_leak_style.c (1) before modification
701 701  
702 702  [[image:image-20241122142129-42.png||height="386" width="613"]]
703 703  
704 - image 7.28 ui_water_leak_style.c (1) after modification
521 + image 5.28 ui_water_leak_style.c (1) after modification
705 705  
706 706  
707 707  Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
708 708  
709 - delete code as shown in image 7.29
526 + delete code as shown in image 5.29
710 710  
711 711  [[image:image-20241122145620-44.png||height="757" width="671"]]
712 712  
713 - image 7.29 ui_water_leak_style.c (2)
530 + image 5.29 ui_water_leak_style.c (2)
714 714  
715 715  
716 -Step3. The image 7.30, 7.31 show the change.
533 +Step3. The image 5.30, 5.31 show the change.
717 717  
718 718  [[image:image-20241122152026-45.png||height="277" width="828"]]
719 719  
720 - image 7.30 ui_water_leak_style.c (3) before modification
537 + image 5.30 ui_water_leak_style.c (3) before modification
721 721  
722 722  [[image:image-20241122152542-46.png||height="293" width="830"]]
723 723  
724 - image 7.31 ui_water_leak_style.c (3) after modification
541 + image 5.31 ui_water_leak_style.c (3) after modification
725 725  
726 726  
727 -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).
544 +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).
728 728  
729 729  [[image:image-20241122153958-47.png]]
730 730  
731 - image 7.32 ui_water_leak_style.c (4)
548 + image 5.32 ui_water_leak_style.c (4)
732 732  
733 -
734 734  [[image:image-20241122154755-49.png||height="864" width="513"]]
735 735  
736 - image 7.33 ui_water_leak_style.c (4)
552 + image 5.33 ui_water_leak_style.c (4)
737 737  
738 738  
739 -Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 7.34).
555 +Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
740 740  
741 741  [[image:image-20241122155650-50.png||height="922" width="513"]]
742 742  
743 - image 7.34 ui_water_leak_style.c (5)
559 + image 5.34 ui_water_leak_style.c (5)
744 744  
745 745  
746 -Step6. Add some lines of code in extra_lib/sort.h as shown in image 7.35.
562 +Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
747 747  
748 748  [[image:image-20241122161934-51.png]]
749 749  
750 - image 7.35
566 + image 5.35
751 751  
752 752  
753 -Step7. Add a line of code in extra_lib/sort.h as shown in image 7.36.
569 +Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
754 754  
755 755  [[image:image-20241122162852-53.png||height="330" width="529"]]
756 756  
757 - image 7.37
573 + image 5.37
758 758  
759 759  
760 -Step8. Add some code in ui_water_leak_style.c as shown in image 7.38 from line534 to line 576 in detail.
576 +Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
761 761  
762 762  panel_with_type union_sensor;
763 763  
... ... @@ -771,45 +771,36 @@
771 771  
772 772  return union_sensor;
773 773  
774 -[[image:image-20250122173546-6.png||height="777" width="922"]]
590 +[[image:image-20241122171211-54.png||height="635" width="792"]]
775 775  
776 - image 7.38
592 + image 5.38
777 777  
778 778  
779 -13. Rest midification in sort.h file.
595 +**13. Modify sort.c file.**
780 780  
781 -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.
597 +Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
782 782  
783 -[[image:image-20250122170230-1.png||height="580" width="513"]]
599 +[[image:image-20241122173718-56.png||height="378" width="579"]]
784 784  
785 - image 7.39 sort.h
601 + image 5.39 sort.c (1)
786 786  
787 -13. **Modify sort.c file.**
788 -
789 -Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 26.
790 -
791 -[[image:image-20250122171910-5.png||height="524" width="510"]]
792 -
793 - image 7.40 sort.c (1)
794 -
795 795  There are still some changes need to be done in sort.c, and omit here for the moment.
796 796  
797 797  
606 += 6. FAQ =
798 798  
799 -= 8. FAQ =
608 +== 6.1 ==
800 800  
801 -== 8.1 ==
802 802  
611 += 7. Order Info =
803 803  
804 -= 9. Order Info =
613 +== 7. Part Number ==
805 805  
806 -== 9.1  Part Number ==
807 807  
808 -
809 809  Part Number: (% style="color:#4472c4" %)LTS5
810 810  
811 811  
812 -== 9.2  Packing Info ==
619 +== 7.2  Packing Info ==
813 813  
814 814  
815 815  **Package Includes**:
... ... @@ -818,21 +818,20 @@
818 818  * 5V,2A DC Power Adapter.
819 819  * USB Type C Program Cable
820 820  
821 -= 10. Support =
628 += 8. Support =
822 822  
823 823  
824 824  * 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.
825 825  * 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]].
826 826  
827 -= 11.  Reference material =
634 += 9.  Reference material =
828 828  
829 829  
830 830  * Datasheet
831 -* schematic: [[LTS5-V1>>attach:LTS5-V1.pdf]]
832 -* 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]]
638 +* Source Code
833 833  * Mechinical
834 834  
835 -= 12. FCC Warning =
641 += 10. FCC Warning =
836 836  
837 837  
838 838  This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
1738893226894-758.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -25.6 KB
Content
LTS5-V1.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -661.6 KB
Content
image-20241226135550-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -293.3 KB
Content
image-20250122170230-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -77.3 KB
Content
image-20250122171809-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20250122171825-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20250122171832-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20250122171910-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20250122173546-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -200.4 KB
Content
image-20250207100150-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -54.1 KB
Content
image-20250207101415-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -17.6 KB
Content
image-20250207101515-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -24.1 KB
Content
image-20250207142334-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -62.0 KB
Content
image-20250207143131-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -48.7 KB
Content
image-20250207144605-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -58.1 KB
Content
image-20250207164320-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -194.5 KB
Content
image-20250207165702-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -78.1 KB
Content
image-20250207170215-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.6 KB
Content
image-20250207170307-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.2 KB
Content
image-20250207171650-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -11.0 KB
Content
image-20250207171851-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.5 KB
Content
image-20250207172010-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.5 KB
Content
image-20250207172246-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.5 KB
Content
image-20250207172443-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207172821-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -0 bytes
Content
image-20250207172834-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -0 bytes
Content
image-20250207173152-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207173159-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207173206-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207173212-27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207192107-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -14.3 KB
Content
image-20250208170737-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -36.9 KB
Content
image-20250208170758-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -36.9 KB
Content
image-20250208175819-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -36.3 KB
Content
image-20250208175918-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -37.8 KB
Content
image-20250208180010-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -36.7 KB
Content
image-20250208181019-4.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -546.8 KB
Content
image-20250208181139-5.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -320.5 KB
Content
image-20250208181317-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -34.8 KB
Content
image-20250208181328-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -34.8 KB
Content
image-20250208181700-8.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -526.4 KB
Content