Last modified by BoYang Xie on 2025/05/05 12:26
<
From version < 117.1 >
edited by Dilisi S
on 2024/12/20 21:52
To version < 165.3 >
edited by BoYang Xie
on 2025/02/08 16:45
>
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  
... ... @@ -102,7 +102,7 @@
102 102  * Smart Cities
103 103  * Smart Factory
104 104  
105 -= 2.  Getting Started with Hello World =
104 += 2.  Getting Started with 'Hello World' =
106 106  
107 107  == 2.1  About this demo ==
108 108  
... ... @@ -113,7 +113,6 @@
113 113  * Implementing functionality to navigate the Web UI to a new page when the button is clicked.
114 114  * Uploading the UI to the LTS5 device.
115 115  
116 -
117 117  By completing this demo, you will gain foundational knowledge for customizing the LTS5 interface and building more advanced IoT applications.
118 118  
119 119  
... ... @@ -120,19 +120,20 @@
120 120  == 2.2  Install Software Running Environment ==
121 121  
122 122  
123 -The **ESP MCU** supports development using **ESP-IDF**, **Arduino**, or **MicroPython**. For this project, we use **ESP-IDF** for compilation and **Visual Studio Code (VS Code)** as the development environment.
121 +The **ESP MCU** supports development with **ESP-IDF**, **Arduino**, or **MicroPython**. We use **ESP-IDF** for compilation and **Visual Studio Code (VS Code)** as the development environment for this project.
124 124  
125 125  
126 -=== 2.2.1 Install VSCode and ESP-IDF extension ===
124 +=== 2.2.1 Install VS Code and ESP-IDF extension ===
127 127  
128 128  
129 -Firstly, download and install VSCode for your computer's operating system from the official website: [[Download Visual Studio Code - Mac, Linux, Windows>>url:https://code.visualstudio.com/download]].
127 +First, download and install **VS Code** for your operating system from the Visual Studio Code website: [[Visual Studio Code - Mac, Linux, Windows>>https://code.visualstudio.com/download]].
130 130  
131 -Next, you need to install the ESP-IDF extension within VSCode. The detailed operation steps are illustrated in image 1.
129 +Next, install the **ESP-IDF** extension within **VS Code**. Detailed steps for this process are shown in Image 1.
132 132  
131 +
133 133  [[image:image-20240928110211-5.png||height="508" width="866"]]
134 134  
135 - image 1 ESP-IDF extension install
134 + Image 1: ESP-IDF extension install
136 136  
137 137  Links for reference: [[Install ESP32 ESP-IDF on Windows and Integrate with VS code (esp32tutorials.com)>>url:https://esp32tutorials.com/install-esp32-esp-idf-windows-integrate-vs-code/#:~~:text=In%20this%20tutorial,%20we%20will%20show%20you%20how%20to%20install]]
138 138  
... ... @@ -140,159 +140,218 @@
140 140  === 2.2.2 Install SquareLine Studio ===
141 141  
142 142  
143 -The version we are utilizing for this software is 1.4.2. You can download it from the official link: [[SquareLine Studio - Download the current version of SquareLine Studio>>url:https://squareline.io/downloads#lastRelease]].
142 +Download and install the latest version of [[SquareLine Studio>>https://squareline.io/downloads#lastRelease]] on your computer. It supports Windows, Linux, and Mac OS. The software version we are using here is 1.5.0. See the image below.
144 144  
145 -Please note that this software necessitates the registration of a license prior to usage, and various licenses come with distinct limitations. For instance, the free version imposes restrictions such as a limit of 1 component, 150 widgets, and 10 screens. However, for first-time downloads, you are granted unrestricted access for a period of 30 days without the need for immediate registration.
144 +[[image:squareline.io_downloads.png||height="888" width="1294"]]
146 146  
147 147  
148 -== 2.3 Simple usage of SquareLine Studio and export UI code ==
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:
149 149  
149 +* Max. 10 screens
150 +* Max. 150 widgets
151 +* Max. 5 global colors
152 +* Max. 2 themes
153 +* Max. 1 component
150 150  
151 -After launching and logging in to this software, create a project as shown in the following image 2. The version of LVGL is 8.3.11.
155 +== 2.3 Simple usage of SquareLine Studio and exporting UI code ==
152 152  
153 -[[image:image-20240928103357-2.png||height="680" width="708"]]
154 154  
155 - image 2 create a SquareLine project
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**.
156 156  
157 -Next, we need to make some settings for this project. By clicking in the specified order on image 3, we can see the page as shown in image 4.
160 +* In the **PROJECT SETTINGS**, select **LVGL version **as **8.3.11** and **Resolution** as **800** x **480**.
161 +* Select the **CREATE **button to create the new project with the selected settings.
158 158  
163 +[[image:squareline-studio-launcher-screen.png||height="752" width="1415"]]
164 +
165 +
166 +Next, you need to configure some additional settings for this project. To do so, select** File  -> Project Settings** as shown in the image below.
167 +
159 159  [[image:1727229582471-566.png]]
160 160  
161 - image 3 project settings
162 162  
171 +In the **PROJECT SETTINGS** dialog box, configure/modify the project settings as shown in the image below.
172 +
173 +* **UI Files Export Root**: Select a folder on your computer to store the UI files.
174 +* **LVGL Include Path**: Set this to **lvgl.h**
175 +* Click on the **APPLY CHANGES** button.
176 +
163 163  [[image:image-20240928105309-4.png||height="526" width="556"]]
164 164  
165 - image 4 modify project settings
166 166  
167 -Now we can start to use this software. Here are some usage information for this software.
180 +Now you can start building the user interface. Follow the steps below:
168 168  
169 -**~1. add widget**
170 170  
171 -To add a widget, you should click a widget you want to add at the area entitled “Widgets”. In image , demonstrate a add process of label, button, and image 5.
183 +=== **Add widgets** ===
172 172  
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.
187 +
173 173  [[image:image-20240928111412-6.png||height="526" width="864"]]
174 174  
175 - image 5 add widgets
176 176  
177 -**2. modify widget**
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**.
178 178  
179 -The area for modifying widgets is called "Inspector". There are four parts in the "Inspector" tab. We use three of them more frequently, excluding "COMPONENT". The second part is aimed at adjusting the layout, size, position, alignment, flags, and states, etc. of widgets. The name of the second part indicates the type of widget it is representing, and in image 6, it is "BUTTON".
193 +[[image:Screenshot 2024-12-24 140459.png||height="278" width="290"]]
180 180  
195 +=== **Modify widget properties** ===
196 +
197 +
198 +The area for modifying widgets is called the **Inspector** panel. The Inspector panel consists of four sections: **COMPONENT**, **<WIDGET>**, **STYLE SETTINGS**, and **EVENTS**, as shown in the image below. The second section allows you to adjust a widget's layout, size, position, alignment, flags, states, and more. When you select a widget on the screen, the name of this section changes to match the name of the selected widget.
199 +
181 181  [[image:1727485118799-984.png]]
182 182  
183 - image 6 the button widget's "Inspector" tab
184 184  
185 -Second part: "Layout" means a auto position-management for widgets contained in the parent widget. "Transform" includes size, position and align modification.
203 +==== **Changing the Button properties** ====
186 186  
205 +
206 +Click the **Button **you have added to the screen. Under the **Layout** you can change the button's position and size. Use the following settings:
207 +
208 +* **Flex Flow**: No Layout
209 +* **Transform**:
210 +** **X**: 331 px
211 +** **Y**: 203 px
212 +** **Width**: 100 px
213 +** **Height**: 50 px
214 +** **Align**: CENTER
215 +
187 187  [[image:1727485251053-655.png]]
188 188  
189 -image 7 the button widget's "BUTTON" tab
190 190  
191 -Third part: It is an area of style setting.
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.
192 192  
193 -Fourth part: It is an area for adding events. In image 8, it is adding a click event to a button. If the button is clicked after the click event is added as shown in image 8, the current screen will fade into another specified screen, and the switching process will last 500ms.
221 +* Click **ADD EVENT** button. A new section will appear to configure this event.
194 194  
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 +
195 195  [[image:1727485480434-713.png||height="395" width="290"]]
196 196  
197 - image 8 add event for button
234 + Image 8: Add an event for the button
198 198  
199 -**3. change label widget content**
200 200  
201 -Modify the content in text as shown in image 9, the text content of label widget will be changed accordingly.
237 +==== **Changing the label properties** ====
202 202  
239 +
240 +Click the Label you have added to the screen. Under the **Label** section, type "**Click for Detail**" in the **Text** textbox.
241 +
203 203  [[image:image-20240928090825-1.png||height="327" width="391"]]
204 204  
205 - image 9 modify text content of label widget
206 206  
207 -**4. Add image into project**
245 +Once you enter the text, it will immediately appear on the label.
208 208  
209 -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.
210 210  
248 +==== **Changing image properties** ====
249 +
250 +
251 +To use the **Image **widget, you should first add an image to your project. The image format must be PNG, and its resolution should not exceed 800x480 pixels. There are two ways to add an image file.
252 +
253 +One way is to move your image into the folder "…/squareline project/assets/", as shown in the image below.
254 +
211 211  [[image:image-20240928113424-9.png||height="355" width="505"]]
212 212  
213 - image 10 add image file into SquareLine Studio project
214 214  
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 +
215 215  [[image:image-20240928114139-10.png||height="559" width="810"]]
216 216  
217 - image 11 use image widget in SquareLine Studio
218 218  
219 -**5. The relationship between widgets**
263 +==== **The relationship between widgets** ====
220 220  
221 -There are two common relationships between widgets: one is parallel, the other is parent-child. The parallel relationship means that widgets' relative position is based on a collective object of reference. In parent-child relationship, the parts of the child object that are outside the boundaries of the parent object are not visible by default. Therefore, we need to adjust the position of the child object so that it falls within the range of the parent object, allowing it to be seen as illustrated in image 13.
222 222  
266 +Widgets commonly have two types of relationships: **parallel** and **parent-child**.
267 +
268 +* In a **parallel relationship**, widgets' positions are determined relative to a shared reference object.
269 +* In a **parent-child relationship**, any part of the child object outside the parent's boundaries is hidden by default. To make the child object fully visible, you must adjust its position to fit within the parent's range.
270 +
223 223  [[image:1727486567182-334.png||height="318" width="278"]]
224 224  
225 -image 12 move label1 to make label1 widget be a child of button1 widget(1)
226 226  
274 +Move the label, **Label1** to make it a child of **Button1** as shown in the image below.
275 +
227 227  [[image:image-20240928112001-8.png||height="431" width="796"]]
228 228  
229 - image 13 move label1 to make label1 widget be a child of button1 widget(2)
230 230  
231 -**6. Preview the final effect**
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.
232 232  
233 -An advantage of this kind of software is that you can edit the UI with quick previews. In other words, it provides a way of combining graphical programming with simulation immediately.
281 +[[image:Screenshot 2024-12-24 144005.png||height="360" width="290"]]
234 234  
283 +
284 +==== **Preview the screen** ====
285 +
286 +
287 +You can test the result by clicking on the **PLAY** button as shown in the image below. The screen will change into play mode.
288 +
235 235  [[image:1727487368023-281.png]]
236 236  
237 - image 14 click on the triangle icon to start or end the simulation
238 238  
239 -For more detailed usage, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
292 +For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
240 240  
241 241  
242 242  == 2.4 Integrate UI Code to ESP-IDF Project ==
243 243  
244 244  
245 -To achieve the integrating, we first need to export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
298 +To integrate, first export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
246 246  
300 +On the  menubar, click **Export -> Export UI** Files as shown in the image below.
301 +
247 247  [[image:1727229798126-306.png]]
248 248  
249 - image 15 export UI file
250 250  
305 +The exported UI files can be found in your SquareLine project folder as shown in the image below.
306 +
307 +
251 251  [[image:1727229821582-258.png||height="333" width="662"]]
252 252  
253 - image 16 exported UI file
254 254  
255 -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.
256 256  
257 257  [[image:image-20240928144830-11.png]]
258 258  
259 - image 17 open CMakeLists.txt
260 260  
316 +Open the **CMakeLists.txt** file and edit it as ahown below.
317 +
261 261  [[image:1727229892636-154.png||height="521" width="407"]]
262 262  
263 - image 18 modify CMakeLists.txt
264 264  
265 -The last step of integrating is adding two lines of code in main.c file.
321 +Open the main.c file and  add two lines of code as shown in the below images.
266 266  
323 +Add **#include "ui.h"**
324 +
267 267  [[image:1727229926561-300.png]]
268 268  
269 - image 19 add "ui.h"
270 270  
328 +Add **ui_init();**
329 +
271 271  [[image:1727229955611-607.png]]
272 272  
273 - image 20 add "ui_init()"
274 274  
333 +== 2.5 Brief introduction to the Hello World project ==
275 275  
276 -== 2.5 Brief introduction of hello world project ==
277 277  
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.
278 278  
279 -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.
280 280  
281 -
282 282  == 2.6 Test Result ==
283 283  
284 284  
285 -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.
286 286  
344 +Screen 1:
345 +
287 287  [[image:1727488067077-684.png||height="402" width="574"]]
288 288  
289 - image 21 screen1
290 290  
349 +Screen 2:
350 +
291 291  [[image:1727488157579-949.png||height="397" width="572"]]
292 292  
293 - image 22 screen2
294 294  
295 -
296 296  = 3. Example Project 1: LoRa Central Display =
297 297  
298 298  [[image:image-20240916101737-1.png||height="468" width="683"]]
... ... @@ -300,135 +300,293 @@
300 300  
301 301  = 4. Example Project 2: LoRaWAN RS485 Alarm =
302 302  
303 -= 5.  The way to add a new panel to project =
361 += 5. Example Project 3: P2P =
304 304  
305 -**~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.**
363 +The project achieves the function of receiving LoRa P2P messages and displaying them on the screen. The workflow is as follows: A LA66, running a P2P program, sends a message in a particular format via an AT command. Then, the LTS5 receives the message and displays it on the screen.
306 306  
365 +The project can be found at [[this link>>url:https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/P2P]].
366 +
367 +== 5.1 firmware flashing approach. ==
368 +
369 +5.1.1 Download this project
370 +
371 +5.1.2 Download esp32 firmware flash tool in [[this link>>https://docs.espressif.com/projects/esp-test-tools/en/latest/esp32/production_stage/tools/flash_download_tool.html]].
372 +
373 +5.1.3 Download la66 firmware flash tool in [[this link>>https://www.dropbox.com/scl/fo/9kqeqf6wmet10o9hgxuwa/h?rlkey=4ikrg6kg5v0yjxwhp0i37wrv7&e=1&dl=0]].
374 +
375 +5.1.4 Upload firmware to esp32
376 +
377 +Open flash_download_tool.exe, and then follow the steps below.
378 +
379 +[[image:1738893226894-758.png||height="170" width="176"]]
380 +
381 +[[image:image-20250207100150-7.png||height="476" width="538"]]
382 +
383 +5.1.5 Upload firmware to la66
384 +
385 +Open Dragino_Sensor_Manager_Utility.exe, and then follow the steps below.
386 +
387 +[[image:image-20250207101415-8.png||height="522" width="618"]]
388 +
389 +[[image:image-20250207101515-9.png||height="522" width="618"]]
390 +
391 +== 5.2 AT command and P2P data format ==
392 +
393 +AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**01**A4CBBB0A8E085C02,0,3
394 +
395 +AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**02**A4CB00,0,3
396 +
397 +AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**03**A4CB00,0,3
398 +
399 +AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**04**A4CB00,0,3
400 +
401 +AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**05**A4CB00,0,3
402 +
403 +AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**06**A4CB00,0,3
404 +
405 +**Data format**:
406 +
407 +~1. AT+SEND=1,**01** **4b69746368656e2d467269676531FFFF A84041000181D4A8 01  A4CB  BB0A  8E08  5C02**,0,3
408 +
409 +**01:** encrypt. 1 Byte. 01 ~-~-> no encryption. This 1-byte information is now invalid; simply write 0x01 instead.
410 +
411 +**4b69746368656e2d467269676531FFFF: **Device Name. 16 Bytes. The Device Name for this piece of information is "Kitchen-Frige1," and the subsequent "FFFF" is intended to pad it up to 16 Bytes. The Device Name for this piece of information is 'Kitchen-Frige1,' and the subsequent 'FFFF' is intended to pad it up to 16 Bytes, but it is not necessary as the system can handle shorter names as well.
412 +
413 +**A84041000181D4A8:** Device EUI. 8 Bytes. The last three Bytes will be extracted by the ESP32-S3 and displayed on the screen.
414 +
415 +**01: **Panel Type. 1 Byte. 0x01~-~->Tem & Hum,
416 +
417 + 0x02~-~->Door,
418 +
419 + 0x03~-~->Water Leak,
420 +
421 + 0x04~-~->Occupied,
422 +
423 + 0x05~-~->Button,
424 +
425 + 0x06~-~->Alarm,
426 +
427 +**A4CB: **Battery level//. //2 Bytes. Battery Voltage =0xCBA4&0x3FFF=0x0BA4=2980mV
428 +
429 +**BB0A: **The temperature of the built-in sensor in LHT65N.// //2 Bytes. Temperature:  0x0ABB/100=27.47℃
430 +
431 +**8E08: **The temperature of the External temperature sensor.// //2 Bytes. Temperature:  0x088E/100=21.90℃
432 +
433 +**5C02：**The humidity of the built-in sensor in LHT65N. 2 Bytes. Humidity: 0x025C/10=60.4%
434 +
435 +2. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF**  **A84041000181D4A8**  **02  A4CB  00**,0,3
436 +
437 +Specific sections of the data share the same function.
438 +
439 +**00: Status. **1 Byte//. //If Panel Type is 0x02, **Status: 00~-~->Open; 01~-~->Close.**
440 +
441 + If Panel Type is 0x03, **Status: 00~-~->Normal; 01~-~->Water Leaking.**
442 +
443 + If Panel Type is 0x04, **Status: 00~-~->Free; 01~-~->Occupied.**
444 +
445 + If Panel Type is 0x05, **Status: 00~-~->OFF; 01~-~->ON.**
446 +
447 + If Panel Type is 0x06, **Status: 00~-~->OFF; 01~-~->Alarm.**
448 +
449 +== 5.3 Usage ==
450 +
451 +After burning the firmware into LTS5, you can use an LA66 equipped with peer-to-peer firmware to send data to LTS5 via AT commands.
452 +
453 +5.3.1 Connect LA66 to the computer, open Serial Port Utility, and send the AT+CFG instruction to check whether the LA66 has downloaded correct program.
454 +
455 +[[image:image-20250207143131-11.png||height="527" width="547"]]
456 +
457 +5.3.2 Copy an AT instruction example, click "Send" button, then the led in LA66 will flash and the LTS5 will display the LoRa information.
458 +
459 +[[image:image-20250207144605-12.png||height="634" width="548"]]
460 +
461 += 6. Example Project 4: LoRaWAN_CLASS_C =
462 +
463 +
464 +The project achieves the function of receiving LoRaWAN Class C messages and displaying them on the screen. Note: The Things Network (TTN) needs to enable Class C support, and the LA66 within the LTS5 needs to operate in Class C mode.
465 +
466 +The downlink workflow proceeds as follows: The Things Network (TTN) sends a message in a specific format via downlink. Then, a LoRaWAN gateway relays this message to the LTS5. Finally, the LTS5 receives the message and displays it on its screen.
467 +
468 +The uplink workflow is as follows: The LA66 within the LTS5 sends a LoRaWAN message, for some reason, to a LoRaWAN gateway, which then forwards it to The Things Network (TTN).
469 +
470 +The project can be found at [[this link>>https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/LoRaWAN_CLASS_C]].
471 +
472 +== 6.1 firmware flashing approach ==
473 +
474 +The firmware flashing approach is the same as described in section 5.1.
475 +
476 +== 6.2 flowchart ==
477 +
478 +[[image:image-20250207164320-13.png||height="696" width="1344"]]
479 +
480 +== 6.3 Usage ==
481 +
482 +This section now describes a process involving TTN downlink panel data that is to be displayed on the LTS5 screen.
483 +
484 +6.3.1 Connect LA66 to the computer, open Serial Port Utility, and send the AT+CFG instruction to check whether the LA66 has downloaded correct program.
485 +
486 +[[image:image-20250207165702-14.png||height="830" width="563"]]
487 +
488 +6.3.2 Switch to Class C using "AT+CLASS=C", and check the class with "AT+CLASS=?".
489 +
490 +[[image:image-20250207173212-27.png]]
491 +
492 +[[image:image-20250207172246-20.png]]
493 +
494 +6.3.3 Verify LA66's join status (in LTS5) with "AT+NJS=?". If not joined, connect manually to LoRaWAN with "AT+JOIN".
495 +
496 +[[image:image-20250207172010-19.png]]
497 +
498 +[[image:image-20250207171650-17.png]]
499 +
500 +6.3.4 After joining, send a message to TTN, such as "AT+SENDB=01,02,8,05820802581ea0a5", to activate communication.
501 +
502 +[[image:image-20250207192107-28.png]]
503 +
504 +6.3.5 TTN distributes panel data in three phases: DEUI, Dev Name, and Sensor Data. The Dev Name, the last three bytes of the DEUI, and the panel type union together ensure the identification of a panel. Data about the same panel type will update the existing panel display, while data about a different panel type will create a new panel display on the LTS5 screen.
505 +
506 +There is an example for TTN downlink.
507 +
508 +1. downlink DEUI F1A84041000181D4A8
509 +1. downlink Dev Name F24B69746368656E2D467269676531FFFF
510 +1. downlink Sensor Data 5501A4CBBB0A8E085C02 or 5504A4CB01. Both of them are vaild formats for LTS5. Note: 0x55 as prefix and any other prefix except 0xF1, 0xF2, 0xF3 means downlink is Sensor Data.
511 +
512 += 7. The method for adding a new type of panel to the project =
513 +
514 +If you don't have this need, then this part of the content can be ignored.
515 +
516 +1. Design a panel in SquareLine Studio, as shown in Image 7.1 below for reference.
517 +
307 307  [[image:image-20241121113445-1.png||height="584" width="934"]]
308 308  
309 - image 5.1 a panel about water_leak
520 + Image 7.1: a panel about water_leak
310 310  
311 -**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.
312 312  
523 +2. **Export the UI file: **You need to adjust the export path first, then click '**Export -> Export UI Files**' on the menu bar. This step was introduced earlier. After that, you can get the UI files as shown in Image 7.2.
524 +
313 313  [[image:image-20241121141120-4.png||height="383" width="795"]]
314 314  
315 - image 5.2 ui files exported
527 + Image 7.2: Exported UI files
316 316  
317 -**3. Delete or rename some file.** Here are the steps:
318 318  
319 - Step1 Delete the 'components' directory.
320 - Step2 Delete 'filelist.txt'.
321 - Step3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
322 - Step4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
323 - Step5 Rename the 'screens' directory to 'styles'.
530 +3. **Delete and rename some file.** Here are the steps:
324 324  
532 + Step 1: Delete the 'components' directory.
533 + Step 2: Delete 'filelist.txt'.
534 + Step 3: Delete 'ui_helpers.c' and 'ui_helpers.h'.
535 + Step 4: Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
536 + Step 5: Rename the 'screens' directory to 'styles'.
537 +
325 325  [[image:image-20241121151934-10.png||height="303" width="792"]]
326 326  
327 - image 5.3 rest file (1)
540 + image 7.3 rest file (1)
328 328  
329 329  [[image:image-20241121142925-7.png||height="141" width="793"]]
330 330  
331 - image 5.4 rest file (2)
544 + image 7.4 rest file (2)
332 332  
333 -**4. Open this project in vscode.**
546 +4. Open the project in VS Code.
334 334  
335 -5. Add file include path about water_leak in extra_lib/CMakeLists.txt as shown in image 5.5, 5.6, and its format is similar to the tem_hum or door.
548 +5. Add the file include path for **water_leak** in **extra_lib/CMakeLists.txt**, as shown in Images 7.5 and 7.6. Its format is similar to that of **tem_hum** or **door**."
336 336  
337 337  [[image:image-20241121181957-17.png||height="438" width="516"]]
338 338  
339 - image 5.5 extra_lib/CMakeLists.txt before add
552 + image 7.5 extra_lib/CMakeLists.txt before adding
340 340  
341 341  [[image:image-20241121182239-18.png||height="520" width="518"]]
342 342  
343 - image 5.6 extra_lib/CMakeLists.txt after add
556 + image 7.6 extra_lib/CMakeLists.txt after adding
344 344  
345 -**6. Modify header file include in fonts and images directory.** Open the fonts/ui_font_Font12.c file, as shown in image 5.7, then modify the '#include "../ui.h"' to '#include "../ui_water_leak.h"', the image 5.8 is the modified image. Other font file need to be modified in same way.
558 +6.  **Modify the header files included in the fonts and images directories**.
346 346  
560 +Open the **fonts/ui_font_Font12.c** file, as shown in Image 7.7, and change **#include "../ui.h"** to **#include "../ui_water_leak.h"**. The modified file is shown in Image 7.8. Other font files need to be modified in the same way.
561 +
347 347  [[image:image-20241121171629-11.png]]
348 348  
349 - image 5.7 before-modified font file
564 + image 7.7 unmodified font file
350 350  
351 351  [[image:image-20241121171901-12.png]]
352 352  
353 - image 5.8 modified font file
568 + image 7.8 modified font file
354 354  
355 -Open the images/ui_img_battery_empty_png.c file, as shown in image 5.9, then modify the '#include "../ui.h"' to '#include "../ui_water_leak.h"', the image 5.10 is the modified image. Other image file need to be modified in same way.
570 +Open the **images/ui_img_battery_empty_png.c** file, as shown in Image 7.9, and change **#include "../ui.h"** to **#include "../ui_water_leak.h"**. The modified file is shown in Image 7.10. Other image files need to be modified in the same way.
356 356  
357 357  [[image:image-20241121172714-13.png]]
358 358  
359 - image 5.9 before-modified image file
574 + image 7.9 unmodified image file
360 360  
361 361  [[image:image-20241121172908-14.png]]
362 362  
363 - image 5.10 modified image file
578 + image 7.10 modified image file
364 364  
365 -**7. Modify the ui_water_leak/CMakeLists.txt.** Open this file, and modify it from image 5.11 to image 5.12.
580 +7. Modify the **ui_water_leak/CMakeLists.txt**. Open this file, and modify it as shown in image 7.11 (before) and image 7.12 (after).
366 366  
367 367  [[image:image-20241121180030-15.png]]
368 368  
369 - image 5.11 ui_water_leak/CMakeLists.txt before modification
584 + image 7.11 ui_water_leak/CMakeLists.txt before modification
370 370  
371 371  [[image:image-20241121180517-16.png]]
372 372  
373 - image 5.12 ui_water_leak/CMakeLists.txt after modification
588 + image 7.12 ui_water_leak/CMakeLists.txt after modification
374 374  
375 -**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.
376 376  
591 +8. Modify the **ui_water_leak.h** file. Images 7.13 and 7.14 show the code before modification, while Images 7.15 and 7.16 show the code after modification.
592 +
377 377  [[image:image-20241122094200-23.png]]
378 378  
379 - image 5.13 ui_water_leak.h (1) before modification
595 + image 7.13 ui_water_leak.h (1) before modification
380 380  
381 381  [[image:image-20241122094320-24.png||height="852" width="554"]]
382 382  
383 - image 5.14 ui_water_leak.h (2) before modification
599 + image 7.14 ui_water_leak.h (2) before modification
384 384  
385 385  [[image:image-20241122094600-25.png||height="1078" width="554"]]
386 386  
387 - image 5.15 ui_water_leak.h (1) after modification
603 + image 7.15 ui_water_leak.h (1) after modification
388 388  
389 389  [[image:image-20241122094719-26.png||height="941" width="583"]]
390 390  
391 - image 5.16 ui_water_leak.h (2) before modification
607 + image 7.16 ui_water_leak.h (2) before modification
392 392  
393 -**9. Modify ui_water_leak.c file.** The image 5.17, 5.18, 5.19 show the code before modification, and the image 5.20, 5.21, 5.22 show the code after modification.
609 +9. **Modify ui_water_leak.c file.** The image 7.17, 7.18, 7.19 show the code before modification, and the image 7.20, 7.21, 7.22 show the code after modification.
394 394  
395 395  _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.
396 396  
397 397  [[image:image-20241122102929-27.png||height="619" width="426"]]
398 398  
399 - image 5.17 ui_water_leak.c (1) before modification
615 + image 7.17 ui_water_leak.c (1) before modification
400 400  
401 401  [[image:image-20241122112838-30.png||height="551" width="628"]]
402 402  
403 - image 5.18 ui_water_leak.c (2) before modification
619 + image 7.18 ui_water_leak.c (2) before modification
404 404  
405 405  [[image:image-20241122110815-29.png||height="725" width="712"]]
406 406  
407 - image 5.19 ui_water_leak.c (3) before modification
623 + image 7.19 ui_water_leak.c (3) before modification
408 408  
409 409  [[image:image-20241122113158-31.png||height="872" width="677"]]
410 410  
411 - image 5.20 ui_water_leak.c (1) after modification
627 + image 7.20 ui_water_leak.c (1) after modification
412 412  
413 413  [[image:image-20241122113259-33.png||height="874" width="724"]]
414 414  
415 - image 5.21 ui_water_leak.c (2) after modification
631 + image 7.21 ui_water_leak.c (2) after modification
416 416  
417 417  [[image:image-20241122113359-34.png||height="804" width="746"]]
418 418  
419 - image 5.22 ui_water_leak.c (3) after modification
635 + image 7.22 ui_water_leak.c (3) after modification
420 420  
421 -**10. Modify ui_water_leak_events.h file.** The image 5.23 show the code before modification, and the image 5.24 show the code after modification.
637 +10. **Modify ui_water_leak_events.h file.** The image 7.23 show the code before modification, and the image 7.24 show the code after modification.
422 422  
423 423  [[image:image-20241122134113-35.png||height="380" width="421"]]
424 424  
425 - image 5.23 ui_water_leak_events_.h before modification
641 + image 7.23 ui_water_leak_events_.h before modification
426 426  
427 427  [[image:image-20241122134420-37.png||height="201" width="283"]]
428 428  
429 -image 5.24 ui_water_leak_events_.h after modification
645 +image 7.24 ui_water_leak_events_.h after modification
430 430  
431 -**11. Modify ui_water_leak_events.c file.** The image 5.25 show the code before modification, and the image 5.26 show the code after modification.
647 +11.** Modify ui_water_leak_events.c file.** The image 7.25 show the code before modification, and the image 7.26 show the code after modification.
432 432  
433 433  Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
434 434  
... ... @@ -442,14 +442,15 @@
442 442  
443 443  [[image:image-20241122135023-38.png||height="358" width="372"]]
444 444  
445 - image 5.25 ui_water_leak_events_.c before modification
661 + image 7.25 ui_water_leak_events_.c before modification
446 446  
447 447  [[image:image-20241122135258-39.png||height="403" width="559"]]
448 448  
449 - image 5.26 ui_water_leak_events_.c after modification
665 + image 7.26 ui_water_leak_events_.c after modification
450 450  
451 -**12. Modify ui_water_leak_style.c file.**
452 452  
668 +12. **Modify ui_water_leak_style.c file.**
669 +
453 453  Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
454 454  
455 455   add '#include "../../sort.h"'
... ... @@ -458,60 +458,68 @@
458 458  
459 459  [[image:image-20241122141536-41.png||height="361" width="612"]]
460 460  
461 - image 5.27 ui_water_leak_style.c (1) before modification
678 + image 7.27 ui_water_leak_style.c (1) before modification
462 462  
463 463  [[image:image-20241122142129-42.png||height="386" width="613"]]
464 464  
465 - image 5.28 ui_water_leak_style.c (1) after modification
682 + image 7.28 ui_water_leak_style.c (1) after modification
466 466  
684 +
467 467  Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
468 468  
469 - delete code as shown in image 5.29
687 + delete code as shown in image 7.29
470 470  
471 471  [[image:image-20241122145620-44.png||height="757" width="671"]]
472 472  
473 - image 5.29 ui_water_leak_style.c (2)
691 + image 7.29 ui_water_leak_style.c (2)
474 474  
475 -Step3. The image 5.30, 5.31 show the change.
476 476  
694 +Step3. The image 7.30, 7.31 show the change.
695 +
477 477  [[image:image-20241122152026-45.png||height="277" width="828"]]
478 478  
479 - image 5.30 ui_water_leak_style.c (3) before modification
698 + image 7.30 ui_water_leak_style.c (3) before modification
480 480  
481 481  [[image:image-20241122152542-46.png||height="293" width="830"]]
482 482  
483 - image 5.31 ui_water_leak_style.c (3) after modification
702 + image 7.31 ui_water_leak_style.c (3) after modification
484 484  
485 -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).
486 486  
705 +Step4. Copy partly the code in ui_water_leak.c, paste at extra_lib/sort.h(The process is shown in image 7.32, 7.33).
706 +
487 487  [[image:image-20241122153958-47.png]]
488 488  
489 - image 5.32 ui_water_leak_style.c (4)
709 + image 7.32 ui_water_leak_style.c (4)
490 490  
711 +
491 491  [[image:image-20241122154755-49.png||height="864" width="513"]]
492 492  
493 - image 5.33 ui_water_leak_style.c (4)
714 + image 7.33 ui_water_leak_style.c (4)
494 494  
495 -Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
496 496  
717 +Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 7.34).
718 +
497 497  [[image:image-20241122155650-50.png||height="922" width="513"]]
498 498  
499 - image 5.34 ui_water_leak_style.c (5)
721 + image 7.34 ui_water_leak_style.c (5)
500 500  
501 -Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
502 502  
724 +Step6. Add some lines of code in extra_lib/sort.h as shown in image 7.35.
725 +
503 503  [[image:image-20241122161934-51.png]]
504 504  
505 - image 5.35
728 + image 7.35
506 506  
507 -Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
508 508  
731 +Step7. Add a line of code in extra_lib/sort.h as shown in image 7.36.
732 +
509 509  [[image:image-20241122162852-53.png||height="330" width="529"]]
510 510  
511 - image 5.37
735 + image 7.37
512 512  
513 -Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
514 514  
738 +Step8. Add some code in ui_water_leak_style.c as shown in image 7.38 from line534 to line 576 in detail.
739 +
515 515  panel_with_type union_sensor;
516 516  
517 517  union_sensor.panel_type = WATER_LEAK_TYPE;
... ... @@ -524,35 +524,45 @@
524 524  
525 525  return union_sensor;
526 526  
527 -[[image:image-20241122171211-54.png||height="635" width="792"]]
752 +[[image:image-20250122173546-6.png||height="777" width="922"]]
528 528  
529 - image 5.38
754 + image 7.38
530 530  
531 -**13. Modify sort.c file.**
532 532  
533 -Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
757 +13. Rest midification in sort.h file.
534 534  
535 -[[image:image-20241122173718-56.png||height="378" width="579"]]
759 +In image 7.39 as below, we can see "WATER_LEAK_TYPE" at line 24 and water leak switch status definition at line 32,33, and these are what we need to add in sort.h.
536 536  
537 - image 5.39 sort.c (1)
761 +[[image:image-20250122170230-1.png||height="580" width="513"]]
538 538  
763 + image 7.39 sort.h
764 +
765 +13. **Modify sort.c file.**
766 +
767 +Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 26.
768 +
769 +[[image:image-20250122171910-5.png||height="524" width="510"]]
770 +
771 + image 7.40 sort.c (1)
772 +
539 539  There are still some changes need to be done in sort.c, and omit here for the moment.
540 540  
541 541  
542 -= 6. FAQ =
543 543  
544 -== 6.1 ==
777 += 8. FAQ =
545 545  
779 +== 8.1 ==
546 546  
547 -= 7. Order Info =
548 548  
549 -== 7.1  Part Number ==
782 += 9. Order Info =
550 550  
784 +== 9.1  Part Number ==
551 551  
786 +
552 552  Part Number: (% style="color:#4472c4" %)LTS5
553 553  
554 554  
555 -== 7.2  Packing Info ==
790 +== 9.2  Packing Info ==
556 556  
557 557  
558 558  **Package Includes**:
... ... @@ -561,20 +561,20 @@
561 561  * 5V,2A DC Power Adapter.
562 562  * USB Type C Program Cable
563 563  
564 -= 8. Support =
799 += 10. Support =
565 565  
566 566  
567 567  * 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.
568 568  * 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]].
569 569  
570 -= 9.  Reference material =
805 += 11.  Reference material =
571 571  
572 572  
573 573  * Datasheet
574 -* Source Code
809 +* Source Code: [[dragino/LoRa-HMI-Touch-Screen: Open Source LoRa / LoRaWAN HMI Touch Screen Project>>url:https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main]]
575 575  * Mechinical
576 576  
577 -= 10. FCC Warning =
812 += 12. FCC Warning =
578 578  
579 579  
580 580  This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
1738893226894-758.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +25.6 KB
Content
Screenshot 2024-12-24 134818.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +15.0 KB
Content
Screenshot 2024-12-24 134937.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +3.6 KB
Content
Screenshot 2024-12-24 140459.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +12.0 KB
Content
Screenshot 2024-12-24 144005.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +28.0 KB
Content
image-20241226135550-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +293.3 KB
Content
image-20250122170230-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +77.3 KB
Content
image-20250122171809-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +51.1 KB
Content
image-20250122171825-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +51.1 KB
Content
image-20250122171832-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +51.1 KB
Content
image-20250122171910-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +51.1 KB
Content
image-20250122173546-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +200.4 KB
Content
image-20250207100150-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +54.1 KB
Content
image-20250207101415-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +17.6 KB
Content
image-20250207101515-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +24.1 KB
Content
image-20250207142334-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +62.0 KB
Content
image-20250207143131-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +48.7 KB
Content
image-20250207144605-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +58.1 KB
Content
image-20250207164320-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +194.5 KB
Content
image-20250207165702-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +78.1 KB
Content
image-20250207170215-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.6 KB
Content
image-20250207170307-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.2 KB
Content
image-20250207171650-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +11.0 KB
Content
image-20250207171851-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.5 KB
Content
image-20250207172010-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.5 KB
Content
image-20250207172246-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.5 KB
Content
image-20250207172443-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207172821-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +0 bytes
Content
image-20250207172834-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +0 bytes
Content
image-20250207173152-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207173159-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207173206-26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207173212-27.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207192107-28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +14.3 KB
Content
squalreline-trial.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +60.4 KB
Content
squareline-studio-launcher-screen.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +203.4 KB
Content
squareline.io_downloads.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +1.5 MB
Content

Applications

Navigation

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