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

Summary

Details

Page properties
Content
... ... @@ -7,12 +7,15 @@
7 7  **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
8 8  
9 9  
10 +
10 10  **Table of Contents:**
11 11  
13 +{{toc/}}
12 12  
13 13  
14 14  
15 15  
18 +
16 16  = 1.Introduction =
17 17  
18 18  == 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
... ... @@ -60,7 +60,7 @@
60 60  * Power Consumption (exclude RS485 device):
61 61  ** Idle: 6uA@3.3v
62 62  
63 -*
66 +*
64 64  ** 20dB Transmit: 130mA@3.3v
65 65  
66 66  **Interface for Model:**
... ... @@ -140,6 +140,8 @@
140 140  
141 141  (((
142 142  Release version ​​​​​
146 +
147 +
143 143  )))
144 144  
145 145  = 2. Pin mapping and Power ON Device =
... ... @@ -153,6 +153,7 @@
153 153  
154 154  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
155 155  
161 +
156 156  = 3. Operation Mode =
157 157  
158 158  == 3.1 How it works? ==
... ... @@ -159,6 +159,8 @@
159 159  
160 160  (((
161 161  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 +
162 162  )))
163 163  
164 164  == 3.2 Example to join LoRaWAN network ==
... ... @@ -222,7 +222,9 @@
222 222  == 3.3 Configure Commands to read data ==
223 223  
224 224  (((
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 +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 +
226 226  )))
227 227  
228 228  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
... ... @@ -397,7 +397,8 @@
397 397  
398 398  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
399 399  
400 -|(((
410 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
411 +|(% style="width:498px" %)(((
401 401  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
402 402  
403 403  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -411,38 +411,36 @@
411 411  
412 412  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
413 413  
414 -|(((
425 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
426 +|(% style="width:577px" %)(((
415 415  **AT+SEARCHx=aa,xx xx xx xx xx**
416 416  
417 417  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
418 418  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
419 -
420 -
421 421  )))
422 422  
423 -Examples:
433 +**Examples:**
424 424  
425 425  1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
426 426  
427 427  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
428 428  
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
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**
430 430  
431 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
441 +[[image:1653271044481-711.png]]
432 432  
433 -
434 434  1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
435 435  
436 436  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
437 437  
438 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
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**
439 439  
440 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
449 +[[image:1653271276735-972.png]]
441 441  
442 -
443 443  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
444 444  
445 -|(((
453 +(% style="background-color:#4f81bd; color:white; width:729px" %)
454 +|(% style="width:726px" %)(((
446 446  **AT+DATACUTx=a,b,c**
447 447  
448 448  * **a: length for the return of AT+COMMAND**
... ... @@ -454,95 +454,130 @@
454 454  
455 455  * Grab bytes:
456 456  
457 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
466 +[[image:1653271581490-837.png||height="313" width="722"]]
458 458  
459 459  * Grab a section.
460 460  
461 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
470 +[[image:1653271648378-342.png||height="326" width="720"]]
462 462  
463 463  * Grab different sections.
464 464  
465 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
474 +[[image:1653271657255-576.png||height="305" width="730"]]
466 466  
476 +(((
477 +(% style="color:red" %)**Note:**
478 +)))
467 467  
468 -Note:
469 -
480 +(((
470 470  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 +)))
471 471  
472 -Example:
484 +(((
485 +**Example:**
486 +)))
473 473  
474 -AT+COMMAND1=11 01 1E D0,0
488 +(((
489 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
490 +)))
475 475  
476 -AT+SEARCH1=1,1E 56 34
492 +(((
493 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
494 +)))
477 477  
478 -AT+DATACUT1=0,2,1~~5
496 +(((
497 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
498 +)))
479 479  
480 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
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 +)))
481 481  
482 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
504 +(((
505 +(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
506 +)))
483 483  
484 -Valid payload after DataCUT command: 2e 30 58 5f 36
508 +(((
509 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
510 +)))
485 485  
486 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
512 +[[image:1653271763403-806.png]]
487 487  
514 +=== 3.3.4 Compose the uplink payload ===
488 488  
489 -
490 -
491 -1.
492 -11.
493 -111. Compose the uplink payload
494 -
516 +(((
495 495  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 +)))
496 496  
520 +(((
521 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
522 +)))
497 497  
498 -**Examples: AT+DATAUP=0**
524 +(((
525 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
526 +)))
499 499  
500 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
501 -
528 +(((
502 502  Final Payload is
530 +)))
503 503  
504 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
532 +(((
533 +(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
534 +)))
505 505  
536 +(((
506 506  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
538 +)))
507 507  
508 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
540 +[[image:1653272787040-634.png||height="515" width="719"]]
509 509  
542 +(((
543 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
544 +)))
510 510  
546 +(((
547 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
548 +)))
511 511  
512 -**Examples: AT+DATAUP=1**
513 -
514 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
515 -
550 +(((
516 516  Final Payload is
552 +)))
517 517  
518 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
554 +(((
555 +(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
556 +)))
519 519  
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
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 +)))
525 525  
526 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
574 +[[image:1653272817147-600.png||height="437" width="717"]]
527 527  
528 -
529 529  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
530 530  
531 -DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
578 +DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
532 532  
533 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
580 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
534 534  
535 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
582 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
536 536  
537 -
538 -
539 539  Below are the uplink payloads:
540 540  
541 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
586 +[[image:1653272901032-107.png]]
542 542  
588 +(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
543 543  
544 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
545 -
546 546   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
547 547  
548 548   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
... ... @@ -551,90 +551,121 @@
551 551  
552 552   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
553 553  
598 +=== 3.3.5 Uplink on demand ===
554 554  
555 -
556 -1.
557 -11.
558 -111. Uplink on demand
559 -
600 +(((
560 560  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 +)))
561 561  
604 +(((
562 562  Downlink control command:
606 +)))
563 563  
564 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
608 +(((
609 +**0x08 command**: Poll an uplink with current command set in RS485-BL.
610 +)))
565 565  
566 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
612 +(((
613 +**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
614 +)))
567 567  
616 +=== 3.3.6 Uplink on Interrupt ===
568 568  
618 +Put the interrupt sensor between 3.3v_out and GPIO ext.
569 569  
570 -1.
571 -11.
572 -111. Uplink on Interrupt
620 +[[image:1653273818896-432.png]]
573 573  
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 -
622 +(((
576 576  AT+INTMOD=0  Disable Interrupt
624 +)))
577 577  
626 +(((
578 578  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
628 +)))
579 579  
630 +(((
580 580  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
632 +)))
581 581  
634 +(((
582 582  AT+INTMOD=3  Interrupt trigger by rising edge.
636 +)))
583 583  
638 +== 3.4 Uplink Payload ==
584 584  
585 -1.
586 -11. Uplink Payload
587 -
588 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
589 -|Value|(((
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 +(((
590 590  Battery(mV)
645 +)))
591 591  
647 +(((
592 592  &
649 +)))
593 593  
651 +(((
594 594  Interrupt _Flag
595 -)))|(((
653 +)))
654 +)))|(% style="width:93px" %)(((
596 596  PAYLOAD_VER
597 597  
598 598  
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.
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.
600 600  
601 601  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
602 602  
603 -
662 +(((
604 604  function Decoder(bytes, port) {
664 +)))
605 605  
666 +(((
606 606  ~/~/Payload Formats of RS485-BL Deceive
668 +)))
607 607  
670 +(((
608 608  return {
672 +)))
609 609  
674 +(((
610 610   ~/~/Battery,units:V
676 +)))
611 611  
678 +(((
612 612   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
680 +)))
613 613  
682 +(((
614 614   ~/~/GPIO_EXTI 
684 +)))
615 615  
686 +(((
616 616   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
688 +)))
617 617  
690 +(((
618 618   ~/~/payload of version
692 +)))
619 619  
694 +(((
620 620   Pay_ver:bytes[2],
696 +)))
621 621  
698 +(((
622 622   };
700 +)))
623 623  
702 +(((
624 624   }
704 +)))
625 625  
626 -
627 -
628 -
629 -
630 -
631 -
706 +(((
632 632  TTN V3 uplink screen shot.
708 +)))
633 633  
634 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
710 +[[image:1653274001211-372.png||height="192" width="732"]]
635 635  
636 -1.
637 -11. Configure RS485-BL via AT or Downlink
712 +== 3.5 Configure RS485-BL via AT or Downlink ==
638 638  
639 639  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
640 640  
... ... @@ -644,15 +644,15 @@
644 644  
645 645  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
646 646  
647 -1.
648 -11.
722 +1.
723 +11.
649 649  111. Common Commands:
650 650  
651 651  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]]
652 652  
653 653  
654 -1.
655 -11.
729 +1.
730 +11.
656 656  111. Sensor related commands:
657 657  
658 658  ==== Choose Device Type (RS485 or TTL) ====
... ... @@ -958,13 +958,13 @@
958 958  
959 959  
960 960  
961 -1.
1036 +1.
962 962  11. Buttons
963 963  
964 964  |**Button**|**Feature**
965 965  |**RST**|Reboot RS485-BL
966 966  
967 -1.
1042 +1.
968 968  11. +3V3 Output
969 969  
970 970  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
... ... @@ -982,7 +982,7 @@
982 982  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
983 983  
984 984  
985 -1.
1060 +1.
986 986  11. +5V Output
987 987  
988 988  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
... ... @@ -1002,13 +1002,13 @@
1002 1002  
1003 1003  
1004 1004  
1005 -1.
1080 +1.
1006 1006  11. LEDs
1007 1007  
1008 1008  |**LEDs**|**Feature**
1009 1009  |**LED1**|Blink when device transmit a packet.
1010 1010  
1011 -1.
1086 +1.
1012 1012  11. Switch Jumper
1013 1013  
1014 1014  |**Switch Jumper**|**Feature**
... ... @@ -1054,7 +1054,7 @@
1054 1054  
1055 1055  
1056 1056  
1057 -1.
1132 +1.
1058 1058  11. Common AT Command Sequence
1059 1059  111. Multi-channel ABP mode (Use with SX1301/LG308)
1060 1060  
... ... @@ -1073,8 +1073,8 @@
1073 1073  
1074 1074  ATZ
1075 1075  
1076 -1.
1077 -11.
1151 +1.
1152 +11.
1078 1078  111. Single-channel ABP mode (Use with LG01/LG02)
1079 1079  
1080 1080  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
... ... @@ -1149,7 +1149,7 @@
1149 1149  [[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]]
1150 1150  
1151 1151  
1152 -1.
1227 +1.
1153 1153  11. How to change the LoRa Frequency Bands/Region?
1154 1154  
1155 1155  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1156,7 +1156,7 @@
1156 1156  
1157 1157  
1158 1158  
1159 -1.
1234 +1.
1160 1160  11. How many RS485-Slave can RS485-BL connects?
1161 1161  
1162 1162  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]].
... ... @@ -1173,7 +1173,7 @@
1173 1173  
1174 1174  
1175 1175  
1176 -1.
1251 +1.
1177 1177  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1178 1178  
1179 1179  It might about the channels mapping. Please see for detail.
1652954654347-831.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653271044481-711.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.8 KB
Content
1653271276735-972.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.6 KB
Content
1653271581490-837.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653271648378-342.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +131.4 KB
Content
1653271657255-576.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +142.6 KB
Content
1653271763403-806.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.7 KB
Content
1653272787040-634.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +294.0 KB
Content
1653272817147-600.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +143.3 KB
Content
1653272901032-107.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +197.8 KB
Content
1653273818896-432.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.6 KB
Content
1653274001211-372.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +91.4 KB
Content