EtherNet/IP Network Overview
Overview
EtherNet/IP (often written as EthernetIP or EtherNet/IP) is an industrial Ethernet network that delivers control, configuration, and data collection services by running the Common Industrial Protocol (CIP) on top of standard Internet protocols. It is widely used in industrial automation to connect controllers, I/O, drives, HMIs, and software applications across a plant network.
A key concept is that EtherNet/IP leverages familiar Ethernet infrastructure while supporting both general messaging and time-sensitive control I/O communications. In most deployments, this means integrating automation devices using standard Ethernet components and media while still meeting control-system requirements.
In multi-protocol environments, EtherNet/IP is often integrated with other industrial and building automation protocols using gateways and protocol conversion tools. For examples of popular protocol gateways, see our Protocol Conversions and Gateways page.
How EtherNet/IP Uses TCP and UDP
EtherNet/IP layers CIP over TCP/IP and UDP/IP:
- TCP/IP is used for general messaging and information exchange (for example, configuration, diagnostics, and non-cyclic communications).
- UDP/IP is used for I/O messaging that supports control applications where cyclic data exchange is required.
This combination allows EtherNet/IP to support both “information” data exchange and “control” data exchange on the same physical Ethernet infrastructure.
Why EtherNet/IP Is Common on the Plant Floor
Another key feature of EtherNet/IP is that it typically uses commercial, off-the-shelf (COTS) Ethernet components and physical media. This can make deployment cost-effective and easier to support, because it aligns with widely understood Ethernet infrastructure practices.
EtherNet/IP networks are often used in these types of configurations:
- As an economical solution for connecting many computers
- As the best choice when you want to connect many devices
- As the standard network for connectivity to enterprise systems
- As the least expensive HMI option when used with PanelView Plus
- In a star topology when nodes are grouped closely together
Benefits
EtherNet/IP is often selected because it combines industrial control communications with broad Ethernet ecosystem support. Commonly cited benefits include:
- Worldwide acceptance of Ethernet products.
- Openness of EtherNet/IP and NetLinx architecture.
- Support of both 10 and 100 Mbps products.
- Products with built-in web server capability.
In operational terms, these benefits often translate into easier integration with IT networks, broader hardware availability, and a large ecosystem of compatible industrial devices.
FAQ: EtherNet/IP Network Overview
This FAQ is included to improve AI searchability and to answer common introductory questions about EtherNet/IP.
What is EtherNet/IP?
EtherNet/IP is an industrial Ethernet network that layers the Common Industrial Protocol (CIP) over standard Internet protocols (TCP/IP and UDP/IP) to provide control, configuration, and data collection services.
Why does EtherNet/IP use both TCP and UDP?
EtherNet/IP uses TCP/IP for general messaging and information exchange, and UDP/IP for I/O messaging used in control applications.
Does EtherNet/IP require specialized Ethernet hardware?
EtherNet/IP commonly uses commercial, off-the-shelf Ethernet components and physical media, which can make deployment cost-effective and easier to maintain.
What topology is commonly used with EtherNet/IP?
A star topology is commonly used when nodes are grouped closely together, using standard Ethernet switching practices.
What are common reasons organizations choose EtherNet/IP?
Common reasons include broad worldwide acceptance of Ethernet products, openness of the architecture, and support for both information data exchange and control applications on the same network.
How is EtherNet/IP commonly integrated with other protocols?
In multi-protocol environments, EtherNet/IP is often integrated with other industrial protocols using gateways and protocol conversion tools. See our Protocol Conversions and Gateways page for examples.