EtherNet/IP to CANopen Gateway for Rockwell PLC Integration
In modern manufacturing, mixed production lines often combine heavy machinery and textile equipment, each relying on different communication protocols. A common challenge arises when Rockwell PLCs using EtherNet/IP need to interface with CANopen-based encoders that follow the CiA 406 profile. Without a proper bridge, position data remains isolated, forcing manual intervention and causing safety delays.
The Role of a Protocol Gateway
An EtherNet/IP to CANopen gateway acts as a translator between these two worlds. On one side, it functions as an EtherNet/IP slave, seamlessly integrating into the Rockwell PLC network. On the other, it operates as a CANopen master, actively polling encoders for position feedback—including revolutions, angle, and linear displacement. This gateway supports full parameter mapping of the CiA 406 profile, achieving real-time synchronization with micron-level resolution.
Key Hardware Features: DIN-rail mounting, 24V DC power supply, dual Ethernet ports, and dual CAN ports with galvanic isolation. Configuration is done via PC software by importing the encoder’s EDS file, mapping position values (e.g., 0x6064) and control words (0x6040) in the object dictionary, and setting the EtherNet/IP IP address with I/O instance sizes.
Configuration and Integration Steps
Integrating the gateway involves a few straightforward steps:
- Import the encoder’s EDS file into the gateway configuration tool.
- Map the required CANopen objects (position, control word, status) to the gateway’s internal memory.
- Define the EtherNet/IP connection parameters: IP address, input/output assembly instances, and data sizes.
- Add the gateway’s EDS file to the Rockwell PLC project, allowing it to recognize the device as a standard I/O module.
Once configured, the PLC can read encoder data as if it were local registers, enabling direct use in motion control, tension loops, and position limiting.
| Parameter | Typical Value | Notes |
|---|---|---|
| CANopen Baud Rate | 250 kbps, 500 kbps, 1 Mbps | Select based on cable length and node count |
| EtherNet/IP Data Size | Up to 512 bytes input / 512 bytes output | Configurable per application needs |
| Polling Cycle | 1 ms to 100 ms | Adjustable for real-time requirements |
| Alarm Response Time | < 5 ms | From encoder fault to PLC flag |
| Power Supply | 24V DC (±20%) | Typical industrial control voltage |
Operational Benefits and Real-World Impact
The gateway breaks down protocol barriers, allowing the PLC to directly access real-time encoder positions. This data is used for travel limits in heavy machinery and closed-loop tension control in textile lines. Remote configuration becomes possible: the PLC can modify the CANopen master’s polling cycle, heartbeat settings, and even trigger encoder zero-point calibration via the gateway.
Safety is enhanced through proactive alarming. If position deviation exceeds limits or an encoder disconnects, the gateway immediately sets an alarm flag in the PLC, with a response time under 5 milliseconds. This shifts safety from reactive to preventive.
Case Example: In a mixed heavy machinery and textile line, the gateway replaced hardwired switch signals with transparent data flow over EtherNet/IP. Changeover time dropped from 2 hours to 15 minutes, and unplanned downtime decreased by 70%.
Technical Considerations for Deployment
When selecting a gateway, ensure it supports the CiA 406 device profile for encoders, as this standardizes the object dictionary layout. The gateway should handle both rotary and linear encoders, with scalable I/O sizes to accommodate multiple axes. Look for features like automatic baud rate detection, error logging, and web-based diagnostics to simplify troubleshooting.
Network topology matters: the dual Ethernet ports often support daisy-chain or ring topologies, reducing cabling costs. The CAN side should allow flexible termination and bus length up to several hundred meters at lower baud rates.
Future-Proofing with Protocol Converters
As industrial automation evolves, the need to connect legacy CANopen devices to modern EtherNet/IP networks grows. A gateway not only solves immediate integration issues but also preserves investments in existing sensors and actuators. It enables gradual migration to unified networks without replacing all field devices.
For system integrators and plant engineers, mastering such gateways is essential. They provide a cost-effective path to Industry 4.0 by making data from all devices accessible for analytics, predictive maintenance, and flexible manufacturing.
Pro Tip: Always test the gateway with actual encoder models in a lab setup before deployment. Verify timing behavior under maximum node count and data load to ensure deterministic performance.
In summary, an EtherNet/IP to CANopen gateway is more than a simple converter—it’s a critical enabler for mixed-protocol production lines. By allowing Rockwell PLCs to communicate natively with CANopen encoders, it streamlines operations, enhances safety, and significantly cuts downtime.
