Interface AB Experion

Honeywell Process Solutions
Experion
Allen-Bradley Drive Interface

through ControlNet
Reference
EP-DCX606
R400
April 2010
Release 400
Honeywell
Notices and Trademarks

Copyright 2010 by Honeywell International Srl.
Release 400 April 2010
While this information is presented in good faith and believed to be accurate, Honeywell disclaims
the implied warranties of merchantability and fitness for a particular purpose and makes no
express warranties except as may be stated in its written agreement with and for its customers.
In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The
information and specifications in this document are subject to change without notice.
Honeywell, PlantScape, Experion PKS, and TotalPlant are registered trademarks of Honeywell
International Inc.
Other brand or product names are trademarks of their respective owners.

1860 W. Rose Garden Lane
Phoenix, AZ 85027 USA
1-800 822-7673
ii
Experion Allen-Bradley Drive Interface through ControlNet Reference

Honeywell
R400
April 2010
About This Document

This document provides information for planning, installing, configuring, operating, maintaining
and troubleshooting hardware components and software function blocks associated with an AllenBradley Drive Interface function
Release Information
Document Name
Allen-Bradley Drive Interface through
ControlNet Reference - abdir
Document ID
EP-DCX606
Release
Number
Publication
Date
400
April 2010
Document Category
Reference
R400
April 2010

Honeywell
iii
Support and Other Contacts

United States and Canada
Contact:
Phone:
Fascimile:
Mail:
Honeywell Solution Support Center

1-800-822-7673
Calls are answered by dispatcher between 6:00 am and 4:00 pm
Mountain Standard Time. Emergency calls outside normal working hours
are received by an answering service and returned within one hour.
1-973-455-5000
Honeywell TAC, MS L17
1860 W. Garden Lane
Phoenix, AZ, 85027 USA
Europe, Middle East, and Africa (EMEA)

Contact:
Phone:
Fascimile:
Mail:
Honeywell TAC-EMEA
+32-2-728-2345
+32-2-728-2696
TAC-BE02
Hermes Plaza
Hermeslaan, 1H
B-1831 Diegem, Belgium
Contact:
Phone:
Honeywell Global TAC Pacific

1300-364-822 (toll free within Australia)
+61-8-9362-9559 (outside Australia)
+61-8-9362-9564
Honeywell Limited Australia
5 Kitchener Way
Burswood 6100, Western Australia
GTAC@honeywell.com
Pacific
Fascimile:
Mail:
Email:
India
Contact:
Phone:
Fascimile:
Mail:
Email:
iv
Honeywell Global TAC India

+91-20- 6603-9400
+91-20- 6603-9800
Honeywell Automation India Ltd
56 and 57, Hadapsar Industrial Estate
Hadapsar, Pune 411 013, India
Global-TAC-India@honeywell.com

Honeywell
R400
April 2010
Korea
Contact:
Phone:
Fascimile:
Mail:
Email:
Honeywell Global TAC Korea

+82-2-799-6317
+82-2-792-9015
Honeywell Co., Ltd
4F, Sangam IT Tower
1590, DMC Sangam-dong, Mapo-gu
Seoul, 121-836, Korea
Global-TAC-Korea@honeywell.com
Peoples Republic of China

Contact:
Phone:
Mail:
Email:
Honeywell Global TAC China

+86- 21-2219-6888
800-820-0237
400-820-0386
Honeywell (China) Co., Ltd
33/F, Tower A, City Center, 100 Zunyi Rd.
Shanghai 200051, Peoples Republic of China
Global-TAC-China@honeywell.com
Singapore
Contact:
Phone:
Fascimile:
Mail:
Email:
Honeywell Global TAC South East Asia

+65-6580-3500
+65-6580-3501
+65-6445-3033
Honeywell Private Limited
Honeywell Building
17, Changi Business Park Central 1
Singapore 486073
GTAC-SEA@honeywell.com
Taiwan
Contact:
Phone:
Fascimile:
Mail:
Email:
R400
April 2010
Honeywell Global TAC Taiwan

+886-7-536-2567
+886-7-536-2039
Honeywell Taiwan Ltd.
17F-1, No. 260, Jhongshan 2nd Road.
Cianjhen District
Kaohsiung, Taiwan, ROC
Global-TAC-Taiwan@honeywell.com

Honeywell
Japan
Contact:
Phone:
Fascimile:
Mail:
Email:
Honeywell Global TAC Japan

+81-3-6730-7160
+81-3-6730-7228
Honeywell Japan Inc.
New Pier Takeshiba, South Tower Building,
20th Floor, 1-16-1 Kaigan, Minato-ku,
Tokyo 105-0022, Japan
Global-TAC-JapanJA25@honeywell.com
Elsewhere
Call your nearest Honeywell office.
World Wide Web

Honeywell Solution Support Online:
http://www.honeywell.com/ps
Training Classes
Honeywell Automation College:
http://www.automationcollege.com
vi

Honeywell
R400
April 2010
Symbol Definitions
Symbol Definitions
The following table lists those symbols used in this document to denote certain conditions.
Symbol
Definition
ATTENTION: Identifies information that requires special
consideration.
TIP: Identifies advice or hints for the user, often in terms of

performing a task.
REFERENCE -EXTERNAL: Identifies an additional source of
information outside of the bookset.
REFERENCE - INTERNAL: Identifies an additional source of
information within the bookset.
CAUTION
Indicates a situation which, if not avoided, may result in equipment

or work (data) on the system being damaged or lost, or may result in
the inability to properly operate the process.
CAUTION: Indicates a potentially hazardous situation which, if not
avoided, may result in minor or moderate injury. It may also be used
to alert against unsafe practices.
CAUTION symbol on the equipment refers the user to the product
manual for additional information. The symbol appears next to
required information in the manual.
WARNING: Indicates a potentially hazardous situation, which, if not
avoided, could result in serious injury or death.
WARNING symbol on the equipment refers the user to the product
manual for additional information. The symbol appears next to
required information in the manual.
R400
April 2010

Honeywell
vii
Symbol Definitions
Symbol
Definition
WARNING, Risk of electrical shock: Potential shock hazard where
HAZARDOUS LIVE voltages greater than 30 Vrms, 42.4 Vpeak, or
60 VDC may be accessible.
ESD HAZARD: Danger of an electro-static discharge to which
equipment may be sensitive. Observe precautions for handling
electrostatic sensitive devices.
Protective Earth (PE) terminal: Provided for connection of the
protective earth (green or green/yellow) supply system conductor.
Functional earth terminal: Used for non-safety purposes such as

noise immunity improvement. NOTE: This connection shall be
bonded to Protective Earth at the source of supply in accordance
with national local electrical code requirements.
Earth Ground: Functional earth connection. NOTE: This
connection shall be bonded to Protective Earth at the source of
supply in accordance with national and local electrical code
requirements.
Chassis Ground: Identifies a connection to the chassis or frame of
the equipment shall be bonded to Protective Earth at the source of
supply in accordance with national and local electrical code
requirements.
viii

Honeywell
R400
April 2010
Contents
1.
INTRODUCTION ..........................................................................15
1.1
About this guide ............................................................................................ 15
Intended audience................................................................................................................15
Prerequisite skills .................................................................................................................15
How to use this guide ...........................................................................................................15
Related Documents..............................................................................................................15
2.
ALLEN-BRADLEY DRIVE INTERFACE PURPOSE....................17

2.1
A-B Drive Interface Library........................................................................... 17
2.2
I/O Channel Library ....................................................................................... 18
2.3
Drive Interface Data Flow Model.................................................................. 18
2.4
A-B Drive Support and Documentation ...................................................... 20
Legacy SCANport drives support .........................................................................................20

PowerFlex drives support.....................................................................................................21
2.5
About ControlNet I/O drive data transfer.................................................... 23
Logic command data ............................................................................................................24

Drive status data ..................................................................................................................25
Analog frequency reference and feedback...........................................................................26
Datalink parameters .............................................................................................................26
2.6
3.
Differences between Legacy SCANport and PowerFlex Drives............... 28
ALLEN-BRADLEY DRIVE INTERFACE PLANNING AND DESIGN

31
3.1
General Planning References ...................................................................... 31
3.2
C200 with A-B Drive Interface Topology..................................................... 31
3.3
A-B Drive Interface Configuration Rules .................................................... 33
3.4
A-B Drive Interface Capacity considerations ............................................. 34
4.
ALLEN-BRADLEY DRIVE INTERFACE INSTALLATION AND
UPGRADES ..........................................................................................37
R400
April 2010

Honeywell
ix
Contents
4.1
Installation References .................................................................................37
4.2
Firmware Upgrade References for A-B Drive and ControlNet Adapters .37
5.
ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION ...... 39

5.1
Configuration Tools for A-B Drive Interface ...............................................39
5.2
A-B Drive Interface Configuration Data Location and Interaction............39
5.3
Configuring CNI Module for Use with A-B Drive Interface ........................40
Prerequisites ....................................................................................................................... 40
Considerations .................................................................................................................... 40
To configure CNI module .................................................................................................... 41
5.4
Adding Allen-Bradley DRIVE block to Project ............................................42
Prerequisites ....................................................................................................................... 42
General Considerations....................................................................................................... 43
PowerFlex drive configuration considerations ..................................................................... 44
To create A-B Drive Interface Block .................................................................................... 46
5.5
Adding Drive I/O Channel to Control Module .............................................50
DRIVE_INPUT block functional overview............................................................................ 50

DRIVE_OUTPUT block functional overview........................................................................ 51
AOCHANNEL block functional overview for drive interface................................................. 52
Prerequisites ....................................................................................................................... 54
Considerations .................................................................................................................... 54
To add DRIVE_INPUT block to CM..................................................................................... 55
5.6
Assigning A-B Drive to Execution Environment ........................................61
Prerequisites ....................................................................................................................... 61
Considerations .................................................................................................................... 61
To assign A-B Drive to CEE ................................................................................................ 62
5.7
Loading configuration data to A-B Drive ....................................................64
Prerequisites ....................................................................................................................... 64
Considerations .................................................................................................................... 64
To load A-B Drive block....................................................................................................... 64
6.
ALLEN-BRADLEY DRIVE INTERFACE OPERATION ............... 67

6.1
Monitoring Allen-Bradley Drive Interface Functions through Monitoring
Tab in Control Builder..............................................................................................67
Checking operational Status ............................................................................................... 67
A-B drive interface block icon appearances ........................................................................ 67
Monitoring/Interacting with given component/block ............................................................. 68
Component/block interaction considerations ....................................................................... 69

Honeywell
R400
April 2010
Contents
6.2
Monitoring Allen-Bradley Drive Interface Functions through Station
Displays .................................................................................................................... 72
Using Station Detail displays................................................................................................72
Using Station Event Summary display .................................................................................72
7.
ALLEN-BRADLEY DRIVE INTERFACE TROUBLESHOOTING.73

7.1
Isolating Problems ........................................................................................ 73
7.2
Fault Classifications ..................................................................................... 73
7.3
Initial Checks ................................................................................................. 74
Checking Control Builder error code reference ....................................................................74

Viewing flash log ..................................................................................................................75
Viewing release information log ...........................................................................................75
Viewing trace log..................................................................................................................75
Checking server point build log ............................................................................................75
Checking server point build error log....................................................................................75
Checking error log................................................................................................................75
Using NetworkTools to capture chassis information.............................................................76
7.4
Fixing Common Problems............................................................................ 76
Controller switchover............................................................................................................76
Cable fault or loss of power..................................................................................................76
7.5
Getting Further Assistance .......................................................................... 78
Allen-Bradley drive troubleshooting reference......................................................................78

Other troubleshooting sources .............................................................................................78
Guidelines for requesting support ........................................................................................79
R400
April 2010

Honeywell
xi
Contents
Tables
Tables
Table 1 Logic command comparison between Legacy SCANport and PowerFlex Drives
................................................................................................................................24
Table 2 Drive status data comparison between Legacy SCANport and PowerFlex Drives
................................................................................................................................25
Table 3 Legacy SCANport and PowerFlex Drives Comparison ...................................28
Table 4 Configuration Data/Function and Tool Applicability .........................................39
Table 5 PowerFlex 700S Configuration Parameters.....................................................45
xii

Honeywell
R400
April 2010
Contents
Figures
Figures
Figure 1 Typical A-B Drive Data Flow Model................................................................ 19
Figure 2 ControlNet I/O Drive Data Transfer Map........................................................ 23
Figure 3 Typical Datalink Parameter Exchange ........................................................... 27
Figure 4 Typical Multiple A-B Drive Interface with Redundant C200 Controller Topology
................................................................................................................................ 32
Figure 5 Typical Single A-B Drive Interface with Redundant C200 Controller and Buddy
CNI Topology.......................................................................................................... 33
Figure 6 Typical PowerFlex 700S scaling for AOCHANNEL output. ........................... 45
Figure 7 Typical DRIVE_INPUT Block A-B Drive Data Exchange ............................... 51
Figure 8 Typical DRIVE_OUTPUT Block A-B Drive Data Exchange ........................... 52
Figure 9 Typical AOCHANNEL Block A-B Drive Data Exchange................................. 53
R400
April 2010

Honeywell
xiii
Contents
Figures
xiv

Honeywell
R400
April 2010
1. Introduction
1.1
About this guide
Intended audience
Personnel who are responsible for integrating an Allen-Bradley Drive Interface through
ControlNet media with the Experion system.
Prerequisite skills
Familiar with working in a Windows operating environment.
Familiar with using these Experion applications:
Configuration Studio
Control Builder
Network Tools
How to use this guide

Choose a topic associated with the task you want to complete on the tree view in
Knowledge Builder. This guide covers tasks for planning your installation through
troubleshooting considerations.
Related Documents
For more information about using Control Builder, see:
R400
April 2010
Control Building Guide

Honeywell
15
1. Introduction
1.1. About this guide
16

Honeywell
R400
April 2010
2. Allen-Bradley Drive Interface Purpose

The Allen-Bradley Drive Interface (AB_DRIVE_IF) Control Component Library
includes function blocks to integrate selected Allen-Bradley drives with Experion control
strategies configured through Control Builder.
ATTENTION
The Allen-Bradley Drive Interface (AB_DRIVE_IF) Library is not supported on
the C300 Controller at this time.
2.1
A-B Drive Interface Library

The Library tab in the Experion Control Builder includes the following AB_DRIVE_IF
library of I/O Module and I/O Channel type function blocks to support configuration of
drive interface components with Experion control strategies.
Description
Block Name and Icon
Legacy SCANport Drives
This block represents the 1203-CN1 module and
the 1305 AC Drive as one entity.
the 1336 Plus II AC Drive as one entity.
a generic Legacy SCANport Drive as one entity.
The generic drive must support I/O data transfer
similar to the 1305 and 1336-PLUS-II drives.
The Drive Input I/O Channel block allows the
control strategy to use data published by the
drive.
The Drive Output I/O Channel block allows the
control strategy to push data to the drive.
PowerFlex Drives
This block represents the generic PowerFlex
R400
April 2010

Honeywell
17

2.2. I/O Channel Library
drive and the 20-COMM-C as one entity.
The PowerFlex In I/O Channel block allows the

control strategy to use data published by the
drive.
The PowerFlex Out I/O Channel block allows the
This block represents the generic PowerFlex
drive and the 20-COMM-C as one entity.
The 700S In I/O Channel block allows the control
strategy to use data published by the drive.
The 700S Out I/O Channel block allows the
2.2
I/O Channel Library

The Library tab in the Experion Control Builder includes the following IOCHANNEL
library of I/O Channel function blocks to support configuration of Series A chassis I/O
Module components with Experion control Strategies. Only the AOCHANNEL block is
shown since it also can be used with A-B drive interface components.
Description
Block Name and Icon
This block can be used with all the A-B Drive
function blocks listed in the previous table. Its
output (OP) parameter can be used to write the
Analog Speed Reference to the given drive.
2.3
Drive Interface Data Flow Model

The following diagram shows how drive data flows through the various components and
blocks in the Experion architecture.
18

Honeywell
R400
April 2010

2.3. Drive Interface Data Flow Model
Figure 1 Typical A-B Drive Data Flow Model
R400
April 2010

Honeywell
19

2.4. A-B Drive Support and Documentation
2.4
A-B Drive Support and Documentation
Legacy SCANport drives support

The Allen-Bradley 1203-CN1 ControlNet communications module serves as the bridge
between the Experion control environment and any single SCANport product. The
following Allen-Bradley SCANport products are qualified for use with Experion
systems:
CAUTION
Only the 1305 and 1336 Plus II drives have been fully qualified for use with
Experion systems. You can use other Allen-Bradley drives at your own Risk.
Model Names
FW Rev
HIM Rev
Adapter Rev
1305 Adjustable
Frequency AC Drive
(Series C)
N/A
N/A
N/A
1336 PLUS II
Adjustable Frequency
AC Drive
1.07 Series B
N/A
2.002 Build 01
20

Honeywell
R400
April 2010

Model Names
FW Rev
HIM Rev
Adapter Rev
REFERENCE - EXTERNAL
Please refer to the applicable Allen-Bradley documentation for a given device
for more information.
Allen-Bradley ControlNet (1203-CN1) Communications Module User

Manual
Allen-Bradley 1305 Adjustable Frequency AC Drive User Manual
Allen-Bradley 1336 PLUS II Adjustable Frequency AC Drive User Manual
PowerFlex drives support

The following Allen-Bradley PowerFlex 7 Class drives are qualified for use with
Experion systems: The Allen-Bradley 20-COMM-C communication adapter provides an
electronic communications interface between a ControlNet network and a PowerFlex 7Class drive or any other Allen-Bradley product that supports an internal DPI (Drive
Peripheral Interface) adapter.
The 20-COMM-C translates the ControlNet messages between Experion Controllers and
the PowerFlex drives.
R400
April 2010

Honeywell
21

CAUTION
Only the PowerFlex 700, 700VC, and 700S drives have been fully
qualified for use with Experion systems. You can use other Allen-Bradley
drives at your own Risk.
Honeywell recommends using Qualified drives in place of Compatible

drives wherever possible.
You must confirm that the Logic Command and Drive Status bit
definitions for the drive match the bit definitions defined in the following
Logic command data and Drive Status data sections.
Compatible1
Qualified2
Yes
No
Yes
PowerFlex700H
Model Names
HIM Rev
Adapter Rev
N/A
N/A
N/A
Yes
3.002
Series A
3.006
Series A
2.005
Series B
Yes
No
N/A
N/A
N/A
PowerFlex700L
Yes
No
N/A
N/A
N/A
PowerFlex700VC
Yes
Yes
4.006
Series B
3.006
Series A
2.005
Series B
PowerFlex700S3
Yes
Yes
4.001
N/A
N/A
PowerFlex7000
No
No
N/A
N/A
N/A
PowerFlex70
PowerFlex700
FW Rev
Compatible drives implement the same communications protocol described in this document
and should function with Experion systems, but have not been fully tested by Honeywell.
Qualified drives have been fully tested by Honeywell with firmware versions listed.
Only 700S-Phase II drives are compatible. You cannot use 700S-Phase I drives.
22

Honeywell
R400
April 2010

2.5. About ControlNet I/O drive data transfer
Please refer to the applicable Allen-Bradley documentation for a given device
for more information.
2.5
Allen-Bradley PowerFlex 70 Adjustable Frequency AC Drive User

Manual
Allen-Bradley PowerFlex 700 Adjustable Frequency AC Drive User

Manual - Series A
Allen-Bradley PowerFlex 700 Drive w/Vector Control Option Release

Notes (Revision 4.006)
About ControlNet I/O drive data transfer

The drive parameter data that can be read from and written to the Experion Controllers is
consistent with the data that can be programmed and displayed using PLC's, SLC's, or
other logic controllers, as illustrated below. The configuration of the ControlNet
communications adapter determines the amount of information that can be transferred.
Figure 2 ControlNet I/O Drive Data Transfer Map

R400
April 2010

Honeywell
23

Logic command data

The 16-bit Logic Command word is sent from the Experion Controller through the
adapter to the drive. The following table compares the Logic Command Data for
different drive types. The Legacy SCANport Drives and all PowerFlex drives, except for
the 700S, are basically the same.
Table 1 Logic command comparison between Legacy SCANport and
PowerFlex Drives
Bit
Legacy SCANport
Drives
(1305, 1336-PLUS-II)
PowerFlex Drives
(except 700S)
PowerFlex 700S
Stop
Stop
Stop
Start
Start
Start
Jog
Jog
Jog 1
Clear Faults
Clear Faults
Clear Fault
Direction
Direction
Unipolor Direction
Local
Local
Reserved
MOP Incr.
MOP Incr.
Jog 2
Accel Rate
Accel Rate
Current Limit Stop
9
10
Coast Stop
Decel Rate
Decel Rate
Reserved
Ref Select
Ref Select
Spd Ref Sel
MOP Decr.
MOP Decr.
Reserved
11
12
13
14
15
24

Honeywell
R400
April 2010

Please refer to the applicable Allen-Bradley User's Manual for complete
details about the communication structures.
Drive status data

The 16-bit Drive Status word is sent from the drive through the adapter to the Experion
Controller.
Table 2 Drive status data comparison between Legacy SCANport and
PowerFlex Drives
Bit
Legacy SCANport
Drives
(1305, 1336-PLUS-II)
PowerFlex Drives
(except 700S)
PowerFlex 700S
Enabled
Ready
Active
Running
Active
Running
Cmd Dir
Cmd Dir
Cmd Dir
Actual Dir
Actual Dir
Actual Dir
Accel
Accel
Accel
Decel
Decel
Decel
Warning
Alarm
Jogging
Fault
Fault
Fault
At Reference
At Speed
Alarm
Local
Local
Flash Mode
10
Run Ready
11
At Limit
12
Ref Source
Ref Source
Tach Loss Sw
13
At Zero Spd
14
At Setpt Spd
15
Enable
R400
April 2010

Honeywell
25

Please refer to the applicable Allen-Bradley User's Manual for complete
details about the communication structures.
Analog frequency reference and feedback

All Compatible Drives except the PowerFlex 700S
The 16-bit Analog Frequency Reference word is sent from the Experion Controller
through the communications adapter to the drive. This is the frequency that the drive is
commanded to output. This is the same value as the drive's [Freq Command] parameter.
The 16-bit Frequency Feedback word is sent from the drive through the communications
adapter to the Experion Controller. This is the drive's current output frequency. This is
the same value as the drive's [Output Freq] parameter.
The valid range for both words is 0 to 32767, where zero corresponds to 0 Hertz and
32767 corresponds to the maximum frequency configured for the drive.
PowerFlex 700S
For the 700S, the Speed Reference and Feedback are 32-bits in size rather than 16-bits as
in other A-B drives.
The Speed Reference is scaled:
Commanded RPM
Speed Reference
32767
Motor NP RPM
The Speed Feedback is scaled:

Feedback
Feedback RPM
Motor NP RPM
32767
The Motor NP RPM is Motor Nameplate rated RPM (Parameter 4 in 700S drive).
Datalink parameters
The drives can be configured to send/receive up to eight additional parameters through
datalinks. There are four (4) datalinks (A through D) which consist of two (2) parameter
data words each, as illustrated below.
26

Honeywell
R400
April 2010

Figure 3 Typical Datalink Parameter Exchange
R400
April 2010

Honeywell
27

2.6. Differences between Legacy SCANport and PowerFlex Drives
2.6 Differences between Legacy SCANport and

PowerFlex Drives
The following table summarizes the basic functional differences between the AllenBradley legacy SCANport drives and the PowerFlex 7 Class drives as integrated in the
Experion system.
Table 3 Legacy SCANport and PowerFlex Drives Comparison
Function/Area
Legacy SCANport
Drives
(1305, 1336-PLUS-II)
PowerFlex Drives
(except 700S)
PowerFlex 700S Drive
Communications
Adapter
1203-CN1
20-COMM-C
20-COMM-C
Drive Status Word
All bits exposed as

parameters on input
channel block.
Same as Legacy
SCANport.
700S supports
additional parameters.
Logic Command Word
All bits exposed as

parameters on output
channel block.
Same as Legacy
SCANport.
700S supports
additional parameters.
OP Scaling of
Reference and
Feedback
The valid range for

both words is 032767, where 0
corresponds to 0 Hz
and 32767
corresponds to the
maximum frequency
configured for the
drive.
Same as Legacy
SCANport.
For 700S, the valid

range for both words is
the Drive's Par 30 [Min
Spd Ref Lim] to Par 31
[Max Spd Ref Lim].
These parameters must
be configured on the
Experion Drive IOM
function block.
Datalinks
Only 16-bit integer

and 16-bit unsigned
integer data types are
supported.
70 and 700 support

16-bit integer, 16-bit
unsigned integer and
32-bit integer data
types.
700S supports 32-bit

integer and FLOAT32.
700VC supports 32-bit

integer only.
Experion Function
Blocks
28
Drive IOM blocks

1305
1336-PLUS-II
Drive IOM blocks

POWERFLEXDRIVE
Drive IOM blocks

700S

Honeywell
R400
April 2010

Function/Area
Legacy SCANport
Drives
(1305, 1336-PLUS-II)
PowerFlex Drives
(except 700S)
PowerFlex 700S Drive
GENERIC_DRIVE
Drive channel blocks
DRIVE_INPUT
DRIVE_OUTPUT

POWERFLEX_IN
POWERFLEX_OUT

700S_IN
700S_OUT
Station Displays
Default detailed and

group displays:
sysDtlABDa
sysDtlABDa_fp

group displays:
sysDtlABDPFa
sysDtlABDPFa_fp

group displays:
sysDtlABDPF700Sa
sysDtlABDPF700Sa_fp
Supported Topology
No difference
No difference
No difference
Performance/Capacity
No difference
No difference
No difference
R400
April 2010

Honeywell
29

30

Honeywell
R400
April 2010
3. Allen-Bradley Drive Interface Planning and

Design
3.1
General Planning References

Please refer to the following Knowledge Builder publications for planning and design
details for the Experion system in general and the ControlNet supervisory network. For
the sake of brevity, this Guide does not repeat the applicable general guidelines,
considerations, cautions, and so on that are covered in these other Guides.
3.2
Control Hardware Planning Guide
Server and Client Planning Guide
C200 with A-B Drive Interface Topology

The following illustrations show a typical topologies for integrating an Experion C200
Controller with multiple Allen-Bradley drives and a small system with only one AllenBradley drive. See the following configuration rules for special topology considerations.
R400
April 2010

Honeywell
31
3. Allen-Bradley Drive Interface Planning and Design

3.2. C200 with A-B Drive Interface Topology
Figure 4 Typical Multiple A-B Drive Interface with Redundant C200

Controller Topology
32

Honeywell
R400
April 2010

3.3. A-B Drive Interface Configuration Rules
Figure 5 Typical Single A-B Drive Interface with Redundant C200

Controller and Buddy CNI Topology
3.3
A-B Drive Interface Configuration Rules
Reference
Description
CR_ABD.0
Each 1203-CN1 and 20-COMM-C adapter can only be connected to one drive.
CR_ABD.1
The 1203-CN1 and 20-COMM-C adapters, and the attached drive must reside
on an I/O ControlNet segment that is physically isolated from unscheduled I/O
communications.
CR_ABD.2
The 1203-CN1 module provides a connection for terminals capable of RS232

serial communications. This port can be used to edit the module's parameter
and to upgrade the module's firmware. An Allen-Bradley 1203-SFC serial
cable is required to use this port. As pictured, a dedicated computer can be
R400
April 2010

Honeywell
33

3.4. A-B Drive Interface Capacity considerations
Reference
Description
used for configuration operations, or alternatively, an Experion Client Station

node can be used for this purpose.
CR_ABD.3
The Human Interface Module is used to program the drive and 20-COMM-C
adapter as well as to view various operating parameters.
CR_ABD.4
ControlNet or FTE is depicted for the supervisory network; however, Ethernet

supervisory networks are also possible using non-redundant C200s only.
CR_ABD.5
Single or dual media ControlNet configurations are permitted for the I/O
Network.
CR_ABD_6
A redundant controller configuration is depicted; however, non-redundant

configurations are also permitted.
CR_ABD_7
The communication adapter 1203-CN1 or 20-COMM-C and the attached drive

must reside on an I/O ControlNet segment that is physically isolated from
unscheduled I/O communications.
CR_ABD_8
For redundant controller configurations, locate the ControlNet moderator

outside the redundant chassis pair (RCP) and do not assign the MAC ID 1 to
the downlink CNIs.
CR_ABD_9
For redundant controller configurations, at least four (4) nodes are required on
every ControlNet segment to prevent nodes from becoming lonely during a
RCP switchover. If only one A-B Drive is present on the I/O ControlNet
segment, then an additional CNI (Buddy) node must be added. The MAC ID 1
should be assigned to the additional CNI.
CR_ABD_10
No Buddy CNI is required for non-redundant configurations, which do not

require four (4) nodes on the ControlNet segment.
3.4
A-B Drive Interface Capacity considerations

Consider the following considerations when planning to include an Allen-Bradley Drive
Interface in your Experion system.
34
The C200 Controller supports a maximum of 64 I/O modules. Since each A-B drive
uses one connection, each drive has the weight of one I/O Module. This means you
can have a maximum of 64 A-B drives.
The maximum number of A-B drives per downlink ControlNet Interface module
(CNI) is 18.
Each Legacy SCANport Drive with 1203-CN1 adapter counts as one I/O Unit.
Honeywell
R400
April 2010

Each PowerFlex Drive with 20-COMM-C adapter counts as one I/O Unit.
Each A-B drive must be equipped with a communications adapter and must reside on
an isolated I/O network separate from the Series A Chassis or Series H Rail I/O.
Each physical I/O ControlNet segment can only support either scheduled or
unscheduled communications but not both. This means that more than one downlink
CNI can share a physical ControlNet segment only if all I/O on this shared segment
uses the same scheduled or unscheduled communications.
R400
April 2010

Honeywell
35

36

Honeywell
R400
April 2010
4. Allen-Bradley Drive Interface Installation and

Upgrades
4.1
Installation References
You install the Experion control hardware as outlined in the applicable control hardware
documentation included in Knowledge Builder.
See the Software Installation Guide to install the latest Experion software.
See the applicable Allen-Bradley documentation to install the A-B dive interface
components.
4.2 Firmware Upgrade References for A-B Drive and

ControlNet Adapters
You can use either a HyperTerminal with a 1203-SSS adapter or Allen-Bradley's
ControlFLASH, DriveExplorer, or DriveExecutive application across ControlNet to
upgrade PowerFlex drives and the 20-COMM-C adapter. You can use a HyperTerminal
to upgrade Legacy SCANport drives and the 1203-CN1 adapter.
ATTENTION
Since certain restrictions and limitations may apply, please refer to AllenBradley's technical support for drive specific direction for upgrading firmware.
R400
April 2010

Honeywell
37
4. Allen-Bradley Drive Interface Installation and Upgrades

4.2. Firmware Upgrade References for A-B Drive and ControlNet Adapters
38

Honeywell
R400
April 2010
5. Allen-Bradley Drive Interface Configuration

5.1
Configuration Tools for A-B Drive Interface

The following table identifies the tools you need to configure a given component of an
A-B Drive Interface strategy.
If Component is . . .
Then, Use This Configuration Tool . . .
1203-CN1 Adapter
A computer running a Windows terminal emulation program such as

Hyperterminal. Upon establishing a serial connection with the 1203-CN1,
the module's software allows you to edit the 1203-CN1's parameter, view
current I/O data, and perform a flash upgrade of the firmware.
20-COMM-C Adapter
The Human Interface Module (HIM) allows you to program the drive,
view operating parameters, and control certain drive functions.
Allen-Bradley Drive
The Human Interface Module (HIM) allows you to program the drive,
view operating parameters, and control certain drive functions.
C200 / CEE
The Experion Control Builder is used to configure the drive data used
by the control strategy
CNI
The Experion NetworkTools application is used to configure the

ControlNet parameters.
5.2 A-B Drive Interface Configuration Data Location and

Interaction
The following table identifies what configuration data/functions are applicable to the
given Allen-Bradley and Experion configuration tools and which functions interact with
both tools.
CAUTION
You must carefully monitor configuration data/functions that are

applicable to both Allen-Bradley and Experion configuration tools, so
that when a change is made using one tool, a corresponding change is
made using the other tool.
Table 4 Configuration Data/Function and Tool Applicability

Configuration
Data/Function
R400
April 2010
Applicable Configuration Tool

Allen-Bradley HIM or Terminal
Experion Control Builder

Honeywell
39

5.3. Configuring CNI Module for Use with A-B Drive Interface
Applicable Configuration Tool

Allen-Bradley HIM or Terminal
Experion Control Builder
A-B
Drive
1203-CN1
Adapter
20-COMM-C
Adapter
Legacy
Drive
Block
PowerFlex
Drive
Block
Channel
Blocks
Setting ControlNet
MAC address
No
Yes
Yes
Yes
Yes
No
Enabling Datalinks
Yes
Yes
Yes
Yes
Yes
No
Changing the
specific parameters
to be sent over
Datalinks
Yes
No
No
No
Yes
Yes
5.3 Configuring CNI Module for Use with A-B Drive

Interface
You must configure the Keep Object of the CNI module for the isolated I/O ControlNet
segment connected to the A-B communications adapter to orchestrate the distribution of
new network parameters to all segment nodes.
Prerequisites
You have launched Configuration Studio with Security level of at least Engineer.
Considerations
40
The CNI modules must be on a ControlNet that is plugged into a chassis, cabled to
the ControlNet, and have unique MAC addresses in order to change their ControlNet
parameters, such as. NUT Time, UMAX, SMAX, and so on. The ControlNet
parameters are updated for all CNIs on the ControlNet at the same time.
After reprogramming the Secondary CNI's ControlNet parameters to match that of

the Primary CNI, the Secondary CNI must be power-cycled so that redundant partner
compatibility checks are re-attempted.
For redundant controller configurations, locate the ControlNet moderator outside the
redundant chassis pair (RCP) and do not assign MAC ID 1 to the downlink CNIs.
For redundant controller configurations, at least four (4) nodes are required on every
ControlNet segment to prevent nodes from becoming lonely during a RCP
switchover. If only one A-B Drive is present on the I/O ControlNet segment, then an
Honeywell
R400
April 2010

5.3. Configuring CNI Module for Use with A-B Drive Interface
additional CNI (Buddy) node must be added. The MAC ID 1 should be assigned to
the additional CNI.
Must configure the CNI module Keeper values as follows:
Network Update Time (NUT) = 6250 microseconds
Maximum Scheduled Nodes (SMax) = The highest MAC Address of all

modules on the I/O ControlNet segment.
REFERENCE - INTERNAL
Please refer to the NetworkTools (NTools) for Chassis Based Components
(C200) section in the Control Hardware Troubleshooting and Maintenance
Guide for more information about the NTools application.
To configure CNI module

Step
Action
On the Configuration Explorer tab in Configuration Studio, click Control

Strategy and then click Maintain control system firmware to launch
Network Tools.
Click the OK button to acknowledge the Warning message.
Click the Resume button on the toolbar to initiate a network scan.
In the Desktop tree, click the required FTEB or CNI icon. Wait for the chassis
details to display in the Detail pane.
Click the CNI module's graphic representation in the Details pane. The CNI
module is the item with the Network Address displayed.
Click the Change ControlNet button on the toolbar to display the Keeper
Values dialog.
Click the Change tab.
Confirm, and change if required, the parameter values to match the ones
listed below
Parameter
NUT Time
SMAX
R400
April 2010
Value
6250 microSeconds
Highest MAC Address of all
modules on the I/O ControlNet

Honeywell
41

5.4. Adding Allen-Bradley DRIVE block to Project
Step
Action
segment
5.4
UMAX
20
Number of Repeaters
Cable Length
1000 (meters)
Cable Usage
A+B (for dual media cable

configuration) - or -A (for single
media cable configuration)
If you are not using fiber optic media, clear the My System uses Fiber
Optics option.
10
If you did not change any of the parameter values, click Cancel and continue
to step 15.
11
Click the OK button.
12
Click Yes to acknowledge the confirmation messages. Wait for the data
transfer to complete.
13
Click OK to acknowledge the completion of the update without errors.
14
If a communications message dialog appears, click OK to acknowledge the

message dialog and then click the Pause button on the toolbar to halt the
network scan.
15
On the Network Tools menu, click Exit to close the application.
16
This completes the procedure. Go to the next section.
Adding Allen-Bradley DRIVE block to Project

Please refer to the Control Building Guide for basic functionality details about
calling up, navigating and interacting with the application. Also, be aware that
menus, selections, tree views, and configuration forms may vary depending
upon the licensed options installed on your system.
Prerequisites
42
You have started Configuration Studio and launched the Control Builder application.
Honeywell
R400
April 2010

You have logged on with sufficient privileges to create control strategies using
Control Builder.
General Considerations
You can only view I/O Module blocks in the Project tab set for Assignment view.
The Assignment view shows the relationship among all blocks while the
Containment view only shows templates that contain other templates or Control
Modules (CM), Sequential Control Modules (SCM), and basic blocks. To toggle the
view, right-click in an open area of the tab window and select Assignment View or
Containment View from the list, as applicable.
Each A-B Drive I/O module block represents both the communications adapter and
the given Allen-Bradley drive as one entity. The A-B Drive blocks are similar to
other Chassis I/O module blocks and share many common parameters.
The 1305 and 1336-PLUS-II drive blocks represent both the 1203-CN1
communications adapter and their associated hardware devices.
The Generic drive blocks represent both the 1203-CN1 communications adapter
and any A-B generic drive.
The POWERFLEXDRIVE block represents both the 20-COMM-C

communications adapter and the PowerFlex drive.
The 700S drive block represents both the 20-COMM-C communications adapter
and the PowerFlex 700S drive.
The A-B Drive I/O module block receives input data from the module consisting of a
drive status word, analog frequency feedback, and any optional datalink information.
The Drive-Input channel block fetches this data to be used in a control strategy.
The A-B Drive I/O module block also receives data from the control strategy
through the Drive_Output and Analog Output channel blocks consisting of a logic
control word, analog frequency reference, and any optional datalink information.
This data is sent to the drive.
You make the I/O Channel to I/O Module assignments for A-B drive blocks as you
would for other Series A Chassis I/O Module blocks. The following table lists the
specific channel numbers and block types used.
Channel Number
R400
April 2010
Block Type
Drive Input Channel
Drive Output Channel

Honeywell
43

Channel Number
Block Type
Analog Output Channel
The IO module function blocks only handle configuration information for datalink
enabling from the C200 Controller's perspective. The device must be configured
independently using Allen-Bradley configuration tools.
You can choose to enable any combination of datalinks A to D. If you enable

datalink A, the C200 controller will expect the assembly received from the drive to
contain the two parameter values configured for datalink A in both the
communications adapter and the drive.
The block module name can be up to 16 characters long and must contain at least
one letter (A-Z). It must not contain an embedded space or leading space, and dots
are allowed in parameter naming only.
The item name can be up to 40 characters long and must contain at least one letter
(A-Z). It is a name by which an entity is known within the context of the enterprise
model. The Item name must be unique among children of the same containment
parent in the Enterprise Model Builder hierarchy and should conform to the standard
convention for names within the system.
The IOM Slot Number (IOMSLOT) field on the Main tab of the configuration form
for the A-B Drive IOM block is not used, since the communications adapter sits
directly on the ControlNet and not in a chassis slot.
Press the F1 key to call up online help for the selected parameter in Control Builder.
The illustrations used in the following procedure are for example purposes only.
PowerFlex drive configuration considerations
44
The different PowerFlex drives support different data types. The drive and channel
blocks must know the data type of the parameters sent to and from the drive through
the datalinks to perform proper data scaling and range checking. Within the Experion
Controller, the data types are only configured on the A-B Drive block. The Channel
blocks retrieve data type information from the A-B Drive block at run time. See the
Control Component Library (CCL) Help included in Knowledge Builder for more
information about the valid values for data type parameters.
The PowerFlex 700S drive operation requires additional Experion Controller

configuration for proper scaling of the AOCHANNEL's (AOC) output (OP)
parameter. You must set the values of the parameters listed in the following table to
match the corresponding PowerFlex 700S parameters.
Honeywell
R400
April 2010

Table 5 PowerFlex 700S Configuration Parameters

Experion Parameter
Description
PowerFlex 700S
Parameter
MOTORNPRPM
Motor Nameplate Rated RPM
Par 4 - Motor NP RPM
MAXSPDREFLIM
Maximum Speed Reference

Limit
Par 31 - Max Spd Ref Lim
MINSPDREFLIM
Minimum Speed Reference

Limit
Par 30 - Min Spd Ref Lim
The following illustration and description shows how the parameters influence the
scaling.
Figure 6 Typical PowerFlex 700S scaling for AOCHANNEL output.

If . . .
R400
April 2010
Then, . . .
AOC.OP = 0.0
Speed Reference is always set to 0.
Command Direction is Forward
the valid range for Speed Reference is 0 to Par

Honeywell
45

If . . .
Then, . . .
31 - Max Spd Ref Lim. And, the AOCHANNEL's

output (OP) represents the scaled Speed
Reference from 0 to 100 where:
AOC.OP = 0.0 corresponds to Speed
Reference = 0.0, and

AOC.OP = 100.0 corresponds to the Max Spd
Ref Lim.
Command Direction is Reverse
AOC.OP = 100.0 corresponds to the Min Spd Ref

Lim where:
AOC.OP = 0.0 corresponds to Speed
Reference = 0.0, and

AOC.OP = 100.0 corresponds to Min Spd Ref
Lim.
To create A-B Drive Interface Block

The following procedure creates a 1305 drive block for example purposes only. You can
easily adapt the procedure to create a 1336 PLUS II, GENERIC, POWERFLEXDRIVE,
or 700S drive block instead.
Step
1
46
Action
On the File menu, Click New>I/O Modules>AB_DRIVE_IF - 1305 - AllenBradley AC Drive. Calls up the 1305 block parameters configuration form
Main tab with default name entered in the Module Name box, as shown in
the following sample illustration.

Honeywell
R400
April 2010

R400
April 2010
Step
Action
If you want to change the default name, double-click the Module Name box
and key in the desired name. Otherwise, go to Step 3.
With cursor in the Item Name box and key in the name of the item that this
object will be associated with in the Enterprise Model Builder hierarchy.
Click the Module Description box and key in the desired descriptive text to
be used on displays.
Double-click the Remote IO Chassis MAC Address (ULCNBMAC) box and

key in the MAC address of the 1203-CN1 communications adapter for this
drive.
Double-click the ControlNet Module Slot Number (connected to IO

Chassis) (DLCNBSLOT) box and key in the number of the slot the downlink
CNI module occupies in the C200 Controller chassis.
Honeywell
47

Step
Action
Click the Module Configuration tab to display it.
Be sure the check box for the Alarming Enabled function is checked, if you
want alarm reporting enabled. A blank check box means that the alarm
reporting function is disabled.
Click the check box(es) for the Datalink(s) A to D that you want to enable, as
shown in the following sample illustration.
If you are configuring a PowerFlex drive, see the previous PowerFlex drive
configuration considerations section for additional configuration details.
CAUTION
You must be absolutely certain that the datalink configuration you enter on
the Module Configuration tab for the drive perfectly matches the
configuration of the communications adapter. Failure to do this may result in
the inability to establish a connection to the device, inaccurate and faulty data
(provided by this block), and unexpected and undesirable behavior of any
control strategy using this data.
48

Honeywell
R400
April 2010

Step
Action
10
Click the Server History tab to display it.
11
Use this tab to configure desired history parameters and create or edit server
scripts. See the Control Building Guide and/or the online help for more
information.
12
Click the Server Displays tab to display it.
13
Use this tab to configure parameters associated with Station displays. See
the Control Building Guide and/or the online help for more information. The
default Point Detail and Group Detail display selections should be as noted
below.
A-B Drive Type
R400
April 2010
Point Detail Display
Group Detail Display

Honeywell
49

5.5. Adding Drive I/O Channel to Control Module
Step
5.5
Action
Legacy SCANport
sysDtlABDa
sysDtlABDa_fp
PowerFlex
(except 700S)
sysDtlABDPFa
sysDtlABDPFa_fp
PowerFlex 700S
sysDtlABDPF700Sa
sysDtlABDPF700Sa_fp
14
Click the Control Confirmation tab to display it.
15
Use this tab to configure parameters for control confirmation associated with
the licensed Electronic Signature option. See the Control Building Guide
and/or the online help for more information.
16
Click the Identification tab to display it
17
Use this tab to configure parameters associated with the licensed template
option. See the Control Building Guide and/or the online help for more
information.
18
When you completed entering configuration data, click the OK button to close
the configuration form and add the icon for the A-B drive to the Project tab.
19
Adding Drive I/O Channel to Control Module

You can add a DRIVE_INPUT, POWERFLEX_IN, 700S_IN, DRIVE_OUTPUT,
POWERFLEX_OUT, 700S_OUT and/or native AOCHANNEL block to a Control
Module to support A-B drive I/O communications.
DRIVE_INPUT block functional overview

The DRIVE_INPUT, POWERFLEX_IN, or 700S_IN function block serves as an input
channel that fetches real-time data from the given Allen-Bradley drive module function
block for use in control strategies.
The input data consists of the information within the Drive Status word, Analog
Frequency Reference Feedback, and any optional Datalink parameters along with
appropriate scaling factors, as shown in the illustration below.
50

Honeywell
R400
April 2010

Figure 7 Typical DRIVE_INPUT Block A-B Drive Data Exchange

DRIVE_OUTPUT block functional overview
The DRIVE_OUTPUT, POWERFLEX_OUT, and 700S_OUT function block serve as
output channels that send real-time data from control strategies to the given A-B drive
module function block.
The output data consists of the information within the Logic Control word, as defined in
the A-B Drive User Manuals, and any optional Datalink parameters along with
appropriate scaling factors, as shown in the illustration below.
R400
April 2010

Honeywell
51

Figure 8 Typical DRIVE_OUTPUT Block A-B Drive Data Exchange

AOCHANNEL block functional overview for drive interface
The AOCHANNEL function block allows the control strategy to set the Analog
Frequency Reference of the associated Allen-Bradley drive, as shown in the illustration
below. The AOCHANNEL block's output (OP) parameter is the scaled speed reference
between 0 and 100 percent, where 100 percent represents the maximum speed configured
on the device. See the Analog frequency reference and feedback section for more
information.
52

Honeywell
R400
April 2010

Figure 9 Typical AOCHANNEL Block A-B Drive Data Exchange

Using the AOCHANNEL block, provides full back initialization to the control strategy.
Any loss of the downstream communication path will assert the AOC's INIT_REQ
parameter. A bumpless transition will occur upon restoration of the communication path.
ATTENTION
The AOCHANNEL will NOT request initialization when the Drive is not
running. If the Drive is stopped, the AOCHANNEL accepts writes to OP even
though the speed reference feedback will not be updated. When the Drive is
commanded to start, the OP does NOT back initialize to 0. The current OP
value will be sent to the drive and the drive will accelerate based on its
configured rates.
You can set the output direction for the AOCHANNEL block through the OPTDIR
parameter as either DIRECT or REVERSE acting. The default setting is DIRECT. The
DIRECT or REVERSE action simply determines if the OP range before conversion is 0
to 100% (DIRECT) or 100 to 0% (REVERSE). Initialization takes reverse output
direction into consideration, so that the initialization value is consistent with the OP
parameter, which is always ranged from 0 to 100%.
R400
April 2010

Honeywell
53

In Monitoring mode, you can only change OPTDIR if the control block itself is inactive,
which requires Engineer Level access, or unless the assigned control module is in an
IDLE state. Any attempt to change OPTDIR for an AOCHANNEL block or
PWMCHANNEL block triggers a message indicating the reason that the request was
blocked.
Prerequisites
Control Builder.
You have added an Allen-Bradley Drive block to the Project tab.
You have created a Control Module in the Project tab.
Considerations
54
The following procedure adds a DRIVE_INPUT block to a CM and assigns a

channel to a corresponding A-B drive for example purposes only. You can easily
adapt this procedure to apply to POWERFLEX_IN or 700S_IN block as well as a
DRIVE_OUTPUT, POWERFLEX_OUT, 700S_OUT, or AOCHANNEL block.
Each block is automatically assigned a unique default channel name when it is

created. If your system will include multiple IOCHANNEL blocks, you may want to
adopt a more structured syntax for naming them.
The channel name can be up to 16 characters long and must contain at least one
letter (A-Z). It must not contain an embedded space or leading space, and dots are
allowed in parameter naming only.
The A-B Drive input/output channel blocks execute as dependent blocks at the base
period of the Control Module (CM). The Drive input block fetches the most recent
input data from the A-B Drive block. The Drive output block sends commands it has
received from the control strategy to the associated A-B Drive block
The A-B Drive input/output channel blocks support all of the parameters typically
associated with I/O Channel blocks, in general, in the Experion system. In addition
there are supported parameters that are specific to the A-B Drive input or output
block itself. See the Control Component Library (CCL) Help in Knowledge Builder
for detailed parameter definitions.
All illustrations used in the following procedure are for example purposes only.

Honeywell
R400
April 2010

To add DRIVE_INPUT block to CM

Step
R400
April 2010
Action
In the Project tab, double-click the icon for the Control Module that is to
include a DRIVE_INPUT block to open it in the Control Drawing pane, as
shown in the following sample illustration.
In the Library tab, scroll to the AB_DRIVE_IF icon and click the plus sign to
expand the tree.
Click and drag the icon for the DRIVE_INPUT block to the open CM in the
Control Drawing to add the block to the CM, as shown in the following sample
illustration.

Honeywell
55

Step
56
Action
Double-click the DRIVE_INPUT block to open its configuration parameters

form.

Honeywell
R400
April 2010

Step
R400
April 2010
Action
Accept the highlighted default Channel Name or key in a new one.
Select the Execution Order in CM box and key in the desired number in
multiples of 10 to define the execution order of the block in the CM.
Click the down arrow in the Module Name box and select the A-B Drive to be
associated with this channel. Once the drive is selected, the Module Type
and Channel Number fields are automatically updated, as shown in the
following sample illustration.

Honeywell
57

58
Step
Action
In the Channel Number list box, click the desired drive channel number this
channel block is to be assigned to. Channel 0 is the default selection.
Click the Assign Channel Block button to assign this channel to the
selected drive channel number. The Channel Name field and the Assigned to
fields are automatically updated, as shown in the following sample
illustration.
10
Click the Datalink Configuration tab to display it.

Honeywell
R400
April 2010

Step
11
Action
Click cursor in the desired Descriptor (24 char), Drive Units Scale Factor,
Minimum, or Maximum range value box and key in applicable data. Repeat
as required to fill in all required fields, as shown in the sample illustration
below.
CAUTION
R400
April 2010
You must be absolutely certain that the datalink configuration you enter
on the Datalink Configuration tab of this block perfectly matches the
datalink parameters configured in the drive device.
You must also be sure that the corresponding datalink is enabled on the
Module Configuration tab of the configuration form for the associated A-B
Drive block.

Honeywell
59

Step
60
Action
12
Click the Identification tab to display it
13
Use this tab to configure parameters associated with the licensed template
option. See the Control Building Guide and/or the online help for more
information.
14
Click the Block Pins tab to display it.
15
Use this tab to configure the pins you want to expose for this block. See the
Control Building Guide and/or the online help for more information.
16
Click the Configuration Parameters tab to display it.

Honeywell
R400
April 2010

5.6. Assigning A-B Drive to Execution Environment
5.6
Step
Action
17
Use this tab to configure the parameters to be displayed on the block in the
Project mode. See the Control Building Guide and/or the online help for more
information.
18
Click the Monitoring Parameters tab to display it.
19
Use this tab to configure the parameters to be displayed on the block in the
Monitoring mode. See the Control Building Guide and/or the online help for
more information.
20
Click the Block Preferences tab to display it.
21
Use this tab to configure the viewing preferences for the block. See the
22
If you have a template license, click the Template Defining tab to display it.
23
Use this tab to select which parameters are to be template defining. See the
24
When you completed entering configuration data, click the OK button to close
the configuration form and save the data.
25
Assigning A-B Drive to Execution Environment
Prerequisites
Control Builder.
You have created a C200 Controller block in the Project tab.
You have added an A-B Drive Interface block to the Project tab.
Considerations
R400
April 2010
All illustrations used in the following procedure are for example purposes only.

Honeywell
61

To assign A-B Drive to CEE

Step
1
Action
On the Edit menu, click Execution Environment Assignment; or click the

on the toolbar to call up the
Execution Environment Assignment button
Execution Environment Assignment dialog, as shown in the sample
illustration below.
If the IOMs tab is not on display in the Available modules list box, click the
tab to display it.
Click the A-B Drive Interface module to be assigned to select it.
62
In the Assign To list box, click the CEE block that the A-B Drive is to be
assigned to select it.
Click the Assign -> button to assign the selected module to the given CEE
Honeywell
R400
April 2010

Step
Action
block.
5
Check that the A-B Drive Interface block now appears in the Assigned
Modules list box for the given CEE block, as shown in the sample illustration
below.
Note that the equal symbol
and the down arrow symbol
to the Controller.
R400
April 2010
prefix means that the block has been assigned

prefix means that the block has been loaded
Click the Close button to exit the dialog and save the assignments.

Honeywell
63

5.7. Loading configuration data to A-B Drive
5.7
Loading configuration data to A-B Drive
Prerequisites
Control Builder.
You have loaded the Controller and its execution environment.
You have assigned the A-B Drive Interface block to the loaded Execution
Environment
Considerations
The following procedure is based on doing an initial load of a block from the
Project tab. You can also initiate a re-load of a block from the Monitoring tab.
If you change the values of the datalink enabling configuration parameters, a re-load
will fail. These parameters can change the sizes of the ASA connection points. If the
datalink enabling parameters must be changed, delete the A-B Drive Interface block
from the Controller in the Monitoring tab first and then reload the block from the
Project tab.
All the illustrations used in the procedure are for example purposes only.
The load operation is still an offline function. The Load Dialog box
provides the ability to automatically inactivate a component during a
load and then return the component to its active state. Do not use
this automatic inactivate/activate function, if your process cannot
tolerate the load disruption and consequent delay in activation. In
this case, you must manually toggle the component state through
the Monitoring tab in Control Builder.
To load A-B Drive block

Step
1
64
Action
In the Project tab, click the plus signs to expand the tree hierarchy for the
Controller, CEE, and I/O icons, as required.

Honeywell
R400
April 2010

Step
R400
April 2010
Action
Right-click the A-B Drive icon and select Load from the menu to call up the
Load dialog.

Honeywell
65

Step
Action
Be sure the check box in the Load column is checked.

Click the down arrow in the Post Load State column to select another
state.
Check the check box at the bottom of the dialog to automatically change
the state of the A-B Drive to the selected Post Load State after the load is
completed.
66
Click the OK button to initiate the load and track progress through the Load
Monitor dialog.
After load completes, check that the A-B Drive icon now appears in the
Monitoring tab tree hierarchy.

Honeywell
R400
April 2010
6. Allen-Bradley Drive Interface Operation

6.1 Monitoring Allen-Bradley Drive Interface Functions
through Monitoring Tab in Control Builder
Checking operational Status
You can monitor the run-time parameter values for a given drive through the Monitoring
tab in Control Builder as outlined in the following procedure.
Prerequisites
You have logged on with sufficient privileges to make changes in a control strategy.
You have loaded a control strategy to the Controller and can view the A-B Drive
icon through the Monitoring tab of Control Builder.
Considerations
The following procedure outlines how to view A-B Drive operation. You can also
view I/O channel operation through the Drive Status and Datalink Status tabs for
the given A-B Drive Input block or Logic Control and Datalink Status tabs for the
given A-B Drive Output block on their respective configuration forms in the Control
Module.
To monitor drive operation

Step
Action
In the Monitoring tab, double-click the A-B Drive I/O icon (green) to open its
configuration form.
Click the Status/Data tab to open it and view its contents.
Click the Datalink Parameters tab to open it and view its contents.
Click the OK button to close the configuration form.
A-B drive interface block icon appearances

The following table summarizes the various appearances that an A-B Drive I/O block
icon in Control Builder can assume based on configuration, view, and current A-B Drive
operating state and status.
R400
April 2010

Honeywell
67

6.1. Monitoring Allen-Bradley Drive Interface Functions through Monitoring Tab in Control Builder
If Icon is . . .
Then, it represents . . .
And, Module
State Is. . .
Project Tab
Drive configured for operation in Project.
N/A
Drive is loaded, but not monitoring
N/A
Drive is inactive
Idle
Drive is Active
Run
Drive with communication failure
Offnet
Failed Drive
Offnet
(gray)
Monitoring Tab
(gray)
(blue)
(green)
(red/black
exclamation)
(red/red
exclamation)
Monitoring/Interacting with given component/block

Once you download a Controller and its contents, you can use the Monitoring tab to
interact with the components including the function blocks in the Control Module.
You simply double-click the desired component/block icon in the hierarchy tree menus
under the Controller icon to call up the associated Configuration form or open the
Control Module in the Control Drawing to double-click blocks contained in the CM.
Click the given Configuration form tab to view the current status of the related block
data. Both the A-B Drive Interface and CM function blocks must be active to view on68

Honeywell
R400
April 2010

line data. The data can be viewed either by name or parameter reference by not checking
or checking the Show Parameter Names checkbox at the bottom of each tab.
Please refer to the Control Building Guide sections in On-Line Monitoring
Using Control Builder for detailed information:
Setting the CEE Inactive
Changing Parameters while Monitoring
Component/block interaction considerations

The following table summarizes things to consider when interacting with a given
component/block through the Monitoring tab in Control Builder.
If You Initiate This Action . . .
Inactivate A-B Drive I/O block
Then, Resulting Operation Is . . .

Drive output terminals hold the value applied at
the time of inactivation.

Fail-safe values are applied to all parameters.
INIT_REQ is asserted on associated Analog
Output Channel block.

The icon representing the module in the
Monitoring tab becomes blue.

The Detail Display shows INACTIVE state (and
proper Fail-Safe values on parameters).

No fault alarms in Experion Server (communication
with the module is not disrupted).

No change in the Status LED of the
communications adapter.
Inactivate a Control Module containing

a Drive Output block

Fail-safe values are applied to all parameters.

R400
April 2010

Honeywell
69


Inactivate a Control Module containing

an AOCHANNEL block associated with
an A-B Drive I/O block

Output Channel block.


Inactivate a CEE block containing an

A-B Drive I/O block

Output channel block.


Delete an A-B Drive I/O block
The A-B Drive I/O module block sends a last
packet of data to the drive with the Stop bit set and
the frequency reference to 0. The drive will stop.
The A-B Drive I/O block closes the connection to
the drive.
The Status LED of the communications adapter
will be flashing green.

The icon for the A-B Drive I/O block is removed
from the Monitoring tab under Control Builder

Delete a Drive Output Channel block
70
The system behavior depends on the A-B Drive I/O
block's EXECSTATE.
If the A-B Drive I/O block is Active, the block

sets the Stop bit in the Logic Command word
and sends it to the drive. The drive will stop.
If the A-B Drive I/O block is Inactive, the

communication path is broken and the
controller cannot stop the drive when the
Drive Output channel block is deleted.

Honeywell
R400
April 2010

WARNING
Deleting the Drive Output Channel Block
while the A-B Drive I/O block is Inactive
does not set the STOP bit in the Logic
Control word.
The drive may continue to operate after
the block is deleted.
Delete an AOCHANNEL block

associated with an A-B drive
The A-B Drive I/O block sends a last packet of data
to the drive commanding the device to go to the

'unpowered state' or a speed reference of 0 Hz.
WARNING
The drive may continue to operate after
the block is deleted.
A Speed Reference of 0 (zero) may not
stop the drive device. The behavior
depends on the Min/Max and
Forward/Reverse Speed Limits as
configured in the Drive.
Ram Retention Restart of C200

Controller
The following occurs after a Ram Retention Restart:

The CEE will be in the IDLE state.
All parameters will be set to their fail safe values.
The A-B Drive will be in the state based on the
communications adapter configuration.
When you command the CEE to RUN, the following

occurs:
The AOCHANNEL' s output (OP) parameter back
initializes to the current speed for the drive.

The Drive Output Channel resumes sending the
Logic Command parameters to the drive device.

R400
April 2010

Honeywell
71

6.2. Monitoring Allen-Bradley Drive Interface Functions through Station Displays

The Drive Input Channel displays the current Drive
Status parameters received from the drive device.
6.2 Monitoring Allen-Bradley Drive Interface Functions

through Station Displays
Using Station Detail displays
The Experion server Station application includes pre-configured Detail displays for the
A-B Drive Interface function blocks. These displays are the default entries for the Point
Detail Page parameter on the Server Displays tab of the configuration form. Once you
establish communications with an A-B Drive, you can begin monitoring the status of any
component that has been loaded as part of a Control Strategy to an Experion Controller
with points registered in the Experion server. The Detail displays let you quickly view
the component's current state, fault status, and pertinent configuration data.
Using Station Event Summary display
Like the Detail displays, the Alarm and Event Summary displays support the integration
of A-B Drive generated notifications and events. It is integrated with Experion
component data and is for the most part self-explanatory. Use this display to get a quick
review of recent actions that have been initiated within the system.
72

Honeywell
R400
April 2010
7. Allen-Bradley Drive Interface Troubleshooting

7.1
Isolating Problems
This section offers some general data about fault classifications, initial checks, and fixing
common problems that may help you isolate the cause of a problem.
If you have observed a specific symptom and/or identified an error code, go to the Fixing
Common Problems section to see if you can find a matching topic.
7.2
Fault Classifications
The following table lists some possible ways for classifying faults along with some
identifying characteristics.
Fault Classification
Hard Failure
Characteristics
Failure detected by hardware; operation cannot continue.

If the fault does not prevent software processing the
problem, the affected node will be rebooted under
software control into the FAIL State.
If failure occurs on Primary node, it triggers a
switchover to synchronized Secondary node.

If failure occurs on Secondary node, it results in loss of
synchronization and reduced availability until the

problem is resolved.
If failure occurs on non-redundant node, it results in
loss of control and loss of view.

Severe Failure
Failure detected by software; operation cannot continue.

The affected node will be rebooted under software control
into the FAIL State.
The failure scenarios are as listed in the row above for the
Hard Failure.
Soft Failure
Failure detected by software; operation continues with full

control and full view. Soft failures are alarmed to the
operator. FTE will be monitored by the FTE System
Management Tool.
If failure occurs on Primary node, it does not trigger a
switchover to synchronized Secondary node.

If failure occurs on Secondary node, it does not result
R400
April 2010

Honeywell
73

7.3. Initial Checks
Fault Classification
Characteristics
in loss of synchronization.
If failure occurs on non-redundant node, it does not
result in loss of control and loss of view.

Installation/Startup
Failure
Detected by software. Node may not become operational.

This failure does not apply to synchronized Primary
node, since installation and startup must be successful

to reach synchronized Primary state.
If failure occurs on Secondary node, it results in the
inability to complete the initial synchronization and to

view the node on the network.
If failure occurs on non-redundant node, it results in the
inability to commence control and to view the node on

the network.
Communication
7.3
Communication errors between peer nodes and/or I/O

devices, including Fault Tolerant Ethernet Bridge (FTEB),
do not cause any node state change.
Initial Checks
This section offers some checks that you can make to help isolate the problem. The
checks are arranged in no particular order.
Checking Control Builder error code reference

An indication of a problem may be in the form of an error dialog that includes an error
message and possibly an error code in Control Builder.
The syntax for a typical Control Builder error message is as follows:
Connection to device is not open EPKS_E_CL_NOCONN(6L.101.3326)
In this syntax, the error code is the last four digits in the message or 3326.
Please refer to the Control Builder Error Codes Reference book for applicable error code
information.
74

Honeywell
R400
April 2010

7.3. Initial Checks
Viewing flash log

The Flash.txt log provides a list of firmware updates that have been initiated.
To view the log, navigate to this file location on the server: C:\Program
Files\Honeywell\Experion PKS\Engineering Tools\system\bin\Flash.txt.
Viewing release information log
The ReleaseInfo.txt log provides a list of Experion software releases that have been
installed on the computer.
Files\Honeywell\Experion PKS\Engineering Tools\system\bin\ReleaseInfo.txt.
Viewing trace log
The TraceLogRs.txt log provides a list of definitions for strings associated with
breadcrumbs data for given hardware components. The breadcrumbs provide a way to
trace operations leading up to an event.
Files\Honeywell\Experion PKS\Engineering Tools\system\bin\TraceLogRs.txt.
Checking server point build log
The SvrPtBld_servername.txt log provides list of process (CB) points built in the server
database.
To check the log, navigate to this file location on the server: C:\Program
Files\Honeywell\Experion PKS\Engineering Tools\temp\SvrPtBld_servername.txt.
Checking server point build error log
The svrptblderr_servername.txt log provides list of any errors associated with process
(CB) points built in the server database
To check the log, navigate to this file location on the server: C:\Program
Files\Honeywell\Experion PKS\Engineering Tools\temp\svrptblderr_servername.txt.
Checking error log
The Errlog_n.txt log provides a running list of Control Builder detected errors in
chronological order. The n represents any number that is assigned to the most recent log.
To check the log, navigate to this file location on the server:
C:\ProgramData\Honeywell\Experion PKS\ErrLog_n.txt.
R400
April 2010

Honeywell
75

7.4. Fixing Common Problems
Prior to R400, the Errlog_n.txt file was stored in the following location on the server:
C:\Documents and Settings\All Users\Application Data\Honeywell\Experion PKS\Errlog_n.txt.
Using NetworkTools to capture chassis information
Please refer to the Capturing chassis information using NetworkTools section
in the Control Hardware Troubleshooting and Maintenance Guide for more
information.
7.4
Fixing Common Problems

This section identifies some common problems and describes how you might fix them.
Controller switchover
The redundant C200 Controller initiates a switchover while connected to Allen-Bradley
drive.
Diagnostic Check
Backup C200 Controller becomes the primary controller.
Cause 1
Switchover initiated through operator command or fault detection.
Solution
Works as intended. Check secondary Controller for cause of fault, if

applicable.
A-B Drive Response
No loss of connection to the drive.
The communication adapter Status LED remains solid Green.
No communication fault alarms are generated for the module

as a result of the switchover.
Output signal on the field terminals of the A-B drive holds its value
during switchover of the connection. This lasts no more than 500

milliseconds.
Cable fault or loss of power

Cable connection to A-B drive is lost. The main power source has been shut down or is
experiencing a brownout or blackout condition.
Diagnostic Check
The LEDs on the communications adapter are off.

In the Monitoring tab, the A-B Drive icon turns Red.
76

Honeywell
R400
April 2010

7.4. Fixing Common Problems
Comm Failure is displayed on the Detail Display of the connected A-B
drive.
Communication failure alarms are generated for connected A-B drive
blocks.
Cause 1
Main power source has been disconnected or shut down either manually
or temporarily by brownout or blackout condition.
Solution
Re-connect the main power source or turn it On or wait for temporary

brownout or blackout condition to pass.
Restore broken cable connection.
A-B Drive Response
When connection to A-B drive is lost:

The A-B drive goes into the Faulted state. The A-B Drive behavior is
based on the communication adapter's configuration.

A-B Drive block stops writing data to the drive as long as the
connection is bad.
A-B drive block clears all fault indications.
A-B drive block Indicates 'Path Broken', which in turn asserts
INITREQ on all associated Analog Output Channel blocks.

A-B Drive block parameters go to fail-safe values.
When connection to A-B drive is restored:

In the Monitoring tab, the A-B Drive icon turns Green.
OK is displayed in on the Detail Display of the connected A-B drive.
Associated alarms 'return to normal' for the connected A-B drive
Output device terminals continue to hold at the drive's faulted state.
This continues until the connection has remained good for two
executions of the A-B drive block. At this point, data from the associated
I/O Channel blocks will then once again be written to the output device.
Cause 2
The 24 Vdc or 120/240 Vac chassis power supply failed or power cable
has been disconnected or failed.
Solution
Replace the chassis power supply or re-connect/replace the power

cable.
R400
April 2010

Honeywell
77

7.5. Getting Further Assistance
7.5
Getting Further Assistance
Allen-Bradley drive troubleshooting reference

Refer to the given Allen-Bradley Drive User Manual or Hardware Service Manual for
more information.
Other troubleshooting sources
The following table lists other documents and sections that contain troubleshooting
information for other Experion subsystems.
All of these documents are available from Knowledge Builder. Some documents are also
supplied as part of Station Help. For documents that can be accessed directly from this
page, click on the link, otherwise look for the document within Knowledge Builder
where xxx equals the current release number.
Document/Section
Experion Rxxx > Reference
Comments
There is a separate interface reference for

each type of controller other than the Process
Controller; for example, the ASEA Interface
Reference.
Most of these references contain an interfacespecific troubleshooting section.
Experion Rxxx > Reference > Control Builder

Error Codes Reference
Describes error codes generated from within

Control Builder.
Experion Rxxx > Troubleshooting and

Maintenance > Control Hardware
Troubleshooting and Maintenance Guide
The main repository for troubleshooting,

maintenance and repair of Process Controllers.
Experion Rxxx > Configuration > DeviceNet

Implementation Guide > Troubleshooting
DeviceNet Status Failures
Describes error codes generated from

DeviceNet Interface Board.
Experion Rxxx > Installation and Upgrades >

Fault Tolerant Ethernet Bridge Implementation
Guide > Service > Troubleshooting
Troubleshooting FTE bridges.
Experion Rxxx > Installation and Upgrades >

Fault Tolerant Ethernet Installation and Service
Guide > Troubleshooting FTE Nodes
Troubleshooting FTE nodes.
Experion Rxxx> Reference > Honeywell TDC

3000 Data Hiway Interface Reference > TDC
Troubleshooting TDC 3000 Hiway problems.
78

Honeywell
R400
April 2010

Document/Section
Comments
error codes and Troubleshooting

Experion Rxxx > Configuration > Qualification
and Version Control System User Guide >
QVCS Troubleshooting
Troubleshooting QVCS.
Experion Rxxx > Operations > SafeView User's

Guide > Appendix D - SafeView Error
Messages
Describes the meaning of SafeView

configuration errors.
Experion Rxxx > Reference > Server Scripting

Reference > Server scripting error messages
Describes the meaning of error messages in

the server log specific to server scripting.
Experion Rxxx > Reference > System

Management Configuration Guide >
Troubleshooting System Management
Describes the meaning of System

Management Configuration errors.

Troubleshooting SES
Describes the meaning of SES Configuration

errors.

Troubleshooting SPS
Describes the meaning of SPS Configuration

errors.
Experion Rxxx > Planning and Design >

Planning, Installation, and Service for WS360
Troubleshooting workstation nodes used in

Experion and TPN.
Guidelines for requesting support

If you cannot resolve a problem using this guide, you can request support from your
Honeywell Solution Support Center.
When requesting support, please supply as many relevant details as possible, including:
Short summary of the problem
Product Name and release.
Recent changes, such as upgrades/service packs, to Experion software, Windows or

other applications.
Subsystem and its version/build, if the problem relates to a particular subsystem,

such as Station or Quick Builder.
If the problem relates to Display Builder, please specify whether it is HMIWeb
Display Builder (for HMIWeb displays) or Display Builder (for DSP displays).
R400
April 2010

Honeywell
79

80
Operating system, variant and service pack, for example "Windows 2000 Server,
SP5".
Instructions on how to reproduce the problem. If the problem is reproducible,

please supply step-by-step instructions - the more detailed the steps the better.
Diagnostic package that contains any relevant logs.

Honeywell
R400
April 2010

1860 W. Rose Garden Lane
Phoenix, AZ 85027 USA

Interface AB Experion

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Interface AB Experion

Hochgeladen von

Copyright:

Verfügbare Formate

Honeywell Process Solutions

Allen-Bradley Drive Interface

Notices and Trademarks

Honeywell Process Solutions

Experion Allen-Bradley Drive Interface through ControlNet Reference

About This Document

Experion Allen-Bradley Drive Interface through ControlNet Reference

Support and Other Contacts

Support and Other Contacts

Honeywell Solution Support Center

Europe, Middle East, and Africa (EMEA)

Honeywell Global TAC Pacific

Honeywell Global TAC India

Experion Allen-Bradley Drive Interface through ControlNet Reference

Support and Other Contacts

Honeywell Global TAC Korea

Peoples Republic of China

Honeywell Global TAC China

Honeywell Global TAC South East Asia

Honeywell Global TAC Taiwan

Experion Allen-Bradley Drive Interface through ControlNet Reference

Support and Other Contacts

Honeywell Global TAC Japan

World Wide Web

Experion Allen-Bradley Drive Interface through ControlNet Reference

TIP: Identifies advice or hints for the user, often in terms of

Indicates a situation which, if not avoided, may result in equipment

Experion Allen-Bradley Drive Interface through ControlNet Reference

Functional earth terminal: Used for non-safety purposes such as

Experion Allen-Bradley Drive Interface through ControlNet Reference

About this guide ............................................................................................ 15

ALLEN-BRADLEY DRIVE INTERFACE PURPOSE....................17

A-B Drive Interface Library........................................................................... 17

I/O Channel Library ....................................................................................... 18

Drive Interface Data Flow Model.................................................................. 18

A-B Drive Support and Documentation ...................................................... 20

Legacy SCANport drives support .........................................................................................20

About ControlNet I/O drive data transfer.................................................... 23

Logic command data ............................................................................................................24

Differences between Legacy SCANport and PowerFlex Drives............... 28

ALLEN-BRADLEY DRIVE INTERFACE PLANNING AND DESIGN

General Planning References ...................................................................... 31

C200 with A-B Drive Interface Topology..................................................... 31

A-B Drive Interface Configuration Rules .................................................... 33

A-B Drive Interface Capacity considerations ............................................. 34

Experion Allen-Bradley Drive Interface through ControlNet Reference

Installation References .................................................................................37

ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION ...... 39

Configuration Tools for A-B Drive Interface ...............................................39

A-B Drive Interface Configuration Data Location and Interaction............39

Adding Allen-Bradley DRIVE block to Project ............................................42

Adding Drive I/O Channel to Control Module .............................................50

DRIVE_INPUT block functional overview............................................................................ 50

Assigning A-B Drive to Execution Environment ........................................61

Loading configuration data to A-B Drive ....................................................64

ALLEN-BRADLEY DRIVE INTERFACE OPERATION ............... 67

Experion Allen-Bradley Drive Interface through ControlNet Reference

ALLEN-BRADLEY DRIVE INTERFACE TROUBLESHOOTING.73

Isolating Problems ........................................................................................ 73

Fault Classifications ..................................................................................... 73

Initial Checks ................................................................................................. 74

Checking Control Builder error code reference ....................................................................74

Fixing Common Problems............................................................................ 76

Getting Further Assistance .......................................................................... 78