Changes for page MQTT Forward Instruction
Last modified by Kilight Cao on 2024/08/31 16:26
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 5 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -7,12 +7,13 @@ 7 7 8 8 Dragino LoRa/LoRaWAN gateway support MQTT forwarding. It can forward the sensor data from LoRa network to MQTT server , and vice verse. 9 9 10 + 10 10 == 1.1 Support Devices == 11 11 12 12 This MQTT forward instruction is for below devices: 13 13 14 14 * Firmware Version > LG02_LG08-5.3.1580178039 [[Firmware Download>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]] 15 -* LG01N, OLG01N ((% class="mark" %)**Warning**(%%): LG01-P LG01-S use another instruction: [[MQTT for LG01-P/LG01S>>url:https://wiki.dragino.com/index.php/Through_MQTT_to_upload_data]])16 +* LG01N, OLG01N ((% style="color:red" %)**Warning**(%%): LG01-P LG01-S use another instruction: [[MQTT for LG01-P/LG01S>>url:https://wiki.dragino.com/index.php/Through_MQTT_to_upload_data]]) 16 16 * LG02, OLG02 17 17 * LG308, DLOS8 18 18 * LPS8 ... ... @@ -19,7 +19,6 @@ 19 19 * LIG16 20 20 * MS14 series if installed with the same firmware. (in this case, the MQTT forward will work , but no LoRa support) 21 21 22 - 23 23 = 2. Firmware Change Log for MQTT feature = 24 24 25 25 ((( ... ... @@ -29,7 +29,6 @@ 29 29 * LG02_LG08-5.3.1580178039 30 30 ** Initiate version 31 31 32 - 33 33 = 3. MQTT forward operating principle = 34 34 35 35 == 3.1 Network Structure == ... ... @@ -39,7 +39,7 @@ 39 39 * For Uplink: The sensor sends data to LoRa Gateway via LoRa wireless, The gateway will process these data and forward to remote MQTT Broker via Internet. 40 40 * For Downlink: The gateway subscribe a topic in the MQTT broker, when there is update on the topic, the gateway will know and broadcast the data to Local LoRa network, 41 41 42 -[[image: https://wiki.dragino.com/images/thumb/4/45/MQTT_Forward_1.png/600px-MQTT_Forward_1.png||height="348" width="600"]]41 +[[image:image-20220527133547-1.png]] 43 43 44 44 General MQTT structure 45 45 ... ... @@ -57,7 +57,7 @@ 57 57 The data flow works as below diagram. 58 58 ))) 59 59 60 -[[ ~[~[image:https://wiki.dragino.com/images/thumb/2/2a/MQTT_Forward_2.png/600px-MQTT_Forward_2.png~|~|height="355" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Forward_2.png]]59 +[[image:image-20220527134000-2.png]] 61 61 62 62 ((( 63 63 Upstream path ... ... @@ -79,7 +79,7 @@ 79 79 Below are the data flow for downstream. 80 80 ))) 81 81 82 -[[image: https://wiki.dragino.com/images/thumb/3/3a/MQTT_Forward_3.png/600px-MQTT_Forward_3.png||height="368" width="600"]]81 +[[image:image-20220527134038-3.png]] 83 83 84 84 Downstream path 85 85 ... ... @@ -89,7 +89,9 @@ 89 89 The MQTT publish command use Macro settings to generate flexible upstream payload for MQTT publish. 90 90 91 91 ((( 92 -Currently the (% class="mark" %)**-t (topic)**(%%) and (% class="mark" %)**-m (message)**(%%) support Macros. 91 +Currently the (% style="color:#4f81bd" %)**-t (topic)**(%%) and (% style="color:#4f81bd" %)**-m (message)**(%%) support Macros. 92 + 93 + 93 93 ))) 94 94 95 95 === 3.3.1 -t topic macro === ... ... @@ -110,7 +110,7 @@ 110 110 111 111 === 3.3.3 Example for Macro === 112 112 113 -[[image: https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]]114 +[[image:image-20220527134251-4.png]] 114 114 115 115 MQTT Publish configure 116 116 ... ... @@ -121,12 +121,12 @@ 121 121 122 122 When there is a LoRa sensor arrive. it will be store at the /var/iot/channels as below: 123 123 124 -[[image: https://wiki.dragino.com/images/thumb/c/c4/MQTT_Command_20.png/600px-MQTT_Command_20.png||height="325" width="600"]]125 +[[image:image-20220527134332-5.png]] 125 125 126 126 Sensor Data 127 127 128 128 ((( 129 -According to above macro. Gateway will publish (% class="mark" %)**field1=22.0&field2=49.0**(%%) to topic: (%class="mark" %)**dragino-1b7060/78901/data**(%%), where 78901 is the remote channel for this node ID.130 +According to above macro. Gateway will publish (% style="color:#4f81bd" %)**field1=22.0&field2=49.0**(%%) to topic: (% style="color:#4f81bd" %)**dragino-1b7060/78901/data**(%%), where 78901 is the remote channel for this node ID. 130 130 ))) 131 131 132 132 ... ... @@ -139,8 +139,7 @@ 139 139 root@dragino-1ec39c:~~# mosquitto_pub ~-~-help 140 140 mosquitto_pub is a simple mqtt client that will publish a message on a single topic and exit. 141 141 mosquitto_pub version 1.6.4 running on libmosquitto 1.6.4. 142 - 143 -Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL} 143 +\\Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL} 144 144 {-f file | -l | -n | -m message} 145 145 [-c] [-k keepalive] [-q qos] [-r] [~-~-repeat N] [~-~-repeat-delay time] 146 146 [-A bind_address] ... ... @@ -158,8 +158,7 @@ 158 158 [~-~-property command identifier value] 159 159 [-D command identifier value] 160 160 mosquitto_pub ~-~-help 161 - 162 --A : bind the outgoing socket to this host/ip address. Use to control which interface 161 +\\-A : bind the outgoing socket to this host/ip address. Use to control which interface 163 163 the client communicates over. 164 164 -d : enable debug messages. 165 165 -D : Define MQTT v5 properties. See the documentation for more details. ... ... @@ -187,7 +187,7 @@ 187 187 ~-~-help : display this message. 188 188 ~-~-repeat : if publish mode is -f, -m, or -s, then repeat the publish N times. 189 189 ~-~-repeat-delay : if using ~-~-repeat, wait time seconds between publishes. Defaults to 0. 190 -~-~-quiet : (% class="mark" %)don't print error messages.189 +~-~-quiet : (% style="color:red" %)don't print error messages. 191 191 ~-~-will-payload : payload for the client Will, which is sent by the broker in case of 192 192 unexpected disconnection. If not given and will-topic is set, a zero 193 193 length message will be sent. ... ... @@ -215,52 +215,46 @@ 215 215 ~-~-proxy : SOCKS5 proxy URL of the form: 216 216 socks5h:~/~/[username[:password]@]hostname[:port] 217 217 Only "none" and "username" authentication is supported. 218 - 219 -See https:~/~/mosquitto.org/ for more information. 217 +\\See https:~/~/mosquitto.org/ for more information. 220 220 ))) 221 221 222 222 221 +((( 223 223 and modify the /usr/bin/mqtt_process.sh script, the location to change the command option is below lines: 223 +))) 224 224 225 225 (% class="box" %) 226 226 ((( 227 -# Call MQTT Publish command 228 - 229 -# 1. Case with User, Password and Client ID present (e.g. Azure) 227 +//# Call MQTT Publish command 228 +\\# 1. Case with User, Password and Client ID present (e.g. Azure) 230 230 if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then 231 231 case="1" 232 232 mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user -P "$pass" $C $cafile $PUB_FLAG "$mqtt_data" 233 - 234 -# 2. Case with Certificate, Key and ClientID present (e.g. AWS) 232 +\\# 2. Case with Certificate, Key and ClientID present (e.g. AWS) 235 235 elif [ ! -z "$certfile" ] && [ ! -z "$key" ] && [ ! -z "$clientID" ]; then 236 236 case="2" 237 237 mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic ~-~-cert $cert ~-~-key $key $C $cafile $PUB_FLAG "$mqtt_data" 238 - 239 -# 3. Case with no User, Certificate or ClientID present 236 +\\# 3. Case with no User, Certificate or ClientID present 240 240 elif [ -z "$user" ] && [ -z "$certfile" ] && [ -z "$clientID" ]; then 241 241 case="3" 242 242 mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data" 243 - 244 -# 4. Case with no User, Certificate, but with ClientID present 240 +\\# 4. Case with no User, Certificate, but with ClientID present 245 245 elif [ -z "$user" ] && [ -z "$certfile" ] && [ ! -z "$clientID" ]; then 246 246 case="4" 247 247 mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data" 248 - 249 -# 5. Case with User and ClientID present, but no Password and no Certificate present 244 +\\# 5. Case with User and ClientID present, but no Password and no Certificate present 250 250 elif [ -z "$pass" ] && [ -z "$certfile" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then 251 251 case="5" 252 252 mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user $PUB_FLAG "$mqtt_data" 253 - 254 -# 6. Case with User and Password present, but no ClientID and no Certificate present 248 +\\# 6. Case with User and Password present, but no ClientID and no Certificate present 255 255 elif [ ! -z "$user" ] && [ ! -z "$pass" ] && [ -z "$clientID" ] && [ -z "$certfile" ]; then 256 256 case="6" 257 257 mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data" 258 - 259 -# 0. Else - invalid parameters, just log 252 +\\# 0. Else - invalid parameters, just log 260 260 else 261 -case="Invalid parameters" 262 -logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called." 263 -fi 254 +case="(% style="color:red" %)Invalid parameters" (%%) 255 +logger (% style="color:red" %)"[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."(%%) 256 +fi// 264 264 ))) 265 265 266 266 ... ... @@ -274,7 +274,9 @@ 274 274 275 275 The [[MQTT.fx>>url:http://mqttfx.jensd.de/index.php/download]] is a MQTT client tool. We can use this to simulate a MQTT connection to our MQTT broker first to make sure the MQTT broker works. This will also help us understand how it works. 276 276 270 +((( 277 277 In this test, the MQTT broker and MQTT.fx are installed in the same PC, so the MQTT server address in MQTT.fx should be localhost. Below shows how to connect to the server. 272 +))) 278 278 279 279 [[image:https://wiki.dragino.com/images/thumb/0/06/MQTT_Forward_4.png/600px-MQTT_Forward_4.png||height="201" width="600"]] 280 280 ... ... @@ -300,7 +300,7 @@ 300 300 In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection. 301 301 302 302 303 -For Upstream 298 +(% class="mark" %)**For Upstream** 304 304 305 305 command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]] 306 306 ... ... @@ -313,7 +313,7 @@ 313 313 mosquitto_pub 314 314 315 315 316 -For Downstream 311 +(% class="mark" %)**For Downstream** 317 317 318 318 Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic. 319 319 ... ... @@ -326,13 +326,17 @@ 326 326 327 327 This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection. 328 328 329 -Go to Dragino Menu ~-~-> MQTT Client 324 +((( 325 +Go to (% class="mark" %)**Dragino Menu ~-~-> MQTT Client** 326 +))) 330 330 331 331 [[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png||height="249" width="600"]] 332 332 333 333 go to mqtt configure menu 334 334 335 -Select Forward to MQTT server. Notice: This option is removed from the latest firmware, in the latest firmware, if user submit "SAVE & APPLY" in MQTT page, the gateway will use MQTT service. 332 +((( 333 +Select **Forward to MQTT server**. (% class="mark" %)**Notice**(%%): This option is removed from the latest firmware, in the latest firmware, if user submit "SAVE & APPLY" in MQTT page, the gateway will use MQTT service. 334 +))) 336 336 337 337 [[image:https://wiki.dragino.com/images/thumb/1/14/MQTT_Commands_8.png/600px-MQTT_Commands_8.png||height="240" width="600"]] 338 338 ... ... @@ -343,30 +343,41 @@ 343 343 344 344 Below screenshot is same as the publish command: 345 345 346 -{{{mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA 347 -//where the CLIENTID, CHANNEL & DATA are macro. represent for 348 -//CLIENTID: dragino-1b7060 349 -//CHANNEL: Remote ID in Channel settings; here is 78901 or 567456 350 -//DATA: The data stores in /var/iot/channels/ 351 -}}} 345 +(% class="box" %) 346 +((( 347 +mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA 348 +~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for 349 +~/~/CLIENTID: dragino-1b7060 350 +~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456 351 +~/~/DATA: The data stores in /var/iot/channels/ 352 +))) 352 352 353 353 [[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]] 354 354 355 355 MQTT Publish configure 356 356 358 + 357 357 [[image:https://wiki.dragino.com/images/thumb/b/b7/MQTT_Command_10.png/600px-MQTT_Command_10.png||height="544" width="600"]] 358 358 359 359 MQTT Channel settings 360 360 363 +((( 361 361 For example, if we put a data(temp=46) on the file /var/iot/channels/4567, because 4567 match the remote channel 78901. the gateway will run this command: 365 +))) 362 362 363 -{{{mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46 364 -}}} 367 +(% class="box" %) 368 +((( 369 +mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46 370 +))) 365 365 372 +((( 366 366 to MQTT broker. 374 +))) 367 367 368 368 377 +((( 369 369 Below is a simulation to put this data to active the MQTT publish. 379 +))) 370 370 371 371 [[image:https://wiki.dragino.com/images/thumb/3/30/MQTT_Command_11.png/600px-MQTT_Command_11.png||height="308" width="600"]] 372 372 ... ... @@ -377,8 +377,10 @@ 377 377 378 378 Below screen shot equal to this subscribe command: 379 379 380 -{{{ mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command. 381 -}}} 390 +(% class="box" %) 391 +((( 392 +mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command. 393 +))) 382 382 383 383 [[image:https://wiki.dragino.com/images/3/36/MQTT_Command_12.png||height="173" width="579"]] 384 384 ... ... @@ -385,7 +385,9 @@ 385 385 MQTT Subscribe 386 386 387 387 400 +((( 388 388 When MQTT broker receive a update on this topic, the gateway will get the update and use LoRa radio to broadcast this message. The LoRa parameters used for update is: 402 +))) 389 389 390 390 [[image:https://wiki.dragino.com/images/thumb/b/b8/MQTT_Command_13.png/600px-MQTT_Command_13.png||height="300" width="600"]] 391 391 ... ... @@ -405,13 +405,21 @@ 405 405 406 406 === 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 === 407 407 422 +((( 408 408 We can use [[LoRa Shield>>url:http://www.dragino.com/products/lora/item/102-lora-shield.html]] to send LoRa Raw data to Gateway and receive data from gateway. 424 +))) 409 409 426 +((( 410 410 The example Sketch for LoRa Shield +Arduino is here: [[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]] 428 +))) 411 411 430 +((( 412 412 And this link is the required library: [[arduino-LoRa-master>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]. Unzip this library and put in Arduino library location. 432 +))) 413 413 434 +((( 414 414 What does the Arduino Sketch do? The Arduino Sketch will: 436 +))) 415 415 416 416 * Upstream: Keep sending a LoRa Message every minutes with this payload : <4567>tem=xx&hum=yy (Where xx and yy are temperature and humidity value generated randomly). 417 417 * Downstream: Listening broadcast message from gateway, and print it in console. ... ... @@ -435,25 +435,33 @@ 435 435 436 436 === 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 === 437 437 438 -Since firmware LG02_LG08~-~-build-v5.3.1585192026-20200326-1109, Dragino LoRaWAN gateways support the communication to LoRaWAN ABP end node locally without the need of LoRaWAN server. This feature allow us to integrate MQTT in the gateway to support LoRaWAN to MQTT forwarding or visa verse. 460 +((( 461 +Since firmware (% class="mark" %)**LG02_LG08~-~-build-v5.3.1585192026-20200326-1109,**(%%) Dragino LoRaWAN gateways support the communication to LoRaWAN (% class="mark" %)**ABP end node**(%%) locally without the need of LoRaWAN server. This feature allow us to integrate MQTT in the gateway to support LoRaWAN to MQTT forwarding or visa verse. 462 +))) 439 439 440 -When use test this feature, please use the version higher then : LG02_LG08~-~-build-v5.4.1593400722-20200629-1120, in this version, the upload format is changed and readable, which is easier for integration. 464 +((( 465 +When use test this feature, please use the version higher then : (% class="mark" %)**LG02_LG08~-~-build-v5.4.1593400722-20200629-1120**(%%), in this version, the upload format is changed and readable, which is easier for integration. 466 +(% class="mark" %)**Video Instruction**(%%):[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]] 467 +))) 441 441 469 +((( 470 +**Step 1**: Refer [[Communicate with ABP End Node>>url:https://wiki.dragino.com/index.php/Communication_with_ABP_End_Node]] to know how to set up LG308 to work with LoRaWAN End node. 471 +))) 442 442 473 +((( 474 +**Step 2**: Make sure your Radio settings match the End Node settings. 475 +))) 443 443 444 -Video Instruction:[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]] 445 - 446 - 447 -Step 1: Refer [[Communicate with ABP End Node>>url:https://wiki.dragino.com/index.php/Communication_with_ABP_End_Node]] to know how to set up LG308 to work with LoRaWAN End node. 448 - 449 -Step 2: Make sure your Radio settings match the End Node settings. 450 - 451 451 [[image:https://wiki.dragino.com/images/thumb/f/f7/LG308_MQTT_5.png/600px-LG308_MQTT_5.png||height="387" width="600"]] 452 452 453 453 Use Same Frequency Band as End Node 454 454 455 455 456 -Step 3: Set up publish format and MQTT channel. The LG308 will store the Data from End node in HEX format in the file. And we need to config the format to META 482 +((( 483 +((( 484 +**Step 3**: Set up publish format and MQTT channel. The LG308 will store the Data from End node in HEX format in the file. And we need to config the format to META 485 +))) 486 +))) 457 457 458 458 [[image:https://wiki.dragino.com/images/thumb/8/8d/LG308_MQTT_3.png/600px-LG308_MQTT_3.png||height="385" width="600"]] 459 459 ... ... @@ -460,7 +460,7 @@ 460 460 Publish mush use META as data format for LG308 461 461 462 462 463 -Step 4: Map the Device Address to Remote ID in MQTT server. 493 +**Step 4**: Map the Device Address to Remote ID in MQTT server. 464 464 465 465 [[image:https://wiki.dragino.com/images/thumb/7/7f/LG308_MQTT_4.png/600px-LG308_MQTT_4.png||height="335" width="600"]] 466 466 ... ... @@ -467,7 +467,7 @@ 467 467 Map Dev Addr to remote ID 468 468 469 469 470 -Step 5: Upstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server 500 +**Step 5: Upstream**: Save the change, we can see the log info via "sytem log", End Node and MQTT Server 471 471 472 472 [[image:https://wiki.dragino.com/images/thumb/b/be/LG308_MQTT_6.png/600px-LG308_MQTT_6.png||height="279" width="600"]] 473 473 ... ... @@ -481,20 +481,21 @@ 481 481 482 482 LHT65 Decoder 483 483 484 -Step 6: Set up subscribe: Subscribe a topci for downstream. 485 485 515 +**Step 6: Set up subscribe:** Subscribe a topci for downstream. 516 + 486 486 [[image:https://wiki.dragino.com/images/thumb/b/b9/LG308_MQTT_7.png/600px-LG308_MQTT_7.png||height="176" width="600"]] 487 487 488 488 Subscribe to a topic 489 489 490 490 491 -Step 7: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server. 522 +**Step 7**: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server. 492 492 493 493 [[image:https://wiki.dragino.com/images/thumb/9/97/LG308_MQTT_8.png/600px-LG308_MQTT_8.png||height="298" width="600"]] 494 494 495 495 Downstream Flow 496 496 497 -Notice: The text use for Downstream must meet the requirement from [[LG308 Downstream Payload>>url:https://wiki.dragino.com/index.php/Communication_with_ABP_End_Node#Downstream]] 528 +(% class="mark" %)**Notice: The text use for Downstream must meet the requirement from [[LG308 Downstream Payload>>url:https://wiki.dragino.com/index.php/Communication_with_ABP_End_Node#Downstream]]** 498 498 499 499 500 500 = 5. Example For Different MQTT Servers = ... ... @@ -510,8 +510,6 @@ 510 510 )))|=(% style="width: 242px;" %)((( 511 511 [[image:https://wiki.dragino.com/images/thumb/3/3b/Lewei50.png/200px-Lewei50.png||alt="Lewei50.png" height="65" width="223"]] 512 512 513 -(% class="wikigeneratedid" %) 514 -== == 515 515 516 516 == [[乐联网平台>>url:https://www.lewei50.com/]] == 517 517
- image-20220527133547-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +199.3 KB - Content
- image-20220527134000-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +115.8 KB - Content
- image-20220527134038-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +94.2 KB - Content
- image-20220527134251-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +35.1 KB - Content
- image-20220527134332-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +34.7 KB - Content