Summary

The EIOC supports communications with Ethernet Devices

using Modbus TCP, EtherNet/IP, IEC61850 MMS, OPC UA client

and Ethernet/IP Control Tag Integration protocols. The EIOC

supports a huge capacity of data for monitoring or control.

The Capacity, polling and switchover times vary based on

protocol, device type, and loading. Refer to the DeltaV System

Planning Guide for more information.

The EIOC capacity lends itself to very large integration projects

with limited control needs. For applications that require

batch or sequence control (class-based units, PLMs, SFCs,

and Equipment Modules are not supported in the EIOC)

or more complex control that requires other functionality

such as traditional, bus, or Electronic Marshalling IO, then a

PK controller or a VIM2 card combined with a DeltaV controller

could be a better solution. Please consult your local Emerson

office for more details.

EIOC Licensing

Licensing for the EIOC is easy and scalable. Just buy the

hardware assembly for the EIOC, simplex or redundant.

No additional license is required for redundancy. Then decide

which protocol you need (one per EIOC is permitted),

and pick the appropriate license. Next, determine how many

Ethernet Devices you need to connect, and pick the license

containing the required number. Once the EIOC is configured

one DST license will be consumed per LDT, with the type being

determined based on the highest value configured in the LDT

(except for the EtherNet/IP Control Tag Integration Protocol).

For the EtherNet/IP Control Tag Integration protocol,

one DST license is consumed per Control Tag. The DST license is

consumed based on the type of Control Tag that is configured.

PRP does not require a license, as it is included as part of the

EIOC functionality.

EIOC Configuration

The EIOC is configured in the I/O network level of DeltaV

Explorer and it does not count towards the controller node

count limit (limited to 60 EIOCs per system). The hierarchy

of the EIOC in DeltaV Explorer consist of:

„ EIOC

z Assigned Modules – Modules configured and running

inside the EIOC.

z Hardware Alarms – Hardware alarms associated with

the EIOC.

z PO1 – EIOC port, where the Ethernet Device Network

and protocol is setup.

z PDT – The Ethernet Devices are added and configured

under the EIOC port as Physical Devices (PDTs).

The amounts of PDTs that can be configured will vary

depending of the protocol selected in the port and

the amount of device licenses assigned. The PDTs can

be renamed.

z LDT – Logical Devices (LDTs) are added under the PDTs to

configure signals or control tags depending of the protocol

that has been selected at the port level. DST licenses are

applied at this level.

Parallel Redundant Protocol (PRP)

PRP is a network protocol standard for Ethernet that provides

seamless failover against failure of any network component.

Therefore, it is a great solution when high availability and short

switchover time is required (e.g. electrical monitoring using

IEC 61850 MMS). PRP allows for communications in Primary and

Secondary ports of the Ethernet Device Network in the EIOC to

happen at the same time. This means that a device connected

to the Ethernet Device network is getting the same information

at the same time, through different network paths. In case of

failure in one of the networks it basically provides a zero-time

to recovery (no time to switchover) and eliminates any single

point of failure in a redundant Ethernet Device Network.

PRP is independent of the application-protocol and can be

used by most Industrial Ethernet protocols. In the EIOC,

PRP is an optional feature than can be enabled at the port level

and is available with all the protocols supported in the EIOC.

When enabled, PRP runs on top of the protocol that is selected

at that time.

For PRP to work properly, the Ethernet Devices connected to

the redundant network needs to support PRP natively as well.

If the devices do not support PRP natively, then a RedBox must

be used to allow the connection into the PRP network without

having bad status in diagnostics.

IEC 61850 (MMS)

The IEC 61850 MMS interface will allow data from Intelligent

Electronic Devices (IEDs) such as motor protection relays,

motor starters, motor control centers, switchgear, and similar

MMS-based devices to be integrated into DeltaV. The MMS

interface will be a client reading and writing data from/to the

Intelligent Electronic Device which acts as the server.

The EIOC only supports reading and writing of real time

signals using this protocol. Reading historical data or

Goose applications are not supported.

OPC UA Client

The OPC UA Client in the EIOC provides native client

implementation of a Data Access profile (real time data)

compliant with OPC UA version 1.03. The OPC UA client will

read and write up to 30,000 real time signals coming from

up to 64 OPC UA servers.

EtherNet/IP Control Tag Integration protocol

The EtherNet/IP Control Tag Integration protocol utilizes

EtherNet/IP Class 3 messaging to provide integration with

tag-based PLC data sources. Referencing data by tag name

eliminates the need for register mapping. Read or write up

to 10 signals per tag, and up to 2000 tags per EIOC for a total

of 20,000 signals. The EtherNet/IP Control Tag Integration

protocol supports reading string type signals and read/write

of arrays up to 64 elements each (max 100 arrays per EIOC).

The EtherNet/IP Control Tag Integration protocol supports

integration with ControlLogix and CompactLogix PLCs utilizing tags.

EtherNet /IP

The EtherNet/IP protocol allows data sources such as

PLCs, Intelligent Field Devices (IFDs), variable-speed drives,

MCCs, and analyzers; as well as other devices communicating

EtherNet/IP to connect directly in to DeltaV via the EIOC.

The EtherNet/IP interface will support connections for

both implicit and explicit messaging to allow access to both

Class 1 and Class 3 EtherNet/IP I/O adapters. Redundancy with

EtherNet/IP Class 1 Implicit and Class 3 Explicit messaging

for control (sending outputs to the devices) require special

considerations due to exclusive owner communications defined

by the protocol. Please refer to the DeltaV System Planning

Guide for more information. Class 3 PCCC and UCMM with

Logix tags message classes are also supported.