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.

32

33

34

**//Note: Due to the current incomplete functionality, it is not recommended to purchase at this time.//**

== 1.2 Features ==

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

40

* Dragino LA66 LoRa Module

41

* Support Private LoRa protocol or LoRaWAN protocol

42

* Support WiFi & BLE wireless protocol

43

* 5.0" HMI touch screen

44

* Support LVGL case. SquareLine program.

45

* Support RS485 Interface

46

* Open Source Project

* Wall Attachable.

* 5V DC power

* IP Rating: IP52

== 1.3 Specifications ==

**LoRa**:

* Frequency Range: 870 MHz ~~ 960 MHz

57

* TCXO crystal to ensure RF performance on low temperature

58

* Maximum Power +22 dBm constant RF output

59

* High sensitivity: -148 dBm

60

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

61

* LoRa Rx current: <9 mA

**WiFi:**

* 802.11b/g/n

* Up to 150 Mbps data rate in 802.11n mode

67

* Support A-MPDU and A-MSDU aggregation

68

* zero point four μ S protection interval

69

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

**Bluetooth:**

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

74

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

* AFH

* CVSD and SBC

**Display:**

* 5.0 Inch , 800 x 480

81

* IPS Capacitive Touch SCreen

82

* RGB color.

83

* Display Area: 120.7*75.80 mm

84

85

== 1.4 Power Consumption ==

86

87

88

* External 5V DC power adapter

89

90

== 1.5 Storage & Operation Temperature ==

91

92

93

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

94

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

95

96

== 1.6 Applications ==

97

98

99

* Smart Buildings & Home Automation

100

* Logistics and Supply Chain Management

* Smart Metering

* Smart Agriculture

* Smart Cities

* Smart Factory

= 2. Getting Started with 'Hello World' =

107

108

== 2.1 About this demo ==

109

110

111

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

112

113

* Creating a basic UI with a single button.

114

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

115

* Uploading the UI to the LTS5 device.

116

117

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

118

119

120

== 2.2 Install Software Running Environment ==

121

122

123

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.

124

125

126

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

127

128

129

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

130

131

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

132

133

134

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

135

136

Image 1: ESP-IDF extension install

137

138

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

139

140

141

=== 2.2.2 Install SquareLine Studio ===

142

143

144

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.

145

146

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

147

148

149

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

158

159

160

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

161

162

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

163

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

164

165

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

166

167

168

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

169

170

[[image:1727229582471-566.png]]

171

172

173

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

174

175

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

176

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

177

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

178

179

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

180

181

182

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

183

184

185

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

186

187

188

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

189

190

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.

191

192

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

193

194

195

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

196

197

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

198

199

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

200

201

202

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.

203

204

[[image:1727485118799-984.png]]

205

206

207

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

208

209

210

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:

211

212

* **Flex Flow**: No Layout

* **Transform**:

** **X**: 331 px

** **Y**: 203 px

** **Width**: 100 px

** **Height**: 50 px

** **Align**: CENTER

[[image:1727485251053-655.png]]

221

222

223

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.

224

225

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

226

227

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

228

229

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

230

231

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

232

233

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

234

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

235

236

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

237

238

Image 8: Add an event for the button

239

240

241

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

242

243

244

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

245

246

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

247

248

249

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

250

251

252

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

253

254

255

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.

256

257

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

258

259

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

260

261

262

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.

263

264

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

265

266

267

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

268

269

270

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

271

272

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

273

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

274

275

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

276

277

278

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

279

280

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

281

282

283

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.

284

285

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

286

287

288

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

289

290

291

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

292

293

[[image:1727487368023-281.png]]

294

295

296

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

297

298

299

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

300

301

302

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

303

304

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

305

306

[[image:1727229798126-306.png]]

307

308

309

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

310

311

312

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

313

314

315

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.

316

317

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

318

319

320

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

321

322

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

323

324

325

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

326

327

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

328

329

[[image:1727229926561-300.png]]

Add **ui_init();**

[[image:1727229955611-607.png]]

335

336

337

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

338

339

340

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.

341

342

343

== 2.6 Test Result ==

344

345

346

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

356

357

358

= 3. Example Project 1: LoRa Central Display =

359

360

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

361

362

363

= 4. Example Project 2: LoRaWAN RS485 Alarm =

364

365

= 5. Example Project 3: P2P =

366

367

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.

368

369

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

370

371

== 5.1 Firmware Flashing ==

372

373

374

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

375

376

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

377

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

378

379

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

380

381

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

382

383

* **Chip Type**: ESP32-S3

384

* **WorkMode**: Develop

385

* **LoadMode**: UART

386

* Click on the **OK** button.

387

388

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

389

390

391

In the **SPIDownload** tab,

392

393

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

394

* SPI Flashing Config(default configuration):

395

** **SPI SPEED**: 40MHz

396

** **SPI MODE**: DIO

397

** Check **DoNotChgBin** option.

398

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

399

* **BAUD**: 1152000

400

* Click on the **START** button.

401

402

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

403

404

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

405

406

407

If you want to compile your own ESP32 project and burn the firmware instead of using the pre-provided firmware in the Firmware folder, please use the following method.

408

409

410

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

411

412

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

413

414

* Click on the UART Update Firmware tab.

415

* Select the correct COM port.

416

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

417

* Click on the Start button.

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

422

423

424

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

425

426

(% class="wikigeneratedid" %)

427

The progress bar will indicate the firmware update progress.

428

429

430

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

431

432

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

433

434

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

435

436

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

437

438

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

439

440

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

441

442

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

443

444

**LTS5 panel data format**:

445

446

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

447

448

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

449

450

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

451

452

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

453

454

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

467

468

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

469

470

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

471

472

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

473

474

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

475

476

Specific sections of the data share the same function.

477

478

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

479

480

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

481

482

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

483

484

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

485

486

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.

491

492

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.

493

494

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

495

496

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.

497

498

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

499

500

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

501

502

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

503

504

= 6. Example Project 4: LoRaWAN_CLASS_C =

505

506

507

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.

508

509

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.

510

511

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

512

513

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

514

515

== 6.1 firmware flashing approach ==

516

517

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.

526

527

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.

528

529

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

530

531

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

532

533

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

534

535

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

536

537

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

538

539

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

540

541

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

542

543

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

544

545

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

546

547

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.

548

549

There is an example for TTN downlink.

550

551

1. downlink DEUI F1A84041000181D4A8

552

1. downlink Dev Name F24B69746368656E2D467269676531FFFF

553

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.

554

555

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

556

557

558

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

559

560

561

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

562

563

564

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

565

566

567

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

568

569

570

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

571

572

573

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

574

575

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

576

577

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

578

579

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

580

581

Image 7.1: a panel about water_leak

582

583

584

2. **Export the UI file. **

585

586

You need to adjust the export path first, then click '**Export -> Export UI Files**' on the menu bar. The method for exporting UI files using the SquareLine software has already been described earlier.

587

588

Next, create a new folder named "ui_water_leak" under "app_components/extra_lib/", and then cut all the UI files you just exported into this newly created folder.

589

590

Image 7.2 shows the result of the operation.

591

592

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

593

594

Image 7.2: Exported UI files

595

596

597

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

598

599

Step 1: Delete the 'components' directory.

600

Step 2: Delete 'filelist.txt'.

601

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

602

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

603

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

604

605

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

606

607

image 7.3 rest file (1)

608

609

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

610

611

image 7.4 rest file (2)

612

613

4. Open the project in VS Code.

614

615

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

616

617

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

618

619

image 7.5 extra_lib/CMakeLists.txt before adding

620

621

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

622

623

image 7.6 extra_lib/CMakeLists.txt after adding

624

625

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

626

627

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.

628

629

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

630

631

image 7.7 unmodified font file

632

633

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

634

635

image 7.8 modified font file

636

637

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.

638

639

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

640

641

image 7.9 unmodified image file

642

643

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

644

645

image 7.10 modified image file

646

647

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

648

649

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

650

651

image 7.11 ui_water_leak/CMakeLists.txt before modification

652

653

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

654

655

image 7.12 ui_water_leak/CMakeLists.txt after modification

656

657

658

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.

659

660

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

661

662

image 7.13 ui_water_leak.h (1) before modification

663

664

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

665

666

image 7.14 ui_water_leak.h (2) before modification

667

668

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

669

670

image 7.15 ui_water_leak.h (1) after modification

671

672

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

673

674

image 7.16 ui_water_leak.h (2) before modification

675

676

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.

677

678

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

679

680

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

681

682

image 7.17 ui_water_leak.c (1) before modification

683

684

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

685

686

image 7.18 ui_water_leak.c (2) before modification

687

688

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

689

690

image 7.19 ui_water_leak.c (3) before modification

691

692

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

693

694

image 7.20 ui_water_leak.c (1) after modification

695

696

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

697

698

image 7.21 ui_water_leak.c (2) after modification

699

700

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

701

702

image 7.22 ui_water_leak.c (3) after modification

703

704

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.

705

706

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

707

708

image 7.23 ui_water_leak_events_.h before modification

709

710

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

711

712

image 7.24 ui_water_leak_events_.h after modification

713

714

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.

715

716

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

717

718

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

719

720

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

721

722

size_t index = panel->panel_obj_index;

723

724

deleteElement(&arr, index);

725

726

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

727

728

image 7.25 ui_water_leak_events_.c before modification

729

730

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

731

732

image 7.26 ui_water_leak_events_.c after modification

733

734

735

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

736

737

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

738

739

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

740

741

add '#include "ui.h"'

742

743

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

744

745

image 7.27 ui_water_leak_style.c (1) before modification

746

747

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

748

749

image 7.28 ui_water_leak_style.c (1) after modification

750

751

752

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

753

754

delete code as shown in image 7.29

755

756

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

757

758

image 7.29 ui_water_leak_style.c (2)

759

760

761

Step3. The image 7.30, 7.31 show the change.

762

763

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

764

765

image 7.30 ui_water_leak_style.c (3) before modification

766

767

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

768

769

image 7.31 ui_water_leak_style.c (3) after modification

770

771

772

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

773

774

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

775

776

image 7.32 ui_water_leak_style.c (4)

777

778

779

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

780

781

image 7.33 ui_water_leak_style.c (4)

782

783

784

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

785

786

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

787

788

image 7.34 ui_water_leak_style.c (5)

789

790

791

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

792

793

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

799

800

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

806

807

panel_with_type union_sensor;

808

809

union_sensor.panel_type = WATER_LEAK_TYPE;

......

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

814

815

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.

825

826

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.

827

828

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

image 7.39 sort.h

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

833

834

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

835

836

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

837

838

image 7.40 sort.c (1)

839

840

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

852

853

854

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

855

856

857

== 9.2 Packing Info ==

858

859

860

**Package Includes**:

861

862

* LTS5 HMI Touch Screen

863

* 5V,2A DC Power Adapter.

864

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

870

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

871

872

= 11. Reference material =

873

874

875

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

876

* schematic: [[LTS5-V1>>https://www.dropbox.com/scl/fo/grwr5b4x1tk2omyjwg06y/ACleSdi5f7p5zRB2mfPH7CE?rlkey=vhcs83jrj9tkmw8wa9m9wo5rx&st=hkhe3bbj&dl=0]]

877

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

884

885

(1) This device may not cause harmful interference;