Wiki source code of LTS5 LoRa HMI Touch Screen

Version 184.1 by BoYang Xie on 2025/05/05 11:20

version	line-number	content
133.2	1
	2
56.1	3	(% style="text-align:center" %)
133.2	4	[[image:image-20241226135550-1.png]]
2.1	5
	6
56.1	7
	8
2.1	9	(% _mstvisible="1" %)
56.1	10	(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)Table of Contents:
2.1	11
	12	{{toc/}}
	13
	14
	15
	16
	17
	18
	19
	20
	21	= 1. Introduction =
	22
116.1	23	== 1.1 What is the LTS5 LoRa HMI Touch Screen? ==
2.1	24
56.1	25
116.1	26	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.
2.1	27
116.1	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.
2.1	29
116.1	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.
2.1	31
116.1	32	The LA66 LoRa module can be programmed to support either private LoRa protocols or the LoRaWAN protocol.
2.1	33
	34	== 1.2 Features ==
	35
115.1	36
55.1	37	* ESP32-WROOM MCU: 8MB RAM & 16MB ROM
	38	* Dragino LA66 LoRa Module
4.2	39	* Support Private LoRa protocol or LoRaWAN protocol
	40	* Support WiFi & BLE wireless protocol
	41	* 5.0" HMI touch screen
4.6	42	* Support LVGL case. SquareLine program.
4.2	43	* Support RS485 Interface
	44	* Open Source Project
2.1	45	* Wall Attachable.
4.2	46	* 5V DC power
2.1	47	* IP Rating: IP52
	48
116.1	49	== 1.3 Specifications ==
2.1	50
56.1	51
4.9	52	LoRa:
	53
55.1	54	* 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
4.9	60
4.7	61	WiFi:
	62
	63	* 802.11b/g/n
	64	* 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
	68
	69	Bluetooth:
	70
	71	* Bluetooth V4.2 BR/EDR and Bluetooth LE standard
	72	* Class-1, Class-2, and Class-3 transmitters.
	73	* AFH
	74	* CVSD and SBC
	75
4.2	76	Display:
2.1	77
4.9	78	* 5.0 Inch , 800 x 480
	79	* IPS Capacitive Touch SCreen
4.11	80	* RGB color.
	81	* Display Area: 120.7*75.80 mm
2.1	82
	83	== 1.4 Power Consumption ==
	84
56.1	85
4.5	86	* External 5V DC power adapter
2.1	87
	88	== 1.5 Storage & Operation Temperature ==
	89
56.1	90
4.10	91	* Operation Temperature: -20 ~~ 70°C (No Dew)
	92	* Storage Temperature: -30 ~~ 70°C (No Dew)
2.1	93
	94	== 1.6 Applications ==
	95
56.1	96
2.1	97	* Smart Buildings & Home Automation
	98	* Logistics and Supply Chain Management
	99	* Smart Metering
	100	* Smart Agriculture
	101	* Smart Cities
	102	* Smart Factory
	103
122.1	104	= 2. Getting Started with 'Hello World' =
2.1	105
5.1	106	== 2.1 About this demo ==
2.1	107
56.1	108
117.1	109	This getting started example demonstrates how to design and deploy a simple display UI for the LTS5 device. The example includes:
2.1	110
117.1	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.
56.1	114
117.1	115	By completing this demo, you will gain foundational knowledge for customizing the LTS5 interface and building more advanced IoT applications.
	116
	117
5.1	118	== 2.2 Install Software Running Environment ==
2.1	119
115.1	120
120.1	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.
2.1	122
115.1	123
120.1	124	=== 2.2.1 Install VS Code and ESP-IDF extension ===
26.2	125
56.1	126
120.1	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]].
26.2	128
120.1	129	Next, install the ESP-IDF extension within VS Code. Detailed steps for this process are shown in Image 1.
26.2	130
120.1	131
51.2	132	[[image:image-20240928110211-5.png\|\|height="508" width="866"]]
	133
120.1	134	Image 1: ESP-IDF extension install
26.2	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
56.1	138
5.1	139	=== 2.2.2 Install SquareLine Studio ===
2.1	140
56.1	141
125.1	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.
2.1	143
133.2	144	[[image:squareline.io_downloads.png\|\|height="888" width="1294"]]
2.1	145
56.1	146
121.1	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:
120.1	148
121.1	149	* Max. 10 screens
	150	* Max. 150 widgets
	151	* Max. 5 global colors
	152	* Max. 2 themes
	153	* Max. 1 component
120.1	154
121.1	155	== 2.3 Simple usage of SquareLine Studio and exporting UI code ==
2.1	156
56.1	157
131.1	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.
2.1	159
125.1	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.
121.1	162
133.2	163	[[image:squareline-studio-launcher-screen.png\|\|height="752" width="1415"]]
26.2	164
	165
131.1	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
26.2	168	[[image:1727229582471-566.png]]
	169
	170
131.1	171	In the PROJECT SETTINGS dialog box, configure/modify the project settings as shown in the image below.
121.1	172
179.1	173	* UI Files Export Path: Select a folder on your computer to store the UI files.
121.1	174	* LVGL Include Path: Set this to lvgl.h
131.1	175	* Click on the APPLY CHANGES button.
121.1	176
51.2	177	[[image:image-20240928105309-4.png\|\|height="526" width="556"]]
	178
26.2	179
131.1	180	Now you can start building the user interface. Follow the steps below:
26.2	181
121.1	182
123.2	183	=== Add widgets ===
26.2	184
123.2	185
180.1	186	After creating a project, a Screen will be automatically added. Its name is Screen1 by default.
	187
131.1	188	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.
26.2	189
51.2	190	[[image:image-20240928111412-6.png\|\|height="526" width="864"]]
26.2	191
	192
131.1	193	Then click the Screen widget to add the second screen. After adding the second screen, it will appear in the Screens panel as Screen2.
26.2	194
131.1	195	[[image:Screenshot 2024-12-24 140459.png\|\|height="278" width="290"]]
	196
123.2	197	=== Modify widget properties ===
	198
	199
131.1	200	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.
26.2	201
51.2	202	[[image:1727485118799-984.png]]
26.2	203
	204
123.2	205	==== Changing the Button properties ====
122.1	206
123.2	207
131.1	208	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:
122.1	209
131.1	210	* Flex Flow: No Layout
	211	* Transform:
	212	X**: 331 px
	213	Y**: 203 px
	214	Width**: 100 px
	215	Height**: 50 px
	216	Align**: CENTER
122.1	217
51.2	218	[[image:1727485251053-655.png]]
26.2	219
	220
123.1	221	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.
26.2	222
131.1	223	* Click ADD EVENT button. A new section will appear to configure this event.
26.2	224
131.1	225	[[image:Screenshot 2024-12-24 134937.png\|\|height="80" width="290"]]
	226
	227	* 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.
	228
	229	[[image:Screenshot 2024-12-24 134818.png\|\|height="222" width="290"]]
	230
	231	* 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.
	232	* Finally, click the ADD button.
	233
51.2	234	[[image:1727485480434-713.png\|\|height="395" width="290"]]
26.2	235
123.2	236	Image 8: Add an event for the button
51.2	237
	238
123.2	239	==== Changing the label properties ====
51.2	240
123.2	241
131.1	242	Click the Label you have added to the screen. Under the Label section, type "Click for Detail" in the Text textbox.
122.1	243
51.2	244	[[image:image-20240928090825-1.png\|\|height="327" width="391"]]
	245
	246
131.1	247	Once you enter the text, it will immediately appear on the label.
51.2	248
131.1	249
123.2	250	==== Changing image properties ====
122.1	251
123.2	252
131.1	253	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.
51.2	254
131.1	255	One way is to move your image into the folder "…/squareline project/assets/", as shown in the image below.
	256
51.2	257	[[image:image-20240928113424-9.png\|\|height="355" width="505"]]
	258
	259
131.1	260	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.
	261
51.2	262	[[image:image-20240928114139-10.png\|\|height="559" width="810"]]
	263
	264
123.2	265	==== The relationship between widgets ====
51.2	266
123.2	267
123.1	268	Widgets commonly have two types of relationships: parallel and parent-child.
	269
	270	* In a parallel relationship, widgets' positions are determined relative to a shared reference object.
132.1	271	* 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.
123.1	272
51.2	273	[[image:1727486567182-334.png\|\|height="318" width="278"]]
	274
	275
131.1	276	Move the label, Label1 to make it a child of Button1 as shown in the image below.
123.1	277
51.2	278	[[image:image-20240928112001-8.png\|\|height="431" width="796"]]
	279
	280
131.1	281	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.
51.2	282
131.1	283	[[image:Screenshot 2024-12-24 144005.png\|\|height="360" width="290"]]
	284
	285
123.2	286	==== Preview the screen ====
51.2	287
123.2	288
132.1	289	You can test the result by clicking on the PLAY button as shown in the image below. The screen will change into play mode.
122.1	290
51.2	291	[[image:1727487368023-281.png]]
	292
	293
123.1	294	For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~\| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
51.2	295
123.1	296
181.1	297	== 2.4 Integrate UI Code into an ESP-IDF Project ==
26.2	298
56.1	299
132.1	300	To integrate, first export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
26.2	301
135.1	302	On the menubar, click Export -> Export UI Files as shown in the image below.
	303
26.2	304	[[image:1727229798126-306.png]]
	305
	306
135.1	307	The exported UI files can be found in your SquareLine project folder as shown in the image below.
	308
	309
51.2	310	[[image:1727229821582-258.png\|\|height="333" width="662"]]
26.2	311
	312
135.1	313	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.
26.2	314
54.1	315	[[image:image-20240928144830-11.png]]
26.2	316
	317
135.1	318	Open the CMakeLists.txt file and edit it as ahown below.
	319
51.2	320	[[image:1727229892636-154.png\|\|height="521" width="407"]]
26.2	321
	322
135.1	323	Open the main.c file and add two lines of code as shown in the below images.
132.1	324
135.1	325	Add #include "ui.h"
26.2	326
	327	[[image:1727229926561-300.png]]
	328
	329
135.1	330	Add ui_init();
	331
26.2	332	[[image:1727229955611-607.png]]
	333
	334
135.1	335	== 2.5 Brief introduction to the Hello World project ==
56.1	336
2.1	337
135.1	338	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.
56.1	339
51.2	340
	341	== 2.6 Test Result ==
	342
56.1	343
135.1	344	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.
2.1	345
135.1	346	Screen 1:
	347
51.2	348	[[image:1727488067077-684.png\|\|height="402" width="574"]]
26.2	349
	350
135.1	351	Screen 2:
	352
51.2	353	[[image:1727488157579-949.png\|\|height="397" width="572"]]
26.2	354
	355
5.1	356	= 3. Example Project 1: LoRa Central Display =
2.1	357
7.1	358	[[image:image-20240916101737-1.png\|\|height="468" width="683"]]
2.1	359
7.1	360
8.1	361	= 4. Example Project 2: LoRaWAN RS485 Alarm =
2.1	362
165.2	363	= 5. Example Project 3: P2P =
164.2	364
	365	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.
	366
	367	The project can be found at [[this link>>url:https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/P2P]].
	368
182.1	369	== 5.1 Firmware Flashing ==
164.2	370
	371
182.1	372	The following software tools are required to flash firmware to the ESP32 and LA66.
164.2	373
182.1	374	* 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]].
	375	* Download the LA66 firmware flash tool from [[this link>>https://www.dropbox.com/scl/fo/9kqeqf6wmet10o9hgxuwa/h?rlkey=4ikrg6kg5v0yjxwhp0i37wrv7&e=1&dl=0]].
164.2	376
182.1	377	=== 5.1.1 Upload the Firmware to the ESP32 ===
164.2	378
182.1	379	Open //flash_download_tool.exe// and follow the steps below.
	380
	381	* Chip Type: ESP32-S3
	382	* WorkMode: Develop
	383	* LoadMode: UART
	384	* Click on the OK button.
	385
164.2	386	[[image:1738893226894-758.png\|\|height="170" width="176"]]
	387
182.1	388
	389	In the SPIDownload tab,
	390
	391	* Select the checkboxes for //bootloader.bin, partition-table.bin, ota_data_initial.bin//, and //project.bin//.
	392	* SPI Flashing Config:
	393	SPI SPEED**: 40MHz
	394	SPI MODE**: DIO
	395	Check DoNotChgBin** option.
	396	* COM: Select the correct COM port.
	397	* BAUD: 1152000
	398	* Click on the START button.
	399
164.2	400	[[image:image-20250207100150-7.png\|\|height="476" width="538"]]
	401
	402
182.1	403	The progress bar will indicate the firmware update progress and display a FINISH message once the update is complete.
164.2	404
182.1	405
	406	=== 5.1.2 Upload the Firmware to the LA66 ===
	407
	408	Open Dragino_Sensor_Manager_Utility.exe, and then follow the steps below.
	409
	410	* Click on the UART Update Firmware tab.
	411	* Select the correct COM port.
	412	* Click on the Upload_File button and select the DRAGINO-LRWAN-AT.bin file.
	413	* Click on the Start button.
	414
164.2	415	[[image:image-20250207101415-8.png\|\|height="522" width="618"]]
	416
182.1	417
164.2	418	[[image:image-20250207101515-9.png\|\|height="522" width="618"]]
	419
182.1	420
	421	(% class="wikigeneratedid" %)
	422	The progress bar will indicate the firmware update progress.
	423
	424
183.1	425	== 5.2 AT commands and LTS5 Panel Data Formats ==
164.2	426
	427	AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A801A4CBBB0A8E085C02,0,3
	428
	429	AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A802A4CB00,0,3
	430
	431	AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A803A4CB00,0,3
	432
	433	AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A804A4CB00,0,3
	434
	435	AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A805A4CB00,0,3
	436
	437	AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A806A4CB00,0,3
	438
178.1	439	LTS5 panel data format:
164.2	440
178.1	441	~1. AT+SEND=1,01 4b69746368656e2d467269676531FFFF A84041000181D4A8 01 A4CB BB0A 8E08 5C02,0,3
164.2	442
	443	01: encrypt. 1 Byte. 01 ~-~-> no encryption. This 1-byte information is now invalid; simply write 0x01 instead.
	444
	445	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.
	446
	447	A84041000181D4A8: Device EUI. 8 Bytes. The last three Bytes will be extracted by the ESP32-S3 and displayed on the screen.
	448
	449	01: Panel Type. 1 Byte. 0x01~-~->Tem & Hum,
	450
	451	0x02~-~->Door,
	452
	453	0x03~-~->Water Leak,
	454
	455	0x04~-~->Occupied,
	456
	457	0x05~-~->Button,
	458
	459	0x06~-~->Alarm,
	460
	461	A4CB: Battery level//. //2 Bytes. Battery Voltage =0xCBA4&0x3FFF=0x0BA4=2980mV
	462
	463	BB0A: The temperature of the built-in sensor in LHT65N.// //2 Bytes. Temperature: 0x0ABB/100=27.47℃
	464
	465	8E08: The temperature of the External temperature sensor.// //2 Bytes. Temperature: 0x088E/100=21.90℃
	466
	467	5C02：The humidity of the built-in sensor in LHT65N. 2 Bytes. Humidity: 0x025C/10=60.4%
	468
	469	2. AT+SEND=1,01 4b69746368656e2d467269676531FFFF A84041000181D4A8 02 A4CB 00,0,3
	470
	471	Specific sections of the data share the same function.
	472
	473	00: Status. 1 Byte//. //If Panel Type is 0x02, Status: 00~-~->Open; 01~-~->Close.
	474
	475	If Panel Type is 0x03, Status: 00~-~->Normal; 01~-~->Water Leaking.
	476
	477	If Panel Type is 0x04, Status: 00~-~->Free; 01~-~->Occupied.
	478
	479	If Panel Type is 0x05, Status: 00~-~->OFF; 01~-~->ON.
	480
	481	If Panel Type is 0x06, Status: 00~-~->OFF; 01~-~->Alarm.
	482
	483	== 5.3 Usage ==
	484
	485	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.
	486
	487	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.
	488
	489	[[image:image-20250207143131-11.png\|\|height="527" width="547"]]
	490
	491	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.
	492
	493	[[image:image-20250207144605-12.png\|\|height="634" width="548"]]
	494
178.1	495	LTS5 receives this message and displays it on its screen as the image below shows.
	496
	497	[[image:image-20250208181700-8.jpeg\|\|height="528" width="704"]]
	498
164.2	499	= 6. Example Project 4: LoRaWAN_CLASS_C =
	500
	501
	502	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.
	503
	504	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.
	505
	506	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).
	507
	508	The project can be found at [[this link>>https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/LoRaWAN_CLASS_C]].
	509
	510	== 6.1 firmware flashing approach ==
	511
165.3	512	The firmware flashing approach is the same as described in section 5.1.
164.2	513
	514	== 6.2 flowchart ==
	515
	516	[[image:image-20250207164320-13.png\|\|height="696" width="1344"]]
	517
	518	== 6.3 Usage ==
	519
165.3	520	This section now describes a process involving TTN downlink panel data that is to be displayed on the LTS5 screen.
164.2	521
	522	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.
	523
	524	[[image:image-20250207165702-14.png\|\|height="830" width="563"]]
	525
	526	6.3.2 Switch to Class C using "AT+CLASS=C", and check the class with "AT+CLASS=?".
	527
	528	[[image:image-20250207173212-27.png]]
	529
	530	[[image:image-20250207172246-20.png]]
	531
	532	6.3.3 Verify LA66's join status (in LTS5) with "AT+NJS=?". If not joined, connect manually to LoRaWAN with "AT+JOIN".
	533
	534	[[image:image-20250207172010-19.png]]
	535
	536	[[image:image-20250207171650-17.png]]
	537
	538	6.3.4 After joining, send a message to TTN, such as "AT+SENDB=01,02,8,05820802581ea0a5", to activate communication.
	539
	540	[[image:image-20250207192107-28.png]]
	541
165.3	542	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.
164.2	543
165.3	544	There is an example for TTN downlink.
165.2	545
164.2	546	1. downlink DEUI F1A84041000181D4A8
	547	1. downlink Dev Name F24B69746368656E2D467269676531FFFF
165.2	548	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.
164.2	549
178.1	550	[[image:image-20250208175819-1.png\|\|height="503" width="502"]]
	551
	552
	553	[[image:image-20250208175918-2.png\|\|height="505" width="502"]]
	554
	555
	556	[[image:image-20250208180010-3.png\|\|height="507" width="503"]]
	557
	558
	559	[[image:image-20250208181019-4.jpeg\|\|height="592" width="790"]]
	560
	561
	562	[[image:image-20250208181328-7.png\|\|height="505" width="504"]]
	563
	564
	565	[[image:image-20250208181139-5.jpeg\|\|height="594" width="792"]]
	566
	567
165.3	568	= 7. The method for adding a new type of panel to the project =
2.1	569
141.2	570	If you don't have this need, then this part of the content can be ignored.
123.2	571
165.3	572	1. Design a panel in SquareLine Studio, as shown in Image 7.1 below for reference.
75.1	573
	574	[[image:image-20241121113445-1.png\|\|height="584" width="934"]]
	575
165.3	576	Image 7.1: a panel about water_leak
75.1	577
123.2	578
165.3	579	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.
75.1	580
	581	[[image:image-20241121141120-4.png\|\|height="383" width="795"]]
	582
165.3	583	Image 7.2: Exported UI files
75.1	584
123.2	585
141.2	586	3. Delete and rename some file. Here are the steps:
75.1	587
135.1	588	Step 1: Delete the 'components' directory.
	589	Step 2: Delete 'filelist.txt'.
	590	Step 3: Delete 'ui_helpers.c' and 'ui_helpers.h'.
	591	Step 4: Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
	592	Step 5: Rename the 'screens' directory to 'styles'.
75.1	593
	594	[[image:image-20241121151934-10.png\|\|height="303" width="792"]]
	595
165.3	596	image 7.3 rest file (1)
75.1	597
	598	[[image:image-20241121142925-7.png\|\|height="141" width="793"]]
	599
165.3	600	image 7.4 rest file (2)
75.1	601
165.3	602	4. Open the project in VS Code.
75.1	603
165.3	604	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."
75.1	605
	606	[[image:image-20241121181957-17.png\|\|height="438" width="516"]]
	607
165.3	608	image 7.5 extra_lib/CMakeLists.txt before adding
75.1	609
	610	[[image:image-20241121182239-18.png\|\|height="520" width="518"]]
	611
165.3	612	image 7.6 extra_lib/CMakeLists.txt after adding
75.1	613
141.2	614	6. Modify the header files included in the fonts and images directories.
75.1	615
165.3	616	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.
135.1	617
75.1	618	[[image:image-20241121171629-11.png]]
	619
165.3	620	image 7.7 unmodified font file
75.1	621
	622	[[image:image-20241121171901-12.png]]
	623
165.3	624	image 7.8 modified font file
75.1	625
165.3	626	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.
75.1	627
	628	[[image:image-20241121172714-13.png]]
	629
165.3	630	image 7.9 unmodified image file
75.1	631
	632	[[image:image-20241121172908-14.png]]
	633
165.3	634	image 7.10 modified image file
75.1	635
165.3	636	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).
75.1	637
	638	[[image:image-20241121180030-15.png]]
	639
165.3	640	image 7.11 ui_water_leak/CMakeLists.txt before modification
75.1	641
	642	[[image:image-20241121180517-16.png]]
	643
165.3	644	image 7.12 ui_water_leak/CMakeLists.txt after modification
75.1	645
	646
165.3	647	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.
135.1	648
113.2	649	[[image:image-20241122094200-23.png]]
75.1	650
165.3	651	image 7.13 ui_water_leak.h (1) before modification
75.1	652
113.2	653	[[image:image-20241122094320-24.png\|\|height="852" width="554"]]
75.1	654
165.3	655	image 7.14 ui_water_leak.h (2) before modification
75.1	656
113.2	657	[[image:image-20241122094600-25.png\|\|height="1078" width="554"]]
75.1	658
165.3	659	image 7.15 ui_water_leak.h (1) after modification
75.1	660
113.2	661	[[image:image-20241122094719-26.png\|\|height="941" width="583"]]
75.1	662
165.3	663	image 7.16 ui_water_leak.h (2) before modification
75.1	664
165.3	665	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.
75.1	666
113.2	667	_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.
75.1	668
113.2	669	[[image:image-20241122102929-27.png\|\|height="619" width="426"]]
	670
165.3	671	image 7.17 ui_water_leak.c (1) before modification
113.2	672
	673	[[image:image-20241122112838-30.png\|\|height="551" width="628"]]
	674
165.3	675	image 7.18 ui_water_leak.c (2) before modification
113.2	676
	677	[[image:image-20241122110815-29.png\|\|height="725" width="712"]]
	678
165.3	679	image 7.19 ui_water_leak.c (3) before modification
113.2	680
	681	[[image:image-20241122113158-31.png\|\|height="872" width="677"]]
	682
165.3	683	image 7.20 ui_water_leak.c (1) after modification
113.2	684
	685	[[image:image-20241122113259-33.png\|\|height="874" width="724"]]
	686
165.3	687	image 7.21 ui_water_leak.c (2) after modification
113.2	688
	689	[[image:image-20241122113359-34.png\|\|height="804" width="746"]]
	690
165.3	691	image 7.22 ui_water_leak.c (3) after modification
113.2	692
165.3	693	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.
113.2	694
	695	[[image:image-20241122134113-35.png\|\|height="380" width="421"]]
	696
165.3	697	image 7.23 ui_water_leak_events_.h before modification
113.2	698
	699	[[image:image-20241122134420-37.png\|\|height="201" width="283"]]
	700
165.3	701	image 7.24 ui_water_leak_events_.h after modification
113.2	702
165.3	703	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.
113.2	704
	705	Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
	706
	707	Step2. add code below in delete_object() function definition.
	708
	709	panel_all * panel = find_upper_by_SensorPanel(&arr,((lv_obj_t *)(e->user_data~)~)~);
	710
	711	size_t index = panel->panel_obj_index;
	712
	713	deleteElement(&arr, index);
	714
	715	[[image:image-20241122135023-38.png\|\|height="358" width="372"]]
	716
165.3	717	image 7.25 ui_water_leak_events_.c before modification
113.2	718
	719	[[image:image-20241122135258-39.png\|\|height="403" width="559"]]
	720
165.3	721	image 7.26 ui_water_leak_events_.c after modification
113.2	722
123.2	723
141.2	724	12. Modify ui_water_leak_style.c file.
113.2	725
	726	Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
	727
	728	add '#include "../../sort.h"'
	729
	730	add '#include "ui.h"'
	731
	732	[[image:image-20241122141536-41.png\|\|height="361" width="612"]]
	733
165.3	734	image 7.27 ui_water_leak_style.c (1) before modification
113.2	735
	736	[[image:image-20241122142129-42.png\|\|height="386" width="613"]]
	737
165.3	738	image 7.28 ui_water_leak_style.c (1) after modification
113.2	739
123.2	740
113.2	741	Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
	742
165.3	743	delete code as shown in image 7.29
113.2	744
	745	[[image:image-20241122145620-44.png\|\|height="757" width="671"]]
	746
165.3	747	image 7.29 ui_water_leak_style.c (2)
113.2	748
123.2	749
165.3	750	Step3. The image 7.30, 7.31 show the change.
113.2	751
	752	[[image:image-20241122152026-45.png\|\|height="277" width="828"]]
	753
165.3	754	image 7.30 ui_water_leak_style.c (3) before modification
113.2	755
	756	[[image:image-20241122152542-46.png\|\|height="293" width="830"]]
	757
165.3	758	image 7.31 ui_water_leak_style.c (3) after modification
113.2	759
123.2	760
165.3	761	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).
113.2	762
	763	[[image:image-20241122153958-47.png]]
	764
165.3	765	image 7.32 ui_water_leak_style.c (4)
113.2	766
141.2	767
113.2	768	[[image:image-20241122154755-49.png\|\|height="864" width="513"]]
	769
165.3	770	image 7.33 ui_water_leak_style.c (4)
113.2	771
123.2	772
165.3	773	Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 7.34).
113.2	774
	775	[[image:image-20241122155650-50.png\|\|height="922" width="513"]]
	776
165.3	777	image 7.34 ui_water_leak_style.c (5)
113.2	778
123.2	779
165.3	780	Step6. Add some lines of code in extra_lib/sort.h as shown in image 7.35.
113.2	781
	782	[[image:image-20241122161934-51.png]]
	783
165.3	784	image 7.35
113.2	785
123.2	786
165.3	787	Step7. Add a line of code in extra_lib/sort.h as shown in image 7.36.
113.2	788
	789	[[image:image-20241122162852-53.png\|\|height="330" width="529"]]
	790
165.3	791	image 7.37
113.2	792
123.2	793
165.3	794	Step8. Add some code in ui_water_leak_style.c as shown in image 7.38 from line534 to line 576 in detail.
113.2	795
	796	panel_with_type union_sensor;
	797
	798	union_sensor.panel_type = WATER_LEAK_TYPE;
	799
	800	......
	801
	802	lv_obj_set_x(union_sensor.panel_union.door.ui_PanelSensorDoor, x_by_index(index));
	803
	804	lv_obj_set_y(union_sensor.panel_union.door.ui_PanelSensorDoor, y_by_index(index));
	805
	806	return union_sensor;
	807
141.2	808	[[image:image-20250122173546-6.png\|\|height="777" width="922"]]
113.2	809
165.3	810	image 7.38
113.2	811
123.2	812
141.2	813	13. Rest midification in sort.h file.
113.2	814
165.3	815	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.
113.2	816
141.2	817	[[image:image-20250122170230-1.png\|\|height="580" width="513"]]
113.2	818
165.3	819	image 7.39 sort.h
113.2	820
141.2	821	13. Modify sort.c file.
	822
	823	Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 26.
	824
	825	[[image:image-20250122171910-5.png\|\|height="524" width="510"]]
	826
165.3	827	image 7.40 sort.c (1)
141.2	828
113.2	829	There are still some changes need to be done in sort.c, and omit here for the moment.
	830
	831
141.2	832
165.3	833	= 8. FAQ =
2.1	834
165.3	835	== 8.1 ==
2.1	836
	837
165.3	838	= 9. Order Info =
2.1	839
165.3	840	== 9.1 Part Number ==
2.1	841
56.1	842
4.4	843	Part Number: (% style="color:#4472c4" %)LTS5
2.1	844
	845
165.3	846	== 9.2 Packing Info ==
2.1	847
56.1	848
4.4	849	Package Includes:
2.1	850
4.4	851	* LTS5 HMI Touch Screen
	852	* 5V,2A DC Power Adapter.
	853	* USB Type C Program Cable
2.1	854
165.3	855	= 10. Support =
2.1	856
56.1	857
2.1	858	* 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.
	859	* 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]].
	860
165.3	861	= 11. Reference material =
2.1	862
56.1	863
4.2	864	* Datasheet
178.1	865	* schematic: [[LTS5-V1>>attach:LTS5-V1.pdf]]
141.2	866	* 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]]
4.3	867	* Mechinical
2.1	868
165.3	869	= 12. FCC Warning =
2.1	870
	871
	872	This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
	873
	874	(1) This device may not cause harmful interference;
	875
	876	(2) this device must accept any interference received,including interference that may cause undesired operation.
	877

Wiki source code of LTS5 LoRa HMI Touch Screen

Applications