Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 32.12 >
edited by Xiaoling
on 2022/06/02 15:26
To version < 40.1 >
edited by Xiaoling
on 2022/06/02 16:33
>
Change comment: Uploaded new attachment "image-20220602163333-5.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -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,8 +100,6 @@
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/]]
... ... @@ -152,10 +152,15 @@
152 152  
153 153  [[image:1653268155545-638.png||height="334" width="724"]]
154 154  
149 +
155 155  (((
151 +(((
156 156  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:
153 +)))
157 157  
155 +(((
158 158  485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
157 +)))
159 159  
160 160  [[image:1653268227651-549.png||height="592" width="720"]]
161 161  
... ... @@ -207,6 +207,7 @@
207 207  
208 208  [[image:1652953568895-172.png||height="232" width="724"]]
209 209  
209 +
210 210  == 3.3 Configure Commands to read data ==
211 211  
212 212  (((
... ... @@ -216,6 +216,8 @@
216 216  
217 217  (((
218 218  (% 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
219 +
220 +
219 219  )))
220 220  )))
221 221  
... ... @@ -223,19 +223,19 @@
223 223  
224 224  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:
225 225  
226 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
227 -|(((
228 +(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
229 +|(% style="width:128px" %)(((
228 228  **AT Commands**
229 -)))|(% style="width:285px" %)(((
231 +)))|(% style="width:305px" %)(((
230 230  **Description**
231 -)))|(% style="width:347px" %)(((
233 +)))|(% style="width:346px" %)(((
232 232  **Example**
233 233  )))
234 -|(((
236 +|(% style="width:128px" %)(((
235 235  AT+BAUDR
236 -)))|(% style="width:285px" %)(((
238 +)))|(% style="width:305px" %)(((
237 237  Set the baud rate (for RS485 connection). Default Value is: 9600.
238 -)))|(% style="width:347px" %)(((
240 +)))|(% style="width:346px" %)(((
239 239  (((
240 240  AT+BAUDR=9600
241 241  )))
... ... @@ -244,11 +244,11 @@
244 244  Options: (1200,2400,4800,14400,19200,115200)
245 245  )))
246 246  )))
247 -|(((
249 +|(% style="width:128px" %)(((
248 248  AT+PARITY
249 -)))|(% style="width:285px" %)(((
251 +)))|(% style="width:305px" %)(((
250 250  Set UART parity (for RS485 connection)
251 -)))|(% style="width:347px" %)(((
253 +)))|(% style="width:346px" %)(((
252 252  (((
253 253  AT+PARITY=0
254 254  )))
... ... @@ -257,9 +257,9 @@
257 257  Option: 0: no parity, 1: odd parity, 2: even parity
258 258  )))
259 259  )))
260 -|(((
262 +|(% style="width:128px" %)(((
261 261  AT+STOPBIT
262 -)))|(% style="width:285px" %)(((
264 +)))|(% style="width:305px" %)(((
263 263  (((
264 264  Set serial stopbit (for RS485 connection)
265 265  )))
... ... @@ -267,7 +267,7 @@
267 267  (((
268 268  
269 269  )))
270 -)))|(% style="width:347px" %)(((
272 +)))|(% style="width:346px" %)(((
271 271  (((
272 272  AT+STOPBIT=0 for 1bit
273 273  )))
... ... @@ -302,77 +302,34 @@
302 302  === 3.3.3 Configure read commands for each sampling ===
303 303  
304 304  (((
305 -RS485-BL is a battery powered device; it will sleep most of time. And wake up on each period and read RS485 / TTL sensor data and uplink.
306 -)))
307 +During each sampling, we need confirm what commands we need to send to the RS485 sensors to read data. After the RS485 sensors send back the value, it normally include some bytes and we only need a few from them for a shorten payload.
307 307  
308 -(((
309 -During each sampling, we need to confirm what commands we need to send to the sensors to read data. After the RS485/TTL sensors send back the value, it normally includes some bytes and we only need a few from them for a shorten payload.
310 -)))
311 -
312 -(((
313 313  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
314 -)))
315 315  
316 -(((
317 317  This section describes how to achieve above goals.
318 -)))
319 319  
320 -(((
321 -During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
322 -)))
313 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
323 323  
324 -(((
325 -**Command from RS485-BL to Sensor:**
326 -)))
327 327  
328 -(((
329 -RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
330 -)))
316 +**Each RS485 commands include two parts:**
331 331  
332 -(((
333 -**Handle return from sensors to RS485-BL**:
334 -)))
318 +~1. What commands RS485-LN will send to the RS485 sensors. There are total 15 commands from **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF**. All commands are of same grammar.
335 335  
336 -(((
337 -After RS485-BL send out a string to sensor, RS485-BL will wait for the return from RS485 or TTL sensor. And user can specify how to handle the return, by **AT+DATACUT or AT+SEARCH commands**
338 -)))
320 +2. How to get wanted value the from RS485 sensors returns from by 1). There are total 15 AT Commands to handle the return, commands are **AT+DATACUT1**,**AT+DATACUT2**,…, **AT+DATACUTF** corresponding to the commands from 1). All commands are of same grammar.
339 339  
340 -* (((
341 -**AT+DATACUT**
342 -)))
322 +3. Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example **AT+CMDDL1=1000** to send the open time to 1000ms
343 343  
344 -(((
345 -When the return value from sensor have fix length and we know which position the valid value we should get, we can use AT+DATACUT command.
346 -)))
347 347  
348 -* (((
349 -**AT+SEARCH**
350 -)))
351 -
352 -(((
353 -When the return value from sensor is dynamic length and we are not sure which bytes the valid data is, instead, we know what value the valid value following. We can use AT+SEARCH to search the valid value in the return string.
354 -)))
355 -
356 -(((
357 -**Define wait timeout:**
358 -)))
359 -
360 -(((
361 -Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example, AT+CMDDL1=1000 to send the open time to 1000ms
362 -)))
363 -
364 -(((
365 365  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
366 -)))
367 367  
368 -**Examples:**
369 369  
370 370  Below are examples for the how above AT Commands works.
371 371  
372 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
373 373  
374 -(% border="1" class="table-bordered" %)
375 -|(((
331 +**AT+COMMANDx : **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:
332 +
333 +(% border="1" style="background-color:#4bacc6; color:white; width:499px" %)
334 +|(% style="width:496px" %)(((
376 376  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
377 377  
378 378  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -380,49 +380,15 @@
380 380  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
381 381  )))
382 382  
383 -(((
384 384  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.
385 -)))
386 386  
387 -(((
388 -In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
389 -)))
344 +In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
390 390  
391 -(((
392 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
393 -)))
394 394  
395 -(% border="1" class="table-bordered" %)
396 -|(((
397 -**AT+SEARCHx=aa,xx xx xx xx xx**
398 -
399 -* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
400 -* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
401 -
402 -
403 -)))
404 -
405 -**Examples:**
406 -
407 -~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
408 -
409 -If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
410 -
411 -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**
412 -
413 -[[image:1653269403619-508.png]]
414 -
415 -2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
416 -
417 -If we set AT+SEARCH1=2, 1E 56 34+31 00 49
418 -
419 -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**
420 -
421 -[[image:1653269438444-278.png]]
422 -
423 423  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
424 424  
425 -|(((
349 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
350 +|(% style="width:722px" %)(((
426 426  **AT+DATACUTx=a,b,c**
427 427  
428 428  * **a: length for the return of AT+COMMAND**
... ... @@ -430,48 +430,37 @@
430 430  * **c: define the position for valid value.  **
431 431  )))
432 432  
433 -Examples:
358 +**Examples:**
434 434  
435 435  * Grab bytes:
436 436  
437 -[[image:1653269551753-223.png||height="311" width="717"]]
362 +[[image:image-20220602153621-1.png]]
438 438  
364 +
439 439  * Grab a section.
440 440  
441 -[[image:1653269568276-930.png||height="325" width="718"]]
367 +[[image:image-20220602153621-2.png]]
442 442  
369 +
443 443  * Grab different sections.
444 444  
445 -[[image:1653269593172-426.png||height="303" width="725"]]
372 +[[image:image-20220602153621-3.png]]
446 446  
447 -(% style="color:red" %)**Note:**
374 +
375 +)))
448 448  
449 -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.
450 -
451 -Example:
452 -
453 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
454 -
455 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
456 -
457 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
458 -
459 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
460 -
461 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
462 -
463 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
464 -
465 -[[image:1653269618463-608.png]]
466 -
467 467  === 3.3.4 Compose the uplink payload ===
468 468  
469 469  (((
470 470  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.**
381 +
382 +
471 471  )))
472 472  
473 473  (((
474 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
386 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
387 +
388 +
475 475  )))
476 476  
477 477  (((
... ... @@ -492,8 +492,10 @@
492 492  
493 493  [[image:1653269759169-150.png||height="513" width="716"]]
494 494  
495 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
496 496  
410 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
411 +
412 +
497 497  Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
498 498  
499 499  Final Payload is
... ... @@ -500,138 +500,98 @@
500 500  
501 501  (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
502 502  
503 -1. Battery Info (2 bytes): Battery voltage
504 -1. PAYVER (1 byte): Defined by AT+PAYVER
505 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
506 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
507 -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
419 +1. PAYVER: Defined by AT+PAYVER
420 +1. PAYLOAD COUNT: Total how many uplinks of this sampling.
421 +1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
422 +1. DATA: Valid value: max 8 bytes for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 8 bytes
508 508  
509 -[[image:1653269916228-732.png||height="433" width="711"]]
424 +[[image:image-20220602155039-4.png]]
510 510  
511 511  
512 -So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
427 +So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
513 513  
514 -DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41
429 +DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= **20 20 0a 33 90 41 02 aa**
515 515  
516 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 02 aa 05 81 0a 20
431 +DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= **05 81 0a 20 20 20 20 2d**
517 517  
518 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (% style="background-color:green; color:white" %)20 20 20 2d 30
433 +DATA3=the rest of Valid value of RETURN10= **30**
519 519  
520 -Below are the uplink payloads:
521 521  
522 -[[image:1653270130359-810.png]]
436 +(% style="color:red" %)Notice: In firmware v1.3, the Max bytes has been changed according to the max bytes in different Frequency Bands for lowest SF. As below:
523 523  
438 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
524 524  
525 -(% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
440 + * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
526 526  
527 - ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
442 + * For US915 band, max 11 bytes for each uplink.
528 528  
529 - * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
444 + ~* For all other bands: max 51 bytes for each uplink.
530 530  
531 - * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
532 532  
533 - ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
447 +Below are the uplink payloads:
534 534  
449 +[[image:1654157178836-407.png]]
450 +
451 +
535 535  === 3.3.5 Uplink on demand ===
536 536  
537 -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.
454 +Except uplink periodically, RS485-LN is able to uplink on demand. The server send downlink command to RS485-LN and RS485 will uplink data base on the command.
538 538  
539 539  Downlink control command:
540 540  
541 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
458 +**0x08 command**: Poll an uplink with current command set in RS485-LN.
542 542  
543 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
460 +**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors.
544 544  
545 545  
546 546  
547 -1.
548 -11.
549 -111. Uplink on Interrupt
464 +=== 3.3.6 Uplink on Interrupt ===
550 550  
551 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
466 +RS485-LN support external Interrupt uplink since hardware v1.2 release.
552 552  
553 -AT+INTMOD=0  Disable Interrupt
468 +[[image:1654157342174-798.png]]
554 554  
555 -AT+INTMOD=1  Interrupt trigger by rising or falling edge.
470 +Connect the Interrupt pin to RS485-LN INT port and connect the GND pin to V- port. When there is a high voltage (Max 24v) on INT pin. Device will send an uplink packet.
556 556  
557 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
558 558  
559 -AT+INTMOD=3  Interrupt trigger by rising edge.
473 +== 3.4 Uplink Payload ==
560 560  
561 -
562 -1.
563 -11. Uplink Payload
564 -
565 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
566 -|Value|(((
475 +(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
476 +|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands**
477 +|Value|(% style="width:120px" %)(((
567 567  Battery(mV)
568 568  
569 569  &
570 570  
571 571  Interrupt _Flag
572 -)))|(((
483 +)))|(% style="width:116px" %)(((
573 573  PAYLOAD_VER
574 574  
575 575  
576 -)))|If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.
487 +)))|(% style="width:386px" %)If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.
577 577  
578 578  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
579 579  
580 580  
581 -function Decoder(bytes, port) {
492 +== 3.5 Configure RS485-BL via AT or Downlink ==
582 582  
583 -~/~/Payload Formats of RS485-BL Deceive
494 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
584 584  
585 -return {
496 +There are two kinds of Commands:
586 586  
587 - ~/~/Battery,units:V
498 +* (% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
588 588  
589 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
500 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
590 590  
591 - ~/~/GPIO_EXTI 
592 592  
593 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
594 594  
595 - ~/~/payload of version
504 +=== 3.5.1 Common Commands ===
596 596  
597 - Pay_ver:bytes[2],
506 +They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
598 598  
599 - };
600 600  
601 - }
509 +=== 3.5.2 Sensor related commands: ===
602 602  
603 -
604 -
605 -
606 -
607 -
608 -
609 -TTN V3 uplink screen shot.
610 -
611 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
612 -
613 -1.
614 -11. Configure RS485-BL via AT or Downlink
615 -
616 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
617 -
618 -There are two kinds of Commands:
619 -
620 -* **Common Commands**: They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: http:~/~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands
621 -
622 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
623 -
624 -1.
625 -11.
626 -111. Common Commands:
627 -
628 -They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands>>url:http://wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands]]
629 -
630 -
631 -1.
632 -11.
633 -111. Sensor related commands:
634 -
635 635  ==== Choose Device Type (RS485 or TTL) ====
636 636  
637 637  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
1654157178836-407.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +179.9 KB
Content
1654157342174-798.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.9 KB
Content
1654158783574-851.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +40.6 KB
Content
image-20220602153621-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +23.4 KB
Content
image-20220602153621-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.2 KB
Content
image-20220602153621-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content
image-20220602155039-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +24.6 KB
Content
image-20220602163333-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +48.2 KB
Content

Applications

Navigation

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