Rockwell Automation PowerFlex 22-COMM-C ControlNet Adapter, PowerFlex 40 Drive, 400 Drive PowerFlex 4 Drive, PowerFlex 22-XCOMM-DC-BASE DSI External Comms Kit User Manual
Below you will find brief information for ControlNet Adapter PowerFlex 22-COMM-C, PowerFlex 4 Drive PowerFlex 40 Drive, PowerFlex 4 Drive PowerFlex 400 Drive. The ControlNet Adapter PowerFlex 22-COMM-C is a communication option intended for installation into a PowerFlex 40 or PowerFlex 400 drive. It can also be used with other {detected_brand} products that support a DSI communication adapter, such as the DSI External Comms Kit (22-XCOMM-DC-BASE). The External Comms Kit enables PowerFlex 4 drives (which cannot support an internally-mounted adapter) to connect to a ControlNet network.
Advertisement
Advertisement
ControlNet
Adapter
22-COMM-C
FRN 1.xxx
User Manual
Important User Information
Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and
Maintenance of Solid State Controls (Publication SGI-1.1 available from your local
Rockwell Automation sales office or online at http://www.rockwellautomation.com/
literature) describes some important differences between solid state equipment and hard-wired electromechanical devices. Because of this difference, and also because of the wide variety of uses for solid state equipment, all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc. is prohibited.
Throughout this manual, when necessary we use notes to make you aware of safety considerations.
WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss.
Important: Identifies information that is critical for successful application and understanding of the product.
ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you:
• identify a hazard
• avoid the hazard
• recognize the consequences
Shock Hazard labels may be located on or inside the equipment (e.g., drive or motor) to alert people that dangerous voltage may be present.
Burn Hazard labels may be located on or inside the equipment (e.g., drive or motor) to alert people that surfaces may be at dangerous temperatures.
Allen-Bradley, PowerFlex, ControlLogix, PLC-5, DriveExplorer, DriveExecutive, DriveTools SP, and ControlFLASH are either registered trademarks or trademarks of Rockwell Automation, Inc.
RSLogix, RSLinx, and RSNetWorx are trademarks of Rockwell Software.
ControlNet is a trademark of ControlNet International.
Windows and Microsoft are registered trademarks of Microsoft Corporation.
Summary of Changes
The information below summarizes the changes made to this manual since its last release (May 2005):
Description of New or Updated Information
In the Chapter 4 introduction, added an Important paragraph about I/O connections.
In the “About Explicit Messaging” section, added an Important paragraph about “unconnected” and “connected” messages.
In the “Configuring the RS-485 Network” section, corrected the Important paragraph text. The daisy-chained drive(s) parameter A106 - [Comm Loss
Time] is not used in Multi-Drive mode.
In the “ControlLogix Explicit Messaging” section, corrected these drive parameter subheading names:
• Parameter D003 from [Current Output] to [Output Current]
• Parameter P039 from [Current Output] to [Accel Time 1]
In the “Environmental” specifications section, corrected the maximum
Farenheit Operating Temperature value from 149°F to 122°F.
Page(s)
soc-ii
Summary of Changes
Table of Contents
Preface
Chapter 1
Chapter 2
Chapter 3
Chapter 4
Chapter 5
About This Manual
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1
Conventions Used in this Manual . . . . . . . . . . . . . . . . . . . . . P-2
Rockwell Automation Support. . . . . . . . . . . . . . . . . . . . . . . . P-3
Getting Started
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Compatible Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Required Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Quick Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Installing the Adapter
Preparing for an Installation. . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Setting Operating Mode and Node Address Switches . . . . . . 2-1
Connecting the Adapter to the Network . . . . . . . . . . . . . . . . 2-3
Connecting the Adapter to the Drive . . . . . . . . . . . . . . . . . . . 2-4
Applying Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Configuring the Adapter
Configuration Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Using the PowerFlex 4-Class HIM . . . . . . . . . . . . . . . . . . . . 3-2
Setting the Node Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Setting the I/O Configuration. . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Setting a Fault Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Viewing the Adapter Configuration . . . . . . . . . . . . . . . . . . . . 3-7
Resetting the Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Configuring the I/O
ControlLogix Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
PLC-5 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Using the I/O
About I/O Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Understanding the I/O Image. . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Using Logic Command/Status . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Using Reference/Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Example Ladder Logic Program Information . . . . . . . . . . . . 5-4
ControlLogix Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
PLC-5 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
ii
Table of Contents
Chapter 6
Chapter 7
Chapter 8
Using Explicit Messaging
About Explicit Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Performing Explicit Messages . . . . . . . . . . . . . . . . . . . . . . . 6-2
ControlLogix Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
PLC-5 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Using Multi-Drive Mode
Single Mode vs. Multi-Drive Mode . . . . . . . . . . . . . . . . . . . . 7-1
System Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Understanding the I/O Image . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Configuring the RS-485 Network . . . . . . . . . . . . . . . . . . . . . 7-7
Example Configuration Settings . . . . . . . . . . . . . . . . . . . . . . 7-8
ControlLogix I/O Example . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
ControlLogix Explicit Messaging . . . . . . . . . . . . . . . . . . . . 7-22
PLC-5 I/O Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
Troubleshooting
Locating the Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . 8-1
PORT Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
MOD Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Net A and B Status Indicators Together. . . . . . . . . . . . . . . . . 8-4
Net A or B Status Indicators Independently . . . . . . . . . . . . . 8-4
Adapter Diagnostic Items in Single Mode . . . . . . . . . . . . . . 8-5
Adapter Diagnostic Items in Multi-Drive Mode . . . . . . . . . . 8-6
Viewing and Clearing Events. . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Appendix A Specifications
Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Electrical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Mechanical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Regulatory Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Appendix B Adapter Parameters
About Parameter Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Parameter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Table of Contents
Appendix C ControlNet Objects
Identity Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Assembly Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Register Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6
Parameter Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9
Parameter Group Object (Single Mode only) . . . . . . . . . . . C-12
PCCC Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14
DSI Device Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20
DSI Parameter Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-23
DSI Fault Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-27
DSI Diagnostic Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-29
Appendix D Logic Command/Status Words
PowerFlex 4/40/400 Drives . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Glossary
Index
iii
iv
Table of Contents
Preface
About This Manual
Topic
Page
Conventions Used in this Manual P-2
Rockwell Automation Support P-3
Related Documentation
For:
DriveTools™ SP (includes
DriveExecutive™)
HIM
PowerFlex
®
4 Drive
PowerFlex
®
40 Drive
PowerFlex
®
400 Drive
RSLinx™ or RSLinx Lite
RSLogix™ 5
RSLogix™ 5000
RSNetWorx™ for
ControlNet™
1756-CNB/R
®
and ControlLogix
Refer to:
DriveExplorer online Help (installed with the software) http://www.ab.com/drives/drivetools, and
DriveTools SP online Help (installed with the software)
HIM Quick Reference
PowerFlex 4 User Manual
PowerFlex 4 Quick Start
PowerFlex 40 User Manual
PowerFlex 40 Quick Start
PowerFlex 400 User Manual
Getting Results with RSLinx Guide, and online help (installed with the software)
RSLogix 5 Getting Results Guide*
RSLogix 5000 Getting Results Guide*
* And online help (installed with the software)
RSNetWorx for ControlNet Getting Results Guide, and online help (installed with the software)
Publication
—
—
22HIM-QR001…
22A-UM001…
22A-QS001…
22B-UM001…
22B-QS001…
22C-UM001…
LINX-GR001…
LG5-GR001…
9399-RLD300GR
CNET-GR001…
ControlLogix ControlNet Interface Module User Manual 1756-6.5.3
Documentation can be obtained online at http://www.rockwellautomation.com/literature .
P-2
About This Manual
Conventions Used in this Manual
The following conventions are used throughout this manual:
• Parameter names are shown in the format Parameter xx - [*]. The xx represents the parameter number, and the * represents the parameter name — for example, Parameter 01 - [Mode].
• Menu commands are shown in bold type face and follow the format
Menu > Command. For example, if you read “Select File > Open,” you should click the File menu and then click the Open command.
• The firmware release is displayed as FRN X.xxx. The “FRN” signifies Firmware Release Number. The “X” is the major release number. The “xxx” is the minor update number.
• RSNetWorx for ControlNet (version 5.11), RSLinx (version 2.43),
RSLogix 5000 (version 13.03) and RSLogix 5 (version 6.30) were used for the screen shots in this manual. Different versions of the software may differ in appearance and procedures.
• This manual provides information about the 22-COMM-C ControlNet adapter and using it with PowerFlex 4-Class drives. The adapter can be used with other products that support a DSI adapter, such as the
DSI External Comms Kit (22-XCOMM-DC-BASE). Refer to the documentation for your product for specific information about how it works with the adapter.
About This Manual
P-3
Rockwell Automation Support
Rockwell Automation, Inc. offers support services worldwide, with over
75 sales/support offices, over 500 authorized distributors, and over 250 authorized systems integrators located through the United States alone.
In addition, Rockwell Automation, Inc. representatives are in every major country in the world.
Local Product Support
Contact your local Rockwell Automation, Inc. representative for:
• Sales and order support
• Product technical training
• Warranty support
• Support service agreements
Technical Product Assistance
If you need to contact Rockwell Automation, Inc. for technical assistance, please review the information in
first. If you still have problems, then call your local Rockwell
Automation, Inc. representative.
U.S. Allen-Bradley Drives Technical Support:
E-mail: [email protected]
Tel: (1) 262.512.8176
Fax:
Fax (1) 262.512.2222
Online: www.ab.com/support/abdrives
UK Customer Support Center:
E-mail: [email protected]
Tel: +44 (0) 870 2411802
+44 (0) 1908 838804
Germany Customer Service Center:
E-mail: [email protected]
Tel:
Fax:
+49 (0) 2104 960-630
+49 (0) 2104 960-501
P-4
Notes:
About This Manual
Chapter
1
Getting Started
The 22-COMM-C ControlNet adapter is a communication option intended for installation into a PowerFlex 40 or PowerFlex 400 drive. It can also be used with other Allen-Bradley products that support a DSI communication adapter, such as the DSI External Comms Kit
(22-XCOMM-DC-BASE). The External Comms Kit enables PowerFlex
4 drives (which cannot support an internally-mounted adapter) to connect to a ControlNet network.
Topic
Components
Page
Topic
Page
Figure 1.1 Components of the Adapter
➊
➋
LEDs are located on bottom side of adapter board
➏
➌ ➍ ➎
Description Item Component
➊
Status Indicators Four LEDs that indicate the status of the ControlNet connection,
DSI, and the adapter. Refer to
➋
DSI Connector A 20-pin, single-row shrouded male header. An Internal Interface cable is connected to this connector and a connector on the drive.
➌
Channel A Coax Receptacle Channel A BNC connection for the ControlNet cable.
➍
Channel B Coax Receptacle Channel B BNC connection for the ControlNet cable.
➎
1x/5x Operating Mode
Jumper (J7)
Selects Single (1x) or Multi-Drive (5x) mode of operation. Refer to
Setting Operating Mode and Node Address Switches on page 2-1
.
➏
ControlNet Node Address
Switches
Sets a unique node address for the adapter. Refer to Setting
Operating Mode and Node Address Switches on page 2-1 .
1-2
Getting Started
Features
The ControlNet adapter features the following:
• The adapter is normally installed in a PowerFlex 40 or PowerFlex 400 drive. It can also be used in a DSI External Comms Kit
(22-XCOMM-DC-BASE).
• A jumper lets you select between Single or Multi-Drive mode of operation. In Single mode (default), the adapter represents a single drive on one node. In Multi-Drive mode, the adapter represents up to
5 drives on one node.
• A number of configuration tools can be used to configure the adapter and connected drive. The tools include an external PowerFlex 4-Class
HIM (22-HIM-*) or drive-configuration software such as
DriveExplorer (version 3.01 or higher) or DriveExecutive (version
3.01 or higher).
• Status indicators report the status of drive communications, the adapter, and network.
• Supports I/O, including Logic Command/Reference, for all drives connected in Single or Multi-Drive mode.
• The following table shows the various controllers that can be used with the 22-COMM-C adapter and whether they support explicit messaging (parameter read/write, etc.) on a ControlNet network:
Controller Used With 22-COMM-C
ControlLogix 1756-L55/L61/L62/L63
FlexLogix 1794-L33/L34
CompactLogix 1769-L20/L30/L35E
MicroLogix1000 1761-L10/L16/L20/L32
MicroLogix1200 1762-L24/L40
MicroLogix1500 1764-LSP/LRP
PLC-5 1785-L20C/L40C/L46C/L80C
SoftLogix 1789-L10/L30/L60
Supports Explicit Messaging
Yes
✔
✔
✔
✔
✔
✔
✔ (1)
✔
Single Mode Multi-Drive
No Yes
✔
✔
✔
✔
✔
✔
No
✔
✔
(1)
Due to controller limitations, explicit messaging can only be performed on drive parameters up to Parameter 256.
• User-defined fault actions determine how the adapter and drive (or the network and controllers in program mode.
DSI External Comms Kit) respond to communication disruptions on
Getting Started
Compatible Products
The adapter is compatible with Allen-Bradley PowerFlex 4-Class
(Component-Class) drives and other products that support an internal
DSI adapter. At the time of publication, compatible products include:
• PowerFlex 4 drives with DSI External Comms Kit
• PowerFlex 40 drives
• PowerFlex 400 drives
1-3
Required Equipment
Equipment Shipped with the Adapter
When you unpack the adapter, verify that the package includes:
❑ One ControlNet adapter
❑ One 15.24 cm (6 in.) Internal Interface Cable
❑ This manual
User-Supplied Equipment
To install and configure the adapter, you must supply:
❑ A small flathead screwdriver
❑ Appropriate ControlNet cables (refer to the ControlNet Fiber Media
Planning and Installation Guide, Publication CNET-IN001…, for details.)
❑ A configuration tool, such as:
– PowerFlex 4-Class HIM (22-HIM-*)
– DriveExplorer (version 3.01 or higher)
– DriveExecutive stand-alone software (version 3.01 or higher) or bundled with the DriveTools SP suite (version 1.01 or higher)
– RSNetWorx for ControlNet
❑ Controller configuration software (Example: RSLogix 5000)
❑ A PC connection to the ControlNet network
1-4
Getting Started
!
!
!
!
!
!
!
Safety Precautions
Please read the following safety precautions carefully.
ATTENTION: Risk of injury or death exists. The PowerFlex drive may contain high voltages that can cause injury or death. Remove power from the PowerFlex drive, and then verify power has been discharged before installing or removing the adapter.
ATTENTION: Risk of injury or equipment damage exists. Only personnel familiar with drive and power products and the associated machinery should plan or implement the installation, start-up, configuration, and subsequent maintenance of the product using the adapter. Failure to comply may result in injury and/or equipment damage.
ATTENTION: Risk of equipment damage exists. The adapter contains ESD (Electrostatic Discharge) sensitive parts that can be damaged if you do not follow ESD control procedures. Static control precautions are required when handling the adapter. If you are unfamiliar with static control procedures, refer to Guarding Against
Electrostatic Damage, Publication 8000-4.5.2.
ATTENTION: Risk of injury or equipment damage exists. If the adapter is transmitting control I/O to the drive, the drive may fault when you reset the adapter. Determine how your drive will respond before resetting the adapter.
ATTENTION: Risk of injury or equipment damage exists. Parameters
08 - [Comm Flt Action] and 09 - [Idle Flt Action] let you determine the action of the adapter and connected PowerFlex drive if communications are disrupted. By default, these parameters fault the drive. You can set these parameters so that the drive continues to run. Precautions should be taken to ensure that the settings of these parameters do not create a risk of injury or equipment damage. When commissioning the drive, verify that your system responds correctly to various situations (for example, a disconnected cable or a faulted controller).
ATTENTION: Risk of injury or equipment damage exists. When a system is configured for the first time, there may be unintended or incorrect machine motion. Disconnect the motor from the machine or process during initial system testing.
ATTENTION: Risk of injury or equipment damage exists. The examples in this publication are intended solely for purposes of example. There are many variables and requirements with any application. Rockwell Automation, Inc. does not assume responsibility or liability (to include intellectual property liability) for actual use of the examples shown in this publication.
Getting Started
1-5
Quick Start
This section is provided to help experienced users quickly start using the adapter. If you are unsure how to complete a step, refer to the referenced chapter.
7
8
2
3
4
5
6
Step
1 Review the safety precautions for the adapter.
Refer to …
Throughout this manual
Drive User Manual
Verify that the PowerFlex drive is properly installed.
Install the adapter.
Verify that the PowerFlex drive is not powered. Then, connect the adapter to the network using a ControlNet cable and to the drive using the Internal Interface cable. Use the captive screw to secure and ground the adapter to the drive.
When installing the adapter in a DSI External Comms Kit, refer to the 22-XCOMM-DC-BASE Installation Instructions
(Publication No. 22COMM-IN001…) supplied with the kit.
Apply power to the adapter.
The adapter receives power from the drive. Apply power to the drive. The status indicators should be green. If they flash
red, there is a problem. Refer to Chapter 8 , Troubleshooting .
Configure the adapter for your application.
Set the following parameters for the adapter as required by your application:
• I/O configuration
• Fault actions
Apply power to the ControlNet scanner and other devices on the network.
—
Verify that the scanner and network are installed and functioning in accordance with ControlNet standards, and then apply power to them.
Configure the scanner or bridge to communicate with the adapter.
Use a network tool such as RSNetWorx for ControlNet to configure the scanner or bridge on the network.
Create a ladder logic program.
Use a programming tool such as RSLogix to create a ladder logic program that enables you to:
• Control the adapter and connected drive using I/O.
• Monitor or configure the drive using Explicit Messages.
1-6
Getting Started
Modes of Operation
The adapter uses four status indicators to report its operating status. They can be viewed on the adapter or through the drive cover (
Figure 1.2 Status Indicators (location on drive may vary)
➊
➋
➌
➍
Bottom side of adapter board
Item
➊
PORT
➋
➌
➍
Status
Indicator
MOD
NET B
NET A or
Normal
Status
(1)
Green
Green
Flashing
Green
Green
Flashing
Green
Off
Description
Normal Operation. The adapter is properly connected and is communicating with the drive.
Normal Operation. The adapter is operational and is transferring I/O data.
Normal Operation. The adapter is operational but is not transferring I/O data.
Normal Operation. The adapter channel is properly connected and communicating on the network.
Normal Operation. The adapter channel has a temporary error, or is in listen-only mode.
Normal Operation. The adapter channel is disabled or not supported.
(1)
If all status indicators are off, the adapter is not receiving power. Refer to
, for instructions on installing the adapter.
If any other conditions occur, refer to Chapter 8
,
➊
➋
➌
➍
Chapter
2
Installing the Adapter
Chapter 2 provides instructions for installing the adapter in a PowerFlex
40 or PowerFlex 400 drive. This adapter can also be installed in a DSI
External Comms Kit. In this case, refer to the 22-XCOMM-DC-BASE
Installation Instructions (Publication No. 22COMM-IN001…) supplied with the kit.
Topic
Page
Setting Operating Mode and Node Address Switches 2-1
Connecting the Adapter to the Network 2-3
Connecting the Adapter to the Drive
Preparing for an Installation
Before installing the adapter, verify that you have all required equipment. Refer to
.
!
Setting Operating Mode and Node Address Switches
Before installing the adapter, you must set its Operating Mode Jumper for Single or Multi-Drive operation, and its Node Address Switches to a unique ControlNet node address.
Important: New settings are recognized only when power is applied to the adapter, or the adapter is reset. If you change a setting, cycle power or reset the adapter to invoke the change.
ATTENTION: Risk of equipment damage exists. The adapter contains ESD (Electrostatic Discharge) sensitive parts that can be damaged if you do not follow ESD control procedures. Static control precautions are required when handling the adapter. If you are
Electrostatic Damage, Publication 8000-4.5.2.
unfamiliar with static control procedures, refer to Guarding Against
2-2
Installing the Adapter
1. Set the adapter Operating Mode Jumper (J7) for Single (1x) or
Multi-Drive (5x) operation (see
below). For complete details on Multi-Drive mode operation, see
Chapter 7 , Using Multi-Drive Mode .
Figure 2.1 Setting Single/Multi-Drive Operation and Node Address Switches
Node Address
Switches
0
9
S2
(Tens Digit)
2 3
1 4
6
5
8 7
0
9
S3
(Ones Digit)
2 3
1 4
6
5
8 7
J7
Single Mode
1x
Operating
Mode Jumper
J7
5x
Multi-Drive
Mode
Jumper Setting Description
Right (1x) position or jumper missing
Sets the adapter for Single mode (default setting) using a single drive connection.
Important: In this mode, connections to multiple drives must be removed since all powered and connected hosts will respond to any message sent by the adapter.
Left (5x) position Sets the adapter for Multi-Drive mode using up to 5 different drives. DSI peripherals (22-HIM-*, 22-SCM-*, etc.) do not operate with the adapter in this mode.
2. Set the adapter node address by rotating the Node Address Switches to the desired value for each digit.
Important: Each node on the network must have a unique address.
The node address must be set before power is applied because the adapter uses the node address it detects when it first receives power. To change a node address, you must set the new value. Then remove and reapply power to the adapter, or reset the adapter.
Switch Settings Description
00-99 Node address used by the adapter if switches are enabled. The default switch setting is 02.
Important: If the address switches are set to “00,” the adapter will use the setting of Parameter 02 - [CN Addr Cfg] for the
node address. Refer to Setting the Node Address on page 3-3 .
The node address switch settings can be verified using a PowerFlex
4-Class HIM, DriveExplorer, or DriveExecutive to view Diagnostic
Item number 28 (listed on
).
Installing the Adapter
Connecting the Adapter to the Network
!
ATTENTION: Risk of injury or death exists. The PowerFlex drive may contain high voltages that can cause injury or death. Remove power from the PowerFlex drive, and then verify power has been discharged before installing or removing an adapter.
1. Remove power from the drive.
2. Use static control precautions.
3. Remove the drive cover.
4. Connect a ControlNet cable to the ControlNet network. See
for an example of wiring to a ControlNet network.
Figure 2.2 Connecting the ControlNet Cable to the Network
ControlLogix Controller with 1756-CNB/R
PowerFlex 40 or PowerFlex 400 Drives
(each with a 22-COMM-C ControlNet Adapter)
2-3
ControlNet Network
(optional redundancy)
5. Route the ControlNet cable through the bottom of the PowerFlex drive (
), and insert the cable plug into the adapter’s mating
receptacle.
2-4
Installing the Adapter
Connecting the Adapter to the Drive
PowerFlex 40 Frames B and C, and PowerFlex 400 Frame C
1. Remove power from the drive.
2. Use static control precautions.
3. Mount the adapter on the required special drive cover (ordered separately — see
for part numbers).
• Frame C: Use the adapter screw to secure the adapter to the cover.
• Frame B: Disregard the screw and snap the adapter in place.
Important: For Frame C drives, tighten the adapter’s lower left screw to ground the adapter (see
). For Frame
B drives, install the special drive cover onto the drive using both cover fasteners to ground the adapter.
4. Connect the Internal Interface cable to the DSI port on the drive and then to the mating DSI connector on the adapter.
Figure 2.3 Connecting DSI Ports with Internal Interface Cable
22-COMM-C Adapter
➊
➋
➌
PowerFlex 40 Drive
(Frame C shown with cover removed)
Item Description
➊
DSI connector
➋
15.24 cm (6 in.) Internal Interface cable
➌
ControlNet cable
Back of Required
Special Drive Cover
Installing the Adapter
2-5
Figure 2.4 Mounting and Grounding the Adapter – PowerFlex 40 Frames B and C, and
PowerFlex 400 Frame C
Adapter Mounted on Back of
Required Special Drive Cover
(Frame C cover shown)
PowerFlex 40 Frame B -- Part Number 22B-CCB
PowerFlex 40 Frame C -- Part Number 22B-CCC
PowerFlex 400 Frame C -- Part Number 22C-CCC
PowerFlex 40 Drive
(Frame C shown with cover removed)
Ground for Frame C Drives
NOTE: For Frame B drives, the lower left adapter screw does not ground the adapter.
To ground the adapter, install the special drive cover onto the drive using both cover fasteners.
2-6
Installing the Adapter
PowerFlex 400 Frames D, E, and F
1. Remove power from the drive.
2. Use static control precautions.
3. Remove the drive cover.
4. With the adapter board right side up, remove its mounting screw from the lower left hole. Save the screw for mounting in Step 7.
5. Connect the Internal Interface cable to the DSI port on the drive (see
).
6. With the adapter board oriented bottom side up, route the Internal
Interface cable under the adapter, and then to the mating DSI connector on the adapter.
7. Install the adapter, bottom side up, to the right side of the display board by snapping it into place. Then insert the adapter mounting screw into the lower left hole on the board.
Important: Tighten the mounting screw in the adapter’s lower left hole to ground the adapter to the drive.
Figure 2.5 Mounting and Connecting the Adapter – PowerFlex 400 Frame D, E, and F Drives
Adapter Installation
(Side View)
Bottom of
Adapter Board
LEDs
Internal Interface
Ribbon Cable
Connector
PowerFlex 400
(Frame D shown with cover removed)
Installing the Adapter
2-7
Applying Power
!
ATTENTION: Risk of equipment damage, injury, or death exists.
Unpredictable operation may occur if you fail to verify that parameter settings and switch settings are compatible with your application.
Verify that settings are compatible with your application before applying power to the drive.
1. Install the drive cover. The status indicators can be viewed on the front of the drive after power has been applied.
2. Apply power to the PowerFlex drive. The adapter receives its power from the connected drive. When you apply power to the adapter for the first time, the status indicators should be green or off after an initialization. If the status indicators are red, there is a problem.
Refer to
,
2-8
Notes:
Installing the Adapter
Chapter
3
Configuring the Adapter
Chapter 3 provides instructions and information for setting the parameters in the adapter.
Topic
Using the PowerFlex 4-Class HIM
Page
Viewing the Adapter Configuration 3-7
For a list of parameters, refer to Appendix B , Adapter Parameters . For
definitions of terms in this chapter, refer to the
Configuration Tools
The adapter stores parameters and other information in its own non-volatile memory. You must, therefore, access the adapter to view and edit its parameters. The following tools can be used to access the
Tool
adapter parameters:
PowerFlex 4-Class HIM
(22-HIM-*)
DriveExplorer Software
(version 3.01 or higher)
DriveExecutive Software
(version 3.01 or higher)
Refer to…
http://www.ab.com/drives/driveexplorer, and
DriveExplorer online help (installed with the software) http://www.ab.com/drives/drivetools, and
DriveExecutive online help (installed with the software)
3-2
Configuring the Adapter
Using the PowerFlex 4-Class HIM
The PowerFlex 4-Class HIM (Human Interface Module) can be used to access parameters in the adapter (see basic steps shown below). It is recommended that you read through the steps for your HIM before performing the sequence. For additional HIM information, refer to the
HIM Quick Reference card.
Note: The HIM will only work when the adapter is set to Single mode.
Using the HIM
Step
1. Power up the drive.
Then plug the HIM into the drive. The
Parameters menu for the drive will be displayed.
2. Press Sel key once to display the Device
Select menu.
Key(s)
Sel
Example Screens
Parameters
Groups
Linear List
Changed Params
DIAG PARAM DSEL MEM SEL
!
Device Select
DSI Devices
DIAG PARAM DSEL MEM SEL
!
DSI Devices
PowerFlex 40
22-COMM-C
3. Press Enter to display the DSI Devices menu. Press Down
Arrow to scroll to
22-COMM-C.
4. Press Enter to select the adapter. The
Parameters menu for the adapter will be displayed.
and
5. Press Enter to access the parameters. Edit the adapter parameters using the same techniques that parameters. you use to edit drive
Parameters
Linear List
Changed Params
DIAG PARAM DSEL MEM SEL
!
Mode
Parameter:
Single Drv
VALUE LIMITS
RO
# 001
0
SEL
!
Configuring the Adapter
3-3
Setting the Node Address
If the Node Address Switches on the adapter are set to a node address of
“00,” the value of Parameter 02 - [CN Addr Cfg] determines the
ControlNet node address.
1. Set the value of Parameter 02 - [CN Addr Cfg] to a unique node address.
Figure 3.1 Node Address Screen on PowerFlex 4-Class HIM (22-HIM-*)
CN Addr Cfg
Parameter: # 002
Default = 2
2
VALUE LIMITS SEL
!
2. Reset the adapter (see Resetting the Adapter on Page 3-6 ).
Setting the I/O Configuration
The I/O configuration determines the number of drives that will be represented on the network as one node by the adapter. If the Operating
is set to the “1x” (Single mode) default position, only one drive is represented by the adapter and Parameter 12
- [DSI I/O Cfg] has no effect. If the Operating Mode Jumper is set to the
“5x” (Multi-Drive) position, up to five drives can be represented as one node by the adapter.
1. Set the value in Parameter 12 - [DSI I/O Cfg].
Figure 3.2 I/O Configuration Screen on Powerflex 4-Class HIM (22-HIM-*)
DSI I/O Cfg
Parameter:
VALUE LIMITS
Drive 0
# 012
0
SEL
!
0
1
2
3
4
Drives 0-1
Drives 0-2
Drives 0-3
Drives 0-4
Mode Jumper Position
Value Description
Single Multi-Drive
Drive 0 (Default)
✓
✓
✓
✓
✓
✓
When the adapter is internally mounted in a PowerFlex 40 or 400 drive, this drive is always Drive 0. Drives 1 through 4 are PowerFlex
3-4
Configuring the Adapter
4-Class drives that are daisy-chained to the RJ45 (RS-485) port on
Drive 0. When the adapter is externally mounted in a DSI External
Comms Kit, Drives 0 through 4 are daisy-chained to the RJ45
(RS-485) port on the Comms Kit. Refer to Chapter 7 , Using
Multi-Drive Mode for more information.
2. If a drive is enabled, configure the parameters in the drive to accept the Logic Command and Reference from the adapter. For example, set a PowerFlex 40 drive’s parameter P036 - [Start Source] and parameter P038 - [Speed Reference] both to “5” (Comm Port). When using the adapter in Multi-Drive mode, each daisy-chained drive requires that additional parameters be set. See
RS-485 Network on page 7-7 for these parameters and their settings.
3. Reset the adapter (see Resetting the Adapter on page 3-6
).
Setting a Fault Action
By default, when communications are disrupted (for example, a cable is disconnected) or the controller is in program mode, the drive responds by faulting if it is using I/O from the network. You can configure a different response to communication disruptions using Parameter 08 -
[Comm Flt Action] and a different response to a controller in program mode using Parameter 09 - [Idle Flt Action].
!
ATTENTION: Risk of injury or equipment damage exists.
Parameters 08 - [Comm Flt Action] and 09 - [Idle Flt Action] let you determine the action of the adapter and connected drive if communications are disrupted or the controller is in program mode. By default, these parameters fault the drive. You can set these parameters so that the drive continues to run. Some ControlNet scanners may operate differently when a controller is in program mode which could limit the Idle Fault Action’s operating states. Precautions should be taken to ensure that the settings of these parameters do not create a risk of injury or equipment damage. When commissioning the drive, verify that your system responds correctly to various situations (for example, a disconnected cable or faulted controller).
Configuring the Adapter
3-5
To change the fault action
Set the values of Parameters 08 - [Comm Flt Action] and 09 - [Idle Flt
Action] to the desired responses:
3
4
1
2
Value Action
0 Fault
Stop
Description
The drive is faulted and stopped. (Default)
The drive is stopped, but not faulted.
Zero Data The drive is sent 0 for output data. This does not command a stop.
Hold Last The drive continues in its present state.
Send Flt Cfg The drive is sent the data that you set in the fault configuration parameters (Parameter 10 - [Flt Cfg Logic] and Parameter 11 - [Flt Cfg Ref]).
Figure 3.3 Fault Action Screens on PowerFlex 4-Class HIM (22-HIM-*)
# 008
Idle Flt Action
Parameter: # 009
Comm Flt Action
Parameter:
VALUE LIMITS
Fault 0
SEL
!
VALUE LIMITS
Fault 0
SEL
!
Changes to these parameters take effect immediately. A reset is not required.
If Multi-Drive mode is used, the same fault action is used by the adapter for all of the drives (Drive 0 - Drive 4) it controls.
To set the fault configuration parameters
If you set Parameter 08 - [Comm Flt Action] or 09 - [Idle Flt Action] to “Send Flt Cfg,” the values in the following parameters are sent to the drive after a communications fault and/or idle fault occurs. You must set these parameters to values required by your application:
Parameter Name
10
11
Flt Cfg Logic
Description
A 16-bit value sent to the drive for Logic Command.
Flt Cfg Ref A 16-bit value (0 – 65535) sent to the drive as a
Reference.
Changes to these parameters take effect immediately. A reset is not required.
3-6
Configuring the Adapter
Resetting the Adapter
Changes to switch settings and some adapter parameters require that you reset the adapter before the new settings take effect. You can reset the adapter by cycling power to the drive or by using the following parameter:
!
ATTENTION: Risk of injury or equipment damage exists. If the adapter is transmitting control I/O to the drive, the drive may fault when you reset the adapter. Determine how your drive will respond before resetting a connected adapter.
Set Parameter 07 - [Reset Module] to Reset Module.
Figure 3.4 Reset Screen on PowerFlex 4-Class HIM (22-HIM-*)
Parameter:
Reset Module
VALUE LIMITS
Ready
# 007
0
SEL
!
1
2
Value Description
0 Ready (Default)
Reset Module
Set Defaults
When you enter 1 = Reset Module, the adapter will be immediately reset. When you enter 2 = Set Defaults, the adapter will set all adapter parameters to their factory-default settings. After performing a Set
Defaults, enter 1 = Reset Module so that the new values take effect. The value of this parameter will be restored to 0 = Ready after the adapter is reset.
Configuring the Adapter
3-7
Viewing the Adapter Configuration
The following parameters provide information about how the adapter is configured. You can view these parameters at any time.
Number
01
03
Name
Mode
Description
The operating mode in which the adapter is set:
Values
0 = Single Drv
1 = Multiple Drv
CN Addr Act The node address used by the adapter. This will be one of the following values:
• The address set by the adapter Node Address switches.
• The value of Parameter 02 - [CN Addr Cfg] if the switches are set to 0.
• An old address of the switches or parameter if they have been changed and the adapter has not been reset.
13 DSI I/O Act Indicates the drives that are active in the Multi-Drive mode:
Bit Definitions
0 = Drive 0 Active
1 = Drive 1 Active
2 = Drive 2 Active
3 = Drive 3 Active
4 = Drive 4 Active
3-8
Notes:
Configuring the Adapter
Chapter
4
Configuring the I/O
Chapter 4 provides instructions on how to configure a ControlLogix controller with 1756-CNB/R bridge or PLC-5 controller to communicate with the adapter and connected PowerFlex drive.
Topic
Page
Important: The I/O consumes only one connection between the controller and drive(s) regardless of whether the adapter is in Single or Multi-Drive mode. When using DriveExecutive to configure/monitor the drive, an additional I/O connection will be consumed between the computer and controller.
When using Explicit Messaging for time-critical messages, you can create additional dedicated message connections to ensure the timing of their transactions. For more details, see the Important statement in
.
ControlLogix Example
Example Network
After the adapter is configured, the connected drive and adapter will be a single node on the network. This section provides the steps that are needed to configure a simple network like the network in Figure 4.1
. In our example, we will configure a 1756-CNB/R bridge to communicate with a drive using Logic Command/Status and Reference/Feedback over the network.
4-2
Configuring the I/O
Figure 4.1 Example ControlNet Network
Node 1
ControlLogix Controller with 1756-CNB/R Bridge
Node 2
PowerFlex 40 Drive with 22-COMM-C
ControlNet Adapter
ControlNet Network
(optional redundancy)
Node 99
Computer with 1784-PCC
Network Interface Card and
RSNetWorx for ControlNet
Adding the Bridge to the I/O Configuration
To establish communications over a ControlNet network, you must first add the ControlLogix controller and its bridge to the I/O configuration.
1. Start RSLogix 5000. The RSLogix 5000 window appears. Select
File > New to display the New Controller screen (
Figure 4.2 New Controller Screen
Select the appropriate choices for the fields in the screen to match your application. Then click OK. The RSLogix 5000 window reappears with the project tree in the left pane.
Configuring the I/O
4-3
2. In the project tree, right-click the I/O Configuration folder and select
New Module. The Select Module Type screen ( Figure 4.3
) appears.
Figure 4.3 Select Module Type Screen
Step 3
Step 4
3. In the list, select the ControlNet bridge used by your controller. In this example ( Figure 4.3
), we use a 1756-CNBR/D ControlNet
Bridge (Series D), so the 1756-CNBR/D option is selected.
4. Click OK. The Module Properties screen (
Figure 4.4 Module Properties Screen
5. Edit the following:
Box Setting
Name A name to identify the bridge.
Node Select the node address setting of the ControlNet bridge (default = 1).
Slot The slot of the ControlNet bridge in the rack.
Revision The minor revision of the firmware in the bridge. (You already set the major revision by selecting the bridge series in Step 3.)
4-4
Configuring the I/O
Box
Electronic
Keying
Setting
Compatible Module. The “Compatible Module” setting for Electronic
Keying ensures that the physical module is consistent with the software configuration before the controller and bridge make a connection.
Therefore, ensure that you have set the correct revision in this screen.
Refer to the online help if the controller and bridge have problems making a connection and you want to change this setting.
6. Click Finish>>. The bridge is now configured for the ControlNet network. It appears in the I/O Configuration folder. In our example, a
1756-CNBR/D bridge appears under the I/O Configuration folder
) with its assigned name.
Figure 4.5 RSLogix 5000: I/O Configuration Folder
Adding the Adapter and Drive to the I/O Configuration
To transmit data between the bridge and the adapter, you must add the
22-COMM-C adapter as a child device to the parent bridge.
1. In the project tree, right-click on the bridge and select New Module to display the Select Module Type screen (
example, right-click on the 1756-CNBR/D bridge.
Figure 4.6 Select Module Type Screen
2. Select CONTROLNET-MODULE (
) to configure the
22-COMM-C adapter, and then click OK. The Module Properties screen (
Figure 4.7 Module Properties Screen
Configuring the I/O
4-5
3. Edit the following information about the adapter:
Box Setting
Name A name to identify the adapter and drive.
Comm Format
Node
Data - INT (This setting formats the data in 16-bit words.)
The node address setting of the adapter.
4. Under Connection Parameters, edit the following:
Box Assembly Instance Size
Input 1 (This value is required.)
The value will vary based on your application
(setting of Parameter 12 - [DSI I/O Cfg]). It will contain 2 additional words for ControlNet bridge overhead. Refer to
Output 2 (This value is required.)
The value will vary based on your application
(setting of Parameter 12 - [DSI I/O Cfg]). Refer
Configuration 6 (This value is 0 (This value is required.) required.)
Enter the number of words that are required for your I/O in the Input
Size and Output Size boxes. The size will depend on the I/O that you enabled in the adapter. This information can be found in Parameter
12 - [DSI I/O Cfg] in the adapter.
configuration Input/Output sizes.
In our example, we entered “4” in the Input Size and “2” in the
Output Size boxes because the Operating Mode Jumper on the adapter is set to “1x” (Single mode, which is the default). Logic
Status/Feedback uses 2 words of input and an additional 2 words of input are reserved for ControlNet bridge overhead. Logic Command/
Reference uses 2 words of output.
4-6
Configuring the I/O
Table 4.A ControlLogix Input/Output Size Configurations
6
8
10
12
Input
Size
4
Output
Size
Logic Command/
Status
2
4
6
8
10
✔
✔
✔
✔
✔
Reference/
Feedback
✔
✔
✔
✔
✔
Parameter 12 -
[DSI I/O Cfg]
Drive 0
Drives 0-1
Drives 0-2
Drives 0-3
Drives 0-4
Parameter 01 -
[Mode]
Single
Multi-Drive
TIP: For instructions on configuring the I/O for the adapter
(Parameter 12 - [DSI I/O Cfg]), see Setting the I/O
5. Click Next > to display the Requested Packet Interval screen
( Figure 4.8
).
Figure 4.8 Requested Packet Interval Screen
6. In the Requested Packet Interval (RPI) box, set the value to 5.0 milliseconds or greater. This value determines the maximum interval that a controller should use to move data to and from the adapter. To conserve bandwidth, use higher values for communicating with low priority devices.
7. Click Finish >>. The new node (“PowerFlex_40_Drive” in this example) now appears under the bridge (“1756-CNBR/D” in this example) in the I/O Configuration folder. If you double-click on the
Controller Tags ( Figure 4.9
), you will see that module-defined data types and tags have been automatically created. After you save and download the configuration, these tags allow you to access the Input and Output data of the adapter via the controller’s ladder logic.
Figure 4.9 Controller Tags Overview Window
Configuring the I/O
4-7
4-8
Configuring the I/O
Saving the I/O Configuration to the Controller
After adding the bridge and the adapter to the I/O configuration, you must download the configuration to the controller. You should also save the configuration to a file on your computer.
1. Select Communications > Download. The Download dialog box
( Figure 4.10
) appears.
Figure 4.10 Download Dialog Box
TIP: If a message box reports that RSLogix 5000 is unable to go online, select Communications > Who Active to try to find your controller in the Who Active screen. After finding the controller, click the Set Project Path button to establish the path. If your controller does not appear, you need to add or configure the ControlNet driver in RSLinx. Refer to the
RSLinx online help.
2. Click Download to download the configuration to the controller.
5000 enters the Rem Prog (Remote Program) mode.
When the download is completed successfully, click Yes. RSLogix
3. Select File > Save. If this is the first time that you saved the project, the Save As dialog box appears. Navigate to a folder, type a file name, and click Save to save the configuration to a file on your computer.
Configuring the I/O
4-9
Saving the I/O Configuration to the Bridge
You also need to download the I/O configuration to the bridge. You should also save the configuration to a file on your computer.
1. Launch RSNetWorx for ControlNet. In the RSNetWorx for
ControlNet window, select File > New to display the New File screen. Then select “ControlNet Configuration” as the network configuration type, and click OK.
2. Select Network > Online to display the Browse for Network screen
Figure 4.11 Browse for Network Screen
3. Expand the communications path from your computer to the
ControlNet bridge.
shows our example navigating to
devices that are on a ControlNet network. Depending on the communication link you are using, the navigation path may be different. After selecting a valid ControlNet path (for this example,
A, ControlNet), click OK.
4-10
Configuring the I/O
Figure 4.12 Expanded Browse for Network Screen
4. As the selected ControlNet path is browsed, RSNetWorx for
ControlNet creates a graphical representation of the devices on the
Figure 4.13 RSNetWorx for ControlNet Graph View Screen
Configuring the I/O
4-11
5. Select Network > Enable Edits. If the bridge has a different I/O configuration than the configuration now being saved, the Online /
Offline mismatch dialog box ( Figure 4.14
Figure 4.14 Online / Offline mismatch Dialog Box
When both radio button choices are available, use the preselected default “Use online data (upload).” When this choice is unavailable
(grayed out), you must select “Use offline data (download).” Then click OK.
6. Select File > Save to save the I/O configuration file to the computer.
If this is the first time that you saved the project, the Save As dialog box appears. Navigate to a folder, type a file name, and click Save to save the configuration to a file on your computer. The Save
Configuration dialog box ( Figure 4.15
) appears. Then click OK to download the I/O configuration to the bridge.
Figure 4.15 Save Configuration Dialog Box
TIP: If both Save Type choices are available, it is recommended to select the “Optimize and re-write schedule for all connections” radio button.
4-12
Configuring the I/O
PLC-5 Example
Example Network
After the adapter is configured, the connected drive and adapter will be a single node on the network. This section provides the steps that are needed to configure a simple network like the network in
our example, we will configure a PLC-5/40C controller to communicate with a drive using Logic Command/Status and Reference/Feedback over the network.
Figure 4.16 Example ControlNet Network
Node 1
PLC-5/40C Controller
Node 2
PowerFlex 40 Drive with 22-COMM-C
ControlNet Adapter
ControlNet Network
(optional redundancy)
Node 99
Computer with 1784-PCC
Network Interface Card and
RSNetWorx for ControlNet
Adding the Drive and Adapter I/O to the Controller
To establish an I/O configuration that can be used between the controller and drive over a ControlNet network, you must first create an I/O image for the PLC-5/40C controller’s built-in scanner.
1. Launch RSNetWorx for ControlNet. In the RSNetWorx for
ControlNet window, select File > New to display the New File screen. Then select ControlNet Configuration as the network configuration type, and click OK.
2. Select Network > Online to display the Browse for Network screen
Figure 4.17 Browse for Network Screen
Configuring the I/O
4-13
3. Expand the communications path from your computer to the
ControlNet scanner.
shows our example navigating to
devices that are on a ControlNet network. Depending on the communication link you are using, the navigation path may be different. After selecting a valid ControlNet path (for example, A,
ControlNet), click OK.
Figure 4.18 Expanded Browse for Network Screen
4-14
Configuring the I/O
4. As the selected ControlNet path is browsed, RSNetWorx for
ControlNet creates a graphical representation of the devices on the
Figure 4.19 RSNetWorx for ControlNet Graph View Screen
5. Select Network > Enable Edits. If the scanner has a different I/O configuration than the configuration now being saved, the Online /
Offline mismatch dialog box ( Figure 4.20
) will appear.
Figure 4.20 Online / Offline mismatch Dialog Box
When both radio button choices are available, use the preselected default “Use online data (upload).” When this choice is unavailable click OK.
(grayed out), you must select “Use offline data (download).” Then
Configuring the I/O
4-15
6. In the RSNetWorx for ControlNet graph view screen, right-click the
PLC-5/40C icon and select Scanlist Configuration to display the
Scanlist Configuration screen (
).
Figure 4.21 Scanlist Configuration Screen
7. Right-click on the PowerFlex 40 drive row in the screen and select
Insert Connection… to display the Connection Properties screen
Figure 4.22 Connection Properties Screen
In this screen, leave the Connection Name box at the default value shown. Choose a Requested Packet Interval that is suitable for your application, but is at least 5 ms. Use the pull-down lists to select the
4-16
Configuring the I/O number of words that are required for your I/O in the Input Size and
Output Size boxes. The size will depend on the I/O that you enabled in the adapter. This information can be found in Parameter 12 -
[DSI I/O Cfg] in the adapter.
configuration Input/Output sizes.
Table 4.B PLC-5/40C Input/Output Size Configurations
4
6
8
10
Input
Size
2
Output
Size
Logic Command/
Status
2
4
6
8
10
✔
✔
✔
✔
✔
Reference/
Feedback
✔
✔
✔
✔
✔
Parameter 12 -
[DSI I/O Cfg]
Drive 0
Drives 0-1
Drives 0-2
Drives 0-3
Drives 0-4
Parameter 01 -
[Mode]
Single
Multi-Drive
TIP: If necessary, the N9:0, N10:0, and N11:0 address defaults can be changed to meet processor address requirements or eliminate address conflicts.
8. Then click OK. An address row (in blue text) will be added below the PowerFlex 40 drive row.
9. Select File > Save to save the I/O configuration file to the computer.
If this is the first time that you saved the project, the Save As dialog box appears. Navigate to a folder, type a file name, and click Save to save the configuration to a file on your computer. The Save
Configuration dialog box ( Figure 4.23
download the I/O configuration to the scanner.
Figure 4.23 Save Configuration Dialog Box
TIP: If both Save Type choices are available, it is recommended to select the “Optimize and re-write schedule for all connections” radio button.
10. A warning will appear about communication and I/O disruption on the network. Click Yes.
Chapter
5
Using the I/O
!
Chapter 5 provides information and examples that explain how to use the
I/O to control, configure, and monitor a PowerFlex 4-Class drive.
Topic
Example Ladder Logic Program Information
Page
ATTENTION: Risk of injury or equipment damage exists. The examples in this publication are intended solely for purposes of example. There are many variables and requirements with any application. Rockwell Automation, Inc. does not assume responsibility or liability (to include intellectual property liability) for actual use of the examples shown in this publication.
About I/O Messaging
On ControlNet, I/O messaging is used to transfer the data which controls the PowerFlex drive and sets its Reference.
The adapter provides many options for configuring and using I/O, including configuring the size of I/O by selecting the number of attached drives (Single or Multi-Drive mode).
Chapter 3 , Configuring the Adapter , and
Chapter 4 , Configuring the I/O ,
discuss how to configure the adapter and controller on the network for these options. The
Glossary defines the different options. This chapter
discusses how to use I/O after you have configured the adapter and controller.
5-2
Using the I/O
Understanding the I/O Image
The terms input and output are defined from the controller’s point of view. Therefore, output I/O is data that is produced by the controller and consumed by the adapter. Input I/O is status data that is produced by the adapter and consumed as input by the controller. The I/O image table will vary based on the configuration of the adapter:
• Parameter 12 - [DSI I/O Cfg]
The image table always uses consecutive words starting at word 0.
illustrate examples of a Single drive I/O image
(16-bit words) for ControlLogix and PLC-5 controllers respectively.
Figure 5.1 Single Drive Example of I/O Image for ControlLogix
DSI
Controller Scanner
Output
Image
(Write)
ControlNet
Adapter
Word and I/O
0 Logic Command
1 Reference
Input
Image
(Read)
0 Pad Word
1 Pad Word
2 Logic Status
3 Feedback
PowerFlex 40 Drive
Logic Command
Reference
Logic Status
Feedback
Message
Handler
Message
Buffer
Message
Handler
Figure 5.2 Single Drive Example of I/O Image for PLC-5
ControlNet
Controller Scanner
Output
Image
(Write)
Adapter
Word and I/O
0 Logic Command
1 Reference
DSI
Input
Image
(Read)
0 Logic Status
1 Feedback
Message
Handler
Message
Buffer
PowerFlex 40 Drive
Logic Command
Reference
Logic Status
Feedback
Message
Handler
Single mode is the typical configuration, where one node consists of a
PowerFlex 40 or PowerFlex 400 drive with a 22-COMM-C adapter. For
Multi-Drive mode, where one node can consist of up to 5 drives, refer to
Chapter 7 , Using Multi-Drive Mode .
Using the I/O
5-3
Using Logic Command/Status
The Logic Command word is always word 0 in the output image. The
Logic Command is a 16-bit word of control produced by the controller and consumed by the adapter. The Logic Status word is input word 2 for
ControlLogix or input word 0 for PLC-5. The Logic Status is a 16-bit word of status produced by the adapter and consumed by the controller.
This manual contains the bit definitions for compatible products
available at the time of publication in Appendix D
,
. For other products, refer to their documentation.
Using Reference/Feedback
The Reference word is always word 1 in the output image. The
Reference (16 bits) is produced by the controller and consumed by the adapter. The Feedback word begins at input word 3 for ControlLogix or input word 1 for PLC-5. The Feedback (16 bits) is produced by the adapter and consumed by the controller.
Size
16-bit
Drive
PowerFlex 4
PowerFlex 40
PowerFlex 400
Valid Values
(1)
-240.0 to +240.0 Hz
-400.0 to +400.0 Hz
-320.00 to +320.00 Hz
Example
(1)
The Reference/Feedback for a PowerFlex 4, PowerFlex 40 or Powerflex 400 drive is set in Hz and not in engineering units like PowerFlex 7-Class drives. For example,
“300” equates to 30.0 Hz (the decimal point is always implied) for PowerFlex 4/40, and motor direction, and a plus value equates to forward motor direction.
“3000” equates to 30.00 Hz for PowerFlex 400. Also, a minus value equates to reverse
5-4
Using the I/O
Example Ladder Logic Program Information
The example ladder logic programs in the ControlLogix Example and
sections of this chapter are intended for and operate
PowerFlex 4-Class drives.
Functions of the Example Programs
The example programs enable an operator to perform the following:
• Obtain status information from the drive.
• Use the Logic Command to control the drive (for example, start, stop).
• Send a Reference to the drive and receive Feedback from the drive.
Adapter Settings for the Example Programs
• Node address 2 is set using parameters.
• The adapter is configured for Single mode operation (Operating Mode
Jumper J7 is set to “1x”).
Scanner Settings for the ControlLogix Example Program
• The scanner is in slot 1 and is node 1 on the ControlNet network.
• Output to the adapter is mapped in word 0 and word 1, and input from the adapter is in words 2 and 3 (0 and 1 are pad words).
Scanner Settings for the PLC-5 Example Program
• The scanner is node 1 on the ControlNet network.
• Output to the adapter is mapped in N10:0 and N10:1, and input from the adapter is in N9:0 and N9:1.
Logic Command/Status Words
These examples use the Logic Command word and Logic Status word
for PowerFlex 40 drives. Refer to Appendix D , Logic Command/Status
Words to view these. The definition of the bits in these words may vary if
you are using a different DSI product. Refer to the documentation for your product.
Using the I/O
ControlLogix Example
The Drive I/O Control program ( Figure 5.3
control the drive.
The following program tags are used for the Drive I/O Control Routine:
Tag Name
Status_Ready
Status_Active
Status_Forward
Status_Reverse
Status_Faulted
Status_At_Speed
Speed_Feedback
Command_Stop
Command_Start
Command_Jog
Command_Clear_Faults
Command_Forward_Reverse
Speed_Reference
INT
BOOL
BOOL
BOOL
BOOL
BOOL
INT
Type
BOOL
BOOL
BOOL
BOOL
BOOL
BOOL
Description
Ready bit
Active bit
Forward bit
Reverse bit
Faulted bit
At speed bit
Speed feedback word
Stop bit
Start bit
Jog bit
Clear faults bit
Forward/reverse bit
Speed reference word
5-5
5-6
Using the I/O
Figure 5.3 ControlLogix Ladder Logic Example for Drive I/O Control
This ControlLogix example system consists of a 1756-CNBR/D in Slot 4 communicating on a ControlNet network with a
PowerFlex 40 drive with an installed 22-COMM-C ControlNet adapter. You may substitute the "PowerFlex 40" for a
INPUT (4 INT words)
PowerFlex_40_Drive:I.Data[0] = 1756-CNBR Overhead (Not Used)
PowerFlex_40_Drive:I.Data[1] = 1756-CNBR Overhead (Not Used)
PowerFlex_40_Drive:I.Data[2] = PowerFlex 40 Logic Status
PowerFlex_40_Drive:I.Data[3] = PowerFlex 40 Speed Feedback
PowerFlex_40_Drive:O.Data[0] = PowerFlex 40 Logic Command
PowerFlex_40_Drive:O.Data[1] = PowerFlex 40 Speed Reference
0
PowerFlex_40_Drive:I.Data[2].0
Status_Ready
1
2
3
4
5
6
7
8
PowerFlex_40_Drive:I.Data[2].1
PowerFlex_40_Drive:I.Data[2].3
PowerFlex_40_Drive:I.Data[2].3
/
PowerFlex_40_Drive:I.Data[2].7
Status_Active
Status_Forward
Status_Reverse
Status_Faulted
PowerFlex_40_Drive:I.Data[2].8
Status_At_Speed
This rung displays the Speed Feedback word from the PowerFlex 40. Note that it is set in Hz and not in engineering units like PowerFlex 7-Class drives. For example, "300" equates to 30.0 Hz (the decimal point is always implied).
MOV
Move
Source PowerFlex_40_Drive:I.Data[3]
0
Dest Speed_Feedback
0
Logic Command bit control rungs are provided for display purposes only. The PowerFlex_40_Drive:O.Data[0].x bits could be used directly elsewhere in the ladder program.
Command_Stop PowerFlex_40_Drive:O.Data[0].0
Command_Start PowerFlex_40_Drive:O.Data[0].1
Using the I/O
Figure 5.3 ControlLogix Ladder Logic Example for Drive I/O Control (Continued)
5-7
(End)
9
10
Command_Jog
Command_Clear_Faults
PowerFlex_40_Drive:O.Data[0].2
PowerFlex_40_Drive:O.Data[0].3
11
12
13
Command_Forward_Reverse PowerFlex_40_Drive:O.Data[0].4
Command_Forward_Reverse
/
PowerFlex_40_Drive:O.Data[0].5
This rung provides the Speed Reference word to the PowerFlex 40. Note that it is set in Hz and not in engineering units like
PowerFlex 7-Class drives. For example, "300" equates to 30.0 Hz (the decimal point is always implied).
MOV
Move
Source Speed_Reference
600
Dest PowerFlex_40_Drive:O.Data[1]
0
For a ControlLogix controller explicit message ladder example program, see
5-8
Using the I/O
PLC-5 Example
The Drive I/O Control program ( Figure 5.4
control the drive.
Figure 5.4 PLC-5 Ladder Logic Example for Drive I/O Control
0000
0001
0002
0003
0004
0005
In this example, an operator station is wired into the local PLC-5/40C rack as follows:
O:000/0 Drive Ready
O:000/1 Drive Active
O:000/2 Drive Forward
O:000/3 Drive Reverse
O:000/4 Drive Faulted
O:000/5 Drive At Speed
O:001 Operator Speed Feedback
Open Pushbutton)
I:000/1 Start (Normally Open Pushbutton)
I:000/2 Jog (Normally Open Pushbutton)
I:000/3 Clear Faults (Normally Open Pushbutton)
I:000/4 Forward / Reverse Selector Switch
I:001 Operator Speed Reference
In this example, a PowerFlex 40 drive with installed 22-COMM-C ControlNet adapter is mapped as follows:
N9:0 Logic Status N10:0 Logic Command
N9:1 Speed Feedback N10:1 Speed Reference
Rungs 0000 through 0005 move the Logic Status from the drive to the operator station.
Drive Logic Status
READY
N9:0
0
Operator
Drive Ready Status
Display
O:000
0
Drive Logic Status
ACTIVE
N9:0
1
Drive Logic Status
ACTUAL FORWARD /
REVERSE DIRECTION
N9:0
3
Drive Logic Status
ACTUAL FORWARD /
REVERSE DIRECTION
N9:0
3
Drive Logic Status
FAULTED
N9:0
7
Drive Logic Status
AT SPEED
N9:0
8
Operator
Drive Active Status
Display
O:000
1
Operator
Drive Actual Forward
Status Display
O:000
2
Operator
Drive Actual Reverse
Status Display
O:000
3
Operator
Drive Fault Status
Display
O:000
4
Operator
Drive At Speed
Status Display
O:000
5
Using the I/O
Figure 5.4 PLC-5 Ladder Logic Example for Drive I/O Control (Continued)
5-9
0014
0006
Rung 0006 moves the Speed Feedback from the drive to the operator station.
Drive
Speed Feedback
MOV
Move
Source N9:1
0<
Dest O:001
0<
0007
0008
0009
0010
0011
0012
0013
Rungs 0007 through 0012 move the Logic Command from the operator station to the drive.
Operator
Stop Pushbutton
I:000
0
Drive Logic Command
STOP
N10:0
0
Operator
Start Pushbutton
I:000
1
Operator
Jog Pushbutton
I:000
Operator
Clear Faults
Pushbutton
I:000
2
Drive Logic Command
START
N10:0
1
Drive Logic Command
JOG
N10:0
2
Drive Logic Command
CLEAR FAULTS
N10:0
3 3
Operator
Forward / Reverse
Selector Switch
I:000
4
Drive Logic Command
FORWARD
N10:0
4
Operator
Forward / Reverse
Selector Switch
I:000
Rung 0013 moves the Speed Reference from the operator station to the drive.
4
Drive Logic Command
REVERSE
N10:0
5
Drive
Speed Reference
MOV
Move
Source I:001
0<
Dest N10:1
0<
END
For a PLC-5 controller explicit message ladder example program, see
5-10
Notes:
Using the I/O
Chapter
6
Using Explicit Messaging
Chapter 6 provides information and examples that explain how to use
Explicit Messaging to configure and monitor the 22-COMM-C adapter and PowerFlex 4-Class drive to which it is connected.
Topic
Page
Performing Explicit Messages 6-2
Topic
Page
!
!
ATTENTION: Risk of injury or equipment damage exists. The examples in this publication are intended solely for purposes of example. There are many variables and requirements with any application. Rockwell Automation, Inc. does not assume responsibility or liability (to include intellectual property liability) for actual use of the examples shown in this publication.
ATTENTION: Risk of equipment damage exists. If Explicit Messages are programmed to write parameter data to Non-Volatile Storage (NVS) frequently, the NVS will quickly exceed its life cycle and cause the drive to malfunction. Do not create a program that frequently uses
Explicit Messages to write parameter data to NVS.
Refer to Chapter 5 for information about the I/O image, using Logic
Command/Status and Reference/Feedback.
About Explicit Messaging
Explicit Messaging is used to transfer data that does not require continuous updates. With Explicit Messaging, you can configure and monitor a slave device’s parameters on the ControlNet network.
Important: When an explicit message is performed, by default no I/O connection is made since it is an “unconnected” message.
When timing of the message transaction is important, you can create a dedicated message connection between the controller and drive by checking the “Connected” box on the Communications tab message configuration screen
6-2
Using Explicit Messaging during message setup. These message connections are in addition to the I/O connection. However, the tradeoff for more message connections is decreased network performance. If your application cannot tolerate this, do not check the “Connected” box.
Performing Explicit Messages
There are five basic events in the Explicit Messaging process. The details of each step will vary depending on the type of controller being used.
Refer to the documentation for your controller.
Important: There must be a request message and a response message for all Explicit Messages, whether you are reading or writing data.
➎
Figure 6.1 Explicit Message Process
Complete Explicit
Message
➊ Set up and send Explicit
Message Request
➍
Retrieve Explicit
Message Response ➋
➌
Event
1. You format the required data and set up the ladder logic program to send an Explicit Message request to the scanner or bridge module
(download).
2. The scanner or bridge module transmits the Explicit Message
Request to the slave device over the ControlNet network.
3. The slave device transmits the Explicit Message Response back to the scanner or bridge. The data is stored in the scanner buffer.
4. The controller retrieves the Explicit Message Response from the scanner’s buffer (upload).
5. The Explicit Message is complete. Note: When using a PLC-5 controller, delete the transaction ID so that it can be reused.
For information on the maximum number of Explicit Messages that can be executed at a time, refer to the user manual for the bridge or scanner and/or controller that is being used.
Using Explicit Messaging
6-3
ControlLogix Example
TIP: To display the Message Configuration screen in RSLogix 5000, add a message instruction (MSG), create a new tag for the message
(Properties: Base tag type, MESSAGE data type, controller scope), and click the button in the message instruction.
Formatting a Message to Read a Parameter
A Get Attribute Single message is used to read a single parameter. This example read message is for parameter d003 - [Output Current] for a
PowerFlex 4-Class drive.
Figure 6.2 Get Attribute Single Message Configuration Screens
Configuration Tab
Message Type
Service Type
(1)
Service Code
(1)
Class
Instance
Attribute
Destination
Example Value
CIP Generic
Get Attribute Single e (Hex.) f (Hex.)
3 (Dec.)
1 (Hex.)
Output_Current
Description
CIP messages are used to access the Parameter object in the 22-COMM-C.
This service is used to read a parameter value.
The code for the requested service.
The Class ID for the CIP Parameter object.
The instance number is the same as the parameter number in Single mode operation.
The attribute number for the Parameter Value attribute.
The tag where the data that is read is stored.
Communication Tab Example Value
Path
(2)
PowerFlex_40…
Description
The path is the route that the message will follow.
(1)
(2)
The default setting for Service Type is “Custom,” enabling entry of a Service Code not available from the Service
Type pull-down menu. When selecting a Service Type other than “Custom” from the pull-down menu, an appropriate Hex. value is automatically assigned to the Service Code box which grays out (unavailable).
Click Browse to find the path, or type in the name of the device listed in the I/O Configuration folder.
6-4
Using Explicit Messaging
For supported classes, instances, and attributes, refer to
,
.
Formatting a Message to Write to a Parameter
A Set Attribute Single message is used to write to a single parameter.
This example write message is for parameter P039 - [Accel Time 1] for a
PowerFlex 4-Class drive.
Figure 6.3 Set Attribute Single Message Configuration Screens
Configuration Tab
Message Type
Service Type
(1)
Service Code
(1)
Class
Instance
Attribute
Source Element
Source Length
Example Value
CIP Generic
Set Attribute Single
10 (Hex.) f (Hex.)
39 (Dec.)
1 (Hex.)
Accel_Time_1
2 bytes
Description
CIP messages are used to access the Parameter object in the 22-COMM-C.
This service is used to write a parameter value.
The code for the requested service.
The Class ID for the CIP Parameter object.
The instance number is the same as the parameter number in Single mode operation.
The attribute number for the Parameter Value attribute.
The tag where the data that is written is stored.
The size of a parameter value in a PowerFlex 4-Class drive is always 2 bytes.
Communication Tab Example Value
Path
(2)
PowerFlex_40…
Description
The path is the route that the message will follow.
(1)
The default setting for Service Type is “Custom,” enabling entry of a Service Code not available from the Service
Type pull-down menu. When selecting a Service Type other than “Custom” from the pull-down menu, an appropriate Hex. value is automatically assigned to the Service Code box which grays out (unavailable).
(2)
Click Browse to find the path, or type in the name of the device listed in the I/O Configuration folder.
For supported classes, instances, and attributes, refer to
,
.
Using Explicit Messaging
6-5
Table 6.A Tags for the ControlLogix Example Explicit Messaging Program
Tag Names for Read Message Type
Perform_Parameter_Read BOOL
Parameter_Read_Message MESSAGE
Output_Current INT
Tag Names for Write Message Type
Perform_Parameter_Write BOOL
Parameter_Write_Message MESSAGE
Accel_Time_1 INT
Ladder Logic Program
Figure 6.4 Example ControlLogix Ladder Logic Explicit Messaging Program
(End)
0
1
This message example reads from Parameter d003 - [Output Current] and stores its value in the "Output_Current" controller tag.
Perform_Parameter_Read
Type - CIP Generic
Message Control
MSG
Parameter_Read_Message ...
EN
DN
ER
Perform_Parameter_Write
Type - CIP Generic
Message Control
MSG
Parameter_Write_Message ...
EN
DN
ER
For a ControlLogix controller I/O ladder example program, see
6-6
Using Explicit Messaging
PLC-5 Example
Important: Due to controller limitations, explicit messaging can only be performed on drive parameters up to Parameter 256.
The ControlNet I/O Transfer (CIO) instruction is used for PLC-5 controllers to send explicit messages.
Formatting a Message to Read a Parameter
This read message example is for parameter d003 - [Output Current] for a PowerFlex 4-Class drive.
Configuration Box
Communication
Command
Service Code
Class Number
Instance Number
Attribute Number
PLC-5 Data Table
Address
Size in Elements
Port Number
Local ControlNet Node
1
2
2
Example Value Description
CIP Generic e (Hex.) f (Hex.)
3 (Hex.)
1 (Hex.)
N7:2
CIP messages are used to access the Parameter object in the 22-COMM-C.
The code for the Get_Attribute_Single service.
The Class ID for the CIP Parameter object.
The instance number is the same as the parameter number in Single mode operation.
The attribute number for the Parameter Value attribute.
The user-defined address for any response service data received by the controller.
The number of elements in the response data.
The channel on the PLC-5 used for the ControlNet network.
The node address of the 22-COMM-C adapter.
For supported classes, instances, and attributes, refer to
,
.
Using Explicit Messaging
6-7
Formatting a Message to Write to a Parameter
This write message example is for parameter P039 - [Accel Time 1] for a
PowerFlex 4-Class drive.
Configuration Box
Communication
Command
Service Code
Class Number
Instance Number
Attribute Number
PLC-5 Data Table
Address
Size in Elements
Port Number
Local ControlNet Node
1
2
2
Example Value Description
CIP Generic
10 (Hex.) f (Hex.)
27 (Hex.)
1 (Hex.)
N7:3
CIP messages are used to access the Parameter object in the 22-COMM-C.
The code for the Set_Attribute_Single service.
The Class ID for the CIP Parameter object.
The instance number is the same as the parameter number in Single mode operation.
The attribute number for the Parameter Value attribute.
The user-defined address for any request service data sent by the controller.
The number of elements in the request data.
The channel on the PLC-5 used for the ControlNet network.
The node address of the 22-COMM-C adapter.
For supported classes, instances, and attributes, refer to
,
.
6-8
Using Explicit Messaging
Ladder Logic Program
Figure 6.5 Example PLC-5 Ladder Logic Explicit Messaging Program
0000
Rung 0000 enables the user to initiate an explicit message to read from Parameter d003 [Output
Current] in the drive.
Initiate Explicit
Message Parameter Explicit Message
Read
B3:0
0
Parameter Read
CIO
ControlNet I/O Transfer
Control CT12:0
Setup Screen
EN
DN
ER
0001
0002
Rung 0001 enables the user to initiate an explicit message to write to Parameter P039 [Accel
Time 1] in the drive.
Initiate Explicit
Message Parameter Explicit Message
Write
B3:0
1
Parameter Write
CIO
ControlNet I/O Transfer
Control CT12:1
Setup Screen
EN
DN
ER
END
For a PLC-5 controller I/O ladder example program, see Figure 5.4
Chapter
7
Using Multi-Drive Mode
!
Chapter 7 provides information on how to use Multi-Drive mode and includes ControlLogix and PLC-5 ladder examples.
Topic
Single Mode vs. Multi-Drive Mode
Configuring the RS-485 Network
Example Configuration Settings
ControlLogix Explicit Messaging
Page
ATTENTION: Risk of injury or equipment damage exists. The examples in this publication are intended solely for purposes of example. There are many variables and requirements with any application. Rockwell Automation, Inc. does not assume responsibility or liability (to include intellectual property liability) for actual use of the examples shown in this publication.
Single Mode vs. Multi-Drive Mode
Single mode is a typical network installation, where a single ControlNet
node consists of a single drive with a 22-COMM-C adapter ( Figure 7.1
7-2
Using Multi-Drive Mode
Figure 7.1 Single Mode Example for Network
1 drive per node
ControlNet Network
PowerFlex 40 or 400 Drive with 22-COMM-C Adapter
PowerFlex 40 or 400 Drive with 22-COMM-C Adapter
PowerFlex 40 or 400 Drive with 22-COMM-C Adapter
Multi-Drive mode is an alternative to the typical network installation, where a single ControlNet node can consist of one to five drives. In
, the 22-COMM-C adapter is internally mounted in a
PowerFlex 40/400 drive, and the remaining PowerFlex 4-Class drives are daisy-chained from the RS-485 port on the first drive. In
22-COMM-C adapter is externally mounted in a DSI External Comms
Kit, and all PowerFlex 4-Class drives are daisy-chained from it.
Figure 7.2 Multi-Drive Mode Example for Network - PowerFlex 40 Mounting up to 5 drives per node
ControlNet Network
Up to 4 Additional PowerFlex 4-Class Drives
PowerFlex 40 or 400 Drive
22-COMM-C
Adapter
AK-U0-RJ45-TB2P
Connector with
Terminating Resistor
RS-485 AK-U0-RJ45-TB2P AK-U0-RJ45-TB2P
Connector with
Terminating Resistor
Figure 7.3 Multi-Drive Mode Example for Network - External Comms Kit Mounting up to 5 drives per node
ControlNet Network
DSI External Comms Kit
(22-XCOMM-DC-BASE)
PORT
MOD
NET A
NET B
22-COMM-C
Adapter
Up to 5 PowerFlex 4-Class Drives
NOTE: A terminating resistor is not required for this end of of the wiring. The resistor is built into the circuitry of the
DSI External Comms Kit.
RS-485 AK-U0-RJ45-TB2P AK-U0-RJ45-TB2P
Connector with
Terminating Resistor
Using Multi-Drive Mode
Benefits of Multi-Drive mode include:
• Lower hardware costs. Only one adapter is needed for up to five drives. Any PowerFlex 4-Class drive can be daisy-chained.
• Reduces the network node count. For example, in Single mode 30 drives would consume 30 nodes. In Multi-Drive mode, 30 drives can be connected in 6 nodes.
• Provides a convenient way to put more than one PowerFlex 4 drive on the network using only one adapter (PowerFlex 4 drives do not have an internal communications adapter slot).
• Controller can control, monitor, and read/write parameters for all five drives.
Trade-offs of Multi-Drive mode include:
• When a PowerFlex 40/400 drive with an internal-mounted adapter is powered down, communications with the daisy-chained drives is disrupted and the drives will take the appropriate communications loss action set in each drive. However, communications will not be disrupted when the adapter is used in a DSI External Comms Kit and a daisy-chained drive is powered down.
• Communications throughput to the daisy-chained drives will be slower than if each drive was a separate node on the network (Single mode). This is because the adapter must take the network data for the other drives and sequentially send the respective data to each drive over RS-485. The approximate additional throughput time for Logic
Command/Reference to be transmitted and received by each drive in
Multi-Drive mode is:
Adapter Mounted In
PowerFlex 40/400 or
DSI External Comms
Kit
Drives per
Node
1 drive
2 drives
3 drives
4 drives
5 drives
Additional Throughput
Time versus Single Mode
0 milliseconds
+24 milliseconds
+48 milliseconds
+72 milliseconds
+96 milliseconds
• Since the RS-485 ports are used for daisy-chaining the drives, there is no connection for a peripheral device such as a HIM. The
AK-U0-RJ45-SC1 DSI Splitter cable cannot be used to add a second connection for a peripheral device.
7-3
7-4
Using Multi-Drive Mode
System Wiring
The AK-U0-RJ45-TB2P two-position terminal block connector
(
) can be used to conveniently daisy-chain the PowerFlex
4-Class drives. Two terminating resistors are also included with terminal block connectors in the AK-U0-RJ45-TB2P kit.
Figure 7.4 AK-U0-RJ45-TB2P Terminal Block Connector
show wiring diagrams for using the
AK-U0-RJ45-TB2P terminal block connectors.
Figure 7.5 Connector Wiring Diagram - Adapter Mounted in PowerFlex 40/400
To PowerFlex 40 or PowerFlex 400 Drive
(with 22-COMM-C adapter)
To
Drive 1
To
Drive 2
To
Drive 3
To
Drive 4
120
Ω
¼ Watt
Resistor
120
Ω
¼ Watt
Resistor
Figure 7.6 Connector Wiring Diagram - Adapter Mounted in DSI External Comms Kit
To DSI External Comms Kit
(with 22-COMM-C adapter)
To
Drive 0
To
Drive 1
To
Drive 2
To
Drive 3
To
Drive 4
NOTE: A terminating resistor is not required for this end of of the wiring. The resistor is
DSI External Comms Kit. built into the circuitry of the
120
Ω
¼ Watt
Resistor
Using Multi-Drive Mode
Understanding the I/O Image
The terms input and output are defined from the scanner’s point of view.
Therefore, output I/O is data that is output from the scanner and consumed by the adapter. Input I/O is status data that is produced by the adapter and consumed as input by the scanner. The I/O image table will vary based on the configuration of the adapter:
• Parameter 12 - [DSI I/O Cfg]
The image table always uses consecutive words starting at word 0.
illustrate examples of the Multi-Drive I/O
image with 16-bit words for ControlLogix and PLC-5 controllers respectively.
Figure 7.7 Multi-Drive Example of I/O Image for ControlLogix
DSI ControlNet
Controller Scanner or
Bridge
Output
Image
(Write)
Adapter
Word and I/O
0 Logic Command
1 Reference
2 Logic Command
3 Reference
4 Logic Command
5 Reference
6 Logic Command
7 Reference
8 Logic Command
9 Reference
Input
Image
(Read)
0 Pad Word
1 Pad Word
2 Logic Status
3 Feedback
4 Logic Status
5 Feedback
6 Logic Status
7 Feedback
8 Logic Status
9 Feedback
10 Logic Status
11 Feedback
Message
Handler
Message
Buffer
PowerFlex Drive 0
PowerFlex Drive 1
PowerFlex Drive 2
PowerFlex Drive 3
PowerFlex Drive 4
PowerFlex Drive 0
PowerFlex Drive 1
PowerFlex Drive 2
PowerFlex Drive 3
PowerFlex Drive 4
7-5
7-6
Using Multi-Drive Mode
Figure 7.8 Multi-Drive Example of I/O Image for PLC-5
ControlNet
Controller Scanner or
Bridge
Output
Image
(Write)
Adapter
Word and I/O
0 Logic Command
1 Reference
2 Logic Command
3 Reference
4 Logic Command
5 Reference
6 Logic Command
7 Reference
8 Logic Command
9 Reference
Input
Image
(Read)
0 Logic Status
1 Feedback
2 Logic Status
3 Feedback
4 Logic Status
5 Feedback
6 Logic Status
7 Feedback
8 Logic Status
9 Feedback
Message
Handler
Message
Buffer
DSI
PowerFlex Drive 0
PowerFlex Drive 1
PowerFlex Drive 2
PowerFlex Drive 3
PowerFlex Drive 4
PowerFlex Drive 0
PowerFlex Drive 1
PowerFlex Drive 2
PowerFlex Drive 3
PowerFlex Drive 4
Note: If a daisy-chained drive is disconnected from the RS-485 (DSI) network or powered down, the Logic Status and Feedback words for the affected drive will be set to 0.
Using Multi-Drive Mode
Configuring the RS-485 Network
The following parameters in each daisy-chained drive must be set to these values:
Parameter
P36 - [Start Source]
P38 - [Speed Reference]
A103 - [Comm Data Rate]
A104 - [Comm Node Addr]
A107 - [Comm Format]
Value
5 (Comm Port)
5 (Comm Port)
4 (19.2K)
1-247 (must be unique)
0 (RTU 8-N-1)
Note that the RS-485 network is fixed at 19.2K baud, 8 data bits, no parity, and 1 stop bit.
Important: Parameter A105 - [Comm Loss Action] in the drives that are daisy chained is still used in Multi-Drive mode. If the
RS-485 cable is disconnected or broken, the disconnected drive(s) will immediately take the corresponding Comm
Loss Action(s). Drive parameter A106 - [Comm Loss
Time] is not used in Multi-Drive mode. For a network disruption, adapter Parameters 08 - [Comm Flt Action] and 09 - [Idle Flt Action] determine the action taken for
ALL of the drives on the Multi-Drive node.
The following Multi-Drive parameters must be set in the 22-COMM-C:
Parameter
12 - [DSI I/O Cfg]
14 - [Drv 0 Addr]
15 - [Drv 1 Addr]
16 - [Drv 2 Addr]
17 - [Drv 3 Addr]
18 - [Drv 4 Addr]
Value
0 = Drive 0 connected
1 = Drives 0-1 connected
2 = Drives 0-2 connected
3 = Drives 0-3 connected
4 = Drives 0-4 connected
Equal to Drive 0 parameter A104 - [Comm Node Address]
Equal to Drive 1 parameter A104 - [Comm Node Address]
Equal to Drive 2 parameter A104 - [Comm Node Address]
Equal to Drive 3 parameter A104 - [Comm Node Address]
Equal to Drive 4 parameter A104 - [Comm Node Address]
After setting the 22-COMM-C parameters, set the Operating Mode
Jumper (J7) from “1x” (Single mode) to “5x” (Multi-Drive) operation, and reset the adapter or cycle power to invoke the change. Refer to
Setting Operating Mode and Node Address Switches on page 2-1 .
Important: The 22-COMM-C parameters can be set using a DSI peripheral (HIM, DriveExplorer with 22-SCM-232, etc.)
ONLY when the Operating Mode Jumper is in the “1x”
(Single mode) position.
7-7
7-8
Using Multi-Drive Mode
Example Configuration Settings
Adapter Settings
• The adapter Operating Mode Jumper (J7 in
) is set to the
“5x” (Multi-Drive) position.
• The 22-COMM-C adapter parameters are set as follows:
Parameter
12 - [DSI I/O Cfg]
14 - [Drv 0 Addr]
(1)
15 - [Drv 1 Addr]
(1)
16 - [Drv 2 Addr]
(1)
17 - [Drv 3 Addr]
(1)
18 - [Drv 4 Addr]
(1)
3
4
5
1
2
Value Description
4 “Drives 0-4” (5 drives on 1 node)
Address of Drive 0
Address of Drive 1
Address of Drive 2
Address of Drive 3
Address of Drive 4
(1)
The settings for these parameters must match the parameter A104 - [Comm Node
Addr] settings in the respective drives.
Drive Settings
Parameters for the five drives are set as follows:
Parameter
Value
Drive 0 Drive 1 Drive 2 Drive 3 Drive 4
P36 - [Start Source]
(2)
5 5 5
P38 - [Speed Reference] 5 5 5
A103 - [Comm Data Rate]
(1)
4 4 4
A104 - [Comm Node Addr]
A106 - [Comm Loss Time]
(1)
A105 - [Comm Loss Action]
1
0
5
0
2
0
5
0
3
0
5
0
The drive must be reset for a change to this parameter to take effect.
0
5
5
5
4
4
0
4
5
5
5
0
The settings for these parameters must match the respective parameter settings in the adapter (Parameter 14 - [Drv 0 Addr] through Parameter 18 - [Drv 4 Addr]).
0
5
Using Multi-Drive Mode
7-9
ControlLogix I/O Example
This example ladder logic program demonstrates using Multi-Drive
mode with five drives. See Figure 7.2
diagram.
Function of the Example Program
This example program enables you to:
• View status information from the drives such as Ready, Faulted, At
Speed, and Feedback.
• Control the drives using various Logic Command bits (Stop, Start, etc.) and Reference.
• Perform a single parameter read of drive parameter d003 - [Output
[Accel Time 1].
Current] and a single parameter write to drive parameter P039 -
Main Routine
The Main Routine reads the network Input Image from the scanner, initiates Drive 0 through Drive 4 control subroutines, and writes the network Output Image to the scanner. See Figure 7.9
. The Generic
Controller Module is configured for an Input Size of 12 words and an
Output Size of 10 words. For additional information about I/O
connection sizes, see Table 4.A
The following controller tags are used:
Tag Name Type
Drive_Input_Image
Drive_Output_Image
INT [10]
INT [10]
Description
Input Image Table
Output Image Table
7-10
Using Multi-Drive Mode
Figure 7.9 ControlLogix Main Routine
ControlLogix Multi-Drive Mode example program with a PowerFlex 40 on ControlNet (22-COMM-C adapter). In this example,
Four (4) PowerFlex 4 drives are daisy-chained to the main PowerFlex 40 (with installed 22-COMM-C adapter) via their RJ-45
ports (RS-485). In this mode, a total of up to five (5) PowerFlex 4/40/400's can exist as one (1) ControlNet node on the network.
0
Drive_Input_Image[0] and Drive_Input_Image[1] = Drive 0 Logic Status and Speed Feedback
Drive_Input_Image[2] and Drive_Input_Image[3] = Drive 1 Logic Status and Speed Feedback
Drive_Input_Image[4] and Drive_Input_Image[5] = Drive 2 Logic Status and Speed Feedback
Drive_Input_Image[6] and Drive_Input_Image[7] = Drive 3 Logic Status and Speed Feedback
Drive_Input_Image[8] and Drive_Input_Image[9] = Drive 4 Logic Status and Speed Feedback
COP
Copy File
Source _5_PowerFlex_4_Class_Drives:I.Data[2]
Dest Drive_Input_Image[0]
Length 10
1
2
JSR
Jump To Subroutine
Routine Name Drive_0
JSR
Jump To Subroutine
Routine Name Drive_1
3
JSR
Jump To Subroutine
Routine Name Drive_2
(End)
4
JSR
Jump To Subroutine
Routine Name Drive_3
5
6
Drive_Output_Image[2] and Drive_Output_Image[3] = Drive 1 Logic Command and Speed Reference
Drive_Output_Image[4] and Drive_Output_Image[5] = Drive 2 Logic Command and Speed Reference
Drive_Output_Image[6] and Drive_Output_Image[7] = Drive 3 Logic Command and Speed Reference
Drive_Output_Image[8] and Drive_Output_Image[9] = Drive 4 Logic Command and Speed Reference
JSR
Jump To Subroutine
Routine Name Drive_4
COP
Copy File
Source
Dest _5_PowerFlex_4_Class_Drives:O.Data[0]
Length
Drive_Output_Image[0]
10
Using Multi-Drive Mode
Drive 0 - Drive 4 Control Subroutines
The following Drive Control subroutines provide status information
(Logic Status and Feedback), control (Logic Command and Reference), and parameter read/write for each of the respective drives:
Control Subroutine Refer to…
Drive 0
Drive 1
Drive 2
Drive 3
Drive 4
The following program tags are used for the Drive 0 Control Subroutine:
Tag Name
Drive_0_Status_Ready
Drive_0_Status_Active
Drive_0_Status_Forward
Drive_0_Status_Reverse
Drive_0_Status_Faulted
Drive_0_Status_At_Speed
Drive_0_Speed_Feedback
Type
BOOL
BOOL
BOOL
BOOL
BOOL
BOOL
INT
Description
Drive 0 ready bit
Drive 0 active bit
Drive 0 forward bit
Drive 0 reverse bit
Drive 0 faulted bit
Drive 0 at speed bit
Drive 0 speed feedback word
Drive_0_Command_Stop
Drive_0_Command_Start
Drive_0_Command_Jog
Drive_0_Command_Clear_Faults
BOOL
BOOL
BOOL
BOOL
Drive 0 stop bit
Drive 0 start bit
Drive 0 jog bit
Drive 0 clear faults bit
Drive_0_Command_Forward_Reverse BOOL
Drive_0_Speed_Reference INT
Drive_0_Parameter_Read_Message
Drive_0_Parameter_Write_Message
MESSAGE
MESSAGE
Drive 0 forward/reverse bit
Drive 0 speed reference word
Get_Attribute_Single (Read)
Set_Atrribute_Single (Write)
Drive 1 through Drive 4 program tags are identical except for the naming convention. For example, “Drive_0_Status_Ready” for Drive 0 would be
“Drive_1_Status_Ready” for Drive 1.
7-11
7-12
Using Multi-Drive Mode
Figure 7.10 ControlLogix Drive 0 Control Subroutine
8
9
0
This section takes the data from the input image area and moves it to specific tags (Logic Status bits and Speed Feedback) for use elsewhere in the ladder program.
Drive_Input_Image[0].0
Drive_0_Status_Ready
10
11
12
1
2
3
4
5
6
7
Drive_Input_Image[0].1
Drive_Input_Image[0].3
Drive_Input_Image[0].3
/
Drive_Input_Image[0].7
Drive_0_Status_Active
Drive_0_Status_Forward
Drive_0_Status_Reverse
Drive_0_Status_Faulted
Drive_Input_Image[0].8
Drive_0_Status_At_Speed
COP
Copy File
Source Drive_Input_Image[1]
Dest Drive_0_Speed_Feedback
Length 1
This section takes the data from specific tags (Logic Command bits and Speed Reference) and moves them to the output image area for transmission to the scanner.
Drive_0_Command_Stop Drive_Output_Image[0].0
Drive_0_Command_Start
Drive_0_Command_Jog
Drive_0_Command_Clear_Faults
Drive_0_Command_Forward_Reverse
/
Drive_0_Command_Forward_Reverse
Drive_Output_Image[0].1
Drive_Output_Image[0].2
Drive_Output_Image[0].3
Drive_Output_Image[0].4
Drive_Output_Image[0].5
Using Multi-Drive Mode
Figure 7.10 ControlLogix Drive 0 Control Subroutine (Continued)
7-13
13
COP
Copy File
Source Drive_0_Speed_Reference
Dest
Length
Drive_Output_Image[1]
1
14
Drive 0 parameters are accessed by adding 17408 decimal (4400 hex) to the desired parameter number. This example reads data from Parameter d003 - [Output Current] by using an Instance of 17411 (17408 + 3).
Drive_0_Perform_Parameter_Read
Type - CIP Generic
Message Control
MSG
Drive_0_Parameter_Read_Message ...
EN
DN
ER
(End)
15
16
Drive 0 parameters are accessed by adding 17408 decimal (4400 hex) to the desired parameter number. This example writes data to Parameter P039 - [Accel Time 1] by using an Instance of 17447 (17408 + 39).
Drive_0_Perform_Parameter_Write
Type - CIP Generic
Message Control
MSG
Drive_0_Parameter_Write_Message ...
EN
DN
ER
Return
RET
7-14
Using Multi-Drive Mode
Figure 7.11 ControlLogix Drive 1 Control Subroutine
10
11
8
9
12
0
This section takes the data from the input image area and moves it to specific tags (Logic Status bits and Speed Feedback) for use elsewhere in the ladder program.
Drive_Input_Image[2].0
Drive_1_Status_Ready
5
6
1
2
3
4
7
Drive_Input_Image[2].1
Drive_Input_Image[2].3
Drive_Input_Image[2].3
/
Drive_Input_Image[2].7
Drive_1_Status_Active
Drive_1_Status_Forward
Drive_1_Status_Reverse
Drive_1_Status_Faulted
Drive_Input_Image[2].8
Drive_1_Status_At_Speed
COP
Copy File
Source Drive_Input_Image[3]
Dest Drive_1_Speed_Feedback
Length 1
This section takes the data from specific tags (Logic Command bits and Speed Reference) and moves them to the output image area for transmission to the scanner.
Drive_1_Command_Stop Drive_Output_Image[2].0
Drive_1_Command_Start
Drive_1_Command_Jog
Drive_1_Command_Clear_Faults
Drive_1_Command_Forward_Reverse
Drive_1_Command_Forward_Reverse
/
Drive_Output_Image[2].1
Drive_Output_Image[2].2
Drive_Output_Image[2].3
Drive_Output_Image[2].4
Drive_Output_Image[2].5
Using Multi-Drive Mode
Figure 7.11 ControlLogix Drive 1 Control Subroutine (Continued)
7-15
13
COP
Copy File
Source Drive_1_Speed_Reference
Dest
Length
Drive_Output_Image[3]
1
(End)
14
Drive_1_Perform_Parameter_Read
Type - CIP Generic
Message Control
MSG
Drive_1_Parameter_Read_Message ...
EN
DN
ER
15
16
Drive 1 parameters are accessed by adding 18432 decimal (4800 hex) to the desired parameter number. This example writes data to Parameter P039 - [Accel Time 1] by using an Instance of 18471 (18432 + 39).
Drive_1_Perform_Parameter_Write
Type - CIP Generic
Message Control
MSG
Drive_1_Parameter_Write_Message ...
EN
DN
ER
Return
RET
7-16
Using Multi-Drive Mode
Figure 7.12 ControlLogix Drive 2 Control Subroutine
10
11
8
9
12
0
This section takes the data from the input image area and moves it to specific tags (Logic Status bits and Speed Feedback) for use elsewhere in the ladder program.
Drive_Input_Image[4].0
Drive_2_Status_Ready
5
6
1
2
3
4
7
Drive_Input_Image[4].1
Drive_Input_Image[4].3
Drive_Input_Image[4].3
/
Drive_Input_Image[4].7
Drive_2_Status_Active
Drive_2_Status_Forward
Drive_2_Status_Reverse
Drive_2_Status_Faulted
Drive_Input_Image[4].8
Drive_2_Status_At_Speed
COP
Copy File
Source Drive_Input_Image[5]
Dest Drive_2_Speed_Feedback
Length 1
This section takes the data from specific tags (Logic Command bits and Speed Reference) and moves them to the output image area for transmission to the scanner.
Drive_2_Command_Stop Drive_Output_Image[4].0
Drive_2_Command_Start
Drive_2_Command_Jog
Drive_2_Command_Clear_Faults
Drive_2_Command_Forward_Reverse
/
Drive_2_Command_Forward_Reverse
Drive_Output_Image[4].1
Drive_Output_Image[4].2
Drive_Output_Image[4].3
Drive_Output_Image[4].4
Drive_Output_Image[4].5
Using Multi-Drive Mode
Figure 7.12 ControlLogix Drive 2 Control Subroutine (Continued)
7-17
13
COP
Copy File
Source Drive_2_Speed_Reference
Dest
Length
Drive_Output_Image[5]
1
14
Drive_2_Perform_Parameter_Read
Type - CIP Generic
Message Control
MSG
Drive_2_Parameter_Read_Message ...
EN
DN
ER
(End)
15
16
Drive_2_Perform_Parameter_Write
Type - CIP Generic
Message Control
MSG
Drive_2_Parameter_Write_Message ...
EN
DN
ER
Return
RET
7-18
Using Multi-Drive Mode
Figure 7.13 ControlLogix Drive 3 Control Subroutine
10
11
8
9
12
0
Drive_Input_Image[6].0
Drive_3_Command_Start
Drive_3_Command_Jog
Drive_3_Command_Clear_Faults
Drive_3_Command_Forward_Reverse
Drive_3_Command_Forward_Reverse
/
Drive_3_Status_Ready
5
6
1
2
3
4
7
Drive_Input_Image[6].1
Drive_Input_Image[6].3
Drive_Input_Image[6].3
/
Drive_Input_Image[6].7
Drive_3_Status_Active
Drive_3_Status_Forward
Drive_3_Status_Reverse
Drive_3_Status_Faulted
Drive_Input_Image[6].8
Drive_3_Status_At_Speed
COP
Copy File
Source Drive_Input_Image[7]
Dest Drive_3_Speed_Feedback
Length 1
This section takes the data from specific tags (Logic Command bits and Speed Reference) and moves them to the output image area for transmission to the scanner.
Drive_3_Command_Stop Drive_Output_Image[6].0
Drive_Output_Image[6].1
Drive_Output_Image[6].2
Drive_Output_Image[6].3
Drive_Output_Image[6].4
Drive_Output_Image[6].5
Using Multi-Drive Mode
Figure 7.13 ControlLogix Drive 3 Control Subroutine (Continued)
7-19
13
COP
Copy File
Source Drive_3_Speed_Reference
Dest Drive_Output_Image[7]
Length 1
(End)
14
Drive 3 parameters are accessed by adding 20480 decimal (5000 hex) to the desired parameter number. This example reads data from Parameter d003 - [Output Current] by using an Instance of 20483 (20480 + 3).
Drive_3_Perform_Parameter_Read
Type - CIP Generic
Message Control
MSG
Drive_3_Parameter_Read_Message ...
EN
DN
ER
15
16
Drive 3 parameters are accessed by adding 20480 decimal (5000 hex) to the desired parameter number. This example writes data to Parameter P039 - [Accel Time 1] by using an Instance of 20519 (20480 + 39).
Drive_3_Perform_Parameter_Write
Type - CIP Generic
Message Control
MSG
Drive_3_Parameter_Write_Message ...
EN
DN
ER
Return
RET
7-20
Using Multi-Drive Mode
Figure 7.14 ControlLogix Drive 4 Control Subroutine
10
11
8
9
12
0
Drive_Input_Image[8].0
Drive_4_Command_Start
Drive_4_Command_Jog
Drive_4_Command_Clear_Faults
Drive_4_Command_Forward_Reverse
Drive_4_Command_Forward_Reverse
/
Drive_4_Status_Ready
5
6
1
2
3
4
7
Drive_Input_Image[8].1
Drive_Input_Image[8].3
Drive_Input_Image[8].3
/
Drive_Input_Image[8].7
Drive_4_Status_Active
Drive_4_Status_Forward
Drive_4_Status_Reverse
Drive_4_Status_Faulted
Drive_Input_Image[8].8
Drive_4_Status_At_Speed
COP
Copy File
Source Drive_Input_Image[9]
Dest Drive_4_Speed_Feedback
Length 1
This section takes the data from specific tags (Logic Command bits and Speed Reference) and moves them to the output image area for transmission to the scanner.
Drive_4_Command_Stop Drive_Output_Image[8].0
Drive_Output_Image[8].1
Drive_Output_Image[8].2
Drive_Output_Image[8].3
Drive_Output_Image[8].4
Drive_Output_Image[8].5
Using Multi-Drive Mode
Figure 7.14 ControlLogix Drive 4 Control Subroutine (Continued)
7-21
13
COP
Copy File
Source Drive_4_Speed_Reference
Dest
Length
Drive_Output_Image[9]
1
14
Drive_4_Perform_Parameter_Read
Type - CIP Generic
Message Control
MSG
Drive_4_Parameter_Read_Message ...
EN
DN
ER
(End)
15
16
Drive_4_Perform_Parameter_Write
Type - CIP Generic
Message Control
MSG
Drive_4_Parameter_Write_Message ...
EN
DN
ER
Return
RET
7-22
Using Multi-Drive Mode
ControlLogix Explicit Messaging
Parameter addressing for Explicit messaging is different in Multi-Drive than with Single mode. In Single mode, the Instance value in the message equals the desired parameter number in the drive. In
Multi-Drive mode, an Instance table is used to account for the parameters in the adapter and up to 5 drives. The parameters in the adapter and each of the drives are offset by 400 hex (1024 decimal):
Instance (Hex.) (Dec.)
4000 - 43FF
4400 - 47FF
16384 - 17407
17408 - 18431
Device
22-COMM-C
Drive 0
Parameter
0 - 1023
0 - 1023
4800 - 4BFF
4C00 - 4FFF
5000 - 53FF
5400 - 57FF
18432 - 19455
19456 - 20479
20480 - 21503
21504 - 22527
Drive 1
Drive 2
Drive 3
Drive 4
0 - 1023
0 - 1023
0 - 1023
0 - 1023
Explicit messages for Drive 0 through Drive 4 are identical except for the Instance values. The following PowerFlex 4-Class drive parameters used for the explicit message example in this section show the different
Instance values required for each drive:
Parameter d003 - [Output Current]
Drive 0 Instance = 17411 (17408 + 3)
Drive 1 Instance = 18435 (18432 + 3)
Drive 2 Instance = 19459 (19456 + 3)
Drive 3 Instance = 20483 (20480 + 3)
Drive 4 Instance = 21507 (21504 + 3)
Parameter P039 - [Accel Time 1]
Drive 0 Instance = 17447 (17408 + 39)
Drive 1 Instance = 18471 (18432 + 39)
Drive 2 Instance = 19495 (19456 + 39)
Drive 3 Instance = 20519 (20480 + 39)
Drive 4 Instance = 21543 (21504 + 39)
Drive 0 Explicit Message Example
The Explicit message examples in the ControlLogix example program
(
) perform a read (Get_Attribute_Single) of parameter d003 -
[Output Current] and a write (Set_Attribute_Single) to parameter P039 -
[Accel Time 1] for PowerFlex 4-Class drives. The configuration for the read is shown in
and the write is shown in
Using Multi-Drive Mode
Figure 7.15 ControlLogix Parameter Read Message Configuration
7-23
Figure 7.16 ControlLogix Parameter Write Message Configuration
The Class Code is “ f ” for the CIP Parameter Object and the Attribute is
“1” to select the parameter value. See
for more information. The Instance value is “17411” to access parameter
Time 1].
d003 - [Output Current] and “17447” to access parameter P039 - [Accel
7-24
Using Multi-Drive Mode
PLC-5 I/O Example
Important: Due to PLC-5 controller limitations, explicit messaging cannot be performed in Multi-Drive mode.
This example ladder logic program demonstrates using Multi-Drive
mode with five drives. See Figure 7.2
diagram.
Function of the Example Program
This example program enables you to:
• View status information from the drives such as Ready, Faulted, At
Speed, and Feedback.
• Control the drives using various Logic Command bits (Stop, Start, etc.) and Reference.
Main Routine
The Main Routine reads the network Input Image from the scanner, initiates Drive 0 through Drive 4 control subroutines (U:3 through U:7 files), and writes the network Output Image to the scanner. See
.
Using Multi-Drive Mode
7-25
Figure 7.17 PLC-5 Main Routine
0000
Rung 0000 enables the controller to activate the Drive 0 control (DRIVE 0) subroutine (LAD 3)
JSR
Jump To Subroutine
Prog File Number U:3
0001
Rung 0001 enables the controller to activate the Drive 1 control (DRIVE 1) subroutine (LAD 4)
JSR
Jump To Subroutine
Prog File Number U:4
0002
Rung 0002 enables the controller to activate the Drive 2 control (DRIVE 2) subroutine (LAD 5)
JSR
Jump To Subroutine
Prog File Number U:5
0003
Rung 0003 enables the controller to activate the Drive 3 control (DRIVE 3) subroutine (LAD 6)
JSR
Jump To Subroutine
Prog File Number U:6
0004
Rung 0004 enables the controller to activate the Drive 4 control (DRIVE 4) subroutine (LAD 7)
JSR
Jump To Subroutine
Prog File Number U:7
0005 END
7-26
Using Multi-Drive Mode
Drive 0 - Drive 4 Control Subroutines
The following Drive Control Subroutines provide status information
(Logic Status and Feedback) and control (Logic Command and
Reference) for each of the respective drives:
Control Subroutine Refer to…
Drive 0
Drive 1
Drive 2
Drive 3
Drive 4
Figure 7.18 PLC-5 Drive 0 Control Subroutine (U:3)
0000
0001
0002
0003
0004
0005
Drive 0 Control Subroutine
In this example, an operator station is wired into the local PLC-5/40C rack as follows:
O:000/0 Drive 0 Ready
O:000/1 Drive 0 Active
O:000/2 Drive 0 Forward
O:000/3 Drive 0 Reverse
O:000/4 Drive 0 Faulted
O:000/5 Drive 0 At Speed
O:001 Drive 0 Operator Speed Feedback
I:000/0 Drive 0 Stop (Normally Open Pushbutton)
I:000/1 Drive 0 Start (Normally Open Pushbutton)
I:000/2 Drive 0 Jog (Normally Open Pushbutton)
I:000/3 Drive 0 Clear Faults (Normally Open Pushbutton)
I:000/4 Drive 0 Forward / Reverse Selector Switch
I:001 Drive 0 Operator Speed Reference
In this example, a PowerFlex 40 drive with installed 22-COMM-C ControlNet adapter is mapped as follows:
N9:0 Drive 0 Logic Status N10:0 Drive 0 Logic Command
N9:1 Drive 0 Speed Feedback N10:1 Drive 0 Speed Reference
Rungs 0000 through 0005 move the Logic Status from Drive 0 to the operator station.
Drive 0 Logic Status
READY
N9:0
0
Drive 0 Logic Status
ACTIVE
N9:0
1
Drive 0 Logic Status
ACTUAL FORWARD /
REVERSE DIRECTION
N9:0
3
Drive 0 Logic Status
ACTUAL FORWARD /
REVERSE DIRECTION
N9:0
3
Drive 0 Logic Status
FAULTED
N9:0
7
Drive 0 Logic Status
AT SPEED
N9:0
8
Drive 0 Operator
Ready Status
Display
O:000
0
Drive 0 Operator
Active Status
Display
O:000
1
Drive 0 Operator
Actual Forward
Status Display
O:000
2
Drive 0 Operator
Actual Reverse
Status Display
O:000
3
Drive 0 Operator
Fault Status
Display
O:000
4
Drive 0 Operator
At Speed Status
Display
O:000
5
Using Multi-Drive Mode
Figure 7.18 PLC-5 Drive 0 Control Subroutine (U:3) (Continued)
7-27
0006
Rung 0006 moves the Speed Feedback from Drive 0 to the operator station.
0007
Rungs 0007 through 0012 move the Logic Command from the operator station to Drive 0.
Drive 0 Operator
Stop Pushbutton
I:000
0
0008
Drive 0 Operator
Start Pushbutton
I:000
1
0014
0013
0009
0010
0011
0012
Drive 0 Operator
Clear Faults
Pushbutton
I:000
Drive 0 Operator
Jog Pushbutton
I:000
2
3
Drive 0 Operator
Forward / Reverse
Selector Switch
I:000
4
Drive 0 Operator
Forward / Reverse
Selector Switch
I:000
4
Rung 0013 moves the Speed Reference from the operator station to Drive 0.
Drive 0
Speed Feedback
MOV
Move
Source N9:1
0<
Dest O:001
0<
Drive 0 Logic
Command
STOP
N10:0
0
Drive 0 Logic
Command
START
N10:0
1
Drive 0 Logic
Command
JOG
N10:0
2
Drive 0 Logic
Command
CLEAR FAULTS
N10:0
3
Drive 0 Logic
Command
FORWARD
N10:0
4
Drive 0 Logic
Command
REVERSE
N10:0
5
Drive 0
Speed Reference
MOV
Move
Source I:001
0<
Dest N10:1
0<
END
7-28
Using Multi-Drive Mode
Figure 7.19 PLC-5 Drive 1 Control Subroutine (U:4)
0000
0001
0002
0003
0004
0005
Drive 1 Control Subroutine
In this example, an operator station is wired into the local PLC-5/40C rack as follows:
O:002/0 Drive 1 Ready
O:002/1 Drive 1 Active
O:002/2 Drive 1 Forward
O:002/3 Drive 1 Reverse
O:002/4 Drive 1 Faulted
O:002/5 Drive 1 At Speed
O:003 Drive 1 Operator Speed Feedback
I:002/0 Drive 1 Stop (Normally
Open Pushbutton)
I:002/1 Drive 1 Start (Normally Open Pushbutton)
I:002/2 Drive 1 Jog (Normally Open Pushbutton)
I:002/3 Drive 1 Clear Faults (Normally Open Pushbutton)
I:002/4 Drive 1 Forward / Reverse Selector Switch
I:003 Drive 1 Operator Speed Reference
In this example, a PowerFlex 40 drive with installed 22-COMM-C ControlNet adapter is mapped as follows:
N9:2 Drive 1 Logic Status N10:2 Drive 1 Logic Command
N9:3 Drive 1 Speed Feedback N10:3 Drive 1 Speed Reference
Rungs 0000 through 0005 move the Logic Status from Drive 1 to the operator station.
Drive 1 Logic Status
READY
N9:2
0
Drive 1 Logic Status
ACTIVE
N9:2
1
Drive 1 Operator
Ready Status
Display
O:002
0
Drive 1 Operator
Active Status
Display
O:002
1
Drive 1 Logic Status
ACTUAL FORWARD /
REVERSE DIRECTION
N9:2
3
Drive 1 Logic Status
ACTUAL FORWARD /
REVERSE DIRECTION
N9:2
3
Drive 1 Logic Status
FAULTED
N9:2
7
Drive 1 Logic Status
AT SPEED
N9:2
8
Drive 1 Operator
Actual Forward
Status Display
O:002
2
Drive 1 Operator
Actual Reverse
Status Display
O:002
3
Drive 1 Operator
Fault Status
Display
O:002
4
Drive 1 Operator
At Speed Status
Display
O:002
5
Using Multi-Drive Mode
Figure 7.19 PLC-5 Drive 1 Control Subroutine (U:4) (Continued)
7-29
0006
Rung 0006 moves the Speed Feedback from Drive 1 to the operator station.
0007
Rungs 0007 through 0012 move the Logic Command from the operator station to Drive 1.
Drive 1 Operator
Stop Pushbutton
I:002
0
0008
Drive 1 Operator
Start Pushbutton
I:002
1
0014
0009
0010
0011
0012
0013
Drive 1 Operator
Clear Faults
Pushbutton
I:002
Drive 1 Operator
Jog Pushbutton
I:002
2
3
Drive 1 Operator
Forward / Reverse
Selector Switch
I:002
4
Drive 1 Operator
Forward / Reverse
Selector Switch
I:002
4
Rung 0013 moves the Speed Reference from the operator station to Drive 1.
Drive 1
Speed Feedback
MOV
Move
Source N9:3
0<
Dest O:003
0<
Drive 1 Logic
Command
STOP
N10:2
0
Drive 1 Logic
Command
START
N10:2
1
Drive 1 Logic
Command
JOG
N10:2
2
Drive 1 Logic
Command
CLEAR FAULTS
N10:2
3
Drive 1 Logic
Command
FORWARD
N10:2
4
Drive 1 Logic
Command
REVERSE
N10:2
5
Drive 1
Speed Reference
MOV
Move
Source I:003
0<
Dest N10:3
0<
END
7-30
Using Multi-Drive Mode
Figure 7.20 PLC-5 Drive 2 Control Subroutine (U:5)
0000
0001
0002
0003
0004
0005
Drive 2 Control Subroutine
In this example, an operator station is wired into the local PLC-5/40C rack as follows:
O:004/0 Drive 2 Ready
O:004/1 Drive 2 Active
O:004/2 Drive 2 Forward
O:004/3 Drive 2 Reverse
O:004/4 Drive 2 Faulted
O:004/5 Drive 2 At Speed
O:005 Drive 2 Operator Speed Feedback
I:004/0 Drive 2 Stop (Normally Open Pushbutton)
I:004/1 Drive 2 Start (Normally Open Pushbutton)
I:004/2 Drive 2 Jog (Normally Open Pushbutton)
I:004/3 Drive 2 Clear Faults (Normally Open Pushbutton)
I:004/4 Drive 2 Forward / Reverse Selector Switch
I:005 Drive 2 Operator Speed Reference
In this example, a PowerFlex 40 drive with installed 22-COMM-C ControlNet adapter is mapped as follows:
N9:4 Drive 2 Logic Status N10:4 Drive 2 Logic Command
N9:5 Drive 2 Speed Feedback N10:5 Drive 2 Speed Reference
Rungs 0000 through 0005 move the Logic Status from Drive 2 to the operator station.
Drive 2 Logic Status
READY
N9:4
0
Drive 2 Logic Status
ACTIVE
N9:4
1
Drive 2 Operator
Ready Status
Display
O:004
0
Drive 2 Operator
Active Status
Display
O:004
1
Drive 2 Logic Status
ACTUAL FORWARD /
REVERSE DIRECTION
N9:4
3
Drive 2 Logic Status
ACTUAL FORWARD /
REVERSE DIRECTION
N9:4
3
Drive 2 Logic Status
FAULTED
N9:4
7
Drive 2 Logic Status
AT SPEED
N9:4
8
Drive 2 Operator
Actual Forward
Status Display
O:004
2
Drive 2 Operator
Actual Reverse
Status Display
O:004
3
Drive 2 Operator
Fault Status
Display
O:004
4
Drive 2 Operator
At Speed Status
Display
O:004
5
Using Multi-Drive Mode
Figure 7.20 PLC-5 Drive 2 Control Subroutine (U:5) (Continued)
7-31
0006
Rung 0006 moves the Speed Feedback from Drive 2 to the operator station.
0007
Rungs 0007 through 0012 move the Logic Command from the operator station to Drive 2.
Drive 2 Operator
Stop Pushbutton
I:004
0
0008
Drive 2 Operator
Start Pushbutton
I:004
1
0014
0009
0010
0011
0012
0013
Drive 2 Operator
Clear Faults
Pushbutton
I:004
Drive 2 Operator
Jog Pushbutton
I:004
2
3
Drive 2 Operator
Forward / Reverse
Selector Switch
I:004
4
Drive 2 Operator
Forward / Reverse
Selector Switch
I:004
4
Rung 0013 moves the Speed Reference from the operator station to Drive 2.
Drive 2
Speed Feedback
MOV
Move
Source N9:5
0<
Dest O:005
0<
Drive 2 Logic
Command
STOP
N10:4
0
Drive 2 Logic
Command
START
N10:4
1
Drive 2 Logic
Command
JOG
N10:4
2
Drive 2 Logic
Command
CLEAR FAULTS
N10:4
3
Drive 2 Logic
Command
FORWARD
N10:4
4
Drive 2 Logic
Command
REVERSE
N10:4
5
Drive 2
Speed Reference
MOV
Move
Source I:005
0<
Dest N10:5
0<
END
7-32
Using Multi-Drive Mode
Figure 7.21 PLC-5 Drive 3 Control Subroutine (U:6)
0000
0001
0002
0003
0004
0005
Drive 3 Control Subroutine
In this example, an operator station is wired into the local PLC-5/40C rack as follows:
O:006/0 Drive 3 Ready
O:006/1 Drive 3 Active
O:006/2 Drive 3 Forward
O:006/3 Drive 3 Reverse
O:006/4 Drive 3 Faulted
O:006/5 Drive 3 At Speed
O:007 Drive 3 Operator Speed Feedback
I:006/0 Drive 3 Stop (Normally Open Pushbutton)
I:006/1 Drive 3 Start (Normally Open Pushbutton)
I:006/2 Drive 3 Jog (Normally Open Pushbutton)
I:006/3 Drive 3 Clear Faults (Normally Open Pushbutton)
I:006/4 Drive 3 Forward / Reverse Selector Switch
I:007 Drive 3 Operator Speed Reference
In this example, a PowerFlex 40 drive with installed 22-COMM-C ControlNet adapter is mapped as follows:
N9:6 Drive 3 Logic Status N10:6 Drive 3 Logic Command
N9:7 Drive 3 Speed Feedback N10:7 Drive 3 Speed Reference
Rungs 0000 through 0005 move the Logic Status from Drive 3 to the operator station.
Drive 3 Logic Status
READY
N9:6
0
Drive 3 Logic Status
ACTIVE
N9:6
1
Drive 3 Operator
Ready Status
Display
O:006
0
Drive 3 Operator
Active Status
Display
O:006
1
Drive 3 Logic Status
ACTUAL FORWARD /
REVERSE DIRECTION
N9:6
3
Drive 3 Logic Status
ACTUAL FORWARD /
REVERSE DIRECTION
N9:6
3
Drive 3 Logic Status
FAULTED
N9:6
7
Drive 3 Logic Status
AT SPEED
N9:6
8
Drive 3 Operator
Actual Forward
Status Display
O:006
2
Drive 3 Operator
Actual Reverse
Status Display
O:006
3
Drive 3 Operator
Fault Status
Display
O:006
4
Drive 3 Operator
At Speed Status
Display
O:006
5
Using Multi-Drive Mode
Figure 7.21 PLC-5 Drive 3 Control Subroutine (U:6) (Continued)
7-33
0006
Rung 0006 moves the Speed Feedback from Drive 3 to the operator station.
0007
Rungs 0007 through 0012 move the Logic Command from the operator station to Drive 3.
Drive 3 Operator
Stop Pushbutton
I:006
0
0008
Drive 3 Operator
Start Pushbutton
I:006
1
0014
0009
0010
0011
0012
0013
Drive 3 Operator
Clear Faults
Pushbutton
I:006
Drive 3 Operator
Jog Pushbutton
I:006
2
3
Drive 3 Operator
Forward / Reverse
Selector Switch
I:006
4
Drive 3 Operator
Forward / Reverse
Selector Switch
I:006
4
Rung 0013 moves the Speed Reference from the operator station to Drive 3.
Drive 3
Speed Feedback
MOV
Move
Source N9:7
0<
Dest O:007
0<
Drive 3 Logic
Command
STOP
N10:6
0
Drive 3 Logic
Command
START
N10:6
1
Drive 3 Logic
Command
JOG
N10:6
2
Drive 3 Logic
Command
CLEAR FAULTS
N10:6
3
Drive 3 Logic
Command
FORWARD
N10:6
4
Drive 3 Logic
Command
REVERSE
N10:6
5
Drive 3
Speed Reference
MOV
Move
Source I:007
0<
Dest N10:7
0<
END
7-34
Using Multi-Drive Mode
Figure 7.22 PLC-5 Drive 4 Control Subroutine (U:7)
0000
0001
0002
0003
0004
0005
Drive 4 Control Subroutine
In this example, an operator station is wired into the local PLC-5/40C rack as follows:
O:010/0 Drive 4 Ready
O:010/1 Drive 4 Active
O:010/2 Drive 4 Forward
O:010/3 Drive 4 Reverse
O:010/4 Drive 4 Faulted
O:010/5 Drive 4 At Speed
O:011 Drive 4 Operator Speed Feedback
I:010/0 Drive 4 Stop (Normally Open Pushbutton)
I:010/1 Drive 4 Start (Normally Open Pushbutton)
I:010/2 Drive 4 Jog (Normally Open Pushbutton)
I:010/3 Drive 4 Clear Faults (Normally Open Pushbutton)
I:010/4 Drive 4 Forward / Reverse Selector Switch
I:011 Drive 4 Operator Speed Reference
In this example, a PowerFlex 40 drive with installed 22-COMM-C ControlNet adapter is mapped as follows:
N9:8 Drive 4 Logic Status N10:8 Drive 4 Logic Command
N9:9 Drive 4 Speed Feedback N10:9 Drive 4 Speed Reference
Rungs 0000 through 0005 move the Logic Status from Drive 4 to the operator station.
Drive 4 Logic Status
READY
N9:8
0
Drive 4 Logic Status
ACTIVE
N9:8
1
Drive 4 Operator
Ready Status
Display
O:010
0
Drive 4 Operator
Active Status
Display
O:010
1
Drive 4 Logic Status
ACTUAL FORWARD /
REVERSE DIRECTION
N9:8
3
Drive 4 Logic Status
ACTUAL FORWARD /
REVERSE DIRECTION
N9:8
3
Drive 4 Logic Status
FAULTED
N9:8
8
7
Drive 4 Logic Status
AT SPEED
N9:8
Drive 4 Operator
Actual Forward
Status Display
O:010
2
Drive 4 Operator
Actual Reverse
Status Display
O:010
3
Drive 4 Operator
Fault Status
Display
O:010
4
Drive 4 Operator
At Speed Status
Display
O:010
5
Using Multi-Drive Mode
Figure 7.22 PLC-5 Drive 4 Control Subroutine (U:7) (Continued)
7-35
0006
Rung 0006 moves the Speed Feedback from Drive 4 to the operator station.
0007
Rungs 0007 through 0012 move the Logic Command from the operator station to Drive 4.
Drive 4 Operator
Stop Pushbutton
I:010
0
0008
Drive 4 Operator
Start Pushbutton
I:010
1
0014
0009
0010
0011
0012
0013
Drive 4 Operator
Clear Faults
Pushbutton
I:010
Drive 4 Operator
Jog Pushbutton
I:010
2
3
Drive 4 Operator
Forward / Reverse
Selector Switch
I:010
4
Drive 4 Operator
Forward / Reverse
Selector Switch
I:010
4
Rung 0013 moves the Speed Reference from the operator station to Drive 4.
Drive 4
Speed Feedback
MOV
Move
Source N9:9
0<
Dest O:011
0<
Drive 4 Logic
Command
STOP
N10:8
0
Drive 4 Logic
Command
START
N10:8
1
Drive 4 Logic
Command
JOG
N10:8
2
Drive 4 Logic
Command
CLEAR FAULTS
N10:8
3
Drive 4 Logic
Command
FORWARD
N10:8
4
Drive 4 Logic
Command
REVERSE
N10:8
5
Drive 4
Speed Reference
MOV
Move
Source I:011
0<
Dest N10:9
0<
END
7-36
Using Multi-Drive Mode
Additional Information
• When the adapter — mounted in a PowerFlex 40/400 drive (Drive 0) or a DSI External Comms Kit — is powered up, all configured daisy-chained drives must be present before an I/O connection is allowed on the network (i.e., before the drives can be controlled).
• When the PowerFlex 40/400 drive with the internal-mounted adapter
(Drive 0) is powered down, communications with the daisy-chained drives is disrupted and the drives will take their respective Comm
Loss Actions. When the adapter is used in a DSI External Comms Kit
(22-XCOMM-DC-BASE), communications will not be disrupted when a daisy-chained drive is powered down.
• When any of the daisy-chained drives are powered down, the respective Input Image (Logic Status and Feedback) sent to the scanner will be zeros, and the PORT and MOD LEDs on the adapter the last drive is disconnected or powered down.
will alternately flash red. The I/O connection will not be dropped until
Important: Status information from the scanner will not indicate there is a fault at the node, and the I/O connection will not be dropped. If your application requires an action to be taken when DSI communication is lost with one or more drives, monitor adapter Parameter 13 - [DSI I/O
Act] to verify that the adapter is communicating with all connected drives.
Chapter
8
Troubleshooting
Chapter 8 provides information for troubleshooting potential problems with the adapter.
Topic
Locating the Status Indicators
Net A and B Status Indicators Together
Net A or B Status Indicators Independently
Adapter Diagnostic Items in Single Mode
Adapter Diagnostic Items in Multi-Drive Mode
Locating the Status Indicators
Page
The adapter has four status indicators. They can be viewed on the adapter or through the drive cover. See
.
Figure 8.1 Status Indicators (location on drive may vary)
➊
➋
➌
➍
Bottom side of adapter board
Item Status Indicator Description
➊
PORT
➋
MOD
➌
NET A
➍
NET B
Page
DSI Connection Status
Adapter Status
ControlNet A Status
ControlNet B Status
➊
➋
➌
➍
8-2
Troubleshooting
PORT Status Indicator
Status Cause
Off The adapter is not powered or not properly connected to the drive.
Flashing
Red
Corrective Action
• Securely connect the adapter to the drive using the Internal Interface (ribbon) cable.
In Single mode, the adapter is not receiving communication from the drive.
• Apply power to the drive (or adapter if mounted in a DSI External Comms Kit).
• Verify that the Operating Mode Jumper
corresponding to the mode in which the adapter is being used.
In Multi-Drive mode, the adapter is not receiving communication from a drive, or a drive is not an
Allen-Bradley drive.
• Verify the setting for Parameter 12 - [DSI
I/O Cfg].
• Verify that cables are securely connected and not damaged. Replace cables if necessary.
• Cycle power to the drive (or adapter if mounted in a DSI External Comms Kit).
Solid
Green
Green
Flashing The adapter is establishing communications with the drive.
The adapter is properly connected and is communicating with the drive.
Orange The drive is not an
Allen-Bradley drive.
• Use Allen-Bradley PowerFlex 4/40/400 drives.
No action required. This status indicator will turn solid green or flashing red.
No action required.
Use an Allen-Bradley PowerFlex 4/40/400 drive.
Troubleshooting
8-3
MOD Status Indicator
Status
Off
Flashing
Red
Solid
Solid
Green
Red
Green
Flashing
Cause
The adapter is not powered or not properly connected to the drive.
The adapter has failed the firmware test.
The adapter has failed the hardware test.
The adapter is operational, but is not transferring I/O data.
The adapter is operational and transferring I/O data.
Corrective Action
• Securely connect the adapter to the drive using the Internal Interface (ribbon) cable.
• Apply power to the drive (or adapter if mounted in a DSI External Comms Kit).
• Cycle power to the drive (or adapter if mounted in a DSI External Comms Kit).
• If cycling power does not correct the problem, the adapter parameter settings may have been corrupted. Reset defaults and reconfigure the adapter.
• If resetting defaults does not correct the problem, flash the adapter with the latest firmware release.
• Cycle power to the drive (or adapter if mounted in a DSI External Comms Kit).
• Replace the adapter.
• Place the scanner in RUN mode.
• Program the controller to recognize and transmit I/O to the adapter.
• Configure the adapter for the program in the controller.
No action required.
8-4
Troubleshooting
Net A and B Status Indicators Together
Status
Both LEDs are
Off.
Both LEDs are steady Red.
LEDs are alternating
Red/Green.
LEDs are alternating
Red/Off.
Cause
A reset occurred or there is no power.
A link interface failed.
Corrective Actions
Apply power to the drive (or adapter if mounted in a DSI External Comms Kit).
• Check media for broken cables, loose connectors, missing terminators, etc.
The adapter is in self-test mode.
There is a bad node configuration.
• Power cycle or reset the adapter. If the problem persists, contact
Allen-Bradley Drives Technical
Support.
No action required. The adapter will exit this mode when the self-test is completed.
• Verify that all node addresses are unique.
• Check the adapter’s configuration.
• Check media for broken cables, loose connectors, missing terminators, etc.
• Power cycle or reset the adapter.
Net A or B Status Indicators Independently
Status
One channel
LED is steady
Off.
One channel
LED is flashing
Red/Green.
One channel
LED is flashing
Red/Off.
Cause
That channel is disabled or not supported.
There is an invalid link configuration for that channel.
The channel is not receiving network activity.
Corrective Actions
Program the network for redundant media, if required.
• Power cycle or reset the adapter.
• Reset the controller.
• If the problem persists, contact
Allen-Bradley Drives Technical
Support.
Check media for broken cables, loose connectors, missing terminators, etc.
One channel
LED is flashing
Green/Off.
One channel
LED is steady
Green.
A temporary channel error has occurred, or the channel is in listen-only mode.
Normal operation for that channel.
Verify the controller is present on the network and working.
No action required.
Troubleshooting
Adapter Diagnostic Items in Single Mode
The following diagnostic items can be accessed using a PowerFlex
4-Class HIM, DriveExplorer (version 3.01 or higher), or DriveExecutive
(version 3.01 or higher).
2
3
No.
Name
1 Reserved
Logic Cmd
Reference
4
5
Reserved
Logic Sts
6 Feedback
7 – 22 Reserved
Description
—
The Logic Command being transmitted to the drive by the adapter.
The Reference being transmitted to the drive by the adapter.
—
The Logic Status being received from the drive by the adapter.
The Feedback being received from the drive by the adapter.
—
23 DSI Overrun Errs The number of DSI receive overrun errors.
24 DSI Framing Errs The number of DSI receive framing errors.
25 DSI CRC Errs The number of DSI receive CRC errors.
26 Boot Flash Count The number of boot firmware flash updates made to the adapter after
27 App Flash Count shipping.
The number of application firmware flash updates made to the adapter after shipping.
28 Node Address SW The current value of the node address switches.
29 CN Packets Rcvd A count of the number of network packets received by the adapter.
30 CN Rx Underflows A count of the number of network receive underflow errors.
31 CN Rx Overflows A count of the number of network receive overflow errors.
32 CN Rx Bad Frames A count of the number of network receive bad frame errors.
33 CN Packets Sent A count of the number of network packets transmitted by the adapter.
34 CN Tx Underflows A count of the number of network transmit underflow errors.
35 CN Tx Overflows A count of the number of network transmit overflow errors.
36 CN Tx Out Of Steps A count of the number of network transmit out of step errors.
37 CN Tx Blockages A count of the number of network transmit blockage errors.
8-5
8-6
Troubleshooting
Adapter Diagnostic Items in Multi-Drive Mode
The following diagnostic items can be accessed using a PowerFlex
4-Class HIM or DriveExplorer (version 3.01 or higher).
5
6
3
4
No.
Name
1
2
Reserved
Description
—
Drv 0 Logic Cmd The Logic Command being transmitted to drive 0 by the adapter.
Drv 0 Reference
Reserved
Drv 0 Logic Sts
Drv 0 Feedback
The Reference being transmitted to drive 0 by the adapter.
—
The Logic Status being received from drive 0 by the adapter.
The Feedback being received from drive 0 by the adapter.
7
8
Drv 1 Logic Cmd The Logic Command being transmitted to drive 1 by the adapter.
Drv 1 Reference The Reference being transmitted to drive 1 by the adapter.
9 Drv 1 Logic Sts
10 Drv 1 Feedback
The Logic Status being received from drive 1 by the adapter.
The Feedback being received from drive 1 by the adapter.
11 Drv 2 Logic Cmd The Logic Command being transmitted to drive 2 by the adapter.
12 Drv 2 Reference
13 Drv 2 Logic Sts
14 Drv 2 Feedback
The Reference being transmitted to drive 2 by the adapter.
The Logic Status being received from drive 2 by the adapter.
The Feedback being received from drive 2 by the adapter.
15 Drv 3 Logic Cmd The Logic Command being transmitted to drive 3 by the adapter.
16 Drv 3 Reference The Reference being transmitted to drive 3 by the adapter.
17 Drv 3 Logic Sts
18 Drv 3 Feedback
The Logic Status being received from drive 3 by the adapter.
The Feedback being received from drive 3 by the adapter.
19 Drv 4 Logic Cmd The Logic Command being transmitted to drive 4 by the adapter.
20 Drv 4 Reference The Reference being transmitted to drive 4 by the adapter.
21 Drv 4 Logic Sts
22 Drv 4 Feedback
The Logic Status being received from drive 4 by the adapter.
The Feedback being received from drive 4 by the adapter.
23 DSI Overrun Errs The number of DSI receive overrun errors.
24 DSI Framing Errs The number of DSI receive framing errors.
25 DSI CRC Errs
27 App Flash Count
The number of DSI receive CRC errors.
26 Boot Flash Count The number of boot firmware flash updates made to the adapter after shipping.
The number of application firmware flash updates made to the adapter after shipping.
28 Node Address SW The current value of the node address switches.
29 CN Packets Rcvd A count of the number of network packets received by the adapter.
30 CN Rx Underflows A count of the number of network receive underflow errors.
31 CN Rx Overflows A count of the number of network receive overflow errors.
32 CN Rx Bad Frames A count of the number of network receive bad frame errors.
33 CN Packets Sent A count of the number of network packets transmitted by the adapter.
34 CN Tx Underflows A count of the number of network transmit underflow errors.
35 CN Tx Overflows A count of the number of network transmit overflow errors.
36 CN Tx Out Of Steps A count of the number of network transmit out of step errors.
37 CN Tx Blockages A count of the number of network transmit blockage errors.
Troubleshooting
8-7
Viewing and Clearing Events
The adapter maintains an event queue that reports the history of its actions. You can view the event queue using a PowerFlex 4-Class HIM,
DriveExplorer (version 3.01 or higher), or DriveExecutive (version 3.01 or higher).
Figure 8.2 DriveExplorer Event View/Clear Screen
Events
Many events in the event queue occur under normal operation. If you encounter unexpected communications problems, the events may help you or Allen-Bradley personnel troubleshoot the problem. The following events may appear in the event queue:
Code Event Description
0
1
2
3
Adapter Events
No Event
Normal Startup
Manual Reset
Text displayed in an empty event queue entry.
Power is applied to the adapter.
The adapter was reset from the “Reset Module” parameter.
Watchdog T/O Flt The software watchdog detected a failure and reset the adapter.
App Updated The application firmware has been flash updated.
10
11
12
13
14
4
5
6
Boot Updated The boot firmware has been flash updated.
EEPROM Sum Flt The EEPROM checksum/CRC is incorrect. The functionality of the adapter will be limited. Default parameter values must be loaded to clear the condition.
7 – 9 Reserved
Slave Detected
Slave Removed
Slave Logon
Slave Timeout
Slave Brand Flt
—
DSI Events
The adapter detected that the slave has been connected.
The adapter detected that the slave has been disconnected.
The adapter has established communications with the slave.
The adapter has lost communications with the slave.
The slave brand is different than the adapter.
8-8
Troubleshooting
49
50
51
52
53
54
24
25
26
27
20
21
22
23
Code Event
15 Host 0 Logon
16
17
18
19
Host 1 Logon
Host 2 Logon
Host 3 Logon
Host 4 Logon
Host 0 Timeout
Host 1 Timeout
Host 2 Timeout
Host 3 Timeout
Description
The adapter has established communications with Drive 0.
The adapter has established communications with Drive 1.
The adapter has established communications with Drive 2.
The adapter has established communications with Drive 3.
The adapter has established communications with Drive 4.
The adapter has lost communications with Drive 0.
The adapter has lost communications with Drive 1.
The adapter has lost communications with Drive 2.
The adapter has lost communications with Drive 3.
Host 4 Timeout The adapter has lost communications with Drive 4.
Host 0 Brand Flt Drive 0 is not an Allen-Bradley brand drive.
Host 1 Brand Flt Drive 1 is not an Allen-Bradley brand drive.
Host 2 Brand Flt Drive 2 is not an Allen-Bradley brand drive.
48
47
46
44
45
43
28
29
Host 3 Brand Flt
Host 4 Brand Flt
30 – 39 Reserved
Drive 3 is not an Allen-Bradley brand drive.
Drive 4 is not an Allen-Bradley brand drive.
—
Network Events
40
41
42
CN Link Up
CN Link Down
Dup CN Addr
The network link is established.
The network link is lost.
The adapter detected that another device is using its network address. In this case, the adapter will not participate in any network activity.
An I/O connection from the network to the adapter was opened.
CN Open
CN Close
CN Timeout
CN Comm Flt
An I/O connection from the network to the adapter was closed.
An I/O connection from the network to the adapter has timed out.
The adapter has performed the “Comm Flt” action specified by the user.
The adapter has performed the “Idle Flt” action specified by the user.
CN Idle Flt
PCCC IO Open
PCCC IO Close
The adapter has begun receiving PCCC Control messages
(the PCCC Control Timeout was previously set to a non-zero value).
The device sending PCCC Control messages to the adapter
PCCC IO Time Flt The adapter has not received a PCCC Control message for has set the PCCC Control Timeout to a value of zero.
longer than the PCCC Control Timeout.
CN Sent Reset The adapter received a reset from the network.
Msg Ctrl Open
Msg Ctrl Close
The adapter has begun receiving Client-Server Control messages (the Client-Server Control Timeout was previously set to a non-zero value).
The device sending Client-Server Control messages to the adapter has set the Client-Server Control Timeout to a value of zero.
Msg Ctrl Timeout The adapter has not received a Client-Server Control message for longer than the established timeout period.
Specifications
Appendix A presents the specifications for the adapter.
Topic
Page
Communications
Network
Protocol
Data Rate
Media
ControlNet
5M baud
Coax with BNC connector
Drive
Protocol
Data Rate
DSI
19.2 kbps
Appendix
A
Electrical
Consumption
Drive
Network
275 mA at 5 VDC, supplied through the drive or DSI
External Comms Kit
None
Mechanical
Dimensions
Height
Length
Weight
Width
19 mm (0.75 inches)
86 mm (3.39 inches)
78.5 mm (3.09 inches)
85g (3 oz.)
A-2
Specifications
Environmental
Temperature
Operating
Storage
-10 to 50°C (14 to 122°F)
-40 to 85°C (-40 to 185°F)
Relative Humidity 5 to 95% non-condensing
Atmosphere Important: Adapter must not be installed in an area where the ambient atmosphere contains volatile or corrosive gas, vapors or dust. If the adapter is not going to be installed for a period of time, it must be stored in an area where it will not be exposed to a corrosive atmosphere.
Regulatory Compliance
Certification
UL cUL
CE
CTick
Specification
UL508C
CAN / CSA C22.2 No. 14-M91
EN50178 and EN61800-3
AS / NZS 2064, Group 1, Class A
NOTE: This is a product of category C3 according to IEC 61800-3. This product is not intended for use in a domestic environment.
Appendix
B
Adapter Parameters
Appendix B provides information about the ControlNet adapter parameters.
Topic
Page
About Parameter Numbers
The parameters in the adapter are numbered consecutively. However, depending on which configuration tool you use, they may have different numbers.
Configuration Tool
• DriveExplorer
• DriveExecutive
• HIM
• Explicit Messaging
• RSNetWorx for ControlNet
Numbering Scheme
The adapter parameters begin with parameter 1. For example, Parameter 01 - [Mode] is parameter 1 as indicated by this manual.
Refer to Chapter 6 , Using Explicit Messaging , and
Appendix C , ControlNet Objects for details.
Parameter List
No. Name and Description
Parameter
01
[Mode]
Displays the Single or Multi-Drive operating mode selected with the Operating Mode Jumper (J7) on the adapter.
02
[CN Addr Cfg]
Sets the ControlNet node address if the Node
Address Switches are set to “00.” (Updates
Parameter 03 - [CN Addr Act] after a reset.)
03
[CN Addr Act]
used by the adapter.
Displays the ControlNet node address actually
Details
Default:
Values:
Type:
0 = Single Drv
0 = Single Drv
1 = Multiple Drv
Read Only
Default:
Minimum:
Maximum:
2
1
99
Type: Read/Write
Reset Required: Yes
Default:
Minimum:
Maximum:
Type:
2
1
99
Read Only
B-2
Adapter Parameters
Parameter
No. Name and Description
04
[CN Rate Cfg]
Sets the ControlNet data rate (megabits per second) at which the adapter communicates.
(Updates Parameter 05 - [CN Rate Act] after a reset.)
05
[CN Rate Act]
Displays the ControlNet data rate (megabits per second) actually used by the adapter.
Details
Default:
Values:
0 = 5 Mbps
0 = 5 Mbps
Type: Read/Write
Reset Required: Yes
Default:
Values:
Type:
0 = 5 Mbps
0 = 5 Mbps
Read Only
06
[CN Active Cfg]
Displays the source from which the adapter node address is taken. This will either be switches or
Parameter 02 - [CN Addr Cfg] in EEPROM. It is determined by the settings of the Node Address
Switches on the adapter. If the Node Address
Switches = “00” on power up, then Parameter 02 -
[CN Addr Cfg] is used to configure the adapter’s
ControlNet address.
Default:
Values:
Type:
0 = Switches
0 = Switches
1 = EEPROM
Read Only
Default:
Values
0 = Ready
0 = Ready
07
[Reset Module]
No action if set to “Ready.” Resets the adapter if
!
set to “Reset Module.” Restores the adapter to its factory default settings if set to “Set Defaults.” This parameter is a command. It will be reset to “0 =
Ready” after the command has been performed.
Type:
1 = Reset Module
2 = Set Defaults
Read/Write
Reset Required: No
ATTENTION: Risk of injury or equipment damage exists. If the adapter is transmitting I/O that controls the drive, the drive may fault when you reset the adapter. Determine how your drive will respond before resetting a connected adapter.
08
[Comm Flt Action]
Sets the action that the adapter and drive will take if the adapter detects that network communications have been disrupted. This setting is effective only if I/O that controls the drive is transmitted through the adapter.
!
Default:
Values:
0 = Fault
0 = Fault
1 = Stop
2 = Zero Data
3 = Hold Last
4 = Send Flt Cfg
Read/Write Type:
Reset Required: No
ATTENTION: Risk of injury or equipment damage exists. Parameter 08 - [Comm
Flt Action] lets you determine the action of the adapter and connected drive if communications are disrupted. By default, this parameter faults the drive. You can set this parameter so that the drive continues to run. Precautions should be taken to ensure that the setting of this parameter does not create a risk of injury or equipment damage. When commissioning the drive, verify that your system responds correctly to various situations (for example, a disconnected drive).
Adapter Parameters
Parameter
No. Name and Description
09
[Idle Flt Action]
Sets the action that the adapter and drive will take if the adapter detects that the controller is in program mode. This setting is effective only if I/O that controls the drive is transmitted through the adapter.
Details
Default:
Values:
0 = Fault
0 = Fault
1 = Stop
2 = Zero Data
3 = Hold Last
4 = Send Flt Cfg
Type: Read/Write
Reset Required: No
!
ATTENTION: Risk of injury or equipment damage exists. Parameter 09 - [Idle
Flt Action] lets you determine the action of the adapter and connected drive when the controller is in program mode. By default, this parameter faults the drive. You can set this parameter so that the drive continues to run. Precautions should be taken to ensure that the setting of this parameter does not create a risk of injury or equipment damage. When commissioning the drive, verify that your system responds correctly to various situations (for example, a disconnected drive).
10
[Flt Cfg Logic]
Sets the Logic Command data that is sent to the drive if any of the following is true:
• Parameter 08 - [Comm Flt Action] is set to
“Send Flt Cfg” and communications are disrupted.
• Parameter 09 - [Idle Flt Action] is set to “Send
Flt Cfg” and the controller is in program mode.
Default:
Minimum:
Maximum:
Type:
0000 0000 0000 0000
0000 0000 0000 0000
1111 1111 1111 1111
Read/Write
Reset Required: No
The bit definitions will depend on the product to which the adapter is connected. See
or the documentation for the drive being used.
11
[Flt Cfg Ref]
Sets the Reference data that is sent to the drive if any of the following is true:
• Parameter 08 - [Comm Flt Action] is set to
“Send Flt Cfg” and communications are disrupted.
• Parameter 09 - [Idle Flt Action] is set to “Send
Flt Cfg” and the controller is in program mode.
12
[DSI I/O Cfg]
Sets the configuration of the drives that are active in the Multi-Drive mode. Identifies the DSI connections that would be attempted on a reset or power cycle.
Default:
Minimum:
Maximum:
Type:
0
0
65535
Read/Write
Reset Required: No
Default:
Values:
0
0 = Drive 0
1 = Drives 0-1
2 = Drives 0-2
3 = Drives 0-3
4 = Drives 0-4
Type: Read/Write
Reset Required: Yes
B-3
B-4
Adapter Parameters
Parameter
No. Name and Description
13
[DSI I/O Act]
Displays the drives that are active in the
Multi-Drive mode.
Details
Default:
Bit Values:
Type: xxx0 0000
0 = Drive Active
1 = Drive Inactive
Read Only
Bit
Definition
Default x x x 0 0 0 0 0
Bit 7 6 5 4 3 2 1 0
14
15
16
17
18
[Drv 0 Addr]
[Drv 1 Addr]
[Drv 2 Addr]
[Drv 3 Addr]
[Drv 4 Addr]
Sets the corresponding node addresses of the daisy-chained drives when the Operating Mode
Jumper (J7) on the adapter is set for Multi-Drive operation.
Important: The settings for these parameters must match the Comm Node Addr parameter settings in the respective drives. Each setting must also be unique (no duplicate node addresses).
See Configuring the RS-485 Network on page 7-7
for a list of other parameters that must be set correctly in each daisy-chained drive.
Default:
Default:
Default:
Default:
100
101
102
103
Default:
Minimum:
Maximum:
Type:
104
1
247
Read/Write
Reset Required: Yes
19
[Ref Adjust]
Sets the percent scale factor for the Reference from the network.
!
Default:
Minimum:
Maximum:
Type:
100.00
0.00
200.00
Read/Write
Reset Required: No
ATTENTION: To guard against equipment damage and/or personal injury, note that changes to Parameter 19 - [Ref Adjust] take effect immediately. A drive receiving its Reference from the adapter will receive the newly scaled Reference, resulting in a change of speed.
Appendix
C
ControlNet Objects
Appendix C provides information about the ControlNet objects that can be accessed using Explicit Messages.
For information on the format of
Explicit Messages and example ladder logic programs, refer to
Chapter 6 , Using Explicit Messaging .
Object
Class Code
Hex.
Dec.
0x01 1
0x04 4
0x07 7
Page
Object
Class Code
Hex.
Dec.
0x67 103
Page
0x92 146
0x93 147
0x0F 15
0x97 151
0x10 16
0x99 153
TIP: Refer to the ControlNet specification for more information about
ControlNet objects. Information about the ControlNet specification is available on the ControlNet web site ( http://www.controlnet.org
).
Supported Data Types
Data Type
BYTE
WORD
DWORD
SINT
USINT
INT
UINT
LWORD
DINT
UDINT
BOOL
BOOL[n]
STRING[n]
Description
8-bit unsigned integer
16-bit unsigned integer
32-bit unsigned integer
64-bit unsigned integer
8-bit signed integer
8-bit unsigned integer
16-bit signed integer
16-bit unsigned integer
32-bit signed integer
32-bit unsigned integer
8-bit value -- low bit is true or false
Array of n bits
Array of n characters
SHORT_STRING 1-byte length indicator + that many characters
STRUCT Structure name only - no size in addition to elements
CONTAINER 32-bit parameter value - sign extended if necessary
8 or 16-bit character
32-bit floating point REAL
TCHAR
C-2
ControlNet Objects
Identity Object
Class Code
Hexadecimal
0x01
Decimal
1
Services
Service Code Implemented for:
0x01
Class
Yes
Instance
Yes
0x05
0x0E
No
Yes
Yes
Yes
Service Name
Get_Attributes_All
Reset
Get_Attribute_Single
1
2
3
0
Instances – Single Mode
The number of instances is fixed at three and is shown below:
Instance Description
Class
Host drive
22-COMM-C
22-SCM-232 or 22-HIM-* (when present)
Instances – Multi-Drive Mode
0
1
The number of instances is fixed at one and is shown below:
Instance Description
Class
22-COMM-C
ControlNet Objects
C-3
Identity Object
(Continued)
Class Attributes
1
2
6
Attribute
ID
Access
Rule
Get
Get
Get
7 Get
Name
Revision
Max Instance
Max ID Number of Class
Attributes
Max ID Number of Instance
Attributes
Data Type Description
UINT
UINT
UINT
1
Total number of instances
7
UINT 100
1
2
3
4
5
6
7
9
100
Instance Attributes
Attribute
ID
Access
Rule Name
Get
Get
Get
Get
Get
Get
Get
Get
Get
Vendor ID
Data Type
UINT
Device Type UINT
Product Code UINT
Description
1 = Allen-Bradley
136
Number identifying product name and rating
Revision:
Major
Minor
Status
STRUCT of:
USINT
USINT
WORD
Value varies
Value varies
Bit 0 = Owned
Bit 2 = Configured
Bit 10 = Recoverable fault
Bit 11 = Unrecoverable fault
Serial Number UDINT Unique 32-bit number
Product Name SHORT_STRING Product name and rating
Configuration
Consistency
Value
NVS Info
UINT CRC representing the configuration of the product
STRUCT of:
UDINT
SHORT_STRING
First NVS instance
Sub-assembly name
C-4
ControlNet Objects
Assembly Object
Class Code
Hexadecimal
0x04
Decimal
4
Services
Service Code
0x0E
0x10
Implemented for:
Class
Yes
Yes
Instance
Yes
Yes
Service Name
Get_Attribute_Single
Set_Attribute_Single
1
2
Instances
Instance Description
All I/O data being read from the DSI drives (read-only)
All I/O data written to the DSI drives (read/write)
Class Attributes
1
2
Attribute
ID
100
Access Rule
Get
Get
Set
Name Data Type Description
Revision UINT
Max Instance UINT
Control
Timeout
UINT
2
2
Control timeout in seconds
ControlNet Objects
C-5
Assembly Object
(Continued)
Instance Attributes
3
4
Attribute
ID
1
2
Access Rule
Get
Get
Name
Number of
Members
Data Type Description
UINT
Member List ARRAY of
STRUCT:
UINT
UINT
Packed
EPATH
1
Size of member data
Size of member path
Member path
Conditional
(1)
Get
Data
Size
Array of Bits Data to be transferred
UINT Size of assembly data in bits
(1)
For instance 1, access rule for the data attribute is Get. For instance 2, it is Get/Set.
Important: Setting an Assembly object attribute can be done only when the Control Timeout (class attribute 100) has been set to a non-zero value.
C-6
ControlNet Objects
Register Object
Class Code
Hexadecimal
0x07
Decimal
7
Services
Service Code
0x0E
0x10
Implemented for:
Class
Yes
Yes
Instance
Yes
Yes
Service Name
Get_Attribute_Single
Set_Attribute_Single
15
16
17
18
11
12
13
14
19
20
7
8
9
10
5
6
3
4
1
2
Instances
Instance Description
Logic Command and Reference for all drives
Logic Status and Feedback for all drives
Logic Command and Reference for Drive 0
Logic Status and Feedback for Drive 0
Logic Command and Reference for Drive 1
Logic Status and Feedback for Drive 1
Logic Command and Reference for Drive 2
Logic Status and Feedback for Drive 2
Logic Command and Reference for Drive 3
Logic Status and Feedback for Drive 3
Logic Command and Reference for Drive 4
Logic Status and Feedback for Drive 4
Logic Command for all drives — mask-and-match register
(2)
Logic Command for Drive 0 — mask-and-match register
Logic Command for Drive 1 — mask-and-match register
Logic Command for Drive 2 — mask-and-match register
Logic Command for Drive 3 — mask-and-match register
Logic Command for Drive 4 — mask-and-match register
Logic Command for Drive 0
Logic Status for Drive 0
(1)
The size for this Register Object instance is 32 bits per drive. For example, if the adapter is operating in
Multi-Drive mode, and is configured with Drives 0 through 4, then the size is 160 bits.
(2)
The structure for this Register Object instance is a Mask word followed by a Command word for each drive.
The Logic Command for each drive is set to the value of the second word of the data where there are ones in the first word of the data.
Logic Command = (Logic Command and not Mask word) or (Command word and Mask word)
Out
Out
Out
Out
Out
In
Out
In
Out
Out
Out
In
Out
In
Out
In
Out
In
Input/
Output
Out
In
32
32
32
32
16
16
32
32
32
32
Size
(in bits)
Varies
(1)
Varies
32
32
32
32
32
32
Varies
32
ControlNet Objects
C-7
Register Object
(Continued)
Instances (Continued)
Instance Description
32
33
34
35
28
29
30
31
36
37
38
24
25
26
27
21
22
23
Reference for Drive 0
Feedback for Drive 0
Logic Command for Drive 1
Logic Status for Drive 1
Reference for Drive 1
Feedback for Drive 1
Logic Command for Drive 2
Logic Status for Drive 2
Reference for Drive 2
Feedback for Drive 2
Logic Command for Drive 3
Logic Status for Drive 3
Reference for Drive 3
Feedback for Drive 3
Logic Command for Drive 4
Logic Status for Drive 4
Reference for Drive 4
Feedback for Drive 4
16
16
16
16
16
16
16
16
16
16
16
16
16
16
16
16
16
Size
(in bits)
16
In
Out
In
Out
In
Out
In
Out
In
Out
In
Out
In
Input/
Output
Out
In
Out
In
Out
Class Attributes
1
2
3
100
Attribute
ID
Get
Get
Get
Set
Access
Rule Name
Revision
Max Instance
Data Type
UINT
UINT
Number of Instances UINT
Control Timeout UINT
Description
1
38
38
Control timeout in seconds
C-8
ControlNet Objects
Register Object
(Continued)
Instance Attributes
2
3
4
Attribute
ID Access Rule Name
1 Get Bad Flag
Get Direction
Get
Conditional
(1)
Size
Data
Data Type Description
BOOL
BOOL
UINT
If set to 1, then attribute 4 contains invalid, bad or otherwise corrupt data.
0 = good
1 = bad
Direction of data transfer
0 = Input (drive to network)
1 = Output (network to drive)
Size of register data in bits
ARRAY of
BITS
Data to be transferred
(1)
The access rule of Set is optional if attribute 2, Direction = 1. If Direction = 0, the access rule is Get.
Important: Setting a Register Object attribute can be done only when the Control Timeout (class attribute 100) has been set to a non-zero value.
ControlNet Objects
C-9
Parameter Object
Class Code
Hexadecimal
0x0F
Decimal
15
Services
Service Code
0x01
0x05
0x0E
Implemented for:
Class
Yes
Yes
Yes
Instance
Yes
No
Yes
0x10 No Yes
Yes 0x4B No
Instances – Single Mode
The number of instances is shown below:
Instance
0
Description
Class
1
" n
Drive Parameter 1
"
Drive Parameter n
(1) n + 1 Adapter Parameter 1
" "
(1)
(2) n + m Adapter Parameter m
(2) n represents the number of parameters in the drive.
m represents the number of parameters in the adapter.
Service Name
Get_Attribute_All
Reset
Get_Attribute_Single
Set_Attribute_Single
Get_Enum_String
C-10
ControlNet Objects
Parameter Object
(Continued)
Instances – Multi-Drive Mode
The number of instances is shown below:
1
" m
Instance
0
Description
Class
Adapter Parameter 1
"
Adapter Parameter m
(1)
(1) m represents the number of parameters in the adapter.
In addition, the parameters for the DSI drives can be accessed using the instance-offset encoding shown in the table below:
Instances (Dec.) Single Mode
17408 – 18431 Instances 0 – 1023 in the drive
Multi-Drive Mode
16384 – 17407 Instances 0 – 1023 in the adapter Instances 0 – 1023 in the adapter
Instances 0 – 1023 in Drive 0
18432 – 19455 Not supported
19456 – 20479 Not supported
Instances 0 – 1023 in Drive 1
Instances 0 – 1023 in Drive 2
20480 – 21503 Not supported Instances 0 – 1023 in Drive 3
21504 – 22527 Not supported Instances 0 – 1023 in Drive 4
Class Attributes
1
2
8
Attribute
ID
9
10
Access
Rule
Get
Get
Get
Get
Get
Name
Revision UINT
Max Instance UINT
Parameter
Class
Descriptor
Configuration
Assembly
Instance
Native
Language
Data Type Description
WORD
UINT
USINT
1
Number of parameters
0 = False, 1 = True
Bit 0 = Supports parameter instances
Bit 1 = Supports full attributes
Bit 2 = Must do NVS save command
Bit 3 = Parameters are stored in NVS
0
0 = English
1 = French
2 = Spanish
3 = Italian
4 = German
5 = Japanese
6 = Portuguese
7 = Mandarin Chinese
8 = Russian
9 = Dutch
ControlNet Objects
C-11
Parameter Object
(Continued)
Instance Attributes
3
4
5
6
7
8
9
10
11
Attribute
ID
1
Access
Rule Name
(1)
Parameter Value
2 Get Link Path Size
12
13
14
15
16
17
18
19
20
21
Get
Get
Get
Get
Get
Get
Get
Get
Get
Get
Get
Get
Get
Get
Get
Get
Get
Get
Get
Data Type
(2)
Description
(3)
USINT 0 = No link specified n = The size of Attribute 3 in bytes
(4)
Link Path
Descriptor WORD 0 = False, 1 = True
Bit 1 = Supports ENUMs
Bit 2 = Supports scaling
Bit 3 = Supports scaling links
Bit 4 = Read only
Bit 5 = Monitor
Bit 6 = Extended precision scaling
Data Type USINT 0xC2 = SINT (8-bits)
0xC3 = INT (16-bits)
0xC4 = DINT (32-bits)
0xC6 = USINT (8-bits)
0xC7 = UINT (16-bits)
0xCA = REAL (32-bits)
0xD2 = WORD (16-bits)
(3)
Data Size
Parameter Name
String
Scaling Divisor
SHORT_STRING
UINT
(3)
Units String
Help String
SHORT_STRING
(3)
SHORT_STRING Null string
(3)
Minimum Value
Maximum Value
Default Value
Scaling Multiplier UINT
(3)
(3)
(3)
(3)
Scaling Base UINT
(3)
Scaling Offset
USINT
UINT
(3)
Multiplier Link UINT
(3)
Divisor Link UINT
(3)
Base Link UINT
(3)
Offset Link UINT
(3)
Decimal Precision USINT
(3)
(1)
Access rule is defined in bit 4 of instance attribute 4. 0 = Get/Set, 1 = Get.
(2)
Specified in descriptor, data type, and data size.
(3)
Value varies based on parameter instance.
(4)
Refer to the ControlNet specification for a description of the link path.
C-12
ControlNet Objects
Parameter Group Object (Single Mode only)
Class Code
Hexadecimal
0x10
Decimal
16
Services
Service Code
0x0E
0x01
Implemented for:
Class
Yes
Yes
Instance
Yes
Yes
Service Name
Get_Attribute_Single
Get_Attributes_All
Instances
1
0
The number of instances depends on the number of groups in the device.
A group of adapter parameters is appended to the list of groups in the device. The total number of groups can be read in Instance 0, Attribute 2.
Number Description
Class Attributes
Drive Group 1 Attributes n n + 1
Drive Group n Attributes
(1)
Adapter Group Attributes
(1) n represents the number of parameter groups in the drive.
2
8
1
Class Attributes
Attribute
ID
Access
Rule
Get
Name
Parameter
Group Version
Get
Set
Data
Type
UINT
Description
1
Max Instance UINT
Native
Language
USINT
Total number of groups
0 = English
1 = French
2 = Spanish (Mexican)
3 = Italian
4 = German
5 = Japanese
6 = Portuguese
7 = Mandarin Chinese
8 = Russian
9 = Dutch
ControlNet Objects
C-13
Parameter Group Object (Single Mode only)
(Continued)
Instance Attributes
Attribute
ID
1
2
3
4
Access
Rule
Get
Get
Get
Get
Name
Group Name String
Data Type Description
SHORT_
STRING
Group name
Number of Members in Group
1st Parameter Number in Group
UINT
UINT
Number of parameters in group.
(1)
2nd Parameter
Number in Group
UINT
(1)
UINT
(1) n
(1)
Get n Parameter
Number in Group
Value varies based on group instance.
C-14
ControlNet Objects
PCCC Object
Class Code
Hexadecimal
0x67
Decimal
103
Services
Service Code
0x4B
0x4C
Implemented for:
Class
No
No
Instance
Yes
Yes
Service Name
Execute_PCCC
Execute_DH+
Instances
Supports Instance 1.
Class Attributes
Not supported.
Instance Attributes
Not supported.
Name
Message Structure for Execute_PCCC
Request
Data
Type Description
Response
Name
Data
Type
Length USINT Length USINT Length of requestor ID
Vendor UINT Vendor number of requestor
Vendor UINT
Serial
Number
UDINT ASA serial number of requestor
Other Product
Specific
Identifier of user, task, etc. on the requestor
CMD USINT Command byte
Serial
Number
Other
CMD
UDINT
Product
Specific
USINT
(Message structure continued on next page.)
Description
Length of requestor ID
Vendor number of requestor
ASA serial number of requestor
Identifier of user, task, etc. on the requestor
Command byte
ControlNet Objects
C-15
PCCC Object
(Continued)
Message Structure for Execute_PCCC (Continued)
Request
Name
STS
Data
Type
TNSW UINT
Description
USINT 0
Transport word
FNC USINT Function code. Not used for all CMD’s.
PCCC_ params
ARRAY of
USINT
CMD/FNC specific parameters
Response
Name
STS
TNSW
Data
Type
USINT
UINT
EXT_STS USINT
PCCC_ results
ARRAY of
USINT
Description
Status byte
Transport word.
Same value as the request.
Extended status.
Not used for all
CMD’s.
CMD/FNC specific result data
FNC
Name
Message Structure for Execute_DH+
Request
Data
Response
Type Description Name
Data
Type
DLink
DSta
DLink
DSta
UINT
USINT
Destination Link ID
Destination Station number
DUser USINT Destination “User” number
SLink UINT Source Link ID
SSta USINT Source Station number
DUser
SLink
SSta
UINT
USINT
USINT
UINT
USINT
STS
SUser USINT Source User
CMD number
USINT Command byte
USINT
TNSW UINT
0
Transport word
SUser
CMD
STS
TNSW
USINT
USINT
USINT
UINT
EXT_STS USINT
PCCC_ results
ARRAY of
USINT
Description
Destination Link ID
Destination Station number
Destination “User” number
Source Link ID
Source Station number
Source User number
Command byte
Status byte
Transport word.
Same value as the request.
Extended Status; not used for all
CMD’s
CMD/FNC specific result data
PCCC_ params
USINT Function code; not used for all CMD’s
ARRAY of
USINT
CMD/FNC specific parameters
C-16
ControlNet Objects
PCCC Object
(Continued)
The adapter supports the following PCCC command types:
CMD
0x06
0x0F
0x0F
0x0F
0x0F
0x0F
0x0F
0x0F
0x0F
0x0F
FNC Description
0x03 Identify host and some status
0x67 PLC-5 typed write
0x68 PLC-5 typed read
0x95 Encapsulate other protocol
0xA2 SLC 500 protected typed read with 3 address fields
0xAA SLC 500 protected typed write with 3 address fields
0xA1 SLC 500 protected typed read with 2 address fields
0xA9 SLC 500 protected typed write with 2 address fields
0x00 Word range read
0x01 Word range write
N40
See DF1 Protocol and Command Set Manual, Allen-Bradley Publication
N-File
No. 1770-6.5.16
.
N-Files
Description
This N-file lets you use Emulated Block Transfer to send many types of messages. To use Emulated Block Transfer messages, you send a Write message to N40:0 – N40:63, wait until the adapter responds with a reply message, and then read the response data in N40:0 – N40:63 with a Read message.
For details about Block Transfer messages and the data required for each byte in the N-File, refer to the Remote I/O Adapter User Manual, Publication
20COMM-UM004….
N40:4
N40:5
N40:6
N40:3
N40:1
N40:2
N40:0
Bits 15
Bits 15 to 8 are the Most Significant Byte. Bits 7 to 0 are the Least Significant
Byte.
Write
Read
0 15 0
Length (in Bytes) 0x00 Length (in Bytes) 0x00
DSI Port
(1)
0x00
0x81
CIP Service
Status Size Status Type
Data
(length varies based on message)
CIP Class
CIP Instance
CIP Attribute
Data
(length varies based on message)
(1)
N40:63
Use the following DSI Port Assignment table to determine the value for the DSI port.
ControlNet Objects
C-17
PCCC Object
(Continued)
N42:8
N42:7
N41:0
N41:1
N42
N42:3
N41:2
N-Files (Continued)
DSI Port Assignments
3
4
5
1
2
DSI Port No. Single Mode
0 The drive
The adapter
The slave
Not supported
Not supported
Not supported
N41
N-File
Multi-Drive Mode
Drive 0
Drive 1
Drive 2
Drive 3
Drive 4
The adapter
Description
For Single Mode Only
This N-file lets you read and write control I/O messages. You can write control I/O messages only when all of the following conditions are true:
• The adapter is not receiving I/O from a scanner. For example, there is no scanner on the network, the scanner is in idle (program) mode, the scanner is faulted, or the adapter is not mapped to the scanner.
• The value of N42:3 is set to a non-zero value.
Write
Read
Logic Command Word
Unused
Reference
Logic Status Word
Unused
Feedback
This N-file lets you read and write some values configuring the port.
Control Time-out (read/write): Time (in seconds) allowed between messages to the N41 or N44 file. If the adapter does not receive a message in the specified time, it performs the fault action configured in its
[Comm Flt Action] parameter.
Adapter Port Number (read only): DSI port on the drive to which the adapter is connected.
Peer Adapters (read only): Bit field of devices having Peer capabilities.
C-18
ControlNet Objects
PCCC Object
(Continued)
N44:0
N44:2
N44:3
N44:4
N44:5
N44:1
N44:6
N44:7
N44:8
N44:9
N44:10
N-Files (Continued)
N-File Description
N44
For Multi-Drive Mode Only
This N-file lets you read and write control I/O messages. You can write control I/O messages only when all of the following conditions are true:
• The adapter is not receiving I/O from a scanner. For example, there is no scanner on the network, the scanner is in idle (program) mode, the scanner is faulted, or the adapter is not mapped to the scanner.
• The value of N42:3 is set to a non-zero value.
Write
Drive 0 Logic Command
Unused
Drive 0 Reference
Drive 1 Logic Command
Drive 1 Reference
Drive 2 Logic Command
Drive 2 Reference
Drive 3 Logic Command
Drive 3 Reference
Drive 4 Logic Command
Drive 4 Reference
Read
Drive 0 Logic Status
Unused
Drive 0 Feedback
Drive 1 Logic Status
Drive 1 Feedback
Drive 2 Logic Status
Drive 2 Feedback
Drive 3 Logic Status
Drive 3 Feedback
Drive 4 Logic Status
Drive 4 Feedback
ControlNet Objects
C-19
PCCC Object
(Continued)
N-Files (Continued)
Important: If your controller or HMI platform supports CIP messaging, use the CIP Parameter object to get and set parameters.
N-File Description
N10 – N18 These N-files let you read and write parameter values in the drive and the adapter.
N10:0
N10:1 – 999
Single Mode
Number of parameters in the drive
Drive parameters 1 – 999
N11:0 – 999 Drive parameters 1000 – 1999
N12:0 – 999 Drive parameters 2000 – 2999
Multi-Drive Mode
Number of parameters in Drive 0
Drive 0 parameters 1 - 999
Drive 0 parameters 1000 - 1999
Drive 0 parameters 2000 - 2999
N14:0
Number of parameters in this adapter
Number of parameters in this
Number of parameters in this adapter
N13:0
N13:1 – 999 Parameters 1 – 999 in this adapter Parameters 1 – 999 in this adapter adapter
Number of parameters in Drive 1
N14:1 – 999 Parameters 1 – 999 in this adapter Drive 1 parameters 1 – 999
N15:0 Number of parameters in the slave Number of parameters in Drive 2
N15:1 – 999 Parameters 1 – 999 in the slave Drive 2 parameters 1 – 999
N16:0 Not supported
N16:1 – 999 Not supported
Number of parameters in Drive 3
Drive 3 parameters 1 – 999
N17:0 Not supported
N17:1 – 999 Not supported
N18:0 Not supported
Number of parameters in Drive 4
Drive 4 parameters 1 – 999
Number of parameters in this adapter
Parameters 1 – 999 in this adapter N18:1 – 999 Not supported
C-20
ControlNet Objects
DSI Device Object
Class Code
Hexadecimal
0x92
Decimal
146
Services
Service Code
0x0E
0x10
Implemented for:
Class
Yes
Yes
Instance
Yes
Yes
Service Name
Get_Attribute_Single
Set_Attribute_Single
Instances
The number of instances depends on the number of components in the device. The total number of components can be read in Instance 0, Class
Attribute 4.
Instances (Dec.) Single Mode
0 – 16383 Instances 0 – 16383 in the drive
Multi-Drive Mode
Instances 0 – 16383 in Drive 0
16384 – 17407 Instances 0 – 1023 in the adapter Instances 0 – 1023 in the adapter
17408 – 18431 Instances 0 – 1023 in the adapter Instances 0 – 1023 in Drive 1
18432 – 19455 Instances 0 – 1023 in the slave
19456 – 20479 Not supported
Instances 0 – 1023 in Drive 2
Instances 0 – 1023 in Drive 3
Instances 0 – 1023 in Drive 4
Instances 0 – 1023 in the adapter
1
2
0
20480 – 21503 Not supported
ID
Attribute
21504 – 22527 Not supported
Class Attributes
Access
Rule Name
Get Family Code
Get
Set
Data Type
BYTE
Description
Code identifying the device.
Family Text STRING[16] Text identifying the device.
Language Code BYTE 0 = English
1 = French
2 = Spanish
3 = Italian
4 = German
5 = Japanese
6 = Portuguese
7 = Mandarin Chinese
8 = Russian
9 = Dutch
ControlNet Objects
C-21
DSI Device Object
(Continued)
Class Attributes (Continued)
18
15
16
17
12
13
6
7
Attribute
ID
3
4
5
Access
Rule
Get
Get
Set
Get
Name
Product Series
Number of
Components
User Definable
Text
Status Text
Data Type
BYTE
Description
1 = A
2 = B …
BYTE Number of components (e.g., main control board, I/O boards) in the device.
STRING[16] Text identifying the device with a user-supplied name
STRING[12] Text describing the status of the device.
Get
8 Get
Configuration
Code
BYTE Identification of variations.
Configuration Text STRING[16] Text identifying a variation of a family device.
9
11 Get
Get
Get
Get Brand Code WORD
NVS Checksum WORD
Class Revision WORD
Character Set
Code
BYTE
0x0001 = Allen-Bradley
Checksum of the Non-Volatile Storage in the device.
2
0 = SCANport HIM
1 = ISO 8859-1 (Latin 1)
2 = ISO 8859-2 (Latin 2)
3 = ISO 8859-3 (Latin 3)
4 = ISO 8859-4 (Latin 4)
5 = ISO 8859-5 (Cyrillic)
6 = ISO 8859-6 (Arabic)
7 = ISO 8859-7 (Greek)
8 = ISO 8859-8 (Hebrew)
9 = ISO 8859-9 (Turkish)
10 = ISO 8859-10 (Nordic)
255 = ISO 10646 (Unicode)
Get
Get
Get Languages
Supported
Date of
Manufacture
STRUCT of:
BYTE
BYTE[n]
STRUCT of:
WORD
BYTE
BYTE
Product Revision STRUCT of:
BYTE
BYTE
Number of Languages
Language Codes (See Class Attribute 2)
Year
Month
Day
Major Firmware Release
Minor Firmware Release
Value between 0x00 and 0xFFFFFFFF Get Serial Number DWORD
C-22
ControlNet Objects
DSI Device Object
(Continued)
Instance Attributes
Attribute
ID
Access
Rule
3 Get
Name
Component
Name
4
5
8
Get
Get
Get
Data Type
STRING[32] Name of the component
Component
Firmware
Revision
Component
Hardware
Change Number
STRUCT of:
BYTE
BYTE
BYTE
Component Serial
Number
DWORD
Description
Major Revision
Minor Revision
Value between 0x00 and
0xFFFFFFFF
ControlNet Objects
C-23
DSI Parameter Object
Class Code
Hexadecimal
0x93
Decimal
147
Instances
The number of instances depends on the number of parameters in the device. The total number of parameters can be read in Instance 0,
Attribute 0.
Instances (Dec.) Single Mode Multi-Drive Mode
0 – 16383 Instances 0 – 16383 in the drive Instances 0 – 16383 in Drive 0
16384 – 17407 Instances 0 – 1023 in the adapter Instances 0 – 1023 in the adapter
17408 – 18431 Instances 0 – 1023 in the adapter Instances 0 – 1023 in Drive 1
18432 – 19455 Instances 0 – 1023 in the slave
19456 – 20479 Not supported
Instances 0 – 1023 in Drive 2
Instances 0 – 1023 in Drive 3
20480 – 21503 Not supported
21504 – 22527 Not supported
Instances 0 – 1023 in Drive 4
Instances 0 – 1023 in the adapter
9
7
8
Class Attributes
1
2
3
4
5
Attribute
ID
0
Get
Get
Access
Rule Name
Get
Set
Number of
Instances
Write Protect
Password
Set
Get
NVS Command
Write
NVS Parameter
Value Checksum
NVS Link Value
Checksum
First Accessible
Parameter
Data Type
WORD
WORD
BYTE
WORD
WORD
WORD
Get
Get
Class Revision WORD
First Parameter
Processing Error
WORD
Set Link Command BYTE
Description
Number of parameters in the device
0 = Password disabled n = Password
0 = No Operation
1 = Store values in active memory to NVS
2 = Load values in NVS to active memory
3 = Load default values to active memory
Checksum of all parameter values in a user set in NVS
Checksum of parameter links in a user set in NVS
First parameter available if parameters are protected by passwords. A “0” indicates all parameters are protected.
2
The first parameter that has been written with a value outside of its range. A “0” indicates no errors.
0 = No Operation
1 = Clear All Parameter Links (This does not clear links to function blocks.)
C-24
ControlNet Objects
DSI Parameter Object
(Continued)
Instance Attributes
12
13
14
15
16
8
9
10
11
Attribute
ID
7
Access
Rule Name Data Type
Get Online Read Full STRUCT of:
BOOL[32]
CONTAINER
(1)
CONTAINER
CONTAINER
CONTAINER
WORD
WORD
STRING[4]
UINT
UINT
UINT
Get
Get/Set Parameter Value Various
Descriptor
INT
BYTE[3]
BYTE
STRING[16]
BOOL[32]
Various Get/Set RAM Parameter
Value
Get/Set Link BYTE[3]
Description
Descriptor (Refer to pages
–
Parameter value
Minimum value
Maximum value
Default value
Next parameter
Previous parameter
Units (e.g., Amp, Hz)
Multiplier
(2)
Divisor
Base
Offset
Link (source of the value) (0 = no link)
Always zero (0)
Parameter name
Descriptor (Refer to pages
–
Parameter value in NVS.
(3)
Parameter value in temporary memory.
Link (parameter or function block that is the source of the value) (0 = no link)
ID for help text for this parameter Get
Get
Get
Get
Get
WORD Help Object
Instance
Read Basic STRUCT of:
BOOL[32]
CONTAINER
CONTAINER
CONTAINER
CONTAINER
STRING[16]
STRING[4]
Parameter Name STRING[16]
Parameter Alias STRING[16]
Parameter
Processing Error
BYTE
Descriptor (Refer to pages
–
Parameter value
Minimum value
Maximum value
Default value
Parameter name
Units (e.g., Amp, Hz)
Parameter name
Customer supplied parameter name.
0 = No error
1 = Value is less than the minimum
2 = Value is greater than the maximum
(1)
A CONTAINER is a 32-bit block of data that contains the data type used by a parameter value. If signed, the value is sign extended. Padding is used in the CONTAINER to ensure that it is always 32-bits.
(2)
This value is used in the formulas used to convert the parameter value between display units and internal units.
Refer to Formulas for Converting on page C-26 .
(3)
Do NOT continually write parameter data to NVS. Refer to the attention on
.
ControlNet Objects
C-25
DSI Parameter Object
(Continued)
Descriptor Attributes
1
2
3
4
5
6
7
8
9
10
14
15
16
11
12
13
17
18
19
20
21
Bit
0
Name
Data Type (Bit 1)
Data Type (Bit 2)
Data Type (Bit 3)
Sign Type
Hidden
Not a Link Sink
Not Recallable
ENUM
Writable
Description
Right bit is least significant bit (0).
000 = BYTE used as an array of Boolean
001 = WORD used as an array of Boolean
010 = BYTE (8-bit integer)
011 = WORD (16-bit integer)
100 = DWORD (32-bit integer)
101 = TCHAR (8-bit (not unicode) or 16-bits (unicode))
110 = REAL (32-bit floating point value)
111 = Use bits 16, 17, 18
0 = unsigned
1 = signed
0 = visible
1 = hidden
0 = Parameter can sink a link
1 = Parameter cannot sink a link
0 = Recallable from NVS
1 = Not Recallable from NVS
0 = No ENUM text
1 = ENUM text
0 = Read only
1 = Read/write
0 = Writable when enabled (e.g., drive running)
1 = Not writable when enabled
Not Writable When
Enabled
Instance
Reserved
Not Used
Formula Links
0 = Parameter value is not a Reference to another parameter
1 = Parameter value refers to another parameter
Must be zero
Decimal Place (Bit 0) Number of digits to the right of the decimal point.
Decimal Place (Bit 1)
0000 = 0
1111 = 15
Decimal Place (Bit 2)
Decimal Place (Bit 3)
Extended Right bit is least significant bit (16).
Data Type (Bit 1) 000 = Reserved
Extended
Data Type (Bit 2)
Extended
Data Type (Bit 2)
001 = DWORD used as an array of Boolean
010 = Reserved
011 = Reserved
100 = Reserved
101 = Reserved
110 = Reserved
111 = Reserved
Parameter Exists Reserved
Reserved
Reserved
C-26
ControlNet Objects
DSI Parameter Object
(Continued)
27
28
29
30
31
Descriptor Attributes (Continued)
Bit
22
23
24
25
26
Name
Access Level (Bit 1)
Access Level (Bit 2)
Access Level (Bit 3)
Writable ENUM
Not a Link Source
Description
Reserved
Reserved
Reserved
Reserved
0 = Parameter can be a source for a link
1 = Parameter cannot be a source for a link
Enhanced Bit ENUM Reserved
Enhanced ENUM Reserved
Not Used
Not Used
Not Used
Reserved
Reserved
Reserved
Formulas for Converting
Display Value = ((Internal Value + Offset) x Multiplier x Base) / (Divisor x 10
Internal Value = ((Display Value x Divisor x 10
Decimal Places
)
Decimal Places
) / (Multiplier x Base)) - Offset
Common Services
Service Code
0x0E
0x10
Implemented for:
Class
Yes
Yes
Instance
Yes
Yes
Service Name
Get_Attribute_Single
Set_Attribute_Single
Object Specific Services
Service Code Service Name
0x32 Get_Attributes_Scattered
(1)
0x34 Set_Attributes_Scattered
(1)
The instance and attribute are ignored for these services.
The table below lists the parameters for the Get_Attributes_Scattered and Set_Attributes_Scattered object-specific service:
Name Data Type Description
Scattered Parameters STRUCT of —
Parameter Number WORD Parameter to read or write
Parameter Value WORD Parameter value to read or write (zero when reading)
Important: The STRUCT may repeat up to 64 times in a single message.
ControlNet Objects
C-27
DSI Fault Object
Class Code
Hexadecimal
0x97
Decimal
151
Products such as PowerFlex drives use this object for faults. Adapters use this object for events.
Services
Service Code
0x0E
0x10
Instances
Implemented for:
Class Instance
Yes
Yes
Yes
Yes
Service Name
Get_Attribute_Single
Set_Attribute_Single
The number of instances depends on the maximum number of faults or events supported in the queue. The maximum number of faults/events can be read in Instance 0, Attribute 2.
Instances (Dec.) Single Mode Multi-Drive Mode
0 – 16383 Instances 0 – 16383 in the drive Instances 0 – 16383 in Drive 0
16384 – 17407 Instances 0 – 1023 in the adapter Instances 0 – 1023 in the adapter
17408 – 18431 Instances 0 – 1023 in the adapter Instances 0 – 1023 in Drive 1
18432 – 19455 Instances 0 – 1023 in the slave
19456 – 20479 Not supported
20480 – 21503 Not supported
21504 – 22527 Not supported
Instances 0 – 1023 in Drive 2
Instances 0 – 1023 in Drive 3
Instances 0 – 1023 in Drive 4
Instances 0 – 1023 in the adapter
Class Attributes
1
2
Attribute
ID
Access
Rule
3
Get
Get
Set
Name
Fault Command
Write
Data Type
Class Revision WORD
Number of
Instances
WORD
BYTE
Description
Revision of object
Maximum number of faults/events that the device can record in its queue
0 = No Operation
1 = Clear Fault/Event
2 = Clear Fault/Event Queue
3 = Reset Device
C-28
ControlNet Objects
DSI Fault Object
(Continued)
Class Attributes (Continued)
Attribute
ID
Access
Rule
4 Get
5 Get
Name
Fault Trip
Instance Read
Fault Data List
Data Type
WORD
6 Get
STRUCT of:
BYTE
BYTE
WORD[n]
WORD
7 Get
Number of
Recorded Faults
Fault Parameter
Reference
WORD
Description
Fault that tripped the device. For adapters, this value is always 1 when faulted.
Reserved
Number of faults/events in the queue. A
“0” indicates the fault queue is empty.
Reserved
1
ID
0
Attribute
Instance Attributes
Access
Rule
Get
Name
Full/All
Information
Get Basic
Information
Data Type
STRUCT of:
WORD
STRUCT of:
BYTE
BYTE
STRING[16]
STRUCT of:
LWORD
BOOL[16]
WORD
CONTAINER[n]
STRUCT of:
WORD
STRUCT of:
BYTE
BYTE
STRUCT of:
LWORD
BOOL[16]
Description
Fault code
Fault source
DSI port
DSI Device Object
Fault text
Fault time stamp
Timer value (0 = Timer not supported)
BOOL[0]: (0 = invalid data, 1 = valid data)
BOOL[1]: (0 = elapsed time, 1 = real time)
BOOL[2 - 15]: Not used
Reserved
Reserved
Fault code
Fault source
DSI port
DSI Device Object
Fault time stamp
Timer value (0 = Timer not supported)
BOOL[0]: (0 = invalid data, 1 = valid data)
BOOL[1]: (0 = elapsed time, 1 = real time)
BOOL[2 - 15]: Not used
ControlNet Objects
C-29
DSI Diagnostic Object
Class Code
Hexadecimal
0x99
Decimal
153
Services
Service Code
0x0E
0x10
Implemented for:
Class
Yes
Yes
Instance
Yes
Yes
Service Name
Get_Attribute_Single
Set_Attribute_Single
Instances
The number of instances depends on the maximum number of diagnostic items in the device. The total number of diagnostic items can be read in
Instance 0, Attribute 2.
Instances (Dec.) Single Mode
0 – 16383 Instances 0 – 16383 in the drive
Multi-Drive Mode
Instances 0 – 16383 in Drive 0
16384 – 17407 Instances 0 – 1023 in the adapter Instances 0 – 1023 in the adapter
17408 – 18431 Instances 0 – 1023 in the adapter Instances 0 – 1023 in Drive 1
18432 – 19455 Instances 0 – 1023 in the slave
19456 – 20479 Not supported
Instances 0 – 1023 in Drive 2
Instances 0 – 1023 in Drive 3
3
2
20480 – 21503 Not supported
1
ID
21504 – 22527 Not supported
Class Attributes
Attribute Access
Rule Name Data Type Description
Class Revision WORD 1 Get
Instances 0 – 1023 in Drive 4
Instances 0 – 1023 in the adapter
Get WORD Number of
Instances
ENUM Offset
Number of diagnostic items in the device
DSI ENUM object instance offset Get WORD
C-30
ControlNet Objects
DSI Diagnostic Object
(Continued)
Instance Attributes
(2)
1
(1)
Data Type Description
Attribute
ID
Access
Rule Name
0 Get
Get/Set Value
Full/All Info STRUCT of:
BOOL[32]
CONTAINER
(1)
CONTAINER
CONTAINER
CONTAINER
WORD
WORD
STRING[4]
UINT
UINT
UINT
INT
DWORD
STRING[16]
Various
Descriptor (Refer to pages
Value
Minimum value
Maximum value
Default value
Pad Word
Pad Word
Units (e.g., Amp, Hz)
Multiplier
(2)
Divisor
Base
Link (source of the value) (0 = no link)
Always zero (0)
Parameter name
Diagnostic item value
A CONTAINER is a 32-bit block of data that contains the data type used by a value. If signed, the value is sign extended. Padding is used in the CONTAINER to ensure that it is always 32-bits.
This value is used in the formulas used to convert the value between display units and internal units. Refer
to Formulas for Converting on page C-26 .
Appendix
D
Logic Command/Status Words
Appendix D provides the definitions of the Logic Command/Logic
Status words that are used for some products that can be connected to the adapter. If you do not see the Logic Command/Logic Status for the product that you are using, refer to your product’s documentation.
PowerFlex 4/40/400 Drives
Logic Command Word
x
Logic Bits
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Command
Description
x Stop x Start
(1)
0 = Not Stop
1 = Stop
0 = Not Start
1 = Start x x x x x
Jog 0 = Not Jog
1 = Jog
Clear Faults 0 = Not Clear Faults
1 = Clear Faults
Direction 00 = No Command
01 = Forward Command
10 = Reverse Command
11 = No Command
Not used x x x x x x x x Not used
Accel Rate 00 = No Command
01 = Accel Rate 1 Command
10 = Accel Rate 2 Command
11 = Hold Accel Rate
Decel Rate 00 = No Command
01 = Decel Rate 1 Command
10 = Decel Rate 2 Command
11 = Hold Decel Rate
Reference
Select
000 = No Command
001 = Freq Source = Select
010 = Freq Source = Int. Freq
011 = Freq Source = Comm
100 = Preset Freq 0
101 = Preset Freq 1
110 = Preset Freq 2
111 = Preset Freq 3
Not used
(1)
A “0 = Not Stop condition (logic 0)” must first be present before a “1 = Start condition” will start the drive.
D-2
Logic Command/Status Words
PowerFlex 4/40/400 Drives
(Continued)
Logic Status Word
Logic Bits
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Status x x x x x x x x x x x x x x x x Ready
Active
Command
Direction
Actual
Direction
Accel
Decel
Alarm
Description
0 = Not Ready
1 = Ready
0 = Not Active
1 = Active
0 = Reverse
1 = Forward
0 = Reverse
1 = Forward
0 = Not Accelerating
1 = Accelerating
0 = Not Decelerating
1 = Decelerating
0 = No Alarm
1 = Alarm
Fault
At Speed
Main Freq
0 = No Fault
1 = Fault
0 = Not At Reference
1 = At Reference
0 = Not Controlled By Comm
1 = Controlled By Comm
0 = Not Controlled By Comm
1 = Controlled By Comm
Operation
Command
Parameters 0 = Not Locked
1 = Locked
Digital Input 1
Status
Digital Input 2
Status
Digital Input 3
Status
(1)
Digital Input 4
Status
(1)
This status is available for only PowerFlex 40 drives with firmware version 2.xx (or higher).
Glossary
A
Adapter
Devices such as drives, controllers, and computers usually require an adapter to provide a communication interface between them and a network such as ControlNet. An adapter reads data on the network and transmits it to the connected drive. It also reads data in the drive and transmits it to the network.
The 22-COMM-C ControlNet adapter connects PowerFlex 4-Class drives to a ControlNet network. Adapters are sometimes also called
“cards,” “embedded communication options,” “gateways,” “modules,” and “peripherals.”
B
Bridge
A bridge refers to a network device that can route messages from one network to another.
A bridge also refers to a communications module in a ControlLogix controller that connects the controller to a network. See also Scanner.
C
CIP (Common Industrial Protocol)
CIP is the transport and application layer protocol used for messaging over EtherNet/IP, ControlNet, and DeviceNet networks. The protocol is used for implicit messaging (real-time I/O) and explicit messaging
(configuration, data collection, and diagnostics).
ControlFLASH
ControlFLASH is an Allen-Bradley software tool that lets users electronically update firmware on printed circuit boards. The tool takes advantage of the growing use of flash memory (electronic erasable chips) across industrial control products.
Controller
A controller, also called programmable logic controller, is a solid-state control system that has a user-programmable memory for storage of instructions to implement specific functions such as I/O control, logic, timing, counting, report generation, communication, arithmetic, and data file manipulation. A controller consists of a central processor, input/ output interface, and memory. See also Scanner.
ControlNet
An open producer-consumer communication network with features such as redundant media and deterministic I/O timing, designed for high performance or time critical requirements.
G-2
Glossary
D
Data Rate
The data rate is the speed at which data is transferred on the ControlNet network (fixed at 5Mbps).
DSI (Drive Serial Interface)
DSI is based on the Modbus RTU serial communication protocol and is used by PowerFlex 4-Class drives.
DSI Peripheral
A device that provides an interface between DSI and a network or user.
Peripheral devices are also referred to as “adapters” and “modules.” The
22-COMM-C, 22-SCM-232 serial converter, and PowerFlex 4-Class
HIMs (22-HIM-xxx) are examples of DSI peripherals.
DSI Product
A device that uses the DSI communications interface to communicate with one or more peripheral devices. For example, a motor drive such as a PowerFlex 4-Class drive is a DSI product. In this manual, a DSI product is also referred to as “drive” or “host.”
DriveExplorer Software
DriveExplorer software is a tool for monitoring and configuring
Allen-Bradley products and adapters. It can be run on computers running various Microsoft Windows operating systems. DriveExplorer (version
3.xx or higher) can be used to configure this adapter and PowerFlex drives. Information about DriveExplorer software and a free lite version can be accessed at http://www.ab.com/drives/driveexplorer.
DriveTools SP Software
A software suite designed for running on various Microsoft Windows operating systems. This software suite provides a family of tools, including DriveExecutive (version 3.01 or higher), that you can use to program, monitor, control, troubleshoot, and maintain Allen-Bradley products. DriveTools SP (version 1.01 or higher) can be used with
PowerFlex drives. Information about DriveTools SP can be accessed at http://www.ab.com/drives/drivetools.
E
EDS (Electronic Data Sheet) Files
EDS files are simple text files that are used by network configuration tools such as RSNetWorx for ControlNet to describe products so that you can easily commission them on a network. EDS files describe a product device type, revision, and configurable parameters. EDS files for many Allen-Bradley products can be found at http://www.ab.com/ networks/eds.
Glossary
Explicit Messaging
Explicit Messages are used to transfer data that does not require continuous updates. They are typically used to configure, monitor, and diagnose a device over the network.
F
Fault Action
A fault action determines how the adapter and connected drive act when a communications fault (for example, a cable is disconnected) occurs or when the scanner is switched out of run mode. The former uses a communications fault action, and the latter uses an idle fault action.
Fault Configuration
When communication is disrupted (for example, a cable is disconnected), the adapter and PowerFlex drive can respond with a user-defined fault configuration. The user sets the data that is sent to the drive using specific fault configuration parameters in the adapter. When a fault action parameter is set to use the fault configuration data and a fault occurs, the data from these parameters is sent as the Logic
Command and Reference.
Flash Update
The process of updating firmware in the adapter. The adapter can be flash updated using the Allen-Bradley software tool ControlFLASH, the built-in flash capability of DriveExplorer (version 4.01 or higher), or when the adapter is installed in a DSI External Comms Kit, the
X-Modem protocol and a 22-SCM-232 serial converter (version 3.xx or higher firmware).
H
HIM (Human Interface Module)
A device that can be used to configure and control a PowerFlex 4-Class drive. PowerFlex 4-Class HIMs (22-HIM-xxx) can be used to configure connected peripherals.
Hold Last
When communication is disrupted (for example, a cable is disconnected), the adapter and PowerFlex drive can respond by holding last. Hold last results in the drive receiving the last data received via the network connection before the disruption. If the drive was running and using the Reference from the adapter, it will continue to run at the same
Reference.
I
I/O Data
I/O data, sometimes called “implicit messages” or “input/output,” transmit time-critical data such as a Logic Command and Reference. The
G-3
G-4
Glossary terms “input” and “output” are defined from the scanner’s point of view.
Output is produced by the scanner and consumed by the adapter. Input is produced by the adapter and consumed by the scanner.
L
Logic Command/Logic Status
The Logic Command is used to control the PowerFlex drive (for example, start, stop, direction). It consists of one 16-bit word of output to the adapter from the network. The definitions of the bits in this word depend on the drive.
The Logic Status is used to monitor the PowerFlex drive (for example, operating state, motor direction). It consists of one 16-bit word of input from the adapter to the network. The definitions of the bits in this word depend on the drive.
N
Node Address
The valid range of ControlNet addresses is 1-99. The 22-COMM-C adapter includes two rotary switches to allow the ControlNet address to be set. The adapter reads the values of the switches only at power-up.
NVS (Non-Volatile Storage)
NVS is the permanent memory of a device. Devices such as the adapter and drive store parameters and other information in NVS so that they are not lost when the device loses power. NVS is sometimes called
“EEPROM.”
P
PCCC (Programmable Controller Communications Commands)
PCCC is the protocol used by some controllers to communicate with devices on a network. Some software products (for example,
DriveExplorer and DriveExecutive) also use PCCC to communicate.
PowerFlex 4-Class (Component-Class) Drives
The Allen-Bradley PowerFlex 4-Class (Component-Class) family of drives include the PowerFlex 4, PowerFlex 40, and PowerFlex 400.
These drives can be used for applications ranging from 0.2 kW (0.25
HP) to 7.5 kW (10 HP).
R
Reference/Feedback
The Reference is used to send a setpoint (for example, speed, frequency, torque) to the drive. It consists of one 16-bit word of output to the adapter from the network.
Feedback is used to monitor the speed of the drive. It consists of one
16-bit word of input from the adapter to the network.
Glossary
RSLogix 5/500/5000
RSLogix software is a tool for configuring and monitoring controllers to execute logic and communicate with connected devices. It is a 32-bit application that runs on various Microsoft Windows operating systems.
Information about RSLogix software can be found at http:// www.software.rockwell.com/rslogix.
RSNetWorx for ControlNet
RSNetWorx for ControlNet software is a tool for configuring and monitoring ControlNet networks and connected devices. It is a 32-bit application that runs on various Microsoft Windows operating systems.
Information about RSNetWorx for ControlNet software can be found at http://www.software.rockwell.com/rsnetworx.
S
Scanner
A scanner is a separate module (of a multi-module controller) or a built-in component (of a single-module controller) that provides communication with adapters connected to a network. See also
Controller.
Status Indicators
Status indicators are LEDs that are used to report the status of the adapter, network, and drive. They are on the adapter and can be viewed on the front cover of the drive when the drive is powered.
G-5
Z
Zero Data
When communications are disrupted (for example, a cable is disconnected), the adapter and drive can respond with zero data. Zero data results in the drive receiving zero as values for Logic Command and
Reference data. If the drive was running and using the Reference from the adapter, it will stay running but at zero Reference.
G-6
Notes:
Glossary
Index
B
A
adapter
Single versus Multi-Drive mode of
applying power to the adapter, 2-7
bit definitions for Logic Command/
Comm Flt Action parameter, B-2
communications module, see adapter
connecting adapter to the network,
ControlFLASH, G-1 controller, G-1
ControlLogix controller
with adapter in Multi-Drive mode
Explicit Message example,
with adapter in Single mode
ControlNet
ControlNet Objects
C
cables
CIP (Common Industrial Protocol),
D
diagnostic items
Index-2
DriveExplorer
accessing parameters with, 3-1
definition, G-2 free lite version, G-2
DriveTools SP
accessing parameters with, 3-1
Drv 0 - 4 Addr parameters, B-4
DSI
E
EDS (Electronic Data Sheet) files
EEPROM, see Non-Volatile Storage
(NVS)
environmental specifications, A-2
events
clearing, 8-7 list of, 8-7 viewing, 8-7
Explicit Messages
with adapter in Multi-Drive mode
with adapter in Single mode
F
fault action
configuring the adapter for, 3-4
fault configuration
configuring the adapter for, 3-4
G
H
HIM (Human Interface Module)
accessing parameters with, 3-1
hold last
configuring the adapter for, 3-4
I
I/O
configuring the adapter for, 3-3
configuring the network for
using example program for
Idle Flt Action parameter, B-3
installation
applying power to the adapter, 2-7
connecting to the network, 2-3
Internal Interface cable
connecting to the adapter, 2-4 connecting to the drive, 2-4 illustration, 2-4
MOD status indicator
mounting the adapter, 2-4 to 2-5
Multi-Drive mode
using ControlLogix controller
Explicit Message example,
using PLC-5 controller
L
Logic Command/Status
M
manual
related documentation, P-1 web site, P-1
messages, see Explicit Messages or
I/O
N
NET A status indicator
NET B status indicator
node address
Non-Volatile Storage (NVS)
O
Index-3
Index-4
P
parameters
editing with PowerFlex 4-Class
PCCC (Programmable Controller
Communication
PLC-5 controller
with adapter in Multi-Drive mode
with adapter in Single mode
PORT status indicator
PowerFlex drives
preparing for an installation, 2-1
processor, see controller programmable logic controller, see
controller
R
Reference/Feedback
requested packet interval, 4-6
ribbon cable, see Internal Interface
cable
RSNetWorx for ControlNet
S
Single mode
using ControlLogix controller
using PLC-5 controller
specifications for adapter, A-1
status indicators
Q
switches on adapter
T
U
W
web site
for DriveExplorer software, G-2 for DriveTools SP software, G-2 for EDS files, G-2
Z
zero data
configuring the adapter for, 3-4
Index-5
Index-6
U.S. Allen-Bradley Drives Technical Support
Tel: (1) 262.512.8176, Fax: (1) 262.512.2222, Email: [email protected], Online: www.ab.com/support/abdrives
www.rockwellautomation.com
Power, Control and Information Solutions Headquarters
Europe/Middle East/Africa: Rockwell Automation, Vorstlaan/Boulevard du Souverain 36, 1170 Brussels, Belgium, Tel: (32) 2 663 0600, Fax: (32) 2 663 0640
Asia Pacific: Rockwell Automation, Level 14, Core F, Cyberport 3, 100 Cyberport Road, Hong Kong, Tel: (852) 2887 4788, Fax: (852) 2508 1846
Americas: Rockwell Automation, 1201 South Second Street, Milwaukee, WI 53204-2496 USA, Tel: (1) 414.382.2000, Fax: (1) 414.382.4444
Publication 22COMM-UM006B-EN-P – September, 2005
Supersedes 22COMM-UM006A-EN-P dated May, 2005
P/N 348209-P02
Copyright © 2005 Rockwell Automation, Inc. All rights reserved. Printed in USA.

Public link updated
The public link to your chat has been updated.
Advertisement
Key features
- Connects to ControlNet network
- Communicates with PowerFlex 4, 40, 400 Drives
- Supports I/O, Logic Command/Reference
- Supports up to 5 drives in Multi-Drive mode
- Provides status indicators
- Requires external configuration using HIM or software
- Provides configurable fault actions
- Can be used with DSI External Comms Kit