Changes for page RS485-BL – Waterproof RS485 to LoRaWAN Converter
Last modified by Xiaoling on 2025/04/23 15:57
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 11 removed)
Details
- Page properties
-
- Content
-
... ... @@ -7,15 +7,12 @@ 7 7 **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual** 8 8 9 9 10 - 11 11 **Table of Contents:** 12 12 13 -{{toc/}} 14 14 15 15 16 16 17 17 18 - 19 19 = 1.Introduction = 20 20 21 21 == 1.1 What is RS485-BL RS485 to LoRaWAN Converter == ... ... @@ -63,7 +63,7 @@ 63 63 * Power Consumption (exclude RS485 device): 64 64 ** Idle: 6uA@3.3v 65 65 66 -* 63 +* 67 67 ** 20dB Transmit: 130mA@3.3v 68 68 69 69 **Interface for Model:** ... ... @@ -156,7 +156,6 @@ 156 156 157 157 The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper. 158 158 159 - 160 160 = 3. Operation Mode = 161 161 162 162 == 3.1 How it works? == ... ... @@ -163,8 +163,6 @@ 163 163 164 164 ((( 165 165 The RS485-BL is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join network. To connect a local LoRaWAN network, user just need to input the OTAA keys in the network server and power on the RS485-BL. It will auto join the network via OTAA. 166 - 167 - 168 168 ))) 169 169 170 170 == 3.2 Example to join LoRaWAN network == ... ... @@ -228,9 +228,7 @@ 228 228 == 3.3 Configure Commands to read data == 229 229 230 230 ((( 231 -There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors. 232 - 233 - 225 +There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>path:#AT_COMMAND]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors. 234 234 ))) 235 235 236 236 === 3.3.1 onfigure UART settings for RS485 or TTL communication === ... ... @@ -405,8 +405,8 @@ 405 405 406 406 **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is: 407 407 408 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px"%)409 -|( % style="width:498px" %)(((400 +(% border="1" class="table-bordered" %) 401 +|((( 410 410 **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m** 411 411 412 412 **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent** ... ... @@ -420,36 +420,39 @@ 420 420 421 421 **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx. 422 422 423 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px"%)424 -|( % style="width:577px" %)(((415 +(% border="1" class="table-bordered" %) 416 +|((( 425 425 **AT+SEARCHx=aa,xx xx xx xx xx** 426 426 427 427 * **aa: 1: prefix match mode; 2: prefix and suffix match mode** 428 428 * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix** 421 + 422 + 429 429 ))) 430 430 431 - **Examples:**425 +Examples: 432 432 433 433 1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 434 434 435 435 If we set AT+SEARCH1=1,1E 56 34. (max 5 bytes for prefix) 436 436 437 -The valid data will be all bytes after 1E 56 34 , so it is (% style="background-color:yellow" %)**2e 30 58 5f 36 41 30 31 00 49**431 +The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49 438 438 439 -[[image: 1653271044481-711.png]]433 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]] 440 440 435 + 441 441 1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 442 442 443 443 If we set AT+SEARCH1=2, 1E 56 34+31 00 49 444 444 445 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is (%style="background-color:yellow" %) **2e 30 58 5f 36 41 30**440 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30 446 446 447 -[[image: 1653271276735-972.png]]442 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]] 448 448 444 + 449 449 **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes. 450 450 451 -(% style="background-color:#4f81bd; color:white; width:729px" %) 452 -|(% style="width:726px" %)((( 447 +|((( 453 453 **AT+DATACUTx=a,b,c** 454 454 455 455 * **a: length for the return of AT+COMMAND** ... ... @@ -461,130 +461,95 @@ 461 461 462 462 * Grab bytes: 463 463 464 -[[image: 1653271581490-837.png||height="313" width="722"]]459 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]] 465 465 466 466 * Grab a section. 467 467 468 -[[image: 1653271648378-342.png||height="326" width="720"]]463 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]] 469 469 470 470 * Grab different sections. 471 471 472 -[[image: 1653271657255-576.png||height="305" width="730"]]467 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]] 473 473 474 -((( 475 -(% style="color:red" %)**Note:** 476 -))) 477 477 478 -((( 470 +Note: 471 + 479 479 AT+SEARCHx and AT+DATACUTx can be used together, if both commands are set, RS485-BL will first process AT+SEARCHx on the return string and get a temporary string, and then process AT+DATACUTx on this temporary string to get the final payload. In this case, AT+DATACUTx need to set to format AT+DATACUTx=0,xx,xx where the return bytes set to 0. 480 -))) 481 481 482 -((( 483 -**Example:** 484 -))) 474 +Example: 485 485 486 -((( 487 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0 488 -))) 476 +AT+COMMAND1=11 01 1E D0,0 489 489 490 -((( 491 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34 492 -))) 478 +AT+SEARCH1=1,1E 56 34 493 493 494 -((( 495 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5 496 -))) 480 +AT+DATACUT1=0,2,1~~5 497 497 498 -((( 499 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 500 -))) 482 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 501 501 502 -((( 503 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49 504 -))) 484 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49 505 505 506 -((( 507 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36 508 -))) 486 +Valid payload after DataCUT command: 2e 30 58 5f 36 509 509 510 -[[image: 1653271763403-806.png]]488 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]] 511 511 512 -=== 3.3.4 Compose the uplink payload === 513 513 514 -((( 491 + 492 + 493 +1. 494 +11. 495 +111. Compose the uplink payload 496 + 515 515 Through AT+COMMANDx and AT+DATACUTx we got valid value from each RS485 commands, Assume these valid value are RETURN1, RETURN2, .., to RETURNx. The next step is how to compose the LoRa Uplink Payload by these RETURNs. The command is **AT+DATAUP.** 516 -))) 517 517 518 -((( 519 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0** 520 -))) 521 521 522 -((( 523 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**. 524 -))) 500 +**Examples: AT+DATAUP=0** 525 525 526 -((( 502 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**. 503 + 527 527 Final Payload is 528 -))) 529 529 530 -((( 531 -(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx 532 -))) 506 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx 533 533 534 -((( 535 535 Where PAYVER is defined by AT+PAYVER, below is an example screen shot. 536 -))) 537 537 538 -[[image: 1653272787040-634.png||height="515" width="719"]]510 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]] 539 539 540 -((( 541 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1** 542 -))) 543 543 544 -((( 545 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**. 546 -))) 547 547 548 -((( 514 +**Examples: AT+DATAUP=1** 515 + 516 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**. 517 + 549 549 Final Payload is 550 -))) 551 551 552 -((( 553 -(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA 554 -))) 520 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA 555 555 556 -1. ((( 557 -Battery Info (2 bytes): Battery voltage 558 -))) 559 -1. ((( 560 -PAYVER (1 byte): Defined by AT+PAYVER 561 -))) 562 -1. ((( 563 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling. 564 -))) 565 -1. ((( 566 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 567 -))) 568 -1. ((( 569 -DATA: Valid value: max 6 bytes(US915 version here, Notice*!) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes 570 -))) 522 +1. Battery Info (2 bytes): Battery voltage 523 +1. PAYVER (1 byte): Defined by AT+PAYVER 524 +1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling. 525 +1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 526 +1. DATA: Valid value: max 6 bytes(US915 version here, [[Notice*!>>path:#max_byte]]) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes 571 571 572 -[[image: 1653272817147-600.png||height="437" width="717"]]528 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]] 573 573 530 + 574 574 So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA 575 575 576 -DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %)20 20 0a 33 90 41533 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41 577 577 578 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20535 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20 579 579 580 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (%style="background-color:#4f81bd; color:white" %)20 20 20 2d 30537 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30 581 581 539 + 540 + 582 582 Below are the uplink payloads: 583 583 584 -[[image: 1653272901032-107.png]]543 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]] 585 585 586 -(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below: 587 587 546 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below: 547 + 588 588 ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date) 589 589 590 590 * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date). ... ... @@ -593,121 +593,90 @@ 593 593 594 594 ~* For all other bands: max 51 bytes for each uplink ( so 51 -5 = 46 max valid date). 595 595 596 -=== 3.3.5 Uplink on demand === 597 597 598 -((( 557 + 558 +1. 559 +11. 560 +111. Uplink on demand 561 + 599 599 Except uplink periodically, RS485-BL is able to uplink on demand. The server sends downlink command to RS485-BL and RS485 will uplink data base on the command. 600 -))) 601 601 602 -((( 603 603 Downlink control command: 604 -))) 605 605 606 -((( 607 -**0x08 command**: Poll an uplink with current command set in RS485-BL. 608 -))) 566 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL. 609 609 610 -((( 611 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors. 612 -))) 568 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors. 613 613 614 -=== 3.3.6 Uplink on Interrupt === 615 615 616 -Put the interrupt sensor between 3.3v_out and GPIO ext. 617 617 618 -[[image:1653273818896-432.png]] 572 +1. 573 +11. 574 +111. Uplink on Interrupt 619 619 620 -((( 576 +Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]] 577 + 621 621 AT+INTMOD=0 Disable Interrupt 622 -))) 623 623 624 -((( 625 625 AT+INTMOD=1 Interrupt trigger by rising or falling edge. 626 -))) 627 627 628 -((( 629 629 AT+INTMOD=2 Interrupt trigger by falling edge. ( Default Value) 630 -))) 631 631 632 -((( 633 633 AT+INTMOD=3 Interrupt trigger by rising edge. 634 -))) 635 635 636 -== 3.4 Uplink Payload == 637 637 638 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %) 639 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands** 640 -|Value|(% style="width:130px" %)((( 641 -((( 587 +1. 588 +11. Uplink Payload 589 + 590 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands** 591 +|Value|((( 642 642 Battery(mV) 643 -))) 644 644 645 -((( 646 646 & 647 -))) 648 648 649 -((( 650 650 Interrupt _Flag 651 -))) 652 -)))|(% style="width:93px" %)((( 597 +)))|((( 653 653 PAYLOAD_VER 654 654 655 655 656 -)))| (% style="width:509px" %)If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.601 +)))|If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server. 657 657 658 658 Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors. 659 659 660 - (((605 + 661 661 function Decoder(bytes, port) { 662 -))) 663 663 664 -((( 665 665 ~/~/Payload Formats of RS485-BL Deceive 666 -))) 667 667 668 -((( 669 669 return { 670 -))) 671 671 672 -((( 673 673 ~/~/Battery,units:V 674 -))) 675 675 676 -((( 677 677 BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000, 678 -))) 679 679 680 -((( 681 681 ~/~/GPIO_EXTI 682 -))) 683 683 684 -((( 685 685 EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE", 686 -))) 687 687 688 -((( 689 689 ~/~/payload of version 690 -))) 691 691 692 -((( 693 693 Pay_ver:bytes[2], 694 -))) 695 695 696 -((( 697 697 }; 698 -))) 699 699 700 -((( 701 701 } 702 -))) 703 703 704 -((( 628 + 629 + 630 + 631 + 632 + 633 + 705 705 TTN V3 uplink screen shot. 706 -))) 707 707 708 -[[image: 1653274001211-372.png||height="192" width="732"]]636 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]] 709 709 710 -== 3.5 Configure RS485-BL via AT or Downlink == 638 +1. 639 +11. Configure RS485-BL via AT or Downlink 711 711 712 712 User can configure RS485-BL via [[AT Commands >>path:#_Using_the_AT]]or LoRaWAN Downlink Commands 713 713 ... ... @@ -717,15 +717,15 @@ 717 717 718 718 * **Sensor Related Commands**: These commands are special designed for RS485-BL. User can see these commands below: 719 719 720 -1. 721 -11. 649 +1. 650 +11. 722 722 111. Common Commands: 723 723 724 724 They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands>>url:http://wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands]] 725 725 726 726 727 -1. 728 -11. 656 +1. 657 +11. 729 729 111. Sensor related commands: 730 730 731 731 ==== Choose Device Type (RS485 or TTL) ==== ... ... @@ -1031,13 +1031,13 @@ 1031 1031 1032 1032 1033 1033 1034 -1. 963 +1. 1035 1035 11. Buttons 1036 1036 1037 1037 |**Button**|**Feature** 1038 1038 |**RST**|Reboot RS485-BL 1039 1039 1040 -1. 969 +1. 1041 1041 11. +3V3 Output 1042 1042 1043 1043 RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor. ... ... @@ -1055,7 +1055,7 @@ 1055 1055 By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time 1056 1056 1057 1057 1058 -1. 987 +1. 1059 1059 11. +5V Output 1060 1060 1061 1061 RS485-BL has a Controllable +5V output, user can use this output to power external sensor. ... ... @@ -1075,13 +1075,13 @@ 1075 1075 1076 1076 1077 1077 1078 -1. 1007 +1. 1079 1079 11. LEDs 1080 1080 1081 1081 |**LEDs**|**Feature** 1082 1082 |**LED1**|Blink when device transmit a packet. 1083 1083 1084 -1. 1013 +1. 1085 1085 11. Switch Jumper 1086 1086 1087 1087 |**Switch Jumper**|**Feature** ... ... @@ -1127,7 +1127,7 @@ 1127 1127 1128 1128 1129 1129 1130 -1. 1059 +1. 1131 1131 11. Common AT Command Sequence 1132 1132 111. Multi-channel ABP mode (Use with SX1301/LG308) 1133 1133 ... ... @@ -1146,8 +1146,8 @@ 1146 1146 1147 1147 ATZ 1148 1148 1149 -1. 1150 -11. 1078 +1. 1079 +11. 1151 1151 111. Single-channel ABP mode (Use with LG01/LG02) 1152 1152 1153 1153 AT+FDR Reset Parameters to Factory Default, Keys Reserve ... ... @@ -1222,7 +1222,7 @@ 1222 1222 [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image035.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image036.png]] 1223 1223 1224 1224 1225 -1. 1154 +1. 1226 1226 11. How to change the LoRa Frequency Bands/Region? 1227 1227 1228 1228 User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download. ... ... @@ -1229,7 +1229,7 @@ 1229 1229 1230 1230 1231 1231 1232 -1. 1161 +1. 1233 1233 11. How many RS485-Slave can RS485-BL connects? 1234 1234 1235 1235 The RS485-BL can support max 32 RS485 devices. Each uplink command of RS485-BL can support max 16 different RS485 command. So RS485-BL can support max 16 RS485 devices pre-program in the device for uplink. For other devices no pre-program, user can use the [[downlink message (type code 0xA8) to poll their info>>path:#downlink_A8]]. ... ... @@ -1246,7 +1246,7 @@ 1246 1246 1247 1247 1248 1248 1249 -1. 1178 +1. 1250 1250 11. Why I can’t join TTN V3 in US915 /AU915 bands? 1251 1251 1252 1252 It might about the channels mapping. Please see for detail.
- 1653271044481-711.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -27.8 KB - Content
- 1653271276735-972.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -26.6 KB - Content
- 1653271581490-837.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.7 KB - Content
- 1653271648378-342.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -131.4 KB - Content
- 1653271657255-576.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -142.6 KB - Content
- 1653271763403-806.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -27.7 KB - Content
- 1653272787040-634.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -294.0 KB - Content
- 1653272817147-600.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -143.3 KB - Content
- 1653272901032-107.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -197.8 KB - Content
- 1653273818896-432.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.6 KB - Content
- 1653274001211-372.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -91.4 KB - Content