Last modified by BoYang Xie on 2025/07/17 15:54

From version 54.1
edited by BoYang Xie
on 2024/09/28 18:56
Change comment: There is no comment for this version
To version 4.5
edited by Edwin Chen
on 2024/09/16 08:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.xieby
1 +XWiki.Edwin
Content
... ... @@ -29,11 +29,9 @@
29 29  
30 30  == 1.2  Features ==
31 31  
32 -* ESP32-WROOM MCU + Dragino LA66 LoRa Module
33 33  * Support Private LoRa protocol or LoRaWAN protocol
34 34  * Support WiFi & BLE wireless protocol
35 35  * 5.0" HMI touch screen
36 -* Support LVGL case. SquareLine program.
37 37  * Support RS485 Interface
38 38  * Open Source Project
39 39  * Wall Attachable.
... ... @@ -40,44 +40,32 @@
40 40  * 5V DC power
41 41  * IP Rating: IP52
42 42  
41 +
43 43  == 1.3  Specification ==
44 44  
45 -**LoRa**:
46 -
47 -
48 -**WiFi:**
49 -
50 -* 802.11b/g/n
51 -* Up to 150 Mbps data rate in 802.11n mode
52 -* Support A-MPDU and A-MSDU aggregation
53 -* zero point four μ S protection interval
54 -* Working channel center frequency range: 2412~~2484 MHz
55 -
56 -**Bluetooth:**
57 -
58 -* Bluetooth V4.2 BR/EDR and Bluetooth LE standard
59 -* Class-1, Class-2, and Class-3 transmitters.
60 -* AFH
61 -* CVSD and SBC
62 -
63 63  **Display:**
64 64  
65 -* 5.0 Inch , 800 x 480
66 -* IPS Capacitive Touch SCreen
67 -* RGB color.
68 -* Display Area: 120.7*75.80 mm
46 +* TFT Touch SCreen
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"]])
69 69  
51 +
52 +
70 70  == 1.4  Power Consumption ==
71 71  
72 72  * External 5V DC power adapter
73 73  
57 +
74 74  == 1.5  Storage & Operation Temperature ==
75 75  
76 -* Operation Temperature: -20 ~~ 70°C  (No Dew)
77 -* Storage Temperature: -30 ~~ 70°C  (No Dew)
78 78  
61 +-10 ~~ 50 °C  or -40 ~~ 60 °C (depends on battery type, see [[FAQ>>||anchor="H6.5Whyiseedifferentworkingtemperatureforthedevice3F"]])
62 +
63 +
79 79  == 1.6  Applications ==
80 80  
66 +
81 81  * Smart Buildings & Home Automation
82 82  * Logistics and Supply Chain Management
83 83  * Smart Metering
... ... @@ -85,188 +85,722 @@
85 85  * Smart Cities
86 86  * Smart Factory
87 87  
88 -= 2.  Getting Started with Hello World =
89 89  
90 -== 2.1  About this demo ==
75 += 2.  Operation Mode =
91 91  
92 -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.
77 +== 2.1  How it work? ==
93 93  
94 -== 2.2  Install Software Running Environment ==
95 95  
96 -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.
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**.
97 97  
98 -=== 2.2.1 Install VSCode and ESP-IDF extension ===
99 99  
100 -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]].
83 +== 2.2  How to Activate PB01? ==
101 101  
102 -Next, you need to install the ESP-IDF extension within VSCode. The detailed operation steps are illustrated in image 1.
103 103  
104 -[[image:image-20240928110211-5.png||height="508" width="866"]]
86 +(% style="color:red" %)** 1.  Open enclosure from below position.**
105 105  
106 - image 1 ESP-IDF extension install
88 +[[image:image-20220621093835-1.png]]
107 107  
108 -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]]
109 109  
110 -=== 2.2.2 Install SquareLine Studio ===
91 +(% style="color:red" %)** 2.  Insert 2 x AAA LR03 batteries and the node is activated.**
111 111  
112 -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]].
93 +[[image:image-20220621093835-2.png]]
113 113  
114 -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.
115 115  
116 -== 2.3 Simple usage of SquareLine Studio and export UI code ==
96 +(% style="color:red" %)** 3. Under the above conditions, users can also reactivate the node by long pressing the ACT button.**
117 117  
118 -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.
98 +[[image:image-20220621093835-3.png]]
119 119  
120 120  
121 -[[image:image-20240928103357-2.png||height="680" width="708"]]
101 +User can check [[LED Status>>||anchor="H2.8LEDIndicator"]] to know the working state of PB01.
122 122  
123 - image 2 create a SquareLine project
124 124  
125 -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.
104 +== 2.3  Example to join LoRaWAN network ==
126 126  
127 -[[image:1727229582471-566.png]]
128 128  
129 - image 3 project settings
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.
130 130  
131 -[[image:image-20240928105309-4.png||height="526" width="556"]]
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. 
132 132  
133 - image 4 modify project settings
112 +[[image:image-20240705094824-4.png]]
134 134  
135 -Now we can start to use this software. Here are some usage information for this software.
114 +(% style="color:blue" %)**Step 1**(%%):  Create a device in TTN V3 with the OTAA keys from PB01.
136 136  
137 -**1.add widget**
116 +Each PB01 is shipped with a sticker with the default DEV EUI as below:
138 138  
139 -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.
118 +[[image:image-20230426083617-1.png||height="294" width="633"]]
140 140  
141 -[[image:image-20240928111412-6.png||height="526" width="864"]]
142 142  
143 - image 5 add widgets
121 +Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
144 144  
145 -**2.modify widget**
123 +Create application.
146 146  
147 -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".
125 +choose to create the device manually.
148 148  
149 -[[image:1727485118799-984.png]]
127 +Add JoinEUI(AppEUI), DevEUI, AppKey.(% style="display:none" %)
150 150  
151 - image 6 the button widget's "Inspector" tab
129 +[[image:image-20240507142116-1.png||height="410" width="1138"]](% style="display:none" %) (%%)
130 +
152 152  
153 -Second part: "Layout" means a auto position-management for widgets contained in the parent widget. "Transform" includes size, position and align modification.
132 +[[image:image-20240507142157-2.png||height="559" width="1147"]]
154 154  
155 -[[image:1727485251053-655.png]]
134 +[[image:image-20240507142401-3.png||height="693" width="1202"]]
156 156  
157 -image 7 the button widget's "BUTTON" tab
136 +[[image:image-20240507142651-4.png||height="760" width="1190"]]
158 158  
159 -Third part: It is an area of style setting.
138 +**Default mode OTAA**(% style="display:none" %)
160 160  
161 -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.
162 162  
163 -[[image:1727485480434-713.png||height="395" width="290"]]
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.
164 164  
165 - image 8 add event for button
143 +[[image:image-20240507143104-5.png||height="434" width="1398"]]
166 166  
167 -**3.change label widget content**
168 168  
169 -Modify the content in text as shown in image 9, the text content of label widget will be changed accordingly.
146 +== 2.4  Uplink Payload ==
170 170  
171 -[[image:image-20240928090825-1.png||height="327" width="391"]]
172 172  
173 - image 9 modify text content of label widget
149 +Uplink payloads include two types: Valid Sensor Value and other status / control command.
174 174  
175 -**4.Add image into project**
151 +* Valid Sensor Value: Use FPORT=2
152 +* Other control command: Use FPORT other than 2.
176 176  
177 -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.
154 +=== 2.4.1  Uplink FPORT~=5, Device Status ===
178 178  
179 -[[image:image-20240928113424-9.png||height="355" width="505"]]
180 180  
181 - image 10 add image file into SquareLine Studio project
157 +Users ca get the Device Status uplink through the downlink command:
182 182  
183 -[[image:image-20240928114139-10.png||height="559" width="810"]]
159 +(% style="color:#4472c4" %)**Downlink:  **(%%)**0x2601**
184 184  
185 - image 11 use image widget in SquareLine Studio
161 +Uplink the device configures with FPORT=5.
186 186  
187 -**5.The relationship between widgets**
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
188 188  
189 -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.
167 +[[image:image-20240507152130-12.png||height="469" width="1366"]](% style="display:none" %)
190 190  
191 -[[image:1727486567182-334.png||height="318" width="278"]]
169 +Example Payload (FPort=5):  [[image:image-20240507152254-13.png||height="26" width="130"]]
192 192  
193 -image 12 move label1 to make label1 widget be a child of button1 widget(1)
194 194  
195 -[[image:image-20240928112001-8.png||height="431" width="796"]]
172 +(% style="color:#4472c4" %)**Sensor Model**(%%): For PB01, this value is 0x35.
196 196  
197 - image 13 move label1 to make label1 widget be a child of button1 widget(2)
174 +(% style="color:#4472c4" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version.
198 198  
199 -**6.Preview the final effect**
176 +(% style="color:#4472c4" %)**Frequency Band**:
200 200  
201 -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.
178 +*0x01: EU868
202 202  
203 -[[image:1727487368023-281.png]]
180 +*0x02: US915
204 204  
205 - image 14 click on the triangle icon to start or end the simulation
182 +*0x03: IN865
206 206  
207 -For more detailed usage, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
184 +*0x04: AU915
208 208  
186 +*0x05: KZ865
209 209  
210 -== 2.4 Integrate UI Code to ESP-IDF Project ==
188 +*0x06: RU864
211 211  
212 -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.
190 +*0x07: AS923
213 213  
214 -[[image:1727229798126-306.png]]
192 +*0x08: AS923-1
215 215  
216 - image 15 export UI file
194 +*0x09: AS923-2
217 217  
218 -[[image:1727229821582-258.png||height="333" width="662"]]
196 +*0x0a: AS923-3
219 219  
220 - image 16 exported UI file
221 221  
222 -Create a empty directory entitled "ui" in path "basic_prj/app_components/ui/", and then copy all UI code exported to this directory.
199 +(% style="color:#4472c4" %)**Sub-Band**(%%): value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
223 223  
224 -[[image:image-20240928144830-11.png]]
201 +(% style="color:#4472c4" %)**BAT**(%%): shows the battery voltage for PB01.
225 225  
226 - image 17 open CMakeLists.txt
203 +(% style="color:#4472c4" %)**Ex1**(%%): 0x0C DE = 3294mV
227 227  
228 -[[image:1727229892636-154.png||height="521" width="407"]]
229 229  
230 - image 18 modify CMakeLists.txt
206 +=== 2.4.2  Uplink FPORT~=2, Real time sensor value ===
231 231  
232 -The last step of integrating is adding two lines of code in main.c file.
233 233  
234 -[[image:1727229926561-300.png]]
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"]].
235 235  
236 - image 19 add "ui.h"
211 +Uplink uses FPORT=2 and every 20 minutes send one uplink by default.
237 237  
238 -[[image:1727229955611-607.png]]
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
239 239  
240 - image 20 add "ui_init()"
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 +)))
241 241  
242 -== 2.5 Brief introduction of hello world project ==
243 +Example in TTN.
243 243  
244 -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.
245 +[[image:image-20240507150155-11.png||height="549" width="1261"]]
245 245  
246 -== 2.6 Test Result ==
247 +Example Payload (FPort=2):  (% style="background-color:yellow" %)**0C EA 03 01 01 11 02 A8**
247 247  
248 -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.
249 +==== (% style="color:blue" %)**Battery:**(%%) ====
249 249  
250 -[[image:1727488067077-684.png||height="402" width="574"]]
251 +Check the battery voltage.
251 251  
252 - image 21 screen1
253 +* Ex1: 0x0CEA = 3306mV
254 +* Ex2: 0x0D08 = 3336mV
253 253  
254 -[[image:1727488157579-949.png||height="397" width="572"]]
256 +==== (% style="color:blue" %)**Sound_ACK & Sound_key:**(%%) ====
255 255  
256 - image 22 screen2
258 +Key sound and ACK sound are enabled by default.
257 257  
258 -= 3. Example Project 1: LoRa Central Display =
260 +* Example1: 0x03
259 259  
260 -[[image:image-20240916101737-1.png||height="468" width="683"]]
262 + Sound_ACK: (03>>1) & 0x01=1, OPEN.
261 261  
264 +**~ ** Sound_key:  03 & 0x01=1, OPEN.
262 262  
266 +* Example2: 0x01
263 263  
264 -= 4. Example Project 2: LoRaWAN RS485 Alarm =
268 + Sound_ACK: (01>>1) & 0x01=0, CLOSE.
265 265  
270 +**~ ** Sound_key:  01 & 0x01=1, OPEN.
266 266  
272 +
273 +==== (% style="color:blue" %)**Alarm:**(%%) ====
274 +
275 +Key alarm.
276 +
277 +* Ex1: 0x01 & 0x01=1, TRUE.
278 +* Ex2: 0x00 & 0x01=0, FALSE.
279 +
280 +==== (% style="color:blue" %)**Temperature:**(%%) ====
281 +
282 +* Example1:  0x0111/10=27.3℃
283 +* Example2:  (0xFF0D-65536)/10=-24.3℃
284 +
285 +If payload is: FF0D :  (FF0D & 8000 == 1) , temp = (FF0D - 65536)/100 =-24.3℃
286 +
287 +(FF0D & 8000:Judge whether the highest bit is 1, when the highest bit is 1, it is negative)
288 +
289 +
290 +==== (% style="color:blue" %)**Humidity:**(%%) ====
291 +
292 +* Humidity:    0x02A8/10=68.0%
293 +
294 +=== 2.4.3  Uplink FPORT~=3, Datalog sensor value ===
295 +
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.
298 +
299 +[[image:image-20240510144912-1.png||height="471" width="1178"]](% style="display:none" %)
300 +
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" %)
303 +
304 +For example, in US915 band, the max payload for different DR is:
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 +
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 +
313 +See more info about the [[Datalog feature>>||anchor="H2.6A0DatalogFeature"]].
314 +
315 +(% style="display:none" %) (%%)
316 +
317 +=== 2.4.4  Decoder in TTN V3 ===
318 +
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.
321 +
322 +In TTN , add formatter as below:
323 +
324 +[[image:image-20240507162814-16.png||height="778" width="1135"]]
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 +)))
329 +
330 +(((
331 +
332 +)))
333 +
334 +== 2.5 Show data on Datacake ==
335 +
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 +
341 +(((
342 +
343 +)))
344 +
345 +(((
346 +(% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the LoRaWAN network.
347 +)))
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 +)))
352 +
353 +(((
354 +~1. Add Datacake:
355 +)))
356 +
357 +(((
358 +2. Select default key as Access Key:
359 +)))
360 +
361 +(((
362 +3. In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add PB01:
363 +)))
364 +
365 +(((
366 + Please refer to the figure below.
367 +)))
368 +
369 +[[image:image-20240510150924-2.png||height="612" width="1186"]]
370 +
371 +
372 +Log in to DATACAKE, copy the API under the account.
373 +
374 +[[image:image-20240510151944-3.png||height="581" width="1191"]]
375 +
376 +
377 +
378 +[[image:image-20240510152150-4.png||height="697" width="1188"]]
379 +
380 +
381 +[[image:image-20240510152300-5.png||height="298" width="1191"]]
382 +
383 +
384 +[[image:image-20240510152355-6.png||height="782" width="1193"]]
385 +
386 +[[image:image-20240510152542-8.png||height="545" width="739"]]
387 +
388 +[[image:image-20240510152634-9.png||height="748" width="740"]]
389 +
390 +
391 +[[image:image-20240510152809-10.png||height="607" width="732"]]
392 +
393 +[[image:image-20240510153934-14.png||height="460" width="1199"]]
394 +
395 +
396 +[[image:image-20240510153435-12.png||height="428" width="1197"]]
397 +
398 +
399 +Copy and paste the [[TTN decoder>>https://github.com/dragino/dragino-end-node-decoder]] here and save.
400 +
401 +[[image:image-20240510153624-13.png||height="468" width="1195"]]
402 +
403 +
404 +Visual widgets please read the DATACAKE documentation.
405 +
406 +(% style="display:none" %) (%%)
407 +
408 +== 2.6  Datalog Feature ==
409 +
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.
413 +
414 +
415 +=== 2.6.1  Unix TimeStamp ===
416 +
417 +
418 +Unix TimeStamp shows the sampling time of uplink payload. format base on
419 +
420 +[[image:image-20220523001219-11.png||_mstalt="450450" _mstvisible="3" height="97" width="627"]]
421 +
422 +User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/||_mstvisible="3"]] :
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)
425 +
426 +
427 +[[image:1655782409139-256.png]]
428 +
429 +
430 +=== 2.6.2  Poll sensor value ===
431 +
432 +
433 +(((
434 +User can poll sensor value based on timestamps from the server. Below is the downlink command.
435 +)))
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 +)))
440 +
441 +(((
442 +For example, downlink command [[image:image-20220621113526-13.png]] (% _mstvisible="3" style="display:none" %)
443 +)))
444 +
445 +(((
446 +Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00's data
447 +)))
448 +
449 +(((
450 +Uplink Internal =5s,means PB01 will send one packet every 5s. range 5~~255s.
451 +)))
452 +
453 +
454 +=== 2.6.3  Datalog Uplink payload ===
455 +
456 +
457 +See [[Uplink FPORT=3, Datalog sensor value>>||anchor="H2.4.3A0UplinkFPORT3D32CDatalogsensorvalue"]]
458 +
459 +(% style="display:none" %) (%%) (% style="display:none" %)
460 +
461 +== 2.7 Button ==
462 +
463 +
464 +* ACT button
465 +
466 +Long press this button PB01 will reset and join network again.
467 +
468 +[[image:image-20240510161626-17.png||height="192" width="224"]]
469 +
470 +* Alarm button
471 +
472 +Press the button PB01 will immediately uplink data, and alarm is "TRUE".
473 +
474 +[[image:image-20240705095149-5.png||height="164" width="162"]](% style="display:none" %)
475 +
476 +
477 +== 2.8 LED Indicator ==
478 +
479 +
480 +(((
481 +The PB01 has a triple color LED which for easy showing different stage.
482 +)))
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
485 +
486 +(((
487 +(% style="color:#037691" %)**In a normal working state**:
488 +)))
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.
496 +
497 +(((
498 +
499 +)))
500 +
501 +== 2.9 Buzzer ==
502 +
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"]].
505 +
506 +* (% style="color:#4f81bd" %)**Button sound**(%%)** **is the music produced by the node after the alarm button is pressed.
507 +
508 + Users can use[[ AT+OPTION>>||anchor="H3.4A0Setbuzzermusic2807E429"]] to set different button sounds.
509 +
510 +* (% style="color:#4f81bd" %)**ACK sound **(%%)is the notification tone that the node receives ACK.
511 +
512 += 3.  Configure PB01 via AT command or LoRaWAN downlink =
513 +
514 +
515 +Users can configure PB01 via AT Command or LoRaWAN Downlink.
516 +
517 +* AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
518 +
519 +* LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
520 +
521 +There are two kinds of commands to configure PB01, they are:
522 +
523 +* (% style="color:#4f81bd" %)**General Commands:**
524 +
525 +These commands are to configure:
526 +
527 +* General system settings like: uplink interval.
528 +
529 +* LoRaWAN protocol & radio-related commands.
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]]
532 +
533 +
534 +* (% style="color:#4f81bd" %)**Commands special design for PB01**
535 +
536 +These commands are only valid for PB01, as below:
537 +
538 +(% style="display:none" %) (%%)
539 +
540 +== 3.1  Downlink Command Set ==
541 +
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 +
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=
558 +
559 +300(seconds)
560 +)))
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 +
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 +
267 267  = 6. FAQ =
268 268  
269 -== 6.1 ==
789 +== 6.1 ==
270 270  
271 271  
272 272  = 7. Order Info =
... ... @@ -275,6 +275,7 @@
275 275  
276 276  Part Number: (% style="color:#4472c4" %)LTS5
277 277  
798 +
278 278  
279 279  == 7.2  Packing Info ==
280 280  
... ... @@ -284,11 +284,13 @@
284 284  * 5V,2A DC Power Adapter.
285 285  * USB Type C Program Cable
286 286  
808 +
287 287  = 8. Support =
288 288  
289 289  * 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.
290 290  * 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]].
291 291  
814 +
292 292  = 9.  Reference material =
293 293  
294 294  * Datasheet
... ... @@ -295,6 +295,7 @@
295 295  * Source Code
296 296  * Mechinical
297 297  
821 +
298 298  = 10. FCC Warning =
299 299  
300 300  
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