Changes for page Notes for TTN

Last modified by Mengting Qiu on 2024/08/20 17:29
<
From version < 49.1 >
edited by Xiaoling
on 2022/05/25 09:35
To version < 99.14 >
edited by Xiaoling
on 2022/07/25 09:10
>
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  )))
... ... @@ -15,10 +15,14 @@
15 15  
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.
22 +
23 +
24 +
18 18  )))
19 19  
20 -=== 1.1.2 Login or crate an account ===
27 +=== 1.1.2  Login or crate an account ===
21 21  
29 +
22 22  (((
23 23  [[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.
24 24  )))
... ... @@ -25,42 +25,60 @@
25 25  
26 26  (((
27 27  Once you have an account,get started by following steps for adding Gateway,Device and Intergrations.
36 +
37 +
38 +
28 28  )))
29 29  
30 -=== 1.1.3 List the support products and Requirements ===
41 +=== 1.1.3  List the support products and Requirements ===
31 31  
43 +
32 32  LoRaWAN Gateway model: Existing Gateway
33 33  
34 -= 2. Gateway Registration for Semtech UDP =
35 35  
36 -== 2.1 Primary LoRaWAN Server ==
37 37  
38 -[[image:image-20220525093339-3.png]]
48 += 2.  Gateway Registration for Semtech UDP =
39 39  
50 +
51 +== 2.1  Primary LoRaWAN Server ==
52 +
53 +
54 +[[image:image-20220526134633-2.png||height="616" width="1323"]]
55 +
40 40  Register Gateway
41 41  
42 42  
43 -[[image:image-20220525093402-4.png]]
44 44  
60 +[[image:image-20220526134826-4.png]]
61 +
45 45  Put Gateway ID
46 46  
47 47  
48 48  
66 +[[image:image-20220526134759-3.png]]
67 +
49 49  Choose Frequency Band
50 50  
51 51  
52 -[[image:image-20220525093308-2.png]]
53 53  
72 +[[image:image-20220526134919-5.png]]
73 +
54 54  Show Status
55 55  
56 -== 2.2 Secondary LoRaWAN Server ==
57 57  
58 -=== 2.2.1 Introduction ===
59 59  
78 +== 2.2  Secondary LoRaWAN Server ==
79 +
80 +
81 +=== 2.2.1  Introduction ===
82 +
83 +
60 60  The Dragino gateway has supports the Secondary server settings.
61 61  
62 -=== 2.2.2 Below list the support products and Requirements: ===
63 63  
87 +=== 2.2.2  Below list the support products and Requirements: ===
88 +
89 +
64 64  (((
65 65  ~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]]
66 66  )))
... ... @@ -69,62 +69,85 @@
69 69  2. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
70 70  )))
71 71  
72 -=== 2.2.3 Example ===
73 73  
74 -The following takes Helium as a Secondary LoRaWAN server as an example,
75 75  
76 -=== 2.2.4 Step 1: Download and Install the helium gateway-rs ===
100 +=== 2.2.3  Example ===
77 77  
102 +
103 +The following takes Helium as a Secondary LoRaWAN server as an example
104 +
105 +
106 +
107 +=== 2.2.4  Step 1: Download and Install the helium gateway-rs ===
108 +
109 +
78 78  The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
79 79  
80 -[[image:image-20220525085117-5.png]]
112 +[[image:image-20220526135049-6.png]]
81 81  
82 82  Download and Install gateway-rs
83 83  
84 -=== 2.2.5 Step 2: Back to Semtech UDP page ===
85 85  
117 +
118 +=== 2.2.5  Step 2: Back to Semtech UDP page ===
119 +
120 +
86 86  Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
87 87  
88 -[[image:image-20220525085152-6.png]]
123 +​​​​[[image:image-20220526135125-7.png]]
89 89  
90 90  Configuration of helium
91 91  
92 -= 3. Gateway Registration for Basics Station =
93 93  
94 -== 3.1 Introduction ==
95 95  
129 += 3.  Gateway Registration for Basics Station =
130 +
131 +
132 +== 3.1  Introduction ==
133 +
134 +
96 96  (((
97 97  (((
98 98  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 +
99 99  )))
100 100  )))
101 101  
102 102  (((
103 -**Below list the support products and Requirements:**
144 +(% style="color:blue" %)**Below list the support products and Requirements:**
104 104  )))
105 105  
106 106  (((
107 107  (((
108 - ~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]]
109 109  )))
110 110  
111 111  (((
112 112   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 +
113 113  )))
114 114  )))
115 115  
116 116  (((
117 -**What do you need to prepare**
162 +(% style="color:blue" %)**What do you need to prepare**
118 118  )))
119 119  
120 120  (((
121 121  (((
122 122  A gateway that can access the internet normally
168 +
169 +
170 +
123 123  )))
124 124  )))
125 125  
126 -== 3.2 Step 1. Add Gateway ==
174 +== 3.2  Step 1: Add Gateway ==
127 127  
176 +
128 128  (((
129 129  (((
130 130  The example for **EU**
... ... @@ -140,92 +140,129 @@
140 140  (((
141 141  (((
142 142  Following picture is the successful added.
192 +
193 +
143 143  )))
144 144  )))
145 145  
146 -[[image:image-20220525085231-7.png]]
197 +[[image:image-20220526135316-8.png]]
147 147  
148 148  Add Gateway
149 149  
150 -== 3.3 Step 2. Create the API key ==
151 151  
202 +
203 +== 3.3  Step 2: Create the API key ==
204 +
205 +
152 152  user need to create the CUPS API key and LNS API key.
153 153  
154 -[[image:image-20220525085329-8.png]]
155 155  
209 +[[image:image-20220526135349-9.png]]
210 +
156 156  Create CUPS API key
157 157  
158 158  
159 -[[image:image-20220525085414-9.png]]
160 160  
215 +[[image:image-20220526135428-10.png]]
216 +
161 161  Create LNS API key
162 162  
219 +
163 163  (% style="color:red" %)**Note : Please copy the API key.**
164 164  
165 -== 3.4 Step 3. Update the gateway setting ==
166 166  
223 +
224 +== 3.4  Step 3: Update the gateway setting ==
225 +
226 +
167 167  In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
168 168  
169 -[[image:image-20220525085441-10.png]]
170 170  
230 +[[image:image-20220526135528-11.png]]
231 +
171 171  paste the API key
172 172  
173 -== 3.5 Step 4. Access the gateway GUI ==
174 174  
235 +
236 +== 3.5  Step 4: Access the gateway GUI ==
237 +
238 +
175 175  User need to update the API key and install the Certificate
176 176  
177 -[[image:image-20220525085522-11.png]]
178 178  
242 +[[image:image-20220526135601-12.png]]
243 +
179 179  Access the gateway GUI
180 180  
181 -== 3.6 Step 5. Configure Station ==
182 182  
247 +
248 +== 3.6  Step 5: Configure Station ==
249 +
250 +
183 183  User need to input Server URI, Server CUPS Key and LNS Key, as well as install CUPS certificate.
184 184  
185 -**just to clarify.**
186 186  
254 +(% style="color:blue" %)**just to clarify:**
255 +
187 187  (% class="box" %)
188 188  (((
189 - CUPS Server URI  ~-~-> Server Adress
190 - CUPS Authorization Key         ~-~-> Server CUPS API Key
191 - LNS Authorization Key  ~-~-> Server LNS API Key
192 - 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)
193 193  )))
194 194  
195 -[[image:image-20220525085557-12.png]]
264 +[[image:image-20220526135654-13.png]]
196 196  
197 197  Congfigure Station
198 198  
199 -== 3.7 Start Station ==
200 200  
269 +
270 +== 3.7  Start Station ==
271 +
272 +
201 201  (((
202 202  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
275 +
276 +
277 +
203 203  )))
204 204  
205 -== 3.8 Siccessful Connection ==
280 +== 3.8  Siccessful Connection ==
206 206  
282 +
207 207  If user completes the above steps,which will see live date in the TTN.
208 208  
209 -[[image:image-20220525085636-13.png]]
210 210  
286 +[[image:image-20220526135734-14.png]]
287 +
211 211  Station live date
212 212  
213 -== 3.9 Trouble Shooting ==
214 214  
291 +
292 +== 3.9  Trouble Shooting ==
293 +
294 +
215 215  User can check the station log in the logread/system log page.
216 216  
217 -[[image:image-20220525090622-14.png]]
218 218  
298 +[[image:image-20220526135845-15.png]]
299 +
219 219  Station Log
220 220  
302 +
303 +
221 221  and recode the station log in the system/Recode log page.
222 222  
223 -[[image:image-20220525090705-15.png]]
306 +[[image:image-20220526135940-16.png]]
224 224  
225 225  Recore Log
226 226  
227 -= 4. Configure node connection to TTNv3 =
228 228  
311 +
312 += 4.  Configure node connection to TTNv3 =
313 +
314 +
229 229  (((
230 230  (((
231 231  Following is an example for how to join the TTN v3 LoRaWAN Network.
... ... @@ -241,11 +241,15 @@
241 241  (((
242 242  (((
243 243  We take LES01 as an example.
330 +
331 +
332 +
244 244  )))
245 245  )))
246 246  
247 -== 4.1 Step1 ==
336 +== 4.1  Step1 ==
248 248  
338 +
249 249  (((
250 250  (((
251 251  Create a device in TTN with the OTAA keys from LSE01.
... ... @@ -264,44 +264,65 @@
264 264  )))
265 265  )))
266 266  
267 -[[image:image-20220525090739-16.png]]
357 +[[image:image-20220526140015-17.png]]
268 268  
269 -[[image:image-20220525090833-17.png]]
359 +[[image:image-20220526140044-18.png]]
270 270  
271 -== 4.2 Step2 ==
272 272  
362 +
363 +== 4.2  Step2 ==
364 +
365 +
273 273  (((
274 274  (((
275 275  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 +
276 276  )))
277 277  )))
278 278  
279 -[[image:image-20220525090920-18.png]]
374 +[[image:image-20220526140132-19.png]]
280 280  
281 -== 4.3 Step3 ==
282 282  
377 +
378 +== 4.3  Step3 ==
379 +
380 +
283 283  Add APP EUI in the application:
284 284  
285 -[[image:image-20220525091022-19.png]]
286 286  
287 -== 4.4 Step4 ==
384 +[[image:image-20220526140205-20.png]]
288 288  
386 +
387 +
388 +== 4.4  Step4 ==
389 +
390 +
289 289  Add APP KEY and DEV EUI:
290 290  
291 -[[image:image-20220525091128-20.png]]
292 292  
293 -= 5. TTN V3 integrated into MQTT server =
394 +[[image:image-20220526140251-21.png]]
294 294  
295 -== 5.1 Introduction ==
296 296  
397 +
398 += 5.  TTN V3 integrated into MQTT server =
399 +
400 +
401 +== 5.1  Introduction ==
402 +
403 +
297 297  (((
298 298  (((
299 299  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 +
300 300  )))
301 301  )))
302 302  
303 -== 5.2 Create device steps at MQTT ==
413 +== 5.2  Create device steps at MQTT ==
304 304  
415 +
305 305  (((
306 306  (((
307 307  The user creates a new API KEY after creating a device on TTN V3.
... ... @@ -317,16 +317,20 @@
317 317  (((
318 318  (((
319 319  Fill in Broker Address and Broker port.
431 +
432 +
320 320  )))
321 321  )))
322 322  
323 -[[image:image-20220525091251-22.png]]
436 +[[image:image-20220526140347-22.png]]
324 324  
325 325  Fill in the username and password into MQTT.
326 326  
327 327  
328 -[[image:image-20220525091333-23.png]]
329 329  
442 +[[image:image-20220526140420-23.png]]
443 +
444 +
330 330  The Application Server publishes uplink traffic on the following topics:
331 331  
332 332  (% class="box" %)
... ... @@ -343,13 +343,18 @@
343 343  )))
344 344  
345 345  (((
461 +
462 +
346 346  (((
347 -**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 +
348 348  )))
349 349  )))
350 350  
351 -[[image:image-20220525091430-24.png]]
470 +[[image:image-20220526140452-24.png]]
352 352  
472 +
353 353  (((
354 354  (((
355 355  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.
... ... @@ -356,7 +356,7 @@
356 356  )))
357 357  )))
358 358  
359 -[[image:image-20220525091458-25.png]]
479 +[[image:image-20220526140708-25.png]]
360 360  
361 361  (((
362 362  (((
... ... @@ -366,7 +366,11 @@
366 366  
367 367  (((
368 368  (((
369 -**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 +
370 370  )))
371 371  )))
372 372  
... ... @@ -376,20 +376,27 @@
376 376  )))
377 377  )))
378 378  
379 -[[image:image-20220525091618-27.png]]
503 +[[image:image-20220526140856-26.png]]
380 380  
381 381  (((
382 382  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 +
383 383  )))
384 384  
385 385  (((
386 -**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 +
387 387  )))
388 388  
389 -[[image:image-20220525091702-28.png]]
517 +[[image:image-20220526140936-27.png]]
390 390  
391 -== 5.3 Send Downlink message ==
392 392  
520 +
521 +== 5.3  Send Downlink message ==
522 +
523 +
393 393  (((
394 394  How to configure downlink in TTN V3?
395 395  )))
... ... @@ -399,31 +399,40 @@
399 399  )))
400 400  
401 401  (((
402 -Downlink command:01 00 00 5A
533 +(% style="color:blue" %)**Downlink command: 01 00 00 5A**
534 +
535 +
403 403  )))
404 404  
405 -[[image:image-20220525091752-29.png]]
538 +[[image:image-20220526141021-28.png]]
406 406  
407 407  downlink
408 408  
542 +
543 +
409 409  After sending, you can view it in live data.
410 410  
411 -[[image:image-20220525091816-30.png]]
546 +[[image:image-20220526141052-29.png]]
412 412  
413 413  downlink
414 414  
550 +
551 +
415 415  (((
416 416  When downlink is successfully sent, the downlink information can be received on the serial port.
417 417  )))
418 418  
419 419  (((
420 -**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 +
421 421  )))
422 422  
423 -[[image:image-20220525091855-31.png]]
562 +[[image:image-20220526141116-30.png]]
424 424  
425 425  downlink
426 426  
566 +
427 427  (((
428 428  (((
429 429  If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
... ... @@ -432,13 +432,13 @@
432 432  
433 433  (((
434 434  (((
435 -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**
436 436  )))
437 437  )))
438 438  
439 439  (((
440 440  (((
441 -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**
442 442  )))
443 443  )))
444 444  
... ... @@ -445,15 +445,19 @@
445 445  (((
446 446  (((
447 447  When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
588 +
589 +
448 448  )))
449 449  )))
450 450  
451 -[[image:image-20220525091925-32.png]]
593 +[[image:image-20220526141149-31.png]]
452 452  
453 453  downlink
454 454  
455 -= 6. Request Remote Support =
456 456  
598 +
599 += 6.  Request Remote Support =
600 +
457 457  (((
458 458  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.
459 459  \\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:**
... ... @@ -470,7 +470,7 @@
470 470  * If the device is sending join request to server?
471 471  * What frequency the device is sending?
472 472  
473 -[[image:image-20220525092012-33.png]]
617 +[[image:image-20220526141308-33.png]]
474 474  
475 475  Console Output from End device to see the transmit frequency
476 476  
... ... @@ -478,10 +478,12 @@
478 478  
479 479  * Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
480 480  
481 -[[image:image-20220525092043-34.png]]
625 +[[image:image-20220526141612-36.png]]
482 482  
627 +
483 483  Console Output from End device to see the transmit frequency
484 484  
630 +
485 485  **2. Gateway packet traffic in gateway web or ssh. we can check:**
486 486  
487 487  * (((
... ... @@ -491,7 +491,7 @@
491 491  If the gateway gets the Join Accept message from server and transmit it via LoRa?
492 492  )))
493 493  
494 -[[image:image-20220525092124-35.png]]
640 +[[image:image-20220526141739-37.png]]
495 495  
496 496  Console Output from Gateway to see packets between end node and server.
497 497  
... ... @@ -508,15 +508,16 @@
508 508  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.
509 509  )))
510 510  
511 -[[image:image-20220525092157-36.png]]
657 +[[image:image-20220526141823-38.png||height="501" width="1144"]]
512 512  
513 513  The Traffic for the End node in the server, use TTNv3 as example
514 514  
515 515  
516 -[[image:image-20220525092231-37.png]]
662 +[[image:image-20220526141917-39.png]]
517 517  
518 518  The Traffic for the End node in the server, use TTNv3 as example
519 519  
666 +
520 520  **4. Data Page in LoRaWAN server**
521 521  
522 522  (((
... ... @@ -524,7 +524,7 @@
524 524  (((
525 525  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.
526 526  
527 -[[image:image-20220525092546-1.png]]
674 +[[image:image-20220526141956-40.png]]
528 528  )))
529 529  )))
530 530  )))
... ... @@ -531,6 +531,7 @@
531 531  
532 532  The data for the end device set in server
533 533  
534 -[[image:image-20220525092430-40.png]]
535 535  
682 +[[image:image-20220526142033-41.png]]
683 +
536 536  Check if OTAA Keys match the keys in device
image-20220525093626-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +92.9 KB
Content
image-20220525093929-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +107.5 KB
Content
image-20220525094010-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.4 KB
Content
image-20220525094115-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +60.7 KB
Content
image-20220525094146-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +65.2 KB
Content
image-20220525094220-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +72.6 KB
Content
image-20220525094257-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +117.3 KB
Content
image-20220525094329-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +130.0 KB
Content
image-20220525094409-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +113.6 KB
Content
image-20220526134447-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +278.2 KB
Content
image-20220526134633-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +86.7 KB
Content
image-20220526134759-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +113.4 KB
Content
image-20220526134826-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +149.6 KB
Content
image-20220526134919-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +123.3 KB
Content
image-20220526135049-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +79.8 KB
Content
image-20220526135125-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.4 KB
Content
image-20220526135316-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.1 KB
Content
image-20220526135349-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +69.4 KB
Content
image-20220526135428-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +68.6 KB
Content
image-20220526135528-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +104.4 KB
Content
image-20220526135601-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +115.2 KB
Content
image-20220526135654-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +123.6 KB
Content
image-20220526135734-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +122.5 KB
Content
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