Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 32.2
edited by Xiaoling
on 2022/07/13 14:44
Change comment: There is no comment for this version
To version 4.2
edited by Xiaoling
on 2022/05/11 14:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,9 +1,8 @@
1 -**~ Table of Contents:**
1 +**~ Contents:**
2 2  
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,33 +95,25 @@
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 -(((
109 109  CN470 Channels
110 -)))
111 111  
112 -(((
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 -)))
115 115  
116 -[[image:image-20220526164052-9.png]]
111 +[[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 -(((
119 119  TTN FREQUENCY PLAN
120 -)))
121 121  
122 -(((
123 123  In dragino end node, user can use AT+CHE command to set what frequencies set the end node will use. The default settings for Dragino end node are preconfigure for TTN server, so use 8~~15 channels, which is **AT+CHE=2**. (AT+CHE=1 for first 8 channels, AT+CHE=2 for second 8 channels.. etc, and AT+CHE=0 for all 72 channels. )
124 -)))
125 125  
126 126  
127 127  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
... ... @@ -132,42 +132,20 @@
132 132  * **Gateway** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
133 133  * **LoRaWAN server** ~-~-> ChirpStack default installation and use Sub-band1, **enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7]** in the file chirpstack-network-server.toml.
134 134  
135 -(((
136 136  When Sensor power on, it will use sub-band2 to join the network, the frequency matches the settings in gateway so all Join Request will be passed to the server for Join. Server will ask the sensor to change to Sub-band1 in the Join Accept downlink message. Sensor will change to sub-band1 for data upload. This cause the sensor and gateway have different frequencies so user see lost of most data or even no data.
137 -)))
138 138  
139 -(((
140 -
141 -)))
142 -
143 -(((
144 144  Use Subband2 as a default subband cause the sensor to have problem to work with the LoRaWAN server which use other subband, and use need to access to the end node to change the subband by console. that is not user frendily,. So since Dragino LoRaWAN Stack version DLS-005(release on end of 2020), we have changed the device to use All Subbands for OTAA join, for example, device will use the first frequency in Sub-Band1 as firt OTAA join packet, then use the first frequency in Sub-Band 2 , then first frequency in sub-band 3, and so on. LoRaWAN server will normally provide the required subband in the OTAA accept process, so end node will know what subband it use after join. If LoRaWAN server doesn't provide subband info in OTAA join, end node will use the subband which join success as the working subband. So the new method cause a longer OTAA Join time but will be compatible with all LoRaWAN server. And new method won't affect the normal uplink after Join Success.
145 -)))
146 146  
147 147  
148 148  = 4. Transmision on ABP Mode =
149 149  
150 -(((
151 151  In ABP mode, there is a Frame Counter Checks. With this check enabled, the server will only accept the frame with a higher counter. If you reboot the device in ABP mode, the device will start from count 0, so you won't be able to see the frame update in server.
152 -)))
153 153  
154 -(((
155 -
156 -)))
157 -
158 -(((
159 159  So in ABP mode, first check if the packet already arrive your gateway, if the packet arrive gatewat but didn't arrive server. Please check if this is the issue.
160 -)))
161 161  
162 -(((
163 -
164 -)))
165 -
166 -(((
167 167  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
168 -)))
169 169  
170 -[[image:image-20220526164508-10.png]]
139 +[[~[~[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  
... ... @@ -178,11 +178,9 @@
178 178  
179 179  LoRaWAN End node will open two receive windows to receive the downstream data. If the downstream packets arrive the end node at these receive windows, the end node will be able to get this packet and process it.
180 180  
181 -(((
182 182  Depends on Class A or Class C, the receive windows will be a little difference,
183 -)))
184 184  
185 -[[image:image-20220531161828-1.png]]
152 +[[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  
... ... @@ -196,108 +196,84 @@
196 196  
197 197  == 5.2 See Debug Info ==
198 198  
199 -(((
200 200  **For LoRaWAN Server**
201 -)))
202 202  
203 -(((
204 204  We can check if there is downlink message for this end node, use TTN for example:
205 -)))
206 206  
207 -(((
208 208  Configure a downstream to the end device
209 -)))
210 210  
211 -[[image:image-20220526164623-12.png]]
172 +[[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
212 212  
213 -(((
214 214  Set a downstream in TTN and see it is sent
215 -)))
216 216  
217 217  
218 -(((
219 219  This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
220 -)))
221 221  
222 -[[image:image-20220526164650-13.png]]
179 +[[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
223 223  
224 -(((
225 225  Gateway Traffic can see this downstream info
226 -)))
227 227  
228 228  
229 -(((
230 230  **For LoRaWAN Gateway**
231 -)))
232 232  
233 -(((
234 234  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:
235 -)))
236 236  
237 -[[image:image-20220526164734-14.png]]
188 +[[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
238 238  
239 -(((
240 240  Gateway Sent out this packet
241 -)))
242 242  
243 243  
244 -(((
245 245  **For End Node**
246 -)))
247 247  
248 -(((
249 249  we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
250 -)))
251 251  
197 +(% class="box infomessage" %)
252 252  (((
253 -
199 +AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
254 254  )))
255 255  
256 -(((
257 257  (% class="box infomessage" %)
258 258  (((
259 -AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
260 -AT+RX2DR=3      ~-~--> The RX2 DataRate
261 -AT+RX1DL=1000   ~-~--> Receive Delay 1
262 -AT+RX2DL=2000   ~-~--> Receive Delay 2
204 +AT+RX2DR=3 ~-~--> The RX2 DataRate
263 263  )))
264 -)))
265 265  
207 +(% class="box infomessage" %)
266 266  (((
267 -**when the device running, we can see below info:**
209 +AT+RX1DL=1000 ~-~--> Receive Delay 1
268 268  )))
269 269  
270 -{{{ [12502]***** UpLinkCounter= 0 *****
271 - [12503]TX on freq 868500000 Hz at DR 0
272 - [13992]txDone
273 - [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
274 - [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
275 - [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
276 - [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
277 -
212 +(% class="box infomessage" %)
278 278  (((
279 -
214 +AT+RX2DL=2000 ~-~--> Receive Delay 2
280 280  )))
281 281  
282 -(((
283 -**Another message:**
284 -)))
217 +when the device running, we can see below info:
285 285  
286 -{{{ [12502]***** UpLinkCounter= 0 *****
287 - [12503]TX on freq 868100000 Hz at DR 0
288 - [13992]txDone
289 - [15022]RX on freq 868100000 Hz at DR 0
290 - [15222]rxTimeOut
291 - [15987]RX on freq 869525000 Hz at DR 3
292 - [16185]rxDone --> We have got the downstream packet.
293 - Rssi= -64
294 - Receive data
295 - 1:0012345678}}}
219 +{{{[12502]***** UpLinkCounter= 0 *****
220 +[12503]TX on freq 868500000 Hz at DR 0
221 +[13992]txDone
222 +[15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
223 +[15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
224 +[15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
225 +[16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)
226 +}}}
296 296  
228 +{{{Another message:
229 +[12502]***** UpLinkCounter= 0 *****
230 +[12503]TX on freq 868100000 Hz at DR 0
231 +[13992]txDone
232 +[15022]RX on freq 868100000 Hz at DR 0
233 +[15222]rxTimeOut
234 +[15987]RX on freq 869525000 Hz at DR 3
235 +[16185]rxDone --> We have got the downstream packet.
236 +Rssi= -64
237 +Receive data
238 +1:0012345678
239 +}}}
297 297  
298 298  == 5.3 If problem doesn’t solve ==
299 299  
300 -(% 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:**
243 +**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:**
301 301  
302 302  * End node console to show the transmit freuqency and DR.
303 303  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
... ... @@ -306,27 +306,14 @@
306 306  
307 307  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
308 308  
309 -(((
310 310  In LoRaWAN, the gatewat will use the frequency specify by the server to transmit a packet as downlink purpose. Each Frequency band has different downlink frequency. and the gateway has a frequency range limited to transmit downlink.
311 -)))
312 312  
313 -(((
314 -
315 -)))
316 -
317 -(((
318 318  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:
319 -)))
320 320  
321 -{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}}
256 +{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)
257 +}}}
322 322  
323 -(((
324 -
325 -)))
326 -
327 -(((
328 328  In this case, please double check the gateway frequency and the server frequency band.
329 -)))
330 330  
331 331  
332 332  = 7. Decrypt a LoRaWAN Packet =
... ... @@ -335,24 +335,29 @@
335 335  
336 336  (% class="box infomessage" %)
337 337  (((
338 -**Change to ABP Mode: AT+NJM=0**
339 -**Change to fix frequency: AT+CHS=904900000**
340 -**Change to fix DR: AT+DR=0**
268 +Change to ABP Mode: AT+NJM=0
341 341  )))
342 342  
343 -[[image:image-20220526165525-16.png]]
271 +(% class="box infomessage" %)
272 +(((
273 +Change to fix frequency: AT+CHS=904900000
274 +)))
344 344  
276 +(% class="box infomessage" %)
277 +(((
278 +Change to fix DR: AT+DR=0
279 +)))
345 345  
281 +[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
282 +
346 346  2. In LG02 , configure to receive above message
347 347  
348 -[[image:image-20220526165612-17.png]]
285 +[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
349 349  
350 -
351 351  In LG02 console, we can see the hex receive are:
352 352  
353 -[[image:image-20220526171112-21.png]]
289 +[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
354 354  
355 -
356 356  3. Decode the info in web
357 357  
358 358  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
... ... @@ -367,11 +367,9 @@
367 367  
368 368  [[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]]
369 369  
370 -[[image:image-20220526171029-20.png]]
305 +[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
371 371  
372 -(((
373 - The FRMPayload is the device payload.
374 -)))
307 +The FRMPayload is the device payload.
375 375  
376 376  
377 377  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
... ... @@ -378,121 +378,34 @@
378 378  
379 379  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.
380 380  
381 -
382 382  = 9. Why do I see a "MIC Mismatch" error message from the server? =
383 383  
384 -(((
385 385  1)If the user receives a "MIC Mismatch" message after registering the node on the server.
386 -)))
387 387  
388 -(((
389 389  It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
390 -)))
391 391  
392 -* (((
393 -Please note the distinction between "APPKEY" and "APPSKEY".
394 -)))
320 +* Please note the distinction between "APPKEY" and "APPSKEY".
395 395  
396 -(((
397 397  2）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
398 -)))
399 399  
400 -(((
401 401  The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
402 -)))
403 403  
404 -* (((
405 -If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
326 +* If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
406 406  
407 -
408 -)))
409 -
410 410  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
411 411  
412 412  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
413 413  
414 -(((
415 415  When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
416 -)))
417 417  
418 -(((
419 -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.
420 -)))
334 +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,
421 421  
422 -* (((
423 -Solution: Use the decoder to filter out this 00 packet.
424 -)))
425 -* (((
426 -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]]
336 +and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
427 427  
428 -
429 -)))
338 +so it will send a normal uplink packet, and an additional 00 data packet.
430 430  
431 -= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
340 +* Solution: Use the decoder to filter out this 00 packet.
341 +* 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
432 432  
433 -(((
434 -It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
435 -)))
436 -
437 -(((
438 -AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
439 -)))
440 -
441 -(((
442 -AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
443 -)))
444 -
445 -(((
446 -AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
447 -)))
448 -
449 -(((
450 -AT+APPEUI=00 00 00 00 00 00 00 00
451 -)))
452 -
453 -(((
343 +(% class="wikigeneratedid" id="H" %)
454 454  
455 -)))
456 -
457 -(((
458 -You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
459 -)))
460 -
461 -(((
462 -You can rewrites the keys by running commands in AT Console
463 -)))
464 -
465 -(((
466 -**For example：**
467 -)))
468 -
469 -(((
470 -AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
471 -)))
472 -
473 -(((
474 -AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
475 -)))
476 -
477 -(((
478 -AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
479 -)))
480 -
481 -(((
482 -AT+APPEUI=2C 45 47 E3 24 12 23 24
483 -)))
484 -
485 -(((
486 -(Any combination of 16 bit codes can be used）
487 -
488 -
489 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
490 -)))
491 -
492 -
493 -Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
494 -
495 -
496 -
497 -(% class="wikigeneratedid" %)
498 -
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