Skip to Content
Last modified by BoYang Xie on 2025/07/17 15:54
From version 122.1
edited by Dilisi S
on 2024/12/23 04:44
Change comment: Dec 22 edits - part 3
To version 26.1
edited by BoYang Xie
on 2024/09/25 10:23
Change comment: Uploaded new attachment "1727231038705-173.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.pradeeka
1 +XWiki.xieby
Content
... ... @@ -1,14 +1,9 @@
1 -(% style="text-align:center" %)
1 +
2 2  [[image:image-20240915231842-1.png]]
3 3  
4 4  
5 -
6 -
7 -
8 -
9 -
10 10  (% _mstvisible="1" %)
11 -(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:**
6 +(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents：**
12 12  
13 13  {{toc/}}
14 14  
... ... @@ -21,22 +21,20 @@
21 21  
22 22  = 1.  Introduction =
23 23  
24 -== 1.1  What is the LTS5 LoRa HMI Touch Screen? ==
19 +== 1.1  What is LTS5 LoRa HMI touch screen ==
25 25  
21 +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.
26 26  
27 -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.
23 +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.
28 28  
29 -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.
25 +The HMI touch screen of LTS5 supports drap & drop design. Developer can use SquareLine to easily customize the display UI for different application.
30 30  
31 -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.
27 +LTS5 use LA66 LoRa module, this module can be program to support private LoRa protocol or LoRaWAN protocol.
32 32  
33 -The LA66 LoRa module can be programmed to support either private LoRa protocols or the LoRaWAN protocol.
34 34  
35 35  == 1.2  Features ==
36 36  
37 -
38 -* ESP32-WROOM MCU: 8MB RAM & 16MB ROM
39 -* Dragino LA66 LoRa Module
32 +* ESP32-WROOM MCU + Dragino LA66 LoRa Module
40 40  * Support Private LoRa protocol or LoRaWAN protocol
41 41  * Support WiFi & BLE wireless protocol
42 42  * 5.0" HMI touch screen
... ... @@ -47,17 +47,10 @@
47 47  * 5V DC power
48 48  * IP Rating: IP52
49 49  
50 -== 1.3  Specifications ==
43 +== 1.3  Specification ==
51 51  
52 -
53 53  **LoRa**:
54 54  
55 -* Frequency Range: 870 MHz ~~ 960 MHz
56 -* TCXO crystal to ensure RF performance on low temperature
57 -* Maximum Power +22 dBm constant RF output
58 -* High sensitivity: -148 dBm
59 -* LoRa Tx Current: <90 mA at +17 dBm, 108 mA at +22 dBm
60 -* LoRa Rx current: <9 mA
61 61  
62 62  **WiFi:**
63 63  
... ... @@ -83,18 +83,15 @@
83 83  
84 84  == 1.4  Power Consumption ==
85 85  
86 -
87 87  * External 5V DC power adapter
88 88  
89 89  == 1.5  Storage & Operation Temperature ==
90 90  
91 -
92 92  * Operation Temperature: -20 ~~ 70°C  (No Dew)
93 93  * Storage Temperature: -30 ~~ 70°C  (No Dew)
94 94  
95 95  == 1.6  Applications ==
96 96  
97 -
98 98  * Smart Buildings & Home Automation
99 99  * Logistics and Supply Chain Management
100 100  * Smart Metering
... ... @@ -102,483 +102,38 @@
102 102  * Smart Cities
103 103  * Smart Factory
104 104  
105 -= 2.  Getting Started with 'Hello World' =
88 += 2.  Getting Start with Hello World =
106 106  
107 107  == 2.1  About this demo ==
108 108  
92 +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.
109 109  
110 -This getting started example demonstrates how to design and deploy a simple display UI for the LTS5 device. The example includes:
111 111  
112 -* Creating a basic UI with a single button.
113 -* Implementing functionality to navigate the Web UI to a new page when the button is clicked.
114 -* Uploading the UI to the LTS5 device.
115 -
116 -By completing this demo, you will gain foundational knowledge for customizing the LTS5 interface and building more advanced IoT applications.
117 -
118 -
119 119  == 2.2  Install Software Running Environment ==
120 120  
97 +=== 2.2.1 Install ESP-IDF tool ===
121 121  
122 -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.
123 -
124 -
125 -=== 2.2.1 Install VS Code and ESP-IDF extension ===
126 -
127 -
128 -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]].
129 -
130 -Next, install the **ESP-IDF** extension within **VS Code**. Detailed steps for this process are shown in Image 1.
131 -
132 -
133 -[[image:image-20240928110211-5.png||height="508" width="866"]]
134 -
135 - Image 1: ESP-IDF extension install
136 -
137 -Links for reference: [[Install ESP32 ESP-IDF on Windows and Integrate with VS code (esp32tutorials.com)>>url:https://esp32tutorials.com/install-esp32-esp-idf-windows-integrate-vs-code/#:~~:text=In%20this%20tutorial,%20we%20will%20show%20you%20how%20to%20install]]
138 -
139 -
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.
102 +== 2.3 Program in SquareLine and get UI code ==
144 144  
145 -[[image:squareline.io_downloads.png]]
146 146  
105 +== 2.4 Intergrate UI Code to ESP32 ==
147 147  
148 -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 -* Max. 10 screens
151 -* Max. 150 widgets
152 -* Max. 5 global colors
153 -* Max. 2 themes
154 -* Max. 1 component
108 +== 2.5 Test Result ==
155 155  
156 -== 2.3 Simple usage of SquareLine Studio and exporting UI code ==
157 157  
158 -
159 -After launching and logging into the software, create a new project as shown in Image 2.
160 -
161 -* Select the major **LVGL** version as **8.3**.
162 -* Select the **Desktop** tab.
163 -* Select  **Eclipse with  SDL for  development on PC**:
164 -* In the **PROJECT SETTINGS**, select **LVGL version** **8.3.11**
165 -* Select the **CREATE **button.
166 -
167 -[[image:image-20240928103357-2.png||height="680" width="708"]]
168 -
169 - Image 2: Creating a new SquareLine project
170 -
171 -
172 -Next, you need to configure some settings for this project. By clicking in the specified order shown in Image 3, you will be directed to the page displayed in Image 4.
173 -
174 -* Select** File  -> Project Settings**
175 -
176 -[[image:1727229582471-566.png]]
177 -
178 - Image 3 accessing project settings
179 -
180 -
181 -In the PROJECT SETTINGS dialog box, configure/modify the project settings:
182 -
183 -* **UI Files Export Root**: Select a folder on your computer to store the UI files.
184 -* **LVGL Include Path**: Set this to **lvgl.h**
185 -* **Click on the APPLY CHANGES button.**
186 -
187 -[[image:image-20240928105309-4.png||height="526" width="556"]]
188 -
189 - Image 4 Configure/modify project settings
190 -
191 -
192 -Now you can start building the sample UI. Follow the steps below:
193 -
194 -
195 -=== Add widgets ===
196 -
197 -To add widgets navigate to the **Widgets** area, then click on the widgets you want to add. The selected widgets will be added to the screen. You can reposition the widgets in the screen area by clicking and dragging them.
198 -
199 -Add a Label, Button, and Image to the screen as shown in **Image 5**.
200 -
201 -[[image:image-20240928111412-6.png||height="526" width="864"]]
202 -
203 - Image 5: Add widgets
204 -
205 -=== Modify widget properties ===
206 -
207 -The area for modifying widgets is called the **Inspector** tab. The Inspector tab consists of four sections: **COMPONENT**, **<WIDGET>**, **STYLE SETTINGS**, and **EVENTS**, as shown in Image 6.
208 -
209 -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.
210 -
211 -[[image:1727485118799-984.png]]
212 -
213 - Image 6: The button widget's "Inspector" tab
214 -
215 -
216 -==== Changing the Button properties ====
217 -
218 -Click the Button. Under the **Label** section, type "Click for details..." in the **Text** textbox.
219 -
220 -Under the "Layout" you can
221 -
222 -[[image:1727485251053-655.png]]
223 -
224 -image 7 the button widget's "BUTTON" tab
225 -
226 -
227 -Third part: It is an area of style setting.
228 -
229 -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.
230 -
231 -[[image:1727485480434-713.png||height="395" width="290"]]
232 -
233 - image 8 add event for button
234 -
235 -
236 -==== Changing the label properties ====
237 -
238 -Click the label. Under the **Label** section, type "Hello World!" in the **Text** textbox.
239 -
240 -
241 -[[image:image-20240928090825-1.png||height="327" width="391"]]
242 -
243 - Image 9:  Modify text of label widget
244 -
245 -
246 -==== 4. Changing image properties ====
247 -
248 -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.
249 -
250 -[[image:image-20240928113424-9.png||height="355" width="505"]]
251 -
252 - image 10 add image file into SquareLine Studio project
253 -
254 -[[image:image-20240928114139-10.png||height="559" width="810"]]
255 -
256 - image 11 use image widget in SquareLine Studio
257 -
258 -**5. The relationship between widgets**
259 -
260 -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.
261 -
262 -[[image:1727486567182-334.png||height="318" width="278"]]
263 -
264 -image 12 move label1 to make label1 widget be a child of button1 widget(1)
265 -
266 -[[image:image-20240928112001-8.png||height="431" width="796"]]
267 -
268 - image 13 move label1 to make label1 widget be a child of button1 widget(2)
269 -
270 -
271 -**6. Preview the screen**
272 -
273 -You can test the result by clicking on the **PLAY** button. The screen will change into play mode.
274 -
275 -[[image:1727487368023-281.png]]
276 -
277 - image 14 click on the triangle icon to start or end the simulation
278 -
279 -For more detailed usage, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
280 -
281 -
282 -== 2.4 Integrate UI Code to ESP-IDF Project ==
283 -
284 -
285 -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.
286 -
287 -[[image:1727229798126-306.png]]
288 -
289 - image 15 export UI file
290 -
291 -[[image:1727229821582-258.png||height="333" width="662"]]
292 -
293 - image 16 exported UI file
294 -
295 -Create a empty directory entitled "ui" in path "basic_prj/app_components/ui/", and then copy all UI code exported to this directory.
296 -
297 -[[image:image-20240928144830-11.png]]
298 -
299 - image 17 open CMakeLists.txt
300 -
301 -[[image:1727229892636-154.png||height="521" width="407"]]
302 -
303 - image 18 modify CMakeLists.txt
304 -
305 -The last step of integrating is adding two lines of code in main.c file.
306 -
307 -[[image:1727229926561-300.png]]
308 -
309 - image 19 add "ui.h"
310 -
311 -[[image:1727229955611-607.png]]
312 -
313 - image 20 add "ui_init()"
314 -
315 -
316 -== 2.5 Brief introduction of hello world project ==
317 -
318 -
319 -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.
320 -
321 -
322 -== 2.6 Test Result ==
323 -
324 -
325 -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.
326 -
327 -[[image:1727488067077-684.png||height="402" width="574"]]
328 -
329 - image 21 screen1
330 -
331 -[[image:1727488157579-949.png||height="397" width="572"]]
332 -
333 - image 22 screen2
334 -
335 -
336 336  = 3. Example Project 1: LoRa Central Display =
337 337  
338 338  [[image:image-20240916101737-1.png||height="468" width="683"]]
339 339  
340 340  
116 +
341 341  = 4. Example Project 2: LoRaWAN RS485 Alarm =
342 342  
343 -= 5.  The way to add a new panel to project =
344 344  
345 -**~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.**
346 -
347 -[[image:image-20241121113445-1.png||height="584" width="934"]]
348 -
349 - image 5.1 a panel about water_leak
350 -
351 -**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.
352 -
353 -[[image:image-20241121141120-4.png||height="383" width="795"]]
354 -
355 - image 5.2 ui files exported
356 -
357 -**3. Delete or rename some file.** Here are the steps:
358 -
359 - Step1 Delete the 'components' directory.
360 - Step2 Delete 'filelist.txt'.
361 - Step3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
362 - Step4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
363 - Step5 Rename the 'screens' directory to 'styles'.
364 -
365 -[[image:image-20241121151934-10.png||height="303" width="792"]]
366 -
367 - image 5.3 rest file (1)
368 -
369 -[[image:image-20241121142925-7.png||height="141" width="793"]]
370 -
371 - image 5.4 rest file (2)
372 -
373 -**4. Open this project in vscode.**
374 -
375 -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.
376 -
377 -[[image:image-20241121181957-17.png||height="438" width="516"]]
378 -
379 - image 5.5 extra_lib/CMakeLists.txt before add
380 -
381 -[[image:image-20241121182239-18.png||height="520" width="518"]]
382 -
383 - image 5.6 extra_lib/CMakeLists.txt after add
384 -
385 -**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.
386 -
387 -[[image:image-20241121171629-11.png]]
388 -
389 - image 5.7 before-modified font file
390 -
391 -[[image:image-20241121171901-12.png]]
392 -
393 - image 5.8 modified font file
394 -
395 -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.
396 -
397 -[[image:image-20241121172714-13.png]]
398 -
399 - image 5.9 before-modified image file
400 -
401 -[[image:image-20241121172908-14.png]]
402 -
403 - image 5.10 modified image file
404 -
405 -**7. Modify the ui_water_leak/CMakeLists.txt.** Open this file, and modify it from image 5.11 to image 5.12.
406 -
407 -[[image:image-20241121180030-15.png]]
408 -
409 - image 5.11 ui_water_leak/CMakeLists.txt before modification
410 -
411 -[[image:image-20241121180517-16.png]]
412 -
413 - image 5.12 ui_water_leak/CMakeLists.txt after modification
414 -
415 -**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.
416 -
417 -[[image:image-20241122094200-23.png]]
418 -
419 - image 5.13 ui_water_leak.h (1) before modification
420 -
421 -[[image:image-20241122094320-24.png||height="852" width="554"]]
422 -
423 - image 5.14 ui_water_leak.h (2) before modification
424 -
425 -[[image:image-20241122094600-25.png||height="1078" width="554"]]
426 -
427 - image 5.15 ui_water_leak.h (1) after modification
428 -
429 -[[image:image-20241122094719-26.png||height="941" width="583"]]
430 -
431 - image 5.16 ui_water_leak.h (2) before modification
432 -
433 -**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.
434 -
435 -_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.
436 -
437 -[[image:image-20241122102929-27.png||height="619" width="426"]]
438 -
439 - image 5.17 ui_water_leak.c (1) before modification
440 -
441 -[[image:image-20241122112838-30.png||height="551" width="628"]]
442 -
443 - image 5.18 ui_water_leak.c (2) before modification
444 -
445 -[[image:image-20241122110815-29.png||height="725" width="712"]]
446 -
447 - image 5.19 ui_water_leak.c (3) before modification
448 -
449 -[[image:image-20241122113158-31.png||height="872" width="677"]]
450 -
451 - image 5.20 ui_water_leak.c (1) after modification
452 -
453 -[[image:image-20241122113259-33.png||height="874" width="724"]]
454 -
455 - image 5.21 ui_water_leak.c (2) after modification
456 -
457 -[[image:image-20241122113359-34.png||height="804" width="746"]]
458 -
459 - image 5.22 ui_water_leak.c (3) after modification
460 -
461 -**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.
462 -
463 -[[image:image-20241122134113-35.png||height="380" width="421"]]
464 -
465 - image 5.23 ui_water_leak_events_.h before modification
466 -
467 -[[image:image-20241122134420-37.png||height="201" width="283"]]
468 -
469 -image 5.24 ui_water_leak_events_.h after modification
470 -
471 -**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.
472 -
473 -Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
474 -
475 -Step2. add code  below in delete_object() function definition.
476 -
477 - panel_all * panel = find_upper_by_SensorPanel(&arr,((lv_obj_t *)(e->user_data~)~)~);
478 -
479 - size_t index = panel->panel_obj_index;
480 -
481 - deleteElement(&arr, index);
482 -
483 -[[image:image-20241122135023-38.png||height="358" width="372"]]
484 -
485 - image 5.25 ui_water_leak_events_.c before modification
486 -
487 -[[image:image-20241122135258-39.png||height="403" width="559"]]
488 -
489 - image 5.26 ui_water_leak_events_.c after modification
490 -
491 -**12. Modify ui_water_leak_style.c file.**
492 -
493 -Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
494 -
495 - add '#include "../../sort.h"'
496 -
497 - add '#include "ui.h"'
498 -
499 -[[image:image-20241122141536-41.png||height="361" width="612"]]
500 -
501 - image 5.27 ui_water_leak_style.c (1) before modification
502 -
503 -[[image:image-20241122142129-42.png||height="386" width="613"]]
504 -
505 - image 5.28 ui_water_leak_style.c (1) after modification
506 -
507 -Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
508 -
509 - delete code as shown in image 5.29
510 -
511 -[[image:image-20241122145620-44.png||height="757" width="671"]]
512 -
513 - image 5.29 ui_water_leak_style.c (2)
514 -
515 -Step3. The image 5.30, 5.31 show the change.
516 -
517 -[[image:image-20241122152026-45.png||height="277" width="828"]]
518 -
519 - image 5.30 ui_water_leak_style.c (3) before modification
520 -
521 -[[image:image-20241122152542-46.png||height="293" width="830"]]
522 -
523 - image 5.31 ui_water_leak_style.c (3) after modification
524 -
525 -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).
526 -
527 -[[image:image-20241122153958-47.png]]
528 -
529 - image 5.32 ui_water_leak_style.c (4)
530 -
531 -[[image:image-20241122154755-49.png||height="864" width="513"]]
532 -
533 - image 5.33 ui_water_leak_style.c (4)
534 -
535 -Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
536 -
537 -[[image:image-20241122155650-50.png||height="922" width="513"]]
538 -
539 - image 5.34 ui_water_leak_style.c (5)
540 -
541 -Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
542 -
543 -[[image:image-20241122161934-51.png]]
544 -
545 - image 5.35
546 -
547 -Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
548 -
549 -[[image:image-20241122162852-53.png||height="330" width="529"]]
550 -
551 - image 5.37
552 -
553 -Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
554 -
555 -panel_with_type union_sensor;
556 -
557 -union_sensor.panel_type = WATER_LEAK_TYPE;
558 -
559 -......
560 -
561 -lv_obj_set_x(union_sensor.panel_union.door.ui_PanelSensorDoor, x_by_index(index));
562 -
563 -lv_obj_set_y(union_sensor.panel_union.door.ui_PanelSensorDoor, y_by_index(index));
564 -
565 -return union_sensor;
566 -
567 -[[image:image-20241122171211-54.png||height="635" width="792"]]
568 -
569 - image 5.38
570 -
571 -**13. Modify sort.c file.**
572 -
573 -Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
574 -
575 -[[image:image-20241122173718-56.png||height="378" width="579"]]
576 -
577 - image 5.39 sort.c (1)
578 -
579 -There are still some changes need to be done in sort.c, and omit here for the moment.
580 -
581 -
582 582  = 6. FAQ =
583 583  
584 584  == 6.1 ==
... ... @@ -588,13 +588,11 @@
588 588  
589 589  == 7.1  Part Number ==
590 590  
591 -
592 592  Part Number: (% style="color:#4472c4" %)LTS5
593 593  
594 594  
595 595  == 7.2  Packing Info ==
596 596  
597 -
598 598  **Package Includes**:
599 599  
600 600  * LTS5 HMI Touch Screen
... ... @@ -603,13 +603,11 @@
603 603  
604 604  = 8. Support =
605 605  
606 -
607 607  * 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.
608 608  * 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]].
609 609  
610 610  = 9.  Reference material =
611 611  
612 -
613 613  * Datasheet
614 614  * Source Code
615 615  * Mechinical
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-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
image-20241121113445-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -250.0 KB
Content
image-20241121120222-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -44.8 KB
Content
image-20241121120830-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -42.6 KB
Content
image-20241121141120-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -41.7 KB
Content
image-20241121141315-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -29.4 KB
Content
image-20241121141329-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -29.4 KB
Content
image-20241121142925-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -14.8 KB
Content
image-20241121145915-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -61.0 KB
Content
image-20241121150911-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -73.0 KB
Content
image-20241121151934-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -32.9 KB
Content
image-20241121171629-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -16.9 KB
Content
image-20241121171901-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -17.2 KB
Content
image-20241121172714-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -26.4 KB
Content
image-20241121172908-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -27.1 KB
Content
image-20241121180030-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -27.7 KB
Content
image-20241121180517-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -26.5 KB
Content
image-20241121181957-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -59.3 KB
Content
image-20241121182239-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -71.3 KB
Content
image-20241122092239-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -270.9 KB
Content
image-20241122092655-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -251.6 KB
Content
image-20241122093445-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -128.9 KB
Content
image-20241122093601-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -120.0 KB
Content
image-20241122094200-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -289.2 KB
Content
image-20241122094320-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -182.4 KB
Content
image-20241122094600-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -136.0 KB
Content
image-20241122094719-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -129.5 KB
Content
image-20241122102929-27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -219.9 KB
Content
image-20241122104344-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -257.1 KB
Content
image-20241122110815-29.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -246.1 KB
Content
image-20241122112838-30.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -263.9 KB
Content
image-20241122113158-31.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -133.7 KB
Content
image-20241122113252-32.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -152.3 KB
Content
image-20241122113259-33.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -152.3 KB
Content
image-20241122113359-34.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -126.5 KB
Content
image-20241122134113-35.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -69.3 KB
Content
image-20241122134412-36.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
image-20241122134420-37.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
image-20241122135023-38.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -28.7 KB
Content
image-20241122135258-39.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -40.3 KB
Content
image-20241122141526-40.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
image-20241122141536-41.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
image-20241122142129-42.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -85.1 KB
Content
image-20241122143105-43.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -60.2 KB
Content
image-20241122145620-44.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -394.0 KB
Content
image-20241122152026-45.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -201.6 KB
Content
image-20241122152542-46.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -95.3 KB
Content
image-20241122153958-47.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -241.1 KB
Content
image-20241122154745-48.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -135.7 KB
Content
image-20241122154755-49.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -135.7 KB
Content
image-20241122155650-50.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -104.4 KB
Content
image-20241122161934-51.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -230.3 KB
Content
image-20241122162612-52.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -58.7 KB
Content
image-20241122162852-53.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -125.5 KB
Content
image-20241122171211-54.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -173.3 KB
Content
image-20241122173706-55.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -37.6 KB
Content
image-20241122173718-56.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -37.6 KB
Content
squalreline-trial.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -60.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