Skip to Content
Last modified by BoYang Xie on 2025/07/24 16:47
From version 4.8
edited by Edwin Chen
on 2024/09/16 09:00
Change comment: There is no comment for this version
To version 123.2
edited by Xiaoling
on 2024/12/24 11:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -1,9 +1,14 @@
1 -
1 +(% style="text-align:center" %)
2 2  [[image:image-20240915231842-1.png]]
3 3  
4 4  
5 +
6 +
7 +
8 +
9 +
5 5  (% _mstvisible="1" %)
6 -(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents：**
11 +(% _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 ==
24 +== 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.
27 +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.
29 +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.
31 +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  
33 +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
37 +
38 +* ESP32-WROOM MCU: 8MB RAM & 16MB ROM
39 +* 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,9 +40,18 @@
40 40  * 5V DC power
41 41  * IP Rating: IP52
42 42  
50 +== 1.3  Specifications ==
43 43  
44 -== 1.3  Specification ==
45 45  
53 +**LoRa**:
54 +
55 +* Frequency Range: 870 MHz ~~ 960 MHz
56 +* TCXO crystal to ensure RF performance on low temperature
57 +* Maximum Power +22 dBm constant RF output
58 +* High sensitivity: -148 dBm
59 +* LoRa Tx Current: <90 mA at +17 dBm, 108 mA at +22 dBm
60 +* LoRa Rx current: <9 mA
61 +
46 46  **WiFi:**
47 47  
48 48  * 802.11b/g/n
... ... @@ -56,29 +56,26 @@
56 56  * Bluetooth V4.2 BR/EDR and Bluetooth LE standard
57 57  * Class-1, Class-2, and Class-3 transmitters.
58 58  * AFH
59 -*
60 60  * CVSD and SBC
61 61  
62 62  **Display:**
63 63  
64 -* TFT Touch SCreen
65 -* Accuracy Tolerance: Typ ±0.2 °C
66 -* Long Term Drift: < 0.03 °C/yr
67 -* Operating Range: -10 ~~ 50 °C  or -40 ~~ 60 °C (depends on battery type, see [[FAQ>>||anchor="H6.5Whyiseedifferentworkingtemperatureforthedevice3F"]])
79 +* 5.0 Inch , 800 x 480
80 +* IPS Capacitive Touch SCreen
81 +* RGB color.
82 +* Display Area: 120.7*75.80 mm
68 68  
69 -
70 -
71 71  == 1.4  Power Consumption ==
72 72  
86 +
73 73  * External 5V DC power adapter
74 74  
75 -
76 76  == 1.5  Storage & Operation Temperature ==
77 77  
78 78  
79 --10 ~~ 50 °C  or -40 ~~ 60 °C (depends on battery type, see [[FAQ>>||anchor="H6.5Whyiseedifferentworkingtemperatureforthedevice3F"]])
92 +* Operation Temperature: -20 ~~ 70°C  (No Dew)
93 +* Storage Temperature: -30 ~~ 70°C  (No Dew)
80 80  
81 -
82 82  == 1.6  Applications ==
83 83  
84 84  
... ... @@ -89,722 +89,516 @@
89 89  * Smart Cities
90 90  * Smart Factory
91 91  
105 += 2.  Getting Started with 'Hello World' =
92 92  
93 -= 2.  Operation Mode =
107 +== 2.1  About this demo ==
94 94  
95 -== 2.1  How it work? ==
96 96  
110 +This getting started example demonstrates how to design and deploy a simple display UI for the LTS5 device. The example includes:
97 97  
98 -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**.
112 +* Creating a basic UI with a single button.
113 +* Implementing functionality to navigate the Web UI to a new page when the button is clicked.
114 +* Uploading the UI to the LTS5 device.
99 99  
116 +By completing this demo, you will gain foundational knowledge for customizing the LTS5 interface and building more advanced IoT applications.
100 100  
101 -== 2.2  How to Activate PB01? ==
102 102  
119 +== 2.2  Install Software Running Environment ==
103 103  
104 -(% style="color:red" %)** 1.  Open enclosure from below position.**
105 105  
106 -[[image:image-20220621093835-1.png]]
122 +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 107  
108 108  
109 -(% style="color:red" %)** 2.  Insert 2 x AAA LR03 batteries and the node is activated.**
125 +=== 2.2.1 Install VS Code and ESP-IDF extension ===
110 110  
111 -[[image:image-20220621093835-2.png]]
112 112  
128 +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]].
113 113  
114 -(% style="color:red" %)** 3. Under the above conditions, users can also reactivate the node by long pressing the ACT button.**
130 +Next, install the **ESP-IDF** extension within **VS Code**. Detailed steps for this process are shown in Image 1.
115 115  
116 -[[image:image-20220621093835-3.png]]
117 117  
133 +[[image:image-20240928110211-5.png||height="508" width="866"]]
118 118  
119 -User can check [[LED Status>>||anchor="H2.8LEDIndicator"]] to know the working state of PB01.
135 + Image 1: ESP-IDF extension install
120 120  
137 +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]]
121 121  
122 -== 2.3  Example to join LoRaWAN network ==
123 123  
140 +=== 2.2.2 Install SquareLine Studio ===
124 124  
125 -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.
126 126  
127 -(% _mstvisible="1" class="wikigeneratedid" %)
128 -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 +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.4.2.
129 129  
130 -[[image:image-20240705094824-4.png]]
145 +[[image:squareline.io_downloads.png]]
131 131  
132 -(% style="color:blue" %)**Step 1**(%%):  Create a device in TTN V3 with the OTAA keys from PB01.
133 133  
134 -Each PB01 is shipped with a sticker with the default DEV EUI as below:
148 +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 135  
136 -[[image:image-20230426083617-1.png||height="294" width="633"]]
150 +* Max. 10 screens
151 +* Max. 150 widgets
152 +* Max. 5 global colors
153 +* Max. 2 themes
154 +* Max. 1 component
137 137  
156 +== 2.3 Simple usage of SquareLine Studio and exporting UI code ==
138 138  
139 -Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
140 140  
141 -Create application.
159 +After launching and logging into the software, create a new project as shown in Image 2.
142 142  
143 -choose to create the device manually.
161 +* Select the major **LVGL** version as **8.3**.
162 +* Select the **Desktop** tab.
163 +* Select  **Eclipse with  SDL for  development on PC**:
164 +* In the **PROJECT SETTINGS**, select **LVGL version** **8.3.11**
165 +* Select the **CREATE **button.
144 144  
145 -Add JoinEUI(AppEUI), DevEUI, AppKey.(% style="display:none" %)
167 +[[image:image-20240928103357-2.png||height="680" width="708"]]
146 146  
147 -[[image:image-20240507142116-1.png||height="410" width="1138"]](% style="display:none" %) (%%)
148 -
169 + Image 2: Creating a new SquareLine project
149 149  
150 -[[image:image-20240507142157-2.png||height="559" width="1147"]]
151 151  
152 -[[image:image-20240507142401-3.png||height="693" width="1202"]]
172 +Next, you need to configure some settings for this project. By clicking in the specified order shown in Image 3, you will be directed to the page displayed in Image 4.
153 153  
154 -[[image:image-20240507142651-4.png||height="760" width="1190"]]
174 +* Select** File  -> Project Settings**
155 155  
156 -**Default mode OTAA**(% style="display:none" %)
176 +[[image:1727229582471-566.png]]
157 157  
178 + Image 3 accessing project settings
158 158  
159 -(% 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.
160 160  
161 -[[image:image-20240507143104-5.png||height="434" width="1398"]]
181 +In the PROJECT SETTINGS dialog box, configure/modify the project settings:
162 162  
183 +* **UI Files Export Root**: Select a folder on your computer to store the UI files.
184 +* **LVGL Include Path**: Set this to **lvgl.h**
185 +* **Click on the APPLY CHANGES button.**
163 163  
164 -== 2.4  Uplink Payload ==
187 +[[image:image-20240928105309-4.png||height="526" width="556"]]
165 165  
189 + Image 4 Configure/modify project settings
166 166  
167 -Uplink payloads include two types: Valid Sensor Value and other status / control command.
168 168  
169 -* Valid Sensor Value: Use FPORT=2
170 -* Other control command: Use FPORT other than 2.
192 +Now you can start building the sample UI. Follow the steps below:
171 171  
172 -=== 2.4.1  Uplink FPORT~=5, Device Status ===
173 173  
195 +=== **Add widgets** ===
174 174  
175 -Users can  get the Device Status uplink through the downlink command:
176 176  
177 -(% style="color:#4472c4" %)**Downlink:  **(%%)**0x2601**
198 +To add widgets navigate to the **Widgets** area, then click on the widgets you want to add. The selected widgets will be added to the screen. You can reposition the widgets in the screen area by clicking and dragging them.
178 178  
179 -Uplink the device configures with FPORT=5.
200 +Add a Label, Button, and Image to the screen as shown in **Image 5**.
180 180  
181 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:370px" %)
182 -|=(% 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**
183 -|(% 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
202 +[[image:image-20240928111412-6.png||height="526" width="864"]]
184 184  
185 -[[image:image-20240507152130-12.png||height="469" width="1366"]](% style="display:none" %)
204 + Image 5: Add widgets
186 186  
187 -Example Payload (FPort=5):  [[image:image-20240507152254-13.png||height="26" width="130"]]
188 188  
207 +=== **Modify widget properties** ===
189 189  
190 -(% style="color:#4472c4" %)**Sensor Model**(%%): For PB01, this value is 0x35.
191 191  
192 -(% style="color:#4472c4" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version.
210 +The area for modifying widgets is called the **Inspector** tab. The Inspector tab consists of four sections: **COMPONENT**, **<WIDGET>**, **STYLE SETTINGS**, and **EVENTS**, as shown in Image 6.
193 193  
194 -(% style="color:#4472c4" %)**Frequency Band**:
212 +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.
195 195  
196 -*0x01: EU868
214 +[[image:1727485118799-984.png]]
197 197  
198 -*0x02: US915
216 + Image 6: The button widget's "Inspector" tab
199 199  
200 -*0x03: IN865
201 201  
202 -*0x04: AU915
219 +==== **Changing the Button properties** ====
203 203  
204 -*0x05: KZ865
205 205  
206 -*0x06: RU864
222 +Click the Button.
207 207  
208 -*0x07: AS923
224 +Under the "Layout" you can change the button's position and size.
209 209  
210 -*0x08: AS923-1
226 +[[image:1727485251053-655.png]]
211 211  
212 -*0x09: AS923-2
228 +Image 7: The button widget's "BUTTON" tab
213 213  
214 -*0x0a: AS923-3
215 215  
231 +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.
216 216  
217 -(% style="color:#4472c4" %)**Sub-Band**(%%): value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
233 +* Click **ADD EVENT** button.
234 +* Select **CLICKED** under the Trigger.
235 +* Select **Screen2** from **Screen to**.
236 +* Select **FADE ON** from **Fade mode**.
237 +* Enter **500** in the **Speed** text box.
238 +* Finally, click **ADD** button.
218 218  
219 -(% style="color:#4472c4" %)**BAT**(%%): shows the battery voltage for PB01.
240 +[[image:1727485480434-713.png||height="395" width="290"]]
220 220  
221 -(% style="color:#4472c4" %)**Ex1**(%%): 0x0C DE = 3294mV
242 + Image 8: Add an event for the button
222 222  
223 223  
224 -=== 2.4.2  Uplink FPORT~=2, Real time sensor value ===
245 +==== **Changing the label properties** ====
225 225  
226 226  
227 -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"]].
248 +Click the label. Under the **Label** section, type "Click For Detail" in the **Text** textbox.
228 228  
229 -Uplink uses FPORT=2 and every 20 minutes send one uplink by default.
250 +[[image:image-20240928090825-1.png||height="327" width="391"]]
230 230  
231 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:460px" %)
232 -|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
233 -**Size(bytes)**
234 -)))|=(% style="width: 60px;background-color:#4F81BD;color:white" %)2|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
235 -**1**
236 -)))|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
237 -**1**
238 -)))|=(% style="width: 90px;background-color:#4F81BD;color:white" %)(((
239 -**2**
240 -)))|=(% style="width: 40px;background-color:#4F81BD;color:white" %)(((
241 -**2**
242 -)))
243 -|(% style="width:97px" %)(((
244 -Value
245 -)))|(% style="width:39px" %)Battery|(% style="width:39px" %)(((
246 -Sound_ACK
252 + Image 9:  Modify text of label widget
247 247  
248 -&Sound_key
249 -)))|(% style="width:100px" %)(((
250 -(((
251 -Alarm
252 -)))
253 -)))|(% style="width:77px" %)(((
254 -(((
255 -Temperature
256 -)))
257 -)))|(% style="width:47px" %)(((
258 -Humidity
259 -)))
260 260  
261 -Example in TTN.
255 +==== **Changing image properties** ====
262 262  
263 -[[image:image-20240507150155-11.png||height="549" width="1261"]]
264 264  
265 -Example Payload (FPort=2):  (% style="background-color:yellow" %)**0C EA 03 01 01 11 02 A8**
258 +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. One way is to move your image into the folder "…/squareline project/assets/", as shown in image 10. 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" area in SquareLine Studio, as demonstrated in image 11.
266 266  
267 -==== (% style="color:blue" %)**Battery:**(%%) ====
260 +[[image:image-20240928113424-9.png||height="355" width="505"]]
268 268  
269 -Check the battery voltage.
262 + image 10 add image file into SquareLine Studio project
270 270  
271 -* Ex1: 0x0CEA = 3306mV
272 -* Ex2: 0x0D08 = 3336mV
264 +[[image:image-20240928114139-10.png||height="559" width="810"]]
273 273  
274 -==== (% style="color:blue" %)**Sound_ACK & Sound_key:**(%%) ====
266 + image 11 use image widget in SquareLine Studio
275 275  
276 -Key sound and ACK sound are enabled by default.
277 277  
278 -* Example1: 0x03
269 +==== **The relationship between widgets** ====
279 279  
280 - Sound_ACK: (03>>1) & 0x01=1, OPEN.
281 281  
282 -**~ ** Sound_key:  03 & 0x01=1, OPEN.
272 +Widgets commonly have two types of relationships: **parallel** and **parent-child**.
283 283  
284 -* Example2: 0x01
274 +* In a **parallel relationship**, widgets' positions are determined relative to a shared reference object.
275 +* 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, as shown in Image 13.
285 285  
286 - Sound_ACK: (01>>1) & 0x01=0, CLOSE.
277 +[[image:1727486567182-334.png||height="318" width="278"]]
287 287  
288 -**~ ** Sound_key:  01 & 0x01=1, OPEN.
289 289  
280 +Move **Label1** to make it a child of **Button1**. See Image 13.
290 290  
291 -==== (% style="color:blue" %)**Alarm:**(%%) ====
282 +[[image:image-20240928112001-8.png||height="431" width="796"]]
292 292  
293 -Key alarm.
284 + Image 13: Move Label1 to make it a child of Button1.
294 294  
295 -* Ex1: 0x01 & 0x01=1, TRUE.
296 -* Ex2: 0x00 & 0x01=0, FALSE.
297 297  
298 -==== (% style="color:blue" %)**Temperature:**(%%) ====
287 +==== **Preview the screen** ====
299 299  
300 -* Example1:  0x0111/10=27.3℃
301 -* Example2:  (0xFF0D-65536)/10=-24.3℃
302 302  
303 -If payload is: FF0D :  (FF0D & 8000 == 1) , temp = (FF0D - 65536)/100 =-24.3℃
290 +You can test the result by clicking on the **PLAY** button. The screen will change into play mode. See Image 14.
304 304  
305 -（FF0D & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative）
292 +[[image:1727487368023-281.png]]
306 306  
294 + Image 14: Simulating the project
307 307  
308 -==== (% style="color:blue" %)**Humidity:**(%%) ====
309 309  
310 -* Humidity:    0x02A8/10=68.0%
297 +For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
311 311  
312 -=== 2.4.3  Uplink FPORT~=3, Datalog sensor value ===
313 313  
300 +== 2.4 Integrate UI Code to ESP-IDF Project ==
314 314  
315 -PB01 stores sensor value and user can retrieve these history value via downlink command. The Datalog sensor value are sent via FPORT=3.
316 316  
317 -[[image:image-20240510144912-1.png||height="471" width="1178"]](% style="display:none" %)
303 +To achieve the integrating, we first need to export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
318 318  
305 +[[image:1727229798126-306.png]]
319 319  
320 -* 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" %)
307 + image 15 export UI file
321 321  
322 -For example, in US915 band, the max payload for different DR is:
309 +[[image:1727229821582-258.png||height="333" width="662"]]
323 323  
324 -1. **DR0**: max is 11 bytes so one entry of data
325 -1. **DR1**: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
326 -1. **DR2**: total payload includes 11 entries of data
327 -1. **DR3**: total payload includes 22 entries of data.
311 + image 16 exported UI file
328 328  
329 -(% 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.**
313 +Create a empty directory entitled "ui" in path "basic_prj/app_components/ui/", and then copy all UI code exported to this directory.
330 330  
331 -See more info about the [[Datalog feature>>||anchor="H2.6A0DatalogFeature"]].
315 +[[image:image-20240928144830-11.png]]
332 332  
333 -(% style="display:none" %) (%%)
317 + image 17 open CMakeLists.txt
334 334  
335 -=== 2.4.4  Decoder in TTN V3 ===
319 +[[image:1727229892636-154.png||height="521" width="407"]]
336 336  
321 + image 18 modify CMakeLists.txt
337 337  
338 -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.
323 +The last step of integrating is adding two lines of code in main.c file.
339 339  
340 -In TTN , add formatter as below:
325 +[[image:1727229926561-300.png]]
341 341  
342 -[[image:image-20240507162814-16.png||height="778" width="1135"]]
327 + image 19 add "ui.h"
343 343  
344 -(((
345 -Please check the decoder from this link:  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]
346 -)))
329 +[[image:1727229955611-607.png]]
347 347  
348 -(((
349 -
350 -)))
331 + image 20 add "ui_init()"
351 351  
352 -== 2.5 Show data on Datacake ==
353 353  
334 +== 2.5 Brief introduction of hello world project ==
354 354  
355 -(((
356 -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:
357 -)))
358 358  
359 -(((
360 -
361 -)))
337 +The project consists of two screens. The first screen displays the company's logo, the project name, and a button to navigate to the next screen. The second screen presents some information about this HMI screen product through an image and includes a button to return to the previous screen.
362 362  
363 -(((
364 -(% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the LoRaWAN network.
365 -)))
366 366  
367 -(((
368 -(% 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.
369 -)))
340 +== 2.6 Test Result ==
370 370  
371 -(((
372 -~1. Add Datacake:
373 -)))
374 374  
375 -(((
376 -2. Select default key as Access Key:
377 -)))
343 +By pressing the button lying bottom right, the screen can switch to another as expected. This indicates that the UI file has been successfully integrated into the project and is now effective.
378 378  
379 -(((
380 -3. In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add PB01:
381 -)))
345 +[[image:1727488067077-684.png||height="402" width="574"]]
382 382  
383 -(((
384 - Please refer to the figure below.
385 -)))
347 + image 21 screen1
386 386  
387 -[[image:image-20240510150924-2.png||height="612" width="1186"]]
349 +[[image:1727488157579-949.png||height="397" width="572"]]
388 388  
351 + image 22 screen2
389 389  
390 -Log in to DATACAKE, copy the API under the account.
391 391  
392 -[[image:image-20240510151944-3.png||height="581" width="1191"]]
354 += 3. Example Project 1: LoRa Central Display =
393 393  
356 +[[image:image-20240916101737-1.png||height="468" width="683"]]
394 394  
395 395  
396 -[[image:image-20240510152150-4.png||height="697" width="1188"]]
359 += 4. Example Project 2: LoRaWAN RS485 Alarm =
397 397  
361 += 5. The way to add a new panel to project =
398 398  
399 -[[image:image-20240510152300-5.png||height="298" width="1191"]]
400 400  
364 +**~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.**
401 401  
402 -[[image:image-20240510152355-6.png||height="782" width="1193"]]
366 +[[image:image-20241121113445-1.png||height="584" width="934"]]
403 403  
404 -[[image:image-20240510152542-8.png||height="545" width="739"]]
368 + image 5.1 a panel about water_leak
405 405  
406 -[[image:image-20240510152634-9.png||height="748" width="740"]]
407 407  
371 +**2. Export the ui file.** You need  to adjust the export path first, then click "Export->Export UI Files". This step had been introduced before. Then you can get the ui files as shown in image 5.2.
408 408  
409 -[[image:image-20240510152809-10.png||height="607" width="732"]]
373 +[[image:image-20241121141120-4.png||height="383" width="795"]]
410 410  
411 -[[image:image-20240510153934-14.png||height="460" width="1199"]]
375 + image 5.2 ui files exported
412 412  
413 413  
414 -[[image:image-20240510153435-12.png||height="428" width="1197"]]
378 +**3. Delete or rename some file.** Here are the steps:
415 415  
380 + Step1 Delete the 'components' directory.
381 + Step2 Delete 'filelist.txt'.
382 + Step3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
383 + Step4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
384 + Step5 Rename the 'screens' directory to 'styles'.
416 416  
417 -Copy and paste the [[TTN decoder>>https://github.com/dragino/dragino-end-node-decoder]] here and save.
386 +[[image:image-20241121151934-10.png||height="303" width="792"]]
418 418  
419 -[[image:image-20240510153624-13.png||height="468" width="1195"]]
388 + image 5.3 rest file (1)
420 420  
390 +[[image:image-20241121142925-7.png||height="141" width="793"]]
421 421  
422 -Visual widgets please read the DATACAKE documentation.
392 + image 5.4 rest file (2)
423 423  
424 -(% style="display:none" %) (%%)
394 +**4. Open this project in vscode.**
425 425  
426 -== 2.6  Datalog Feature ==
396 +5. Add file include path about water_leak in extra_lib/CMakeLists.txt as shown in image 5.5, 5.6, and its format is similar to the tem_hum or door.
427 427  
398 +[[image:image-20241121181957-17.png||height="438" width="516"]]
428 428  
429 -(% _msthash="315262" _msttexthash="32283004" _mstvisible="1" %)
430 -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.
400 + image 5.5 extra_lib/CMakeLists.txt before add
431 431  
402 +[[image:image-20241121182239-18.png||height="520" width="518"]]
432 432  
433 -=== 2.6.1  Unix TimeStamp ===
404 + image 5.6 extra_lib/CMakeLists.txt after add
434 434  
406 +**6. Modify header file include in fonts and images directory.** Open the fonts/ui_font_Font12.c file, as shown in image 5.7, then modify the '#include "../ui.h"' to '#include "../ui_water_leak.h"', the image 5.8 is the modified image. Other font file need to be modified in same way.
435 435  
436 -Unix TimeStamp shows the sampling time of uplink payload. format base on
408 +[[image:image-20241121171629-11.png]]
437 437  
438 -[[image:image-20220523001219-11.png||_mstalt="450450" _mstvisible="3" height="97" width="627"]]
410 + image 5.7 before-modified font file
439 439  
440 -User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/||_mstvisible="3"]] :
412 +[[image:image-20241121171901-12.png]]
441 441  
442 -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)
414 + image 5.8 modified font file
443 443  
416 +Open the images/ui_img_battery_empty_png.c file, as shown in image 5.9, then modify the '#include "../ui.h"' to '#include "../ui_water_leak.h"', the image 5.10 is the modified image. Other image file need to be modified in same way.
444 444  
445 -[[image:1655782409139-256.png]]
418 +[[image:image-20241121172714-13.png]]
446 446  
420 + image 5.9 before-modified image file
447 447  
448 -=== 2.6.2  Poll sensor value ===
422 +[[image:image-20241121172908-14.png]]
449 449  
424 + image 5.10 modified image file
450 450  
451 -(((
452 -User can poll sensor value based on timestamps from the server. Below is the downlink command.
453 -)))
426 +**7. Modify the ui_water_leak/CMakeLists.txt.** Open this file, and modify it from image 5.11 to image 5.12.
454 454  
455 -(((
456 -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.
457 -)))
428 +[[image:image-20241121180030-15.png]]
458 458  
459 -(((
460 -For example, downlink command [[image:image-20220621113526-13.png]] (% _mstvisible="3" style="display:none" %)
461 -)))
430 + image 5.11 ui_water_leak/CMakeLists.txt before modification
462 462  
463 -(((
464 -Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00's data
465 -)))
432 +[[image:image-20241121180517-16.png]]
466 466  
467 -(((
468 -Uplink Internal =5s，means PB01 will send one packet every 5s. range 5~~255s.
469 -)))
434 + image 5.12 ui_water_leak/CMakeLists.txt after modification
470 470  
436 +**8. Modify ui_water_leak.h file.** The image 5.13, 5.14 show the code before modification, and the image 5.15, 5.16 show the code after modification.
471 471  
472 -=== 2.6.3  Datalog Uplink payload ===
438 +[[image:image-20241122094200-23.png]]
473 473  
440 + image 5.13 ui_water_leak.h (1) before modification
474 474  
475 -See [[Uplink FPORT=3, Datalog sensor value>>||anchor="H2.4.3A0UplinkFPORT3D32CDatalogsensorvalue"]]
442 +[[image:image-20241122094320-24.png||height="852" width="554"]]
476 476  
477 -(% style="display:none" %) (%%) (% style="display:none" %)
444 + image 5.14 ui_water_leak.h (2) before modification
478 478  
479 -== 2.7 Button ==
446 +[[image:image-20241122094600-25.png||height="1078" width="554"]]
480 480  
448 + image 5.15 ui_water_leak.h (1) after modification
481 481  
482 -* ACT button
450 +[[image:image-20241122094719-26.png||height="941" width="583"]]
483 483  
484 -Long press this button PB01 will reset and join network again.
452 + image 5.16 ui_water_leak.h (2) before modification
485 485  
486 -[[image:image-20240510161626-17.png||height="192" width="224"]]
454 +**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.
487 487  
488 -* Alarm button
456 +_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.
489 489  
490 -Press the button PB01 will immediately uplink data, and alarm is "TRUE".
458 +[[image:image-20241122102929-27.png||height="619" width="426"]]
491 491  
492 -[[image:image-20240705095149-5.png||height="164" width="162"]](% style="display:none" %)
460 + image 5.17 ui_water_leak.c (1) before modification
493 493  
462 +[[image:image-20241122112838-30.png||height="551" width="628"]]
494 494  
495 -== 2.8 LED Indicator ==
464 + image 5.18 ui_water_leak.c (2) before modification
496 496  
466 +[[image:image-20241122110815-29.png||height="725" width="712"]]
497 497  
498 -(((
499 -The PB01 has a triple color LED which for easy showing different stage.
500 -)))
468 + image 5.19 ui_water_leak.c (3) before modification
501 501  
502 -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
470 +[[image:image-20241122113158-31.png||height="872" width="677"]]
503 503  
504 -(((
505 -(% style="color:#037691" %)**In a normal working state**:
506 -)))
472 + image 5.20 ui_water_leak.c (1) after modification
507 507  
508 -* 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" %)**.**
509 -* During OTAA Join:
510 -** **For each Join Request uplink:** the (% style="color:green" %)**GREEN LED** (%%)will blink once.
511 -** **Once Join Successful:** the (% style="color:green" %)**GREEN LED**(%%) will be solid on for 5 seconds.
512 -* After joined, for each uplink, the (% style="color:blue" %)**BLUE LED**(%%) or (% style="color:green" %)**GREEN LED** (%%)will blink once.
513 -* 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.
474 +[[image:image-20241122113259-33.png||height="874" width="724"]]
514 514  
515 -(((
516 -
517 -)))
476 + image 5.21 ui_water_leak.c (2) after modification
518 518  
519 -== 2.9 Buzzer ==
478 +[[image:image-20241122113359-34.png||height="804" width="746"]]
520 520  
480 + image 5.22 ui_water_leak.c (3) after modification
521 521  
522 -The PB01 has** button sound** and** ACK sound** and users can turn on or off both sounds by using [[AT+SOUND>>||anchor="H3.3A0Setbuttonsoundandbuttonalarm"]].
482 +**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.
523 523  
524 -* (% style="color:#4f81bd" %)**Button sound**(%%)** **is the music produced by the node after the alarm button is pressed.
484 +[[image:image-20241122134113-35.png||height="380" width="421"]]
525 525  
526 - Users can use[[ AT+OPTION>>||anchor="H3.4A0Setbuzzermusic2807E429"]] to set different button sounds.
486 + image 5.23 ui_water_leak_events_.h before modification
527 527  
528 -* (% style="color:#4f81bd" %)**ACK sound **(%%)is the notification tone that the node receives ACK.
488 +[[image:image-20241122134420-37.png||height="201" width="283"]]
529 529  
530 -= 3.  Configure PB01 via AT command or LoRaWAN downlink =
490 +image 5.24 ui_water_leak_events_.h after modification
531 531  
492 +**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.
532 532  
533 -Users can configure PB01 via AT Command or LoRaWAN Downlink.
494 +Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
534 534  
535 -* AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
496 +Step2. add code  below in delete_object() function definition.
536 536  
537 -* LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
498 + panel_all * panel = find_upper_by_SensorPanel(&arr,((lv_obj_t *)(e->user_data~)~)~);
538 538  
539 -There are two kinds of commands to configure PB01, they are:
500 + size_t index = panel->panel_obj_index;
540 540  
541 -* (% style="color:#4f81bd" %)**General Commands:**
502 + deleteElement(&arr, index);
542 542  
543 -These commands are to configure:
504 +[[image:image-20241122135023-38.png||height="358" width="372"]]
544 544  
545 -* General system settings like: uplink interval.
506 + image 5.25 ui_water_leak_events_.c before modification
546 546  
547 -* LoRaWAN protocol & radio-related commands.
508 +[[image:image-20241122135258-39.png||height="403" width="559"]]
548 548  
549 -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]]
510 + image 5.26 ui_water_leak_events_.c after modification
550 550  
551 551  
552 -* (% style="color:#4f81bd" %)**Commands special design for PB01**
513 +**12. Modify ui_water_leak_style.c file.**
553 553  
554 -These commands are only valid for PB01, as below:
515 +Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
555 555  
556 -(% style="display:none" %) (%%)
517 + add '#include "../../sort.h"'
557 557  
558 -== 3.1  Downlink Command Set ==
519 + add '#include "ui.h"'
559 559  
521 +[[image:image-20241122141536-41.png||height="361" width="612"]]
560 560  
561 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %)
562 -|=(% 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**
563 -|(% style="width:130px" %)AT+TDC=?|(% style="width:151px" %)(((
564 -
523 + image 5.27 ui_water_leak_style.c (1) before modification
565 565  
566 -View current TDC time
567 -)))|(% style="width:92px" %)(((
568 -1200000
569 -OK
570 -)))|(% style="width:206px" %)Default 1200000(ms)
571 -|(% style="width:130px" %)AT+TDC=300000|(% style="width:151px" %)Set TDC time|(% style="width:92px" %)OK|(% style="width:206px" %)(((
572 -(((
573 -0X0100012C:
574 -01: fixed command
575 -00012C: 0X00012C=
525 +[[image:image-20241122142129-42.png||height="386" width="613"]]
576 576  
577 -300(seconds)
578 -)))
527 + image 5.28 ui_water_leak_style.c (1) after modification
579 579  
580 -(((
581 -
582 -)))
583 -)))
584 -|(% style="width:130px" %)ATZ|(% style="width:151px" %)Reset node|(% style="width:92px" %) |(% style="width:206px" %)0x04FF
585 -|(% style="width:130px" %)AT+FDR|(% style="width:151px" %)Restore factory settings|(% style="width:92px" %) |(% style="width:206px" %)0X04FE
586 -|(% style="width:130px" %)AT+CFM=?|(% style="width:151px" %)View the current confirmation mode status|(% style="width:92px" %)(((
587 -0,7,0
588 588  
589 -OK
590 -)))|(% style="width:206px" %)Default 0,7,0
591 -|(% style="width:130px" %)AT+CFM=1,7,1|(% style="width:151px" %)(((
592 -Confirmed uplink mode, the maximum number of retries is seven, and uplink fcnt increase by 1 for each retry
593 -)))|(% style="width:92px" %)(((
594 -OK
595 -)))|(% style="width:206px" %)(((
596 -05010701
530 +Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
597 597  
598 -05: fixed command
532 + delete code as shown in image 5.29
599 599  
600 -01:confirmed uplink
534 +[[image:image-20241122145620-44.png||height="757" width="671"]]
601 601  
602 -07: retry 7 times
536 + image 5.29 ui_water_leak_style.c (2)
603 603  
604 -01: fcnt count plus 1
605 -)))
606 -|(% style="width:130px" %)AT+NJM=?|(% style="width:151px" %)(((
607 -Check the current network connection method
608 -)))|(% style="width:92px" %)(((
609 -1
610 -OK
611 -)))|(% style="width:206px" %)Default 1
612 -|(% style="width:130px" %)AT+NJM=0|(% style="width:151px" %)Change the network connection method to ABP|(% style="width:92px" %)(((
613 -Attention:Take effect after ATZ
614 -OK
615 -)))|(% style="width:206px" %)(((
616 -0X2000: ABP
617 -0x2001: OTAA
618 -20: fixed command
619 -)))
620 -|(% style="width:130px" %)AT+RPL=?|(% style="width:151px" %)View current RPL settings|(% style="width:92px" %)(((
621 -0
622 -OK
623 -)))|(% style="width:206px" %)Default 0
624 -|(% style="width:130px" %)AT+RPL=1|(% style="width:151px" %)set RPL=1    |(% style="width:92px" %)OK|(% style="width:206px" %)(((
625 -0x2101:
626 -21: fixed command
627 -01: for details, check wiki
628 -)))
629 -|(% style="width:130px" %)AT+ADR=?|(% style="width:151px" %)View current ADR status|(% style="width:92px" %)(((
630 -1
631 -OK
632 -)))|(% style="width:206px" %)Default 0
633 -|(% style="width:130px" %)AT+ADR=0|(% style="width:151px" %)Set the ADR state to off|(% style="width:92px" %)OK|(% style="width:206px" %)(((
634 -0x2200: close
635 -0x2201: open
636 -22: fixed command
637 -)))
638 -|(% style="width:130px" %)AT+DR=?|(% style="width:151px" %)View the current DR settings|(% style="width:92px" %)OK|(% style="width:206px" %)
639 -|(% style="width:130px" %)AT+DR=1|(% style="width:151px" %)(((
640 -set DR to 1
641 -It takes effect only when ADR=0
642 -)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
643 -0X22000101:
644 -00: ADR=0
645 -01: DR=1
646 -01: TXP=1
647 -22: fixed command
648 -)))
649 -|(% style="width:130px" %)AT+TXP=?|(% style="width:151px" %)View the current TXP|(% style="width:92px" %)OK|(% style="width:206px" %)
650 -|(% style="width:130px" %)AT+TXP=1|(% style="width:151px" %)(((
651 -set TXP to 1
652 -It takes effect only when ADR=0
653 -)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
654 -0X22000101:
655 -00: ADR=0
656 -01: DR=1
657 -01: TXP=1
658 -22: fixed command
659 -)))
660 -|(% style="width:130px" %)AT+RJTDC=10|(% style="width:151px" %)Set RJTDC time interval|(% style="width:92px" %)OK|(% style="width:206px" %)(((
661 -0X26000A:
662 -26: fixed command
663 -000A: 0X000A=10(min)
664 -for details, check wiki
665 -)))
666 -|(% style="width:130px" %) |(% style="width:151px" %)(((
667 -(((
668 -~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_
669 669  
670 -Retrieve stored data for a specified period of time
671 -)))
539 +Step3. The image 5.30, 5.31 show the change.
672 672  
673 -(((
674 -
675 -)))
676 -)))|(% style="width:92px" %) |(% style="width:206px" %)(((
677 -0X3161DE7C7061DE8A800A:
678 -31: fixed command
679 -61DE7C70:0X61DE7C70=2022/1/12 15:00:00
680 -61DE8A80:0X61DE8A80=2022/1/12 16:00:00
681 -0A: 0X0A=10(second)
682 -View details 2.6.2
683 -)))
684 -|(% style="width:130px" %)AT+DDETECT=?|(% style="width:151px" %)View the current DDETECT setting status and time|(% style="width:92px" %)(((
685 -1,1440,2880
686 -OK
687 -)))|(% style="width:206px" %)Default 1,1440,2880(min)
688 -|(% style="width:130px" %)AT+DDETECT=(((
689 -1,1440,2880
690 -)))|(% style="width:151px" %)(((
691 -Set DDETECT setting status and time
692 -((% style="color:red" %)When the node does not receive the downlink packet within the set time, it will re-enter the network(%%))
693 -)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
694 -0X320005A0: close
695 -0X320105A0: open
696 -32: fixed command
697 -05A0: 0X05A0=1440(min)
698 -)))
541 +[[image:image-20241122152026-45.png||height="277" width="828"]]
699 699  
700 -== 3.2  Set Password ==
543 + image 5.30 ui_water_leak_style.c (3) before modification
701 701  
545 +[[image:image-20241122152542-46.png||height="293" width="830"]]
702 702  
703 -Feature: Set device password, max 9 digits.
547 + image 5.31 ui_water_leak_style.c (3) after modification
704 704  
705 -(% style="color:#4f81bd" %)**AT Command: AT+PWORD**
706 706  
707 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
708 -|(% 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**
709 -|(% style="width:155px" %)AT+PWORD=?|(% style="width:124px" %)Show password|(% style="width:86px" %)(((
710 -123456
711 -OK
712 -)))
713 -|(% style="width:155px" %)AT+PWORD=999999|(% style="width:124px" %)Set password|(% style="width:86px" %)OK
550 +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).
714 714  
715 -(% style="color:#4f81bd" %)**Downlink Command:**
552 +[[image:image-20241122153958-47.png]]
716 716  
717 -No downlink command for this feature.
554 + image 5.32 ui_water_leak_style.c (4)
718 718  
556 +[[image:image-20241122154755-49.png||height="864" width="513"]]
719 719  
720 -== 3.3  Set button sound and ACK sound ==
558 + image 5.33 ui_water_leak_style.c (4)
721 721  
722 722  
723 -Feature: Turn on/off button sound and ACK alarm.
561 +Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
724 724  
725 -(% style="color:#4f81bd" %)**AT Command: AT+SOUND**
563 +[[image:image-20241122155650-50.png||height="922" width="513"]]
726 726  
727 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
728 -|(% 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**
729 -|(% style="width:155px" %)(((
730 -AT+SOUND=?
731 -)))|(% style="width:124px" %)Get the current status of button sound and ACK sound|(% style="width:86px" %)(((
732 -1,1
733 -OK
734 -)))
735 -|(% style="width:155px" %)(((
736 -AT+SOUND=0,1
737 -)))|(% style="width:124px" %)Turn off the button sound and turn on ACK sound|(% style="width:86px" %)OK
565 + image 5.34 ui_water_leak_style.c (5)
738 738  
739 -(% style="color:#4f81bd" %)**Downlink Command: 0xA1 **
740 740  
741 -Format: Command Code (0xA1) followed by 2 bytes mode value.
568 +Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
742 742  
743 -The first byte after 0XA1 sets the button sound, and the second byte after 0XA1 sets the ACK sound.** (0: off, 1: on)**
570 +[[image:image-20241122161934-51.png]]
744 744  
745 -* **Example: **Downlink Payload: A10001  ~/~/ Set AT+SOUND=0,1  Turn off the button sound and turn on ACK sound.
572 + image 5.35
746 746  
747 -== 3.4  Set buzzer music type(0~~4) ==
748 748  
575 +Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
749 749  
750 -Feature: Set different alarm key response sounds.There are five different types of button music.
577 +[[image:image-20241122162852-53.png||height="330" width="529"]]
751 751  
752 -(% style="color:#4f81bd" %)**AT Command: AT+OPTION**
579 + image 5.37
753 753  
754 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
755 -|(% 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**
756 -|(% style="width:155px" %)(((
757 -AT+OPTION=?
758 -)))|(% style="width:124px" %)(((
759 -Get the buzzer music type
760 -)))|(% style="width:86px" %)(((
761 -3
762 762  
763 -OK
764 -)))
765 -|(% style="width:155px" %)AT+OPTION=1|(% style="width:124px" %)Set the buzzer music to type 1|(% style="width:86px" %)OK
582 +Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
766 766  
767 -(% style="color:#4f81bd" %)**Downlink Command: 0xA3**
584 +panel_with_type union_sensor;
768 768  
769 -Format: Command Code (0xA3) followed by 1 byte mode value.
586 +union_sensor.panel_type = WATER_LEAK_TYPE;
770 770  
771 -* **Example: **Downlink Payload: A300  ~/~/ Set AT+OPTION=0  Set the buzzer music to type 0.
588 +......
772 772  
773 -== 3.5  Set Valid Push Time ==
590 +lv_obj_set_x(union_sensor.panel_union.door.ui_PanelSensorDoor, x_by_index(index));
774 774  
592 +lv_obj_set_y(union_sensor.panel_union.door.ui_PanelSensorDoor, y_by_index(index));
775 775  
776 -Feature: Set the holding time for pressing the alarm button to avoid miscontact. Values range from** 0 ~~1000ms**.
594 +return union_sensor;
777 777  
778 -(% style="color:#4f81bd" %)**AT Command: AT+STIME**
596 +[[image:image-20241122171211-54.png||height="635" width="792"]]
779 779  
780 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
781 -|(% 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**
782 -|(% style="width:155px" %)(((
783 -AT+STIME=?
784 -)))|(% style="width:124px" %)(((
785 -Get the button sound time
786 -)))|(% style="width:86px" %)(((
787 -0
788 -OK
789 -)))
790 -|(% style="width:155px" %)(((
791 -AT+STIME=1000
792 -)))|(% style="width:124px" %)Set the button sound time to 1000**ms**|(% style="width:86px" %)OK
598 + image 5.38
793 793  
794 -(% style="color:#4f81bd" %)**Downlink Command: 0xA2**
795 795  
796 -Format: Command Code (0xA2) followed by 2 bytes mode value.
601 +**13. Modify sort.c file.**
797 797  
798 -* **Example: **Downlink Payload: A203E8  ~/~/ Set AT+STIME=1000  
603 +Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
799 799  
800 -**~ Explain: **Hold the alarm button for 10 seconds before the node will send the alarm packet.
605 +[[image:image-20241122173718-56.png||height="378" width="579"]]
801 801  
607 + image 5.39 sort.c (1)
802 802  
803 -
609 +There are still some changes need to be done in sort.c, and omit here for the moment.
804 804  
611 +
805 805  = 6. FAQ =
806 806  
807 -== 6.1 ==
614 +== 6.1 ==
808 808  
809 809  
810 810  = 7. Order Info =
... ... @@ -811,12 +811,13 @@
811 811  
812 812  == 7.1  Part Number ==
813 813  
621 +
814 814  Part Number: (% style="color:#4472c4" %)LTS5
815 815  
816 -
817 817  
818 818  == 7.2  Packing Info ==
819 819  
627 +
820 820  **Package Includes**:
821 821  
822 822  * LTS5 HMI Touch Screen
... ... @@ -823,20 +823,19 @@
823 823  * 5V,2A DC Power Adapter.
824 824  * USB Type C Program Cable
825 825  
826 -
827 827  = 8. Support =
828 828  
636 +
829 829  * 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.
830 830  * 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]].
831 831  
832 -
833 833  = 9.  Reference material =
834 834  
642 +
835 835  * Datasheet
836 836  * Source Code
837 837  * Mechinical
838 838  
839 -
840 840  = 10. FCC Warning =
841 841  
842 842  
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
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
squalreline-trial.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +60.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