The extension of the EtherNet/IP specification makes it possible to better connect IO-Link sensors and devices at the lowest level of the network with EtherNet/IP controllers and devices at higher levels of the network. "IO-Link device integration with CIP provides seamless communication between CIP originators and IO-Link devices via the intermediate IO-Link master, with all parties using existing IO-Link hardware and standards," explains Dr. Al Beydoun, President and Executive Director at the Open DeviceNet Vendors Association (ODVA).

IO-Link to CIP connectivity reduces engineering effort and simplifies the collection of data and information, resulting in a more efficient production facility that meets the demands of IT/OT convergence. IO-Link devices can now be recognized within EtherNet/IP without end users having to deal with data conversion. From the EtherNet/IP perspective, an IO-Link device is seen as a native CIP device located in a (virtual) subnet. The IO-Link master provides the CIP functions for the IO-Link device in a way that is transparent to the CIP originator application. All three types of IO-Link communication (cyclic, acyclic and events) are mapped to CIP communication types. CIP-to-IO-Link communication is possible with an unmodified IO-Link master and device specification, which is standardized by the IEC. Direct communication is made possible by conversion between CIP originators and IO-Link devices via the intermediate IO-Link master. All IO-Link devices are treated as if they were CIP connection target devices (I/O adapters) in a virtual IO-Link subnet.

Supplements for the process industry

In addition, the ODVA has supplemented the EtherNet/IP specification with regulations that define the integration of NAMUR-NE-107 diagnostics for process automation in CIP architectures. The addition of this function provides process users with industry-standard diagnostic information and allows them to benefit from the advantages of Industrial Ethernet. "The integration of NE-107 diagnostics is another step towards realizing our vision for optimizing process integration," explains Al Beydoun.

The Process Diagnostics Update for EtherNet/IP creates a CIP Process Device Diagnostics Object that provides a known, public interface to a device's current diagnostics and indicates the NE-107 status according to the NAMUR recommendation NE 107 for self-monitoring and diagnostics of field devices. The NAMUR NE 107 status signal, now available with EtherNet/IP, provides the following status information: Error, Functional Check, Out of Specification, Maintenance Required or None. The CIP Process Device Diagnostics Object expands the amount of useful data available with EtherNet/IP with the latest NE-107 diagnostic information from field devices from various vendors.

In addition to the status signal, the CIP Process Diagnostics Object displays up to 64 diagnostics of a device, such as flow, pressure or temperature status. The user can then group these as required. Vendor-specific diagnostics can also be added. Applications can now query supported EtherNet/IP field devices for changes in diagnostic status and obtain further diagnostic information using Explicit Messaging (acyclic messaging) or object-specific services. This allows all devices diagnosed with a specific NE-107 signal (e.g. maintenance required) to be retrieved with a single common service request. With EtherNet/IP, this diagnostic information can be easily transmitted to where it is needed, such as to a DCS for inspection by an operator for possible maintenance action or to an edge device for predictive maintenance analysis. "The integration of NE-107 diagnostics is designed to meet the needs of programmers, operators and maintenance technicians from both a process optimization and IIoT perspective," concludes Dr. Beydoun.

SPS 2019: Hall 5, Stand 128