Last modified by BoYang Xie on 2025/05/05 12:26
<
From version < 120.1 >
edited by Dilisi S
on 2024/12/22 15:47
To version < 166.1 >
edited by BoYang Xie
on 2025/02/08 16:46
>
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  
... ... @@ -140,165 +140,218 @@
140 140  === 2.2.2 Install SquareLine Studio ===
141 141  
142 142  
143 -Download and install the latest version of [[SquareLine Studio>>https://squareline.io/downloads#lastRelease]] on your computer. It supports Windows, Linux, and Mac OS. The software version we are using here is 1.4.2.
142 +Download and install the latest version of [[SquareLine Studio>>https://squareline.io/downloads#lastRelease]] on your computer. It supports Windows, Linux, and Mac OS. The software version we are using here is 1.5.0. See the image below.
144 144  
145 -[[image:squareline.io_downloads.png]]
144 +[[image:squareline.io_downloads.png||height="888" width="1294"]]
146 146  
147 147  
148 -After installation, you can use SquareLine Studio as a trial version for 30 days without activation. Click **CONTINUE WITH TRIAL** to use the trial version, or click **LOG IN** to activate the software with your license key.
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  
150 -[[image:squalreline-trial.png||height="602" width="400"]]
149 +* Max. 10 screens
150 +* Max. 150 widgets
151 +* Max. 5 global colors
152 +* Max. 2 themes
153 +* Max. 1 component
151 151  
152 -The free version restricts usage to 1 component, 150 widgets, and 10 screens.
155 +== 2.3 Simple usage of SquareLine Studio and exporting UI code ==
153 153  
154 -== 2.3 Simple usage of SquareLine Studio and export UI code ==
155 155  
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 -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.
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  
159 -[[image:image-20240928103357-2.png||height="680" width="708"]]
163 +[[image:squareline-studio-launcher-screen.png||height="752" width="1415"]]
160 160  
161 - image 2 create a SquareLine project
162 162  
163 -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.
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.
164 164  
165 165  [[image:1727229582471-566.png]]
166 166  
167 - image 3 project settings
168 168  
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 +
169 169  [[image:image-20240928105309-4.png||height="526" width="556"]]
170 170  
171 - image 4 modify project settings
172 172  
173 -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:
174 174  
175 -**~1. add widget**
176 176  
177 -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** ===
178 178  
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 +
179 179  [[image:image-20240928111412-6.png||height="526" width="864"]]
180 180  
181 - image 5 add widgets
182 182  
183 -**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**.
184 184  
185 -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"]]
186 186  
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 +
187 187  [[image:1727485118799-984.png]]
188 188  
189 - image 6 the button widget's "Inspector" tab
190 190  
191 -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** ====
192 192  
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 +
193 193  [[image:1727485251053-655.png]]
194 194  
195 -image 7 the button widget's "BUTTON" tab
196 196  
197 -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.
198 198  
199 -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.
200 200  
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 +
201 201  [[image:1727485480434-713.png||height="395" width="290"]]
202 202  
203 - image 8 add event for button
234 + Image 8: Add an event for the button
204 204  
205 -**3. change label widget content**
206 206  
207 -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** ====
208 208  
239 +
240 +Click the Label you have added to the screen. Under the **Label** section, type "**Click for Detail**" in the **Text** textbox.
241 +
209 209  [[image:image-20240928090825-1.png||height="327" width="391"]]
210 210  
211 - image 9 modify text content of label widget
212 212  
213 -**4. Add image into project**
245 +Once you enter the text, it will immediately appear on the label.
214 214  
215 -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.
216 216  
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 +
217 217  [[image:image-20240928113424-9.png||height="355" width="505"]]
218 218  
219 - image 10 add image file into SquareLine Studio project
220 220  
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 +
221 221  [[image:image-20240928114139-10.png||height="559" width="810"]]
222 222  
223 - image 11 use image widget in SquareLine Studio
224 224  
225 -**5. The relationship between widgets**
263 +==== **The relationship between widgets** ====
226 226  
227 -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.
228 228  
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 +
229 229  [[image:1727486567182-334.png||height="318" width="278"]]
230 230  
231 -image 12 move label1 to make label1 widget be a child of button1 widget(1)
232 232  
274 +Move the label, **Label1** to make it a child of **Button1** as shown in the image below.
275 +
233 233  [[image:image-20240928112001-8.png||height="431" width="796"]]
234 234  
235 - image 13 move label1 to make label1 widget be a child of button1 widget(2)
236 236  
237 -**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.
238 238  
239 -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"]]
240 240  
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 +
241 241  [[image:1727487368023-281.png]]
242 242  
243 - image 14 click on the triangle icon to start or end the simulation
244 244  
245 -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/]].
246 246  
247 247  
248 248  == 2.4 Integrate UI Code to ESP-IDF Project ==
249 249  
250 250  
251 -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.
252 252  
300 +On the  menubar, click **Export -> Export UI** Files as shown in the image below.
301 +
253 253  [[image:1727229798126-306.png]]
254 254  
255 - image 15 export UI file
256 256  
305 +The exported UI files can be found in your SquareLine project folder as shown in the image below.
306 +
307 +
257 257  [[image:1727229821582-258.png||height="333" width="662"]]
258 258  
259 - image 16 exported UI file
260 260  
261 -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.
262 262  
263 263  [[image:image-20240928144830-11.png]]
264 264  
265 - image 17 open CMakeLists.txt
266 266  
316 +Open the **CMakeLists.txt** file and edit it as ahown below.
317 +
267 267  [[image:1727229892636-154.png||height="521" width="407"]]
268 268  
269 - image 18 modify CMakeLists.txt
270 270  
271 -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.
272 272  
323 +Add **#include "ui.h"**
324 +
273 273  [[image:1727229926561-300.png]]
274 274  
275 - image 19 add "ui.h"
276 276  
328 +Add **ui_init();**
329 +
277 277  [[image:1727229955611-607.png]]
278 278  
279 - image 20 add "ui_init()"
280 280  
333 +== 2.5 Brief introduction to the Hello World project ==
281 281  
282 -== 2.5 Brief introduction of hello world project ==
283 283  
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.
284 284  
285 -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.
286 286  
287 -
288 288  == 2.6 Test Result ==
289 289  
290 290  
291 -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.
292 292  
344 +Screen 1:
345 +
293 293  [[image:1727488067077-684.png||height="402" width="574"]]
294 294  
295 - image 21 screen1
296 296  
349 +Screen 2:
350 +
297 297  [[image:1727488157579-949.png||height="397" width="572"]]
298 298  
299 - image 22 screen2
300 300  
301 -
302 302  = 3. Example Project 1: LoRa Central Display =
303 303  
304 304  [[image:image-20240916101737-1.png||height="468" width="683"]]
... ... @@ -306,135 +306,293 @@
306 306  
307 307  = 4. Example Project 2: LoRaWAN RS485 Alarm =
308 308  
309 -= 5.  The way to add a new panel to project =
361 += 5. Example Project 3: P2P =
310 310  
311 -**~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.
312 312  
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 +
313 313  [[image:image-20241121113445-1.png||height="584" width="934"]]
314 314  
315 - image 5.1 a panel about water_leak
520 + Image 7.1: a panel about water_leak
316 316  
317 -**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.
318 318  
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 +
319 319  [[image:image-20241121141120-4.png||height="383" width="795"]]
320 320  
321 - image 5.2 ui files exported
527 + Image 7.2: Exported UI files
322 322  
323 -**3. Delete or rename some file.** Here are the steps:
324 324  
325 - Step1 Delete the 'components' directory.
326 - Step2 Delete 'filelist.txt'.
327 - Step3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
328 - Step4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
329 - Step5 Rename the 'screens' directory to 'styles'.
530 +3. **Delete and rename some file.** Here are the steps:
330 330  
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 +
331 331  [[image:image-20241121151934-10.png||height="303" width="792"]]
332 332  
333 - image 5.3 rest file (1)
540 + image 7.3 rest file (1)
334 334  
335 335  [[image:image-20241121142925-7.png||height="141" width="793"]]
336 336  
337 - image 5.4 rest file (2)
544 + image 7.4 rest file (2)
338 338  
339 -**4. Open this project in vscode.**
546 +4. Open the project in VS Code.
340 340  
341 -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**."
342 342  
343 343  [[image:image-20241121181957-17.png||height="438" width="516"]]
344 344  
345 - image 5.5 extra_lib/CMakeLists.txt before add
552 + image 7.5 extra_lib/CMakeLists.txt before adding
346 346  
347 347  [[image:image-20241121182239-18.png||height="520" width="518"]]
348 348  
349 - image 5.6 extra_lib/CMakeLists.txt after add
556 + image 7.6 extra_lib/CMakeLists.txt after adding
350 350  
351 -**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**.
352 352  
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 +
353 353  [[image:image-20241121171629-11.png]]
354 354  
355 - image 5.7 before-modified font file
564 + image 7.7 unmodified font file
356 356  
357 357  [[image:image-20241121171901-12.png]]
358 358  
359 - image 5.8 modified font file
568 + image 7.8 modified font file
360 360  
361 -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.
362 362  
363 363  [[image:image-20241121172714-13.png]]
364 364  
365 - image 5.9 before-modified image file
574 + image 7.9 unmodified image file
366 366  
367 367  [[image:image-20241121172908-14.png]]
368 368  
369 - image 5.10 modified image file
578 + image 7.10 modified image file
370 370  
371 -**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).
372 372  
373 373  [[image:image-20241121180030-15.png]]
374 374  
375 - image 5.11 ui_water_leak/CMakeLists.txt before modification
584 + image 7.11 ui_water_leak/CMakeLists.txt before modification
376 376  
377 377  [[image:image-20241121180517-16.png]]
378 378  
379 - image 5.12 ui_water_leak/CMakeLists.txt after modification
588 + image 7.12 ui_water_leak/CMakeLists.txt after modification
380 380  
381 -**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.
382 382  
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 +
383 383  [[image:image-20241122094200-23.png]]
384 384  
385 - image 5.13 ui_water_leak.h (1) before modification
595 + image 7.13 ui_water_leak.h (1) before modification
386 386  
387 387  [[image:image-20241122094320-24.png||height="852" width="554"]]
388 388  
389 - image 5.14 ui_water_leak.h (2) before modification
599 + image 7.14 ui_water_leak.h (2) before modification
390 390  
391 391  [[image:image-20241122094600-25.png||height="1078" width="554"]]
392 392  
393 - image 5.15 ui_water_leak.h (1) after modification
603 + image 7.15 ui_water_leak.h (1) after modification
394 394  
395 395  [[image:image-20241122094719-26.png||height="941" width="583"]]
396 396  
397 - image 5.16 ui_water_leak.h (2) before modification
607 + image 7.16 ui_water_leak.h (2) before modification
398 398  
399 -**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.
400 400  
401 401  _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.
402 402  
403 403  [[image:image-20241122102929-27.png||height="619" width="426"]]
404 404  
405 - image 5.17 ui_water_leak.c (1) before modification
615 + image 7.17 ui_water_leak.c (1) before modification
406 406  
407 407  [[image:image-20241122112838-30.png||height="551" width="628"]]
408 408  
409 - image 5.18 ui_water_leak.c (2) before modification
619 + image 7.18 ui_water_leak.c (2) before modification
410 410  
411 411  [[image:image-20241122110815-29.png||height="725" width="712"]]
412 412  
413 - image 5.19 ui_water_leak.c (3) before modification
623 + image 7.19 ui_water_leak.c (3) before modification
414 414  
415 415  [[image:image-20241122113158-31.png||height="872" width="677"]]
416 416  
417 - image 5.20 ui_water_leak.c (1) after modification
627 + image 7.20 ui_water_leak.c (1) after modification
418 418  
419 419  [[image:image-20241122113259-33.png||height="874" width="724"]]
420 420  
421 - image 5.21 ui_water_leak.c (2) after modification
631 + image 7.21 ui_water_leak.c (2) after modification
422 422  
423 423  [[image:image-20241122113359-34.png||height="804" width="746"]]
424 424  
425 - image 5.22 ui_water_leak.c (3) after modification
635 + image 7.22 ui_water_leak.c (3) after modification
426 426  
427 -**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.
428 428  
429 429  [[image:image-20241122134113-35.png||height="380" width="421"]]
430 430  
431 - image 5.23 ui_water_leak_events_.h before modification
641 + image 7.23 ui_water_leak_events_.h before modification
432 432  
433 433  [[image:image-20241122134420-37.png||height="201" width="283"]]
434 434  
435 -image 5.24 ui_water_leak_events_.h after modification
645 +image 7.24 ui_water_leak_events_.h after modification
436 436  
437 -**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.
438 438  
439 439  Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
440 440  
... ... @@ -448,14 +448,15 @@
448 448  
449 449  [[image:image-20241122135023-38.png||height="358" width="372"]]
450 450  
451 - image 5.25 ui_water_leak_events_.c before modification
661 + image 7.25 ui_water_leak_events_.c before modification
452 452  
453 453  [[image:image-20241122135258-39.png||height="403" width="559"]]
454 454  
455 - image 5.26 ui_water_leak_events_.c after modification
665 + image 7.26 ui_water_leak_events_.c after modification
456 456  
457 -**12. Modify ui_water_leak_style.c file.**
458 458  
668 +12. **Modify ui_water_leak_style.c file.**
669 +
459 459  Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
460 460  
461 461   add '#include "../../sort.h"'
... ... @@ -464,60 +464,68 @@
464 464  
465 465  [[image:image-20241122141536-41.png||height="361" width="612"]]
466 466  
467 - image 5.27 ui_water_leak_style.c (1) before modification
678 + image 7.27 ui_water_leak_style.c (1) before modification
468 468  
469 469  [[image:image-20241122142129-42.png||height="386" width="613"]]
470 470  
471 - image 5.28 ui_water_leak_style.c (1) after modification
682 + image 7.28 ui_water_leak_style.c (1) after modification
472 472  
684 +
473 473  Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
474 474  
475 - delete code as shown in image 5.29
687 + delete code as shown in image 7.29
476 476  
477 477  [[image:image-20241122145620-44.png||height="757" width="671"]]
478 478  
479 - image 5.29 ui_water_leak_style.c (2)
691 + image 7.29 ui_water_leak_style.c (2)
480 480  
481 -Step3. The image 5.30, 5.31 show the change.
482 482  
694 +Step3. The image 7.30, 7.31 show the change.
695 +
483 483  [[image:image-20241122152026-45.png||height="277" width="828"]]
484 484  
485 - image 5.30 ui_water_leak_style.c (3) before modification
698 + image 7.30 ui_water_leak_style.c (3) before modification
486 486  
487 487  [[image:image-20241122152542-46.png||height="293" width="830"]]
488 488  
489 - image 5.31 ui_water_leak_style.c (3) after modification
702 + image 7.31 ui_water_leak_style.c (3) after modification
490 490  
491 -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).
492 492  
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 +
493 493  [[image:image-20241122153958-47.png]]
494 494  
495 - image 5.32 ui_water_leak_style.c (4)
709 + image 7.32 ui_water_leak_style.c (4)
496 496  
711 +
497 497  [[image:image-20241122154755-49.png||height="864" width="513"]]
498 498  
499 - image 5.33 ui_water_leak_style.c (4)
714 + image 7.33 ui_water_leak_style.c (4)
500 500  
501 -Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
502 502  
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 +
503 503  [[image:image-20241122155650-50.png||height="922" width="513"]]
504 504  
505 - image 5.34 ui_water_leak_style.c (5)
721 + image 7.34 ui_water_leak_style.c (5)
506 506  
507 -Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
508 508  
724 +Step6. Add some lines of code in extra_lib/sort.h as shown in image 7.35.
725 +
509 509  [[image:image-20241122161934-51.png]]
510 510  
511 - image 5.35
728 + image 7.35
512 512  
513 -Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
514 514  
731 +Step7. Add a line of code in extra_lib/sort.h as shown in image 7.36.
732 +
515 515  [[image:image-20241122162852-53.png||height="330" width="529"]]
516 516  
517 - image 5.37
735 + image 7.37
518 518  
519 -Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
520 520  
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 +
521 521  panel_with_type union_sensor;
522 522  
523 523  union_sensor.panel_type = WATER_LEAK_TYPE;
... ... @@ -530,35 +530,45 @@
530 530  
531 531  return union_sensor;
532 532  
533 -[[image:image-20241122171211-54.png||height="635" width="792"]]
752 +[[image:image-20250122173546-6.png||height="777" width="922"]]
534 534  
535 - image 5.38
754 + image 7.38
536 536  
537 -**13. Modify sort.c file.**
538 538  
539 -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.
540 540  
541 -[[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.
542 542  
543 - image 5.39 sort.c (1)
761 +[[image:image-20250122170230-1.png||height="580" width="513"]]
544 544  
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 +
545 545  There are still some changes need to be done in sort.c, and omit here for the moment.
546 546  
547 547  
548 -= 6. FAQ =
549 549  
550 -== 6.1 ==
777 += 8. FAQ =
551 551  
779 +== 8.1 ==
552 552  
553 -= 7. Order Info =
554 554  
555 -== 7.1  Part Number ==
782 += 9. Order Info =
556 556  
784 +== 9.1  Part Number ==
557 557  
786 +
558 558  Part Number: (% style="color:#4472c4" %)LTS5
559 559  
560 560  
561 -== 7.2  Packing Info ==
790 +== 9.2  Packing Info ==
562 562  
563 563  
564 564  **Package Includes**:
... ... @@ -567,20 +567,20 @@
567 567  * 5V,2A DC Power Adapter.
568 568  * USB Type C Program Cable
569 569  
570 -= 8. Support =
799 += 10. Support =
571 571  
572 572  
573 573  * 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.
574 574  * 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]].
575 575  
576 -= 9.  Reference material =
805 += 11.  Reference material =
577 577  
578 578  
579 579  * Datasheet
580 -* 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]]
581 581  * Mechinical
582 582  
583 -= 10. FCC Warning =
812 += 12. FCC Warning =
584 584  
585 585  
586 586  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
squareline-studio-launcher-screen.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +203.4 KB
Content

Applications

Navigation

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