Fieldbus & networking
EtherNet/IP
Industrial Ethernet protocol built on CIP that links robot controllers to PLCs, I/O blocks, and HMIs over standard Ethernet cabling.
EtherNet/IP wraps the Common Industrial Protocol in standard TCP/IP and UDP frames, so a robot controller can share the same switch infrastructure as PLCs, drives, and HMIs. Most FANUC, ABB, and Yaskawa controllers support it as a built-in option or factory-installed card.
Cell integrators use it for two jobs: explicit messaging for configuration and diagnostics, and implicit I/O for real-time bit and register exchange with a PLC. Rockwell Automation ControlLogix and CompactLogix processors treat the robot as a generic Ethernet module or add-on profile.
Because it rides on commodity Ethernet, EtherNet/IP scales well from a single cell to a plant-wide network. That also means it competes with other traffic for bandwidth if VLANs aren't set up correctly.
Related integrations
Common questions
- What does EtherNet/IP do?
- Industrial Ethernet protocol built on CIP that links robot controllers to PLCs, I/O blocks, and HMIs over standard Ethernet cabling.
- What does EtherNet/IP work with?
- It works with Allen Bradley ControlLogix, Rockwell CompactLogix, FANUC R 30iB, ABB IRC5, Yaskawa DX200.
- What should I watch for with EtherNet/IP?
- Requires proper VLAN segmentation to keep I/O traffic deterministic. Add-on profiles differ by controller vendor and firmware version. Explicit messaging adds latency compared to implicit I/O.