EtherCAT to EtherNet/IP Gateway for Rockwell & Omron PLC Integration
Integrating devices from different industrial Ethernet protocols is a common challenge in modern automation. When a production line uses Rockwell ControlLogix PLCs on EtherNet/IP and Omron NJ-series controllers with EtherCAT servo drives, the inherent differences in clock synchronization and frame formats make direct communication impossible. Traditional workarounds like adding motion modules to the PLC or replacing servo drives are costly and often sacrifice the high-speed, deterministic performance of EtherCAT. A dedicated protocol conversion gateway offers a more elegant solution by acting as a slave on both networks, enabling transparent data exchange without modifying existing PLC programs.
How the Gateway Architecture Works
The gateway functions as a dual-network slave: on the EtherCAT side, it appears as an EtherCAT slave device with a standard ESI file; on the EtherNet/IP side, it presents itself as a generic Ethernet module with configurable assemblies. This design eliminates the need for either PLC to act as a master for the other protocol. The gateway handles all protocol translation internally, mapping I/O data between the two networks with minimal latency.
In a typical setup, the gateway supports up to 500 bytes of I/O data in each direction. The EtherNet/IP side uses Assembly instances (e.g., 100 for output, 101 for input) to exchange data with a Rockwell ControlLogix PLC via a 1756-EN2T module. The EtherCAT side uses Process Data Objects (PDOs) to communicate with an Omron NJ501-1500 motion controller, which in turn controls R88D-KN15H-ECT servo drives with distributed clocks (DC).
Key Performance Metrics
| Parameter | Value |
|---|---|
| Forwarding Latency (E/IP to E/CAT) | 250 µs (measured) |
| Max I/O Size per Direction | 500 bytes |
| EtherCAT Cycle Time | 1 ms (servo loop) |
| EtherNet/IP RPI (optimized) | 2 ms |
| Power Supply | 24 VDC, 3.5 W |
| Operating Temperature | -25°C to +55°C |
Data Mapping Strategy for Bidirectional Control
Effective data mapping is critical for real-time motion control. The gateway’s internal mapping table links EtherNet/IP assemblies to EtherCAT PDOs, ensuring consistent data exchange every cycle.
From EtherNet/IP to EtherCAT (Commands): The ControlLogix writes a 32-byte output assembly containing spindle speed, feed override, and clamping pressure. This data is mapped to EtherCAT PDO 0x1600, which the Omron master reads directly. The gateway updates this data within the 1 ms EtherCAT cycle, so the servo drive receives new setpoints without delay.
From EtherCAT to EtherNet/IP (Status): The servo drive’s status word, actual position, torque, and alarm codes (64 bytes total) are mapped to EtherNet/IP Assembly 101. The ControlLogix reads this assembly at a configured RPI, making the data available for HMI displays and MES integration. This bidirectional flow enables closed-loop control across the two networks.
Step-by-Step Configuration Guide
Setting up the gateway involves configuration on both PLC platforms and the gateway itself. Here’s a practical walkthrough based on a real-world deployment.
Omron Sysmac Studio (EtherCAT Side)
- Import the gateway’s ESI file into the EtherCAT device library.
- Drag the gateway onto the EtherCAT bus, assign station alias (e.g., Node 5), and set DC mode with a cycle time of 500 µs (or 1 ms depending on system requirements).
- Create a virtual axis (e.g., GateWay_Axis) and link control/status words (0x6040/0x6041) to the corresponding PDOs.
- In the motion program, use standard PLCopen blocks like MC_MoveVelocity to command the virtual axis; the gateway forwards the velocity setpoint to the actual servo.
Rockwell Studio 5000 (EtherNet/IP Side)
- Register the gateway’s EDS file using the EDS Hardware Installation Tool.
- Add a new module to the Ethernet tree: choose “Generic Ethernet Module”, set Assembly Instance 100 (Output) and 101 (Input), and configure the RPI (start with 4 ms, then optimize to 2 ms).
- Create controller-scoped tags: Gateway_In (SINT array, 64 bytes) and Gateway_Out (SINT array, 32 bytes).
- Use COP instructions to copy data between the gateway tags and user-defined structures for alarm handling and MES communication.
Gateway Configuration Tool
- Launch the vendor’s configuration software and verify that the data lengths on both sides match the PLC settings.
- Enable “Distributed Clock” if the EtherCAT master uses DC synchronization.
- Use the “Auto-Mapping” feature to align assemblies with PDOs, then download the configuration and reboot the gateway.
- Monitor the diagnostic page: both network port counters should show zero error frames under normal operation.
Troubleshooting Common Integration Issues
Even with careful configuration, real-world installations can encounter problems. Here are three typical issues and their solutions.
Synchronization Jitter Causing Position Errors
Symptom: Occasional overshoot or undershoot of 0.01 mm during machining.
Root Cause: The EtherNet/IP RPI was left at the default 10 ms, while the EtherCAT cycle was 1 ms, causing uneven velocity command updates.
Solution: Reduce the ControlLogix RPI to 2 ms and enable “buffer interpolation” in the gateway. This smoothed out the command updates and reduced jitter to less than 1 µm.
Network Overload from Vision Traffic
Symptom: EtherNet/IP timeouts occurred when a vision camera triggered, sending burst image data.
Root Cause: The camera and PLC shared the same switch without traffic segregation.
Solution: Configure VLANs on the managed switch: assign the camera to a separate VLAN with 1 Gbps uplink. Additionally, enable QoS Priority 6 on the gateway for EtherNet/IP traffic. This eliminated packet loss.
Common-Mode Noise from VFD
Symptom: The gateway’s EtherCAT status LED flashed red intermittently when machining aluminum parts.
Root Cause: Common-mode noise from the spindle VFD coupled into the Ethernet cable.
Solution: Replace the cable with shielded CAT6a and use proper grounding clamps. Install a common-mode choke on the gateway’s 24 VDC power supply line. The fault cleared immediately.
Benefits of a Dual-Slave Gateway Approach
This architecture offers several advantages over alternative methods:
- Preserves existing investments: No need to replace servo drives or add expensive motion modules to the PLC.
- Maintains real-time performance: The 250 µs forwarding latency and DC synchronization ensure that the 1 ms EtherCAT cycle is not compromised.
- Simplifies programming: Both PLCs operate as if they are communicating with native devices; no complex protocol handling in ladder logic.
- Scalable and flexible: The same gateway can be used for various combinations of EtherCAT and EtherNet/IP devices, making it a reusable solution for mixed-protocol lines.
In high-precision applications such as aerospace component machining, the ability to integrate Omron’s high-speed EtherCAT servos with a Rockwell-dominated plant network without sacrificing performance is a significant competitive advantage. The gateway’s robust design, with industrial temperature range and low power consumption, makes it suitable for demanding factory environments.
Conclusion: A protocol conversion gateway configured as a slave on both EtherCAT and EtherNet/IP networks provides a seamless, low-latency bridge between Rockwell and Omron systems. With bidirectional 500-byte mapping, 250 µs forwarding delay, and distributed clock support, it meets the stringent requirements of high-speed motion control. This approach offers a proven, low-risk template for integrating multi-protocol equipment in modern smart factories.
