Month: July 2025

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.

Supported Industrial

Ethernet Protocols:

Modbus TCP Interface

The Modbus TCP interface will support Modbus data

sources such as PLCs, MCCs, analyzers and similar devices

communicating Modbus TCP. The Modbus TCP interface is a

Modbus Client reading and writing data from/to Modbus Server

devices. The Modbus server devices can be Modbus TCP devices

or Modbus serial devices using a Modbus TCP gateway.

The Modbus TCP interface supports the following types of

data access:

„ Reading input data from Modbus Coils, Discrete Input,

Holding Registers, and Input Registers.

„ Writing output data to Coils and Holding registers.

All reads will be performed periodically and outputs will be

sent when they are written.

Listed by category, the following is a complete list of the

function blocks available with the EIOC.

Advanced Control – None

Advanced Functions – State Transition, Step Sequencer

Analog Control – Analog Tracking, Calc/Logic, Filter,

Input Selector, Scaler, Signal Characterizer, Signal Generator,

Signal Selector, Bias/Gain, Manual Loader, PID, Rate Limit,

Ramp, Enhanced Ramp, Splitter, Limit

Energy Metering – None

IO – Alarm Detection, AI, AO, DI, DO

Tag I/O – DI, DO, AI, AO

Logical – All

Math – All

Special Items – All

Timer Counter – All

Access to DeltaV Live graphics, DeltaV Operate graphics, and

the alarms and history collection from EIOC control modules

follows the same rules and mechanisms as control modules

running in the controllers in a DeltaV System.

The EIOC mounts on the dual horizontal carrier, which includes

redundant Power input Terminals as well as redundant

Ethernet Isolation ports. The Ethernet Isolation ports isolate

the redundant DeltaV Control Network communication

from the redundant Ethernet Device Networks. An Industrial

Networks Firewall is recommended to provide added security

based on deep packet inspection to restrict communications

at the Ethernet device and Ethernet protocol level. In this way,

Robustness and Security is ensured.

When configuring the EIOC Control Modules, all typical

Function blocks needed for continuous operation are available;

however, the usage of the following Function blocks are limited

in the EIOC:

„ 256 DC’s, EDC’s and DCC’s – used for such applications as

motor control in MCCs.

„ 26 PID’s – analog control where all or most of the signals are

coming from Ethernet Devices.

„ 16 SEQs – Sequence function block used for sequencing

motor control states.

„ 16 STDs – State Transition Diagram used in sequencing and

can be used with the SEQ function blocks.

„ Batch control, SFCs, PLMs, and Equipment Modules are not

supported in the EIOC.

To maintain the capacity of the EIOC, consideration should be

taken to keep modules as lean as possible. Heavy configuration

in the modules will decrease the capacity of 2000 modules in

the EIOC.

Product Description

The EIOC is a big pipe for the integration of process data from

3rd party Ethernet Devices, such as PLCs and smart field devices

such as Intelligent Field Devices (IFDs) and Intelligent Electronic

Devices (IEDs). A network of these Ethernet Devices can be

directly connected to the EIOC. The Ethernet Devices can

communicate to the EIOC using one of five protocols;

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

and EtherNet/IP Control Tag Integration. The EIOC connects

directly into the DeltaV Control Network and can be placed

remotely in an enclosure in the field.

The EIOC is an independent embedded data server. This means

that there is no need for a separate controller to process the

data being integrated into the EIOC. Control Modules needed

to process the data from the Ethernet Devices are assigned and

executed in the EIOC. In this way, communications with the

devices are fast and direct. Any parameters from the modules

running in the EIOC can be read by both S-series and M-series

controllers using External References when needed in control

strategies at the controller level.

„ Powerful solution that communicates directly

to external Ethernet Device Networks

„ Easy connection to devices using Modbus TCP,

EtherNet/IP, IEC61850 MMS, OPC UA client or

EtherNet/IP Control Tag Integration protocols

„ Proven S-series packaging

„ Modular with easy to add redundancy

„ Communication to any M- and S-series Controller

Introduction

The Ethernet I/O Card (EIOC) provides a platform to access data

from Ethernet devices in the DeltaV™ system. Ethernet Devices

capable of talking Modbus TCP, EtherNet/IP, IEC 61850 MMS

(Manufacturing Message Specification), OPC UA client and

EtherNet/IP Control Tag Integration protocols are supported.

The EIOC provides monitoring and control of Ethernet Devices

on the Ethernet Device Network via control modules assigned

to and executed in the EIOC. Ethernet Devices like PLCs,

Motor Control Centers, drives, switchgear and others can be

controlled directly by the EIOC, independent of a controller

WirelessHART devices can be easily added to a mesh network

using AMS Device Manager to assign the Network ID and

Join Key. Once configured, simply install the device in the

field and it is automatically detected and reconciled through

DeltaV Explorer. The device can be assigned to any one of

four controllers. Each device is also automatically defined

with PlantWeb alerts that proactively report device health to

maintenance personnel, with zero configuration.

This provides added flexibility and accommodates late

changes where control modules may be reassigned to a

different controller.

The Ethernet I/O Ports of the WIOC are the same as DeltaV

CHARM I/O Cards (CIOC) and can be connected with CIOCs

in the DeltaV network topology. The I/O Port for copper

10/100BASE-TX media support a second “cascade” port that

allows a series of WIOCs to be daisy-chained together to

simplify the network design and reduce cost.