Skip to Content
Last modified by BoYang Xie on 2025/07/24 16:47
From version 195.13
edited by BoYang Xie
on 2025/07/24 16:47
Change comment: There is no comment for this version
To version 129.1
edited by Dilisi S
on 2024/12/24 21:05
Change comment: Uploaded new attachment "Screenshot 2024-12-24 140459.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.xieby
1 +XWiki.pradeeka
Content
... ... @@ -1,10 +1,12 @@
1 -
1 +(% style="text-align:center" %)
2 +[[image:image-20240915231842-1.png]]
2 2  
3 -[[image:image-20241226135550-1.png||data-xwiki-image-style-alignment="center"]]
4 4  
5 5  
6 6  
7 7  
8 +
9 +
8 8  (% _mstvisible="1" %)
9 9  (% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:**
10 10  
... ... @@ -30,9 +30,6 @@
30 30  
31 31  The LA66 LoRa module can be programmed to support either private LoRa protocols or the LoRaWAN protocol.
32 32  
33 -
34 -**//Note: Due to the current incomplete functionality, it is not recommended to purchase at this time.//**
35 -
36 36  == 1.2  Features ==
37 37  
38 38  
... ... @@ -143,7 +143,7 @@
143 143  
144 144  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.
145 145  
146 -[[image:squareline.io_downloads.png||height="888" width="1294"]]
145 +[[image:squareline.io_downloads.png]]
147 147  
148 148  
149 149  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:
... ... @@ -157,82 +157,81 @@
157 157  == 2.3 Simple usage of SquareLine Studio and exporting UI code ==
158 158  
159 159  
160 -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.
161 161  
161 +* Select major **LVGL** version: **8.3**.
162 +* Select the **Desktop** tab.
163 +* Select  **Eclipse with  SDL for  development on PC**:
162 162  * In the **PROJECT SETTINGS**, select **LVGL version **as **8.3.11** and **Resolution** as **800** x **480**.
163 163  * Select the **CREATE **button to create the new project with the selected settings.
164 164  
165 -[[image:squareline-studio-launcher-screen.png||height="752" width="1415"]]
167 +[[image:image-20240928103357-2.png||height="680" width="708"]]
166 166  
167 167  
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.
170 +Next, you need to configure some additional settings for this project. Select** File  -> Project Settings** as shown in the image below.
169 169  
170 170  [[image:1727229582471-566.png]]
171 171  
172 172  
173 -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:
174 174  
175 -* **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.
176 176  * **LVGL Include Path**: Set this to **lvgl.h**
177 -* Click on the **APPLY CHANGES** button.
179 +* **Click on the APPLY CHANGES button.**
178 178  
179 179  [[image:image-20240928105309-4.png||height="526" width="556"]]
180 180  
183 + Image 4 Configure/modify project settings
181 181  
182 -Now you can start building the user interface. Follow the steps below:
183 183  
186 +Now you can start building the sample UI. Follow the steps below:
184 184  
188 +
185 185  === **Add widgets** ===
186 186  
187 187  
188 -After creating a project, a **Screen** will be automatically added. Its name is **Screen1** by default.
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.
189 189  
190 -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.
194 +Add a Label, Button, and Image to the screen as shown in **Image 5**.
191 191  
192 192  [[image:image-20240928111412-6.png||height="526" width="864"]]
193 193  
198 + Image 5: Add widgets
194 194  
195 -Then click the **Screen **widget to add the second screen. After adding the second screen, it will appear in the Screens panel as **Screen2**.
196 196  
197 -[[image:Screenshot 2024-12-24 140459.png||height="278" width="290"]]
198 -
199 199  === **Modify widget properties** ===
200 200  
201 201  
202 -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.
203 203  
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 +
204 204  [[image:1727485118799-984.png]]
205 205  
210 + Image 6: The button widget's "Inspector" tab
206 206  
212 +
207 207  ==== **Changing the Button properties** ====
208 208  
209 209  
210 -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.
211 211  
212 -* **Flex Flow**: No Layout
213 -* **Transform**:
214 -** **X**: 331 px
215 -** **Y**: 203 px
216 -** **Width**: 100 px
217 -** **Height**: 50 px
218 -** **Align**: CENTER
218 +Under the "Layout" you can change the button's position and size.
219 219  
220 220  [[image:1727485251053-655.png]]
221 221  
222 +Image 7: The button widget's "BUTTON" tab
222 222  
224 +
223 223  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.
224 224  
225 -* 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.
226 226  
227 -[[image:Screenshot 2024-12-24 134937.png||height="80" width="290"]]
228 -
229 -* 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.
230 -
231 -[[image:Screenshot 2024-12-24 134818.png||height="222" width="290"]]
232 -
233 -* 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.
234 -* Finally, click the **ADD** button.
235 -
236 236  [[image:1727485480434-713.png||height="395" width="290"]]
237 237  
238 238   Image 8: Add an event for the button
... ... @@ -241,29 +241,27 @@
241 241  ==== **Changing the label properties** ====
242 242  
243 243  
244 -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.
245 245  
246 246  [[image:image-20240928090825-1.png||height="327" width="391"]]
247 247  
246 + Image 9:  Modify text of label widget
248 248  
249 -Once you enter the text, it will immediately appear on the label.
250 250  
251 -
252 252  ==== **Changing image properties** ====
253 253  
254 254  
255 -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.
256 256  
257 -One way is to move your image into the folder "…/squareline project/assets/", as shown in the image below.
258 -
259 259  [[image:image-20240928113424-9.png||height="355" width="505"]]
260 260  
256 + image 10 add image file into SquareLine Studio project
261 261  
262 -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.
263 -
264 264  [[image:image-20240928114139-10.png||height="559" width="810"]]
265 265  
260 + image 11 use image widget in SquareLine Studio
266 266  
262 +
267 267  ==== **The relationship between widgets** ====
268 268  
269 269  
... ... @@ -270,91 +270,85 @@
270 270  Widgets commonly have two types of relationships: **parallel** and **parent-child**.
271 271  
272 272  * In a **parallel relationship**, widgets' positions are determined relative to a shared reference object.
273 -* 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.
274 274  
275 275  [[image:1727486567182-334.png||height="318" width="278"]]
276 276  
277 277  
278 -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.
279 279  
280 280  [[image:image-20240928112001-8.png||height="431" width="796"]]
281 281  
278 + Image 13: Move Label1 to make it a child of Button1.
282 282  
283 -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.
284 284  
285 -[[image:Screenshot 2024-12-24 144005.png||height="360" width="290"]]
286 -
287 -
288 288  ==== **Preview the screen** ====
289 289  
290 290  
291 -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.
292 292  
293 293  [[image:1727487368023-281.png]]
294 294  
288 + Image 14: Simulating the project
295 295  
290 +
296 296  For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
297 297  
298 298  
299 -== 2.4 Integrate UI Code into an ESP-IDF Project ==
294 +== 2.4 Integrate UI Code to ESP-IDF Project ==
300 300  
301 301  
302 -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.
303 303  
304 -On the  menubar, click **Export -> Export UI** Files as shown in the image below.
305 -
306 306  [[image:1727229798126-306.png]]
307 307  
301 + image 15 export UI file
308 308  
309 -The exported UI files can be found in your SquareLine project folder as shown in the image below.
310 -
311 -
312 312  [[image:1727229821582-258.png||height="333" width="662"]]
313 313  
305 + image 16 exported UI file
314 314  
315 -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.
316 316  
317 317  [[image:image-20240928144830-11.png]]
318 318  
311 + image 17 open CMakeLists.txt
319 319  
320 -Open the **CMakeLists.txt** file and edit it as ahown below.
321 -
322 322  [[image:1727229892636-154.png||height="521" width="407"]]
323 323  
315 + image 18 modify CMakeLists.txt
324 324  
325 -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.
326 326  
327 -Add **#include "ui.h"**
328 -
329 329  [[image:1727229926561-300.png]]
330 330  
321 + image 19 add "ui.h"
331 331  
332 -Add **ui_init();**
333 -
334 334  [[image:1727229955611-607.png]]
335 335  
325 + image 20 add "ui_init()"
336 336  
337 -== 2.5 Brief introduction to the Hello World project ==
338 338  
328 +== 2.5 Brief introduction of hello world project ==
339 339  
340 -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.
341 341  
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.
342 342  
333 +
343 343  == 2.6 Test Result ==
344 344  
345 345  
346 -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.
347 347  
348 -Screen 1:
349 -
350 350  [[image:1727488067077-684.png||height="402" width="574"]]
351 351  
341 + image 21 screen1
352 352  
353 -Screen 2:
354 -
355 355  [[image:1727488157579-949.png||height="397" width="572"]]
356 356  
345 + image 22 screen2
357 357  
347 +
358 358  = 3. Example Project 1: LoRa Central Display =
359 359  
360 360  [[image:image-20240916101737-1.png||height="468" width="683"]]
... ... @@ -362,372 +362,138 @@
362 362  
363 363  = 4. Example Project 2: LoRaWAN RS485 Alarm =
364 364  
365 -= 5. Example Project 3: P2P =
355 += 5. The way to add a new panel to project =
366 366  
367 -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.
368 368  
369 -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.**
370 370  
371 -== 5.1 Firmware Flashing ==
372 -
373 -
374 -The following software tools are required to flash firmware to the ESP32 and LA66.
375 -
376 -* Download the ESP32 firmware flash tool from [[this link>>https://docs.espressif.com/projects/esp-test-tools/en/latest/esp32/production_stage/tools/flash_download_tool.html]].
377 -* Download the LA66 firmware flash tool from [[this link>>https://www.dropbox.com/scl/fo/9kqeqf6wmet10o9hgxuwa/h?rlkey=4ikrg6kg5v0yjxwhp0i37wrv7&e=1&dl=0]].
378 -
379 -=== 5.1.1 Upload the Firmware to the ESP32 ===
380 -
381 -Open //**flash_download_tool.exe**// and follow the steps below.
382 -
383 -* **Chip Type**: ESP32-S3
384 -* **WorkMode**: Develop
385 -* **LoadMode**: UART
386 -* Click on the **OK** button.
387 -
388 -[[image:1738893226894-758.png||height="170" width="176"]]
389 -
390 -
391 -In the **SPIDownload** tab,
392 -
393 -* Select the checkboxes for ESP32_LoRaC-P2P_CommonFW_v1.0.0.bin.
394 -* SPI Flashing Config(default configuration):
395 -** **SPI SPEED**: 40MHz
396 -** **SPI MODE**: DIO
397 -** Check **DoNotChgBin** option.
398 -* **COM**: Select the correct COM port.
399 -* **BAUD**: 1152000
400 -* Click on the **START** button.
401 -
402 -[[image:image-20250505122103-4.png||height="551" width="705"]]
403 -
404 -The progress bar will indicate the firmware update progress and display a **FINISH** message once the update is complete.
405 -
406 -
407 -If you want to compile your own ESP32 project and burn the firmware instead of using the pre-provided firmware in the Firmware folder, please use the following method.
408 -
409 -~1. The first method is to use the IDF plugin in VSCode for flashing. Just click the button circled in red in the picture.
410 -
411 -[[image:1752737375843-555.png]]
412 -
413 -2. The second method is to use the FLASH DOWNLOAD TOOL. Select the 4 bin files under the build folder in the project as shown in the following figure.
414 -
415 -Click the "CombineBin" button (indicated by the red box) in the following figure to combine the selected 4 bin files. The combined firmware can be found in the "flash_download_tool_3.9.7/combine/" directory of this software. The ESP32_LoRaC-P2P_CommonFW_v1.0.0.bin firmware is a combined firmware.
416 -
417 -[[image:1752738269428-241.png||height="574" width="674"]]
418 -
419 -
420 -=== 5.1.2 Upload the Firmware to the LA66 ===
421 -
422 -Open **Dragino_Sensor_Manager_Utility.exe**, and then follow the steps below.
423 -
424 -* Click on the UART Update Firmware tab.
425 -* Select the correct COM port.
426 -* Click on the Upload_File button and select the LA66_P2P_FW_v1.0.0.bin file.
427 -* Click on the Start button.
428 -
429 -
430 -
431 -[[image:image-20250505121328-2.png]]
432 -
433 -
434 -[[image:image-20250505121531-3.png]]
435 -
436 -(% class="wikigeneratedid" %)
437 -The progress bar will indicate the firmware update progress.
438 -
439 -
440 -== 5.2 AT commands and LTS5 Panel Data Formats ==
441 -
442 -Currently, there are two types of panel data formats in LTS5. One is the temperature and humidity type, and the other is the "switch" type. Here is the detailed introduction.
443 -
444 -~1. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF  A84041000181D4A8  01  A4CB  BB0A  8E08  5C02**,0,3
445 -
446 -**01:** encrypt. 1 Byte. 01 ~-~-> no encryption. This 1-byte information is now invalid; simply write 0x01 instead.
447 -
448 -**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, but it is not necessary as the LTS5 can handle shorter names as well.
449 -
450 -**A84041000181D4A8:** Device EUI. 8 Bytes. The last three Bytes will be extracted by the ESP32-S3 and displayed on the screen.
451 -
452 -**01: **Panel Type. 1 Byte. 0x01~-~->Tem & Hum,
453 -
454 - 0x02~-~->Door,
455 -
456 - 0x03~-~->Water Leak,
457 -
458 - 0x04~-~->Occupied,
459 -
460 - 0x05~-~->Button,
461 -
462 - 0x06~-~->Alarm,
463 -
464 -**A4CB: **Battery level//. //2 Bytes. Battery Voltage =0xCBA4&0x3FFF=0x0BA4=2980mV
465 -
466 -**BB0A: **The temperature of the built-in sensor in LHT65N.// //2 Bytes. Temperature:  0x0ABB/100=27.47℃
467 -
468 -**8E08: **The temperature of the External temperature sensor.// //2 Bytes. Temperature:  0x088E/100=21.90℃
469 -
470 -**5C02：**The humidity of the built-in sensor in LHT65N. 2 Bytes. Humidity: 0x025C/10=60.4%
471 -
472 -
473 -2. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF**  **A84041000181D4A8**  **02  A4CB  00**,0,3
474 -
475 -Specific sections of the data share the same function.
476 -
477 -**00: Status. **1 Byte//. //If Panel Type is 0x02, **Status: 00~-~->Open; 01~-~->Close.**
478 -
479 - If Panel Type is 0x03, **Status: 00~-~->Normal; 01~-~->Water Leaking.**
480 -
481 - If Panel Type is 0x04, **Status: 00~-~->Free; 01~-~->Occupied.**
482 -
483 - If Panel Type is 0x05, **Status: 00~-~->OFF; 01~-~->ON.**
484 -
485 - If Panel Type is 0x06, **Status: 00~-~->OFF; 01~-~->Alarm.**
486 -
487 -
488 -Below are examples of AT commands for each type.
489 -
490 -
491 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**01**A4CBBB0A8E085C02,0,3
492 -
493 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**02**A4CB00,0,3
494 -
495 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**03**A4CB00,0,3
496 -
497 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**04**A4CB00,0,3
498 -
499 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**05**A4CB00,0,3
500 -
501 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**06**A4CB00,0,3
502 -
503 -
504 -== 5.3 Usage ==
505 -
506 -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.
507 -
508 -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.
509 -
510 -[[image:image-20250207143131-11.png||height="527" width="547"]]
511 -
512 -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.
513 -
514 -[[image:image-20250207144605-12.png||height="634" width="548"]]
515 -
516 -LTS5 receives this message and displays it on its screen as the image below shows.
517 -
518 -[[image:image-20250208181700-8.jpeg||height="528" width="704"]]
519 -
520 -= 6. Example Project 4: LoRaWAN_CLASS_C =
521 -
522 -
523 -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.
524 -
525 -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.
526 -
527 -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).
528 -
529 -The project can be found at [[this link>>https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/LoRaWAN_CLASS_C]].
530 -
531 -== 6.1 firmware flashing approach ==
532 -
533 -The firmware flashing approach is the same as described in section 5.1.
534 -
535 -== 6.2 flowchart ==
536 -
537 -[[image:image-20250207164320-13.png||height="696" width="1344"]]
538 -
539 -== 6.3 Usage ==
540 -
541 -This section now describes a process involving TTN downlink panel data that is to be displayed on the LTS5 screen.
542 -
543 -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.
544 -
545 -[[image:image-20250207165702-14.png||height="830" width="563"]]
546 -
547 -6.3.2 Switch to Class C using "AT+CLASS=C", and check the class with "AT+CLASS=?".
548 -
549 -[[image:image-20250207173212-27.png]]
550 -
551 -[[image:image-20250207172246-20.png]]
552 -
553 -6.3.3 Verify LA66's join status (in LTS5) with "AT+NJS=?". If not joined, connect manually to LoRaWAN with "AT+JOIN".
554 -
555 -[[image:image-20250207172010-19.png]]
556 -
557 -[[image:image-20250207171650-17.png]]
558 -
559 -6.3.4 After joining, send a message to TTN, such as "AT+SENDB=01,02,8,05820802581ea0a5", to activate communication.
560 -
561 -[[image:image-20250207192107-28.png]]
562 -
563 -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.
564 -
565 -There is an example for TTN downlink.
566 -
567 -1. downlink DEUI F1A84041000181D4A8
568 -1. downlink Dev Name F24B69746368656E2D467269676531FFFF
569 -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.
570 -
571 -[[image:image-20250208175819-1.png||height="503" width="502"]]
572 -
573 -
574 -[[image:image-20250208175918-2.png||height="505" width="502"]]
575 -
576 -
577 -[[image:image-20250208180010-3.png||height="507" width="503"]]
578 -
579 -
580 -[[image:image-20250208181019-4.jpeg||height="592" width="790"]]
581 -
582 -
583 -[[image:image-20250208181328-7.png||height="505" width="504"]]
584 -
585 -
586 -[[image:image-20250208181139-5.jpeg||height="594" width="792"]]
587 -
588 -
589 -= 7. The method for adding a new type of panel to the project =
590 -
591 -If you don't have this need, then this part of the content can be ignored.
592 -
593 -1. Design a panel in SquareLine Studio, as shown in Image 7.1 below for reference.
594 -
595 595  [[image:image-20241121113445-1.png||height="584" width="934"]]
596 596  
597 - Image 7.1: a panel about water_leak
362 + image 5.1 a panel about water_leak
598 598  
599 599  
600 -2. **Export the UI file. **
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.
601 601  
602 -You need to adjust the export path first, then click '**Export -> Export UI Files**' on the menu bar. The method for exporting UI files using the SquareLine software has already been described earlier.
603 -
604 -Next, create a new folder named "ui_water_leak" under "app_components/extra_lib/", and then cut all the UI files you just exported into this newly created folder.
605 -
606 -Image 7.2 shows the result of the operation.
607 -
608 608  [[image:image-20241121141120-4.png||height="383" width="795"]]
609 609  
610 - Image 7.2: Exported UI files
369 + image 5.2 ui files exported
611 611  
612 612  
613 -3. **Delete and rename some file.** Here are the steps:
372 +**3. Delete or rename some file.** Here are the steps:
614 614  
615 - Step 1: Delete the 'components' directory.
616 - Step 2: Delete 'filelist.txt'.
617 - Step 3: Delete 'ui_helpers.c' and 'ui_helpers.h'.
618 - Step 4: Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
619 - 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'.
620 620  
621 621  [[image:image-20241121151934-10.png||height="303" width="792"]]
622 622  
623 - image 7.3 rest file (1)
382 + image 5.3 rest file (1)
624 624  
625 625  [[image:image-20241121142925-7.png||height="141" width="793"]]
626 626  
627 - image 7.4 rest file (2)
386 + image 5.4 rest file (2)
628 628  
629 -4. Open the project in VS Code.
388 +**4. Open this project in vscode.**
630 630  
631 -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.
632 632  
633 633  [[image:image-20241121181957-17.png||height="438" width="516"]]
634 634  
635 - image 7.5 extra_lib/CMakeLists.txt before adding
394 + image 5.5 extra_lib/CMakeLists.txt before add
636 636  
637 637  [[image:image-20241121182239-18.png||height="520" width="518"]]
638 638  
639 - image 7.6 extra_lib/CMakeLists.txt after adding
398 + image 5.6 extra_lib/CMakeLists.txt after add
640 640  
641 -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.
642 642  
643 -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.
644 -
645 645  [[image:image-20241121171629-11.png]]
646 646  
647 - image 7.7 unmodified font file
404 + image 5.7 before-modified font file
648 648  
649 649  [[image:image-20241121171901-12.png]]
650 650  
651 - image 7.8 modified font file
408 + image 5.8 modified font file
652 652  
653 -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.
654 654  
655 655  [[image:image-20241121172714-13.png]]
656 656  
657 - image 7.9 unmodified image file
414 + image 5.9 before-modified image file
658 658  
659 659  [[image:image-20241121172908-14.png]]
660 660  
661 - image 7.10 modified image file
418 + image 5.10 modified image file
662 662  
663 -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.
664 664  
665 665  [[image:image-20241121180030-15.png]]
666 666  
667 - image 7.11 ui_water_leak/CMakeLists.txt before modification
424 + image 5.11 ui_water_leak/CMakeLists.txt before modification
668 668  
669 669  [[image:image-20241121180517-16.png]]
670 670  
671 - image 7.12 ui_water_leak/CMakeLists.txt after modification
428 + image 5.12 ui_water_leak/CMakeLists.txt after modification
672 672  
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.
673 673  
674 -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.
675 -
676 676  [[image:image-20241122094200-23.png]]
677 677  
678 - image 7.13 ui_water_leak.h (1) before modification
434 + image 5.13 ui_water_leak.h (1) before modification
679 679  
680 680  [[image:image-20241122094320-24.png||height="852" width="554"]]
681 681  
682 - image 7.14 ui_water_leak.h (2) before modification
438 + image 5.14 ui_water_leak.h (2) before modification
683 683  
684 684  [[image:image-20241122094600-25.png||height="1078" width="554"]]
685 685  
686 - image 7.15 ui_water_leak.h (1) after modification
442 + image 5.15 ui_water_leak.h (1) after modification
687 687  
688 688  [[image:image-20241122094719-26.png||height="941" width="583"]]
689 689  
690 - image 7.16 ui_water_leak.h (2) before modification
446 + image 5.16 ui_water_leak.h (2) before modification
691 691  
692 -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.
693 693  
694 694  _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.
695 695  
696 696  [[image:image-20241122102929-27.png||height="619" width="426"]]
697 697  
698 - image 7.17 ui_water_leak.c (1) before modification
454 + image 5.17 ui_water_leak.c (1) before modification
699 699  
700 700  [[image:image-20241122112838-30.png||height="551" width="628"]]
701 701  
702 - image 7.18 ui_water_leak.c (2) before modification
458 + image 5.18 ui_water_leak.c (2) before modification
703 703  
704 704  [[image:image-20241122110815-29.png||height="725" width="712"]]
705 705  
706 - image 7.19 ui_water_leak.c (3) before modification
462 + image 5.19 ui_water_leak.c (3) before modification
707 707  
708 708  [[image:image-20241122113158-31.png||height="872" width="677"]]
709 709  
710 - image 7.20 ui_water_leak.c (1) after modification
466 + image 5.20 ui_water_leak.c (1) after modification
711 711  
712 712  [[image:image-20241122113259-33.png||height="874" width="724"]]
713 713  
714 - image 7.21 ui_water_leak.c (2) after modification
470 + image 5.21 ui_water_leak.c (2) after modification
715 715  
716 716  [[image:image-20241122113359-34.png||height="804" width="746"]]
717 717  
718 - image 7.22 ui_water_leak.c (3) after modification
474 + image 5.22 ui_water_leak.c (3) after modification
719 719  
720 -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.
721 721  
722 722  [[image:image-20241122134113-35.png||height="380" width="421"]]
723 723  
724 - image 7.23 ui_water_leak_events_.h before modification
480 + image 5.23 ui_water_leak_events_.h before modification
725 725  
726 726  [[image:image-20241122134420-37.png||height="201" width="283"]]
727 727  
728 -image 7.24 ui_water_leak_events_.h after modification
484 +image 5.24 ui_water_leak_events_.h after modification
729 729  
730 -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.
731 731  
732 732  Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
733 733  
... ... @@ -741,14 +741,14 @@
741 741  
742 742  [[image:image-20241122135023-38.png||height="358" width="372"]]
743 743  
744 - image 7.25 ui_water_leak_events_.c before modification
500 + image 5.25 ui_water_leak_events_.c before modification
745 745  
746 746  [[image:image-20241122135258-39.png||height="403" width="559"]]
747 747  
748 - image 7.26 ui_water_leak_events_.c after modification
504 + image 5.26 ui_water_leak_events_.c after modification
749 749  
750 750  
751 -12. **Modify ui_water_leak_style.c file.**
507 +**12. Modify ui_water_leak_style.c file.**
752 752  
753 753  Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
754 754  
... ... @@ -758,67 +758,66 @@
758 758  
759 759  [[image:image-20241122141536-41.png||height="361" width="612"]]
760 760  
761 - image 7.27 ui_water_leak_style.c (1) before modification
517 + image 5.27 ui_water_leak_style.c (1) before modification
762 762  
763 763  [[image:image-20241122142129-42.png||height="386" width="613"]]
764 764  
765 - image 7.28 ui_water_leak_style.c (1) after modification
521 + image 5.28 ui_water_leak_style.c (1) after modification
766 766  
767 767  
768 768  Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
769 769  
770 - delete code as shown in image 7.29
526 + delete code as shown in image 5.29
771 771  
772 772  [[image:image-20241122145620-44.png||height="757" width="671"]]
773 773  
774 - image 7.29 ui_water_leak_style.c (2)
530 + image 5.29 ui_water_leak_style.c (2)
775 775  
776 776  
777 -Step3. The image 7.30, 7.31 show the change.
533 +Step3. The image 5.30, 5.31 show the change.
778 778  
779 779  [[image:image-20241122152026-45.png||height="277" width="828"]]
780 780  
781 - image 7.30 ui_water_leak_style.c (3) before modification
537 + image 5.30 ui_water_leak_style.c (3) before modification
782 782  
783 783  [[image:image-20241122152542-46.png||height="293" width="830"]]
784 784  
785 - image 7.31 ui_water_leak_style.c (3) after modification
541 + image 5.31 ui_water_leak_style.c (3) after modification
786 786  
787 787  
788 -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).
789 789  
790 790  [[image:image-20241122153958-47.png]]
791 791  
792 - image 7.32 ui_water_leak_style.c (4)
548 + image 5.32 ui_water_leak_style.c (4)
793 793  
794 -
795 795  [[image:image-20241122154755-49.png||height="864" width="513"]]
796 796  
797 - image 7.33 ui_water_leak_style.c (4)
552 + image 5.33 ui_water_leak_style.c (4)
798 798  
799 799  
800 -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).
801 801  
802 802  [[image:image-20241122155650-50.png||height="922" width="513"]]
803 803  
804 - image 7.34 ui_water_leak_style.c (5)
559 + image 5.34 ui_water_leak_style.c (5)
805 805  
806 806  
807 -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.
808 808  
809 809  [[image:image-20241122161934-51.png]]
810 810  
811 - image 7.35
566 + image 5.35
812 812  
813 813  
814 -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.
815 815  
816 816  [[image:image-20241122162852-53.png||height="330" width="529"]]
817 817  
818 - image 7.37
573 + image 5.37
819 819  
820 820  
821 -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.
822 822  
823 823  panel_with_type union_sensor;
824 824  
... ... @@ -832,45 +832,36 @@
832 832  
833 833  return union_sensor;
834 834  
835 -[[image:image-20250122173546-6.png||height="777" width="922"]]
590 +[[image:image-20241122171211-54.png||height="635" width="792"]]
836 836  
837 - image 7.38
592 + image 5.38
838 838  
839 839  
840 -13. Rest midification in sort.h file.
595 +**13. Modify sort.c file.**
841 841  
842 -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.
843 843  
844 -[[image:image-20250122170230-1.png||height="580" width="513"]]
599 +[[image:image-20241122173718-56.png||height="378" width="579"]]
845 845  
846 - image 7.39 sort.h
601 + image 5.39 sort.c (1)
847 847  
848 -13. **Modify sort.c file.**
849 -
850 -Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 26.
851 -
852 -[[image:image-20250122171910-5.png||height="524" width="510"]]
853 -
854 - image 7.40 sort.c (1)
855 -
856 856  There are still some changes need to be done in sort.c, and omit here for the moment.
857 857  
858 858  
606 += 6. FAQ =
859 859  
860 -= 8. FAQ =
608 +== 6.1 ==
861 861  
862 -== 8.1 ==
863 863  
611 += 7. Order Info =
864 864  
865 -= 9. Order Info =
613 +== 7.1  Part Number ==
866 866  
867 -== 9.1  Part Number ==
868 868  
869 -
870 870  Part Number: (% style="color:#4472c4" %)LTS5
871 871  
872 872  
873 -== 9.2  Packing Info ==
619 +== 7.2  Packing Info ==
874 874  
875 875  
876 876  **Package Includes**:
... ... @@ -879,21 +879,20 @@
879 879  * 5V,2A DC Power Adapter.
880 880  * USB Type C Program Cable
881 881  
882 -= 10. Support =
628 += 8. Support =
883 883  
884 884  
885 885  * 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.
886 886  * 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]].
887 887  
888 -= 11.  Reference material =
634 += 9.  Reference material =
889 889  
890 890  
891 -* Datasheet: [[https:~~/~~/www.dropbox.com/scl/fo/fr7wjsdfh9huchg59p7bv/APASCR0elWtp_EbUZ1W9K-A?rlkey=pcuptw3dtg5pw9vgt4ag6hs9z&st=ds6hdztg&dl=0>>https://www.dropbox.com/scl/fo/fr7wjsdfh9huchg59p7bv/APASCR0elWtp_EbUZ1W9K-A?rlkey=pcuptw3dtg5pw9vgt4ag6hs9z&st=ds6hdztg&dl=0]]
892 -* schematic: [[LTS5-V1>>https://www.dropbox.com/scl/fo/grwr5b4x1tk2omyjwg06y/ACleSdi5f7p5zRB2mfPH7CE?rlkey=vhcs83jrj9tkmw8wa9m9wo5rx&st=hkhe3bbj&dl=0]]
893 -* 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]]
637 +* Datasheet
638 +* Source Code
894 894  * Mechinical
895 895  
896 -= 12. FCC Warning =
641 += 10. FCC Warning =
897 897  
898 898  
899 899  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
1752737128542-192.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -52.4 KB
Content
1752737375843-555.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -9.4 KB
Content
1752738269428-241.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -52.7 KB
Content
LTS5-V1.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -661.6 KB
Content
Screenshot 2024-12-24 144005.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -28.0 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
image-20250505112032-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -43.9 KB
Content
image-20250505121328-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -12.2 KB
Content
image-20250505121531-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -21.3 KB
Content
image-20250505122103-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -46.1 KB
Content