Skip to Content
Last modified by BoYang Xie on 2025/07/24 16:47
From version 125.1
edited by Dilisi S
on 2024/12/24 15:25
Change comment: Dec 24 edits - part 1
To version 3.1
edited by Edwin Chen
on 2024/09/15 23:18
Change comment: Uploaded new attachment "image-20240915231842-1.png", version {1}

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -LTS5 LoRa HMI Touch Screen
1 +LTS5 LoRa Touch Screen
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.pradeeka
1 +XWiki.Edwin
Content
... ... @@ -1,14 +1,12 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20240915231842-1.png]]
2 +[[image:image-20240705094013-3.png]]
3 3  
4 4  
5 5  
6 6  
7 7  
8 -
9 -
10 10  (% _mstvisible="1" %)
11 -(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:**
9 +(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents：**
12 12  
13 13  {{toc/}}
14 14  
... ... @@ -21,77 +21,64 @@
21 21  
22 22  = 1.  Introduction =
23 23  
24 -== 1.1  What is the LTS5 LoRa HMI Touch Screen? ==
22 +== 1.1  What is PB01 LoRaWAN Push Button ==
25 25  
26 26  
27 -The LTS5 is a (% style="color:blue" %)**LoRa / LoRaWAN HMI Touch Screen**(%%) designed for displaying information in IoT projects. It features a **5.0-inch HMI touch screen** and supports **Wi-Fi**, **Bluetooth**, and **LoRa** wireless protocols.
25 +PB01 LoRaWAN Button is a LoRaWAN wireless device with one (% style="color:blue" %)**push button**(%%). Once user push the button, PB01 will transfer the signal to IoT server via Long Range LoRaWAN wireless protocol. PB01 also senses the (% style="color:blue" %)**environment temperature & humidity**(%%) and will also uplink these data to IoT Server.
28 28  
29 -The LTS5 is an open-source software project powered by an **ESP32 MCU** and a **Dragino LA66 LoRa** module. The extensive development resources available for ESP32 can significantly reduce development time.
27 +PB01 supports (% style="color:blue" %)** 2 x AAA batteries**(%%) and works for a long time up to several years*. User can replace the batteries easily after they are finished.
30 30  
31 -The LTS5's HMI touch screen supports **drag-and-drop** design, allowing developers to use SquareLine to easily customize the display UI for various applications.
29 +PB01 has a built-in speaker, it can pronouns different sound when press button and get reply from server. The speaker can by disable if user want it.
32 32  
33 -The LA66 LoRa module can be programmed to support either private LoRa protocols or the LoRaWAN protocol.
31 +PB01 is fully compatible with LoRaWAN v1.0.3 protocol, it can work with standard LoRaWAN gateway.
34 34  
33 +*Battery life depends how often to send data, please see [[battery analyzer>>||anchor="H4.2A0PowerConsumptionAnalyze"]].
34 +
35 +
35 35  == 1.2  Features ==
36 36  
37 37  
38 -* ESP32-WROOM MCU: 8MB RAM & 16MB ROM
39 -* Dragino LA66 LoRa Module
40 -* Support Private LoRa protocol or LoRaWAN protocol
41 -* Support WiFi & BLE wireless protocol
42 -* 5.0" HMI touch screen
43 -* Support LVGL case. SquareLine program.
44 -* Support RS485 Interface
45 -* Open Source Project
46 46  * Wall Attachable.
47 -* 5V DC power
40 +* LoRaWAN v1.0.3 Class A protocol.
41 +* 1 x push button. Different Color available.
42 +* Built-in Temperature & Humidity sensor
43 +* Built-in speaker
44 +* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915
45 +* AT Commands to change parameters
46 +* Remote configure parameters via LoRaWAN Downlink
47 +* Firmware upgradable via program port
48 +* Support 2 x AAA LR03 batteries.
48 48  * IP Rating: IP52
49 49  
50 -== 1.3  Specifications ==
51 +== 1.3  Specification ==
51 51  
52 52  
53 -**LoRa**:
54 +**Built-in Temperature Sensor:**
54 54  
55 -* Frequency Range: 870 MHz ~~ 960 MHz
56 -* TCXO crystal to ensure RF performance on low temperature
57 -* Maximum Power +22 dBm constant RF output
58 -* High sensitivity: -148 dBm
59 -* LoRa Tx Current: <90 mA at +17 dBm, 108 mA at +22 dBm
60 -* LoRa Rx current: <9 mA
56 +* Resolution: 0.01 °C
57 +* Accuracy Tolerance: Typ ±0.2 °C
58 +* Long Term Drift: < 0.03 °C/yr
59 +* Operating Range: -10 ~~ 50 °C  or -40 ~~ 60 °C (depends on battery type, see [[FAQ>>||anchor="H6.5Whyiseedifferentworkingtemperatureforthedevice3F"]])
61 61  
62 -**WiFi:**
61 +**Built-in Humidity Sensor:**
63 63  
64 -* 802.11b/g/n
65 -* Up to 150 Mbps data rate in 802.11n mode
66 -* Support A-MPDU and A-MSDU aggregation
67 -* zero point four μ S protection interval
68 -* Working channel center frequency range: 2412~~2484 MHz
63 +* Resolution: 0.01 %RH
64 +* Accuracy Tolerance: Typ ±1.8 %RH
65 +* Long Term Drift: < 0.2% RH/yr
66 +* Operating Range: 0 ~~ 99.0 %RH(no Dew)
69 69  
70 -**Bluetooth:**
71 -
72 -* Bluetooth V4.2 BR/EDR and Bluetooth LE standard
73 -* Class-1, Class-2, and Class-3 transmitters.
74 -* AFH
75 -* CVSD and SBC
76 -
77 -**Display:**
78 -
79 -* 5.0 Inch , 800 x 480
80 -* IPS Capacitive Touch SCreen
81 -* RGB color.
82 -* Display Area: 120.7*75.80 mm
83 -
84 84  == 1.4  Power Consumption ==
85 85  
86 86  
87 -* External 5V DC power adapter
71 +PB01 : Idle: 5uA, Transmit: max 110mA
88 88  
73 +
89 89  == 1.5  Storage & Operation Temperature ==
90 90  
91 91  
92 -* Operation Temperature: -20 ~~ 70°C  (No Dew)
93 -* Storage Temperature: -30 ~~ 70°C  (No Dew)
77 +-10 ~~ 50 °C  or -40 ~~ 60 °C (depends on battery type, see [[FAQ>>||anchor="H6.5Whyiseedifferentworkingtemperatureforthedevice3F"]])
94 94  
79 +
95 95  == 1.6  Applications ==
96 96  
97 97  
... ... @@ -102,528 +102,1037 @@
102 102  * Smart Cities
103 103  * Smart Factory
104 104  
105 -= 2.  Getting Started with 'Hello World' =
90 += 2.  Operation Mode =
106 106  
107 -== 2.1  About this demo ==
92 +== 2.1  How it work? ==
108 108  
109 109  
110 -This getting started example demonstrates how to design and deploy a simple display UI for the LTS5 device. The example includes:
95 +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**.
111 111  
112 -* Creating a basic UI with a single button.
113 -* Implementing functionality to navigate the Web UI to a new page when the button is clicked.
114 -* Uploading the UI to the LTS5 device.
115 115  
116 -By completing this demo, you will gain foundational knowledge for customizing the LTS5 interface and building more advanced IoT applications.
98 +== 2.2  How to Activate PB01? ==
117 117  
118 118  
119 -== 2.2  Install Software Running Environment ==
101 +(% style="color:red" %)** 1.  Open enclosure from below position.**
120 120  
103 +[[image:image-20220621093835-1.png]]
121 121  
122 -The **ESP MCU** supports development with **ESP-IDF**, **Arduino**, or **MicroPython**. We use **ESP-IDF** for compilation and **Visual Studio Code (VS Code)** as the development environment for this project.
123 123  
106 +(% style="color:red" %)** 2.  Insert 2 x AAA LR03 batteries and the node is activated.**
124 124  
125 -=== 2.2.1 Install VS Code and ESP-IDF extension ===
108 +[[image:image-20220621093835-2.png]]
126 126  
127 127  
128 -First, download and install **VS Code** for your operating system from the Visual Studio Code website: [[Visual Studio Code - Mac, Linux, Windows>>https://code.visualstudio.com/download]].
111 +(% style="color:red" %)** 3. Under the above conditions, users can also reactivate the node by long pressing the ACT button.**
129 129  
130 -Next, install the **ESP-IDF** extension within **VS Code**. Detailed steps for this process are shown in Image 1.
113 +[[image:image-20220621093835-3.png]]
131 131  
132 132  
133 -[[image:image-20240928110211-5.png||height="508" width="866"]]
116 +User can check [[LED Status>>||anchor="H2.8LEDIndicator"]] to know the working state of PB01.
134 134  
135 - Image 1: ESP-IDF extension install
136 136  
137 -Links for reference: [[Install ESP32 ESP-IDF on Windows and Integrate with VS code (esp32tutorials.com)>>url:https://esp32tutorials.com/install-esp32-esp-idf-windows-integrate-vs-code/#:~~:text=In%20this%20tutorial,%20we%20will%20show%20you%20how%20to%20install]]
119 +== 2.3  Example to join LoRaWAN network ==
138 138  
139 139  
140 -=== 2.2.2 Install SquareLine Studio ===
122 +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.
141 141  
124 +(% _mstvisible="1" class="wikigeneratedid" %)
125 +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. 
142 142  
143 -Download and install the latest version of [[SquareLine Studio>>https://squareline.io/downloads#lastRelease]] on your computer. It supports Windows, Linux, and Mac OS. The software version we are using here is 1.5.0. See the image below.
127 +[[image:image-20240705094824-4.png]]
144 144  
145 -[[image:squareline.io_downloads.png]]
129 +(% style="color:blue" %)**Step 1**(%%):  Create a device in TTN V3 with the OTAA keys from PB01.
146 146  
131 +Each PB01 is shipped with a sticker with the default DEV EUI as below:
147 147  
148 -After installation, you can use SquareLine Studio with a **PERSONAL license plan**. Click **LOG IN** and create a free account using your email address. Then activate your PERSONAL license plan for free. You don’t need to provide any credit card information. However, the PERSONAL license plan has the following limitations:
133 +[[image:image-20230426083617-1.png||height="294" width="633"]]
149 149  
150 -* Max. 10 screens
151 -* Max. 150 widgets
152 -* Max. 5 global colors
153 -* Max. 2 themes
154 -* Max. 1 component
155 155  
156 -== 2.3 Simple usage of SquareLine Studio and exporting UI code ==
136 +Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
157 157  
138 +Create application.
158 158  
159 -Start the SquareLine Studio. The **launcher screen** appears as shown in the below image. You can create a new project by clicking **Create** in the top menu.
140 +choose to create the device manually.
160 160  
161 -* Select major **LVGL** version: **8.3**.
162 -* Select the **Desktop** tab.
163 -* Select  **Eclipse with  SDL for  development on PC**:
164 -* In the **PROJECT SETTINGS**, select **LVGL version **as **8.3.11** and **Resolution** as **800** x **480**.
165 -* Select the **CREATE **button to create the new project with the selected settings.
142 +Add JoinEUI(AppEUI), DevEUI, AppKey.(% style="display:none" %)
166 166  
167 -[[image:image-20240928103357-2.png||height="680" width="708"]]
144 +[[image:image-20240507142116-1.png||height="410" width="1138"]](% style="display:none" %) (%%)
145 +
168 168  
147 +[[image:image-20240507142157-2.png||height="559" width="1147"]]
169 169  
170 -Next, you need to configure some additional settings for this project. Select** File  -> Project Settings** as shown in the image below.
149 +[[image:image-20240507142401-3.png||height="693" width="1202"]]
171 171  
172 -[[image:1727229582471-566.png]]
151 +[[image:image-20240507142651-4.png||height="760" width="1190"]]
173 173  
153 +**Default mode OTAA**(% style="display:none" %)
174 174  
175 -In the PROJECT SETTINGS dialog box, configure/modify the project settings:
176 176  
177 -* **UI Files Export Root**: Select a folder on your computer to store the UI files.
178 -* **LVGL Include Path**: Set this to **lvgl.h**
179 -* **Click on the APPLY CHANGES button.**
156 +(% style="color:blue" %)**Step 2**(%%):  Use ACT button to activate PB01 and it will auto join to the TTN V3 network. After join success, it will start to upload sensor data to TTN V3 and user can see in the panel.
180 180  
181 -[[image:image-20240928105309-4.png||height="526" width="556"]]
158 +[[image:image-20240507143104-5.png||height="434" width="1398"]]
182 182  
183 - Image 4 Configure/modify project settings
184 184  
161 +== 2.4  Uplink Payload ==
185 185  
186 -Now you can start building the sample UI. Follow the steps below:
187 187  
164 +Uplink payloads include two types: Valid Sensor Value and other status / control command.
188 188  
189 -=== **Add widgets** ===
166 +* Valid Sensor Value: Use FPORT=2
167 +* Other control command: Use FPORT other than 2.
190 190  
169 +=== 2.4.1  Uplink FPORT~=5, Device Status ===
191 191  
192 -To add widgets navigate to the **Widgets** area, then click on the widgets you want to add. The selected widgets will be added to the screen. You can reposition the widgets in the screen area by clicking and dragging them.
193 193  
194 -Add a Label, Button, and Image to the screen as shown in **Image 5**.
172 +Users can  get the Device Status uplink through the downlink command:
195 195  
196 -[[image:image-20240928111412-6.png||height="526" width="864"]]
174 +(% style="color:#4472c4" %)**Downlink:  **(%%)**0x2601**
197 197  
198 - Image 5: Add widgets
176 +Uplink the device configures with FPORT=5.
199 199  
178 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:370px" %)
179 +|=(% 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**
180 +|(% 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
200 200  
201 -=== **Modify widget properties** ===
182 +[[image:image-20240507152130-12.png||height="469" width="1366"]](% style="display:none" %)
202 202  
184 +Example Payload (FPort=5):  [[image:image-20240507152254-13.png||height="26" width="130"]]
203 203  
204 -The area for modifying widgets is called the **Inspector** tab. The Inspector tab consists of four sections: **COMPONENT**, **<WIDGET>**, **STYLE SETTINGS**, and **EVENTS**, as shown in Image 6.
205 205  
206 -The second section allows you to adjust a widget's layout, size, position, alignment, flags, states, and more. When you select a widget on the screen, the name of this section changes to match the name of the selected widget.
187 +(% style="color:#4472c4" %)**Sensor Model**(%%): For PB01, this value is 0x35.
207 207  
208 -[[image:1727485118799-984.png]]
189 +(% style="color:#4472c4" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version.
209 209  
210 - Image 6: The button widget's "Inspector" tab
191 +(% style="color:#4472c4" %)**Frequency Band**:
211 211  
193 +*0x01: EU868
212 212  
213 -==== **Changing the Button properties** ====
195 +*0x02: US915
214 214  
197 +*0x03: IN865
215 215  
216 -Click the Button.
199 +*0x04: AU915
217 217  
218 -Under the "Layout" you can change the button's position and size.
201 +*0x05: KZ865
219 219  
220 -[[image:1727485251053-655.png]]
203 +*0x06: RU864
221 221  
222 -Image 7: The button widget's "BUTTON" tab
205 +*0x07: AS923
223 223  
207 +*0x08: AS923-1
224 224  
225 -Next, add a click event to the button. When the button is clicked, an event should trigger to change the current screen (Screen1) to a new screen (Screen2) with a fade effect and the transition from Screen1 to Screen2 should take 500ms.
209 +*0x09: AS923-2
226 226  
227 -* Click **ADD EVENT** button.
228 -* Select **CLICKED** under the Trigger.
229 -* Select **Screen2** from **Screen to**.
230 -* Select **FADE ON** from **Fade mode**.
231 -* Enter **500** in the **Speed** text box.
232 -* Finally, click **ADD** button.
211 +*0x0a: AS923-3
233 233  
234 -[[image:1727485480434-713.png||height="395" width="290"]]
235 235  
236 - Image 8: Add an event for the button
214 +(% style="color:#4472c4" %)**Sub-Band**(%%): value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
237 237  
216 +(% style="color:#4472c4" %)**BAT**(%%): shows the battery voltage for PB01.
238 238  
239 -==== **Changing the label properties** ====
218 +(% style="color:#4472c4" %)**Ex1**(%%): 0x0C DE = 3294mV
240 240  
241 241  
242 -Click the label. Under the **Label** section, type "Click For Detail" in the **Text** textbox.
221 +=== 2.4.2  Uplink FPORT~=2, Real time sensor value ===
243 243  
244 -[[image:image-20240928090825-1.png||height="327" width="391"]]
245 245  
246 - Image 9:  Modify text of label widget
224 +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"]].
247 247  
226 +Uplink uses FPORT=2 and every 20 minutes send one uplink by default.
248 248  
249 -==== **Changing image properties** ====
228 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:460px" %)
229 +|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
230 +**Size(bytes)**
231 +)))|=(% style="width: 60px;background-color:#4F81BD;color:white" %)2|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
232 +**1**
233 +)))|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
234 +**1**
235 +)))|=(% style="width: 90px;background-color:#4F81BD;color:white" %)(((
236 +**2**
237 +)))|=(% style="width: 40px;background-color:#4F81BD;color:white" %)(((
238 +**2**
239 +)))
240 +|(% style="width:97px" %)(((
241 +Value
242 +)))|(% style="width:39px" %)Battery|(% style="width:39px" %)(((
243 +Sound_ACK
250 250  
245 +&Sound_key
246 +)))|(% style="width:100px" %)(((
247 +(((
248 +Alarm
249 +)))
250 +)))|(% style="width:77px" %)(((
251 +(((
252 +Temperature
253 +)))
254 +)))|(% style="width:47px" %)(((
255 +Humidity
256 +)))
251 251  
252 -To use the image widget, you should first add an image to your project. The image format must be PNG, and its resolution should not exceed 800x480 pixels. There are two ways to add an image file. One way is to move your image into the folder "…/squareline project/assets/", as shown in image 10. The other way is to click the "ADD FILE INTO ASSETS" button, then select an image from your computer to import. After adding, you can see the image in the "assets" area in SquareLine Studio, as demonstrated in image 11.
258 +Example in TTN.
253 253  
254 -[[image:image-20240928113424-9.png||height="355" width="505"]]
260 +[[image:image-20240507150155-11.png||height="549" width="1261"]]
255 255  
256 - image 10 add image file into SquareLine Studio project
262 +Example Payload (FPort=2):  (% style="background-color:yellow" %)**0C EA 03 01 01 11 02 A8**
257 257  
258 -[[image:image-20240928114139-10.png||height="559" width="810"]]
264 +==== (% style="color:blue" %)**Battery:**(%%) ====
259 259  
260 - image 11 use image widget in SquareLine Studio
266 +Check the battery voltage.
261 261  
268 +* Ex1: 0x0CEA = 3306mV
269 +* Ex2: 0x0D08 = 3336mV
262 262  
263 -==== **The relationship between widgets** ====
271 +==== (% style="color:blue" %)**Sound_ACK & Sound_key:**(%%) ====
264 264  
273 +Key sound and ACK sound are enabled by default.
265 265  
266 -Widgets commonly have two types of relationships: **parallel** and **parent-child**.
275 +* Example1: 0x03
267 267  
268 -* In a **parallel relationship**, widgets' positions are determined relative to a shared reference object.
269 -* In a **parent-child relationship**, any part of the child object outside the parent's boundaries is hidden by default. To make the child object fully visible, you must adjust its position to fit within the parent's range, as shown in Image 13.
277 + Sound_ACK: (03>>1) & 0x01=1, OPEN.
270 270  
271 -[[image:1727486567182-334.png||height="318" width="278"]]
279 +**~ ** Sound_key:  03 & 0x01=1, OPEN.
272 272  
281 +* Example2: 0x01
273 273  
274 -Move **Label1** to make it a child of **Button1**. See Image 13.
283 + Sound_ACK: (01>>1) & 0x01=0, CLOSE.
275 275  
276 -[[image:image-20240928112001-8.png||height="431" width="796"]]
285 +**~ ** Sound_key:  01 & 0x01=1, OPEN.
277 277  
278 - Image 13: Move Label1 to make it a child of Button1.
279 279  
288 +==== (% style="color:blue" %)**Alarm:**(%%) ====
280 280  
281 -==== **Preview the screen** ====
290 +Key alarm.
282 282  
292 +* Ex1: 0x01 & 0x01=1, TRUE.
293 +* Ex2: 0x00 & 0x01=0, FALSE.
283 283  
284 -You can test the result by clicking on the **PLAY** button. The screen will change into play mode. See Image 14.
295 +==== (% style="color:blue" %)**Temperature:**(%%) ====
285 285  
286 -[[image:1727487368023-281.png]]
297 +* Example1:  0x0111/10=27.3℃
298 +* Example2:  (0xFF0D-65536)/10=-24.3℃
287 287  
288 - Image 14: Simulating the project
300 +If payload is: FF0D :  (FF0D & 8000 == 1) , temp = (FF0D - 65536)/100 =-24.3℃
289 289  
302 +（FF0D & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative）
290 290  
291 -For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
292 292  
305 +==== (% style="color:blue" %)**Humidity:**(%%) ====
293 293  
294 -== 2.4 Integrate UI Code to ESP-IDF Project ==
307 +* Humidity:    0x02A8/10=68.0%
295 295  
309 +=== 2.4.3  Uplink FPORT~=3, Datalog sensor value ===
296 296  
297 -To achieve the integrating, we first need to export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
298 298  
299 -[[image:1727229798126-306.png]]
312 +PB01 stores sensor value and user can retrieve these history value via downlink command. The Datalog sensor value are sent via FPORT=3.
300 300  
301 - image 15 export UI file
314 +[[image:image-20240510144912-1.png||height="471" width="1178"]](% style="display:none" %)
302 302  
303 -[[image:1727229821582-258.png||height="333" width="662"]]
304 304  
305 - image 16 exported UI file
317 +* 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" %)
306 306  
307 -Create a empty directory entitled "ui" in path "basic_prj/app_components/ui/", and then copy all UI code exported to this directory.
319 +For example, in US915 band, the max payload for different DR is:
308 308  
309 -[[image:image-20240928144830-11.png]]
321 +1. **DR0**: max is 11 bytes so one entry of data
322 +1. **DR1**: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
323 +1. **DR2**: total payload includes 11 entries of data
324 +1. **DR3**: total payload includes 22 entries of data.
310 310  
311 - image 17 open CMakeLists.txt
326 +(% 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.**
312 312  
313 -[[image:1727229892636-154.png||height="521" width="407"]]
328 +See more info about the [[Datalog feature>>||anchor="H2.6A0DatalogFeature"]].
314 314  
315 - image 18 modify CMakeLists.txt
330 +(% style="display:none" %) (%%)
316 316  
317 -The last step of integrating is adding two lines of code in main.c file.
332 +=== 2.4.4  Decoder in TTN V3 ===
318 318  
319 -[[image:1727229926561-300.png]]
320 320  
321 - image 19 add "ui.h"
335 +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.
322 322  
323 -[[image:1727229955611-607.png]]
337 +In TTN , add formatter as below:
324 324  
325 - image 20 add "ui_init()"
339 +[[image:image-20240507162814-16.png||height="778" width="1135"]]
326 326  
341 +(((
342 +Please check the decoder from this link:  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]
343 +)))
327 327  
328 -== 2.5 Brief introduction of hello world project ==
345 +(((
346 +
347 +)))
329 329  
349 +== 2.5 Show data on Datacake ==
330 330  
331 -The project consists of two screens. The first screen displays the company's logo, the project name, and a button to navigate to the next screen. The second screen presents some information about this HMI screen product through an image and includes a button to return to the previous screen.
332 332  
352 +(((
353 +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:
354 +)))
333 333  
334 -== 2.6 Test Result ==
356 +(((
357 +
358 +)))
335 335  
360 +(((
361 +(% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the LoRaWAN network.
362 +)))
336 336  
337 -By pressing the button lying bottom right, the screen can switch to another as expected. This indicates that the UI file has been successfully integrated into the project and is now effective.
364 +(((
365 +(% style="color:blue" %)**Step 2**(%%):  Configure your Application to forward data to Datacake you will need to add integration. Go to TTN V3 Console ~-~-> Applications ~-~-> Integrations ~-~-> Add Integrations.
366 +)))
338 338  
339 -[[image:1727488067077-684.png||height="402" width="574"]]
368 +(((
369 +~1. Add Datacake:
370 +)))
340 340  
341 - image 21 screen1
372 +(((
373 +2. Select default key as Access Key:
374 +)))
342 342  
343 -[[image:1727488157579-949.png||height="397" width="572"]]
376 +(((
377 +3. In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add PB01:
378 +)))
344 344  
345 - image 22 screen2
380 +(((
381 + Please refer to the figure below.
382 +)))
346 346  
384 +[[image:image-20240510150924-2.png||height="612" width="1186"]]
347 347  
348 -= 3. Example Project 1: LoRa Central Display =
349 349  
350 -[[image:image-20240916101737-1.png||height="468" width="683"]]
387 +Log in to DATACAKE, copy the API under the account.
351 351  
389 +[[image:image-20240510151944-3.png||height="581" width="1191"]]
352 352  
353 -= 4. Example Project 2: LoRaWAN RS485 Alarm =
354 354  
355 -= 5. The way to add a new panel to project =
356 356  
393 +[[image:image-20240510152150-4.png||height="697" width="1188"]]
357 357  
358 -**~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.**
359 359  
360 -[[image:image-20241121113445-1.png||height="584" width="934"]]
396 +[[image:image-20240510152300-5.png||height="298" width="1191"]]
361 361  
362 - image 5.1 a panel about water_leak
363 363  
399 +[[image:image-20240510152355-6.png||height="782" width="1193"]]
364 364  
365 -**2. Export the ui file.** You need  to adjust the export path first, then click "Export->Export UI Files". This step had been introduced before. Then you can get the ui files as shown in image 5.2.
401 +[[image:image-20240510152542-8.png||height="545" width="739"]]
366 366  
367 -[[image:image-20241121141120-4.png||height="383" width="795"]]
403 +[[image:image-20240510152634-9.png||height="748" width="740"]]
368 368  
369 - image 5.2 ui files exported
370 370  
406 +[[image:image-20240510152809-10.png||height="607" width="732"]]
371 371  
372 -**3. Delete or rename some file.** Here are the steps:
408 +[[image:image-20240510153934-14.png||height="460" width="1199"]]
373 373  
374 - Step1 Delete the 'components' directory.
375 - Step2 Delete 'filelist.txt'.
376 - Step3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
377 - Step4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
378 - Step5 Rename the 'screens' directory to 'styles'.
379 379  
380 -[[image:image-20241121151934-10.png||height="303" width="792"]]
411 +[[image:image-20240510153435-12.png||height="428" width="1197"]]
381 381  
382 - image 5.3 rest file (1)
383 383  
384 -[[image:image-20241121142925-7.png||height="141" width="793"]]
414 +Copy and paste the [[TTN decoder>>https://github.com/dragino/dragino-end-node-decoder]] here and save.
385 385  
386 - image 5.4 rest file (2)
416 +[[image:image-20240510153624-13.png||height="468" width="1195"]]
387 387  
388 -**4. Open this project in vscode.**
389 389  
390 -5. Add file include path about water_leak in extra_lib/CMakeLists.txt as shown in image 5.5, 5.6, and its format is similar to the tem_hum or door.
419 +Visual widgets please read the DATACAKE documentation.
391 391  
392 -[[image:image-20241121181957-17.png||height="438" width="516"]]
421 +(% style="display:none" %) (%%)
393 393  
394 - image 5.5 extra_lib/CMakeLists.txt before add
423 +== 2.6  Datalog Feature ==
395 395  
396 -[[image:image-20241121182239-18.png||height="520" width="518"]]
397 397  
398 - image 5.6 extra_lib/CMakeLists.txt after add
426 +(% _msthash="315262" _msttexthash="32283004" _mstvisible="1" %)
427 +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.
399 399  
400 -**6. Modify header file include in fonts and images directory.** Open the fonts/ui_font_Font12.c file, as shown in image 5.7, then modify the '#include "../ui.h"' to '#include "../ui_water_leak.h"', the image 5.8 is the modified image. Other font file need to be modified in same way.
401 401  
402 -[[image:image-20241121171629-11.png]]
430 +=== 2.6.1  Unix TimeStamp ===
403 403  
404 - image 5.7 before-modified font file
405 405  
406 -[[image:image-20241121171901-12.png]]
433 +Unix TimeStamp shows the sampling time of uplink payload. format base on
407 407  
408 - image 5.8 modified font file
435 +[[image:image-20220523001219-11.png||_mstalt="450450" _mstvisible="3" height="97" width="627"]]
409 409  
410 -Open the images/ui_img_battery_empty_png.c file, as shown in image 5.9, then modify the '#include "../ui.h"' to '#include "../ui_water_leak.h"', the image 5.10 is the modified image. Other image file need to be modified in same way.
437 +User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/||_mstvisible="3"]] :
411 411  
412 -[[image:image-20241121172714-13.png]]
439 +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)
413 413  
414 - image 5.9 before-modified image file
415 415  
416 -[[image:image-20241121172908-14.png]]
442 +[[image:1655782409139-256.png]]
417 417  
418 - image 5.10 modified image file
419 419  
420 -**7. Modify the ui_water_leak/CMakeLists.txt.** Open this file, and modify it from image 5.11 to image 5.12.
445 +=== 2.6.2  Poll sensor value ===
421 421  
422 -[[image:image-20241121180030-15.png]]
423 423  
424 - image 5.11 ui_water_leak/CMakeLists.txt before modification
448 +(((
449 +User can poll sensor value based on timestamps from the server. Below is the downlink command.
450 +)))
425 425  
426 -[[image:image-20241121180517-16.png]]
452 +(((
453 +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.
454 +)))
427 427  
428 - image 5.12 ui_water_leak/CMakeLists.txt after modification
456 +(((
457 +For example, downlink command [[image:image-20220621113526-13.png]] (% _mstvisible="3" style="display:none" %)
458 +)))
429 429  
430 -**8. Modify ui_water_leak.h file.** The image 5.13, 5.14 show the code before modification, and the image 5.15, 5.16 show the code after modification.
460 +(((
461 +Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00's data
462 +)))
431 431  
432 -[[image:image-20241122094200-23.png]]
464 +(((
465 +Uplink Internal =5s，means PB01 will send one packet every 5s. range 5~~255s.
466 +)))
433 433  
434 - image 5.13 ui_water_leak.h (1) before modification
435 435  
436 -[[image:image-20241122094320-24.png||height="852" width="554"]]
469 +=== 2.6.3  Datalog Uplink payload ===
437 437  
438 - image 5.14 ui_water_leak.h (2) before modification
439 439  
440 -[[image:image-20241122094600-25.png||height="1078" width="554"]]
472 +See [[Uplink FPORT=3, Datalog sensor value>>||anchor="H2.4.3A0UplinkFPORT3D32CDatalogsensorvalue"]]
441 441  
442 - image 5.15 ui_water_leak.h (1) after modification
474 +(% style="display:none" %) (%%) (% style="display:none" %)
443 443  
444 -[[image:image-20241122094719-26.png||height="941" width="583"]]
476 +== 2.7 Button ==
445 445  
446 - image 5.16 ui_water_leak.h (2) before modification
447 447  
448 -**9. Modify ui_water_leak.c file.** The image 5.17, 5.18, 5.19 show the code before modification, and the image 5.20, 5.21, 5.22 show the code after modification.
479 +* ACT button
449 449  
450 -_ui_flag_modify( ((lv_obj_t *)(e->user_data)), LV_OBJ_FLAG_HIDDEN, _UI_MODIFY_FLAG_TOGGLE);  This code replaces 4 lines of code in ui_water_leak.c, so it is pasted here for convenience.
481 +Long press this button PB01 will reset and join network again.
451 451  
452 -[[image:image-20241122102929-27.png||height="619" width="426"]]
483 +[[image:image-20240510161626-17.png||height="192" width="224"]]
453 453  
454 - image 5.17 ui_water_leak.c (1) before modification
485 +* Alarm button
455 455  
456 -[[image:image-20241122112838-30.png||height="551" width="628"]]
487 +Press the button PB01 will immediately uplink data, and alarm is "TRUE".
457 457  
458 - image 5.18 ui_water_leak.c (2) before modification
489 +[[image:image-20240705095149-5.png||height="164" width="162"]](% style="display:none" %)
459 459  
460 -[[image:image-20241122110815-29.png||height="725" width="712"]]
461 461  
462 - image 5.19 ui_water_leak.c (3) before modification
492 +== 2.8 LED Indicator ==
463 463  
464 -[[image:image-20241122113158-31.png||height="872" width="677"]]
465 465  
466 - image 5.20 ui_water_leak.c (1) after modification
495 +(((
496 +The PB01 has a triple color LED which for easy showing different stage.
497 +)))
467 467  
468 -[[image:image-20241122113259-33.png||height="874" width="724"]]
499 +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
469 469  
470 - image 5.21 ui_water_leak.c (2) after modification
501 +(((
502 +(% style="color:#037691" %)**In a normal working state**:
503 +)))
471 471  
472 -[[image:image-20241122113359-34.png||height="804" width="746"]]
505 +* 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" %)**.**
506 +* During OTAA Join:
507 +** **For each Join Request uplink:** the (% style="color:green" %)**GREEN LED** (%%)will blink once.
508 +** **Once Join Successful:** the (% style="color:green" %)**GREEN LED**(%%) will be solid on for 5 seconds.
509 +* After joined, for each uplink, the (% style="color:blue" %)**BLUE LED**(%%) or (% style="color:green" %)**GREEN LED** (%%)will blink once.
510 +* 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.
473 473  
474 - image 5.22 ui_water_leak.c (3) after modification
512 +(((
513 +
514 +)))
475 475  
476 -**10. Modify ui_water_leak_events.h file.** The image 5.23 show the code before modification, and the image 5.24 show the code after modification.
516 +== 2.9 Buzzer ==
477 477  
478 -[[image:image-20241122134113-35.png||height="380" width="421"]]
479 479  
480 - image 5.23 ui_water_leak_events_.h before modification
519 +The PB01 has** button sound** and** ACK sound** and users can turn on or off both sounds by using [[AT+SOUND>>||anchor="H3.3A0Setbuttonsoundandbuttonalarm"]].
481 481  
482 -[[image:image-20241122134420-37.png||height="201" width="283"]]
521 +* (% style="color:#4f81bd" %)**Button sound**(%%)** **is the music produced by the node after the alarm button is pressed.
483 483  
484 -image 5.24 ui_water_leak_events_.h after modification
523 + Users can use[[ AT+OPTION>>||anchor="H3.4A0Setbuzzermusic2807E429"]] to set different button sounds.
485 485  
486 -**11. Modify ui_water_leak_events.c file.** The image 5.25 show the code before modification, and the image 5.26 show the code after modification.
525 +* (% style="color:#4f81bd" %)**ACK sound **(%%)is the notification tone that the node receives ACK.
487 487  
488 -Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
527 += 3.  Configure PB01 via AT command or LoRaWAN downlink =
489 489  
490 -Step2. add code  below in delete_object() function definition.
491 491  
492 - panel_all * panel = find_upper_by_SensorPanel(&arr,((lv_obj_t *)(e->user_data~)~)~);
530 +Users can configure PB01 via AT Command or LoRaWAN Downlink.
493 493  
494 - size_t index = panel->panel_obj_index;
532 +* AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
495 495  
496 - deleteElement(&arr, index);
534 +* LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
497 497  
498 -[[image:image-20241122135023-38.png||height="358" width="372"]]
536 +There are two kinds of commands to configure PB01, they are:
499 499  
500 - image 5.25 ui_water_leak_events_.c before modification
538 +* (% style="color:#4f81bd" %)**General Commands:**
501 501  
502 -[[image:image-20241122135258-39.png||height="403" width="559"]]
540 +These commands are to configure:
503 503  
504 - image 5.26 ui_water_leak_events_.c after modification
542 +* General system settings like: uplink interval.
505 505  
544 +* LoRaWAN protocol & radio-related commands.
506 506  
507 -**12. Modify ui_water_leak_style.c file.**
546 +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]]
508 508  
509 -Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
510 510  
511 - add '#include "../../sort.h"'
549 +* (% style="color:#4f81bd" %)**Commands special design for PB01**
512 512  
513 - add '#include "ui.h"'
551 +These commands are only valid for PB01, as below:
514 514  
515 -[[image:image-20241122141536-41.png||height="361" width="612"]]
553 +(% style="display:none" %) (%%)
516 516  
517 - image 5.27 ui_water_leak_style.c (1) before modification
555 +== 3.1  Downlink Command Set ==
518 518  
519 -[[image:image-20241122142129-42.png||height="386" width="613"]]
520 520  
521 - image 5.28 ui_water_leak_style.c (1) after modification
558 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %)
559 +|=(% 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**
560 +|(% style="width:130px" %)AT+TDC=?|(% style="width:151px" %)(((
561 +
522 522  
563 +View current TDC time
564 +)))|(% style="width:92px" %)(((
565 +1200000
566 +OK
567 +)))|(% style="width:206px" %)Default 1200000(ms)
568 +|(% style="width:130px" %)AT+TDC=300000|(% style="width:151px" %)Set TDC time|(% style="width:92px" %)OK|(% style="width:206px" %)(((
569 +(((
570 +0X0100012C:
571 +01: fixed command
572 +00012C: 0X00012C=
523 523  
524 -Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
574 +300(seconds)
575 +)))
525 525  
526 - delete code as shown in image 5.29
577 +(((
578 +
579 +)))
580 +)))
581 +|(% style="width:130px" %)ATZ|(% style="width:151px" %)Reset node|(% style="width:92px" %) |(% style="width:206px" %)0x04FF
582 +|(% style="width:130px" %)AT+FDR|(% style="width:151px" %)Restore factory settings|(% style="width:92px" %) |(% style="width:206px" %)0X04FE
583 +|(% style="width:130px" %)AT+CFM=?|(% style="width:151px" %)View the current confirmation mode status|(% style="width:92px" %)(((
584 +0,7,0
527 527  
528 -[[image:image-20241122145620-44.png||height="757" width="671"]]
586 +OK
587 +)))|(% style="width:206px" %)Default 0,7,0
588 +|(% style="width:130px" %)AT+CFM=1,7,1|(% style="width:151px" %)(((
589 +Confirmed uplink mode, the maximum number of retries is seven, and uplink fcnt increase by 1 for each retry
590 +)))|(% style="width:92px" %)(((
591 +OK
592 +)))|(% style="width:206px" %)(((
593 +05010701
529 529  
530 - image 5.29 ui_water_leak_style.c (2)
595 +05: fixed command
531 531  
597 +01:confirmed uplink
532 532  
533 -Step3. The image 5.30, 5.31 show the change.
599 +07: retry 7 times
534 534  
535 -[[image:image-20241122152026-45.png||height="277" width="828"]]
601 +01: fcnt count plus 1
602 +)))
603 +|(% style="width:130px" %)AT+NJM=?|(% style="width:151px" %)(((
604 +Check the current network connection method
605 +)))|(% style="width:92px" %)(((
606 +1
607 +OK
608 +)))|(% style="width:206px" %)Default 1
609 +|(% style="width:130px" %)AT+NJM=0|(% style="width:151px" %)Change the network connection method to ABP|(% style="width:92px" %)(((
610 +Attention:Take effect after ATZ
611 +OK
612 +)))|(% style="width:206px" %)(((
613 +0X2000: ABP
614 +0x2001: OTAA
615 +20: fixed command
616 +)))
617 +|(% style="width:130px" %)AT+RPL=?|(% style="width:151px" %)View current RPL settings|(% style="width:92px" %)(((
618 +0
619 +OK
620 +)))|(% style="width:206px" %)Default 0
621 +|(% style="width:130px" %)AT+RPL=1|(% style="width:151px" %)set RPL=1    |(% style="width:92px" %)OK|(% style="width:206px" %)(((
622 +0x2101:
623 +21: fixed command
624 +01: for details, check wiki
625 +)))
626 +|(% style="width:130px" %)AT+ADR=?|(% style="width:151px" %)View current ADR status|(% style="width:92px" %)(((
627 +1
628 +OK
629 +)))|(% style="width:206px" %)Default 0
630 +|(% style="width:130px" %)AT+ADR=0|(% style="width:151px" %)Set the ADR state to off|(% style="width:92px" %)OK|(% style="width:206px" %)(((
631 +0x2200: close
632 +0x2201: open
633 +22: fixed command
634 +)))
635 +|(% style="width:130px" %)AT+DR=?|(% style="width:151px" %)View the current DR settings|(% style="width:92px" %)OK|(% style="width:206px" %)
636 +|(% style="width:130px" %)AT+DR=1|(% style="width:151px" %)(((
637 +set DR to 1
638 +It takes effect only when ADR=0
639 +)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
640 +0X22000101:
641 +00: ADR=0
642 +01: DR=1
643 +01: TXP=1
644 +22: fixed command
645 +)))
646 +|(% style="width:130px" %)AT+TXP=?|(% style="width:151px" %)View the current TXP|(% style="width:92px" %)OK|(% style="width:206px" %)
647 +|(% style="width:130px" %)AT+TXP=1|(% style="width:151px" %)(((
648 +set TXP to 1
649 +It takes effect only when ADR=0
650 +)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
651 +0X22000101:
652 +00: ADR=0
653 +01: DR=1
654 +01: TXP=1
655 +22: fixed command
656 +)))
657 +|(% style="width:130px" %)AT+RJTDC=10|(% style="width:151px" %)Set RJTDC time interval|(% style="width:92px" %)OK|(% style="width:206px" %)(((
658 +0X26000A:
659 +26: fixed command
660 +000A: 0X000A=10(min)
661 +for details, check wiki
662 +)))
663 +|(% style="width:130px" %) |(% style="width:151px" %)(((
664 +(((
665 +~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_
536 536  
537 - image 5.30 ui_water_leak_style.c (3) before modification
667 +Retrieve stored data for a specified period of time
668 +)))
538 538  
539 -[[image:image-20241122152542-46.png||height="293" width="830"]]
670 +(((
671 +
672 +)))
673 +)))|(% style="width:92px" %) |(% style="width:206px" %)(((
674 +0X3161DE7C7061DE8A800A:
675 +31: fixed command
676 +61DE7C70:0X61DE7C70=2022/1/12 15:00:00
677 +61DE8A80:0X61DE8A80=2022/1/12 16:00:00
678 +0A: 0X0A=10(second)
679 +View details 2.6.2
680 +)))
681 +|(% style="width:130px" %)AT+DDETECT=?|(% style="width:151px" %)View the current DDETECT setting status and time|(% style="width:92px" %)(((
682 +1,1440,2880
683 +OK
684 +)))|(% style="width:206px" %)Default 1,1440,2880(min)
685 +|(% style="width:130px" %)AT+DDETECT=(((
686 +1,1440,2880
687 +)))|(% style="width:151px" %)(((
688 +Set DDETECT setting status and time
689 +((% style="color:red" %)When the node does not receive the downlink packet within the set time, it will re-enter the network(%%))
690 +)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
691 +0X320005A0: close
692 +0X320105A0: open
693 +32: fixed command
694 +05A0: 0X05A0=1440(min)
695 +)))
540 540  
541 - image 5.31 ui_water_leak_style.c (3) after modification
697 +== 3.2  Set Password ==
542 542  
543 543  
544 -Step4. Copy partly the code in ui_water_leak.c, paste at extra_lib/sort.h(The process is shown in image 5.32, 5.33).
700 +Feature: Set device password, max 9 digits.
545 545  
546 -[[image:image-20241122153958-47.png]]
702 +(% style="color:#4f81bd" %)**AT Command: AT+PWORD**
547 547  
548 - image 5.32 ui_water_leak_style.c (4)
704 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
705 +|(% 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**
706 +|(% style="width:155px" %)AT+PWORD=?|(% style="width:124px" %)Show password|(% style="width:86px" %)(((
707 +123456
708 +OK
709 +)))
710 +|(% style="width:155px" %)AT+PWORD=999999|(% style="width:124px" %)Set password|(% style="width:86px" %)OK
549 549  
550 -[[image:image-20241122154755-49.png||height="864" width="513"]]
712 +(% style="color:#4f81bd" %)**Downlink Command:**
551 551  
552 - image 5.33 ui_water_leak_style.c (4)
714 +No downlink command for this feature.
553 553  
554 554  
555 -Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
717 +== 3.3  Set button sound and ACK sound ==
556 556  
557 -[[image:image-20241122155650-50.png||height="922" width="513"]]
558 558  
559 - image 5.34 ui_water_leak_style.c (5)
720 +Feature: Turn on/off button sound and ACK alarm.
560 560  
722 +(% style="color:#4f81bd" %)**AT Command: AT+SOUND**
561 561  
562 -Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
724 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
725 +|(% 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**
726 +|(% style="width:155px" %)(((
727 +AT+SOUND=?
728 +)))|(% style="width:124px" %)Get the current status of button sound and ACK sound|(% style="width:86px" %)(((
729 +1,1
730 +OK
731 +)))
732 +|(% style="width:155px" %)(((
733 +AT+SOUND=0,1
734 +)))|(% style="width:124px" %)Turn off the button sound and turn on ACK sound|(% style="width:86px" %)OK
563 563  
564 -[[image:image-20241122161934-51.png]]
736 +(% style="color:#4f81bd" %)**Downlink Command: 0xA1 **
565 565  
566 - image 5.35
738 +Format: Command Code (0xA1) followed by 2 bytes mode value.
567 567  
740 +The first byte after 0XA1 sets the button sound, and the second byte after 0XA1 sets the ACK sound.** (0: off, 1: on)**
568 568  
569 -Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
742 +* **Example: **Downlink Payload: A10001  ~/~/ Set AT+SOUND=0,1  Turn off the button sound and turn on ACK sound.
570 570  
571 -[[image:image-20241122162852-53.png||height="330" width="529"]]
572 572  
573 - image 5.37
745 +== 3.4  Set buzzer music type(0~~4) ==
574 574  
575 575  
576 -Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
748 +Feature: Set different alarm key response sounds.There are five different types of button music.
577 577  
578 -panel_with_type union_sensor;
750 +(% style="color:#4f81bd" %)**AT Command: AT+OPTION**
579 579  
580 -union_sensor.panel_type = WATER_LEAK_TYPE;
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
581 581  
582 -......
761 +OK
762 +)))
763 +|(% style="width:155px" %)AT+OPTION=1|(% style="width:124px" %)Set the buzzer music to type 1|(% style="width:86px" %)OK
583 583  
584 -lv_obj_set_x(union_sensor.panel_union.door.ui_PanelSensorDoor, x_by_index(index));
765 +(% style="color:#4f81bd" %)**Downlink Command: 0xA3**
585 585  
586 -lv_obj_set_y(union_sensor.panel_union.door.ui_PanelSensorDoor, y_by_index(index));
767 +Format: Command Code (0xA3) followed by 1 byte mode value.
587 587  
588 -return union_sensor;
769 +* **Example: **Downlink Payload: A300  ~/~/ Set AT+OPTION=0  Set the buzzer music to type 0.
589 589  
590 -[[image:image-20241122171211-54.png||height="635" width="792"]]
771 +== 3.5  Set Valid Push Time ==
591 591  
592 - image 5.38
593 593  
774 +Feature: Set the holding time for pressing the alarm button to avoid miscontact. Values range from** 0 ~~1000ms**.
594 594  
595 -**13. Modify sort.c file.**
776 +(% style="color:#4f81bd" %)**AT Command: AT+STIME**
596 596  
597 -Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
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
598 598  
599 -[[image:image-20241122173718-56.png||height="378" width="579"]]
792 +(% style="color:#4f81bd" %)**Downlink Command: 0xA2**
600 600  
601 - image 5.39 sort.c (1)
794 +Format: Command Code (0xA2) followed by 2 bytes mode value.
602 602  
603 -There are still some changes need to be done in sort.c, and omit here for the moment.
796 +* **Example: **Downlink Payload: A203E8  ~/~/ Set AT+STIME=1000  
604 604  
798 +**~ Explain: **Hold the alarm button for 10 seconds before the node will send the alarm packet.
605 605  
800 +
801 +
802 += 4.  Battery & How to replace =
803 +
804 +== 4.1  Battery Type and replace ==
805 +
806 +
807 +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.
808 +
809 +(% style="color:red" %)**Note: **
810 +
811 +1.  The PB01 doesn't have any screw, users can use nail to open it by the middle.
812 +
813 +[[image:image-20220621143535-5.png]]
814 +
815 +
816 +2.  Make sure the direction is correct when install the AAA batteries.
817 +
818 +[[image:image-20220621143535-6.png]]
819 +
820 +
821 +== 4.2  Power Consumption Analyze ==
822 +
823 +
824 +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.
825 +
826 +Instruction to use as below:
827 +
828 +(% style="color:blue" %)**Step 1**(%%):  Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
829 +
830 +[[battery calculator>>https://www.dropbox.com/sh/sxrgszkac4ips0q/AAA4XjBI3HAHNpdbU3ALN1j0a/Battery%20Document/Battery_Analyze?dl=0&subfolder_nav_tracking=1]]
831 +
832 +
833 +(% style="color:blue" %)**Step 2**(%%):  (% style="display:none" %) (%%)Open it and choose
834 +
835 +* Product Model
836 +* Uplink Interval
837 +* Working Mode
838 +
839 +And the Life expectation in difference case will be shown on the right.
840 +
841 +[[image:image-20220621143643-7.png||height="429" width="1326"]]
842 +
843 +
844 += 5.  Accessories =
845 +
846 +
847 +* (((
848 +(% class="wikigeneratedid" id="H5.2A0ProgramConverter28AS-0229" %)
849 +**Program Converter (AS-02)**
850 +)))
851 +
852 +AS-02 is an optional accessory, it is USB Type-C converter. AS-02 provide below feature:
853 +
854 +1. Access AT console of PB01 when used with USB-TTL adapter. [[See this link>>||anchor="H6.1HowtouseATCommandtoconfigurePB01"]].
855 +
856 +[[image:image-20220621141724-3.png]]
857 +
858 +
606 606  = 6. FAQ =
607 607  
608 -== 6.1 ==
861 +== 6.1 How to use AT Command to configure PB01 ==
609 609  
610 610  
864 +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.
865 +
866 +[[image:image-20240511085914-1.png||height="570" width="602"]]
867 +
868 +
869 +**Connection:**
870 +
871 +* (% style="background-color:yellow" %)USB to TTL GND <~-~-> Program Converter GND pin
872 +* (% style="background-color:yellow" %)USB to TTL RXD  <~-~-> Program Converter D+ pin
873 +* (% style="background-color:yellow" %)USB to TTL TXD  <~-~-> Program Converter A11 pin
874 +
875 +(((
876 +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.
877 +)))
878 +
879 +(((
880 +Input password and ATZ to activate PB01, as shown below:
881 +)))
882 +
883 +[[image:image-20240510174509-18.png||height="572" width="791"]]
884 +
885 +
886 +== 6.2  AT Command and Downlink ==
887 +
888 +
889 +(((
890 +Sending ATZ will reboot the node
891 +)))
892 +
893 +(((
894 +Sending AT+FDR will restore the node to factory settings
895 +)))
896 +
897 +(((
898 +Get the node's AT command setting by sending AT+CFG
899 +)))
900 +
901 +(((
902 +
903 +)))
904 +
905 +(((
906 +**Example：**                                           
907 +)))
908 +
909 +(((
910 +AT+DEUI=FA 23 45 55 55 55 55 51
911 +
912 +AT+APPEUI=FF AA 23 45 42 42 41 11
913 +
914 +AT+APPKEY=AC D7 35 81 63 3C B6 05 F5 69 44 99 C1 12 BA 95
915 +
916 +AT+DADDR=FFFFFFFF
917 +
918 +AT+APPSKEY=FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
919 +
920 +AT+NWKSKEY=FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
921 +
922 +AT+ADR=1
923 +
924 +AT+TXP=7
925 +
926 +AT+DR=5
927 +
928 +AT+DCS=0
929 +
930 +AT+PNM=1
931 +
932 +AT+RX2FQ=869525000
933 +
934 +AT+RX2DR=0
935 +
936 +AT+RX1DL=5000
937 +
938 +AT+RX2DL=6000
939 +
940 +AT+JN1DL=5000
941 +
942 +AT+JN2DL=6000
943 +
944 +AT+NJM=1
945 +
946 +AT+NWKID=00 00 00 13
947 +
948 +AT+FCU=61
949 +
950 +AT+FCD=11
951 +
952 +AT+CLASS=A
953 +
954 +AT+NJS=1
955 +
956 +AT+RECVB=0:
957 +
958 +AT+RECV=
959 +
960 +AT+VER=EU868 v1.0.0
961 +
962 +AT+CFM=0,7,0
963 +
964 +AT+SNR=0
965 +
966 +AT+RSSI=0
967 +
968 +AT+TDC=1200000
969 +
970 +AT+PORT=2
971 +
972 +AT+PWORD=123456
973 +
974 +AT+CHS=0
975 +
976 +AT+RX1WTO=24
977 +
978 +AT+RX2WTO=6
979 +
980 +AT+DECRYPT=0
981 +
982 +AT+RJTDC=20
983 +
984 +AT+RPL=0
985 +
986 +AT+TIMESTAMP=systime= 2024/5/11 01:10:58 (1715389858)
987 +
988 +AT+LEAPSEC=18
989 +
990 +AT+SYNCMOD=1
991 +
992 +AT+SYNCTDC=10
993 +
994 +AT+SLEEP=0
995 +
996 +AT+ATDC=1
997 +
998 +AT+UUID=003C0C53013259E0
999 +
1000 +AT+DDETECT=1,1440,2880
1001 +
1002 +AT+SETMAXNBTRANS=1,0
1003 +
1004 +AT+DISFCNTCHECK=0
1005 +
1006 +AT+DISMACANS=0
1007 +
1008 +AT+PNACKMD=0
1009 +
1010 +AT+SOUND=0,0
1011 +
1012 +AT+STIME=0
1013 +
1014 +AT+OPTION=3
1015 +)))
1016 +
1017 +(((
1018 +**Example：**
1019 +)))
1020 +
1021 +[[image:image-20240511091518-2.png||height="601" width="836"]]
1022 +
1023 +
1024 +== 6.3  How to upgrade the firmware? ==
1025 +
1026 +
1027 +PB01 requires a program converter to upload images to PB01, which is used to upload image to PB01 for:
1028 +
1029 +* Support new features
1030 +* For bug fix
1031 +* Change LoRaWAN bands.
1032 +
1033 + PB01 internal program is divided into bootloader and work program, shipping is included bootloader, the user can choose to directly update the work program.
1034 +
1035 +If the bootloader is erased for some reason, users will need to download the boot program and the work program.
1036 +
1037 +
1038 +=== 6.3.1 Update firmware (Assume device have bootloader) ===
1039 +
1040 +
1041 +(% style="color:blue" %)**Step 1**(%%):** Connect UART as per FAQ 6.1**
1042 +
1043 +(% 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]]. **
1044 +
1045 +
1046 +=== 6.3.2 Update firmware (Assume device doesn't have bootloader) ===
1047 +
1048 +
1049 +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.
1050 +
1051 +(% style="color:blue" %)**Step 1**(%%):** **Install [[TremoProgrammer>>url:https://www.dropbox.com/scl/fo/gk1rb5pnnjw4kv5m5cs0z/h?rlkey=906ouvgbvif721f9bj795vfrh&dl=0]]  first.
1052 +
1053 +[[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"]]
1054 +
1055 +(% style="color:blue" %)**Step 2**(%%): Hardware Connection
1056 +
1057 +Connect PC and PB01 via USB-TTL adapter .
1058 +
1059 +(% 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.**
1060 +
1061 +**Connection:**
1062 +
1063 +* (% style="background-color:yellow" %)USB-TTL GND <~-~-> Program Converter GND pin
1064 +* (% style="background-color:yellow" %)USB-TTL RXD  <~-~-> Program Converter D+ pin
1065 +* (% style="background-color:yellow" %)USB-TTL TXD  <~-~-> Program Converter A11 pin
1066 +* (% style="background-color:yellow" %)USB-TTL 3V3 <~-~-> Program Converter D- pin
1067 +
1068 +(% style="color:blue" %)**Step 3**(%%):** **Select the device port to be connected, baud rate and bin file to be downloaded.
1069 +
1070 +[[image:image-20240701160913-1.png]]
1071 +
1072 +Users need to reset the node to start downloading the program.
1073 +~1. Reinstall the battery to reset the node
1074 +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]] ).
1075 +
1076 +When this interface appears, it indicates that the download has been completed.
1077 +
1078 +[[image:image-20240701160924-2.png]]
1079 +
1080 +Finally, Disconnect Program Converter D- pin, reset the node again , and the node exits burning mode.
1081 +
1082 +
1083 +== 6.4  How to change the LoRa Frequency Bands/Region? ==
1084 +
1085 +
1086 +User can follow the introduction for [[how to upgrade image>>||anchor="H6.3A0Howtoupgradethefirmware3F"]]. When download the images, choose the required image file for download.
1087 +
1088 +
1089 +== 6.5 Why i see different working temperature for the device? ==
1090 +
1091 +
1092 +The working temperature range of device depends on the battery user choose.
1093 +
1094 +* Normal AAA Battery can support -10 ~~ 50°C working range.
1095 +* Special AAA battery can support -40 ~~ 60 °C working range. For example: [[Energizer L92>>https://data.energizer.com/pdfs/l92.pdf]]
1096 +
611 611  = 7. Order Info =
612 612  
613 -== 7.1  Part Number ==
1099 +== 7.1  Main Device ==
614 614  
615 615  
616 -Part Number: (% style="color:#4472c4" %)LTS5
1102 +Part Number: (% style="color:#4472c4" %)PB01-LW-XX(%%) (white button) / (% style="color:#4472c4" %)PB01-LR-XX(%%)(Red Button)
617 617  
1104 +(% style="color:#4472c4" %)**XX **(%%): The default frequency band
618 618  
619 -== 7.2  Packing Info ==
1106 +* (% style="color:red" %)**AS923**(%%)**: **LoRaWAN AS923 band
1107 +* (% style="color:red" %)**AU915**(%%)**: **LoRaWAN AU915 band
1108 +* (% style="color:red" %)**EU433**(%%)**: **LoRaWAN EU433 band
1109 +* (% style="color:red" %)**EU868**(%%)**:** LoRaWAN EU868 band
1110 +* (% style="color:red" %)**KR920**(%%)**: **LoRaWAN KR920 band
1111 +* (% style="color:red" %)**US915**(%%)**: **LoRaWAN US915 band
1112 +* (% style="color:red" %)**IN865**(%%)**:  **LoRaWAN IN865 band
1113 +* (% style="color:red" %)**CN470**(%%)**: **LoRaWAN CN470 band
620 620  
1115 += 7. Packing Info =
621 621  
1117 +
622 622  **Package Includes**:
623 623  
624 -* LTS5 HMI Touch Screen
625 -* 5V,2A DC Power Adapter.
626 -* USB Type C Program Cable
1120 +* PB01 LoRaWAN Push Button x 1
627 627  
628 628  = 8. Support =
629 629  
... ... @@ -634,9 +634,7 @@
634 634  = 9.  Reference material =
635 635  
636 636  
637 -* Datasheet
638 -* Source Code
639 -* Mechinical
1131 +* [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/scl/fo/y7pvm58wcr8319d5o4ujr/APZtqlbzRCNbHoPWTmmMMWs?rlkey=wfh93x2dhcev3ydn0846rinf0&st=kdp6lg7t&dl=0]]
640 640  
641 641  = 10. FCC Warning =
642 642  
1727229396732-319.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -197.2 KB
Content
1727229550717-684.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -113.9 KB
Content
1727229582471-566.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -73.6 KB
Content
1727229618724-758.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -118.7 KB
Content
1727229653254-680.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -116.2 KB
Content
1727229682537-381.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -51.5 KB
Content
1727229715361-392.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -75.2 KB
Content
1727229740592-843.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -87.3 KB
Content
1727229760857-521.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -24.7 KB
Content
1727229798126-306.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -53.6 KB
Content
1727229821582-258.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -76.1 KB
Content
1727229845835-509.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -68.3 KB
Content
1727229892636-154.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -192.0 KB
Content
1727229926561-300.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -178.0 KB
Content
1727229955611-607.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -100.4 KB
Content
1727229990795-405.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -383.6 KB
Content
1727230012478-930.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -477.1 KB
Content
1727231038705-173.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -94.6 KB
Content
1727233636007-933.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -114.8 KB
Content
1727484665746-713.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -94.9 KB
Content
1727485118799-984.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -11.8 KB
Content
1727485251053-655.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -20.4 KB
Content
1727485480434-713.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -24.7 KB
Content
1727485933579-550.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -55.6 KB
Content
1727485953726-175.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -91.6 KB
Content
1727486567182-334.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -42.6 KB
Content
1727486578489-774.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -66.0 KB
Content
1727487368023-281.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -28.5 KB
Content
1727488067077-684.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -604.7 KB
Content
1727488099947-341.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -877.7 KB
Content
1727488108117-780.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -877.7 KB
Content
1727488157579-949.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -877.7 KB
Content
image-20240916101737-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -156.7 KB
Content
image-20240925110638-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -262.7 KB
Content
image-20240928090825-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -30.2 KB
Content
image-20240928103357-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -153.7 KB
Content
image-20240928103506-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -197.7 KB
Content
image-20240928105309-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -80.2 KB
Content
image-20240928110211-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -228.0 KB
Content
image-20240928111412-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -150.9 KB
Content
image-20240928111654-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -105.4 KB
Content
image-20240928112001-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -75.6 KB
Content
image-20240928113424-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -50.8 KB
Content
image-20240928114139-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -114.3 KB
Content
image-20240928144830-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -25.5 KB
Content
image-20241121113445-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -250.0 KB
Content
image-20241121120222-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -44.8 KB
Content
image-20241121120830-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -42.6 KB
Content
image-20241121141120-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -41.7 KB
Content
image-20241121141315-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -29.4 KB
Content
image-20241121141329-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -29.4 KB
Content
image-20241121142925-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -14.8 KB
Content
image-20241121145915-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -61.0 KB
Content
image-20241121150911-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -73.0 KB
Content
image-20241121151934-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -32.9 KB
Content
image-20241121171629-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -16.9 KB
Content
image-20241121171901-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -17.2 KB
Content
image-20241121172714-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -26.4 KB
Content
image-20241121172908-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -27.1 KB
Content
image-20241121180030-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -27.7 KB
Content
image-20241121180517-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -26.5 KB
Content
image-20241121181957-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -59.3 KB
Content
image-20241121182239-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -71.3 KB
Content
image-20241122092239-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -270.9 KB
Content
image-20241122092655-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -251.6 KB
Content
image-20241122093445-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -128.9 KB
Content
image-20241122093601-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -120.0 KB
Content
image-20241122094200-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -289.2 KB
Content
image-20241122094320-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -182.4 KB
Content
image-20241122094600-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -136.0 KB
Content
image-20241122094719-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -129.5 KB
Content
image-20241122102929-27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -219.9 KB
Content
image-20241122104344-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -257.1 KB
Content
image-20241122110815-29.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -246.1 KB
Content
image-20241122112838-30.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -263.9 KB
Content
image-20241122113158-31.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -133.7 KB
Content
image-20241122113252-32.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -152.3 KB
Content
image-20241122113259-33.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -152.3 KB
Content
image-20241122113359-34.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -126.5 KB
Content
image-20241122134113-35.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -69.3 KB
Content
image-20241122134412-36.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
image-20241122134420-37.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
image-20241122135023-38.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -28.7 KB
Content
image-20241122135258-39.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -40.3 KB
Content
image-20241122141526-40.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
image-20241122141536-41.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
image-20241122142129-42.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -85.1 KB
Content
image-20241122143105-43.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -60.2 KB
Content
image-20241122145620-44.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -394.0 KB
Content
image-20241122152026-45.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -201.6 KB
Content
image-20241122152542-46.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -95.3 KB
Content
image-20241122153958-47.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -241.1 KB
Content
image-20241122154745-48.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -135.7 KB
Content
image-20241122154755-49.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -135.7 KB
Content
image-20241122155650-50.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -104.4 KB
Content
image-20241122161934-51.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -230.3 KB
Content
image-20241122162612-52.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -58.7 KB
Content
image-20241122162852-53.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -125.5 KB
Content
image-20241122171211-54.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -173.3 KB
Content
image-20241122173706-55.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -37.6 KB
Content
image-20241122173718-56.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.xieby
Size
... ... @@ -1,1 +1,0 @@
1 -37.6 KB
Content
squalreline-trial.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -60.4 KB
Content
squareline.io_downloads.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -1.5 MB
Content