Ethernet/Ip Devicenet Configuration: Power and Productivity For A Better World™

AC 800M
EtherNet/IP DeviceNet
Configuration
System Version 6.0
Power and productivity

for a better world™
AC 800M
EtherNet/IP DeviceNet
Configuration
System Version 6.0

NOTICE
This document contains information about one or more ABB products and may include a description
of or a reference to one or more standards that may be generally relevant to the ABB products. The
presence of any such description of a standard or reference to a standard is not a representation that
all of the ABB products referenced in this document support all of the features of the described or ref-
erenced standard. In order to determine the specific features supported by a particular ABB product,
the reader should consult the product specifications for the particular ABB product.
ABB may have one or more patents or pending patent applications protecting the intellectual property
in the ABB products described in this document.
The information in this document is subject to change without notice and should not be construed as
a commitment by ABB. ABB assumes no responsibility for any errors that may appear in this document.
Products described or referenced in this document are designed to be connected, and to communicate
information and data via a secure network. It is the sole responsibility of the system/product owner to
provide and continuously ensure a secure connection between the product and the system network
and/or any other networks that may be connected.
The system/product owners must establish and maintain appropriate measures, including, but not lim-
ited to, the installation of firewalls, application of authentication measures, encryption of data, installa-
tion of antivirus programs, and so on, to protect the system, its products and networks, against security
breaches, unauthorized access, interference, intrusion, leakage, and/or theft of data or information.
ABB verifies the function of released products and updates. However system/product owners are ulti-
mately responsible to ensure that any system update (including but not limited to code changes, con-
figuration file changes, third-party software updates or patches, hardware change out, and so on) is
compatible with the security measures implemented. The system/product owners must verify that the
system and associated products function as expected in the environment they are deployed.
In no event shall ABB be liable for direct, indirect, special, incidental or consequential damages of any
nature or kind arising from the use of this document, nor shall ABB be liable for incidental or conse-
quential damages arising from use of any software or hardware described in this document.
This document and parts thereof must not be reproduced or copied without written permission from
ABB, and the contents thereof must not be imparted to a third party nor used for any unauthorized pur-
pose.
The software or hardware described in this document is furnished under a license and may be used,
copied, or disclosed only in accordance with the terms of such license. This product meets the require-
ments specified in EMC Directive 2004/108/EC and in Low Voltage Directive 2006/95/EC.
TRADEMARKS
All rights to copyrights, registered trademarks, and trademarks reside with their respective owners.
Copyright © 2003-2016 by ABB.

All rights reserved.
Release: April 2016

Document number: 9ARD000014-600 A
Table of Contents
About This User Manual

Intended User...................................................................................................................11
User Manual Conventions ...............................................................................................12
Warning, Caution, Information, and Tip Icons ....................................................12
Terminology.....................................................................................................................13
Released User Manuals and Release Notes.....................................................................17
Section 1 - Introduction
Overview..........................................................................................................................19
CI873 Communication Interface Module ............................................................19
Linking Device LD 800DN..................................................................................20
Device Import Wizard ..........................................................................................20
EtherNet/IP Embedded Switch Technology Overview ...................................................23
EtherNet/IP Star Topology ...................................................................................23
Linear Network ....................................................................................................24
Section 2 - Functional Description

Overview..........................................................................................................................27
User Interface ..................................................................................................................28
Hardware Tree ......................................................................................................28
CI873 Connections...............................................................................................30
Status Handling ...............................................................................................................33
Status Handling for CI873 ...................................................................................33
Status Handling for LD 800DN ...........................................................................35
Status Handling for DeviceNet Slaves .................................................................37
Status Handling for EtherNet/IP Device ..............................................................39
9ARD000014-600 A 5
Table of Contents
Status Handling for S200 IO Modules................................................................. 41

CI873 Module Redundancy ............................................................................................ 42
Hot Swap ......................................................................................................................... 42
Hot Swap of CI873 .............................................................................................. 43
Hot Swap of LD 800DN ...................................................................................... 44
Hot Swap of DeviceNet Devices.......................................................................... 44
Hot Swap of EtherNet/IP Device ......................................................................... 45
Section 3 - Device Import Wizard

Introduction ..................................................................................................................... 47
EDS File Content ................................................................................................. 47
Converting an EDS File to a Hardware Unit Type.......................................................... 49
Device ............................................................................................................ 57
File ............................................................................................................ 61
I/O Settings .......................................................................................................... 73
Section 4 - Configuration
Introduction ................................................................................................................... 103
Hardware Libraries........................................................................................................ 103
CI873 Hardware units ........................................................................................ 103
S200 Hardware Units......................................................................................... 106
Adding CI873................................................................................................................ 107
Inserting CI873 EtherNet/IP Communication Interface Unit ............................ 107
Configuring CI873 EtherNet/IP Communication Interface Unit....................... 108
Adding LD 800DN Linking Device Unit...................................................................... 109
Inserting LD 800DN Linking Device Unit ........................................................ 109
Configuring LD 800DN Linking Device Unit................................................... 110
Adding DeviceNet Slave Device Unit........................................................................... 121
Inserting DeviceNet Slave Device Unit ............................................................. 121
Configuring a DeviceNet Slave Device Unit ..................................................... 122
Device Identification Parameters ....................................................................... 124
Electronic Key Parameters................................................................................. 124
Communication Related Parameters.................................................................. 125
6 9ARD000014-600 A
Table of Contents
Configuration Recovery Parameter ....................................................................131

Adding EtherNet/IP Device...........................................................................................132
Setting IP Address to an EtherNet/IP Device.....................................................132
Inserting EtherNet/IP Device unit ......................................................................133
Configuring EtherNet/IP Device ........................................................................135
EtherNet/IP Device with Tag Support................................................................141
Configuring Logix 5000 series PLC Unit ..........................................................141
Adding S200 I/O Modules.............................................................................................146
Configuring S200 Adapter .................................................................................148
Inserting S200 I/O Modules ...............................................................................150
Configuring S200 I/O Modules..........................................................................152
Section 5 - Run-Time Operation

Run-Time Behavior .......................................................................................................165
Guidelines for Re-import and Re-configuration............................................................168
Re-import ...........................................................................................................168
Re-configuration.................................................................................................170
Online Upgrade and Coexistence.......................................................................172
Section 6 - Linking Device LD 800DN

Overview........................................................................................................................173
Features..........................................................................................................................173
Configuration.................................................................................................................174
BridgeWay Configuration Tool ..........................................................................174
Updating LD 800DN Firmware .........................................................................176
IP Address and MAC ID Configuration for LD 800DN ....................................179
Scan Cycle .....................................................................................................................182
LD 800DN I/O Tables ...................................................................................................183
Status and Diagnostics Indicators..................................................................................183
LD 800DN Status LED ......................................................................................184
DeviceNet Network Status LED ........................................................................184
DeviceNet Module Status LED..........................................................................185
Ethernet Activity LED .......................................................................................186
9ARD000014-600 A 7
Table of Contents
Ethernet Link LED............................................................................................. 186

Ethernet Module Status LED ............................................................................. 186
Ethernet Network Status LED ........................................................................... 187
Specifications for LD 800DN ............................................................................ 188
Diagnostics through Web Interface ............................................................................... 189
Active Slaves...................................................................................................... 191
Idle Slaves Web Page ......................................................................................... 192
Faulted Slaves Web Page ................................................................................... 193
Invalid Slaves Web Page .................................................................................... 194
Slave Status Web Page ....................................................................................... 195
Status & Settings Web Page............................................................................... 196
DeviceNet Devices Web Page............................................................................ 199
Files and File System in LD 800DN ............................................................................. 201
File System Structure......................................................................................... 202
File System Security .......................................................................................... 202
User Accounts on LD 800DN............................................................................ 203
Pre-existing Directories and Files...................................................................... 204
LD 800DN System Files.................................................................................... 204
Run/Idle State................................................................................................................ 209
Automatic Device Recovery ......................................................................................... 210
Address Recovery .............................................................................................. 210
Configuration Recovery ..................................................................................... 211
Configuring ADR from Control Builder............................................................ 211
Section 7 - Technical Data

General Technical Data ................................................................................................. 213
Technical Data for LD 800DN ...................................................................................... 214
Technical Data for connection to Allen Bradley Logix 5000 Series PLC on EtherNet/IP215
Technical data for S200 IO modules ............................................................................. 215
Performance Data.......................................................................................................... 216
Section 8 - Hardware Connections

Connect CI873 on CEX Bus ......................................................................................... 217
8 9ARD000014-600 A
Table of Contents
Connect CI873 to LD 800DN........................................................................................218

Connectors..........................................................................................................218
Power ...........................................................................................................218
DeviceNet...........................................................................................................219
Ethernet RJ45 .....................................................................................................220
Auxiliary RS-232 9 Pin D-Subminiature ...........................................................221
Appendix A - Troubleshooting EDS File
Appendix B - Troubleshooting CI873 Log Entries

Connection Error ................................................................................................247
Configuration Error ............................................................................................252
Index
9ARD000014-600 A 9
Table of Contents
10 9ARD000014-600 A
About This User Manual
Any security measures described in this document, for example, for user access,
password security, network security, firewalls, virus protection, etc., represent
possible steps that a user of an 800xA System may want to consider based on a
risk assessment for a particular application and installation. This risk assessment,
as well as the proper implementation, configuration, installation, operation,
administration, and maintenance of all relevant security related equipment,
software, and procedures, are the responsibility of the user of the 800xA System.
This user manual describes the integration of CI873 interface for EtherNet/IP and
DeviceNet communication in AC 800M, Common Industrial Protocol (CIP)
architecture, and integration of CIP in Control Builder and AC 800M.
The main areas covered in user manual are:
• CI873 EtherNet/IP Hardware Library (CI873EthernetIPHWLib).
• Device Import Wizard, used to import the Electronic Data Sheet (EDS) files
into Control Builder.
Intended User
This user manual is intended for engineers who are planning and designing
EtherNet/IP and DeviceNet networks. The reader is expected to be familiar with the
Control Builder programming tool and the AC 800M products under the 800xA
system.
9ARD000014-600 A 11
User Manual Conventions About This User Manual
User Manual Conventions

Microsoft Windows conventions are normally used for the standard presentation of
material when entering text, key sequences, prompts, messages, menu items, screen
elements, etc.
Warning, Caution, Information, and Tip Icons

This User Manual includes Warning, Caution, and Information where appropriate to
point out safety related or other important information. It also includes Tip to point
out useful hints to the reader. The corresponding symbols should be interpreted as
follows:
Electrical warning icon indicates the presence of a hazard that could result in
electrical shock.
Warning icon indicates the presence of a hazard that could result in personal
injury.
Caution icon indicates important information or warning related to the concept
discussed in the text. It might indicate the presence of a hazard that could result
in corruption of software or damage to equipment/property.
Information icon alerts the reader to pertinent facts and conditions.
Tip icon indicates advice on, for example, how to design your project or how to
use a certain function
Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
fully comply with all Warning and Caution notices.
12 9ARD000014-600 A
About This User Manual Terminology
Terminology
A complete and comprehensive list of terms is included in System 800xA System
Guide Functional Description (3BSE038018*). The listing includes terms and
definitions that apply to the 800xA System where the usage is different from
commonly accepted industry standard definitions and definitions given in standard
dictionaries such as Webster’s Dictionary of Computer Terms. Terms that uniquely
apply to this User Manual are listed in the following table.
Term/Acronym Description
AC 800M ABB controller 800 series, general purpose process
controller series by ABB.
ADR Automatic Device Recovery: Feature of the DeviceNet
master which allows a slave node that has dropped off
the network to be replaced with another device of the
same type.
BWConfig BWConfig is an MS Windows application, which is used
to communicate with LD 800DN over a standard RS-232
serial link. BWConfig is used to set the IP address, MAC
ID, and upgrade firmware for the LD 800DN (Ethernet to
DeviceNet Gateway).
CIP Common Industrial Protocol.
Class 1 Communication I/O Communication which requires dedicated CIP
connection to be established.
Class 3 Communication I/O communication that uses symbolic representation
(tag based) to write data in to the Allen Bradley PLC.
DeviceNet Network The DeviceNet network is an open device level network
that provides connections between simple industrial
devices (such as sensors and actuators) and 
higher-level devices (such as programmable controllers).
Devices Represents EtherNet/IP or DeviceNet device with
profiles (general purpose, modular, PLC, etc).
9ARD000014-600 A 13
Terminology About This User Manual
EDS The Electronic Data Sheet (EDS) file contains device
specific information of EtherNet/IP and DeviceNet
devices.
EtherNet/IP The EtherNet/IP network offers a full suite of control,
configuration, and data collection services by layering
the Common Industrial Protocol over the standard
protocols used by the Internet (TCP/IP and UDP).
EtherNet/IP uses TCP/IP for general
messaging/information exchange services and UDP/IP
for I/O messaging services for control applications. This
combination of well-accepted standards provides the
functionality required to support both information data
exchange as well as control applications.
Explicit Messaging Explicit Messaging provide a one-time transport of a
data item. They can be sent as connected or
unconnected. These messages are typically point-to-
point.
HW Abbreviation for Hardware.
I/O Abbreviation for Input and Output.
I/O Adapter An I/O Adapter receives implicit communications
requests from an I/O Scanner, then produces and
consumes its I/O data, typically at the requested cyclic
rate. An I/O adapter can be a simple digital input device,
or something more complex such as modular pneumatic
valve system.
I/O Connection CIP connection which provides dedicated, special
purpose communication paths between producing
application and one or more consuming applications for
data exchange.
I/O Messages/Packet I/O Message consists of a Connection ID and optional
associated I/O data. One I/O message means one
complete Input/ Output Assembly data.
14 9ARD000014-600 A
About This User Manual Terminology
Implicit messaging  Also known as I/O messaging. Implicit Messages are
(I/O Messaging) exchanged across I/O Connections with an associated
Connection ID. The Connection ID defines the meaning
of the data and establishes the regular/repeated
transport rate and the transport class. It can be point-to-
point or multicast and are used to transmit application
specific I/O data.
ISP Input Set as Predetermined. ISP values are preset
default values of channels, as seen by the application,
when communication between CI873 and I/O devices
break. ISP is set to the last good value if there is any
channel error.
I/O Scanner An I/O Scanner initiates implicit connections with I/O
adapter devices, that is, it is an I/O Client. A scanner is
typically the most complex type of EtherNet/IP device, as
it must deal with issues such as configuration of which
connections to make, and how to configure the adapter
device. Scanners also typically support initiating explicit
messages, that is, it is also an Explicit Message Client. A
programmable controller is an example of an I/O
scanner (used interchangeably with Scanner class).
LD 800DN LD 800DN is a linking device, which is used to connect
DeviceNet devices with the control level network.
Linking Device EtherNet/IP to DeviceNet gateway, referred to as LD
800DN in the Control Builder hardware tree.
O->T Originator to Target. (used to describe packets that are
sent from the originator to the target)
RPI The rate of packet transmission from one node to
(Requested Packet another.
Interval)
Scan List The list of DeviceNet devices that needs LD 800DN to
establish connection with.
9ARD000014-600 A 15
Terminology About This User Manual
T->O Target to Originator. (used to describe packets that are
sent from the target to the originator).
Target Term used for Server/Slave of CIP connection.
16 9ARD000014-600 A
About This User Manual Released User Manuals and Release Notes
Released User Manuals and Release Notes

A complete list of all User Manuals and Release Notes applicable to System 800xA
is provided in System 800xA Released User Manuals and Release Notes
(3BUA000263*).
System 800xA Released User Manuals and Release Notes (3BUA000263*) is
updated each time a document is updated or a new document is released. It is in pdf
format and is provided in the following ways:
• Included on the documentation media provided with the system and published
to ABB SolutionsBank when released as part of a major or minor release,
Service Pack, Feature Pack, or System Revision.
• Published to ABB SolutionsBank when a User Manual or Release Note is
updated in between any of the release cycles listed in the first bullet.
A product bulletin is published each time System 800xA Released User Manuals
and Release Notes (3BUA000263*) is updated and published to ABB
SolutionsBank.
9ARD000014-600 A 17
Released User Manuals and Release Notes About This User Manual
18 9ARD000014-600 A
Section 1 Introduction
Overview
The Industrial Ethernet Protocol (EtherNet/IP) is the combination of traditional
Ethernet and an industrial application layer protocol, called the Common Industrial
Protocol (CIP). EtherNet/IP is used in industrial automation applications.
DeviceNet is a low-level industrial application layer protocol, based on Common
Industrial Protocol, for industrial automation applications. DeviceNet is built on the
standard Controller Area Network (CAN).
Both EtherNet/IP and DeviceNet have several features in common with CIP. Both
serve as communication networks between industrial controllers and I/O devices.
CI873 Communication Interface Module

EtherNet/IP device interfaces with the AC 800M controller, through the CI873
communication interface module. CI873 acts as an EtherNet/IP I/O scanner class
device. It originates connections to EtherNet/IP enabled devices and exchanges real
time I/O data with them.
The CI873 communication interface provides the following functionalities:
• Configuration of EtherNet/IP and DeviceNet devices.
• CI873 as EtherNet/IP I/O scanner.
• I/O communication with EtherNet/IP and DeviceNet devices using Class 1
connection.
• Status supervision of CI873, EtherNet/IP, DeviceNet, and Linking devices.
CI873 originate a Class 1 connection to Linking device (LD 800DN) for
DeviceNet device status.
• Hot swap of CI873, LD 800DN, DeviceNet, and EtherNet/IP devices.
9ARD000014-600 A 19
Linking Device LD 800DN Section 1 Introduction
• CI873 supports connection point based Class 1 connection for reading and
writing data to EtherNet/IP devices (except Allen Bradley PLC).
• CI873 supports tag based Class 1 for tag reading and Class 3 for tag writing to
Allen Bradley Logix 5000 series PLC.
• CI873 Scanner diagnostics.
• LD 800DN Scanner diagnostics.
• CI873 Firmware Upgrade.
• Online upgrade for CI873 Firmware.
• CI873 module redundancy.
Linking Device LD 800DN

The linking device LD 800DN functions as an EtherNet/IP target on the EtherNet
network. It acts as a gateway device by forwarding the content of the messages from
EtherNet/IP networks to DeviceNet networks and vice-versa, without acting on the
content of the messages.
The LD 800DN Linking device acts as the DeviceNet Master in the DeviceNet
network, allowing connectivity to 63 DeviceNet slave devices.
Device Import Wizard

For configuring EtherNet/IP and DeviceNet devices using Control Builder, the
Electronic Data Sheet (EDS) file of the device is required. The EDS file is a
specially formatted ASCII file of the device, defining its characteristics. The device
vendor provides this file, to allow access to device configuration parameters. The
Device Import Wizard, an integrated component of the Control Builder, allows
importing of such EDS files into the hardware library.
20 9ARD000014-600 A
Section 1 Introduction Device Import Wizard
The Device Import Wizard essentially converts the device description files (EDS
files) of EtherNet/IP and DeviceNet devices into hardware unit types. These unit
types are then instantiated in the Hardware tree of Control Builder.
The configuration of the CI873 communication interface, linking devices, EtherNet/IP
devices and DeviceNet devices are done through the Control Builder. Figure 1
illustrates a possible system configuration scenario.
9ARD000014-600 A 21
Device Import Wizard Section 1 Introduction
Figure 1. System configuration
22 9ARD000014-600 A
Section 1 Introduction EtherNet/IP Embedded Switch Technology Overview
EtherNet/IP Embedded Switch Technology Overview

The EtherNet/IP embedded switch technology offers alternative network topologies
for interconnecting EtherNet/IP devices by embedding switches into the end
devices.
EtherNet/IP Star Topology

The traditional EtherNet/IP network topology has been a star, where end devices are
connected and communicate with each other via a switch. The Figure 2 below
shows an EtherNet/IP star configuration.
Figure 2. EtherNet/IP Star Topology
9ARD000014-600 A 23
Linear Network Section 1 Introduction
Linear Network
Embedded switch technology is designed to enable end devices to form linear and
ring network topologies.
Products with EtherNet/IP embedded switch technology have two ports to
connect to a linear or DLR network in a single subnet.
You cannot use these ports as two Network Interface Cards (NICs) connected to
two different subnets.
A linear network is a collection of devices that are daisy-chained together. The
EtherNet/IP embedded switch technology lets you implement this topology at the
device level. No additional switches are required.
200-AENTR is a device that can be connected linear.
Figure 3. Linear Network Topology
24 9ARD000014-600 A
Section 1 Introduction Linear Network
The following are advantages of a linear network:

• Simple installation.
• Reduced wiring and installation costs.
• No special software configuration required.
• Improved CIP Sync application performance on linear networks.
The primary disadvantage of a linear network is that any break of the cable
disconnects all devices downstream from the break from the rest of the network.
9ARD000014-600 A 25
Linear Network Section 1 Introduction
26 9ARD000014-600 A
Section 2 Functional Description
Overview
This section covers the following topics:
• User Interface on page 28.
• CI873 Connections on page 30
• CI873 Module Redundancy on page 42
• Status Handling:
– Status Handling for CI873 on page 33
– Status Handling for LD 800DN on page 35
– Status Handling for DeviceNet Slaves on page 37
– Status Handling for EtherNet/IP Device on page 39
– Status Handling for S200 IO Modules on page 41
• Hot Swap:
– Hot Swap of CI873 on page 43
– Hot Swap of LD 800DN on page 44
– Hot Swap of DeviceNet Devices on page 44
– Hot Swap of EtherNet/IP Device on page 45
9ARD000014-600 A 27
User Interface Section 2 Functional Description
User Interface
This section describes the user interface for the protocol, such as hardware units and
their configuration parameters, status, alarms, and events.
Hardware Tree
The Hardware Tree is a hierarchical representation of information in the Control
Builder. The configuration of the controller, the Communication interfaces and the
devices and I/O modules under it is specified in the hardware tree. Configuration
information is provided at each level in the hardware tree.
Figure 4 shows the typical hardware tree for CI873, depicting the DeviceNet and
EtherNet/IP device unit types imported into hardware library using EDS files. The
CI873 represents an EtherNet/IP I/O scanner which originates the CIP connections.
All the devices configured under CI873 represent targets to which the I/O scanner
establishes the connections. Each device is represented with one hardware unit
which contains the configuration related parameters to be downloaded to the device.
The hardware unit also contains connection related parameters to establish
connections to the device, and I/O channels to view the I/O data.
The CI873EthernetIPHWLib contains the hardware units for CI873, CI873 Scanner
Diagnostics, LD 800DN linking device, and LD 800DN diagnostics.
28 9ARD000014-600 A
Section 2 Functional Description Hardware Tree
Figure 4. A typical hardware tree configuration in Control Builder
9ARD000014-600 A 29
CI873 Connections Section 2 Functional Description
CI873 Connections
All connections between the CI873 EtherNet/IP I/O scanner and the EtherNet/IP
targets (like LD 800DN linking devices) can be categorized as I/O connections (also
called, implicit connections).
The following chart categorizes the message transport classes supported by
EtherNet/IP:
Explicit Messaging Implicit Data Transfer

Unscheduled TCP/IP Scheduled UDP/IP
Unconnected UCMM n/a
Connected Class 3 Class 1
Implicit Messaging (Class1)

Implicit messaging connections are used for real time I/O data transfer and is
transmitted via UDP.
Class 1 can be either be tag based or connection point based.
• Also known as I/O messaging. Implicit messages are exchanged across I/O
connections with an associated connection ID. The connection ID defines the
meaning of the data and establishes the regular or repeated transport rate and
the transport class. It can be point-to-point or multicast.
• Used to transmit time critical I/O data as it is faster than Class 3.
30 9ARD000014-600 A
Section 2 Functional Description CI873 Connections
Explicit Messaging (Class 3 or UCMM)

Unconnected explicit messaging is used for configuration. It is transmitted over a
TCP connection.
• Explicit messages provide a one-time transport of data item. They can be sent
as connected or unconnected. These messages are typically point-to-point.
• Explicit messages provide the typical request or response-oriented network
communications.
• Predominantly used for device configuration and diagnostics.
For class 3, communication is tag based.
CIP Connection Time-out Calculation

The Requested Packet Interval (RPI) is the requested time interval between packets
in case of Implicit communication for I/O data transfer. In the T -> O RPI
parameter on the EtherNet/IP target, the time interval between packets received by
CI873 EtherNet/IP I/O scanner from target, can be configured.
T -> O RPI value should suit the requirement of the application. The lowest value
configurable to this parameter is 10ms, which results in the fastest possible
communication.
9ARD000014-600 A 31
CI873 Connections Section 2 Functional Description
For example, in case of LD 800DN linking device, where T -> O RPI is set to 10ms.
The time out multiplier is preset at 2 (not configurable by user). The Time Out value
is derived from the following formula:
Time Out value = T -> O RPI * Time Out Multiplier = 40ms.
So, if the CI873 EtherNet/IP I/O scanner does not receive any packets from LD
800DN for a period defined by the Time Out Value (here, 40ms) then the Implicit
messaging connection to LD 800DN times out and no I/O data from DeviceNet
slaves are updated to IEC 1131 application, but instead will have ISP values.
Connection Time-out Multiplier

The Connection Time-out Multiplier specifies the multiplier applied to the RPI to
obtain the connection time-out value. Devices shall stop transmitting on a
connection whenever the connection times out even if the pending close has been
sent. The multiplier shall be as represented in the below Table 1.
Table 1. Connection Time-out Multiplier Values
Value Multiplier
0 x4
1 x8
2 x16
3 x32
4 x64
5 x128
6 x256
7 x512
32 9ARD000014-600 A
Section 2 Functional Description Status Handling
Status Handling
This section describes the status handling for CI873, LD 800DN linking device,
DeviceNet slave units, and EtherNet/IP devices.
Status Handling for CI873

Table 2 shows all CI873 specific Unit Status bits in ErrorAndWarnings.
Table 2. Errors and warnings for CI873 Hardware Unit
Bit Value Text Indication Alarm/Event Severity Description

31 0x80000000 Internal Hardware Error Alarm High Set when there
Error is a hardware
problem in the
CI873 board.
30 0x40000000 Internal Firm Ware Error Alarm High Set when there
Error is a problem in
the CI873
firmware and not
due to user
configuration.
29 0x20000000 Error Generated by Warning Alarm Medium Set when a
Task Supervisor software task is
not responding.
The CI873
restarts when
this error
happens.
9ARD000014-600 A 33
Status Handling for CI873 Section 2 Functional Description
Table 3. Extended status of CI873 Hardware Unit

1 0x00000002 E-net Link Warning Alarm High Set when Ethernet
Down. Cable is removed
from the port.
2 0x00000004 Backup Enet Warning Alarm Medium Set when Backup
Link Down CI873 Ethernet cable
is removed.
3 0x00000008 NETWORK Error Alarm High Set when network
STORM storm is detected
DETECTED either in Backup or
Primary CI.
4 0x00000010 Backup Warning Alarm Medium Backup device is
device is being configured
being
configured
5 0x00000020 Backup Warning Alarm Medium Backup device not
device not synchronized
synchronized
34 9ARD000014-600 A
Section 2 Functional Description Status Handling for LD 800DN
Status Handling for LD 800DN

Table 4 shows all LD 800DN specific Unit Status bits in ErrorAndWarnings and
ExtendedStatus.
Table 4. Errors and Warnings of LD 800DN

13 0x00002000 Connection Error Alarm Medium Set when the connection
Error between CI873 and 
LD 800DN is failed to
establish or timedout.
31 0x80000000 Device Not Error Alarm High Set when LD 800DN is
Found not present in the network
29 0x20000000 Internal Warning - - Set when the
Config Error configuration requests, to
configure LD, fails.
27 0x08000000 Duplicate Error Alarm High Set when one of the
MAC ID DeviceNet device has the
same MAC ID as 
LD 800DN
24 0x01000000 ADR Error Error Alarm High Set when an error
occurred during auto
device recovery of a
DeviceNet device.
23 0x00800000 No Error Alarm High Set when there is no
DeviceNet Network power detected
Power on the DeviceNet network
22 0x00400000 CAN Bus off Error Alarm High Set when the CAN
Controller is in the Bus-
Off state
9ARD000014-600 A 35
Status Handling for LD 800DN Section 2 Functional Description
Table 5. Extended status of LD 800DN

1 0x00000002 No Warning Alarm Low Set when no CAN
Messages packets received from
for DeviceNet network for
Scanner more than 10 seconds
2 0x00000004 In Idle Warning Alarm Low Set when LD goes to
Mode Idle Mode
3 0x00000008 Duplicate Error Alarm Medium Set when LD is checking
MAC Id for Duplicate MAC ID
Check in Check during start up.
progress
4 0x00000010 In Fault Error Alarm High Set when LD goes to
Mode Fault state
5 0x00000020 Wrong Error Alarm High Set when the actual
MacID MAC ID of LD 800DN in
the network is not
matching with the MAC
ID configured in CB for
LD 800DN HWUnit
6 0x00000040 Duplicate Error Alarm Medium Set when LD 800DN
MAC Id fails to send Duplicate
Check MAC ID Check request
Error
36 9ARD000014-600 A
Section 2 Functional Description Status Handling for DeviceNet Slaves
Status Handling for DeviceNet Slaves

Table 6 shows all DeviceNet slave specific Unit Status bits in ErrorAndWarnings.
Table 6. Errors and Warnings of DeviceNet Device

31 0x80000000 Device Not Warning Alarm High Set when
Found DeviceNet device
is removed from
network or it is not
accessible.
30 0x40000000 Wrong Warning Alarm High Set if the
Device Type electronic Key is
enabled for
DeviceNet device
and its Identity
Information is not
matching with the
device in network.
29 0x20000000 Internal Warning - - Set when the
Config Error configuration
requests, to
configure
DeviceNet device,
fails.
28 0x10000000 Connection Warning Alarm High Set when
Timed Out Connection with
the DeviceNet
device is not
Timed out
27 0x08000000 Duplicate Warning Alarm High Set when another
MAC Id DeviceNet device
Error found at the same
MAC id.
9ARD000014-600 A 37
Status Handling for DeviceNet Slaves Section 2 Functional Description
Table 6. Errors and Warnings of DeviceNet Device (Continued)

26 0x04000000 Keeper Warning - - Set if
space ConfigRecovery is
exceeded. enabled for device
ADR not and its
configured configuration is
not able to write to
LD 800DN’s
Keeper memory
due to lack of
Keeper Memory
25 0x02000000 Slave Warning - - Set when the
Connection Connection
Initialization between 
in progress LD 800DN and
DeviceNet device
is in progress
24 0x01000000 ADR Error Warning Alarm High Set if an error
occurred during
auto device
replacement or
auto configuration
23 0x00800000 No Warning Alarm High Set when there is
DeviceNet no Network power
Power detected on the
DeviceNet
network
22 0x00400000 CAN Bus Warning Alarm High Set when the CAN
Off Controller is in the
Bus-Off state
38 9ARD000014-600 A
Section 2 Functional Description Status Handling for EtherNet/IP Device
Table 7. Extended status of DeviceNet Device

7 0x00000080 No Warning Alarm Low Set when no
Connection connections are
enabled for the device
Enabled
During the update of status information for a modular DeviceNet adapter, the I/O
modules configured under the adapter (the child units) are also updated with the
same status information. The Sub I/O modules that are configured with addresses
1 to 63 under the adapter are updated with status information.
Status Handling for EtherNet/IP Device

Table 8 shows all EtherNet/IP device specific Unit Status bits in ErrorAndWarnings
and ExtendedStatus.
Table 8. Errors and Warnings of EtherNet/IP device

13 0x00002000 Connection Error Alarm High Set when connection
Error request from CI873
to this device returns
error.
14 0x00004000 Configuration Error Alarm High Set when the CI
Error receives wrong
response when it
wrote configuration
data.
31 0x80000000 Device Not Error Alarm High Set when the Device
Found is not present in the
network
9ARD000014-600 A 39
Status Handling for EtherNet/IP Device Section 2 Functional Description
Table 8. Errors and Warnings of EtherNet/IP device (Continued)

30 0x40000000 Wrong Error Alarm High Set when the
Device Type different device is
present at the
specified network
address.
29 0x20000000 Internal Warning Alarm Medium Set when the device
Config Error returns any of the
general error codes
24 0x01000000 Tag Error Warning Alarm High Set when class3
write fails
Table 9. Extended Status of EtherNet/IP device

7 0x00000080 No Warning Alarm Low Set when no
Connection connections are
Enabled enabled for the device
Refer Appendix B, Troubleshooting CI873 Log Entries for details on

troubleshooting messages displayed in CI873 log files.
40 9ARD000014-600 A
Section 2 Functional Description Status Handling for S200 IO Modules
Status Handling for S200 IO Modules

Refer to Table 10 for the alarm and events generated for S200 I/O units.
Table 10. Errors and Warnings of S200 IO modules

13 0x00002000 Connection Error Alarm High Set when connection
Error request from CI873 to
this device returns
error.
14 0x00004000 Configurati Error Alarm High Set when the CI
on Error receives wrong
response when it wrote
configuration data.
31 0x80000000 Device Not Error Alarm High Set when the Device is
Found not present in the
network
30 0x40000000 Wrong Error Alarm High Set when the different
Device device is present at the
Type specified network
address.
29 0x20000000 Internal Warning Alarm Medium Set when the device
Config Error returns any of the
general error codes
9ARD000014-600 A 41
CI873 Module Redundancy Section 2 Functional Description
Table 11. Extended status of S200 IO modules

0 0x00000001 Minor Warning Alarm Low Set when there is
Revision any mismatch
Mismatch between the minor
revision in the hwd
file and device.
7 0x00000080 No Warning Alarm Low Set when no IO
Connection modules are
Enabled connected for S200
adapter
CI873 Module Redundancy

In CI873 module redundancy functionality, there is primary and backup CI873
modules available in the network. When the Configuration is downloaded from
Control Builder, the primary and backup CI873 modules are configured with
primary and backup IP address respectively. Both primary and backup modules
receive the configuration data, and store them in their internal structures. During a
failure of primary CI873 module, the back up CI873 module takes over and all
connections are synchronized with the back up CI873 module. This leads to
continuous I/O communication with minimal downtime.
The module redundancy also works with the slave devices, irrespective if the slave
supports redundant connection from the master. This is because at any time there
shall only be single connection from the primary CI873 to the slave.
Hot Swap
This section describes the hot swap functionality for CI873, DeviceNet devices,
EtherNet/IP devices, and LD 800DN linking devices.
42 9ARD000014-600 A
Section 2 Functional Description Hot Swap of CI873
Hot Swap of CI873

CI873 supports hot swap. The faulty unit can be replaced online, without disturbing
other units connected to the CEX bus.
After hot removal, the connected I/O channels are marked bad and IEC 1131
variables are set to last good value. Following the subsequent insertion, the new
CI873 gets configured automatically.
In case of redundant CI873, after hot removal of primary CI873, the back up CI873
will take over the EtherNet/IP network and establish the I/O connections.
When CI873 is hot swapped, there shall be a re-configuration of all devices
(EtherNet/IP as well as DeviceNet) under it.
The following conditions exists when the CI873 device is not responding or is not
available in the network:
• The device configuration is skipped, if the CI873 device fails to connect for 3
times. The Unit Status of CI873 /alarm displays Waiting for Hardware
Initialization, until CI873 boots-up.
• During this error status, the I/O value update to the application stops.
• The error status continues to display Waiting for Hardware
Initialization on the CI873, when the cable connected to the CI873 is
removed followed by the hot swap of CI873. During this, the status of the
devices under CI873 is not updated in Control Builder. The error status is reset
on CI873 and the status of devices under CI873 is updated, when the cable is
connected back to the CI873.
The time taken for the CI873 to boot up after a hot insert depends on the hardware
tree, that is, the number of devices connected under the CI873.
The maximum time taken by CI873 for boot-up is 3 minutes. In addition to this
boot-up time, the CI873 takes some time to establish communication
(EtherNet/IP Communication) with the devices configured under it.
The time required for CI873 to boot up shall also depends on the configuration of
the devices after the hot insert. If an device is not physically available, the time
required for configuration increases as it would wait for time-out for the device.
9ARD000014-600 A 43
Hot Swap of LD 800DN Section 2 Functional Description
Hot Swap of LD 800DN

LD 800DN devices supports hot swap. Faulty units can be replaced online and
status is communicated to the CI873. After the hot insertion of new linking device
unit, CI873 configures the linking device automatically.
The new linking device replacing the faulty unit should be configured with the
same IP address and MAC ID used previously.
Hot Swap of DeviceNet Devices

Hot swap of DeviceNet devices is supported through the Automatic Device
Recovery (ADR) feature of the LD 800DN linking device. Faulty units can be
replaced online without disturbing the communication with other DeviceNet slaves
in the network.
Automatic Device Recovery

Automatic Device Recovery (ADR) is a feature of the LD 800DN linking device.
This feature allows a DeviceNet slave node to be replaced with another device of the
same type.
In this feature, if a DeviceNet slave device drops off the network due to fault or
power loss, and is replaced with another device of the same type, then LD 800DN
automatically configures the new device (the replacement) to the MAC ID address
downloaded for the device in the Control Builder.
The ADR feature consists of Address Recovery and Configuration Recovery.
Address Recovery automatically sets the address of the new slave device to that of
the slave device which has lost communication, provided the new device is inserted
at MAC ID 63. Address Recovery is enabled by enabling the ADR parameter of the
LD 800DN.
Configuration Recovery automatically configures the new slave device to the
settings of the slave device it replaces. For enabling Configuration Recovery, both
the ADR parameter of the LD 800DN and the Config Recovery parameter of the
associated DeviceNet device should be enabled.
When a DeviceNet slave is replaced with a new one, the linking device LD 800DN
checks the identity of the new device before performing any operation. The extent of
44 9ARD000014-600 A
Section 2 Functional Description Hot Swap of EtherNet/IP Device
check done depends on the Electronic Key parameters enabled. For more details on
the Electronic Key parameters, refer to Electronic Key Parameters on page 124.
When the DeviceNet IP device is removed and re-inserted, it shall be 

re-configured only if the address recovery for the LD800DN and the Config
recovery for the device are enabled.
For details on the ADR parameter, refer Configuring LD 800DN Linking Device
Unit on page 110.
For details on the parameter for Configuration Recovery, refer Configuring a
DeviceNet Slave Device Unit on page 122.
Address recovery will not work for DeviceNet device which has physical
switches/jumpers for setting MAC address. It works for DeviceNet devices whose
MAC address can be dynamically set, either from the LD 800DN Web interface,
or by any device specific configuration tools, for example, RSNetworks for
DeviceNet.
When wrong MAC ID is specified in the Control Builder configuration it is
detected through the MAC ID check and shown error on the linking device. But
the communication between linking device and DeviceNet devices happens at the
right MAC ID configured at the linking device level and the communication
between communication interface and linking device is using IP address so there
will not be any problem.
Hot Swap of EtherNet/IP Device

EtherNet/IP devices supports hot swap. Faulty units can be replaced online without
disturbing the communication with other EtherNet/IP slaves in the network.
When the EtherNet/IP device is removed and re-inserted, it shall be re-configured
again by the CI873.
9ARD000014-600 A 45
Hot Swap of EtherNet/IP Device Section 2 Functional Description
46 9ARD000014-600 A
Section 3 Device Import Wizard
Introduction
The Device Import Wizard is an integrated component of the Control Builder. It
converts the device description files (EDS files) of EtherNet/IP and DeviceNet
devices into hardware unit types. These unit types can be instantiated in the
Hardware tree of the Control Builder.
While converting the EDS files of EtherNet/IP into hardware unit types, it is
possible to add Class 3 and Class 1 connections with tag information. For more
information refer, Allen Bradley Logix 5000 Series PLCs on page 81.
EDS File Content

The EDS file should have specific contents to establish connection with the devices.
EDS file for an Ethernet/IP device

The Connection Manager section in EDS is required to establish connection and
communication to the device. And for configuration, Parameter section is required.
EDS file for an Allen Bradley Logix 5000 series PLC

Tag based Class 1 connection information should be available in EDS file of the
Logix 5000 Controllers for communication with CI873.
EDS file for a DeviceNet device

The IO_Info section in EDS is required to establish connection to the device.
The DIW uses the following rules in case there are vendor specific keywords in
DeviceNet EDS files for connections:
9ARD000014-600 A 47
EDS File Content Section 3 Device Import Wizard
• If the EDS file has both normal connections as well as vendor specific
connections, the DIW considers the normal connections while generating the
hardware file. The vendor specific connections are ignored. If the EDS file has
only vendor specific connections, then the vendor specific connections will be
considered while generating the hardware file.
• DIW supports vendor specific connections provided the fields for these
connections in the EDS file are as per the CIP specification. Else the import is
aborted with a message mentioning that the vendor connection fields are not as
per the CIP specification.
If the EDS file does not have relevant sections as mentioned above related to
connection, the import process of that EDS file is aborted.
48 9ARD000014-600 A
Section 3 Device Import Wizard Converting an EDS File to a Hardware Unit Type
Converting an EDS File to a Hardware Unit Type

To use the Device Import Wizard for converting an EDS file to a hardware unit type,
follow these steps:
1. Open the Control Builder and create a new project.
2. Select Libraries > Hardware.
3. If a new library is to be created, then:
– Right-click Hardware and select New Library. The New Library
window is displayed, as shown in Figure 5.
Figure 5. New Library Window
– Enter a library name in the Name field and click OK. The new user
defined library is created under the hardware tree.
4. From the hardware tree, expand the user defined library.
5. Right-click Hardware types and select Insert/Replace Hardware Type(s).
The Insert Hardware Definitions window appears as shown in Figure 6.
9ARD000014-600 A 49
Converting an EDS File to a Hardware Unit Type Section 3 Device Import Wizard
Figure 6. Insert Hardware Definitions
6. Select the file type as EthernetIP(*.eds).

7. Browse and select the File Name of the EDS file to be converted.
The EDS file to be selected, depends on whether to import a modular or non-
modular file. For modular file import, ensure that the adapter's EDS file is
selected first.
8. After selecting the EDS file, click Open. The Welcome screen of Device
Import Wizard appears as shown in Figure 7.
50 9ARD000014-600 A
Figure 7. Device Import Wizard Welcome Dialog
9. If loading of EDS file fails, then an erroneous welcome page appears as shown
in Figure 8.
9ARD000014-600 A 51
Figure 8. Erroneous Welcome page
10. Click Cancel to exit from the import process.
Repeat the preceding steps to re-attempt the loading of the EDS file. If the
loading fails again, install Control Builder again.
11. Click Next in the Welcome screen of Device Import Wizard. Depending on
the EDS file initially selected in Step 7, either of following windows are
displayed.
– If the EDS file belongs to a non-modular device, then General Purpose
Device window appears as shown in Figure 9.
– If the EDS file is an adapter’s file, then Modular IO System window
appears as shown in Figure 10.
52 9ARD000014-600 A
Figure 9. General Purpose Device
General Purpose Device

In the General Purpose Device window, the selected EDS file is displayed.
The EDS file is displayed under different category namely, File name, Product
Name, Device Type and Device Profile. Click Next in the General Purpose
Device window to proceed to Step 12.
9ARD000014-600 A 53
Figure 10. Modular I/O System
Modular IO System
In the Modular IO System window, click Browse. A File Open dialog box is
displayed as shown in Figure 11. Select the IO modules to be imported with the
adaptor and proceed with the import process.
Click Delete to remove any unnecessary file selected before.
54 9ARD000014-600 A
Figure 11. Multiple file selection dialog
In case of performing a re-import of a Modular I/O EDS file, select the required
adapter file during re-import. A Modular I/O re-import can be done by selecting
the adapter file alone, as the adapter file holds all the references to I/O modules.
If a user attempts importing an adapter consecutively from two different folders
under the same hardware library, then the import is blocked and the following
message is displayed:
An adapter of the similar name from a folder <folder_name>
other than the current folder has been imported. Please
select the adapter from the earlier imported folder or
change the name of the current adapter's eds being imported
and try again.
9ARD000014-600 A 55
12. In the Device Import Wizard, click Next. The File and Device Information
window is displayed as shown in Figure 12.
Figure 12. File and Device Information window
The File and Device Information window is displayed after the EDS file has been
selected through the Device Import Wizard. The File and Device Information
window consists of the following two tabs:
• Device (see Device on page 57).
• File (see File on page 61).
56 9ARD000014-600 A
Section 3 Device Import Wizard Device
Device
The Device tab displays the device information of the EDS file being imported. The
Device tab has a tree view on the left pane. The tree view displays devices by their
product names or catalog numbers, depending on whether Catalog number or
Product name option is selected. By default, Product name is selected.
The tree view has check mark icons beside the product names or catalog numbers.
The color of a check mark icon indicates the following:
• Green – Indicates that the EDS file is being imported for the first time.
• Blue – Indicates that the EDS file is being re-imported.
• Red - Indicates that the EDS file import was aborted during a previous import.
Selecting a product name or catalog name from the tree view displays the following
details:
• Product name.
• Product type description.
• Vendor name.
• Major revision number.
• Minor revision number.
• Catalog number.
Modify the following details as required:
• Product name as in HWD file - The product name as it appears in the HWD
file.
• Description - A brief description of the product.
• Hardware Tree icon - This drop-down list enables to change the icon displayed
in the Control Builder Hardware tree. The listed icons are shown in Table 12:
9ARD000014-600 A 57
Device Section 3 Device Import Wizard
Table 12. Hardware Tree Icons
Icon Name Icon for

ETHERNETIP_ADAPTERType Ethernet/IP Modular Adapter
ETHERNETIP_DEVICEType Ethernet/IP Non-Modular Device
DEVICENET_ADAPTERTypes DeviceNet Modular Adapter
DEVICENET_DEVICEType DeviceNet Non-Modular Device
RackIOType Any I/O module
Only existing icons can be selected from the Hardware tree icon drop-down list,
based on the device type.
In the Device tab, click Restore Defaults to restore the values of modified fields
back to their original values, as per the EDS file.
Select All and Select None are enabled only for multiple EDS file import (Modular
import), as shown in Figure 14. In this case, the tree view shows multiple EDS files,
with the Adapter file at the top.
Two devices with same names cannot exist under the same hardware library.
Hence, to allow import of the same device with different major revisions, the
Major Revision number is appended at the end of Product name and Product
name in HWD.
These are the examples of different EDS file selected.
• Refer Figure 13 to see how Device tab appears when a non-modular file is
selected.
• Refer Figure 14 to see how Device tab appears when a modular file is selected
• Refer Figure 15 to see how Device tab appears when a Control Logix PLC
EDS file is selected
58 9ARD000014-600 A
Section 3 Device Import Wizard Device
Figure 13. Device Tab for Non-Modular
9ARD000014-600 A 59
Device Section 3 Device Import Wizard
Figure 14. Device tab for Modular I/O
60 9ARD000014-600 A
Section 3 Device Import Wizard File
Figure 15. Device Tab for Control Logix PLC
File
The File tab, as shown in Figure 16, displays the details of the EDS file. They are:
• Creation date and time.
• Modification date and time.
• File revision number of the EDS file.
9ARD000014-600 A 61
File Section 3 Device Import Wizard
Figure 16. File and Device Information - File Tab
Click View EDS File to view the contents of EDS file in the EDS Viewer, as shown
in Figure 17.
In case of performing a Modular re-import of an I/O EDS file by selecting the
adapter file alone, then View EDS File for the I/O modules is disabled, as the I/O
modules are not selected during the import process.
62 9ARD000014-600 A
Figure 17. EDS Viewer
The EDS Viewer has the following features:

• Displays the EDS file path.
• Displays the EDS file’s contents.
Go to line and Find features, which allow search operations within the content.
9ARD000014-600 A 63
13. Click Next from the File and Device Information window. The EDS file
import - Parameter Settings window is displayed as shown in Figure 18.
Figure 18. EDS file import - Parameters setting
14. Select the EDS file in the left pane. The module name of the selected EDS file
is displayed and Customize tab is enabled, in the right pane. List of parameters
is displayed in the drop-down list of the right pane as shown in Figure 18.
a. Click the Customize tab. The Parameters Edit window is displayed, as
shown in Figure 19.
64 9ARD000014-600 A
Figure 19. Parameter Edit
In the Parameter Edit window, Name and Description field shows the name of the
selected module and the description provided by the vendor in the EDS file (if
available). Under Parameter, all the defined parameters with the corresponding
settings are shown in the same order as they will later appear in the Hardware editor.
b. Double-click the values in the row to edit for columns Parameter Name,
Link Path, Data Type, Default, Link Path and Unit.
If the data type selected is bool, it is not possible to edit the values for Min and
Max. It will not be possible to change the datatype of an enumrange parameter if
it is referenced by an analog channel.
9ARD000014-600 A 65
– Right-click the Number column to open the shortcut menu. This allows to
insert a new parameter, delete a parameter, move up the parameter position
and move down the parameter position, as shown in Figure 20.
If an EDS defined parameter is deleted, the parameter appears strikeout but not
deleted, and later excluded in the generation of HWD file. Select Undelete from
the shortcut menu to restore the deleted parameter.
Figure 20. Parameter Edit window with shortcut menu
The field “Number” will show the Parameter no. of the device from EDS file.
The Parameters tab will show parameters whose values can be changed from Device
Import Wizard or from the settings tab for the device in hardware tree.
66 9ARD000014-600 A
Figure 21. Parameter Edit window
c. Enum Values box is available on the right pane when enum or enumrange
is selected from the Data Type drop-down box. The Enum Values box
contains the currently defined list of enumeration values for the parameter
selected, on the left pane under Parameter.
For enumrange parameter, Enum Values box contains Value, Text, Min,
Max, Underflow and Overflow columns.
– In Enum Values box, double-click the values in the row to edit. If invalid
values are entered, a warning message is displayed and the old value is
retained.
The Overflow value should be greater than the Max value and the Underflow
value should be less than the Min value.
9ARD000014-600 A 67
Figure 22. Enum Values
68 9ARD000014-600 A
Only two parameters are able to change in the 51 parameters.
Figure 23. EDS Parameter values
9ARD000014-600 A 69
The variants which the user can able to select the range parameters contains only
default values [0(parm1), 1(parm2), 2(parm3), 3(parm4)].
Figure 24. EDS Variants
70 9ARD000014-600 A
Figure 25. EDS Range selection
9ARD000014-600 A 71
Depending on the EDS file being imported, the “Customize” window for Parameter
settings page shall show only one tab “Parameters” or two tabs namely
“Parameters” and “Parameters configurable from Device Import Wizard”
The Parameters configurable from Device Import Wizard will show the parameters
that has to be configured from device import wizard only.
d. In the Enum Values box, right-click the row to open the shortcut menu.
This allows to insert a new value and delete a value, as shown in
Figure 26.
Figure 26. Shortcut for Enum Values
e. Click OK to save the changes in the Parameter Edit window.

15. Click Next in the EDS file import window. The I/O settings window appears
as shown in Figure 27.
72 9ARD000014-600 A
Section 3 Device Import Wizard I/O Settings
I/O Settings
The EDS file import - I/O Settings window is used to assign conversion rules for
the input and output area. Based on the conversion rule assigned for the input and
output area, the input and output channels are created.
In certain cases, the assembly definition in the respective EDS file(s), provides the
necessary information regarding creation of channels. In such cases the input and
output channels may get configured prior to entering the I/O Settings window.
The following I/O Settings window is for a DeviceNet device non-modular EDS
file. Figure 28 is an example of the I/O Settings window for a modular DeviceNet
device.
9ARD000014-600 A 73
I/O Settings Section 3 Device Import Wizard
Figure 27. I/O Settings for a DeviceNet Non-Modular System
74 9ARD000014-600 A
Figure 28. I/O Settings window for a DeviceNet Device Modular System
DeviceNet Device
The I/O Settings window has a tree view on the left pane. The tree view displays
the product names and catalog numbers depending on whether Catalog number or
Product name option is chosen, in the File and Device Information window.
Under each product name/catalog number in the tree view, one or more of the
following trigger types is/are listed:
9ARD000014-600 A 75
• Strobe - Multi-cast message starts the scan cycle. Strobe-able slaves respond,
based on their latency.
• Poll - The Master queries each sensor/actuator according to the polling list.
Polls are sent out even as strobe responses are being received, as much as
bandwidth allows.
• COS - A device reports its data only when there is a change. This is considered
more efficient since only data changes are transmitted. It can be used along
with Poll or Strobe.
• Cyclic - Devices report data on a user-configured, time-increment basis (input
or output). Cyclic data production is considered more efficient for applications
with slowly changing analog I/O.
For DeviceNet modules, avoid selecting COS and Cyclic modes simultaneously,
as this is not allowed on DeviceNet networks.
The tree view has check mark icons beside the product names/catalog numbers and
the trigger types. The color of a check mark icon indicates the following:
• Green - Indicates that the complete I/O area of this specific connection has
already been assigned to I/O channels.
• Orange - Indicates that some, but not all, of the I/O channels have been created.
I/O Setting and I/O Channel Creation

Enter the number of bytes in the Input area and Output area. This field displays
the number of bytes of I/O data available for the selected connection in the input and
output area, respectively.
The input and output area bytes are defined for each device in the respective
EDS files. The following are the supported standard conversion rules:
– 1 Byte to 8 Bool.
– 1 Byte to 1 DInt.
– 2 Byte to 1 DInt unsigned.
– 4 Byte to 1 DInt.
– 1 Byte to 1 DWord.
76 9ARD000014-600 A
– 2 Byte to 1 DWord
– 4 Byte to 1 Real.
– 1 Byte to 1 DInt signed.
– 2 Byte to 1 DInt signed.
– 2 Byte to 1 DInt unsigned + Swap.
– 2 Byte to 1 Dword + Swap.
– 4 Byte to 1 Real + Swap.
– 2 Byte to 1 DInt signed + Swap.
I/O channel creation can happen in the following ways:
• Automatic channel creation - Execute the following steps to create I/O
channels through automatic conversion:
a. Select the required connection in the tree view. The corresponding details
are displayed in the right hand section of the window.
b. Click Standard rule Byte Mapping. The EDS Byte drop-down list is
enabled.
c. Select the required conversion rule and click Apply. The I/O channels are
created.
Example for I/O channel creation using automatic conversion - If the
default input area is 4 bytes and output area is 2 bytes, and the conversion rule
selected is 1 Byte to 8 Bool, then:
4 x 8 = 32 Input channels
2 x 8 = 16 Output channels
Total 32 + 16 = 48 channels are created
9ARD000014-600 A 77
• Manual channel creation - Execute the following steps to create I/O channels
through manual conversion:
a. Select the required connection in the tree view. The corresponding details
are displayed in the right hand section of the window.
b. Enable Manual Bit Mapping. This in turn enables Customize Input and
View and Customize Output and View.
If the I/O connection has only input area, then only Customize Input and View
is enabled. If the I/O connection has only output area, then only Customize
Output and View is enabled. If the I/O connection has both input and output
area, then both buttons are enabled.
If the number of bytes, chosen as per the rule are unavailable, then the wizard
does not create any channels of the chosen data type.
c. Depending on the requirement, click Customize Input and View and/or
Customize Output and View.
After Step c, depending on whether the channels are Digital or Analog
channels, proceed to either of these:
– Customizing Input and Output for Digital Channels on page 91
– Customizing Input and Output for Analog Channels on page 94
78 9ARD000014-600 A
EtherNet/IP Device
Figure 29 shows the I/O Settings window for EtherNet/IP non-modular system.
Example of EtherNet/IP modular I/O system is shown in Figure 30.
Figure 29. EtherNet/IP Non-modular system
9ARD000014-600 A 79
Figure 30. Ethernet/IP Modular I/O system
The I/O Settings window for EtherNet/IP device displays the connections listed
under the product name/ catalog number in a tree view, on the left pane, as shown in
Figure 30. One or more of the following connections are listed:
• Exclusive Owner - If a connection has an application type of exclusive owner,
it shall not be dependent on any other connection for its existence. This
requirement exists to signal the originator of the exclusive owner connection
that the O=>T data is no longer being received by the target device.
80 9ARD000014-600 A
• Input Only- A specific implementation may limit the number of input only
connections it accepts. In addition, the target may accept listen only
connections that use the same multicast T=>O data.
• Listen Only- A target may accept multiple listen only connections which
specify the same T=>O path. Devices that wish to listen to multicast data
without providing configuration may use this application type. Is the last
connection on which a listen only connection depends is closed or times out,
the target device shall stop sending the T=>O data which will result in the
listen only connection being timed our by the originator device.
• Redundant Owner- The redundant owner connection shall allow multiple
separate originator applications to each establish an independent, identical
connection to the transport of a target application.The target transport shall in
turn send events to the target application so that the redundant owner
connection appears as a single, exclusive owner connection to the target
application.
The CI873 does not support Redundant owner connections for EtherNet/IP
devices.
To create I/O channels for an EtherNet/IP device (Modular and non-modular), refer
I/O Setting and I/O Channel Creation on page 76.
Allen Bradley Logix 5000 Series PLCs

Figure 31 shows the I/O Settings window for Allen Bradley Control Logix PLC
unit. The Class 1 and Class 3 connections can be set in the I/O Settings window.
Under each product name/catalog number in the tree view, the connections listed are
— Class 1 Connections and Class 3 Connections. Figure 31 and Figure 32 shows
the Class 1 and Class 3 connection respectively.
Tag based Class 1 connection information should be available in EDS file of the
Logix 5000 Controllers for communication with CI873.
9ARD000014-600 A 81
Figure 31. I/O Settings window for a Control Logix PLC (Class 1)
Execute the following steps to create Class 1 Connection:

a. Select the Class 1 Connections in the tree view. Corresponding details are
displayed on the right pane.
b. Follow the steps described in I/O Setting and I/O Channel Creation to set
the Class 1 connection.
82 9ARD000014-600 A
The following is an example for Class 3 connections.
Figure 32. I/O Settings window for Control Logix PLC (Class 3)
Execute the following steps to create Class 3 connection:

a. Select the Class 3 Connections in the tree view. In the right pane of the
window, Class 3 connections check box is displayed.
b. Select the Class 3 connections check box. The corresponding details are
displayed.
9ARD000014-600 A 83
c. Enter the port number in the Port Number field or select Use Default to
set the default value.
d. Under Write Tag 1, enter or select the following details:
– Service ID: Select CIP Table Write Service from the drop-down list.
This is the vendor specific CIP service to be executed to read or write the
data.
– Data Type: Select data type from the drop-down list. After data type is
selected, Configured channels window is opened as shown in Figure 35.
The data type is defined for each tag for the Class 3 connections. The
following are the supported standard data types:
– SINT
– INT
– DINT
– REAL
– BOOL
– DWORD
– USINT
– UDINT
– BYTE
– WORD
– STRUCTURE. If this data type is selected, DataSize dialog box appears
If the 64-bit data type is Dword, the data can be split into 2 Dword each of 32-bit
data type.
64 bit data of any other data type like Real and Integer is not supported.
– No. of elements: Type the number of data elements of the particular data
type, that is read or written from or to Allen Bradley PLC device.
84 9ARD000014-600 A
Figure 33. DataSize dialog box
In the Name field, enter the structure name with valid ASCII characters as
shown in Figure 33.
Under Members table, enter the name of the element of the Structure and data
type. Click in the Data type column, Select Data Type dialog box
displays as shown in Figure 34.
9ARD000014-600 A 85
Figure 34. Select Data Type dialog box.
Select the data type listed under Datatype, for example DINT, SINT, REAL, etc.
In Array Dimensions group, click the up and down arrow to select the array of
dimensions for the data type selected as shown in Figure 34.
Click OK to save the changes.
Click Apply and Ok to save the changes in the DataSize dialog box as shown in
Figure 33. The Configured channels window is opened as shown in Figure 35.
86 9ARD000014-600 A
Figure 35. Configure channels window
The Configured channel window displays the number of channels created

based on the datatype selected. The channels are editable to different datatype
as per requirement. From the Configured Channels, double-click the
Features or Data type conversion column to bring up the Frame Format
dialog box, as shown in Figure 36.
9ARD000014-600 A 87
Figure 36. Frame format dialog box
In the Frame format dialog box, specify the byte swap parameters. Select
Big endian or Little endian and click OK to save the details.
CI873 is a big-endian system. While Allen Bradley PLC is a little-endian system.
So before mapping the bytes to the channels, ensure that all the channels are
made to little-endian.
e. Click Customize tab in the I/O Settings window, configured channels
detail are displayed.
f. Click Add Write Tag tab to add new write tag to the Class 3 connection.
You can add three Write tags at a time.
88 9ARD000014-600 A
Advanced configuration for multiple channels.

Select multiple channels by clicking the channels or using keyboard shortcut
Ctrl + A. Right click and in the menu there will be an option 'Advanced
configurations'.
Irrespective of the type of the channels selected the 'Advanced configuration'
will show the 3 options to set - status bits, range parameter and frame format.
The selected settings will be applied to all the selected channels based on the
channel type.
Figure 37. Advanced Configuration
If the user selects one channel and clicks on Advanced configuration menu,
only the settings applicable to the selected channel will be shown.
User will be allowed to copy/paste using keyboard shortcuts Ctrl + C, Ctrl + V.
Copied channels will be added to the end of the available channels. If there is
no available space in the I/O area to add the channels a message will be shown
to the user. If there is some available space, then channels which fit into the
space will be added.
Copy paste channel names from excel to the channel names column is allowed.
Copy the channel names from excel. Select the channel name for which the
modification needs to be done and paste using Ctrl + V.
9ARD000014-600 A 89
The Table 13 shows some configuration examples for Class 3 communication with
Allen Bradley Logix 5000 series PLC using BOOL data type (present inside a
structure).
Table 13. Configuration Examples
Configuration in RS Logix on Allen

Configuration in Control Builder in AC 800M
Bradley Logix 5000 series controller
Less than or equal to 8 Bool variables defined in a To be configured as SINT
structure
Greater than 8 but less or equal to 32 bool To be defined as BOOL[32]
variables defined in a structure
Greater than 32 but less or equal to 64 bool To be defined as BOOL[64]
variables defined in a structure
Array of bool: BOOL[n] where n is less than or To be defined as BOOL[32]
equal to 32 defined in structure
Array of bool: BOOL[n] where n is greater than 32 To be defined as BOOL[64]
but less than or equal to 64 defined in structure
Array of bool: BOOL[n] where n is greater than 64 To be defined as BOOL[96]
but less than or equal to 96 defined in structure
Nested Structured data type (structure within a structure) is not supported.
90 9ARD000014-600 A
Customizing Input and Output for Digital Channels

Click Customize Input and View from the I/O Settings screen. This brings up the
Input Area Configuration screen, as shown in Figure 38,where the input area can be
assigned to input channels.
Figure 38. Input Area Configuration for Poll trigger type

(Digital Input Channels - Non Modular Import)
The Customize Input and View I/O Area Configuration screen has two panes -
Input area and Configured channels.
The Input Area section displays the I/O channels available for the selected
connection. For example, if the connection has 4 bytes of input area, then 4 rows of
channel slots are displayed with bits. I/O channels are created based on the number
of bytes defined for each connection in the EDS file.
The Configured Channels tabular section has following details of the I/O channels
defined:
9ARD000014-600 A 91
• Byte, bit - Displays the starting byte and bit of the I/O channel.
• Length - Displays the number of bits for each I/O channel.
• Name - Displays the name of each I/O channel.
• Data type conversion - Displays the channel’s data type and the corresponding
copy routine function which is generated in the hardware definition file for
each I/O channel.
• Features - Displays the specific features or properties of the I/O channel.
The byte swapping feature is available for specific copy functions only.
From the Input Area Configuration, in digital channels, double-click the Features
or Data type conversion column to bring up the Advanced Settings window, 
Figure 39. Advanced Settings with Status for a digital input channel
From the Advanced Settings dialog box, specify the Status parameters in the Input
Area tab. Click to select the number of bits to indicate channel status. For details on
92 9ARD000014-600 A
specifying the Status Parameters for a channel, refer Specifying Status and Signal
Range Parameters for Channels on page 98.
For customizing the output area, click Customize Output and View from the I/O
Settings screen. This brings up the Output Area Configuration screen, as shown in
Figure 40,where the output area can be assigned to output channels.
Figure 40. Output Area Configuration for Poll trigger type

(Digital Output Channels - Non Modular Import)
Operate the Output Area Configuration screen in the same manner as the Input Area
Configuration screen. The advanced feature option for boolean/digital output
channels is not available.
9ARD000014-600 A 93
Customizing Input and Output for Analog Channels

During manual creation of channels, the drop-down rules for analog channels are
similar to those for digital channels. Choose the rule as Real Datatype during
manual creation for analog channels.
Click Customize Input and View from the I/O Settings screen. This brings up the
Input Area Configuration screen, where the input area can be assigned to input
channels. The Input Area Configuration screen for analog channels has the same
features as the one for digital channels. Figure 41 shows the Input Area
Configuration screen.
Figure 41. Input Area Configuration for Poll trigger type

(Analog Input Channel - Modular I/O Import)
From the Input Area Configuration screen, double-click the Features or Data type
conversion column to bring up the Advanced Settings window, as shown in
Figure 42.
94 9ARD000014-600 A
Figure 42. Advanced Settings for an Analog Input channel
The Advanced Settings window for analog input channels support Status Parameter
and Signal Range Parameter selection. To specify the Status Parameters, click and
select the number of bits to indicate channel status. The Signal Range Parameters
appears as drop-down list in the Range Parameter tab of the Advanced Settings
window.
For details on specifying the Status and Signal Range Parameters for a channel,
refer Specifying Status and Signal Range Parameters for Channels on page 98.
For customizing the output area, click Customize Output and View from the I/O
Settings screen. This brings up the Output Area Configuration screen, as shown in
Figure 43, where the output area can be assigned to the output channels.
9ARD000014-600 A 95
Figure 43. Output Area Configuration for Poll trigger type

(Analog Output Channels - Modular I/O Import)
From the Output Area Configuration screen, double-click the Features or Data
type conversion column to bring up the Advanced Settings window, as shown in
Figure 44.
The Output Area Configuration’s Advanced Settings window supports only Signal
Range Parameter selection. There is no support for Status for output channels. For
details on specifying the Signal Range Parameters for a channel, refer Specifying
Status and Signal Range Parameters for Channels on page 98.
96 9ARD000014-600 A
Figure 44. Advanced Settings for an Analog Output channel
Scaling for DeviceNet Devices

Scaling is handled in the following ways for DeviceNet devices:
• For each of the trigger type that is supported by the device, the assembly being
referenced in the input/output area is scanned for the presence of scaling
parameter.
• The information of the scanned parameter is then used as the scaling parameter
for all the channels that are created from that particular assembly.
• The scaling is done for both the input and output channels.
9ARD000014-600 A 97
Scaling for EtherNet/IP Devices

Scaling is handled in the following ways for EtherNet/IP devices:
• The assembly being referenced in the connection manager is for the O->T and
T->O is scanned for the presence of the scaling parameter.
• The information of the scanned parameter is then used as the scaling parameter
for all the channels that are created from that particular assembly.
• The scaling is done for both the input and output channels.
Specifying Status and Signal Range Parameters for Channels

The Status parameters and Signal Range parameters are set in the Advanced settings
with status window, while configuring input and output areas for analog and digital
channels.
For digital channels, only Status parameters can be defined. For analog channels
input area configuration, both Status and Signal Range parameters can be defined.
For analog channels output area configuration, only Signal Range parameters can be
defined.
Status Parameter
Status Parameter is set by defining a status bit for a channel. This status bit indicates
the status of the channel – whether the channel data is in correct or in corrupted
state. The status bit hence determines whether or not the channel data is fit to be
transferred from the controller to the application.
For a particular connection type, select the status bit for a parameter from the
available input/output bits only. Select the status bit for a particular channel
according to the instructions present in the Device manual. If a bit is selected as a
status bit for a particular channel, then the bit cannot be used again for channel data
in the same connection type. The bits selected as status bits cannot be assigned
again to other channels either. Refer the following example for better understanding.
Assume there is 1byte to indicate a connection. This means that there are only 8 bits
to both define the channels and specify the status of those channels. In such a case,
for 1Byte of data the status bits can be set as illustrated in Figure 45.
98 9ARD000014-600 A
Figure 45. Sample allocation of Status bits and Data bits for a channel
Select any of the bits displayed as the status bit for any particular channel. As seen
in Figure 45, the 0th bit channel has the status parameter as 7th bit and 1st bit
channel has the status parameter as 6th bit and so on. This means that the 7th bit
determines the availability of the 0th bit, and the 1st bit determines the availability
of the 6th bit, and so on. Here the bits 4,5,6,7 cannot be used for channel data.
The example provided for setting up the Status parameters is generic and for
illustration only. Before setting up the Status parameters for a particular device,
refer the device's manual provided by the device vendor.
Signal Range Parameter

The Signal Range parameter is defined by selecting a suitable range from the Range
Parameter drop-down list box. The list contains possible signal ranges, each of
which have pre-defined minimum and maximum values specified in the
corresponding HWD file.
9ARD000014-600 A 99
Deleting I/O Channels

Steps to delete I/O channels are:
a. Right-click the selected entries in the Configured Channels section. To
delete the I/O channel, select Delete from the context menu.
b. The I/O channel slots become empty in the left side pane.
Modifying I/O Channels

Steps to modify I/O channel details are:
a. Double-click the entry in the Configured Channels section. The Byte, bit,
length and the Name fields become editable.
b. Select OK.
Recreating I/O Channels

Steps to recreate I/O channels are:
a. Select an empty bit to create a single I/O channel.
b. Select the required number of I/O channels by running the mouse pointer
up or down.
c. Select the blue triangle to select an entire byte.
d. On performing any of the above mentioned steps, a context menu is
displayed with the permissible copy functions.
e. Select the required copy function. The I/O channels are assigned to the
selected copy function. The assignment is represented by colors.
f. Select the bits that have to indicate a status for a particular channel. This
provides the status reference and status mask to be used in the selected
copy function.
100 9ARD000014-600 A
16. Click Next from the I/O settings window. The Device Import Wizard screen
appears with a Comment section as shown in Figure 46.
Figure 46. Device Import Wizard Comment Dialog
In the Comment section, edit or add required comments as required. These

comments appear in the HWD file.
17. Click Next in the Comment section of the Device Import Wizard window
and view the results of the conversion, as shown in Figure 47.
9ARD000014-600 A 101
Figure 47. Conversion Results
Conversion results section lists warnings or minor errors which may have
occurred during file conversion/import. For instance, illegal characters
(characters that do not fall within the 0-127 ASCI range) are replaced with an
underscore, and the HWD file is created.
Click View/Print HWD to view and print the generated HWD file.
18. Click Finish to exit the Device Import Wizard. The *.hwd file is added in the
hardware library.
For details on re-import scenarios, refer to Re-import on page 168.
In case the configuration imported for EDS file is not correct, the hardware type
should not be deleted from the hardware library, after it has been created by
importing an EDS file in Control Builder.
Instead, to correct the configuration, re-import the EDS file in the same hardware
library, or create a new hardware library and import the EDS file under it.
102 9ARD000014-600 A
Section 4 Configuration
Introduction
The Configuration section contains the configurations to be made from Control
Builder when setting up EtherNet/IP and DeviceNet networks.
Hardware Libraries
Hardware libraries are required for configuring CI873 and the hardware types of
EtherNet/IP and DeviceNet devices.
Insert the hardware library CI873EthernetHwLib in the project and add it under
Connected Libraries in the Controller in Control Builder.
For more information about handling hardware libraries, refer to System 800xA
Control, AC 800M Configuration (3BSE035980*).
CI873 Hardware units

The CI873EthernetIPHWLib contains the hardware units for CI873, Linking Device
and their diagnostics.
The EtherNet/IP and DeviceNet devices need to be inserted in under CI873 in

hardware tree. Before importing the EDS files of EtherNet/IP, DeviceNet, I/O
devices, user has to create new hardware library, if not exist, and then import the
EDS files into user created hardware library. Once the EDS file import is
successful then the hardware units for corresponding devices are created in the
user created library.
9ARD000014-600 A 103
CI873 Hardware units Section 4 Configuration
The Table 14 below lists all the hardware units which can be configured in Control
Builder under CI873.
Table 14. Table showing all the Hardware units
Hardware
Device Status
Position (Root. Has IO
Name Description Icon Reported to
Allowed Channels
User
position)
CI873 Communication PM, Yes No
Interface for Pos:1-12
EtherNet/IP
CI873 Diagnostics of CI873, No Yes
Scanner CI873 Pos: 254
Diagnostics EtherNet/IP
Scanner
LD800DN Linking Device CI873, Yes No
for DeviceNet Pos: 1-253 but
devices max of 4
Instances
LD800DN Diagnostics of LD800DN, No Yes
Diagnostics LD800DN Pos: 64
EtherNet/IP See Note (2) CI873, Yes Yes
Devices (1) Pos: 1-253
DeviceNet See Note (2) LD800DN, Yes Yes
Device (1) Pos : 1-63
EtherNet/IP See Note (2) CI873, Yes No
Modular Pos: 1-253
Adapter (1)
104 9ARD000014-600 A
Section 4 Configuration CI873 Hardware units
Table 14. Table showing all the Hardware units
Hardware
Device Status
Allowed Channels
User
position)
DeviceNet See Note (2) LD800DN, Yes Yes
Modular Pos: 1-63
Adapter (1)
I/O Module See Note (2) Modular Adapter, Yes Yes
(1)
Pos: 1-253
(1) The name of the hardware unit for devices is taken from the 'Product Name' field in the Device section of the
corresponding EDS file. Also note that user has the possibility to change the product name during Importing of
EDS file.
(2) The description for the Devices is a string containing values of fields 'Vendor ID', 'Device Type', 'Product Code',
'Major Revision', 'Minor Revision' under Device section of the corresponding EDS file.
As shown in the above Table 14, total number of DeviceNet devices is limited to 63
in compliance with the DeviceNet standard. These 63 devices include both non
modular and modular DeviceNet devices which can be connected directly under
Linking Device.
9ARD000014-600 A 105
S200 Hardware Units Section 4 Configuration
S200 Hardware Units

The S200IOCI873HwLib contains the hardware units for S200 I/O modules and
their diagnostics.
The Table 15 below lists the S200 I/O modules which can be configured in Control
Builder under CI873 and 200-AENTR.
Table 15. Table showing S200 Hardware units
Hardware
Device Status
Allowed Channels
User
Position)
200-AENTR EtherNet/IP CI873, Yes No
adapter for Pos: 1-253 but
S200 IO max of 30
modules Instances
S200 I/O 200 - I/O 200-AENTR Yes Yes
Module module Pos:1-8
S200 I/O 200C and 200-AENTR Yes Yes
Module 200L I/O Pos:1-8
module
106 9ARD000014-600 A
Section 4 Configuration Adding CI873
Adding CI873
This section describes about inserting of CI873 and configuring of CI873.
Inserting CI873 EtherNet/IP Communication Interface Unit

Follow these steps to insert a new CI873 EtherNet/IP communication interface unit:
1. In the Control Builder hardware tree, right-click the AC 800M controller to add
a new CI873, and select Insert Unit. The Insert Unit window appears as
shown in Figure 48.
Figure 48. Insert Unit Window
2. Expand the CI873 library under Connected Libraries and select the CI873
hardware type.
9ARD000014-600 A 107
Configuring CI873 EtherNet/IP Communication Interface Unit Section 4 Configuration
3. In the right side pane, select a position for the hardware unit in the Position
drop-down list. The first available position is chosen by default.
4. Click Insert to apply the changes. Repeat previous steps to insert further units.
5. Click Close to close the Insert window. The unit(s) are included in the
hardware tree.
It is possible to connect up to four CI873 under one AC 800M.
Configuring CI873 EtherNet/IP Communication Interface Unit

For configuring the CI873 EtherNet/IP Communication Interface Unit, in the
hardware tree double-click CI873 or right-click and select Editor from the context
menu. This opens the Hardware Editor, as shown in Figure 49.
Figure 49. Hardware Editor – Settings for CI873
The Hardware Editor contains three tabs — Settings, Connections and Unit Status.
The parameters for configuring the CI873 EtherNet/IP Communication Interface
Unit are found in the Settings tab. Configure the parameters according to the
description of parameters given in Table 16.
108 9ARD000014-600 A
Section 4 Configuration Adding LD 800DN Linking Device Unit
Table 16. Settings for CI873 EtherNet/IP Communication Interface Unit
Parameter Default Value Description Consequence of Change

Configured 192.168.0.3 IP address of CI873 CI873 closes all the CIP
Primary IP when configured in connections configured
address single or the IP address and re-establishes with the
of Primary when new IP address.
configured in
redundant.
Configured 192.168.0.30 IP address of Backup CI873 re-configures its
Backup IP CI873 when configured Ethernet interface with the
address in redundant. new IP address.
Subnet Mask 255.255.255.0 Net mask Communication with all the
devices stops. Connection
will be re-established, then
the communication
resumes.
Adding LD 800DN Linking Device Unit

This section describes how to insert and configure LD 800DN linking device unit in
Control Builder.
Inserting LD 800DN Linking Device Unit

For inserting a new LD 800DN Linking Device Unit in the hardware tree, follow
these steps:
1. Right-click the CI873 and select Insert Unit. The Insert Unit window appears
9ARD000014-600 A 109
Configuring LD 800DN Linking Device Unit Section 4 Configuration
Figure 50. Inserting an LD 800DN Linking Device Unit
2. Under Connected Libraries, expand the library for CI873 and select the
LD 800DN hardware type.
3. Select a position for the hardware unit in the Position drop-down list. The first
available position is chosen by default.
4. Click Insert to apply the current changes. Repeat previous steps to insert
further units.
5. Click Close to close the Insert window. The unit(s) are included in the
hardware tree.
Configuring LD 800DN Linking Device Unit

For configuring an LD 800DN Linking Device Unit, in the hardware tree double-
click LD 800DN or right-click and select Editor from the context menu. This opens
the Hardware Editor, as shown in Figure 51.
110 9ARD000014-600 A
Section 4 Configuration Configuring LD 800DN Linking Device Unit
Figure 51. Hardware Editor – Settings for LD 800DN
The parameters for configuring the LD 800DN Linking Device Unit are found in the
Settings tab. Configure the parameters according to the description of parameters
given in Table 17.
9ARD000014-600 A 111
Table 17. Settings for LD 800DN Linking Device Unit
Editable
Parameter Data Type Unit Min Max /Read Description
Only
Vendor ID INT - - - Read ABB vendor Identification number.
Only
Product INT - - - Read Device Type to identify the device
Type Only profile of LD 800DN as
Communication adapter
device(0x0C).
Product INT - - - Read Identification number for the linking
Code Only device within the communication
adapter profile of adapter.
Major INT - - - Read Major revision of the linking device.
Revision Only
Minor INT - - - Read Minor revision of the linking device.
Revision Only
Electronic 0 1 Editable Criteria that can be specified by user
Key for LD 800DN to accept connection
VendorID from CI873 only when Vendor ID of
LD 800DN configured in Control
Builder matches with the Vendor ID of
LD 800DN device in the network.
Values are:
Enable Keying, Disable Keying
Upon modification, connection
between LD 800DN and CI873 gets
disconnected and connected again.
Hence communication with
DeviceNet slaves stop momentarily.
112 9ARD000014-600 A
Table 17. Settings for LD 800DN Linking Device Unit (Continued)
Editable
Only
Electronic Enum 0 1 Editable Criteria that can be specified by user
Key Product for LD 800DN to accept connection
Type from CI873 only when Product Type
of LD 800DN configured in Control
Builder matches with the Product
Type of LD 800DN device in the
network.
Values are:
DeviceNet slaves stop momentarily
Key Product for LD 800DN to accept connection
Code from CI873 only when Product code
code of LD 800DN device in the
network.
Values are:
9ARD000014-600 A 113
Editable
Only
Key Major for LD 800DN to accept connection
Revision from CI873 only when major revision
Builder matches or is greater than the
major revision of LD 800DN device in
the network.
Values are:
Disable Keying, Exact Match,
Current and Higher
IP String - - - Editable The IP address of the linking device
Address(1) LD 800DN in the network. It must be
an IP address on the same subnet as
where the CI873 is placed.
If the IP address is blank, then first
three fields are taken from its parent
CI873 IP address and the fourth is
taken from its hardware tree position.
Upon modification, connection of
CI873 with the Linking Device is
reestablished.
114 9ARD000014-600 A
Editable
Only
EtherNet Enum 0 4 Editable Speed and Duplex of the Ethernet
Speed and Port of Linking Device which are used
Duplex for its communication over the
EtherNet network.
Values are:
100Mbps Full Duplex,
100Mbps Half Duplex,
10Mbps Full Duplex,
10Mbps Half Duplex,
Auto Negotiation.
Upon modification, communication
with the Linking Device is stopped,
and resumes after the Linking Device
is reconfigured with the new value.
MAC ID(2) INT - 0 63 Editable The network address that the
LD 800DN uses on the DeviceNet
network.
Upon modification, communication
with the Linking Device and
DeviceNet devices is stopped and
resumes once the Linking Device is
configured with the new MAC ID.
The default value is 0 (zero)
9ARD000014-600 A 115
Editable
Only
Baud Rate ENUM kbps 0 3 Editable The baud rate of the DeviceNet
network.
Values are:
125kbps, 250kbps, 500kbps.
Upon modification, Communication
with all DeviceNet devices stops.
Communication resumes after the
connection is re-established.
The modification of the Baud Rate
does not take effect until the device is
power cycled.
Inter Scan INT ms 2 9000 Editable The time delay between successive
Delay4 scan cycles following the last polled
message.
Upon modification, communication of
linking device with all DeviceNet
devices is stopped momentarily.
The default value is 25ms.
Expected INT - 10 32000 Editable The rate at which DeviceNet master
Packet Rate (Linking Device) expects the data to
be received. Applicable only for poll
and strobe type of connections.
The value is unit less and must be
multiplied with 4 to determine the
value in milliseconds
The default value is 75.
116 9ARD000014-600 A
Editable
Only
Foreground Dint ms 1 32000 Editable Ratio of foreground to background
to poll. If configured to poll at the
Background background rate, then, this parameter
Poll Ratio sets the rate at which it's polled with
respect to scan cycle. This is valid
only for Poll.
The default value is 3.
(3)
ADR Dint - - - Editable For setting Automatic Device
Recovery. It is enabled by default.
Enabling/disabling of ADR feature, in
turn automatically enables/disables
the Address Recovery feature.
I/O Enum - 0 0 Read The trigger type of the I/O
Connection Only connection.
- Trigger LD 800DN supports cyclic trigger
type only.
9ARD000014-600 A 117
Editable
Only
I/O Dint ms 10 500 Editable Requested Packet Interval in
Connection- milliseconds for O -> T packets. The
O -> T RPI value is used to allocate bandwidth at
each of the producing nodes (CI873)
CI873 re-establishes the connection
with the Linking Device. The
bandwidth is allotted to the new value
by the CI873. The default value is
10ms.
CI873 with all DeviceNet devices is
stopped till the connection is re-
established.
I/O Dint ms 10 500 Editable Requested Packet Interval in
Connection milliseconds for T -> O packets
- T -> O RPI Measures how frequently CI873
requires the transmission of data
from the linking device. The default
value is 10ms.
Upon modification, CI873
re-establishes the connection with
linking device. Communication of
CI873 with all DeviceNet devices is
stopped till the connection is 
re-established.
118 9ARD000014-600 A
Editable
Only
I/O Dint 0 500 Read The consuming connection size for
Connection Only I/O connection.
- O -> T Size Number of bytes of data that gets
transferred from Originator (CI873) to
Target (LD 800DN) over the I/O
connection.
I/O Dint 0 500 Read The producing connection size for I/O
Connection Only connection.
- T -> O Size Number of bytes of data that gets
transferred from Target (LD 800DN)
to Originator (CI873) over the I/O
connection.
(1) If the IP Address parameter is left blank, then it is evaluated from the LD 800DN’s position in the hardware tree along
with the IP address of its CI873 parent unit. The first three octets are taken from the parent unit and last octet from
the hardware tree position.
If the IP address was already set using the BridgeWay Configuration tool, then the same value needs to be put in
here. If it's left blank, the LD 800DN needs to inserted at the position equal to the last byte of this IP address. If the
IP address updated into this parameter doesn't match the actual IP address set to the linking device, then no
communication happens. The unit status shows the error 'Device not found'.
(2) The MAC ID set for the LD 800DN using the BridgeWay Configuration tool needs to be entered here. If the MAC ID
entered here is different, then communication does not happen.
(3) For more details on the ADR feature, refer Automatic Device Recovery on page 210.
The LD 800DN may not detect hot insertion of a device at MAC ID 63, even
when Automatic Device Recovery is enabled. Consider a case, where two
identical DeviceNet devices configured at different MAC ID positions, for
example, 1 and 2 are removed and one of them is inserted back at MAC ID
position 63. Here, the LD 800DN may not detect the device. The status of the
inserted DeviceNet device will be seen as DeviceNotFound.
9ARD000014-600 A 119
LD 800DN Timing Parameters

A direct correlation exists between the following LD 800DN timing parameters:
• Foreground to Background Poll Ratio.
• Inter Scan Delay and their corresponding Expected Packet Rate value.
The following conditions need to be satisfied for a successful communication in
DeviceNet devices:
• If the Strobe connection is enabled or the Polled connection is enabled with
Poll Type set as Poll Every Scan Cycle, then
((Inter Scan Delay) <= (Expected Packet Rate))
• If the Polled connection is enabled with Poll Type set as Poll At Background
Rate, then
((Foreground to Background Poll Ratio * Inter Scan
Delay) <= (Expected Packet Rate)
The Control Builder checks the above correlation between the parameters based on
the connections enabled on the DeviceNet devices. The download is aborted with an
error message if the conditions are not satisfied.
120 9ARD000014-600 A
Section 4 Configuration Adding DeviceNet Slave Device Unit
Adding DeviceNet Slave Device Unit

This section describes how to insert and configure DeviceNet devices in Control
Builder.
Inserting DeviceNet Slave Device Unit

Certain DeviceNet slave devices require custom software utilities, provided by their
vendors, to configure them. Refer to the respective device manual to configure them
properly before using them with CI873 for communication.
Follow these steps for inserting a DeviceNet Slave Device Unit in the hardware tree:
1. Right-click the LD 800DN and select Insert Unit. The Insert Unit window
Figure 52. Inserting a DeviceNet Slave Device
9ARD000014-600 A 121
Configuring a DeviceNet Slave Device Unit Section 4 Configuration
2. Under Connected Libraries, expand the user created library and select the
DeviceNet device hardware type. Refer Converting an EDS File to a Hardware
Unit Type on page 49, for importing a DeviceNet EDS file into the hardware
unit type using the Device Import Wizard.
3. In the Position drop-down list, select a position which is equal the hardware
unit’s MAC ID. The first available position is chosen by default.
If the MAC ID of a DeviceNet slave in the network is x then, it must be inserted
under the linking device at position x, otherwise communication between the
linking device and the DeviceNet slave is not possible.
4. Click Insert to apply the changes made. Repeat previous steps to insert further
units.
5. Click Close to close the dialog box.
When adding/deleting an I/O module or changing the position of an I/O module,
under a DeviceNet adaptor, first make such additions/deletions and position
changes using the device specific tool. This should be done before making the
corresponding changes in the Control Builder and downloading the changes to
the controller.
Configuring a DeviceNet Slave Device Unit

For configuring a DeviceNet slave device unit, in the hardware tree double-click
DeviceNet or right-click and select Editor from the context menu. This opens the
Hardware Editor as shown in Figure 53.
The configuration parameters of a DeviceNet device appear in the Hardware Editor.
It is directly taken from the EDS file provided by the device vendor. For details on
device configuration parameters from the EDS file, refer Section 3, Device Import
Wizard.
Apart from the device configuration parameters from the EDS file, there are four
more sets of parameters available in the hardware editor for every DeviceNet slave
unit. These are:
• Device Identification Parameters.
• Electronic Key Parameters.
122 9ARD000014-600 A
Section 4 Configuration Configuring a DeviceNet Slave Device Unit
• Communication Related Parameters.

• Configuration Recovery Parameter.
When a DeviceNet device configured in Control Builder does not match with the
DeviceNet device available in the network, the device status shown in Control
Builder is I/O Connection Error and not Wrong Device Type.
Figure 53. Hardware Editor – Settings for a DeviceNet slave unit
9ARD000014-600 A 123
Device Identification Parameters Section 4 Configuration
Device Identification Parameters

These are parameters showing the identity of the slave device. They appear as Read
Only and cannot be modified. They are:
• Vendor ID
• Product Type
• Product Code
• Major Revision
• Minor Revision
Electronic Key Parameters

A linking device identifies a DeviceNet slave device by its electronic key
parameters, before communicating with it. With these set of parameters, it is
possible for user to specify the DeviceNet device identity criteria that the linking
device should use before communicating with them.
Set the four Electronic Key Parameters based on their descriptions given in
Table 18. All parameters are user editable. Upon modification of any of the
parameters, the connection between LD 800DN and the DeviceNet slaves
configured under it, stops momentarily.
124 9ARD000014-600 A
Section 4 Configuration Communication Related Parameters
Table 18. Electronic Key Parameters
Default Data
Parameter Description
Value Type
Electronic Key Disable Enum When enabled, there will be a check to see if the
VendorID Keying Vendor ID of the configured slave in Control Builder
matches with that of the device in the network, before
connection establishment.
Values are: Enable Keying, Disable Keying
Product Type Keying Product Type of the configured slave in Control Builder
Product Code Keying Product Code of the configured slave in Control Builder
Electronic Key Disable Enum When enabled, there will be a check to see if Major
Major Keying Revision of the configured slave in Control Builder
Revision matches or is higher than that of the device in the
network before connection establishment.
Values are: Disable Keying, Exact Match,
Current and Higher
Communication Related Parameters

Communication related parameters have a bearing on the communication between
the DeviceNet device and the linking device LD 800DN. The communication
related parameters depend on the type of connection trigger types supported by the
slave device. The four possible connection types that can be supported by a device
are:
• Poll Connection (see Poll Connection on page 126)
9ARD000014-600 A 125
Communication Related Parameters Section 4 Configuration
• Change Of State (COS) Connection (see COS Connection on page 127)

• Strobe Connection (see Strobe Connection on page 128)
• Cyclic Connection (see Cyclic Connection on page 129)
The communication between CI873 and LD800DN work properly when the
CI873 is flooded with
- Ethernet /ARP/IP/ICMP/TCP packets at the rate less than 9Mbps (13500
packets/sec).
- UDP packets @rate less than 4500 packets/sec.
Poll Connection
The Poll Connection parameters in the hardware editor are described in Table 19.
Upon modification of editable parameters, the connection between LD 800DN and
all DeviceNet slaves configured under it, stops momentarily.
Table 19. Poll Connection Parameters
Read
Data
Parameter Default Value Only / Description
Type
Editable
Poll Type Poll every scan Enum Editable Poll the DeviceNet slave every scan or less
cycle. frequently at a background rate.
Values are: Poll every scan cycle,
Poll at background rate.
Poll Depends on the Enum Editable Enable or disable the connection. If
Connection device support enabled, linking device communicates with
Enabled as stated in the the device over the Poll connection.
EDS file. Values are: Enabled and Disabled.
126 9ARD000014-600 A
Table 19. Poll Connection Parameters
Read
Data
Parameter Default Value Only / Description
Type
Editable
Conn Poll Depends on the Int Read Number of bytes of data that gets
InputSize device support Only transferred from the device to the linking
as stated in its device over the Poll connection.
EDS file
Conn Poll Depends on the Int Read Number of bytes of data that gets
OutputSize device support Only transferred from linking device to the device
as stated in its over the Poll connection.
EDS file
COS Connection
The Change Of State (COS) Connection parameters in the hardware editor are
described in Table 20. Upon modification of the editable parameters, the connection
between LD 800DN and all DeviceNet slaves configured under it stops
momentarily.
Table 20. COS Connection Parameters
Default Read Only/

Parameter Type Description
Value Editable
Acknowledge 16 ms Dint Editable It is the amount of time that a producing node
time (for example - DeviceNet slave) waits for an
acknowledgement (ACK) from the consuming
node (linking device LD 800DN) before it re-sends
the data.
Heart Beat 250 ms Int Editable It is the background production interval for the
change-of-state connection. It is the rate at which
the device produces the data, even if the data has
not changed.
9ARD000014-600 A 127
Table 20. COS Connection Parameters (Continued)
Default Read Only/

Parameter Type Description
Value Editable
Inhibit Time 1 ms Int Editable This is the new data production inhibit time. This is
the rate at which the slave produces the data even
if it has a new value before this time.
COS Depends Enum Editable Enable or disable the connection. If enabled,
Connection on the linking device communicates with the device over
Enabled device the COS connection
support Values are: Enabled and Disabled.
as stated
in its
EDS file.
Conn COS Depends Int Read Only Number of bytes of data that gets transferred from
InputSize on the the device to the linking device over the COS
device connection.
support
as stated
in its
EDS file.
Conn COS Depends Int Read Only Number of bytes of data that gets transferred from
OutputSize on the linking device to the device over the COS
device connection.
support
as stated
in its
EDS file.
Strobe Connection
The Strobe Connection parameters in the hardware editor are described in Table 21.
128 9ARD000014-600 A
Table 21. Strobe Connection Parameters
Data Read Only /

Parameter Default Value Description
Type Editable
Strobe Depends on Enum Editable Enable or disable the connection. If
Connection the device enabled, linking device communicates
Enabled support as with the device over the Strobe
stated in its connection
EDS file. Values are: Enabled and Disabled.
Conn Strobe Depends on Int Read Only Number of bytes of data that gets
InputSize the device transferred from the device to the linking
support as device, over the Strobe connection.
stated in its
EDS file.
Conn Strobe Depends on Int Read Only Number of bytes of data that gets
OutputSize the device transferred from linking device to the
support as device, over the Strobe connection.
stated in its
EDS file.
Cyclic Connection
The Cyclic Connection parameters in the hardware editor are described in Table 22.
9ARD000014-600 A 129
Table 22. Cyclic Connection Parameters
Default Data Read Only /

Value Type Editable
Acknowledge 16 Int Editable It is the amount of time that a producing
time node (a DeviceNet slave) waits for an
acknowledgement from the consuming node
(a linking device LD 800DN) before it re-
sends the data.
Send Rate 1000 ms Int Editable This is the background production interval
for cyclic connection. If 1000ms is the Send
Rate, then the device cyclically produces
data every 1000ms.
Inhibit time 1 ms Int Editable This is the new data production inhibit time.
If it is set as 1ms, then the slave produces
the data after every 1ms, even if it has new
data ready before this time elapses.
Cyclic Depends Enum Editable Enable or disable the connection. If enabled,
Connection on the linking device communicates with the device
Enabled device over the Cyclic connection
support Values are: Enabled and Disabled.
as stated
in its EDS
file
130 9ARD000014-600 A
Section 4 Configuration Configuration Recovery Parameter
Table 22. Cyclic Connection Parameters (Continued)
Default Data Read Only /

Value Type Editable
Conn Cyclic Depends Int Read Only Number of bytes of data that gets
InputSize on the transferred from the device to the linking
device device over the Cyclic connection.
support
as stated
in its EDS
file
Conn Cyclic Depends Int Read Only Number of bytes of data that gets
OutputSize on the transferred from linking device to the device
device over the Cyclic connection.
support
as stated
in its EDS
file
Configuration Recovery Parameter

The Config Recovery parameter allows users to explicitly enable or disable the
Configuration Recovery feature for each DeviceNet slave unit. This parameter
appears in the hardware editor of every DeviceNet slave unit.
Refer Automatic Device Recovery on page 210, to know more about Configuration
Recovery.
9ARD000014-600 A 131
Adding EtherNet/IP Device Section 4 Configuration
Adding EtherNet/IP Device

This section describes how to insert and configure EtherNet/IP device and Allen
Bradley Control Logix PLC units, in Control Builder.
Setting IP Address to an EtherNet/IP Device

For setting IP address, you can use some or all of these tools:
1. Assign the IP address of EtherNet/IP device by using thumb wheel switch,
jumper switch, or dip switch that is available with the device.
2. Assign the IP address as per vendor specific tool.
If already an EtherNet/IP device is assigned with an IP address, Need to reboot
the device by assigning the thumb wheel switch to 888 and then change back the
switch settings to 999.
132 9ARD000014-600 A
Section 4 Configuration Inserting EtherNet/IP Device unit
Inserting EtherNet/IP Device unit

EtherNet/IP devices can be added under the CI873 module in the hardware tree.
Follow these steps to insert a new EtherNet/IP Device:
1. Right-click CI873 to insert the EtherNet/IP Device and select Insert Unit. The
Insert Unit dialog is displayed as shown in Figure 54.
Figure 54. Inserting EtherNet/IP Device
While inserting the Non modular EtherNet/IP Device under CI873, it can be
inserted at any position between 1-253 if the IP address is provided in the device
setting tab or it has be inserted at a position corresponding to last byte of IP
address for the device. For example, if IP Address is 10.140.201.139 then insert it
at position 139 as shown in Figure 54.
2. Expand the library for CI873 under AC 800M and select the CI873 hardware
type.
3. Select a position from the drop-down for the hardware unit as shown in
Figure 54.
4. Click Insert to apply the changes.
5. Click Close to close the dialog box. The hardware unit is included in the
hardware tree as shown in Figure 55.
9ARD000014-600 A 133
Inserting EtherNet/IP Device unit Section 4 Configuration
Figure 55. Inserted EtherNet/IP Device
134 9ARD000014-600 A
Section 4 Configuration Configuring EtherNet/IP Device
Configuring EtherNet/IP Device

For configuring the EtherNet/IP Device Unit, in the hardware tree double-click
EtherNet/IP device unit or right-click and select Editor from the context menu.
This opens the Hardware Editor, as shown in Figure 56.
The following example shows the Settings tab of EtherNet/IP device with Class 1
Exclusive Owner connection. This is based on the EtherNet/IP EDS file selected
during converting the EDS file into hardware unit types through Device Import
Wizard. The configuration parameters of an EtherNet/IP device appear in the
Hardware Editor. It is directly taken from the EDS file provided by the device
vendor. For details on device configuration parameters from the EDS file, refer
Section 3, Device Import Wizard.
9ARD000014-600 A 135
Configuring EtherNet/IP Device Section 4 Configuration
Figure 56. Hardware Editor – Settings for EtherNet/IP device
136 9ARD000014-600 A
The parameters for configuring the EtherNet/IP device are found in the Settings tab.
Configure the parameters according to the description of parameters given in
Table 23.
Table 23. Settings for EtherNet/IP Device Unit
Editable
Only
Vendor ID Dint - - - Read ABB vendor Identification number.
Only
Product Dint - - - Read Device Type to identify the device
Type Only profile of Ethernet/IP as
Communication adapter
device(0x0C).
Product Dint - - - Read Identification number for the
Code Only EtherNet/IP device within the
communication adapter profile of
adapter.
Major Dint - - - Read Major revision of the EtherNet/IP
Revision Only device.
Minor Dint - - - Read Minor revision of the EtherNet/IP
Revision Only device.
Key for EtherNet/IP to accept connection
VendorID from CI873 only when Vendor ID of
EtherNet/IP configured in Control
Builder matches with the Vendor ID of
EtherNet/IP device in the network.
Values are:
Enable Keying, Disable Keying
between EtherNet/IP and CI873 gets
9ARD000014-600 A 137
Table 23. Settings for EtherNet/IP Device Unit (Continued)
Editable
Only
Electronic Enum - 0 1 Editable Criteria that can be specified by user
Key Product for EtherNet/IP to accept connection
Type from CI873 only when Product Type
of EtherNet/IP configured in Control
Type of EtherNet/IP device in the
network.
Values are:
Key Product for EtherNet/IP to accept connection
Code from CI873 only when Product code
code of EtherNet/IP device in the
network.
Values are:
138 9ARD000014-600 A
Editable
Only
Key Major for EtherNet/IP to accept connection
Revision from CI873 only when major revision
Builder matches or is greater than the
major revision of EtherNet/IP device
in the network.
Values are:
Disable Keying, Exact Match, Current
and Higher
IP String - - - Editable The IP address of the EtherNet/IP
Address(1) device on the network. It must be an
IP address on the same subnet as
where the CI873 is placed.
CI873 with the EtherNet/IP Device is
re-established.
Class Dint ms 10 500 Editable Requested Packet Interval in
1ExclusiveO milliseconds for O->T packets.
wner Upon modification, connection with
O2TRPI the Ethernet/IP device is re-
established.
9ARD000014-600 A 139
Editable
Only
Class Dint ms 10 500 Editable Requested Packet Interval in
1 Exclusive milliseconds for T->O packets.
Owner Upon modification, connection with
T2ORPI the Ethernet/IP device is re-
established.
Class Enum - - - Editable Class 1 connection is logical segment
1 Exclusive that is connection point based.
Owner The name of the connection is
Enabled derived from Connection Manager
section of EDS file by the EDS DIW.
Options are:
• Enabled - New connection will
be established and the data
starts updating on the
corresponding connection
channel.
• Disabled - Connection that is
already established, will be
closed.
(1) If the IP Address parameter is left blank, then it is evaluated from the EtherNet/IP device’s position in the hardware
tree along with the IP address of its CI873 parent unit. The first three octets are taken from the parent unit and last
octet from the hardware tree position.
140 9ARD000014-600 A
Section 4 Configuration EtherNet/IP Device with Tag Support
EtherNet/IP Device with Tag Support

EtherNet/IP device with tag support, enables class 1 and class 3 connection. The tag
supported EtherNet/IP devices are, such as Allen Bradley Logix 500 series PLC.
It is possible to add the Logix 5000 series PLC under the CI873 module in the
hardware tree. Before adding a new Allen bradley Control Logix 5000 series PLC,
ensure that PLC specific hardware types is added in the Hardware Library by using
Device Import Wizard. For more information, refer Converting an EDS File to a
Hardware Unit Type.
Configuring Logix 5000 series PLC Unit

Given below is an example for configuring a Control Logix PLC unit.
For configuring a Control Logix PLC Unit, in the hardware tree double-click
Control Logix PLC unit or right-click and select Editor from the context menu.
This opens the Hardware Editor, as shown in Figure 57.
9ARD000014-600 A 141
Configuring Logix 5000 series PLC Unit Section 4 Configuration
Figure 57. Hardware Editor – Settings for Allen Bradley Control Logix PLC
142 9ARD000014-600 A
Section 4 Configuration Configuring Logix 5000 series PLC Unit
The parameters for configuring the Control Logix PLC device are found in the
given in Table 24.
Table 24. Settings for Allen Bradley Control Logix PLC
Editable
Only
IP Address String - - - Editable The IP address of the PLC unit on the
network. It must be an IP address on
the same subnet as where the CI873
is placed.
CI873 with the PLC unit is re-
established.
Slot Number Dint - - - Editable The slot position occupied by the
PLC in the chassis.
ReceiveDat Dint ms 10 500 Editable Requested Packet Interval in
aFrom milliseconds for O->T packets.
O2TRPI Upon modification, connection with
the PLC unit is re-established.
ReceiveDat Dint ms 10 500 Editable Requested Packet Interval in
aFrom milliseconds for T->O packets.
T2ORPI Upon modification, connection with
the PLC is re-established.
Class 3 Enum - - - Editable This parameter is to enable/disable
Enabled the class 3 support.
9ARD000014-600 A 143
Configuring Logix 5000 series PLC Unit Section 4 Configuration
Table 24. Settings for Allen Bradley Control Logix PLC (Continued)
Editable
Only
Class 3 Dint - - 500 Editable Requested Packet Interval in
T2ORPI milliseconds for T->O packets.
(Applicable
only for
Class 3)
Tag1 Enum - - - Editable This parameter is used to enable or
Enabled disable the tag 1.
(Applicable
only for
Class 3)
Tag1 String - - 150 Editable This parameter shows the tag defined
TagName in the Allen Bradley PLC to which the
(Applicable connection is established.
only for
Class 3)
Tag1Cycle Dint ms 100 1000 Editable This is the scan cycle for tag 1.
Time
(Applicable
only for
Class 3)
Tag1Data Dint - 0 500 Editable This parameter determines the data
Type type of the tag defined in the Allen
(Applicable Bradley PLC.
only for
Class 3)
(Applicable
only for
Class 3)
144 9ARD000014-600 A
Section 4 Configuration Configuring Logix 5000 series PLC Unit
Table 24. Settings for Allen Bradley Control Logix PLC (Continued)
Editable
Only
Tag2 String - - - Editable This parameter shows the tag defined
only for
Class 3)
Tag2 Cycle Dint ms 100 1000 Editable This is the scan cycle for tag 2.
Time
(Applicable
only for
Class 3)
Tag2 Data Dint - 0 500 Editable This parameter determines the data
Type type of the tag defined in the Allen
(Applicable Bradley PLC.
only for
Class 3)
(Applicable
only for
Class 3)
Tag3 String - - - Editable This parameter shows the tag defined
only for
Class 3)
Tag3 Cycle Dint ms 100 1000 Editable This is the scan cycle for tag 3.
Time
(Applicable
only for
Class 3)
9ARD000014-600 A 145
Adding S200 I/O Modules Section 4 Configuration
Adding S200 I/O Modules

This section describes about inserting of S200 adapter, S200 I/O modules,
configuring of S200 adapter and S200 I/O modules.
Follow these steps to insert a new S200 adapter:
1. From the hardware library, right click and select Insert Library. Select
S200IoCI873HWLib and Insert as shown in Figure 58.
Figure 58. Insert Library
2. To insert the CI873 see Adding CI873 on page 107.

3. Connect the S200 Hardware library to the connected libraries.
146 9ARD000014-600 A
Section 4 Configuration Adding S200 I/O Modules
4. In the control builder hardware tree, right click the CI873 to select Insert Unit.
Select 200-AENTR Adapter, and click Insert as shown in Figure 59.
Figure 59. Insert 200-AENTR
9ARD000014-600 A 147
Configuring S200 Adapter Section 4 Configuration
Configuring S200 Adapter

For configuring the S200 adapter in the hardware tree double-click 200-AENTR or
right-click and select Editor from the context menu. This opens the Hardware
Editor, as shown in Figure 60.
Figure 60. Hardware Editor – Settings for S200 Adapter
The parameters for configuring the S200 adapter are found in the Settings tab.
Configure the parameters according to the description of parameters given in
Table 25.
Table 25. Settings for S200 Adapter
Parameter Default Value Description Consequence of Change

IP Address Empty String IP address of the S200 Connections to the I/O
(See adapter will use on the modules connected under
information network. It must be an the adapter are
note below) IP address on the same reestablished.
subnet as the CI873 it's
placed under.
If blank, the first three
fields are taken from its
parent CI873 IP
Address and the fourth
is from its hardware tree
position.
148 9ARD000014-600 A
Section 4 Configuration Configuring S200 Adapter
The IP address of 200-AENTR can be set in two ways:

• By using the Rotary wheel on the adapter. The limitation when using rotary
wheel is that one can configure IP address of the adapter to only Class C
address range. When the rotary switch is set to a valid number(001-254), the
adapter IP address is192.168.1.xxx (where xxx represents the number set
on the switches). The Adapter will have subnet mask is 255.255.255.0
• The second option is using BOOTP/DHCP server. This has no limitations.
Paths to the BOOTP utility:
For Control Builder Professional:
\Engineering & Development\Control Builder M\Tools\ 200-
AENTR\BOOTP-DHCP Server
For Compact Control Builder:
\Tools\ABB\ 200-AENTR\BOOTP-DHCP Server
9ARD000014-600 A 149
Inserting S200 I/O Modules Section 4 Configuration
Inserting S200 I/O Modules

In the control builder tree right click the 200-AENTR Adapter and select Insert
Unit. The Insert Unit for 200-AENTR window appears as shown in Figure 61.
Figure 61. Select S200 I/O Modules
Select the I/O Modules and click Insert. The modules will be inserted under 
200-AENTR as shown in Figure 62.
150 9ARD000014-600 A
Section 4 Configuration Inserting S200 I/O Modules
Figure 62. Inserted S200 I/O Modules
Upto 8 I/O Modules can be inserted under each 200-AENTR.
9ARD000014-600 A 151
Configuring S200 I/O Modules Section 4 Configuration
S200 IO modules that are supported with Ethernet/IP connectivity are mentioned
below:
200-IB16, 200-OB8EP, 200-OB16, 200-OB16P, 200-IB10XOB6, 200-IE8, 
200-OE4, 200-IE4XOE2, 200-IP2, 200-IP4, 200-IR8, 200-IR8R, 200-IT8, 200-IA8,
200-OA8, 200-OW8, 200-IF4I, 200-OF4I, 200-IM8, 200-OM8, 200-IB32, 
200-OB32P, 200-IB16XOB16P, 200-DUTB.
In addition to the above I/O modules following S200L I/O and S200C I/O modules
are also supported.
S200C - I/O: 200C-IB16, 200C-IB10XOB6P, 200C-OB16P, 200C-IE8, 
200C-IE4XOE2, 200C-OE4.
S200L - I/O: DI210, DX210, DO210, AI210, AX210, AO210.
Configuring S200 I/O Modules

For configuring the S200 I/O Modules in the hardware tree double-click I/O
Module or right-click and select Editor from the context menu. This opens the
Hardware Editor, as shown in Figure 63.
Figure 63. Hardware Editor – Settings for S200 I/O Modules
152 9ARD000014-600 A
Section 4 Configuration Configuring S200 I/O Modules
The Hardware Editor contains four tabs — Settings, Connections, Status and Unit
Status. The parameters for configuring the S200 I/O Modules are found in the
given in Table 26.
Table 26. Parameters on S200 IO modules
Default
Parameter Type Unit Min Max Description Consequence
Value
Connection 500 dint ms 10 1000 Requested Packet Connection
O2TRPI Interval for O->T with the IO
packets. module is 
re-established
Connection 500 dint ms 10 1000 Requested Packet Connection
T2ORPI Interval for T>O with the IO
packets. module is 
re-established
Connection 4 dint - 0 7 Specifies the multiplier Connection
Timeout applied to RPI to obtain with the IO
Multiplier the connection time-out module is 
value used for re-established
establishing implicit
messaging connection.
Refer Table 1 for
connection time-out
multiplier
These parameters are common for all the S200 I/O Modules.
Apart from these there are specific settings to be done for 200-IP2 and 200-IP4 I/O
Modules.
9ARD000014-600 A 153
The Table 27 below gives description about settings which are to be applied on
output channels and the interpretation of data received on the Input channels for
200-IP2.
Table 27. Description of Channels for 200-IP2
Channel Name Bit Definition

CtrlSig In 0 Bit 00 Status for input A (pulse transmitter 0) - This bit, when set,
indicates a signal at A
Bit 01 Status for input B (pulse transmitter 0) - This bit, when set,
indicates a signal at B
Bit 02 Status for input Z (pulse transmitter 0) - This bit, when set,
indicates a signal at Z
Bit 03 Status for input G (pulse transmitter 0) - This bit, when set,
indicates a signal at G
Bit 04 0 - Not Used
Bit 05 0 - Not Used
Bit 06 0 - Not Used
Bit 07 0 - Not Used
Bit 08 (10) This bit, when set (1), indicates that counter 0 has been calibrated.
This bit is reset by CalReset.
Bit 10 (12) This bit, when set (1), indicates a counter value is saved in store 0.
This bit is reset by StoreReset.
Bit 12 (14) Preset Reached - When this bit is set (1), in all configuration
modes, the counter 0 value equals the preset 0 value, either in a
positive or negative direction. This bit is reset by PresetReset0 and
can only be set again after at least 1 more pulse.
Bit 14 (16) Count Direction - Increase/Decrease counter value of counter 0 set
to 0 at startup.
0 = last pulse decreased counter value;
1 = last pulse increased counter value.
154 9ARD000014-600 A
Table 27. Description of Channels for 200-IP2 (Continued)

CtrlSig In 1 Bit 00 0 - Not Used
Bit 01 0 - Not Used
Bit 02 0 - Not Used
Bit 03 0 - Not Used
Bit 04 Status for input A (pulse transmitter 1) - This bit, when set,
indicates a signal at A
Bit 05 Status for input B (pulse transmitter 1) - This bit, when set,
indicates a signal at B
Bit 06 Status for input Z (pulse transmitter 1) - This bit, when set,
indicates a signal at Z
Bit 07 Status for input G (pulse transmitter 1) - This bit, when set,
indicates a signal at G
Bit 09 (11) This bit, when set (1), indicates that counter 1 has been calibrated.
This bit is reset by CalReset.
Bit 11 (13) This bit, when set (1), indicates a counter value is saved in store 1.
This bit is reset by StoreReset.
Bit 13 (15) Preset Reached - When this bit is set (1), in all configuration
modes, the counter 1 value equals the preset 1 value, either in a
positive or negative direction. This bit is reset by PresetReset1 and
can only be set again after at least 1 more pulse.
Bit 15 (17) Count Direction - Increase/Decrease counter value of counter 1 set
to 0 at startup.
0 = last pulse decreased counter value;
1 = last pulse increased counter value.
Latch In 0 Bits 00-15 Saved counter value on channel 0
Latch In 1 Bits 00-15 Saved counter value on channel 1
Value In 0 Bits 00-15 Current value in counter 0
9ARD000014-600 A 155

Value In 1 Bits 00-15 Current value in counter 1
Ctrl Out 0 0-15 Control word for setting the function of counter 0
Bits 00-02 02 01 00 Mode Selection bits
0 0 0 Counting on positive (rising) edge of input
signal A (Up/dwn counting determined by B)
0 0 1 Quadrature encoder X1
1 0 0 Counting up on the positive edge of input
signal A and down on positive edge of input
signal B.
1 0 1 No Count Function
Bit 03 Preset (Reset) bit - A positive edge on this bit moves the value in
Preset X to Counter X, independent of Preset Enable.
NOTE: To use Preset as Reset, use a count value of 0000 in the
Preset value word.
Bit 04 Enable Z Preset bit - When this bit is set (1), a positive edge on Z
preloads Counter X = Preset X, independent of Cal Enable.
NOTE: If Z is configured to do Store and Preset (Reset), the Store
will occur first.
Bit 05 Count Enable bit - When this is set (1), the incremental encoder is
enabled.
156 9ARD000014-600 A

Ctrl Out 0 Bits 06-08 Calibration Control bits - bits 06. 07 and 08
06 Enable bit - When this bit is set (1), the counter can be
calibrated
07 Direction bit - When this bit is set (1), calibration is
performed in a negative direction; when reset (0),
calibration is performed in a positive direction.
08 Reset bit - Calibration is acknowledged and a new
calibration is enabled on a positive edge on this bit.
Bits 09-10 10 09 Gate Control bits
0 0 No gate function on input G
0 1 Counting only if G is high (active)
1 0 Counting only if G is low (inactive)
1 1 The counter can be calibrated when G is high
(active)
Bits 11-12 12 11 Store Control bits - These bits will trigger a Store
only if the channel Store status bit (L0 or L1) is
cleared (0).
0 0 Save the counter value on the positive edge of Z (if
StoredX= O)
0 1 Save the counter value on the positive edge of G (if
StoredX= O)
1 0 Save the counter value on the negative edge of G (if
StoredX= O)
1 1 Save the counter value on the positive edge and
negative edge of G (if Stored X = 0)
Bit 13 Rollover bit - When set (1), the counter counts up to the preset
and then restarts at 0. If this bit is reset (0) (not rollover), the
rollover preset value = FFFF (hex = 65535 (decimal).
9ARD000014-600 A 157

Ctrl Out 0 Bit 14 Store Reset bit - A positive edge on this bit resets Store X in
Signals.
Bit 15 Preset Reset bit - A positive edge on this bit resets Preset
Reached in Signals.
Ctrl Out 1 Control word for setting the function of counter 1.
Bits 00-02 02 01 00 Mode Selection bits
0 0 0 Counting on positive (rising) edge of input
signa A. (Up/dwn counting determined by B.)
1 0 0 Counting up on the positive edge of input
signal A, and down on positive edge of input
signal B.
1 0 1 No count function
Bit 03 Preset bit - A positive edge on this bit moves the value in Preset X
to Counter X, independent of Preset Enable.
Bit 04 Preset Enable bit - When this bit is set (1), a positive edge on Z
preloads Counter X = Preset X, independent of Cal Enable.
Bit 05 Count Enable bit - When this is set (1), the incremental encoder is
counting.
158 9ARD000014-600 A

Ctrl Out 1 Bits 06-08 Calibration Control bits - bits 06, 07 and 08
06 Enable bit - When this bit is set (1), the counter can be
calibrated.
07 Direction bit - When this bit set (1), calibration is
performed in a negative direction; when reset (0),
calibration is performed in a positive direction.
08 Reset bit - Calibration is acknowledged and a new
calibration is enabled on a positive edge on this bit.
Bits 09-10 10 09 Gate Control bits
0 0 No gate function on input G
0 1 Counting on y if G is high (active)
1 0 Counting on y if G is low (inactive)
1 1 Calibration if G is high {active) and ???
Bits 11-12 12 11 Store Control bits - These bits will trigger a Store
only if the channel Store status bit (LO or L1) is
cleared (O).
0 0 Save the counter value on the positive edge of Z (if
Store X= O)
0 1 Save the counter value on the positive edge of G (if
Store X= O)
1 0 Save the counter value on the negative edge of G (if
Store X= O)
1 1 Save the counter value on the positive edge and
negative edge of G (if Store X= O)
Bit 13 Rollover bit - When set (1), the counter counts up to the preset
and then restarts at 0. If this bit is reset (0) (not rollover), the
rollover preset value = FFFF (hex = 65535 (decimal).
9ARD000014-600 A 159

Ctrl Out 1 Bit 14 Store Reset bit - A positive edge on this bit resets Store X in
Signals.
Bit 15 Store Reset bit - A positive edge on this bit resets Preset
Reached in Signals.
Preset Out 0 Bits 00-15 Preset 0 - Value to load or compare with counter 0
Preset Out 1 Bits 00-15 Preset 1 - Value to load or compare with counter 1
The Table 28 below gives description about settings which needs to be applied on
output channels and the interpretation of data received on the Input channels for
200-IP4.
Table 28. Description of Channels for 200-IP4
Channel Name Definition

Value in Period16 0 It gives 16 Bit period measurement for channel 0
Value in Counter 0 This channel shows pulse counter value for channel 0
160 9ARD000014-600 A

Ctrl In 0 Bit
Bit 00 Positive edge - Channel 0 - measurement ready
Bit 04 Reset Done, Channel 0 - a positive edge on this bit indicates
counter 0 reset done
Ctrl In 1 Bit
Ctrl In 2 Bit
Ctrl In 3 Bit
Bit 08-15 Reserved for factory use
9ARD000014-600 A 161

Function Select Bits 00 Pulse counting and period time measurement selection for
Channel 0 -
0 = pulse counting and period time measurement selected
1 = period time measurement selected
Bits 01 Pulse counting and period time measurement selection for
Channel 1 -
Channel 2 -
Channel 3 -
Bits 04-15 Reserved
162 9ARD000014-600 A

Frequency Select Bit 00 Clock frequency for period time measurement - Channel 0 -
0 = period time measurement with 10MHz internal clock
selected
1 = period time measurement with 1MHz internal clock selected
Bits 01-03 03 02 01 Number of periods for measurement - Channel 0
0 0 0 1 period
0 0 1 2 periods
0 1 0 4 periods
0 1 1 8 periods
1 0 0 16 periods
1 0 1 32 periods
1 1 0 64 periods
1 1 1 128 periods
Bit 04 Clock frequency for period time measurement - Channel 1 -
refer to bit 00.
Bits 05-07 Selection of Number of periods for measurement - Channel 1 -
see bits 01-03 above
refer to bit 00.
refer to bit 00.
9ARD000014-600 A 163

Ctrl Out 0 Bit 00 Start new measurement bit - Channel 0 - when set, start new
measurement on positive edge
Bit 04 Reset Counter, Channel 0 - a positive edge on this bit resets
counter 01
counter 11
counter 21
counter 31
Bit 08-15 Not Used
164 9ARD000014-600 A
Section 5 Run-Time Operation
This section describes the run-time behavior of DeviceNet device, LD 800DN

linking device, and EtherNet/IP device, and provides guidelines for operating these
devices during re-import and re-configuration.
Run-Time Behavior
The run-time behavior of DeviceNet device, LD 800DN linking device, and
EtherNet/IP device are:
• When a DeviceNet device configured in Control Builder, does not match with
the DeviceNet device available in the network, the device status shown in
Control Builder is I/O Connection Error and not Wrong Device Type.
• If the connection between LD 800DN and CI873 is lost or connection between
LD 800DN and configured DeviceNet slaves is lost, then IEC 1131 variables
connected to input channels of DeviceNet slaves get set to last good value.
• Consider an LD 800DN, with either DeviceNet devices or Modular I/O devices
is configured under it. On checking the diagnostic information channel of the
LD 800DN in Control Builder, there may be increase in the value of Number of
lost EtherNet/IP messages on the LD 800DN. To reduce the number of lost
message packets, increase the Requested Packet Interval (RPI) value. The RPI
value can be increased from 10 (minimum) to 500 (maximum). By increasing
the RPI value, it helps in reducing/stopping the increase in the number of lost
packets.
• Error is not set for EtherNet/IP and DeviceNet devices if the configuration is
cold downloaded or CI873 is hot swaped with its Ethernet cable removed.
However, if the cable is removed during run time, all the slave devices under
CI873 are updated with the connection related status.
9ARD000014-600 A 165
Run-Time Behavior Section 5 Run-Time Operation
• "Wrong MAC ID" Error status is not set in Unit Status for the LD 800DN in
Control Builder, if the user specifies a MAC ID for the LD 800DN, and this
MAC ID is already set for a physically available DeviceNet device on the
network but not available in the Control builder configuration that has been
downloaded to the LD 800DN.
• When the communication of DeviceNet devices is working properly with 
LD 800DN, if the MAC ID is changed to a wrong MAC ID and configuration is
downloaded, then the Unit Status for the LD 800DN in Control Builder shows
error for Wrong MAC ID. However, the communication between LD 800DN
and DeviceNet devices continues as before the MAC ID was changed. The
communication between CI873 and LD 800DN is also not affected.
• Some devices do not accept configuration of some parameters from CI873
when the connection to the device is already established. For such devices,
when there is power reset for the ethernet switch or CI873 ethernet cable
removal and insertion, connection is re-established to the device followed by
configuration of the parameters. Since some of the parameters for such a device
is not configured, the "Internal Config Error" warning is shown. 
To overcome this, perform the following:
– Perform a hot swap of CI873, the configuration is downloaded before the
connection is established. Hence all device configuration parameters are
accepted by the device and the Unit status does not displays the "Internal
Config Error" warning.
– Move that specific device to another position in Control Builder, and
download followed by changing it back to original position.
166 9ARD000014-600 A
Section 5 Run-Time Operation Run-Time Behavior
• Address recovery will not work for DeviceNet device which has physical
switches/jumpers for setting MAC address. It works for DeviceNet devices
whose MAC address can be dynamically set from either the LD 800DN Web
interface or by any device specific configuration tools, for example,
RSNetworks for DeviceNet.
• For any errors for DeviceNet devices that is reported in Unit Status in Control
Builder, due to communication break between the LD 800DN and the device,
the user can still force a value into the output channel of the device from
Control Builder or from the 1131 application. This output channel value shall
be written into the LD 800DN. This value shall be written into the device once
the communication between the LD 800DN and the device is restored.
Some devices like Allen Bradley PLC do not support client CI873 going offline
without closing existing connection. Since, the existing connections of such
devices with CI873 are not closed when the latter is hot removed, this could lead
to connection starvation. The error/status that is displayed in the Unit Status of
such device is, No more consumer resources available in the
producing object.
Therefore, communication with such devices may fail during the hot swap of the
CI873 module.
The DeviceNet EDS file could have a configuration parameters related to Safer
State Value (or a 'Fault Action' parameter) that can be configured to 'Clear data' or
'Hold last value', in case the deviceNet device looses communication with LD
800DN.
User needs to configure the configuration parameters for the channels of the
device have desired result.
9ARD000014-600 A 167
Guidelines for Re-import and Re-configuration Section 5 Run-Time Operation
The EDS file of some device may have a lot of configuration parameters and
connections. In rare scenarios this would exceed the maximum configuration size
per device in control builder of 65535 bytes. If this happens, a compilation error
would be displayed when the user tries to download such a hardware type to the
controller and the download would be aborted.
User would then need to re-import the EDS file of such a device and delete some
parameters/ connection that are not required so as to bring the configuration size
of the device to acceptable limits.
Guidelines for Re-import and Re-configuration

This section describes the guidelines to be followed during re-import and re-
configuration.
Re-import
There is a possibility of I/O modules duplication within the same hardware library
during re-import.
Consider a modular import scenario in which certain I/O modules are selected to be
imported under the adapter, the hardware types for all the I/O modules are created in
the hardware library.
So all the I/O modules imported are available to be inserted in the hardware tree
under the adapter.
1. Considering a modular re-import scenario, where, certain I/O modules are 
de-selected and only a subset of the modules are imported, which are currently
available under the adapter. These de-selected modules still appears under the
hardware library as they have not been physically deleted from the hardware
library.
However de-selected I/O modules cannot be added in the hardware tree under
the adapter. Hence, only the I/O modules being included or selected in the most
recent import of the adapter will be available for configuration under the
adapter.
168 9ARD000014-600 A
Section 5 Run-Time Operation Re-import
2. If in the next re-import if the de-selected modules from point 1 above are
selected again and the import is proceeded, the hardware types for the newly
selected I/O modules are created with new hardware ID's. If such I/O module
were already available under adapter in the hardware tree, they to be deleted
and has to be added again under the adapter.
When re-importing an EDS file, the name and location of the EDS file should be
same as the previously imported EDS files. If these are the same, then the Device
Import Wizard considers this as a re-import. Else the Device Import Wizard
considers this as a fresh import.
Hence, re-importing of an EDS file is not possible if the EDS file is renamed and
then re-imported.
The user can choose for fresh import instead of a re-import, if the newly created
hardware type has to coexist with old hardware type.
In case the configuration imported for EDS file is not correct, the hardware type
should not be deleted from the hardware library, after it has been created by
importing an EDS file in Control Builder.
Instead, to correct the configuration, re-import the EDS file in the same hardware
library, or create a new hardware library and import the EDS file under it.
9ARD000014-600 A 169
Re-configuration Section 5 Run-Time Operation
Re-configuration
Re-configuration of DeviceNet Devices and LD 800DN
The following are the re-configuration scenarios when the connection between
linking device and all connected DeviceNet devices times out for a while and are
then reconnected:
• Re-configuration of Connection related parameters (Scan list parameters) of
DeviceNet/LD 800DN
– When a connection related parameter is modified for a device in the
Control Builder.
– When parameters like Inter Scan Delay, Expected Packet Rate,
Foreground to Background Poll Ratio, ADR are changed for LD 800DN
in the Control Builder. See Updation of Scan List on DeviceNet Device
Parameter Change.
• Re-configuring DeviceNet Parameters on LD 800DN. See Re-configuring
DeviceNet Parameters on LD 800DN.
During re-configuration, the DeviceNet communication is stopped and restarted
as the LD 800DN is put to Idle mode before modifying any configuration data on
LD 800DN. During such time, the input data from the DeviceNet slave devices to
the CI873 is not affected. However, there is no output data from the linking
device to the DeviceNet slave devices.
If the connections related to some DeviceNet devices are changed (if some
existing connection as disabled and others are enabled) as part of a 
re-configuration, the communication does not start with a new connection. 
The LD 800DN needs to be reset so as to establish communication with such
devices.
• Adding/deleting DeviceNet devices online
– When a new DeviceNet device is configured or added in Control Builder.
– When a DeviceNet device is deleted in the Control Builder.
–
170 9ARD000014-600 A
Section 5 Run-Time Operation Re-configuration
Updation of Scan List on DeviceNet Device Parameter Change

While re-configuration of a DeviceNet device, do not change the scan list
parameters, which are not associated with the connection trigger type to which
the DeviceNet device is configured initially.
For example, assume that the Poll connection trigger type is selected during
fresh configuration of DeviceNet device. During re-configuration, the scan list
parameters associated with the COS connection trigger type is changed, such
as Inhibit time and Acknowledgement time. These changed scan list
parameters are not associated with the Poll connection trigger type to which the
device is configured. Since, the CI873 does not verify whether the changed
parameters have any effect on the trigger type selected, the communication is
considered changed. As a result the scan list configured on the LD 800DN gets
updated, leading to the stoppage of communication in the DeviceNet network.
The Control Builder displays a warning indicating the break down of
communication.
Re-configuring DeviceNet Parameters on LD 800DN
Re-configuring the DeviceNet parameters on an LD 800DN does not disrupt
the flow of input data from the DeviceNet slave devices to the CI873. However,
the linking device has to be in Idle mode before modifying any configuration
data on it. There is no output data from the linking device to the DeviceNet
slave devices while the linking device is in Idle mode
Re-configuring LD 800DN by changing Baud Rate
If the baud rate of the LD 800DN is changed, then a matching baud rate change
should be made in all the DeviceNet devices connected to that LD 800DN. A
power recycle is then needed for these changes to take effect. A matching baud
rate change is not possible in DeviceNet devices which do not have any baud
rate option in its configuration parameters. As a result, such devices may
become incompatible with the LD 800DN's baud rate configuration. In such a
case, the error displayed is CAN Bus Off or DeviceNet MAC ID
initialization in progress.
Re-configuration of EtherNet/IP devices

When an EtherNet/IP device or EtherNet/IP modular IO is added /removed online,
then the communication with other EtherNet/IP devices will not be affected.
9ARD000014-600 A 171
Online Upgrade and Coexistence Section 5 Run-Time Operation
Online Upgrade and Coexistence

In the SV 6.0, there are two CI873 hardware libraries available in the 800xA system.
The usage of the two hardware libraries in the control builder projects will be as
follows:
1. CI873EtherenetIPHwlib 1.x.: Used only when a coexistence download is done
from a SV 6.0 Control Builder project to a controller of SV 5.1 and rollups.
2. CI873EtherenetIPHwlib 2.x.: Used in all other scenarios in SV 6.0 that
includes:
a. Co-existence download from SV 6.0 Control Builder project to a
controller having SV 5.1 FP4.
b. Online upgrade is done from SV 5.1 FP4 to SV 6.0.
c. Online upgrade is done from SV 5.1 and rollups to SV 6.0.
When an online upgrade is done from SV 5.1 and rollups to SV 6.0, at step 7 of
the online upgrade, the trainee controller that has been upgraded with new
firmware would have become primary. The communication of CI873 with the
devices under it would stop, as the CI873 is still having old firmware. At step 8,
the firmware upgrade of the non-redundant CI873 would be done. After the
CI873 is upgraded with latest firmware, it shall boot up and restart
communication with devices under it. This is observed as the there is a major
version change of the CI873 hardware library in SV 6.0 compared to that in SV
5.1 and rollups.
172 9ARD000014-600 A
Section 6 Linking Device LD 800DN
Overview
The LD 800DN, EtherNet/IP to DeviceNet linking device, provides full DeviceNet
master functionality, allowing connectivity to 63 DeviceNet slaves. It also supports
EtherNet/IP adapter class functionality with CIP Message Routing.
LD 800DN can be used to:
• Connect EtherNet/IP to DeviceNet (bridge functionality).
• Connect information or control level networks to device level networks for
programming, configuration, control or data collection.
Features
The features of the LD 800DN linking device are:
• Baud rates of 125, 250, and 500 Kbps are supported.
• Automatic Address Recovery to replace a faulty slave device with a
replacement device, at the same MAC ID.
• Configuration Recovery can be enabled for slave devices. Thus, a newly
replaced device slave can be configured to the same settings of the device, it
replaces.
• Transfers 496 bytes Input and 492 bytes Output.
• An FTP server functionality, which provides easy file management using
standard FTP clients.
• A flexible HTTP server functionality (Web server).
• Firmware updates using the RS232 port and BridgeWay Configuration Tool.
9ARD000014-600 A 173
Configuration Section 6 Linking Device LD 800DN
Configuration
This section describes the configuration of the LD 800DN Ethernet to DeviceNet
linking device.
BridgeWay Configuration Tool

Before configuring the LD 800DN in the Control Builder and going online, it should
be configured with an IP Address and MAC ID. This is done by using the
BridgeWay Configuration tool.
The BridgeWay Configuration is a Microsoft Windows application that
communicates with the LD 800DN over a standard RS-232 serial link, using the PC
serial port or USB serial adapter.
The BridgeWay Configuration must be used only for setting the IP address, MAC
ID and upgrading the firmware. Making any other changes will cause a conflict
with the settings downloaded from CI873.
Installing BridgeWay Configuration Tool

To install BridgeWay Configuration from the System 800xA Media, run Setup.exe
available in the following directory of the System 800xA Media:
• For Control Builder Professional:
\Engineering & Development\Control Builder M\Tools\
LD800DN\ConfigurationTool
• For Compact Control Builder:
\Tools\ABB\LD800DN\ConfigurationTool.
Connecting to the LD 800DN Module

Connect the system, in which BridgeWay Configuration is run, to the LD 800DN
module by using a standard Null-Modem (pin 2 and pin 3) serial cable. This cable
should connect the PC serial port (or the USB serial adapter, if used) to the 9 pin D-
Sub connector on the module.
BridgeWay Configuration scans for each available port, detects the connection and
automatically sets the baud rate.
174 9ARD000014-600 A
Section 6 Linking Device LD 800DN BridgeWay Configuration Tool
Starting BridgeWay Configuration

Ensure that the LD 800DN module is powered and connected to the PC serial port.
Select Start > BridgeWay Configuration, to run the BridgeWay Configuration
tool.
When BridgeWay Configuration is launched, it attempts to locate a LD 800DN
module on one of the PC serial ports. After locating the module, the status area of
the tool displays the type and the status of that module.
If module is not connected to the PC or if it is powered off, the status area indicates
that no module is detected. If the module is powered off, switch it on and ensure that
the connection is proper. Then, click Refresh icon on the BridgeWay Configuration
tool bar.
BridgeWay Configuration User Interface

Figure 64 shows the BridgeWay Configuration user interface.
Figure 64. BridgeWay Configuration User Interface
9ARD000014-600 A 175
Updating LD 800DN Firmware Section 6 Linking Device LD 800DN
The BridgeWay Configuration window is divided into the following three panes:
• BridgeWay Configuration - Used for displaying the module type and the
status information about the detected LD 800DN module.
• Ethernet Configuration - Used for configuring the Ethernet network
parameters.
• DeviceNet Configuration - Used for configuring the DeviceNet network
parameters. It also displays network interface status.
Updating LD 800DN Firmware

You can perform a Flash Update of the LD 800DN’s firmware, using the BridgeWay
Configuration tool.
Follow these steps for updating the firmware of the linking device:
1. Launch the BridgeWay Configuration tool, by selecting
Start > BridgeWay Configuration. The tool connect to the LD 800DN
module and the BridgeWay Configuration user interface appears
2. Click Update from the Flash menu in the menu bar. The Flash Update window
For Modular DeviceNet devices, LD establishes connection only to the adapter,

since the connection size is mismatched connection will fail and the whole device
is marked error. If the query interface is in then user can see which specific I/O
module has created this problem as the I/O module which is physically not
available will be marked as Device Not found.
176 9ARD000014-600 A
Section 6 Linking Device LD 800DN Updating LD 800DN Firmware
Figure 65. Flash Update for updating firmware
3. From the Flash Update window, click Select File to browse for the firmware
update files. Select the .nvs file.
Firmware files are available in the following directory of the product System
800xA Media:
– For Control Builder Professional:
\Engineering & Development\Control Builder M\
Tools\LD800DN\Firmware
– For Compact Control Builder:
Tools\ABB\LD800DN\Firmware
9ARD000014-600 A 177
Updating LD 800DN Firmware Section 6 Linking Device LD 800DN
Upon selecting the firmware update files, the details about the revisions of the
firmware, that is going to be updated, appears under Image Revisions as
shown in Figure 66.
Ensure that the latest firmware is used for firmware updates. Invalid/obsolete
firmware update combinations if detected, will not be allowed.
Figure 66. Image Revisions
4. Click Start to start the firmware update.

Upon successful firmware update, the LD 800DN is automatically reset. When
it comes online, following the reset, it will have the updated firmware.
178 9ARD000014-600 A
Section 6 Linking Device LD 800DN IP Address and MAC ID Configuration for LD 800DN
IP Address and MAC ID Configuration for LD 800DN

To configure the IP address and MAC ID of LD 800DN by using the BridgeWay
Configuration tool, follow these steps:
1. Launch the BridgeWay Configuration tool, by selecting
Start > BridgeWay Configuration. The tool connect to the LD 800DN
module and the BridgeWay Configuration user interface appears
2. In the Ethernet Configuration pane of the user interface, edit the IP Address
and the Subnet Mask fields to the desired values.
3. In the DeviceNet Configuration pane of the user interface, edit the MAC
Address field to set the desired node address/MAC ID.
4. Click Download to Module from the Configuration menu, to initiate
download of the new configuration to the LD 800DN linking device. On
clicking Download to Module, a dialog box with the following message is
displayed:
Downloading the configuration may cause the device to
reset or active connections to be interrupted. Do you wish
to continue?
5. Click Yes if you wish to continue with the download.
The LD 800DN is automatically reset after the IP Address and MAC ID
configuration is downloaded from the BridgeWay Configuration tool.
Apart from using the BridgeWay Configuration tool, other methods to set the IP
Address of the linking device are:
• Setting IP Address using LD 800DN DIP Switch on page 179
• Setting the IP Address through the Web Page on page 180
Setting IP Address using LD 800DN DIP Switch

There is an 8 position Dual In-line Package (DIP) switch on one end of the
LD 800DN module. This DIP switch can be used to select a portion of the default
IP Address.
The value of the switch is assigned as the last octet of the IP Address when the
module powers up.
9ARD000014-600 A 179
IP Address and MAC ID Configuration for LD 800DN Section 6 Linking Device LD 800DN
The DIP Switch value is the binary value of the last byte in the 4 byte IP address.
Considering it as n, then:
• IP Address – 192.168.1.n
• Subnet Mask – 255.255.255.0
• Gateway Address – 0.0.0.0 (No gateway set)
A non-zero DIP switch setting overrides any other IP Address setting done.
Hence, set the DIP switch value to zero if other methods are used to set the IP
address of the LD 800DN.
Refer to Figure 67, for a sample illustration of a DIP Switch.
Figure 67. DIP Switch Configuration
The switches are set to 00010100 (20 decimal) (The switch position is shown in
White in Figure 67). Hence, the IP address of the module is set to 192.168.1.20.
The numbers on the switches of DIP switch do not correspond to bit locations in
the address value. Instead, the numbers are reversed. That is, bit 0 is set by
switch 8.
Setting the IP Address through the Web Page

The IP address of the linking device can also be configured by using the LD 800DN
Status & Settings web page from the linking device.
To view the web page, use http://<IP Address> as the URL, where
<IP Address> is the current IP Address of the module. This URL brings up the
Status & Settings web page. For details on the Status & Settings web page and on
setting up the IP address, refer Status & Settings Web Page on page 196.
180 9ARD000014-600 A
Section 6 Linking Device LD 800DN IP Address and MAC ID Configuration for LD 800DN
IP Address Initialization
Figure 68 shows a flowchart that describes how the IP configuration is determined
when the LD 800DN is powered up.
Figure 68. IP configuration
9ARD000014-600 A 181
Scan Cycle Section 6 Linking Device LD 800DN
Scan Cycle
The Scan cycle of the linking device is used for its communication with DeviceNet
slaves. A scan cycle consists of the following:
• A Strobed Message and associated Strobed responses.
• Polled messages and responses.
• Inter scan delay, which is the time delay between consecutive I/O scans.
Figure 69 shows a graphical illustration of the Scan cycles.
Figure 69. Scan Cycles
Inter Scan Delay is used for performing non-time-critical operations, like

configuration using explicit messages.
Setting Inter Scan Delay to a very low value increases the latency for non-time-
critical operations. Setting this parameter to a very large value reduces the
newness of the I/O data being collected by the linking device and is not advisable.
182 9ARD000014-600 A
Section 6 Linking Device LD 800DN LD 800DN I/O Tables
LD 800DN I/O Tables

The LD 800DN maintains an I/O table accessible by both DeviceNet slaves and
CI873. The DeviceNet interface in the LD 800DN accesses the I/O tables, as slave
I/O connections are processed by the DeviceNet master. There is no buffering or
timed updates of the I/O within the module. Safeguards are in place to ensure data
integrity by prohibiting simultaneous access by the Ethernet and DeviceNet
interfaces. There is no synchronization between the two network interfaces.
When an output data is required on a I/O connection of a slave, the output data is
read from the Output table. This output data is written by the Ethernet interface.
When an input data is received on a I/O connection of a slave, it is copied to the
Input table. This data is available for reading by the Ethernet interface and sent to
the EtherNet/IP I/O scanner during the next data exchange.
Status and Diagnostics Indicators

LD 800DN has a group of LED indicators on its front side for displaying the current
status of the module and the network interfaces. The layout of the LEDs is shown in
Figure 70.
Figure 70. LD 800DN LEDs
9ARD000014-600 A 183
LD 800DN Status LED Section 6 Linking Device LD 800DN
LD 800DN Status LED

Table 29 shows the status of LD 800DN LED states.
Table 29. LD 800DN Status LED States
State Summary Description

Flashing Green Idle Module is in Idle mode.
Solid Green Run Module is in Run mode.
Solid Orange Hardware The LED will be in this state immediately after the
Initialization power is switched on.
Flashing Red/Green Error A major, unrecoverable fault has been detected.

Red, Green, Orange Self Test A self test of the module is in progress.
Alternate Flashing
Major unrecoverable faults are indicated by a series of green and red flashes. If the
LD 800DN Status LED is flashing red and green for an extended period of time,
then contact ABB technical support for assistance in problem reporting.
DeviceNet Network Status LED

Table 30 shows the DeviceNet Network Status LED states.
Table 30. DeviceNet Network Status LED States

Solid Green Online and communicating The LD 800DN is on the DeviceNet
network and communicating with at
least 1 device.
Flashing Online, no communication The LD 800DN is on the DeviceNet
Green network and is currently not
communicating with any devices.
184 9ARD000014-600 A
Section 6 Linking Device LD 800DN DeviceNet Module Status LED
Table 30. DeviceNet Network Status LED States (Continued)

Solid Red DeviceNet interface fault A major fault in the DeviceNet interface
has been detected. Possible causes
include Bus-off or duplicate MAC ID.
Flashing Red Connection time-out A connection with at least 1 slave device
has timed out.
Red,Green Self Test A self test of the module is in progress.
Alternate
Flashing
Bus-off is generated if LD 800DN is transmitting messages at the time of

disconnection and the internal error counter in the CAN controller in the LD 800DN
reaches the Bus-off state. If LD is not transmitting messages at the time of
disconnection or CAN controller is not reaching the Bus-off state the module could
be prevented from reaching this state.
DeviceNet Module Status LED

Table 31 shows the DeviceNet module’s Status LED states.
Table 31. DeviceNet Module Status LED States

Flashing Initializing, standby, or not The module is initializing.
Green configured
The DeviceNet network configuration
has not been configured and is currently
using default values.
Solid Green Normal Normal operation.
Solid Red Unrecoverable fault A fault that requires user intervention
has been detected. Correct the problem
and reset the LD 800DN.
9ARD000014-600 A 185
Ethernet Activity LED Section 6 Linking Device LD 800DN
Table 31. DeviceNet Module Status LED States (Continued)

Flashing Red Recoverable fault A fault that can be corrected and does
not require a LD 800DN reset has been
detected. This will typically be a
configuration error.
Alternate
Flashing
Ethernet Activity LED

The Ethernet Activity LED flashes green as Ethernet packets are received or
transmitted.
Ethernet Link LED

The Ethernet Link LED indicates that the module is connected to an Ethernet
network. The LED displays solid green if there is a valid physical link.
Ethernet Module Status LED

Table 32 shows the Status LED states of an Ethernet module.
Table 32. Ethernet Module Status LED States

Off No Power No power supply.
Solid Green Normal The module is operating correctly.
Flashing Green Standby The module has not been initialized.
Solid Red Unrecoverable fault A fault the requires user intervention has
been detected. Correct the problem and
reset the LD 800DN.
186 9ARD000014-600 A
Section 6 Linking Device LD 800DN Ethernet Network Status LED
Table 32. Ethernet Module Status LED States (Continued)

Flashing Red Recoverable fault A fault that can be corrected and does not
require a LD 800DN reset has been
detected.
Alternate
Flashing
Ethernet Network Status LED

Table 33 shows the Status LED states of an Ethernet Network.
Table 33. Ethernet Network Status LED States

Off No Power The module has no power or no IP address
assigned.
Solid Green Network OK and communicating There is at least one EtherNet/IP connection.
Flashing Green Network OK There are no active connections.
Solid Red Address conflict The IP address of the module is already in
use by another module.
Flashing Red Connection Time-out The module which is the target in one or more
connection has timed out. This state occurs if
all timed out connections are reestablished or
if the module is reset.
Alternate
Flashing
9ARD000014-600 A 187
Specifications for LD 800DN Section 6 Linking Device LD 800DN
Specifications for LD 800DN

Figure 71 shows the physical dimensions of LD 800DN hardware module:
Figure 71. LD 800DN Specifications
188 9ARD000014-600 A
Section 6 Linking Device LD 800DN Diagnostics through Web Interface
Diagnostics through Web Interface

LD 800DN, acting as a Web Server, provides diagnostic functionalities through a
web interface. To access the home page of this interface, use http://<IP Address> as
the URL, where <IP Address> is the IP address of the LD 800DN module.
To display the diagnostic web pages properly, Web browser must have Java
Virtual Machine/Microsoft Virtual Machine installed.
The home page opens as shown in Figure 72.
The EtherNet to DeviceNet Gateway home page has links to the following
diagnostic web pages:
• Active Slaves (see Active Slaves on page 191).
• Idle Slaves (see Idle Slaves Web Page on page 192).
• Faulted Slaves (see Faulted Slaves Web Page on page 193).
• Invalid Slaves (see Invalid Slaves Web Page on page 194).
• Slave Status (see Slave Status Web Page on page 195).
• Status and Settings (see Status & Settings Web Page on page 196).
• DeviceNet Devices (see DeviceNet Devices Web Page on page 199).
9ARD000014-600 A 189
Diagnostics through Web Interface Section 6 Linking Device LD 800DN
Figure 72. EtherNet to DeviceNet Gateway home page
190 9ARD000014-600 A
Section 6 Linking Device LD 800DN Active Slaves
Active Slaves
The Active Slaves web page, shown in Figure 73, displays the DeviceNet slave
nodes which are configured as slave units under LD 800DN DeviceNet master in
Control Builder. Each node that is configured as slave is displayed with Active
status next to the MAC ID of the node.
Figure 73. Active Slaves web page
9ARD000014-600 A 191
Idle Slaves Web Page Section 6 Linking Device LD 800DN
Idle Slaves Web Page

The Idle Slaves web page, shown in Figure 74, indicates the DeviceNet slave nodes
which are currently in the Idle state. This indication is only for nodes configured as
slaves under LD 800DN in Control Builder. If a slave is Idle, the page displays Idle
status next to the MAC ID of the slave.
Figure 74. Idle Slaves web page
192 9ARD000014-600 A
Section 6 Linking Device LD 800DN Faulted Slaves Web Page
Faulted Slaves Web Page

The Faulted Slaves web page, shown in Figure 75, indicates DeviceNet slave nodes
which currently have faults. This indication is only for nodes configured as slaves
under LD 800DN in Control Builder. If a slave is in fault state, the page displays
Faulted status next to the MAC ID of the slave.
Figure 75. Faulted Slaves web page
A slave node is considered to be in fault, if the LD 800DN has lost communication

or is unable to establish communication with the slave node. The actual problem can
be determined by viewing the Slave Status web page.
9ARD000014-600 A 193
Invalid Slaves Web Page Section 6 Linking Device LD 800DN
Invalid Slaves Web Page

The Invalid Slaves page, as shown in, indicates DeviceNet slave nodes that are not
of the correct device type. This indication is only for nodes configured as slaves
under LD 800DN in Control Builder. If a device type of a slave is different than that
configured in Control Builder, then the page displays Invalid status next to the
MAC ID of the slave.
Figure 76. Invalid Slaves web page
194 9ARD000014-600 A
Section 6 Linking Device LD 800DN Slave Status Web Page
Slave Status Web Page

The Slave Status page, shown in Figure 77, displays the current status of all
DeviceNet slave nodes that are configured as slaves to the LD 800DN and also the
status of the LD 800DN itself. The status of each node is displayed next to the MAC
ID of the node.
Figure 77. Slave Status web page
9ARD000014-600 A 195
Status & Settings Web Page Section 6 Linking Device LD 800DN
Status & Settings Web Page

The Status and Settings web page, shown in Figure 78, displays the LD 800DN
identification information, DeviceNet network status. It also allows re-configuration
of the Ethernet network settings. The details displayed in this web page are as
follows:
• Product Name
• Vendor ID
• Product Type
• Product Code
• Product Revision
• Anybus Revision
• Serial Number
• DeviceNet MAC ID
• DeviceNet Baud Rate
• DeviceNet Autobaud Enabled/Disabled
• DeviceNet Network Status
• DeviceNet Scanner Mode
• Current IP Address, Subnet Mask, Gateway IP Address, and Mail Server IP
Address
• DHCP Enabled/Disabled
196 9ARD000014-600 A
Section 6 Linking Device LD 800DN Status & Settings Web Page
Figure 78. Status & Settings web page
Changing IP Settings
The Status and Settings page allows re-configuration of the ethernet network's
settings. Follow these steps to reconfigure the network settings:
1. Click Change IP Settings.
A security check is made by the system to prevent unauthorized change of
settings. A valid LD 800DN Administrator Account is required to proceed
further. Refer User Accounts on LD 800DN on page 203 for more details.
9ARD000014-600 A 197
Status & Settings Web Page Section 6 Linking Device LD 800DN
Once a valid user account is provided, the IP Settings screen is displayed, as

shown in Figure 79.
Figure 79. Changing IP Settings
2. Change the following configuration settings in the IP Settings screen:

– Change the address values of IP Address, Subnet Mask, Gateway IP
Address, Mail Server IP Address
– Select/Clear the DHCP Enabled check box to enable/disable DHCP
3. Click Submit Values to save the configuration changes. On successful storage
of configuration changes, the following message is displayed:
Configuration stored successfully. The IP address switch
must be set to 0000_0000 and the LD 800DN must be reset or
power cycled in order to apply the stored configuration.
198 9ARD000014-600 A
Section 6 Linking Device LD 800DN DeviceNet Devices Web Page
4. Click Reset Module to apply the stored configuration. The new IP settings will
then be visible in the Status and Settings page when the Web page is refreshed
after the module boots up.
If the Web browser is configured to cache Web pages, it may appear that the
LD 800DN has not changed address after the power cycle. Ensure that the
browser settings are configured to always reload pages. In Internet Explorer, this
is done in the Temporary Internet Files and History Settings dialog by
selecting the Every time I visit option for when the browser should check for
newer versions of the Web page.
DeviceNet Devices Web Page

The DeviceNet Devices link displays the Detected DeviceNet Devices Web page, as
shown in Figure 80. This page shows the MAC ID and device names of all
DeviceNet devices which are configured under the LD 800DN. All MAC IDs at
which a configured device is detected, appear underlined. The device name of a
configured device is displayed only if the device name has been setup within the
device.
9ARD000014-600 A 199
DeviceNet Devices Web Page Section 6 Linking Device LD 800DN
Figure 80. Detected DeviceNet Devices web page
The Detected DeviceNet Devices page is not updated/refreshed automatically. Click

Refresh Display to view the latest updated details.
Changing the MAC ID

The MAC ID (or MAC Address) of a detected DeviceNet device can be changed by
following these steps:
1. To change the MAC ID of a detected device, click the ID.
When the MAC ID is clicked, a security check is made by the system to prevent
unauthorized change of settings. A valid LD 800DN Administrator Account is
required to proceed further. Refer User Accounts on LD 800DN on page 203
for more details.
200 9ARD000014-600 A
Section 6 Linking Device LD 800DN Files and File System in LD 800DN
The Set New DeviceNet Address page, appears as shown in Figure 81.
2. The Set New DeviceNet Devices page contains the following:
– Device - The device name of the DeviceNet device is displayed here. The
device name is not displayed if the device vendor has not configured it
within the device.
– Current MAC ID - The current MAC ID is displayed here.
– Desired MAC ID - Specify the new MAC ID here. It can be any free
MAC ID from 0 to 63.
3. After specifying the new MAC ID, click Set New MAC ID. If the ID has been
successfully changed, the MAC ID set successfully message is displayed.
Figure 81. Setting New MAC ID
Files and File System in LD 800DN

The LD 800DN provides a file system and file transfer capabilities. The user data
and application data can be stored, if required, in files within this file system.
The size available for user data files is approximately 1 Mega Byte. The files can
also be grouped into directories. An inbuilt FTP server provides easy file access and
management through standard FTP clients.
9ARD000014-600 A 201
File System Structure Section 6 Linking Device LD 800DN
File System Structure

Figure 82 illustrates the structure of the file system — where the system files are
located and which areas can be accessed by normal/admin users.
Figure 82. File System Structure in LD 800DN
File System Security

The LD 800DN file system has two security levels — Admin mode and Normal
mode. Depending on the security level allowed for different users, they can have
access to different files and directories.
202 9ARD000014-600 A
Section 6 Linking Device LD 800DN User Accounts on LD 800DN
User Accounts on LD 800DN

The LD 800DN contains two user accounts on initial power up, namely the
Administrator Mode and the Normal Mode.
Administrator Mode
In Administrator mode, the Admin user has full access to the file system through
FTP. This enables to access areas of the file system that are restricted or inaccessible
for Normal mode users.
The default password is DNmemmap. Replace this with a password that

conforms with your organization's security policy at the first possible
opportunity. Failure to replace the default password makes the system susceptible
to unauthorized access.Refer to the Password Security topic in System 800xA
Administration and Security (3BSE037410*) for recommendations on
establishing a password security scheme.
The account login details are:
• User Name = Admin
• Default Password = DNmemmap
The default password can be changed by changing the password files. The
Administrator can access the password files to add or remove users or change
passwords. Refer Password Files on page 207 for more details.
Normal Mode
The Normal mode is recommended for normal user operation. In this mode, the
Web pages and other settings are protected from unauthorized modification. In
normal mode the FTP services are only enabled if there is a subdirectory called
\user. When a normal user connects via FTP, this directory is the root directory.
Only the files and subdirectories in this directory can be accessed.
9ARD000014-600 A 203
Pre-existing Directories and Files Section 6 Linking Device LD 800DN
The default password is EIPnetwork. Replace this with a password that conforms
with your organization's security policy at the first possible opportunity. Failure
to replace the default password makes the system susceptible to unauthorized
access. Refer to the Password Security topic in System 800xA Administration and
Security (3BSE037410*) for recommendations on establishing a password
security scheme.
The Normal Mode account login details are:

• User Name = guest
• Default Password = EIPnetwork
The default password can be changed by changing the password files. The
Administrator can access the password files to add or remove users or change
passwords. Refer Password Files on page 207 for more details.
Pre-existing Directories and Files

The following directories are present on the LD 800DN upon first power up:
• \pswd
• \user
• \web
• \web\styles
• \user\pswd
The following files are also present on the LD 800DN:
• \pswd\ad_pswd.cfg
• \ethcfg.cfg
• \index.htm
• \user\pswd\sys_pswd.cfg
LD 800DN System Files

The LD 800DN uses the system files for configuration purposes. These files are not
used to store any user data or application data. These pre-existing files are ASCII
204 9ARD000014-600 A
Section 6 Linking Device LD 800DN LD 800DN System Files
files and can be edited using any text editor. However, the LD 800DN must undergo
a power cycle for the changes to take effect.
Depending on the security settings, the system files may or may not be accessible
for normal users. System files include:
• Configuration Files (see Configuration Files on page 205).
• Password Files (see Password Files on page 207).
Configuration Files
ethcfg.cfg — This file contains the network configuration data and is read by the
module at start up. The settings in this file are affected by SSI commands. The
components and format of the file is shown in Table 34.
Table 34. ethcfg.cfg Configuration File Format
Format Component
[File path] This is optional, and redirects the
\user\eth_settings.cfg contents of the file to another file path.
In this case the new file path is
\user\eth_settings.cfg
The new path permits normal users to
access the network configuration
settings.
[IP address] Denotes the IP address. In this case, the
10.10.12.212 address is 10.10.12.212
[Subnet mask] Denotes the subnet mask. In this case, it

255.255.255.0 is
255.255.255.0
[Gateway address] Denotes the gateway address. In this
0.0.0.0 case, it is
0.0.0.0
9ARD000014-600 A 205
LD 800DN System Files Section 6 Linking Device LD 800DN
Table 34. ethcfg.cfg Configuration File Format (Continued)
Format Component
[DHCP/BOOTP] DHCP/BootP Enabled — ON
OFF DHCP/BootP Disabled — OFF
In this case it is set as ‘OFF’
[Speed] Auto — Autonegotiation is used
Auto 100 — Sets the module speed at
100mbits
10 — Sets the module speed at 10mbits
In this case, Autonegotiation is used
[Duplex] Auto — Autonegotiation is used
Auto Full — Sets the module to operate at full
duplex mode
Half — Sets the module to operate at
half duplex.
In this case, Autonegotiation is used
ip_accs.cfg — It is possible to configure which IP addresses and what protocols are

allowed for connecting to the module. This information is stored in the ip_accs.cfg
file.
The file contains one or several of these headers:
• [Web]
• [FTP]
• [Ethernet/IP]
• [All]
Under each header the allowed IP addresses are written. The wildcard '*' can be
used to allow series of IP addresses. If a protocol header is not given, then the
system uses the configuration set under the [All] header. If the [All] header is not
given, then the protocol does not accept any connections.
Example for ip_accs.cfg is shown in Table 35.
206 9ARD000014-600 A
Section 6 Linking Device LD 800DN LD 800DN System Files
Table 35. Example for ip_accs.cfg configuration file
ip_accs.cfg
[Web]
10.10.12.*
10.10.13.*
[FTP]
10.10.12.*
[All]
*.*.*.*
The above example allows all IP addresses beginning with 10.10.12 to access all
protocols in the module. IP numbers beginning with 10.10.13 will not be able to
access the FTP server. EtherNet/IP servers will accept connections from any IP
address. The contents of the file can be redirected by placing the line '[File path]' on
the first row, and a file path on the second.
Password Files
sys_pswd.cfg and ad_pswd.cfg — These files contain user/password information.
Data for normal mode users is in sys_pswd.cfg (located in \user\pswd). Data for
administrator mode users is in ad_pswd.cfg (located in \pswd). These files and
directories are protected from Web browser access.
The file format for sys_pswd.cfg and ad_pswd.cfg is shown in Table 36.
9ARD000014-600 A 207
LD 800DN System Files Section 6 Linking Device LD 800DN
Table 36. Password Files Format
Password File
User1:password1
User2:password2
...
...
UserN:passwordN
Example of the contents of a password file:

JohnQ:Password
In this example, the username is JohnQ, and the password is Password. If no colon
separator is present, then the password will be same as the username.
web_accs.cfg — Files within the file system can be protected from web access
through username/password protection. To put username/password protection for
required files, the file web_accs.cfg must be located in the same directory as the
files, subdirectories to be protected.
The file format for web_accs.cfg is the same as that for the ad_pswd.cfg and
sys_pswd.cfg files, except that the optional parameter Auth Name can be added.
The value of this parameter is presented in the login window as the Realm. If it is
not given, the requested file/pathname is presented instead.
Example of web_accs.cfg:
User:Password
[Auth Name]
(Message goes here)
The contents of this file can be redirected by placing the line [File path] on the first
row, followed by a list of password files.
208 9ARD000014-600 A
Section 6 Linking Device LD 800DN Run/Idle State
Run/Idle State
The linking device LD 800DN has two modes of operation — Run and Idle.
In Run mode, the LD 800DN sends output data to the slaves and receives input data.
During normal operation, it must be in Run Mode.
In Idle mode, the LD 800DN receives input data from the slaves but it does not send
output data to the DeviceNet slave devices. In Idle mode the LD 800DN’s
configuration can be changed.
The LD 800DN module powers up in Idle mode. CI873 sets it into Run mode after
configuration, before starting I/O communication. A re-configuration performed
from Control Builder, requires LD 800DN to be put in Idle mode. These state
changes are handled by CI873.
The LD 800DN linking device has to be in Idle mode before modifying any
configuration data on it. Re-configuring the DeviceNet parameters on an
LD 800DN does not disrupt the flow of input data from the DeviceNet slave
devices to the CI873. However, no output data is applied from the linking device
to the DeviceNet slave devices while the linking device is in Idle mode.
9ARD000014-600 A 209
Automatic Device Recovery Section 6 Linking Device LD 800DN
Automatic Device Recovery

The Automatic Device Recovery (ADR) is introduced in Automatic Device
Recovery on page 44.
The ADR feature consists of Address Recovery and Configuration Recovery.
Address Recovery
The Address Recovery is enabled when the Automatic Device Recovery (ADR)
parameter of the Linking Device is enabled. By disabling ADR, it also disables
Address Recovery.
The LD 800DN executes the following steps to perform an address recovery:
1. On detecting the loss of a slave, LD 800DN begins to monitor MAC ID 63 for
an identical device. Add an identical device to the network at MAC ID 63 as
required.
2. The LD 800DN then verifies whether the newly added device is exactly the
same kind as the lost slave device. This depends on the electronic key setting of
the device.
3. Upon successful verification, LD 800DN changes the MAC ID of the new
device from 63 to that of the lost slave device.
If a slave device has a switch to change its node address, then Address Recovery
may not work. In this case, ensure that the switch is set to that of the lost slave
device.
If two devices of the same type are replaced simultaneously, the LD 800DN
disables the Address Recovery feature. In this case, ensure that the new devices
have the same addresses as the corresponding earlier devices.
210 9ARD000014-600 A
Section 6 Linking Device LD 800DN Configuration Recovery
Configuration Recovery
Configuration Recovery can be enabled only if the ADR parameter is enabled.
Configuration Recovery is enabled by enabling the Config Recovery parameter of
the DeviceNet slave device. In Configuration Recovery, the DeviceNet device
configuration stored in LD 800DN is written into the slave device that replaces the
lost slave device.
When Configuration Recovery is disabled, newly inserted DeviceNet device will
not be configured with the existing configuration parameters.
Memory Space Limitations for Configuration Recovery

Every Config Recovery enabled slave device, which has user configurable
parameters, occupy some memory space in the linking device. The size of memory
available for this, in LD 800DN, is limited to 130560 bytes.
If the total size of the user configurable parameters of all Config Recovery enabled
devices exceed 130560 bytes, then Configuration Recovery will not work for the
DeviceNet devices. This is stated in a warning, shown during download, along with
the hardware tree positions of the devices. When this warning appears, perform
either of these:
• Cancel the process and go online to disable the configuration recovery for some
slaves in Control Builder, so that other required devices can get this feature
enabled.
• Ignore the warning. In this case, the Configuration Recovery will not be
enabled for some devices and they will have the warning in UnitStatus —
Keeper space exceeded. ADR not configured.
Configuring ADR from Control Builder

Consider the following factors when you configure the ADR feature from Control
Builder:
• For ADR feature to work, enable the parameter ADR in the hardware editor of
LD 800DN. By disabling this parameter, it disables Address Recovery and
Configuration Recovery for all DeviceNet devices.
9ARD000014-600 A 211
Configuring ADR from Control Builder Section 6 Linking Device LD 800DN
• Address Recovery cannot be disabled individually for each configured

DeviceNet slave device. However, it can be disabled for all DeviceNet slave
devices by disabling the ADR parameter on LD 800DN.
• Configuration Recovery can be individually enabled or disabled for each
DeviceNet slave through the Config Recovery parameter on the DeviceNet
device. For this, the ADR parameter on LD 800DN must be kept enabled.
212 9ARD000014-600 A
Section 7 Technical Data
General Technical Data

The general technical data that need to be considered while Connecting to the
DeviceNet and EtherNet/IP devices are:
• CI873 communicates only on Auto negotiation. Due to this it is recommended
and mandatory to configure the switch port to which CI873 is connected as
Auto negotiation.
• For the CI873 to connect to the DeviceNet devices and EtherNet/IP devices, the
EDS file of the devices should have all the mandatory connection information
as mentioned in Section , Device Import Wizard.
• Tag based Class 1 connection information should be available in the EDS file
of the Logix 5000 Controllers for communication with the CI873 as mentioned
in Section , Device Import Wizard.
• The number of I/O modules that can be connected under EtherNet/IP or
DeviceNet device adapter type device is 63.
• The number of configuration parameters supported per EtherNet/IP or
DeviceNet device is 1000.
• The CI873 supports listen only connection with the EtherNet/IP device,
provided that there is already exclusive owner connection in the device.
• The CI873 does not support redundant owner connections for the EtherNet/IP
devices. That is, at the same time both primary and backup CI873 cannot
connect to the same assembly object of the EtherNet/IP device even though the
device supports such connections.
• Read Only and Monitoring Parameters in EDS file of the
EtherNet/IP/DeviceNet device are not supported. That is, DIW ignores such
parameters while generating the Hardware type from the EDS file.
9ARD000014-600 A 213
Technical Data for LD 800DN Section 7 Technical Data
• Total number of Input and Output Bytes along with channel status bytes of the
device configured under one CI873 should not exceed more than 72Kb.
• Configuration assembly (grouping of parameter configuration for an device)
size of 512 bytes is supported per EtherNet/IP/device and 200 bytes is
supported per DeviceNet device.
• Maximum CIP connections supported (including Class 1 and Class 3) per
EtherNet/IP Device is 20.
• The CI873 supports total of 128 connections.
• The CI873 only supports devices which uses EtherNet/IP encapsulation of CIP.
It does not support PCCC, Modbus encapsulation.
• CI873 cannot accept class 1 and class 3 connections from any scanner. That is,
it can act only as master originating CIP connections to EtherNet/IP devices.
• Maximum 1000 bytes per Connection point based Class 1 Connection is
supported where O->T can have maximum of 500 bytes and T->O can have
maximum of 500 bytes.
• Supports only 10 CIP connections with 10ms RPI.
• CI873 does not support FTP commands.
Technical Data for LD 800DN

The technical data that need to be considered while configuring an LD 800DN
linking device (for DeviceNet) are:
• One CI873 supports maximum of 4 LD 800DN.
• The maximum number of input bytes supported by LD 800DN is 496 bytes. If
the total number of input bytes of all the DeviceNet slaves configured under the
linking device exceeds 496 bytes, then the download is stopped.
• The maximum number of output bytes supported by LD 800DN is 492 bytes. If
the total number of output bytes of all the DeviceNet slaves configured under
the linking device exceeds 500 bytes, then the download is stopped.
• Multiple CI873 cannot communicate to same LD 800DN data. That is more
than one CI873 cannot be connected to same LD 800DN at any time.
• The maximum number of DeviceNet connections per device is restricted to 5.
214 9ARD000014-600 A
Section 7 Technical Data Technical Data for connection to Allen Bradley Logix 5000 Series PLC on
Technical Data for connection to Allen Bradley Logix 5000

Series PLC on EtherNet/IP
The technical data that need to be considered while connecting to Allen Bradley
Logix 5000 PLC's on EtherNet/IP are:
• EtherNet/IP supports three Class 1 connection and three Class 3 tag per Allen
Bradley Logix 5000 series PLC. The CI873 supports three Class 3 tags with
100ms cycle time.
• The data transfer, using the Class 3 connection, will be slower than the Class 1
connection.
• The Class 3 connection is not supported for any EtherNet/IP devices except
Allen Bradley Logix 5000 series PLC. The CI873 uses tag based Class 3 to
write data to it.
• The maximum number of bytes supported for Class 1 read tag is 496 and for
Class 3 write tag is 432.
CI873 supports tag based CIP communication with Allen Bradley Logix 5000
series controllers, catalog numbers for the same are mentioned below: 
-1756 ControlLogix, 1756 GuardLogix, 1768 CompactLogix, 
1769 CompactLogix, 1789 SoftLogix.
CI873 does not support communication with MicroLogix series controllers as it
does not support Tag based communication, instead use PCCC commands
encapsulated in a EtherNet/IP message.
Technical data for S200 IO modules

The technical data that need to be considered while configuring S200 IO Modules
are:
• Maximum of 30 200-AENTR Adapters can be added under CI873.
• Each S200 IO module will consume one CIP connection.
9ARD000014-600 A 215
Performance Data Section 7 Technical Data
Performance Data
• The CI873 can handle maximum of 10 CIP connections with 10ms RPI.
However it can handle maximum of 128 CIP connections.
• Reaction time of CI873, that is, the time from changed input channel to the
time setting an output channel shall be less than 100ms at a maximum CI873
CPU Load of 80%, provided that the data is sent over the connection operating
at RPI of 50ms or less.
• Data throughput of 1000 CIP I/O packets Receive/Sec and 500 CIP I/O Packets
sent/sec can be achieved at an optimum load of 85%. Each I/O packet can have
data size ranging from 4 to 500 bytes.
• Redundancy Switchover time is 120ms for 10 CIP connections operating at
10ms RPI, 93% CI873 CPU Load i.e the time I/O communication stops in
primary to the time I/O communication starts in switched primary.
216 9ARD000014-600 A
Section 8 Hardware Connections
Connect CI873 on CEX Bus

CI873 should be physically present on the CEX Bus once it is configured in the
Control Builder. Figure 83 displays the complete setup.
Figure 83. I/O Devices connected through LD 800DN
9ARD000014-600 A 217
Connect CI873 to LD 800DN Section 8 Hardware Connections
Connect CI873 to LD 800DN

Connectors
The following are the connectors for LD 800DN:
– Power.
– DeviceNet.
– Ethernet RJ45.
– Auxiliary RS-232 9 Pin D-Subminiature.
Power
Figure 84 shows the LD 800DN power connectors.
Figure 84. Power Connector
Table 37 shows the Pin definitions for Power Connector.
Table 37. Power Connector Pin Definitions
Pin Connection
1 24V DC +
2 24V DC Common
Use Phoenix connector part number MSTB 2,5/2-ST-5,08 ABGY.
218 9ARD000014-600 A
Section 8 Hardware Connections DeviceNet
DeviceNet
Figure 85 shows the DeviceNet connectors.
Figure 85. DeviceNet Pinout
Table 38 shows signals assigned to the DeviceNet pins.
Table 38. DeviceNet Pinout
Pin Signal
1 V-
2 CAN_L
3 Shield
4 CAN_H
5 V+
Use Phoenix connector part number MSTB 2,5/5-ST-5,08-ABGYAU.
9ARD000014-600 A 219
Ethernet RJ45 Section 8 Hardware Connections
Ethernet RJ45
Figure 86 shows the pinout details for RJ45.
Figure 86. RJ45 Pinout
Table 39 shows signals assigned to the RJ45 pins.
Table 39. RJ45 Pinout
Pin Signal
1 TD+
2 TD-
3 RD+
4 Termination
5 Termination
6 RD-
7 Termination
8 Termination
220 9ARD000014-600 A
Section 8 Hardware Connections Auxiliary RS-232 9 Pin D-Subminiature
Auxiliary RS-232 9 Pin D-Subminiature

Figure 87 shows the pinout details for RS-232 9 pin D-Subminiature.
Figure 87. RS232 9 Pin
Table 40 shows signals assigned to the RS232 9 pins.
Table 40. RS232 9 Pin
Pin Signal
1 NC
2 Receive
3 Transmit
4 NC
5 Signal Ground
6 NC
7 NC
8 NC
9 NC
9ARD000014-600 A 221
Auxiliary RS-232 9 Pin D-Subminiature Section 8 Hardware Connections
222 9ARD000014-600 A
Appendix A Troubleshooting EDS File
Table 41 shows the messages that are displayed during the import of EDS files using
the Device Import Wizard:
Table 41. Messages - Import of EDS Files
Applicability Additional
Sl
Message Reason Based on Device Information and
No
Classification Workaround
1 There are important During a re-import, EtherNet/IP/ Import will abort. 
changes in some the major revision of DeviceNet Start a fresh import of
basic device the EDS file is the EDS file in a new
information between different from the hardware library.
the current EDS EDS file used in first
file. Major import.
revision has been
changed (1-->2).
Please cancel the
process and use a
different new
Library to import
the revised version
of EDS.
2 The EDS file used The file used to Modular Import will abort. 
to invoke the invoke the wizard is EtherNet/IP/ Start the import with
wizard is a modular an IO file and not an DeviceNet adapter EDS file, and
IO. Please invoke adapter. not with IO EDS file.
the wizard with an
adapter EDS file
and proceed with
the import process
9ARD000014-600 A 223
Table 41. Messages - Import of EDS Files (Continued)
Sl
No
3 There is more than There are more Modular Deselect one adapter
one adapter than one adapter EtherNet/IP/ to proceed with the
selected. Please selected by the user DeviceNet import.
select one and only which is not
one adapter with allowed.
the IO modules and
proceed with the
import process
4 An adapter of the Adapter file from a Modular Import will abort.
similar name from a different folder with EtherNet/IP/ During re-import,
folder other than the same name is DeviceNet select the adapter file
the current folder not allowed. This is from the folder that
has been imported. observed during a was from the same
Please select the re-import. location as selected
adapter from the during fresh import.
earlier folder or
change the name of
the adapter EDS
being imported and
try again
5 Please cancel the Major revision has EtherNet/IP/ Import will abort. 
process and use a been changed in  DeviceNet Start a fresh import of
different/new re-import which is the EDS file in a new
Library to import not allowed. hardware library.
the revised version
of EDS file.
224 9ARD000014-600 A
Sl
No
6 The eds file <eds The particular IO Modular The IO module that is
file name> is not module file is not EtherNet/IP/ incompatible with the
compatible with the compatible with the DeviceNet adapter shall not be
adapter being adapter which is considered, and the
imported. The selected by the import will continue.
import will proceed user. So the import
with the other will proceed by
compatible IO avoiding that
modules and adapter particular file.
7 Atleast one None of the IO Modular Select the IO module
selected IO eds modules are EtherNet/IP/ that is compatible with
file Should be compatible with the DeviceNet the adapter to
compatible with the adapter which is continue the import.
adapter being selected.
imported. The
import will not
proceed only with
adapter
8 The EDS file name The EDS file name EtherNet/IP/ Import will abort. 
used to invoke the has illegal DeviceNet Rename the EDS file
wizard has special characters which so that it does not
characters outside are not allowed by have special
the permissible DIW characters. After this,
ASCII range. start the import for the
Proceeding with the EDS file.
import would lead
to an error in
saving the
generated HWD file.
Please modify the
EDS file name and
proceed with the
import process.
9ARD000014-600 A 225
Sl
No
9 IO files can be Import has been Modular Import will abort. 
imported only along started with IO EDS EtherNet/IP/ Start the import with
with corresponding file instead of DeviceNet an adapter EDS file in
adapter files! adapter EDS file in case of Modular IO.
case of Modular IO
10 The wizard cannot Any of the EtherNet/IP/ Import will abort. 
proceed as the file mandatory fields in DeviceNet Contact the vendor to
is not as per CIP File Section get device EDS files
specifications. required in EDS file with all the mandatory
There are required is missing or fields fields.
fields in the File available as not as
section that are per CIP
missing. Please specifications
restart the wizard (example: create
with the correct date, create time
EDS file. etc.)
11 The wizard cannot Any of the EtherNet/IP/ Import will abort. 
proceed as the file mandatory fields in DeviceNet Contact the vendor to
is not as per CIP Device Section get device EDS files
specifications. required in EDS file with all the mandatory
There are required is missing or fields fields.
fields in the available as not as
Device section that per CIP
are missing. Please specifications
restart the wizard (example: vendor
with the correct code, product code
EDS file. etc.)
226 9ARD000014-600 A
Sl
No
12 An error occurred Erroneous EDS file. EtherNet/IP/ Import will abort. 
while the EDS file Any of the DeviceNet Contact the vendor to
was parsed. mandatory fields in get device EDS files
Unfortunately no EDS file is missing with all the mandatory
more information or fields available as fields.
about the error are not as per CIP
available. Please specifications.
check the EDS file
13 Error occurred This can occur due EtherNet/IP/ Import will abort.
to import if user DeviceNet Check the DIW log for
performs actions more information.
before the parsing Then start a fresh
activity is import to come out of
complete.Check the the problem.
DIW log for more
information
14 Param section is Any of the EtherNet/IP/ Import will abort. 
not as per CIP mandatory fields in DeviceNet Contact the vendor to
standard. Please Parameter Section get device EDS files
retry with the required in EDS file with all the mandatory
correct EDS file is missing or fields fields.
available as not as
per CIP
specifications.
9ARD000014-600 A 227
Sl
No
15 <EDS file name> The IO Info section DeviceNet Import will abort. 
doesn't have any is not present in Contact the vendor to
connection names. DeviceNet EDS file get device EDS files
Import cannot or the Connection with all the mandatory
proceed further! name in IO Info fields.
Section required in
EDS file is missing
or fields available as
not as per CIP
specification
16 Invalid device The connection EtherNet/IP Import will abort. 
connections. Please manager section is Contact the vendor to
use correct EDS not found in EDS get device EDS files
file and try again! file with all the mandatory
fields.
17 All the IO Modules This shall come for EtherNet/IP/ Import will abort. 
importing are not IO modules EDS Modular Contact the vendor to
having connections. files if they do not get IO EDS files with
Import cannot have connections in all the Connection
proceed further Connection information available.
Manager
18 The following IO This shall come for EtherNet/IP/ Proceed with the
Modules does not IO modules EDS Modular import by deselecting
have connections files if they do not the IO modules that
<Rejected Module have valid do not have valid
name> So the connections in connections. Contact
modules are not Connection the vendor to get IO
added to the Manager. EDS files with all the
parsing list connection
information available
228 9ARD000014-600 A
Sl
No
19 The device has no This shall come for DeviceNet/ Import will abort. 
input and output adapter EDS files if Modular Contact the vendor to
data. Import cannot they do not have get adapter EDS files
proceed further. valid Input and with all the Input and
Output data in Output data available.
IO_Info section
20 <EDS file name> has If in the EDS file, General Purpose Import will abort. 
no valid the IO Info section Device DeviceNet Contact the vendor to
connections in the is not present or get device EDS files
eds file. Import they do not have with all the mandatory
cannot proceed valid Trigger types fields.
further. in IO_Info section.
21 <EDS file name> has If the connection General Purpose Import will abort. 
no valid Class1 manager is not Device Contact the vendor to
connections in the present in EDS file EtherNet/IP get device EDS files
eds file. Import or they do not have with all the mandatory
cannot proceed valid Class 1 fields.
further. connections
22 Connection Manager Some entries in General Purpose Import will abort. 
section is not as Connection Device Contact the vendor to
per CIP standard. Manager section is EtherNet/IP get device EDS files
Please retry with missing or empty in with all the mandatory
the correct EDS EDS file for fields.
file example: name,
connection path,
trigger type etc.
9ARD000014-600 A 229
Sl
No
23 Connection Path for Connection Path in General Purpose Import will abort. 
<connection name> Connection Device Contact the vendor to
connection is not Manager section is EtherNet/IP get device EDS files
as per CIP invalid and not as with all the valid
standard. Please per CIP entries.
retry with the specification in EDS
correct EDS file file
24 Device The EDS file does DeviceNet/ Import will abort. 
Classification not have device Modular Contact the vendor to
section is faulty. classification field to get device EDS files
Retry with correct classify it as with all the mandatory
EDS file DeviceNet or fields.
EtherNet/IP
25 Descriptor field of Descriptor field of General Purpose Import will abort. 
Param Class section param class section Device Contact the vendor to
is not present. in EDS file is empty. EtherNet/IP/ get device EDS files
Please retry with DeviceNet with all the mandatory
correct EDS file. fields with non-empty
entries.
26 Member size and If the member size Modular Import will abort. 
Member reference of and member EtherNet/IP/ Contact the vendor to
assembly entry reference fields of DeviceNet get device EDS files
cannot be null assembly section in with all the mandatory
together. Please EDS file is empty. fields without any
retry with a empty entries.
correct EDS file
230 9ARD000014-600 A
Sl
No
27 Member size and If the member size General Purpose Import will abort. 
Member reference of and member Device DeviceNet Contact the vendor to
assemExa entry reference fields of get device EDS files
cannot be null assemExa section with all the mandatory
together. Please in EDS file is null fields without any
retry with a empty entries.
correct EDS file
28 Variant entries are If some entries in General Purpose Import will abort. 
not as per variant field is Device Contact the vendor to
standard. Please empty in the EDS EtherNet/IP/ get device EDS files
retry with correct file. For example: DeviceNet with all the mandatory
EDS file selector, value, fields with non-empty
entry etc. entries.
29 CfgAssembly field Config assembly DeviceNet Import will abort. 
is not as per field of EDS file is Contact the vendor to
specifications. empty. get device EDS files
Please retry with with all the mandatory
correct EDS file. fields with non-empty
entries.
30 There is a problem Refer the DIW log EtherNet/IP/ Import will abort.
in parsing of file for information DeviceNet Refer the DIW log file
files, please refer for information.
the Log for more
information.
31 The 'size' field in Size field of DeviceNet Import will abort. 
the Producing producing Contact the vendor to
Connection Entry is connection in EDS get device EDS files
null. Please retry file is null with all the mandatory
with a valid EDS fields without any
file. empty entries.
9ARD000014-600 A 231
Sl
No
32 The value of the Size field of DeviceNet Import will abort. 
'size' field in the producing Contact the vendor to
Producing connection in EDS get device EDS files
Connection Entry is file has an invalid with all the valid
invalid. Please entry entries.
retry with a valid
EDS file.
33 The value of the Number of DeviceNet Import will abort. 
'Number of significant bits field Contact the vendor to
Significant bits' of producing get device EDS files
field in the connection in IO with all the valid
Producing info section of EDS entries.
Connection Entry is file has an invalid
invalid. Please entry
retry with a valid
EDS file.
34 The 'No. of Number of DeviceNet Import will abort. 
significant bits' significant bits field Contact the vendor to
field in the of producing get device EDS files
Producing connection in IO with all the mandatory
Connection Entry is info section of EDS fields with non-empty
null. Please retry file is empty entries.
with a valid EDS
file.
35 The 'Compatible I/O Compatible IO DeviceNet Import will abort. 
mask field' field mask field of Contact the vendor to
in the Producing producing get device EDS files
Connection Entry is connection entry of with all the valid
invalid. Please IO info section has entries.
retry with a valid an invalid entry
EDS file.
232 9ARD000014-600 A
Sl
No
36 The 'Compatible I/O Compatible IO DeviceNet Import will abort. 
mask field' field mask field of Contact the vendor to
in the Producing producing get device EDS files
Connection Entry is connection entry of with all the mandatory
null. Please retry IO info section is fields with non-empty
with a valid EDS empty entries.
file.
37 The 'name' field in Name field of DeviceNet Import will abort. 
the Producing producing Contact the vendor to
Connection Entry is connection entry in get device EDS files
null. Please retry IO info section is with all the mandatory
with a valid EDS null fields without any
file. empty entries.
38 The 'connection The connection DeviceNet Import will abort. 
path size' field in path size field in the Contact the vendor to
the Producing producing get device EDS files
invalid. Please IO info section has fields with all valid
retry with a valid an invalid entry. entries.
EDS file.
39 The 'connection “The connection DeviceNet Import will abort. 
path size' field in path size field in the Contact the vendor to
the Producing producing get device EDS files
null. Please retry IO info section is fields with non-empty
with a valid EDS empty. entries.
file.
9ARD000014-600 A 233
Sl
No
40 The 'help string' The help string field DeviceNet Import will abort. 
field in the in producing Contact the vendor to
Producing connection of IO get device EDS files
Connection Entry is info section is null. with all the mandatory
null. Please retry fields without any
with a valid EDS empty entries.
file.
41 Invalid Epath in Epath field in assem Modular Continue the import
assembly section. section of EDS file EtherNet/IP/ with this message.
Do you want to has invalid entry. DeviceNet Else, import will be
continue? aborted, and contact
the vendor to get
device EDS files with
all the valid entries.
42 Invalid size in Size field in assem Modular Continue the import
assembly section. section of EDS file EtherNet/IP/ with this message.
Do you want to has invalid entry DeviceNet Else, import will be
the vendor to get
43 Invalid descriptor Descriptor field in Modular Continue the import
in assembly assem section of EtherNet/IP/ with this message.
section. Do you EDS file has invalid DeviceNet Else, import will be
want to continue? entry aborted and contact
the vendor to get
234 9ARD000014-600 A
Sl
No
44 Invalid member Member size field Modular Continue the import
size in assembly has invalid entry in EtherNet/IP/ with this message.
section. Do you assem section of DeviceNet Else, import will be
want to continue? EDS file aborted and contact
the vendor to get
45 Invalid Switch Switch selector field General Purpose Continue the import
selector, in in variants section Device with this message.
variants. Do you of EDS file has EtherNet/IP/ Else, import will be
want to continue? invalid entry DeviceNet aborted and contact
the vendor to get
46 Invalid selection Selection entry is General Purpose Continue the import
entry, in variants. invalid in variants Device with this message.
Do you want to section of EDS file. EtherNet/IP/ Else, import will be
continue? DeviceNet aborted and contact
the vendor to get
47 Invalid IO mask, in IO mask field has DeviceNet Continue the import
IO section. Do you an invalid entry in with this message.
want to continue? IO section of EDS Else, import will be
file aborted and contact
the vendor to get
9ARD000014-600 A 235
Sl
No
48 Invalid producer, Producer field in IO DeviceNet Continue the import
in IO section. Do section of EDS file with this message.
you want to has an invalid entry Else, import will be
the vendor to get
49 Invalid consumer, Consumer field in DeviceNet Continue the import
in IO section. Do IO section of EDS with this message.
you want to file has an invalid Else, import will be
continue? entry aborted, and contact
the vendor to get
50 First character Space cannot be EtherNet/IP/ Continue the import
cannot be a space the first character in DeviceNet with this message.
product description Else, import will be
or product name aborted, and contact
the vendor to get
51 Please enter only Only alpha numeric EtherNet/IP/ Continue the import
aplha numeric text text is allowed for DeviceNet with this message
description field after specifying
correct syntax.
52 Product Name should If the product name EtherNet/IP/ Continue the import
be aplha numeric is not alpha numeric DeviceNet with this message
text for <EDS file text after specifying
name> correct syntax.
236 9ARD000014-600 A
Sl
No
53 Product name in the Dots and spaces EtherNet/IP/ Continue the import
Hwd should not not allowed in DeviceNet with this message
contain only product name in after specifying
dots/spaces. hwd field correct syntax.
54 <Product name> is a Two modules have EtherNet/IP/ Continue the import
duplicate module, same product name DeviceNet with this message
please change the which is not after specifying
product name and allowed. correct syntax.
proceed with the
import process.
55 Catalog number for Catalog number for EtherNet/IP/ Continue the import
the device is not the device is empty. DeviceNet with this message.
present. Hence
selection would be
changed to product
name
56 Please enter a If the product name EtherNet/IP/ Continue the import
valid product name. specified is not DeviceNet with this message
valid. after specifying valid
Product name.
57 First character of If the first character EtherNet/IP/ Continue the import
the Product Name in the product name DeviceNet with this message
cannot be a space field is a space. after specifying
correct syntax.
58 First character of If the first character EtherNet/IP/ Continue the import
the Description in the description DeviceNet with this message
cannot be a space field is a space. after specifying
correct syntax.
9ARD000014-600 A 237
Sl
No
59 Product Description If the product EtherNet/IP/ Continue the import
should be aplha description field is DeviceNet with this message
numeric text not an after specifying
alphanumeric text correct syntax.
60 You cannot uncheck Unchecking a Modular Continue the import
the devices that module which was EtherNet/IP/ with this message.
were enabled during imported earlier is DeviceNet
the first import. not allowed.
61 Select atleast one If no device is Modular Continue the import
device to proceed selected from the EtherNet/IP/ selecting atleast one
with the import tree DeviceNet device.
62 Please select the If the adapter file is Modular Continue the import
adapter and proceed not selected while EtherNet/IP/ selecting the adapter.
with the import doing a modular DeviceNet
import.
63 Please select If none of the Modular Continue the import
atleast one IO modular IO files is EtherNet/IP/ selecting atleast one
module and proceed selected from the DeviceNet IO file.
with the import! tree while doing a
modular import.
64 Something has been This message EtherNet/IP/ Continue the import
changed in the shows to the user to DeviceNet with this message by
parameter select "Ok" or selecting "ok".
definition dialog. "Cancel" to the user
Are you sure that to intimate him that
you will discard some changes are
happen in the
Parameter Edit GUI.
238 9ARD000014-600 A
Sl
No
65 The enumrange This message EtherNet/IP/ Continue the import
parameter is comes when user DeviceNet with this message
currently in use clicks delete a after specifying valid
parameter which is enum range
been referred by a parameter.
Channel.
66 Overflow value When overflow EtherNet/IP/ Continue the import
should be greater value entered is DeviceNet with this message
than max less than the after specifying valid
maximum value overflow value for the
parameter.
67 Underfolw value when underflow EtherNet/IP/ Continue the import
should be less than value entered is DeviceNet with this message
Min more than the after specifying valid
minimum value. underflow value for
the parameter.
68 Min value should be When minimum EtherNet/IP/ Continue the import
in between Max and value entered is not DeviceNet with this message
Underfolw in the range of after specifying valid
maximum and minimum value for the
underflow value. parameter.
69 Max value should be when maximum EtherNet/IP/ Continue the import
in between Min and value entered is not DeviceNet with this message
Overfolw in the range of after specifying valid
minimum and maximum value for
overflow value. the parameter.
9ARD000014-600 A 239
Sl
No
70 The value entered When the value EtherNet/IP/ Continue the import
already exists entered is already DeviceNet with this message
existing in the range after specifying valid
values for range value for the
enumrange parameter.
parameter
71 Value is not within When the value EtherNet/IP/ Continue the import
Min and Max range entered is not in the DeviceNet with this message.
minimum and
maximum range for
the enumrange
parameter.
72 This is not a valid When the link path EtherNet/IP/ Continue the import
Link path entry is according to the DeviceNet after specifying a valid
Epath syntax. link path value for the
parameter.
73 Out of Range When the value EtherNet/IP/ Continue the import
entered is in the DeviceNet after specifying a valid
audiotape range in datatype value for the
minimum, maximum parameter.
and default values.
74 invalid entry When the value EtherNet/IP/ Continue the import
entered is not DeviceNet with this message.
having valid ASCII
characters.
240 9ARD000014-600 A
Sl
No
75 The default value When the default EtherNet/IP/ Continue the import
is no longer in the value of the DeviceNet with this message.
enum values, parameter is not
therefore it will available in the
automatically be range values.
changed into
nearest value
76 Maximum number of When the number EtherNet/IP/ Continue the import
entries is reached of the entries DeviceNet with this message.
exceeds the total
number of
maximum number
of the values for the
enum and enum
range parameters.
77 This will delete To create the EtherNet/IP/ Continue the import
all the existing channels based on DeviceNet with this message.
channels! the selection
78 Out of Range When the value EtherNet/IP/ Continue the import
entered is not in the DeviceNet with this message.
range of the
minimum and
maximum value.
79 All channels When datatype is EtherNet/IP Continue the import
created for this changed for the tag with this message.
tag will be lost, in Class 3 for PLC
Do you want to device type.
proceed?
9ARD000014-600 A 241
Sl
No
80 No. of elements When the value is EtherNet/IP/ Continue the import
should be less than more than the DeviceNet with this message.
or equal to limit permissible number
of elements based
on the datatype
selected for the
specific tag.
81 Invalid port number If the value entered EtherNet/IP/ Continue the import
is more than 255 DeviceNet with this message.
82 Cannot deleted as When the EtherNet/IP/ Continue the import
the Connection is connection that DeviceNet with this message.
EDS based wanted to deleted is
from EDS file under
import.
83 Reached Maximum When total number EtherNet/IP Continue the import
limit of 3 Symbolic of tag based with this message.
Tags connections for the
EDS device is more
than 3
84 Delete all the When the value EtherNet/IP/ Continue the import
existing channels entered is less than DeviceNet with this message.
to proceed further the already
available value and
channels for the
same has already
been created.
85 Invalid Input value When the digit EtherNet/IP/ Continue the import
typed is not in the DeviceNet with this message.
range of 0 to 9
242 9ARD000014-600 A
Sl
No
86 No structure If the datatype of EtherNet/IP Continue the import
members are defined class3 tag is with this message
for class3 tag structure and does after specifying
not have any structure members for
elements for the class3 tag.
structure.
87 All the channels To confirm the EtherNet/IP/ Continue the import
that have been deletion of the DeviceNet with this message.
created under all channels.
connections will be
deleted. Do you
want to proceed?
88 There are no When no further EtherNet/IP/ Continue the import
further options for options like byte DeviceNet with this message.
this data type swapping is not
available for some
datatypes.
(example.
Byte=>Dword)
89 Do you really want To confirm the EtherNet/IP/ Continue the import
to delete this deletion of the DeviceNet with this message.
<selected channel channels.
count>channels?
90 Are you sure you To confirm whether EtherNet/IP/ Continue the import
want to cancel? All the user wants to DeviceNet with this message.
changes will be retain the changes
lost! which he made.
91 First character of Space cannot be EtherNet/IP/ Continue the import
Channel name cannot the first character of DeviceNet with this message
be a space a channel name. after specifying proper
character channel name
9ARD000014-600 A 243
Sl
No
92 Channel Name should Only alpha numeric EtherNet/IP/ Continue the import
be aplha numeric text is allowed as DeviceNet with this message
text for <channel channel name. after specifying proper
name> channel name
93 <Name/length/audiot Empty string is not EtherNet/IP/ Continue the import
ape> shouldn't be allowed for channel DeviceNet with this message
empty name, length after specifying proper
datatype etc channel name
94 Collision with Same bit position is EtherNet/IP/ Continue the import
other channels or not allowed for more DeviceNet with this message
out of area than one channel after specifying proper
channel details.
95 Invalid parameter. Syntax for Bit, byte EtherNet/IP/ Continue the import
(Syntax failure) column entry is DeviceNet with this message
wrong after specifying proper
channel details.
96 Problem with the Syntax wrong or EtherNet/IP/ Continue the import
data type, wrong invalid entry in DeviceNet with this message
parameter? length column after specifying proper
value in length
column.
97 There is already a Duplicate channel EtherNet/IP/ Continue the import
channel with this names are not DeviceNet with this message
name. Please choose allowed. after specifying proper
another one. channel name
244 9ARD000014-600 A
Sl
No
98 One or more illegal Channel name EtherNet/IP/ Continue the import
characters are cannot contain DeviceNet with this message
replaced by illegal characters. after specifying proper
underscores (_) Then it will be channel name
replaced by
underscore.
99 Channels Channels are not EtherNet/IP/ Continue the import
initialization initialized properly/ DeviceNet with this message
error There is some
problem with
initializing the
channels.
100 Structure name Structure name is a EtherNet/IP Continue the import
required mandatory field in with this message
Data Size window after specifying proper
structure name
101 Please enter Atleast one EtherNet/IP Continue the import
stucture elements structure member with this message
and datatype is after specifying
required. structure elements.
102 Member name Member name is a EtherNet/IP Continue the import
required mandatory field in with this message
Datasize window after specifying
member name
103 Invalid member name Member name EtherNet/IP Continue the import
should contain only with this message
alphanumeric after specifying
characters proper member name
9ARD000014-600 A 245
Sl
No
104 Member name already No duplicate EtherNet/IP Continue the import
exists! member names with this message
allowed. after specifying
proper member name.
105 Invalid datatype If the datatype EtherNet/IP Continue the import
doesn't match with with this message
the list of datatypes after specifying
provided. proper datatypes.
106 Structure size If the structure size EtherNet/IP Continue the import
exceeds 500 bytes exceeds 500 bytes. with this message
after specifying
proper structure size.
107 Atleast one Class 1 User has not EtherNet/IP Import shall not
or Class 3 channel configured any continue until user
is required to Class 1 or Class 3 creates Class 1 or
proceed further channels. Class 3 channels.
with the import
246 9ARD000014-600 A
Appendix B Troubleshooting CI873 Log
Entries
Connection Error
This is displayed as “I/O Connection Error” for the device in Unit Status of the
device. This is indicated as an error. The messages displayed in CI873 log files for
the Connected related errors with the device are shown in the Table 42. The position
of the device in the hardware tree for which the message is printed, is also printed in
the CI873 logs.
Table 42. Connection Errors
Sl Applicability based on
Message in CI873 Log Description
No device classification
1 Connection in use or Requested connection is already EtherNet/IP
Duplicate Forward available in the slave device.
Open
2 Transport Class and Transport Class (Class 1 0r class 3) EtherNet/IP
Trigger combination and trigger (Cyclic,COS) used in the
not supported connection request is not supported
by the device. Check the EDS file for
correctness.
3 Connection ownership Connection request sent is already EtherNet/IP
conflict available in slave device which is
originated by some other master.
9ARD000014-600 A 247
Connection Error Appendix B Troubleshooting CI873 Log Entries
Table 42. Connection Errors (Continued)
4 Connection not found Data sent to slave device for a EtherNet/IP
at target connection that is not available in
application the slave device. Try closing the
existing connection and establish a
new connection.
5 Invalid connection Connection type (point to point, EtherNet/IP/DeviceNet
type or connection multicast) and connection priority
priority (schedule, High, Low) used in the
connection request is not supported
by the device. Check the EDS file for
correctness.
6 Invalid connection Either the O->T or T-> size specified EtherNet/IP/DeviceNet
size in the control builder configuration
does not match the size in the
physical device. Check the
correctness of the EDS file.
7 RPI not supported or Check the EDS file for the EtherNet/IP
there is a problem correctness.
with connection
time-out multiplier
or production
inhibit time
8 Connection Manager All the connections of the slave EtherNet/IP
cannot support any device have been utilized. No more
more connections connections available.
9 Either the Vendor Id Check the correctness of the EDS EtherNet/IP/DeviceNet
or the Product Code file. Ensure that the device used in
in the key segment the control builder configuration is
did not match the same as the physical device.
device
248 9ARD000014-600 A
Appendix B Troubleshooting CI873 Log Entries Connection Error
10 Product Type in the Check the correctness of the EDS EtherNet/IP/DeviceNet
key segment did not file. Ensure that the device used in
match the device the control builder configuration is
same as the physical device.
11 Major or Minor Check the correctness of the EDS EtherNet/IP/DeviceNet
revision information file. Ensure that the device used in
in the key segment the control builder configuration is
did not match the same as the physical device.
device
12 Invalid connection Check the EDS file for the EtherNet/IP
point specified in correctness. Connection point used
the connection path does not match with the physical
device.
13 Invalid Ensure that the right device is EtherNet/IP
configuration format configured in the control builder.
Check the EDS file for the
correctness.
14 Connection request For listen only connection there EtherNet/IP
fails since there is should be an exclusive owner
no controlling connection originated to the slave
connection currently device.
open
15 Target application All the connection resources in the EtherNet/IP
cannot support any slave device are exhausted. Try
more connections closing certain connections and
retry.
16 RPI is smaller than Check the EDS file for the EtherNet/IP
the Production correctness.
Inhibit time
9ARD000014-600 A 249
Connection Error Appendix B Troubleshooting CI873 Log Entries
17 Connection timed out Connection between CI873 and the EtherNet/IP
slave device timed out. Check if the
slave device is available in the
network. Check the load of CL and
slave device.
18 Unconnected Send Reply to the connection request is EtherNet/IP
timed out waiting not received from the slave device
for a response within the stipulated time period.
Check if the device is available in
the network.
19 Network bandwidth Slave device is too busy to handle EtherNet/IP
not available for the connection request. Check the
data load of the slave device.
20 Port specified in Check the EDS file for correctness. EtherNet/IP/DeviceNet
port segment not
available
21 Link Address Check the EDS file for correctness. EtherNet/IP
specified in port
segment not
available
22 Invalid Segment Type Check the EDS file for correctness. EtherNet/IP
or Segment Value in
Path
23 Connection already Check if the connection is already EtherNet/IP
established available in slave device.
24 Direct connection Check if the connection is already EtherNet/IP
already established available in slave device.
250 9ARD000014-600 A
Appendix B Troubleshooting CI873 Log Entries Connection Error
25 No more consumer All the connections to the particular EtherNet/IP
resources available tag is consumed, and the device will
in the producing not accept any more connections to
object the tag.
26 Producing Symbol Check if the Tag configured in EtherNet/IP
does not exist control builder is defined in AB PLC
27 The object cannot The device is in a state where it can EtherNet/IP/DeviceNet
perform the not accept any connections. Contact
requested service in the device vendor to resolve it.
its current
mode/state
9ARD000014-600 A 251
Configuration Error Appendix B Troubleshooting CI873 Log Entries
Configuration Error
This will be displayed as “Internal Config Error” for the device in Unit Status of the
device. This is indicated as an Warning. The messages displayed in CI873 log files
for the Configuration related errors with the device are shown in the Table 43. The
position of the device in the hardware tree for which the message is printed, is also
printed in the CI873 logs.
Table 43. Configuration Error
1 Resources needed for Slave device is loaded heavily EtherNet/IP/DeviceNet
the object to perform that, it can't handle this
the requested service request time being. Try
were unavailable reducing the slave device load.
2 Invalid Parameter Value sent in the configuration EtherNet/IP/DeviceNet
value request is invalid. Check that
parameter value in EDS file for
the correctness.
3 The path segment Path used in the configuration EtherNet/IP
identifier or the request is not valid. Check the
segment syntax was not EDS file for the correctness.
understood by the
processing node
4 The path is Certain information in EDS file EtherNet/IP/DeviceNet
referencing an object does not match with the slave
class, instance or device configuration. Ensure
structure element that that the right EDS file for the
is not known or is not device is used. Check the
contained in the major and minor version of the
processing node EDS file.
5 Only part of the The data sent in the EtherNet/IP
expected data was configuration request is not
transferred complete. Check the EDS file
for the correctness.
252 9ARD000014-600 A
Appendix B Troubleshooting CI873 Log Entries Configuration Error
Table 43. Configuration Error (Continued)
6 The messaging Connection used to send the EtherNet/IP
connection was lost Tag data to PLC is
disconnected for some reason.
Ensure that the PLC is
available in the network.
7 The requested service Certain information in EDS file EtherNet/IP/DeviceNet
was not implemented or does not match with the slave
was not defined for device configuration. Ensure
this object that the right EDS file for the
class/instance device is used. Check the
Major and minor version of the
EDS file.
8 Invalid attribute data Value sent in the configuration EtherNet/IP/DeviceNet
detected request is invalid. Check the
correctness of the EDS file.
9 The object is already While trying to change the EtherNet/IP/DeviceNet
in the mode/state state of the device say from
being requested by the Idle to Run or Run to idle
service check if the device is already in
that required state.
10 A request to modify a  EtherNet/IP/DeviceNet
non-modifiable
attribute was received
11 The device's current Configuration of certain EtherNet/IP/DeviceNet
mode/state prohibits parameters are not allowed
the execution of the when the device is in run or
requested service connected state. Ensure that
the device is in right state.
9ARD000014-600 A 253
12 The data to be Data sent to the device is more EtherNet/IP
transmitted in the than what is expected.Check
response buffer is the EDS file for the
larger than the correctness.
allocated response
buffer
13 The service did not the configuration request sent EtherNet/IP/DeviceNet
supply enough data to to the device is
perform the specified incomplete.Check the EDS file
operation for correctness.
14 The attribute Check the EDS file if right EtherNet/IP/DeviceNet
specified in the version is been used.
request is not
supported
15 The service supplied Data sent to the device is more EtherNet/IP/DeviceNet
more data than was than what is expected. Check
expected the EDS file for the
correctness.
16 The object specified Check the EDS file if right EtherNet/IP/DeviceNet
does not exist in the version is been used.
device
17 The attribute data of Certain parameters have to be EtherNet/IP/DeviceNet
this object was not saved in ROM after
saved prior to the configuration, so that it can be
requested service automatically configured
during power failure condition.
Check the EDS file if the
option to save the parameter is
provided.
254 9ARD000014-600 A
Appendix B Troubleshooting CI873 Log Entries Configuration Error
18 An attempt was made to Configuration of certain EtherNet/IP/DeviceNet
write to a write-once parameters are not allowed
medium that has when the device is in run or
already been written, connected state. Ensure that
or to modify a value the device is in right state.
that cannot be changed
once established
19 An invalid reply is Invalid reply is received from EtherNet/IP/DeviceNet
received (e.g. reply the slave device wither for the
service code does not configuration or connection
match the request request. Contact the device
service code, or reply vendor.
message is shorter
than the minimum
expected reply size).
20 Invalid Vendor Id or Check the EDS file for the EtherNet/IP/DeviceNet
Product Code specified correctness. Ensure that the
in the Key segment right EDS file is used. It can be
that device configured in
control builder is different from
the device physically available.
21 Invalid Product Type Check the EDS file for the EtherNet/IP/DeviceNet
specified in the Key correctness. Ensure that the
segment right EDS file is used. It can be
that device configured in
control builder which is
different from the device
physically available.
9ARD000014-600 A 255
22 Invalid Major or Minor Check if the right version of the EtherNet/IP/DeviceNet
revision specified in EDS file is used.
the Key segment
23 An attempt was made to Slave device is loaded heavily EtherNet/IP/DeviceNet
set an attribute that that, it cannot handle this
is not able to be set request time being. Try
at this time reducing the slave device load.
256 9ARD000014-600 A
Index
Numerics Re-import 168
200-AENTR 147, 150 DeviceNet
Configuration Recovery 131
A Configure Slave Device 122
Address Recovery 44 COS Connection 127
Cyclic Connection 129
Device Identification Parameters 124
C
Electronic Key Parameters 124
CI873 19
Hot Swap 44
CEX Bus 217
Insert Slave Device 121
CI873 Connections 30
Poll Connection 126
CI873 Module Redundancy 42
Re-configuration 170
Configuration 108
Status Handling 37
Explicit Messaging 31
Strobe Connection 128
Hot Swap 43
Diagnostic Webpages 189
Implicit Messaging 30
Insert 107
Status Handling 33 E
Common Industrial Protocol 19 EDS File 47
Config Recovery 131 EDS Viewer 62
Configuration Recovery 44 Electronic Key Parameters 124
Controller Area Network 19 EtherNet/IP
COS Connection 127 Configuration 135
Cyclic Connection 129 Hot Swap 45
Insert 133
Set IP Address 132
D
Technical Data 215
Device Identification Parameters 124
Device Import Wizard 47
Control Logix PLC 81 F
Convert EDS File 49 Firmware
Device 57 LD 800DN 176
EtherNet/IP Device 79
File 61 H
I/O Channel Creation 76 Hardware Library 103
I/O Settings 73 Hardware Tree 28
Modular I/O System 54 Hot Swapping 27
9ARD000014-600 A 257
Index
I P
I/O Settings Poll Connection 126
Analog Channels 94 Protocol User Interface 28
Delete I/O Channels 100
DeviceNet Device 75 R
Digital Channels 91 Requested Packet Interval 31
Modify I/O Channels 100 RPI 31
Recreate I/O Channels 100 Run-Time Behavior 165
Inter Scan Delay 120
S
L S200 I/O 146
LD 800DN 173 Scan Cycle 182
BridgeWay Configuration Tool 174 Status Handling 27
Configuration 110 Strobe Connection 128
File System 201
Hot Swap 44 T
Insert 109 Technical Data 213
IP Address 179
MAC ID 179
U
Re-configuration 171
User Interface 28
Run/Idle State 209
Scan Cycle 182
Status and Diagnostics Indicators 183
Status Handling 35
System Files 204
Technical Data 214
Timing Parameters 120
Updating Firmware 176
User Accounts 203
Web Interface 189
Active Nodes 191
Faulted Nodes 193
Idle Nodes 192
Invalid Nodes 194
Node Status 195
Status & Settings 196
LED Indicators 183
Logix 5000 series PLC
Configuration 141
258 9ARD000014-600 A
Contact us
www.abb.com/800xA Copyright © 2016 ABB.
9ARD000014-600 A
www.abb.com/controlsystems All rights reserved.
Power and productivity

for a better worldTM

Ethernet/Ip Devicenet Configuration: Power and Productivity For A Better World™

Uploaded by

Copyright:

Available Formats

You might also like

Ethernet/Ip Devicenet Configuration: Power and Productivity For A Better World™

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

Ethernet/Ip Devicenet Configuration: Power and Productivity For A Better World™

Uploaded by

Copyright:

Available Formats

AC 800M

Power and productivity

System Version 6.0

Copyright © 2003-2016 by ABB.

Release: April 2016

About This User Manual

Section 2 - Functional Description

Status Handling for S200 IO Modules................................................................. 41

Section 3 - Device Import Wizard

Configuration Recovery Parameter ....................................................................131

Section 5 - Run-Time Operation

Section 6 - Linking Device LD 800DN

Ethernet Link LED............................................................................................. 186

Section 7 - Technical Data

Section 8 - Hardware Connections

Connect CI873 to LD 800DN........................................................................................218

Appendix A - Troubleshooting EDS File

Appendix B - Troubleshooting CI873 Log Entries

User Manual Conventions

Warning, Caution, Information, and Tip Icons

Released User Manuals and Release Notes

CI873 Communication Interface Module

Linking Device LD 800DN

Device Import Wizard

Figure 1. System configuration

EtherNet/IP Embedded Switch Technology Overview

EtherNet/IP Star Topology

Figure 2. EtherNet/IP Star Topology

Figure 3. Linear Network Topology

The following are advantages of a linear network:

Figure 4. A typical hardware tree configuration in Control Builder

Explicit Messaging Implicit Data Transfer

Unconnected UCMM n/a

Connected Class 3 Class 1

Implicit Messaging (Class1)

Explicit Messaging (Class 3 or UCMM)

CIP Connection Time-out Calculation

Connection Time-out Multiplier

Table 1. Connection Time-out Multiplier Values

Status Handling for CI873

Table 2. Errors and warnings for CI873 Hardware Unit

Bit Value Text Indication Alarm/Event Severity Description

Table 3. Extended status of CI873 Hardware Unit

Bit Value Text Indication Alarm/Event Severity Description

Status Handling for LD 800DN

Table 4. Errors and Warnings of LD 800DN

Bit Value Text Indication Alarm/Event Severity Description

Table 5. Extended status of LD 800DN

Bit Value Text Indication Alarm/Event Severity Description

Status Handling for DeviceNet Slaves

Table 6. Errors and Warnings of DeviceNet Device

Bit Value Text Indication Alarm/Event Severity Description

Table 6. Errors and Warnings of DeviceNet Device (Continued)

Bit Value Text Indication Alarm/Event Severity Description

Table 7. Extended status of DeviceNet Device

Bit Value Text Indication Alarm/Event Severity Description

Status Handling for EtherNet/IP Device

Table 8. Errors and Warnings of EtherNet/IP device