Changes for page Notes for TTN

Last modified by Mengting Qiu on 2024/08/20 17:29
<
From version < 73.2 >
edited by Xiaoling
on 2022/05/26 13:57
To version < 99.15 >
edited by Xiaoling
on 2022/07/25 09:15
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,14 +1,18 @@
1 -**~ Contents：**
1 +**~ Table of Contents：**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 +
6 6  = 1. The Things Network-V3 =
7 7  
8 -== 1.1 Introduction ==
9 9  
10 -=== 1.1.1 What is The Things Network ===
10 +== 1.1  Introduction ==
11 11  
12 +
13 +=== 1.1.1  What is The Things Network ===
14 +
15 +
12 12  (((
13 13  The Things Network is a global collaborative Internet of Things ecosystem that creates networks, devices and solutions using LoRaWAN.
14 14  )))
... ... @@ -16,11 +16,13 @@
16 16  (((
17 17  The Things Network runs The Things Stack Community Edition, which is a crowdsourced, open and decentralized LoRaWAN network. This network is a great way to get started testing devices, applications, and integrations, and get familiar with LoRaWAN.
18 18  
23 +
19 19  
20 20  )))
21 21  
22 -=== 1.1.2 Login or crate an account ===
27 +=== 1.1.2  Login or crate an account ===
23 23  
29 +
24 24  (((
25 25  [[Login or create an account>>url:https://console.cloud.thethings.network/]] to get started with The Things Network and start using The Things Stack Console.
26 26  )))
... ... @@ -28,47 +28,59 @@
28 28  (((
29 29  Once you have an account,get started by following steps for adding Gateway,Device and Intergrations.
30 30  
37 +
31 31  
32 32  )))
33 33  
34 -=== 1.1.3 List the support products and Requirements ===
41 +=== 1.1.3  List the support products and Requirements ===
35 35  
43 +
36 36  LoRaWAN Gateway model: Existing Gateway
37 37  
38 38  
39 -= 2. Gateway Registration for Semtech UDP =
40 40  
41 -== 2.1 Primary LoRaWAN Server ==
48 += 2.  Gateway Registration for Semtech UDP =
42 42  
50 +
51 +== 2.1  Primary LoRaWAN Server ==
52 +
53 +
43 43  [[image:image-20220526134633-2.png||height="616" width="1323"]]
44 44  
45 45  Register Gateway
46 46  
47 47  
59 +
48 48  [[image:image-20220526134826-4.png]]
49 49  
50 50  Put Gateway ID
51 51  
52 52  
65 +
53 53  [[image:image-20220526134759-3.png]]
54 54  
55 55  Choose Frequency Band
56 56  
57 57  
71 +
58 58  [[image:image-20220526134919-5.png]]
59 59  
60 60  Show Status
61 61  
62 62  
63 -== 2.2 Secondary LoRaWAN Server ==
64 64  
65 -=== 2.2.1 Introduction ===
78 +== 2.2  Secondary LoRaWAN Server ==
66 66  
80 +
81 +=== 2.2.1  Introduction ===
82 +
83 +
67 67  The Dragino gateway has supports the Secondary server settings.
68 68  
69 69  
70 -=== 2.2.2 Below list the support products and Requirements: ===
87 +=== 2.2.2  Below list the support products and Requirements: ===
71 71  
89 +
72 72  (((
73 73  ~1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
74 74  )))
... ... @@ -78,13 +78,17 @@
78 78  )))
79 79  
80 80  
81 -=== 2.2.3 Example ===
82 82  
100 +=== 2.2.3  Example ===
101 +
102 +
83 83  The following takes Helium as a Secondary LoRaWAN server as an example
84 84  
85 85  
86 -=== 2.2.4 Step 1: Download and Install the helium gateway-rs ===
87 87  
107 +=== 2.2.4  Step 1: Download and Install the helium gateway-rs ===
108 +
109 +
88 88  The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
89 89  
90 90  [[image:image-20220526135049-6.png]]
... ... @@ -92,8 +92,10 @@
92 92  Download and Install gateway-rs
93 93  
94 94  
95 -=== 2.2.5 Step 2: Back to Semtech UDP page ===
96 96  
118 +=== 2.2.5  Step 2: Back to Semtech UDP page ===
119 +
120 +
97 97  Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
98 98  
99 99  ​​​​[[image:image-20220526135125-7.png]]
... ... @@ -101,32 +101,41 @@
101 101  Configuration of helium
102 102  
103 103  
104 -= 3. Gateway Registration for Basics Station =
105 105  
106 -== 3.1 Introduction ==
129 += 3.  Gateway Registration for Basics Station =
107 107  
131 +
132 +== 3.1  Introduction ==
133 +
134 +
108 108  (((
109 109  (((
110 110  The LoRa Basics™ Station protocol simplifies management of large scale LoRaWAN networks. LoRa Basics™ Station is the preferred way of connecting Gateways to The Things Stack. [[The LoRa Basics Station doc>>url:https://www.thethingsindustries.com/docs/gateways/lora-basics-station/]]
138 +
139 +
111 111  )))
112 112  )))
113 113  
114 114  (((
115 -**Below list the support products and Requirements:**
144 +(% style="color:blue" %)**Below list the support products and Requirements:**
116 116  )))
117 117  
118 118  (((
119 119  (((
120 - ~1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
149 +1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
121 121  )))
122 122  
123 123  (((
124 124   2. Firmware version since :[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
154 +
155 +
156 +
157 +
125 125  )))
126 126  )))
127 127  
128 128  (((
129 -**What do you need to prepare**
162 +(% style="color:blue" %)**What do you need to prepare**
130 130  )))
131 131  
132 132  (((
... ... @@ -133,12 +133,14 @@
133 133  (((
134 134  A gateway that can access the internet normally
135 135  
169 +
136 136  
137 137  )))
138 138  )))
139 139  
140 -== 3.2 Step 1. Add Gateway ==
174 +== 3.2  Step 1: Add Gateway ==
141 141  
176 +
142 142  (((
143 143  (((
144 144  The example for **EU**
... ... @@ -154,6 +154,8 @@
154 154  (((
155 155  (((
156 156  Following picture is the successful added.
192 +
193 +
157 157  )))
158 158  )))
159 159  
... ... @@ -162,52 +162,66 @@
162 162  Add Gateway
163 163  
164 164  
165 -== 3.3 Step 2. Create the API key ==
166 166  
203 +== 3.3  Step 2: Create the API key ==
204 +
205 +
167 167  user need to create the CUPS API key and LNS API key.
168 168  
208 +
169 169  [[image:image-20220526135349-9.png]]
170 170  
171 171  Create CUPS API key
172 172  
173 173  
214 +
174 174  [[image:image-20220526135428-10.png]]
175 175  
176 176  Create LNS API key
177 177  
219 +
178 178  (% style="color:red" %)**Note : Please copy the API key.**
179 179  
180 180  
181 -== 3.4 Step 3. Update the gateway setting ==
182 182  
224 +== 3.4  Step 3: Update the gateway setting ==
225 +
226 +
183 183  In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
184 184  
229 +
185 185  [[image:image-20220526135528-11.png]]
186 186  
187 187  paste the API key
188 188  
189 189  
190 -== 3.5 Step 4. Access the gateway GUI ==
191 191  
236 +== 3.5  Step 4: Access the gateway GUI ==
237 +
238 +
192 192  User need to update the API key and install the Certificate
193 193  
241 +
194 194  [[image:image-20220526135601-12.png]]
195 195  
196 196  Access the gateway GUI
197 197  
198 198  
199 -== 3.6 Step 5. Configure Station ==
200 200  
248 +== 3.6  Step 5: Configure Station ==
249 +
250 +
201 201  User need to input Server URI, Server CUPS Key and LNS Key, as well as install CUPS certificate.
202 202  
203 -**just to clarify.**
204 204  
254 +(% style="color:blue" %)**just to clarify:**
255 +
205 205  (% class="box" %)
206 206  (((
207 - CUPS Server URI  ~-~-> Server Adress
208 - CUPS Authorization Key         ~-~-> Server CUPS API Key
209 - LNS Authorization Key  ~-~-> Server LNS API Key
210 - CUPS certificate  ~-~-> Server CA(user can use the button to install the certificate by default)
258 + CUPS Server URI  ~-~->  Server Adress
259 + CUPS Authorization Key         ~-~->  Server CUPS API Key
260 + LNS Authorization Key  ~-~->  Server LNS API Key
261 + CUPS certificate  ~-~->  Server CA(user can use the button to install the certificate by default)
211 211  )))
212 212  
213 213  [[image:image-20220526135654-13.png]]
... ... @@ -215,38 +215,52 @@
215 215  Congfigure Station
216 216  
217 217  
218 -== 3.7 Start Station ==
219 219  
270 +== 3.7  Start Station ==
271 +
272 +
220 220  (((
221 221  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
222 222  
276 +
223 223  
224 224  )))
225 225  
226 -== 3.8 Siccessful Connection ==
280 +== 3.8  Siccessful Connection ==
227 227  
282 +
228 228  If user completes the above steps,which will see live date in the TTN.
229 229  
285 +
230 230  [[image:image-20220526135734-14.png]]
231 231  
232 232  Station live date
233 233  
234 -== 3.9 Trouble Shooting ==
235 235  
291 +
292 +== 3.9  Trouble Shooting ==
293 +
294 +
236 236  User can check the station log in the logread/system log page.
237 237  
238 -[[image:image-20220525090622-14.png]]
239 239  
298 +[[image:image-20220526135845-15.png]]
299 +
240 240  Station Log
241 241  
302 +
303 +
242 242  and recode the station log in the system/Recode log page.
243 243  
244 -[[image:image-20220525090705-15.png]]
306 +[[image:image-20220526135940-16.png]]
245 245  
246 246  Recore Log
247 247  
248 -= 4. Configure node connection to TTNv3 =
249 249  
311 +
312 += 4.  Configure node connection to TTNv3 =
313 +
314 +
250 250  (((
251 251  (((
252 252  Following is an example for how to join the TTN v3 LoRaWAN Network.
... ... @@ -262,11 +262,15 @@
262 262  (((
263 263  (((
264 264  We take LES01 as an example.
330 +
331 +
332 +
265 265  )))
266 266  )))
267 267  
268 -== 4.1 Step1 ==
336 +== 4.1  Step1 ==
269 269  
338 +
270 270  (((
271 271  (((
272 272  Create a device in TTN with the OTAA keys from LSE01.
... ... @@ -285,44 +285,65 @@
285 285  )))
286 286  )))
287 287  
288 -[[image:image-20220525090739-16.png]]
357 +[[image:image-20220526140015-17.png]]
289 289  
290 -[[image:image-20220525090833-17.png]]
359 +[[image:image-20220526140044-18.png]]
291 291  
292 -== 4.2 Step2 ==
293 293  
362 +
363 +== 4.2  Step2 ==
364 +
365 +
294 294  (((
295 295  (((
296 296  There are all our nodes in the repository. Users can choose the corresponding brand, model, firmware version and frequency.The decoder and configuration information of the node are pre-configured.Users do not need to configure them.
369 +
370 +
297 297  )))
298 298  )))
299 299  
300 -[[image:image-20220525090920-18.png]]
374 +[[image:image-20220526140132-19.png]]
301 301  
302 -== 4.3 Step3 ==
303 303  
377 +
378 +== 4.3  Step3 ==
379 +
380 +
304 304  Add APP EUI in the application:
305 305  
306 -[[image:image-20220525091022-19.png]]
307 307  
308 -== 4.4 Step4 ==
384 +[[image:image-20220526140205-20.png]]
309 309  
386 +
387 +
388 +== 4.4  Step4 ==
389 +
390 +
310 310  Add APP KEY and DEV EUI:
311 311  
312 -[[image:image-20220525091128-20.png]]
313 313  
314 -= 5. TTN V3 integrated into MQTT server =
394 +[[image:image-20220526140251-21.png]]
315 315  
316 -== 5.1 Introduction ==
317 317  
397 +
398 += 5.  TTN V3 integrated into MQTT server =
399 +
400 +
401 +== 5.1  Introduction ==
402 +
403 +
318 318  (((
319 319  (((
320 320  The Application Server exposes an MQTT server to work with streaming events. In order to use the MQTT server you need to create a new API key, which will function as connection password. You can also use an existing API key, as long as it has the necessary rights granted.
407 +
408 +
409 +
321 321  )))
322 322  )))
323 323  
324 -== 5.2 Create device steps at MQTT ==
413 +== 5.2  Create device steps at MQTT ==
325 325  
415 +
326 326  (((
327 327  (((
328 328  The user creates a new API KEY after creating a device on TTN V3.
... ... @@ -338,16 +338,20 @@
338 338  (((
339 339  (((
340 340  Fill in Broker Address and Broker port.
431 +
432 +
341 341  )))
342 342  )))
343 343  
344 -[[image:image-20220525091251-22.png]]
436 +[[image:image-20220526140347-22.png]]
345 345  
346 346  Fill in the username and password into MQTT.
347 347  
348 348  
349 -[[image:image-20220525091333-23.png]]
350 350  
442 +[[image:image-20220526140420-23.png]]
443 +
444 +
351 351  The Application Server publishes uplink traffic on the following topics:
352 352  
353 353  (% class="box" %)
... ... @@ -364,13 +364,18 @@
364 364  )))
365 365  
366 366  (((
461 +
462 +
367 367  (((
368 -**Note**: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
464 +(% style="color:red" %)**Note**: **Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.**
465 +
466 +
369 369  )))
370 370  )))
371 371  
372 -[[image:image-20220525091430-24.png]]
470 +[[image:image-20220526140452-24.png]]
373 373  
472 +
374 374  (((
375 375  (((
376 376  While you could subscribe to all of these topics separately, for the simplicity of this tutorial we use # to subscribe to all topics, i.e. to receive all uplink traffic.
... ... @@ -377,7 +377,7 @@
377 377  )))
378 378  )))
379 379  
380 -[[image:image-20220525091458-25.png]]
479 +[[image:image-20220526140708-25.png]]
381 381  
382 382  (((
383 383  (((
... ... @@ -387,7 +387,11 @@
387 387  
388 388  (((
389 389  (((
390 -**Note**: Remember that the format of this topic for The Things Stack Open Source deployment would be v3/{application id}/devices/{device id}/down/push.
489 +
490 +
491 +(% style="color:red" %)**Note**: **Remember that the format of this topic for The Things Stack Open Source deployment would be v3/{application id}/devices/{device id}/down/push.**
492 +
493 +
391 391  )))
392 392  )))
393 393  
... ... @@ -397,20 +397,27 @@
397 397  )))
398 398  )))
399 399  
400 -[[image:image-20220525091618-27.png]]
503 +[[image:image-20220526140856-26.png]]
401 401  
402 402  (((
403 403  To send an unconfirmed downlink message to the device dev1 in application app1 in tenant tenant1 with the hexadecimal payload BE EF on FPort 15 with normal priority, use the topic v3/app1@tenant1/devices/dev1/down/push with the following contents:
507 +
508 +
404 404  )))
405 405  
406 406  (((
407 -**Note**: Use this handy tool to convert hexadecimal to base64.
512 +(% style="color:red" %)**Note**: **Use this handy tool to convert hexadecimal to base64.**
513 +
514 +
408 408  )))
409 409  
410 -[[image:image-20220525091702-28.png]]
517 +[[image:image-20220526140936-27.png]]
411 411  
412 -== 5.3 Send Downlink message ==
413 413  
520 +
521 +== 5.3  Send Downlink message ==
522 +
523 +
414 414  (((
415 415  How to configure downlink in TTN V3?
416 416  )))
... ... @@ -420,31 +420,40 @@
420 420  )))
421 421  
422 422  (((
423 -Downlink command:01 00 00 5A
533 +(% style="color:blue" %)**Downlink command: 01 00 00 5A**
534 +
535 +
424 424  )))
425 425  
426 -[[image:image-20220525091752-29.png]]
538 +[[image:image-20220526141021-28.png]]
427 427  
428 428  downlink
429 429  
542 +
543 +
430 430  After sending, you can view it in live data.
431 431  
432 -[[image:image-20220525091816-30.png]]
546 +[[image:image-20220526141052-29.png]]
433 433  
434 434  downlink
435 435  
550 +
551 +
436 436  (((
437 437  When downlink is successfully sent, the downlink information can be received on the serial port.
438 438  )))
439 439  
440 440  (((
441 -**Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
557 +(% style="color:red" %)**Note**:** If the downlink byte sent is longer, the number of bytes will be displayed.**
558 +
559 +
442 442  )))
443 443  
444 -[[image:image-20220525091855-31.png]]
562 +[[image:image-20220526141116-30.png]]
445 445  
446 446  downlink
447 447  
566 +
448 448  (((
449 449  (((
450 450  If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
... ... @@ -453,13 +453,13 @@
453 453  
454 454  (((
455 455  (((
456 -If the equipment uses CLASS A. You can set **AT+RPL=2** or send the downlink command: **2102**
575 +If the equipment uses (% style="color:blue" %)**CLASS A**(%%). You can set (% style="color:red" %)**AT+RPL=2** (%%)or send the downlink command: (% style="color:red" %)**2102**
457 457  )))
458 458  )))
459 459  
460 460  (((
461 461  (((
462 -If the equipment uses CLASS C. You can set** AT+RPL=4** or send the downlink command: **2104**
581 +If the equipment uses (% style="color:blue" %)**CLASS C**(%%). You can set** (% style="color:red" %)AT+RPL=4(%%)** or send the downlink command: (% style="color:red" %)**2104**
463 463  )))
464 464  )))
465 465  
... ... @@ -466,15 +466,20 @@
466 466  (((
467 467  (((
468 468  When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
588 +
589 +
469 469  )))
470 470  )))
471 471  
472 -[[image:image-20220525091925-32.png]]
593 +[[image:image-20220526141149-31.png]]
473 473  
474 474  downlink
475 475  
476 -= 6. Request Remote Support =
477 477  
598 +
599 += 6.  Request Remote Support =
600 +
601 +
478 478  (((
479 479  These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
480 480  \\If problem not solve, and you need dragino remote support, please follow to this document: [[TTN Support instruction>>url:https://www.dragino.com/downloads/index.php?dir=&file=TTNv3_Support_Guide.pdf]](% style="color:red" %) **If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the screenshots for each step to check. They include:**
... ... @@ -486,39 +486,51 @@
486 486  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
487 487  * End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI)
488 488  
489 -**~1. End Device Join Screen shot, we can check:**
490 490  
614 +(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
615 +
491 491  * If the device is sending join request to server?
492 492  * What frequency the device is sending?
493 493  
494 -[[image:image-20220525092012-33.png]]
495 495  
620 +[[image:image-20220526141308-33.png]]
621 +
496 496  Console Output from End device to see the transmit frequency
497 497  
498 -User can run **AT+CFG **command to print configuration information.
499 499  
500 -* Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
625 +User can run (% style="color:blue" %)**AT+CFG **(%%)command to print configuration information.
501 501  
502 -[[image:image-20220525092043-34.png]]
627 +* Is the device in OTAA mode or ABP mode? (% style="color:red" %)**AT+NJM=1** (%%)(OTAA mode), (% style="color:red" %)**AT+NJM=0**(%%) (ABP mode)
503 503  
629 +
630 +
631 +[[image:image-20220526141612-36.png]]
632 +
633 +
504 504  Console Output from End device to see the transmit frequency
505 505  
506 -**2. Gateway packet traffic in gateway web or ssh. we can check:**
507 507  
637 +
638 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
639 +
508 508  * (((
509 509  If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
510 510  )))
511 511  * (((
512 512  If the gateway gets the Join Accept message from server and transmit it via LoRa?
645 +
646 +
647 +
513 513  )))
514 514  
515 -[[image:image-20220525092124-35.png]]
650 +[[image:image-20220526141739-37.png]]
516 516  
517 517  Console Output from Gateway to see packets between end node and server.
518 518  
519 519  
520 -**3. Gateway Traffic Page in LoRaWAN Server**
521 521  
656 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
657 +
522 522  * (((
523 523  If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
524 524  )))
... ... @@ -527,25 +527,32 @@
527 527  )))
528 528  * (((
529 529  If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
666 +
667 +
668 +
530 530  )))
531 531  
532 -[[image:image-20220525092157-36.png]]
671 +[[image:image-20220526141823-38.png||height="501" width="1144"]]
533 533  
534 534  The Traffic for the End node in the server, use TTNv3 as example
535 535  
536 536  
537 -[[image:image-20220525092231-37.png]]
538 538  
677 +[[image:image-20220526141917-39.png]]
678 +
539 539  The Traffic for the End node in the server, use TTNv3 as example
540 540  
541 -**4. Data Page in LoRaWAN server**
542 542  
682 +
683 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
684 +
543 543  (((
544 544  (((
545 545  (((
546 546  If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
547 547  
548 -[[image:image-20220525092546-1.png]]
690 +
691 +[[image:image-20220526141956-40.png]]
549 549  )))
550 550  )))
551 551  )))
... ... @@ -552,6 +552,8 @@
552 552  
553 553  The data for the end device set in server
554 554  
555 -[[image:image-20220525092430-40.png]]
556 556  
699 +
700 +[[image:image-20220526142033-41.png]]
701 +
557 557  Check if OTAA Keys match the keys in device
image-20220526135845-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +159.3 KB
Content
image-20220526135940-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +32.9 KB
Content
image-20220526140015-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +24.4 KB
Content
image-20220526140044-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +42.0 KB
Content
image-20220526140132-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +60.2 KB
Content
image-20220526140205-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.6 KB
Content
image-20220526140251-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +67.9 KB
Content
image-20220526140347-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +63.0 KB
Content
image-20220526140420-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.4 KB
Content
image-20220526140452-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +32.4 KB
Content
image-20220526140708-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +827.1 KB
Content
image-20220526140856-26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +114.9 KB
Content
image-20220526140936-27.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +103.1 KB
Content
image-20220526141021-28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +74.8 KB
Content
image-20220526141052-29.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +84.1 KB
Content
image-20220526141116-30.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +10.1 KB
Content
image-20220526141149-31.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +59.0 KB
Content
image-20220526141236-32.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +114.0 KB
Content
image-20220526141308-33.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +90.1 KB
Content
image-20220526141350-34.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.7 KB
Content
image-20220526141612-36.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.2 KB
Content
image-20220526141739-37.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +288.0 KB
Content
image-20220526141823-38.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +197.3 KB
Content
image-20220526141917-39.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +154.2 KB
Content
image-20220526141956-40.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +163.5 KB
Content
image-20220526142033-41.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +25.2 KB
Content

Applications

Navigation

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