Yaskawa EtherCAT Communication Setup Guide for Robotics
Overview: EtherCAT (Ethernet for Control Automation Technology) is a high-performance industrial Ethernet protocol widely used in robotics and motion control. This article provides a step-by-step guide to establishing EtherCAT communication between Yaskawa robots and PLCs, covering hardware installation, parameter configuration, and troubleshooting tips.
1. Hardware Installation
Before configuring the software, ensure the physical components are correctly installed. The EtherCAT communication card must be securely mounted in the robot controller or PLC rack. Follow these steps:
- Power off all devices and follow proper lockout/tagout procedures.
- Insert the EtherCAT option card into the designated slot on the Yaskawa controller (e.g., MP3300 or MP2310iec).
- Secure the card with screws and ensure it is firmly seated.
- Connect the EtherCAT cable (CAT5e or higher, shielded) from the robot controller to the PLC master port.
- If using a daisy-chain topology, connect additional slave devices in series and ensure the last device has a termination resistor or enable its internal termination.
Typical network topology: PLC (Master) → Robot Controller (Slave) → I/O Modules (Slaves). Always use industrial-grade Ethernet cables and avoid routing near high-voltage lines to minimize noise.
| Component | Specification | Notes |
|---|---|---|
| EtherCAT Master | PLC with EtherCAT port (e.g., Siemens S7-1200, Beckhoff CX series) | Supports CoE (CANopen over EtherCAT) |
| EtherCAT Slave | Yaskawa robot controller with EtherCAT option card | Firmware must support EtherCAT |
| Cable | Shielded CAT5e/6, 100 m max between nodes | Use RJ45 connectors with metal housing |
| Power Supply | 24 V DC for I/O modules if used | Separate from motor power |
2. Parameter Configuration
After hardware setup, configure the communication parameters on both the master and slave sides. The exact steps may vary depending on the PLC brand and Yaskawa controller model, but the general principles remain consistent.
2.1 PLC (Master) Configuration
In the PLC engineering software (e.g., TIA Portal, TwinCAT, or Sysmac Studio), add the Yaskawa robot as an EtherCAT slave device. You will need the ESI (EtherCAT Slave Information) XML file provided by Yaskawa. Import this file into the configuration tool to recognize the device.
Key settings:
- Slave Address: Set a unique station alias or use the default (usually 0).
- PDO Mapping: Map the process data objects (PDOs) for cyclic data exchange. Typical mappings include control word, target position, status word, and actual position.
- Sync Manager: Configure sync managers for process data and mailbox communication.
- Cycle Time: Set the EtherCAT cycle time (e.g., 1 ms, 2 ms) according to your application requirements. Shorter cycles improve responsiveness but increase CPU load.
2.2 Yaskawa Robot (Slave) Configuration
On the Yaskawa robot controller, access the parameter settings via the teach pendant or MotoAdmin software. Navigate to the communication or fieldbus menu and set the following:
- Communication Protocol: Select EtherCAT (sometimes labeled as “ECAT” or “EtherCAT Slave”).
- Node ID: Assign a unique node ID (1–65535) that matches the master configuration.
- Data Size: Define the input/output data sizes in bytes. Common sizes are 32 bytes in/out for basic motion control.
- Watchdog Timer: Set a reasonable timeout (e.g., 100 ms) to detect communication loss.
- Operational Mode: Choose the appropriate mode (e.g., CSP – Cyclic Synchronous Position, or CSV – Cyclic Synchronous Velocity).
After saving parameters, reboot the controller to apply changes.
3. Network Commissioning and Testing
Once both sides are configured, power up the system and check the EtherCAT status LEDs. The master should detect all slaves and transition through INIT, PREOP, SAFEOP, to OP (Operational) state. Use the PLC diagnostic tools to verify:
- All slaves are present and in OP state.
- No lost frames or CRC errors (check counters).
- PDO data is updating correctly (monitor live values).
Perform a simple test: from the PLC, send a control command (e.g., enable drive) and observe the robot’s response. Gradually increase motion complexity, testing jogging, homing, and programmed paths.
Important: Always verify emergency stop functionality over EtherCAT. The safety signals (STO, SS1) may require separate wiring or use FSoE (Fail Safe over EtherCAT) if supported.
4. Troubleshooting Common Issues
Even with careful setup, issues can arise. Here are some common problems and solutions:
| Symptom | Possible Cause | Solution |
|---|---|---|
| Slave not found or stays in INIT | Cable fault, wrong topology, or missing termination | Check cables, ensure last slave has termination, verify power |
| Slave in SAFEOP but not OP | PDO mapping mismatch or watchdog settings | Compare PDO sizes and mappings on both sides; adjust watchdog |
| Intermittent communication loss | EMI noise, loose connectors, or long cable runs | Use shielded cables, separate from power lines, reduce cycle time if possible |
| Robot does not respond to commands | Incorrect control word or mode setting | Verify control word sequence (enable, mode select, start) and mode parameter |
5. Best Practices for Reliable EtherCAT Networks
To ensure long-term stability, follow these guidelines:
- Use a dedicated network for EtherCAT; do not mix with office Ethernet.
- Implement ring redundancy if high availability is required (most Yaskawa controllers support cable redundancy).
- Regularly update firmware and ESI files to the latest versions.
- Document all node IDs, PDO mappings, and network topology for future maintenance.
- Monitor network load; keep it below 80% of maximum bandwidth.
By following this guide, you can achieve a robust EtherCAT connection between Yaskawa robots and PLCs, enabling high-speed, deterministic control for demanding automation tasks.
