The Essential Guide to the ODVA EtherNet/IP Protocol

The ODVA EtherNet/IP Protocol represents a cornerstone in the realm of industrial automation, serving as a pivotal means for integrating Ethernet connectivity with precision-engineered network topology options. Its adherence to IEEE Ethernet standards not only broadens the choice of network interface speeds but also ensures a flexible architecture that aligns with contemporary Ethernet installation practices.

Beginning with an insight into the EtherNet/IP Protocol to OSI model mapping, this guide elaborates on the operational intricacies that make the EtherNet/IP Protocol an exemplary model in the automation sector, including EtherNet/IP Encapsulation Protocol, Explicit and Implicit Messaging, and the objects required for implementation. As an industrial IoT protocol, the EtherNet/IP Protocol enables seamless connectivity between field devices and enterprise systems over standard Ethernet infrastructure.

Key Features of the EtherNet/IP Protocol

Exploring the robust features of the ODVA EtherNet/IP Protocol reveals why it stands out as a preferred choice in industrial automation. Here, we delve into the key features that underpin its functionality and widespread adoption:

Common Interface Protocol (CIP):

The EtherNet/IP Protocol runs ODVA's CIP protocols on its application layers. As discussed earlier in our article, CIP is a powerful and versatile communication protocol that is inspired by an object-oriented design methodology. CIP over Ethernet is the defining characteristic of the EtherNet/IP Protocol — it enables the same object model, device profiles, and services familiar from DeviceNet and ControlNet to operate over standard TCP/IP networks. With extensive support for various objects and device profiles, CIP over Ethernet caters to a wide range of use cases. Embedded product teams leveraging Embien's gain access to proven EtherNet/IP Protocol integration expertise across hardware, firmware, and conformance testing.

Scalability and Network Configuration:

Running on standard Ethernet cables and switches, the EtherNet/IP Protocol can support thousands of devices in the same network. A different physical layer such as optical fiber can be chosen based on the application-specific use case.

Communication and Data Management:

The EtherNet/IP Protocol utilizes both TCP for Explicit Messaging and UDP for Implicit or I/O messaging, enhancing data transfer efficiency across different network conditions. It organizes data as objects within a CIP framework, each containing attributes that detail specific data values, ensuring structured and accessible data management.

Real-Time Capabilities and Protocol Support:

The EtherNet/IP Protocol relies on CIPSync for synchronization, compliant with IEEE 1588, allowing synchronization accuracy of fewer than 100 nanoseconds. Devices can support additional TCP/IP protocols like embedded web servers, DHCP, and Modbus, broadening the application scope of this industrial IoT protocol across various industrial settings.

These features collectively ensure that the ODVA EtherNet/IP Protocol not only meets diverse industrial requirements but also integrates seamlessly with existing network infrastructures, offering a reliable and efficient communication backbone for modern automation systems.

EtherNet/IP Protocol to OSI Model Mapping

Understanding the mapping of the EtherNet/IP Protocol to the OSI model provides a clearer view of how this protocol fits within the broader networking framework.

Ethernet/IP OSI Layer Mapping

Here's a breakdown of this mapping:

• Layers 1 and 2 (Physical and Data Link): Ethernet, which operates at these foundational layers, facilitates the physical and data link communication between devices in a network. The EtherNet/IP Protocol adheres to IEEE 802.3 standards, ensuring robust handling of physical connections and data link protocols.
• Layer 3 (Network): While Ethernet primarily functions at layers 1 and 2, it collaborates with IP at the network layer to enable inter-network communication. The network layer of TCP/IP, which the EtherNet/IP Protocol uses, offers a connectionless method of sending data packets, ensuring each device on the network is uniquely identified through IP addresses.
• Layers 4 (Transport): The EtherNet/IP Protocol utilizes TCP for reliable data transmission and UDP for simpler, connectionless messages. This flexibility allows the EtherNet/IP Protocol to support a wide range of industrial applications, from real-time machine data feedback to complex automation setups.
• Layers 5 to 7 (Session to Application): The EtherNet/IP Protocol shines from layer 5 upwards, implementing CIP. It fully integrates the high-level services of control, configuration, and data collection, essential for modern industrial environments.

This layered approach allows the EtherNet/IP Protocol to coexist with other protocols on an Ethernet network, enhancing its utility in diverse industrial settings.

EtherNet/IP Encapsulation Protocol

The EtherNet/IP Encapsulation Protocol is a vital component in the operation of the ODVA EtherNet/IP Protocol, ensuring that the Common Industrial Protocol (CIP) data is effectively structured within the TCP Data field. The EtherNet/IP Encapsulation Protocol specifically structures the CIP data, which is then encapsulated within the TCP Data field of the Ethernet frame. An encapsulation header is defined to hold the length and session data related to the CIP data communication in progress. All encapsulated messages, whether over TCP or UDP, are directed to port 0xAF12. This designated port helps in the standardized routing and recognition of EtherNet/IP Protocol messages across the network. A session in the EtherNet/IP Encapsulation Protocol context refers to the setup of TCP resources, essentially opening a socket. This session establishment is crucial for maintaining a stable and continuous communication channel during device interactions.

The EtherNet/IP Encapsulation Protocol's structured approach ensures that data is transmitted in a manner that is both recognizable and accessible to receiving devices configured to the EtherNet/IP Protocol standard. Devices are expected to handle the segmentation and de-segmentation features that are inherent to a TCP stream — i.e., a single CIP message received over multiple Ethernet frames and multiple CIP messages over a single Ethernet frame. Hardware teams using Embien's embedded hardware development services can accelerate EtherNet/IP Encapsulation Protocol implementation by leveraging pre-validated MAC/PHY configurations and CIP stack integration.

Implementing the EtherNet/IP Encapsulation Protocol correctly requires careful attention to session management, port binding, and header parsing — all areas where the EtherNet/IP Protocol specification provides detailed normative requirements.

Explicit and Implicit Messaging

In the ODVA EtherNet/IP Protocol, communication is efficiently managed through two primary types of messaging captured under Explicit and Implicit Messaging. Understanding these messaging types is crucial for leveraging the EtherNet/IP Protocol's full capabilities in industrial automation.

Explicit Messaging:

Function: Used for non-time-critical communications such as configuration and parameter updates, Explicit and Implicit Messaging in the EtherNet/IP Protocol relies on TCP for the explicit path to ensure data is sent reliably and in the correct order.

Process: Messages are sent on an as-needed basis, typically initiated by a request from a client (scanner) to a server (adapter). This includes reading or writing data to a device.

Advantages: Provides error checking and retransmission mechanisms, making Explicit and Implicit Messaging ideal for complex and detailed communication that requires confirmation of delivery.

Implicit Messaging:

Function: Suited for real-time I/O data, the implicit side of Explicit and Implicit Messaging uses UDP for its speed and efficiency, broadcasting data cyclically and continuously without waiting for a request.

Process: Data is sent at regular intervals automatically, which is crucial for tasks that require timely updates such as sensor data monitoring in a manufacturing process.

Advantages: Lower overhead than TCP, allowing for faster data transmission. This method is less reliable in terms of delivery confirmation but is optimal for high-speed data exchanges where timing is critical.

By integrating both explicit and implicit message types, the ODVA EtherNet/IP Protocol ensures versatile and robust communication options tailored for a variety of industrial applications, from precise machine control to broad system monitoring. These Explicit and Implicit Messaging strategies enhance the EtherNet/IP Protocol's adaptability and efficiency in diverse operational environments.

Types of EtherNet/IP Protocol Devices

Here, we explore the various types of EtherNet/IP Protocol devices that are integral to implementing robust and efficient networks:

Explicit Message Server: Supports request/response-oriented data transfer initiated by an explicit messaging client. Typically used for non-critical applications. E.g. Bar code reader.

Explicit Message Client: Initiates the request/response-oriented data transfer for non-critical control. Examples are engineering tools for configuration purposes and HMIs etc.

I/O Adapter/Server: Receives implicit communication connection requests from an I/O scanner then produces its I/O data at the specified rate. Typically, they also implement an explicit message server. They implement device-specific data functionality and examples include sensors, valves, gateways etc.

I/O Scanner: This class of device initiates implicit communication with IO adapters and is used to configure and control the devices. They also implement explicit messaging client functionality and examples include controllers, HMIs, and PLCs.

EtherNet/IP Protocol-Specific Objects

TCP/IP Interface Object: This object is crucial for configuring the underlying network interface settings of a device, supporting a wide range of interfaces including IEEE 802.3, ATM, and serial ports running SLIP or PPP.

Ethernet Link Object: It maintains link-specific counters and status information for an IEEE 802.3 communications interface, and there shall be only one instance of the object for each IEEE 802.3 communications interface on the module.

Device Level Ring (DLR) Object, QoS Object, Base Switch Object, SNMP, and RSTP are a few more object types defined by the ODVA EtherNet/IP Protocol specification. The availability of these standard objects makes the EtherNet/IP Protocol a compelling industrial IoT protocol for connected factory deployments where both real-time control and remote diagnostics are required simultaneously. Embien’s digital transformation and Digital Twin–based predictive maintenance services leverage Ethernet/IP connectivity to enable intelligent, data-driven industrial operations.

Conclusion

The EtherNet/IP Protocol is a leading industrial IoT protocol for connected manufacturing, combining CIP over Ethernet with robust EtherNet/IP Encapsulation to deliver scalable, standards-compliant automation. Its support for Explicit and Implicit Messaging makes it uniquely suited to serve both time-critical I/O control and on-demand configuration needs within the same network infrastructure.