Skip to Content
Last modified by BoYang Xie on 2025/07/24 16:47
From version 4.9
edited by Edwin Chen
on 2024/09/16 09:31
Change comment: There is no comment for this version
To version 132.1
edited by Dilisi S
on 2024/12/25 01:39
Change comment: Dec 24 edits - part 3

Summary

Details

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