Last modified by Xiaoling on 2023/04/20 18:14
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 10 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,14 +1,16 @@ 1 - 1 +**Table of Contents:** 2 2 3 3 {{toc/}} 4 4 5 5 6 + 6 6 = 1. Introduction = 7 7 9 + 8 8 The Dragino LoRaWAN gateway can commuicate with LoRaWAN ABP End Node without the need of LoRaWAN server. It can be used in some cases such as: 9 9 10 10 * No internet connection. 11 -* User wants to get data forward in gateway and forward to their server base on MQTT/HTTP, etc. (Combine ABP communication method and [[MQTT forward together>> url:https://wiki.dragino.com/index.php/MQTT_Forward_Instruction]]).13 +* User wants to get data forward in gateway and forward to their server base on MQTT/HTTP, etc. (Combine ABP communication method and [[MQTT forward together>>MQTT Forward Instruction]]). 12 12 13 13 ((( 14 14 The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements: ... ... @@ -28,18 +28,20 @@ 28 28 29 29 (% class="box infomessage" %) 30 30 ((( 31 -AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df 33 +**AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df 32 32 AT+APPSKEY=b3 17 f8 14 7a 43 27 8a 6a 31 c4 47 3d 55 5d 33 33 -AT+DADDR=2602111D 35 +AT+DADDR=2602111D** 34 34 ))) 35 35 36 36 ((( 37 37 and we have the LG308 works and US915 band and support ABP decryption. User can input these keys in LG308 so the LG308 can communicate with LGT92. 40 + 41 + 38 38 ))) 39 39 40 40 We need to input above keys in LG308 and enable ABP decryption. 41 41 42 -[[image: https://wiki.dragino.com/images/thumb/5/55/LG308_MQTT_1.png/600px-LG308_MQTT_1.png||height="329" width="600"]]46 +[[image:image-20220527161119-1.png]] 43 43 44 44 Input the ABP keys in LG308 45 45 ... ... @@ -46,6 +46,7 @@ 46 46 47 47 == 2.1 Upstream == 48 48 53 + 49 49 Now when this End Node (Dev Addr=2602111D) send a uplink packet. When this packet arrive LG308, LG308 will decode it and put the decode data on the file /var/iot/channels/2602111D . So we have this data for further process with other applications in LG308. 50 50 51 51 ((( ... ... @@ -52,9 +52,9 @@ 52 52 We can see the log of LG308 to know this packet arrive 53 53 ))) 54 54 55 -[[image: https://wiki.dragino.com/images/thumb/1/16/ABP_DECODE_2.png/600px-ABP_DECODE_2.png||height="205" width="600"]]60 +[[image:image-20220527161149-2.png]] 56 56 57 -LG308 log by "logread -f" command 62 +LG308 log by "(% style="color:red" %)**logread -f**" (%%)command 58 58 59 59 60 60 The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it. ... ... @@ -62,19 +62,19 @@ 62 62 (% class="box" %) 63 63 ((( 64 64 root@dragino-1d25dc:~~# hexdump /var/iot/channels/2602111D 65 -0000000 (% class="mark" %)**4646 4646 4646 3946 3030 3030 3030 3546**(%%) ~-~-> Got RSSI and SNR66 -0000010 (% class="mark" %)**cc0c 0b63 0266 017f ff7f ff00 **(%%) ~-~-> Payload70 +0000000 (% style="color:#037691" %)**4646 4646 4646 3946 3030 3030 3030 3546**(%%) ~-~-> Got RSSI and SNR 71 +0000010 (% style="color:#037691" %)**cc0c 0b63 0266 017f ff7f ff00 **(%%) ~-~-> Payload 67 67 000001c 68 68 ))) 69 69 70 -* RSSI: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97 71 -* SNR: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5 72 -* Payload: 0xcc0c 0b63 0266 017f ff7f ff00 75 +* **RSSI**: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97 76 +* **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5 77 +* **Payload**: 0xcc0c 0b63 0266 017f ff7f ff00 73 73 74 74 (% class="box" %) 75 75 ((( 76 -(% class="mark" %)**Notice 1**(%%): The data file stored in LG308 for the end node is bin file. If the end node sends ASCII string to gateway, the output will as below:77 -in LGT92, use **AT+SEND=12 **:hello world to send ASCII string81 +(% style="color:red" %)**Notice 1**(%%): The data file stored in LG308 for the end node is bin file. If the end node sends ASCII string to gateway, the output will as below: 82 +in LGT92, use (% style="color:#037691" %)**AT+SEND=12:hello world** (%%)to send ASCII string 78 78 root@dragino-1d25dc:~~# hexdump /var/iot/channels/2602111D 79 79 0000000 4646 4646 4646 3946 3030 3030 3030 3546 80 80 0000010 6865 6c6c 6f20 776f 726c 6400 ~-~-> Got ASCII code "hello world" ... ... @@ -83,13 +83,15 @@ 83 83 84 84 (% class="box" %) 85 85 ((( 86 -(% class="mark" %)**Notice 2**(%%): The upstream payload length should match the LoRaWAN length requirement (max length depends on Frequency and DR), otherwise the gateway can't decode the payload.91 +(% style="color:red" %)**Notice 2**(%%): The upstream payload length should match the LoRaWAN length requirement (max length depends on Frequency and DR), otherwise the gateway can't decode the payload. 87 87 ))) 88 88 94 + 89 89 === 2.2.1 Decode Method === 90 90 91 -The decode methods: **ASCII String, Decode_LHT65** doesn't affect how the sensor data is stored, they are to define how should the sensor data to be sent. 92 92 98 +The decode methods: (% style="color:#037691" %)**ASCII String, Decode_LHT65**(%%) doesn't affect how the sensor data is stored, they are to define how should the sensor data to be sent. 99 + 93 93 For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are: 94 94 95 95 (% class="box" %) ... ... @@ -100,6 +100,7 @@ 100 100 000001c 101 101 ))) 102 102 110 + 103 103 If we choose ASCII decoder, the MQTT process will send out with mqtt-data: 104 104 105 105 (% class="box" %) ... ... @@ -106,9 +106,10 @@ 106 106 ((( 107 107 Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data 108 108 Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:decoder: ASCII 109 -Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: ffffffe700000048ccd17fff7fff017fff7fff00 117 +Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00** 110 110 ))) 111 111 120 + 112 112 If we choose Decode_LHT65, the MQTT process will send out with mqtt-data 113 113 114 114 (% class="box" %) ... ... @@ -115,28 +115,34 @@ 115 115 ((( 116 116 Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data 117 117 Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:decoder: Dragino_LHT65 118 -Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: {"Hum_SHT":32.7,"BatV":3.281,"TempC_DS":32.9, 119 -"EXT":"Temperature Sensor","RSSI":-24,"TempC_SHT":85.0,"SNR":8.2,"ext_sensor":0} 127 +Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]:** (% style="color:#037691" %){"Hum_SHT":32.7,"BatV":3.281,"TempC_DS":32.9, 128 +"EXT":"Temperature Sensor","RSSI":-24,"TempC_SHT":85.0,"SNR":8.2,"ext_sensor":0}(%%)** 120 120 ))) 121 121 122 122 Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI. 123 123 124 124 134 + 125 125 === 2.2.2 How to Decode My End Node === 126 126 127 -1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI 128 128 129 - 2/Don'tchooseMQTTservice,useLoRaWAN.138 +**1.** Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI 130 130 131 - 3/When your endnodesendamessageto the gateway, there will be a file store in /var/iot/channels.full pathshould be/var/iot/channels/END_NODE_DEV_ADDR140 +**2. **Don't choose MQTT service, use LoRaWAN. 132 132 133 - 4/Use the/etc/lora/decoder/Dragino_LHT65astemplate todecodeyour payload.This scriptiswrittenin Lua language.Usercanmanuallycall thisscript when yousee thedatafilein/var/iot/channelsby running:142 +**3.** When your end node send a message to the gateway, there will be a file store in /var/iot/channels. full path should be /var/iot/channels/END_NODE_DEV_ADDR 134 134 144 +**4.** Use the /etc/lora/decoder/Dragino_LHT65 as template to decode your payload. This script is written in Lua language. User can manually call this script when you see the data file in /var/iot/channels by running: 145 + 135 135 {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR 136 136 }}} 137 137 138 -5 /What you see as output is the MQTT data device will upload, user's end node has different payload compare with LHT65, most properly this file will report with error. User need to modify to match the actual payload.Some notice:149 +**5.** What you see as output is the MQTT data device will upload, user's end node has different payload compare with LHT65, most properly this file will report with error. User need to modify to match the actual payload. 139 139 151 + 152 +(% style="color:red" %) 153 +**Some notice:** 154 + 140 140 * RSSI and SNR are added when gateway receive the packet, so there is always this field. 141 141 * If you rename the file, please make it executable. 142 142 * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]] ... ... @@ -144,43 +144,49 @@ 144 144 * the last line return is what will be used for MQTT 145 145 * User can use other language ,not limited to Lua, just make sure the return is what you want to send. 146 146 162 + 147 147 == 2.2 Downstream == 148 148 165 + 149 149 In LG308, we can create a file in the directory /var/iot/push for downstream purpose. We recommend using each command to generate this file. This file will be used for transmission and auto-deleted after used 150 150 151 151 The file should use below format: 152 152 153 -(% class="mark" %)**dev_addr,imme/time,txt/hex,payload**170 +(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload** 154 154 155 155 Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option 156 156 157 -(% class="mark" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**174 +(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow** 158 158 159 -* dev_addr: Inptu the device address 160 -* imme/time: 176 +* **dev_addr:** Inptu the device address 177 +* **imme/time:** 161 161 ** imme: send downstream immediately,For Class C end node. 162 162 ** time: send downstream after receive device's uplink. For Class A end node 163 -* txt/hex: 180 +* **txt/hex:** 164 164 ** txt: send payload in ASCII 165 165 ** hex: send payload in HEX 166 -* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement. 167 -* txpw: Transmit Power. example: 20 168 -* txbw: bandwidth: 183 +* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement. 184 +* **txpw:** Transmit Power. example: 20 185 +* **txbw:** bandwidth: 169 169 ** 1: 500 kHz 170 170 ** 2: 250 kHz 171 171 ** 3: 125 kHz 172 172 ** 4: 62.5 kHz 173 -* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12 174 -* Frequency: Transmit Frequency: example: 923300000 175 -* rxwindow: transmit on Rx1Window or Rx2Window. 190 +* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12 191 +* **Frequency:** Transmit Frequency: example: 923300000 192 +* **rxwindow:** transmit on Rx1Window or Rx2Window. 176 176 177 -Completely exmaple: 178 178 179 -* Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test 180 -* New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test 181 181 182 -(% class="mark" %)**DownstreamFrequency**196 +(% style="color:blue" %)**Completely exmaple:** 183 183 198 +* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test 199 +* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test 200 + 201 + 202 + 203 +(% style="color:#037691" %)**Downstream Frequency** 204 + 184 184 The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below: 185 185 186 186 * EU868: 869.525Mhz, DR0(SF12BW125) ... ... @@ -192,32 +192,28 @@ 192 192 * IN865: 866.55Mhz, SF10 BW125 193 193 * RU864: 869.1Mhz, SF12 BW125 194 194 195 -(% class="mark" %)**Examples:** 196 196 217 + 218 +(% style="color:#037691" %)**Examples:** 219 + 197 197 (% class="box" %) 198 198 ((( 199 199 we can use echo command to create files in LG308 for downstream. 200 200 root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test 201 -))) 202 202 203 -(% class="box" %) 204 -((( 205 -1) From logread -f of gateway, we can see it has been added as pedning. 225 + 226 +**1)** From logread -f of gateway, we can see it has been added as pedning. 206 206 lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test 207 207 lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90 208 208 lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems). 209 -))) 210 210 211 -(% class="box" %) 212 -((( 213 -2) When there is an upstrea from end node, this downstream will be sent and shows: 231 + 232 +**2)** When there is an upstrea from end node, this downstream will be sent and shows: 214 214 lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000) 215 215 lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17 216 -))) 217 217 218 -(% class="box" %) 219 -((( 220 -3) and the end node will got: 236 + 237 +**3)** and the end node will got: 221 221 [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~** 222 222 [5764827]TX on freq 905300000 Hz at DR 0 223 223 Update Interval: 60000 ms ... ... @@ -228,12 +228,10 @@ 228 228 [5767501]rxDone 229 229 Rssi= -41 230 230 Receive data 231 -2:12345678 ~-~-> Hex 232 -))) 248 +(% style="color:#037691" %)**2:12345678** (%%) ~-~-> Hex 233 233 234 -(% class="box" %) 235 -((( 236 -4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got: 250 + 251 +**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got: 237 237 [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~** 238 238 [5955879]TX on freq 904100000 Hz at DR 0 239 239 Update Interval: 60000 ms ... ... @@ -244,16 +244,18 @@ 244 244 [5958595]rxDone 245 245 Rssi= -37 246 246 Receive data 247 -2:3132333435363738 ~-~-> ASCII string "12345678" 262 +(% style="color:#037691" %)**2:3132333435363738**(%%) ~-~-> ASCII string "12345678" 248 248 ))) 249 249 265 + 250 250 = 3. Example 1: Communicate with LT-22222-L = 251 251 268 + 252 252 Script can be download from: [[Example Script 1>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/customized_script/&file=talk_to_lt-22222-l_v0.1.sh]] 253 253 254 254 (% class="box" %) 255 255 ((( 256 -#!/bin/sh 273 +//#!/bin/sh 257 257 # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server 258 258 # 259 259 # Hardware Prepare: ... ... @@ -286,40 +286,46 @@ 286 286 # Device1: DI1: ON, DI2: ON , DO1: ON, DO2: ON 287 287 # Device2: DI1: OFF, DI2: OFF , DO1: ON, DO2: ON 288 288 # So if a person is in the Device 1 location, he can check if the DO LED match DI LEDs on Device 1 to confirm 289 -# whether the Device 2 has been changed. 306 +# whether the Device 2 has been changed.// 290 290 ))) 291 291 292 -~1. Input keys 293 293 294 - [[image:https://wiki.dragino.com/images/thumb/b/bf/LPS8_LT-22222_1.png/600px-LPS8_LT-22222_1.png||height="335"width="600"]]310 +**~1. Input keys** 295 295 312 +[[image:image-20220527162450-3.png]] 313 + 296 296 Input Keys in LPS8 297 297 298 -2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test. 299 299 300 - 3.ChooseBuilt-in server317 +**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.** 301 301 302 -[[image:https://wiki.dragino.com/images/thumb/d/d7/LPS8_LT-22222_2.png/600px-LPS8_LT-22222_2.png||height="264" width="600"]] 303 303 320 +**3. Choose Built-in server** 321 + 322 +[[image:image-20220527162518-4.png]] 323 + 304 304 Choose Built-in server 305 305 306 -4. Run the script. 307 307 308 - [[image:https://wiki.dragino.com/images/thumb/3/39/LPS8_LT-22222_3.png/600px-LPS8_LT-22222_3.png||height="389"width="600"]]327 +**4. Run the script.** 309 309 329 +[[image:image-20220527162552-5.png]] 330 + 310 310 Run the script 311 311 312 -5. Output: 313 313 314 - [[image:https://wiki.dragino.com/images/thumb/f/fe/LPS8_LT-22222_4.png/600px-LPS8_LT-22222_4.png||height="433" width="600"]]334 +**5. Output:** 315 315 336 +[[image:image-20220527162619-6.png]] 337 + 316 316 Output from LPS8 317 317 318 318 319 319 = 4. Example 2: Communicate to TCP Server = 320 320 321 -[[image:https://wiki.dragino.com/images/thumb/7/75/LPS8_TCP_0.png/600px-LPS8_TCP_0.png||height="370" width="600"]] 322 322 344 +[[image:image-20220527162648-7.png]] 345 + 323 323 Network Structure 324 324 325 325 ... ... @@ -326,34 +326,42 @@ 326 326 Full instruction video inlcude how to write scripts to fit server needed is here: 327 327 328 328 329 -(% class="mark" %)**Video Instruction**: [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]352 +(% style="color:#037691" %)**Video Instruction**(%%): **[[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]** 330 330 331 -(% class="mark" %)**Note: Firmware version must be higher than lgw-5.4.1607519907** 332 332 355 +(% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907** 356 + 357 + 333 333 Assume we already set up ABP keys in the gateway: 334 334 335 -[[image: https://wiki.dragino.com/images/thumb/b/bf/LPS8_LT-22222_1.png/600px-LPS8_LT-22222_1.png||height="335" width="600"]]360 +[[image:image-20220527162852-8.png]] 336 336 337 337 Input Keys in LPS8 338 338 339 -run socket tool in PC 340 340 341 -[[image:https://wiki.dragino.com/images/thumb/4/4b/LPS8_TCP_2.png/600px-LPS8_TCP_2.png||height="212" width="600"]] 342 342 366 +**run socket tool in PC** 367 + 368 +[[image:image-20220527163028-9.png]] 369 + 370 + 343 343 Socket tool 344 344 345 345 346 -Input Server address and port 347 347 348 - [[image:https://wiki.dragino.com/images/thumb/c/c6/LPS8_TCP_3.png/600px-LPS8_TCP_3.png||height="306" width="600"]]375 +**Input Server address and port** 349 349 377 +[[image:image-20220527163106-10.png]] 378 + 350 350 Input Server address and port 351 351 352 352 353 -See value receive in socket tool. : 354 354 355 - [[image:https://wiki.dragino.com/images/thumb/2/20/LPS8_TCP_4.png/600px-LPS8_TCP_4.png||height="219"width="600"]]383 +**See value receive in socket tool:** 356 356 385 +[[image:image-20220527163144-11.png]] 386 + 357 357 value receive in socket tool 358 358 389 + 359 359 If user want to modify the TCP connection method. He can refer: [[https:~~/~~/github.com/dragino/dragino-packages/blob/lg02/haserl-ui/root/usr/bin/tcp_process.sh>>url:https://github.com/dragino/dragino-packages/blob/lg02/haserl-ui/root/usr/bin/tcp_process.sh]]. Same script is on /usr/bin of gateway.
- image-20220527161149-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +103.9 KB - Content
- image-20220527162450-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +125.4 KB - Content
- image-20220527162518-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +72.8 KB - Content
- image-20220527162552-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +33.6 KB - Content
- image-20220527162619-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +41.0 KB - Content
- image-20220527162648-7.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +151.7 KB - Content
- image-20220527162852-8.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +125.6 KB - Content
- image-20220527163028-9.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +32.9 KB - Content
- image-20220527163106-10.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +34.5 KB - Content
- image-20220527163144-11.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +107.7 KB - Content