Last modified by Dilisi S on 2025/02/26 19:24
<
From version < 165.2 >
edited by BoYang Xie
on 2025/02/08 14:35
To version < 115.1 >
edited by Xiaoling
on 2024/12/17 17:47
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.xieby
1 +XWiki.Xiaoling
Content
... ... @@ -1,11 +3,12 @@
1 -
2 -
3 3  (% style="text-align:center" %)
4 -[[image:image-20241226135550-1.png]]
2 +[[image:image-20240915231842-1.png]]
5 5  
6 6  
7 7  
8 8  
7 +
8 +
9 +
9 9  (% _mstvisible="1" %)
10 10  (% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:**
11 11  
... ... @@ -20,17 +20,18 @@
20 20  
21 21  = 1.  Introduction =
22 22  
23 -== 1.1  What is the LTS5 LoRa HMI Touch Screen? ==
24 +== 1.1  What is LTS5 LoRa HMI touch screen ==
24 24  
25 25  
26 -The LTS5 is a (% style="color:blue" %)**LoRa / LoRaWAN HMI Touch Screen**(%%) designed for displaying information in IoT projects. It features a **5.0-inch HMI touch screen** and supports **Wi-Fi**, **Bluetooth**, and **LoRa** wireless protocols.
27 +LTS5 is a (% style="color:blue" %)**LoRa / LoRaWAN HMI Touch Screen**(%%) designed for display purpose of IoT project. It have a **5.0" HMI touch screen**, and **support WiFi, Bluetooch, LoRa wireless protocol**.
27 27  
28 -The LTS5 is an open-source software project powered by an **ESP32 MCU** and a **Dragino LA66 LoRa** module. The extensive development resources available for ESP32 can significantly reduce development time.
29 +LTS5 is an Open Source software project. The MCU is ESP32 and Dragino LA66 LoRa module. There are lots of development source for ESP32 which can greatly reduce the development time.
29 29  
30 -The LTS5's HMI touch screen supports **drag-and-drop** design, allowing developers to use SquareLine to easily customize the display UI for various applications.
31 +The HMI touch screen of LTS5 **supports drap & drop design**. Developer can use SquareLine to easily customize the display UI for different application.
31 31  
32 -The LA66 LoRa module can be programmed to support either private LoRa protocols or the LoRaWAN protocol.
33 +LTS5 use LA66 LoRa module, this module can be program to support private LoRa protocol or LoRaWAN protocol.
33 33  
35 +
34 34  == 1.2  Features ==
35 35  
36 36  
... ... @@ -46,7 +46,7 @@
46 46  * 5V DC power
47 47  * IP Rating: IP52
48 48  
49 -== 1.3  Specifications ==
51 +== 1.3  Specification ==
50 50  
51 51  
52 52  **LoRa**:
... ... @@ -85,6 +85,7 @@
85 85  
86 86  * External 5V DC power adapter
87 87  
90 +
88 88  == 1.5  Storage & Operation Temperature ==
89 89  
90 90  
... ... @@ -91,6 +91,7 @@
91 91  * Operation Temperature: -20 ~~ 70°C  (No Dew)
92 92  * Storage Temperature: -30 ~~ 70°C  (No Dew)
93 93  
97 +
94 94  == 1.6  Applications ==
95 95  
96 96  
... ... @@ -101,37 +101,31 @@
101 101  * Smart Cities
102 102  * Smart Factory
103 103  
104 -= 2.  Getting Started with 'Hello World' =
105 105  
109 += 2.  Getting Started with Hello World =
110 +
106 106  == 2.1  About this demo ==
107 107  
108 108  
109 -This getting started example demonstrates how to design and deploy a simple display UI for the LTS5 device. The example includes:
114 +In this Getting Started Example, we will show how to design a simple Display UI and upload it to LTS5. This UI has  a button , when user click the button. The Web UI will jump to a new page.
110 110  
111 -* Creating a basic UI with a single button.
112 -* Implementing functionality to navigate the Web UI to a new page when the button is clicked.
113 -* Uploading the UI to the LTS5 device.
114 114  
115 -By completing this demo, you will gain foundational knowledge for customizing the LTS5 interface and building more advanced IoT applications.
116 -
117 -
118 118  == 2.2  Install Software Running Environment ==
119 119  
120 120  
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.
120 +The ESP MCU can be developed using ESP-IDF, Arduino, or MicroPython. For this project, we utilize ESP-IDF for compilation and Visual Studio Code (VSCode) for editing.
122 122  
123 123  
124 -=== 2.2.1 Install VS Code and ESP-IDF extension ===
123 +=== 2.2.1 Install VSCode and ESP-IDF extension ===
125 125  
126 126  
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]].
126 +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]].
128 128  
129 -Next, install the **ESP-IDF** extension within **VS Code**. Detailed steps for this process are shown in Image 1.
128 +Next, you need to install the ESP-IDF extension within VSCode. The detailed operation steps are illustrated in image 1.
130 130  
131 -
132 132  [[image:image-20240928110211-5.png||height="508" width="866"]]
133 133  
134 - Image 1: ESP-IDF extension install
132 + image 1 ESP-IDF extension install
135 135  
136 136  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]]
137 137  
... ... @@ -139,218 +139,159 @@
139 139  === 2.2.2 Install SquareLine Studio ===
140 140  
141 141  
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.
140 +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]].
143 143  
144 -[[image:squareline.io_downloads.png||height="888" width="1294"]]
142 +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.
145 145  
146 146  
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:
145 +== 2.3 Simple usage of SquareLine Studio and export UI code ==
148 148  
149 -* Max. 10 screens
150 -* Max. 150 widgets
151 -* Max. 5 global colors
152 -* Max. 2 themes
153 -* Max. 1 component
154 154  
155 -== 2.3 Simple usage of SquareLine Studio and exporting UI code ==
148 +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.
156 156  
150 +[[image:image-20240928103357-2.png||height="680" width="708"]]
157 157  
158 -Start the SquareLine Studio. The **launcher screen** appears as shown in the below image. You can create a new project by clicking **Create** in the top menu. Then select the **Desktop** tab. Select the development platform, **Eclipse with  SDL for development on PC**.
152 + image 2 create a SquareLine project
159 159  
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.
154 +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.
162 162  
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 -
168 168  [[image:1727229582471-566.png]]
169 169  
158 + image 3 project settings
170 170  
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 -
177 177  [[image:image-20240928105309-4.png||height="526" width="556"]]
178 178  
162 + image 4 modify project settings
179 179  
180 -Now you can start building the user interface. Follow the steps below:
164 +Now we can start to use this software. Here are some usage information for this software.
181 181  
166 +**~1. add widget**
182 182  
183 -=== **Add widgets** ===
168 +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.
184 184  
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 -
188 188  [[image:image-20240928111412-6.png||height="526" width="864"]]
189 189  
172 + image 5 add widgets
190 190  
191 -Then click the **Screen **widget to add the second screen. After adding the second screen, it will appear in the Screens panel as **Screen2**.
174 +**2. modify widget**
192 192  
193 -[[image:Screenshot 2024-12-24 140459.png||height="278" width="290"]]
176 +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".
194 194  
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 -
200 200  [[image:1727485118799-984.png]]
201 201  
180 + image 6 the button widget's "Inspector" tab
202 202  
203 -==== **Changing the Button properties** ====
182 +Second part: "Layout" means a auto position-management for widgets contained in the parent widget. "Transform" includes size, position and align modification.
204 204  
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 -
216 216  [[image:1727485251053-655.png]]
217 217  
186 +image 7 the button widget's "BUTTON" tab
218 218  
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.
188 +Third part: It is an area of style setting.
220 220  
221 -* Click **ADD EVENT** button. A new section will appear to configure this event.
190 +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.
222 222  
223 -[[image:Screenshot 2024-12-24 134937.png||height="80" width="290"]]
224 -
225 -* Select **CLICKED** from the dropdown under **Trigger**. Choose **CHANGE SCREEN** under **Action**, then click the **ADD** button. A new section will appear to configure the action.
226 -
227 -[[image:Screenshot 2024-12-24 134818.png||height="222" width="290"]]
228 -
229 -* Select **Screen2** under **Screen to**. Select **FADE ON** from **Fade mode**. The default value **500** means the transition takes 500 milliseconds to appear the Screen2.
230 -* Finally, click the **ADD** button.
231 -
232 232  [[image:1727485480434-713.png||height="395" width="290"]]
233 233  
234 - Image 8: Add an event for the button
194 + image 8 add event for button
235 235  
196 +**3. change label widget content**
236 236  
237 -==== **Changing the label properties** ====
198 +Modify the content in text as shown in image 9, the text content of label widget will be changed accordingly.
238 238  
239 -
240 -Click the Label you have added to the screen. Under the **Label** section, type "**Click for Detail**" in the **Text** textbox.
241 -
242 242  [[image:image-20240928090825-1.png||height="327" width="391"]]
243 243  
202 + image 9 modify text content of label widget
244 244  
245 -Once you enter the text, it will immediately appear on the label.
204 +**4. Add image into project**
246 246  
206 +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.
247 247  
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 -
255 255  [[image:image-20240928113424-9.png||height="355" width="505"]]
256 256  
210 + image 10 add image file into SquareLine Studio project
257 257  
258 -The other way is to click the "**ADD FILE INTO ASSETS**" button, then select an image from your computer to import. After adding, you can see the image in the "**assets**" panel in SquareLine Studio, as shown in the image below.
259 -
260 260  [[image:image-20240928114139-10.png||height="559" width="810"]]
261 261  
214 + image 11 use image widget in SquareLine Studio
262 262  
263 -==== **The relationship between widgets** ====
216 +**5. The relationship between widgets**
264 264  
218 +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.
265 265  
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 -
271 271  [[image:1727486567182-334.png||height="318" width="278"]]
272 272  
222 +image 12 move label1 to make label1 widget be a child of button1 widget(1)
273 273  
274 -Move the label, **Label1** to make it a child of **Button1** as shown in the image below.
275 -
276 276  [[image:image-20240928112001-8.png||height="431" width="796"]]
277 277  
226 + image 13 move label1 to make label1 widget be a child of button1 widget(2)
278 278  
279 -Then set the **X** and **Y** position of the label to **0** as shown in the image below. The label will appear on the button. If you move the button on the screen, the label will move along with it as part of the button.
228 +**6. Preview the final effect**
280 280  
281 -[[image:Screenshot 2024-12-24 144005.png||height="360" width="290"]]
230 +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.
282 282  
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 -
289 289  [[image:1727487368023-281.png]]
290 290  
234 + image 14 click on the triangle icon to start or end the simulation
291 291  
292 -For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
236 +For more detailed usage, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
293 293  
294 294  
295 295  == 2.4 Integrate UI Code to ESP-IDF Project ==
296 296  
297 297  
298 -To integrate, first export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
242 +To achieve the integrating, we first need to export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
299 299  
300 -On the  menubar, click **Export -> Export UI** Files as shown in the image below.
301 -
302 302  [[image:1727229798126-306.png]]
303 303  
246 + image 15 export UI file
304 304  
305 -The exported UI files can be found in your SquareLine project folder as shown in the image below.
306 -
307 -
308 308  [[image:1727229821582-258.png||height="333" width="662"]]
309 309  
250 + image 16 exported UI file
310 310  
311 -Create a new folder named "**ui**" at path "**basic_prj/app_components/ui/**", and copy all the exported UI code into it as shown in the image below.
252 +Create a empty directory entitled "ui" in path "basic_prj/app_components/ui/", and then copy all UI code exported to this directory.
312 312  
313 313  [[image:image-20240928144830-11.png]]
314 314  
256 + image 17 open CMakeLists.txt
315 315  
316 -Open the **CMakeLists.txt** file and edit it as ahown below.
317 -
318 318  [[image:1727229892636-154.png||height="521" width="407"]]
319 319  
260 + image 18 modify CMakeLists.txt
320 320  
321 -Open the main.c file and  add two lines of code as shown in the below images.
262 +The last step of integrating is adding two lines of code in main.c file.
322 322  
323 -Add **#include "ui.h"**
324 -
325 325  [[image:1727229926561-300.png]]
326 326  
266 + image 19 add "ui.h"
327 327  
328 -Add **ui_init();**
329 -
330 330  [[image:1727229955611-607.png]]
331 331  
270 + image 20 add "ui_init()"
332 332  
333 -== 2.5 Brief introduction to the Hello World project ==
334 334  
273 +== 2.5 Brief introduction of hello world project ==
335 335  
336 -The project consists of two screens. The first screen displays the company's logo, the project name, and a button to navigate to the next screen. The second screen provides information about the HMI screen product through an image and includes a button to return to the previous screen.
337 337  
276 +The project consists of two screens. The first screen displays the company's logo, the project name, and a button to navigate to the next screen. The second screen presents some information about this HMI screen product through an image and includes a button to return to the previous screen.
338 338  
278 +
339 339  == 2.6 Test Result ==
340 340  
341 341  
342 -By pressing the button located at the bottom right, the screen switches to the next one as expected. This confirms that the UI file has been successfully integrated into the project and is functioning correctly.
282 +By pressing the button lying bottom right, the screen can switch to another as expected. This indicates that the UI file has been successfully integrated into the project and is now effective.
343 343  
344 -Screen 1:
345 -
346 346  [[image:1727488067077-684.png||height="402" width="574"]]
347 347  
286 + image 21 screen1
348 348  
349 -Screen 2:
350 -
351 351  [[image:1727488157579-949.png||height="397" width="572"]]
352 352  
290 + image 22 screen2
353 353  
292 +
354 354  = 3. Example Project 1: LoRa Central Display =
355 355  
356 356  [[image:image-20240916101737-1.png||height="468" width="683"]]
... ... @@ -358,183 +358,28 @@
358 358  
359 359  = 4. Example Project 2: LoRaWAN RS485 Alarm =
360 360  
361 -= 5. Example Project 3: P2P =
300 += 5.  The way to add a new panel to project =
362 362  
363 -The project achieves the function of receiving LoRa P2P messages and displaying them on the screen. The workflow is as follows: A LA66, running a P2P program, sends a message in a particular format via an AT command. Then, the LTS5 receives the message and displays it on the screen.
302 +**~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.**
364 364  
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>>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 about TTN downlink panel data to display on 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 batches~-~-DEUI, Dev Name, 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 a 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 -= 5. 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 5.1 below for reference.
517 -
518 518  [[image:image-20241121113445-1.png||height="584" width="934"]]
519 519  
520 - Image 5.1: a panel about water_leak
306 + image 5.1 a panel about water_leak
521 521  
308 +**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.
522 522  
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 5.2.
524 -
525 525  [[image:image-20241121141120-4.png||height="383" width="795"]]
526 526  
527 - Image 5.2: Exported UI files
312 + image 5.2 ui files exported
528 528  
314 +**3. Delete or rename some file.** Here are the steps:
529 529  
530 -3. **Delete and rename some file.** Here are the steps:
316 + Step1 Delete the 'components' directory.
317 + Step2 Delete 'filelist.txt'.
318 + Step3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
319 + Step4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
320 + Step5 Rename the 'screens' directory to 'styles'.
531 531  
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 -
538 538  [[image:image-20241121151934-10.png||height="303" width="792"]]
539 539  
540 540   image 5.3 rest file (1)
... ... @@ -543,9 +543,9 @@
543 543  
544 544   image 5.4 rest file (2)
545 545  
546 -4. Open the project in **VS Code**.
330 +**4. Open this project in vscode.**
547 547  
548 -5. Add the file include path for **water_leak** in **extra_lib/CMakeLists.txt**, as shown in Images 5.5 and 5.6. Its format is similar to that of **tem_hum** or **door**."
332 +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.
549 549  
550 550  [[image:image-20241121181957-17.png||height="438" width="516"]]
551 551  
... ... @@ -555,10 +555,8 @@
555 555  
556 556   image 5.6 extra_lib/CMakeLists.txt after add
557 557  
558 -6.  **Modify the header files included in the fonts and images directories**.
342 +**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.
559 559  
560 -Open the **fonts/ui_font_Font12.c** file, as shown in Image 5.7, and change **#include "../ui.h"** to **#include "../ui_water_leak.h"**. The modified file is shown in Image 5.8. Other font files need to be modified in the same way.
561 -
562 562  [[image:image-20241121171629-11.png]]
563 563  
564 564   image 5.7 before-modified font file
... ... @@ -567,7 +567,7 @@
567 567  
568 568   image 5.8 modified font file
569 569  
570 -Open the **images/ui_img_battery_empty_png.c** file, as shown in Image 5.9, and change **#include "../ui.h"** to **#include "../ui_water_leak.h"**. The modified file is shown in Image 5.10. Other image files need to be modified in the same way.
352 +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.
571 571  
572 572  [[image:image-20241121172714-13.png]]
573 573  
... ... @@ -577,7 +577,7 @@
577 577  
578 578   image 5.10 modified image file
579 579  
580 -7. Modify the **ui_water_leak/CMakeLists.txt**. Open this file, and modify it as shown in image 5.11 (before) and image 5.12 (after).
362 +**7. Modify the ui_water_leak/CMakeLists.txt.** Open this file, and modify it from image 5.11 to image 5.12.
581 581  
582 582  [[image:image-20241121180030-15.png]]
583 583  
... ... @@ -587,9 +587,8 @@
587 587  
588 588   image 5.12 ui_water_leak/CMakeLists.txt after modification
589 589  
372 +**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.
590 590  
591 -8. Modify the **ui_water_leak.h** file. Images 5.13 and 5.14 show the code before modification, while Images 5.15 and 5.16 show the code after modification.
592 -
593 593  [[image:image-20241122094200-23.png]]
594 594  
595 595   image 5.13 ui_water_leak.h (1) before modification
... ... @@ -606,7 +606,7 @@
606 606  
607 607   image 5.16 ui_water_leak.h (2) before modification
608 608  
609 -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.
390 +**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.
610 610  
611 611  _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.
612 612  
... ... @@ -634,7 +634,7 @@
634 634  
635 635   image 5.22 ui_water_leak.c (3) after modification
636 636  
637 -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.
418 +**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.
638 638  
639 639  [[image:image-20241122134113-35.png||height="380" width="421"]]
640 640  
... ... @@ -644,7 +644,7 @@
644 644  
645 645  image 5.24 ui_water_leak_events_.h after modification
646 646  
647 -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.
428 +**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.
648 648  
649 649  Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
650 650  
... ... @@ -664,9 +664,8 @@
664 664  
665 665   image 5.26 ui_water_leak_events_.c after modification
666 666  
448 +**12. Modify ui_water_leak_style.c file.**
667 667  
668 -12. **Modify ui_water_leak_style.c file.**
669 -
670 670  Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
671 671  
672 672   add '#include "../../sort.h"'
... ... @@ -681,7 +681,6 @@
681 681  
682 682   image 5.28 ui_water_leak_style.c (1) after modification
683 683  
684 -
685 685  Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
686 686  
687 687   delete code as shown in image 5.29
... ... @@ -690,7 +690,6 @@
690 690  
691 691   image 5.29 ui_water_leak_style.c (2)
692 692  
693 -
694 694  Step3. The image 5.30, 5.31 show the change.
695 695  
696 696  [[image:image-20241122152026-45.png||height="277" width="828"]]
... ... @@ -701,7 +701,6 @@
701 701  
702 702   image 5.31 ui_water_leak_style.c (3) after modification
703 703  
704 -
705 705  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).
706 706  
707 707  [[image:image-20241122153958-47.png]]
... ... @@ -708,12 +708,10 @@
708 708  
709 709   image 5.32 ui_water_leak_style.c (4)
710 710  
711 -
712 712  [[image:image-20241122154755-49.png||height="864" width="513"]]
713 713  
714 714   image 5.33 ui_water_leak_style.c (4)
715 715  
716 -
717 717  Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
718 718  
719 719  [[image:image-20241122155650-50.png||height="922" width="513"]]
... ... @@ -720,7 +720,6 @@
720 720  
721 721   image 5.34 ui_water_leak_style.c (5)
722 722  
723 -
724 724  Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
725 725  
726 726  [[image:image-20241122161934-51.png]]
... ... @@ -727,7 +727,6 @@
727 727  
728 728   image 5.35
729 729  
730 -
731 731  Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
732 732  
733 733  [[image:image-20241122162852-53.png||height="330" width="529"]]
... ... @@ -734,7 +734,6 @@
734 734  
735 735   image 5.37
736 736  
737 -
738 738  Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
739 739  
740 740  panel_with_type union_sensor;
... ... @@ -749,31 +749,21 @@
749 749  
750 750  return union_sensor;
751 751  
752 -[[image:image-20250122173546-6.png||height="777" width="922"]]
524 +[[image:image-20241122171211-54.png||height="635" width="792"]]
753 753  
754 754   image 5.38
755 755  
528 +**13. Modify sort.c file.**
756 756  
757 -13. Rest midification in sort.h file.
530 +Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
758 758  
759 -In image 5.39 as below, we can see "WATER_LEAK_TYPE" at line 24 and water leak switch status definition at line 32,33, and these are what we need to add in sort.h.
532 +[[image:image-20241122173718-56.png||height="378" width="579"]]
760 760  
761 -[[image:image-20250122170230-1.png||height="580" width="513"]]
534 + image 5.39 sort.c (1)
762 762  
763 - image 5.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 5.40 sort.c (1)
772 -
773 773  There are still some changes need to be done in sort.c, and omit here for the moment.
774 774  
775 775  
776 -
777 777  = 6. FAQ =
778 778  
779 779  == 6.1 ==
... ... @@ -806,7 +806,7 @@
806 806  
807 807  
808 808  * Datasheet
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]]
571 +* Source Code
810 810  * Mechinical
811 811  
812 812  = 10. FCC Warning =
1738893226894-758.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -25.6 KB
Content
Screenshot 2024-12-24 134818.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -15.0 KB
Content
Screenshot 2024-12-24 134937.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -3.6 KB
Content
Screenshot 2024-12-24 140459.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -12.0 KB
Content
Screenshot 2024-12-24 144005.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -28.0 KB
Content
image-20241226135550-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -293.3 KB
Content
image-20250122170230-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -77.3 KB
Content
image-20250122171809-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20250122171825-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20250122171832-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20250122171910-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20250122173546-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -200.4 KB
Content
image-20250207100150-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -54.1 KB
Content
image-20250207101415-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -17.6 KB
Content
image-20250207101515-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -24.1 KB
Content
image-20250207142334-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -62.0 KB
Content
image-20250207143131-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -48.7 KB
Content
image-20250207144605-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -58.1 KB
Content
image-20250207164320-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -194.5 KB
Content
image-20250207165702-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -78.1 KB
Content
image-20250207170215-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.6 KB
Content
image-20250207170307-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.2 KB
Content
image-20250207171650-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -11.0 KB
Content
image-20250207171851-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.5 KB
Content
image-20250207172010-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.5 KB
Content
image-20250207172246-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.5 KB
Content
image-20250207172443-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207172821-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -0 bytes
Content
image-20250207172834-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -0 bytes
Content
image-20250207173152-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207173159-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207173206-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207173212-27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207192107-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -14.3 KB
Content
squalreline-trial.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -60.4 KB
Content
squareline-studio-launcher-screen.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -203.4 KB
Content
squareline.io_downloads.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -1.5 MB
Content

Applications

Navigation

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