Skip to Content
Last modified by BoYang Xie on 2025/07/24 16:47
From version 4.12
edited by Edwin Chen
on 2024/09/16 09:37
Change comment: There is no comment for this version
To version 164.2
edited by BoYang Xie
on 2025/02/07 19:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.xieby
Content
... ... @@ -1,9 +1,13 @@
1 -
2 -[[image:image-20240915231842-1.png]]
1 +
3 3  
3 +(% style="text-align:center" %)
4 +[[image:image-20241226135550-1.png]]
4 4  
6 +
7 +
8 +
5 5  (% _mstvisible="1" %)
6 -(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents：**
10 +(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:**
7 7  
8 8  {{toc/}}
9 9  
... ... @@ -16,20 +16,22 @@
16 16  
17 17  = 1.  Introduction =
18 18  
19 -== 1.1  What is LTS5 LoRa HMI touch screen ==
23 +== 1.1  What is the LTS5 LoRa HMI Touch Screen? ==
20 20  
21 -LTS5 is a (% style="color:blue" %)LoRa / LoRaWAN HMI Touch Screen(%%) designed for display purpose of IoT project. It have a 5.0" HMI touch screen, and support WiFi, Bluetooch, LoRa wireless protocol.
22 22  
23 -LTS5 is an Open Source software project. The MCU is ESP32 and Dragino LA66 LoRa module. There are lots of development source for ESP32 which can greatly reduce the development time.
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.
24 24  
25 -The HMI touch screen of LTS5 supports drap & drop design. Developer can use SquareLine to easily customize the display UI for different application.
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.
26 26  
27 -LTS5 use LA66 LoRa module, this module can be program to support private LoRa protocol or LoRaWAN protocol.
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.
28 28  
32 +The LA66 LoRa module can be programmed to support either private LoRa protocols or the LoRaWAN protocol.
29 29  
30 30  == 1.2  Features ==
31 31  
32 -* ESP32-WROOM MCU + Dragino LA66 LoRa Module
36 +
37 +* ESP32-WROOM MCU: 8MB RAM & 16MB ROM
38 +* Dragino LA66 LoRa Module
33 33  * Support Private LoRa protocol or LoRaWAN protocol
34 34  * Support WiFi & BLE wireless protocol
35 35  * 5.0" HMI touch screen
... ... @@ -40,11 +40,17 @@
40 40  * 5V DC power
41 41  * IP Rating: IP52
42 42  
49 +== 1.3  Specifications ==
43 43  
44 -== 1.3  Specification ==
45 45  
46 46  **LoRa**:
47 47  
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
48 48  
49 49  **WiFi:**
50 50  
... ... @@ -68,21 +68,20 @@
68 68  * RGB color.
69 69  * Display Area: 120.7*75.80 mm
70 70  
71 -
72 -
73 73  == 1.4  Power Consumption ==
74 74  
85 +
75 75  * External 5V DC power adapter
76 76  
77 -
78 78  == 1.5  Storage & Operation Temperature ==
79 79  
90 +
80 80  * Operation Temperature: -20 ~~ 70°C  (No Dew)
81 81  * Storage Temperature: -30 ~~ 70°C  (No Dew)
82 82  
83 -
84 84  == 1.6  Applications ==
85 85  
96 +
86 86  * Smart Buildings & Home Automation
87 87  * Logistics and Supply Chain Management
88 88  * Smart Metering
... ... @@ -90,722 +90,680 @@
90 90  * Smart Cities
91 91  * Smart Factory
92 92  
104 += 2.  Getting Started with 'Hello World' =
93 93  
94 -= 2.  Operation Mode =
106 +== 2.1  About this demo ==
95 95  
96 -== 2.1  How it work? ==
97 97  
109 +This getting started example demonstrates how to design and deploy a simple display UI for the LTS5 device. The example includes:
98 98  
99 -Each PB01 is shipped with a worldwide unique set of LoRaWAN OTAA keys. To use PB01 in a LoRaWAN network, user needs to input the OTAA keys in LoRaWAN network server. After this, if PB01 is under this LoRaWAN network coverage, PB01 can join the LoRaWAN network and start to transmit sensor data. The default period for each uplink is** 20 minutes**.
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.
100 100  
115 +By completing this demo, you will gain foundational knowledge for customizing the LTS5 interface and building more advanced IoT applications.
101 101  
102 -== 2.2  How to Activate PB01? ==
103 103  
118 +== 2.2  Install Software Running Environment ==
104 104  
105 -(% style="color:red" %)** 1.  Open enclosure from below position.**
106 106  
107 -[[image:image-20220621093835-1.png]]
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.
108 108  
109 109  
110 -(% style="color:red" %)** 2.  Insert 2 x AAA LR03 batteries and the node is activated.**
124 +=== 2.2.1 Install VS Code and ESP-IDF extension ===
111 111  
112 -[[image:image-20220621093835-2.png]]
113 113  
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]].
114 114  
115 -(% style="color:red" %)** 3. Under the above conditions, users can also reactivate the node by long pressing the ACT button.**
129 +Next, install the **ESP-IDF** extension within **VS Code**. Detailed steps for this process are shown in Image 1.
116 116  
117 -[[image:image-20220621093835-3.png]]
118 118  
132 +[[image:image-20240928110211-5.png||height="508" width="866"]]
119 119  
120 -User can check [[LED Status>>||anchor="H2.8LEDIndicator"]] to know the working state of PB01.
134 + Image 1: ESP-IDF extension install
121 121  
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]]
122 122  
123 -== 2.3  Example to join LoRaWAN network ==
124 124  
139 +=== 2.2.2 Install SquareLine Studio ===
125 125  
126 -This section shows an example for how to join the [[TheThingsNetwork>>url:https://www.thethingsnetwork.org/]] LoRaWAN IoT server. Usages with other LoRaWAN IoT servers are of similar procedure.
127 127  
128 -(% _mstvisible="1" class="wikigeneratedid" %)
129 -Assume the LPS8v2 is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. We need to add the PB01 device in TTN V3 portal. 
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.
130 130  
131 -[[image:image-20240705094824-4.png]]
144 +[[image:squareline.io_downloads.png||height="888" width="1294"]]
132 132  
133 -(% style="color:blue" %)**Step 1**(%%):  Create a device in TTN V3 with the OTAA keys from PB01.
134 134  
135 -Each PB01 is shipped with a sticker with the default DEV EUI as below:
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:
136 136  
137 -[[image:image-20230426083617-1.png||height="294" width="633"]]
149 +* Max. 10 screens
150 +* Max. 150 widgets
151 +* Max. 5 global colors
152 +* Max. 2 themes
153 +* Max. 1 component
138 138  
155 +== 2.3 Simple usage of SquareLine Studio and exporting UI code ==
139 139  
140 -Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
141 141  
142 -Create application.
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**.
143 143  
144 -choose to create the device manually.
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.
145 145  
146 -Add JoinEUI(AppEUI), DevEUI, AppKey.(% style="display:none" %)
163 +[[image:squareline-studio-launcher-screen.png||height="752" width="1415"]]
147 147  
148 -[[image:image-20240507142116-1.png||height="410" width="1138"]](% style="display:none" %) (%%)
149 -
150 150  
151 -[[image:image-20240507142157-2.png||height="559" width="1147"]]
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.
152 152  
153 -[[image:image-20240507142401-3.png||height="693" width="1202"]]
168 +[[image:1727229582471-566.png]]
154 154  
155 -[[image:image-20240507142651-4.png||height="760" width="1190"]]
156 156  
157 -**Default mode OTAA**(% style="display:none" %)
171 +In the **PROJECT SETTINGS** dialog box, configure/modify the project settings as shown in the image below.
158 158  
173 +* **UI Files Export Root**: Select a folder on your computer to store the UI files.
174 +* **LVGL Include Path**: Set this to **lvgl.h**
175 +* Click on the **APPLY CHANGES** button.
159 159  
160 -(% style="color:blue" %)**Step 2**(%%):  Use ACT button to activate PB01 and it will auto join to the TTN V3 network. After join success, it will start to upload sensor data to TTN V3 and user can see in the panel.
177 +[[image:image-20240928105309-4.png||height="526" width="556"]]
161 161  
162 -[[image:image-20240507143104-5.png||height="434" width="1398"]]
163 163  
180 +Now you can start building the user interface. Follow the steps below:
164 164  
165 -== 2.4  Uplink Payload ==
166 166  
183 +=== **Add widgets** ===
167 167  
168 -Uplink payloads include two types: Valid Sensor Value and other status / control command.
169 169  
170 -* Valid Sensor Value: Use FPORT=2
171 -* Other control command: Use FPORT other than 2.
186 +To add a widget, navigate to the **Widgets** panel, and then click on the widget you want to add to the screen. You can reposition the widgets in the screen area by clicking and dragging them. Now add a **Label**, **Button**, and **Image** as shown in the image below. The added widgets are also displayed in the **Hierarchy **panel.
172 172  
173 -=== 2.4.1  Uplink FPORT~=5, Device Status ===
188 +[[image:image-20240928111412-6.png||height="526" width="864"]]
174 174  
175 175  
176 -Users can  get the Device Status uplink through the downlink command:
191 +Then click the **Screen **widget to add the second screen. After adding the second screen, it will appear in the Screens panel as **Screen2**.
177 177  
178 -(% style="color:#4472c4" %)**Downlink:  **(%%)**0x2601**
193 +[[image:Screenshot 2024-12-24 140459.png||height="278" width="290"]]
179 179  
180 -Uplink the device configures with FPORT=5.
195 +=== **Modify widget properties** ===
181 181  
182 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:370px" %)
183 -|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**Size(bytes)(% style="display:none" %) (%%)**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 30px;background-color:#4F81BD;color:white" %)**2**
184 -|(% style="width:99px" %)Value|(% style="width:62px" %)Sensor Model|(% style="width:80px" %)Firmware Version|(% style="width:82px" %)Frequency Band|(% style="width:85px" %)Sub-band|(% style="width:46px" %)BAT
185 185  
186 -[[image:image-20240507152130-12.png||height="469" width="1366"]](% style="display:none" %)
198 +The area for modifying widgets is called the **Inspector** panel. The Inspector panel consists of four sections: **COMPONENT**, **<WIDGET>**, **STYLE SETTINGS**, and **EVENTS**, as shown in the image below. The second section allows you to adjust a widget's layout, size, position, alignment, flags, states, and more. When you select a widget on the screen, the name of this section changes to match the name of the selected widget.
187 187  
188 -Example Payload (FPort=5):  [[image:image-20240507152254-13.png||height="26" width="130"]]
200 +[[image:1727485118799-984.png]]
189 189  
190 190  
191 -(% style="color:#4472c4" %)**Sensor Model**(%%): For PB01, this value is 0x35.
203 +==== **Changing the Button properties** ====
192 192  
193 -(% style="color:#4472c4" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version.
194 194  
195 -(% style="color:#4472c4" %)**Frequency Band**:
206 +Click the **Button **you have added to the screen. Under the **Layout** you can change the button's position and size. Use the following settings:
196 196  
197 -*0x01: EU868
208 +* **Flex Flow**: No Layout
209 +* **Transform**:
210 +** **X**: 331 px
211 +** **Y**: 203 px
212 +** **Width**: 100 px
213 +** **Height**: 50 px
214 +** **Align**: CENTER
198 198  
199 -*0x02: US915
216 +[[image:1727485251053-655.png]]
200 200  
201 -*0x03: IN865
202 202  
203 -*0x04: AU915
219 +Next, add a click event to the button. When the button is clicked, an event should trigger to change the current screen (Screen1) to a new screen (Screen2) with a fade effect and the transition from Screen1 to Screen2 should take 500ms.
204 204  
205 -*0x05: KZ865
221 +* Click **ADD EVENT** button. A new section will appear to configure this event.
206 206  
207 -*0x06: RU864
223 +[[image:Screenshot 2024-12-24 134937.png||height="80" width="290"]]
208 208  
209 -*0x07: AS923
225 +* Select **CLICKED** from the dropdown under **Trigger**. Choose **CHANGE SCREEN** under **Action**, then click the **ADD** button. A new section will appear to configure the action.
210 210  
211 -*0x08: AS923-1
227 +[[image:Screenshot 2024-12-24 134818.png||height="222" width="290"]]
212 212  
213 -*0x09: AS923-2
229 +* Select **Screen2** under **Screen to**. Select **FADE ON** from **Fade mode**. The default value **500** means the transition takes 500 milliseconds to appear the Screen2.
230 +* Finally, click the **ADD** button.
214 214  
215 -*0x0a: AS923-3
232 +[[image:1727485480434-713.png||height="395" width="290"]]
216 216  
234 + Image 8: Add an event for the button
217 217  
218 -(% style="color:#4472c4" %)**Sub-Band**(%%): value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
219 219  
220 -(% style="color:#4472c4" %)**BAT**(%%): shows the battery voltage for PB01.
237 +==== **Changing the label properties** ====
221 221  
222 -(% style="color:#4472c4" %)**Ex1**(%%): 0x0C DE = 3294mV
223 223  
240 +Click the Label you have added to the screen. Under the **Label** section, type "**Click for Detail**" in the **Text** textbox.
224 224  
225 -=== 2.4.2  Uplink FPORT~=2, Real time sensor value ===
242 +[[image:image-20240928090825-1.png||height="327" width="391"]]
226 226  
227 227  
228 -PB01 will send this uplink after Device Status uplink once join LoRaWAN network successfully. And it will periodically send this uplink. Default interval is 20 minutes and [[can be changed>>||anchor="H3.1A0DownlinkCommandSet"]].
245 +Once you enter the text, it will immediately appear on the label.
229 229  
230 -Uplink uses FPORT=2 and every 20 minutes send one uplink by default.
231 231  
232 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:460px" %)
233 -|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
234 -**Size(bytes)**
235 -)))|=(% style="width: 60px;background-color:#4F81BD;color:white" %)2|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
236 -**1**
237 -)))|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
238 -**1**
239 -)))|=(% style="width: 90px;background-color:#4F81BD;color:white" %)(((
240 -**2**
241 -)))|=(% style="width: 40px;background-color:#4F81BD;color:white" %)(((
242 -**2**
243 -)))
244 -|(% style="width:97px" %)(((
245 -Value
246 -)))|(% style="width:39px" %)Battery|(% style="width:39px" %)(((
247 -Sound_ACK
248 +==== **Changing image properties** ====
248 248  
249 -&Sound_key
250 -)))|(% style="width:100px" %)(((
251 -(((
252 -Alarm
253 -)))
254 -)))|(% style="width:77px" %)(((
255 -(((
256 -Temperature
257 -)))
258 -)))|(% style="width:47px" %)(((
259 -Humidity
260 -)))
261 261  
262 -Example in TTN.
251 +To use the **Image **widget, you should first add an image to your project. The image format must be PNG, and its resolution should not exceed 800x480 pixels. There are two ways to add an image file.
263 263  
264 -[[image:image-20240507150155-11.png||height="549" width="1261"]]
253 +One way is to move your image into the folder "…/squareline project/assets/", as shown in the image below.
265 265  
266 -Example Payload (FPort=2):  (% style="background-color:yellow" %)**0C EA 03 01 01 11 02 A8**
255 +[[image:image-20240928113424-9.png||height="355" width="505"]]
267 267  
268 -==== (% style="color:blue" %)**Battery:**(%%) ====
269 269  
270 -Check the battery voltage.
258 +The other way is to click the "**ADD FILE INTO ASSETS**" button, then select an image from your computer to import. After adding, you can see the image in the "**assets**" panel in SquareLine Studio, as shown in the image below.
271 271  
272 -* Ex1: 0x0CEA = 3306mV
273 -* Ex2: 0x0D08 = 3336mV
260 +[[image:image-20240928114139-10.png||height="559" width="810"]]
274 274  
275 -==== (% style="color:blue" %)**Sound_ACK & Sound_key:**(%%) ====
276 276  
277 -Key sound and ACK sound are enabled by default.
263 +==== **The relationship between widgets** ====
278 278  
279 -* Example1: 0x03
280 280  
281 - Sound_ACK: (03>>1) & 0x01=1, OPEN.
266 +Widgets commonly have two types of relationships: **parallel** and **parent-child**.
282 282  
283 -**~ ** Sound_key:  03 & 0x01=1, OPEN.
268 +* In a **parallel relationship**, widgets' positions are determined relative to a shared reference object.
269 +* In a **parent-child relationship**, any part of the child object outside the parent's boundaries is hidden by default. To make the child object fully visible, you must adjust its position to fit within the parent's range.
284 284  
285 -* Example2: 0x01
271 +[[image:1727486567182-334.png||height="318" width="278"]]
286 286  
287 - Sound_ACK: (01>>1) & 0x01=0, CLOSE.
288 288  
289 -**~ ** Sound_key:  01 & 0x01=1, OPEN.
274 +Move the label, **Label1** to make it a child of **Button1** as shown in the image below.
290 290  
276 +[[image:image-20240928112001-8.png||height="431" width="796"]]
291 291  
292 -==== (% style="color:blue" %)**Alarm:**(%%) ====
293 293  
294 -Key alarm.
279 +Then set the **X** and **Y** position of the label to **0** as shown in the image below. The label will appear on the button. If you move the button on the screen, the label will move along with it as part of the button.
295 295  
296 -* Ex1: 0x01 & 0x01=1, TRUE.
297 -* Ex2: 0x00 & 0x01=0, FALSE.
281 +[[image:Screenshot 2024-12-24 144005.png||height="360" width="290"]]
298 298  
299 -==== (% style="color:blue" %)**Temperature:**(%%) ====
300 300  
301 -* Example1:  0x0111/10=27.3℃
302 -* Example2:  (0xFF0D-65536)/10=-24.3℃
284 +==== **Preview the screen** ====
303 303  
304 -If payload is: FF0D :  (FF0D & 8000 == 1) , temp = (FF0D - 65536)/100 =-24.3℃
305 305  
306 -（FF0D & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative）
287 +You can test the result by clicking on the **PLAY** button as shown in the image below. The screen will change into play mode.
307 307  
289 +[[image:1727487368023-281.png]]
308 308  
309 -==== (% style="color:blue" %)**Humidity:**(%%) ====
310 310  
311 -* Humidity:    0x02A8/10=68.0%
292 +For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
312 312  
313 -=== 2.4.3  Uplink FPORT~=3, Datalog sensor value ===
314 314  
295 +== 2.4 Integrate UI Code to ESP-IDF Project ==
315 315  
316 -PB01 stores sensor value and user can retrieve these history value via downlink command. The Datalog sensor value are sent via FPORT=3.
317 317  
318 -[[image:image-20240510144912-1.png||height="471" width="1178"]](% style="display:none" %)
298 +To integrate, first export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
319 319  
300 +On the  menubar, click **Export -> Export UI** Files as shown in the image below.
320 320  
321 -* Each data entry is 11 bytes, to save airtime and battery, PB01 will send max bytes according to the current DR and Frequency bands.(% style="display:none" %)
302 +[[image:1727229798126-306.png]]
322 322  
323 -For example, in US915 band, the max payload for different DR is:
324 324  
325 -1. **DR0**: max is 11 bytes so one entry of data
326 -1. **DR1**: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
327 -1. **DR2**: total payload includes 11 entries of data
328 -1. **DR3**: total payload includes 22 entries of data.
305 +The exported UI files can be found in your SquareLine project folder as shown in the image below.
329 329  
330 -(% style="color:red" %)**Notice: PB01 will save 178 set of history data, If device doesn't have any data in the polling time. Device will uplink 11 bytes of 0.**
331 331  
332 -See more info about the [[Datalog feature>>||anchor="H2.6A0DatalogFeature"]].
308 +[[image:1727229821582-258.png||height="333" width="662"]]
333 333  
334 -(% style="display:none" %) (%%)
335 335  
336 -=== 2.4.4  Decoder in TTN V3 ===
311 +Create a new folder named "**ui**" at path "**basic_prj/app_components/ui/**", and copy all the exported UI code into it as shown in the image below.
337 337  
313 +[[image:image-20240928144830-11.png]]
338 338  
339 -In LoRaWAN protocol, the uplink payload is HEX format, user need to add a payload formatter/decoder in LoRaWAN Server to get human friendly string.
340 340  
341 -In TTN , add formatter as below:
316 +Open the **CMakeLists.txt** file and edit it as ahown below.
342 342  
343 -[[image:image-20240507162814-16.png||height="778" width="1135"]]
318 +[[image:1727229892636-154.png||height="521" width="407"]]
344 344  
345 -(((
346 -Please check the decoder from this link:  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]
347 -)))
348 348  
349 -(((
350 -
351 -)))
321 +Open the main.c file and  add two lines of code as shown in the below images.
352 352  
353 -== 2.5 Show data on Datacake ==
323 +Add **#include "ui.h"**
354 354  
325 +[[image:1727229926561-300.png]]
355 355  
356 -(((
357 -Datacake IoT platform provides a human friendly interface to show the sensor data in charts, once we have sensor data in TTN V3, we can use Datacake to connect to TTN V3 and see the data in Datacake. Below are the steps:
358 -)))
359 359  
360 -(((
361 -
362 -)))
328 +Add **ui_init();**
363 363  
364 -(((
365 -(% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the LoRaWAN network.
366 -)))
330 +[[image:1727229955611-607.png]]
367 367  
368 -(((
369 -(% style="color:blue" %)**Step 2**(%%):  Configure your Application to forward data to Datacake you will need to add integration. Go to TTN V3 Console ~-~-> Applications ~-~-> Integrations ~-~-> Add Integrations.
370 -)))
371 371  
372 -(((
373 -~1. Add Datacake:
374 -)))
333 +== 2.5 Brief introduction to the Hello World project ==
375 375  
376 -(((
377 -2. Select default key as Access Key:
378 -)))
379 379  
380 -(((
381 -3. In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add PB01:
382 -)))
336 +The project consists of two screens. The first screen displays the company's logo, the project name, and a button to navigate to the next screen. The second screen provides information about the HMI screen product through an image and includes a button to return to the previous screen.
383 383  
384 -(((
385 - Please refer to the figure below.
386 -)))
387 387  
388 -[[image:image-20240510150924-2.png||height="612" width="1186"]]
339 +== 2.6 Test Result ==
389 389  
390 390  
391 -Log in to DATACAKE, copy the API under the account.
342 +By pressing the button located at the bottom right, the screen switches to the next one as expected. This confirms that the UI file has been successfully integrated into the project and is functioning correctly.
392 392  
393 -[[image:image-20240510151944-3.png||height="581" width="1191"]]
344 +Screen 1:
394 394  
346 +[[image:1727488067077-684.png||height="402" width="574"]]
395 395  
396 396  
397 -[[image:image-20240510152150-4.png||height="697" width="1188"]]
349 +Screen 2:
398 398  
351 +[[image:1727488157579-949.png||height="397" width="572"]]
399 399  
400 -[[image:image-20240510152300-5.png||height="298" width="1191"]]
401 401  
354 += 3. Example Project 1: LoRa Central Display =
402 402  
403 -[[image:image-20240510152355-6.png||height="782" width="1193"]]
356 +[[image:image-20240916101737-1.png||height="468" width="683"]]
404 404  
405 -[[image:image-20240510152542-8.png||height="545" width="739"]]
406 406  
407 -[[image:image-20240510152634-9.png||height="748" width="740"]]
359 += 4. Example Project 2: LoRaWAN RS485 Alarm =
408 408  
361 += 5. Example Project 3: P2P =
409 409  
410 -[[image:image-20240510152809-10.png||height="607" width="732"]]
363 +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.
411 411  
412 -[[image:image-20240510153934-14.png||height="460" width="1199"]]
365 +The project can be found at [[this link>>url:https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/P2P]].
413 413  
367 +== 5.1 firmware flashing approach. ==
414 414  
415 -[[image:image-20240510153435-12.png||height="428" width="1197"]]
369 +5.1.1 Download this project
416 416  
371 +5.1.2 Download esp32 firmware flash tool in [[this link>>https://docs.espressif.com/projects/esp-test-tools/en/latest/esp32/production_stage/tools/flash_download_tool.html]].
417 417  
418 -Copy and paste the [[TTN decoder>>https://github.com/dragino/dragino-end-node-decoder]] here and save.
373 +5.1.3 Download la66 firmware flash tool in [[this link>>https://www.dropbox.com/scl/fo/9kqeqf6wmet10o9hgxuwa/h?rlkey=4ikrg6kg5v0yjxwhp0i37wrv7&e=1&dl=0]].
419 419  
420 -[[image:image-20240510153624-13.png||height="468" width="1195"]]
375 +5.1.4 Upload firmware to esp32
421 421  
377 +Open flash_download_tool.exe, and then follow the steps below.
422 422  
423 -Visual widgets please read the DATACAKE documentation.
379 +[[image:1738893226894-758.png||height="170" width="176"]]
424 424  
425 -(% style="display:none" %) (%%)
381 +[[image:image-20250207100150-7.png||height="476" width="538"]]
426 426  
427 -== 2.6  Datalog Feature ==
383 +5.1.5 Upload firmware to la66
428 428  
385 +Open Dragino_Sensor_Manager_Utility.exe, and then follow the steps below.
429 429  
430 -(% _msthash="315262" _msttexthash="32283004" _mstvisible="1" %)
431 -When user want to retrieve sensor value, he can send a poll command from the IoT platform to ask sensor to send value in the required time slot.
387 +[[image:image-20250207101415-8.png||height="522" width="618"]]
432 432  
389 +[[image:image-20250207101515-9.png||height="522" width="618"]]
433 433  
434 -=== 2.6.1  Unix TimeStamp ===
391 +== 5.2 AT command and P2P data format ==
435 435  
393 +AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**01**A4CBBB0A8E085C02,0,3
436 436  
437 -Unix TimeStamp shows the sampling time of uplink payload. format base on
395 +AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**02**A4CB00,0,3
438 438  
439 -[[image:image-20220523001219-11.png||_mstalt="450450" _mstvisible="3" height="97" width="627"]]
397 +AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**03**A4CB00,0,3
440 440  
441 -User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/||_mstvisible="3"]] :
399 +AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**04**A4CB00,0,3
442 442  
443 -For example: if the Unix Timestamp we got is hex 0x60137afd, we can convert it to Decimal: 1611889405. and then convert to the time: 2021 – Jan ~-~- 29 Friday 03:03:25 (GMT)
401 +AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**05**A4CB00,0,3
444 444  
403 +AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**06**A4CB00,0,3
445 445  
446 -[[image:1655782409139-256.png]]
405 +**Data format**:
447 447  
407 +~1. AT+SEND=1,**01** **4b69746368656e2d467269676531FFFF A84041000181D4A8 01  A4CB  BB0A  8E08  5C02**,0,3
448 448  
449 -=== 2.6.2  Poll sensor value ===
409 +**01:** encrypt. 1 Byte. 01 ~-~-> no encryption. This 1-byte information is now invalid; simply write 0x01 instead.
450 450  
411 +**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 451  
452 -(((
453 -User can poll sensor value based on timestamps from the server. Below is the downlink command.
454 -)))
413 +**A84041000181D4A8:** Device EUI. 8 Bytes. The last three Bytes will be extracted by the ESP32-S3 and displayed on the screen.
455 455  
456 -(((
457 -Timestamp start and Timestamp end use Unix TimeStamp format as mentioned above. Devices will reply with all data log during this time period, use the uplink interval.
458 -)))
415 +**01: **Panel Type. 1 Byte. 0x01~-~->Tem & Hum,
459 459  
460 -(((
461 -For example, downlink command [[image:image-20220621113526-13.png]] (% _mstvisible="3" style="display:none" %)
462 -)))
417 + 0x02~-~->Door,
463 463  
464 -(((
465 -Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00's data
466 -)))
419 + 0x03~-~->Water Leak,
467 467  
468 -(((
469 -Uplink Internal =5s，means PB01 will send one packet every 5s. range 5~~255s.
470 -)))
421 + 0x04~-~->Occupied,
471 471  
423 + 0x05~-~->Button,
472 472  
473 -=== 2.6.3  Datalog Uplink payload ===
425 + 0x06~-~->Alarm,
474 474  
427 +**A4CB: **Battery level//. //2 Bytes. Battery Voltage =0xCBA4&0x3FFF=0x0BA4=2980mV
475 475  
476 -See [[Uplink FPORT=3, Datalog sensor value>>||anchor="H2.4.3A0UplinkFPORT3D32CDatalogsensorvalue"]]
429 +**BB0A: **The temperature of the built-in sensor in LHT65N.// //2 Bytes. Temperature:  0x0ABB/100=27.47℃
477 477  
478 -(% style="display:none" %) (%%) (% style="display:none" %)
431 +**8E08: **The temperature of the External temperature sensor.// //2 Bytes. Temperature:  0x088E/100=21.90℃
479 479  
480 -== 2.7 Button ==
433 +**5C02：**The humidity of the built-in sensor in LHT65N. 2 Bytes. Humidity: 0x025C/10=60.4%
481 481  
435 +2. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF**  **A84041000181D4A8**  **02  A4CB  00**,0,3
482 482  
483 -* ACT button
437 +Specific sections of the data share the same function.
484 484  
485 -Long press this button PB01 will reset and join network again.
439 +**00: Status. **1 Byte//. //If Panel Type is 0x02, **Status: 00~-~->Open; 01~-~->Close.**
486 486  
487 -[[image:image-20240510161626-17.png||height="192" width="224"]]
441 + If Panel Type is 0x03, **Status: 00~-~->Normal; 01~-~->Water Leaking.**
488 488  
489 -* Alarm button
443 + If Panel Type is 0x04, **Status: 00~-~->Free; 01~-~->Occupied.**
490 490  
491 -Press the button PB01 will immediately uplink data, and alarm is "TRUE".
445 + If Panel Type is 0x05, **Status: 00~-~->OFF; 01~-~->ON.**
492 492  
493 -[[image:image-20240705095149-5.png||height="164" width="162"]](% style="display:none" %)
447 + If Panel Type is 0x06, **Status: 00~-~->OFF; 01~-~->Alarm.**
494 494  
449 +== 5.3 Usage ==
495 495  
496 -== 2.8 LED Indicator ==
451 +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.
497 497  
453 +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.
498 498  
499 -(((
500 -The PB01 has a triple color LED which for easy showing different stage.
501 -)))
455 +[[image:image-20250207143131-11.png||height="527" width="547"]]
502 502  
503 -Hold the ACT green light to rest, then the green flashing node restarts, the blue flashing once upon request for network access, and the green constant light for 5 seconds after successful network access
457 +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.
504 504  
505 -(((
506 -(% style="color:#037691" %)**In a normal working state**:
507 -)))
459 +[[image:image-20250207144605-12.png||height="634" width="548"]]
508 508  
509 -* When the node is restarted, hold the ACT (% style="color:green" %)**GREEN**(%%) lights up , then the (% style="color:green" %)**GREEN**(%%) flashing node restarts.The (% style="color:blue" %)**BLUE**(%%) flashing once upon request for network access, and the (% style="color:green" %)**GREEN**(%%) constant light for 5 seconds after successful network access(% style="color:#0000ff" %)**.**
510 -* During OTAA Join:
511 -** **For each Join Request uplink:** the (% style="color:green" %)**GREEN LED** (%%)will blink once.
512 -** **Once Join Successful:** the (% style="color:green" %)**GREEN LED**(%%) will be solid on for 5 seconds.
513 -* After joined, for each uplink, the (% style="color:blue" %)**BLUE LED**(%%) or (% style="color:green" %)**GREEN LED** (%%)will blink once.
514 -* Press the alarm button，The (% style="color:red" %)**RED**(%%) flashes until the node receives the ACK from the platform and the (% style="color:blue" %)**BLUE**(%%) light stays 5s.
461 += 6. Example Project 4: LoRaWAN_CLASS_C =
515 515  
516 -(((
517 -
518 -)))
519 519  
520 -== 2.9 Buzzer ==
464 +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.
521 521  
466 +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.
522 522  
523 -The PB01 has** button sound** and** ACK sound** and users can turn on or off both sounds by using [[AT+SOUND>>||anchor="H3.3A0Setbuttonsoundandbuttonalarm"]].
468 +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).
524 524  
525 -* (% style="color:#4f81bd" %)**Button sound**(%%)** **is the music produced by the node after the alarm button is pressed.
470 +The project can be found at [[this link>>https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/LoRaWAN_CLASS_C]].
526 526  
527 - Users can use[[ AT+OPTION>>||anchor="H3.4A0Setbuzzermusic2807E429"]] to set different button sounds.
472 +== 6.1 firmware flashing approach ==
528 528  
529 -* (% style="color:#4f81bd" %)**ACK sound **(%%)is the notification tone that the node receives ACK.
474 +The firmware flashing approach is the same as described in section [[5.1>>5.1]].
530 530  
531 -= 3.  Configure PB01 via AT command or LoRaWAN downlink =
476 +== 6.2 flowchart ==
532 532  
478 +[[image:image-20250207164320-13.png||height="696" width="1344"]]
533 533  
534 -Users can configure PB01 via AT Command or LoRaWAN Downlink.
480 +== 6.3 Usage ==
535 535  
536 -* AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
482 +6.3.1 TTN downlink panel data to display in LTS5
537 537  
538 -* LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
484 +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.
539 539  
540 -There are two kinds of commands to configure PB01, they are:
486 +[[image:image-20250207165702-14.png||height="830" width="563"]]
541 541  
542 -* (% style="color:#4f81bd" %)**General Commands:**
488 +6.3.2 Switch to Class C using "AT+CLASS=C", and check the class with "AT+CLASS=?".
543 543  
544 -These commands are to configure:
490 +[[image:image-20250207173212-27.png]]
545 545  
546 -* General system settings like: uplink interval.
492 +[[image:image-20250207172246-20.png]]
547 547  
548 -* LoRaWAN protocol & radio-related commands.
494 +6.3.3 Verify LA66's join status (in LTS5) with "AT+NJS=?". If not joined, connect manually to LoRaWAN with "AT+JOIN".
549 549  
550 -They are the same for all Dragino Devices which supports DLWS-005 LoRaWAN Stack(Note~*~*). These commands can be found on the wiki: [[End Device Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
496 +[[image:image-20250207172010-19.png]]
551 551  
498 +[[image:image-20250207171650-17.png]]
552 552  
553 -* (% style="color:#4f81bd" %)**Commands special design for PB01**
500 +6.3.4 After joining, send a message to TTN, such as "AT+SENDB=01,02,8,05820802581ea0a5", to activate communication.
554 554  
555 -These commands are only valid for PB01, as below:
502 +[[image:image-20250207192107-28.png]]
556 556  
557 -(% style="display:none" %) (%%)
504 +6.3.5 TTN distributes panel data in three batches.
558 558  
559 -== 3.1  Downlink Command Set ==
506 +1. downlink DEUI F1A84041000181D4A8
507 +1. downlink Dev Name F24B69746368656E2D467269676531FFFF
508 +1. downlink Sensor Data 5501A4CBBB0A8E085C02 或 5504A4CB01
560 560  
510 += 5. The method for adding a new type of panel to the project =
561 561  
562 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %)
563 -|=(% style="width: 130px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 151px; background-color: rgb(79, 129, 189); color: white;" %)**Function**|=(% style="width: 92px; background-color: rgb(79, 129, 189); color: white;" %)**Response**|=(% style="width: 206px; background-color: rgb(79, 129, 189); color: white;" %)**Downlink**
564 -|(% style="width:130px" %)AT+TDC=?|(% style="width:151px" %)(((
565 -
512 +If you don't have this need, then this part of the content can be ignored.
566 566  
567 -View current TDC time
568 -)))|(% style="width:92px" %)(((
569 -1200000
570 -OK
571 -)))|(% style="width:206px" %)Default 1200000(ms)
572 -|(% style="width:130px" %)AT+TDC=300000|(% style="width:151px" %)Set TDC time|(% style="width:92px" %)OK|(% style="width:206px" %)(((
573 -(((
574 -0X0100012C:
575 -01: fixed command
576 -00012C: 0X00012C=
514 +1. Design a panel in SquareLine Studio, as shown in Image 5.1 below for reference.
577 577  
578 -300(seconds)
579 -)))
516 +[[image:image-20241121113445-1.png||height="584" width="934"]]
580 580  
581 -(((
582 -
583 -)))
584 -)))
585 -|(% style="width:130px" %)ATZ|(% style="width:151px" %)Reset node|(% style="width:92px" %) |(% style="width:206px" %)0x04FF
586 -|(% style="width:130px" %)AT+FDR|(% style="width:151px" %)Restore factory settings|(% style="width:92px" %) |(% style="width:206px" %)0X04FE
587 -|(% style="width:130px" %)AT+CFM=?|(% style="width:151px" %)View the current confirmation mode status|(% style="width:92px" %)(((
588 -0,7,0
518 + Image 5.1: a panel about water_leak
589 589  
590 -OK
591 -)))|(% style="width:206px" %)Default 0,7,0
592 -|(% style="width:130px" %)AT+CFM=1,7,1|(% style="width:151px" %)(((
593 -Confirmed uplink mode, the maximum number of retries is seven, and uplink fcnt increase by 1 for each retry
594 -)))|(% style="width:92px" %)(((
595 -OK
596 -)))|(% style="width:206px" %)(((
597 -05010701
598 598  
599 -05: fixed command
521 +2. **Export the UI file: **You need to adjust the export path first, then click '**Export -> Export UI Files**' on the menu bar. This step was introduced earlier. After that, you can get the UI files as shown in Image 5.2.
600 600  
601 -01:confirmed uplink
523 +[[image:image-20241121141120-4.png||height="383" width="795"]]
602 602  
603 -07: retry 7 times
525 + Image 5.2: Exported UI files
604 604  
605 -01: fcnt count plus 1
606 -)))
607 -|(% style="width:130px" %)AT+NJM=?|(% style="width:151px" %)(((
608 -Check the current network connection method
609 -)))|(% style="width:92px" %)(((
610 -1
611 -OK
612 -)))|(% style="width:206px" %)Default 1
613 -|(% style="width:130px" %)AT+NJM=0|(% style="width:151px" %)Change the network connection method to ABP|(% style="width:92px" %)(((
614 -Attention:Take effect after ATZ
615 -OK
616 -)))|(% style="width:206px" %)(((
617 -0X2000: ABP
618 -0x2001: OTAA
619 -20: fixed command
620 -)))
621 -|(% style="width:130px" %)AT+RPL=?|(% style="width:151px" %)View current RPL settings|(% style="width:92px" %)(((
622 -0
623 -OK
624 -)))|(% style="width:206px" %)Default 0
625 -|(% style="width:130px" %)AT+RPL=1|(% style="width:151px" %)set RPL=1    |(% style="width:92px" %)OK|(% style="width:206px" %)(((
626 -0x2101:
627 -21: fixed command
628 -01: for details, check wiki
629 -)))
630 -|(% style="width:130px" %)AT+ADR=?|(% style="width:151px" %)View current ADR status|(% style="width:92px" %)(((
631 -1
632 -OK
633 -)))|(% style="width:206px" %)Default 0
634 -|(% style="width:130px" %)AT+ADR=0|(% style="width:151px" %)Set the ADR state to off|(% style="width:92px" %)OK|(% style="width:206px" %)(((
635 -0x2200: close
636 -0x2201: open
637 -22: fixed command
638 -)))
639 -|(% style="width:130px" %)AT+DR=?|(% style="width:151px" %)View the current DR settings|(% style="width:92px" %)OK|(% style="width:206px" %)
640 -|(% style="width:130px" %)AT+DR=1|(% style="width:151px" %)(((
641 -set DR to 1
642 -It takes effect only when ADR=0
643 -)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
644 -0X22000101:
645 -00: ADR=0
646 -01: DR=1
647 -01: TXP=1
648 -22: fixed command
649 -)))
650 -|(% style="width:130px" %)AT+TXP=?|(% style="width:151px" %)View the current TXP|(% style="width:92px" %)OK|(% style="width:206px" %)
651 -|(% style="width:130px" %)AT+TXP=1|(% style="width:151px" %)(((
652 -set TXP to 1
653 -It takes effect only when ADR=0
654 -)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
655 -0X22000101:
656 -00: ADR=0
657 -01: DR=1
658 -01: TXP=1
659 -22: fixed command
660 -)))
661 -|(% style="width:130px" %)AT+RJTDC=10|(% style="width:151px" %)Set RJTDC time interval|(% style="width:92px" %)OK|(% style="width:206px" %)(((
662 -0X26000A:
663 -26: fixed command
664 -000A: 0X000A=10(min)
665 -for details, check wiki
666 -)))
667 -|(% style="width:130px" %) |(% style="width:151px" %)(((
668 -(((
669 -~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_
670 670  
671 -Retrieve stored data for a specified period of time
672 -)))
528 +3. **Delete and rename some file.** Here are the steps:
673 673  
674 -(((
675 -
676 -)))
677 -)))|(% style="width:92px" %) |(% style="width:206px" %)(((
678 -0X3161DE7C7061DE8A800A:
679 -31: fixed command
680 -61DE7C70:0X61DE7C70=2022/1/12 15:00:00
681 -61DE8A80:0X61DE8A80=2022/1/12 16:00:00
682 -0A: 0X0A=10(second)
683 -View details 2.6.2
684 -)))
685 -|(% style="width:130px" %)AT+DDETECT=?|(% style="width:151px" %)View the current DDETECT setting status and time|(% style="width:92px" %)(((
686 -1,1440,2880
687 -OK
688 -)))|(% style="width:206px" %)Default 1,1440,2880(min)
689 -|(% style="width:130px" %)AT+DDETECT=(((
690 -1,1440,2880
691 -)))|(% style="width:151px" %)(((
692 -Set DDETECT setting status and time
693 -((% style="color:red" %)When the node does not receive the downlink packet within the set time, it will re-enter the network(%%))
694 -)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
695 -0X320005A0: close
696 -0X320105A0: open
697 -32: fixed command
698 -05A0: 0X05A0=1440(min)
699 -)))
530 + Step 1: Delete the 'components' directory.
531 + Step 2: Delete 'filelist.txt'.
532 + Step 3: Delete 'ui_helpers.c' and 'ui_helpers.h'.
533 + Step 4: Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
534 + Step 5: Rename the 'screens' directory to 'styles'.
700 700  
701 -== 3.2  Set Password ==
536 +[[image:image-20241121151934-10.png||height="303" width="792"]]
702 702  
538 + image 5.3 rest file (1)
703 703  
704 -Feature: Set device password, max 9 digits.
540 +[[image:image-20241121142925-7.png||height="141" width="793"]]
705 705  
706 -(% style="color:#4f81bd" %)**AT Command: AT+PWORD**
542 + image 5.4 rest file (2)
707 707  
708 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
709 -|(% style="background-color:#4f81bd; color:white; width:155px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:128px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:89px" %)**Response**
710 -|(% style="width:155px" %)AT+PWORD=?|(% style="width:124px" %)Show password|(% style="width:86px" %)(((
711 -123456
712 -OK
713 -)))
714 -|(% style="width:155px" %)AT+PWORD=999999|(% style="width:124px" %)Set password|(% style="width:86px" %)OK
544 +4. Open the project in **VS Code**.
715 715  
716 -(% style="color:#4f81bd" %)**Downlink Command:**
546 +5. Add the file include path for **water_leak** in **extra_lib/CMakeLists.txt**, as shown in Images 5.5 and 5.6. Its format is similar to that of **tem_hum** or **door**."
717 717  
718 -No downlink command for this feature.
548 +[[image:image-20241121181957-17.png||height="438" width="516"]]
719 719  
550 + image 5.5 extra_lib/CMakeLists.txt before add
720 720  
721 -== 3.3  Set button sound and ACK sound ==
552 +[[image:image-20241121182239-18.png||height="520" width="518"]]
722 722  
554 + image 5.6 extra_lib/CMakeLists.txt after add
723 723  
724 -Feature: Turn on/off button sound and ACK alarm.
556 +6.  **Modify the header files included in the fonts and images directories**.
725 725  
726 -(% style="color:#4f81bd" %)**AT Command: AT+SOUND**
558 +Open the **fonts/ui_font_Font12.c** file, as shown in Image 5.7, and change **#include "../ui.h"** to **#include "../ui_water_leak.h"**. The modified file is shown in Image 5.8. Other font files need to be modified in the same way.
727 727  
728 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
729 -|(% style="background-color:#4f81bd; color:white; width:155px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:128px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:89px" %)**Response**
730 -|(% style="width:155px" %)(((
731 -AT+SOUND=?
732 -)))|(% style="width:124px" %)Get the current status of button sound and ACK sound|(% style="width:86px" %)(((
733 -1,1
734 -OK
735 -)))
736 -|(% style="width:155px" %)(((
737 -AT+SOUND=0,1
738 -)))|(% style="width:124px" %)Turn off the button sound and turn on ACK sound|(% style="width:86px" %)OK
560 +[[image:image-20241121171629-11.png]]
739 739  
740 -(% style="color:#4f81bd" %)**Downlink Command: 0xA1 **
562 + image 5.7 before-modified font file
741 741  
742 -Format: Command Code (0xA1) followed by 2 bytes mode value.
564 +[[image:image-20241121171901-12.png]]
743 743  
744 -The first byte after 0XA1 sets the button sound, and the second byte after 0XA1 sets the ACK sound.** (0: off, 1: on)**
566 + image 5.8 modified font file
745 745  
746 -* **Example: **Downlink Payload: A10001  ~/~/ Set AT+SOUND=0,1  Turn off the button sound and turn on ACK sound.
568 +Open the **images/ui_img_battery_empty_png.c** file, as shown in Image 5.9, and change **#include "../ui.h"** to **#include "../ui_water_leak.h"**. The modified file is shown in Image 5.10. Other image files need to be modified in the same way.
747 747  
748 -== 3.4  Set buzzer music type(0~~4) ==
570 +[[image:image-20241121172714-13.png]]
749 749  
572 + image 5.9 before-modified image file
750 750  
751 -Feature: Set different alarm key response sounds.There are five different types of button music.
574 +[[image:image-20241121172908-14.png]]
752 752  
753 -(% style="color:#4f81bd" %)**AT Command: AT+OPTION**
576 + image 5.10 modified image file
754 754  
755 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
756 -|(% style="background-color:#4f81bd; color:white; width:155px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:128px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:89px" %)**Response**
757 -|(% style="width:155px" %)(((
758 -AT+OPTION=?
759 -)))|(% style="width:124px" %)(((
760 -Get the buzzer music type
761 -)))|(% style="width:86px" %)(((
762 -3
578 +7. Modify the **ui_water_leak/CMakeLists.txt**. Open this file, and modify it as shown in image 5.11 (before) and image 5.12 (after).
763 763  
764 -OK
765 -)))
766 -|(% style="width:155px" %)AT+OPTION=1|(% style="width:124px" %)Set the buzzer music to type 1|(% style="width:86px" %)OK
580 +[[image:image-20241121180030-15.png]]
767 767  
768 -(% style="color:#4f81bd" %)**Downlink Command: 0xA3**
582 + image 5.11 ui_water_leak/CMakeLists.txt before modification
769 769  
770 -Format: Command Code (0xA3) followed by 1 byte mode value.
584 +[[image:image-20241121180517-16.png]]
771 771  
772 -* **Example: **Downlink Payload: A300  ~/~/ Set AT+OPTION=0  Set the buzzer music to type 0.
586 + image 5.12 ui_water_leak/CMakeLists.txt after modification
773 773  
774 -== 3.5  Set Valid Push Time ==
775 775  
589 +8. Modify the **ui_water_leak.h** file. Images 5.13 and 5.14 show the code before modification, while Images 5.15 and 5.16 show the code after modification.
776 776  
777 -Feature: Set the holding time for pressing the alarm button to avoid miscontact. Values range from** 0 ~~1000ms**.
591 +[[image:image-20241122094200-23.png]]
778 778  
779 -(% style="color:#4f81bd" %)**AT Command: AT+STIME**
593 + image 5.13 ui_water_leak.h (1) before modification
780 780  
781 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
782 -|(% style="background-color:#4f81bd; color:white; width:155px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:128px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:89px" %)**Response**
783 -|(% style="width:155px" %)(((
784 -AT+STIME=?
785 -)))|(% style="width:124px" %)(((
786 -Get the button sound time
787 -)))|(% style="width:86px" %)(((
788 -0
789 -OK
790 -)))
791 -|(% style="width:155px" %)(((
792 -AT+STIME=1000
793 -)))|(% style="width:124px" %)Set the button sound time to 1000**ms**|(% style="width:86px" %)OK
595 +[[image:image-20241122094320-24.png||height="852" width="554"]]
794 794  
795 -(% style="color:#4f81bd" %)**Downlink Command: 0xA2**
597 + image 5.14 ui_water_leak.h (2) before modification
796 796  
797 -Format: Command Code (0xA2) followed by 2 bytes mode value.
599 +[[image:image-20241122094600-25.png||height="1078" width="554"]]
798 798  
799 -* **Example: **Downlink Payload: A203E8  ~/~/ Set AT+STIME=1000  
601 + image 5.15 ui_water_leak.h (1) after modification
800 800  
801 -**~ Explain: **Hold the alarm button for 10 seconds before the node will send the alarm packet.
603 +[[image:image-20241122094719-26.png||height="941" width="583"]]
802 802  
605 + image 5.16 ui_water_leak.h (2) before modification
803 803  
804 -
607 +9. **Modify ui_water_leak.c file.** The image 5.17, 5.18, 5.19 show the code before modification, and the image 5.20, 5.21, 5.22 show the code after modification.
805 805  
609 +_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.
610 +
611 +[[image:image-20241122102929-27.png||height="619" width="426"]]
612 +
613 + image 5.17 ui_water_leak.c (1) before modification
614 +
615 +[[image:image-20241122112838-30.png||height="551" width="628"]]
616 +
617 + image 5.18 ui_water_leak.c (2) before modification
618 +
619 +[[image:image-20241122110815-29.png||height="725" width="712"]]
620 +
621 + image 5.19 ui_water_leak.c (3) before modification
622 +
623 +[[image:image-20241122113158-31.png||height="872" width="677"]]
624 +
625 + image 5.20 ui_water_leak.c (1) after modification
626 +
627 +[[image:image-20241122113259-33.png||height="874" width="724"]]
628 +
629 + image 5.21 ui_water_leak.c (2) after modification
630 +
631 +[[image:image-20241122113359-34.png||height="804" width="746"]]
632 +
633 + image 5.22 ui_water_leak.c (3) after modification
634 +
635 +10. **Modify ui_water_leak_events.h file.** The image 5.23 show the code before modification, and the image 5.24 show the code after modification.
636 +
637 +[[image:image-20241122134113-35.png||height="380" width="421"]]
638 +
639 + image 5.23 ui_water_leak_events_.h before modification
640 +
641 +[[image:image-20241122134420-37.png||height="201" width="283"]]
642 +
643 +image 5.24 ui_water_leak_events_.h after modification
644 +
645 +11.** Modify ui_water_leak_events.c file.** The image 5.25 show the code before modification, and the image 5.26 show the code after modification.
646 +
647 +Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
648 +
649 +Step2. add code  below in delete_object() function definition.
650 +
651 + panel_all * panel = find_upper_by_SensorPanel(&arr,((lv_obj_t *)(e->user_data~)~)~);
652 +
653 + size_t index = panel->panel_obj_index;
654 +
655 + deleteElement(&arr, index);
656 +
657 +[[image:image-20241122135023-38.png||height="358" width="372"]]
658 +
659 + image 5.25 ui_water_leak_events_.c before modification
660 +
661 +[[image:image-20241122135258-39.png||height="403" width="559"]]
662 +
663 + image 5.26 ui_water_leak_events_.c after modification
664 +
665 +
666 +12. **Modify ui_water_leak_style.c file.**
667 +
668 +Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
669 +
670 + add '#include "../../sort.h"'
671 +
672 + add '#include "ui.h"'
673 +
674 +[[image:image-20241122141536-41.png||height="361" width="612"]]
675 +
676 + image 5.27 ui_water_leak_style.c (1) before modification
677 +
678 +[[image:image-20241122142129-42.png||height="386" width="613"]]
679 +
680 + image 5.28 ui_water_leak_style.c (1) after modification
681 +
682 +
683 +Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
684 +
685 + delete code as shown in image 5.29
686 +
687 +[[image:image-20241122145620-44.png||height="757" width="671"]]
688 +
689 + image 5.29 ui_water_leak_style.c (2)
690 +
691 +
692 +Step3. The image 5.30, 5.31 show the change.
693 +
694 +[[image:image-20241122152026-45.png||height="277" width="828"]]
695 +
696 + image 5.30 ui_water_leak_style.c (3) before modification
697 +
698 +[[image:image-20241122152542-46.png||height="293" width="830"]]
699 +
700 + image 5.31 ui_water_leak_style.c (3) after modification
701 +
702 +
703 +Step4. Copy partly the code in ui_water_leak.c, paste at extra_lib/sort.h(The process is shown in image 5.32, 5.33).
704 +
705 +[[image:image-20241122153958-47.png]]
706 +
707 + image 5.32 ui_water_leak_style.c (4)
708 +
709 +
710 +[[image:image-20241122154755-49.png||height="864" width="513"]]
711 +
712 + image 5.33 ui_water_leak_style.c (4)
713 +
714 +
715 +Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
716 +
717 +[[image:image-20241122155650-50.png||height="922" width="513"]]
718 +
719 + image 5.34 ui_water_leak_style.c (5)
720 +
721 +
722 +Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
723 +
724 +[[image:image-20241122161934-51.png]]
725 +
726 + image 5.35
727 +
728 +
729 +Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
730 +
731 +[[image:image-20241122162852-53.png||height="330" width="529"]]
732 +
733 + image 5.37
734 +
735 +
736 +Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
737 +
738 +panel_with_type union_sensor;
739 +
740 +union_sensor.panel_type = WATER_LEAK_TYPE;
741 +
742 +......
743 +
744 +lv_obj_set_x(union_sensor.panel_union.door.ui_PanelSensorDoor, x_by_index(index));
745 +
746 +lv_obj_set_y(union_sensor.panel_union.door.ui_PanelSensorDoor, y_by_index(index));
747 +
748 +return union_sensor;
749 +
750 +[[image:image-20250122173546-6.png||height="777" width="922"]]
751 +
752 + image 5.38
753 +
754 +
755 +13. Rest midification in sort.h file.
756 +
757 +In image 5.39 as below, we can see "WATER_LEAK_TYPE" at line 24 and water leak switch status definition at line 32,33, and these are what we need to add in sort.h.
758 +
759 +[[image:image-20250122170230-1.png||height="580" width="513"]]
760 +
761 + image 5.39 sort.h
762 +
763 +13. **Modify sort.c file.**
764 +
765 +Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 26.
766 +
767 +[[image:image-20250122171910-5.png||height="524" width="510"]]
768 +
769 + image 5.40 sort.c (1)
770 +
771 +There are still some changes need to be done in sort.c, and omit here for the moment.
772 +
773 +
774 +
806 806  = 6. FAQ =
807 807  
808 -== 6.1 ==
777 +== 6.1 ==
809 809  
810 810  
811 811  = 7. Order Info =
... ... @@ -812,12 +812,13 @@
812 812  
813 813  == 7.1  Part Number ==
814 814  
784 +
815 815  Part Number: (% style="color:#4472c4" %)LTS5
816 816  
817 -
818 818  
819 819  == 7.2  Packing Info ==
820 820  
790 +
821 821  **Package Includes**:
822 822  
823 823  * LTS5 HMI Touch Screen
... ... @@ -824,20 +824,19 @@
824 824  * 5V,2A DC Power Adapter.
825 825  * USB Type C Program Cable
826 826  
827 -
828 828  = 8. Support =
829 829  
799 +
830 830  * 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.
831 831  * 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]].
832 832  
833 -
834 834  = 9.  Reference material =
835 835  
805 +
836 836  * Datasheet
837 -* Source Code
807 +* 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]]
838 838  * Mechinical
839 839  
840 -
841 841  = 10. FCC Warning =
842 842  
843 843  
1727229396732-319.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +197.2 KB
Content
1727229550717-684.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +113.9 KB
Content
1727229582471-566.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +73.6 KB
Content
1727229618724-758.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +118.7 KB
Content
1727229653254-680.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +116.2 KB
Content
1727229682537-381.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +51.5 KB
Content
1727229715361-392.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +75.2 KB
Content
1727229740592-843.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +87.3 KB
Content
1727229760857-521.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +24.7 KB
Content
1727229798126-306.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +53.6 KB
Content
1727229821582-258.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +76.1 KB
Content
1727229845835-509.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +68.3 KB
Content
1727229892636-154.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +192.0 KB
Content
1727229926561-300.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +178.0 KB
Content
1727229955611-607.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +100.4 KB
Content
1727229990795-405.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +383.6 KB
Content
1727230012478-930.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +477.1 KB
Content
1727231038705-173.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +94.6 KB
Content
1727233636007-933.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +114.8 KB
Content
1727484665746-713.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +94.9 KB
Content
1727485118799-984.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +11.8 KB
Content
1727485251053-655.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +20.4 KB
Content
1727485480434-713.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +24.7 KB
Content
1727485933579-550.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +55.6 KB
Content
1727485953726-175.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +91.6 KB
Content
1727486567182-334.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +42.6 KB
Content
1727486578489-774.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +66.0 KB
Content
1727487368023-281.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +28.5 KB
Content
1727488067077-684.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +604.7 KB
Content
1727488099947-341.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +877.7 KB
Content
1727488108117-780.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +877.7 KB
Content
1727488157579-949.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +877.7 KB
Content
1738893226894-758.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +25.6 KB
Content
Screenshot 2024-12-24 134818.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +15.0 KB
Content
Screenshot 2024-12-24 134937.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +3.6 KB
Content
Screenshot 2024-12-24 140459.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +12.0 KB
Content
Screenshot 2024-12-24 144005.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +28.0 KB
Content
image-20240916101737-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +156.7 KB
Content
image-20240925110638-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +262.7 KB
Content
image-20240928090825-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +30.2 KB
Content
image-20240928103357-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +153.7 KB
Content
image-20240928103506-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +197.7 KB
Content
image-20240928105309-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +80.2 KB
Content
image-20240928110211-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +228.0 KB
Content
image-20240928111412-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +150.9 KB
Content
image-20240928111654-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +105.4 KB
Content
image-20240928112001-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +75.6 KB
Content
image-20240928113424-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +50.8 KB
Content
image-20240928114139-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +114.3 KB
Content
image-20240928144830-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +25.5 KB
Content
image-20241121113445-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +250.0 KB
Content
image-20241121120222-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +44.8 KB
Content
image-20241121120830-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +42.6 KB
Content
image-20241121141120-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +41.7 KB
Content
image-20241121141315-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +29.4 KB
Content
image-20241121141329-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +29.4 KB
Content
image-20241121142925-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +14.8 KB
Content
image-20241121145915-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +61.0 KB
Content
image-20241121150911-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +73.0 KB
Content
image-20241121151934-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +32.9 KB
Content
image-20241121171629-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +16.9 KB
Content
image-20241121171901-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +17.2 KB
Content
image-20241121172714-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +26.4 KB
Content
image-20241121172908-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +27.1 KB
Content
image-20241121180030-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +27.7 KB
Content
image-20241121180517-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +26.5 KB
Content
image-20241121181957-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +59.3 KB
Content
image-20241121182239-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +71.3 KB
Content
image-20241122092239-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +270.9 KB
Content
image-20241122092655-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +251.6 KB
Content
image-20241122093445-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +128.9 KB
Content
image-20241122093601-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +120.0 KB
Content
image-20241122094200-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +289.2 KB
Content
image-20241122094320-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +182.4 KB
Content
image-20241122094600-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +136.0 KB
Content
image-20241122094719-26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +129.5 KB
Content
image-20241122102929-27.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +219.9 KB
Content
image-20241122104344-28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +257.1 KB
Content
image-20241122110815-29.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +246.1 KB
Content
image-20241122112838-30.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +263.9 KB
Content
image-20241122113158-31.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +133.7 KB
Content
image-20241122113252-32.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +152.3 KB
Content
image-20241122113259-33.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +152.3 KB
Content
image-20241122113359-34.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +126.5 KB
Content
image-20241122134113-35.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +69.3 KB
Content
image-20241122134412-36.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +14.9 KB
Content
image-20241122134420-37.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +14.9 KB
Content
image-20241122135023-38.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +28.7 KB
Content
image-20241122135258-39.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +40.3 KB
Content
image-20241122141526-40.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +78.8 KB
Content
image-20241122141536-41.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +78.8 KB
Content
image-20241122142129-42.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +85.1 KB
Content
image-20241122143105-43.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +60.2 KB
Content
image-20241122145620-44.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +394.0 KB
Content
image-20241122152026-45.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +201.6 KB
Content
image-20241122152542-46.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +95.3 KB
Content
image-20241122153958-47.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +241.1 KB
Content
image-20241122154745-48.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +135.7 KB
Content
image-20241122154755-49.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +135.7 KB
Content
image-20241122155650-50.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +104.4 KB
Content
image-20241122161934-51.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +230.3 KB
Content
image-20241122162612-52.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +58.7 KB
Content
image-20241122162852-53.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +125.5 KB
Content
image-20241122171211-54.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +173.3 KB
Content
image-20241122173706-55.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +37.6 KB
Content
image-20241122173718-56.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +37.6 KB
Content
image-20241226135550-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +293.3 KB
Content
image-20250122170230-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +77.3 KB
Content
image-20250122171809-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +51.1 KB
Content
image-20250122171825-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +51.1 KB
Content
image-20250122171832-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +51.1 KB
Content
image-20250122171910-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +51.1 KB
Content
image-20250122173546-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +200.4 KB
Content
image-20250207100150-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +54.1 KB
Content
image-20250207101415-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +17.6 KB
Content
image-20250207101515-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +24.1 KB
Content
image-20250207142334-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +62.0 KB
Content
image-20250207143131-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +48.7 KB
Content
image-20250207144605-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +58.1 KB
Content
image-20250207164320-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +194.5 KB
Content
image-20250207165702-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +78.1 KB
Content
image-20250207170215-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.6 KB
Content
image-20250207170307-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.2 KB
Content
image-20250207171650-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +11.0 KB
Content
image-20250207171851-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.5 KB
Content
image-20250207172010-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.5 KB
Content
image-20250207172246-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.5 KB
Content
image-20250207172443-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207172821-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +0 bytes
Content
image-20250207172834-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +0 bytes
Content
image-20250207173152-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207173159-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207173206-26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207173212-27.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207192107-28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +14.3 KB
Content
squalreline-trial.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +60.4 KB
Content
squareline-studio-launcher-screen.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +203.4 KB
Content
squareline.io_downloads.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +1.5 MB
Content