Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 29.22
edited by Xiaoling
on 2022/06/01 18:08
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 ==
... ... @@ -25,19 +25,19 @@
25 25  )))
26 26  
27 27  (((
28 -The Dragino RS485-BL is a (% style="color:blue" %)**RS485 / UART to LoRaWAN Converter**(%%) for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.
25 +The Dragino RS485-BL is a **RS485 / UART to LoRaWAN Converter** for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.
29 29  )))
30 30  
31 31  (((
32 -RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides (% style="color:blue" %)**a 3.3v output**(%%) and** (% style="color:blue" %)a 5v output(%%)** to power external sensors. Both output voltages are controllable to minimize the total system power consumption.
29 +RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides **a 3.3v output** and** a 5v output** to power external sensors. Both output voltages are controllable to minimize the total system power consumption.
33 33  )))
34 34  
35 35  (((
36 -RS485-BL is IP67 (% style="color:blue" %)**waterproof**(%%) and powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use for several years.
33 +RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years.
37 37  )))
38 38  
39 39  (((
40 -RS485-BL runs standard (% style="color:blue" %)**LoRaWAN 1.0.3 in Class A**(%%). It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server.
37 +RS485-BL runs standard **LoRaWAN 1.0.3 in Class A**. It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server.
41 41  )))
42 42  
43 43  (((
... ... @@ -54,11 +54,8 @@
54 54  
55 55  [[image:1652953304999-717.png||height="424" width="733"]]
56 56  
57 -
58 -
59 59  == 1.2 Specifications ==
60 60  
61 -
62 62  **Hardware System:**
63 63  
64 64  * STM32L072CZT6 MCU
... ... @@ -65,9 +65,10 @@
65 65  * SX1276/78 Wireless Chip 
66 66  * Power Consumption (exclude RS485 device):
67 67  ** Idle: 6uA@3.3v
62 +
63 +*
68 68  ** 20dB Transmit: 130mA@3.3v
69 69  
70 -
71 71  **Interface for Model:**
72 72  
73 73  * 1 x RS485 Interface
... ... @@ -77,7 +77,6 @@
77 77  * 1 x Interrupt Interface
78 78  * 1 x Controllable 5V output, max
79 79  
80 -
81 81  **LoRa Spec:**
82 82  
83 83  * Frequency Range:
... ... @@ -96,7 +96,6 @@
96 96  * 127 dB Dynamic Range RSSI.
97 97  * Automatic RF Sense and CAD with ultra-fast AFC. ​​​
98 98  
99 -
100 100  == 1.3 Features ==
101 101  
102 102  * LoRaWAN Class A & Class C protocol (default Class A)
... ... @@ -108,7 +108,6 @@
108 108  * Support Modbus protocol
109 109  * Support Interrupt uplink
110 110  
111 -
112 112  == 1.4 Applications ==
113 113  
114 114  * Smart Buildings & Home Automation
... ... @@ -118,17 +118,13 @@
118 118  * Smart Cities
119 119  * Smart Factory
120 120  
121 -
122 122  == 1.5 Firmware Change log ==
123 123  
124 124  [[RS485-BL Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Firmware/||style="background-color: rgb(255, 255, 255);"]]
125 125  
126 -
127 127  == 1.6 Hardware Change log ==
128 128  
129 129  (((
130 -
131 -
132 132  v1.4
133 133  )))
134 134  
... ... @@ -152,8 +152,6 @@
152 152  
153 153  (((
154 154  Release version ​​​​​
155 -
156 -
157 157  )))
158 158  
159 159  = 2. Pin mapping and Power ON Device =
... ... @@ -167,7 +167,6 @@
167 167  
168 168  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
169 169  
170 -
171 171  = 3. Operation Mode =
172 172  
173 173  == 3.1 How it works? ==
... ... @@ -174,8 +174,6 @@
174 174  
175 175  (((
176 176  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.
177 -
178 -
179 179  )))
180 180  
181 181  == 3.2 Example to join LoRaWAN network ==
... ... @@ -211,6 +211,8 @@
211 211  )))
212 212  
213 213  
197 +
198 +
214 214  [[image:image-20220519174512-1.png]]
215 215  
216 216  [[image:image-20220519174512-2.png||height="328" width="731"]]
... ... @@ -234,13 +234,10 @@
234 234  
235 235  [[image:1652953568895-172.png||height="232" width="724"]]
236 236  
237 -
238 238  == 3.3 Configure Commands to read data ==
239 239  
240 240  (((
241 -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.
242 -
243 -
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.
244 244  )))
245 245  
246 246  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
... ... @@ -321,8 +321,6 @@
321 321  )))
322 322  )))
323 323  
324 -
325 -
326 326  === 3.3.2 Configure sensors ===
327 327  
328 328  (((
... ... @@ -345,7 +345,6 @@
345 345  
346 346  Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
347 347  
348 -
349 349  === 3.3.3 Configure read commands for each sampling ===
350 350  
351 351  (((
... ... @@ -418,8 +418,8 @@
418 418  
419 419  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
420 420  
421 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
422 -|(% style="width:498px" %)(((
400 +(% border="1" class="table-bordered" %)
401 +|(((
423 423  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
424 424  
425 425  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -433,36 +433,39 @@
433 433  
434 434  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
435 435  
436 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
437 -|(% style="width:577px" %)(((
415 +(% border="1" class="table-bordered" %)
416 +|(((
438 438  **AT+SEARCHx=aa,xx xx xx xx xx**
439 439  
440 440  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
441 441  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
421 +
422 +
442 442  )))
443 443  
444 -**Examples:**
425 +Examples:
445 445  
446 446  1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
447 447  
448 448  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
449 449  
450 -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
451 451  
452 -[[image:1653271044481-711.png]]
433 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
453 453  
435 +
454 454  1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
455 455  
456 456  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
457 457  
458 -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
459 459  
460 -[[image:1653271276735-972.png]]
442 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
461 461  
444 +
462 462  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
463 463  
464 -(% style="background-color:#4f81bd; color:white; width:729px" %)
465 -|(% style="width:726px" %)(((
447 +|(((
466 466  **AT+DATACUTx=a,b,c**
467 467  
468 468  * **a: length for the return of AT+COMMAND**
... ... @@ -474,130 +474,95 @@
474 474  
475 475  * Grab bytes:
476 476  
477 -[[image:1653271581490-837.png||height="313" width="722"]]
459 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
478 478  
479 479  * Grab a section.
480 480  
481 -[[image:1653271648378-342.png||height="326" width="720"]]
463 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
482 482  
483 483  * Grab different sections.
484 484  
485 -[[image:1653271657255-576.png||height="305" width="730"]]
467 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
486 486  
487 -(((
488 -(% style="color:red" %)**Note:**
489 -)))
490 490  
491 -(((
470 +Note:
471 +
492 492  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.
493 -)))
494 494  
495 -(((
496 -**Example:**
497 -)))
474 +Example:
498 498  
499 -(((
500 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
501 -)))
476 +AT+COMMAND1=11 01 1E D0,0
502 502  
503 -(((
504 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
505 -)))
478 +AT+SEARCH1=1,1E 56 34
506 506  
507 -(((
508 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
509 -)))
480 +AT+DATACUT1=0,2,1~~5
510 510  
511 -(((
512 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
513 -)))
482 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
514 514  
515 -(((
516 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
517 -)))
484 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
518 518  
519 -(((
520 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
521 -)))
486 +Valid payload after DataCUT command: 2e 30 58 5f 36
522 522  
523 -[[image:1653271763403-806.png]]
488 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
524 524  
525 -=== 3.3.4 Compose the uplink payload ===
526 526  
527 -(((
491 +
492 +
493 +1.
494 +11.
495 +111. Compose the uplink payload
496 +
528 528  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.**
529 -)))
530 530  
531 -(((
532 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
533 -)))
534 534  
535 -(((
536 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
537 -)))
500 +**Examples: AT+DATAUP=0**
538 538  
539 -(((
502 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
503 +
540 540  Final Payload is
541 -)))
542 542  
543 -(((
544 -(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
545 -)))
506 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
546 546  
547 -(((
548 548  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
549 -)))
550 550  
551 -[[image:1653272787040-634.png||height="515" width="719"]]
510 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
552 552  
553 -(((
554 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
555 -)))
556 556  
557 -(((
558 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
559 -)))
560 560  
561 -(((
514 +**Examples: AT+DATAUP=1**
515 +
516 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
517 +
562 562  Final Payload is
563 -)))
564 564  
565 -(((
566 -(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
567 -)))
520 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
568 568  
569 -1. (((
570 -Battery Info (2 bytes): Battery voltage
571 -)))
572 -1. (((
573 -PAYVER (1 byte): Defined by AT+PAYVER
574 -)))
575 -1. (((
576 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
577 -)))
578 -1. (((
579 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
580 -)))
581 -1. (((
582 -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
583 -)))
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
584 584  
585 -[[image:1653272817147-600.png||height="437" width="717"]]
528 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
586 586  
530 +
587 587  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
588 588  
589 -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
590 590  
591 -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
592 592  
593 -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
594 594  
539 +
540 +
595 595  Below are the uplink payloads:
596 596  
597 -[[image:1653272901032-107.png]]
543 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
598 598  
599 -(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
600 600  
546 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
547 +
601 601   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
602 602  
603 603   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
... ... @@ -606,121 +606,90 @@
606 606  
607 607   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
608 608  
609 -=== 3.3.5 Uplink on demand ===
610 610  
611 -(((
557 +
558 +1.
559 +11.
560 +111. Uplink on demand
561 +
612 612  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.
613 -)))
614 614  
615 -(((
616 616  Downlink control command:
617 -)))
618 618  
619 -(((
620 -**0x08 command**: Poll an uplink with current command set in RS485-BL.
621 -)))
566 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
622 622  
623 -(((
624 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
625 -)))
568 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
626 626  
627 -=== 3.3.6 Uplink on Interrupt ===
628 628  
629 -Put the interrupt sensor between 3.3v_out and GPIO ext.
630 630  
631 -[[image:1653273818896-432.png]]
572 +1.
573 +11.
574 +111. Uplink on Interrupt
632 632  
633 -(((
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 +
634 634  AT+INTMOD=0  Disable Interrupt
635 -)))
636 636  
637 -(((
638 638  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
639 -)))
640 640  
641 -(((
642 642  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
643 -)))
644 644  
645 -(((
646 646  AT+INTMOD=3  Interrupt trigger by rising edge.
647 -)))
648 648  
649 -== 3.4 Uplink Payload ==
650 650  
651 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
652 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
653 -|Value|(% style="width:130px" %)(((
654 -(((
587 +1.
588 +11. Uplink Payload
589 +
590 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
591 +|Value|(((
655 655  Battery(mV)
656 -)))
657 657  
658 -(((
659 659  &
660 -)))
661 661  
662 -(((
663 663  Interrupt _Flag
664 -)))
665 -)))|(% style="width:93px" %)(((
597 +)))|(((
666 666  PAYLOAD_VER
667 667  
668 668  
669 -)))|(% 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.
670 670  
671 671  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
672 672  
673 -(((
605 +
674 674  function Decoder(bytes, port) {
675 -)))
676 676  
677 -(((
678 678  ~/~/Payload Formats of RS485-BL Deceive
679 -)))
680 680  
681 -(((
682 682  return {
683 -)))
684 684  
685 -(((
686 686   ~/~/Battery,units:V
687 -)))
688 688  
689 -(((
690 690   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
691 -)))
692 692  
693 -(((
694 694   ~/~/GPIO_EXTI 
695 -)))
696 696  
697 -(((
698 698   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
699 -)))
700 700  
701 -(((
702 702   ~/~/payload of version
703 -)))
704 704  
705 -(((
706 706   Pay_ver:bytes[2],
707 -)))
708 708  
709 -(((
710 710   };
711 -)))
712 712  
713 -(((
714 714   }
715 -)))
716 716  
717 -(((
628 +
629 +
630 +
631 +
632 +
633 +
718 718  TTN V3 uplink screen shot.
719 -)))
720 720  
721 -[[image:1653274001211-372.png||height="192" width="732"]]
636 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
722 722  
723 -== 3.5 Configure RS485-BL via AT or Downlink ==
638 +1.
639 +11. Configure RS485-BL via AT or Downlink
724 724  
725 725  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
726 726  
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