Profinet to EtherCAT Gateway for Servo Synchronization
In modern high-speed packaging lines, achieving tight synchronization between multiple servo-driven stations is critical for throughput and product quality. A common challenge arises when the central PLC uses Profinet while the servo drives communicate over EtherCAT. This is where a Profinet to EtherCAT gateway becomes essential. It bridges the two industrial Ethernet protocols, enabling seamless data exchange and real-time motion control. This article explores how to configure such a system, using a typical setup with a Siemens PLC and Yaskawa servo drives, and provides practical tips for commissioning.
Hardware Configuration
The core components of the system include a central controller, a protocol gateway, and the servo drives. A typical hardware setup might look like this:
| Component | Role | Example Model |
|---|---|---|
| PLC | Main logic controller, Profinet master | Siemens S7-1200 |
| Protocol Gateway | Converts Profinet to EtherCAT and vice versa | Anybus X-gateway, Hilscher NT 100, or equivalent |
| Servo Drives | EtherCAT slave devices, execute motion commands | Yaskawa Sigma-7 series with EtherCAT |
The gateway features a Profinet interface on one side and an EtherCAT interface on the other. It acts as a Profinet device (slave) to the PLC and as an EtherCAT master to the servo drives. This allows the PLC to treat the entire EtherCAT network as a single I/O device, simplifying configuration. The gateway handles the cyclic data exchange, mapping Profinet telegrams to EtherCAT process data objects (PDOs).
Software Configuration Steps
Proper software setup is crucial for reliable communication. The following steps outline the process using Siemens TIA Portal and the gateway’s configuration tool.
1. PLC Programming (TIA Portal)
- Create a new project and add the S7-1200 CPU.
- Install the GSDML file for the Profinet to EtherCAT gateway. This file describes the gateway’s Profinet capabilities and I/O data structure.
- Add the gateway to the Profinet network and assign it a device name and IP address.
- Configure the I/O data sizes (input/output bytes) according to the number of servo axes and required control/status words.
2. EtherCAT Network Configuration
- Use the gateway’s proprietary configuration software (often web-based or a dedicated tool) to scan the EtherCAT bus.
- Import the ESI (EtherCAT Slave Information) files for the servo drives. Critical: The ESI file must match the exact drive model and firmware version. Using a similar but not identical file can cause communication failures.
- Assign EtherCAT addresses (station aliases) to each drive and configure the PDO mapping. Typically, you’ll map control word, target position, target velocity, and status word, actual position, actual velocity.
- Set the EtherCAT cycle time (e.g., 1 ms or 2 ms) based on the motion control requirements.
3. Servo Drive Parameterization
- Set basic parameters such as motor type, encoder resolution, and limits via the drive’s keypad or software (e.g., SigmaWin+).
- Configure the EtherCAT communication settings: station alias, sync manager settings, and PDO assignments must match the gateway configuration.
- Tune the servo loops (current, velocity, position) for optimal performance. This may require running an auto-tuning routine and then fine-tuning manually.
Communication and Data Exchange
Once configured, the data flow is straightforward. The PLC sends motion commands (target position, velocity, acceleration) to the gateway’s output area via Profinet. The gateway converts these values into EtherCAT PDOs and transmits them to the respective servo drives during each EtherCAT cycle. Simultaneously, the drives return actual position, velocity, torque, and status bits, which the gateway places into its input area for the PLC to read.
The gateway typically supports acyclic data exchange as well (via Profinet record data or EtherCAT SDO) for parameter read/write and diagnostics. This is useful for changing drive parameters on the fly or retrieving detailed fault information.
Achieving Multi-Station Synchronization
In a packaging line, multiple stations (filling, capping, labeling) must operate in perfect harmony. The PLC orchestrates this by sending coordinated motion commands. For example, when a bottle enters the filling station, the PLC commands the filler servo to follow a specific cam profile while the capper and labeler servos wait for their triggers. The gateway ensures that these commands reach all drives with minimal jitter, thanks to EtherCAT’s distributed clock mechanism.
Real-time feedback allows the PLC to monitor each axis. If a drive reports a following error or a fault, the PLC can immediately stop the entire line or take corrective action. This closed-loop control is essential for high-speed applications where a small misalignment can cause product damage or machine jams.
Common Pitfall: ESI File Mismatch
A frequent issue during commissioning is that the gateway cannot find the EtherCAT slaves even though they are physically connected. The root cause is often an incorrect ESI file. The ESI file contains the device identity (vendor ID, product code, revision). If any of these do not match the actual drive, the EtherCAT master will reject the slave. Always obtain the exact ESI file from the drive manufacturer’s website or support, matching the model and firmware version.
Benefits of Using a Protocol Gateway
- Flexibility: Allows mixing Profinet and EtherCAT devices without replacing existing equipment.
- Performance: Modern gateways support cycle times down to 250 µs, suitable for demanding motion control.
- Simplified Integration: The PLC sees the gateway as a single Profinet node, hiding the complexity of the EtherCAT network.
- Diagnostics: Many gateways provide web-based diagnostics, showing network status, error counters, and I/O data monitoring.
Conclusion
A Profinet to EtherCAT gateway is a powerful tool for integrating high-performance servo drives into a Profinet-based control system. By following the correct hardware and software configuration steps, and paying close attention to details like ESI file matching, engineers can achieve reliable, synchronized motion across multiple stations. This approach not only preserves existing PLC investments but also leverages the speed and precision of EtherCAT for demanding automation tasks.
