Last modified by BoYang Xie on 2025/05/05 12:26
<
From version < 4.10 >
edited by Edwin Chen
on 2024/09/16 09:34
To version < 54.1 >
edited by BoYang Xie
on 2024/09/28 18:56
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.xieby
Content
... ... @@ -40,7 +40,6 @@
40 40  * 5V DC power
41 41  * IP Rating: IP52
42 42  
43 -
44 44  == 1.3  Specification ==
45 45  
46 46  **LoRa**:
... ... @@ -65,26 +65,20 @@
65 65  
66 66  * 5.0 Inch , 800 x 480
67 67  * IPS Capacitive Touch SCreen
68 -* Accuracy Tolerance: Typ ±0.2 °C
69 -* Long Term Drift: < 0.03 °C/yr
70 -* Operating Range: -10 ~~ 50 °C  or -40 ~~ 60 °C (depends on battery type, see [[FAQ>>||anchor="H6.5Whyiseedifferentworkingtemperatureforthedevice3F"]])
67 +* RGB color.
68 +* Display Area: 120.7*75.80 mm
71 71  
72 -
73 -
74 74  == 1.4  Power Consumption ==
75 75  
76 76  * External 5V DC power adapter
77 77  
78 -
79 79  == 1.5  Storage & Operation Temperature ==
80 80  
81 81  * Operation Temperature: -20 ~~ 70°C  (No Dew)
82 82  * Storage Temperature: -30 ~~ 70°C  (No Dew)
83 83  
84 -
85 85  == 1.6  Applications ==
86 86  
87 -
88 88  * Smart Buildings & Home Automation
89 89  * Logistics and Supply Chain Management
90 90  * Smart Metering
... ... @@ -92,722 +92,188 @@
92 92  * Smart Cities
93 93  * Smart Factory
94 94  
88 += 2.  Getting Started with Hello World =
95 95  
96 -= 2.  Operation Mode =
90 +== 2.1  About this demo ==
97 97  
98 -== 2.1  How it work? ==
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.
99 99  
94 +== 2.2  Install Software Running Environment ==
100 100  
101 -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**.
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.
102 102  
98 +=== 2.2.1 Install VSCode and ESP-IDF extension ===
103 103  
104 -== 2.2  How to Activate PB01? ==
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]].
105 105  
102 +Next, you need to install the ESP-IDF extension within VSCode. The detailed operation steps are illustrated in image 1.
106 106  
107 -(% style="color:red" %)** 1.  Open enclosure from below position.**
104 +[[image:image-20240928110211-5.png||height="508" width="866"]]
108 108  
109 -[[image:image-20220621093835-1.png]]
106 + image 1 ESP-IDF extension install
110 110  
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]]
111 111  
112 -(% style="color:red" %)** 2.  Insert 2 x AAA LR03 batteries and the node is activated.**
110 +=== 2.2.2 Install SquareLine Studio ===
113 113  
114 -[[image:image-20220621093835-2.png]]
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]].
115 115  
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.
116 116  
117 -(% style="color:red" %)** 3. Under the above conditions, users can also reactivate the node by long pressing the ACT button.**
116 +== 2.3 Simple usage of SquareLine Studio and export UI code ==
118 118  
119 -[[image:image-20220621093835-3.png]]
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.
120 120  
121 121  
122 -User can check [[LED Status>>||anchor="H2.8LEDIndicator"]] to know the working state of PB01.
121 +[[image:image-20240928103357-2.png||height="680" width="708"]]
123 123  
123 + image 2 create a SquareLine project
124 124  
125 -== 2.3  Example to join LoRaWAN network ==
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.
126 126  
127 +[[image:1727229582471-566.png]]
127 127  
128 -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.
129 + image 3 project settings
129 129  
130 -(% _mstvisible="1" class="wikigeneratedid" %)
131 -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. 
131 +[[image:image-20240928105309-4.png||height="526" width="556"]]
132 132  
133 -[[image:image-20240705094824-4.png]]
133 + image 4 modify project settings
134 134  
135 -(% style="color:blue" %)**Step 1**(%%):  Create a device in TTN V3 with the OTAA keys from PB01.
135 +Now we can start to use this software. Here are some usage information for this software.
136 136  
137 -Each PB01 is shipped with a sticker with the default DEV EUI as below:
137 +**1.add widget**
138 138  
139 -[[image:image-20230426083617-1.png||height="294" width="633"]]
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.
140 140  
141 +[[image:image-20240928111412-6.png||height="526" width="864"]]
141 141  
142 -Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
143 + image 5 add widgets
143 143  
144 -Create application.
145 +**2.modify widget**
145 145  
146 -choose to create the device manually.
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".
147 147  
148 -Add JoinEUI(AppEUI), DevEUI, AppKey.(% style="display:none" %)
149 +[[image:1727485118799-984.png]]
149 149  
150 -[[image:image-20240507142116-1.png||height="410" width="1138"]](% style="display:none" %) (%%)
151 -
151 + image 6 the button widget's "Inspector" tab
152 152  
153 -[[image:image-20240507142157-2.png||height="559" width="1147"]]
153 +Second part: "Layout" means a auto position-management for widgets contained in the parent widget. "Transform" includes size, position and align modification.
154 154  
155 -[[image:image-20240507142401-3.png||height="693" width="1202"]]
155 +[[image:1727485251053-655.png]]
156 156  
157 -[[image:image-20240507142651-4.png||height="760" width="1190"]]
157 +image 7 the button widget's "BUTTON" tab
158 158  
159 -**Default mode OTAA**(% style="display:none" %)
159 +Third part: It is an area of style setting.
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.
161 161  
162 -(% 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.
163 +[[image:1727485480434-713.png||height="395" width="290"]]
163 163  
164 -[[image:image-20240507143104-5.png||height="434" width="1398"]]
165 + image 8 add event for button
165 165  
167 +**3.change label widget content**
166 166  
167 -== 2.4  Uplink Payload ==
169 +Modify the content in text as shown in image 9, the text content of label widget will be changed accordingly.
168 168  
171 +[[image:image-20240928090825-1.png||height="327" width="391"]]
169 169  
170 -Uplink payloads include two types: Valid Sensor Value and other status / control command.
173 + image 9 modify text content of label widget
171 171  
172 -* Valid Sensor Value: Use FPORT=2
173 -* Other control command: Use FPORT other than 2.
175 +**4.Add image into project**
174 174  
175 -=== 2.4.1  Uplink FPORT~=5, Device Status ===
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.
176 176  
179 +[[image:image-20240928113424-9.png||height="355" width="505"]]
177 177  
178 -Users can  get the Device Status uplink through the downlink command:
181 + image 10 add image file into SquareLine Studio project
179 179  
180 -(% style="color:#4472c4" %)**Downlink:  **(%%)**0x2601**
183 +[[image:image-20240928114139-10.png||height="559" width="810"]]
181 181  
182 -Uplink the device configures with FPORT=5.
185 + image 11 use image widget in SquareLine Studio
183 183  
184 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:370px" %)
185 -|=(% 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**
186 -|(% 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
187 +**5.The relationship between widgets**
187 187  
188 -[[image:image-20240507152130-12.png||height="469" width="1366"]](% style="display:none" %)
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.
189 189  
190 -Example Payload (FPort=5):  [[image:image-20240507152254-13.png||height="26" width="130"]]
191 +[[image:1727486567182-334.png||height="318" width="278"]]
191 191  
193 +image 12 move label1 to make label1 widget be a child of button1 widget(1)
192 192  
193 -(% style="color:#4472c4" %)**Sensor Model**(%%): For PB01, this value is 0x35.
195 +[[image:image-20240928112001-8.png||height="431" width="796"]]
194 194  
195 -(% style="color:#4472c4" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version.
197 + image 13 move label1 to make label1 widget be a child of button1 widget(2)
196 196  
197 -(% style="color:#4472c4" %)**Frequency Band**:
199 +**6.Preview the final effect**
198 198  
199 -*0x01: EU868
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.
200 200  
201 -*0x02: US915
203 +[[image:1727487368023-281.png]]
202 202  
203 -*0x03: IN865
205 + image 14 click on the triangle icon to start or end the simulation
204 204  
205 -*0x04: AU915
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/]].
206 206  
207 -*0x05: KZ865
208 208  
209 -*0x06: RU864
210 +== 2.4 Integrate UI Code to ESP-IDF Project ==
210 210  
211 -*0x07: AS923
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.
212 212  
213 -*0x08: AS923-1
214 +[[image:1727229798126-306.png]]
214 214  
215 -*0x09: AS923-2
216 + image 15 export UI file
216 216  
217 -*0x0a: AS923-3
218 +[[image:1727229821582-258.png||height="333" width="662"]]
218 218  
220 + image 16 exported UI file
219 219  
220 -(% style="color:#4472c4" %)**Sub-Band**(%%): value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
222 +Create a empty directory entitled "ui" in path "basic_prj/app_components/ui/", and then copy all UI code exported to this directory.
221 221  
222 -(% style="color:#4472c4" %)**BAT**(%%): shows the battery voltage for PB01.
224 +[[image:image-20240928144830-11.png]]
223 223  
224 -(% style="color:#4472c4" %)**Ex1**(%%): 0x0C DE = 3294mV
226 + image 17 open CMakeLists.txt
225 225  
228 +[[image:1727229892636-154.png||height="521" width="407"]]
226 226  
227 -=== 2.4.2  Uplink FPORT~=2, Real time sensor value ===
230 + image 18 modify CMakeLists.txt
228 228  
232 +The last step of integrating is adding two lines of code in main.c file.
229 229  
230 -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"]].
234 +[[image:1727229926561-300.png]]
231 231  
232 -Uplink uses FPORT=2 and every 20 minutes send one uplink by default.
236 + image 19 add "ui.h"
233 233  
234 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:460px" %)
235 -|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
236 -**Size(bytes)**
237 -)))|=(% style="width: 60px;background-color:#4F81BD;color:white" %)2|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
238 -**1**
239 -)))|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
240 -**1**
241 -)))|=(% style="width: 90px;background-color:#4F81BD;color:white" %)(((
242 -**2**
243 -)))|=(% style="width: 40px;background-color:#4F81BD;color:white" %)(((
244 -**2**
245 -)))
246 -|(% style="width:97px" %)(((
247 -Value
248 -)))|(% style="width:39px" %)Battery|(% style="width:39px" %)(((
249 -Sound_ACK
238 +[[image:1727229955611-607.png]]
250 250  
251 -&Sound_key
252 -)))|(% style="width:100px" %)(((
253 -(((
254 -Alarm
255 -)))
256 -)))|(% style="width:77px" %)(((
257 -(((
258 -Temperature
259 -)))
260 -)))|(% style="width:47px" %)(((
261 -Humidity
262 -)))
240 + image 20 add "ui_init()"
263 263  
264 -Example in TTN.
242 +== 2.5 Brief introduction of hello world project ==
265 265  
266 -[[image:image-20240507150155-11.png||height="549" width="1261"]]
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.
267 267  
268 -Example Payload (FPort=2):  (% style="background-color:yellow" %)**0C EA 03 01 01 11 02 A8**
246 +== 2.6 Test Result ==
269 269  
270 -==== (% style="color:blue" %)**Battery:**(%%) ====
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.
271 271  
272 -Check the battery voltage.
250 +[[image:1727488067077-684.png||height="402" width="574"]]
273 273  
274 -* Ex1: 0x0CEA = 3306mV
275 -* Ex2: 0x0D08 = 3336mV
252 + image 21 screen1
276 276  
277 -==== (% style="color:blue" %)**Sound_ACK & Sound_key:**(%%) ====
254 +[[image:1727488157579-949.png||height="397" width="572"]]
278 278  
279 -Key sound and ACK sound are enabled by default.
256 + image 22 screen2
280 280  
281 -* Example1: 0x03
258 += 3. Example Project 1: LoRa Central Display =
282 282  
283 - Sound_ACK: (03>>1) & 0x01=1, OPEN.
260 +[[image:image-20240916101737-1.png||height="468" width="683"]]
284 284  
285 -**~ ** Sound_key:  03 & 0x01=1, OPEN.
286 286  
287 -* Example2: 0x01
288 288  
289 - Sound_ACK: (01>>1) & 0x01=0, CLOSE.
264 += 4. Example Project 2: LoRaWAN RS485 Alarm =
290 290  
291 -**~ ** Sound_key:  01 & 0x01=1, OPEN.
292 292  
293 -
294 -==== (% style="color:blue" %)**Alarm:**(%%) ====
295 -
296 -Key alarm.
297 -
298 -* Ex1: 0x01 & 0x01=1, TRUE.
299 -* Ex2: 0x00 & 0x01=0, FALSE.
300 -
301 -==== (% style="color:blue" %)**Temperature:**(%%) ====
302 -
303 -* Example1:  0x0111/10=27.3℃
304 -* Example2:  (0xFF0D-65536)/10=-24.3℃
305 -
306 -If payload is: FF0D :  (FF0D & 8000 == 1) , temp = (FF0D - 65536)/100 =-24.3℃
307 -
308 -（FF0D & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative）
309 -
310 -
311 -==== (% style="color:blue" %)**Humidity:**(%%) ====
312 -
313 -* Humidity:    0x02A8/10=68.0%
314 -
315 -=== 2.4.3  Uplink FPORT~=3, Datalog sensor value ===
316 -
317 -
318 -PB01 stores sensor value and user can retrieve these history value via downlink command. The Datalog sensor value are sent via FPORT=3.
319 -
320 -[[image:image-20240510144912-1.png||height="471" width="1178"]](% style="display:none" %)
321 -
322 -
323 -* 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" %)
324 -
325 -For example, in US915 band, the max payload for different DR is:
326 -
327 -1. **DR0**: max is 11 bytes so one entry of data
328 -1. **DR1**: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
329 -1. **DR2**: total payload includes 11 entries of data
330 -1. **DR3**: total payload includes 22 entries of data.
331 -
332 -(% 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.**
333 -
334 -See more info about the [[Datalog feature>>||anchor="H2.6A0DatalogFeature"]].
335 -
336 -(% style="display:none" %) (%%)
337 -
338 -=== 2.4.4  Decoder in TTN V3 ===
339 -
340 -
341 -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.
342 -
343 -In TTN , add formatter as below:
344 -
345 -[[image:image-20240507162814-16.png||height="778" width="1135"]]
346 -
347 -(((
348 -Please check the decoder from this link:  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]
349 -)))
350 -
351 -(((
352 -
353 -)))
354 -
355 -== 2.5 Show data on Datacake ==
356 -
357 -
358 -(((
359 -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:
360 -)))
361 -
362 -(((
363 -
364 -)))
365 -
366 -(((
367 -(% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the LoRaWAN network.
368 -)))
369 -
370 -(((
371 -(% 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.
372 -)))
373 -
374 -(((
375 -~1. Add Datacake:
376 -)))
377 -
378 -(((
379 -2. Select default key as Access Key:
380 -)))
381 -
382 -(((
383 -3. In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add PB01:
384 -)))
385 -
386 -(((
387 - Please refer to the figure below.
388 -)))
389 -
390 -[[image:image-20240510150924-2.png||height="612" width="1186"]]
391 -
392 -
393 -Log in to DATACAKE, copy the API under the account.
394 -
395 -[[image:image-20240510151944-3.png||height="581" width="1191"]]
396 -
397 -
398 -
399 -[[image:image-20240510152150-4.png||height="697" width="1188"]]
400 -
401 -
402 -[[image:image-20240510152300-5.png||height="298" width="1191"]]
403 -
404 -
405 -[[image:image-20240510152355-6.png||height="782" width="1193"]]
406 -
407 -[[image:image-20240510152542-8.png||height="545" width="739"]]
408 -
409 -[[image:image-20240510152634-9.png||height="748" width="740"]]
410 -
411 -
412 -[[image:image-20240510152809-10.png||height="607" width="732"]]
413 -
414 -[[image:image-20240510153934-14.png||height="460" width="1199"]]
415 -
416 -
417 -[[image:image-20240510153435-12.png||height="428" width="1197"]]
418 -
419 -
420 -Copy and paste the [[TTN decoder>>https://github.com/dragino/dragino-end-node-decoder]] here and save.
421 -
422 -[[image:image-20240510153624-13.png||height="468" width="1195"]]
423 -
424 -
425 -Visual widgets please read the DATACAKE documentation.
426 -
427 -(% style="display:none" %) (%%)
428 -
429 -== 2.6  Datalog Feature ==
430 -
431 -
432 -(% _msthash="315262" _msttexthash="32283004" _mstvisible="1" %)
433 -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.
434 -
435 -
436 -=== 2.6.1  Unix TimeStamp ===
437 -
438 -
439 -Unix TimeStamp shows the sampling time of uplink payload. format base on
440 -
441 -[[image:image-20220523001219-11.png||_mstalt="450450" _mstvisible="3" height="97" width="627"]]
442 -
443 -User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/||_mstvisible="3"]] :
444 -
445 -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)
446 -
447 -
448 -[[image:1655782409139-256.png]]
449 -
450 -
451 -=== 2.6.2  Poll sensor value ===
452 -
453 -
454 -(((
455 -User can poll sensor value based on timestamps from the server. Below is the downlink command.
456 -)))
457 -
458 -(((
459 -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.
460 -)))
461 -
462 -(((
463 -For example, downlink command [[image:image-20220621113526-13.png]] (% _mstvisible="3" style="display:none" %)
464 -)))
465 -
466 -(((
467 -Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00's data
468 -)))
469 -
470 -(((
471 -Uplink Internal =5s，means PB01 will send one packet every 5s. range 5~~255s.
472 -)))
473 -
474 -
475 -=== 2.6.3  Datalog Uplink payload ===
476 -
477 -
478 -See [[Uplink FPORT=3, Datalog sensor value>>||anchor="H2.4.3A0UplinkFPORT3D32CDatalogsensorvalue"]]
479 -
480 -(% style="display:none" %) (%%) (% style="display:none" %)
481 -
482 -== 2.7 Button ==
483 -
484 -
485 -* ACT button
486 -
487 -Long press this button PB01 will reset and join network again.
488 -
489 -[[image:image-20240510161626-17.png||height="192" width="224"]]
490 -
491 -* Alarm button
492 -
493 -Press the button PB01 will immediately uplink data, and alarm is "TRUE".
494 -
495 -[[image:image-20240705095149-5.png||height="164" width="162"]](% style="display:none" %)
496 -
497 -
498 -== 2.8 LED Indicator ==
499 -
500 -
501 -(((
502 -The PB01 has a triple color LED which for easy showing different stage.
503 -)))
504 -
505 -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
506 -
507 -(((
508 -(% style="color:#037691" %)**In a normal working state**:
509 -)))
510 -
511 -* 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" %)**.**
512 -* During OTAA Join:
513 -** **For each Join Request uplink:** the (% style="color:green" %)**GREEN LED** (%%)will blink once.
514 -** **Once Join Successful:** the (% style="color:green" %)**GREEN LED**(%%) will be solid on for 5 seconds.
515 -* After joined, for each uplink, the (% style="color:blue" %)**BLUE LED**(%%) or (% style="color:green" %)**GREEN LED** (%%)will blink once.
516 -* 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.
517 -
518 -(((
519 -
520 -)))
521 -
522 -== 2.9 Buzzer ==
523 -
524 -
525 -The PB01 has** button sound** and** ACK sound** and users can turn on or off both sounds by using [[AT+SOUND>>||anchor="H3.3A0Setbuttonsoundandbuttonalarm"]].
526 -
527 -* (% style="color:#4f81bd" %)**Button sound**(%%)** **is the music produced by the node after the alarm button is pressed.
528 -
529 - Users can use[[ AT+OPTION>>||anchor="H3.4A0Setbuzzermusic2807E429"]] to set different button sounds.
530 -
531 -* (% style="color:#4f81bd" %)**ACK sound **(%%)is the notification tone that the node receives ACK.
532 -
533 -= 3.  Configure PB01 via AT command or LoRaWAN downlink =
534 -
535 -
536 -Users can configure PB01 via AT Command or LoRaWAN Downlink.
537 -
538 -* AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
539 -
540 -* LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
541 -
542 -There are two kinds of commands to configure PB01, they are:
543 -
544 -* (% style="color:#4f81bd" %)**General Commands:**
545 -
546 -These commands are to configure:
547 -
548 -* General system settings like: uplink interval.
549 -
550 -* LoRaWAN protocol & radio-related commands.
551 -
552 -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]]
553 -
554 -
555 -* (% style="color:#4f81bd" %)**Commands special design for PB01**
556 -
557 -These commands are only valid for PB01, as below:
558 -
559 -(% style="display:none" %) (%%)
560 -
561 -== 3.1  Downlink Command Set ==
562 -
563 -
564 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %)
565 -|=(% 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**
566 -|(% style="width:130px" %)AT+TDC=?|(% style="width:151px" %)(((
567 -
568 -
569 -View current TDC time
570 -)))|(% style="width:92px" %)(((
571 -1200000
572 -OK
573 -)))|(% style="width:206px" %)Default 1200000(ms)
574 -|(% style="width:130px" %)AT+TDC=300000|(% style="width:151px" %)Set TDC time|(% style="width:92px" %)OK|(% style="width:206px" %)(((
575 -(((
576 -0X0100012C:
577 -01: fixed command
578 -00012C: 0X00012C=
579 -
580 -300(seconds)
581 -)))
582 -
583 -(((
584 -
585 -)))
586 -)))
587 -|(% style="width:130px" %)ATZ|(% style="width:151px" %)Reset node|(% style="width:92px" %) |(% style="width:206px" %)0x04FF
588 -|(% style="width:130px" %)AT+FDR|(% style="width:151px" %)Restore factory settings|(% style="width:92px" %) |(% style="width:206px" %)0X04FE
589 -|(% style="width:130px" %)AT+CFM=?|(% style="width:151px" %)View the current confirmation mode status|(% style="width:92px" %)(((
590 -0,7,0
591 -
592 -OK
593 -)))|(% style="width:206px" %)Default 0,7,0
594 -|(% style="width:130px" %)AT+CFM=1,7,1|(% style="width:151px" %)(((
595 -Confirmed uplink mode, the maximum number of retries is seven, and uplink fcnt increase by 1 for each retry
596 -)))|(% style="width:92px" %)(((
597 -OK
598 -)))|(% style="width:206px" %)(((
599 -05010701
600 -
601 -05: fixed command
602 -
603 -01:confirmed uplink
604 -
605 -07: retry 7 times
606 -
607 -01: fcnt count plus 1
608 -)))
609 -|(% style="width:130px" %)AT+NJM=?|(% style="width:151px" %)(((
610 -Check the current network connection method
611 -)))|(% style="width:92px" %)(((
612 -1
613 -OK
614 -)))|(% style="width:206px" %)Default 1
615 -|(% style="width:130px" %)AT+NJM=0|(% style="width:151px" %)Change the network connection method to ABP|(% style="width:92px" %)(((
616 -Attention:Take effect after ATZ
617 -OK
618 -)))|(% style="width:206px" %)(((
619 -0X2000: ABP
620 -0x2001: OTAA
621 -20: fixed command
622 -)))
623 -|(% style="width:130px" %)AT+RPL=?|(% style="width:151px" %)View current RPL settings|(% style="width:92px" %)(((
624 -0
625 -OK
626 -)))|(% style="width:206px" %)Default 0
627 -|(% style="width:130px" %)AT+RPL=1|(% style="width:151px" %)set RPL=1    |(% style="width:92px" %)OK|(% style="width:206px" %)(((
628 -0x2101:
629 -21: fixed command
630 -01: for details, check wiki
631 -)))
632 -|(% style="width:130px" %)AT+ADR=?|(% style="width:151px" %)View current ADR status|(% style="width:92px" %)(((
633 -1
634 -OK
635 -)))|(% style="width:206px" %)Default 0
636 -|(% style="width:130px" %)AT+ADR=0|(% style="width:151px" %)Set the ADR state to off|(% style="width:92px" %)OK|(% style="width:206px" %)(((
637 -0x2200: close
638 -0x2201: open
639 -22: fixed command
640 -)))
641 -|(% style="width:130px" %)AT+DR=?|(% style="width:151px" %)View the current DR settings|(% style="width:92px" %)OK|(% style="width:206px" %)
642 -|(% style="width:130px" %)AT+DR=1|(% style="width:151px" %)(((
643 -set DR to 1
644 -It takes effect only when ADR=0
645 -)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
646 -0X22000101:
647 -00: ADR=0
648 -01: DR=1
649 -01: TXP=1
650 -22: fixed command
651 -)))
652 -|(% style="width:130px" %)AT+TXP=?|(% style="width:151px" %)View the current TXP|(% style="width:92px" %)OK|(% style="width:206px" %)
653 -|(% style="width:130px" %)AT+TXP=1|(% style="width:151px" %)(((
654 -set TXP to 1
655 -It takes effect only when ADR=0
656 -)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
657 -0X22000101:
658 -00: ADR=0
659 -01: DR=1
660 -01: TXP=1
661 -22: fixed command
662 -)))
663 -|(% style="width:130px" %)AT+RJTDC=10|(% style="width:151px" %)Set RJTDC time interval|(% style="width:92px" %)OK|(% style="width:206px" %)(((
664 -0X26000A:
665 -26: fixed command
666 -000A: 0X000A=10(min)
667 -for details, check wiki
668 -)))
669 -|(% style="width:130px" %) |(% style="width:151px" %)(((
670 -(((
671 -~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_
672 -
673 -Retrieve stored data for a specified period of time
674 -)))
675 -
676 -(((
677 -
678 -)))
679 -)))|(% style="width:92px" %) |(% style="width:206px" %)(((
680 -0X3161DE7C7061DE8A800A:
681 -31: fixed command
682 -61DE7C70:0X61DE7C70=2022/1/12 15:00:00
683 -61DE8A80:0X61DE8A80=2022/1/12 16:00:00
684 -0A: 0X0A=10(second)
685 -View details 2.6.2
686 -)))
687 -|(% style="width:130px" %)AT+DDETECT=?|(% style="width:151px" %)View the current DDETECT setting status and time|(% style="width:92px" %)(((
688 -1,1440,2880
689 -OK
690 -)))|(% style="width:206px" %)Default 1,1440,2880(min)
691 -|(% style="width:130px" %)AT+DDETECT=(((
692 -1,1440,2880
693 -)))|(% style="width:151px" %)(((
694 -Set DDETECT setting status and time
695 -((% style="color:red" %)When the node does not receive the downlink packet within the set time, it will re-enter the network(%%))
696 -)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
697 -0X320005A0: close
698 -0X320105A0: open
699 -32: fixed command
700 -05A0: 0X05A0=1440(min)
701 -)))
702 -
703 -== 3.2  Set Password ==
704 -
705 -
706 -Feature: Set device password, max 9 digits.
707 -
708 -(% style="color:#4f81bd" %)**AT Command: AT+PWORD**
709 -
710 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
711 -|(% 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**
712 -|(% style="width:155px" %)AT+PWORD=?|(% style="width:124px" %)Show password|(% style="width:86px" %)(((
713 -123456
714 -OK
715 -)))
716 -|(% style="width:155px" %)AT+PWORD=999999|(% style="width:124px" %)Set password|(% style="width:86px" %)OK
717 -
718 -(% style="color:#4f81bd" %)**Downlink Command:**
719 -
720 -No downlink command for this feature.
721 -
722 -
723 -== 3.3  Set button sound and ACK sound ==
724 -
725 -
726 -Feature: Turn on/off button sound and ACK alarm.
727 -
728 -(% style="color:#4f81bd" %)**AT Command: AT+SOUND**
729 -
730 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
731 -|(% 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**
732 -|(% style="width:155px" %)(((
733 -AT+SOUND=?
734 -)))|(% style="width:124px" %)Get the current status of button sound and ACK sound|(% style="width:86px" %)(((
735 -1,1
736 -OK
737 -)))
738 -|(% style="width:155px" %)(((
739 -AT+SOUND=0,1
740 -)))|(% style="width:124px" %)Turn off the button sound and turn on ACK sound|(% style="width:86px" %)OK
741 -
742 -(% style="color:#4f81bd" %)**Downlink Command: 0xA1 **
743 -
744 -Format: Command Code (0xA1) followed by 2 bytes mode value.
745 -
746 -The first byte after 0XA1 sets the button sound, and the second byte after 0XA1 sets the ACK sound.** (0: off, 1: on)**
747 -
748 -* **Example: **Downlink Payload: A10001  ~/~/ Set AT+SOUND=0,1  Turn off the button sound and turn on ACK sound.
749 -
750 -== 3.4  Set buzzer music type(0~~4) ==
751 -
752 -
753 -Feature: Set different alarm key response sounds.There are five different types of button music.
754 -
755 -(% style="color:#4f81bd" %)**AT Command: AT+OPTION**
756 -
757 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
758 -|(% 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**
759 -|(% style="width:155px" %)(((
760 -AT+OPTION=?
761 -)))|(% style="width:124px" %)(((
762 -Get the buzzer music type
763 -)))|(% style="width:86px" %)(((
764 -3
765 -
766 -OK
767 -)))
768 -|(% style="width:155px" %)AT+OPTION=1|(% style="width:124px" %)Set the buzzer music to type 1|(% style="width:86px" %)OK
769 -
770 -(% style="color:#4f81bd" %)**Downlink Command: 0xA3**
771 -
772 -Format: Command Code (0xA3) followed by 1 byte mode value.
773 -
774 -* **Example: **Downlink Payload: A300  ~/~/ Set AT+OPTION=0  Set the buzzer music to type 0.
775 -
776 -== 3.5  Set Valid Push Time ==
777 -
778 -
779 -Feature: Set the holding time for pressing the alarm button to avoid miscontact. Values range from** 0 ~~1000ms**.
780 -
781 -(% style="color:#4f81bd" %)**AT Command: AT+STIME**
782 -
783 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
784 -|(% 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**
785 -|(% style="width:155px" %)(((
786 -AT+STIME=?
787 -)))|(% style="width:124px" %)(((
788 -Get the button sound time
789 -)))|(% style="width:86px" %)(((
790 -0
791 -OK
792 -)))
793 -|(% style="width:155px" %)(((
794 -AT+STIME=1000
795 -)))|(% style="width:124px" %)Set the button sound time to 1000**ms**|(% style="width:86px" %)OK
796 -
797 -(% style="color:#4f81bd" %)**Downlink Command: 0xA2**
798 -
799 -Format: Command Code (0xA2) followed by 2 bytes mode value.
800 -
801 -* **Example: **Downlink Payload: A203E8  ~/~/ Set AT+STIME=1000  
802 -
803 -**~ Explain: **Hold the alarm button for 10 seconds before the node will send the alarm packet.
804 -
805 -
806 -
807 -
808 808  = 6. FAQ =
809 809  
810 -== 6.1 ==
269 +== 6.1 ==
811 811  
812 812  
813 813  = 7. Order Info =
... ... @@ -816,7 +816,6 @@
816 816  
817 817  Part Number: (% style="color:#4472c4" %)LTS5
818 818  
819 -
820 820  
821 821  == 7.2  Packing Info ==
822 822  
... ... @@ -826,13 +826,11 @@
826 826  * 5V,2A DC Power Adapter.
827 827  * USB Type C Program Cable
828 828  
829 -
830 830  = 8. Support =
831 831  
832 832  * 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.
833 833  * 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]].
834 834  
835 -
836 836  = 9.  Reference material =
837 837  
838 838  * Datasheet
... ... @@ -839,7 +839,6 @@
839 839  * Source Code
840 840  * Mechinical
841 841  
842 -
843 843  = 10. FCC Warning =
844 844  
845 845  
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

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0