Skip to Content
Last modified by BoYang Xie on 2025/07/24 16:47
From version 4.7
edited by Edwin Chen
on 2024/09/16 08:58
Change comment: There is no comment for this version
To version 116.1
edited by Dilisi S
on 2024/12/17 21:42
Change comment: Dec 17 edits - part 1

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