Changes for page RS485-BL – Waterproof RS485 to LoRaWAN Converter

Last modified by Xiaoling on 2025/04/23 15:57

From 15.4 to 15.3 From 29.13 to 29.12

From version 29.12

edited by Xiaoling
on 2022/06/01 18:02

Change comment: There is no comment for this version

To version 15.4

edited by Xiaoling
on 2022/05/19 17:48

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 12 removed)

Details

Page properties

Content

@@ -7,15 +7,12 @@
  **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
--
  **Table of Contents:**
--{{toc/}}
--
  = 1.Introduction =
  == 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
@@ -104,8 +104,6 @@
  * Support Modbus protocol
  * Support Interrupt uplink
--
--
  == 1.4 Applications ==
  * Smart Buildings & Home Automation
@@ -115,13 +115,10 @@
  * Smart Cities
  * Smart Factory
--
--
  == 1.5 Firmware Change log ==
  [[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);"]]
--
  == 1.6 Hardware Change log ==
  (((
@@ -148,8 +148,6 @@
  (((
  Release version
--
--
  )))
  = 2. Pin mapping and Power ON Device =
@@ -163,7 +163,6 @@
  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
--
  = 3. Operation Mode =
  == 3.1 How it works? ==
@@ -170,8 +170,6 @@
  (((
  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.
--
--
  )))
  == 3.2 Example to join LoRaWAN network ==
@@ -232,188 +232,143 @@
  [[image:1652953568895-172.png||height="232" width="724"]]
--== 3.3 Configure Commands to read data ==
--(((
--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.
--
--)))
--=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
++1.
++11. Configure Commands to read data
++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.
++
++
++1.
++11.
++111. Configure UART settings for RS485 or TTL communication
++
  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
--**~1. RS485-MODBUS mode:**
++1. RS485-MODBUS mode:
  AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
--**2. TTL mode:**
++1. TTL mode:
++
  AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
++
  RS485-BL default UART settings is **9600, no parity, stop bit 1**. If the sensor has a different settings, user can change the RS485-BL setting to match.
--(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
--|(((
--**AT Commands**
--)))|(% style="width:285px" %)(((
--**Description**
--)))|(% style="width:347px" %)(((
--**Example**
--)))
--|(((
--AT+BAUDR
--)))|(% style="width:285px" %)(((
--Set the baud rate (for RS485 connection). Default Value is: 9600.
--)))|(% style="width:347px" %)(((
--(((
++
++|**AT Commands**|**Description**|**Example**
++|AT+BAUDR|Set the baud rate (for RS485 connection). Default Value is: 9600.|(((
  AT+BAUDR=9600
--)))
--(((
  Options: (1200,2400,4800,14400,19200,115200)
  )))
--)))
--|(((
--AT+PARITY
--)))|(% style="width:285px" %)(((
--(((
++|AT+PARITY|(((
  Set UART parity (for RS485 connection)
--)))
--(((
  Default Value is: no parity.
--)))
--)))|(% style="width:347px" %)(((
--(((
++)))|(((
  AT+PARITY=0
--)))
--(((
  Option: 0: no parity, 1: odd parity, 2: even parity
  )))
--)))
--|(((
--AT+STOPBIT
--)))|(% style="width:285px" %)(((
--(((
++|AT+STOPBIT|(((
  Set serial stopbit (for RS485 connection)
--)))
--(((
  Default Value is: 1bit.
--)))
--)))|(% style="width:347px" %)(((
--(((
++)))|(((
  AT+STOPBIT=0 for 1bit
--)))
--(((
  AT+STOPBIT=1 for 1.5 bit
--)))
--(((
  AT+STOPBIT=2 for 2 bits
  )))
--)))
--=== 3.3.2 Configure sensors ===
--(((
--Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**.
--)))
--(((
--When user issue an (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) command, Each (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling.
--)))
--(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
--|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
--|AT+CFGDEV|(% style="width:418px" %)(((
++1.
++11.
++111. Configure sensors
++
++Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands AT+CFGDEV.
++
++
++When user issue an AT+CFGDEV command, Each AT+CFGDEV equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling.
++
++|**AT Commands**|**Description**|**Example**
++|AT+CFGDEV|(((
  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
--AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
++AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
--mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
--)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
++m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
++)))|AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
  Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
--=== 3.3.3 Configure read commands for each sampling ===
--(((
++
++
++
++1.
++11.
++111. Configure read commands for each sampling
++
  RS485-BL is a battery powered device; it will sleep most of time. And wake up on each period and read RS485 / TTL sensor data and uplink.
--)))
--(((
++
  During each sampling, we need to confirm what commands we need to send to the sensors to read data. After the RS485/TTL sensors send back the value, it normally includes some bytes and we only need a few from them for a shorten payload.
--)))
--(((
++
  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
--)))
--(((
++
  This section describes how to achieve above goals.
--)))
--(((
++
  During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
--)))
--(((
++
  **Command from RS485-BL to Sensor:**
--)))
--(((
  RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
--)))
--(((
++
  **Handle return from sensors to RS485-BL**:
--)))
--(((
  After RS485-BL send out a string to sensor, RS485-BL will wait for the return from RS485 or TTL sensor. And user can specify how to handle the return, by **AT+DATACUT or AT+SEARCH commands**
--)))
--* (((
--**AT+DATACUT**
--)))
--(((
++* **AT+DATACUT**
++
  When the return value from sensor have fix length and we know which position the valid value we should get, we can use AT+DATACUT command.
--)))
--* (((
--**AT+SEARCH**
--)))
--(((
++* **AT+SEARCH**
++
  When the return value from sensor is dynamic length and we are not sure which bytes the valid data is, instead, we know what value the valid value following. We can use AT+SEARCH to search the valid value in the return string.
--)))
--(((
++
  **Define wait timeout:**
--)))
--(((
  Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example, AT+CMDDL1=1000 to send the open time to 1000ms
--)))
--(((
++
  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
--)))
++
  **Examples:**
  Below are examples for the how above AT Commands works.
++
  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
--(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
--|(% style="width:498px" %)(((
++|(((
  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
@@ -425,38 +425,41 @@
  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
++
  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
--(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
--|(% style="width:577px" %)(((
++|(((
  **AT+SEARCHx=aa,xx xx xx xx xx**
  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
++
++
  )))
--**Examples:**
++Examples:
 . For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
--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**
++The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
--[[image:1653271044481-711.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
++
 . For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
--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**
++Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
--[[image:1653271276735-972.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
++
  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
--(% style="background-color:#4f81bd; color:white; width:729px" %)
--|(% style="width:726px" %)(((
++|(((
  **AT+DATACUTx=a,b,c**
  * **a: length for the return of AT+COMMAND**
@@ -468,130 +468,95 @@
  * Grab bytes:
--[[image:1653271581490-837.png||height="313" width="722"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
  * Grab a section.
--[[image:1653271648378-342.png||height="326" width="720"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
  * Grab different sections.
--[[image:1653271657255-576.png||height="305" width="730"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
--(((
--(% style="color:red" %)**Note:**
--)))
--(((
++Note:
++
  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.
--)))
--(((
--**Example:**
--)))
++Example:
--(((
--(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
--)))
++AT+COMMAND1=11 01 1E D0,0
--(((
--(% style="color:red" %)AT+SEARCH1=1,1E 56 34
--)))
++AT+SEARCH1=1,1E 56 34
--(((
--(% style="color:red" %)AT+DATACUT1=0,2,1~~5
--)))
++AT+DATACUT1=0,2,1~~5
--(((
--(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
--)))
++Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
--(((
--(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
--)))
++String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
--(((
--(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
--)))
++Valid payload after DataCUT command: 2e 30 58 5f 36
--[[image:1653271763403-806.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
--=== 3.3.4 Compose the uplink payload ===
--(((
++
++
++1.
++11.
++111. Compose the uplink payload
++
  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.**
--)))
--(((
--(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
--)))
--(((
--Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
--)))
++**Examples: AT+DATAUP=0**
--(((
++Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
++
  Final Payload is
--)))
--(((
--(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
--)))
++Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
--(((
  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
--)))
--[[image:1653272787040-634.png||height="515" width="719"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
--(((
--(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
--)))
--(((
--Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
--)))
--(((
++**Examples: AT+DATAUP=1**
++
++Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
++
  Final Payload is
--)))
--(((
--(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
--)))
++Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
--1. (((
--Battery Info (2 bytes): Battery voltage
--)))
--1. (((
--PAYVER (1 byte): Defined by AT+PAYVER
--)))
--1. (((
--PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
--)))
--1. (((
--PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
--)))
--1. (((
--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
--)))
++1. Battery Info (2 bytes): Battery voltage
++1. PAYVER (1 byte): Defined by AT+PAYVER
++1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
++1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
++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
--[[image:1653272817147-600.png||height="437" width="717"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
++
  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
--DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
++DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
--DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
++DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
--DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
++DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
++
++
  Below are the uplink payloads:
--[[image:1653272901032-107.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
--(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
++Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
++
     ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
     * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
@@ -600,121 +600,90 @@
     ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
--=== 3.3.5 Uplink on demand ===
--(((
++
++1.
++11.
++111. Uplink on demand
++
  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.
--)))
--(((
  Downlink control command:
--)))
--(((
--**0x08 command**: Poll an uplink with current command set in RS485-BL.
--)))
++[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
--(((
--**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
--)))
++[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
--=== 3.3.6 Uplink on Interrupt ===
--Put the interrupt sensor between 3.3v_out and GPIO ext.
--[[image:1653273818896-432.png]]
++1.
++11.
++111. Uplink on Interrupt
--(((
++Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
++
  AT+INTMOD=0  Disable Interrupt
--)))
--(((
  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
--)))
--(((
  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
--)))
--(((
  AT+INTMOD=3  Interrupt trigger by rising edge.
--)))
--== 3.4 Uplink Payload ==
--(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
--|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
--|Value|(% style="width:130px" %)(((
--(((
++1.
++11. Uplink Payload
++
++|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
++|Value|(((
  Battery(mV)
--)))
--(((
  &
--)))
--(((
  Interrupt _Flag
--)))
--)))|(% style="width:93px" %)(((
++)))|(((
  PAYLOAD_VER
--)))|(% 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.
++)))|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.
  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
--(((
++
  function Decoder(bytes, port) {
--)))
--(((
  ~/~/Payload Formats of RS485-BL Deceive
--)))
--(((
  return {
--)))
--(((
      ~/~/Battery,units:V
--)))
--(((
      BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
--)))
--(((
      ~/~/GPIO_EXTI
--)))
--(((
      EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
--)))
--(((
      ~/~/payload of version
--)))
--(((
      Pay_ver:bytes[2],
--)))
--(((
      };
--)))
--(((
    }
--)))
--(((
++
++
++
++
++
++
  TTN V3 uplink screen shot.
--)))
--[[image:1653274001211-372.png||height="192" width="732"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
--== 3.5 Configure RS485-BL via AT or Downlink ==
++1.
++11. Configure RS485-BL via AT or Downlink
  User can configure RS485-BL via [[AT Commands >>path:#_Using_the_AT]]or LoRaWAN Downlink Commands

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