Last modified by Karry Zhuang on 2024/07/11 11:58
<
From version < 57.12 >
edited by Xiaoling
on 2022/07/14 09:48
To version < 21.2 >
edited by Xiaoling
on 2022/05/27 09:34
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,23 +1,14 @@
1 1  (% class="wikigeneratedid" %)
2 -*
3 -** Table of** **Contents:
2 + **Contents:**
4 4  
5 5  {{toc/}}
6 6  
6 += 1. Introduction =
7 7  
8 -
9 -
10 -
11 -
12 -= **1. Introduction** =
13 -
14 -
15 15  This article provide the examples for RS485-LN to connect to different type of RS485 sensors.
16 16  
10 +== 1.1 Example 1: Connect to Leak relay and VFD ==
17 17  
18 -== **1.1 Example 1: Connect to Leak relay and VFD** ==
19 -
20 -
21 21  This instruction is provided by Xavier Florensa Berenguer from [[NORIA GRUPO DE COMPRAS>>url:http://www.gruponovelec.com/]]. It is to show how to use RS485-LN to connect to Relay and VFD and communicate with Mobile. The structure is like below:
22 22  
23 23  [[image:image-20220527091852-1.png]]
... ... @@ -37,33 +37,30 @@
37 37  * [[Configure Manual>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Relay_VFD/]] : Explanation on how to integrate to Node-red and to the Mobile Phone, and with link to the Github code.
38 38  * [[Video Demo>>url:https://www.youtube.com/watch?v=TAFZ5eaf-MY&t=6s&ab_channel=XavierFlorensaBerenguer]]
39 39  
40 -== **1.2 Example 2: Connect to Pulse Counter** ==
31 +== 1.2 Example 2: Connect to Pulse Counter ==
41 41  
42 -
43 43  This instruction is provided by Xavier Florensa Berenguer from [[NORIA GRUPO DE COMPRAS>>url:http://www.gruponovelec.com/]]. It is to show how to use RS485-LN to connect to Pulse Counter and communicate with Mobile. This example and example 2 compose the structure for a farm IoT solution. The structure is like below:
44 44  
45 -
46 46  [[image:image-20220527092058-3.png]]
47 47  
48 48  Connection
49 49  
50 50  
51 -
52 52  [[image:image-20220527092146-4.png]]
53 53  
54 54  Connection
55 55  
56 -
57 -* Configure Document: [[Pickdata MIO40 water pulse counter to LoRa with Dragino RS485-LN>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Pulse-Counter/]]
44 +* [[Pickdata MIO40 water pulse counter to LoRa with Dragino RS485-LN>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Pulse-Counter/]] : Configure Document
58 58  * [[Dragino Solution in Farm>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/&file=Dragino%20on%20Farms.pptx]]
59 59  
60 -== **1.3 Example3: Use RS485-LN with energy meters** ==
47 +== ==
61 61  
62 -=== **1.3.1 OverView** ===
49 +== 1.3 Example3: Use RS485-LN with energy meters ==
63 63  
51 +=== 1.3.1 OverView ===
64 64  
65 65  (((
66 -(% style="color:red" %)**Note**：The specifications of each energy meter are different, please refer to your own energy meter specifications.
54 +**Note**：The specifications of each energy meter are different, please refer to your own energy meter specifications.
67 67  )))
68 68  
69 69  (((
... ... @@ -75,11 +75,8 @@
75 75  Connection1
76 76  
77 77  
78 -
79 79  (((
80 -**How to connect with Energy Meter：**
81 -
82 -
67 +How to connect with Energy Meter：
83 83  )))
84 84  
85 85  (((
... ... @@ -107,21 +107,22 @@
107 107  Connection2
108 108  
109 109  
110 -
111 111  [[image:image-20220527092555-7.png]]
112 112  
113 113  Connection3
114 114  
115 115  
116 -=== **1.3.2 How to use the parameters of the energy meter and MODBUS commands** ===
100 +=== 1.3.2 How to use the parameters of the energy meter and MODBUS commands ===
117 117  
118 -
119 119  If the user needs to read the parameters of the electric energy meter and use the modbus command,please refer to the appendix of the MODBUS communication protocol in the user manual of the energy meter.
120 120  
121 -[[image:image-20220601143257-10.png]]
104 +[[image:image-20220527092629-8.png]]
122 122  
123 123  
124 -(% style="color:blue" %)**Example:**(%%)  AT+COMMAND1=01 03 00 00 00 01 84 0A
107 +(% class="box infomessage" %)
108 +(((
109 +**Example:** AT+COMMAND1=01 03 00 00 00 01 84 0A
110 +)))
125 125  
126 126  * The first byte : slave address code (=001～247)
127 127  * The second byte : read register value function code
... ... @@ -130,12 +130,12 @@
130 130  * 7th and 8th bytes: CRC16 checksum from bytes 1 to 6.
131 131  
132 132  (((
133 -
134 -
135 -
136 136  How to parse the reading of the return command of the parameter：
120 +)))
137 137  
138 -(% style="color:blue" %)**Example:**(%%) RETURN1：01 03 02 08 FD 7E 05
122 +(% class="box infomessage" %)
123 +(((
124 +**Example:** RETURN1：01 03 02 08 FD 7E 05
139 139  )))
140 140  
141 141  * The first byte ARD: slave address code (=001～254)
... ... @@ -148,27 +148,22 @@
148 148  (% class="wikigeneratedid" %)
149 149  (((
150 150  
151 -
152 -
153 -
154 154  )))
155 155  
156 -=== **1.3.3 How to configure RS485-LN and parse output commands** ===
139 +=== 1.3.3 How to configure RS485-LN and parse output commands ===
157 157  
158 -
159 159  RS485-LN provides two configuration methods: AT COMMAND and DOWNLINK.
160 160  
161 161  
162 -==== **1.3.3.1 via AT COMMAND** ====
144 +==== 1.3.3.1 via AT COMMAND: ====
163 163  
146 +First, we can use **AT+CFGDEV** to get the return value, and we can also judge whether the input parameters are correct.
164 164  
165 -First, we can use (% style="color:blue" %)**AT+CFGDEV**(%%) to get the return value, and we can also judge whether the input parameters are correct.
166 -
167 167  (((
168 168  If the configured parameters and commands are incorrect, the return value is not obtained.
169 169  )))
170 170  
171 -[[image:image-20220601143201-9.png]]
152 +[[image:image-20220527092748-9.png]]
172 172  
173 173  AT COMMAND
174 174  
... ... @@ -175,33 +175,31 @@
175 175  
176 176  (% class="box infomessage" %)
177 177  (((
178 - **AT+DATACUTx **:  This command defines how to handle the return from AT+COMMANDx, max reture length is 40 bytes. AT+DATACUTx=a,b,c
159 + AT+DATACUTx : This command defines how to handle the return from AT+COMMANDx, max reture length is 40 bytes. AT+DATACUTx=a,b,c
179 179  )))
180 180  
181 -a:  length for the return of AT+COMMAND
162 +a: length for the return of AT+COMMAND
182 182  
183 -b: 1: grab valid value by byte, max 6 bytes;  2: grab valid value by bytes section, max 3 sections.
164 +b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.
184 184  
185 -c:  define the position for valid value.
166 +c: define the position for valid value.
186 186  
187 -[[image:image-20220601143115-8.png]]
168 +[[image:image-20220527092936-10.png]]
188 188  
189 189  AT COMMAND
190 190  
191 191  
192 -
193 193  PAYLOAD is available after the valid value is intercepted.
194 194  
195 195  
196 -[[image:image-20220601143046-7.png]]
176 +[[image:image-20220527093059-11.png]]
197 197  
198 198  AT COMMAND
199 199  
200 200  
201 -
202 202  You can get configured PAYLOAD on TTN.
203 203  
204 -[[image:image-20220601143519-1.png]]
183 +[[image:image-20220527093133-12.png]]
205 205  
206 206  (((
207 207  AT COMMAND
... ... @@ -212,52 +212,46 @@
212 212  )))
213 213  
214 214  (((
215 -(% style="color:blue" %)**Example**:
216 -
217 -CMD1: Read current data with MODBUS command. address: 0x03 AT+COMMAND1= 01 03 00 03 00 01,1
194 +**Example**: CMD1:Read current data with MODBUS command. address:0x03 AT+COMMAND1= 01 03 00 03 00 01,1
218 218  )))
219 219  
220 220  (((
221 -RETURN1: 01 03 02 00 02 39 85 00 00(return data)
198 +RETURN1:01 03 02 00 02 39 85 00 00(return data)
222 222  )))
223 223  
224 224  (((
225 -AT+DATACUT1: 9,1,4+5+6+7 Take the return value 00 02 39 85 as the valid value of reading current data and used to splice payload.
226 -
227 -
202 +AT+DATACUT1:9,1,4+5+6+7 Take the return value 00 02 39 85 as the valid value of reading current data and used to splice payload.
228 228  )))
229 229  
230 230  (((
231 -CMD2: Read voltage data with MODBUS command. address: 0x00 AT+COMMAND2= 01 03 00 00 00 01,1
206 +CMD2:Read voltage data with MODBUS command. address:0x00 AT+COMMAND2= 01 03 00 00 00 01,1
232 232  )))
233 233  
234 234  (((
235 -RETURN2: 01 03 02 08 DC BE 1D(return data)
210 +RETURN2:01 03 02 08 DC BE 1D(return data)
236 236  )))
237 237  
238 238  (((
239 -AT+DATACUT2: 7,1,4+5 Take the return value 08 DC as the valid value of reading voltage data and used to splice payload.
240 -
241 -
214 +AT+DATACUT2:7,1,4+5 Take the return value 08 DC as the valid value of reading voltage data and used to splice payload.
242 242  )))
243 243  
244 244  (((
245 -CMD3: Read total active energy data with MODBUS command. address: 0x0031 AT+COMMAND3= 01 03 00 31 00 02,1
218 +CMD3:Read total active energy data with MODBUS command. address:0x0031 AT+COMMAND3= 01 03 00 31 00 02,1
246 246  )))
247 247  
248 248  (((
249 -RETURN3: 01 03 04 00 00 00 44 FA 00(return data)
222 +RETURN3:01 03 04 00 00 00 44 FA 00(return data)
250 250  )))
251 251  
252 252  (((
253 -AT+DATACUT3: 9,1,4+5+6+7 Take the return value 00 00 00 44 as the valid value of reading total active energy data and used to splice payload.
226 +AT+DATACUT3:9,1,4+5+6+7 Take the return value 00 00 00 44 as the valid value of reading total active energy data and used to splice payload.
254 254  )))
255 255  
256 256  (((
257 -Payload: 01 00 02 39 85 08 DC 00 00 00 44
230 +Payload:01 00 02 39 85 08 DC 00 00 00 44
258 258  )))
259 259  
260 -[[image:image-20220601142936-6.png]]
233 +[[image:image-20220527093204-13.png]]
261 261  
262 262  AT COMMAND
263 263  
... ... @@ -264,15 +264,13 @@
264 264  
265 265  (% style="color:#4f81bd" %)**01 is device address,00 02 is the current, 08 DC is the voltage,00 00 00 44 is the total active energy.**
266 266  
240 +[[image:image-20220527093251-14.png]]
267 267  
268 -[[image:image-20220601143642-2.png]]
269 -
270 270  AT COMMAND
271 271  
272 272  
273 -==== **1.3.3.2 via LoRaWAN DOWNLINK** ====
245 +==== 1.3.3.2 via LoRaWAN DOWNLINK ====
274 274  
275 -
276 276  [[image:image-20220527093358-15.png]]
277 277  
278 278  (((
... ... @@ -284,7 +284,7 @@
284 284  )))
285 285  
286 286  (((
287 -(% style="color:#4f81bd" %)**Type Code 0xAF**
258 +**Type Code 0xAF**
288 288  )))
289 289  
290 290  (((
... ... @@ -295,7 +295,7 @@
295 295  )))
296 296  
297 297  (((
298 -(% style="color:red" %)Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
269 +Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
299 299  )))
300 300  
301 301  (((
... ... @@ -331,45 +331,39 @@
331 331  )))
332 332  
333 333  (((
334 -
335 -
336 -(% style="color:blue" %)**Example:**
305 +Example:
337 337  )))
338 338  
339 339  (((
340 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
309 +AF 03 01 06 0A 05 00 04 00 01 00: Same as AT+COMMAND3=0A 05 00 04 00 01,1
341 341  )))
342 342  
343 -[[image:image-20220601144149-6.png]]
312 +[[image:https://wiki.dragino.com/images/thumb/4/45/DOWNLINK_METER2.png/600px-DOWNLINK_METER2.png||height="208" width="600"]]
344 344  
345 345  DOWNLINK
346 346  
347 347  
317 +[[~[~[image:https://wiki.dragino.com/images/thumb/2/20/DOWNLINK_METER3.png/600px-DOWNLINK_METER3.png~|~|height="105" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:DOWNLINK_METER3.png]]
348 348  
349 -[[image:image-20220601143803-3.png]]
350 -
351 351  DOWNLINK
352 352  
353 353  
322 +[[image:https://wiki.dragino.com/images/thumb/2/27/DOWNLINK_METER4.png/600px-DOWNLINK_METER4.png||height="210" width="600"]]
354 354  
355 -[[image:image-20220601144053-5.png]]
356 -
357 357  DOWNLINK
358 358  
359 359  
327 +[[~[~[image:https://wiki.dragino.com/images/thumb/3/39/DOWNLINK_METER5.png/600px-DOWNLINK_METER5.png~|~|height="176" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:DOWNLINK_METER5.png]]
360 360  
361 -[[image:image-20220601143921-4.png]]
362 -
363 363  DOWNLINK
364 364  
365 365  
332 +[[image:https://wiki.dragino.com/images/thumb/a/a2/DOWNLINK_METER6.png/600px-DOWNLINK_METER6.png||height="365" width="600"]]
366 366  
367 -[[image:image-20220601142805-5.png]]
368 -
369 369  DOWNLINK
370 370  
371 371  
372 -=== **1.3.4 How to configure and output commands for RS485 to USB** ===
337 +=== 1.3.4 How to configure and output commands for RS485 to USB ===
373 373  
374 374  (((
375 375  This step is not necessary, it is just to show how to use a normal RS485 to USB adapter to connect to the meter to check the input and output. This can be used to test the connection and RS485 command of the meter without RS485-LN.
... ... @@ -389,46 +389,36 @@
389 389  
390 390  (((
391 391  check digit: Even
392 -
393 -
394 394  )))
395 395  
396 -[[image:image-20220527093708-21.png]]
359 +[[image:https://wiki.dragino.com/images/thumb/8/8f/Usb_meter2.jpg/600px-Usb_meter2.jpg||height="725" width="544"]]
397 397  
398 398  USB
399 399  
400 400  
364 +[[image:https://wiki.dragino.com/images/thumb/6/62/Usb_meter1.jpg/600px-Usb_meter1.jpg||height="728" width="546"]]
401 401  
402 -[[image:image-20220527093747-22.png]]
403 -
404 404  USB
405 405  
406 406  
407 -
408 408  (((
409 409  The configuration command is consistent with the AT command, input the hexadecimal command directly into the serial port, and the serial port will output the command.
410 -
411 -
412 412  )))
413 413  
414 414  (((
415 -(% style="color:blue" %)**Example:**  (%%)input：01 03 00 31 00 02 95 c4
374 +**Example:**  input：01 03 00 31 00 02 95 c4
416 416  )))
417 417  
418 418  (((
419 419   output：01 03 04 00 00 00 42 7A 02
420 -
421 -
422 422  )))
423 423  
424 -[[image:image-20220527093821-23.png]]
381 +[[image:https://wiki.dragino.com/images/thumb/b/b3/Usb_meter3.jpg/600px-Usb_meter3.jpg||height="466" width="600"]]
425 425  
426 426  USB
427 427  
385 +=== 1.3.5 How to configure multiple devices and modify device addresses ===
428 428  
429 -=== **1.3.5 How to configure multiple devices and modify device addresses** ===
430 -
431 -
432 432  If users need to read the parameters of multiple energy meters, they need to modify the device address, because the default device address of each energy meter is 01.
433 433  
434 434  (((
... ... @@ -437,17 +437,14 @@
437 437  )))
438 438  )))
439 439  
440 -[[image:image-20220601142044-1.png]]
395 +[[image:https://wiki.dragino.com/images/thumb/1/1f/Double_meter3.png/600px-Double_meter3.png||alt="Double meter3.png" height="83" width="600"]]
441 441  
397 +**Example**:These two meters are examples of setting parameters and device addresses.
442 442  
443 -(% style="color:blue" %)**Example**(%%): These two meters are examples of setting parameters and device addresses.
399 +[[image:https://wiki.dragino.com/images/thumb/e/ee/Double_meter1.jpg/600px-Double_meter1.jpg||alt="Double meter1.jpg" height="737" width="553"]]
444 444  
445 -[[image:image-20220527093950-25.png]]
401 +[[image:https://wiki.dragino.com/images/thumb/7/72/Double_meter2.jpg/600px-Double_meter2.jpg||alt="Double meter2.jpg" height="733" width="550"]]
446 446  
447 -
448 -[[image:image-20220527094028-26.png]]
449 -
450 -
451 451  (((
452 452  (((
453 453  First of all, since the default device address of the energy meter is 01, the configuration of two energy meters will conflict, so we first connect an energy meter and configure the device address.
... ... @@ -456,7 +456,7 @@
456 456  
457 457  (((
458 458  (((
459 -We can use **AT+CFGDEV** to set the device address.
411 +We can use AT+CFGDEV to set the device address.
460 460  )))
461 461  )))
462 462  
... ... @@ -466,14 +466,10 @@
466 466  )))
467 467  )))
468 468  
469 -[[image:image-20220601142354-2.png]]
421 +[[image:https://wiki.dragino.com/images/6/6b/Double_meter4.png||alt="Double meter4.png" height="141" width="456"]]
470 470  
423 +AT+CFGDEV:01 10 00 61 00 01 02 00 02,1
471 471  
472 -(% class="box infomessage" %)
473 -(((
474 -**AT+CFGDEV:01 10 00 61 00 01 02 00 02,1**
475 -)))
476 -
477 477  * 01:device adaress
478 478  
479 479  * 10:function code
... ... @@ -494,48 +494,33 @@
494 494  
495 495  Its default device address is 01, and the following are the parameters for configuring two energy meters.
496 496  
497 -[[image:image-20220601142452-3.png]]
445 +[[image:https://wiki.dragino.com/images/1/13/Meter11.png||alt="Meter11.png" height="576" width="379"]]
498 498  
447 +[[image:https://wiki.dragino.com/images/thumb/7/7e/Meter12.png/600px-Meter12.png||alt="Meter12.png" height="262" width="600"]]
499 499  
500 -[[image:image-20220601142607-4.png]]
449 +PAYLOAD:01 08 DF 43 62
501 501  
502 -
503 -**PAYLOAD:01 08 DF 43 62**
504 -
505 505  * 08 DF is the valid value of the meter with device address 02.
506 506  * 43 62 is the valid value of the meter with device address 01.
507 507  
508 -
509 -
510 -
511 511  == 1.4 Example 4: Circuit Breaker Remote Open Close ==
512 512  
456 +This instruction is provided by Xavier Florensa Berenguer from [[NORIA GRUPO DE COMPRAS>>url:http://www.gruponovelec.com/]]. It is to show how to use RS485-LN to connect to SCHNEIDER SMART and Monitor and control your cabinet remotely with no wires and with Dragino RS485-LN LoRaWAN technology. The structure is like below:
513 513  
514 -This instruction is provided by Xavier Florensa Berenguer from [[NORIA GRUPO DE COMPRAS>>url:http://www.gruponovelec.com/]]. It is to show how to use RS485-LN to connect to SCHNEIDER SMART and Monitor and control your cabinet remotely with no wires and with Dragino RS485-LN LoRaWAN technology.
458 +[[image:https://wiki.dragino.com/images/thumb/f/fa/RS485_04_2.png/600px-RS485_04_2.png||height="336" width="600"]]
515 515  
516 -The structure is like below:
517 -
518 -[[image:image-20220527094330-30.png]]
519 -
520 520  Connection
521 521  
462 +* [[Circuit Breaker Remote Open Close>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Circuit_Breaker_Remote_Open_Close/]] : Configure Documen
522 522  
523 -* Configure Documen: [[Circuit Breaker Remote Open Close>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/Circuit_Breaker_Remote_Open_Close/]]
524 -
525 -
526 -
527 -
528 528  == 1.5 Example 5: SEM Three Energy Meter with RS485-BL or RS485-LN ==
529 529  
530 -
531 531  This instruction is provided by Xavier Florensa Berenguer from [[NORIA GRUPO DE COMPRAS>>url:http://www.gruponovelec.com/]]. It is to show how to use RS485-BL to connect to SEM Three Energy Meter and send the data to mobile phone for remote minitor. The structure is like below:
532 532  
533 -* Configure Document For RS485-BL: [[Connect to SEM Three>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Application_Note/&file=Dragino%20RS485BL%20and%20pickdata%20SEM%20Three%20v1.pdf||style="background-color: rgb(255, 255, 255);"]]
534 -* Configure Document for RS485-LN: [[Connect to SEM Three>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/SEM_Three_Energy_Meter/&file=SEM%20three%20and%20Dragino%20RS485-LN%20v1.pdf]]
468 +* [[Connect to SEM Three>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Application_Note/&file=Dragino%20RS485BL%20and%20pickdata%20SEM%20Three%20v1.pdf]] : Configure Document For RS485-BL
535 535  
470 +* [[Connect to SEM Three>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/Application_Note/SEM_Three_Energy_Meter/&file=SEM%20three%20and%20Dragino%20RS485-LN%20v1.pdf]] : Configure Document for RS485-LN
536 536  
537 -
538 -
539 539  == 1.6 Example 6:CEM C31 485-T1-MID Energy Meter with RS485-LN ==
540 540  
541 541  This instruction is provided by Xavier Florensa Berenguer from [[NORIA GRUPO DE COMPRAS>>url:http://www.gruponovelec.com/]]. It is to show how to use RS485-LN to connect to CEM C31 485-T1-MID and send the data for remote minitor. The structure is like below:
... ... @@ -544,7 +544,7 @@
544 544  
545 545  == 1.7 Example 7:Schneider Electric PLC M221 with RS485-BL ==
546 546  
547 -[[image:image-20220527094556-31.png]]
480 +[[image:https://wiki.dragino.com/images/thumb/9/97/PLC_M221.png/600px-PLC_M221.png||height="353" width="600"]]
548 548  
549 549  Network Structure
550 550  
image-20220527093430-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -16.9 KB
Content
image-20220527093508-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -21.5 KB
Content
image-20220527093530-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -16.5 KB
Content
image-20220527093607-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -28.3 KB
Content
image-20220527093628-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -34.6 KB
Content
image-20220527093708-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -569.4 KB
Content
image-20220527093747-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -672.8 KB
Content
image-20220527093821-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -161.5 KB
Content
image-20220527093849-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -3.4 KB
Content
image-20220527093950-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -624.4 KB
Content
image-20220527094028-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -815.2 KB
Content
image-20220527094100-27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -2.3 KB
Content
image-20220527094150-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.7 KB
Content
image-20220527094224-29.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -25.8 KB
Content
image-20220527094330-30.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -465.2 KB
Content
image-20220527094556-31.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -162.5 KB
Content
image-20220601142044-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -3.7 KB
Content
image-20220601142354-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -2.8 KB
Content
image-20220601142452-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -28.1 KB
Content
image-20220601142607-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.9 KB
Content
image-20220601142805-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -35.8 KB
Content
image-20220601142936-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.7 KB
Content
image-20220601143046-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.2 KB
Content
image-20220601143115-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.9 KB
Content
image-20220601143201-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -16.5 KB
Content
image-20220601143257-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -9.1 KB
Content
image-20220601143519-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -13.2 KB
Content
image-20220601143642-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -41.4 KB
Content
image-20220601143803-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.8 KB
Content
image-20220601143921-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.2 KB
Content
image-20220601144053-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -17.1 KB
Content
image-20220601144149-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -17.4 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0