Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 32.1
edited by Edwin Chen
on 2022/06/10 19:32
Change comment: There is no comment for this version
To version 4.5
edited by Xiaoling
on 2022/05/11 14:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -3,7 +3,6 @@
3 3  {{toc/}}
4 4  
5 5  
6 -
7 7  = 1. OTAA Join Process Debug =
8 8  
9 9  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.
... ... @@ -20,7 +20,7 @@
20 20  * If the device is sending join request to server?
21 21  * What frequency the device is sending?
22 22  
23 -[[image:image-20220526164956-15.png]]
22 +[[image:https://wiki.dragino.com/images/thumb/0/0f/OTAA_Join-1.jpg/600px-OTAA_Join-1.jpg||height="316" width="600"]]
24 24  
25 25  Console Output from End device to see the transmit frequency
26 26  
... ... @@ -30,7 +30,7 @@
30 30  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
31 31  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
32 32  
33 -[[image:image-20220526163608-2.png]]
32 +[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
34 34  
35 35  Console Output from Gateway to see packets between end node and server.
36 36  
... ... @@ -41,7 +41,7 @@
41 41  * If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
42 42  * 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.
43 43  
44 -[[image:image-20220526163633-3.png]]
43 +[[image:https://wiki.dragino.com/images/thumb/5/5c/OTAA_Join-3.png/600px-OTAA_Join-3.png||height="301" width="600"]]
45 45  
46 46  The Traffic for the End node in the server, use TTN as example
47 47  
... ... @@ -50,11 +50,11 @@
50 50  
51 51  * 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.
52 52  
53 -[[image:image-20220526163704-4.png]]
52 +[[image:https://wiki.dragino.com/images/thumb/e/ec/OTAA_Join-4.png/600px-OTAA_Join-4.png||height="181" width="600"]]
54 54  
55 55  The data for the end device set in server
56 56  
57 -[[image:image-20220526163732-5.png]]
56 +[[image:https://wiki.dragino.com/images/thumb/b/b1/OTAA_Join-5.png/600px-OTAA_Join-5.png||height="166" width="600"]]
58 58  
59 59  Check if OTAA Keys match the keys in device
60 60  
... ... @@ -95,15 +95,15 @@
95 95  Here are the freuqency tables for these bands as reference:
96 96  )))
97 97  
98 -[[image:image-20220526163801-6.png]]
97 +[[image:https://wiki.dragino.com/images/thumb/3/3f/US915_FRE_BAND-1.png/600px-US915_FRE_BAND-1.png||height="170" width="600"]]
99 99  
100 100  US915 Channels
101 101  
102 -[[image:image-20220526163926-7.png]]
101 +[[image:https://wiki.dragino.com/images/thumb/8/8a/AU915_FRE_BAND-1.png/600px-AU915_FRE_BAND-1.png||height="167" width="600"]]
103 103  
104 104  AU915 Channels
105 105  
106 -[[image:image-20220526163941-8.png]]
105 +[[image:https://wiki.dragino.com/images/thumb/3/3a/CN470_FRE_BAND-1.png/600px-CN470_FRE_BAND-1.png||height="205" width="600"]]
107 107  
108 108  (((
109 109  CN470 Channels
... ... @@ -113,7 +113,7 @@
113 113  If we look at the [[TTN network server frequency plan>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]], we can see the US915 frequency band use the channel 8~~15.So the End Node must work at the same frequency in US915 8~~15 channels for TTN server.
114 114  )))
115 115  
116 -[[image:image-20220526164052-9.png]]
115 +[[image:https://wiki.dragino.com/images/thumb/9/9a/US915_FRE_BAND-2.png/600px-US915_FRE_BAND-2.png||height="288" width="600"]]
117 117  
118 118  (((
119 119  TTN FREQUENCY PLAN
... ... @@ -167,7 +167,7 @@
167 167  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
168 168  )))
169 169  
170 -[[image:image-20220526164508-10.png]]
169 +[[~[~[image:https://wiki.dragino.com/images/thumb/1/19/ABP_Issue-1.jpg/600px-ABP_Issue-1.jpg~|~|height="340" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:ABP_Issue-1.jpg]]
171 171  
172 172  Disable Frame Counter Check in ABP Mode
173 173  
... ... @@ -182,7 +182,7 @@
182 182  Depends on Class A or Class C, the receive windows will be a little difference,
183 183  )))
184 184  
185 -[[image:image-20220531161828-1.png]]
184 +[[image:https://wiki.dragino.com/images/thumb/1/1a/Downstream_LoRaWAN-1.png/600px-Downstream_LoRaWAN-1.png||height="590" width="600"]]
186 186  
187 187  receive windows for Class A and Class C
188 188  
... ... @@ -194,26 +194,17 @@
194 194  * This packet must match the frequency of the RX1 or RX2 window.
195 195  * This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). **This is the common fail point, because different lorawan server might use different RX2DR and they don't info End Node via ADR message so cause the mismatch. If this happen, user need to change the RX2DR to the right value in end node. In OTAA, LoRaWAN Server will send the RX2DR setting in Join Accept message so the end node will auto adjust. but ABP uplink doesn't support this auto change.**
196 196  
197 -
198 198  == 5.2 See Debug Info ==
199 199  
200 -(((
201 201  **For LoRaWAN Server**
202 -)))
203 203  
204 -(((
205 205  We can check if there is downlink message for this end node, use TTN for example:
206 -)))
207 207  
208 -(((
209 209  Configure a downstream to the end device
210 -)))
211 211  
212 -[[image:image-20220526164623-12.png]]
204 +[[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
213 213  
214 -(((
215 215  Set a downstream in TTN and see it is sent
216 -)))
217 217  
218 218  
219 219  (((
... ... @@ -220,63 +220,66 @@
220 220  This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
221 221  )))
222 222  
223 -[[image:image-20220526164650-13.png]]
213 +[[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
224 224  
225 -(((
226 226  Gateway Traffic can see this downstream info
227 -)))
228 228  
229 229  
230 -(((
231 231  **For LoRaWAN Gateway**
232 -)))
233 233  
234 234  (((
235 235  When the downstream packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragion Gateway, this can be checked by runinng "logread -f" in the SSH console. and see below:
236 236  )))
237 237  
238 -[[image:image-20220526164734-14.png]]
224 +[[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
239 239  
240 -(((
241 241  Gateway Sent out this packet
242 -)))
243 243  
244 244  
245 -(((
246 246  **For End Node**
247 -)))
248 248  
249 -(((
250 250  we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
232 +
233 +(% class="box infomessage" %)
234 +(((
235 + AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
251 251  )))
252 252  
238 +(% class="box infomessage" %)
253 253  (((
254 -
240 + AT+RX2DR=3 ~-~--> The RX2 DataRate
255 255  )))
256 256  
243 +(% class="box infomessage" %)
257 257  (((
245 + AT+RX1DL=1000 ~-~--> Receive Delay 1
246 +)))
247 +
258 258  (% class="box infomessage" %)
259 259  (((
260 -AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
261 -AT+RX2DR=3      ~-~--> The RX2 DataRate
262 -AT+RX1DL=1000   ~-~--> Receive Delay 1
263 -AT+RX2DL=2000   ~-~--> Receive Delay 2
250 + AT+RX2DL=2000 ~-~--> Receive Delay 2
264 264  )))
265 -)))
266 266  
267 267  (((
268 268  **when the device running, we can see below info:**
269 269  )))
270 270  
271 -{{{ [12502]***** UpLinkCounter= 0 *****
272 - [12503]TX on freq 868500000 Hz at DR 0
273 - [13992]txDone
274 - [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
275 - [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
276 - [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
277 - [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
257 +(((
258 +
259 +)))
278 278  
261 +(% class="box" %)
279 279  (((
263 + [12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~**
264 + [12503]TX on freq 868500000 Hz at DR 0
265 + [13992]txDone
266 + [15022]RX on freq 868500000 Hz at DR 0     ~-~-> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
267 + [15222]rxTimeOut                           ~-~-> no packet arrive in RX1 window. (duration: 200ms)
268 + [15987]RX on freq 869525000 Hz at DR 3     ~-~-> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
269 + [16027]rxTimeOut                           ~-~-> no packet arrive in RX2 window. (duration: 40 ms)
270 +)))
271 +
272 +(((
280 280  
281 281  )))
282 282  
... ... @@ -284,21 +284,21 @@
284 284  **Another message:**
285 285  )))
286 286  
287 -{{{ [12502]***** UpLinkCounter= 0 *****
288 - [12503]TX on freq 868100000 Hz at DR 0
289 - [13992]txDone
290 - [15022]RX on freq 868100000 Hz at DR 0
291 - [15222]rxTimeOut
292 - [15987]RX on freq 869525000 Hz at DR 3
293 - [16185]rxDone --> We have got the downstream packet.
294 - Rssi= -64
295 - Receive data
296 - 1:0012345678}}}
297 297  
281 + [12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~**
282 + [12503]TX on freq 868100000 Hz at DR 0
283 + [13992]txDone
284 + [15022]RX on freq 868100000 Hz at DR 0
285 + [15222]rxTimeOut
286 + [15987]RX on freq 869525000 Hz at DR 3
287 + [16185]rxDone                              ~-~-> We have got the downstream packet.
288 + Rssi= -64
289 + Receive data
290 + 1:0012345678
298 298  
299 299  == 5.3 If problem doesn’t solve ==
300 300  
301 -(% style="color:red" %)**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
294 +**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
302 302  
303 303  * End node console to show the transmit freuqency and DR.
304 304  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
... ... @@ -305,7 +305,6 @@
305 305  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
306 306  * End Node traffic (from server UI) to shows end node activity in server.
307 307  
308 -
309 309  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
310 310  
311 311  (((
... ... @@ -320,10 +320,8 @@
320 320  So if the LoRaWAN server is an AS923 server which ask the gateway to transmit at 923.2Mhz frequency, but the gateway is IN868 frequency band (support 865~~867Mhz to transmit). In the gateway log it will show something like below:
321 321  )))
322 322  
323 -{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}}
324 -
325 325  (((
326 -
316 +Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)
327 327  )))
328 328  
329 329  (((
... ... @@ -337,24 +337,29 @@
337 337  
338 338  (% class="box infomessage" %)
339 339  (((
340 -**Change to ABP Mode: AT+NJM=0**
341 -**Change to fix frequency: AT+CHS=904900000**
342 -**Change to fix DR: AT+DR=0**
330 +Change to ABP Mode: AT+NJM=0
343 343  )))
344 344  
345 -[[image:image-20220526165525-16.png]]
333 +(% class="box infomessage" %)
334 +(((
335 +Change to fix frequency: AT+CHS=904900000
336 +)))
346 346  
338 +(% class="box infomessage" %)
339 +(((
340 +Change to fix DR: AT+DR=0
341 +)))
347 347  
343 +[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
344 +
348 348  2. In LG02 , configure to receive above message
349 349  
350 -[[image:image-20220526165612-17.png]]
347 +[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
351 351  
352 -
353 353  In LG02 console, we can see the hex receive are:
354 354  
355 -[[image:image-20220526171112-21.png]]
351 +[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
356 356  
357 -
358 358  3. Decode the info in web
359 359  
360 360  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
... ... @@ -369,11 +369,9 @@
369 369  
370 370  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111]]
371 371  
372 -[[image:image-20220526171029-20.png]]
367 +[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
373 373  
374 -(((
375 - The FRMPayload is the device payload.
376 -)))
369 +The FRMPayload is the device payload.
377 377  
378 378  
379 379  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
... ... @@ -380,121 +380,34 @@
380 380  
381 381  Since firmware v1.8, LHT65 will send MAC command to request time, in the case if DR only support max 11 bytes, this MAC command will be bundled to a separate uplink payload with 0x00.
382 382  
383 -
384 384  = 9. Why do I see a "MIC Mismatch" error message from the server? =
385 385  
386 -(((
387 387  1)If the user receives a "MIC Mismatch" message after registering the node on the server.
388 -)))
389 389  
390 -(((
391 391  It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
392 -)))
393 393  
394 -* (((
395 -Please note the distinction between "APPKEY" and "APPSKEY".
396 -)))
382 +* Please note the distinction between "APPKEY" and "APPSKEY".
397 397  
398 -(((
399 399  2）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
400 -)))
401 401  
402 -(((
403 403  The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
404 -)))
405 405  
406 -* (((
407 -If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
388 +* If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
408 408  
409 -
410 -)))
411 -
412 412  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
413 413  
414 414  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
415 415  
416 -(((
417 417  When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
418 -)))
419 419  
420 -(((
421 -When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the node,and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,so it will send a normal uplink packet, and an additional 00 data packet.
422 -)))
396 +When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the node,
423 423  
424 -* (((
425 -Solution: Use the decoder to filter out this 00 packet.
426 -)))
427 -* (((
428 -Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to [[david.huang@dragino.cc>>mailto:david.huang@dragino.cc]]
398 +and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
429 429  
430 -
431 -)))
400 +so it will send a normal uplink packet, and an additional 00 data packet.
432 432  
433 -= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
402 +* Solution: Use the decoder to filter out this 00 packet.
403 +* Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to david.huang@dragino.cc
434 434  
435 -(((
436 -It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
437 -)))
438 -
439 -(((
440 -AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
441 -)))
442 -
443 -(((
444 -AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
445 -)))
446 -
447 -(((
448 -AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
449 -)))
450 -
451 -(((
452 -AT+APPEUI=00 00 00 00 00 00 00 00
453 -)))
454 -
455 -(((
405 +(% class="wikigeneratedid" id="H" %)
456 456  
457 -)))
458 -
459 -(((
460 -You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
461 -)))
462 -
463 -(((
464 -You can rewrites the keys by running commands in AT Console
465 -)))
466 -
467 -(((
468 -**For example：**
469 -)))
470 -
471 -(((
472 -AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
473 -)))
474 -
475 -(((
476 -AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
477 -)))
478 -
479 -(((
480 -AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
481 -)))
482 -
483 -(((
484 -AT+APPEUI=2C 45 47 E3 24 12 23 24
485 -)))
486 -
487 -(((
488 -(Any combination of 16 bit codes can be used）
489 -
490 -
491 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
492 -)))
493 -
494 -
495 -Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
496 -
497 -
498 -
499 -(% class="wikigeneratedid" %)
500 -
image-20220526163523-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -633.8 KB
Content
image-20220526163608-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -116.4 KB
Content
image-20220526163633-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -65.6 KB
Content
image-20220526163704-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
image-20220526163732-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -18.5 KB
Content
image-20220526163801-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.3 KB
Content
image-20220526163926-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.4 KB
Content
image-20220526163941-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.9 KB
Content
image-20220526164052-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -59.3 KB
Content
image-20220526164508-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -50.2 KB
Content
image-20220526164547-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.9 KB
Content
image-20220526164623-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.2 KB
Content
image-20220526164650-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -45.0 KB
Content
image-20220526164734-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -120.3 KB
Content
image-20220526164956-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -634.4 KB
Content
image-20220526165525-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -185.4 KB
Content
image-20220526165612-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -116.5 KB
Content
image-20220526165855-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -183.7 KB
Content
image-20220526170151-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -70.4 KB
Content
image-20220526171029-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -70.6 KB
Content
image-20220526171112-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -183.8 KB
Content
image-20220531161828-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.6 KB
Content