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.ab.com/manuals/gi)
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 we use notes to make you aware of safety
considerations.
ATTENTION
Identifies information about practices or circumstances
that can 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.
Rockwell Automation
Support
Before you contact Rockwell Automation for technical assistance, we suggest
you please review the troubleshooting information contained in this
publication first.
If the problem persists, call your local distributor or contact Rockwell
Automation in one of the following ways:
PhoneUnited
States/Canada
Outside United
States/Canada
Internet
Email
Be prepared to furnish the following information when you contact support:
• Product Catalog Number
• Product Serial Number
• Firmware Revision Level
Your Questions or Comments on this Manual
⇒
⇒
1.262.512.8176 (7 AM - 6 PM CST)
1.440.646.5800 (24 hour support)
You can access the phone number for your
country via the Internet:
1.Go to http://www.ab.com
2. Click on Support
(http://support.automation.rockwell.com)
3. Under Contact Customer Support, click on
Phone Support
Go to http://ab.com/support/abdrives
support@drives.ra.rockwell.com
If you find a problem with this manual, please notify us of it on the enclosed
How Are We Doing form.
This version of the DriveLogix System User Manual corresponds to version 11
and later of the controller firmware. Changes made to this manual include:
For this updated information:See:
Using the Event Task2-6
How the DriveLogix System Uses Connections2-9
Determining Connections for Produced and Consumed Tags2-10
Determining Connections for Messages2-11
Determining Connections for I/O Modules2-12
Configuring DriveLogix Motion5-1
Communicating with Devices on a Third-Party Link11-1
DriveLogix Back-Up on DeviceNet12-1
Access ProceduresC-1
1Publication 20D-UM002C-EN-P - November 2003
2
Notes:
Publication 20D-UM002C-EN-P - November 2003
Preface
Purpose of this Manual
This manual guides the development of projects for DriveLogix controllers. It
provides procedures on how to establish communications:
• over the following networks
– ControlNet
– DeviceNet
– serial
• with the following devices
– PowerFlex
– controllers
– I/O
– workstations
– PanelView terminals
This manual works together with the Logix5000 Controllers Common Procedures
Programming Manual, publication 1756-PM001, which covers the following
tasks:
• Manage project files
• Organize your logic
• Organize tags
• Program routines
• Test a project
• Handle faults
®
700S drive
This manual works together with the Logix Controller Motion Instruction Set,
publication 1756-RM007D, which covers the following aspects of Logix
Motion commands:
• Instruction Names
• Operands
• Structured Text
• Motion Instruction Structure
• Fault Conditions
• Execution
• Error Codes
• Status Bits
1Publication 20D-UM002C-EN-P - November 2003
2
Who Should Use
This Manual
When to Use This Manual
How to Use this Manual
This manual is intended for those individuals who program applications that
use DriveLogix controllers, such as:
• software engineers
• control engineers
• application engineers
• instrumentation technicians
Use this manual:
• when you are ready to integrate your application with the PowerFlex
700S drive, I/0 devices, controllers, and networks in your system.
• after you perform these actions:
– develop the basic code for your application
– perform isolated tests of your application
This manual is divided into the basic tasks that you perform while
programming a DriveLogix controller. Each chapter covers a main task, such
as communicating over a specific network. For each main task, the chapter:
• lists what you need
• describes the steps to follow to accomplish that task
• provides details for each step, as necessary
• includes example system configurations
Controller Firmware
Revision
This revision of the DriveLogix User Manual corresponds to the following:
• version 12 and later of the controller firmware
• version 12 of RSLogix 5000 programming software
• version 2.02 of DriveExecutive programming software
Publication 20D-UM002C-EN-P - November 2003
Getting Started
Chapter
1
Introduction
ControlLogix controller acting as
centralized controller
DriveLogix controller using an
RS-232 connection
This chapter introduces the DriveLogix controller and provides a quick
overview on creating and downloading a project. The steps in this chapter
introduce the basic aspects of the DriveLogix controller.
The DriveLogix controller offers state-of-art control, communications, and
I/O elements in a embedded control package.
remote workstation
DriveLogix controller using local I/O
DriveLogix controllers, each with a 1788-CNC, -CNCR card,
linked over ControlNet link
This example DriveLogix system demonstrates:
• Centralized control using a ControlLogix™ controller to coordinate
several DriveLogix controllers.
• Distributed control using DriveLogix controllers at several locations.
• DriveLogix controller controlling a maximum of 8 local I/O modules.
• Local RS-232 connection for remote upload/download of a controller
project, for DF1 master/slave communications, or for ASCII
programming.
• Networked DriveLogix controllers using 1788-CNC, -CNCR
communication daugthercards to connect ControlNet links.
• Remote programming over ControlNet and EtherNet/IP.
1Publication 20D-UM002C-EN-P - November 2003
1-2 Getting Started
Connecting Battery
Allen-Bradley ships the DriveLogix controller with the battery installed, but
disconnected. You must connect the battary while installing the drive. Refer
to Installing and Maintaining the Battery on page B-1 and Access Procedures
on page C-1.
Publication 20D-UM002C-EN-P - November 2003
Getting Started 1-3
Creating and Downloading
a Project
Create a project
1
go to page 1-4
Configure
PowerFlex 700S Drive
2
3
4
The following diagram illustrates the steps you follow to create and download
a project. The remainder of this chapter provides examples of each step.
System setup for this quick start:
Local
slot 0 1794-IB16
You need:
Configure
I/O modules
Create tags
• RSLogix 5000 programming software
• RSLinx communication software
• DF1 point-to-point, serial connection from the workstation
to the controller (using 1756-CP3 or 1747-CP3 cable)
If you don’t have this hardware, you can still follow these steps.
Substitute the I/O modules you have for the ones listed here and
make the appropriate changes.
Enter logic
5
Download
a project
6
View status
7
Publication 20D-UM002C-EN-P - November 2003
1-4 Getting Started
Creating a project
1.Select File → New.
2.Define the project.The software uses the project name you enter with an .ACD extension to store your project.
Select a controller type.
Select the controller revision.
Name the project.
Describe the project (optional).
Create a project
1
Select where to store the project
(typically use the default directory).
The software creates the
new controller and displays:
controller organizer
Click OK.
Publication 20D-UM002C-EN-P - November 2003
Changing project properties
1.View properties for Controller quick_start.
A.Place the cursor over the Controller quick_start folder.
B.Click the right mouse button and select Properties.
2.View the General tab.
The screen defaults to the General tab.
Verify that the controller settings are
correct. Make changes if necessary.
Getting Started 1-5
Create a project
1
Click OK.
Publication 20D-UM002C-EN-P - November 2003
1-6 Getting Started
Configuring the host PowerFlex 700S Drive
1.Create the PowerFlex 700S Drive module.
Refer to Chater 3, "Placing and Configuring the
Drive" for more detailed information.
A.Place the cursor over the I/O Configuation folder.
2
Configure
B.Click the right mouse button and select New Module.
2.Select the Drive module.
Select the correct drive type.
Publication 20D-UM002C-EN-P - November 2003
Click the OK button
Configuring the host PowerFlex 700S Drive (continued)
3.Identify the drive module.
You should enter a name.
Describe the module (optional).
Select the communication format.
Select the minor revision and
Specify electronic keying.
Click Next
Getting Started 1-7
2
Configure
4.Use the Create wizard to configure the drive module.
Click Next
Choose the correct drive rating from the
pull-down menu
Click Next
Use default values for this example.
If you do not want to go through each screen in the Create wizard, click Finish
Click on Finish to apply and save the changes.
TIP
If no drive ratings appear, download and install DriveExecutive™ Database files from:
http://www.ab.com/drives/data.html
Publication 20D-UM002C-EN-P - November 2003
1-8 Getting Started
Adding a local input module1
1.Create a new module.
Refer to Chater 4, "Placing and Configuring Local I/O"
for more detailed information.
A.Place the cursor over the local DIN rail (FlexBus Local).
3
Configure
B.Click the right mouse button and select New Module.
2.Select an input module to add.
Select a catalog number.
Click OK.
Publication 20D-UM002C-EN-P - November 2003
continued
Adding a local input module (continued)
3.Identify the input module.
You should enter a name.
Describe the module (optional).
Select the communication format.
Specify electronic keying.
Click Next
These screens are specific to the 1794-IB16 input module.
Getting Started 1-9
3
Configure
4.Use the Create wizard to configure the input module.
Click Next.
Use default values for this example.
If you do not want to go through each screen in the Create wizard, click Finish
Click Finish.
Publication 20D-UM002C-EN-P - November 2003
1-10 Getting Started
Adding a local output module
1.Create a new module.
A.Place the cursor over the local DIN rail (FlexBus Local)
3
Configure
B.Click the right mouse button and select New Module.
2.Select an output module to add.
Select a catalog number.
Publication 20D-UM002C-EN-P - November 2003
Click OK.
continued
Adding a local output module (continued)
Getting Started 1-11
3.Identify the output module.
You should enter a name.
Describe the module (optional).
Select the communication format.
Specify electronic keying.
4.Use the Create wizard to configure the output module.
These screens are specific to the 1794-OB16 output module.
Click Next.
3
Use default values for this example.
If you do not want to go through each screen in the Create wizard, click
Configure
Click Next.
Click Finish.
Publication 20D-UM002C-EN-P - November 2003
1-12 Getting Started
Adding a local analog module
1.Create a new module.
A.Place the cursor over the local DIN rail (FlexBus Local)
3
Configure
B.Click the right mouse button and select New Module.
2.Select an output module to add.
Select a catalog number.
For this quick start example, select
Publication 20D-UM002C-EN-P - November 2003
Click OK.
continued
Adding a local analog module (continued)
Getting Started 1-13
3.Identify the output module.
You should enter a name.
Describe the module (optional).
Select the communication format.
Specify electronic keying.
4.Use the Create wizard to configure the output module.
These screens are specific to the 1794-OB16 output module.
Click Next.
3
Use default values for this example.
If you do not want to go through each screen in the Create wizard, click
Configure
Click Next.
Click Finish.
Publication 20D-UM002C-EN-P - November 2003
1-14 Getting Started
Changing module properties
1.View properties for the module.
A.Place the cursor over the 1794-IB16 module.
3
Configure
B.Click the right mouse button and select Properties.
2.View the General tab.
The screen defaults to the General tab.
Verify that the module settings are
correct. Make changes if necessary.
Click OK.
The tabs that appear depend on the type of module.
Publication 20D-UM002C-EN-P - November 2003
Important: If you want to change the communication format of a module, you must
Viewing I/O tags
1.View the tags for the controller.
Place the cursor on the Controller Tags folder and
double-click.
The software displays the module-defined tags for the I/O modules you created.
PowerFlex 700S tags
Getting Started 1-15
3
Configure
1794-IB16 module tags
1794-OB16 module tags
1794-IF2XOF2I module tags
Local rail tags
Click the Edit Tags tab.
Publication 20D-UM002C-EN-P - November 2003
1-16 Getting Started
Creating other tags
1.Create a tag.
4
Create tags
Enter the name of the new tag.
2.Select the data type.
Click + to display the members
of the TIMER structure.
Tab to this column and select the data type.
Select TIMER.
Click OK.
The software displays the tag.
You might have to resize the column to see the tag extensions.
Publication 20D-UM002C-EN-P - November 2003
continued
Documenting I/O with alias tags
1.Create an alias tag input_1 for Local:0:I.Data.1.
Getting Started 1-17
Create tags
4
Enter the name of the tag.
2.Select an input data word.
Tab here or click in the box.
Click here to display a grid of
bits and select the input bit.
3.Repeat steps 1 and 2 above to create an alias tag output_1 for Local:1:O.Data.1
Publication 20D-UM002C-EN-P - November 2003
1-18 Getting Started
Entering logic
1.Use default task, program, and routine.
When you created the project, the software
automatically created a MainTask, MainProgram, and
MainRoutine. Use these defaults for this example.
Double-click MainRoutine.
5
Enter logic
The software displays an empty routine.
2. Enter an XIO instruction.
Drag and drop the XIO instruction on an empty rung.
Publication 20D-UM002C-EN-P - November 2003
Loading...
+ 233 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.