LTS5 LoRa HMI Touch Screen

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

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

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

32

The LA66 LoRa module can be programmed to support either private LoRa protocols or the LoRaWAN protocol.

== 1.2 Features ==

* ESP32-WROOM MCU: 8MB RAM & 16MB ROM

38

* Dragino LA66 LoRa Module

39

* Support Private LoRa protocol or LoRaWAN protocol

40

* Support WiFi & BLE wireless protocol

41

* 5.0" HMI touch screen

42

* Support LVGL case. SquareLine program.

43

* Support RS485 Interface

44

* Open Source Project

* Wall Attachable.

* 5V DC power

* IP Rating: IP52

== 1.3 Specifications ==

**LoRa**:

* Frequency Range: 870 MHz ~~ 960 MHz

55

* TCXO crystal to ensure RF performance on low temperature

56

* Maximum Power +22 dBm constant RF output

57

* High sensitivity: -148 dBm

58

* LoRa Tx Current: <90 mA at +17 dBm, 108 mA at +22 dBm

59

* LoRa Rx current: <9 mA

**WiFi:**

* 802.11b/g/n

* Up to 150 Mbps data rate in 802.11n mode

65

* Support A-MPDU and A-MSDU aggregation

66

* zero point four μ S protection interval

67

* Working channel center frequency range: 2412~~2484 MHz

**Bluetooth:**

* Bluetooth V4.2 BR/EDR and Bluetooth LE standard

72

* Class-1, Class-2, and Class-3 transmitters.

* AFH

* CVSD and SBC

**Display:**

* 5.0 Inch , 800 x 480

79

* IPS Capacitive Touch SCreen

80

* RGB color.

81

* Display Area: 120.7*75.80 mm

82

83

== 1.4 Power Consumption ==

84

85

86

* External 5V DC power adapter

87

88

== 1.5 Storage & Operation Temperature ==

89

90

91

* Operation Temperature: -20 ~~ 70°C (No Dew)

92

* Storage Temperature: -30 ~~ 70°C (No Dew)

93

94

== 1.6 Applications ==

95

96

97

* Smart Buildings & Home Automation

98

* Logistics and Supply Chain Management

* Smart Metering

* Smart Agriculture

* Smart Cities

* Smart Factory

= 2. Getting Started with 'Hello World' =

105

106

== 2.1 About this demo ==

107

108

109

This getting started example demonstrates how to design and deploy a simple display UI for the LTS5 device. The example includes:

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

115

By completing this demo, you will gain foundational knowledge for customizing the LTS5 interface and building more advanced IoT applications.

116

117

118

== 2.2 Install Software Running Environment ==

119

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.

122

123

124

=== 2.2.1 Install VS Code and ESP-IDF extension ===

125

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]].

128

129

Next, install the **ESP-IDF** extension within **VS Code**. Detailed steps for this process are shown in Image 1.

130

131

132

[[image:image-20240928110211-5.png||height="508" width="866"]]

133

134

Image 1: ESP-IDF extension install

135

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

138

139

=== 2.2.2 Install SquareLine Studio ===

140

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.

143

144

[[image:squareline.io_downloads.png||height="888" width="1294"]]

145

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:

* Max. 10 screens

* Max. 150 widgets

* Max. 5 global colors

* Max. 2 themes

* Max. 1 component

== 2.3 Simple usage of SquareLine Studio and exporting UI code ==

156

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**.

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.

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

[[image:1727229582471-566.png]]

169

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

[[image:image-20240928105309-4.png||height="526" width="556"]]

178

179

180

Now you can start building the user interface. Follow the steps below:

181

182

183

=== **Add widgets** ===

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

[[image:image-20240928111412-6.png||height="526" width="864"]]

189

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**.

192

193

[[image:Screenshot 2024-12-24 140459.png||height="278" width="290"]]

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

[[image:1727485118799-984.png]]

201

202

203

==== **Changing the Button properties** ====

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

* **Transform**:

** **X**: 331 px

** **Y**: 203 px

** **Width**: 100 px

** **Height**: 50 px

** **Align**: CENTER

[[image:1727485251053-655.png]]

217

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.

220

221

* Click **ADD EVENT** button. A new section will appear to configure this event.

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

[[image:1727485480434-713.png||height="395" width="290"]]

233

234

Image 8: Add an event for the button

235

236

237

==== **Changing the label properties** ====

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

[[image:image-20240928090825-1.png||height="327" width="391"]]

243

244

245

Once you enter the text, it will immediately appear on the label.

246

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

[[image:image-20240928113424-9.png||height="355" width="505"]]

256

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

[[image:image-20240928114139-10.png||height="559" width="810"]]

261

262

263

==== **The relationship between widgets** ====

264

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

[[image:1727486567182-334.png||height="318" width="278"]]

272

273

274

Move the label, **Label1** to make it a child of **Button1** as shown in the image below.

275

276

[[image:image-20240928112001-8.png||height="431" width="796"]]

277

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.

280

281

[[image:Screenshot 2024-12-24 144005.png||height="360" width="290"]]

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

[[image:1727487368023-281.png]]

290

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/]].

293

294

295

== 2.4 Integrate UI Code to ESP-IDF Project ==

296

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.

299

300

On the menubar, click **Export -> Export UI** Files as shown in the image below.

301

302

[[image:1727229798126-306.png]]

303

304

305

The exported UI files can be found in your SquareLine project folder as shown in the image below.

306

307

308

[[image:1727229821582-258.png||height="333" width="662"]]

309

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.

312

313

[[image:image-20240928144830-11.png]]

314

315

316

Open the **CMakeLists.txt** file and edit it as ahown below.

317

318

[[image:1727229892636-154.png||height="521" width="407"]]

319

320

321

Open the main.c file and add two lines of code as shown in the below images.

322

323

Add **#include "ui.h"**

324

325

[[image:1727229926561-300.png]]

Add **ui_init();**

[[image:1727229955611-607.png]]

331

332

333

== 2.5 Brief introduction to the Hello World project ==

334

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

338

339

== 2.6 Test Result ==

340

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.

Screen 1:

[[image:1727488067077-684.png||height="402" width="574"]]

Screen 2:

[[image:1727488157579-949.png||height="397" width="572"]]

352

353

354

= 3. Example Project 1: LoRa Central Display =

355

356

[[image:image-20240916101737-1.png||height="468" width="683"]]

357

358

359

= 4. Example Project 2: LoRaWAN RS485 Alarm =

360

361

= 5. The method for adding a new type of panel to the project =

362

363

If you don't have this need, then this part of the content can be ignored.

364

365

1. Design a panel in SquareLine Studio, as shown in Image 5.1 below for reference.

366

367

[[image:image-20241121113445-1.png||height="584" width="934"]]

368

369

Image 5.1: a panel about water_leak

370

371

372

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.

373

374

[[image:image-20241121141120-4.png||height="383" width="795"]]

375

376

Image 5.2: Exported UI files

377

378

379

3. **Delete and rename some file.** Here are the steps:

380

381

Step 1: Delete the 'components' directory.

382

Step 2: Delete 'filelist.txt'.

383

Step 3: Delete 'ui_helpers.c' and 'ui_helpers.h'.

384

Step 4: Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.

385

Step 5: Rename the 'screens' directory to 'styles'.

386

387

[[image:image-20241121151934-10.png||height="303" width="792"]]

388

389

image 5.3 rest file (1)

390

391

[[image:image-20241121142925-7.png||height="141" width="793"]]

392

393

image 5.4 rest file (2)

394

395

4. Open the project in **VS Code**.

396

397

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**."

398

399

[[image:image-20241121181957-17.png||height="438" width="516"]]

400

401

image 5.5 extra_lib/CMakeLists.txt before add

402

403

[[image:image-20241121182239-18.png||height="520" width="518"]]

404

405

image 5.6 extra_lib/CMakeLists.txt after add

406

407

6. **Modify the header files included in the fonts and images directories**.

408

409

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.

410

411

[[image:image-20241121171629-11.png]]

412

413

image 5.7 before-modified font file

414

415

[[image:image-20241121171901-12.png]]

416

417

image 5.8 modified font file

418

419

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.

420

421

[[image:image-20241121172714-13.png]]

422

423

image 5.9 before-modified image file

424

425

[[image:image-20241121172908-14.png]]

426

427

image 5.10 modified image file

428

429

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).

430

431

[[image:image-20241121180030-15.png]]

432

433

image 5.11 ui_water_leak/CMakeLists.txt before modification

434

435

[[image:image-20241121180517-16.png]]

436

437

image 5.12 ui_water_leak/CMakeLists.txt after modification

438

439

440

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.

441

442

[[image:image-20241122094200-23.png]]

443

444

image 5.13 ui_water_leak.h (1) before modification

445

446

[[image:image-20241122094320-24.png||height="852" width="554"]]

447

448

image 5.14 ui_water_leak.h (2) before modification

449

450

[[image:image-20241122094600-25.png||height="1078" width="554"]]

451

452

image 5.15 ui_water_leak.h (1) after modification

453

454

[[image:image-20241122094719-26.png||height="941" width="583"]]

455

456

image 5.16 ui_water_leak.h (2) before modification

457

458

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.

459

460

_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.

461

462

[[image:image-20241122102929-27.png||height="619" width="426"]]

463

464

image 5.17 ui_water_leak.c (1) before modification

465

466

[[image:image-20241122112838-30.png||height="551" width="628"]]

467

468

image 5.18 ui_water_leak.c (2) before modification

469

470

[[image:image-20241122110815-29.png||height="725" width="712"]]

471

472

image 5.19 ui_water_leak.c (3) before modification

473

474

[[image:image-20241122113158-31.png||height="872" width="677"]]

475

476

image 5.20 ui_water_leak.c (1) after modification

477

478

[[image:image-20241122113259-33.png||height="874" width="724"]]

479

480

image 5.21 ui_water_leak.c (2) after modification

481

482

[[image:image-20241122113359-34.png||height="804" width="746"]]

483

484

image 5.22 ui_water_leak.c (3) after modification

485

486

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.

487

488

[[image:image-20241122134113-35.png||height="380" width="421"]]

489

490

image 5.23 ui_water_leak_events_.h before modification

491

492

[[image:image-20241122134420-37.png||height="201" width="283"]]

493

494

image 5.24 ui_water_leak_events_.h after modification

495

496

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.

497

498

Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'

499

500

Step2. add code below in delete_object() function definition.

501

502

panel_all * panel = find_upper_by_SensorPanel(&arr,((lv_obj_t *)(e->user_data~)~)~);

503

504

size_t index = panel->panel_obj_index;

505

506

deleteElement(&arr, index);

507

508

[[image:image-20241122135023-38.png||height="358" width="372"]]

509

510

image 5.25 ui_water_leak_events_.c before modification

511

512

[[image:image-20241122135258-39.png||height="403" width="559"]]

513

514

image 5.26 ui_water_leak_events_.c after modification

515

516

517

12. **Modify ui_water_leak_style.c file.**

518

519

Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'

520

521

add '#include "../../sort.h"'

522

523

add '#include "ui.h"'

524

525

[[image:image-20241122141536-41.png||height="361" width="612"]]

526

527

image 5.27 ui_water_leak_style.c (1) before modification

528

529

[[image:image-20241122142129-42.png||height="386" width="613"]]

530

531

image 5.28 ui_water_leak_style.c (1) after modification

532

533

534

Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'

535

536

delete code as shown in image 5.29

537

538

[[image:image-20241122145620-44.png||height="757" width="671"]]

539

540

image 5.29 ui_water_leak_style.c (2)

541

542

543

Step3. The image 5.30, 5.31 show the change.

544

545

[[image:image-20241122152026-45.png||height="277" width="828"]]

546

547

image 5.30 ui_water_leak_style.c (3) before modification

548

549

[[image:image-20241122152542-46.png||height="293" width="830"]]

550

551

image 5.31 ui_water_leak_style.c (3) after modification

552

553

554

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).

555

556

[[image:image-20241122153958-47.png]]

557

558

image 5.32 ui_water_leak_style.c (4)

559

560

561

[[image:image-20241122154755-49.png||height="864" width="513"]]

562

563

image 5.33 ui_water_leak_style.c (4)

564

565

566

Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).

567

568

[[image:image-20241122155650-50.png||height="922" width="513"]]

569

570

image 5.34 ui_water_leak_style.c (5)

571

572

573

Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.

574

575

[[image:image-20241122161934-51.png]]

image 5.35

Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.

581

582

[[image:image-20241122162852-53.png||height="330" width="529"]]

image 5.37

Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.

588

589

panel_with_type union_sensor;

590

591

union_sensor.panel_type = WATER_LEAK_TYPE;

......

lv_obj_set_x(union_sensor.panel_union.door.ui_PanelSensorDoor, x_by_index(index));

596

597

lv_obj_set_y(union_sensor.panel_union.door.ui_PanelSensorDoor, y_by_index(index));

return union_sensor;

[[image:image-20250122173546-6.png||height="777" width="922"]]

image 5.38

13. Rest midification in sort.h file.

607

608

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.

609

610

[[image:image-20250122170230-1.png||height="580" width="513"]]

image 5.39 sort.h

13. **Modify sort.c file.**

615

616

Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 26.

617

618

[[image:image-20250122171910-5.png||height="524" width="510"]]

619

620

image 5.40 sort.c (1)

621

622

There are still some changes need to be done in sort.c, and omit here for the moment.

= 6. FAQ =

== 6.1 ==

= 7. Order Info =

== 7.1 Part Number ==

634

635

636

Part Number: (% style="color:#4472c4" %)LTS5

637

638

639

== 7.2 Packing Info ==

640

641

642

**Package Includes**:

643

644

* LTS5 HMI Touch Screen

645

* 5V,2A DC Power Adapter.

646

* USB Type C Program Cable

= 8. Support =

* 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.

652

* 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]].

653

654

= 9. Reference material =

* Datasheet

* 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]]

* Mechinical

= 10. FCC Warning =

This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:

665

666

(1) This device may not cause harmful interference;

667

668

(2) this device must accept any interference received,including interference that may cause undesired operation.

669

Wiki source code of LTS5 LoRa HMI Touch Screen