Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 18.1
edited by Xiaoling
on 2022/05/23 09:57
Change comment: Uploaded new attachment "1653271044481-711.png", version {1}
To version 29.39
edited by Xiaoling
on 2022/06/02 09:02
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 ==
... ... @@ -22,19 +22,19 @@
22 22  )))
23 23  
24 24  (((
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.
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.
26 26  )))
27 27  
28 28  (((
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.
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.
30 30  )))
31 31  
32 32  (((
33 -RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years.
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.
34 34  )))
35 35  
36 36  (((
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.
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.
38 38  )))
39 39  
40 40  (((
... ... @@ -51,8 +51,11 @@
51 51  
52 52  [[image:1652953304999-717.png||height="424" width="733"]]
53 53  
57 +
58 +
54 54  == 1.2 Specifications ==
55 55  
61 +
56 56  **Hardware System:**
57 57  
58 58  * STM32L072CZT6 MCU
... ... @@ -59,8 +59,6 @@
59 59  * SX1276/78 Wireless Chip 
60 60  * Power Consumption (exclude RS485 device):
61 61  ** Idle: 6uA@3.3v
62 -
63 -*
64 64  ** 20dB Transmit: 130mA@3.3v
65 65  
66 66  **Interface for Model:**
... ... @@ -114,9 +114,12 @@
114 114  
115 115  [[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);"]]
116 116  
121 +
117 117  == 1.6 Hardware Change log ==
118 118  
119 119  (((
125 +
126 +
120 120  v1.4
121 121  )))
122 122  
... ... @@ -140,6 +140,8 @@
140 140  
141 141  (((
142 142  Release version ​​​​​
150 +
151 +
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  
165 +
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.
172 +
173 +
162 162  )))
163 163  
164 164  == 3.2 Example to join LoRaWAN network ==
... ... @@ -194,8 +194,6 @@
194 194  )))
195 195  
196 196  
197 -
198 -
199 199  [[image:image-20220519174512-1.png]]
200 200  
201 201  [[image:image-20220519174512-2.png||height="328" width="731"]]
... ... @@ -219,10 +219,13 @@
219 219  
220 220  [[image:1652953568895-172.png||height="232" width="724"]]
221 221  
232 +
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.
236 +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.
237 +
238 +
226 226  )))
227 227  
228 228  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
... ... @@ -303,6 +303,7 @@
303 303  )))
304 304  )))
305 305  
319 +
306 306  === 3.3.2 Configure sensors ===
307 307  
308 308  (((
... ... @@ -323,8 +323,9 @@
323 323  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
324 324  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
325 325  
326 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
340 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
327 327  
342 +
328 328  === 3.3.3 Configure read commands for each sampling ===
329 329  
330 330  (((
... ... @@ -397,8 +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 -(% border="1" class="table-bordered" %)
401 -|(((
415 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
416 +|(% style="width:498px" %)(((
402 402  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
403 403  
404 404  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -412,39 +412,36 @@
412 412  
413 413  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
414 414  
415 -(% border="1" class="table-bordered" %)
416 -|(((
430 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
431 +|(% style="width:577px" %)(((
417 417  **AT+SEARCHx=aa,xx xx xx xx xx**
418 418  
419 419  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
420 420  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
421 -
422 -
423 423  )))
424 424  
425 -Examples:
438 +**Examples:**
426 426  
427 -1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
440 +1）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
428 428  
429 429  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
430 430  
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
444 +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**
432 432  
433 -[[image:1652954654347-831.png]]
446 +[[image:1653271044481-711.png]]
434 434  
448 +2）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 -1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
437 -
438 438  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
439 439  
440 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
452 +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**
441 441  
442 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
454 +[[image:1653271276735-972.png]]
443 443  
444 -
445 445  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
446 446  
447 -|(((
458 +(% style="background-color:#4f81bd; color:white; width:729px" %)
459 +|(% style="width:726px" %)(((
448 448  **AT+DATACUTx=a,b,c**
449 449  
450 450  * **a: length for the return of AT+COMMAND**
... ... @@ -452,98 +452,143 @@
452 452  * **c: define the position for valid value.  **
453 453  )))
454 454  
455 -Examples:
467 +**Examples:**
456 456  
457 457  * Grab bytes:
458 458  
459 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
471 +[[image:1653271581490-837.png||height="313" width="722"]]
460 460  
473 +
461 461  * Grab a section.
462 462  
463 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
476 +[[image:1653271648378-342.png||height="326" width="720"]]
464 464  
478 +
465 465  * Grab different sections.
466 466  
467 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
481 +[[image:1653271657255-576.png||height="305" width="730"]]
468 468  
483 +(((
484 +(% style="color:red" %)**Note:**
485 +)))
469 469  
470 -Note:
471 -
487 +(((
472 472  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.
489 +)))
473 473  
474 -Example:
491 +(((
492 +**Example:**
493 +)))
475 475  
476 -AT+COMMAND1=11 01 1E D0,0
495 +(((
496 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
497 +)))
477 477  
478 -AT+SEARCH1=1,1E 56 34
499 +(((
500 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
501 +)))
479 479  
480 -AT+DATACUT1=0,2,1~~5
503 +(((
504 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
505 +)))
481 481  
482 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
507 +(((
508 +(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
509 +)))
483 483  
484 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
511 +(((
512 +(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
513 +)))
485 485  
486 -Valid payload after DataCUT command: 2e 30 58 5f 36
515 +(((
516 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
517 +)))
487 487  
488 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
519 +[[image:1653271763403-806.png]]
489 489  
490 490  
522 +=== 3.3.4 Compose the uplink payload ===
491 491  
492 -
493 -1.
494 -11.
495 -111. Compose the uplink payload
496 -
524 +(((
497 497  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.**
526 +)))
498 498  
528 +(((
529 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
530 +)))
499 499  
500 -**Examples: AT+DATAUP=0**
532 +(((
533 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
534 +)))
501 501  
502 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
503 -
536 +(((
504 504  Final Payload is
538 +)))
505 505  
506 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
540 +(((
541 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
542 +)))
507 507  
544 +(((
508 508  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
546 +)))
509 509  
510 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
548 +[[image:1653272787040-634.png||height="515" width="719"]]
511 511  
512 512  
513 513  
514 -**Examples: AT+DATAUP=1**
552 +(((
553 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
515 515  
516 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
555 +
556 +)))
517 517  
558 +(((
559 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
560 +)))
561 +
562 +(((
518 518  Final Payload is
564 +)))
519 519  
520 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
566 +(((
567 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
568 +)))
521 521  
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
570 +1. (((
571 +Battery Info (2 bytes): Battery voltage
572 +)))
573 +1. (((
574 +PAYVER (1 byte): Defined by AT+PAYVER
575 +)))
576 +1. (((
577 +PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
578 +)))
579 +1. (((
580 +PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
581 +)))
582 +1. (((
583 +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
584 +)))
527 527  
528 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
586 +[[image:1653272817147-600.png||height="437" width="717"]]
529 529  
530 -
531 531  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
532 532  
533 -DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
534 534  
535 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
591 +DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
536 536  
537 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
593 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
538 538  
595 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
539 539  
540 540  
541 541  Below are the uplink payloads:
542 542  
543 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
600 +[[image:1653272901032-107.png]]
544 544  
545 545  
546 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
603 +(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
547 547  
548 548   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
549 549  
... ... @@ -555,89 +555,130 @@
555 555  
556 556  
557 557  
558 -1.
559 -11.
560 -111. Uplink on demand
615 +=== 3.3.5 Uplink on demand ===
561 561  
617 +(((
562 562  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.
619 +)))
563 563  
621 +(((
564 564  Downlink control command:
623 +)))
565 565  
566 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
625 +(((
626 +**0x08 command**: Poll an uplink with current command set in RS485-BL.
627 +)))
567 567  
568 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
629 +(((
630 +**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
569 569  
632 +
633 +)))
570 570  
635 +=== 3.3.6 Uplink on Interrupt ===
571 571  
572 -1.
573 -11.
574 -111. Uplink on Interrupt
637 +Put the interrupt sensor between 3.3v_out and GPIO ext.
575 575  
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]]
639 +[[image:1653273818896-432.png]]
577 577  
641 +
642 +(((
578 578  AT+INTMOD=0  Disable Interrupt
644 +)))
579 579  
646 +(((
580 580  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
648 +)))
581 581  
650 +(((
582 582  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
652 +)))
583 583  
654 +(((
584 584  AT+INTMOD=3  Interrupt trigger by rising edge.
585 585  
657 +
658 +)))
586 586  
587 -1.
588 -11. Uplink Payload
660 +== 3.4 Uplink Payload ==
589 589  
590 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
591 -|Value|(((
662 +(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
663 +|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
664 +|Value|(% style="width:130px" %)(((
665 +(((
592 592  Battery(mV)
667 +)))
593 593  
669 +(((
594 594  &
671 +)))
595 595  
673 +(((
596 596  Interrupt _Flag
597 -)))|(((
675 +)))
676 +)))|(% style="width:93px" %)(((
598 598  PAYLOAD_VER
599 599  
600 600  
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.
680 +)))|(% 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.
602 602  
603 603  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
604 604  
684 +(((
685 +{{{function Decoder(bytes, port) {}}}
686 +)))
605 605  
606 -function Decoder(bytes, port) {
688 +(((
689 +{{{//Payload Formats of RS485-BL Deceive}}}
690 +)))
607 607  
608 -~/~/Payload Formats of RS485-BL Deceive
692 +(((
693 +{{{return {}}}
694 +)))
609 609  
610 -return {
696 +(((
697 +{{{ //Battery,units:V}}}
698 +)))
611 611  
612 - ~/~/Battery,units:V
700 +(((
701 +{{{ BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,}}}
702 +)))
613 613  
614 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
704 +(((
705 +{{{ //GPIO_EXTI }}}
706 +)))
615 615  
616 - ~/~/GPIO_EXTI 
708 +(((
709 +{{{ EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",}}}
710 +)))
617 617  
618 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
712 +(((
713 +{{{ //payload of version}}}
714 +)))
619 619  
620 - ~/~/payload of version
716 +(((
717 +{{{ Pay_ver:bytes[2],}}}
718 +)))
621 621  
622 - Pay_ver:bytes[2],
720 +(((
721 +{{{ }; }}}
722 +)))
623 623  
624 - };
724 +(((
725 +{{{ }}}}
625 625  
626 - }
727 +
728 +)))
627 627  
628 -
629 -
630 -
631 -
632 -
633 -
730 +(((
634 634  TTN V3 uplink screen shot.
732 +)))
635 635  
636 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
734 +[[image:1653274001211-372.png||height="192" width="732"]]
637 637  
638 -1.
639 -11. Configure RS485-BL via AT or Downlink
640 640  
737 +== 3.5 Configure RS485-BL via AT or Downlink ==
738 +
641 641  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
642 642  
643 643  There are two kinds of Commands:
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