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 to OSI model mapping, the guide elaborates on the operational intricacies that make Ethernet/IP an exemplary model in the automation sector, including EtherNet/IP Encapsulation Protocol, explicit and implicit messaging, objects to be supported.
Key Features of EtherNet/IP
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):EtherNet/IP runs the 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. With extensive support for various objects and device profiles, it caters to wide use cases.
Scalability and Network Configuration:Running on standard Ethernet cables and switches it can support thousands of devices in the same network. Further a different physical layer like optical fiber etc can be chosen based on the application specific use case.
Communication and Data Management:Utilizes both TCP for explicit messaging and UDP for implicit or I/O messaging, enhancing data transfer efficiency across different network conditions.
Organizes data as objects within a CIP framework, each containing attributes that detail specific data values, ensuring structured and accessible data management.
Relies on CIPSync for synchronization, compliant with IEEE 1588, allowing synchronization accuracy of fewer than 100 nanoseconds.
Device can support additional TCP/IP protocols like embedded web servers, DHCP, and Modbus, broadening its application scope 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 to OSI model mapping
Understanding the mapping of EtherNet/IP 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. EtherNet/IP 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 EtherNet/IP uses, offers a connectionless method of sending data packets, ensuring each device on the network is uniquely identified through IP addresses.
- Layers 4 (Transport): EtherNet/IP utilizes TCP for reliable data transmission and UDP for simpler, connectionless messages. This flexibility allows EtherNet/IP 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): EtherNet/IP shines from the layer 5 upwards, implementing the CIP. It fully integrates the high-level services of control, configuration, and data collection, essential for modern industrial environments.
This layered approach allows EtherNet/IP 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 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 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 messages across the network. A session in EtherNet/IP 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.
This structured approach ensures that data is transmitted in a manner that is both recognizable and accessible to receiving devices configured to the EtherNet/IP standard. Further the devices are expected to handle the segmentation/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.
Explicit and Implicit Messaging
In the ODVA EtherNet/IP protocol, communication is efficiently managed through two primary types of messaging: Explicit and Implicit Messaging. Understanding these messaging types is crucial for leveraging the protocol's full capabilities in industrial automation.
Explicit Messaging:Function: Used for non-time-critical communications such as configuration and parameter updates, explicit messaging relies on TCP 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 it ideal for complex and detailed communication that requires confirmation of delivery. Implicit Messaging:
Function: Suited for real-time I/O data, 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 messaging, 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 messaging strategies enhance the protocol's adaptability and efficiency in diverse operational environments.
Types of EtherNet/IP devices
Here, we explore the various types of EtherNet/IP 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 HMI’s 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 and examples include controllers, HMIs, and PLCs.EtherNet/IP specific Objects
TCP/IP Interface Object: This object is crucial for configuring the underlying network interface settings of 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 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 specification.
Conclusion
Leveraging Ethernet along with CIP gives an unique place in the industrial automation sector placing EtherNet/IP on par with similar protocols like PROFINET, OPC-UA, EtherCAT. While each of these protocols have their own pros and cons along with application use cases, Ethernet/IP, growing at a rapid pace, has recently surpassed DeviceNet in the U.S., highlighting its increasing preference in industrial settings.
This dive into the ODVA EtherNet/IP protocol offers a structured pathway to understand its comprehensive suite of services, ensuring our readers are well-equipped to leverage its full potential.