Skip to Content
Last modified by BoYang Xie on 2025/07/24 16:47
From version 123.1
edited by Dilisi S
on 2024/12/24 04:36
Change comment: Dec 23 edits - Part 1
To version 4.1
edited by Edwin Chen
on 2024/09/15 23:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.pradeeka
1 +XWiki.Edwin
Content
... ... @@ -1,14 +1,9 @@
1 -(% style="text-align:center" %)
1 +
2 2  [[image:image-20240915231842-1.png]]
3 3  
4 4  
5 -
6 -
7 -
8 -
9 -
10 10  (% _mstvisible="1" %)
11 -(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:**
6 +(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents：**
12 12  
13 13  {{toc/}}
14 14  
... ... @@ -21,77 +21,59 @@
21 21  
22 22  = 1.  Introduction =
23 23  
24 -== 1.1  What is the LTS5 LoRa HMI Touch Screen? ==
19 +== 1.1  What is LTS5 LoRa HMI touch screen ==
25 25  
21 +LTS5 is a (% style="color:blue" %)LoRa / LoRaWAN HMI Touch Screen(%%) designed for display purpose of IoT project. It have a 5.0" HMI touch screen, and support WiFi, Bluetooch, LoRa wireless protocol.
26 26  
27 -The LTS5 is a (% style="color:blue" %)**LoRa / LoRaWAN HMI Touch Screen**(%%) designed for displaying information in IoT projects. It features a **5.0-inch HMI touch screen** and supports **Wi-Fi**, **Bluetooth**, and **LoRa** wireless protocols.
23 +LTS5 is an Open Source software project. The MCU is ESP32 and Dragino LA66 LoRa module. There are lots of development source for ESP32 which can greatly reduce the development time.
28 28  
29 -The LTS5 is an open-source software project powered by an **ESP32 MCU** and a **Dragino LA66 LoRa** module. The extensive development resources available for ESP32 can significantly reduce development time.
25 +The HMI touch screen of LTS5 supports drap & drop design. Developer can use SquareLine to easily customize the UI.
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.
32 32  
33 -The LA66 LoRa module can be programmed to support either private LoRa protocols or the LoRaWAN protocol.
34 -
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
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.
48 48  * IP Rating: IP52
49 49  
50 -== 1.3  Specifications ==
43 +== 1.3  Specification ==
51 51  
52 52  
53 -**LoRa**:
46 +**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
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"]])
61 61  
62 -**WiFi:**
53 +**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
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)
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
63 +PB01 : Idle: 5uA, Transmit: max 110mA
88 88  
65 +
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)
69 +-10 ~~ 50 °C  or -40 ~~ 60 °C (depends on battery type, see [[FAQ>>||anchor="H6.5Whyiseedifferentworkingtemperatureforthedevice3F"]])
94 94  
71 +
95 95  == 1.6  Applications ==
96 96  
97 97  
... ... @@ -102,515 +102,1036 @@
102 102  * Smart Cities
103 103  * Smart Factory
104 104  
105 -= 2.  Getting Started with 'Hello World' =
82 += 2.  Operation Mode =
106 106  
107 -== 2.1  About this demo ==
84 +== 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:
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**.
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.
90 +== 2.2  How to Activate PB01? ==
117 117  
118 118  
119 -== 2.2  Install Software Running Environment ==
93 +(% style="color:red" %)** 1.  Open enclosure from below position.**
120 120  
95 +[[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  
98 +(% 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 ===
100 +[[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]].
103 +(% 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.
105 +[[image:image-20220621093835-3.png]]
131 131  
132 132  
133 -[[image:image-20240928110211-5.png||height="508" width="866"]]
108 +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]]
111 +== 2.3  Example to join LoRaWAN network ==
138 138  
139 139  
140 -=== 2.2.2 Install SquareLine Studio ===
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.
141 141  
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. 
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.4.2.
119 +[[image:image-20240705094824-4.png]]
144 144  
145 -[[image:squareline.io_downloads.png]]
121 +(% style="color:blue" %)**Step 1**(%%):  Create a device in TTN V3 with the OTAA keys from PB01.
146 146  
123 +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:
125 +[[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 ==
128 +Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
157 157  
130 +Create application.
158 158  
159 -After launching and logging into the software, create a new project as shown in Image 2.
132 +choose to create the device manually.
160 160  
161 -* Select the major **LVGL** version as **8.3**.
162 -* Select the **Desktop** tab.
163 -* Select  **Eclipse with  SDL for  development on PC**:
164 -* In the **PROJECT SETTINGS**, select **LVGL version** **8.3.11**
165 -* Select the **CREATE **button.
134 +Add JoinEUI(AppEUI), DevEUI, AppKey.(% style="display:none" %)
166 166  
167 -[[image:image-20240928103357-2.png||height="680" width="708"]]
136 +[[image:image-20240507142116-1.png||height="410" width="1138"]](% style="display:none" %) (%%)
137 +
168 168  
169 - Image 2: Creating a new SquareLine project
139 +[[image:image-20240507142157-2.png||height="559" width="1147"]]
170 170  
141 +[[image:image-20240507142401-3.png||height="693" width="1202"]]
171 171  
172 -Next, you need to configure some settings for this project. By clicking in the specified order shown in Image 3, you will be directed to the page displayed in Image 4.
143 +[[image:image-20240507142651-4.png||height="760" width="1190"]]
173 173  
174 -* Select** File  -> Project Settings**
145 +**Default mode OTAA**(% style="display:none" %)
175 175  
176 -[[image:1727229582471-566.png]]
177 177  
178 - Image 3 accessing project settings
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.
179 179  
150 +[[image:image-20240507143104-5.png||height="434" width="1398"]]
180 180  
181 -In the PROJECT SETTINGS dialog box, configure/modify the project settings:
182 182  
183 -* **UI Files Export Root**: Select a folder on your computer to store the UI files.
184 -* **LVGL Include Path**: Set this to **lvgl.h**
185 -* **Click on the APPLY CHANGES button.**
153 +== 2.4  Uplink Payload ==
186 186  
187 -[[image:image-20240928105309-4.png||height="526" width="556"]]
188 188  
189 - Image 4 Configure/modify project settings
156 +Uplink payloads include two types: Valid Sensor Value and other status / control command.
190 190  
158 +* Valid Sensor Value: Use FPORT=2
159 +* Other control command: Use FPORT other than 2.
191 191  
192 -Now you can start building the sample UI. Follow the steps below:
161 +=== 2.4.1  Uplink FPORT~=5, Device Status ===
193 193  
194 194  
195 -=== Add widgets ===
164 +Users can  get the Device Status uplink through the downlink command:
196 196  
197 -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.
166 +(% style="color:#4472c4" %)**Downlink:  **(%%)**0x2601**
198 198  
199 -Add a Label, Button, and Image to the screen as shown in **Image 5**.
168 +Uplink the device configures with FPORT=5.
200 200  
201 -[[image:image-20240928111412-6.png||height="526" width="864"]]
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
202 202  
203 - Image 5: Add widgets
174 +[[image:image-20240507152130-12.png||height="469" width="1366"]](% style="display:none" %)
204 204  
205 -=== Modify widget properties ===
176 +Example Payload (FPort=5):  [[image:image-20240507152254-13.png||height="26" width="130"]]
206 206  
207 -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.
208 208  
209 -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.
179 +(% style="color:#4472c4" %)**Sensor Model**(%%): For PB01, this value is 0x35.
210 210  
211 -[[image:1727485118799-984.png]]
181 +(% style="color:#4472c4" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version.
212 212  
213 - Image 6: The button widget's "Inspector" tab
183 +(% style="color:#4472c4" %)**Frequency Band**:
214 214  
185 +*0x01: EU868
215 215  
216 -==== Changing the Button properties ====
187 +*0x02: US915
217 217  
218 -Click the Button.
189 +*0x03: IN865
219 219  
220 -Under the "Layout" you can change the button's position and size.
191 +*0x04: AU915
221 221  
222 -[[image:1727485251053-655.png]]
193 +*0x05: KZ865
223 223  
224 -Image 7: The button widget's "BUTTON" tab
195 +*0x06: RU864
225 225  
197 +*0x07: AS923
226 226  
227 -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.
199 +*0x08: AS923-1
228 228  
229 -* Click **ADD EVENT** button.
230 -* Select **CLICKED** under the Trigger.
231 -* Select **Screen2** from **Screen to**.
232 -* Select **FADE ON** from **Fade mode**.
233 -* Enter **500** in the **Speed** text box.
234 -* Finally, click **ADD** button.
201 +*0x09: AS923-2
235 235  
236 -[[image:1727485480434-713.png||height="395" width="290"]]
203 +*0x0a: AS923-3
237 237  
238 - Image 8: Add an event for the button
239 239  
206 +(% style="color:#4472c4" %)**Sub-Band**(%%): value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
240 240  
241 -==== Changing the label properties ====
208 +(% style="color:#4472c4" %)**BAT**(%%): shows the battery voltage for PB01.
242 242  
243 -Click the label. Under the **Label** section, type "Click For Detail" in the **Text** textbox.
210 +(% style="color:#4472c4" %)**Ex1**(%%): 0x0C DE = 3294mV
244 244  
245 245  
246 -[[image:image-20240928090825-1.png||height="327" width="391"]]
213 +=== 2.4.2  Uplink FPORT~=2, Real time sensor value ===
247 247  
248 - Image 9:  Modify text of label widget
249 249  
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"]].
250 250  
251 -==== 4. Changing image properties ====
218 +Uplink uses FPORT=2 and every 20 minutes send one uplink by default.
252 252  
253 -To use the image widget, you should first add an image to your project. The image format must be PNG, and its resolution should not exceed 800x480 pixels. There are two ways to add an image file. 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.
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
254 254  
255 -[[image:image-20240928113424-9.png||height="355" width="505"]]
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 +)))
256 256  
257 - image 10 add image file into SquareLine Studio project
250 +Example in TTN.
258 258  
259 -[[image:image-20240928114139-10.png||height="559" width="810"]]
252 +[[image:image-20240507150155-11.png||height="549" width="1261"]]
260 260  
261 - image 11 use image widget in SquareLine Studio
254 +Example Payload (FPort=2):  (% style="background-color:yellow" %)**0C EA 03 01 01 11 02 A8**
262 262  
256 +==== (% style="color:blue" %)**Battery:**(%%) ====
263 263  
264 -==== 5. The relationship between widgets ====
258 +Check the battery voltage.
265 265  
266 -Widgets commonly have two types of relationships: **parallel** and **parent-child**.
260 +* Ex1: 0x0CEA = 3306mV
261 +* Ex2: 0x0D08 = 3336mV
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.
263 +==== (% style="color:blue" %)**Sound_ACK & Sound_key:**(%%) ====
270 270  
271 -[[image:1727486567182-334.png||height="318" width="278"]]
265 +Key sound and ACK sound are enabled by default.
272 272  
267 +* Example1: 0x03
273 273  
274 -Move **Label1** to make it a child of **Button1**. See Image 13.
269 + Sound_ACK: (03>>1) & 0x01=1, OPEN.
275 275  
276 -[[image:image-20240928112001-8.png||height="431" width="796"]]
271 +**~ ** Sound_key:  03 & 0x01=1, OPEN.
277 277  
278 - Image 13: Move Label1 to make it a child of Button1.
273 +* Example2: 0x01
279 279  
275 + Sound_ACK: (01>>1) & 0x01=0, CLOSE.
280 280  
281 -**6. Preview the screen**
277 +**~ ** Sound_key:  01 & 0x01=1, OPEN.
282 282  
283 -You can test the result by clicking on the **PLAY** button. The screen will change into play mode. See Image 14.
284 284  
285 -[[image:1727487368023-281.png]]
280 +==== (% style="color:blue" %)**Alarm:**(%%) ====
286 286  
287 - Image 14: Simulating the project
282 +Key alarm.
288 288  
284 +* Ex1: 0x01 & 0x01=1, TRUE.
285 +* Ex2: 0x00 & 0x01=0, FALSE.
289 289  
290 -For more information, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
287 +==== (% style="color:blue" %)**Temperature:**(%%) ====
291 291  
289 +* Example1:  0x0111/10=27.3℃
290 +* Example2:  (0xFF0D-65536)/10=-24.3℃
292 292  
293 -== 2.4 Integrate UI Code to ESP-IDF Project ==
292 +If payload is: FF0D :  (FF0D & 8000 == 1) , temp = (FF0D - 65536)/100 =-24.3℃
294 294  
294 +（FF0D & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative）
295 295  
296 -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.
297 297  
298 -[[image:1727229798126-306.png]]
297 +==== (% style="color:blue" %)**Humidity:**(%%) ====
299 299  
300 - image 15 export UI file
299 +* Humidity:    0x02A8/10=68.0%
301 301  
302 -[[image:1727229821582-258.png||height="333" width="662"]]
301 +=== 2.4.3  Uplink FPORT~=3, Datalog sensor value ===
303 303  
304 - image 16 exported UI file
305 305  
306 -Create a empty directory entitled "ui" in path "basic_prj/app_components/ui/", and then copy all UI code exported to this directory.
304 +PB01 stores sensor value and user can retrieve these history value via downlink command. The Datalog sensor value are sent via FPORT=3.
307 307  
308 -[[image:image-20240928144830-11.png]]
306 +[[image:image-20240510144912-1.png||height="471" width="1178"]](% style="display:none" %)
309 309  
310 - image 17 open CMakeLists.txt
311 311  
312 -[[image:1727229892636-154.png||height="521" width="407"]]
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" %)
313 313  
314 - image 18 modify CMakeLists.txt
311 +For example, in US915 band, the max payload for different DR is:
315 315  
316 -The last step of integrating is adding two lines of code in main.c file.
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 -[[image:1727229926561-300.png]]
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.**
319 319  
320 - image 19 add "ui.h"
320 +See more info about the [[Datalog feature>>||anchor="H2.6A0DatalogFeature"]].
321 321  
322 -[[image:1727229955611-607.png]]
322 +(% style="display:none" %) (%%)
323 323  
324 - image 20 add "ui_init()"
324 +=== 2.4.4  Decoder in TTN V3 ===
325 325  
326 326  
327 -== 2.5 Brief introduction of hello world project ==
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.
328 328  
329 +In TTN , add formatter as below:
329 329  
330 -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.
331 +[[image:image-20240507162814-16.png||height="778" width="1135"]]
331 331  
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 +)))
332 332  
333 -== 2.6 Test Result ==
337 +(((
338 +
339 +)))
334 334  
341 +== 2.5 Show data on Datacake ==
335 335  
336 -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.
337 337  
338 -[[image:1727488067077-684.png||height="402" width="574"]]
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 +)))
339 339  
340 - image 21 screen1
348 +(((
349 +
350 +)))
341 341  
342 -[[image:1727488157579-949.png||height="397" width="572"]]
352 +(((
353 +(% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the LoRaWAN network.
354 +)))
343 343  
344 - image 22 screen2
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 +)))
345 345  
360 +(((
361 +~1. Add Datacake:
362 +)))
346 346  
347 -= 3. Example Project 1: LoRa Central Display =
364 +(((
365 +2. Select default key as Access Key:
366 +)))
348 348  
349 -[[image:image-20240916101737-1.png||height="468" width="683"]]
368 +(((
369 +3. In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add PB01:
370 +)))
350 350  
372 +(((
373 + Please refer to the figure below.
374 +)))
351 351  
352 -= 4. Example Project 2: LoRaWAN RS485 Alarm =
376 +[[image:image-20240510150924-2.png||height="612" width="1186"]]
353 353  
354 -= 5.  The way to add a new panel to project =
355 355  
356 -**~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.**
379 +Log in to DATACAKE, copy the API under the account.
357 357  
358 -[[image:image-20241121113445-1.png||height="584" width="934"]]
381 +[[image:image-20240510151944-3.png||height="581" width="1191"]]
359 359  
360 - image 5.1 a panel about water_leak
361 361  
362 -**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.
363 363  
364 -[[image:image-20241121141120-4.png||height="383" width="795"]]
385 +[[image:image-20240510152150-4.png||height="697" width="1188"]]
365 365  
366 - image 5.2 ui files exported
367 367  
368 -**3. Delete or rename some file.** Here are the steps:
388 +[[image:image-20240510152300-5.png||height="298" width="1191"]]
369 369  
370 - Step1 Delete the 'components' directory.
371 - Step2 Delete 'filelist.txt'.
372 - Step3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
373 - Step4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
374 - Step5 Rename the 'screens' directory to 'styles'.
375 375  
376 -[[image:image-20241121151934-10.png||height="303" width="792"]]
391 +[[image:image-20240510152355-6.png||height="782" width="1193"]]
377 377  
378 - image 5.3 rest file (1)
393 +[[image:image-20240510152542-8.png||height="545" width="739"]]
379 379  
380 -[[image:image-20241121142925-7.png||height="141" width="793"]]
395 +[[image:image-20240510152634-9.png||height="748" width="740"]]
381 381  
382 - image 5.4 rest file (2)
383 383  
384 -**4. Open this project in vscode.**
398 +[[image:image-20240510152809-10.png||height="607" width="732"]]
385 385  
386 -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.
400 +[[image:image-20240510153934-14.png||height="460" width="1199"]]
387 387  
388 -[[image:image-20241121181957-17.png||height="438" width="516"]]
389 389  
390 - image 5.5 extra_lib/CMakeLists.txt before add
403 +[[image:image-20240510153435-12.png||height="428" width="1197"]]
391 391  
392 -[[image:image-20241121182239-18.png||height="520" width="518"]]
393 393  
394 - image 5.6 extra_lib/CMakeLists.txt after add
406 +Copy and paste the [[TTN decoder>>https://github.com/dragino/dragino-end-node-decoder]] here and save.
395 395  
396 -**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.
408 +[[image:image-20240510153624-13.png||height="468" width="1195"]]
397 397  
398 -[[image:image-20241121171629-11.png]]
399 399  
400 - image 5.7 before-modified font file
411 +Visual widgets please read the DATACAKE documentation.
401 401  
402 -[[image:image-20241121171901-12.png]]
413 +(% style="display:none" %) (%%)
403 403  
404 - image 5.8 modified font file
415 +== 2.6  Datalog Feature ==
405 405  
406 -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.
407 407  
408 -[[image:image-20241121172714-13.png]]
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.
409 409  
410 - image 5.9 before-modified image file
411 411  
412 -[[image:image-20241121172908-14.png]]
422 +=== 2.6.1  Unix TimeStamp ===
413 413  
414 - image 5.10 modified image file
415 415  
416 -**7. Modify the ui_water_leak/CMakeLists.txt.** Open this file, and modify it from image 5.11 to image 5.12.
425 +Unix TimeStamp shows the sampling time of uplink payload. format base on
417 417  
418 -[[image:image-20241121180030-15.png]]
427 +[[image:image-20220523001219-11.png||_mstalt="450450" _mstvisible="3" height="97" width="627"]]
419 419  
420 - image 5.11 ui_water_leak/CMakeLists.txt before modification
429 +User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/||_mstvisible="3"]] :
421 421  
422 -[[image:image-20241121180517-16.png]]
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)
423 423  
424 - image 5.12 ui_water_leak/CMakeLists.txt after modification
425 425  
426 -**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.
434 +[[image:1655782409139-256.png]]
427 427  
428 -[[image:image-20241122094200-23.png]]
429 429  
430 - image 5.13 ui_water_leak.h (1) before modification
437 +=== 2.6.2  Poll sensor value ===
431 431  
432 -[[image:image-20241122094320-24.png||height="852" width="554"]]
433 433  
434 - image 5.14 ui_water_leak.h (2) before modification
440 +(((
441 +User can poll sensor value based on timestamps from the server. Below is the downlink command.
442 +)))
435 435  
436 -[[image:image-20241122094600-25.png||height="1078" width="554"]]
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 +)))
437 437  
438 - image 5.15 ui_water_leak.h (1) after modification
448 +(((
449 +For example, downlink command [[image:image-20220621113526-13.png]] (% _mstvisible="3" style="display:none" %)
450 +)))
439 439  
440 -[[image:image-20241122094719-26.png||height="941" width="583"]]
452 +(((
453 +Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00's data
454 +)))
441 441  
442 - image 5.16 ui_water_leak.h (2) before modification
456 +(((
457 +Uplink Internal =5s，means PB01 will send one packet every 5s. range 5~~255s.
458 +)))
443 443  
444 -**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.
445 445  
446 -_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.
461 +=== 2.6.3  Datalog Uplink payload ===
447 447  
448 -[[image:image-20241122102929-27.png||height="619" width="426"]]
449 449  
450 - image 5.17 ui_water_leak.c (1) before modification
464 +See [[Uplink FPORT=3, Datalog sensor value>>||anchor="H2.4.3A0UplinkFPORT3D32CDatalogsensorvalue"]]
451 451  
452 -[[image:image-20241122112838-30.png||height="551" width="628"]]
466 +(% style="display:none" %) (%%) (% style="display:none" %)
453 453  
454 - image 5.18 ui_water_leak.c (2) before modification
468 +== 2.7 Button ==
455 455  
456 -[[image:image-20241122110815-29.png||height="725" width="712"]]
457 457  
458 - image 5.19 ui_water_leak.c (3) before modification
471 +* ACT button
459 459  
460 -[[image:image-20241122113158-31.png||height="872" width="677"]]
473 +Long press this button PB01 will reset and join network again.
461 461  
462 - image 5.20 ui_water_leak.c (1) after modification
475 +[[image:image-20240510161626-17.png||height="192" width="224"]]
463 463  
464 -[[image:image-20241122113259-33.png||height="874" width="724"]]
477 +* Alarm button
465 465  
466 - image 5.21 ui_water_leak.c (2) after modification
479 +Press the button PB01 will immediately uplink data, and alarm is "TRUE".
467 467  
468 -[[image:image-20241122113359-34.png||height="804" width="746"]]
481 +[[image:image-20240705095149-5.png||height="164" width="162"]](% style="display:none" %)
469 469  
470 - image 5.22 ui_water_leak.c (3) after modification
471 471  
472 -**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.
484 +== 2.8 LED Indicator ==
473 473  
474 -[[image:image-20241122134113-35.png||height="380" width="421"]]
475 475  
476 - image 5.23 ui_water_leak_events_.h before modification
487 +(((
488 +The PB01 has a triple color LED which for easy showing different stage.
489 +)))
477 477  
478 -[[image:image-20241122134420-37.png||height="201" width="283"]]
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
479 479  
480 -image 5.24 ui_water_leak_events_.h after modification
493 +(((
494 +(% style="color:#037691" %)**In a normal working state**:
495 +)))
481 481  
482 -**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.
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.
483 483  
484 -Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
504 +(((
505 +
506 +)))
485 485  
486 -Step2. add code  below in delete_object() function definition.
508 +== 2.9 Buzzer ==
487 487  
488 - panel_all * panel = find_upper_by_SensorPanel(&arr,((lv_obj_t *)(e->user_data~)~)~);
489 489  
490 - size_t index = panel->panel_obj_index;
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"]].
491 491  
492 - deleteElement(&arr, index);
513 +* (% style="color:#4f81bd" %)**Button sound**(%%)** **is the music produced by the node after the alarm button is pressed.
493 493  
494 -[[image:image-20241122135023-38.png||height="358" width="372"]]
515 + Users can use[[ AT+OPTION>>||anchor="H3.4A0Setbuzzermusic2807E429"]] to set different button sounds.
495 495  
496 - image 5.25 ui_water_leak_events_.c before modification
517 +* (% style="color:#4f81bd" %)**ACK sound **(%%)is the notification tone that the node receives ACK.
497 497  
498 -[[image:image-20241122135258-39.png||height="403" width="559"]]
519 += 3.  Configure PB01 via AT command or LoRaWAN downlink =
499 499  
500 - image 5.26 ui_water_leak_events_.c after modification
501 501  
502 -**12. Modify ui_water_leak_style.c file.**
522 +Users can configure PB01 via AT Command or LoRaWAN Downlink.
503 503  
504 -Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
524 +* AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
505 505  
506 - add '#include "../../sort.h"'
526 +* LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
507 507  
508 - add '#include "ui.h"'
528 +There are two kinds of commands to configure PB01, they are:
509 509  
510 -[[image:image-20241122141536-41.png||height="361" width="612"]]
530 +* (% style="color:#4f81bd" %)**General Commands:**
511 511  
512 - image 5.27 ui_water_leak_style.c (1) before modification
532 +These commands are to configure:
513 513  
514 -[[image:image-20241122142129-42.png||height="386" width="613"]]
534 +* General system settings like: uplink interval.
515 515  
516 - image 5.28 ui_water_leak_style.c (1) after modification
536 +* LoRaWAN protocol & radio-related commands.
517 517  
518 -Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
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]]
519 519  
520 - delete code as shown in image 5.29
521 521  
522 -[[image:image-20241122145620-44.png||height="757" width="671"]]
541 +* (% style="color:#4f81bd" %)**Commands special design for PB01**
523 523  
524 - image 5.29 ui_water_leak_style.c (2)
543 +These commands are only valid for PB01, as below:
525 525  
526 -Step3. The image 5.30, 5.31 show the change.
545 +(% style="display:none" %) (%%)
527 527  
528 -[[image:image-20241122152026-45.png||height="277" width="828"]]
547 +== 3.1  Downlink Command Set ==
529 529  
530 - image 5.30 ui_water_leak_style.c (3) before modification
531 531  
532 -[[image:image-20241122152542-46.png||height="293" width="830"]]
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 +
533 533  
534 - image 5.31 ui_water_leak_style.c (3) after modification
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=
535 535  
536 -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).
566 +300(seconds)
567 +)))
537 537  
538 -[[image:image-20241122153958-47.png]]
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
539 539  
540 - image 5.32 ui_water_leak_style.c (4)
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
541 541  
542 -[[image:image-20241122154755-49.png||height="864" width="513"]]
587 +05: fixed command
543 543  
544 - image 5.33 ui_water_leak_style.c (4)
589 +01:confirmed uplink
545 545  
546 -Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
591 +07: retry 7 times
547 547  
548 -[[image:image-20241122155650-50.png||height="922" width="513"]]
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 +~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_
549 549  
550 - image 5.34 ui_water_leak_style.c (5)
659 +Retrieve stored data for a specified period of time
660 +)))
551 551  
552 -Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
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 +)))
553 553  
554 -[[image:image-20241122161934-51.png]]
689 +== 3.2  Set Password ==
555 555  
556 - image 5.35
557 557  
558 -Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
692 +Feature: Set device password, max 9 digits.
559 559  
560 -[[image:image-20241122162852-53.png||height="330" width="529"]]
694 +(% style="color:#4f81bd" %)**AT Command: AT+PWORD**
561 561  
562 - image 5.37
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
563 563  
564 -Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
704 +(% style="color:#4f81bd" %)**Downlink Command:**
565 565  
566 -panel_with_type union_sensor;
706 +No downlink command for this feature.
567 567  
568 -union_sensor.panel_type = WATER_LEAK_TYPE;
569 569  
570 -......
709 +== 3.3  Set button sound and ACK sound ==
571 571  
572 -lv_obj_set_x(union_sensor.panel_union.door.ui_PanelSensorDoor, x_by_index(index));
573 573  
574 -lv_obj_set_y(union_sensor.panel_union.door.ui_PanelSensorDoor, y_by_index(index));
712 +Feature: Turn on/off button sound and ACK alarm.
575 575  
576 -return union_sensor;
714 +(% style="color:#4f81bd" %)**AT Command: AT+SOUND**
577 577  
578 -[[image:image-20241122171211-54.png||height="635" width="792"]]
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
579 579  
580 - image 5.38
728 +(% style="color:#4f81bd" %)**Downlink Command: 0xA1 **
581 581  
582 -**13. Modify sort.c file.**
730 +Format: Command Code (0xA1) followed by 2 bytes mode value.
583 583  
584 -Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
732 +The first byte after 0XA1 sets the button sound, and the second byte after 0XA1 sets the ACK sound.** (0: off, 1: on)**
585 585  
586 -[[image:image-20241122173718-56.png||height="378" width="579"]]
734 +* **Example: **Downlink Payload: A10001  ~/~/ Set AT+SOUND=0,1  Turn off the button sound and turn on ACK sound.
587 587  
588 - image 5.39 sort.c (1)
736 +== 3.4  Set buzzer music type(0~~4) ==
589 589  
590 -There are still some changes need to be done in sort.c, and omit here for the moment.
591 591  
739 +Feature: Set different alarm key response sounds.There are five different types of button music.
592 592  
741 +(% style="color:#4f81bd" %)**AT Command: AT+OPTION**
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
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
755 +
756 +(% style="color:#4f81bd" %)**Downlink Command: 0xA3**
757 +
758 +Format: Command Code (0xA3) followed by 1 byte mode value.
759 +
760 +* **Example: **Downlink Payload: A300  ~/~/ Set AT+OPTION=0  Set the buzzer music to type 0.
761 +
762 +== 3.5  Set Valid Push Time ==
763 +
764 +
765 +Feature: Set the holding time for pressing the alarm button to avoid miscontact. Values range from** 0 ~~1000ms**.
766 +
767 +(% style="color:#4f81bd" %)**AT Command: AT+STIME**
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
782 +
783 +(% style="color:#4f81bd" %)**Downlink Command: 0xA2**
784 +
785 +Format: Command Code (0xA2) followed by 2 bytes mode value.
786 +
787 +* **Example: **Downlink Payload: A203E8  ~/~/ Set AT+STIME=1000  
788 +
789 +**~ Explain: **Hold the alarm button for 10 seconds before the node will send the alarm packet.
790 +
791 +
792 +
793 += 4.  Battery & How to replace =
794 +
795 +== 4.1  Battery Type and replace ==
796 +
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.
799 +
800 +(% style="color:red" %)**Note: **
801 +
802 +1.  The PB01 doesn't have any screw, users can use nail to open it by the middle.
803 +
804 +[[image:image-20220621143535-5.png]]
805 +
806 +
807 +2.  Make sure the direction is correct when install the AAA batteries.
808 +
809 +[[image:image-20220621143535-6.png]]
810 +
811 +
812 +== 4.2  Power Consumption Analyze ==
813 +
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.
816 +
817 +Instruction to use as below:
818 +
819 +(% style="color:blue" %)**Step 1**(%%):  Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
820 +
821 +[[battery calculator>>https://www.dropbox.com/sh/sxrgszkac4ips0q/AAA4XjBI3HAHNpdbU3ALN1j0a/Battery%20Document/Battery_Analyze?dl=0&subfolder_nav_tracking=1]]
822 +
823 +
824 +(% style="color:blue" %)**Step 2**(%%):  (% style="display:none" %) (%%)Open it and choose
825 +
826 +* Product Model
827 +* Uplink Interval
828 +* Working Mode
829 +
830 +And the Life expectation in difference case will be shown on the right.
831 +
832 +[[image:image-20220621143643-7.png||height="429" width="1326"]]
833 +
834 +
835 += 5.  Accessories =
836 +
837 +
838 +* (((
839 +(% class="wikigeneratedid" id="H5.2A0ProgramConverter28AS-0229" %)
840 +**Program Converter (AS-02)**
841 +)))
842 +
843 +AS-02 is an optional accessory, it is USB Type-C converter. AS-02 provide below feature:
844 +
845 +1. Access AT console of PB01 when used with USB-TTL adapter. [[See this link>>||anchor="H6.1HowtouseATCommandtoconfigurePB01"]].
846 +
847 +[[image:image-20220621141724-3.png]]
848 +
849 +
593 593  = 6. FAQ =
594 594  
595 -== 6.1 ==
852 +== 6.1 How to use AT Command to configure PB01 ==
596 596  
597 597  
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.
856 +
857 +[[image:image-20240511085914-1.png||height="570" width="602"]]
858 +
859 +
860 +**Connection:**
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
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 +
870 +(((
871 +Input password and ATZ to activate PB01, as shown below:
872 +)))
873 +
874 +[[image:image-20240510174509-18.png||height="572" width="791"]]
875 +
876 +
877 +== 6.2  AT Command and Downlink ==
878 +
879 +
880 +(((
881 +Sending ATZ will reboot the node
882 +)))
883 +
884 +(((
885 +Sending AT+FDR will restore the node to factory settings
886 +)))
887 +
888 +(((
889 +Get the node's AT command setting by sending AT+CFG
890 +)))
891 +
892 +(((
893 +
894 +)))
895 +
896 +(((
897 +**Example：**                                           
898 +)))
899 +
900 +(((
901 +AT+DEUI=FA 23 45 55 55 55 55 51
902 +
903 +AT+APPEUI=FF AA 23 45 42 42 41 11
904 +
905 +AT+APPKEY=AC D7 35 81 63 3C B6 05 F5 69 44 99 C1 12 BA 95
906 +
907 +AT+DADDR=FFFFFFFF
908 +
909 +AT+APPSKEY=FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
910 +
911 +AT+NWKSKEY=FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
912 +
913 +AT+ADR=1
914 +
915 +AT+TXP=7
916 +
917 +AT+DR=5
918 +
919 +AT+DCS=0
920 +
921 +AT+PNM=1
922 +
923 +AT+RX2FQ=869525000
924 +
925 +AT+RX2DR=0
926 +
927 +AT+RX1DL=5000
928 +
929 +AT+RX2DL=6000
930 +
931 +AT+JN1DL=5000
932 +
933 +AT+JN2DL=6000
934 +
935 +AT+NJM=1
936 +
937 +AT+NWKID=00 00 00 13
938 +
939 +AT+FCU=61
940 +
941 +AT+FCD=11
942 +
943 +AT+CLASS=A
944 +
945 +AT+NJS=1
946 +
947 +AT+RECVB=0:
948 +
949 +AT+RECV=
950 +
951 +AT+VER=EU868 v1.0.0
952 +
953 +AT+CFM=0,7,0
954 +
955 +AT+SNR=0
956 +
957 +AT+RSSI=0
958 +
959 +AT+TDC=1200000
960 +
961 +AT+PORT=2
962 +
963 +AT+PWORD=123456
964 +
965 +AT+CHS=0
966 +
967 +AT+RX1WTO=24
968 +
969 +AT+RX2WTO=6
970 +
971 +AT+DECRYPT=0
972 +
973 +AT+RJTDC=20
974 +
975 +AT+RPL=0
976 +
977 +AT+TIMESTAMP=systime= 2024/5/11 01:10:58 (1715389858)
978 +
979 +AT+LEAPSEC=18
980 +
981 +AT+SYNCMOD=1
982 +
983 +AT+SYNCTDC=10
984 +
985 +AT+SLEEP=0
986 +
987 +AT+ATDC=1
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 +
598 598  = 7. Order Info =
599 599  
600 -== 7.1  Part Number ==
1090 +== 7.1  Main Device ==
601 601  
602 602  
603 -Part Number: (% style="color:#4472c4" %)LTS5
1093 +Part Number: (% style="color:#4472c4" %)PB01-LW-XX(%%) (white button) / (% style="color:#4472c4" %)PB01-LR-XX(%%)(Red Button)
604 604  
1095 +(% style="color:#4472c4" %)**XX **(%%): The default frequency band
605 605  
606 -== 7.2  Packing Info ==
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
607 607  
1106 += 7. Packing Info =
608 608  
1108 +
609 609  **Package Includes**:
610 610  
611 -* LTS5 HMI Touch Screen
612 -* 5V,2A DC Power Adapter.
613 -* USB Type C Program Cable
1111 +* PB01 LoRaWAN Push Button x 1
614 614  
615 615  = 8. Support =
616 616  
... ... @@ -621,9 +621,7 @@
621 621  = 9.  Reference material =
622 622  
623 623  
624 -* Datasheet
625 -* Source Code
626 -* Mechinical
1122 +* [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/scl/fo/y7pvm58wcr8319d5o4ujr/APZtqlbzRCNbHoPWTmmMMWs?rlkey=wfh93x2dhcev3ydn0846rinf0&st=kdp6lg7t&dl=0]]
627 627  
628 628  = 10. FCC Warning =
629 629  
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