Skip to Content
Last modified by BoYang Xie on 2025/07/17 15:54
From version 55.1
edited by Edwin Chen
on 2024/10/09 10:25
Change comment: There is no comment for this version
To version 5.1
edited by Edwin Chen
on 2024/09/16 09:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -29,8 +29,7 @@
29 29  
30 30  == 1.2  Features ==
31 31  
32 -* ESP32-WROOM MCU: 8MB RAM & 16MB ROM
33 -* Dragino LA66 LoRa Module
32 +* ESP32-WROOM MCU + Dragino LA66 LoRa Module
34 34  * Support Private LoRa protocol or LoRaWAN protocol
35 35  * Support WiFi & BLE wireless protocol
36 36  * 5.0" HMI touch screen
... ... @@ -41,16 +41,11 @@
41 41  * 5V DC power
42 42  * IP Rating: IP52
43 43  
43 +
44 44  == 1.3  Specification ==
45 45  
46 46  **LoRa**:
47 47  
48 -* Frequency Range: 870 MHz ~~ 960 MHz
49 -* TCXO crystal to ensure RF performance on low temperature
50 -* Maximum Power +22 dBm constant RF output
51 -* High sensitivity: -148 dBm
52 -* LoRa Tx Current: <90 mA at +17 dBm, 108 mA at +22 dBm
53 -* LoRa Rx current: <9 mA
54 54  
55 55  **WiFi:**
56 56  
... ... @@ -74,15 +74,19 @@
74 74  * RGB color.
75 75  * Display Area: 120.7*75.80 mm
76 76  
71 +
72 +
77 77  == 1.4  Power Consumption ==
78 78  
79 79  * External 5V DC power adapter
80 80  
77 +
81 81  == 1.5  Storage & Operation Temperature ==
82 82  
83 83  * Operation Temperature: -20 ~~ 70°C  (No Dew)
84 84  * Storage Temperature: -30 ~~ 70°C  (No Dew)
85 85  
83 +
86 86  == 1.6  Applications ==
87 87  
88 88  * Smart Buildings & Home Automation
... ... @@ -92,188 +92,39 @@
92 92  * Smart Cities
93 93  * Smart Factory
94 94  
95 -= 2.  Getting Started with Hello World =
96 96  
94 += 2.  Getting Start with Hello World =
95 +
97 97  == 2.1  About this demo ==
98 98  
99 -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.
98 +In this Getting Start Example, we will show how to desing 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.
100 100  
100 +
101 101  == 2.2  Install Software Running Environment ==
102 102  
103 -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.
103 +=== 2.2.1 Install Arduino IDE tool ===
104 104  
105 -=== 2.2.1 Install VSCode and ESP-IDF extension ===
106 -
107 -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]].
108 -
109 -Next, you need to install the ESP-IDF extension within VSCode. The detailed operation steps are illustrated in image 1.
110 -
111 -[[image:image-20240928110211-5.png||height="508" width="866"]]
112 -
113 - image 1 ESP-IDF extension install
114 -
115 -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]]
116 -
117 117  === 2.2.2 Install SquareLine Studio ===
118 118  
119 -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]].
120 120  
121 -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.
108 +== 2.3 Program in SquareLine and convert it to ESP32 software ==
122 122  
123 -== 2.3 Simple usage of SquareLine Studio and export UI code ==
124 124  
125 -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.
111 +== 2.4 Upload Firmware to ESP32 ==
126 126  
127 127  
128 -[[image:image-20240928103357-2.png||height="680" width="708"]]
114 +== 2.5 Test Result ==
129 129  
130 - image 2 create a SquareLine project
131 131  
132 -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.
133 -
134 -[[image:1727229582471-566.png]]
135 -
136 - image 3 project settings
137 -
138 -[[image:image-20240928105309-4.png||height="526" width="556"]]
139 -
140 - image 4 modify project settings
141 -
142 -Now we can start to use this software. Here are some usage information for this software.
143 -
144 -**1.add widget**
145 -
146 -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.
147 -
148 -[[image:image-20240928111412-6.png||height="526" width="864"]]
149 -
150 - image 5 add widgets
151 -
152 -**2.modify widget**
153 -
154 -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".
155 -
156 -[[image:1727485118799-984.png]]
157 -
158 - image 6 the button widget's "Inspector" tab
159 -
160 -Second part: "Layout" means a auto position-management for widgets contained in the parent widget. "Transform" includes size, position and align modification.
161 -
162 -[[image:1727485251053-655.png]]
163 -
164 -image 7 the button widget's "BUTTON" tab
165 -
166 -Third part: It is an area of style setting.
167 -
168 -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.
169 -
170 -[[image:1727485480434-713.png||height="395" width="290"]]
171 -
172 - image 8 add event for button
173 -
174 -**3.change label widget content**
175 -
176 -Modify the content in text as shown in image 9, the text content of label widget will be changed accordingly.
177 -
178 -[[image:image-20240928090825-1.png||height="327" width="391"]]
179 -
180 - image 9 modify text content of label widget
181 -
182 -**4.Add image into project**
183 -
184 -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.
185 -
186 -[[image:image-20240928113424-9.png||height="355" width="505"]]
187 -
188 - image 10 add image file into SquareLine Studio project
189 -
190 -[[image:image-20240928114139-10.png||height="559" width="810"]]
191 -
192 - image 11 use image widget in SquareLine Studio
193 -
194 -**5.The relationship between widgets**
195 -
196 -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.
197 -
198 -[[image:1727486567182-334.png||height="318" width="278"]]
199 -
200 -image 12 move label1 to make label1 widget be a child of button1 widget(1)
201 -
202 -[[image:image-20240928112001-8.png||height="431" width="796"]]
203 -
204 - image 13 move label1 to make label1 widget be a child of button1 widget(2)
205 -
206 -**6.Preview the final effect**
207 -
208 -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.
209 -
210 -[[image:1727487368023-281.png]]
211 -
212 - image 14 click on the triangle icon to start or end the simulation
213 -
214 -For more detailed usage, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
215 -
216 -
217 -== 2.4 Integrate UI Code to ESP-IDF Project ==
218 -
219 -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.
220 -
221 -[[image:1727229798126-306.png]]
222 -
223 - image 15 export UI file
224 -
225 -[[image:1727229821582-258.png||height="333" width="662"]]
226 -
227 - image 16 exported UI file
228 -
229 -Create a empty directory entitled "ui" in path "basic_prj/app_components/ui/", and then copy all UI code exported to this directory.
230 -
231 -[[image:image-20240928144830-11.png]]
232 -
233 - image 17 open CMakeLists.txt
234 -
235 -[[image:1727229892636-154.png||height="521" width="407"]]
236 -
237 - image 18 modify CMakeLists.txt
238 -
239 -The last step of integrating is adding two lines of code in main.c file.
240 -
241 -[[image:1727229926561-300.png]]
242 -
243 - image 19 add "ui.h"
244 -
245 -[[image:1727229955611-607.png]]
246 -
247 - image 20 add "ui_init()"
248 -
249 -== 2.5 Brief introduction of hello world project ==
250 -
251 -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.
252 -
253 -== 2.6 Test Result ==
254 -
255 -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.
256 -
257 -[[image:1727488067077-684.png||height="402" width="574"]]
258 -
259 - image 21 screen1
260 -
261 -[[image:1727488157579-949.png||height="397" width="572"]]
262 -
263 - image 22 screen2
264 -
265 265  = 3. Example Project 1: LoRa Central Display =
266 266  
267 -[[image:image-20240916101737-1.png||height="468" width="683"]]
268 268  
120 += 4. Example Project 2: LoRa to LoRaWAN RS485 Alarm =
269 269  
270 270  
271 -= 4. Example Project 2: LoRaWAN RS485 Alarm =
272 -
273 -
274 274  = 6. FAQ =
275 275  
276 -== 6.1 ==
125 +== 6.1 ==
277 277  
278 278  
279 279  = 7. Order Info =
... ... @@ -282,6 +282,7 @@
282 282  
283 283  Part Number: (% style="color:#4472c4" %)LTS5
284 284  
134 +
285 285  
286 286  == 7.2  Packing Info ==
287 287  
... ... @@ -291,11 +291,13 @@
291 291  * 5V,2A DC Power Adapter.
292 292  * USB Type C Program Cable
293 293  
144 +
294 294  = 8. Support =
295 295  
296 296  * 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.
297 297  * 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]].
298 298  
150 +
299 299  = 9.  Reference material =
300 300  
301 301  * Datasheet
... ... @@ -302,6 +302,7 @@
302 302  * Source Code
303 303  * Mechinical
304 304  
157 +
305 305  = 10. FCC Warning =
306 306  
307 307  
1727229396732-319.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -197.2 KB
Content
1727229550717-684.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -113.9 KB
Content
1727229582471-566.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -73.6 KB
Content
1727229618724-758.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -118.7 KB
Content
1727229653254-680.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -116.2 KB
Content
1727229682537-381.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.5 KB
Content
1727229715361-392.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -75.2 KB
Content
1727229740592-843.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -87.3 KB
Content
1727229760857-521.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -24.7 KB
Content
1727229798126-306.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -53.6 KB
Content
1727229821582-258.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -76.1 KB
Content
1727229845835-509.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -68.3 KB
Content
1727229892636-154.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -192.0 KB
Content
1727229926561-300.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -178.0 KB
Content
1727229955611-607.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -100.4 KB
Content
1727229990795-405.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -383.6 KB
Content
1727230012478-930.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -477.1 KB
Content
1727231038705-173.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -94.6 KB
Content
1727233636007-933.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -114.8 KB
Content
1727484665746-713.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -94.9 KB
Content
1727485118799-984.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -11.8 KB
Content
1727485251053-655.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -20.4 KB
Content
1727485480434-713.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -24.7 KB
Content
1727485933579-550.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -55.6 KB
Content
1727485953726-175.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -91.6 KB
Content
1727486567182-334.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -42.6 KB
Content
1727486578489-774.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -66.0 KB
Content
1727487368023-281.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -28.5 KB
Content
1727488067077-684.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -604.7 KB
Content
1727488099947-341.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -877.7 KB
Content
1727488108117-780.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -877.7 KB
Content
1727488157579-949.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -877.7 KB
Content
image-20240916101737-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -156.7 KB
Content
image-20240925110638-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -262.7 KB
Content
image-20240928090825-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -30.2 KB
Content
image-20240928103357-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -153.7 KB
Content
image-20240928103506-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -197.7 KB
Content
image-20240928105309-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -80.2 KB
Content
image-20240928110211-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -228.0 KB
Content
image-20240928111412-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -150.9 KB
Content
image-20240928111654-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -105.4 KB
Content
image-20240928112001-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -75.6 KB
Content
image-20240928113424-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -50.8 KB
Content
image-20240928114139-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -114.3 KB
Content
image-20240928144830-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -25.5 KB
Content