Skip to Content
Last modified by BoYang Xie on 2025/07/24 16:47
From version 125.1
edited by Dilisi S
on 2024/12/24 15:25
Change comment: Dec 24 edits - part 1
To version 4.12
edited by Edwin Chen
on 2024/09/16 09:37
Change comment: There is no comment for this version

Summary

Details

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