Last modified by Xiaoling on 2023/04/20 18:14
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 10 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,16 +1,14 @@ 1 -** Table ofContents:**1 + **Contents:** 2 2 3 3 {{toc/}} 4 4 5 5 6 - 7 7 = 1. Introduction = 8 8 9 - 10 10 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: 11 11 12 12 * No internet connection. 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 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]]). 14 14 15 15 ((( 16 16 The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements: ... ... @@ -20,8 +20,6 @@ 20 20 1. LoRaWAN Gateway model: [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] ,[[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]] 21 21 1. Firmware version for below instruction:**[[(% style="color:purple" %)Since LG02_LG08~~-~~-build-v5.4.1593400722-20200629-1120>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]](%%)** 22 22 23 - 24 - 25 25 = 2. How it works = 26 26 27 27 ... ... @@ -32,15 +32,13 @@ 32 32 33 33 (% class="box infomessage" %) 34 34 ((( 35 - **AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df31 +AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df 36 36 AT+APPSKEY=b3 17 f8 14 7a 43 27 8a 6a 31 c4 47 3d 55 5d 33 37 -AT+DADDR=2602111D **33 +AT+DADDR=2602111D 38 38 ))) 39 39 40 40 ((( 41 41 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. 42 - 43 - 44 44 ))) 45 45 46 46 We need to input above keys in LG308 and enable ABP decryption. ... ... @@ -52,7 +52,6 @@ 52 52 53 53 == 2.1 Upstream == 54 54 55 - 56 56 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. 57 57 58 58 ((( ... ... @@ -61,7 +61,7 @@ 61 61 62 62 [[image:image-20220527161149-2.png]] 63 63 64 -LG308 log by " (% style="color:red" %)**logread -f**"(%%)command57 +LG308 log by "logread -f" command 65 65 66 66 67 67 The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it. ... ... @@ -74,16 +74,14 @@ 74 74 000001c 75 75 ))) 76 76 77 -* **RSSI**: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -9778 -* **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.579 -* **Payload**: 0xcc0c 0b63 0266 017f ff7f ff0070 +* 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 80 80 81 - 82 - 83 83 (% class="box" %) 84 84 ((( 85 85 (% 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: 86 -in LGT92, use (% style="color:#037691" %) **AT+SEND=12:hello world** (%%)to send ASCII string77 +in LGT92, use **(% style="color:#037691" %)AT+SEND=12:hello world** (%%)to send ASCII string 87 87 root@dragino-1d25dc:~~# hexdump /var/iot/channels/2602111D 88 88 0000000 4646 4646 4646 3946 3030 3030 3030 3546 89 89 0000010 6865 6c6c 6f20 776f 726c 6400 ~-~-> Got ASCII code "hello world" ... ... @@ -92,15 +92,13 @@ 92 92 93 93 (% class="box" %) 94 94 ((( 95 -(% 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.86 +(% style="color:#037691" %)**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. 96 96 ))) 97 97 98 - 99 99 === 2.2.1 Decode Method === 100 100 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. 101 101 102 -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. 103 - 104 104 For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are: 105 105 106 106 (% class="box" %) ... ... @@ -111,7 +111,6 @@ 111 111 000001c 112 112 ))) 113 113 114 - 115 115 If we choose ASCII decoder, the MQTT process will send out with mqtt-data: 116 116 117 117 (% class="box" %) ... ... @@ -118,10 +118,9 @@ 118 118 ((( 119 119 Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data 120 120 Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:decoder: ASCII 121 -Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00**109 +Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: ffffffe700000048ccd17fff7fff017fff7fff00 122 122 ))) 123 123 124 - 125 125 If we choose Decode_LHT65, the MQTT process will send out with mqtt-data 126 126 127 127 (% class="box" %) ... ... @@ -128,34 +128,28 @@ 128 128 ((( 129 129 Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data 130 130 Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:decoder: Dragino_LHT65 131 -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,132 -"EXT":"Temperature Sensor","RSSI":-24,"TempC_SHT":85.0,"SNR":8.2,"ext_sensor":0} (%%)**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} 133 133 ))) 134 134 135 135 Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI. 136 136 137 137 138 - 139 139 === 2.2.2 How to Decode My End Node === 140 140 127 +1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI 141 141 142 - **1.**ConfiguretheABP keys for yourendnodein thegateway.enable ABP decode inWeb UI129 +2/ Don't choose MQTT service, use LoRaWAN. 143 143 144 - **2.**Don'tchooseMQTTservice,useLoRaWAN.131 +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 145 145 146 - **3.**Whenyourendnodesendamessage tothegateway,therewill beafilestore in/var/iot/channels.fullpath shouldbe /var/iot/channels/END_NODE_DEV_ADDR133 +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: 147 147 148 -**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: 149 - 150 150 {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR 151 151 }}} 152 152 153 - **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.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: 154 154 155 - 156 -(% style="color:red" %) 157 -**Some notice:** 158 - 159 159 * RSSI and SNR are added when gateway receive the packet, so there is always this field. 160 160 * If you rename the file, please make it executable. 161 161 * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]] ... ... @@ -163,53 +163,43 @@ 163 163 * the last line return is what will be used for MQTT 164 164 * User can use other language ,not limited to Lua, just make sure the return is what you want to send. 165 165 166 - 167 - 168 - 169 169 == 2.2 Downstream == 170 170 171 - 172 172 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 173 173 174 174 The file should use below format: 175 175 176 -(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload**153 +(% class="mark" %)**dev_addr,imme/time,txt/hex,payload** 177 177 178 178 Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option 179 179 180 -(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**157 +(% class="mark" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow** 181 181 182 -* **dev_addr:**Inptu the device address183 -* **imme/time:**159 +* dev_addr: Inptu the device address 160 +* imme/time: 184 184 ** imme: send downstream immediately,For Class C end node. 185 185 ** time: send downstream after receive device's uplink. For Class A end node 186 -* **txt/hex:**163 +* txt/hex: 187 187 ** txt: send payload in ASCII 188 188 ** hex: send payload in HEX 189 -* **payload:**payload to be sent, payload lenght should match the LoRaWAN protocol requirement.190 -* **txpw:**Transmit Power. example: 20191 -* **txbw:**bandwidth:166 +* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement. 167 +* txpw: Transmit Power. example: 20 168 +* txbw: bandwidth: 192 192 ** 1: 500 kHz 193 193 ** 2: 250 kHz 194 194 ** 3: 125 kHz 195 195 ** 4: 62.5 kHz 196 -* **SF:**Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12197 -* **Frequency:**Transmit Frequency: example: 923300000198 -* **rxwindow:**transmit on Rx1Window or Rx2Window.173 +* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12 174 +* Frequency: Transmit Frequency: example: 923300000 175 +* rxwindow: transmit on Rx1Window or Rx2Window. 199 199 177 +Completely exmaple: 200 200 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 201 201 182 +(% class="mark" %)**Downstream Frequency** 202 202 203 -(% style="color:blue" %)**Completely exmaple:** 204 - 205 -* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test 206 -* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test 207 - 208 - 209 - 210 - 211 -(% style="color:#037691" %)**Downstream Frequency** 212 - 213 213 The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below: 214 214 215 215 * EU868: 869.525Mhz, DR0(SF12BW125) ... ... @@ -221,29 +221,32 @@ 221 221 * IN865: 866.55Mhz, SF10 BW125 222 222 * RU864: 869.1Mhz, SF12 BW125 223 223 195 +(% class="mark" %)**Examples:** 224 224 225 - 226 - 227 -(% style="color:#037691" %)**Examples:** 228 - 229 229 (% class="box" %) 230 230 ((( 231 231 we can use echo command to create files in LG308 for downstream. 232 232 root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test 201 +))) 233 233 234 - 235 -**1)** From logread -f of gateway, we can see it has been added as pedning. 203 +(% class="box" %) 204 +((( 205 +1) From logread -f of gateway, we can see it has been added as pedning. 236 236 lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test 237 237 lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90 238 238 lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems). 209 +))) 239 239 240 - 241 -**2)** When there is an upstrea from end node, this downstream will be sent and shows: 211 +(% class="box" %) 212 +((( 213 +2) When there is an upstrea from end node, this downstream will be sent and shows: 242 242 lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000) 243 243 lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17 216 +))) 244 244 245 - 246 -**3)** and the end node will got: 218 +(% class="box" %) 219 +((( 220 +3) and the end node will got: 247 247 [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~** 248 248 [5764827]TX on freq 905300000 Hz at DR 0 249 249 Update Interval: 60000 ms ... ... @@ -254,10 +254,12 @@ 254 254 [5767501]rxDone 255 255 Rssi= -41 256 256 Receive data 257 -(% style="color:#037691" %)**2:12345678** (%%) ~-~-> Hex 231 +2:12345678 ~-~-> Hex 232 +))) 258 258 259 - 260 -**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got: 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: 261 261 [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~** 262 262 [5955879]TX on freq 904100000 Hz at DR 0 263 263 Update Interval: 60000 ms ... ... @@ -268,18 +268,16 @@ 268 268 [5958595]rxDone 269 269 Rssi= -37 270 270 Receive data 271 - (% style="color:#037691" %)**2:3132333435363738**(%%)~-~-> ASCII string "12345678"247 +2:3132333435363738 ~-~-> ASCII string "12345678" 272 272 ))) 273 273 274 - 275 275 = 3. Example 1: Communicate with LT-22222-L = 276 276 277 - 278 278 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]] 279 279 280 280 (% class="box" %) 281 281 ((( 282 - //#!/bin/sh256 +#!/bin/sh 283 283 # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server 284 284 # 285 285 # Hardware Prepare: ... ... @@ -312,46 +312,40 @@ 312 312 # Device1: DI1: ON, DI2: ON , DO1: ON, DO2: ON 313 313 # Device2: DI1: OFF, DI2: OFF , DO1: ON, DO2: ON 314 314 # 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 315 -# whether the Device 2 has been changed. //289 +# whether the Device 2 has been changed. 316 316 ))) 317 317 292 +~1. Input keys 318 318 319 - **~1.Inputkeys**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"]] 320 320 321 -[[image:image-20220527162450-3.png]] 322 - 323 323 Input Keys in LPS8 324 324 298 +2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test. 325 325 326 - **2.Make sure the LPS8 and LT use the same frequency bands, chooseEU868inthistest.**300 +3. Choose Built-in server 327 327 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"]] 328 328 329 -**3. Choose Built-in server** 330 - 331 -[[image:image-20220527162518-4.png]] 332 - 333 333 Choose Built-in server 334 334 306 +4. Run the script. 335 335 336 - **4.Runscript.**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"]] 337 337 338 -[[image:image-20220527162552-5.png]] 339 - 340 340 Run the script 341 341 312 +5. Output: 342 342 343 - **5. Output:**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"]] 344 344 345 -[[image:image-20220527162619-6.png]] 346 - 347 347 Output from LPS8 348 348 349 349 350 350 = 4. Example 2: Communicate to TCP Server = 351 351 321 +[[image:https://wiki.dragino.com/images/thumb/7/75/LPS8_TCP_0.png/600px-LPS8_TCP_0.png||height="370" width="600"]] 352 352 353 -[[image:image-20220527162648-7.png]] 354 - 355 355 Network Structure 356 356 357 357 ... ... @@ -358,42 +358,34 @@ 358 358 Full instruction video inlcude how to write scripts to fit server needed is here: 359 359 360 360 361 -(% style="color:#037691" %)**Video Instruction**(%%):**[[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]**329 +(% class="mark" %)**Video Instruction**: [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]] 362 362 331 +(% class="mark" %)**Note: Firmware version must be higher than lgw-5.4.1607519907** 363 363 364 -(% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907** 365 - 366 - 367 367 Assume we already set up ABP keys in the gateway: 368 368 369 -[[image:image-2 0220527162852-8.png]]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"]] 370 370 371 371 Input Keys in LPS8 372 372 339 +run socket tool in PC 373 373 341 +[[image:https://wiki.dragino.com/images/thumb/4/4b/LPS8_TCP_2.png/600px-LPS8_TCP_2.png||height="212" width="600"]] 374 374 375 -**run socket tool in PC** 376 - 377 -[[image:image-20220527163028-9.png]] 378 - 379 - 380 380 Socket tool 381 381 382 382 346 +Input Server address and port 383 383 384 - **Input Serveraddress andport**348 +[[image:https://wiki.dragino.com/images/thumb/c/c6/LPS8_TCP_3.png/600px-LPS8_TCP_3.png||height="306" width="600"]] 385 385 386 -[[image:image-20220527163106-10.png]] 387 - 388 388 Input Server address and port 389 389 390 390 353 +See value receive in socket tool. : 391 391 392 - **See valuereceiveinsocket tool:**355 +[[image:https://wiki.dragino.com/images/thumb/2/20/LPS8_TCP_4.png/600px-LPS8_TCP_4.png||height="219" width="600"]] 393 393 394 -[[image:image-20220527163144-11.png]] 395 - 396 396 value receive in socket tool 397 397 398 - 399 399 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-20220527162450-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -125.4 KB - Content
- image-20220527162518-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -72.8 KB - Content
- image-20220527162552-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -33.6 KB - Content
- image-20220527162619-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -41.0 KB - Content
- image-20220527162648-7.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -151.7 KB - Content
- image-20220527162852-8.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -125.6 KB - Content
- image-20220527163028-9.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -32.9 KB - Content
- image-20220527163106-10.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -34.5 KB - Content
- image-20220527163144-11.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -107.7 KB - Content
- image-20220722115133-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -35.1 KB - Content