Skip to Content
Last modified by BoYang Xie on 2025/07/24 16:47
From version 4.1
edited by Edwin Chen
on 2024/09/15 23:32
Change comment: There is no comment for this version
To version 165.1
edited by BoYang Xie
on 2025/02/07 19:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.xieby
Content
... ... @@ -1,9 +1,13 @@
1 -
2 -[[image:image-20240915231842-1.png]]
1 +
3 3  
3 +(% style="text-align:center" %)
4 +[[image:image-20241226135550-1.png]]
4 4  
6 +
7 +
8 +
5 5  (% _mstvisible="1" %)
6 -(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents：**
10 +(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:**
7 7  
8 8  {{toc/}}
9 9  
... ... @@ -16,59 +16,77 @@
16 16  
17 17  = 1.  Introduction =
18 18  
19 -== 1.1  What is LTS5 LoRa HMI touch screen ==
23 +== 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.
26 +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 UI.
28 +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  
30 +The LTS5's HMI touch screen supports **drag-and-drop** design, allowing developers to use SquareLine to easily customize the display UI for various applications.
27 27  
32 +The LA66 LoRa module can be programmed to support either private LoRa protocols or the LoRaWAN protocol.
33 +
28 28  == 1.2  Features ==
29 29  
30 30  
37 +* ESP32-WROOM MCU: 8MB RAM & 16MB ROM
38 +* Dragino LA66 LoRa Module
39 +* Support Private LoRa protocol or LoRaWAN protocol
40 +* Support WiFi & BLE wireless protocol
41 +* 5.0" HMI touch screen
42 +* Support LVGL case. SquareLine program.
43 +* Support RS485 Interface
44 +* Open Source Project
31 31  * Wall Attachable.
32 -* LoRaWAN v1.0.3 Class A protocol.
33 -* 1 x push button. Different Color available.
34 -* Built-in Temperature & Humidity sensor
35 -* Built-in speaker
36 -* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915
37 -* AT Commands to change parameters
38 -* Remote configure parameters via LoRaWAN Downlink
39 -* Firmware upgradable via program port
40 -* Support 2 x AAA LR03 batteries.
46 +* 5V DC power
41 41  * IP Rating: IP52
42 42  
43 -== 1.3  Specification ==
49 +== 1.3  Specifications ==
44 44  
45 45  
46 -**Built-in Temperature Sensor:**
52 +**LoRa**:
47 47  
48 -* Resolution: 0.01 °C
49 -* Accuracy Tolerance: Typ ±0.2 °C
50 -* Long Term Drift: < 0.03 °C/yr
51 -* Operating Range: -10 ~~ 50 °C  or -40 ~~ 60 °C (depends on battery type, see [[FAQ>>||anchor="H6.5Whyiseedifferentworkingtemperatureforthedevice3F"]])
54 +* Frequency Range: 870 MHz ~~ 960 MHz
55 +* TCXO crystal to ensure RF performance on low temperature
56 +* Maximum Power +22 dBm constant RF output
57 +* High sensitivity: -148 dBm
58 +* LoRa Tx Current: <90 mA at +17 dBm, 108 mA at +22 dBm
59 +* LoRa Rx current: <9 mA
52 52  
53 -**Built-in Humidity Sensor:**
61 +**WiFi:**
54 54  
55 -* Resolution: 0.01 %RH
56 -* Accuracy Tolerance: Typ ±1.8 %RH
57 -* Long Term Drift: < 0.2% RH/yr
58 -* Operating Range: 0 ~~ 99.0 %RH(no Dew)
63 +* 802.11b/g/n
64 +* Up to 150 Mbps data rate in 802.11n mode
65 +* Support A-MPDU and A-MSDU aggregation
66 +* zero point four μ S protection interval
67 +* Working channel center frequency range: 2412~~2484 MHz
59 59  
60 -== 1.4  Power Consumption ==
69 +**Bluetooth:**
61 61  
71 +* Bluetooth V4.2 BR/EDR and Bluetooth LE standard
72 +* Class-1, Class-2, and Class-3 transmitters.
73 +* AFH
74 +* CVSD and SBC
62 62  
63 -PB01 : Idle: 5uA, Transmit: max 110mA
76 +**Display:**
64 64  
78 +* 5.0 Inch , 800 x 480
79 +* IPS Capacitive Touch SCreen
80 +* RGB color.
81 +* Display Area: 120.7*75.80 mm
65 65  
66 -== 1.5  Storage & Operation Temperature ==
83 +== 1.4  Power Consumption ==
67 67  
68 68  
69 --10 ~~ 50 °C  or -40 ~~ 60 °C (depends on battery type, see [[FAQ>>||anchor="H6.5Whyiseedifferentworkingtemperatureforthedevice3F"]])
86 +* External 5V DC power adapter
70 70  
88 +== 1.5  Storage & Operation Temperature ==
71 71  
90 +
91 +* Operation Temperature: -20 ~~ 70°C  (No Dew)
92 +* Storage Temperature: -30 ~~ 70°C  (No Dew)
93 +
72 72  == 1.6  Applications ==
73 73  
74 74  
... ... @@ -79,1036 +79,698 @@
79 79  * Smart Cities
80 80  * Smart Factory
81 81  
82 -= 2.  Operation Mode =
104 += 2.  Getting Started with 'Hello World' =
83 83  
84 -== 2.1  How it work? ==
106 +== 2.1  About this demo ==
85 85  
86 86  
87 -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**.
109 +This getting started example demonstrates how to design and deploy a simple display UI for the LTS5 device. The example includes:
88 88  
111 +* Creating a basic UI with a single button.
112 +* Implementing functionality to navigate the Web UI to a new page when the button is clicked.
113 +* Uploading the UI to the LTS5 device.
89 89  
90 -== 2.2  How to Activate PB01? ==
115 +By completing this demo, you will gain foundational knowledge for customizing the LTS5 interface and building more advanced IoT applications.
91 91  
92 92  
93 -(% style="color:red" %)** 1.  Open enclosure from below position.**
118 +== 2.2  Install Software Running Environment ==
94 94  
95 -[[image:image-20220621093835-1.png]]
96 96  
121 +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.
97 97  
98 -(% style="color:red" %)** 2.  Insert 2 x AAA LR03 batteries and the node is activated.**
99 99  
100 -[[image:image-20220621093835-2.png]]
124 +=== 2.2.1 Install VS Code and ESP-IDF extension ===
101 101  
102 102  
103 -(% style="color:red" %)** 3. Under the above conditions, users can also reactivate the node by long pressing the ACT button.**
127 +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]].
104 104  
105 -[[image:image-20220621093835-3.png]]
129 +Next, install the **ESP-IDF** extension within **VS Code**. Detailed steps for this process are shown in Image 1.
106 106  
107 107  
108 -User can check [[LED Status>>||anchor="H2.8LEDIndicator"]] to know the working state of PB01.
132 +[[image:image-20240928110211-5.png||height="508" width="866"]]
109 109  
134 + Image 1: ESP-IDF extension install
110 110  
111 -== 2.3  Example to join LoRaWAN network ==
136 +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]]
112 112  
113 113  
114 -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.
139 +=== 2.2.2 Install SquareLine Studio ===
115 115  
116 -(% _mstvisible="1" class="wikigeneratedid" %)
117 -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. 
118 118  
119 -[[image:image-20240705094824-4.png]]
142 +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.
120 120  
121 -(% style="color:blue" %)**Step 1**(%%):  Create a device in TTN V3 with the OTAA keys from PB01.
144 +[[image:squareline.io_downloads.png||height="888" width="1294"]]
122 122  
123 -Each PB01 is shipped with a sticker with the default DEV EUI as below:
124 124  
125 -[[image:image-20230426083617-1.png||height="294" width="633"]]
147 +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:
126 126  
149 +* Max. 10 screens
150 +* Max. 150 widgets
151 +* Max. 5 global colors
152 +* Max. 2 themes
153 +* Max. 1 component
127 127  
128 -Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
155 +== 2.3 Simple usage of SquareLine Studio and exporting UI code ==
129 129  
130 -Create application.
131 131  
132 -choose to create the device manually.
158 +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**.
133 133  
134 -Add JoinEUI(AppEUI), DevEUI, AppKey.(% style="display:none" %)
160 +* In the **PROJECT SETTINGS**, select **LVGL version **as **8.3.11** and **Resolution** as **800** x **480**.
161 +* Select the **CREATE **button to create the new project with the selected settings.
135 135  
136 -[[image:image-20240507142116-1.png||height="410" width="1138"]](% style="display:none" %) (%%)
137 -
163 +[[image:squareline-studio-launcher-screen.png||height="752" width="1415"]]
138 138  
139 -[[image:image-20240507142157-2.png||height="559" width="1147"]]
140 140  
141 -[[image:image-20240507142401-3.png||height="693" width="1202"]]
166 +Next, you need to configure some additional settings for this project. To do so, select** File  -> Project Settings** as shown in the image below.
142 142  
143 -[[image:image-20240507142651-4.png||height="760" width="1190"]]
168 +[[image:1727229582471-566.png]]
144 144  
145 -**Default mode OTAA**(% style="display:none" %)
146 146  
171 +In the **PROJECT SETTINGS** dialog box, configure/modify the project settings as shown in the image below.
147 147  
148 -(% 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.
173 +* **UI Files Export Root**: Select a folder on your computer to store the UI files.
174 +* **LVGL Include Path**: Set this to **lvgl.h**
175 +* Click on the **APPLY CHANGES** button.
149 149  
150 -[[image:image-20240507143104-5.png||height="434" width="1398"]]
177 +[[image:image-20240928105309-4.png||height="526" width="556"]]
151 151  
152 152  
153 -== 2.4  Uplink Payload ==
180 +Now you can start building the user interface. Follow the steps below:
154 154  
155 155  
156 -Uplink payloads include two types: Valid Sensor Value and other status / control command.
183 +=== **Add widgets** ===
157 157  
158 -* Valid Sensor Value: Use FPORT=2
159 -* Other control command: Use FPORT other than 2.
160 160  
161 -=== 2.4.1  Uplink FPORT~=5, Device Status ===
186 +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.
162 162  
188 +[[image:image-20240928111412-6.png||height="526" width="864"]]
163 163  
164 -Users can  get the Device Status uplink through the downlink command:
165 165  
166 -(% style="color:#4472c4" %)**Downlink:  **(%%)**0x2601**
191 +Then click the **Screen **widget to add the second screen. After adding the second screen, it will appear in the Screens panel as **Screen2**.
167 167  
168 -Uplink the device configures with FPORT=5.
193 +[[image:Screenshot 2024-12-24 140459.png||height="278" width="290"]]
169 169  
170 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:370px" %)
171 -|=(% 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**
172 -|(% 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
195 +=== **Modify widget properties** ===
173 173  
174 -[[image:image-20240507152130-12.png||height="469" width="1366"]](% style="display:none" %)
175 175  
176 -Example Payload (FPort=5):  [[image:image-20240507152254-13.png||height="26" width="130"]]
198 +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.
177 177  
200 +[[image:1727485118799-984.png]]
178 178  
179 -(% style="color:#4472c4" %)**Sensor Model**(%%): For PB01, this value is 0x35.
180 180  
181 -(% style="color:#4472c4" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version.
203 +==== **Changing the Button properties** ====
182 182  
183 -(% style="color:#4472c4" %)**Frequency Band**:
184 184  
185 -*0x01: EU868
206 +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:
186 186  
187 -*0x02: US915
208 +* **Flex Flow**: No Layout
209 +* **Transform**:
210 +** **X**: 331 px
211 +** **Y**: 203 px
212 +** **Width**: 100 px
213 +** **Height**: 50 px
214 +** **Align**: CENTER
188 188  
189 -*0x03: IN865
216 +[[image:1727485251053-655.png]]
190 190  
191 -*0x04: AU915
192 192  
193 -*0x05: KZ865
219 +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.
194 194  
195 -*0x06: RU864
221 +* Click **ADD EVENT** button. A new section will appear to configure this event.
196 196  
197 -*0x07: AS923
223 +[[image:Screenshot 2024-12-24 134937.png||height="80" width="290"]]
198 198  
199 -*0x08: AS923-1
225 +* 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.
200 200  
201 -*0x09: AS923-2
227 +[[image:Screenshot 2024-12-24 134818.png||height="222" width="290"]]
202 202  
203 -*0x0a: AS923-3
229 +* 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.
230 +* Finally, click the **ADD** button.
204 204  
232 +[[image:1727485480434-713.png||height="395" width="290"]]
205 205  
206 -(% style="color:#4472c4" %)**Sub-Band**(%%): value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
234 + Image 8: Add an event for the button
207 207  
208 -(% style="color:#4472c4" %)**BAT**(%%): shows the battery voltage for PB01.
209 209  
210 -(% style="color:#4472c4" %)**Ex1**(%%): 0x0C DE = 3294mV
237 +==== **Changing the label properties** ====
211 211  
212 212  
213 -=== 2.4.2  Uplink FPORT~=2, Real time sensor value ===
240 +Click the Label you have added to the screen. Under the **Label** section, type "**Click for Detail**" in the **Text** textbox.
214 214  
242 +[[image:image-20240928090825-1.png||height="327" width="391"]]
215 215  
216 -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"]].
217 217  
218 -Uplink uses FPORT=2 and every 20 minutes send one uplink by default.
245 +Once you enter the text, it will immediately appear on the label.
219 219  
220 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:460px" %)
221 -|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
222 -**Size(bytes)**
223 -)))|=(% style="width: 60px;background-color:#4F81BD;color:white" %)2|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
224 -**1**
225 -)))|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
226 -**1**
227 -)))|=(% style="width: 90px;background-color:#4F81BD;color:white" %)(((
228 -**2**
229 -)))|=(% style="width: 40px;background-color:#4F81BD;color:white" %)(((
230 -**2**
231 -)))
232 -|(% style="width:97px" %)(((
233 -Value
234 -)))|(% style="width:39px" %)Battery|(% style="width:39px" %)(((
235 -Sound_ACK
236 236  
237 -&Sound_key
238 -)))|(% style="width:100px" %)(((
239 -(((
240 -Alarm
241 -)))
242 -)))|(% style="width:77px" %)(((
243 -(((
244 -Temperature
245 -)))
246 -)))|(% style="width:47px" %)(((
247 -Humidity
248 -)))
248 +==== **Changing image properties** ====
249 249  
250 -Example in TTN.
251 251  
252 -[[image:image-20240507150155-11.png||height="549" width="1261"]]
251 +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.
253 253  
254 -Example Payload (FPort=2):  (% style="background-color:yellow" %)**0C EA 03 01 01 11 02 A8**
253 +One way is to move your image into the folder "…/squareline project/assets/", as shown in the image below.
255 255  
256 -==== (% style="color:blue" %)**Battery:**(%%) ====
255 +[[image:image-20240928113424-9.png||height="355" width="505"]]
257 257  
258 -Check the battery voltage.
259 259  
260 -* Ex1: 0x0CEA = 3306mV
261 -* Ex2: 0x0D08 = 3336mV
258 +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.
262 262  
263 -==== (% style="color:blue" %)**Sound_ACK & Sound_key:**(%%) ====
260 +[[image:image-20240928114139-10.png||height="559" width="810"]]
264 264  
265 -Key sound and ACK sound are enabled by default.
266 266  
267 -* Example1: 0x03
263 +==== **The relationship between widgets** ====
268 268  
269 - Sound_ACK: (03>>1) & 0x01=1, OPEN.
270 270  
271 -**~ ** Sound_key:  03 & 0x01=1, OPEN.
266 +Widgets commonly have two types of relationships: **parallel** and **parent-child**.
272 272  
273 -* Example2: 0x01
268 +* In a **parallel relationship**, widgets' positions are determined relative to a shared reference object.
269 +* In a **parent-child relationship**, any part of the child object outside the parent's boundaries is hidden by default. To make the child object fully visible, you must adjust its position to fit within the parent's range.
274 274  
275 - Sound_ACK: (01>>1) & 0x01=0, CLOSE.
271 +[[image:1727486567182-334.png||height="318" width="278"]]
276 276  
277 -**~ ** Sound_key:  01 & 0x01=1, OPEN.
278 278  
274 +Move the label, **Label1** to make it a child of **Button1** as shown in the image below.
279 279  
280 -==== (% style="color:blue" %)**Alarm:**(%%) ====
276 +[[image:image-20240928112001-8.png||height="431" width="796"]]
281 281  
282 -Key alarm.
283 283  
284 -* Ex1: 0x01 & 0x01=1, TRUE.
285 -* Ex2: 0x00 & 0x01=0, FALSE.
279 +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.
286 286  
287 -==== (% style="color:blue" %)**Temperature:**(%%) ====
281 +[[image:Screenshot 2024-12-24 144005.png||height="360" width="290"]]
288 288  
289 -* Example1:  0x0111/10=27.3℃
290 -* Example2:  (0xFF0D-65536)/10=-24.3℃
291 291  
292 -If payload is: FF0D :  (FF0D & 8000 == 1) , temp = (FF0D - 65536)/100 =-24.3℃
284 +==== **Preview the screen** ====
293 293  
294 -（FF0D & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative）
295 295  
287 +You can test the result by clicking on the **PLAY** button as shown in the image below. The screen will change into play mode.
296 296  
297 -==== (% style="color:blue" %)**Humidity:**(%%) ====
289 +[[image:1727487368023-281.png]]
298 298  
299 -* Humidity:    0x02A8/10=68.0%
300 300  
301 -=== 2.4.3  Uplink FPORT~=3, Datalog sensor value ===
292 +For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
302 302  
303 303  
304 -PB01 stores sensor value and user can retrieve these history value via downlink command. The Datalog sensor value are sent via FPORT=3.
295 +== 2.4 Integrate UI Code to ESP-IDF Project ==
305 305  
306 -[[image:image-20240510144912-1.png||height="471" width="1178"]](% style="display:none" %)
307 307  
298 +To integrate, first export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
308 308  
309 -* 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" %)
300 +On the  menubar, click **Export -> Export UI** Files as shown in the image below.
310 310  
311 -For example, in US915 band, the max payload for different DR is:
302 +[[image:1727229798126-306.png]]
312 312  
313 -1. **DR0**: max is 11 bytes so one entry of data
314 -1. **DR1**: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
315 -1. **DR2**: total payload includes 11 entries of data
316 -1. **DR3**: total payload includes 22 entries of data.
317 317  
318 -(% 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.**
305 +The exported UI files can be found in your SquareLine project folder as shown in the image below.
319 319  
320 -See more info about the [[Datalog feature>>||anchor="H2.6A0DatalogFeature"]].
321 321  
322 -(% style="display:none" %) (%%)
308 +[[image:1727229821582-258.png||height="333" width="662"]]
323 323  
324 -=== 2.4.4  Decoder in TTN V3 ===
325 325  
311 +Create a new folder named "**ui**" at path "**basic_prj/app_components/ui/**", and copy all the exported UI code into it as shown in the image below.
326 326  
327 -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.
313 +[[image:image-20240928144830-11.png]]
328 328  
329 -In TTN , add formatter as below:
330 330  
331 -[[image:image-20240507162814-16.png||height="778" width="1135"]]
316 +Open the **CMakeLists.txt** file and edit it as ahown below.
332 332  
333 -(((
334 -Please check the decoder from this link:  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]
335 -)))
318 +[[image:1727229892636-154.png||height="521" width="407"]]
336 336  
337 -(((
338 -
339 -)))
340 340  
341 -== 2.5 Show data on Datacake ==
321 +Open the main.c file and  add two lines of code as shown in the below images.
342 342  
323 +Add **#include "ui.h"**
343 343  
344 -(((
345 -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:
346 -)))
325 +[[image:1727229926561-300.png]]
347 347  
348 -(((
349 -
350 -)))
351 351  
352 -(((
353 -(% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the LoRaWAN network.
354 -)))
328 +Add **ui_init();**
355 355  
356 -(((
357 -(% 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.
358 -)))
330 +[[image:1727229955611-607.png]]
359 359  
360 -(((
361 -~1. Add Datacake:
362 -)))
363 363  
364 -(((
365 -2. Select default key as Access Key:
366 -)))
333 +== 2.5 Brief introduction to the Hello World project ==
367 367  
368 -(((
369 -3. In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add PB01:
370 -)))
371 371  
372 -(((
373 - Please refer to the figure below.
374 -)))
336 +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 provides information about the HMI screen product through an image and includes a button to return to the previous screen.
375 375  
376 -[[image:image-20240510150924-2.png||height="612" width="1186"]]
377 377  
339 +== 2.6 Test Result ==
378 378  
379 -Log in to DATACAKE, copy the API under the account.
380 380  
381 -[[image:image-20240510151944-3.png||height="581" width="1191"]]
342 +By pressing the button located at the bottom right, the screen switches to the next one as expected. This confirms that the UI file has been successfully integrated into the project and is functioning correctly.
382 382  
344 +Screen 1:
383 383  
346 +[[image:1727488067077-684.png||height="402" width="574"]]
384 384  
385 -[[image:image-20240510152150-4.png||height="697" width="1188"]]
386 386  
349 +Screen 2:
387 387  
388 -[[image:image-20240510152300-5.png||height="298" width="1191"]]
351 +[[image:1727488157579-949.png||height="397" width="572"]]
389 389  
390 390  
391 -[[image:image-20240510152355-6.png||height="782" width="1193"]]
354 += 3. Example Project 1: LoRa Central Display =
392 392  
393 -[[image:image-20240510152542-8.png||height="545" width="739"]]
356 +[[image:image-20240916101737-1.png||height="468" width="683"]]
394 394  
395 -[[image:image-20240510152634-9.png||height="748" width="740"]]
396 396  
359 += 4. Example Project 2: LoRaWAN RS485 Alarm =
397 397  
398 -[[image:image-20240510152809-10.png||height="607" width="732"]]
361 += 5. Example Project 3: P2P =
399 399  
400 -[[image:image-20240510153934-14.png||height="460" width="1199"]]
363 +The project achieves the function of receiving LoRa P2P messages and displaying them on the screen. The workflow is as follows: A LA66, running a P2P program, sends a message in a particular format via an AT command. Then, the LTS5 receives the message and displays it on the screen.
401 401  
365 +The project can be found at [[this link>>url:https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/P2P]].
402 402  
403 -[[image:image-20240510153435-12.png||height="428" width="1197"]]
367 +== 5.1 firmware flashing approach. ==
404 404  
369 +5.1.1 Download this project
405 405  
406 -Copy and paste the [[TTN decoder>>https://github.com/dragino/dragino-end-node-decoder]] here and save.
371 +5.1.2 Download esp32 firmware flash tool in [[this link>>https://docs.espressif.com/projects/esp-test-tools/en/latest/esp32/production_stage/tools/flash_download_tool.html]].
407 407  
408 -[[image:image-20240510153624-13.png||height="468" width="1195"]]
373 +5.1.3 Download la66 firmware flash tool in [[this link>>https://www.dropbox.com/scl/fo/9kqeqf6wmet10o9hgxuwa/h?rlkey=4ikrg6kg5v0yjxwhp0i37wrv7&e=1&dl=0]].
409 409  
375 +5.1.4 Upload firmware to esp32
410 410  
411 -Visual widgets please read the DATACAKE documentation.
377 +Open flash_download_tool.exe, and then follow the steps below.
412 412  
413 -(% style="display:none" %) (%%)
379 +[[image:1738893226894-758.png||height="170" width="176"]]
414 414  
415 -== 2.6  Datalog Feature ==
381 +[[image:image-20250207100150-7.png||height="476" width="538"]]
416 416  
383 +5.1.5 Upload firmware to la66
417 417  
418 -(% _msthash="315262" _msttexthash="32283004" _mstvisible="1" %)
419 -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.
385 +Open Dragino_Sensor_Manager_Utility.exe, and then follow the steps below.
420 420  
387 +[[image:image-20250207101415-8.png||height="522" width="618"]]
421 421  
422 -=== 2.6.1  Unix TimeStamp ===
389 +[[image:image-20250207101515-9.png||height="522" width="618"]]
423 423  
391 +== 5.2 AT command and P2P data format ==
424 424  
425 -Unix TimeStamp shows the sampling time of uplink payload. format base on
393 +AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**01**A4CBBB0A8E085C02,0,3
426 426  
427 -[[image:image-20220523001219-11.png||_mstalt="450450" _mstvisible="3" height="97" width="627"]]
395 +AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**02**A4CB00,0,3
428 428  
429 -User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/||_mstvisible="3"]] :
397 +AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**03**A4CB00,0,3
430 430  
431 -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)
399 +AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**04**A4CB00,0,3
432 432  
401 +AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**05**A4CB00,0,3
433 433  
434 -[[image:1655782409139-256.png]]
403 +AT+SEND=1,014b69746368656e2d467269676531FFFFA84041000181D4A8**06**A4CB00,0,3
435 435  
405 +**Data format**:
436 436  
437 -=== 2.6.2  Poll sensor value ===
407 +~1. AT+SEND=1,**01** **4b69746368656e2d467269676531FFFF A84041000181D4A8 01  A4CB  BB0A  8E08  5C02**,0,3
438 438  
409 +**01:** encrypt. 1 Byte. 01 ~-~-> no encryption. This 1-byte information is now invalid; simply write 0x01 instead.
439 439  
440 -(((
441 -User can poll sensor value based on timestamps from the server. Below is the downlink command.
442 -)))
411 +**4b69746368656e2d467269676531FFFF: **Device Name. 16 Bytes. The Device Name for this piece of information is "Kitchen-Frige1," and the subsequent "FFFF" is intended to pad it up to 16 Bytes. The Device Name for this piece of information is 'Kitchen-Frige1,' and the subsequent 'FFFF' is intended to pad it up to 16 Bytes, but it is not necessary as the system can handle shorter names as well.
443 443  
444 -(((
445 -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.
446 -)))
413 +**A84041000181D4A8:** Device EUI. 8 Bytes. The last three Bytes will be extracted by the ESP32-S3 and displayed on the screen.
447 447  
448 -(((
449 -For example, downlink command [[image:image-20220621113526-13.png]] (% _mstvisible="3" style="display:none" %)
450 -)))
415 +**01: **Panel Type. 1 Byte. 0x01~-~->Tem & Hum,
451 451  
452 -(((
453 -Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00's data
454 -)))
417 + 0x02~-~->Door,
455 455  
456 -(((
457 -Uplink Internal =5s，means PB01 will send one packet every 5s. range 5~~255s.
458 -)))
419 + 0x03~-~->Water Leak,
459 459  
421 + 0x04~-~->Occupied,
460 460  
461 -=== 2.6.3  Datalog Uplink payload ===
423 + 0x05~-~->Button,
462 462  
425 + 0x06~-~->Alarm,
463 463  
464 -See [[Uplink FPORT=3, Datalog sensor value>>||anchor="H2.4.3A0UplinkFPORT3D32CDatalogsensorvalue"]]
427 +**A4CB: **Battery level//. //2 Bytes. Battery Voltage =0xCBA4&0x3FFF=0x0BA4=2980mV
465 465  
466 -(% style="display:none" %) (%%) (% style="display:none" %)
429 +**BB0A: **The temperature of the built-in sensor in LHT65N.// //2 Bytes. Temperature:  0x0ABB/100=27.47℃
467 467  
468 -== 2.7 Button ==
431 +**8E08: **The temperature of the External temperature sensor.// //2 Bytes. Temperature:  0x088E/100=21.90℃
469 469  
433 +**5C02：**The humidity of the built-in sensor in LHT65N. 2 Bytes. Humidity: 0x025C/10=60.4%
470 470  
471 -* ACT button
435 +2. AT+SEND=1,**01**  **4b69746368656e2d467269676531FFFF**  **A84041000181D4A8**  **02  A4CB  00**,0,3
472 472  
473 -Long press this button PB01 will reset and join network again.
437 +Specific sections of the data share the same function.
474 474  
475 -[[image:image-20240510161626-17.png||height="192" width="224"]]
439 +**00: Status. **1 Byte//. //If Panel Type is 0x02, **Status: 00~-~->Open; 01~-~->Close.**
476 476  
477 -* Alarm button
441 + If Panel Type is 0x03, **Status: 00~-~->Normal; 01~-~->Water Leaking.**
478 478  
479 -Press the button PB01 will immediately uplink data, and alarm is "TRUE".
443 + If Panel Type is 0x04, **Status: 00~-~->Free; 01~-~->Occupied.**
480 480  
481 -[[image:image-20240705095149-5.png||height="164" width="162"]](% style="display:none" %)
445 + If Panel Type is 0x05, **Status: 00~-~->OFF; 01~-~->ON.**
482 482  
447 + If Panel Type is 0x06, **Status: 00~-~->OFF; 01~-~->Alarm.**
483 483  
484 -== 2.8 LED Indicator ==
449 +== 5.3 Usage ==
485 485  
451 +After burning the firmware into LTS5, you can use an LA66 equipped with peer-to-peer firmware to send data to LTS5 via AT commands.
486 486  
487 -(((
488 -The PB01 has a triple color LED which for easy showing different stage.
489 -)))
453 +5.3.1 Connect LA66 to the computer, open Serial Port Utility, and send the AT+CFG instruction to check whether the LA66 has downloaded correct program.
490 490  
491 -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
455 +[[image:image-20250207143131-11.png||height="527" width="547"]]
492 492  
493 -(((
494 -(% style="color:#037691" %)**In a normal working state**:
495 -)))
457 +5.3.2 Copy an AT instruction example, click "Send" button, then the led in LA66 will flash and the LTS5 will display the LoRa information.
496 496  
497 -* 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" %)**.**
498 -* During OTAA Join:
499 -** **For each Join Request uplink:** the (% style="color:green" %)**GREEN LED** (%%)will blink once.
500 -** **Once Join Successful:** the (% style="color:green" %)**GREEN LED**(%%) will be solid on for 5 seconds.
501 -* After joined, for each uplink, the (% style="color:blue" %)**BLUE LED**(%%) or (% style="color:green" %)**GREEN LED** (%%)will blink once.
502 -* 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.
459 +[[image:image-20250207144605-12.png||height="634" width="548"]]
503 503  
504 -(((
505 -
506 -)))
461 += 6. Example Project 4: LoRaWAN_CLASS_C =
507 507  
508 -== 2.9 Buzzer ==
509 509  
464 +The project achieves the function of receiving LoRaWAN Class C messages and displaying them on the screen. Note: The Things Network (TTN) needs to enable Class C support, and the LA66 within the LTS5 needs to operate in Class C mode.
510 510  
511 -The PB01 has** button sound** and** ACK sound** and users can turn on or off both sounds by using [[AT+SOUND>>||anchor="H3.3A0Setbuttonsoundandbuttonalarm"]].
466 +The downlink workflow proceeds as follows: The Things Network (TTN) sends a message in a specific format via downlink. Then, a LoRaWAN gateway relays this message to the LTS5. Finally, the LTS5 receives the message and displays it on its screen.
512 512  
513 -* (% style="color:#4f81bd" %)**Button sound**(%%)** **is the music produced by the node after the alarm button is pressed.
468 +The uplink workflow is as follows: The LA66 within the LTS5 sends a LoRaWAN message, for some reason, to a LoRaWAN gateway, which then forwards it to The Things Network (TTN).
514 514  
515 - Users can use[[ AT+OPTION>>||anchor="H3.4A0Setbuzzermusic2807E429"]] to set different button sounds.
470 +The project can be found at [[this link>>https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main/Example/LoRaWAN_CLASS_C]].
516 516  
517 -* (% style="color:#4f81bd" %)**ACK sound **(%%)is the notification tone that the node receives ACK.
472 +== 6.1 firmware flashing approach ==
518 518  
519 -= 3.  Configure PB01 via AT command or LoRaWAN downlink =
474 +The firmware flashing approach is the same as described in section [[5.1>>5.1]].
520 520  
476 +== 6.2 flowchart ==
521 521  
522 -Users can configure PB01 via AT Command or LoRaWAN Downlink.
478 +[[image:image-20250207164320-13.png||height="696" width="1344"]]
523 523  
524 -* AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
480 +== 6.3 Usage ==
525 525  
526 -* LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
482 +6.3.1 TTN downlink panel data to display in LTS5
527 527  
528 -There are two kinds of commands to configure PB01, they are:
484 +6.3.1 Connect LA66 to the computer, open Serial Port Utility, and send the AT+CFG instruction to check whether the LA66 has downloaded correct program.
529 529  
530 -* (% style="color:#4f81bd" %)**General Commands:**
486 +[[image:image-20250207165702-14.png||height="830" width="563"]]
531 531  
532 -These commands are to configure:
488 +6.3.2 Switch to Class C using "AT+CLASS=C", and check the class with "AT+CLASS=?".
533 533  
534 -* General system settings like: uplink interval.
490 +[[image:image-20250207173212-27.png]]
535 535  
536 -* LoRaWAN protocol & radio-related commands.
492 +[[image:image-20250207172246-20.png]]
537 537  
538 -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]]
494 +6.3.3 Verify LA66's join status (in LTS5) with "AT+NJS=?". If not joined, connect manually to LoRaWAN with "AT+JOIN".
539 539  
496 +[[image:image-20250207172010-19.png]]
540 540  
541 -* (% style="color:#4f81bd" %)**Commands special design for PB01**
498 +[[image:image-20250207171650-17.png]]
542 542  
543 -These commands are only valid for PB01, as below:
500 +6.3.4 After joining, send a message to TTN, such as "AT+SENDB=01,02,8,05820802581ea0a5", to activate communication.
544 544  
545 -(% style="display:none" %) (%%)
502 +[[image:image-20250207192107-28.png]]
546 546  
547 -== 3.1  Downlink Command Set ==
504 +6.3.5 TTN distributes panel data in three batches.
548 548  
506 +1. downlink DEUI F1A84041000181D4A8
507 +1. downlink Dev Name F24B69746368656E2D467269676531FFFF
508 +1. downlink Sensor Data 5501A4CBBB0A8E085C02 或 5504A4CB01
549 549  
550 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %)
551 -|=(% 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**
552 -|(% style="width:130px" %)AT+TDC=?|(% style="width:151px" %)(((
553 -
510 += 5. The method for adding a new type of panel to the project =
554 554  
555 -View current TDC time
556 -)))|(% style="width:92px" %)(((
557 -1200000
558 -OK
559 -)))|(% style="width:206px" %)Default 1200000(ms)
560 -|(% style="width:130px" %)AT+TDC=300000|(% style="width:151px" %)Set TDC time|(% style="width:92px" %)OK|(% style="width:206px" %)(((
561 -(((
562 -0X0100012C:
563 -01: fixed command
564 -00012C: 0X00012C=
512 +If you don't have this need, then this part of the content can be ignored.
565 565  
566 -300(seconds)
567 -)))
514 +1. Design a panel in SquareLine Studio, as shown in Image 5.1 below for reference.
568 568  
569 -(((
570 -
571 -)))
572 -)))
573 -|(% style="width:130px" %)ATZ|(% style="width:151px" %)Reset node|(% style="width:92px" %) |(% style="width:206px" %)0x04FF
574 -|(% style="width:130px" %)AT+FDR|(% style="width:151px" %)Restore factory settings|(% style="width:92px" %) |(% style="width:206px" %)0X04FE
575 -|(% style="width:130px" %)AT+CFM=?|(% style="width:151px" %)View the current confirmation mode status|(% style="width:92px" %)(((
576 -0,7,0
516 +[[image:image-20241121113445-1.png||height="584" width="934"]]
577 577  
578 -OK
579 -)))|(% style="width:206px" %)Default 0,7,0
580 -|(% style="width:130px" %)AT+CFM=1,7,1|(% style="width:151px" %)(((
581 -Confirmed uplink mode, the maximum number of retries is seven, and uplink fcnt increase by 1 for each retry
582 -)))|(% style="width:92px" %)(((
583 -OK
584 -)))|(% style="width:206px" %)(((
585 -05010701
518 + Image 5.1: a panel about water_leak
586 586  
587 -05: fixed command
588 588  
589 -01:confirmed uplink
521 +2. **Export the UI file: **You need to adjust the export path first, then click '**Export -> Export UI Files**' on the menu bar. This step was introduced earlier. After that, you can get the UI files as shown in Image 5.2.
590 590  
591 -07: retry 7 times
523 +[[image:image-20241121141120-4.png||height="383" width="795"]]
592 592  
593 -01: fcnt count plus 1
594 -)))
595 -|(% style="width:130px" %)AT+NJM=?|(% style="width:151px" %)(((
596 -Check the current network connection method
597 -)))|(% style="width:92px" %)(((
598 -1
599 -OK
600 -)))|(% style="width:206px" %)Default 1
601 -|(% style="width:130px" %)AT+NJM=0|(% style="width:151px" %)Change the network connection method to ABP|(% style="width:92px" %)(((
602 -Attention:Take effect after ATZ
603 -OK
604 -)))|(% style="width:206px" %)(((
605 -0X2000: ABP
606 -0x2001: OTAA
607 -20: fixed command
608 -)))
609 -|(% style="width:130px" %)AT+RPL=?|(% style="width:151px" %)View current RPL settings|(% style="width:92px" %)(((
610 -0
611 -OK
612 -)))|(% style="width:206px" %)Default 0
613 -|(% style="width:130px" %)AT+RPL=1|(% style="width:151px" %)set RPL=1    |(% style="width:92px" %)OK|(% style="width:206px" %)(((
614 -0x2101:
615 -21: fixed command
616 -01: for details, check wiki
617 -)))
618 -|(% style="width:130px" %)AT+ADR=?|(% style="width:151px" %)View current ADR status|(% style="width:92px" %)(((
619 -1
620 -OK
621 -)))|(% style="width:206px" %)Default 0
622 -|(% style="width:130px" %)AT+ADR=0|(% style="width:151px" %)Set the ADR state to off|(% style="width:92px" %)OK|(% style="width:206px" %)(((
623 -0x2200: close
624 -0x2201: open
625 -22: fixed command
626 -)))
627 -|(% style="width:130px" %)AT+DR=?|(% style="width:151px" %)View the current DR settings|(% style="width:92px" %)OK|(% style="width:206px" %)
628 -|(% style="width:130px" %)AT+DR=1|(% style="width:151px" %)(((
629 -set DR to 1
630 -It takes effect only when ADR=0
631 -)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
632 -0X22000101:
633 -00: ADR=0
634 -01: DR=1
635 -01: TXP=1
636 -22: fixed command
637 -)))
638 -|(% style="width:130px" %)AT+TXP=?|(% style="width:151px" %)View the current TXP|(% style="width:92px" %)OK|(% style="width:206px" %)
639 -|(% style="width:130px" %)AT+TXP=1|(% style="width:151px" %)(((
640 -set TXP to 1
641 -It takes effect only when ADR=0
642 -)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
643 -0X22000101:
644 -00: ADR=0
645 -01: DR=1
646 -01: TXP=1
647 -22: fixed command
648 -)))
649 -|(% style="width:130px" %)AT+RJTDC=10|(% style="width:151px" %)Set RJTDC time interval|(% style="width:92px" %)OK|(% style="width:206px" %)(((
650 -0X26000A:
651 -26: fixed command
652 -000A: 0X000A=10(min)
653 -for details, check wiki
654 -)))
655 -|(% style="width:130px" %) |(% style="width:151px" %)(((
656 -(((
657 -~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_
525 + Image 5.2: Exported UI files
658 658  
659 -Retrieve stored data for a specified period of time
660 -)))
661 661  
662 -(((
663 -
664 -)))
665 -)))|(% style="width:92px" %) |(% style="width:206px" %)(((
666 -0X3161DE7C7061DE8A800A:
667 -31: fixed command
668 -61DE7C70:0X61DE7C70=2022/1/12 15:00:00
669 -61DE8A80:0X61DE8A80=2022/1/12 16:00:00
670 -0A: 0X0A=10(second)
671 -View details 2.6.2
672 -)))
673 -|(% style="width:130px" %)AT+DDETECT=?|(% style="width:151px" %)View the current DDETECT setting status and time|(% style="width:92px" %)(((
674 -1,1440,2880
675 -OK
676 -)))|(% style="width:206px" %)Default 1,1440,2880(min)
677 -|(% style="width:130px" %)AT+DDETECT=(((
678 -1,1440,2880
679 -)))|(% style="width:151px" %)(((
680 -Set DDETECT setting status and time
681 -((% style="color:red" %)When the node does not receive the downlink packet within the set time, it will re-enter the network(%%))
682 -)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
683 -0X320005A0: close
684 -0X320105A0: open
685 -32: fixed command
686 -05A0: 0X05A0=1440(min)
687 -)))
528 +3. **Delete and rename some file.** Here are the steps:
688 688  
689 -== 3.2  Set Password ==
530 + Step 1: Delete the 'components' directory.
531 + Step 2: Delete 'filelist.txt'.
532 + Step 3: Delete 'ui_helpers.c' and 'ui_helpers.h'.
533 + Step 4: Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
534 + Step 5: Rename the 'screens' directory to 'styles'.
690 690  
536 +[[image:image-20241121151934-10.png||height="303" width="792"]]
691 691  
692 -Feature: Set device password, max 9 digits.
538 + image 5.3 rest file (1)
693 693  
694 -(% style="color:#4f81bd" %)**AT Command: AT+PWORD**
540 +[[image:image-20241121142925-7.png||height="141" width="793"]]
695 695  
696 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
697 -|(% 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**
698 -|(% style="width:155px" %)AT+PWORD=?|(% style="width:124px" %)Show password|(% style="width:86px" %)(((
699 -123456
700 -OK
701 -)))
702 -|(% style="width:155px" %)AT+PWORD=999999|(% style="width:124px" %)Set password|(% style="width:86px" %)OK
542 + image 5.4 rest file (2)
703 703  
704 -(% style="color:#4f81bd" %)**Downlink Command:**
544 +4. Open the project in **VS Code**.
705 705  
706 -No downlink command for this feature.
546 +5. Add the file include path for **water_leak** in **extra_lib/CMakeLists.txt**, as shown in Images 5.5 and 5.6. Its format is similar to that of **tem_hum** or **door**."
707 707  
548 +[[image:image-20241121181957-17.png||height="438" width="516"]]
708 708  
709 -== 3.3  Set button sound and ACK sound ==
550 + image 5.5 extra_lib/CMakeLists.txt before add
710 710  
552 +[[image:image-20241121182239-18.png||height="520" width="518"]]
711 711  
712 -Feature: Turn on/off button sound and ACK alarm.
554 + image 5.6 extra_lib/CMakeLists.txt after add
713 713  
714 -(% style="color:#4f81bd" %)**AT Command: AT+SOUND**
556 +6.  **Modify the header files included in the fonts and images directories**.
715 715  
716 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
717 -|(% 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**
718 -|(% style="width:155px" %)(((
719 -AT+SOUND=?
720 -)))|(% style="width:124px" %)Get the current status of button sound and ACK sound|(% style="width:86px" %)(((
721 -1,1
722 -OK
723 -)))
724 -|(% style="width:155px" %)(((
725 -AT+SOUND=0,1
726 -)))|(% style="width:124px" %)Turn off the button sound and turn on ACK sound|(% style="width:86px" %)OK
558 +Open the **fonts/ui_font_Font12.c** file, as shown in Image 5.7, and change **#include "../ui.h"** to **#include "../ui_water_leak.h"**. The modified file is shown in Image 5.8. Other font files need to be modified in the same way.
727 727  
728 -(% style="color:#4f81bd" %)**Downlink Command: 0xA1 **
560 +[[image:image-20241121171629-11.png]]
729 729  
730 -Format: Command Code (0xA1) followed by 2 bytes mode value.
562 + image 5.7 before-modified font file
731 731  
732 -The first byte after 0XA1 sets the button sound, and the second byte after 0XA1 sets the ACK sound.** (0: off, 1: on)**
564 +[[image:image-20241121171901-12.png]]
733 733  
734 -* **Example: **Downlink Payload: A10001  ~/~/ Set AT+SOUND=0,1  Turn off the button sound and turn on ACK sound.
566 + image 5.8 modified font file
735 735  
736 -== 3.4  Set buzzer music type(0~~4) ==
568 +Open the **images/ui_img_battery_empty_png.c** file, as shown in Image 5.9, and change **#include "../ui.h"** to **#include "../ui_water_leak.h"**. The modified file is shown in Image 5.10. Other image files need to be modified in the same way.
737 737  
570 +[[image:image-20241121172714-13.png]]
738 738  
739 -Feature: Set different alarm key response sounds.There are five different types of button music.
572 + image 5.9 before-modified image file
740 740  
741 -(% style="color:#4f81bd" %)**AT Command: AT+OPTION**
574 +[[image:image-20241121172908-14.png]]
742 742  
743 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
744 -|(% 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**
745 -|(% style="width:155px" %)(((
746 -AT+OPTION=?
747 -)))|(% style="width:124px" %)(((
748 -Get the buzzer music type
749 -)))|(% style="width:86px" %)(((
750 -3
576 + image 5.10 modified image file
751 751  
752 -OK
753 -)))
754 -|(% style="width:155px" %)AT+OPTION=1|(% style="width:124px" %)Set the buzzer music to type 1|(% style="width:86px" %)OK
578 +7. Modify the **ui_water_leak/CMakeLists.txt**. Open this file, and modify it as shown in image 5.11 (before) and image 5.12 (after).
755 755  
756 -(% style="color:#4f81bd" %)**Downlink Command: 0xA3**
580 +[[image:image-20241121180030-15.png]]
757 757  
758 -Format: Command Code (0xA3) followed by 1 byte mode value.
582 + image 5.11 ui_water_leak/CMakeLists.txt before modification
759 759  
760 -* **Example: **Downlink Payload: A300  ~/~/ Set AT+OPTION=0  Set the buzzer music to type 0.
584 +[[image:image-20241121180517-16.png]]
761 761  
762 -== 3.5  Set Valid Push Time ==
586 + image 5.12 ui_water_leak/CMakeLists.txt after modification
763 763  
764 764  
765 -Feature: Set the holding time for pressing the alarm button to avoid miscontact. Values range from** 0 ~~1000ms**.
589 +8. Modify the **ui_water_leak.h** file. Images 5.13 and 5.14 show the code before modification, while Images 5.15 and 5.16 show the code after modification.
766 766  
767 -(% style="color:#4f81bd" %)**AT Command: AT+STIME**
591 +[[image:image-20241122094200-23.png]]
768 768  
769 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
770 -|(% 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**
771 -|(% style="width:155px" %)(((
772 -AT+STIME=?
773 -)))|(% style="width:124px" %)(((
774 -Get the button sound time
775 -)))|(% style="width:86px" %)(((
776 -0
777 -OK
778 -)))
779 -|(% style="width:155px" %)(((
780 -AT+STIME=1000
781 -)))|(% style="width:124px" %)Set the button sound time to 1000**ms**|(% style="width:86px" %)OK
593 + image 5.13 ui_water_leak.h (1) before modification
782 782  
783 -(% style="color:#4f81bd" %)**Downlink Command: 0xA2**
595 +[[image:image-20241122094320-24.png||height="852" width="554"]]
784 784  
785 -Format: Command Code (0xA2) followed by 2 bytes mode value.
597 + image 5.14 ui_water_leak.h (2) before modification
786 786  
787 -* **Example: **Downlink Payload: A203E8  ~/~/ Set AT+STIME=1000  
599 +[[image:image-20241122094600-25.png||height="1078" width="554"]]
788 788  
789 -**~ Explain: **Hold the alarm button for 10 seconds before the node will send the alarm packet.
601 + image 5.15 ui_water_leak.h (1) after modification
790 790  
603 +[[image:image-20241122094719-26.png||height="941" width="583"]]
791 791  
605 + image 5.16 ui_water_leak.h (2) before modification
792 792  
793 -= 4.  Battery & How to replace =
607 +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.
794 794  
795 -== 4.1  Battery Type and replace ==
609 +_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.
796 796  
611 +[[image:image-20241122102929-27.png||height="619" width="426"]]
797 797  
798 -PB01 uses 2 x AAA LR03(1.5v) batteries. If the batteries running low (shows 2.1v in the platform). Users can buy generic AAA battery and replace it.
613 + image 5.17 ui_water_leak.c (1) before modification
799 799  
800 -(% style="color:red" %)**Note: **
615 +[[image:image-20241122112838-30.png||height="551" width="628"]]
801 801  
802 -1.  The PB01 doesn't have any screw, users can use nail to open it by the middle.
617 + image 5.18 ui_water_leak.c (2) before modification
803 803  
804 -[[image:image-20220621143535-5.png]]
619 +[[image:image-20241122110815-29.png||height="725" width="712"]]
805 805  
621 + image 5.19 ui_water_leak.c (3) before modification
806 806  
807 -2.  Make sure the direction is correct when install the AAA batteries.
623 +[[image:image-20241122113158-31.png||height="872" width="677"]]
808 808  
809 -[[image:image-20220621143535-6.png]]
625 + image 5.20 ui_water_leak.c (1) after modification
810 810  
627 +[[image:image-20241122113259-33.png||height="874" width="724"]]
811 811  
812 -== 4.2  Power Consumption Analyze ==
629 + image 5.21 ui_water_leak.c (2) after modification
813 813  
631 +[[image:image-20241122113359-34.png||height="804" width="746"]]
814 814  
815 -Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
633 + image 5.22 ui_water_leak.c (3) after modification
816 816  
817 -Instruction to use as below:
635 +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.
818 818  
819 -(% style="color:blue" %)**Step 1**(%%):  Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
637 +[[image:image-20241122134113-35.png||height="380" width="421"]]
820 820  
821 -[[battery calculator>>https://www.dropbox.com/sh/sxrgszkac4ips0q/AAA4XjBI3HAHNpdbU3ALN1j0a/Battery%20Document/Battery_Analyze?dl=0&subfolder_nav_tracking=1]]
639 + image 5.23 ui_water_leak_events_.h before modification
822 822  
641 +[[image:image-20241122134420-37.png||height="201" width="283"]]
823 823  
824 -(% style="color:blue" %)**Step 2**(%%):  (% style="display:none" %) (%%)Open it and choose
643 +image 5.24 ui_water_leak_events_.h after modification
825 825  
826 -* Product Model
827 -* Uplink Interval
828 -* Working Mode
645 +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.
829 829  
830 -And the Life expectation in difference case will be shown on the right.
647 +Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
831 831  
832 -[[image:image-20220621143643-7.png||height="429" width="1326"]]
649 +Step2. add code  below in delete_object() function definition.
833 833  
651 + panel_all * panel = find_upper_by_SensorPanel(&arr,((lv_obj_t *)(e->user_data~)~)~);
834 834  
835 -= 5.  Accessories =
653 + size_t index = panel->panel_obj_index;
836 836  
655 + deleteElement(&arr, index);
837 837  
838 -* (((
839 -(% class="wikigeneratedid" id="H5.2A0ProgramConverter28AS-0229" %)
840 -**Program Converter (AS-02)**
841 -)))
657 +[[image:image-20241122135023-38.png||height="358" width="372"]]
842 842  
843 -AS-02 is an optional accessory, it is USB Type-C converter. AS-02 provide below feature:
659 + image 5.25 ui_water_leak_events_.c before modification
844 844  
845 -1. Access AT console of PB01 when used with USB-TTL adapter. [[See this link>>||anchor="H6.1HowtouseATCommandtoconfigurePB01"]].
661 +[[image:image-20241122135258-39.png||height="403" width="559"]]
846 846  
847 -[[image:image-20220621141724-3.png]]
663 + image 5.26 ui_water_leak_events_.c after modification
848 848  
849 849  
850 -= 6. FAQ =
666 +12. **Modify ui_water_leak_style.c file.**
851 851  
852 -== 6.1 How to use AT Command to configure PB01 ==
668 +Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
853 853  
670 + add '#include "../../sort.h"'
854 854  
855 -PB01 supports AT Command set. Users can use a USB to TTL adapter plus the Program Cable to connect to PB01 for using AT command, as below.
672 + add '#include "ui.h"'
856 856  
857 -[[image:image-20240511085914-1.png||height="570" width="602"]]
674 +[[image:image-20241122141536-41.png||height="361" width="612"]]
858 858  
676 + image 5.27 ui_water_leak_style.c (1) before modification
859 859  
860 -**Connection:**
678 +[[image:image-20241122142129-42.png||height="386" width="613"]]
861 861  
862 -* (% style="background-color:yellow" %)USB to TTL GND <~-~-> Program Converter GND pin
863 -* (% style="background-color:yellow" %)USB to TTL RXD  <~-~-> Program Converter D+ pin
864 -* (% style="background-color:yellow" %)USB to TTL TXD  <~-~-> Program Converter A11 pin
680 + image 5.28 ui_water_leak_style.c (1) after modification
865 865  
866 -(((
867 -In PC, User needs to set **serial tool**(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600**(%%) to access to access serial console for PB01. The AT commands are disable by default and need to enter password (default:(% style="color:green" %)**123456**(%%)) to active it. Timeout to input AT Command is 5 min, after 5-minute, user need to input password again.
868 -)))
869 869  
870 -(((
871 -Input password and ATZ to activate PB01, as shown below:
872 -)))
683 +Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
873 873  
874 -[[image:image-20240510174509-18.png||height="572" width="791"]]
685 + delete code as shown in image 5.29
875 875  
687 +[[image:image-20241122145620-44.png||height="757" width="671"]]
876 876  
877 -== 6.2  AT Command and Downlink ==
689 + image 5.29 ui_water_leak_style.c (2)
878 878  
879 879  
880 -(((
881 -Sending ATZ will reboot the node
882 -)))
692 +Step3. The image 5.30, 5.31 show the change.
883 883  
884 -(((
885 -Sending AT+FDR will restore the node to factory settings
886 -)))
694 +[[image:image-20241122152026-45.png||height="277" width="828"]]
887 887  
888 -(((
889 -Get the node's AT command setting by sending AT+CFG
890 -)))
696 + image 5.30 ui_water_leak_style.c (3) before modification
891 891  
892 -(((
893 -
894 -)))
698 +[[image:image-20241122152542-46.png||height="293" width="830"]]
895 895  
896 -(((
897 -**Example：**                                           
898 -)))
700 + image 5.31 ui_water_leak_style.c (3) after modification
899 899  
900 -(((
901 -AT+DEUI=FA 23 45 55 55 55 55 51
902 902  
903 -AT+APPEUI=FF AA 23 45 42 42 41 11
703 +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).
904 904  
905 -AT+APPKEY=AC D7 35 81 63 3C B6 05 F5 69 44 99 C1 12 BA 95
705 +[[image:image-20241122153958-47.png]]
906 906  
907 -AT+DADDR=FFFFFFFF
707 + image 5.32 ui_water_leak_style.c (4)
908 908  
909 -AT+APPSKEY=FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
910 910  
911 -AT+NWKSKEY=FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
710 +[[image:image-20241122154755-49.png||height="864" width="513"]]
912 912  
913 -AT+ADR=1
712 + image 5.33 ui_water_leak_style.c (4)
914 914  
915 -AT+TXP=7
916 916  
917 -AT+DR=5
715 +Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
918 918  
919 -AT+DCS=0
717 +[[image:image-20241122155650-50.png||height="922" width="513"]]
920 920  
921 -AT+PNM=1
719 + image 5.34 ui_water_leak_style.c (5)
922 922  
923 -AT+RX2FQ=869525000
924 924  
925 -AT+RX2DR=0
722 +Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
926 926  
927 -AT+RX1DL=5000
724 +[[image:image-20241122161934-51.png]]
928 928  
929 -AT+RX2DL=6000
726 + image 5.35
930 930  
931 -AT+JN1DL=5000
932 932  
933 -AT+JN2DL=6000
729 +Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
934 934  
935 -AT+NJM=1
731 +[[image:image-20241122162852-53.png||height="330" width="529"]]
936 936  
937 -AT+NWKID=00 00 00 13
733 + image 5.37
938 938  
939 -AT+FCU=61
940 940  
941 -AT+FCD=11
736 +Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
942 942  
943 -AT+CLASS=A
738 +panel_with_type union_sensor;
944 944  
945 -AT+NJS=1
740 +union_sensor.panel_type = WATER_LEAK_TYPE;
946 946  
947 -AT+RECVB=0:
742 +......
948 948  
949 -AT+RECV=
744 +lv_obj_set_x(union_sensor.panel_union.door.ui_PanelSensorDoor, x_by_index(index));
950 950  
951 -AT+VER=EU868 v1.0.0
746 +lv_obj_set_y(union_sensor.panel_union.door.ui_PanelSensorDoor, y_by_index(index));
952 952  
953 -AT+CFM=0,7,0
748 +return union_sensor;
954 954  
955 -AT+SNR=0
750 +[[image:image-20250122173546-6.png||height="777" width="922"]]
956 956  
957 -AT+RSSI=0
752 + image 5.38
958 958  
959 -AT+TDC=1200000
960 960  
961 -AT+PORT=2
755 +13. Rest midification in sort.h file.
962 962  
963 -AT+PWORD=123456
757 +In image 5.39 as below, we can see "WATER_LEAK_TYPE" at line 24 and water leak switch status definition at line 32,33, and these are what we need to add in sort.h.
964 964  
965 -AT+CHS=0
759 +[[image:image-20250122170230-1.png||height="580" width="513"]]
966 966  
967 -AT+RX1WTO=24
761 + image 5.39 sort.h
968 968  
969 -AT+RX2WTO=6
763 +13. **Modify sort.c file.**
970 970  
971 -AT+DECRYPT=0
765 +Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 26.
972 972  
973 -AT+RJTDC=20
767 +[[image:image-20250122171910-5.png||height="524" width="510"]]
974 974  
975 -AT+RPL=0
769 + image 5.40 sort.c (1)
976 976  
977 -AT+TIMESTAMP=systime= 2024/5/11 01:10:58 (1715389858)
771 +There are still some changes need to be done in sort.c, and omit here for the moment.
978 978  
979 -AT+LEAPSEC=18
980 980  
981 -AT+SYNCMOD=1
982 982  
983 -AT+SYNCTDC=10
775 += 6. FAQ =
984 984  
985 -AT+SLEEP=0
777 +== 6.1 ==
986 986  
987 -AT+ATDC=1
988 988  
989 -AT+UUID=003C0C53013259E0
990 -
991 -AT+DDETECT=1,1440,2880
992 -
993 -AT+SETMAXNBTRANS=1,0
994 -
995 -AT+DISFCNTCHECK=0
996 -
997 -AT+DISMACANS=0
998 -
999 -AT+PNACKMD=0
1000 -
1001 -AT+SOUND=0,0
1002 -
1003 -AT+STIME=0
1004 -
1005 -AT+OPTION=3
1006 -)))
1007 -
1008 -(((
1009 -**Example：**
1010 -)))
1011 -
1012 -[[image:image-20240511091518-2.png||height="601" width="836"]]
1013 -
1014 -
1015 -== 6.3  How to upgrade the firmware? ==
1016 -
1017 -
1018 -PB01 requires a program converter to upload images to PB01, which is used to upload image to PB01 for:
1019 -
1020 -* Support new features
1021 -* For bug fix
1022 -* Change LoRaWAN bands.
1023 -
1024 - PB01 internal program is divided into bootloader and work program, shipping is included bootloader, the user can choose to directly update the work program.
1025 -
1026 -If the bootloader is erased for some reason, users will need to download the boot program and the work program.
1027 -
1028 -
1029 -=== 6.3.1 Update firmware (Assume device have bootloader) ===
1030 -
1031 -
1032 -(% style="color:blue" %)**Step 1**(%%):** Connect UART as per FAQ 6.1**
1033 -
1034 -(% style="color:blue" %)**Step 2**(%%):** Update follow [[Instruction for update via DraginoSensorManagerUtility.exe>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H3.2.1UpdateafirmwareviaDraginoSensorManagerUtility.exe]]. **
1035 -
1036 -
1037 -=== 6.3.2 Update firmware (Assume device doesn't have bootloader) ===
1038 -
1039 -
1040 -Download both the boot program and the worker program** . **After update , device will have bootloader so can use above 6.3.1 method to update woke program.
1041 -
1042 -(% style="color:blue" %)**Step 1**(%%):** **Install [[TremoProgrammer>>url:https://www.dropbox.com/scl/fo/gk1rb5pnnjw4kv5m5cs0z/h?rlkey=906ouvgbvif721f9bj795vfrh&dl=0]]  first.
1043 -
1044 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/WebHome/image-20220615170542-5.png?rev=1.1||alt="image-20220615170542-5.png"]]
1045 -
1046 -(% style="color:blue" %)**Step 2**(%%): Hardware Connection
1047 -
1048 -Connect PC and PB01 via USB-TTL adapter .
1049 -
1050 -(% style="color:red" %)**Note: To download firmware in this way, you need to pull the boot pin(Program Converter D- pin) high to enter the burn mode. After burning, disconnect the boot pin of the node and the 3V3 pin of the USB-TTL adapter, and reset the node to exit the burning mode.**
1051 -
1052 -**Connection:**
1053 -
1054 -* (% style="background-color:yellow" %)USB-TTL GND <~-~-> Program Converter GND pin
1055 -* (% style="background-color:yellow" %)USB-TTL RXD  <~-~-> Program Converter D+ pin
1056 -* (% style="background-color:yellow" %)USB-TTL TXD  <~-~-> Program Converter A11 pin
1057 -* (% style="background-color:yellow" %)USB-TTL 3V3 <~-~-> Program Converter D- pin
1058 -
1059 -(% style="color:blue" %)**Step 3**(%%):** **Select the device port to be connected, baud rate and bin file to be downloaded.
1060 -
1061 -[[image:image-20240701160913-1.png]]
1062 -
1063 -Users need to reset the node to start downloading the program.
1064 -~1. Reinstall the battery to reset the node
1065 -2. Hold down the ACT button to reset the node (see [[2.7>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PB01--LoRaWAN_Button_User_Manual/#H2.7Button]] ).
1066 -
1067 -When this interface appears, it indicates that the download has been completed.
1068 -
1069 -[[image:image-20240701160924-2.png]]
1070 -
1071 -Finally, Disconnect Program Converter D- pin, reset the node again , and the node exits burning mode.
1072 -
1073 -
1074 -== 6.4  How to change the LoRa Frequency Bands/Region? ==
1075 -
1076 -
1077 -User can follow the introduction for [[how to upgrade image>>||anchor="H6.3A0Howtoupgradethefirmware3F"]]. When download the images, choose the required image file for download.
1078 -
1079 -
1080 -== 6.5 Why i see different working temperature for the device? ==
1081 -
1082 -
1083 -The working temperature range of device depends on the battery user choose.
1084 -
1085 -* Normal AAA Battery can support -10 ~~ 50°C working range.
1086 -* Special AAA battery can support -40 ~~ 60 °C working range. For example: [[Energizer L92>>https://data.energizer.com/pdfs/l92.pdf]]
1087 -
1088 1088  = 7. Order Info =
1089 1089  
1090 -== 7.1  Main Device ==
782 +== 7.1  Part Number ==
1091 1091  
1092 1092  
1093 -Part Number: (% style="color:#4472c4" %)PB01-LW-XX(%%) (white button) / (% style="color:#4472c4" %)PB01-LR-XX(%%)(Red Button)
785 +Part Number: (% style="color:#4472c4" %)LTS5
1094 1094  
1095 -(% style="color:#4472c4" %)**XX **(%%): The default frequency band
1096 1096  
1097 -* (% style="color:red" %)**AS923**(%%)**: **LoRaWAN AS923 band
1098 -* (% style="color:red" %)**AU915**(%%)**: **LoRaWAN AU915 band
1099 -* (% style="color:red" %)**EU433**(%%)**: **LoRaWAN EU433 band
1100 -* (% style="color:red" %)**EU868**(%%)**:** LoRaWAN EU868 band
1101 -* (% style="color:red" %)**KR920**(%%)**: **LoRaWAN KR920 band
1102 -* (% style="color:red" %)**US915**(%%)**: **LoRaWAN US915 band
1103 -* (% style="color:red" %)**IN865**(%%)**:  **LoRaWAN IN865 band
1104 -* (% style="color:red" %)**CN470**(%%)**: **LoRaWAN CN470 band
788 +== 7.2  Packing Info ==
1105 1105  
1106 -= 7. Packing Info =
1107 1107  
1108 -
1109 1109  **Package Includes**:
1110 1110  
1111 -* PB01 LoRaWAN Push Button x 1
793 +* LTS5 HMI Touch Screen
794 +* 5V,2A DC Power Adapter.
795 +* USB Type C Program Cable
1112 1112  
1113 1113  = 8. Support =
1114 1114  
... ... @@ -1119,7 +1119,9 @@
1119 1119  = 9.  Reference material =
1120 1120  
1121 1121  
1122 -* [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/scl/fo/y7pvm58wcr8319d5o4ujr/APZtqlbzRCNbHoPWTmmMMWs?rlkey=wfh93x2dhcev3ydn0846rinf0&st=kdp6lg7t&dl=0]]
806 +* Datasheet
807 +* Source Code: [[dragino/LoRa-HMI-Touch-Screen: Open Source LoRa / LoRaWAN HMI Touch Screen Project>>url:https://github.com/dragino/LoRa-HMI-Touch-Screen/tree/main]]
808 +* Mechinical
1123 1123  
1124 1124  = 10. FCC Warning =
1125 1125  
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
1738893226894-758.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +25.6 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
image-20241226135550-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +293.3 KB
Content
image-20250122170230-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +77.3 KB
Content
image-20250122171809-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +51.1 KB
Content
image-20250122171825-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +51.1 KB
Content
image-20250122171832-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +51.1 KB
Content
image-20250122171910-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +51.1 KB
Content
image-20250122173546-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +200.4 KB
Content
image-20250207100150-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +54.1 KB
Content
image-20250207101415-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +17.6 KB
Content
image-20250207101515-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +24.1 KB
Content
image-20250207142334-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +62.0 KB
Content
image-20250207143131-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +48.7 KB
Content
image-20250207144605-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +58.1 KB
Content
image-20250207164320-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +194.5 KB
Content
image-20250207165702-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +78.1 KB
Content
image-20250207170215-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.6 KB
Content
image-20250207170307-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.2 KB
Content
image-20250207171650-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +11.0 KB
Content
image-20250207171851-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.5 KB
Content
image-20250207172010-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.5 KB
Content
image-20250207172246-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +2.5 KB
Content
image-20250207172443-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207172821-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +0 bytes
Content
image-20250207172834-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +0 bytes
Content
image-20250207173152-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207173159-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207173206-26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207173212-27.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content
image-20250207192107-28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +14.3 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