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

Summary

Details

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