Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 59.1
edited by Mengting Qiu
on 2024/01/29 15:20
Change comment: Uploaded new attachment "image-20240129152049-7.png", version {1}
To version 102.1
edited by Xiaoling
on 2025/05/05 08:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Xiaoling
Content
... ... @@ -26,7 +26,7 @@
26 26  
27 27  * What frequency the device is sending?
28 28  
29 -[[image:image-20240123182345-1.png||height="605" width="946"]]
29 +[[image:image-20240129142147-2.png||height="736" width="964"]]
30 30  
31 31  Console Output from End device to see the transmit frequency.
32 32  
... ... @@ -37,7 +37,7 @@
37 37  
38 38  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
39 39  
40 -[[image:image-20220526163608-2.png]]
40 +[[image:image-20240129151608-6.jpeg||height="725" width="1256"]]
41 41  
42 42  Console Output from Gateway to see packets between end node and server.
43 43  
... ... @@ -50,7 +50,7 @@
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-20220526163633-3.png]]
53 +[[image:image-20240129150821-5.jpeg||height="522" width="1264"]]
54 54  
55 55  The Traffic for the End node in the server, use TTN as example.
56 56  
... ... @@ -59,13 +59,12 @@
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-20240123150720-1.png||height="459" width="1182"]]
62 +[[image:image-20240129142557-3.png||height="488" width="1267"]]
63 63  
64 64  The data for the end device set in server
65 65  
66 +[[image:image-20240129142631-4.png||height="637" width="1256"]]
66 66  
67 -[[image:image-20240123150943-2.png||height="556" width="1179"]]
68 -
69 69  Check if OTAA Keys match the keys in device.
70 70  
71 71  
... ... @@ -163,10 +163,205 @@
163 163  )))
164 164  
165 165  
166 -= 4. Transmision on ABP Mode =
165 += 4. Why i see packet lost =
167 167  
167 +== **1. Signal problem** ==
168 168  
169 +
170 +(% style="color:blue" %)**1)**(%%)  (% style="color:blue" %)**ADR automatic adjustment** (%%)
171 +
172 +**Reason:**
173 +
174 +When the signal is at a critical value, the server may configure the node to adjust to a lower power DR.
175 +At this time, the server is at risk of losing uplink.
176 +
177 +
178 +**Solution:**
179 +
180 +Users can manually fix the DR value.
181 +
182 +
183 +(% style="color:red" %)
184 +**Notice:**
185 +
186 +* 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.
187 +
188 +* 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/]]
189 +
190 +(% style="color:blue" %)**AT Command: AT+DR**
191 +
192 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:409px" %)
193 +|(% 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**
194 +|(% style="width:156px" %)AT+DR=?|(% style="width:147px" %)Get the Data Rate.|(% style="width:100px" %)5(((
195 +OK
196 +)))
197 +|(% style="width:156px" %)AT+DR=2|(% style="width:147px" %)Set the Data Rate.|(% style="width:100px" %)OK(((
198 +
199 +)))
200 +
201 +(% style="color:blue" %)**Downlink Command: 0x2200aaFF**
202 +
203 +If the downlink payload=220001FF, it means setting the data rate to 1, while type code is 22 00 aa FF.
204 +
205 +* **Example 1**: Downlink Payload: **220001FF**  ~/~/ Set AT+DR=1.
206 +
207 +* **Example 2**: Downlink Payload: **220000FF**  ~/~/ Set AT+DR=0.
208 +
209 +(% style="display:none" %) (%%)
210 +
211 +
212 +(% style="color:blue" %)**2)**(%%)  (% style="color:blue" %)**Node antenna problem**
213 +
214 +**Reason:**
215 +
216 +Node antenna is loose
217 +
218 +
219 +**Solution:**
220 +
221 +Please check whether the antenna interface and module interface are detached
222 +
223 +[[image:image-20250429114526-1.png||height="429" width="303"]]
224 +
225 +
226 +
227 +(% style="color:blue" %)**3) **(%%) (% style="color:blue" %)**Gateway antenna problem**
228 +
229 +**Reason:**
230 +Gateway uses antenna with wrong frequency band
231 +
232 +For example: 868-band gateway uses antenna with 915-band, which will cause the signal to be greatly reduced
233 +
234 +
235 +**Solution:**
236 +
237 +Please check whether the silk screen on the antenna conflicts with the frequency you set.
238 +
239 +[[image:image-20250429115124-2.png]][[image:image-20250429115159-3.png||height="550" width="224"]]
240 +
241 +
242 +(% style="color:blue" %)**4) **(%%) (% style="color:blue" %)**Gateway module problem**
243 +
244 +**Reason:**
245 +
246 +Gateway uses module with wrong frequency band
247 +For example: 868-band gateway uses module with 915-band, which will cause the signal to be greatly reduced
248 +
249 +
250 +**Solution:**
251 +
252 +Please check whether the silkscreen of the module conflicts with the frequency you set.
253 +
254 +[[image:image-20250429115951-5.png||height="288" width="384"]][[image:image-20250429133640-7.png||height="284" width="378"]]
255 +
256 +
257 +== **2. Frequency point problem** ==
258 +
259 +
260 +**Reason:**
261 +
262 +There are multiple frequency configurations in AS923/US915/AU915/CN470.
263 +
264 +The frequency point of the gateway or server is wrong or missing.
265 +
266 +
267 +**Solution:**
268 +
269 +Users need to check whether the server or gateway configuration is missing or has an incorrect frequency.
270 +
271 +The frequency range used in the dragino node is as follows
272 +
273 +
274 +== **3. Frequency band problem** ==
275 +
276 +
277 +**Reason:**
278 +
279 +When there are multiple gateways, the node cannot lock the frequency band.
280 +
281 +
282 +**Solution:**
283 +
169 169  (((
285 +By default, the frequency bands US915, AU915, CN470 work in 72 frequencies. Many gateways are 8 channel gateways, and in this case, the OTAA join time and uplink schedule is long and unpredictable while the end node is hopping in 72 frequencies.
286 +)))
287 +
288 +(((
289 +You can configure the end node to work in 8 channel mode by using the AT+CHE command. The 500kHz channels are always included for OTAA.
290 +)))
291 +
292 +(((
293 +
294 +)))
295 +
296 +(((
297 +For example, in (% style="color:blue" %)**US915**(%%) band, the frequency table is as below. By default, the end node will use all channels (0~~71) for OTAA Join process. After the OTAA Join, the end node will use these all channels (0~~71) to send uplink packets.
298 +)))
299 +
300 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220627160940-13.png?rev=1.1||alt="image-20220627160940-13.png"]]
301 +
302 +
303 +(((
304 +When you use the TTN V3 network, the US915 frequency bands use are:
305 +)))
306 +
307 +* (((
308 +903.9 - SF7BW125 to SF10BW125
309 +)))
310 +* (((
311 +904.1 - SF7BW125 to SF10BW125
312 +)))
313 +* (((
314 +904.3 - SF7BW125 to SF10BW125
315 +)))
316 +* (((
317 +904.5 - SF7BW125 to SF10BW125
318 +)))
319 +* (((
320 +904.7 - SF7BW125 to SF10BW125
321 +)))
322 +* (((
323 +904.9 - SF7BW125 to SF10BW125
324 +)))
325 +* (((
326 +905.1 - SF7BW125 to SF10BW125
327 +)))
328 +* (((
329 +905.3 - SF7BW125 to SF10BW125
330 +)))
331 +* (((
332 +904.6 - SF8BW500
333 +)))
334 +
335 +(((
336 +Because the end node is now hopping in 72 frequency, it makes it difficult for the devices to Join the TTN V3 network and uplink data. To solve this issue, you can access the device via the AT commands and run:
337 +)))
338 +
339 +(((
340 +(% style="color:blue" %)**AT+CHE=2**
341 +)))
342 +
343 +(((
344 +(% style="color:blue" %)**ATZ**
345 +)))
346 +
347 +
348 +(((
349 +to set the end node to work in 8 channel mode. The device will work in Channel 8-15 & 64-71 for OTAA, and channel 8-15 for Uplink.
350 +)))
351 +
352 +(((
353 +The (% style="color:blue" %)**AU915**(%%) band is similar. Below are the AU915 Uplink Channels.
354 +
355 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220627161124-14.png?rev=1.1||alt="image-20220627161124-14.png"]]
356 +
357 +
358 +)))
359 +
360 += 5. Transmision on ABP Mode =
361 +
362 +
363 +(((
170 170  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.
171 171  )))
172 172  
... ... @@ -185,15 +185,20 @@
185 185  Disable Frame Counter Check in ABP Mode
186 186  
187 187  
188 -= 5. Downstream Debug =
382 += 6. Downstream Debug =
189 189  
190 -== 5.1 How it work ==
384 +== 6.1 How it work ==
191 191  
192 192  
193 193  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.
194 194  
195 195  (((
196 -Depends on Class A or Class C, the receive windows will be a little difference.
390 +Depends on Class A or Class C, the receive windows will be a little difference. The main difference between Class A and Class C:
391 +
392 +* **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
393 +* **Class C**: End node can receive downlink immediately but have higher power consumption.
394 +
395 +
197 197  )))
198 198  
199 199  [[image:image-20220531161828-1.png]]
... ... @@ -213,10 +213,9 @@
213 213  
214 214  * 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.**
215 215  
415 +== 6.2 See Debug Info ==
216 216  
217 -== 5.2 See Debug Info ==
218 218  
219 -
220 220  (((
221 221  (% style="color:blue" %)**For LoRaWAN Server**
222 222  )))
... ... @@ -227,23 +227,26 @@
227 227  
228 228  (((
229 229  Configure a downlink to the end device
428 +
429 +[[image:image-20240129152412-8.png||height="486" width="1206"]]
230 230  )))
231 231  
232 -[[image:image-20240123163307-7.png||height="330" width="1125"]]
233 233  
234 234  (((
235 235  Set a downstream in TTN and see it is sent
236 236  )))
237 237  
437 +(% 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.**
238 238  
439 +
239 239  (((
240 -This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
441 +This downlink info will then pass to the gateway downlink list. and the DR which is used (SF7BW500) in US915 is DR5.
241 241  )))
242 242  
243 -[[image:image-20220526164650-13.png]]
444 +[[image:image-20240129152049-7.png||height="463" width="1166"]]
244 244  
245 245  (((
246 -Gateway Traffic can see this downstream info
447 +Gateway Traffic can see this downlink info
247 247  )))
248 248  
249 249  
... ... @@ -253,10 +253,10 @@
253 253  )))
254 254  
255 255  (((
256 -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:
457 +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:
257 257  )))
258 258  
259 -[[image:image-20220526164734-14.png]]
460 +[[image:image-20240129154321-9.png]]
260 260  
261 261  (((
262 262  Gateway Sent out this packet
... ... @@ -316,7 +316,7 @@
316 316   1:0012345678}}}
317 317  
318 318  
319 -== 5.3 If problem doesn't solve ==
520 +== 6.3 If problem doesn't solve ==
320 320  
321 321  
322 322  (% 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:**
... ... @@ -329,11 +329,11 @@
329 329  
330 330  * End Node traffic (from server UI) to shows end node activity in server.
331 331  
332 -= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
533 += 7. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
333 333  
334 334  
335 335  (((
336 -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.
537 +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.
337 337  )))
338 338  
339 339  (((
... ... @@ -355,62 +355,72 @@
355 355  )))
356 356  
357 357  
358 -= 7. Decrypt a LoRaWAN Packet =
559 += 8. Decrypt a LoRaWAN Packet =
359 359  
360 360  
361 -(% style="color:blue" %)**1. LHT65 End device configure:**
562 +(% style="color:blue" %)**1. LHT65N End device configure:**
362 362  
363 363  **Change to ABP Mode:  AT+NJM=0**
364 364  
365 -**Change to fix frequency:  AT+CHS=904900000**
566 +**Change to fix frequency:  ​​​​AT+CHE=1**
366 366  
367 -**Change to fix DR:  AT+DR=0**
368 368  
569 +**AT+CFG(Print configuration):**
369 369  
370 -[[image:image-20220526165525-16.png]]
571 +[[image:image-20240129170603-7.png||height="697" width="545"]][[image:image-20240129163741-3.png||height="694" width="565"]]
371 371  
372 372  
574 +**Configuration: **
373 373  
374 -(% style="color:blue" %)**2. In LG02 , configure to receive above message**
576 +[[image:image-20240129164219-4.png||height="612" width="440"]]
375 375  
376 -[[image:image-20220526165612-17.png]]
377 377  
378 378  
379 -In LG02 console, we can see the hex receive are:
580 +(% style="color:blue" %)**2. In LPS8-v2, configure to receive above message**
380 380  
381 -[[image:image-20220526171112-21.png]]
582 +[[image:image-20240129164326-5.png||height="506" width="1114"]]
382 382  
383 383  
585 +In LPS8-v2 console, we can see the Base64 receive are:
384 384  
385 -(% style="color:blue" %)**3. Decode the info in web**
587 +[[image:image-20240129170137-6.png||height="459" width="1116"]]
386 386  
387 -[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
388 388  
389 -Need these three fields:
590 +(% style="color:blue" %)**3. Decode the info in CMD(Command prompt window)**
390 390  
391 -LoRa packet hex format: 40c1190126800100024926272bf18bbb6341584e27e23245 (from LG02)
592 +LoRa packet Base64 format:  QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75 **(from LPS8-v2)**
392 392  
393 -AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End node Network Session Key)
594 +Then the instructions and format parsed in SecureCRT are:  ./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75
394 394  
395 -AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
396 396  
597 +**Step1: Open CMD, Enter the gateway IP and port.(ssh root@gateway IP -p 22)**
397 397  
398 -[[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]]
599 +[[image:image-20240129190752-17.png||height="338" width="901"]]
399 399  
400 -[[image:image-20220526171029-20.png]]
601 +[[image:image-20240129191937-21.png||height="450" width="901"]]
401 401  
402 -(((
403 - The FRMPayload is the device payload.
404 -)))
405 405  
604 +**Step2: Enter the command to download the LoRa parsing package.(npm install lora-packet)**
406 406  
407 -= 8. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
606 +[[image:image-20240129192239-22.png||height="416" width="902"]]
408 408  
608 +[[image:image-20240129192549-23.png||height="459" width="898"]]
409 409  
610 +
611 +**Step3: Parse the gateway raw payload.(./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75)**
612 +
613 +[[image:image-20240129192908-24.png||height="477" width="907"]]
614 +
615 +[[image:image-20240129192954-25.png||height="485" width="916"]]
616 +
617 +
618 += 9. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
619 +
620 +
410 410  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.
411 411  
412 412  
413 -= 9. Why do I see a "MIC Mismatch" error message from the server? =
624 += 10. Why do I see a "MIC Mismatch" error message from the server? =
414 414  
415 415  
416 416  (((
... ... @@ -448,7 +448,7 @@
448 448  4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
449 449  
450 450  
451 -= 10. Why i got the payload only with "0x00" or "AA~=~="? =
662 += 11. Why I got the payload only with "0x00" or "AA~=~="? =
452 452  
453 453  
454 454  (% style="color:blue" %)**Why sensor sends 0x00?**
... ... @@ -482,7 +482,7 @@
482 482  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]]
483 483  
484 484  
485 -= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
696 += 12. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
486 486  
487 487  
488 488  (((
... ... @@ -543,7 +543,7 @@
543 543  (Any combination of 16 bit codes can be used）
544 544  
545 545  
546 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
757 += 13. I set my device is LoRaWAN Class C mode, why I still see Class A after boot? =
547 547  )))
548 548  
549 549  
... ... @@ -550,7 +550,7 @@
550 550  Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
551 551  
552 552  
553 -= 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
764 += 14. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
554 554  
555 555  
556 556  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.
... ... @@ -574,6 +574,3 @@
574 574  
575 575  
576 576  [[image:image-20221215223215-1.png||height="584" width="1280"]]
577 -
578 -(% class="wikigeneratedid" %)
579 -
image-20240129152412-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +133.6 KB
Content
image-20240129154321-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +99.5 KB
Content
image-20240129163533-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +23.0 KB
Content
image-20240129163714-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +39.2 KB
Content
image-20240129163741-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +36.5 KB
Content
image-20240129164219-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +30.3 KB
Content
image-20240129164326-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +80.8 KB
Content
image-20240129170137-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +115.2 KB
Content
image-20240129170603-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +39.2 KB
Content
image-20240129172956-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +54.2 KB
Content
image-20240129173810-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +74.1 KB
Content
image-20240129173932-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +73.6 KB
Content
image-20240129174125-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +77.0 KB
Content
image-20240129174549-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +85.6 KB
Content
image-20240129174717-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +85.6 KB
Content
image-20240129174948-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +85.1 KB
Content
image-20240129175037-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +85.8 KB
Content
image-20240129190344-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +17.2 KB
Content
image-20240129190752-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +39.9 KB
Content
image-20240129190840-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +17.2 KB
Content
image-20240129191130-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +81.7 KB
Content
image-20240129191315-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +50.0 KB
Content
image-20240129191937-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +71.8 KB
Content
image-20240129192239-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +77.5 KB
Content
image-20240129192549-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +59.5 KB
Content
image-20240129192908-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +101.7 KB
Content
image-20240129192954-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +62.4 KB
Content
image-20250429114526-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +3.2 MB
Content
image-20250429115124-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +193.2 KB
Content
image-20250429115159-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +1014.1 KB
Content
image-20250429115942-4.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +435.8 KB
Content
image-20250429115951-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +1.4 MB
Content
image-20250429120030-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +1.4 MB
Content
image-20250429133640-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +1.4 MB
Content