Changes for page RS485-LN – RS485 to LoRaWAN Converter User Manual
Last modified by Bei Jinggeng on 2025/01/16 11:36
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 14 added, 0 removed)
- image-20221130104310-1.png
- image-20221130104310-10.png
- image-20221130104310-11.png
- image-20221130104310-12.png
- image-20221130104310-13.png
- image-20221130104310-14.png
- image-20221130104310-2.png
- image-20221130104310-3.png
- image-20221130104310-4.png
- image-20221130104310-5.png
- image-20221130104310-6.png
- image-20221130104310-7.png
- image-20221130104310-8.png
- image-20221130104310-9.png
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.Bei - Content
-
... ... @@ -33,40 +33,28 @@ 33 33 34 34 == 1.1 What is RS485-LN RS485 to LoRaWAN Converter == 35 35 36 -((( 37 -((( 38 -((( 39 - 40 40 37 +((( 41 41 The Dragino RS485-LN is a (% style="color:blue" %)**RS485 to LoRaWAN Converter**(%%). It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost. 42 42 ))) 43 -))) 44 44 45 45 ((( 46 -((( 47 47 RS485-LN allows user to (% style="color:blue" %)**monitor / control RS485 devices**(%%) and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, smartphone detection, building automation, and so on. 48 48 ))) 49 -))) 50 50 51 51 ((( 52 -((( 53 53 (% style="color:blue" %)**For data uplink**(%%), RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server. 54 54 ))) 55 -))) 56 56 57 57 ((( 58 -((( 59 59 (% style="color:blue" %)**For data downlink**(%%), RS485-LN runs in LoRaWAN Class C. When there downlink commands from LoRaWAN server, RS485-LN will forward the commands from LoRaWAN server to RS485 devices. 60 60 ))) 61 61 62 62 ((( 63 63 (% style="color:blue" %)**Demo Dashboard for RS485-LN**(%%) connect to two energy meters: [[https:~~/~~/app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a>>url:https://app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a]] 64 - 65 - 66 66 ))) 67 -))) 68 -))) 69 69 57 + 70 70 (% aria-label="1653267211009-519.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1653267211009-519.png||data-widget="image" height="419" width="724"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) 71 71 72 72 ... ... @@ -76,7 +76,7 @@ 76 76 77 77 (% style="color:#037691" %)**Hardware System:** 78 78 79 -* STM32L072 CZT6MCU67 +* STM32L072xxxx MCU 80 80 * SX1276/78 Wireless Chip 81 81 * Power Consumption (exclude RS485 device): 82 82 ** Idle: 32mA@12v ... ... @@ -108,7 +108,6 @@ 108 108 * Automatic RF Sense and CAD with ultra-fast AFC. 109 109 * Packet engine up to 256 bytes with CRC 110 110 111 - 112 112 == 1.3 Features == 113 113 114 114 ... ... @@ -121,7 +121,6 @@ 121 121 * Support Modbus protocol 122 122 * Support Interrupt uplink (Since hardware version v1.2) 123 123 124 - 125 125 == 1.4 Applications == 126 126 127 127 ... ... @@ -132,7 +132,6 @@ 132 132 * Smart Cities 133 133 * Smart Factory 134 134 135 - 136 136 == 1.5 Firmware Change log == 137 137 138 138 ... ... @@ -306,10 +306,10 @@ 306 306 To use RS485-LN to read data from RS485 sensors, connect the RS485-LN A/B traces to the sensors. And user need to make sure RS485-LN use the match UART setting to access the sensors. The related commands for UART settings are: 307 307 308 308 309 -(% border="1" cellspacing=" 10" style="background-color:#ffffcc; color:green; width:510px" %)294 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 310 310 |=(% style="width: 110px;" %)((( 311 311 **AT Commands** 312 -)))|=(% style="width: 1 90px;" %)(((297 +)))|=(% style="width: 210px;" %)((( 313 313 **Description** 314 314 )))|=(% style="width: 190px;" %)((( 315 315 **Example** ... ... @@ -364,7 +364,6 @@ 364 364 ))) 365 365 ))) 366 366 367 - 368 368 === 3.3.2 Configure sensors === 369 369 370 370 ... ... @@ -376,8 +376,8 @@ 376 376 ))) 377 377 ))) 378 378 379 -(% border="1" cellspacing=" 10" style="background-color:#ffffcc; color:green; width:510px" %)380 -|=(% style="width: 110px;" %)**AT Commands**|=(% style="width: 1 90px;" %)**Description**|=(% style="width: 190px;" %)**Example**363 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 364 +|=(% style="width: 110px;" %)**AT Commands**|=(% style="width: 210px;" %)**Description**|=(% style="width: 190px;" %)**Example** 381 381 |AT+CFGDEV|(% style="width:110px" %)((( 382 382 ((( 383 383 This command is used to configure the RS485/TTL devices; they won’t be used during sampling. ... ... @@ -392,7 +392,6 @@ 392 392 ))) 393 393 )))|(% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 394 394 395 - 396 396 === 3.3.3 Configure read commands for each sampling === 397 397 398 398 ... ... @@ -425,7 +425,7 @@ 425 425 426 426 (% border="1" style="background-color:#4bacc6; color:white; width:499px" %) 427 427 |(% style="width:496px" %)((( 428 - (% style="color:#037691" %)**AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**411 +**AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m** 429 429 430 430 **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent** 431 431 ... ... @@ -511,12 +511,15 @@ 511 511 Final Payload is (% style="color:#4f81bd" %)**PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA** 512 512 513 513 514 -1. PAYVER: Defined by AT+PAYVER 515 -1. PAYLOAD COUNT: Total how many uplinks of this sampling. 516 -1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 517 -1. DATA: Valid value: max 8 bytes for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 8 bytes 497 +~1. PAYVER: Defined by AT+PAYVER 518 518 499 +2. PAYLOAD COUNT: Total how many uplinks of this sampling. 519 519 501 +3. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 502 + 503 +4. DATA: Valid value: max 8 bytes for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 8 bytes 504 + 505 + 520 520 (% aria-label="image-20220602155039-4.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602155039-4.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) 521 521 522 522 ... ... @@ -582,8 +582,26 @@ 582 582 == 3.4 Uplink Payload == 583 583 584 584 585 -(% aria-label="image-20220606110929-1.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220606110929-1.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]] 571 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %) 572 +|=(% scope="row" style="width: 60px;" %)((( 573 +Size(bytes) 574 +)))|(% style="width:80px" %)1|(% style="width:360px" %)((( 575 +Length depends on the return from the commands 576 +))) 577 +|=(% style="width: 90px;" %)((( 578 +Value 579 +)))|(% style="width:114px" %)((( 580 +PAYLOAD_VER 581 +)))|(% style="width:353px" %)((( 582 +If the valid payload is too long and exceed the maximum 586 586 584 +support payload length in server, server will show payload not 585 + 586 +provided in the LoRaWAN server. 587 +))) 588 + 589 +(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]] 590 + 587 587 (% title="Click and drag to resize" %) 588 588 589 589 Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors. ... ... @@ -645,7 +645,7 @@ 645 645 646 646 647 647 ((( 648 -This command is used to configure the RS485 devices; they won't be used during sampling. 652 +This command is used to configure the RS485 devices; they won't be used during sampling. Max Length of AT+CFGDEV is **40 bytes**. 649 649 ))) 650 650 651 651 ((( ... ... @@ -1184,7 +1184,27 @@ 1184 1184 1185 1185 1186 1186 1191 +==== (% style="color:blue" %)**Configure Databit (Since Version 1.4.0)**(%%) ==== 1187 1187 1193 + 1194 +* ((( 1195 +(% style="color:#037691" %)** AT Command:** 1196 +))) 1197 + 1198 +(% style="color:#4472c4" %)** AT+DATABIT=7 **(%%)~/~/ Set the data bits to 7 1199 + 1200 +(% style="color:#4472c4" %)** AT+DATABIT=8 **(%%)~/~/ Set the data bits to 8 1201 + 1202 +* ((( 1203 +(% style="color:#037691" %)**Downlink Payload:** 1204 +))) 1205 + 1206 +(% style="color:#4472c4" %)** A7 04 07**(%%): Same as AT+DATABIT=7 1207 + 1208 +(% style="color:#4472c4" %)** A7 04 08**(%%): Same as AT+DATABIT=8 1209 + 1210 + 1211 + 1188 1188 ==== (% style="color:blue" %)**Encrypted payload**(%%) ==== 1189 1189 1190 1190 ((( ... ... @@ -1260,20 +1260,17 @@ 1260 1260 1261 1261 (% style="color:#4472c4" %)** AT+RPL=5** (%%) ~/~/ After receiving the package from the server, it will immediately upload the content of the package to the server, the port number is 100. 1262 1262 1263 - 1264 1264 Example:**aa xx xx xx xx** ~/~/ aa indicates whether the configuration has changed, 00 is yes, 01 is no; xx xx xx xx are the bytes sent. 1265 1265 1266 1266 1267 1267 [[image:http://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-20220823173747-6.png?width=1124&height=165&rev=1.1||alt="image-20220823173747-6.png"]] 1268 1268 1269 - 1270 - 1271 1271 For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77. 1272 1272 1273 1273 1295 + 1274 1274 [[image:http://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-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]] 1275 1275 1276 - 1277 1277 For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. 1278 1278 1279 1279 ... ... @@ -1315,7 +1315,7 @@ 1315 1315 (% style="color:#037691" %)**Downlink Payload:** 1316 1316 ))) 1317 1317 1318 -(% style="color:#4472c4" %)** A6 aa bb bb ** (%%) ~/~/same as AT+RXMODE=aa,bb 1339 +(% style="color:#4472c4" %)** A6 aa bb bb ** (%%) ~/~/ same as AT+RXMODE=aa,bb 1319 1319 1320 1320 [[image:image-20220824144240-1.png]] 1321 1321 ... ... @@ -1432,22 +1432,20 @@ 1432 1432 == 3.7 Buttons == 1433 1433 1434 1434 1435 -(% border="1" cellspacing=" 10" style="background-color:#f7faff; width:430px" %)1436 -|=(% style="width: 50px;" %)**Button**|=(% style="width: 3 61px;" %)**Feature**1456 +(% border="1.5" cellspacing="4" style="background-color:#ffffcc; width:430px" %) 1457 +|=(% style="width: 50px;" %)**Button**|=(% style="width: 380px;" %)**Feature** 1437 1437 |(% style="width:50px" %)**ACT**|(% style="width:361px" %)If RS485 joined in network, press this button for more than 1 second, RS485 will upload a packet, and the SYS LED will give a (% style="color:blue" %)**Blue blink** 1438 1438 |(% style="width:50px" %)**RST**|(% style="width:361px" %)Reboot RS485 1439 1439 |(% style="width:50px" %)**PRO**|(% style="width:361px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]] 1440 1440 1441 - 1442 1442 == 3.8 LEDs == 1443 1443 1444 1444 1445 -(% border="1" cellspacing=" 10" style="background-color:#f7faff; width:430px" %)1465 +(% border="1.5" cellspacing="4" style="background-color:#ffffcc; width:430px" %) 1446 1446 |=(% style="width: 50px;" %)**LEDs**|=(% style="width: 380px;" %)**Feature** 1447 1447 |**PWR**|Always on if there is power 1448 1448 |**SYS**|After device is powered on, the SYS will (% style="color:green" %)**fast blink in GREEN**(%%) for 5 times, means RS485-LN start to join LoRaWAN network. If join success, SYS will be (% style="color:green" %)**on GREEN for 5 seconds** (%%)**. **SYS will (% style="color:green" %)**blink Blue**(%%) on every upload and (% style="color:green" %)**blink Green**(%%) once receive a downlink message. 1449 1449 1450 - 1451 1451 = 4. Case Study = 1452 1452 1453 1453 ... ... @@ -1646,7 +1646,7 @@ 1646 1646 == 6.5 Can i use point to point communication for RS485-LN? == 1647 1647 1648 1648 1649 -Yes, please refer [[Point to Point Communication for RS485-LN>>Point to Point Communication for RS485-LN]]. 1668 +Yes, please updating point-to-point [[firmware>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACP33wo_ZQLsxW2MJ70oUoba/RS485-LN/Firmware?dl=0&subfolder_nav_tracking=1]],then refer [[Point to Point Communication for RS485-LN>>Point to Point Communication for RS485-LN]]. 1650 1650 1651 1651 1652 1652 ... ... @@ -1656,7 +1656,107 @@ 1656 1656 [[Use RS485-BL or RS485-LN to connect to RS232 devices. - DRAGINO>>url:http://8.211.40.43:8080/xwiki/bin/view/Main/RS485%20to%20RS232/]] 1657 1657 1658 1658 1678 +== 6.7 How to judge whether there is a problem with the set COMMAND == 1659 1659 1680 +=== 6.7.1 Introduce: === 1681 + 1682 + 1683 +Users can use below the structure to fast debug the communication between RS485BL and RS485-LN. The principle is to put the PC in the RS485 network and sniff the packet between Modbus MTU and RS485-BL/LN. We can use this way to: 1684 + 1685 +1. Test if Modbus-MTU works with PC commands. 1686 +1. Check if RS485-LN sent the expected command to Mobus-MTU 1687 +1. Check if Modbus-MTU return back the expected result to RS485-LN. 1688 +1. If both b) and c) has issue, we can compare PC’s output and RS485-LN output. 1689 + 1690 +[[image:image-20221130104310-1.png||height="380" width="680"]] 1691 + 1692 + 1693 +Example Connection: 1694 + 1695 +[[image:image-20221130104310-2.png]] 1696 + 1697 + 1698 +=== 6.7.2 Set up PC to monitor RS485 network With Serial tool === 1699 + 1700 +Note: Receive and send set to hex mode 1701 + 1702 +[[image:image-20221130104310-3.png||height="616" width="714"]] 1703 + 1704 + 1705 +=== 6.7.3 With ModRSsim2: === 1706 + 1707 +(1)Select serial port MODBUS RS-232 1708 + 1709 +[[image:image-20221130104310-4.png||height="390" width="865"]] 1710 + 1711 + 1712 +(2)Click the serial port icon 1713 + 1714 +[[image:image-20221130104310-5.png||height="392" width="870"]] 1715 + 1716 + 1717 +(3)After selecting the correct serial port and baud rate, click ok 1718 + 1719 +[[image:image-20221130104310-6.png]] 1720 + 1721 +(4)Click the comms. 1722 + 1723 +[[image:image-20221130104310-7.png||height="376" width="835"]] 1724 + 1725 +(% class="wikigeneratedid" id="HRunRS485-LN2FBLcommandandmonitorifitiscorrect." %) 1726 +Run RS485-LN/BL command and monitor if it is correct. 1727 + 1728 + 1729 +=== 6.7.4 Example – Test the CFGDEV command === 1730 + 1731 +RS485-LN sent below command: 1732 + 1733 +AT+CFGDEV=01 03 20 00 01 85 c0,1 to RS485 network, and PC is able to get this command and return commands from MTU to show in the serial tool. 1734 + 1735 + 1736 +We can see the output from the Serial port tool to analyze. And check if they are expected result. 1737 + 1738 +[[image:image-20221130104310-8.png||height="214" width="797"]] 1739 + 1740 +We can also use ModRSsim2 to see the output. 1741 + 1742 +[[image:image-20221130104310-9.png||height="531" width="729"]] 1743 + 1744 + 1745 + 1746 +=== 6.7.5 Example – Test CMD command sets. === 1747 + 1748 +Run AT+SENSORVALUE=1 to test the CMD commands set in RS485-LN. 1749 + 1750 + 1751 +Serial port tool: 1752 + 1753 +[[image:image-20221130104310-10.png||height="339" width="844"]] 1754 + 1755 +ModRSsim2: 1756 + 1757 +[[image:image-20221130104310-11.png||height="281" width="962"]] 1758 + 1759 + 1760 + 1761 +=== 6.7.6 Test with PC === 1762 + 1763 +If there is still have problem to set up correctly the commands between RS485-LN and MTU. User can test the correct RS485 command set in PC and compare with the RS485 command sent out via RS485-LN. as long as both commands are the same, the MTU should return correct result. 1764 + 1765 + 1766 +Or User can send the working commands set in PC serial tool to Dragino Support to check what should be configured in RS485-LN. 1767 + 1768 +Connection method: 1769 + 1770 +[[image:image-20221130104310-12.png]] 1771 + 1772 +Link situation: 1773 + 1774 +[[image:image-20221130104310-13.png||height="458" width="486"]] 1775 + 1776 +[[image:image-20221130104310-14.png||height="371" width="823"]] 1777 + 1778 + 1660 1660 = 7. Trouble Shooting = 1661 1661 1662 1662 ... ... @@ -1692,7 +1692,6 @@ 1692 1692 * (% style="color:red" %)**RU864**(%%): frequency bands RU864 1693 1693 * (% style="color:red" %)**KZ865**(%%): frequency bands KZ865 1694 1694 1695 - 1696 1696 = 9.Packing Info = 1697 1697 1698 1698 ... ... @@ -1709,7 +1709,6 @@ 1709 1709 * Package Size / pcs : 14.5 x 8 x 5 cm 1710 1710 * Weight / pcs : 170g 1711 1711 1712 - 1713 1713 = 10. FCC Caution for RS485LN-US915 = 1714 1714 1715 1715
- image-20221130104310-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +82.0 KB - Content
- image-20221130104310-10.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +17.4 KB - Content
- image-20221130104310-11.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +27.7 KB - Content
- image-20221130104310-12.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +392.9 KB - Content
- image-20221130104310-13.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +23.3 KB - Content
- image-20221130104310-14.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +25.4 KB - Content
- image-20221130104310-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +392.9 KB - Content
- image-20221130104310-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +30.4 KB - Content
- image-20221130104310-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +25.8 KB - Content
- image-20221130104310-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +22.9 KB - Content
- image-20221130104310-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +12.9 KB - Content
- image-20221130104310-7.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +25.1 KB - Content
- image-20221130104310-8.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +9.9 KB - Content
- image-20221130104310-9.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +29.1 KB - Content