Changes for page RS485-LN – RS485 to LoRaWAN Converter User Manual
Last modified by Karry Zhuang on 2025/03/06 16:34
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 15 added, 0 removed)
- 1654160691922-496.png
- 1654162355560-817.png
- 1654162368066-342.png
- 1654162478620-421.png
- 1654162535040-878.png
- image-20220602165351-6.png
- image-20220602165351-7.png
- image-20220602171200-8.png
- image-20220602171200-9.png
- image-20220602175638-10.png
- image-20220602175743-11.png
- image-20220602175818-12.png
- image-20220602175848-13.png
- image-20220602175912-14.png
- image-20220606110929-1.png
Details
- Page properties
-
- Content
-
... ... @@ -6,12 +6,18 @@ 6 6 **RS485-LN – RS485 to LoRaWAN Converter User Manual** 7 7 8 8 9 + 10 + 9 9 **Table of Contents:** 10 10 13 +{{toc/}} 11 11 12 12 13 13 14 14 18 + 19 + 20 + 15 15 = 1.Introduction = 16 16 17 17 == 1.1 What is RS485-LN RS485 to LoRaWAN Converter == ... ... @@ -18,23 +18,33 @@ 18 18 19 19 ((( 20 20 ((( 27 +((( 21 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. 22 22 ))) 30 +))) 23 23 24 24 ((( 33 +((( 25 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. 26 26 ))) 36 +))) 27 27 28 28 ((( 39 +((( 29 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. 30 30 ))) 42 +))) 31 31 32 32 ((( 45 +((( 33 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. 47 +))) 34 34 49 +((( 35 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]] 36 36 ))) 37 37 ))) 53 +))) 38 38 39 39 [[image:1653267211009-519.png||height="419" width="724"]] 40 40 ... ... @@ -74,9 +74,8 @@ 74 74 * Preamble detection. 75 75 * 127 dB Dynamic Range RSSI. 76 76 * Automatic RF Sense and CAD with ultra-fast AFC. 77 -* Packet engine up to 256 bytes with CRC .93 +* Packet engine up to 256 bytes with CRC 78 78 79 - 80 80 == 1.3 Features == 81 81 82 82 * LoRaWAN Class A & Class C protocol (default Class C) ... ... @@ -88,7 +88,6 @@ 88 88 * Support Modbus protocol 89 89 * Support Interrupt uplink (Since hardware version v1.2) 90 90 91 - 92 92 == 1.4 Applications == 93 93 94 94 * Smart Buildings & Home Automation ... ... @@ -98,7 +98,6 @@ 98 98 * Smart Cities 99 99 * Smart Factory 100 100 101 - 102 102 == 1.5 Firmware Change log == 103 103 104 104 [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]] ... ... @@ -108,9 +108,13 @@ 108 108 109 109 ((( 110 110 ((( 124 +((( 111 111 v1.2: Add External Interrupt Pin. 126 +))) 112 112 128 +((( 113 113 v1.0: Release 130 +))) 114 114 115 115 116 116 ))) ... ... @@ -138,7 +138,9 @@ 138 138 == 3.1 How it works? == 139 139 140 140 ((( 158 +((( 141 141 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. 160 +))) 142 142 143 143 144 144 ))) ... ... @@ -162,7 +162,7 @@ 162 162 [[image:1653268227651-549.png||height="592" width="720"]] 163 163 164 164 ((( 165 -The LG308 is already set to connect to [[TTN V3 network >>path: eu1.cloud.thethings.network/]]. So what we need to now is only configure the TTN V3:184 +The LG308 is already set to connect to [[TTN V3 network >>path:https://www.thethingsnetwork.org/]]. So what we need to now is only configure the TTN V3: 166 166 ))) 167 167 168 168 ((( ... ... @@ -214,11 +214,15 @@ 214 214 215 215 ((( 216 216 ((( 217 -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. 236 +((( 237 +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>>||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices. 218 218 ))) 239 +))) 219 219 220 220 ((( 242 +((( 221 221 (% 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 244 +))) 222 222 223 223 224 224 ))) ... ... @@ -228,19 +228,19 @@ 228 228 229 229 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: 230 230 231 -(% border="1" style="background-color:#ffffcc; color:green; width: 782px" %)232 -|(% style="width:1 28px" %)(((254 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 255 +|=(% style="width: 110px;" %)((( 233 233 **AT Commands** 234 -)))|(% style="width: 305px" %)(((257 +)))|=(% style="width: 190px;" %)((( 235 235 **Description** 236 -)))|(% style="width: 346px" %)(((259 +)))|=(% style="width: 190px;" %)((( 237 237 **Example** 238 238 ))) 239 -|(% style="width:1 28px" %)(((262 +|(% style="width:110px" %)((( 240 240 AT+BAUDR 241 -)))|(% style="width: 305px" %)(((264 +)))|(% style="width:190px" %)((( 242 242 Set the baud rate (for RS485 connection). Default Value is: 9600. 243 -)))|(% style="width: 346px" %)(((266 +)))|(% style="width:190px" %)((( 244 244 ((( 245 245 AT+BAUDR=9600 246 246 ))) ... ... @@ -249,11 +249,11 @@ 249 249 Options: (1200,2400,4800,14400,19200,115200) 250 250 ))) 251 251 ))) 252 -|(% style="width:1 28px" %)(((275 +|(% style="width:110px" %)((( 253 253 AT+PARITY 254 -)))|(% style="width: 305px" %)(((277 +)))|(% style="width:190px" %)((( 255 255 Set UART parity (for RS485 connection) 256 -)))|(% style="width: 346px" %)(((279 +)))|(% style="width:190px" %)((( 257 257 ((( 258 258 AT+PARITY=0 259 259 ))) ... ... @@ -262,9 +262,9 @@ 262 262 Option: 0: no parity, 1: odd parity, 2: even parity 263 263 ))) 264 264 ))) 265 -|(% style="width:1 28px" %)(((288 +|(% style="width:110px" %)((( 266 266 AT+STOPBIT 267 -)))|(% style="width: 305px" %)(((290 +)))|(% style="width:190px" %)((( 268 268 ((( 269 269 Set serial stopbit (for RS485 connection) 270 270 ))) ... ... @@ -272,7 +272,7 @@ 272 272 ((( 273 273 274 274 ))) 275 -)))|(% style="width: 346px" %)(((298 +)))|(% style="width:190px" %)((( 276 276 ((( 277 277 AT+STOPBIT=0 for 1bit 278 278 ))) ... ... @@ -295,15 +295,15 @@ 295 295 ))) 296 296 ))) 297 297 298 -(% border="1" style="background-color:#ffffcc; color:green; width: 806px" %)299 -|**AT Commands**|(% style="width: 418px" %)**Description**|(% style="width:256px" %)**Example**300 -|AT+CFGDEV|(% style="width: 418px" %)(((321 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 322 +|=(% style="width: 110px;" %)**AT Commands**|=(% style="width: 190px;" %)**Description**|=(% style="width: 190px;" %)**Example** 323 +|AT+CFGDEV|(% style="width:110px" %)((( 301 301 This command is used to configure the RS485/TTL devices; they won’t be used during sampling. 302 302 303 303 AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx, 304 304 305 305 mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 306 -)))|(% style="width: 256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m329 +)))|(% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 307 307 308 308 309 309 === 3.3.3 Configure read commands for each sampling === ... ... @@ -351,8 +351,8 @@ 351 351 352 352 **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes. 353 353 354 -(% border="1" style="background-color:#4bacc6; color:white; width: 725px" %)355 -|(% style="width: 722px" %)(((377 +(% border="1" style="background-color:#4bacc6; color:white; width:510px" %) 378 +|(% style="width:510px" %)((( 356 356 **AT+DATACUTx=a,b,c** 357 357 358 358 * **a: length for the return of AT+COMMAND** ... ... @@ -421,6 +421,7 @@ 421 421 422 422 (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA** 423 423 447 + 424 424 1. PAYVER: Defined by AT+PAYVER 425 425 1. PAYLOAD COUNT: Total how many uplinks of this sampling. 426 426 1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) ... ... @@ -477,33 +477,33 @@ 477 477 478 478 == 3.4 Uplink Payload == 479 479 480 -(% border="1" style="background-color:#4bacc6; color:white; width:734px" %) 481 -|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands** 482 -|Value|(% style="width:120px" %)((( 483 -Battery(mV) 484 484 485 - &505 +[[image:image-20220606110929-1.png]] 486 486 487 -Interrupt _Flag 488 -)))|(% style="width:116px" %)((( 489 -PAYLOAD_VER 490 - 491 - 492 -)))|(% 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. 493 - 494 494 Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors. 495 495 496 496 497 497 == 3.5 Configure RS485-BL via AT or Downlink == 498 498 512 +((( 499 499 User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands 514 +))) 500 500 516 +((( 501 501 There are two kinds of Commands: 518 +))) 502 502 503 -* (% 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]] 520 +* ((( 521 +(% 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: [[AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]] 522 +))) 504 504 505 -* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN. User can see these commands below: 524 +* ((( 525 +(% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN. User can see these commands below: 526 +))) 506 506 528 +((( 529 + 530 +))) 507 507 508 508 509 509 === 3.5.1 Common Commands === ... ... @@ -520,8 +520,928 @@ 520 520 The first byte of this package represents whether the configuration is successful, 00 represents failure, 01 represents success. Except for the first byte, the other is the previous downlink. (All commands except A8 type commands are applicable) 521 521 522 522 523 -3.5.3 Sensor related commands 547 +=== 3.5.3 Sensor related commands === 524 524 525 -==== ==== 526 526 527 -==== ==== 550 + 551 + 552 +==== **RS485 Debug Command** ==== 553 + 554 +((( 555 +This command is used to configure the RS485 devices; they won’t be used during sampling. 556 +))) 557 + 558 +* ((( 559 +**AT Command** 560 +))) 561 + 562 +(% class="box infomessage" %) 563 +((( 564 +((( 565 +**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m** 566 +))) 567 +))) 568 + 569 +((( 570 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 571 +))) 572 + 573 +* ((( 574 +**Downlink Payload** 575 +))) 576 + 577 +((( 578 +Format: A8 MM NN XX XX XX XX YY 579 +))) 580 + 581 +((( 582 +Where: 583 +))) 584 + 585 +* ((( 586 +MM: 1: add CRC-16/MODBUS ; 0: no CRC 587 +))) 588 +* ((( 589 +NN: The length of RS485 command 590 +))) 591 +* ((( 592 +XX XX XX XX: RS485 command total NN bytes 593 +))) 594 +* ((( 595 +((( 596 +YY: How many bytes will be uplink from the return of this RS485 command, 597 +))) 598 + 599 +* ((( 600 +if YY=0, RS485-LN will execute the downlink command without uplink; 601 +))) 602 +* ((( 603 +if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200 604 +))) 605 +* ((( 606 +if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200. 607 +))) 608 +))) 609 + 610 +((( 611 +**Example 1** ~-~-> Configure without ask for uplink (YY=0) 612 +))) 613 + 614 +((( 615 +To connect a Modbus Alarm with below commands. 616 +))) 617 + 618 +* ((( 619 +The command to active alarm is: 0A 05 00 04 00 01 4C B0. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually. 620 +))) 621 + 622 +* ((( 623 +The command to deactivate alarm is: 0A 05 00 04 00 00 8D 70. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually. 624 +))) 625 + 626 +((( 627 +So if user want to use downlink command to control to RS485 Alarm, he can use: 628 +))) 629 + 630 +((( 631 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm 632 +))) 633 + 634 +((( 635 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm 636 +))) 637 + 638 +((( 639 +A8 is type code and 01 means add CRC-16/MODBUS at the end, the 3^^rd^^ byte is 06, means the next 6 bytes are the command to be sent to the RS485 network, the final byte 00 means this command don’t need to acquire output. 640 +))) 641 + 642 +((( 643 + 644 +))) 645 + 646 +((( 647 +**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**) 648 +))) 649 + 650 +((( 651 +User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY** 652 +))) 653 + 654 +((( 655 + 656 +))) 657 + 658 +((( 659 +RS485-LN got this downlink command and send (% style="color:#4f81bd" %)**0A 08 00 04 00 01 **(%%)to Modbus network. One of the RS485 sensor in the network send back Modbus reply **0A 08 00 04 00 00**. RS485-LN get this reply and combine with the original downlink command and uplink. The uplink message is: 660 +))) 661 + 662 +((( 663 + **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00 **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00** 664 +))) 665 + 666 +((( 667 + [[image:1654159460680-153.png]] 668 +))) 669 + 670 + 671 + 672 + 673 +==== **Set Payload version** ==== 674 + 675 +((( 676 +This is the first byte of the uplink payload. RS485-BL can connect to different sensors. User can set the PAYVER field to tell server how to decode the current payload. 677 +))) 678 + 679 +* ((( 680 +**AT Command:** 681 +))) 682 + 683 +(% class="box infomessage" %) 684 +((( 685 +((( 686 +**AT+PAYVER: Set PAYVER field = 1** 687 +))) 688 +))) 689 + 690 +* ((( 691 +**Downlink Payload:** 692 +))) 693 + 694 +((( 695 +**0xAE 01** ~-~-> Set PAYVER field = 0x01 696 +))) 697 + 698 +((( 699 +**0xAE 0F** ~-~-> Set PAYVER field = 0x0F 700 +))) 701 + 702 + 703 + 704 + 705 +==== **Set RS485 Sampling Commands** ==== 706 + 707 +((( 708 +AT+COMMANDx or AT+DATACUTx 709 +))) 710 + 711 +((( 712 +These three commands are used to configure how the RS485-LN polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]]. 713 +))) 714 + 715 +((( 716 + 717 +))) 718 + 719 +* ((( 720 +**AT Command:** 721 +))) 722 + 723 +(% class="box infomessage" %) 724 +((( 725 +((( 726 +**AT+COMMANDx: Configure RS485 read command to sensor.** 727 +))) 728 +))) 729 + 730 +(% class="box infomessage" %) 731 +((( 732 +((( 733 +**AT+DATACUTx: Configure how to handle return from RS485 devices.** 734 +))) 735 +))) 736 + 737 +((( 738 + 739 +))) 740 + 741 +* ((( 742 +**Downlink Payload:** 743 +))) 744 + 745 +((( 746 +**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx. 747 +))) 748 + 749 +((( 750 +(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink. 751 +))) 752 + 753 +((( 754 +Format: AF MM NN LL XX XX XX XX YY 755 +))) 756 + 757 +((( 758 +Where: 759 +))) 760 + 761 +* ((( 762 +MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F, 763 +))) 764 +* ((( 765 +NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value. 766 +))) 767 +* ((( 768 +LL: The length of AT+COMMAND or AT+DATACUT command 769 +))) 770 +* ((( 771 +XX XX XX XX: AT+COMMAND or AT+DATACUT command 772 +))) 773 +* ((( 774 +YY: If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-LN will execute an uplink after got this command. 775 +))) 776 + 777 +((( 778 +**Example:** 779 +))) 780 + 781 +((( 782 +(% style="color:#037691" %)**AF 03 01 06 0A 05 00 04 00 01 00**(%%): Same as AT+COMMAND3=0A 05 00 04 00 01,1 783 +))) 784 + 785 +((( 786 +(% style="color:#037691" %)**AF 03 02 06**(% style="color:orange" %)** 10 **(% style="color:red" %)**01 **(% style="color:green" %)**05 06 09 0A**(% style="color:#037691" %)** 00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**16**(%%),(% style="color:red" %)**1**(%%),(% style="color:green" %)**5+6+9+10** 787 +))) 788 + 789 +((( 790 +(% style="color:#037691" %)**AF 03 02 06 **(% style="color:orange" %)**0B**(% style="color:red" %)** 02 **(% style="color:green" %)**05 07 08 0A **(% style="color:#037691" %)**00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**11**(%%),(% style="color:red" %)**2**(%%),(% style="color:green" %)**5~~7+8~~10** 791 +))) 792 + 793 + 794 + 795 + 796 +==== **Fast command to handle MODBUS device** ==== 797 + 798 +((( 799 +AT+MBFUN is valid since v1.3 firmware version. The command is for fast configure to read Modbus devices. It is only valid for the devices which follow the [[MODBUS-RTU protocol>>url:https://www.modbustools.com/modbus.html]]. 800 +))) 801 + 802 +((( 803 +This command is valid since v1.3 firmware version 804 +))) 805 + 806 +((( 807 +AT+MBFUN can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore. 808 +))) 809 + 810 +((( 811 + 812 +))) 813 + 814 +((( 815 +**Example:** 816 +))) 817 + 818 +* ((( 819 +AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN. 820 +))) 821 +* ((( 822 +AT+COMMAND1= 01 03 00 10 00 08,1 ~-~-> read slave address 01 , function code 03, start address 00 01, quantity of registers 00 08. 823 +))) 824 +* ((( 825 +AT+COMMAND2= 01 02 00 40 00 10,1 ~-~-> read slave address 01 , function code 02, start address 00 40, quantity of inputs 00 10. 826 +))) 827 + 828 +[[image:image-20220602165351-6.png]] 829 + 830 +[[image:image-20220602165351-7.png]] 831 + 832 + 833 + 834 + 835 +==== **RS485 command timeout** ==== 836 + 837 +((( 838 +Some Modbus device has slow action to send replies. This command is used to configure the RS485-LN to use longer time to wait for their action. 839 +))) 840 + 841 +((( 842 +Default value: 0, range: 0 ~~ 65 seconds 843 +))) 844 + 845 +* ((( 846 +**AT Command:** 847 +))) 848 + 849 +(% class="box infomessage" %) 850 +((( 851 +((( 852 +**AT+CMDDLaa=hex(bb cc)*1000** 853 +))) 854 +))) 855 + 856 +((( 857 +**Example:** 858 +))) 859 + 860 +((( 861 +**AT+CMDDL1=1000** to send the open time to 1000ms 862 +))) 863 + 864 +((( 865 + 866 +))) 867 + 868 +* ((( 869 +**Downlink Payload:** 870 +))) 871 + 872 +((( 873 +**0x AA aa bb cc** 874 +))) 875 + 876 +((( 877 +Same as: AT+CMDDLaa=hex(bb cc)*1000 878 +))) 879 + 880 +((( 881 + **Example:** 882 +))) 883 + 884 +((( 885 + 0xAA 01 00 01 ~-~-> Same as **AT+CMDDL1=1000 ms** 886 +))) 887 + 888 + 889 + 890 + 891 +==== **Uplink payload mode** ==== 892 + 893 +((( 894 +Define to use one uplink or multiple uplinks for the sampling. 895 +))) 896 + 897 +((( 898 +The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]] 899 +))) 900 + 901 +* ((( 902 +**AT Command:** 903 +))) 904 + 905 +(% class="box infomessage" %) 906 +((( 907 +((( 908 +**AT+DATAUP=0** 909 +))) 910 +))) 911 + 912 +(% class="box infomessage" %) 913 +((( 914 +((( 915 +**AT+DATAUP=1** 916 +))) 917 +))) 918 + 919 +((( 920 + 921 +))) 922 + 923 +* ((( 924 +**Downlink Payload:** 925 +))) 926 + 927 +((( 928 +**0xAD 00** **~-~->** Same as AT+DATAUP=0 929 +))) 930 + 931 +((( 932 +**0xAD 01** **~-~->** Same as AT+DATAUP=1 933 +))) 934 + 935 + 936 + 937 + 938 +==== **Manually trigger an Uplink** ==== 939 + 940 +((( 941 +Ask device to send an uplink immediately. 942 +))) 943 + 944 +* ((( 945 +**AT Command:** 946 +))) 947 + 948 +((( 949 +No AT Command for this, user can press the [[ACT button>>||anchor="H3.7Buttons"]] for 1 second for the same. 950 +))) 951 + 952 +((( 953 + 954 +))) 955 + 956 +* ((( 957 +**Downlink Payload:** 958 +))) 959 + 960 +((( 961 +**0x08 FF**, RS485-LN will immediately send an uplink. 962 +))) 963 + 964 + 965 + 966 + 967 +==== **Clear RS485 Command** ==== 968 + 969 +((( 970 +The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them. 971 +))) 972 + 973 +* ((( 974 +**AT Command:** 975 +))) 976 + 977 +((( 978 +**AT+CMDEAR=mm,nn** mm: start position of erase ,nn: stop position of erase 979 +))) 980 + 981 +((( 982 +Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10 983 +))) 984 + 985 +((( 986 +Example screen shot after clear all RS485 commands. 987 +))) 988 + 989 +((( 990 + 991 +))) 992 + 993 +((( 994 +The uplink screen shot is: 995 +))) 996 + 997 +[[image:1654160691922-496.png]] 998 + 999 + 1000 +* ((( 1001 +**Downlink Payload:** 1002 +))) 1003 + 1004 +((( 1005 +**0x09 aa bb** same as AT+CMDEAR=aa,bb 1006 +))) 1007 + 1008 + 1009 + 1010 + 1011 +==== **Set Serial Communication Parameters** ==== 1012 + 1013 +((( 1014 +Set the Rs485 serial communication parameters: 1015 +))) 1016 + 1017 +* ((( 1018 +**AT Command:** 1019 +))) 1020 + 1021 +((( 1022 +Set Baud Rate: 1023 +))) 1024 + 1025 +(% class="box infomessage" %) 1026 +((( 1027 +((( 1028 +**AT+BAUDR=9600** ~/~/ Options: (1200,2400,4800,14400,19200,115200) 1029 +))) 1030 +))) 1031 + 1032 +((( 1033 +Set UART Parity 1034 +))) 1035 + 1036 +(% class="box infomessage" %) 1037 +((( 1038 +((( 1039 +**AT+PARITY=0** ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity 1040 +))) 1041 +))) 1042 + 1043 +((( 1044 +Set STOPBIT 1045 +))) 1046 + 1047 +(% class="box infomessage" %) 1048 +((( 1049 +((( 1050 +**AT+STOPBIT=0** ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits 1051 +))) 1052 +))) 1053 + 1054 +((( 1055 + 1056 +))) 1057 + 1058 +* ((( 1059 +**Downlink Payload:** 1060 +))) 1061 + 1062 +((( 1063 +**A7 01 aa bb**: Same AT+BAUDR=hex(aa bb)*100 1064 +))) 1065 + 1066 +((( 1067 +**Example:** 1068 +))) 1069 + 1070 +* ((( 1071 +A7 01 00 60 same as AT+BAUDR=9600 1072 +))) 1073 +* ((( 1074 +A7 01 04 80 same as AT+BAUDR=115200 1075 +))) 1076 + 1077 +((( 1078 +A7 02 aa: Same as AT+PARITY=aa (aa value: 00 , 01 or 02) 1079 +))) 1080 + 1081 +((( 1082 +A7 03 aa: Same as AT+STOPBIT=aa (aa value: 00 , 01 or 02) 1083 +))) 1084 + 1085 + 1086 + 1087 + 1088 +== 3.6 Listening mode for RS485 network == 1089 + 1090 +((( 1091 +This feature support since firmware v1.4 1092 +))) 1093 + 1094 +((( 1095 +RS485-LN supports listening mode, it can listen the RS485 network packets and send them via LoRaWAN uplink. Below is the structure. The blue arrow shows the RS485 network packets to RS485-LN. 1096 +))) 1097 + 1098 +[[image:image-20220602171200-8.png||height="567" width="1007"]] 1099 + 1100 +((( 1101 +To enable the listening mode, use can run the command AT+RXMODE. 1102 +))) 1103 + 1104 +((( 1105 + 1106 +))) 1107 + 1108 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %) 1109 +|=(% style="width: 100px;" %)((( 1110 +**Command example** 1111 +)))|=(% style="width: 400px;" %)((( 1112 +**Function** 1113 +))) 1114 +|(% style="width:100px" %)((( 1115 +AT+RXMODE=1,10 1116 +)))|(% style="width:400px" %)((( 1117 +Enable listening mode 1, if RS485-LN has received more than 10 RS485 commands from the network. RS485-LN will send these commands via LoRaWAN uplinks. 1118 +))) 1119 +|(% style="width:100px" %)((( 1120 +AT+RXMODE=2,500 1121 +)))|(% style="width:400px" %)((( 1122 +Enable listening mode 2, RS485-LN will capture and send a 500ms content once from the first detect of character. Max value is 65535 ms 1123 +))) 1124 +|(% style="width:100px" %)((( 1125 +AT+RXMODE=0,0 1126 +)))|(% style="width:400px" %)((( 1127 +Disable listening mode. This is the default settings. 1128 +))) 1129 +|(% style="width:100px" %)((( 1130 + 1131 +)))|(% style="width:400px" %)((( 1132 +A6 aa bb cc same as AT+RXMODE=aa,(bb<<8 | cc) 1133 +))) 1134 + 1135 +((( 1136 +**Downlink Command:** 1137 +))) 1138 + 1139 +((( 1140 +**0xA6 aa bb cc ** same as AT+RXMODE=aa,(bb<<8 | cc) 1141 +))) 1142 + 1143 +((( 1144 + 1145 +))) 1146 + 1147 +((( 1148 +**Example**: 1149 +))) 1150 + 1151 +((( 1152 +The RS485-LN is set to AT+RXMODE=2,1000 1153 +))) 1154 + 1155 +((( 1156 +There is a two Modbus commands in the RS485 network as below: 1157 +))) 1158 + 1159 +((( 1160 +The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b 1161 +))) 1162 + 1163 +((( 1164 +And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33 1165 +))) 1166 + 1167 +((( 1168 +RS485-LN will capture both and send the uplink: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33 1169 +))) 1170 + 1171 +((( 1172 +[[image:image-20220602171200-9.png]] 1173 +))) 1174 + 1175 +((( 1176 + 1177 +))) 1178 + 1179 +((( 1180 +(% style="color:red" %)Notice: Listening mode can work with the default polling mode of RS485-LN. When RS485-LN is in to send the RS485 commands (from AT+COMMANDx), the listening mode will be interrupt for a while. 1181 +))) 1182 + 1183 + 1184 +== 3.7 Buttons == 1185 + 1186 + 1187 +(% border="1" cellspacing="10" style="background-color:#f7faff; width:400px" %) 1188 +|=(% style="width: 50px;" %)**Button**|=(% style="width: 350px;" %)**Feature** 1189 +|(% style="width:50px" %)**ACT**|(% style="width:350px" %)If RS485 joined in network, press this button for more than 1 second, RS485 will upload a packet, and the SYS LED will give a (% style="color:blue" %)**Blue blink** 1190 +|(% style="width:50px" %)**RST**|(% style="width:350px" %)Reboot RS485 1191 +|(% style="width:50px" %)**PRO**|(% style="width:350px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]] 1192 + 1193 + 1194 +== 3.8 LEDs == 1195 + 1196 + 1197 +(% border="1" cellspacing="10" style="background-color:#f7faff; width:430px" %) 1198 +|=(% style="width: 50px;" %)**LEDs**|=(% style="width: 380px;" %)**Feature** 1199 +|**PWR**|Always on if there is power 1200 +|**SYS**|After device is powered on, the SYS will (% style="color:green" %)**fast blink in GREEN**(%%) for 5 times, means RS485-LN start to join LoRaWAN network. If join success, SYS will be (% style="color:green" %)**on GREEN for 5 seconds** (%%)**. **SYS will (% style="color:green" %)**blink Blue**(%%) on every upload and (% style="color:green" %)**blink Green**(%%) once receive a downlink message. 1201 + 1202 += 4. Case Study = 1203 + 1204 +User can check this URL for some case studies: [[APP RS485 COMMUNICATE WITH SENSORS>>doc:Main.Application Note \: Communicate with Different Sensors ----- RS485-LN RS485-BL.WebHome]] 1205 + 1206 + 1207 += 5. Use AT Command = 1208 + 1209 +== 5.1 Access AT Command == 1210 + 1211 +((( 1212 +RS485-BL supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to RS485-BL to use AT command, as below. 1213 +))) 1214 + 1215 +[[image:1654162355560-817.png]] 1216 + 1217 + 1218 +((( 1219 +In PC, User needs to set (% style="color:blue" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600**(%%) to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference: 1220 +))) 1221 + 1222 +[[image:1654162368066-342.png]] 1223 + 1224 + 1225 +((( 1226 +More detail AT Command manual can be found at [[AT Command Manual>>https://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]] 1227 +))) 1228 + 1229 + 1230 + 1231 +== 5.2 Common AT Command Sequence == 1232 + 1233 +=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) === 1234 + 1235 +If device has not joined network yet: 1236 + 1237 +(% class="box infomessage" %) 1238 +((( 1239 +**AT+FDR** 1240 +))) 1241 + 1242 +(% class="box infomessage" %) 1243 +((( 1244 +**AT+NJM=0** 1245 +))) 1246 + 1247 +(% class="box infomessage" %) 1248 +((( 1249 +**ATZ** 1250 +))) 1251 + 1252 + 1253 +If device already joined network: 1254 + 1255 +(% class="box infomessage" %) 1256 +((( 1257 +**AT+NJM=0** 1258 +))) 1259 + 1260 +(% class="box infomessage" %) 1261 +((( 1262 +**ATZ** 1263 +))) 1264 + 1265 + 1266 +=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) === 1267 + 1268 + 1269 +(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve 1270 + 1271 +(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode 1272 + 1273 +(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off 1274 + 1275 +(% style="background-color:#dcdcdc" %)**AT+DR=5** (%%)Set Data Rate 1276 + 1277 +(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds 1278 + 1279 +(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz 1280 + 1281 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server) 1282 + 1283 +(% style="background-color:#dcdcdc" %)**AT+RX2DR=5** (%%) Set RX2DR to match the downlink DR from server. see below 1284 + 1285 +(% style="background-color:#dcdcdc" %)**AT+DADDR=26** (%%) 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal. 1286 + 1287 +(% style="background-color:#dcdcdc" %)**ATZ** (%%) Reset MCU 1288 + 1289 + 1290 +(% style="color:red" %)**Note:** 1291 + 1292 +(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server. 1293 +2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting. 1294 +3. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means. 1295 +4. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5 1296 + 1297 +[[image:1654162478620-421.png]] 1298 + 1299 + 1300 += 6. FAQ = 1301 + 1302 +== 6.1 How to upgrade the image? == 1303 + 1304 +((( 1305 +The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to: 1306 +))) 1307 + 1308 +* ((( 1309 +Support new features 1310 +))) 1311 +* ((( 1312 +For bug fix 1313 +))) 1314 +* ((( 1315 +Change LoRaWAN bands. 1316 +))) 1317 + 1318 +((( 1319 +Below shows the hardware connection for how to upload an image to RS485-LN: 1320 +))) 1321 + 1322 +[[image:1654162535040-878.png]] 1323 + 1324 +**Step1:** Download [[flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]]. 1325 + 1326 +**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]]. 1327 + 1328 +**Step3: **Open flashloader; choose the correct COM port to update. 1329 + 1330 +((( 1331 +((( 1332 +(% style="color:blue" %) Hold down the PRO button and then momentarily press the RST reset button and the SYS led will change from OFF to ON, While SYS LED is RED ON, it means the RS485-LN is ready to be program. 1333 +))) 1334 +))) 1335 + 1336 + 1337 +[[image:image-20220602175818-12.png]] 1338 + 1339 + 1340 +[[image:image-20220602175848-13.png]] 1341 + 1342 + 1343 +[[image:image-20220602175912-14.png]] 1344 + 1345 + 1346 +**Notice**: In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is: 1347 + 1348 +[[image:image-20220602175638-10.png]] 1349 + 1350 + 1351 +== 6.2 How to change the LoRa Frequency Bands/Region? == 1352 + 1353 +User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download. 1354 + 1355 + 1356 +== 6.3 How many RS485-Slave can RS485-BL connects? == 1357 + 1358 +The RS485-BL can support max 32 RS485 devices. Each uplink command of RS485-BL can support max 16 different RS485 command. So RS485-BL can support max 16 RS485 devices pre-program in the device for uplink. For other devices no pre-program, user can use the [[downlink message (type code 0xA8) to poll their info>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]]. 1359 + 1360 + 1361 +== 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? == 1362 + 1363 +When user need to use with ChirpStack or TTI. Please set AT+RPL=4. 1364 + 1365 +Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]] 1366 + 1367 + 1368 += 7. Trouble Shooting = 1369 + 1370 +== 7.1 Downlink doesn’t work, how to solve it? == 1371 + 1372 +Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]] 1373 + 1374 + 1375 +== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? == 1376 + 1377 +It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]] 1378 + 1379 + 1380 += 8. Order Info = 1381 + 1382 +(% style="color:blue" %)**Part Number: RS485-LN-XXX** 1383 + 1384 +(% style="color:blue" %)**XXX:** 1385 + 1386 +* (% style="color:blue" %)**EU433**(%%): frequency bands EU433 1387 +* (% style="color:blue" %)**EU868**(%%): frequency bands EU868 1388 +* (% style="color:blue" %)**KR920**(%%): frequency bands KR920 1389 +* (% style="color:blue" %)**CN470**(%%): frequency bands CN470 1390 +* (% style="color:blue" %)**AS923**(%%): frequency bands AS923 1391 +* (% style="color:blue" %)**AU915**(%%): frequency bands AU915 1392 +* (% style="color:blue" %)**US915**(%%): frequency bands US915 1393 +* (% style="color:blue" %)**IN865**(%%): frequency bands IN865 1394 +* (% style="color:blue" %)**RU864**(%%): frequency bands RU864 1395 +* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865 1396 + 1397 += 9.Packing Info = 1398 + 1399 + 1400 +**Package Includes**: 1401 + 1402 +* RS485-LN x 1 1403 +* Stick Antenna for LoRa RF part x 1 1404 +* Program cable x 1 1405 + 1406 +**Dimension and weight**: 1407 + 1408 +* Device Size: 13.5 x 7 x 3 cm 1409 +* Device Weight: 105g 1410 +* Package Size / pcs : 14.5 x 8 x 5 cm 1411 +* Weight / pcs : 170g 1412 + 1413 += 10. FCC Caution for RS485LN-US915 = 1414 + 1415 +((( 1416 +Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment. 1417 +))) 1418 + 1419 +((( 1420 +This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. 1421 +))) 1422 + 1423 +((( 1424 + 1425 +))) 1426 + 1427 +((( 1428 +**IMPORTANT NOTE:** 1429 +))) 1430 + 1431 +((( 1432 +**Note: **This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: 1433 +))) 1434 + 1435 +((( 1436 +—Reorient or relocate the receiving antenna. 1437 +))) 1438 + 1439 +((( 1440 +—Increase the separation between the equipment and receiver. 1441 +))) 1442 + 1443 +((( 1444 +—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. 1445 +))) 1446 + 1447 +((( 1448 +—Consult the dealer or an experienced radio/TV technician for help. 1449 +))) 1450 + 1451 +((( 1452 + 1453 +))) 1454 + 1455 +((( 1456 +**FCC Radiation Exposure Statement:** 1457 +))) 1458 + 1459 +((( 1460 +This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment.This equipment should be installed and operated with minimum distance 20cm between the radiator& your body. 1461 +))) 1462 + 1463 + 1464 += 11. Support = 1465 + 1466 +* ((( 1467 +Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 1468 +))) 1469 +* ((( 1470 +Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]. 1471 +)))
- 1654160691922-496.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +109.3 KB - Content
- 1654162355560-817.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +670.0 KB - Content
- 1654162368066-342.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +192.9 KB - Content
- 1654162478620-421.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +158.9 KB - Content
- 1654162535040-878.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +670.0 KB - Content
- image-20220602165351-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +10.6 KB - Content
- image-20220602165351-7.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +19.3 KB - Content
- image-20220602171200-8.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +276.1 KB - Content
- image-20220602171200-9.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +10.0 KB - Content
- image-20220602175638-10.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +85.5 KB - Content
- image-20220602175743-11.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +85.5 KB - Content
- image-20220602175818-12.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +102.5 KB - Content
- image-20220602175848-13.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +250.9 KB - Content
- image-20220602175912-14.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +176.1 KB - Content
- image-20220606110929-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +13.9 KB - Content