What is the history of Ethernet/IP?

Bringing a shared industrial data model to Ethernet
EtherNet/IP uses Ethernet infrastructure to let industrial devices communicate through a common language. Its history brings together two developments: the standardization of Ethernet and the maturation of CIP-based industrial communication. ODVA dates the introduction of EtherNet/IP to 2001; Ethernet itself has a much longer history.
Editor's note: Ethernet's origin and EtherNet/IP's introduction are different milestones. The key dates are 1973 for Ethernet's origins, 1983 for its IEEE standardization, 1995 for ODVA's founding and 2001 for EtherNet/IP's introduction. Development work, a technology's introduction and the publication of a technical paper should not be treated as the same event.
1973 and 1983: the foundations of a common network
On May 22, 1973, Xerox PARC researcher Bob Metcalfe described the Ethernet approach he developed with David Boggs in an internal memo. Its purpose was communication between computers on a local network. Ethernet's adoption as an IEEE standard in June 1983 helped manufacturers develop products around a common networking technology.
These events did not yet mark the arrival of EtherNet/IP. The distinction between Ethernet and EtherNet/IP is the separation between infrastructure and industrial application services. Within a layered communication architecture, Ethernet provides lower-layer data transport; it does not, by itself, define what industrial device data means.
The 1990s: DeviceNet, ControlNet and the CIP foundation
Industrial networks needed more than the ability to move bits. Controllers needed to identify drives, access parameters and interpret I/O data. The CIP application model used in the Rockwell-originated DeviceNet and ControlNet technologies provided the foundation for EtherNet/IP. Known today as the Common Industrial Protocol, CIP provides a shared structure of objects, services and device profiles.
A media-independent application model preserves similar industrial concepts across different networks. This makes the protocol's operating principles easier to understand across the family; it does not mean that DeviceNet, ControlNet and EtherNet/IP devices can connect directly through the same cable.
1995: ODVA is founded
ODVA was founded in 1995. Working with member companies, it develops specifications for CIP and related network technologies and supports interoperability. This gave the technology a development framework extending beyond one device manufacturer's product schedule. Conformance testing and standards help manufacturers implement common requirements; they do not imply that every product supports every optional function.
2001: CIP meets Ethernet, TCP and UDP
EtherNet/IP was introduced in 2001. An October 2001 technical paper by Rockwell Automation's Paul Brooks describes the work undertaken by ODVA and ControlNet International at that time. The approach placed the existing CIP model over standard Ethernet and the internet protocol suite. The IP in the technology's name means Industrial Protocol; the network-layer IP used for communication means Internet Protocol.
This architecture brought control, configuration and data collection onto a common network structure. Explicit request/reply transactions over TCP and implicit I/O exchange over UDP are fundamental examples. The relationship between message types and ports helps explain how these uses differ.
Why switched Ethernet mattered
On early shared, half-duplex Ethernet networks, collisions and retransmissions could make delivery times variable. Switched, full-duplex links eliminated this type of collision. Queuing, traffic load and device processing times still affect latency and update performance, however.
Using standard Ethernet does not, by itself, guarantee a particular response time. Industrial applications require network architecture, device capacity and cabling and connections to be assessed together. EtherNet/IP's development builds on the use of standard network components while addressing these engineering requirements.
Later developments: beyond basic control data
The CIP family expanded over time to include time synchronization through CIP Sync, motion control through CIP Motion, functional safety through CIP Safety and energy information through CIP Energy. CIP Security added cybersecurity services. Functional safety and cybersecurity serve different purposes; neither replaces the other. Appropriate network security measures must also be planned.
ODVA's 30th-anniversary review in 2025 also addressed developments in process device profiles and security capabilities. Application areas have consequently expanded beyond conventional machine I/O toward richer device information and process integration. In automation systems, available capabilities depend on the functions supported by the actual devices; an EtherNet/IP label alone is insufficient.
What this history means for an existing plant
Suppose an EtherNet/IP drive is being added to an older machine using DeviceNet. Familiar CIP concepts may make the project easier to understand. Nevertheless, device and system compatibility, controller communication capabilities and any need for a gateway must be assessed separately. Connecting the old network cable to a new Ethernet port is not a migration method.
During configuration, verify I/O mappings, data lengths, scaling and update intervals. Use engineering tools to check device definitions and monitor diagnostic information during commissioning. Apply the same approach when assessing future developments: a shared protocol family can simplify migration, but application validation is still required.
Related topics
Ethernet FAQ / Advantages and limitations / Comparison with Modbus TCP / Standards and conformance