Skip to Content
Last modified by BoYang Xie on 2025/07/09 11:46
From version 132.1
edited by Dilisi S
on 2024/12/25 01:39
Change comment: Dec 24 edits - part 3
To version 164.2
edited by BoYang Xie
on 2025/02/07 19:53
Change comment: There is no comment for this version

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  
... ... @@ -142,7 +142,7 @@
142 142  
143 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.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:
... ... @@ -161,10 +161,9 @@
161 161  * In the **PROJECT SETTINGS**, select **LVGL version **as **8.3.11** and **Resolution** as **800** x **480**.
162 162  * Select the **CREATE **button to create the new project with the selected settings.
163 163  
164 -[[image:squareline-studio-launcher-screen.png]]
163 +[[image:squareline-studio-launcher-screen.png||height="752" width="1415"]]
165 165  
166 166  
167 -
168 168  Next, you need to configure some additional settings for this project. To do so, select** File  -> Project Settings** as shown in the image below.
169 169  
170 170  [[image:1727229582471-566.png]]
... ... @@ -299,56 +299,60 @@
299 299  
300 300  To integrate, first export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
301 301  
300 +On the  menubar, click **Export -> Export UI** Files as shown in the image below.
301 +
302 302  [[image:1727229798126-306.png]]
303 303  
304 - image 15 export UI file
305 305  
305 +The exported UI files can be found in your SquareLine project folder as shown in the image below.
306 +
307 +
306 306  [[image:1727229821582-258.png||height="333" width="662"]]
307 307  
308 - image 16 exported UI file
309 309  
310 -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.
311 311  
312 312  [[image:image-20240928144830-11.png]]
313 313  
314 - image 17 open CMakeLists.txt
315 315  
316 +Open the **CMakeLists.txt** file and edit it as ahown below.
317 +
316 316  [[image:1727229892636-154.png||height="521" width="407"]]
317 317  
318 - image 18 modify CMakeLists.txt
319 319  
321 +Open the main.c file and  add two lines of code as shown in the below images.
320 320  
321 -The last step of integrating is adding two lines of code in main.c file.
323 +Add **#include "ui.h"**
322 322  
323 323  [[image:1727229926561-300.png]]
324 324  
325 - image 19 add "ui.h"
326 326  
328 +Add **ui_init();**
329 +
327 327  [[image:1727229955611-607.png]]
328 328  
329 - image 20 add "ui_init()"
330 330  
333 +== 2.5 Brief introduction to the Hello World project ==
331 331  
332 -== 2.5 Brief introduction of hello world project ==
333 333  
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.
334 334  
335 -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.
336 336  
337 -
338 338  == 2.6 Test Result ==
339 339  
340 340  
341 -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.
342 342  
344 +Screen 1:
345 +
343 343  [[image:1727488067077-684.png||height="402" width="574"]]
344 344  
345 - image 21 screen1
346 346  
349 +Screen 2:
350 +
347 347  [[image:1727488157579-949.png||height="397" width="572"]]
348 348  
349 - image 22 screen2
350 350  
351 -
352 352  = 3. Example Project 1: LoRa Central Display =
353 353  
354 354  [[image:image-20240916101737-1.png||height="468" width="683"]]
... ... @@ -356,30 +356,180 @@
356 356  
357 357  = 4. Example Project 2: LoRaWAN RS485 Alarm =
358 358  
359 -= 5. The way to add a new panel to project =
361 += 5. Example Project 3: P2P =
360 360  
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.
361 361  
362 -**~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.**
365 +The project can be found at [[this link>>url:https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/P2P]].
363 363  
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 +
364 364  [[image:image-20241121113445-1.png||height="584" width="934"]]
365 365  
366 - image 5.1 a panel about water_leak
518 + Image 5.1: a panel about water_leak
367 367  
368 368  
369 -**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.
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.
370 370  
371 371  [[image:image-20241121141120-4.png||height="383" width="795"]]
372 372  
373 - image 5.2 ui files exported
525 + Image 5.2: Exported UI files
374 374  
375 375  
376 -**3. Delete or rename some file.** Here are the steps:
528 +3. **Delete and rename some file.** Here are the steps:
377 377  
378 - Step1 Delete the 'components' directory.
379 - Step2 Delete 'filelist.txt'.
380 - Step3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
381 - Step4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
382 - Step5 Rename the 'screens' directory to 'styles'.
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'.
383 383  
384 384  [[image:image-20241121151934-10.png||height="303" width="792"]]
385 385  
... ... @@ -389,9 +389,9 @@
389 389  
390 390   image 5.4 rest file (2)
391 391  
392 -**4. Open this project in vscode.**
544 +4. Open the project in **VS Code**.
393 393  
394 -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.
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**."
395 395  
396 396  [[image:image-20241121181957-17.png||height="438" width="516"]]
397 397  
... ... @@ -401,8 +401,10 @@
401 401  
402 402   image 5.6 extra_lib/CMakeLists.txt after add
403 403  
404 -**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.
556 +6.  **Modify the header files included in the fonts and images directories**.
405 405  
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 +
406 406  [[image:image-20241121171629-11.png]]
407 407  
408 408   image 5.7 before-modified font file
... ... @@ -411,7 +411,7 @@
411 411  
412 412   image 5.8 modified font file
413 413  
414 -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.
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.
415 415  
416 416  [[image:image-20241121172714-13.png]]
417 417  
... ... @@ -421,7 +421,7 @@
421 421  
422 422   image 5.10 modified image file
423 423  
424 -**7. Modify the ui_water_leak/CMakeLists.txt.** Open this file, and modify it from image 5.11 to image 5.12.
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).
425 425  
426 426  [[image:image-20241121180030-15.png]]
427 427  
... ... @@ -431,8 +431,9 @@
431 431  
432 432   image 5.12 ui_water_leak/CMakeLists.txt after modification
433 433  
434 -**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.
435 435  
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 +
436 436  [[image:image-20241122094200-23.png]]
437 437  
438 438   image 5.13 ui_water_leak.h (1) before modification
... ... @@ -449,7 +449,7 @@
449 449  
450 450   image 5.16 ui_water_leak.h (2) before modification
451 451  
452 -**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.
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.
453 453  
454 454  _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.
455 455  
... ... @@ -477,7 +477,7 @@
477 477  
478 478   image 5.22 ui_water_leak.c (3) after modification
479 479  
480 -**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.
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.
481 481  
482 482  [[image:image-20241122134113-35.png||height="380" width="421"]]
483 483  
... ... @@ -487,7 +487,7 @@
487 487  
488 488  image 5.24 ui_water_leak_events_.h after modification
489 489  
490 -**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.
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.
491 491  
492 492  Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
493 493  
... ... @@ -508,7 +508,7 @@
508 508   image 5.26 ui_water_leak_events_.c after modification
509 509  
510 510  
511 -**12. Modify ui_water_leak_style.c file.**
666 +12. **Modify ui_water_leak_style.c file.**
512 512  
513 513  Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
514 514  
... ... @@ -551,6 +551,7 @@
551 551  
552 552   image 5.32 ui_water_leak_style.c (4)
553 553  
709 +
554 554  [[image:image-20241122154755-49.png||height="864" width="513"]]
555 555  
556 556   image 5.33 ui_water_leak_style.c (4)
... ... @@ -591,22 +591,31 @@
591 591  
592 592  return union_sensor;
593 593  
594 -[[image:image-20241122171211-54.png||height="635" width="792"]]
750 +[[image:image-20250122173546-6.png||height="777" width="922"]]
595 595  
596 596   image 5.38
597 597  
598 598  
599 -**13. Modify sort.c file.**
755 +13. Rest midification in sort.h file.
600 600  
601 -Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
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.
602 602  
603 -[[image:image-20241122173718-56.png||height="378" width="579"]]
759 +[[image:image-20250122170230-1.png||height="580" width="513"]]
604 604  
605 - image 5.39 sort.c (1)
761 + image 5.39 sort.h
606 606  
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 +
607 607  There are still some changes need to be done in sort.c, and omit here for the moment.
608 608  
609 609  
774 +
610 610  = 6. FAQ =
611 611  
612 612  == 6.1 ==
... ... @@ -639,7 +639,7 @@
639 639  
640 640  
641 641  * Datasheet
642 -* Source Code
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]]
643 643  * Mechinical
644 644  
645 645  = 10. FCC Warning =
1738893226894-758.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +25.6 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