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.

26

27

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.

28

29

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.

30

31

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

37

* Dragino LA66 LoRa Module

38

* Support Private LoRa protocol or LoRaWAN protocol

39

* Support WiFi & BLE wireless protocol

40

* 5.0" HMI touch screen

41

* Support LVGL case. SquareLine program.

42

* Support RS485 Interface

43

* Open Source Project

* Wall Attachable.

* 5V DC power

* IP Rating: IP52

== 1.3 Specifications ==

**LoRa**:

* Frequency Range: 870 MHz ~~ 960 MHz

54

* TCXO crystal to ensure RF performance on low temperature

55

* Maximum Power +22 dBm constant RF output

56

* High sensitivity: -148 dBm

57

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

58

* LoRa Rx current: <9 mA

**WiFi:**

* 802.11b/g/n

* Up to 150 Mbps data rate in 802.11n mode

64

* Support A-MPDU and A-MSDU aggregation

65

* zero point four μ S protection interval

66

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

**Bluetooth:**

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

71

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

* AFH

* CVSD and SBC

**Display:**

* 5.0 Inch , 800 x 480

78

* IPS Capacitive Touch SCreen

79

* RGB color.

80

* Display Area: 120.7*75.80 mm

81

82

== 1.4 Power Consumption ==

83

84

85

* External 5V DC power adapter

86

87

== 1.5 Storage & Operation Temperature ==

88

89

90

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

91

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

92

93

== 1.6 Applications ==

94

95

96

* Smart Buildings & Home Automation

97

* Logistics and Supply Chain Management

* Smart Metering

* Smart Agriculture

* Smart Cities

* Smart Factory

= 2. Getting Started with 'Hello World' =

104

105

== 2.1 About this demo ==

106

107

108

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

109

110

* Creating a basic UI with a single button.

111

* Implementing functionality to navigate the Web UI to a new page when the button is clicked.

112

* Uploading the UI to the LTS5 device.

113

114

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

115

116

117

== 2.2 Install Software Running Environment ==

118

119

120

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.

121

122

123

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

124

125

126

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

127

128

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

129

130

131

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

132

133

Image 1: ESP-IDF extension install

134

135

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

136

137

138

=== 2.2.2 Install SquareLine Studio ===

139

140

141

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.

142

143

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

144

145

146

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 ==

155

156

157

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

158

159

* In the **PROJECT SETTINGS**, select **LVGL version **as **8.3.11** and **Resolution** as **800** x **480**.

160

* Select the **CREATE **button to create the new project with the selected settings.

161

162

[[image:squareline-studio-launcher-screen.png||height="752" width="1415"]]

163

164

165

Next, you need to configure some additional settings for this project. To do so, select** File -> Project Settings** as shown in the image below.

166

167

[[image:1727229582471-566.png]]

168

169

170

In the **PROJECT SETTINGS** dialog box, configure/modify the project settings as shown in the image below.

171

172

* **UI Files Export Path**: Select a **folder** on your computer to store the **UI files**.

173

* **LVGL Include Path**: Set this to **lvgl.h**

174

* Click on the **APPLY CHANGES** button.

175

176

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

177

178

179

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

180

181

182

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

183

184

185

After creating a project, a **Screen** will be automatically added. Its name is **Screen1** by default.

186

187

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.

188

189

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

190

191

192

Then click the **Screen **widget to add the second screen. After adding the second screen, it will appear in the Screens panel as **Screen2**.

193

194

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

195

196

=== **Modify widget properties** ===

197

198

199

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.

200

201

[[image:1727485118799-984.png]]

202

203

204

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

205

206

207

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:

208

209

* **Flex Flow**: No Layout

* **Transform**:

** **X**: 331 px

** **Y**: 203 px

** **Width**: 100 px

** **Height**: 50 px

** **Align**: CENTER

[[image:1727485251053-655.png]]

218

219

220

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.

221

222

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

223

224

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

225

226

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

227

228

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

229

230

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

231

* Finally, click the **ADD** button.

232

233

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

234

235

Image 8: Add an event for the button

236

237

238

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

239

240

241

Click the Label you have added to the screen. Under the **Label** section, type "**Click for Detail**" in the **Text** textbox.

242

243

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

244

245

246

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

247

248

249

==== **Changing image properties** ====

250

251

252

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.

253

254

One way is to move your image into the folder "…/squareline project/assets/", as shown in the image below.

255

256

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

257

258

259

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.

260

261

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

262

263

264

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

265

266

267

Widgets commonly have two types of relationships: **parallel** and **parent-child**.

268

269

* In a **parallel relationship**, widgets' positions are determined relative to a shared reference object.

270

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

271

272

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

273

274

275

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

276

277

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

278

279

280

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.

281

282

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

283

284

285

==== **Preview the screen** ====

286

287

288

You can test the result by clicking on the **PLAY** button as shown in the image below. The screen will change into play mode.

289

290

[[image:1727487368023-281.png]]

291

292

293

For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].

294

295

296

== 2.4 Integrate UI Code into an ESP-IDF Project ==

297

298

299

To integrate, first export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.

300

301

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

302

303

[[image:1727229798126-306.png]]

304

305

306

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

307

308

309

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

310

311

312

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.

313

314

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

315

316

317

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

318

319

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

320

321

322

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

323

324

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

325

326

[[image:1727229926561-300.png]]

Add **ui_init();**

[[image:1727229955611-607.png]]

332

333

334

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

335

336

337

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.

338

339

340

== 2.6 Test Result ==

341

342

343

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

353

354

355

= 3. Example Project 1: LoRa Central Display =

356

357

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

358

359

360

= 4. Example Project 2: LoRaWAN RS485 Alarm =

361

362

= 5. Example Project 3: P2P =

363

364

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.

365

366

The project can be found at [[this link>>url:https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/P2P]].

367

368

== 5.1 Firmware Flashing ==

369

370

371

The following software tools are required to flash firmware to the ESP32 and LA66.

372

373

* Download the ESP32 firmware flash tool from [[this link>>https://docs.espressif.com/projects/esp-test-tools/en/latest/esp32/production_stage/tools/flash_download_tool.html]].

374

* Download the LA66 firmware flash tool from [[this link>>https://www.dropbox.com/scl/fo/9kqeqf6wmet10o9hgxuwa/h?rlkey=4ikrg6kg5v0yjxwhp0i37wrv7&e=1&dl=0]].

375

376

=== 5.1.1 Upload the Firmware to the ESP32 ===

377

378

Open //**flash_download_tool.exe**// and follow the steps below.

379

380

* **Chip Type**: ESP32-S3

381

* **WorkMode**: Develop

382

* **LoadMode**: UART

383

* Click on the **OK** button.

384

385

[[image:1738893226894-758.png||height="170" width="176"]]

386

387

388

In the **SPIDownload** tab,

389

390

* Select the checkboxes for ESP32_LoRaC-P2P_CommonFW_v1.0.0.bin.

391

* SPI Flashing Config(default configuration):

392

** **SPI SPEED**: 40MHz

393

** **SPI MODE**: DIO

394

** Check **DoNotChgBin** option.

395

* **COM**: Select the correct COM port.

396

* **BAUD**: 1152000

397

* Click on the **START** button.

398

399

[[image:image-20250505122103-4.png||height="551" width="705"]]

400

401

The progress bar will indicate the firmware update progress and display a **FINISH** message once the update is complete.

402

403

404

=== 5.1.2 Upload the Firmware to the LA66 ===

405

406

Open **Dragino_Sensor_Manager_Utility.exe**, and then follow the steps below.

407

408

* Click on the UART Update Firmware tab.

409

* Select the correct COM port.

410

* Click on the Upload_File button and select the LA66_P2P_FW_v1.0.0.bin file.

411

* Click on the Start button.

[[image:image-20250505121328-2.png]]

416

417

418

[[image:image-20250505121531-3.png]]

419

420

(% class="wikigeneratedid" %)

421

The progress bar will indicate the firmware update progress.

422

423

424

== 5.2 AT commands and LTS5 Panel Data Formats ==

425

426

AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**01**A4CBBB0A8E085C02,0,3

427

428

AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**02**A4CB00,0,3

429

430

AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**03**A4CB00,0,3

431

432

AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**04**A4CB00,0,3

433

434

AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**05**A4CB00,0,3

435

436

AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**06**A4CB00,0,3

437

438

**LTS5 panel data format**:

439

440

~1. AT+SEND=1,**01** **4b69746368656e2d467269676531FFFF A84041000181D4A8 01 A4CB BB0A 8E08 5C02**,0,3

441

442

**01:** encrypt. 1 Byte. 01 ~-~-> no encryption. This 1-byte information is now invalid; simply write 0x01 instead.

443

444

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

445

446

**A84041000181D4A8:** Device EUI. 8 Bytes. The last three Bytes will be extracted by the ESP32-S3 and displayed on the screen.

447

448

**01: **Panel Type. 1 Byte. 0x01~-~->Tem & Hum,

0x02~-~->Door,

0x03~-~->Water Leak,

0x04~-~->Occupied,

0x05~-~->Button,

0x06~-~->Alarm,

**A4CB: **Battery level//. //2 Bytes. Battery Voltage =0xCBA4&0x3FFF=0x0BA4=2980mV

461

462

**BB0A: **The temperature of the built-in sensor in LHT65N.// //2 Bytes. Temperature: 0x0ABB/100=27.47℃

463

464

**8E08: **The temperature of the External temperature sensor.// //2 Bytes. Temperature: 0x088E/100=21.90℃

465

466

**5C02：**The humidity of the built-in sensor in LHT65N. 2 Bytes. Humidity: 0x025C/10=60.4%

467

468

2. AT+SEND=1,**01** **4b69746368656e2d467269676531FFFF** **A84041000181D4A8** **02 A4CB 00**,0,3

469

470

Specific sections of the data share the same function.

471

472

**00: Status. **1 Byte//. //If Panel Type is 0x02, **Status: 00~-~->Open; 01~-~->Close.**

473

474

If Panel Type is 0x03, **Status: 00~-~->Normal; 01~-~->Water Leaking.**

475

476

If Panel Type is 0x04, **Status: 00~-~->Free; 01~-~->Occupied.**

477

478

If Panel Type is 0x05, **Status: 00~-~->OFF; 01~-~->ON.**

479

480

If Panel Type is 0x06, **Status: 00~-~->OFF; 01~-~->Alarm.**

== 5.3 Usage ==

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.

485

486

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.

487

488

[[image:image-20250207143131-11.png||height="527" width="547"]]

489

490

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.

491

492

[[image:image-20250207144605-12.png||height="634" width="548"]]

493

494

LTS5 receives this message and displays it on its screen as the image below shows.

495

496

[[image:image-20250208181700-8.jpeg||height="528" width="704"]]

497

498

= 6. Example Project 4: LoRaWAN_CLASS_C =

499

500

501

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.

502

503

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.

504

505

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

506

507

The project can be found at [[this link>>https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/LoRaWAN_CLASS_C]].

508

509

== 6.1 firmware flashing approach ==

510

511

The firmware flashing approach is the same as described in section 5.1.

== 6.2 flowchart ==

[[image:image-20250207164320-13.png||height="696" width="1344"]]

== 6.3 Usage ==

This section now describes a process involving TTN downlink panel data that is to be displayed on the LTS5 screen.

520

521

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.

522

523

[[image:image-20250207165702-14.png||height="830" width="563"]]

524

525

6.3.2 Switch to Class C using "AT+CLASS=C", and check the class with "AT+CLASS=?".

526

527

[[image:image-20250207173212-27.png]]

528

529

[[image:image-20250207172246-20.png]]

530

531

6.3.3 Verify LA66's join status (in LTS5) with "AT+NJS=?". If not joined, connect manually to LoRaWAN with "AT+JOIN".

532

533

[[image:image-20250207172010-19.png]]

534

535

[[image:image-20250207171650-17.png]]

536

537

6.3.4 After joining, send a message to TTN, such as "AT+SENDB=01,02,8,05820802581ea0a5", to activate communication.

538

539

[[image:image-20250207192107-28.png]]

540

541

6.3.5 TTN distributes panel data in three phases: DEUI, Dev Name, and Sensor Data. The Dev Name, the last three bytes of the DEUI, and the panel type union together ensure the identification of a panel. Data about the same panel type will update the existing panel display, while data about a different panel type will create a new panel display on the LTS5 screen.

542

543

There is an example for TTN downlink.

544

545

1. downlink DEUI F1A84041000181D4A8

546

1. downlink Dev Name F24B69746368656E2D467269676531FFFF

547

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.

548

549

[[image:image-20250208175819-1.png||height="503" width="502"]]

550

551

552

[[image:image-20250208175918-2.png||height="505" width="502"]]

553

554

555

[[image:image-20250208180010-3.png||height="507" width="503"]]

556

557

558

[[image:image-20250208181019-4.jpeg||height="592" width="790"]]

559

560

561

[[image:image-20250208181328-7.png||height="505" width="504"]]

562

563

564

[[image:image-20250208181139-5.jpeg||height="594" width="792"]]

565

566

567

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

568

569

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

570

571

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

572

573

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

574

575

Image 7.1: a panel about water_leak

576

577

578

2. **Export the UI file: **You need to adjust the export path first, then click '**Export -> Export UI Files**' on the menu bar. This step was introduced earlier. After that, you can get the UI files as shown in Image 7.2.

579

580

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

581

582

Image 7.2: Exported UI files

583

584

585

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

586

587

Step 1: Delete the 'components' directory.

588

Step 2: Delete 'filelist.txt'.

589

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

590

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

591

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

592

593

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

594

595

image 7.3 rest file (1)

596

597

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

598

599

image 7.4 rest file (2)

600

601

4. Open the project in VS Code.

602

603

5. Add the file include path for **water_leak** in **extra_lib/CMakeLists.txt**, as shown in Images 7.5 and 7.6. Its format is similar to that of **tem_hum** or **door**."

604

605

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

606

607

image 7.5 extra_lib/CMakeLists.txt before adding

608

609

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

610

611

image 7.6 extra_lib/CMakeLists.txt after adding

612

613

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

614

615

Open the **fonts/ui_font_Font12.c** file, as shown in Image 7.7, and change **#include "../ui.h"** to **#include "../ui_water_leak.h"**. The modified file is shown in Image 7.8. Other font files need to be modified in the same way.

616

617

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

618

619

image 7.7 unmodified font file

620

621

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

622

623

image 7.8 modified font file

624

625

Open the **images/ui_img_battery_empty_png.c** file, as shown in Image 7.9, and change **#include "../ui.h"** to **#include "../ui_water_leak.h"**. The modified file is shown in Image 7.10. Other image files need to be modified in the same way.

626

627

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

628

629

image 7.9 unmodified image file

630

631

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

632

633

image 7.10 modified image file

634

635

7. Modify the **ui_water_leak/CMakeLists.txt**. Open this file, and modify it as shown in image 7.11 (before) and image 7.12 (after).

636

637

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

638

639

image 7.11 ui_water_leak/CMakeLists.txt before modification

640

641

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

642

643

image 7.12 ui_water_leak/CMakeLists.txt after modification

644

645

646

8. Modify the **ui_water_leak.h** file. Images 7.13 and 7.14 show the code before modification, while Images 7.15 and 7.16 show the code after modification.

647

648

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

649

650

image 7.13 ui_water_leak.h (1) before modification

651

652

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

653

654

image 7.14 ui_water_leak.h (2) before modification

655

656

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

657

658

image 7.15 ui_water_leak.h (1) after modification

659

660

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

661

662

image 7.16 ui_water_leak.h (2) before modification

663

664

9. **Modify ui_water_leak.c file.** The image 7.17, 7.18, 7.19 show the code before modification, and the image 7.20, 7.21, 7.22 show the code after modification.

665

666

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

667

668

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

669

670

image 7.17 ui_water_leak.c (1) before modification

671

672

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

673

674

image 7.18 ui_water_leak.c (2) before modification

675

676

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

677

678

image 7.19 ui_water_leak.c (3) before modification

679

680

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

681

682

image 7.20 ui_water_leak.c (1) after modification

683

684

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

685

686

image 7.21 ui_water_leak.c (2) after modification

687

688

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

689

690

image 7.22 ui_water_leak.c (3) after modification

691

692

10. **Modify ui_water_leak_events.h file.** The image 7.23 show the code before modification, and the image 7.24 show the code after modification.

693

694

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

695

696

image 7.23 ui_water_leak_events_.h before modification

697

698

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

699

700

image 7.24 ui_water_leak_events_.h after modification

701

702

11.** Modify ui_water_leak_events.c file.** The image 7.25 show the code before modification, and the image 7.26 show the code after modification.

703

704

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

705

706

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

707

708

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

709

710

size_t index = panel->panel_obj_index;

711

712

deleteElement(&arr, index);

713

714

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

715

716

image 7.25 ui_water_leak_events_.c before modification

717

718

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

719

720

image 7.26 ui_water_leak_events_.c after modification

721

722

723

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

724

725

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

726

727

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

728

729

add '#include "ui.h"'

730

731

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

732

733

image 7.27 ui_water_leak_style.c (1) before modification

734

735

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

736

737

image 7.28 ui_water_leak_style.c (1) after modification

738

739

740

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

741

742

delete code as shown in image 7.29

743

744

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

745

746

image 7.29 ui_water_leak_style.c (2)

747

748

749

Step3. The image 7.30, 7.31 show the change.

750

751

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

752

753

image 7.30 ui_water_leak_style.c (3) before modification

754

755

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

756

757

image 7.31 ui_water_leak_style.c (3) after modification

758

759

760

Step4. Copy partly the code in ui_water_leak.c, paste at extra_lib/sort.h(The process is shown in image 7.32, 7.33).

761

762

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

763

764

image 7.32 ui_water_leak_style.c (4)

765

766

767

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

768

769

image 7.33 ui_water_leak_style.c (4)

770

771

772

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

773

774

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

775

776

image 7.34 ui_water_leak_style.c (5)

777

778

779

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

780

781

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

image 7.35

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

787

788

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

image 7.37

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

794

795

panel_with_type union_sensor;

796

797

union_sensor.panel_type = WATER_LEAK_TYPE;

......

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

802

803

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 7.38

13. Rest midification in sort.h file.

813

814

In image 7.39 as below, we can see "WATER_LEAK_TYPE" at line 24 and water leak switch status definition at line 32,33, and these are what we need to add in sort.h.

815

816

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

image 7.39 sort.h

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

821

822

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

823

824

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

825

826

image 7.40 sort.c (1)

827

828

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

= 8. FAQ =

== 8.1 ==

= 9. Order Info =

== 9.1 Part Number ==

840

841

842

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

843

844

845

== 9.2 Packing Info ==

846

847

848

**Package Includes**:

849

850

* LTS5 HMI Touch Screen

851

* 5V,2A DC Power Adapter.

852

* USB Type C Program Cable

= 10. 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.

858

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

859

860

= 11. Reference material =

861

862

863

* Datasheet: [[https:~~/~~/www.dropbox.com/scl/fo/fr7wjsdfh9huchg59p7bv/APASCR0elWtp_EbUZ1W9K-A?rlkey=pcuptw3dtg5pw9vgt4ag6hs9z&st=ds6hdztg&dl=0>>https://www.dropbox.com/scl/fo/fr7wjsdfh9huchg59p7bv/APASCR0elWtp_EbUZ1W9K-A?rlkey=pcuptw3dtg5pw9vgt4ag6hs9z&st=ds6hdztg&dl=0]]

864

* schematic: [[LTS5-V1>>attach:LTS5-V1.pdf]]

865

* 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

= 12. FCC Warning =

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

872

873

(1) This device may not cause harmful interference;