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

Summary

Details

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