Skip to Content
Last modified by BoYang Xie on 2025/07/24 16:47
From version 180.1
edited by Dilisi S
on 2025/02/18 01:33
Change comment: Feb 17 edits - typo
To version 4.12
edited by Edwin Chen
on 2024/09/16 09:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.pradeeka
1 +XWiki.Edwin
Content
... ... @@ -1,13 +1,9 @@
1 -
1 +
2 +[[image:image-20240915231842-1.png]]
2 2  
3 -(% style="text-align:center" %)
4 -[[image:image-20241226135550-1.png]]
5 5  
6 -
7 -
8 -
9 9  (% _mstvisible="1" %)
10 -(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:**
6 +(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents：**
11 11  
12 12  {{toc/}}
13 13  
... ... @@ -20,22 +20,20 @@
20 20  
21 21  = 1.  Introduction =
22 22  
23 -== 1.1  What is the LTS5 LoRa HMI Touch Screen? ==
19 +== 1.1  What is LTS5 LoRa HMI touch screen ==
24 24  
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.
25 25  
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.
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.
27 27  
28 -The LTS5 is an open-source software project powered by an **ESP32 MCU** and a **Dragino LA66 LoRa** module. The extensive development resources available for ESP32 can significantly reduce development time.
25 +The HMI touch screen of LTS5 supports drap & drop design. Developer can use SquareLine to easily customize the display UI for different application.
29 29  
30 -The LTS5's HMI touch screen supports **drag-and-drop** design, allowing developers to use SquareLine to easily customize the display UI for various applications.
27 +LTS5 use LA66 LoRa module, this module can be program to support private LoRa protocol or LoRaWAN protocol.
31 31  
32 -The LA66 LoRa module can be programmed to support either private LoRa protocols or the LoRaWAN protocol.
33 33  
34 34  == 1.2  Features ==
35 35  
36 -
37 -* ESP32-WROOM MCU: 8MB RAM & 16MB ROM
38 -* Dragino LA66 LoRa Module
32 +* ESP32-WROOM MCU + Dragino LA66 LoRa Module
39 39  * Support Private LoRa protocol or LoRaWAN protocol
40 40  * Support WiFi & BLE wireless protocol
41 41  * 5.0" HMI touch screen
... ... @@ -46,17 +46,11 @@
46 46  * 5V DC power
47 47  * IP Rating: IP52
48 48  
49 -== 1.3  Specifications ==
50 50  
44 +== 1.3  Specification ==
51 51  
52 52  **LoRa**:
53 53  
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
60 60  
61 61  **WiFi:**
62 62  
... ... @@ -80,20 +80,21 @@
80 80  * RGB color.
81 81  * Display Area: 120.7*75.80 mm
82 82  
71 +
72 +
83 83  == 1.4  Power Consumption ==
84 84  
85 -
86 86  * External 5V DC power adapter
87 87  
77 +
88 88  == 1.5  Storage & Operation Temperature ==
89 89  
90 -
91 91  * Operation Temperature: -20 ~~ 70°C  (No Dew)
92 92  * Storage Temperature: -30 ~~ 70°C  (No Dew)
93 93  
83 +
94 94  == 1.6  Applications ==
95 95  
96 -
97 97  * Smart Buildings & Home Automation
98 98  * Logistics and Supply Chain Management
99 99  * Smart Metering
... ... @@ -101,719 +101,734 @@
101 101  * Smart Cities
102 102  * Smart Factory
103 103  
104 -= 2.  Getting Started with 'Hello World' =
105 105  
106 -== 2.1  About this demo ==
94 += 2.  Operation Mode =
107 107  
96 +== 2.1  How it work? ==
108 108  
109 -This getting started example demonstrates how to design and deploy a simple display UI for the LTS5 device. The example includes:
110 110  
111 -* Creating a basic UI with a single button.
112 -* Implementing functionality to navigate the Web UI to a new page when the button is clicked.
113 -* Uploading the UI to the LTS5 device.
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**.
114 114  
115 -By completing this demo, you will gain foundational knowledge for customizing the LTS5 interface and building more advanced IoT applications.
116 116  
102 +== 2.2  How to Activate PB01? ==
117 117  
118 -== 2.2  Install Software Running Environment ==
119 119  
105 +(% style="color:red" %)** 1.  Open enclosure from below position.**
120 120  
121 -The **ESP MCU** supports development with **ESP-IDF**, **Arduino**, or **MicroPython**. We use **ESP-IDF** for compilation and **Visual Studio Code (VS Code)** as the development environment for this project.
107 +[[image:image-20220621093835-1.png]]
122 122  
123 123  
124 -=== 2.2.1 Install VS Code and ESP-IDF extension ===
110 +(% style="color:red" %)** 2.  Insert 2 x AAA LR03 batteries and the node is activated.**
125 125  
112 +[[image:image-20220621093835-2.png]]
126 126  
127 -First, download and install **VS Code** for your operating system from the Visual Studio Code website: [[Visual Studio Code - Mac, Linux, Windows>>https://code.visualstudio.com/download]].
128 128  
129 -Next, install the **ESP-IDF** extension within **VS Code**. Detailed steps for this process are shown in Image 1.
115 +(% style="color:red" %)** 3. Under the above conditions, users can also reactivate the node by long pressing the ACT button.**
130 130  
117 +[[image:image-20220621093835-3.png]]
131 131  
132 -[[image:image-20240928110211-5.png||height="508" width="866"]]
133 133  
134 - Image 1: ESP-IDF extension install
120 +User can check [[LED Status>>||anchor="H2.8LEDIndicator"]] to know the working state of PB01.
135 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 137  
123 +== 2.3  Example to join LoRaWAN network ==
138 138  
139 -=== 2.2.2 Install SquareLine Studio ===
140 140  
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.
141 141  
142 -Download and install the latest version of [[SquareLine Studio>>https://squareline.io/downloads#lastRelease]] on your computer. It supports Windows, Linux, and Mac OS. The software version we are using here is 1.5.0. See the image below.
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. 
143 143  
144 -[[image:squareline.io_downloads.png||height="888" width="1294"]]
131 +[[image:image-20240705094824-4.png]]
145 145  
133 +(% style="color:blue" %)**Step 1**(%%):  Create a device in TTN V3 with the OTAA keys from PB01.
146 146  
147 -After installation, you can use SquareLine Studio with a **PERSONAL license plan**. Click **LOG IN** and create a free account using your email address. Then activate your PERSONAL license plan for free. You don’t need to provide any credit card information. However, the PERSONAL license plan has the following limitations:
135 +Each PB01 is shipped with a sticker with the default DEV EUI as below:
148 148  
149 -* Max. 10 screens
150 -* Max. 150 widgets
151 -* Max. 5 global colors
152 -* Max. 2 themes
153 -* Max. 1 component
137 +[[image:image-20230426083617-1.png||height="294" width="633"]]
154 154  
155 -== 2.3 Simple usage of SquareLine Studio and exporting UI code ==
156 156  
140 +Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
157 157  
158 -Start the SquareLine Studio. The **launcher screen** appears as shown in the below image. You can create a new project by clicking **Create** in the top menu. Then select the **Desktop** tab. Select the development platform, **Eclipse with  SDL for development on PC**.
142 +Create application.
159 159  
160 -* In the **PROJECT SETTINGS**, select **LVGL version **as **8.3.11** and **Resolution** as **800** x **480**.
161 -* Select the **CREATE **button to create the new project with the selected settings.
144 +choose to create the device manually.
162 162  
163 -[[image:squareline-studio-launcher-screen.png||height="752" width="1415"]]
146 +Add JoinEUI(AppEUI), DevEUI, AppKey.(% style="display:none" %)
164 164  
148 +[[image:image-20240507142116-1.png||height="410" width="1138"]](% style="display:none" %) (%%)
149 +
165 165  
166 -Next, you need to configure some additional settings for this project. To do so, select** File  -> Project Settings** as shown in the image below.
151 +[[image:image-20240507142157-2.png||height="559" width="1147"]]
167 167  
168 -[[image:1727229582471-566.png]]
153 +[[image:image-20240507142401-3.png||height="693" width="1202"]]
169 169  
155 +[[image:image-20240507142651-4.png||height="760" width="1190"]]
170 170  
171 -In the **PROJECT SETTINGS** dialog box, configure/modify the project settings as shown in the image below.
157 +**Default mode OTAA**(% style="display:none" %)
172 172  
173 -* **UI Files Export Path**: Select a **folder** on your computer to store the **UI files**.
174 -* **LVGL Include Path**: Set this to **lvgl.h**
175 -* Click on the **APPLY CHANGES** button.
176 176  
177 -[[image:image-20240928105309-4.png||height="526" width="556"]]
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.
178 178  
162 +[[image:image-20240507143104-5.png||height="434" width="1398"]]
179 179  
180 -Now you can start building the user interface. Follow the steps below:
181 181  
165 +== 2.4  Uplink Payload ==
182 182  
183 -=== **Add widgets** ===
184 184  
168 +Uplink payloads include two types: Valid Sensor Value and other status / control command.
185 185  
186 -After creating a project, a **Screen** will be automatically added. Its name is **Screen1** by default.
170 +* Valid Sensor Value: Use FPORT=2
171 +* Other control command: Use FPORT other than 2.
187 187  
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.
173 +=== 2.4.1  Uplink FPORT~=5, Device Status ===
189 189  
190 -[[image:image-20240928111412-6.png||height="526" width="864"]]
191 191  
176 +Users can  get the Device Status uplink through the downlink command:
192 192  
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**.
178 +(% style="color:#4472c4" %)**Downlink:  **(%%)**0x2601**
194 194  
195 -[[image:Screenshot 2024-12-24 140459.png||height="278" width="290"]]
180 +Uplink the device configures with FPORT=5.
196 196  
197 -=== **Modify widget properties** ===
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
198 198  
186 +[[image:image-20240507152130-12.png||height="469" width="1366"]](% style="display:none" %)
199 199  
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.
188 +Example Payload (FPort=5):  [[image:image-20240507152254-13.png||height="26" width="130"]]
201 201  
202 -[[image:1727485118799-984.png]]
203 203  
191 +(% style="color:#4472c4" %)**Sensor Model**(%%): For PB01, this value is 0x35.
204 204  
205 -==== **Changing the Button properties** ====
193 +(% style="color:#4472c4" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version.
206 206  
195 +(% style="color:#4472c4" %)**Frequency Band**:
207 207  
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:
197 +*0x01: EU868
209 209  
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
199 +*0x02: US915
217 217  
218 -[[image:1727485251053-655.png]]
201 +*0x03: IN865
219 219  
203 +*0x04: AU915
220 220  
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.
205 +*0x05: KZ865
222 222  
223 -* Click **ADD EVENT** button. A new section will appear to configure this event.
207 +*0x06: RU864
224 224  
225 -[[image:Screenshot 2024-12-24 134937.png||height="80" width="290"]]
209 +*0x07: AS923
226 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.
211 +*0x08: AS923-1
228 228  
229 -[[image:Screenshot 2024-12-24 134818.png||height="222" width="290"]]
213 +*0x09: AS923-2
230 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.
215 +*0x0a: AS923-3
233 233  
234 -[[image:1727485480434-713.png||height="395" width="290"]]
235 235  
236 - Image 8: Add an event for the button
218 +(% style="color:#4472c4" %)**Sub-Band**(%%): value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
237 237  
220 +(% style="color:#4472c4" %)**BAT**(%%): shows the battery voltage for PB01.
238 238  
239 -==== **Changing the label properties** ====
222 +(% style="color:#4472c4" %)**Ex1**(%%): 0x0C DE = 3294mV
240 240  
241 241  
242 -Click the Label you have added to the screen. Under the **Label** section, type "**Click for Detail**" in the **Text** textbox.
225 +=== 2.4.2  Uplink FPORT~=2, Real time sensor value ===
243 243  
244 -[[image:image-20240928090825-1.png||height="327" width="391"]]
245 245  
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"]].
246 246  
247 -Once you enter the text, it will immediately appear on the label.
230 +Uplink uses FPORT=2 and every 20 minutes send one uplink by default.
248 248  
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
249 249  
250 -==== **Changing image properties** ====
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 +)))
251 251  
262 +Example in TTN.
252 252  
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.
264 +[[image:image-20240507150155-11.png||height="549" width="1261"]]
254 254  
255 -One way is to move your image into the folder "…/squareline project/assets/", as shown in the image below.
266 +Example Payload (FPort=2):  (% style="background-color:yellow" %)**0C EA 03 01 01 11 02 A8**
256 256  
257 -[[image:image-20240928113424-9.png||height="355" width="505"]]
268 +==== (% style="color:blue" %)**Battery:**(%%) ====
258 258  
270 +Check the battery voltage.
259 259  
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.
272 +* Ex1: 0x0CEA = 3306mV
273 +* Ex2: 0x0D08 = 3336mV
261 261  
262 -[[image:image-20240928114139-10.png||height="559" width="810"]]
275 +==== (% style="color:blue" %)**Sound_ACK & Sound_key:**(%%) ====
263 263  
277 +Key sound and ACK sound are enabled by default.
264 264  
265 -==== **The relationship between widgets** ====
279 +* Example1: 0x03
266 266  
281 + Sound_ACK: (03>>1) & 0x01=1, OPEN.
267 267  
268 -Widgets commonly have two types of relationships: **parallel** and **parent-child**.
283 +**~ ** Sound_key:  03 & 0x01=1, OPEN.
269 269  
270 -* In a **parallel relationship**, widgets' positions are determined relative to a shared reference object.
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.
285 +* Example2: 0x01
272 272  
273 -[[image:1727486567182-334.png||height="318" width="278"]]
287 + Sound_ACK: (01>>1) & 0x01=0, CLOSE.
274 274  
289 +**~ ** Sound_key:  01 & 0x01=1, OPEN.
275 275  
276 -Move the label, **Label1** to make it a child of **Button1** as shown in the image below.
277 277  
278 -[[image:image-20240928112001-8.png||height="431" width="796"]]
292 +==== (% style="color:blue" %)**Alarm:**(%%) ====
279 279  
294 +Key alarm.
280 280  
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.
296 +* Ex1: 0x01 & 0x01=1, TRUE.
297 +* Ex2: 0x00 & 0x01=0, FALSE.
282 282  
283 -[[image:Screenshot 2024-12-24 144005.png||height="360" width="290"]]
299 +==== (% style="color:blue" %)**Temperature:**(%%) ====
284 284  
301 +* Example1:  0x0111/10=27.3℃
302 +* Example2:  (0xFF0D-65536)/10=-24.3℃
285 285  
286 -==== **Preview the screen** ====
304 +If payload is: FF0D :  (FF0D & 8000 == 1) , temp = (FF0D - 65536)/100 =-24.3℃
287 287  
306 +（FF0D & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative）
288 288  
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.
290 290  
291 -[[image:1727487368023-281.png]]
309 +==== (% style="color:blue" %)**Humidity:**(%%) ====
292 292  
311 +* Humidity:    0x02A8/10=68.0%
293 293  
294 -For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
313 +=== 2.4.3  Uplink FPORT~=3, Datalog sensor value ===
295 295  
296 296  
297 -== 2.4 Integrate UI Code to ESP-IDF Project ==
316 +PB01 stores sensor value and user can retrieve these history value via downlink command. The Datalog sensor value are sent via FPORT=3.
298 298  
318 +[[image:image-20240510144912-1.png||height="471" width="1178"]](% style="display:none" %)
299 299  
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.
301 301  
302 -On the  menubar, click **Export -> Export UI** Files as shown in the image below.
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" %)
303 303  
304 -[[image:1727229798126-306.png]]
323 +For example, in US915 band, the max payload for different DR is:
305 305  
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.
306 306  
307 -The exported UI files can be found in your SquareLine project folder as shown in the image below.
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.**
308 308  
332 +See more info about the [[Datalog feature>>||anchor="H2.6A0DatalogFeature"]].
309 309  
310 -[[image:1727229821582-258.png||height="333" width="662"]]
334 +(% style="display:none" %) (%%)
311 311  
336 +=== 2.4.4  Decoder in TTN V3 ===
312 312  
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.
314 314  
315 -[[image:image-20240928144830-11.png]]
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.
316 316  
341 +In TTN , add formatter as below:
317 317  
318 -Open the **CMakeLists.txt** file and edit it as ahown below.
343 +[[image:image-20240507162814-16.png||height="778" width="1135"]]
319 319  
320 -[[image:1727229892636-154.png||height="521" width="407"]]
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 +)))
321 321  
349 +(((
350 +
351 +)))
322 322  
323 -Open the main.c file and  add two lines of code as shown in the below images.
353 +== 2.5 Show data on Datacake ==
324 324  
325 -Add **#include "ui.h"**
326 326  
327 -[[image:1727229926561-300.png]]
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 +)))
328 328  
360 +(((
361 +
362 +)))
329 329  
330 -Add **ui_init();**
364 +(((
365 +(% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the LoRaWAN network.
366 +)))
331 331  
332 -[[image:1727229955611-607.png]]
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 +)))
333 333  
372 +(((
373 +~1. Add Datacake:
374 +)))
334 334  
335 -== 2.5 Brief introduction to the Hello World project ==
376 +(((
377 +2. Select default key as Access Key:
378 +)))
336 336  
380 +(((
381 +3. In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add PB01:
382 +)))
337 337  
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.
384 +(((
385 + Please refer to the figure below.
386 +)))
339 339  
388 +[[image:image-20240510150924-2.png||height="612" width="1186"]]
340 340  
341 -== 2.6 Test Result ==
342 342  
391 +Log in to DATACAKE, copy the API under the account.
343 343  
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.
393 +[[image:image-20240510151944-3.png||height="581" width="1191"]]
345 345  
346 -Screen 1:
347 347  
348 -[[image:1727488067077-684.png||height="402" width="574"]]
349 349  
397 +[[image:image-20240510152150-4.png||height="697" width="1188"]]
350 350  
351 -Screen 2:
352 352  
353 -[[image:1727488157579-949.png||height="397" width="572"]]
400 +[[image:image-20240510152300-5.png||height="298" width="1191"]]
354 354  
355 355  
356 -= 3. Example Project 1: LoRa Central Display =
403 +[[image:image-20240510152355-6.png||height="782" width="1193"]]
357 357  
358 -[[image:image-20240916101737-1.png||height="468" width="683"]]
405 +[[image:image-20240510152542-8.png||height="545" width="739"]]
359 359  
407 +[[image:image-20240510152634-9.png||height="748" width="740"]]
360 360  
361 -= 4. Example Project 2: LoRaWAN RS485 Alarm =
362 362  
363 -= 5. Example Project 3: P2P =
410 +[[image:image-20240510152809-10.png||height="607" width="732"]]
364 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.
412 +[[image:image-20240510153934-14.png||height="460" width="1199"]]
366 366  
367 -The project can be found at [[this link>>url:https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/P2P]].
368 368  
369 -== 5.1 firmware flashing approach. ==
415 +[[image:image-20240510153435-12.png||height="428" width="1197"]]
370 370  
371 -5.1.1 Download this project
372 372  
373 -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]].
418 +Copy and paste the [[TTN decoder>>https://github.com/dragino/dragino-end-node-decoder]] here and save.
374 374  
375 -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]].
420 +[[image:image-20240510153624-13.png||height="468" width="1195"]]
376 376  
377 -5.1.4 Upload firmware to esp32
378 378  
379 -Open flash_download_tool.exe, and then follow the steps below.
423 +Visual widgets please read the DATACAKE documentation.
380 380  
381 -[[image:1738893226894-758.png||height="170" width="176"]]
425 +(% style="display:none" %) (%%)
382 382  
383 -[[image:image-20250207100150-7.png||height="476" width="538"]]
427 +== 2.6  Datalog Feature ==
384 384  
385 -5.1.5 Upload firmware to la66
386 386  
387 -Open Dragino_Sensor_Manager_Utility.exe, and then follow the steps below.
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.
388 388  
389 -[[image:image-20250207101415-8.png||height="522" width="618"]]
390 390  
391 -[[image:image-20250207101515-9.png||height="522" width="618"]]
434 +=== 2.6.1  Unix TimeStamp ===
392 392  
393 -== 5.2 AT command and LTS5 panel data format ==
394 394  
395 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**01**A4CBBB0A8E085C02,0,3
437 +Unix TimeStamp shows the sampling time of uplink payload. format base on
396 396  
397 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**02**A4CB00,0,3
439 +[[image:image-20220523001219-11.png||_mstalt="450450" _mstvisible="3" height="97" width="627"]]
398 398  
399 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**03**A4CB00,0,3
441 +User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/||_mstvisible="3"]] :
400 400  
401 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**04**A4CB00,0,3
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)
402 402  
403 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**05**A4CB00,0,3
404 404  
405 -AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**06**A4CB00,0,3
446 +[[image:1655782409139-256.png]]
406 406  
407 -**LTS5 panel data format**:
408 408  
409 -~1. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF  A84041000181D4A8  01  A4CB  BB0A  8E08  5C02**,0,3
449 +=== 2.6.2  Poll sensor value ===
410 410  
411 -**01:** encrypt. 1 Byte. 01 ~-~-> no encryption. This 1-byte information is now invalid; simply write 0x01 instead.
412 412  
413 -**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.
452 +(((
453 +User can poll sensor value based on timestamps from the server. Below is the downlink command.
454 +)))
414 414  
415 -**A84041000181D4A8:** Device EUI. 8 Bytes. The last three Bytes will be extracted by the ESP32-S3 and displayed on the screen.
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 +)))
416 416  
417 -**01: **Panel Type. 1 Byte. 0x01~-~->Tem & Hum,
460 +(((
461 +For example, downlink command [[image:image-20220621113526-13.png]] (% _mstvisible="3" style="display:none" %)
462 +)))
418 418  
419 - 0x02~-~->Door,
464 +(((
465 +Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00's data
466 +)))
420 420  
421 - 0x03~-~->Water Leak,
468 +(((
469 +Uplink Internal =5s，means PB01 will send one packet every 5s. range 5~~255s.
470 +)))
422 422  
423 - 0x04~-~->Occupied,
424 424  
425 - 0x05~-~->Button,
473 +=== 2.6.3  Datalog Uplink payload ===
426 426  
427 - 0x06~-~->Alarm,
428 428  
429 -**A4CB: **Battery level//. //2 Bytes. Battery Voltage =0xCBA4&0x3FFF=0x0BA4=2980mV
476 +See [[Uplink FPORT=3, Datalog sensor value>>||anchor="H2.4.3A0UplinkFPORT3D32CDatalogsensorvalue"]]
430 430  
431 -**BB0A: **The temperature of the built-in sensor in LHT65N.// //2 Bytes. Temperature:  0x0ABB/100=27.47℃
478 +(% style="display:none" %) (%%) (% style="display:none" %)
432 432  
433 -**8E08: **The temperature of the External temperature sensor.// //2 Bytes. Temperature:  0x088E/100=21.90℃
480 +== 2.7 Button ==
434 434  
435 -**5C02：**The humidity of the built-in sensor in LHT65N. 2 Bytes. Humidity: 0x025C/10=60.4%
436 436  
437 -2. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF**  **A84041000181D4A8**  **02  A4CB  00**,0,3
483 +* ACT button
438 438  
439 -Specific sections of the data share the same function.
485 +Long press this button PB01 will reset and join network again.
440 440  
441 -**00: Status. **1 Byte//. //If Panel Type is 0x02, **Status: 00~-~->Open; 01~-~->Close.**
487 +[[image:image-20240510161626-17.png||height="192" width="224"]]
442 442  
443 - If Panel Type is 0x03, **Status: 00~-~->Normal; 01~-~->Water Leaking.**
489 +* Alarm button
444 444  
445 - If Panel Type is 0x04, **Status: 00~-~->Free; 01~-~->Occupied.**
491 +Press the button PB01 will immediately uplink data, and alarm is "TRUE".
446 446  
447 - If Panel Type is 0x05, **Status: 00~-~->OFF; 01~-~->ON.**
493 +[[image:image-20240705095149-5.png||height="164" width="162"]](% style="display:none" %)
448 448  
449 - If Panel Type is 0x06, **Status: 00~-~->OFF; 01~-~->Alarm.**
450 450  
451 -== 5.3 Usage ==
496 +== 2.8 LED Indicator ==
452 452  
453 -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.
454 454  
455 -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.
499 +(((
500 +The PB01 has a triple color LED which for easy showing different stage.
501 +)))
456 456  
457 -[[image:image-20250207143131-11.png||height="527" width="547"]]
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
458 458  
459 -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.
505 +(((
506 +(% style="color:#037691" %)**In a normal working state**:
507 +)))
460 460  
461 -[[image:image-20250207144605-12.png||height="634" width="548"]]
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.
462 462  
463 -LTS5 receives this message and displays it on its screen as the image below shows.
516 +(((
517 +
518 +)))
464 464  
465 -[[image:image-20250208181700-8.jpeg||height="528" width="704"]]
520 +== 2.9 Buzzer ==
466 466  
467 -= 6. Example Project 4: LoRaWAN_CLASS_C =
468 468  
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"]].
469 469  
470 -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.
525 +* (% style="color:#4f81bd" %)**Button sound**(%%)** **is the music produced by the node after the alarm button is pressed.
471 471  
472 -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.
527 + Users can use[[ AT+OPTION>>||anchor="H3.4A0Setbuzzermusic2807E429"]] to set different button sounds.
473 473  
474 -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).
529 +* (% style="color:#4f81bd" %)**ACK sound **(%%)is the notification tone that the node receives ACK.
475 475  
476 -The project can be found at [[this link>>https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/LoRaWAN_CLASS_C]].
531 += 3.  Configure PB01 via AT command or LoRaWAN downlink =
477 477  
478 -== 6.1 firmware flashing approach ==
479 479  
480 -The firmware flashing approach is the same as described in section 5.1.
534 +Users can configure PB01 via AT Command or LoRaWAN Downlink.
481 481  
482 -== 6.2 flowchart ==
536 +* AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
483 483  
484 -[[image:image-20250207164320-13.png||height="696" width="1344"]]
538 +* LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
485 485  
486 -== 6.3 Usage ==
540 +There are two kinds of commands to configure PB01, they are:
487 487  
488 -This section now describes a process involving TTN downlink panel data that is to be displayed on the LTS5 screen.
542 +* (% style="color:#4f81bd" %)**General Commands:**
489 489  
490 -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.
544 +These commands are to configure:
491 491  
492 -[[image:image-20250207165702-14.png||height="830" width="563"]]
546 +* General system settings like: uplink interval.
493 493  
494 -6.3.2 Switch to Class C using "AT+CLASS=C", and check the class with "AT+CLASS=?".
548 +* LoRaWAN protocol & radio-related commands.
495 495  
496 -[[image:image-20250207173212-27.png]]
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]]
497 497  
498 -[[image:image-20250207172246-20.png]]
499 499  
500 -6.3.3 Verify LA66's join status (in LTS5) with "AT+NJS=?". If not joined, connect manually to LoRaWAN with "AT+JOIN".
553 +* (% style="color:#4f81bd" %)**Commands special design for PB01**
501 501  
502 -[[image:image-20250207172010-19.png]]
555 +These commands are only valid for PB01, as below:
503 503  
504 -[[image:image-20250207171650-17.png]]
557 +(% style="display:none" %) (%%)
505 505  
506 -6.3.4 After joining, send a message to TTN, such as "AT+SENDB=01,02,8,05820802581ea0a5", to activate communication.
559 +== 3.1  Downlink Command Set ==
507 507  
508 -[[image:image-20250207192107-28.png]]
509 509  
510 -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.
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 +
511 511  
512 -There is an example for TTN downlink.
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=
513 513  
514 -1. downlink DEUI F1A84041000181D4A8
515 -1. downlink Dev Name F24B69746368656E2D467269676531FFFF
516 -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.
578 +300(seconds)
579 +)))
517 517  
518 -[[image:image-20250208175819-1.png||height="503" width="502"]]
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
519 519  
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
520 520  
521 -[[image:image-20250208175918-2.png||height="505" width="502"]]
599 +05: fixed command
522 522  
601 +01:confirmed uplink
523 523  
524 -[[image:image-20250208180010-3.png||height="507" width="503"]]
603 +07: retry 7 times
525 525  
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 +~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_
526 526  
527 -[[image:image-20250208181019-4.jpeg||height="592" width="790"]]
671 +Retrieve stored data for a specified period of time
672 +)))
528 528  
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 +)))
529 529  
530 -[[image:image-20250208181328-7.png||height="505" width="504"]]
701 +== 3.2  Set Password ==
531 531  
532 532  
533 -[[image:image-20250208181139-5.jpeg||height="594" width="792"]]
704 +Feature: Set device password, max 9 digits.
534 534  
706 +(% style="color:#4f81bd" %)**AT Command: AT+PWORD**
535 535  
536 -= 7. The method for adding a new type of panel to the project =
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
537 537  
538 -If you don't have this need, then this part of the content can be ignored.
716 +(% style="color:#4f81bd" %)**Downlink Command:**
539 539  
540 -1. Design a panel in SquareLine Studio, as shown in Image 7.1 below for reference.
718 +No downlink command for this feature.
541 541  
542 -[[image:image-20241121113445-1.png||height="584" width="934"]]
543 543  
544 - Image 7.1: a panel about water_leak
721 +== 3.3  Set button sound and ACK sound ==
545 545  
546 546  
547 -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.
724 +Feature: Turn on/off button sound and ACK alarm.
548 548  
549 -[[image:image-20241121141120-4.png||height="383" width="795"]]
726 +(% style="color:#4f81bd" %)**AT Command: AT+SOUND**
550 550  
551 - Image 7.2: Exported UI files
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
552 552  
740 +(% style="color:#4f81bd" %)**Downlink Command: 0xA1 **
553 553  
554 -3. **Delete and rename some file.** Here are the steps:
742 +Format: Command Code (0xA1) followed by 2 bytes mode value.
555 555  
556 - Step 1: Delete the 'components' directory.
557 - Step 2: Delete 'filelist.txt'.
558 - Step 3: Delete 'ui_helpers.c' and 'ui_helpers.h'.
559 - Step 4: Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
560 - Step 5: Rename the 'screens' directory to 'styles'.
744 +The first byte after 0XA1 sets the button sound, and the second byte after 0XA1 sets the ACK sound.** (0: off, 1: on)**
561 561  
562 -[[image:image-20241121151934-10.png||height="303" width="792"]]
746 +* **Example: **Downlink Payload: A10001  ~/~/ Set AT+SOUND=0,1  Turn off the button sound and turn on ACK sound.
563 563  
564 - image 7.3 rest file (1)
748 +== 3.4  Set buzzer music type(0~~4) ==
565 565  
566 -[[image:image-20241121142925-7.png||height="141" width="793"]]
567 567  
568 - image 7.4 rest file (2)
751 +Feature: Set different alarm key response sounds.There are five different types of button music.
569 569  
570 -4. Open the project in VS Code.
753 +(% style="color:#4f81bd" %)**AT Command: AT+OPTION**
571 571  
572 -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**."
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
573 573  
574 -[[image:image-20241121181957-17.png||height="438" width="516"]]
764 +OK
765 +)))
766 +|(% style="width:155px" %)AT+OPTION=1|(% style="width:124px" %)Set the buzzer music to type 1|(% style="width:86px" %)OK
575 575  
576 - image 7.5 extra_lib/CMakeLists.txt before adding
768 +(% style="color:#4f81bd" %)**Downlink Command: 0xA3**
577 577  
578 -[[image:image-20241121182239-18.png||height="520" width="518"]]
770 +Format: Command Code (0xA3) followed by 1 byte mode value.
579 579  
580 - image 7.6 extra_lib/CMakeLists.txt after adding
772 +* **Example: **Downlink Payload: A300  ~/~/ Set AT+OPTION=0  Set the buzzer music to type 0.
581 581  
582 -6.  **Modify the header files included in the fonts and images directories**.
774 +== 3.5  Set Valid Push Time ==
583 583  
584 -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.
585 585  
586 -[[image:image-20241121171629-11.png]]
777 +Feature: Set the holding time for pressing the alarm button to avoid miscontact. Values range from** 0 ~~1000ms**.
587 587  
588 - image 7.7 unmodified font file
779 +(% style="color:#4f81bd" %)**AT Command: AT+STIME**
589 589  
590 -[[image:image-20241121171901-12.png]]
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
591 591  
592 - image 7.8 modified font file
795 +(% style="color:#4f81bd" %)**Downlink Command: 0xA2**
593 593  
594 -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.
797 +Format: Command Code (0xA2) followed by 2 bytes mode value.
595 595  
596 -[[image:image-20241121172714-13.png]]
799 +* **Example: **Downlink Payload: A203E8  ~/~/ Set AT+STIME=1000  
597 597  
598 - image 7.9 unmodified image file
801 +**~ Explain: **Hold the alarm button for 10 seconds before the node will send the alarm packet.
599 599  
600 -[[image:image-20241121172908-14.png]]
601 601  
602 - image 7.10 modified image file
804 +
603 603  
604 -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).
806 += 6. FAQ =
605 605  
606 -[[image:image-20241121180030-15.png]]
808 +== 6.1 ==
607 607  
608 - image 7.11 ui_water_leak/CMakeLists.txt before modification
609 609  
610 -[[image:image-20241121180517-16.png]]
811 += 7. Order Info =
611 611  
612 - image 7.12 ui_water_leak/CMakeLists.txt after modification
813 +== 7.1  Part Number ==
613 613  
614 -
615 -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.
616 -
617 -[[image:image-20241122094200-23.png]]
618 -
619 - image 7.13 ui_water_leak.h (1) before modification
620 -
621 -[[image:image-20241122094320-24.png||height="852" width="554"]]
622 -
623 - image 7.14 ui_water_leak.h (2) before modification
624 -
625 -[[image:image-20241122094600-25.png||height="1078" width="554"]]
626 -
627 - image 7.15 ui_water_leak.h (1) after modification
628 -
629 -[[image:image-20241122094719-26.png||height="941" width="583"]]
630 -
631 - image 7.16 ui_water_leak.h (2) before modification
632 -
633 -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.
634 -
635 -_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.
636 -
637 -[[image:image-20241122102929-27.png||height="619" width="426"]]
638 -
639 - image 7.17 ui_water_leak.c (1) before modification
640 -
641 -[[image:image-20241122112838-30.png||height="551" width="628"]]
642 -
643 - image 7.18 ui_water_leak.c (2) before modification
644 -
645 -[[image:image-20241122110815-29.png||height="725" width="712"]]
646 -
647 - image 7.19 ui_water_leak.c (3) before modification
648 -
649 -[[image:image-20241122113158-31.png||height="872" width="677"]]
650 -
651 - image 7.20 ui_water_leak.c (1) after modification
652 -
653 -[[image:image-20241122113259-33.png||height="874" width="724"]]
654 -
655 - image 7.21 ui_water_leak.c (2) after modification
656 -
657 -[[image:image-20241122113359-34.png||height="804" width="746"]]
658 -
659 - image 7.22 ui_water_leak.c (3) after modification
660 -
661 -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.
662 -
663 -[[image:image-20241122134113-35.png||height="380" width="421"]]
664 -
665 - image 7.23 ui_water_leak_events_.h before modification
666 -
667 -[[image:image-20241122134420-37.png||height="201" width="283"]]
668 -
669 -image 7.24 ui_water_leak_events_.h after modification
670 -
671 -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.
672 -
673 -Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
674 -
675 -Step2. add code  below in delete_object() function definition.
676 -
677 - panel_all * panel = find_upper_by_SensorPanel(&arr,((lv_obj_t *)(e->user_data~)~)~);
678 -
679 - size_t index = panel->panel_obj_index;
680 -
681 - deleteElement(&arr, index);
682 -
683 -[[image:image-20241122135023-38.png||height="358" width="372"]]
684 -
685 - image 7.25 ui_water_leak_events_.c before modification
686 -
687 -[[image:image-20241122135258-39.png||height="403" width="559"]]
688 -
689 - image 7.26 ui_water_leak_events_.c after modification
690 -
691 -
692 -12. **Modify ui_water_leak_style.c file.**
693 -
694 -Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
695 -
696 - add '#include "../../sort.h"'
697 -
698 - add '#include "ui.h"'
699 -
700 -[[image:image-20241122141536-41.png||height="361" width="612"]]
701 -
702 - image 7.27 ui_water_leak_style.c (1) before modification
703 -
704 -[[image:image-20241122142129-42.png||height="386" width="613"]]
705 -
706 - image 7.28 ui_water_leak_style.c (1) after modification
707 -
708 -
709 -Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
710 -
711 - delete code as shown in image 7.29
712 -
713 -[[image:image-20241122145620-44.png||height="757" width="671"]]
714 -
715 - image 7.29 ui_water_leak_style.c (2)
716 -
717 -
718 -Step3. The image 7.30, 7.31 show the change.
719 -
720 -[[image:image-20241122152026-45.png||height="277" width="828"]]
721 -
722 - image 7.30 ui_water_leak_style.c (3) before modification
723 -
724 -[[image:image-20241122152542-46.png||height="293" width="830"]]
725 -
726 - image 7.31 ui_water_leak_style.c (3) after modification
727 -
728 -
729 -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).
730 -
731 -[[image:image-20241122153958-47.png]]
732 -
733 - image 7.32 ui_water_leak_style.c (4)
734 -
735 -
736 -[[image:image-20241122154755-49.png||height="864" width="513"]]
737 -
738 - image 7.33 ui_water_leak_style.c (4)
739 -
740 -
741 -Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 7.34).
742 -
743 -[[image:image-20241122155650-50.png||height="922" width="513"]]
744 -
745 - image 7.34 ui_water_leak_style.c (5)
746 -
747 -
748 -Step6. Add some lines of code in extra_lib/sort.h as shown in image 7.35.
749 -
750 -[[image:image-20241122161934-51.png]]
751 -
752 - image 7.35
753 -
754 -
755 -Step7. Add a line of code in extra_lib/sort.h as shown in image 7.36.
756 -
757 -[[image:image-20241122162852-53.png||height="330" width="529"]]
758 -
759 - image 7.37
760 -
761 -
762 -Step8. Add some code in ui_water_leak_style.c as shown in image 7.38 from line534 to line 576 in detail.
763 -
764 -panel_with_type union_sensor;
765 -
766 -union_sensor.panel_type = WATER_LEAK_TYPE;
767 -
768 -......
769 -
770 -lv_obj_set_x(union_sensor.panel_union.door.ui_PanelSensorDoor, x_by_index(index));
771 -
772 -lv_obj_set_y(union_sensor.panel_union.door.ui_PanelSensorDoor, y_by_index(index));
773 -
774 -return union_sensor;
775 -
776 -[[image:image-20250122173546-6.png||height="777" width="922"]]
777 -
778 - image 7.38
779 -
780 -
781 -13. Rest midification in sort.h file.
782 -
783 -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.
784 -
785 -[[image:image-20250122170230-1.png||height="580" width="513"]]
786 -
787 - image 7.39 sort.h
788 -
789 -13. **Modify sort.c file.**
790 -
791 -Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 26.
792 -
793 -[[image:image-20250122171910-5.png||height="524" width="510"]]
794 -
795 - image 7.40 sort.c (1)
796 -
797 -There are still some changes need to be done in sort.c, and omit here for the moment.
798 -
799 -
800 -
801 -= 8. FAQ =
802 -
803 -== 8.1 ==
804 -
805 -
806 -= 9. Order Info =
807 -
808 -== 9.1  Part Number ==
809 -
810 -
811 811  Part Number: (% style="color:#4472c4" %)LTS5
812 812  
817 +
813 813  
814 -== 9.2  Packing Info ==
819 +== 7.2  Packing Info ==
815 815  
816 -
817 817  **Package Includes**:
818 818  
819 819  * LTS5 HMI Touch Screen
... ... @@ -820,23 +820,23 @@
820 820  * 5V,2A DC Power Adapter.
821 821  * USB Type C Program Cable
822 822  
823 -= 10. Support =
824 824  
828 += 8. Support =
825 825  
826 826  * 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.
827 827  * 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]].
828 828  
829 -= 11.  Reference material =
830 830  
834 += 9.  Reference material =
831 831  
832 832  * Datasheet
833 -* schematic: [[LTS5-V1>>attach:LTS5-V1.pdf]]
834 -* 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]]
837 +* Source Code
835 835  * Mechinical
836 836  
837 -= 12. FCC Warning =
838 838  
841 += 10. FCC Warning =
839 839  
843 +
840 840  This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
841 841  
842 842  (1) This device may not cause harmful interference;
1727229396732-319.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -197.2 KB
Content
1727229550717-684.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -113.9 KB
Content
1727229582471-566.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -73.6 KB
Content
1727229618724-758.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -118.7 KB
Content
1727229653254-680.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -116.2 KB
Content
1727229682537-381.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.5 KB
Content
1727229715361-392.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -75.2 KB
Content
1727229740592-843.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -87.3 KB
Content
1727229760857-521.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -24.7 KB
Content
1727229798126-306.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -53.6 KB
Content
1727229821582-258.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -76.1 KB
Content
1727229845835-509.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -68.3 KB
Content
1727229892636-154.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -192.0 KB
Content
1727229926561-300.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -178.0 KB
Content
1727229955611-607.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -100.4 KB
Content
1727229990795-405.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -383.6 KB
Content
1727230012478-930.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -477.1 KB
Content
1727231038705-173.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -94.6 KB
Content
1727233636007-933.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -114.8 KB
Content
1727484665746-713.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -94.9 KB
Content
1727485118799-984.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -11.8 KB
Content
1727485251053-655.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -20.4 KB
Content
1727485480434-713.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -24.7 KB
Content
1727485933579-550.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -55.6 KB
Content
1727485953726-175.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -91.6 KB
Content
1727486567182-334.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -42.6 KB
Content
1727486578489-774.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -66.0 KB
Content
1727487368023-281.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -28.5 KB
Content
1727488067077-684.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -604.7 KB
Content
1727488099947-341.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -877.7 KB
Content
1727488108117-780.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -877.7 KB
Content
1727488157579-949.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -877.7 KB
Content
1738893226894-758.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -25.6 KB
Content
LTS5-V1.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -661.6 KB
Content
Screenshot 2024-12-24 134818.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -15.0 KB
Content
Screenshot 2024-12-24 134937.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -3.6 KB
Content
Screenshot 2024-12-24 140459.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -12.0 KB
Content
Screenshot 2024-12-24 144005.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -28.0 KB
Content
image-20240916101737-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -156.7 KB
Content
image-20240925110638-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -262.7 KB
Content
image-20240928090825-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -30.2 KB
Content
image-20240928103357-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -153.7 KB
Content
image-20240928103506-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -197.7 KB
Content
image-20240928105309-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -80.2 KB
Content
image-20240928110211-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -228.0 KB
Content
image-20240928111412-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -150.9 KB
Content
image-20240928111654-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -105.4 KB
Content
image-20240928112001-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -75.6 KB
Content
image-20240928113424-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -50.8 KB
Content
image-20240928114139-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -114.3 KB
Content
image-20240928144830-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -25.5 KB
Content
image-20241121113445-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -250.0 KB
Content
image-20241121120222-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -44.8 KB
Content
image-20241121120830-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -42.6 KB
Content
image-20241121141120-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -41.7 KB
Content
image-20241121141315-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -29.4 KB
Content
image-20241121141329-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -29.4 KB
Content
image-20241121142925-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -14.8 KB
Content
image-20241121145915-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -61.0 KB
Content
image-20241121150911-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -73.0 KB
Content
image-20241121151934-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -32.9 KB
Content
image-20241121171629-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -16.9 KB
Content
image-20241121171901-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -17.2 KB
Content
image-20241121172714-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -26.4 KB
Content
image-20241121172908-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -27.1 KB
Content
image-20241121180030-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -27.7 KB
Content
image-20241121180517-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -26.5 KB
Content
image-20241121181957-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -59.3 KB
Content
image-20241121182239-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -71.3 KB
Content
image-20241122092239-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -270.9 KB
Content
image-20241122092655-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -251.6 KB
Content
image-20241122093445-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -128.9 KB
Content
image-20241122093601-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -120.0 KB
Content
image-20241122094200-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -289.2 KB
Content
image-20241122094320-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -182.4 KB
Content
image-20241122094600-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -136.0 KB
Content
image-20241122094719-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -129.5 KB
Content
image-20241122102929-27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -219.9 KB
Content
image-20241122104344-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -257.1 KB
Content
image-20241122110815-29.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -246.1 KB
Content
image-20241122112838-30.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -263.9 KB
Content
image-20241122113158-31.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -133.7 KB
Content
image-20241122113252-32.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -152.3 KB
Content
image-20241122113259-33.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -152.3 KB
Content
image-20241122113359-34.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -126.5 KB
Content
image-20241122134113-35.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -69.3 KB
Content
image-20241122134412-36.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
image-20241122134420-37.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
image-20241122135023-38.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -28.7 KB
Content
image-20241122135258-39.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -40.3 KB
Content
image-20241122141526-40.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
image-20241122141536-41.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
image-20241122142129-42.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -85.1 KB
Content
image-20241122143105-43.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -60.2 KB
Content
image-20241122145620-44.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -394.0 KB
Content
image-20241122152026-45.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -201.6 KB
Content
image-20241122152542-46.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -95.3 KB
Content
image-20241122153958-47.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -241.1 KB
Content
image-20241122154745-48.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -135.7 KB
Content
image-20241122154755-49.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -135.7 KB
Content
image-20241122155650-50.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -104.4 KB
Content
image-20241122161934-51.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -230.3 KB
Content
image-20241122162612-52.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -58.7 KB
Content
image-20241122162852-53.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -125.5 KB
Content
image-20241122171211-54.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -173.3 KB
Content
image-20241122173706-55.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -37.6 KB
Content
image-20241122173718-56.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -37.6 KB
Content
image-20241226135550-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -293.3 KB
Content
image-20250122170230-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -77.3 KB
Content
image-20250122171809-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20250122171825-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20250122171832-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20250122171910-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20250122173546-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -200.4 KB
Content
image-20250207100150-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -54.1 KB
Content
image-20250207101415-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -17.6 KB
Content
image-20250207101515-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -24.1 KB
Content
image-20250207142334-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -62.0 KB
Content
image-20250207143131-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -48.7 KB
Content
image-20250207144605-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -58.1 KB
Content
image-20250207164320-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -194.5 KB
Content
image-20250207165702-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -78.1 KB
Content
image-20250207170215-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.6 KB
Content
image-20250207170307-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.2 KB
Content
image-20250207171650-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -11.0 KB
Content
image-20250207171851-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.5 KB
Content
image-20250207172010-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.5 KB
Content
image-20250207172246-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -2.5 KB
Content
image-20250207172443-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207172821-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -0 bytes
Content
image-20250207172834-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -0 bytes
Content
image-20250207173152-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207173159-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207173206-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207173212-27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -3.9 KB
Content
image-20250207192107-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -14.3 KB
Content
image-20250208170737-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -36.9 KB
Content
image-20250208170758-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -36.9 KB
Content
image-20250208175819-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -36.3 KB
Content
image-20250208175918-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -37.8 KB
Content
image-20250208180010-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -36.7 KB
Content
image-20250208181019-4.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -546.8 KB
Content
image-20250208181139-5.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -320.5 KB
Content
image-20250208181317-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -34.8 KB
Content
image-20250208181328-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -34.8 KB
Content
image-20250208181700-8.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -526.4 KB
Content
squalreline-trial.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -60.4 KB
Content
squareline-studio-launcher-screen.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -203.4 KB
Content
squareline.io_downloads.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -1.5 MB
Content