experion eim ethernet/ip interface infi90 documentation... · version 1.0 honeywell proprietary jan...
TRANSCRIPT
Version 1.0 Honeywell Proprietary Jan 2017
Experion EIM EtherNet/IP Interface Specification
Technical Information
EP03-561-500 Release 500
Jan 2017, Version 1.0
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 2
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 3
Version 1.0 Honeywell Proprietary Jan 2017
Revision History
Revision Date Description
1.0 January, 2017 First release
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 4
Version 1.0 Honeywell Proprietary Jan 2017
Table of Contents
1. Product Introduction ...................................................................................................................................................... 5
1.1. Solution Introduction ................................................................................................................................................. 5
1.2. CIP and Ethernet/IP™ .............................................................................................................................................. 5
1.2.1. CIP - The Actual Protocol ......................................................................................................................................................... 5
1.2.2. EtherNet/IP ............................................................................................................................................................................... 5
1.2.3. ODVA ....................................................................................................................................................................................... 6
1.3. Two Different C300 EtherNet/IP Solutions ................................................................................................................ 7
1.3.1. C300 Direct EtherNet/IP Solution ............................................................................................................................................. 7
1.3.2. EIM – Common Platform for Ethernet Protocols ...................................................................................................................... 8
1.3.3. C300 EIM Ethernet/IP Solution ................................................................................................................................................ 8
2. The EIM with Ethernet/IP Personality ............................................................................................................................ 9
2.1. EIM Hardware Characteristics .................................................................................................................................. 9
2.2. EIM Hardware and License Model Numbers ............................................................................................................ 9
2.3. EIM Network/Communications Characteristics ....................................................................................................... 12
2.4. 3rd Party Network Hardware Requirements ............................................................................................................. 12
2.5. EtherNet/IP Device/Node Types ............................................................................................................................. 14
2.6. [ UDT ] User-defined Data Types - Overview .......................................................................................................... 15
2.7. [ I/O ] Device Blocks - Overview .............................................................................................................................. 16
2.8. Supported [ I/O ] Device Blocks and Devices.......................................................................................................... 18
2.8.1. Summary - I/O Devices Currently Supported ......................................................................................................................... 18
2.8.2. Additional Details on Validated I/O Devices ........................................................................................................................... 19
2.8.3. Adding New I/O Device Types ............................................................................................................................................... 20
3. Important Communication Concepts .......................................................................................................................... 21
3.1. IP Addresses & CIP Connections ........................................................................................................................... 21
3.1.1. Ethernet IP Address ............................................................................................................................................................... 21
3.1.2. CIP Connections..................................................................................................................................................................... 21
3.2. EIM IP Address and CIP Connection Usage ........................................................................................................... 22
4. Ethernet/IP Capacity, Rules, and Specifications ........................................................................................................ 23
4.1. C300 Direct vs. EIM Solution Notes ........................................................................................................................ 23
4.2. Solution Components and Specifications ................................................................................................................ 23
4.3. Ethernet/IP Performance, Capacity, Limits, and Specifications .............................................................................. 24
4.3.1. EIM with EtherNet/IP - Configuration Limits ........................................................................................................................... 24
4.3.2. EIM with EtherNet/IP™ - Capacity Limits ............................................................................................................................... 25
4.3.3. EIM with EtherNet/ IP - Performance ..................................................................................................................................... 27
4.3.4. EIM with EtherNet/IP™ - Redundancy Specifications ............................................................................................................ 28
4.3.5. UDTs – Supported Data Types .............................................................................................................................................. 28
5. Solution Model Numbers and Licensing ..................................................................................................................... 29
................................................................................................................................................................................................ 30
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 5
Version 1.0 Honeywell Proprietary Jan 2017
1. Product Introduction
1.1. Solution Introduction
Experion R500 introduced a new module in Series C form factor called the Ethernet Interface Module (EIM). When loaded
with the EtherNet/IP personality, the EIM provides a cost effective interface to EtherNet/IP networks and access to data
resident in EtherNet/IP compliant devices.
EtherNet/IP allows the user to satisfy a broad spectrum of process control needs using one protocol. Users can choose from
a comprehensive set of different devices types from a large list of vendors.
1.2. CIP and Ethernet/IP™
1.2.1. CIP - The Actual Protocol
The Common Industrial Protocol (CIP™) is a fully networked solution that encompasses a comprehensive suite of messages
and services to fully support a broad spectrum of process needs and applications on one protocol. CIP is a peer to peer
object oriented protocol that provides connections between industrial devices (sensors, actuators, drives, motors, I/O, etc.)
and higher-level devices (controllers). CIP is applicable to factory and process automation control, safety, synchronization,
motion, and the configuration and management of intelligent field devices.
CIP is the protocol language used to enable communication between all nodes on the network. It is physical media and data
link layer independent. This media independence provides the ability to choose the CIP Network best suited for your
application.
CIP is implemented on various networks as follows…
CompoNet™ ………. CIP on TDMA technology
DeviceNet™ ………. CIP on CAN technology
ControlNet™ ……… CIP on CTDMA technology
EtherNet/IP™….... CIP on ETHERNET technology
1.2.2. EtherNet/IP
Ethernet/IP™ is the name given to the Common Industrial Protocol (CIPTM), as implemented over standard Ethernet (IEEE
802.3 and the TCP/IP UDP protocol suite). Ethernet/IP is a high-level industrial application layer protocol for industrial
automation applications that uses the tools and technologies of traditional Ethernet. Ethernet/IP uses all the transport and
control protocols used in traditional Ethernet including the Transport Control Protocol (TCP), the Internet Protocol (IP) and
the media access and signaling technologies found in off-the-shelf Ethernet interfaces and devices.
EtherNet/IP was introduced in 2001 and today is one of the most developed, proven and complete industrial Ethernet
network solutions available for industrial control and automation solutions. It enables real-time control and data acquisition
for discrete applications, continuous process, safety, drive, motion, and applications requiring high availability. Ethernet/IP is
applicable to factory automation, process automation, and is well suited for both batch and continuous operations.
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 6
Version 1.0 Honeywell Proprietary Jan 2017
1.2.3. ODVA
Founded in 1995, ODVA is a global association whose members comprise the world’s leading automation companies.
ODVA’s mission is to advance open, interoperable information and communication technologies in industrial automation.
EtherNet/IPTM and CIPTM are managed by ODVA. ODVA publishes The EtherNet/IP Specification and helps ensure
compliance through conformance testing.
More information is available at the ODVA website….
WWW.ODVA.org
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 7
Version 1.0 Honeywell Proprietary Jan 2017
1.3. Two Different C300 EtherNet/IP Solutions
Starting with the Experion R500 there will be two separate Experion C300 solutions that support EtherNet/IP. It is important to be aware of these two solutions and any rules or limits that may need to be considered when implementing both on the same Server Cluster. Both solutions are supported in Experion R500.
The two solutions differ primarily in their topologies and the manner in which they interface the C300 to the associated Ethernet/IP network and Ethernet/IP devices.
The two solutions are as follows:
1. C300 Direct Ethernet/IP solution ….. (first released with Experion R430, support will continue in R500)
2. C300 EIM (Ethernet Interface Module) Ethernet/IP solution …… (first released with Experion R500)
Each solution is covered in more detail below.
1.3.1. C300 Direct EtherNet/IP Solution
Figure 1 provides a high level topology diagram.
Some key characteristics…….
C300 EtherNet/IP data access is over FTE Level-2.
The Ethernet/IP network must use the same subnet assignment as the Experion Server Cluster.
Required 3rd party hardware…..
– Cisco 2960 (or newer)
– Tofino Firewall (FTE protection from Ethernet/IP traffic)
– Stratix 8000 switch (FTE Level-2 switch)
For more complete solution information refer to Spec document EP03-560-500_V1_Ethernet_IP.
Figure 1 Experion C300 EtherNet/IP Topology
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 8
Version 1.0 Honeywell Proprietary Jan 2017
1.3.2. EIM – Common Platform for Ethernet Protocols
The EIM (Ethernet Interface Module) is designed to provide a common hardware platform for all Ethernet-based protocols
going forward.
The EIM is an optionally redundant module in the Series C form factor that was first released with Experion R500. Using a
new tool (Firmware Manager), also released with Experion R500, the user will select and download the desired protocol
personality into the EIM (or redundant pair).
In the first release (R500), the following personalities are available for download to an EIM:
1. EtherNet/IP ……. (Covered in the specification document)
2. IEC 61850 …….. (refer to specification document EP03-570-500)
Only one personality can be loaded into a given EIM at one time.
A given Experion Server Cluster can consist of EIMs that have been loaded with the EtherNet/IP and/or IEC 61850
personality. One C300 can connect to 2 different EIMs - one with IEC61850 and another with EtherNet/IP.
1.3.3. C300 EIM Ethernet/IP Solution
As shown in Figure 2, the C300 EIM Ethernet/IP solution is characterized (and differs from the C300 Direct solution) by the use of a new Series C EIM (with the EtherNet/IP personality loaded).
With this solution the C300 communicates through the EIM to read and write data resident in EtherNet/IP compliant nodes (motor starters, drive controllers, I/O, PLCs, etc.) connected to the Ethernet/IP network. This enables the user to create control strategies using information accessed from smart (EtherNet/IP) devices.
The C300 EIM solution provides many advantages and enhancements over the original C300 Direct solution delivered in Experion R430.
One major enhancement is the ability to isolate the FTE subnet from the Ethernet/IP subnet. This provides substantial improvements for both the FTE node and Ethernet/IP node maximum count specifications.
Figure 2 C300 EIM Topology
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 9
Version 1.0 Honeywell Proprietary Jan 2017
2. The EIM with Ethernet/IP Personality
The sections that follow cover concepts and information specific to the EIM with Ethernet/IP personality loaded.
2.1. EIM Hardware Characteristics
Refer to Figure 3 ……The EIM…
Is a standard Series C module and form factor
Mounts to a nine inch IOTA (see Figure 4 for IOTA layout)
Is optionally redundant (using two modules + two IOTAs connected by a redundancy sync cable)
Mounts into a standard Series C cabinet using standard Series C mounting hardware
Uses standard Series C power and grounding components and practices
Has all Series C family certifications and environmental ratings
Has an extended temperature range of -40°C to 70°C
2.2. EIM Hardware and License Model Numbers
EIM Module……. CC-PEIM01
EIM IOTA………. CC-TEIM01 (nine inch IOTA)
Redundancy requires (2) Modules, (2) IOTAs, and a redundancy sync cable (same as used with the C300). Sync cable lengths: 2, 3, 5, 7, 10, and 14 feet.
• EIM (EtherNet/IP) use license …. TC-EPLX02 Every EIM (or redundant pair) loaded with the EtherNet/IP personality will require one use license. This license provides access to all functions and features described in this specification.
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 10
Version 1.0 Honeywell Proprietary Jan 2017
Figure 3 Redundant EIM shown in a Series C Cabinet
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 11
Version 1.0 Honeywell Proprietary Jan 2017
Figure 4 EIM IOTA Layout
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 12
Version 1.0 Honeywell Proprietary Jan 2017
2.3. EIM Network/Communications Characteristics
Refer to Figure 5 ……
EIM serves as the interface between the FTE and EtherNet/IP networks and nodes.
EIM is an FTE node (similar in concept to the FIM4, FIM8, and PGM).
Primary EIM is assigned an odd FTE index address. Optional redundant EIM is assigned the primary index +1.
Both the C300 and EIM can be redundant.
The EIM is an FTE node and can connect at FTE Level-1 (best practice) or Level-2 (supported, but not best practice). Note: Connection of EIM & C300 to the same CF9 ensures the fastest recovery time (<100ms) following an FTE cable failure between these modules. Connections to separate CF9s or to separate L2 Cisco Switches are supported, but some FTE Cable Faults will take between 1-2 seconds for recovery of C300 to EIM communications for these configurations.
EIM supports one EtherNet/IP downlink and Linear Bus, Star, and DLR (Device Level Ring) Topologies.
The EIM provides FTE/EtherNet/IP network isolation. EtherNet/IP devices are isolated from the server cluster subnet by the EIM allowing for the use of different subnet assignments for the EtherNet/IP network.
The EIM has a built in CF9 firewall capability. When implemented at FTE Level-2, no CF9 modules are required.
The EIM has a built in EtherNet/IP firewall capability to protect the FTE from EtherNet/IP network traffic. No 3rd party firewalls are required on the EtherNet/IP downlink.
Important! The EIM solution requires the use of C300 model CC-PCNT02 with the new C300 (large memory) boot image loaded! CC-PCNT01 cannot be used with the EIM solution.
A maximum of (5) EIMs (or redundant pair) may be associated with a single C300 Controller.
A maximum of (5) C300 Controllers may be associated with a single EIM (or redundant pair).
Important! The Honeywell EtherNet/IP SCADA solution and EIM solution can coexist on the same FTE community. However, the SCADA solution cannot communicate with the EIM. For more details, refer to the “IEC 61850 SCADA Configuration Reference Guide”.
2.4. 3rd Party Network Hardware Requirements
The following summarizes the mandatory 3rd party hardware requirements for the EIM Ethernet/IP solution.
The following were qualified for use with the EIM solution:
1. Rockwell Stratix 8000 switch
2. Rockwell Stratix 5700 switch
3. Rockwell 1783-ETAP (used with Device Level Ring topologies)
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 13
Version 1.0 Honeywell Proprietary Jan 2017
Ethernet/IP Data Access
Figure 5 provides a simplified functional diagram of the EIM solution for concept.
Always refer to the Honeywell R500 “Ethernet IP Users Guide” for actual network diagrams and additional rules. Additional details on Liner Bus, Star and DLR topologies are also provided in the User Guide.
Figure 5 EIM - EtherNet/IP Solution (Functional Diagram)
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 14
Version 1.0 Honeywell Proprietary Jan 2017
2.5. EtherNet/IP Device/Node Types
As shown in Figure 8, the Ethernet/IP network hosts Ethernet/IP compliant nodes that connect to the process and perform
process related tasks, control, and provide process level information.
The EtherNet/P solution allows the C300 to read and write data resident in these process connected nodes. This data can
then be used for control, historization, and the operator HMI.
In terms of data access, the C300 Direct solution divides Ethernet/IP devices into two major categories, as follows:
1. ControlLogix Processors:
– The C300 communicates (through the EIM) with the Rockwell ControlLogix processor on a supervisory level.
– The ControlLogix process will have its own dedicated I/O.
– The solution uses UDTs (User-defined Data Types) to communicate (read and write) data between the C300 and the ControlLogix processor.
– Data transfer (EIM to EtherNet/IP device) uses EtherNet/IP (CIP) Explicit Class-3 messaging.
2. Process Connected I/O Devices:
– These device types connect directly to the process and perform some set of process control tasks. Motor starters, drive controllers, and I/O are a few examples.
– C300 connects with the device (through the EIM) to access process and device data that is used for primary control and logic.
– The solution provides device-specific I/O blocks for each particular vendor device type supported.
– Data transfer (EIM to EtherNet/IP device) uses EtherNet/IP (CIP) Implicit Class-1 messaging.
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 15
Version 1.0 Honeywell Proprietary Jan 2017
2.6. [ UDT ] User-defined Data Types - Overview
Refer to Figure 6. UDTs provide an effective and efficient way to read and write data resident in ControlLogix PLCs. UDTs are used for all data transfer between the C300 and ControlLogix processors.
Some Important UDT Characteristics:
The C300 communicates with the ControlLogix through the EIM. EIM to ControlLogix processors utilizes Class-3 “Explicit” CIP messaging to read and write data resident in ControlLogix processors.
UDT data transfer is intended to support a Supervisory control arrangement between the C300 and ControlLogix processor. In this arrangement, the C300 is the supervisor and the ControlLogix processor is the primary controller.
Along with the typical process data, diagnostic data can also be included in UDTs.
Data transfer rate is determined by the user entered UDT RPI (Requested Packet Interval) setting in milli-seconds.
The UDT is a user defined structure that contains a set of user specified parameters and user defined data types.
Concept: As shown in Figure 6, UDTs are fully defined by the user. Users will create a UDT in the appropriate ControlLogix engineering tool and then create a matching UDT in the Honeywell Control Builder.
For each UDT, the user will determine the following:
UDT Tag name
Number of parameters and parameter names
Parameter data types
Parameter read/write access
The EIM EtherNet/IP solution supports both structured (multi-parameter) and Scalar (single parameter) UDTs
UDTs must match exactly on the C300 and ControLogix side
Important! The user should always refer to the ControlLogix documentation to ensure that there are no conflicts between the
C300 and ControlLogix capacity, performance, and specifications that might further limit the UDT solution.
Figure 6 UDT Concept Diagram
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 16
Version 1.0 Honeywell Proprietary Jan 2017
2.7. [ I/O ] Device Blocks - Overview
Refer to Figure 7. I/O device blocks are used to access data from process connected devices such as motor starters, drives,
and I/O. This input and output data can then be used by the C300 for primary control and logic strategies.
I/O Device Block Characterizations:
The C300 communicates with the EIM. The EIM utilizes Class-1 “Implicit” CIP messaging to read and write data resident in process connected I/O device (such as motor starters, drives, I/O, etc.).
Implicit data transfer is fast and deterministic and well suited to the demands of primary control and logic running in the C300.
Cyclic data transfer rate is determined by the user entered RPI (Requested Packet Interval) setting in milli-seconds.
For each device, the device vendor will create an input and an output assembly. These (vendor determined) assemblies contain parameters that are relevant to the input and output data to be provided by the device. These assemblies are read and written to by the C300 (through the EIM) according to the RPI setting.
As supported by each device, device diagnostics may be contained in the assembly.
The parameters contained in these input and output assemblies can be used in Control Modules to create C300 control strategies that use EtherNet/IP resident I/O devices.
In Control Builder, each specific I/O device will have device-specific I/O blocks that are specifically created for that device.
The process of adding new device types requires the creation of new blocks that understand the specific input and output assembly structure for the device to be added.
Note: For complex devices such as motor starters, drive controllers and the like, there is usually one input and one output
assembly per device.
Modular devices like I/O systems usually require an assembly per I/O module. The module type (AI, AO, DI, or DO)
determines if the assembly is of type input or output.
Figure 7 I/O Type Point - Concept Diagram
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 17
Version 1.0 Honeywell Proprietary Jan 2017
Figure 8 Two Types of EtherNet/IP Data Transfer
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 18
Version 1.0 Honeywell Proprietary Jan 2017
2.8. Supported [ I/O ] Device Blocks and Devices
The device list below represents the devices that have been qualified and are currently supported at the time of the release
of this document. To determine the current list or to request the addition of a new EtherNet/IP compliant device type, contact
your Honeywell representative.
2.8.1. Summary - I/O Devices Currently Supported
EIP Device Use Embedded
(Note-1) Requires Import
(Note-2)
1738 ArmorPoint I/O Typical I/O √
1732E ArmorBlock I/O Typical I/O √
E3 Solid State Overload Relay Motor control 2-states Start/Stop
√
E3 + Solid State Overload Relay Motor control 3-states Stop/State-1/State-2
√
PF 755 Drive Command motor direction and speed
√
PF 753 Drive Command motor direction and speed
√
E300 Smart Relay Motor control 3-states Stop/State-1/State-2
√
Note-1: These device blocks are embedded and loaded with the Experion software. No additional steps are required to use these block types.
Note-2: These device blocks are not loaded with the Experion software. They must be downloaded from the Honeywell website and then manually imported by the user.
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 19
Version 1.0 Honeywell Proprietary Jan 2017
2.8.2. Additional Details on Validated I/O Devices
The following provides additional information about the devices validated for the EtherNet/IP solution.
Rockwell Armor Point I/O:
Module Type Channels Signal Type
1738-AENT Adaptor N/A N/A
1738-IB4DM12 DI 4 Sinking 24 Vdc
1738-IB8M12 DI 8 Sinking 24 Vdc
1738-OB2EPM12 DO 2 24 Vdc
1738-OB8EM12 DO 8 24 Vdc
1738-OA2M12AC3 DO 2 120V ac, 220V ac
1738-OE2CM12 AO 2 (4-20 ma)
1738-OE4CM12 AO 4 (4-20 ma)
1738-IE2CM12 AI 2 (4-20 ma)
1738-IE4CM12 AI 4 (4-20 ma)
1738-IT2IM12 AI 2 TC, Milli-volt
1738-IR2M12 AI 2 RTD, resistance
Rockwell Armor Block I/O:
Module Type Channels Signal Type
1732E-IB16M12DR DI 16 with diagnostics
1732E-IF4M12R AI 4 High Level Current/voltage
1732E-OF4M12R AO 4 High Level Current/voltage
1732E-IT4IM12R AI 4 T/C, MV
1732E-IR4IM12R AI 4 RTD, resistance
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 20
Version 1.0 Honeywell Proprietary Jan 2017
Rockwell Drives and Overload Relays:
Device Notes/Comments
Rockwell E3 overload relay:
Provides two states (Start/Stop)
E3+ overload relay:
Provides three states, (fwd/stop/rev)
or (hi-spd/stop/low-spd)
Commonly used to control motors.
These devices are actually DeviceNet devices. The use of these
devices requires the Rockwell 193-DNENCATR EtherNet/IP to
DeviceNet Adapter.
Rockwell Power Flex 753 Drive Commonly used for motor control and motor speed
Rockwell Power Flex 755 Drive Commonly used for motor control and motor speed
Rockwell Power E300 Overload relay Commonly used to control motors. Three state possible.
2.8.3. Adding New I/O Device Types
The device list above represents the devices that have been qualified and are currently supported at the time of the release
of this document. To determine the current list or to request the addition of a new EtherNet/IP compliant device type, contact
your Honeywell representative
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 21
Version 1.0 Honeywell Proprietary Jan 2017
3. Important Communication Concepts
3.1. IP Addresses & CIP Connections
To completely understand the specifications later in this document, it is important that you understand the concept of an IP
address and the concept of a CIP (Common Industrial Protocol) connection. Each is covered in more detail below.
3.1.1. Ethernet IP Address
As mentioned earlier in this document, Ethernet/IP is CIP (Common Industrial Protocol) over Ethernet. As such, each node
on an Ethernet/IP network is identified by a unique user defined IP address.
The IP address has the following format:
### . ### . ### . ###
Where the first three number sets or octets (### . ### . ###) identify the subnet that the device belongs to and the last three
numbers (###) are referred to as the node index number. The node index is used to identify each unique node on a
particular Ethernet/IP network subnet.
Each node on the Ethernet/IP network subnet must have a unique index number. This is the essential method to identify and
communicate with an Ethernet/IP node.
3.1.2. CIP Connections
The EIM communicates with individual Ethernet/IP nodes using the assigned IP address. The EIM also forms one or more
CIP connections (depending on the device type) to transfer (read and write) data to and from the Ethernet/IP node.
There are two CIP connection types used with the EIM solution, as follows:
Class 1 (Implicit) connections:
Is also often referred to as “I/O” and is utilized for data that is time-critical in nature.
EIM uses these connections for data access for I/O devices such as motor starters, drives, and I/O.
With Implicit Messaging you establish an association (a “CIP connection”) between two devices and produce the Implicit Messages according to a predetermined trigger mechanism, typically at a specified packet rate.
The devices both know and agree on the data formats they will use (i.e., the format is “implied”).
Class 3 (Explicit) connections:
In general has a request/reply (or client/server) nature.
The EIM solution uses these connections specifically for data transfer with the ControLogix processors using UDTs.
Explicit messages include a description of their meaning (expressed explicitly), so the transmission is less
efficient, but very flexible.
In CIP terms, with Explicit Messaging you request a service of a particular object, e.g., a read or a write service.
Compared to Implicit messaging, transmission is less efficient, but very flexible in terms of what can be accessed.
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 22
Version 1.0 Honeywell Proprietary Jan 2017
3.2. EIM IP Address and CIP Connection Usage
The table below is provided to help with the concept of IP address and CIP connection usage by node type.
As shown in the table below, in most cases you use one IP address and one CIP connection per Ethernet/IP node. However,
there are cases where you will use one IP address and multiple CIP connections. One example would be standard I/O
subsystem where the headend (gateway module) is assigned the IP address and each individual I/O module would use one
CIP connection.
As shown in the table, all of the Power Flex drives use 1 IP address and only requires 1 CIP connection to transfer all input
and output data related to the device. However, ArmorPoint I/O with the consolidation option set to OFF would consume 1 IP
address and 1 CIP connection for every I/O module on the backplane.
The I/O consolidation option allows you to consolidate (group) several I/O modules into one grouping so all data is returned
using one CIP connection. However, this would also require you to set a common RPI (Requested Packet Interval) for the
entire group of I/O modules.
It is important to identify the IP and CIP connection requirements for a given device type to ensure you stay within the
connection limits provided later in specification section of this document.
For more details on this subject refer to the Ethernet/IP User’s Guide
IP Address and CIP Connection usage table by node type supported by the EIM solution:
EIP Device
CIP
Connection
Type
IP Address Usage Connection Usage
PF 753 and PF 755 Implicit Class-1
1 per Node 1 per Node (includes input & output data)
E3, E3+, and E300 Implicit Class-1
1 per Node 1 per Node (includes input & output data)
ArmorBlock I/O Implicit Class-1
1 per I/O module/block 1 per I/O module/block
ArmorPoint I/O (consolidation option OFF)
Implicit Class-1
1 per I/O chassis/adaptor 1 per I/O module
ArmorPoint I/O (consolidation option ON)
Implicit Class-1
1 per I/O chassis/adaptor 1 per consolidated/module grouping. 1 or more modules can be in a group.
ControlLogix Explicit Class-3
1 per ControlLogix 1 per ControlLogix
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 23
Version 1.0 Honeywell Proprietary Jan 2017
4. Ethernet/IP Capacity, Rules, and Specifications
4.1. C300 Direct vs. EIM Solution Notes
For purposes of simplifying the list below, the following terms will be used………..
Solution D = C300 Direct Ethernet/IP solution
Solution E = C300 EIM Ethernet/IP solution
1. Both Solution D and Solution E can coexist on the same FTE Community.
2. A given C300 controller can host Solution D or Solution E, but not both.
3. The existence of Solution D will reduce the maximum number of FTE nodes from 330 to 200.
4. Solution D can be hosted on C300 model CC-PCNT01 or CC-PCNT02.
5. Solution E can only be hosted on C300 model CC-PCNT02 with large memory firmware loaded.
6. Both solutions are supported on the C300 50ms CEE only (20ms CEE is not qualified at this time).
7. Solution D: The FTE network and the Ethernet/IP network must use the same subnet. This limits the total number of IP addresses available for EtherNet/IP nodes to 200 (non-FTE IP addresses) max for the entire Server Cluster.
8. Solution E: The FTE network and the Ethernet/IP network must use a separate subnet assignment.
9. Both solutions support C300 redundancy.
4.2. Solution Components and Specifications
See Figure 9. The tables on the following pages provide the specifications for the EtherNet/IP solution. As you view these
tables keep in mind that there are specifications that relate to the C300, EIM, Server Cluster, FTE Community, and
EtherNet/IP network.
Also keep in mind that other solutions (like the C300 Direct EtherNet/IP solution) can further limit the EIM solution.
Figure 9 EtherNet/IP Solution Components
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 24
Version 1.0 Honeywell Proprietary Jan 2017
4.3. Ethernet/IP Performance, Capacity, Limits, and Specifications
4.3.1. EIM with EtherNet/IP - Configuration Limits
EIM (Ethernet Interface Module) with EtherNet/IP Configuration Limits
Definitions:
RPI = Requested Packet Interval CLx = ControlLogix PLC CEE = C300 Control Execution Environment
UDT = User-defined Data Type EIP = Ethernet/IP™ CF9 = Experion Control Firewall
Specification Limit Units
Supported EIP Physical Networks 1,2 DLR (Device Level Ring)
Linear Bus
Switched Star
EIP Implicit reads/writes to EIP I/O type devices Yes
EIP Explicit reads/writes to CLx processors (using UDTs) Yes
Supported RPI setting – For EIP devices (Implicit I/O connections) 3 50 to 2000 milliseconds
Supported RPI setting - For UDTs (Explicit CLx UDT connections) 5 100, 200, 500, 1000,
2000
Milliseconds
EIM – EIP solution….. Required C300 model CC-PCNT02 only
EIM – EIP solution….. Supported C300 CEE 50ms
Number of EIP networks supported per EIM module (or redundant pair) 1
Supported EIM firewall security CF9 firewall on uplink port……………
EIP firewall on downlink port…………
Yes
Yes
Port
port
Network Redundancy from C300 to its associated EIP devices 4 Yes
Supported User Defined Types (UDT) 5, 6
Multi-parameter
Scalar
UDT
UDT
Supported UDT Data types
Single bit (Discrete)
8 bit signed/unsigned integer
16 bit signed/unsigned integer
32 bit signed integer
32 bit IEEE floating point
String (Read from CLx only)
Supported/Tested EIP Network Switches Stratix 5700
Stratix 8000
Supported/Tested EIP Tap (ETAP) 1783–ETAP
Notes:
NOTE 1- EIP network connectivity is through isolated EIM-EIP downlink port (ETH1).
NOTE 2- EIM should not connect directly to the DLR or Linear EIP networks. Stratix 5700 or 1783-ETAPs are required.
NOTE 3- Although RPI value is entered as an integer from 50-2000ms, the entered value will be clamped to a multiple of the
base CEE cycle time (50ms). The value will be clamped to the nearest base-cycle during the LOAD operation (a
value clamped warning will be displayed).
NOTE 4 Complete FTE network redundancy is achieved using redundant CF9s, C300s, EIMs, and FTE cables. Addition EIP
network robustness is achieved by using redundant EIMs and DLR (Device Level Ring) topologies.
NOTE 5- Although RPI value is entered as an integer from 50-2000ms, in R500 and onward, the RPI values are clamped to
the closest allowable UDT RPI values (100, 200, 500, 1000, 2000 ms). Clamping happens at configuration time.
NOTE 6- CLx UDT TAG browsing in Control Builder requires either the Matrikon EIP-OPC server or access to the L5X file
(generated and exported using Rockwell software RSLogix /Studio5000).
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 25
Version 1.0 Honeywell Proprietary Jan 2017
4.3.2. EIM with EtherNet/IP™ - Capacity Limits
EIM (Ethernet Interface Module) with EtherNet/IP™ Capacity Limits
Definitions:
RPI = Requested Packet Interval CLx = ControlLogix PLC CEE = C300 Control Execution Environment
UDT = User-defined Data Type EIP = Ethernet/IP™ CIP™ = Common Industrial Protocol
C300- EIM Capacity Specifications Limit Units
Maximum Number of EIMs per Server Cluster 1 64 EIMs/Cluster
C300s per Server Cluster 4 20 C300s
Console Stations per Server Cluster 4 20 Console Stations
Maximum number of FTE Nodes per FTE Community 4 330 FTE nodes
Maximum Number of C300s per EIM 5 C300 connections to
1 EIM
Maximum Number of EIMs per C300 2, 7 5 EIM connections to 1
C300
EtherNet/IP Device Capacity Specification Limit Units
EIM - Maximum class-1 Implicit CIP connections to EIP (I/O) devices/EIM 9 255 CIP/EIP Class-1
connections per EIM
C300 - Maximum class-1 Implicit CIP connections to EIP (I/O)
devices/C3009 80
CIP/EIP Class-1
connections per C300
EIM - Maximum Class-3 Explicit CIP connections (UDTs) to CLx
processors/EIM 10
CIP/EIP Class-3
connections per EIM
C300 - Maximum Class-3 Explicit CIP connections (UDTs) to CLx
processors/C300 4
CIP/EIP Class-3
connections per C300
Experion User Defined Type (UDTs) Capacity Specification Limit Units
Maximum number of parameters per Multi-parameter/ Aggregate UDT 6 64 Parameters
Maximum input size of a Multi-parameter UDTs - Read parameters 480 bytes
Maximum output data size of a Multi-parameter UDTs - Write parameters 256 bytes
Maximum number of parameters per Scalar UDT 1 Parameter
Maximum input size of a Scalar-parameter UDT - Read parameters 4 bytes
Maximum output size of a Scalar-parameter UDT - Write parameters 4 bytes
EIM User Defined Types (UDTs) Capacity Specification Limit Units
Maximum Multi-parameter UDTs per EIM - to all CLx PLCs combined 3 325 Instances
Maximum scalar UDTs per EIM 8 2000-2325 Instances
C300 User Defined Types (UDTs) Capacity Specification Limit Units
Maximum Multi-parameter UDTs per C300 - to all CLx PLCs combined 3,5 65 Instances
Maximum Scalar UDTs per C300 Controller 3,5,8 400-465 Instances
Notes:
Note 1- There is a 128 EIM License limit per Server Cluster – (64) are allocated for EIMs with the EIP personality loaded and (64)
are allocated for EIMs loaded with IEC 61850 personality. Each EIM (and redundant pair) requires/consumes only1
license.
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 26
Version 1.0 Honeywell Proprietary Jan 2017
Note 2- This number is the combined EIM w/EIP or w/IEC61850 case, e.g. 5 total with either protocol.
Note 3- This maximum can be further limited by other user settings such as RPI settings.
Note 4- Other solutions (such as the C300 Direct EIM solution) can further limit these maximums.
Note 5- Maximum number of EIP I/O nodes (I/O, Drives, Motor Controllers, etc.) and UDTs per C300 are affected by other
factors including %CPU loading of the C300 and the RPI settings for each EIP connection.
Note 6- For arrayed parameters, each array element shall count as one parameter against the maximum stated.
Note 7- The IP addresses of devices on the EIP network do not contribute to the FTE addressing limit. Only the EIMs themselves
count as FTE nodes.
Note 8- Unused Multi-parameter UDT buffers can be allocated to the reach the higher Scaler UDT maximum number. If 65 Multi-
parameter UDTs are not used then user can go up to the max of 465 scalar tags.
Note 9- Refer to section 3.2 (EIM IP Address and CIP Connection Usage).
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 27
Version 1.0 Honeywell Proprietary Jan 2017
4.3.3. EIM with EtherNet/ IP - Performance
EIM (Ethernet Interface Module) with EtherNet/ IP Performance
Definitions:
RPI = Requested Packet Interval CLx = ControlLogix PLC CEE = C300 Control Execution Environment
UDT = User-defined Data Type EIP = Ethernet/IP™ CIP™ = Common Industrial Protocol
PPS = Average Parameters Per Second EIM = Ethernet Interface Module
CDA Specification Limit Units
Overall Data Access Performance
Maximum Total Parameter Access Response Rate 1
(Includes all Server Data Requests, Console Station Data Requests, and
peer communications with C300s)
500 PPS
Display Data Access Capacity 1
Maximum Total CDA Subscribed Parameters per EIM
(Includes all Server Data Requests + Console Station Data Requests +
Peer data requests)
500 parameters
Display Data Access Capacity 1
Maximum Number of Display and Server CDA Connections
22 TCP connections
User Defined Types (UDTs) Data Transfer Specification Limit Units
Maximum Multi-parameter and scalar UDT Reads from all ControlLogix
devices 4
400 Parameters per
second
Maximum Multi-parameter UDT writes at any given time 4 65 parameters
Maximum scalar UDT writes at any given time 3,4 135-200 parameters
C300 to ControlLogix Communications Through EIM Specification Limit Units
Maximum read/write access rate per EIM to non-Redundant CLx 150 transactions / sec
Maximum read/write access rate per EIM to Redundant CLx 75 transactions / sec
Communication Recovery Specification Limit Units
Maximum EIM recovery time following a power cycle to retain configuration
and reconnect to all configured target devices
< 7 minutes
Notes:
Note 1- EIM-EIP solution is not intended for Display and History Data Access from EIP network devices. All CDA access to EIP
nodes (I/O and UDTs) is through the associated C300. Information that is specific to and related to the EIM (as a
module) is accessed using CDA.
Note 2- Only C300 (PCNT02) is supported for Peer connections using CDA.
Note 3- If Multi-parameter UDT buffers are not used, C300 can include the Multi-parameter UDT limits for scalar UDT writes.
Note 4- Read/write of string data type is not supported using scalar UDTs.
Note 5- String data type writes to Rockwell CLx are not supported with either Multi-parameter or scalar UDTs.
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 28
Version 1.0 Honeywell Proprietary Jan 2017
4.3.4. EIM with EtherNet/IP™ - Redundancy Specifications
EIM (Ethernet Interface Module) - EtherNet/IP™ Redundancy Specifications
Definitions:
RPI = Requested Packet Interval CLx = ControlLogix PLC CEE = C300 Control Execution Environment
UDT = User-defined Data Type EIP = Ethernet/IP™ CIP™ = Common Industrial Protocol
Specification Limit Units
EIM Function Block Redundancy Configuration Selection: “Module is Redundant”
Number of IOTAs (Input Output Terminal Assembly) used for Redundant
EIM configurations
2 IOTAs
Redundant Device Index Configuration Device Index = n, where n is an odd FTE index
value and the partner device Index = n+1
Redundancy Cable Media Support Shielded Twisted Pair
(STP)
Ethernet
Redundancy Cable Lengths 2 36, 48, 60, 84 Inches
Maximum Publication Processing Switchover Interruption Time 1 500 ms
Maximum Initial Synchronization Time (from Sync Start to Completion) <10 Seconds
Maximum Elapsed Time Between Commanded Switchover and Completion
of Initial Synchronization
150 Seconds
Maximum Elapsed Time Between Switchover Due to Power Cycle of the
Primary and Completion of Initial Synchronization
150 Seconds
Notes:
Note 1- On EIM switchover, EIM can go up to 2 seconds to reform all the EIP IO connections on the downlink, dependent on the
number of EIP IOs configured through that EIM. During this time the IOM and channel blocks in the C300 will hold and
continue calculations with the last IO data received before EIM switchover.
Note-2- This is the same cable set as used with C300 redundancy.
4.3.5. UDTs – Supported Data Types
Experion
Data Type
Equivalent
ControlLogix
Data Type
Data
Read/Write
?
Description/Notes
BOOLEAN Bool R & W 1 –byte… Logical Boolean with values TRUE and FALSE
INT8 SINT R & W 8–bit signed/unsigned integer
INT16 INT R & W 16–bit signed/unsigned integer
INT32 DINIT R & W 32–bit signed integer
FLOAT32 Real R & W 32–bit IEEE floating point
STRING STRING Read only
Note 1: Strings are not supported for Scalar UDTs.
Note 2: String reads from ControlLogix to C300 only. String writes from C300 to ControlLogix are not supported.
Experion EIM EtherNet/IP Interface Specification, EP03-561-500 29
Version 1.0 Honeywell Proprietary Jan 2017
5. Solution Model Numbers and Licensing
Model Description
CC-PEIM01 Series C EIM (Ethernet Interface Module).
CC-TEIM01 Series C EIM IOTA (Input Output Terminal Assembly).
TC-EPLX02 R500 EIM (EtherNet/IP) use license. One required per EIM (or redundant pair).
Important! The EIM EtherNet/IP solution requires the use of C300 module CC-PCNT02. The solution will not run on
C300 module CC-PCNT01.
For more information
To learn more about Honeywell’s products or
solutions visit our website
www.honeywellprocess.com or contact your
Honeywell account manager.
Automation & Control Solutions
Process Solutions
Honeywell
1250 West Sam Houston Parkway South
Houston, TX 77042
Honeywell House, Arlington Business Park,
Bracknell, Berkshire, England RG12 1EB UK
Shanghai City Centre, 100 Junyi Road
Shanghai, China 20051
www.honeywellprocess.com
Experion® is a registered trademark of Honeywell International Inc.
All other products and brand names shown are trademarks of their respective owners.
This document contains Honeywell proprietary information. It is published for the sole usage of Honeywell Process Solutions’
customers and prospective customers worldwide. Information contained herein is to be used solely for the purpose submitted, and
no part of this document or its contents shall be reproduced, published, or disclosed to a third party without the express
permission of Honeywell International Inc.
While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of
merchantability and fitness for a particular purpose and makes no express warranties except as may be stated in its written
agreement with and for its customer.
In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The information and specifications in
this document are subject to change without notice.
EP03-561-500 Jan 2017 © 2014 Honeywell International Inc.