Skip to Content
Last modified by BoYang Xie on 2025/07/24 16:47
From version 4.2
edited by Edwin Chen
on 2024/09/16 08:33
Change comment: There is no comment for this version
To version 115.1
edited by Xiaoling
on 2024/12/17 17:47
Change comment: There is no comment for this version

Summary

Details

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