Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 29.9
edited by Xiaoling
on 2022/06/01 18:01
Change comment: There is no comment for this version
To version 17.1
edited by Xiaoling
on 2022/05/19 18:04
Change comment: Uploaded new attachment "1652954654347-831.png", version {1}

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