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.

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

www.abb-drive.com 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.