PART 01 Initial Product Introduction
EtherCAT splitters are suitable for multi-axis complex equipment and production line networking applications, where the network topology is arranged in a star configuration. They can be cascaded within the address range that the EtherCAT host can handle, enabling flexible cabling solutions.
PART 02 Application Examples
1. The main station is MC532CS
1. Hardware wiring:
Connect the EtherCAT port of the MC532CS to the IN1 port of the RYEC-JC03; connect the X2 port of the RYEC-JC03 to the L7EC servo module; connect the X3 port of the RYEC-JC06 to the IN1 port of the RYEC-JC06; connect the X2-X6 ports of the RYEC-JC06 to the L7EC servo module and the R2 series IO module respectively; as shown in the figure below:
2. XML file for installing the branch unit:
Open LeadSys Studio software, click "Menu Bar - Tools - Device Repository" in sequence, click "Install" in the pop-up dialog box, locate the brancher XML file, select it and click Open, as shown in the following figure:
You can search for the added XML files in the device repository, as shown in the following image:
3. Add an EtherCAT slave:
1) Manual addition: Create a new project using LeadSys software, double-click "Communication Configuration", and manually add EtherCAT slave devices in the "EtherCAT" configuration, as shown in the following figure:
2) Automatic Scan: Power on the test equipment, create a new project using LeadSys software and connect it to the PLC. Right-click "EtherCAT_Master_Leadshine_A" and select "Scan Device", as shown in the following figure:
Copy the scanned EtherCAT slave devices to the project. You can view the slave device configuration status in the device tree on the left, as shown in the following figure:
4. Configure EtherCAT slaves to run in "Alias Mode": 1) Configure slave aliases: After scanning for EtherCAT slave devices in 5.1.3, select the EtherCAT slaves one by one, modify the alias address, and then click "Assign Address". After modifying the alias, you need to power off and restart the device, as shown in the figure below:
2) Configure all EtherCAT slaves to run in "Alias Mode": Double-click to open "EtherCAT_Master_Leadshine_A", select the "Overview" interface, select "Alias Mode", and then recompile the project, as shown in the following figure:
5. Program Execution: Click "Login" to download the project to the PLC and view the current EtherCAT bus execution results, as shown in the following figure:
6. Disconnect a branch network cable of the splitter: When the EtherCAT bus is running normally, disconnect the X4 branch network cable of RYEC-JC06 and check the operating status of other EtherCAT slaves, as shown in the figure below:
2. The main station is DMC-E5032
1. Hardware wiring:
Connect the EtherCAT port of the DMC-E5032 to the IN1 port of the RYEC-JC03; connect the X2 port of the RYEC-JC03 to the L7EC servo module; connect the X3 port of the RYEC-JC06 to the IN1 port of the RYEC-JC06; connect the X2-X6 ports of the RYEC-JC06 to the L7EC servo module and the R2 series IO module respectively; as shown in the figure below:
2. Scan EtherCAT slave stations:
Open the Motion control card, right-click on "EtherCATSuite Master Unit" in the EtherCAT device tree, and click "Scan Devices," as shown in the image below:
The scan is complete, as shown in the image below:
3. Disconnect the network cable of a branch of the splitter:
When the EtherCAT bus is running normally, disconnecting the X4 branch network cable of RYEC-JC06 will allow other branch EtherCAT slave stations to continue operating normally without being affected.
PART 03 Product Features
1. Achieve flexible cabling
The splitter supports star network connections and cascading functionality with no limit on the number of cascaded nodes;
2. Improve system stability and reduce maintenance costs.
If the EtherCAT bus is operating normally, and a branch of the splitter suddenly fails and disconnects, other branch devices can continue to operate normally. Once the fault is resolved, the faulty branch device can be restored to operation.
3. Typical network topology is as follows:
END
