Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 100.1
edited by Bei Jinggeng
on 2025/04/29 13:36
Change comment: Uploaded new attachment "image-20250429133640-7.png", version {1}
To version 49.1
edited by Mengting Qiu
on 2024/01/23 16:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.ting
Content
... ... @@ -4,7 +4,7 @@
4 4  
5 5  
6 6  
7 -= 1. Join process page check =
7 += z =
8 8  
9 9  
10 10  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.
... ... @@ -26,11 +26,12 @@
26 26  
27 27  * What frequency the device is sending?
28 28  
29 -[[image:image-20240129142147-2.png||height="736" width="964"]]
29 +[[image:image-20220526164956-15.png||height="591" width="1153"]]
30 30  
31 -Console Output from End device to see the transmit frequency.
31 +Console Output from End device to see the transmit frequency
32 32  
33 33  
34 +
34 34  (% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
35 35  
36 36  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
... ... @@ -37,11 +37,12 @@
37 37  
38 38  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
39 39  
40 -[[image:image-20240129151608-6.jpeg||height="725" width="1256"]]
41 +[[image:image-20220526163608-2.png]]
41 41  
42 42  Console Output from Gateway to see packets between end node and server.
43 43  
44 44  
46 +
45 45  (% style="color:blue" %)**3. Gateway Live data in LoRaWAN Server**
46 46  
47 47  * Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
... ... @@ -50,21 +50,22 @@
50 50  
51 51  * 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.
52 52  
53 -[[image:image-20240129150821-5.jpeg||height="522" width="1264"]]
55 +[[image:image-20220526163633-3.png]]
54 54  
55 55  The Traffic for the End node in the server, use TTN as example.
56 56  
57 57  
60 +
58 58  (% style="color:blue" %)**4. Data Page in LoRaWAN server**
59 59  
60 60  * 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.
61 61  
62 -[[image:image-20240129142557-3.png||height="488" width="1267"]]
65 +[[image:image-20240123150720-1.png||height="459" width="1182"]]
63 63  
64 64  The data for the end device set in server
65 65  
66 66  
67 -[[image:image-20240129142631-4.png||height="637" width="1256"]]
70 +[[image:image-20240123150943-2.png||height="556" width="1179"]]
68 68  
69 69  Check if OTAA Keys match the keys in device.
70 70  
... ... @@ -73,17 +73,17 @@
73 73  
74 74  
75 75  (((
76 -If user has problem to work with LoRaWAN server in band US915/AU915/CN470, he can check:
79 +If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
77 77  )))
78 78  
79 79  * (((
80 -What **sub-band** the server support?
83 +What **sub-band** the server support ?
81 81  )))
82 82  * (((
83 -What is the **sub-band** the gateway support?
86 +What is the **sub-band** the gateway support ?
84 84  )))
85 85  * (((
86 -What is the **sub-band** the end node is using?
89 +What is the **sub-band** the end node is using ?
87 87  )))
88 88  
89 89  (((
... ... @@ -95,7 +95,7 @@
95 95  )))
96 96  
97 97  (((
98 -In LoRaWAN protocol, the frequency bands US915, AU915, CN470 each includes at least 72 frequencies. Many gateways support only 8 or 16 frequencies, and server might support 8 frequency only. In this case, the OTAA join time and uplink schedule is long and unpredictable while the end node is hopping in 72 frequencies, because the end node will send data in many frequency that the gateway or server doesn't support.
101 +In LoRaWAN protocol, the frequency bands US915, AU915, CN470 each includes at least 72 frequencies. Many gateways support only 8 or 16 frequencies, and server might support 8 frequency only. In this case, the OTAA join time and uplink schedule is long and unpredictable while the end node is hopping in 72 frequencies, because the end node will send data in many frequency that the gateway or server doesn,t support.
99 99  )))
100 100  
101 101  (((
... ... @@ -103,7 +103,7 @@
103 103  )))
104 104  
105 105  (((
106 -Here are the frequency tables for these bands as reference:
109 +Here are the freuqency tables for these bands as reference:
107 107  )))
108 108  
109 109  [[image:image-20220526163801-6.png]]
... ... @@ -163,112 +163,9 @@
163 163  )))
164 164  
165 165  
166 -= 4. Why i see packet lost =
169 += 4. Transmision on ABP Mode =
167 167  
168 -== **1. Signal problem** ==
169 169  
170 -
171 -1)  (% style="color:blue" %)**ADR automatic adjustment** (%%)
172 -
173 -Reason:
174 -
175 -When the signal is at a critical value, the server may configure the node to adjust to a lower power DR.
176 -At this time, the server is at risk of losing uplink.
177 -
178 -
179 -Solution:
180 -
181 -Users can manually fix the DR value.
182 -
183 -
184 -(% style="color:red" %)
185 -**Notice:**
186 -
187 -* User need to set Adaptive Data Rate(ADR)=0 first. otherwise device will respond to server's ADR command and change the DR according to server auto-adjustment.
188 -
189 -* Data Rate specifies Spreading Factor. The mapping varies in different frequency bands. User can check this link for detail. [[rp2-1.0.3-lorawan-regional-parameters.pdf>>https://lora-alliance.org/resource_hub/rp2-1-0-3-lorawan-regional-parameters/]]
190 -
191 -(% style="color:blue" %)**AT Command: AT+DR**
192 -
193 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:409px" %)
194 -|(% style="background-color:#4f81bd; color:white; width:156px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:147px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:100px" %)**Response**
195 -|(% style="width:156px" %)AT+DR=?|(% style="width:147px" %)Get the Data Rate.|(% style="width:100px" %)5(((
196 -OK
197 -)))
198 -|(% style="width:156px" %)AT+DR=2|(% style="width:147px" %)Set the Data Rate.|(% style="width:100px" %)OK(((
199 -
200 -)))
201 -
202 -(% style="color:blue" %)**Downlink Command: 0x2200aaFF**
203 -
204 -If the downlink payload=220001FF, it means setting the data rate to 1, while type code is 22 00 aa FF.
205 -
206 -* **Example 1**: Downlink Payload: **220001FF**  ~/~/ Set AT+DR=1.
207 -
208 -* **Example 2**: Downlink Payload: **220000FF**  ~/~/ Set AT+DR=0.
209 -
210 -(% style="display:none" %) (%%)
211 -
212 -
213 -2)  (% style="color:blue" %)**Node antenna problem**
214 -
215 -Reason:
216 -
217 -Node antenna is loose
218 -
219 -
220 -Solution:
221 -
222 -Please check whether the antenna interface and module interface are detached
223 -
224 -[[image:image-20250429114526-1.png||height="429" width="303"]]
225 -
226 -
227 -
228 -3) (% style="color:blue" %)**Gateway antenna problem**
229 -
230 -Reason:
231 -Gateway uses antenna with wrong frequency band
232 -
233 -For example: 868-band gateway uses antenna with 915-band, which will cause the signal to be greatly reduced
234 -
235 -
236 -Solution:
237 -
238 -Please check whether the silk screen on the antenna conflicts with the frequency you set.
239 -
240 -[[image:image-20250429115124-2.png]][[image:image-20250429115159-3.png||height="550" width="224"]]
241 -
242 -
243 -4) (% style="color:blue" %)**Gateway module problem**
244 -
245 -Reason:
246 -
247 -Gateway uses module with wrong frequency band
248 -For example: 868-band gateway uses module with 915-band, which will cause the signal to be greatly reduced
249 -
250 -
251 -Solution:
252 -
253 -Please check whether the silkscreen of the module conflicts with the frequency you set.
254 -
255 -[[image:image-20250429115951-5.png||height="288" width="384"]][[image:image-20250429120030-6.png||height="284" width="378"]]
256 -
257 -
258 -== **2. Frequency point problem** ==
259 -
260 -The frequency point of the gateway or server is wrong or missing.
261 -
262 -
263 -== **3. Frequency band problem** ==
264 -
265 -When there are multiple gateways, the node cannot lock the frequency band.
266 -
267 -
268 -
269 -= 5. Transmision on ABP Mode =
270 -
271 -
272 272  (((
273 273  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.
274 274  )))
... ... @@ -288,20 +288,15 @@
288 288  Disable Frame Counter Check in ABP Mode
289 289  
290 290  
291 -= 6. Downstream Debug =
191 += 5. Downstream Debug =
292 292  
293 -== 6.1 How it work ==
193 +== 5.1 How it work ==
294 294  
295 295  
296 296  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.
297 297  
298 298  (((
299 -Depends on Class A or Class C, the receive windows will be a little difference. The main difference between Class A and Class C:
300 -
301 -* **Class A** : Suitable for Battery powered end node. Class A will save a lot of power but it can only receive downlink after each uplink
302 -* **Class C**: End node can receive downlink immediately but have higher power consumption.
303 -
304 -
199 +Depends on Class A or Class C, the receive windows will be a little difference.
305 305  )))
306 306  
307 307  [[image:image-20220531161828-1.png]]
... ... @@ -321,9 +321,12 @@
321 321  
322 322  * This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). (% style="color:red" %)**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.**
323 323  
324 -== 6.2 See Debug Info ==
219 +(% class="wikigeneratedid" %)
220 +== ==
325 325  
222 +== 5.2 See Debug Info ==
326 326  
224 +
327 327  (((
328 328  (% style="color:blue" %)**For LoRaWAN Server**
329 329  )))
... ... @@ -334,26 +334,23 @@
334 334  
335 335  (((
336 336  Configure a downlink to the end device
337 -
338 -[[image:image-20240129152412-8.png||height="486" width="1206"]]
339 339  )))
340 340  
237 +[[image:image-20240123163307-7.png||height="330" width="1125"]]
341 341  
342 342  (((
343 343  Set a downstream in TTN and see it is sent
344 344  )))
345 345  
346 -(% style="color:red" %)**Note: After the downlink command is successfully sent from the platform to the node, the downlink command is executed only after the platform receives the next uplink package from the node.**
347 347  
348 -
349 349  (((
350 -This downlink info will then pass to the gateway downlink list. and the DR which is used (SF7BW500) in US915 is DR5.
245 +This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
351 351  )))
352 352  
353 -[[image:image-20240129152049-7.png||height="463" width="1166"]]
248 +[[image:image-20220526164650-13.png]]
354 354  
355 355  (((
356 -Gateway Traffic can see this downlink info
251 +Gateway Traffic can see this downstream info
357 357  )))
358 358  
359 359  
... ... @@ -363,10 +363,10 @@
363 363  )))
364 364  
365 365  (((
366 -When the downlink packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragino Gateway, this can be checked by running "logread -f" in the SSH console. and see below:
261 +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:
367 367  )))
368 368  
369 -[[image:image-20240129154321-9.png]]
264 +[[image:image-20220526164734-14.png]]
370 370  
371 371  (((
372 372  Gateway Sent out this packet
... ... @@ -426,7 +426,7 @@
426 426   1:0012345678}}}
427 427  
428 428  
429 -== 6.3 If problem doesn't solve ==
324 +== 5.3 If problem doesn't solve ==
430 430  
431 431  
432 432  (% 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:**
... ... @@ -439,11 +439,11 @@
439 439  
440 440  * End Node traffic (from server UI) to shows end node activity in server.
441 441  
442 -= 7. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
337 += 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
443 443  
444 444  
445 445  (((
446 -In LoRaWAN, the gateway 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.
341 +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.
447 447  )))
448 448  
449 449  (((
... ... @@ -465,83 +465,62 @@
465 465  )))
466 466  
467 467  
468 -= 8. Decrypt a LoRaWAN Packet =
363 += 7. Decrypt a LoRaWAN Packet =
469 469  
470 470  
471 -(% style="color:blue" %)**1. LHT65N End device configure:**
366 +(% style="color:blue" %)**1. LHT65 End device configure:**
472 472  
473 473  **Change to ABP Mode:  AT+NJM=0**
474 474  
475 -**Change to fix frequency:  ​​​​AT+CHE=1**
370 +**Change to fix frequency:  AT+CHS=904900000**
476 476  
372 +**Change to fix DR:  AT+DR=0**
477 477  
478 -**AT+CFG(Print configuration):**
479 479  
480 -[[image:image-20240129170603-7.png||height="697" width="545"]][[image:image-20240129163741-3.png||height="694" width="565"]]
375 +[[image:image-20220526165525-16.png]]
481 481  
482 482  
483 483  
484 -**Configuration: **
379 +(% style="color:blue" %)**2. In LG02 , configure to receive above message**
485 485  
486 -[[image:image-20240129164219-4.png||height="612" width="440"]]
381 +[[image:image-20220526165612-17.png]]
487 487  
488 488  
384 +In LG02 console, we can see the hex receive are:
489 489  
490 -(% style="color:blue" %)**2. In LPS8-v2, configure to receive above message**
386 +[[image:image-20220526171112-21.png]]
491 491  
492 -[[image:image-20240129164326-5.png||height="506" width="1114"]]
493 493  
494 494  
495 -In LPS8-v2 console, we can see the Base64 receive are:
390 +(% style="color:blue" %)**3. Decode the info in web**
496 496  
497 -[[image:image-20240129170137-6.png||height="459" width="1116"]]
392 +[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
498 498  
394 +Need these three fields:
499 499  
396 +LoRa packet hex format: 40c1190126800100024926272bf18bbb6341584e27e23245 (from LG02)
500 500  
501 -(% style="color:blue" %)**3. Decode the info in CMD(Command prompt window)**
398 +AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End node Network Session Key)
502 502  
503 -LoRa packet Base64 format:  QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75 **(from LPS8-v2)**
400 +AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
504 504  
505 -Then the instructions and format parsed in SecureCRT are:  ./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75
506 506  
403 +[[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]]
507 507  
508 -**Step1: Open CMD, Enter the gateway IP and port.(ssh root@gateway IP -p 22)**
405 +[[image:image-20220526171029-20.png]]
509 509  
510 -[[image:image-20240129190752-17.png||height="338" width="901"]]
407 +(((
408 + The FRMPayload is the device payload.
409 +)))
511 511  
512 -[[image:image-20240129191937-21.png||height="450" width="901"]]
513 513  
412 += 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
514 514  
515 -**Step2: Enter the command to download the LoRa parsing package.(npm install lora-packet)**
516 516  
517 -[[image:image-20240129192239-22.png||height="416" width="902"]]
518 -
519 -[[image:image-20240129192549-23.png||height="459" width="898"]]
520 -
521 -
522 -**Step3: Parse the gateway raw payload.(./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75)**
523 -
524 -
525 -
526 -
527 -[[image:image-20240129192908-24.png||height="477" width="907"]]
528 -
529 -
530 -[[image:image-20240129192954-25.png||height="485" width="916"]]
531 -
532 -
533 -
534 -
535 -
536 -
537 -
538 -= 9. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
539 -
540 -
541 541  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.
542 542  
543 543  
544 -= 10. Why do I see a "MIC Mismatch" error message from the server? =
418 += 9. Why do I see a "MIC Mismatch" error message from the server? =
545 545  
546 546  
547 547  (((
... ... @@ -579,7 +579,7 @@
579 579  4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
580 580  
581 581  
582 -= 11. Why I got the payload only with "0x00" or "AA~=~="? =
456 += 10. Why i got the payload only with "0x00" or "AA~=~="? =
583 583  
584 584  
585 585  (% style="color:blue" %)**Why sensor sends 0x00?**
... ... @@ -613,7 +613,7 @@
613 613  Some node decoders may not have the filter function, or you need decoders of other servers and formats. Please send an email to [[support@dragino.com>>mailto:support@dragino.com]]
614 614  
615 615  
616 -= 12. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
490 += 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
617 617  
618 618  
619 619  (((
... ... @@ -674,7 +674,7 @@
674 674  (Any combination of 16 bit codes can be used）
675 675  
676 676  
677 -= 13. I set my device is LoRaWAN Class C mode, why I still see Class A after boot? =
551 += 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
678 678  )))
679 679  
680 680  
... ... @@ -681,27 +681,30 @@
681 681  Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
682 682  
683 683  
684 -= 14. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
558 += 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
685 685  
686 686  
687 -In US915, AU915 or CN470 frequency band, there are 8 sub-bands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Sub-band 2 in TTN. The gateway also configured to Sub-band 2 and cover eight channels in this sub-band. If the end node transfer data in Sub-band 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other sub-bands, for example sub-band 1, the packet won't arrive both gateway or LoRaWAN server.
561 +In US915, AU915 or CN470 frequency band, there are 8 subbands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Subband 2 in TTN. The gateway also configured to Subband 2 and cover eight channels in this subband. If the end node transfer data in Subband 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other subbands, for example subband 1, the packet won't arrive both gateway or LoRaWAN server.
688 688  
689 689  
690 -In Dragino Sensors old version firmware (before early 2022), the sub-band is fixed the sub-band to 2 , but this cause a problem, the end node is hard to use in other subband and need program. So the new logic is as below:
564 +In Dragino Sensors old version firmware (before early 2022), the subband is fixed the subband to 2 , but this cause a problem, the end node is hard to use in other subband and need program. So the new logic is as below:
691 691  
692 -We have improved this, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join, in this case, in this case, the end node can support LoRaWAN servers with different sub-bands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
566 +We have improved this, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join, In this case, In this case, the end node can support LoRaWAN servers with different subbands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
693 693  
694 694  * (((
695 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band.
569 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
696 696  )))
697 697  * (((
698 -Use the Join successful sub-band if the server doesn't include sub-band info in the OTAA Join Accept message (TTN v2 doesn't include).
572 +Use the Join successful sub-band if the server doesn't include subband info in the OTAA Join Accept message ( TTN v2 doesn't include)
699 699  )))
700 700  
701 -This change will make the activation time a little longer but make sure the device can be used in any sub-band.
575 +This change will make the activation time a littler longer but make sure the device can be used in any subband.
702 702  
703 703  
704 -Below is a photo to show why it takes longer time for OTAA Join. We can see in 72 channels mode, why it takes more time to join success. If users want to have faster OTAA Join success, he can change default CHE to the sub-band he uses.
578 +Below is a photo to show why it takes longer time for OTAA Join. We can see in 72 channels mode, why it takes more time to join success. If users want to have faster OTAA Join success, he can change default CHE to the subband he use.
705 705  
706 706  
707 707  [[image:image-20221215223215-1.png||height="584" width="1280"]]
582 +
583 +(% class="wikigeneratedid" %)
584 +
image-20240123182345-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -108.0 KB
Content
image-20240129142110-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -126.9 KB
Content
image-20240129142147-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -116.1 KB
Content
image-20240129142557-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -125.7 KB
Content
image-20240129142631-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -189.0 KB
Content
image-20240129150821-5.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -129.2 KB
Content
image-20240129151608-6.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -318.1 KB
Content
image-20240129152049-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -148.3 KB
Content
image-20240129152412-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -133.6 KB
Content
image-20240129154321-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -99.5 KB
Content
image-20240129163533-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -23.0 KB
Content
image-20240129163714-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -39.2 KB
Content
image-20240129163741-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -36.5 KB
Content
image-20240129164219-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -30.3 KB
Content
image-20240129164326-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -80.8 KB
Content
image-20240129170137-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -115.2 KB
Content
image-20240129170603-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -39.2 KB
Content
image-20240129172956-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -54.2 KB
Content
image-20240129173810-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -74.1 KB
Content
image-20240129173932-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -73.6 KB
Content
image-20240129174125-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -77.0 KB
Content
image-20240129174549-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -85.6 KB
Content
image-20240129174717-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -85.6 KB
Content
image-20240129174948-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -85.1 KB
Content
image-20240129175037-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -85.8 KB
Content
image-20240129190344-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -17.2 KB
Content
image-20240129190752-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 KB
Content
image-20240129190840-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -17.2 KB
Content
image-20240129191130-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -81.7 KB
Content
image-20240129191315-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -50.0 KB
Content
image-20240129191937-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -71.8 KB
Content
image-20240129192239-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -77.5 KB
Content
image-20240129192549-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -59.5 KB
Content
image-20240129192908-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -101.7 KB
Content
image-20240129192954-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -62.4 KB
Content
image-20250429114526-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -3.2 MB
Content
image-20250429115124-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -193.2 KB
Content
image-20250429115159-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -1014.1 KB
Content
image-20250429115942-4.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -435.8 KB
Content
image-20250429115951-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -1.4 MB
Content
image-20250429120030-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -1.4 MB
Content
image-20250429133640-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -1.4 MB
Content