Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 29.7
edited by Xiaoling
on 2022/06/01 18:01
Change comment: There is no comment for this version
To version 15.6
edited by Xiaoling
on 2022/05/19 17:59
Change comment: There is no comment for this version

Summary

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:**
... ... @@ -162,8 +162,6 @@
162 162  
163 163  (((
164 164  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.
165 -
166 -
167 167  )))
168 168  
169 169  == 3.2 Example to join LoRaWAN network ==
... ... @@ -227,9 +227,7 @@
227 227  == 3.3 Configure Commands to read data ==
228 228  
229 229  (((
230 -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.
231 -
232 -
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.
233 233  )))
234 234  
235 235  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
... ... @@ -404,8 +404,7 @@
404 404  
405 405  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
406 406  
407 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
408 -|(% style="width:498px" %)(((
400 +|(((
409 409  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
410 410  
411 411  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -419,36 +419,38 @@
419 419  
420 420  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
421 421  
422 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
423 -|(% style="width:577px" %)(((
414 +|(((
424 424  **AT+SEARCHx=aa,xx xx xx xx xx**
425 425  
426 426  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
427 427  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
419 +
420 +
428 428  )))
429 429  
430 -**Examples:**
423 +Examples:
431 431  
432 432  1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
433 433  
434 434  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
435 435  
436 -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**
429 +The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
437 437  
438 -[[image:1653271044481-711.png]]
431 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
439 439  
433 +
440 440  1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
441 441  
442 442  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
443 443  
444 -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**
438 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
445 445  
446 -[[image:1653271276735-972.png]]
440 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
447 447  
442 +
448 448  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
449 449  
450 -(% style="background-color:#4f81bd; color:white; width:729px" %)
451 -|(% style="width:726px" %)(((
445 +|(((
452 452  **AT+DATACUTx=a,b,c**
453 453  
454 454  * **a: length for the return of AT+COMMAND**
... ... @@ -460,130 +460,95 @@
460 460  
461 461  * Grab bytes:
462 462  
463 -[[image:1653271581490-837.png||height="313" width="722"]]
457 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
464 464  
465 465  * Grab a section.
466 466  
467 -[[image:1653271648378-342.png||height="326" width="720"]]
461 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
468 468  
469 469  * Grab different sections.
470 470  
471 -[[image:1653271657255-576.png||height="305" width="730"]]
465 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
472 472  
473 -(((
474 -(% style="color:red" %)**Note:**
475 -)))
476 476  
477 -(((
468 +Note:
469 +
478 478  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.
479 -)))
480 480  
481 -(((
482 -**Example:**
483 -)))
472 +Example:
484 484  
485 -(((
486 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
487 -)))
474 +AT+COMMAND1=11 01 1E D0,0
488 488  
489 -(((
490 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
491 -)))
476 +AT+SEARCH1=1,1E 56 34
492 492  
493 -(((
494 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
495 -)))
478 +AT+DATACUT1=0,2,1~~5
496 496  
497 -(((
498 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
499 -)))
480 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
500 500  
501 -(((
502 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
503 -)))
482 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
504 504  
505 -(((
506 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
507 -)))
484 +Valid payload after DataCUT command: 2e 30 58 5f 36
508 508  
509 -[[image:1653271763403-806.png]]
486 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
510 510  
511 -=== 3.3.4 Compose the uplink payload ===
512 512  
513 -(((
489 +
490 +
491 +1.
492 +11.
493 +111. Compose the uplink payload
494 +
514 514  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.**
515 -)))
516 516  
517 -(((
518 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
519 -)))
520 520  
521 -(((
522 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
523 -)))
498 +**Examples: AT+DATAUP=0**
524 524  
525 -(((
500 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
501 +
526 526  Final Payload is
527 -)))
528 528  
529 -(((
530 -(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
531 -)))
504 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
532 532  
533 -(((
534 534  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
535 -)))
536 536  
537 -[[image:1653272787040-634.png||height="515" width="719"]]
508 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
538 538  
539 -(((
540 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
541 -)))
542 542  
543 -(((
544 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
545 -)))
546 546  
547 -(((
512 +**Examples: AT+DATAUP=1**
513 +
514 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
515 +
548 548  Final Payload is
549 -)))
550 550  
551 -(((
552 -(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
553 -)))
518 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
554 554  
555 -1. (((
556 -Battery Info (2 bytes): Battery voltage
557 -)))
558 -1. (((
559 -PAYVER (1 byte): Defined by AT+PAYVER
560 -)))
561 -1. (((
562 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
563 -)))
564 -1. (((
565 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
566 -)))
567 -1. (((
568 -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
569 -)))
520 +1. Battery Info (2 bytes): Battery voltage
521 +1. PAYVER (1 byte): Defined by AT+PAYVER
522 +1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
523 +1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
524 +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
570 570  
571 -[[image:1653272817147-600.png||height="437" width="717"]]
526 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
572 572  
528 +
573 573  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
574 574  
575 -DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
531 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
576 576  
577 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
533 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
578 578  
579 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
535 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
580 580  
537 +
538 +
581 581  Below are the uplink payloads:
582 582  
583 -[[image:1653272901032-107.png]]
541 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
584 584  
585 -(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
586 586  
544 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
545 +
587 587   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
588 588  
589 589   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
... ... @@ -592,121 +592,90 @@
592 592  
593 593   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
594 594  
595 -=== 3.3.5 Uplink on demand ===
596 596  
597 -(((
555 +
556 +1.
557 +11.
558 +111. Uplink on demand
559 +
598 598  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.
599 -)))
600 600  
601 -(((
602 602  Downlink control command:
603 -)))
604 604  
605 -(((
606 -**0x08 command**: Poll an uplink with current command set in RS485-BL.
607 -)))
564 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
608 608  
609 -(((
610 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
611 -)))
566 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
612 612  
613 -=== 3.3.6 Uplink on Interrupt ===
614 614  
615 -Put the interrupt sensor between 3.3v_out and GPIO ext.
616 616  
617 -[[image:1653273818896-432.png]]
570 +1.
571 +11.
572 +111. Uplink on Interrupt
618 618  
619 -(((
574 +Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
575 +
620 620  AT+INTMOD=0  Disable Interrupt
621 -)))
622 622  
623 -(((
624 624  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
625 -)))
626 626  
627 -(((
628 628  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
629 -)))
630 630  
631 -(((
632 632  AT+INTMOD=3  Interrupt trigger by rising edge.
633 -)))
634 634  
635 -== 3.4 Uplink Payload ==
636 636  
637 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
638 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
639 -|Value|(% style="width:130px" %)(((
640 -(((
585 +1.
586 +11. Uplink Payload
587 +
588 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
589 +|Value|(((
641 641  Battery(mV)
642 -)))
643 643  
644 -(((
645 645  &
646 -)))
647 647  
648 -(((
649 649  Interrupt _Flag
650 -)))
651 -)))|(% style="width:93px" %)(((
595 +)))|(((
652 652  PAYLOAD_VER
653 653  
654 654  
655 -)))|(% 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.
599 +)))|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.
656 656  
657 657  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
658 658  
659 -(((
603 +
660 660  function Decoder(bytes, port) {
661 -)))
662 662  
663 -(((
664 664  ~/~/Payload Formats of RS485-BL Deceive
665 -)))
666 666  
667 -(((
668 668  return {
669 -)))
670 670  
671 -(((
672 672   ~/~/Battery,units:V
673 -)))
674 674  
675 -(((
676 676   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
677 -)))
678 678  
679 -(((
680 680   ~/~/GPIO_EXTI 
681 -)))
682 682  
683 -(((
684 684   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
685 -)))
686 686  
687 -(((
688 688   ~/~/payload of version
689 -)))
690 690  
691 -(((
692 692   Pay_ver:bytes[2],
693 -)))
694 694  
695 -(((
696 696   };
697 -)))
698 698  
699 -(((
700 700   }
701 -)))
702 702  
703 -(((
626 +
627 +
628 +
629 +
630 +
631 +
704 704  TTN V3 uplink screen shot.
705 -)))
706 706  
707 -[[image:1653274001211-372.png||height="192" width="732"]]
634 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
708 708  
709 -== 3.5 Configure RS485-BL via AT or Downlink ==
636 +1.
637 +11. Configure RS485-BL via AT or Downlink
710 710  
711 711  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
712 712  
... ... @@ -716,15 +716,15 @@
716 716  
717 717  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
718 718  
719 -1.
720 -11.
647 +1.
648 +11.
721 721  111. Common Commands:
722 722  
723 723  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]]
724 724  
725 725  
726 -1.
727 -11.
654 +1.
655 +11.
728 728  111. Sensor related commands:
729 729  
730 730  ==== Choose Device Type (RS485 or TTL) ====
... ... @@ -1030,13 +1030,13 @@
1030 1030  
1031 1031  
1032 1032  
1033 -1.
961 +1.
1034 1034  11. Buttons
1035 1035  
1036 1036  |**Button**|**Feature**
1037 1037  |**RST**|Reboot RS485-BL
1038 1038  
1039 -1.
967 +1.
1040 1040  11. +3V3 Output
1041 1041  
1042 1042  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
... ... @@ -1054,7 +1054,7 @@
1054 1054  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
1055 1055  
1056 1056  
1057 -1.
985 +1.
1058 1058  11. +5V Output
1059 1059  
1060 1060  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
... ... @@ -1074,13 +1074,13 @@
1074 1074  
1075 1075  
1076 1076  
1077 -1.
1005 +1.
1078 1078  11. LEDs
1079 1079  
1080 1080  |**LEDs**|**Feature**
1081 1081  |**LED1**|Blink when device transmit a packet.
1082 1082  
1083 -1.
1011 +1.
1084 1084  11. Switch Jumper
1085 1085  
1086 1086  |**Switch Jumper**|**Feature**
... ... @@ -1126,7 +1126,7 @@
1126 1126  
1127 1127  
1128 1128  
1129 -1.
1057 +1.
1130 1130  11. Common AT Command Sequence
1131 1131  111. Multi-channel ABP mode (Use with SX1301/LG308)
1132 1132  
... ... @@ -1145,8 +1145,8 @@
1145 1145  
1146 1146  ATZ
1147 1147  
1148 -1.
1149 -11.
1076 +1.
1077 +11.
1150 1150  111. Single-channel ABP mode (Use with LG01/LG02)
1151 1151  
1152 1152  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
... ... @@ -1221,7 +1221,7 @@
1221 1221  [[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]]
1222 1222  
1223 1223  
1224 -1.
1152 +1.
1225 1225  11. How to change the LoRa Frequency Bands/Region?
1226 1226  
1227 1227  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1228,7 +1228,7 @@
1228 1228  
1229 1229  
1230 1230  
1231 -1.
1159 +1.
1232 1232  11. How many RS485-Slave can RS485-BL connects?
1233 1233  
1234 1234  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]].
... ... @@ -1245,7 +1245,7 @@
1245 1245  
1246 1246  
1247 1247  
1248 -1.
1176 +1.
1249 1249  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1250 1250  
1251 1251  It might about the channels mapping. Please see for detail.
1652954654347-831.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
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