b0700wm A

Foxboro™ DCS
FDC280 EtherNet/IP Client Driver
User’s Guide
*B0700WM* *A*
B0700WM, Rev A
May 2022
https://www.se.com
Legal Information
The Schneider Electric brand and any trademarks of Schneider Electric SE and its
subsidiaries referred to in this guide are the property of Schneider Electric SE or its
subsidiaries. All other brands may be trademarks of their respective owners.
This guide and its content are protected under applicable copyright laws and furnished
for informational use only. No part of this guide may be reproduced or transmitted in
any form or by any means (electronic, mechanical, photocopying, recording, or
otherwise), for any purpose, without the prior written permission of Schneider Electric.
Schneider Electric does not grant any right or license for commercial use of the guide
or its content, except for a non-exclusive and personal license to consult it on an "as is"
basis. Schneider Electric products and equipment should be installed, operated,
serviced, and maintained only by qualified personnel.
As standards, specifications, and designs change from time to time, information
contained in this guide may be subject to change without notice.
To the extent permitted by applicable law, no responsibility or liability is assumed by
Schneider Electric and its subsidiaries for any errors or omissions in the informational
content of this material or consequences arising out of or resulting from the use of the
information contained herein.
FDC280 EtherNet/IP Client Driver User’s Guide
Table of Contents
Important Safety Instructions ..........................................................................5
Preface ...............................................................................................................6
Revision Information.........................................................................................6
Related Documents..........................................................................................6
EtherNet/IP Protocol Documents .................................................................6
ControlLogix Documents.............................................................................6
Schneider Electric Products Mentioned in this Document ....................................7
Global Customer Support .................................................................................7
We Welcome Your Comments...........................................................................7
Chapter 1: Getting Started ..............................................................................8
Overview of Redundant ControlLogix.................................................................8
Understanding the Installation and Configuration Process ...................................9
Configuration Guidelines ..................................................................................9
Security Guidelines ........................................................................................10
Supported Hardware Configurations ................................................................10
System Requirements .................................................................................... 11
Hardware Requirements ...........................................................................12
Software Requirements ............................................................................12
Chapter 2: Installation and Uninstallation ...................................................14
Installing on a Foxboro DCS Using the ICC and CCS FDC280 Configurator to
Configure the Driver .......................................................................................14
Installing on a Foxboro DCS Using the Control Software Configurator to
Configure the Driver .......................................................................................17
Procedure When Using Separate Workstations for Control Software
Configurator and Hosting the FDC280........................................................17
Procedure for Workstation Hosting FDC280 ...............................................17
Procedure for Workstation with Control Software Configurator .....................19
Procedure When Using a Single Station for the FDC280 Configuration
and Hosting the FDC280...........................................................................23
Uninstalling FDC280 EtherNet/IP Driver...........................................................23
Uninstalling using CD-ROM with the FDC280 EtherNet/IP Driver .......................23
Uninstalling from the Control Panel..................................................................25
Downloading the EtherNet/IP Driver to the FDC280 ..........................................26
Chapter 3: Configuration ...............................................................................27
Configuration Details ......................................................................................27
Configuring the Equipment Control Block for the Drivers (ECB200) ....................28
Configuring the ControlLogix Connection (ECB201)..........................................28
DVNAME .................................................................................................29
DVOPTS .................................................................................................29
Configuring Groups and I/O Point Aliases for ECB201.................................30
ControlLogix Configuration for Heartbeat Message Support ..............................32
ControlLogix Configuration for Time Synchronization (+TS) Support ..................32
Configuring DCI Blocks to Map I/O Points to DCS.............................................34
DCI Blocks and Default Data Types ...........................................................35
B0700WM, Rev A 3
Support of User-defined Structured Arrays .................................................37

Word Mirroring Option with PAKIN blocks ...................................................42
Device Diagnostic Blocks ..........................................................................45
Turning on the Driver and Enabling Communication with the device ...................47
Chapter 4: Principles of Operation ...............................................................49
EtherNet/IP Driver Operation ..........................................................................49
Fault Tolerant FDC280 to Redundant ControlLogix Interface with no Single
Point Failure ..................................................................................................49
Device ECB201 Operation and Status on the System Manager .........................50
Troubleshooting .............................................................................................51
Appendix A: FDC280 Diagnostic Driver Support .......................................53
Displaying the Packets in EtherNet/IP Format ..................................................54
Appendix B: EtherNet/IP Message Formats Used with
ControlLogix ....................................................................................................56
Multi Request Service for Reading or Writing Multiple Points .............................56
ControlLogix Read Message Format ..........................................................56
ControlLogix Write Message Format ..........................................................56
ControlLogix Read/Write Result Message Format .......................................57
Appendix C: ControlLogix Configuration .....................................................59
ControlLogix IP Address Configuration.............................................................59
Configuring IP Address for the ENBT module..............................................59
Configuring Two ENBT Modules in the Same Chassis.......................................61
Configuring IP Address for the EN2T Module ..............................................61
Configuring Two EN2T Modules in the Same Chassis .................................61
ControlLogix Point Tag Name and Database Configuration................................62
Configuring Drivers...................................................................................62
Appendix D: ControlLogix Redundancy System ........................................74
Ethernet Switchover .......................................................................................74
Configuring Same IP Address to the EN2T Modules..........................................75
Glossary ...........................................................................................................77
Index .................................................................................................................79
4 B0700WM, Rev A
Important Safety Instructions FDC280 EtherNet/IP Client Driver User’s Guide
Important Safety Instructions

Read these instructions carefully and look at the equipment to become familiar with it
before trying to install, operate, service, or maintain it. The following safety messages
might appear throughout this manual or on the equipment to warn of potential hazards
or to call attention to information that clarifies or simplifies a procedure.
The addition of this symbol to a “Danger” or “Warning” safety message

indicates that an electrical hazard exists that results in personal injury if
the instructions are not followed.
This safety alert symbol that lets you know about potential personal
injury hazards. Obey all safety messages with this symbol to avoid
possible injury or death.
DANGER
DANGER indicates a hazardous situation which, if not avoided, will result in death
or serious injury.
Failure to follow these instructions will result in death or serious injury.
WARNING
WARNING indicates a hazardous situation that, if not avoided, could result in
death or serious injury.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
CAUTION
CAUTION indicates a hazardous situation that, if not avoided, could result in
minor or moderate injury.
Failure to follow these instructions can result in injury or equipment damage.
NOTICE
NOTICE is used to address practices not related to physical injury.
Failure to follow these instructions can result in equipment damage.
Please Note
Electrical equipment should only be installed, operated, serviced, and maintained by
qualified personnel. No responsibility is assumed by Schneider Electric for any
consequences arising out of the use of this material.
A qualified person is one who has skills and knowledge related to the construction,
installation, and operation of electrical equipment and has received safety training to
recognize and avoid the hazards involved.
B0700WM, Rev A 5
FDC280 EtherNet/IP Client Driver User’s Guide Preface
Preface
The Field Device Controller (FDC280) EtherNet/IP Driver integrates data from Allen-
Bradley ControlLogix devices in to EcoStruxure™ Foxboro™ DCS. The driver uses the
EtherNet/IP Explicit tag-based protocol for communication. The Driver supports
communication on simplex and fault-tolerant (redundant) Foxboro DCS FDC280
configurations.
Before using this driver, you should be generally familiar with the Foxboro DCS, and
with the Standard and Compact 200 Series Subsystem User’s Guide (B0400FA).
You should also be familiar with the EtherNet/IP protocol that you plan to use to
interface to the Foxboro DCS.
Revision Information
This is the first release of this document.
Related Documents
• Integrated Control Block Descriptions (B0193AX)
• Integrated Control Software Concepts for CP270, FCP280, and FDC280 User’s
Guide (B0700AG)
• System Definition: A Step-by-Step Procedure (B0193WQ)
• Standard and Compact 200 Series Subsystem User’s Guide (B0400FA)
• Control Network Architecture Guide (B0700AZ)
• Process Operations and Displays (B0700BN)
• FoxView Software (B0700FC)
• Field Device Controller 280 (FDC280) User's Guide (B0700GQ)
• System Manager.(B0750AP)
EtherNet/IP Protocol Documents

• The Everyman’s Guide to EtherNet/IP by John S.Rinaldi with Jamin Wendorf
ControlLogix Documents
• Allen-Bradley ControlLogix Redundancy System
(Publication 1756-UM535_-en-p - October 2009)
• Allen-Bradley ControlLogix® Controllers User Manual
(Publication 1756-UM001F- EN-P- May 2005)
• Allen-Bradley Logix5000 Data Access - Reference Manual
(Publication 1756-RM005A-EN-E – March 2000)
• Allen-Bradley ControlLogix Redundancy System
(Publication 1756-UM523E-EN-P- May 2005)
6 B0700WM, Rev A
Preface FDC280 EtherNet/IP Client Driver User’s Guide
Schneider Electric Products Mentioned in this Document

EcoStruxure™ Foxboro™ DCS FDC280
EcoStruxure™ Foxboro™ DCS
Global Customer Support

For support, visit https://pasupport.schneider-electric.com (registration required).
We Welcome Your Comments

To help us improve documentation, we want to know about any corrections,
clarifications, or further information you would find useful. Send us an email at
systemstechpubs@se.com.
This email address is only for documentation feedback. If you have a technical
problem or question, contact Global Customer Support.
B0700WM, Rev A 7
FDC280 EtherNet/IP Client Driver User’s Guide Chapter 1: Getting Started
Chapter 1: Getting Started

The Field Device Controller (FDC280) EtherNet/IP Driver (“EtherNet/IP Driver”
throughout this guide) integrates data from ControlLogix PLCs in to EcoStruxure™
Foxboro™ DCS. The driver supports EtherNet/IP Explicit tag-based protocol for
communication with ControlLogix PLCs. This driver supports communication on
simplex and fault-tolerant (redundant) Foxboro DCS FDC280 configurations.
EtherNet/IP is the application protocol used for this interface, where “IP” stands for
Industrial protocol. EtherNet/IP is part of a class of protocols named CIP (Common
Industrial Protocol). It is an open protocol published and maintained by the ODVA
organization. It runs on top of TCP/IP or UDP/IP.
The driver enables device interfaces on these networks:
• TCP/IP: Ethernet 10/100Mbps/1Gbps networks
Overview of Redundant ControlLogix

The ControlLogix redundancy system uses an identical pair of ControlLogix chassis to
keep the machine or process running if a problem occurs with a controller. When a
failure is detected in any of the components of the primary chassis, control switches to
the secondary chassis.
A switchover occurs for any of these conditions in the Primary chassis:
• Loss of power
• Major fault of the controller
• Removal, insertion, or detected failure of any module in the primary chassis
• Break or disconnection of a ControlNet tap or Ethernet cable
• Command from the Primary controller
• Command from RSLinx® software
Redundancy requires no additional programming. It uses 1757-SRM modules to
maintain communications between the pair of redundant chassis. In a redundant
system, these terms describe the relationship between the two redundant chassis:
Term Description
Primary Controller The controller that is currently controlling the
machine or process.
Primary Chassis The chassis that contains the primary controller
or controllers.
Secondary Controller The controller that is standing by to take control
of the machine or process. A secondary
controller always resides in a different but
identical chassis from the primary controller.
Secondary Chassis The chassis that contains the secondary
controller or controllers.
Switchover Transfer of control from the primary controller to
the secondary controller. After a switchover, the
controller that takes control becomes the
primary controller. Its partner controller (the
controller that was previously the primary
controller) becomes the secondary controller.
8 B0700WM, Rev A
Chapter 1: Getting Started FDC280 EtherNet/IP Client Driver User’s Guide
Understanding the Installation and Configuration Process

These are the main steps to install, configure, and use the driver.
1 Review the supported hardware Supported Hardware Configurations,

configurations. page 10
2 Install the driver. Installing on a Foxboro DCS Using
the ICC and CCS FDC280
Configurator to Configure the Driver,
page 14
3 Download the FDC280 image to the Downloading the EtherNet/IP Driver
simplex or fault-tolerant FDC280. to the FDC280, page 26
4 Configure blocks. • Configuring the Equipment
Control Block for the Drivers
(ECB200), page 28
• Configuring the ControlLogix
Connection (ECB201), page 28
• Configuring DCI Blocks to Map I/
O Points to DCS, page 34
5 Turn on the driver and enable Turning on the Driver and Enabling
communication with the device. Communication with the device,
page 47
6 Enabling diagnostic driver support. Appendix A: FDC280 Diagnostic
Driver Support, page 53
Configuration Guidelines
The FDC280 EtherNet/IP driver supports one ControlLogix PLC and up to 8000 I/O
points, as long as the total number of ECB blocks, DCI blocks, station block, and
compounds it runs does not exceed 8262.
This driver image supports only a single instance of the EtherNet/IP Driver running on
the Ethernet port.
• The EtherNet/IP Driver cannot run concurrently with any other driver type.
• The driver supports up to 8000 DCI blocks. For more details on the number of
points supported by the FDC280, see Field Device Controller 280 (FDC280)
User's Guide (B0700GQ).
• Using the ICC and CCS FDC280 Configurator, the driver supports tag names up
to 29 characters long and in upper case only. The driver does not have this
limitation in Control Software. For more information, see Configuring Groups and
I/O Point Aliases for ECB201, page 30.
• Under Ethernet port ECBP of FDC280, one EtherNet/IP Driver instance can be
created.
• Configure the Input/Output DCI Blocks for device ECB201 configured and turn on
all the compounds with DCI Blocks.
B0700WM, Rev A 9
Security Guidelines
Follow the security guidelines for the FDC280 described in Field Device Controller
280 (FDC280) User’s Guide (B0700GQ).
For more information on the security aspects and considerations of the Foxboro
Distributed Control System (DCS), see Foxboro DCS Cybersecurity Reference Guide
(B0700HZ).
Supported Hardware Configurations

The FDC280 EtherNet/IP Driver works in both FDC280 Simplex and Fault-tolerant
configurations. The EtherNet/IP Driver communicates with the ControlLogix over
Ethernet protocol.
See these images for examples of supported hardware configurations for Ethernet
interface for interfacing Foxboro DCS and ControlLogix.
Figure 1 - FDC280 EtherNet/IP Driver Simplex Interfaced to Simplex

ControlLogix
10 B0700WM, Rev A
Figure 2 - FDC280 EtherNet/IP Driver Fault-Tolerant Interfaced to Redundant

ControlLogix
Figure 3 - FDC280 EtherNet/IP Driver Fault-Tolerant Interfaced to Simplex

ControlLogix
System Requirements
The FDC280 interfaces with the other hardware and software elements of the Foxboro
DCS to provide control, alarming, trending, and display capabilities. Software residing
in the FDC280 and Foxboro DCS workstations provide full support for the EtherNet/IP
Driver functionality.
To support the FDC280 image that introduces EtherNet/IP support, you require:
B0700WM, Rev A 11
• Foxboro DCS Control Core Services v9.3 or later

On stations running Control Core Services v9.3 – 9.4, install Maintenance Pack
MP47481162B.
On stations running Control Core Services v9.5, install Maintenance Pack
MP59953075.
These Maintenance Packs are available from Global Customer Support at https://
pasupport.schneider-electric.com (registration required).
• Foxboro DCS Control Software (CS) 7.1.1 or later
• Foxboro DCS System Manager 2.13 or later
Hardware Requirements
• See the Field Device Controller 280 (FDC280) User's Guide (B0700GQ).
• Allen-Bradley ControlLogix Controller Revision 32.011 or above with either a
1756-ENBT EtherNet/IP module Revision 6.001 or above or a 1756-EN2T
EtherNet/IP module is required. See Allen-Bradley ControlLogix Controllers User
Manual (Publication 1756-UM001F- EN-P) to install, configure, and operate a
ControlLogix system.
Software Requirements
Workstation Software
The workstation software required for the FDC280 includes:
• Foxboro DCS Control Editors
These editors are part of Control Software and provide for configuration of the
FDC280 in the Control Network. The software prepares configuration files that
contain information needed by the FDC280s to communicate with the devices
they are connected to. This software executes in a Foxboro DCS workstation and
includes the necessary user interface. Software in the FDC280 supports run-time
use of the configured information.
• Foxboro DCS Control Core Services (CCS)
This software integrates the FDC280 and connected devices into the overall
Foxboro DCS equipment configuration. Control Core Services includes the CCS
FDC280 Configurator, which allows you to configure additional data for the
FDC280’s operation, including archival capabilities. This product is discussed in
Field Device Controller 280 (FDC280) User's Guide (B0700GQ).
• Configuration of FDC280 is supported both in the Control Software and ICC.
• FDC280 EtherNet/IP Driver License: The license file is required to choose
EtherNet/IP client as a driver to run in FDC280, in the configuration steps. The
license file is also included in the FDC280 EtherNet/IP Driver media.
FDC280 Firmware
The FDC280 firmware for the EtherNet/IP Driver is provided as an image file. This
image is included in the EtherNet/IP Driver media. This firmware image includes:
• EtherNet/IP Driver: Part of the FDC280 image with highly flexible configuration
facilitating interfacing to ControlLogix.
12 B0700WM, Rev A
• Run-Time Software: Supports the reading and writing of data from and to the
connected ControlLogix’s field I/O values in the Foxboro DCS. This software
includes Distributed Control Interface (DCI) control blocks that interface to I/O
signals from the device.
• Diagnostic Driver: Provides startup and maintenance fault detection and
diagnosis for the FDC280.
B0700WM, Rev A 13
FDC280 EtherNet/IP Client Driver User’s Guide Chapter 2: Installation and Uninstallation
Chapter 2: Installation and Uninstallation

The installation provides Complete and Custom installation types. Use Complete to
install all components on one workstation. Use Custom to select the components to
be installed on a workstation.
The installation media includes:
• FDC280 EtherNet/IP Driver Image (EthernetIP_1.0.FDC280)
Provides the EtherNet/IP Driver functionality.
It is installed to path ..\usr\fox\sp\files
Load this image to the FDC280 module from System Manager. The steps to
update the image are specified in Downloading the EtherNet/IP Driver to the
FDC280, page 26.
• FDC280 EtherNet/IP Driver License
Enables you to configure the EtherNet/IP Driver on the FDC280. This component
installs the required entries on the workstation to enable configuration of FDC280
EtherNet/IP Driver using the CCS Configurator or Control Software Editors.
If you are using ICC and the CCS FDC280 Configurator to configure the FDC280,
install this component on the workstation with Control Core Services hosting the
FDC280.
If you are using the Control Software Editors to configure the FDC280, install this
media on the Control Software Client workstation.
Installing on a Foxboro DCS Using the ICC and CCS FDC280

Configurator to Configure the Driver
1. Insert the CD-ROM with the FDC280 EtherNet/IP Driver in the host workstation's
media drive or mount the installation media to a network location accessible by
the host workstation.
2. In File Explorer, go to the root directory of the CD-ROM or installation.
3. Double-click the installer package. The FDC280 EthernetIP Driver Setup
window opens.
14 B0700WM, Rev A
Chapter 2: Installation and Uninstallation FDC280 EtherNet/IP Client Driver User’s Guide
4. Click Next.
5. Click Complete to install the required components.
The window displays the components that will be installed.
B0700WM, Rev A 15
6. When installation is complete, click Finish.
16 B0700WM, Rev A
Installing on a Foxboro DCS Using the Control Software

Configurator to Configure the Driver
Procedure When Using Separate Workstations for Control Software
Configurator and Hosting the FDC280
To complete this installation, you will:
1. Install the EtherNet/IP Driver Image on the workstation hosting the FDC280.
2. Install the EtherNet/IP Driver Licenses on the workstation with the Control
Software Configurator.
Procedure for Workstation Hosting FDC280

2. In File Explorer, go to the root directory of the CD-ROM or installation media.
window opens.
4. Click Next.
B0700WM, Rev A 17
5. In Choose Setup Type, click Custom.
6. Clear EthernetIP Driver Key, then click Next.
18 B0700WM, Rev A
7. In the Installation Summary window, click Install.
Procedure for Workstation with Control Software Configurator

B0700WM, Rev A 19
2. In File Explorer, go to the root directory of the CD-ROM or installation media.

window opens.
4. Click Next.
5. In Choose Setup Type, click Custom.
20 B0700WM, Rev A
6. Unselect EthernetIP Driver Image, then click Next.
7. In the Installation Summary window, click Install.
B0700WM, Rev A 21
To import the driver definition file to enable configuration of the EtherNet/IP Driver
using Control Software, see Importing the Driver Definition File, page 22.
Importing the Driver Definition File

The driver definition file allows you to configure the EtherNet/IP Driver using the
Control Software.
Import the FDC driver file (DriverDefinition.xml) into the Galaxy database. This
file was installed on the Control Software client workstation as described in the
previous steps.
You only need to load this file once.
1. In Control Editors, select Galaxy > Import > FDC Driver. The Import FDC
Driver dialog box appears.
2. Click the “...” beside the text field at the top of the dialog box, then browse to the
location where the FDC280 EtherNet/IP Driver file was installed on the Control
Software client workstation. The location depends on where ArchestrA is
installed. Typically, this file is in D:\Program Files \ArchestrA\Framework
\Bin\Invensys\FDC Drivers\EthernetIP 1.0\DriverDefinition.
xml folder.
3. Select the FDC driver file, then click Validate.
The station is ready to configure the EtherNet/IP Driver on FDC280.
22 B0700WM, Rev A
Procedure When Using a Single Station for the FDC280

Configuration and Hosting the FDC280
1. Install the Driver media. See Installing on a Foxboro DCS Using the ICC and CCS
FDC280 Configurator to Configure the Driver, page 14.
2. Import the driver definition file to enable configuration of EtherNet/IP Driver using
Control Software Editors. See Importing the Driver Definition File, page 22.
Uninstalling FDC280 EtherNet/IP Driver

The driver can be uninstalled in these two ways:
• Using CD-ROM with the FDC280 EtherNet/IP Driver
• From the Control Panel
Uninstalling using CD-ROM with the FDC280 EtherNet/IP

Driver
2. In File Explorer, go to the root directory of the CD-ROM or installation.
3. Double-click the installer package.
The FDC280 EthernetIP Driver Setup window appears.
4. Click Next.
B0700WM, Rev A 23
5. Click Remove.
6. Click Remove.
24 B0700WM, Rev A
7. Click Finish.
8. The FDC280 EtherNet/IP Driver is uninstalled.
Uninstalling from the Control Panel

1. On the Control Panel, click Programs, and then click Programs and Features.
Double-click on FDC280 EthernetIP Driver to uninstall.
2. Click Yes.
3. The FDC280 EthernetIP Driver is uninstalled and removed from Programs and
Features.
B0700WM, Rev A 25
Downloading the EtherNet/IP Driver to the FDC280

NOTE: This is applicable for both Simplex and Fault Tolerant FDC280
configurations.
After installing the EtherNet/IP Driver image (EthernetIP_1.0.FDC280) on the hosting
station, download the image to the FDC280:
1. Install the FDC280 modules as described in "Installing the Field Device Controller
280" in the Field Device Controller 280 (FDC280) User's Guide (B0700GQ).
2. Initialize the FDC280s.
3. Verify the FDC280 EtherNet/IP driver image file EthernetIP_1.0. FDC280 is in the
.../usr/fox/sp/files relative folder path relative to the IA Root path.
4. Run the batch script RenameEthernetIP.BAT. The script file has commands to
rename the existing OS3I80 file to OS3I80.SBY, and rename the
EthernetIP_1.0. FDC280 file to OS3I80.
5. Perform a Major Image update operation as described in "Major Image Update"
under "FDC280 Functionality" in Field Device Controller 280 (FDC280) User's
Guide (B0700GQ).
NOTICE
POTENTIAL DATA LOSS AND EQUIPMENT DAMAGE
Confirm you are performing an image update on the correct FDC280 by
checking the letterbug of the FDC280. If you are not performing this operation
on the correct FDC280, the operation may lead to disruptions in control.
Failure to follow these instructions can lead to data loss and equipment
damage.
6. After the image update process has successfully completed, run the batch script
RestoreEthernetIP.BAT. The script file has commands to rename the
OS3I80 file to EthernetIP_1.0.FDC280 and rename the OS3I80.SBY file to
OS3I80.
26 B0700WM, Rev A
Chapter 3: Configuration FDC280 EtherNet/IP Client Driver User’s Guide
Chapter 3: Configuration
The connection between the FDC280 and its field devices includes these logical
elements in order:
• FDC280
• FDC280 I/O Ethernet port
• FDC280 driver
• ControlLogix (called “FDC field devices” in the Control Software)
Ethernet port connections are configured in the Control Editors or in ICC with the CCS
FDC280 Configurator.
The FDC280 input/output (reading/writing data to/from the ControlLogix) uses
equipment control blocks (ECBs) and Distributed Control Interface (DCI) blocks. The
DCI blocks contain the identification of the data to be transferred to/from the device.
There is one ECB201 per device. There is one ECB200 per driver.
This table lists the ECBs and DCI blocks used with the FDC280. For more detailed
descriptions of the ECBs and DCI blocks used with the FDC280, see Field Device
Controller 280 (FDC280) User's Guide (B0700GQ) and Integrated Control Block
Descriptions (B0193AX).
Table 1 - ECBs and DCI Blocks Used with the FDC280 EtherNet/IP Driver
ECB/DCI Block Description

Primary ECB/ Primary ECBs, representing the FDC280’s I/O Ethernet port
ECBP
ECB200 Parent ECB, representing the FDC280’s EtherNet/IP Driver
ECB201 Child ECB, representing a device
BIN Boolean Input DCI block
BINR Redundant Boolean Input DCI block
BOUT Boolean Output DCI block
RIN Real Input DCI block
RINR Redundant Real Input DCI block
ROUT Real Output DCI block
IIN Integer Input DCI block
IINR Redundant Integer Input DCI block
IOUT Integer Output DCI block
PAKIN Packed Input DCI block
PAKINR Redundant Packed Input DCI block
PAKOUT Packed Output DCI block
Configuration Details
For the configuration details applicable to all the drivers, as well as the configuration
details specific to the EtherNet/IP Driver, see Field Device Controller 280 (FDC280)
User's Guide (B0700GQ).
B0700WM, Rev A 27
FDC280 EtherNet/IP Client Driver User’s Guide Chapter 3: Configuration
For configuration of the Primary ECB (ECBP) for the EtherNet/IP Driver, see Field
Device Controller 280 (FDC280) User's Guide (B0700GQ) and consider the described
limitation.
NOTE: To make any configuration changes to an Ethernet port ECBP, it must be
set to offline mode.
Configuring the Equipment Control Block for the Drivers

(ECB200)
ECB200 is the equipment control block for the FDC280’s driver. This FDC280
EtherNet/IP Driver image supports Ethernet communication.
You can create only one instance of the (ECB200) of the EtherNet/IP driver.
See Integrated Control Block Descriptions (B0193AX) for the ECB200 parameter
definitions.
NOTE: To make any configuration changes to the driver, ECB200 must be set to
offline mode.
Parameter Value Definition

DEV_ID * 6-character ID of the FDC280 driver
HWTYPE 1 The Hardware Type should be:
• 1 for the FDC280’s Ethernet
functionality
SWTYPE 200 The Software Type should be 200, for the
FDC280’s Ethernet functionality
(Automatically filled in)
PARENT * Block name of parent Primary ECB
(ENET_PORT1)
DRVRID 8 Driver ID:
• 8 for EtherNet/IP driver 1.0
CPARM1TO CPARM6 * Not supported
Configuring the ControlLogix Connection (ECB201)

Configure the ECB201 block to represent an ControlLogix that needs to be connected.
For more information on configuring an ECB201 block, see Field Device Controller
280 (FDC280) User's Guide (B0700GQ). This table shows the required configurations
for ECB201.
Table 2 - ECB201 Block Key Parameters/Values

NAME * Name of the block
TYPE ECB201 Type of block
DEV_ID Name Device ID
HWTYPE 1 1 for Ethernet
28 B0700WM, Rev A
Table 2 - ECB201 Block Key Parameters/Values (Continued)

SWTYPE 200
PARENT * Name of the parent ECB200
DVNAME * ControlLogix IP Address
See DVNAME, page 29 for more details.
DVOPTS .... ControlLogix options
See DVOPTS, page 29 for more details.
DVNAME
Case: Simplex configuration FDC280 Case: Redundant with redundant
Ethernet/IP Driver Simplex Interfaced modules FDC280 EtherNet/IP Driver
to Simplex ControlLogix, page 10 Fault-Tolerant Interfaced to
Redundant ControlLogix, page 11
Or
Case: FDC280 EtherNet/IP Driver
Fault-Tolerant Interfaced to Simplex
ControlLogix, page 11
Configure the IP address of the Specify the IP address of the Primary
ControlLogix Ethernet port. ControlLogix Ethernet port.
For example: 192.168.1.150 For example: The redundant Control
Logix Primary module is having the IP
address 192.168.1.20 and SYNC
module is having the IP address
192.168.1.21 then specify the IP
address 192.168.1.20 in DVNAME
parameter.
NOTE: If the IP address in the DVNAME parameter in ECB201 is incorrectly

formatted or not valid, the block is set to the “NOT READY” state and displays
“INVALID DEVICE NAME” in the DCI Block Detailed Display and displays an
Smon Log message as “Invalid Device name configured in DVNAME parameter”.
DVOPTS
Option Description
+@ To specify a scan rate, add “+@X”, where the value of X is in
tenths of a second (the default value is 10, which corresponds to
1 second). X can be one or any higher number.
+TO= To specify how long the driver waits for a response to a
command before retrying, add "+TO=X", where the value of X is
in tenths of a second (the default value is 10, which corresponds
to 1 second). The driver supports the minimum value as 100ms
(+TO=1) and maximum values as 60s(+TO=600).
B0700WM, Rev A 29
Option Description
+SN= To specify the slot number of the ControlLogix processor card,
add “+SN= m”, where m is the physical slot number in the
chassis (default is Slot 0). The driver supports 16 for the
maximum slot number (+SN=16).
+TS Time synchronization of EcoStructure Foxboro DCS software
with ControlLogix devices:
To enable this function add “+TS”.
To use the “TS” option, configure the ControlLogix device as
described in ControlLogix Configuration for Time Synchronization
(+TS) Support section.
The TS feature allows the ControlLogix to be time synchronized
with the Foxboro DCS system with an accuracy of one second.
The driver checks the ControlLogix time at an interval of 30
minutes and sets the new time if required.
NOTE:
• Before modifying the DVNAME or DVOPTS parameters, disable the
ControlLogix communication. After completing modifications, re-enable the
ControlLogix communication.
• The first option configured at DVOPTS need not be preceded with + symbol.
Configuring Groups and I/O Point Aliases for ECB201

Configuring groups and I/O point aliases is required only if any of these apply:
• By default, the driver supports tag names up to 29 characters long; whereas, the
maximum size of a tag name allowed in ControlLogix software is 40 characters.
The driver provides the option to support tag names up to 40 characters by
configuring groups and I/O point aliases.
• Tag names are case sensitive.
• Scanning of different groups of points at different rates. A few important points for
which you need frequent updates can be put in a group with a fast scan rate while
the other groups of points can be scanned at a slower scan rate.
NOTE: Configuring Groups and I/O Point Aliases for ECB201 is allowed only in
Control Software. The CCS configurator does not support this feature.
1. To configure the Groups and Point Aliases, double-click the device object to open
the Editor as shown in this image.
30 B0700WM, Rev A
2. In the Control Editor, click the Groups tab, configure the table Groups shown in
the tab.
Group Configuration
1. Set the Group Name and Scan Rate parameters.
Group Name must be unique, and not exceed 128 characters. The image is an
example usage with EtherNet/IP Driver.
• Group Name – Any unique alphanumeric name for the group
• Scan Rate – Specify the Scan Rate for the Group in milliseconds resolution
• Phase – Leave the field blank
• Custom Parameter 1 to Custom Parameter 4: Leave the fields blank
2. When you have completed configuring all the groups, click a blank row to save
the configuration. If you do not click outside the current row, the configuration is
not saved.
I/O Point Aliases Configuration

In the Control Editor, click the I/O Point Aliases tab, configure the table I/O Point
Aliases as shown in the image.
• Name: It is the PNT_NO parameter of the associated DCI block. This is also what
you see in the HMI. It is an alias name of the point in the ControlLogix.For Control
Logix data types binary or float enter “alias name”. For example LIMIT_
SWITCH1. The Alias Name length should not exceed 32 characters and all in
upper case.
For Control Logix data type integer enter “alias name:datatype”, where data type
can be S1 or S2 or S4 or U2 or U4 as listed in DCI Block Types vs. AB-
ControlLogix Data Types, page 35. For Timer, Counter and Control Data types,
enter the “alias name.field name”. The field name after alias name can be any
one of those listed in Fields Supported In Timer, Counter and Control Data Types,
page 35. An example is PKTIMER.CTL. The Alias Name length should not
exceed 32 characters.
• Address: Enter the actual tag name in the ControlLogix device for all data types
except Timer, Counter and Control data types. For Timer, Counter and Control
data types, specify the actual tag name.field name. The various fields supported
for Timer, Counter and Control data types are listed in Fields Supported In Timer,
Counter and Control Data Types, page 35. For example, TIMER1. CTL.
• Group: Select the Group Name for which this Point belongs to.
• DataType: Leave this field blank.
B0700WM, Rev A 31
ControlLogix Configuration for Heartbeat Message Support

The driver sends out a heartbeat message to read the device time from ControlLogix
software to confirm the link status when a device fails or if no points are configured.
Also, in redundant configuration, the shadow module sends out a heartbeat message
to read the device time from ControlLogix software to confirm the link status.
For this, configure the tag “DEV_TIME” in ControlLogix software as shown.
NOTE: The driver does not require a DCI block to be configured with this tag
name.
Tag name Data Type Ladder Logic Purpose

Needed
DEV_TIME DINT[7] A “GSV” The driver reads
instruction with this tag to check
Class Name: the status of the
WALLCLOCK- link to ControlLogix
TIME Attribute device.
Name: DateTime
Dest: dev_time[0]
ControlLogix Configuration for Time Synchronization (+TS)

Support
If the device option “+TS” is configured in the DVOPTS parameter of the device
ECB201 block, the driver synchronizes ControlLogix time with Foxboro DCS Series
time using the tags as described in the table.
NOTE: The driver does not require any DCI blocks to be configured for any of
these tags.
32 B0700WM, Rev A
Tag Name Data Type Ladder Logic Purpose

Instructions Needed
DEV_TIME DINT[7] A “GSV” instruction The driver reads the
with Class Name: DEV_TIME tag to get
WALLCLOCKTIME the current
Attribute Name: ControlLogix time.
DateTime Dest: dev_
time[0]
TSYNC_TAG DINT[7] As shown in this The driver writes the
image, on its own time values to
rung, create one TSYNC_TAG.
“SSV” instruction with
Class Name:
WALLCLOCKTIME
Attribute Name:
DateTime Dest:
TSYNC_TAG
TSYNC_FLG BOOL As shown in below The TSYNC_FLG XIC
figure, on the same instruction is always
rung as the SSV “false” until the driver
instruction (but writes “true”. After the
positioned before it), driver sets the time
create a single “XIC” values in TSYNC_
using the tag name TAG, it writes “true” to
TSYNC_FLG. TSYNC_FLG.
Below this rung, This causes the XIC
create another rung instruction to allow the
with a single “OU” SSV to execute which
instruction using the sets the time. The
TSYNC_FLG tag TSYNC_FLG must be
name. cleared to prevent the
SSV from
continuously
executing. The Output
Unlatch (OU) on the
next rung clears the
TSYNC_FLG.
A snapshot of the rungs that need to be created at the ControlLogix device for the time
synchronization is shown.
B0700WM, Rev A 33
Figure 4 - Rungs Required for Time Synchronization
Configuring DCI Blocks to Map I/O Points to DCS

The driver supports these predefined data types in ControlLogix device:
• BOOL
• BOOLEAN ARRAY
• SINT (8 bit integer)
• INT (16 bit integer)
• DINT (32 bit integer)
• REAL (32 bit float)
• TIMER (32 bit integer – units of milliseconds)
• COUNTER (32 bit integer)
• CONTROL (32 bit integer)
• Array (single dimensional)
NOTE: ControlLogix data type “User defined data type” (UDT) is not supported by
the driver. A workaround is to use the aliasing feature in ControlLogix software to
map each element in a UDT type data to a new tag which can be accessed as a
simple data type by the driver.
Data type mnemonics used for specifying the type in PNT_NO parameter of the DCI
block are listed in the table below.
Data Type Mnemonic

8 bit signed integer S1
16 bit unsigned integer U2
32 bit unsigned integer U4
34 B0700WM, Rev A
The various configuration options available in the DCI blocks to support the above
data types are listed in below table. An entry of ‘*’ indicates support and ‘#’ indicates
support of Word Mirroring. See Word Mirroring Option with PAKIN blocks, page 42 for
more information on Word Mirroring.
Table 3 - DCI Block Types vs. AB-ControlLogix Data Types
Data Types in Control Block

ControlLogix
BIN BOUT IIN IOUT RIN ROUT PAKIN PAKOUT
Bool * *
Boolean Array *# *
SINT (signed 8 *X:S1 *X:S1
bit)
INT (signed 16 *X:S2 *X:S2 * *
bit)
X:U2 X:U2 X:U2 X:U2
DINT (signed 32 * * * *
bit)
# X:S4
X:S4 X:U4
X:U4
REAL (32 bit) * *
Timer (32 bit) *X.Y *X.Y *X.Y
Counter (32 bit) *X.Y *X.Y *X.Y
Control (32 bit) *X.Y *X.Y *X.Y
Array (one * * * * * *
dimensional)
X: is the tag name and Y: is the field as defined in this table.
Table 4 - Fields Supported In Timer, Counter and Control Data Types
Data Fields
With PAKIN and IIN
Blocks With BIN Block
Timer CTL PRE ACC EN TT DN FS LS OV ER
Counter CTL PRE ACC CU CD DN OV UN
Control CTL LEN POS EN EU DN EM ER UL IN FD
DCI Blocks and Default Data Types

This table lists the default data type assigned for a block when data type specification
is omitted from the PNT_NO parameter.
B0700WM, Rev A 35
Table 5 - DCI Block vs. Default Data Types
DCI Block Default Data Type

IIN, IOUT S4 (32 bit signed integer)
PAKIN, PAKOUT Boolean Array
Support of Arrays
Access of single dimensional array data in ControlLogix software is supported by the
driver.
The supported data types of the elements within the array are:
• SINT (8 bit integer)
• INT (16 bit integer)
• DINT (32 bit integer)
• REAL (32 bit float)
• Boolean Array (32 bit binary)
• Timer Array
• Counter Array
• Control Array
To access the array data type in ControlLogix software, each element of the array
needs to be mapped to a single DCI block. The format of PNT_NO parameter to
access an array element is:
array tag name[index].field - For Timer, Counter and Control
arrays
where field is Field as defined in Fields Supported In Timer, Counter and Control Data
Types, page 35index is zero based.
For example, to access the fields EN and PRE of the array Timer1[10], use this format
for PNT_NO of BIN, PKINGP of PAKIN blocks.
Timer1[0].EN
Timer1[1].EN
.
.
.
Timer1[9].EN for PNT_NO of BIN blocks
Timer1[0].PRE
Timer1[1].PRE
.
.
Timer1[9].PRE for PKINGP of PAKIN blocks
array tag name[index]:data Type
where data Type is optional. If data type is omitted the default data type of the block is
used. If only the array name is entered, the first element of the array is accessed. The
index is zero based.
For example, to access the elements of the array SintArray[50] where the data type of
the elements is signed 8 bit integer, use this format for PNT_NO of IIN or IOUT blocks.
SintArray[0]:S1
SintArray[1]:S1
.
.
SintArray[49]:S1
NOTE: Boolean Arrays are organized differently from other arrays in ControlLogix
software.
36 B0700WM, Rev A
Boolean Array Tags in the ControlLogix device can only be created with array lengths
in multiples of 32. The entries in these arrays cannot be accessed by BIN/BOUT
blocks. They are instead accessed as groups of 32 bits using PAKIN or PKOUT
blocks. For example if you configure a tag BoolArray1 with size 64, to access bits
BoolArray1[0] to BoolArray1[31] using PAKIN, the PKINGP parameter of the block
should be set to BoolArray1[0]; to access bits BoolArray1[32] to BoolArray1[63]
using PAKIN, the PKINGP parameter of the block should be set to BoolArray1[1].
Similarly, PAKOUT can be used to access the Boolean Arrays using the PKCOGP
parameter.
Support of User-defined Structured Arrays

Access to single dimensional user-defined structured arrays are supported by the
driver. To access the user-defined structured array in ControlLogix software, each
element of the structured array needs to be mapped to an individual DCI block. The
format of PNT_NO parameter to access a user-defined structured array member is:
tag name[index].field
where tagname is user-defined structured array type tag, which is zero based index
and field is a member in the structure as defined in this image.
Figure 5 - User-Defined Structured Tags
For example, to access the Blower_Number field in the Blower structure, use this
format for PNT_NO in DCI blocks:
SEQ_EDIT_HMI[0].Blower_Number for PNT_NO of IIN/IOUT block
These formats of PNT_NO parameter to access user defined structured array are not
supported by the driver:
• SEQ_EDIT_HMI[0].Blower_Number.0
• SEQ_EDIT_HMI[0].Blower_Name.Len
• SEQ_EDIT_HMI[0].Blower_Name.Len.0
• SEQ_EDIT_HMI[0].Blower_Name.Data
• SEQ_EDIT_HMI[0].Blower_Name.Data[0]
• SEQ_EDIT_HMI[0].Blower_Name.Data[0].0
• SEQ.HMI[0].Blower_Number
IIN/IINR
Integer input or redundant integer input blocks hold integer values received from the
ControlLogix device.
Parameter Name Value Description

NAME * The name of the point.
TYPE IIN(R) Defines the block as a single (IIN)
Integer input block or redundant (IINR)
Integer input block.
B0700WM, Rev A 37

IOM_ID * The name of the associated ECB201.
PNT_NO (IIN) * Format: Tagname or Tagname:Data
type or Tagname.Field name (for
II1_PT (IINR) Timer, Counter and Control data
types)
II2_PT (IINR)
Tag name: As specified in the Device
II3_PT (IINR)
(If data type is specified, the tag name
can be no longer than 29 characters).
Data type: S1, U2, S2, S4.
32 bit signed integer is assumed if no
data type is specified.
If Groups and I/O Point Aliases is
used, then specify the PNT_NO field
with Alias name as specified in “Name”
field of I/O Point Aliases.
These are the examples:
• DINTTAG1
• INTTAG2:S2
• SINTTAG3:S1
• Timer1.CTL
• Counter1.PRE
• Control1.POS
IOUT
Integer output blocks hold integer values sent to the ControlLogix device.

TYPE IOUT Defines the block as an Integer
output block.
38 B0700WM, Rev A

IOM_ID * The name of the associated
ECB201.
PNT_NO * Tag name (Point name) as
specified in the device. 32-bit
signed integer is assumed if no
data type is specified after the
tag name.
Other allowed formats are:
• Tagname or Tagname:Data
type
Where:
• dataType can be S1, U2,
S2, S4.
• S4 is the default data type.
• If data type is specified, the
tag name can be no longer
than 29 characters.
• If Groups and I/O Point
Aliases is used then specify
the PNT_NO field with Alias
name as specified in “Name”
field of I/O Point Aliases..
◦ DINTTAG2
◦ INTTAG3:S2
◦ SINTTAG4:S1
RIN/RINR
Real input/Redundant Real Input blocks hold real values received from the
ControlLogix device.

TYPE RIN(R) Defines the block as a single (RIN)
or redundant (RINR) Real input
block.
B0700WM, Rev A 39

ECB201.
PNT_NO (RIN) * Tag name as specified in the
Device.
RI1_PT (RINR)
Default 32 bit float assumed.
RI2_PT (RINR)
RI3_PT (RINR) used then specify the PNT_NO
field with Alias name as specified
in “Name” field of I/O Point
Aliases.
• REALTAG1
• REALTAG2
ROUT
Real output blocks hold real values sent to the ControlLogix device.

TYPE ROUT Defines the block as a Real output
block.
ECB201.
PNT_NO * Tag name as specified in the
Device.
Default 32 bit float assumed.
used, then specify the PNT_NO
field with Alias name as specified in
“Name” field of I/O Point Aliases.
• REALTAG3
• REALTAG4
BIN/BINR
Boolean input or redundant Boolean Input blocks hold Boolean values received from
the ControlLogix device. A BIN or BINR block can be mapped to a ControlLogix tag(s)
with data type Boolean or Binary Fields of Timer, Counter, and Control tags. If no data
type is specified in the PNT_NO parameter, the tag is expected to be of type “Boolean
Tag”.
40 B0700WM, Rev A

TYPE BIN(R) Defines the block as a single
(BIN) or redundant (BINR)
Boolean input block.
ECB201.
PNT_NO (BIN) * Format: Tagname or Tagname.
Field name (For Timer, Counter
BI1_PT (BINR) and Control data types)
BI2_PT (BINR) Tag name as specified in the
Device.
BI3_PT (BINR)
If Groups and I/O Point Aliases
is used then specify the PNT_
NO field with Alias name as
specified in “Name” field of I/O
Point Aliases.
• BOOLTAG1
• Timer1.EN
• Counter1.CU
• Control1.FD
BOUT
Boolean output blocks hold Boolean values sent to the ControlLogix device.

TYPE BOUT Defines the block as a Boolean
output block.
ECB201.
PNT_NO * Point name as specified in the
device.
used then specify the PNT_NO field
with Alias name as specified in
This is an example:
BOOLTAG2
PAKIN/PAKINR
Packed input or redundant packed input blocks hold packed binary values received
from the ControlLogix device. A PAKIN or PAKINR block can be mapped to a
ControlLogix tag(s) with data type Boolean Array or DINT. If no data type is specified
in the PNT_NO parameter, the tag is expected to be of type “Boolean Array”.
B0700WM, Rev A 41

TYPE PAKIN(R) Defines the block as a single
(PAKIN) or redundant (PAKINR)
pack input block.
ECB201.
PKINGP (PAKIN) * Tag name as specified in the
Device.
PKI1_PT (PAKINR)
32-bit packed binary is assumed if
PKI2_PT (PAKINR) no data type is specified after the
tag name.
PKI3_PT (PAKINR)
Other allowed formats are:
Tagname or Tagname:Data type or
Tagname.Field name (for Timer,
Counter and Control data types)
Where data type can be U2, U4, S4.
U4 is the default data type. Use S4 if
the data type of point in device is
DINT.
If data type is specified, the tag
name can be no longer than 29
characters.
used then specify the PKINGP field
with Alias name as specified in
• BoolArray1[0]
• DINTTAG3:U4
• DINTTAG4:S4
• INTTAG4:U2
• Timer3.CTL
• Counter3.PRE
• Control3.POS
Word Mirroring Option with PAKIN blocks

The word mirroring is supported with the PAKIN blocks mapped to Dint (signed 32 bit)
or Boolean Array Tags. The option “: WM” after the tag-name at PKINGP parameter of
the PAKIN block mirrors the upper word (bits 1 to 16) and the lower word (bits 17 to
32) as shown in this image.
42 B0700WM, Rev A
Figure 6 - PAKCIN to ControlLogix Data Correspondence with “WM” Option
One of the uses of this option is for the migration of the legacy systems using MCIN
with IOMOPT=1. For more information, see Allen-Bradley Integrator 30 to FDSI
Migration (DI700BS).
These are some examples of PKIN_GP parameters with “: WM” option.
DintTag1:S4: WM for use with a DINT data type in ControlLogix software
DintTag2:U4: WM for use with a unsigned 32-bit data type in ControlLogix software
BoolArray: WM for use with Boolean Array data type
PAKOUT
Packed output block holds packed binary values to be written to the ControlLogix
device. A PAKOUT block can be mapped to a ControlLogix tag with data type Boolean
Array or DINT. If no data type is specified in the PNT_NO parameter, the tag is
expected to be of type “Boolean Array”.
B0700WM, Rev A 43

TYPE PAKOUT Defines the block as a
pack output block.
IOM_ID * The name of the
associated ECB201.
PKCOGP * Tag name (Point name)
as specified in the device.
32-bit boolean array is
assumed if no data type is
specified after the tag
name.
Other allowed formats
are:
• Tagname or
Tagname:Data type
Where
• dataType can be U2,
U4, S4.
Use S4 or U4 if the
data type of point in
device is DINT; and
U2 if the data type is
INT.
• If data type is
specified, the tag
name can be no
longer than 29
characters.
• If Groups and I/O
Point Aliases is used
then specify the
PKCOGP field with
Alias name as
specified in “Name”
field of I/O Point
Aliases.
These are the
examples:
◦ BoolArray1[1]
◦ DINTTAG5:U4
◦ DINTTAG6:S4
◦ INTTAG5:U2
PAKOUT Block Limitations

When using a PAKOUT block, the controller requires exclusive control of the
ControlLogix PLC bits associated with the PAKOUT registers. If a value is set by any
source other than the DCS, Control Software will overwrite the value the next time a
write occurs.
44 B0700WM, Rev A
NOTICE
UNEXPECTED RESULTS
Use the Control Software to modify bits and registers in a PLC associated with a
PAKOUT block.
Failure to follow this instruction can lead to unexpected results.
Device Diagnostic Blocks

Here are the device diagnostic blocks you can configure for the FDC280 EtherNet/IP
Driver.
Good Messages Sent

The number of good messages sent to a specific device may be monitored. Block
definition is:
Name * Block name of the point

Block Type IIN Defines the block as an integer input block
IOM_ID * Provides a complete path to the parent ECB201
device block
PNT_NO * FDC280 Simplex: $L_MSGS_SENT
Prefix ‘$L’ corresponds to counter value on the
FDC280 installed in the left baseplate slot.
FDC280 Fault-Tolerant:
$L_MSGS_SENT
$R_MSGS_SENT
Prefix ‘$R’ corresponds to counter value on the
FDC280 installed in the right baseplate slot.
Good Messages Received

The number of good messages received from a specific device may be monitored.
Block definition is:
B0700WM, Rev A 45

device block
PNT_NO * FDC280 Simplex: $L_MSGS_RCVD
FDC280 Redundant:
$L_MSGS_RCVD
$R_MSGS_RCVD
Worst Case Response Time

The worst-case response timeout (the highest time taken by the device to respond for
a command) on a specific device may be monitored. The block is configured as shown
below. The block displays the value in milliseconds format.

IOM_ID * Provides a complete path to the parent ECB201 device
block
PNT_NO * FDC280 Simplex: $L_WORST_RESP_TIME
Prefix ‘$L’ corresponds to counter value on the FDC280
installed in the left baseplate slot.
FDC280 Redundant:
$L_WORST_RESP_TIME
Prefix ‘$L’ corresponds to counter value on the FDC280
installed in the left baseplate slot.
$R_WORST_RESP_TIME
Prefix ‘$R’ corresponds to counter value on the FDC280
installed in the right baseplate slot.
Response Timeout Counters

The number of response timeouts on a specific device may be monitored using
Response Timeout Counter. The block is configured as shown.
46 B0700WM, Rev A

device block
PNT_NO * FDC280 Simplex: $L_ RESP_TIMEOUTS
FDC280 Redundant:
$L_ RESP_TIMEOUTS
$R_ RESP_TIMEOUTS
Reset Device Counters

It resets the device counters to Zero of a specific device. Block definition is:

Block Type BOUT Defines the block as a Boolean input block
device block
PNT_NO * FDC280 Simplex: $L_RESET_CNTRS
Prefix ‘$L’ represents block for FDC280 installed in
the left baseplate slot.
FDC280 Redundant:
$L_RESET_CNTRS
Prefix ‘$L’ represents block for FDC280 installed in
the left baseplate slot.
$R_RESET_CNTRS
Prefix ‘$R’ represents block for FDC280 installed in
the right baseplate slot.
Turning on the Driver and Enabling Communication with the

device
After configuring the database, interface with the ControlLogix:
1. Set the Driver ECB200 to Online.
2. Set the Device ECB201 communication to Enabled.
3. Change the compounds to the Online state.
B0700WM, Rev A 47
4. Verify that all points are in a Good state.

On deployment, input and output points are in OOS (Out of Service) state. As
soon as the Driver receives a data value for an input and output point from the
device, the points status is set to Good state. The status of an input and output
point remains in the Good state until the Driver detects a connection loss with the
Device.
48 B0700WM, Rev A
Chapter 4: Principles of Operation FDC280 EtherNet/IP Client Driver User’s Guide
Chapter 4: Principles of Operation

The driver runs as an EtherNet/IP client and establishes a connection with the server
in the device to read and write the tags configured. After successful connection, the
Primary module reads the tag values by sending the read command. On receipt of
response from the device, the driver processes and updates the DCI blocks in the
control processor (Core1 of the FDC). The Shadow module sends the heartbeat
message to the device to verify successful communication to the device.
In the fault-tolerant configurations as shown in FDC280 EtherNet/IP Driver Fault-
Tolerant Interfaced to Redundant ControlLogix and FDC280 EtherNet/IP Driver Fault-
Tolerant Interfaced to Simplex ControlLogix, each FDC280 module communicates
independently with the device via its communication connection. When the Primary
FDC280 module fails because it loses communication with the device, it checks the
status of the shadow FDC280 module. If the shadow FDC280 module is good and
having communication with the device, the primary FDC280 module requests a role
switch, causing the shadow FDC280 module to become the new primary module, and
the primary module to become the new shadow module.
For a description of the operation of Simplex and Fault-Tolerant FDC280s interfacing
to ControlLogix using simplex and redundant connections, see Field Device Controller
280 (FDC280) User's Guide (B0700GQ). (In this instance, redundancy is one method
of implementing fault-tolerance.)
EtherNet/IP Driver Operation

FDC280 EtherNet/IP Driver operations include the parsing of received response
messages from ControlLogix to update DCI input and output blocks based on PNT_
NO addresses and creation of output messages to send to the ControlLogix.
The FDC280 EtherNet/IP Driver supports Synchronous mode of communication with
ControlLogix. In Synchronous mode, the EtherNet/IP driver sends a read request
command to the device for the configured tags. On receiving the response message,
the driver will send another read request command to the device. The driver sends the
set of read commands required to read the values for all the I/O points configured
during every scan period. For example, if a given configuration requires 10 read
messages to read the values of all the I/O points configured with a scan rate of
500ms, then 10 read messages are issued every 500ms.This is done assuming that
the device response time is fast enough for all the messages to be sent out and
responses obtained within 500ms. The number of messages required depends on the
number of I/O points configured and the length of associated tags.
Fault Tolerant FDC280 to Redundant ControlLogix Interface

with no Single Point Failure
As shown inFDC280 EtherNet/IP Driver Fault-Tolerant Interfaced to Redundant
ControlLogix, page 11, the FDC280 Fault Tolerant configuration has 2 modules with
Primary and Shadow roles, that run the EtherNet/IP Client driver interface to the
ControlLogix redundant system. The ControlLogix redundant system has controller
modules with Primary and SYNC system roles to run the EtherNet/IP Server. The
interfacing is done through two switches, so that with any single point of failure
detected anywhere in the system, the system can continue to function.
The FDC280s in the system accesses the Primary controller of the ControlLogix
system only using a single IP address for the destination. On the ControlLogix system,
the IP address of the System is owned by the module that assumes the Primary role.
On power-on, one of the 2 modules assumes the role of Primary and the other
B0700WM, Rev A 49
FDC280 EtherNet/IP Client Driver User’s Guide Chapter 4: Principles of Operation
assumes the role of Secondary. State and variable information is synchronized

between the two modules using SRM hardware modules in the ControlLogix chassis
and a communication link between the two modules.
In FDC280, on power-on one of the two modules assumes the role of Primary and the
other assumes the role of Shadow. The Primary FDC sends periodic read message
request messages and on demand write messages to the ControlLogix Primary, while
the shadow sends heartbeat messages to the same ControlLogix module. State and
variable data is synchronized using internal communication links between the two
modules.
If communication between the Primary FDC and ControlLogix system fails because of
hardware fault in the Primary FDC or link failure, and the Shadow FDC can
communicate to ControlLogix failover occurs on the FDC side with the FDC modules
switching their roles with bumpless failover with minimal loss of data accessed from
ControlLogix Primary.
On the other hand if a hardware failure is detected on the Primary ControlLogix or loss
of communication link to the Primary ControlLogix, the Secondary ControlLogix
becomes the Primary. At that time the new Control Logix Primary modules gets the
ownership of the IP address of the ControlLogix system and does an ARP broadcast
so that the FDCs can recognize the change in Primary ownership on the ControlLogix
side and start communicating with the new ControlLogix Primary.
Two switches are used in the system so that it continues to function even with failure
detected in one of the switches.
Device ECB201 Operation and Status on the System

Manager
The initial state of an ECB201 is “disabled”. The ECB must be “enabled” before
communications can take place with a connected ControlLogix. To enable the device,
click the ENABLE COMMUNICATIONS field on the ECB201 Equipment Change
action display.
After DCI blocks are entered on enabling device communication from System
Manager, the ECB201 status is set to Good and the driver starts sending read
command to the ControlLogix controller
With an FDC280 Simplex, the driver sends out a read/write command to the
ControlLogix device and waits until the timeout set in device options expires. If no
reply is received within the “timeout” time, two retries are attempted. If no reply is
received, the device is marked to failed and the all the points associated with the
device are marked OOS (out of service). When a device is in the failed condition, the
driver sends heartbeat messages to the device every second.
With an FDC280 FT/Redundant configuration the driver running in Primary module
sends out a read/write command to the ControlLogix device and waits until the
timeout set in device options expires. If no reply is received within the “timeout” time,
two retries are attempted. If no reply is received and if Shadow module can
communicate with the ControlLogix device, device status is set to Warning state on
system manager and failover occurs with the Shadow module becoming the Primary.
If the Primary module is able to communicate with the ControlLogix controller but not
the Shadow module, device status is set to warning state. When both the Primary
and Shadow modules are unable to communicate with the Control Logix device,
device status is set to failed on System manager.
When a device is in the failed or warning condition on the System Manager, the driver
sends heartbeat messages to the device every second from the module or modules
unable to get responses for read commands from the ControlLogix controller.
50 B0700WM, Rev A
Chapter 4: Principles of Operation FDC280 EtherNet/IP Client Driver User’s Guide
Troubleshooting
To troubleshoot the device failure /invalid condition, review the SMON log messages
from the FDC280. For smon_log messages that are applicable to all drivers, see Field
Device Controller 280 (FDC280) User's Guide (B0700GQ).For SMON log messages
specific to the EtherNet/IP driver, see Symptoms and Corrective Actions, page 51. In
addition, you should see the device documentation provided by the manufacturer to
troubleshoot the devices.
Table 6 - Symptoms and Corrective Actions
Symptom Corrective Action

Device is not responding coming ONLINE Check the cable connection between device and switch,
FDC280 and switch, and IP address configuration of the
device in ECB201.
‘Invalid Device name configured in DVNAME parameter’ The log message is displayed when the IP Address in
displayed at smon_log the DVNAME parameter of ECB201 is incorrectly
formatted. Check if the IP Address is in correct format.
‘Invalid options configured in DVOPTS parameter’ The log message is displayed when anything other than
displayed at smon_log the supported device options is configured in the
DVOPTS of ECB201. Check if the DVOPTS of ECB201
has only supported options.
Invalid DVOPTS parameter configured for device Scan The log message is displayed when user configures
Rate Invalid Scan Rate.
For example: DVOPTS = +@X or +@ or +@ABC
Check the supported values for the Scan Rate.
”Timeout configured in DVOPTS is not a valid number" The log message is displayed when user configures
Invalid Time out value.
For example: DVOPTS = +TO=A or +TO= or +TO=ABC
Check the supported values for the Time out.
“Slot Number configured in DVOPTS is not a valid The log message is displayed when user configures
number” Invalid Slot Number.
For example: DVOPTS = +SN=A or +SN=17 or +SN=
Check the supported values for the Slot Number.
“Name is not specified/Invalid for Device” The log message is displayed when user does not
configure the Groups and I/O Point Aliases for the
device.
"Invalid options configured in Custom Parameter 1" The log message is displayed when user configures
anything in the Custom Parameter 1 in Groups and I/O
Point Aliases. Custom parameter 1 should not be used
for any configuration.
B0700WM, Rev A 51
FDC280 EtherNet/IP Client Driver User’s Guide Chapter 4: Principles of Operation
Table 6 - Symptoms and Corrective Actions (Continued)
Symptom Corrective Action

“Invalid Group Scanrate Configured” The log message is displayed when user configures
invalid number in Scan rate in Groups and I/O Point
Aliases.
"Address is not specified/Invalid for Point" The log message is displayed when the Address of the
Point is invalid string or not specified in Groups and I/O
Point Aliases.
"Server Data type is not empty" The log message is displayed when the Server datatype
is not empty for the point in Groups and I/O Point
Aliases.
"Name is not specified/Invalid for Point" The log message is displayed when the Name for the
Point is invalid string or empty in Groups and I/O Point
Aliases.
"Point specified is duplicate for Device" The log message is displayed when the Point specified
is duplicate in Groups and I/O Point Aliases.
"Exceeded Maximum number of points allowed 8000" The log message is displayed when the Points
configured are more than 8000 in Groups and I/O Point
Aliases.
52 B0700WM, Rev A
Appendix A: FDC280 Diagnostic Driver Support FDC280 EtherNet/IP Client Driver User’s Guide
Appendix A: FDC280 Diagnostic Driver Support

The FDC280 EtherNet/IP Driver includes support for the FDC280 Diagnostic Driver,
which can be used to help diagnose communication between the EtherNet/IP Driver
and ControlLogix. The Diagnostic Driver sends communication echo messages to the
FDC280 IO diagnostic tool, which is a Windows-based user interface that logs the
echo messages and also shows this cumulative diagnostic information.
• Messages Sent
• Messages Received
• Response Timeouts
• Worst-case Response time
Verify that the C:\Program Files (x86)\Schneider Electric\FDC280 IO
Diagnostic Tool\DrvrDiag.xml file with the driver specific content is as in this
excerpt. If this content is not present in the file, then update the file with this content
and save the file before opening the tool.
<Driver decoderID="2">
<id>8</id>
<gms>Good Messages Sent</gms>
<gmr>Good Messages Received</gmr>
<rst>Response Timeouts</rst>
<ms1>Worst Response Time</ms1>
<lex>Last Error Message</lex>
</Driver>
To enable the diagnostic feature, create an ECB200 block and set it to online using
System Manager.
For information, see Field Device Controller 280 (FDC280) User's Guide (B0700GQ).
The FDC280 I/O diagnostic tool running EtherNet/IP Driver appears as shown.
NOTE: The Last Error Message in Diagnostic Info on the Diagnostic Tool does
not apply to the EtherNet/IP driver.
B0700WM, Rev A 53
FDC280 EtherNet/IP Client Driver User’s Guide Appendix A: FDC280 Diagnostic Driver Support
Displaying the Packets in EtherNet/IP Format

The tool displays the packets in Raw Hex format. This is the process to see the
packets in the EtherNet/IP protocol format.
1. On the File menu, click Export to PCAP. It exports the Raw Hex format packets
to PCAP.
2. Open the exported PCAP file in Wireshark. It appears in Wireshark as shown in
this image.
3. Initially the Wireshark displays the protocol as TSAA. Click Analyze, and then
click Decode As to modify this protocol type to ENIP as shown in this image.
54 B0700WM, Rev A
Appendix A: FDC280 Diagnostic Driver Support FDC280 EtherNet/IP Client Driver User’s Guide
4. In Decode As window, select the current protocol as ENIP as shown here.
5. Click OK.
6. After modifying the protocol type, the Wireshark displays the packets as shown in
this image.
B0700WM, Rev A 55
FDC280 EtherNet/IP Client Driver User’s Guide ControlLogix

ControlLogix
This appendix describes the various read/write message formats required by
ControlLogix devices.
These are the application layer message formats.
Multi Request Service for Reading or Writing Multiple Points

The EtherNet/IP driver uses these Logix5000 CIP service commands listed in Allen-
Bradley Logix5000 Data Access - Reference Manual (Publication 1756-RM005A-EN-
E) to interface with ControlLogix devices.
ControlLogix Read Message Format

The message contents are structured as shown:
The tag information sections are structured as shown:
The “Tag Offset” and “Num Elements” parameters are relevant only when specifying
items located within an array.
ControlLogix Write Message Format

The message contents are structured as shown:
The tag information sections are structured as shown:
The “Tag Offset” and “Num Elements” parameters are relevant only when specifying
items located within an array.
Data Type:
• 0xC1 – Boolean
• 0xC2 – 8-bit signed integer
56 B0700WM, Rev A
ControlLogix FDC280 EtherNet/IP Client Driver User’s Guide
• 0xCA – Float
• 0xD3 – 32-bit collection
ControlLogix Read/Write Result Message Format

The format of the result message data is as shown:
Cmd Status: Overall status for entire command. If non-zero, then a failure occurred on
one or more of the tags read or written.
Tag Location: OFFSET FROM CURRENT POSITION where data is located. These
offset locations are in a FIXED position.
Tag Data is structured as shown:
Service Code:
0xCC – read Logix tag reply.
0xCD – write Logix tag reply.
General Status:
0x04 – The tag does not exist.
0x05 – The tag could not be found.
0x06 – The amount of data requested would not fit into the response buffer. Partial
data transfer has occurred.
0x0A – An error has occurred trying to process one of the attributes.
0x13 – Not enough command data / parameters were supplied in the command to
execute the service requested.
0x1C – An insufficient number of attributes were provided compared to the attribute
count.
0x00 – Success!!
Extended Status:
0x05, 0x21 – You have tried to access beyond the end of the data object.
0x07, 0x21 – The abbreviated type does not match the data type of the data object.
0x04, 0x21 – The beginning offset was beyond the end of the template.
Data Type:
0xC1 – Boolean
0xC2 – 8-bit signed integer
0xCA – Float
B0700WM, Rev A 57
FDC280 EtherNet/IP Client Driver User’s Guide ControlLogix
0xD3 – 32-bit collection
58 B0700WM, Rev A
Appendix C: ControlLogix Configuration FDC280 EtherNet/IP Client Driver User’s Guide
Appendix C: ControlLogix Configuration

This appendix provides information regarding the configuration of the ControlLogix IP
address and the ControlLogix point tag name and database.
ControlLogix IP Address Configuration

Configuring IP Address for the ENBT module
The ENBT module comes from the factory in the “BOOTP” mode. To configure the IP
address for the ENBT module you have to use the “BOOTP-DHCP Server” program
which installs along with the RSLogix 5000 software.
1. To start the “BOOTP-DHCP Server”, on Windows Start menu, select All
Programs > Rockwell Software > BOOTP-DHCP Server > BOOTP-DHCP
Server.
2. In the Network Settings dialog box, enter the Subnet Mask and Gateway
details of your system where the BOOTP application is running.
The Network Settings dialog box appears automatically if the settings were not
already entered. You can also open the dialog box by selecting the Tools >
Network Settings.
NOTE: The ControlLogix device and the BOOTP station should be in the
same network.
Setting the IP Address

The application captures the MAC address of the ControlLogix device and displays it
in the application window.
1. Double-click on the entry corresponding to the MAC address of the ControlLogix
device. The New Entry dialog box appears.
B0700WM, Rev A 59
FDC280 EtherNet/IP Client Driver User’s Guide Appendix C: ControlLogix Configuration
2. Set the IP address in the IP Address field and click OK.
Enabling/Disabling BOOTP and DHCP

1. To get the IP address from the DHCP server, you can select the Enable the
DHCP option.
2. If you do not want the BOOTP or DHCP and just want to assign an IP address for
the local network, click the Disable BOOTP/DHCP option and then assign the
required IP address.
NOTE: Any change you make takes effect only after rebooting the ENBT
module (powering off and then powering back on).
60 B0700WM, Rev A
Configuring Two ENBT Modules in the Same Chassis

When you have two ENBT modules in the same chassis, you have to complete the
setup twice to configure the IP addresses.
Configuring IP Address for the EN2T Module

The EN2T module is shipped from the factory in the “BOOTP/DHCP” mode with its
rotary switches (switches are physical parts on the module) set to 888. This image
shows the rotary switches on EN2T module. The switches are located on top of the
module.
Figure 7 - EN2T Module - Top View
The EN2T module IP address can be set using rotary switches. This module comes
from the factory with its IP address set to 192.168.1.xxx (where xxx represents the
switch settings).
1. Set the valid number (001 to 254) for the last portion of the IP address using the
rotary switches.
2. At power up, the module reads the rotary switches to determine if they are set to
a valid number for the last portion of the IP address.
3. If the settings are a valid number (for example, the switches are set to positions 1,
4, 8), these conditions result:
• IP address = 192.168.1.148 (where 148 is from switch settings)
• Subnet mask = 255.255.255.0
• Gateway address = 0.0.0.0
• The module does not have a host name assigned, nor does it use any
Domain Name System.
NOTE: We recommend to set rotary switches to valid number before
installing the module.
Configuring Two EN2T Modules in the Same Chassis

To configure IP addresses of two EN2T modules in the same chassis, set the rotary
switches of the modules with different valid numbers before powering up the modules.
B0700WM, Rev A 61
ControlLogix Point Tag Name and Database Configuration

To configure the ControlLogix device, you need Allen-Bradley RSLogix 5000 software.
The snapshots and other information given below were taken using The RSLogix
5000 software, v13.03.00. The procedure or the figures shown here may differ if you
have any other version of the RSLogix software.
Configuring Drivers
RSLinx® software from AB is used for this step. The RSLogix 5000 software installs
RSLinx application in the system. Start the RSLinx application and follow these steps:
1. Click Communication > Configure Drivers of the RSLinx Lite application.
The Configure Drivers dialog box appears.

2. Choose Ethernet devices from the Available Driver Types list box and click
Add New.
62 B0700WM, Rev A
3. Accept the default name and click OK.
4. Type the IP address of the ControlLogix device you want to communicate with in
the Host Name field and click OK.
The final configuration should appear as shown:
B0700WM, Rev A 63
64 B0700WM, Rev A
Verifying Communication between RSLogix PC and ControlLogix

1. Open the RSWho window by clicking Communications > RSWho.
2. In the tree view on the left side of the window, you should see the entry of AB_
ETH-1, Ethernet. Expand the tree to check all your channels and controller(s).
Communicating with the Device from RSLogix PC

1. Start the RSLogix 5000 application and open the RSWho dialog box by clicking
the Communications > RSWho menu option.
2. Select the processor card and click Upload. This uploads the existing database
from the ControlLogix device to your local system.
After few seconds the Connected to Upload dialog box appears.
B0700WM, Rev A 65
3. Click Select File and store the device configuration database (.acd file) at the
desired location by clicking Select.
4. If prompted, click Yes to create the project file and upload.
Depending on the size of the existing database, uploading may take some time.
66 B0700WM, Rev A
5. From the tree view on the left side of the window, double-click the Controller
Tags option available under Controller xxx directory. The existing data points
appear in the right side of the view panel.
Creating and Downloading a New Database

1. On the New Controller dialog box, click File > New.
2. Select the appropriate controller type, name your database, and select the
correct chassis type and slot number.
B0700WM, Rev A 67
3. Browse to where you want to save the file and click OK.
4. To configure the module, right-click on the I/O Configuration directory and click
New Module.
5. From the Vendor list box select Allen-Bradley.
68 B0700WM, Rev A
6. From the module list, select the 1756-ENET/A 1756 Ethernet Communication
Interface module and click OK. This opens the Module Properties dialog box.
7. Name the module and enter its IP address. Accept the other default values and
click Finish.
8. To configure the Tag, right-click on the Controller Tags option available under
the Controller xxx directory.
B0700WM, Rev A 69
9. Click New Tag from the popup menu. The New Tag dialog box appears.
10. Enter the required name, choose the available data type by clicking Configure,
leave the Scope and Style with their default values, and click OK.
To enter new tag(s) you must repeat the steps in this task.
11. On the Communication menu, click Who Active.
70 B0700WM, Rev A
12. From the WhoActive dialog box, select the proper controller, click Set Project
Path, and then click Download.
13. Click Download in the Download dialog box to complete the download process.
This also brings the device to the online state as shown here, with RSLogix
application communicating with the ControlLogix software which is in “Program”
mode.
B0700WM, Rev A 71
Online Operations
To configure or change the IP address, operate the module in the “Program” mode.
1. Open the Module Properties dialog box by double-clicking your I/O card ([1]1756-
enet/a Unit245) option available under the I/O Configuration directory.
2. Click the Port Configuration tab.
3. If the Enable BootP option is checked, uncheck it and set the required
configuration.
4. Once you are done, check the Enable BootP option and click OK.
5. Put the module in “Run” mode.
Configuring or Changing the Tag

To configure or change the Tag, keep the module in “program” mode.
1. From the tree view on the left side of the window, right-click on the Controller
Tags option under the Controller xxx directory.
2. Click the New Tag option from the popup menu. The New Tag dialog box opens.
72 B0700WM, Rev A
3. Enter the required name, choose the available data type by clicking Configure,
leave the Scope and Style with their default values, and click OK.
To enter a new tag, you must repeat the steps in this task.
4. Once you are done, put the device in Run mode.
Configuring a Large Number of Points

1. To configure a large database, first configure a small number of points in RSLogix
5000 software and export it as a .csv file.
2. Open the .csv file in Microsoft Excel® and make changes in the spreadsheet
using the Microsoft Excel edit functions.
3. Export the edited .csv file to the RSLogix 5000 file and download to the device.
B0700WM, Rev A 73
FDC280 EtherNet/IP Client Driver User’s Guide Appendix D: ControlLogix Redundancy System
Appendix D: ControlLogix Redundancy System

This appendix describes the ControlLogix redundancy system, which requires no
additional programming.
Ethernet Switchover
NOTICE
SWITCHOVER
Set both the EtherNet/IP modules to the same IP address.
Failure to follow this instruction can lead the switchover to fail.
If there is a failure that causes a redundancy system to switchover, the EtherNet/IP

networks automatically swap IP addresses. You must set both EtherNet/IP modules to
the same IP address.
The details are shown in the image. Note that although the Ethernet ports of both
chassis are configured to the same IP address, when the two are connected as a
redundant system, the chassis that acts as thePrimary system uses the IP address
configured. The other chassis, taking the secondary role, uses the IP address
configured plus one for its Ethernet port. When there is a switchover, the secondary
chassis takes up the primary role and uses the IP address configured. Both the
FBM233 modules communicate with the Primary Chassis Ethernet port.
Figure 8 - FBM233 Modules Communication With Primary Chassis Ethernet Port
74 B0700WM, Rev A
Appendix D: ControlLogix Redundancy System FDC280 EtherNet/IP Client Driver User’s Guide
Configuring Same IP Address to the EN2T Modules

For redundancy at ControlLogix devices, the EN2T modules are used along with
1756-RM redundancy modules to maintain communications between the pair of
redundant chassis. To configure the same IP address to both the EN2T modules:
1. Set the same IP address for both the EN2T modules by using rotary switches -
see EN2T Module - Top View. (On top of the EN2T module, set the last portion of
IP address same for both the cards.)
2. Install the EN2T modules along with RM modules in the redundant ControlLogix
chassis. Connect the interlink cable between the RM modules for redundancy.
Make sure the power supply and LAN cables are disconnected.
3. Power on one ControlLogix device and connect the LAN cable to EN2T module.
4. When the Primary ControlLogix device ready, power on the second ControlLogix
device and wait until the IP address is assigned as configured plus one (+ 1) for
its Ethernet port. Now connect the LAN cable for the second EN2T module.
At the time of switchover, the secondary chassis takes up the primary role and
uses the IP address configured.
B0700WM, Rev A 75
Glossary
C
Control Core Services (CCS): Core software environment, formerly known as “I/A
(Intelligent Automation) Series software”.
Control Station/Control Processor: A Foxboro DCS module or workstation that

affects process control via the Foxboro DCS Control Network. An example is the Field
Device Controller 280 (FDC280). The control processor controls process variables
using algorithms contained in functional control blocks configured by on-site process
engineers to implement the desired control strategies.
D
Distributed Control Interface (DCI): Control blocks used between the control
processor and advanced Fieldbus Module (FBM)s. They are used in conjunction with
the FBM to interface digital field device I/O communications with the Foxboro control
station. These control blocks are part of the DCI block family: AI, AO, BIN, BINR,
BOUT, BOUTR, DI, DO, IIN, IINR, IOUT, IOUTR, MAI, MAO, MDI, MDO, PAKIN,
PAKINR, PIDFF, RIN, RINR, ROUT, ROUTR, PAKOUT, PAKOUTR, STRIN,
STROUT, and UNIVFF.
E
Equipment Control Block (ECB): An equipment control block, created for each FBM
and external field device, provides a “holding place” for the software data associated
with that FBM or external field device
F
Fieldbus Module (FBM): FBMs provide the interface between process sensors/
actuators and the Fieldbus in a standard Foxboro DCS. FBM214/214b/214e/215/216/
216b/218/244/245 are examples of the many types of FBMs offered as part of
Foxboro DCS.
Fieldbus Modules (FBMs): Distributed Control System (DCS) Fieldbus Modules,

control and interface modules to third-party control solutions, such as Fisher's
PROVOX Series 20 or Honeywell TDC 2000 systems.
L
Left FDC280: For an FDC280 pair, the FDC280 installed in the left slot in the two-slot
FDC280 baseplate, when facing a horizontally aligned FDC280 baseplate from the
front
P
Parameter: Named element in the data structure of a device function block,
Equipment Control Block (ECB), or other control block.
R
Requested Packet Interval (RPI): Rate at which the input and output messages
should traverse between the Ethernet/IP device and FDC280 Ethernet/IP Driver.
B0700WM, Rev A 77
Index Requirements Software ............................................12

RIN .........................................................................39
ROUT .....................................................................40
B
BIN .........................................................................40 T
BINR .......................................................................40 Turning on the Driver and Enabling Communication
BOUT......................................................................41 with the device .......................................................47
C
Configuration Details ................................................27
Configuration Guidelines ............................................9
Configuring DCI Blocks.............................................34
Configuring DCI Blocks for Points..............................34
Connection Device Failure Detection .........................50
Control Software Configurator ...................................17
D
Device Diagnostic Blocks..........................................45
E
Equipment Control Block for the Drivers (ECB200) .....28
EtherNet/IP Client Device Connection (ECB201) ........28
F
Fault-tolerant ...........................................................49
G
Good Messages Received ........................................45
Good Messages Sent ...............................................45
H
Hardware Configurations ..........................................10
I
ICC and CCS FDC280 Configurator ..........................14
IIN...........................................................................37
Importing the Driver Definition File.............................22
IOUT .......................................................................38
P
PAKIN .....................................................................41
PAKOUT .................................................................43
Procedure Separate Workstations for Control
Software Configurator and Hosting the FDC280........17
Procedure Workstation with Control Software
Configurator...........................................................19
R
Requirements Hardware...........................................12
B0700WM, Rev A 79
Schneider Electric Systems USA, Inc.
70 Mechanic Street
Foxboro, Massachusetts 02035–2040
United States of America
Global Customer Support: https://pasupport.schneider-electric.com
As standards, specifications, and design change from time to time,

please ask for confirmation of the information given in this publication.
© 2022 Schneider Electric. All rights reserved.

B0700WM, Rev A

b0700wm A

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

b0700wm A

Uploaded by

Copyright:

Available Formats

Foxboro™ DCS

FDC280 EtherNet/IP Client Driver

Support of User-defined Structured Arrays .................................................37

Important Safety Instructions

The addition of this symbol to a “Danger” or “Warning” safety message

EtherNet/IP Protocol Documents

Schneider Electric Products Mentioned in this Document

Global Customer Support

We Welcome Your Comments

Chapter 1: Getting Started

Overview of Redundant ControlLogix

Understanding the Installation and Configuration Process

1 Review the supported hardware Supported Hardware Configurations,

Supported Hardware Configurations

Figure 1 - FDC280 EtherNet/IP Driver Simplex Interfaced to Simplex

Figure 2 - FDC280 EtherNet/IP Driver Fault-Tolerant Interfaced to Redundant

Figure 3 - FDC280 EtherNet/IP Driver Fault-Tolerant Interfaced to Simplex

• Foxboro DCS Control Core Services v9.3 or later

Chapter 2: Installation and Uninstallation

Installing on a Foxboro DCS Using the ICC and CCS FDC280

5. Click Complete to install the required components.

The window displays the components that will be installed.

6. When installation is complete, click Finish.

Installing on a Foxboro DCS Using the Control Software

Procedure for Workstation Hosting FDC280

5. In Choose Setup Type, click Custom.

6. Clear EthernetIP Driver Key, then click Next.

7. In the Installation Summary window, click Install.

8. When installation is complete, click Finish.

Procedure for Workstation with Control Software Configurator

2. In File Explorer, go to the root directory of the CD-ROM or installation media.

5. In Choose Setup Type, click Custom.

6. Unselect EthernetIP Driver Image, then click Next.

7. In the Installation Summary window, click Install.

8. When installation is complete, click Finish.

Importing the Driver Definition File

Procedure When Using a Single Station for the FDC280

Uninstalling FDC280 EtherNet/IP Driver

Uninstalling using CD-ROM with the FDC280 EtherNet/IP

8. The FDC280 EtherNet/IP Driver is uninstalled.

Uninstalling from the Control Panel

Downloading the EtherNet/IP Driver to the FDC280

ECB/DCI Block Description

Configuring the Equipment Control Block for the Drivers

Parameter Value Definition

Configuring the ControlLogix Connection (ECB201)

Table 2 - ECB201 Block Key Parameters/Values

Parameter Value Definition

Table 2 - ECB201 Block Key Parameters/Values (Continued)

Parameter Value Definition

NOTE: If the IP address in the DVNAME parameter in ECB201 is incorrectly

Configuring Groups and I/O Point Aliases for ECB201

I/O Point Aliases Configuration

ControlLogix Configuration for Heartbeat Message Support

Tag name Data Type Ladder Logic Purpose

ControlLogix Configuration for Time Synchronization (+TS)

Tag Name Data Type Ladder Logic Purpose

Figure 4 - Rungs Required for Time Synchronization

Configuring DCI Blocks to Map I/O Points to DCS

Data Type Mnemonic

Table 3 - DCI Block Types vs. AB-ControlLogix Data Types

Data Types in Control Block

X: is the tag name and Y: is the field as defined in this table.