Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 32.16 >
edited by Xiaoling
on 2022/06/02 15:30
To version < 22.3 >
edited by Xiaoling
on 2022/05/23 09:12
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,42 +18,40 @@
18 18  
19 19  (((
20 20  (((
21 -The Dragino RS485-LN is a (% style="color:blue" %)**RS485 to LoRaWAN Converter**(%%). It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
21 +The Dragino RS485-LN is a RS485 to LoRaWAN Converter. It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
22 22  )))
23 23  
24 24  (((
25 -RS485-LN allows user to (% style="color:blue" %)**monitor / control RS485 devices**(%%) and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, smartphone detection, building automation, and so on.
25 +RS485-LN allows user to monitor / control RS485 devices and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, smartphone detection, building automation, and so on.
26 26  )))
27 27  
28 28  (((
29 -(% style="color:blue" %)**For data uplink**(%%), RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server.
29 +For data uplink, RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server.
30 30  )))
31 31  
32 32  (((
33 -(% style="color:blue" %)**For data downlink**(%%), RS485-LN runs in LoRaWAN Class C. When there downlink commands from LoRaWAN server, RS485-LN will forward the commands from LoRaWAN server to RS485 devices.
34 -
35 -(% style="color:blue" %)**Demo Dashboard for RS485-LN**(%%) connect to two energy meters: [[https:~~/~~/app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a>>url:https://app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a]]
33 +For data downlink, RS485-LN runs in LoRaWAN Class C. When there downlink commands from LoRaWAN server, RS485-LN will forward the commands from LoRaWAN server to RS485 devices.
36 36  )))
37 37  )))
38 38  
39 39  [[image:1653267211009-519.png||height="419" width="724"]]
40 40  
41 -
42 42  == 1.2 Specifications ==
43 43  
44 -
45 45  **Hardware System:**
46 46  
47 47  * STM32L072CZT6 MCU
48 -* SX1276/78 Wireless Chip 
44 +* SX1276/78 Wireless Chip
49 49  * Power Consumption (exclude RS485 device):
50 50  ** Idle: 32mA@12v
47 +
48 +*
51 51  ** 20dB Transmit: 65mA@12v
52 52  
53 53  **Interface for Model:**
54 54  
55 55  * RS485
56 -* Power Input 7~~ 24V DC. 
54 +* Power Input 7~~ 24V DC.
57 57  
58 58  **LoRa Spec:**
59 59  
... ... @@ -76,8 +76,6 @@
76 76  * Automatic RF Sense and CAD with ultra-fast AFC.
77 77  * Packet engine up to 256 bytes with CRC.
78 78  
79 -
80 -
81 81  == 1.3 Features ==
82 82  
83 83  * LoRaWAN Class A & Class C protocol (default Class C)
... ... @@ -89,8 +89,6 @@
89 89  * Support Modbus protocol
90 90  * Support Interrupt uplink (Since hardware version v1.2)
91 91  
92 -
93 -
94 94  == 1.4 Applications ==
95 95  
96 96  * Smart Buildings & Home Automation
... ... @@ -100,13 +100,10 @@
100 100  * Smart Cities
101 101  * Smart Factory
102 102  
103 -
104 -
105 105  == 1.5 Firmware Change log ==
106 106  
107 107  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
108 108  
109 -
110 110  == 1.6 Hardware Change log ==
111 111  
112 112  (((
... ... @@ -114,8 +114,6 @@
114 114  v1.2: Add External Interrupt Pin.
115 115  
116 116  v1.0: Release
117 -
118 -
119 119  )))
120 120  )))
121 121  
... ... @@ -132,8 +132,6 @@
132 132  )))
133 133  
134 134  [[image:1653268091319-405.png]]
135 -
136 -
137 137  )))
138 138  
139 139  = 3. Operation Mode =
... ... @@ -142,8 +142,6 @@
142 142  
143 143  (((
144 144  The RS485-LN is configured as LoRaWAN OTAA Class C 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-LN. It will auto join the network via OTAA.
145 -
146 -
147 147  )))
148 148  
149 149  == 3.2 Example to join LoRaWAN network ==
... ... @@ -152,15 +152,10 @@
152 152  
153 153  [[image:1653268155545-638.png||height="334" width="724"]]
154 154  
155 -
156 156  (((
157 -(((
158 158  The RS485-LN in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method. The connection is as below:
159 -)))
160 160  
161 -(((
162 162  485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
163 -)))
164 164  
165 165  [[image:1653268227651-549.png||height="592" width="720"]]
166 166  
... ... @@ -207,43 +207,44 @@
207 207  
208 208  
209 209  (((
210 -**Step 2**: Power on RS485-LN and it will auto join to the TTN V3 network. After join success, it will start to upload message to TTN V3 and user can see in the panel.
190 +**Step 2**: Power on RS485-BL and it will auto join to the TTN V3 network. After join success, it will start to upload message to TTN V3 and user can see in the panel.
211 211  )))
212 212  
213 213  [[image:1652953568895-172.png||height="232" width="724"]]
214 214  
215 -
216 216  == 3.3 Configure Commands to read data ==
217 217  
218 218  (((
219 -(((
220 -There are plenty of RS485 devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-LN supports flexible command set. User can use [[AT Commands>>path:#AT_COMMAND]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices.
198 +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.
221 221  )))
222 222  
223 -(((
224 -(% style="color:red" %)Note: below description and commands are for firmware version >v1.1, if you have firmware version v1.0. Please check the [[user manual v1.0>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/&file=RS485-LN_UserManual_v1.0.1.pdf]] or upgrade the firmware to v1.1
201 +=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
225 225  
226 -
227 -)))
228 -)))
203 +RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
229 229  
230 -=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
205 +**~1. RS485-MODBUS mode:**
231 231  
232 -To use RS485-LN to read data from RS485 sensors, connect the RS485-LN A/B traces to the sensors. And user need to make sure RS485-LN use the match UART setting to access the sensors. The related commands for UART settings are:
207 +AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
233 233  
234 -(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
235 -|(% style="width:128px" %)(((
209 +**2. TTL mode:**
210 +
211 +AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
212 +
213 +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.
214 +
215 +(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
216 +|(((
236 236  **AT Commands**
237 -)))|(% style="width:305px" %)(((
218 +)))|(% style="width:285px" %)(((
238 238  **Description**
239 -)))|(% style="width:346px" %)(((
220 +)))|(% style="width:347px" %)(((
240 240  **Example**
241 241  )))
242 -|(% style="width:128px" %)(((
223 +|(((
243 243  AT+BAUDR
244 -)))|(% style="width:305px" %)(((
225 +)))|(% style="width:285px" %)(((
245 245  Set the baud rate (for RS485 connection). Default Value is: 9600.
246 -)))|(% style="width:346px" %)(((
227 +)))|(% style="width:347px" %)(((
247 247  (((
248 248  AT+BAUDR=9600
249 249  )))
... ... @@ -252,12 +252,18 @@
252 252  Options: (1200,2400,4800,14400,19200,115200)
253 253  )))
254 254  )))
255 -|(% style="width:128px" %)(((
236 +|(((
256 256  AT+PARITY
257 -)))|(% style="width:305px" %)(((
238 +)))|(% style="width:285px" %)(((
239 +(((
258 258  Set UART parity (for RS485 connection)
259 -)))|(% style="width:346px" %)(((
241 +)))
242 +
260 260  (((
244 +Default Value is: no parity.
245 +)))
246 +)))|(% style="width:347px" %)(((
247 +(((
261 261  AT+PARITY=0
262 262  )))
263 263  
... ... @@ -265,17 +265,17 @@
265 265  Option: 0: no parity, 1: odd parity, 2: even parity
266 266  )))
267 267  )))
268 -|(% style="width:128px" %)(((
255 +|(((
269 269  AT+STOPBIT
270 -)))|(% style="width:305px" %)(((
257 +)))|(% style="width:285px" %)(((
271 271  (((
272 272  Set serial stopbit (for RS485 connection)
273 273  )))
274 274  
275 275  (((
276 -
263 +Default Value is: 1bit.
277 277  )))
278 -)))|(% style="width:346px" %)(((
265 +)))|(% style="width:347px" %)(((
279 279  (((
280 280  AT+STOPBIT=0 for 1bit
281 281  )))
... ... @@ -289,14 +289,15 @@
289 289  )))
290 290  )))
291 291  
292 -
293 293  === 3.3.2 Configure sensors ===
294 294  
295 295  (((
282 +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**.
283 +)))
284 +
296 296  (((
297 -Some sensors might need to configure before normal operation. User can configure such sensor via PC and RS485 adapter or through RS485-LN AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**(%%). Each (% style="color:#4f81bd" %)**AT+CFGDEV **(%%)equals to send a RS485 command to sensors. This command will only run when user input it and won’t run during each sampling.
286 +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.
298 298  )))
299 -)))
300 300  
301 301  (% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
302 302  |**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
... ... @@ -308,6 +308,8 @@
308 308  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
309 309  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
310 310  
299 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
300 +
311 311  === 3.3.3 Configure read commands for each sampling ===
312 312  
313 313  (((
... ... @@ -389,17 +389,11 @@
389 389  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
390 390  )))
391 391  
392 -(((
393 393  For example, if we have a RS485 sensor. The command to get sensor value is: 01 03 0B B8 00 02 46 0A. Where 01 03 0B B8 00 02 is the Modbus command to read the register 0B B8 where stored the sensor value. The 46 0A is the CRC-16/MODBUS which calculate manually.
394 -)))
395 395  
396 -(((
397 397  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
398 -)))
399 399  
400 -(((
401 401  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
402 -)))
403 403  
404 404  (% border="1" class="table-bordered" %)
405 405  |(((
... ... @@ -411,24 +411,26 @@
411 411  
412 412  )))
413 413  
414 -**Examples:**
398 +Examples:
415 415  
416 -~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
400 +1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
417 417  
418 418  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
419 419  
420 -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**
404 +The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
421 421  
422 -[[image:1653269403619-508.png]]
406 +[[image:1652954654347-831.png]]
423 423  
424 -2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
425 425  
409 +1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
410 +
426 426  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
427 427  
428 -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**
413 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
429 429  
430 -[[image:1653269438444-278.png]]
415 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
431 431  
417 +
432 432  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
433 433  
434 434  |(((
... ... @@ -443,95 +443,94 @@
443 443  
444 444  * Grab bytes:
445 445  
446 -[[image:1653269551753-223.png||height="311" width="717"]]
432 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
447 447  
448 448  * Grab a section.
449 449  
450 -[[image:1653269568276-930.png||height="325" width="718"]]
436 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
451 451  
452 452  * Grab different sections.
453 453  
454 -[[image:1653269593172-426.png||height="303" width="725"]]
440 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
455 455  
456 -(% style="color:red" %)**Note:**
457 457  
443 +Note:
444 +
458 458  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.
459 459  
460 460  Example:
461 461  
462 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
449 +AT+COMMAND1=11 01 1E D0,0
463 463  
464 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
451 +AT+SEARCH1=1,1E 56 34
465 465  
466 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
453 +AT+DATACUT1=0,2,1~~5
467 467  
468 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
455 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
469 469  
470 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
457 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
471 471  
472 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
459 +Valid payload after DataCUT command: 2e 30 58 5f 36
473 473  
474 -[[image:1653269618463-608.png]]
461 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
475 475  
476 -=== 3.3.4 Compose the uplink payload ===
477 477  
478 -(((
464 +
465 +
466 +1.
467 +11.
468 +111. Compose the uplink payload
469 +
479 479  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.**
480 -)))
481 481  
482 -(((
483 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
484 -)))
485 485  
486 -(((
487 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
488 -)))
473 +**Examples: AT+DATAUP=0**
489 489  
490 -(((
475 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
476 +
491 491  Final Payload is
492 -)))
493 493  
494 -(((
495 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
496 -)))
479 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
497 497  
498 -(((
499 499  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
500 -)))
501 501  
502 -[[image:1653269759169-150.png||height="513" width="716"]]
483 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
503 503  
504 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
505 505  
506 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
507 507  
487 +**Examples: AT+DATAUP=1**
488 +
489 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
490 +
508 508  Final Payload is
509 509  
510 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
493 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
511 511  
512 512  1. Battery Info (2 bytes): Battery voltage
513 513  1. PAYVER (1 byte): Defined by AT+PAYVER
514 514  1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
515 515  1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
516 -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
499 +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
517 517  
518 -[[image:1653269916228-732.png||height="433" width="711"]]
501 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
519 519  
520 520  
521 521  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
522 522  
523 -DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41
506 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
524 524  
525 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 02 aa 05 81 0a 20
508 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
526 526  
527 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (% style="background-color:green; color:white" %)20 20 20 2d 30
510 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
528 528  
512 +
513 +
529 529  Below are the uplink payloads:
530 530  
531 -[[image:1653270130359-810.png]]
516 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
532 532  
533 533  
534 -(% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
519 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
535 535  
536 536   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
537 537  
... ... @@ -541,8 +541,12 @@
541 541  
542 542   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
543 543  
544 -=== 3.3.5 Uplink on demand ===
545 545  
530 +
531 +1.
532 +11.
533 +111. Uplink on demand
534 +
546 546  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.
547 547  
548 548  Downlink control command:
1653269403619-508.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.8 KB
Content
1653269438444-278.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.6 KB
Content
1653269551753-223.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
1653269568276-930.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -131.4 KB
Content
1653269593172-426.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -142.6 KB
Content
1653269618463-608.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.7 KB
Content
1653269759169-150.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -294.0 KB
Content
1653269916228-732.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -143.3 KB
Content
1653270130359-810.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -197.8 KB
Content

Applications

Navigation

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