DriveLogix System 5720 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.ab.com/manuals/gi) describes some important differences between solid state equipment and hard-wired electromechanical devices.
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: Phone United States/Canada 1.262.512.8176 (7 AM - 6 PM CST) 1.440.646.5800 (24 hour support) Outside United States/Canada You can access the phone number for your country via the Internet: 1.
Table of Contents Rockwell Automation Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Summary of Changes Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Preface Purpose of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Who Should Use This Manual . . . . . . . . . . . . . . . . . . . . . . .
2 Table of Contents Chapter 3 Placing and Configuring the Drive Using This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Understanding the Interface to the Drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Determining When the Controller Updates the Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Placing and Configuring the Drive . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Chapter 8 3 Communicating with Devices on a DeviceNet Link Using This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Configuring Your System for a DeviceNet Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Placing DeviceNet Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Accessing DeviceNet Devices. . . . . . . . . . . . . . .
4 Table of Contents Appendix C Access Procedures Using this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing Cover(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing Cover (For High Power Drives) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing Cover(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Summary of Changes Introduction 1 This version of the DriveLogix System User Manual corresponds to version 11 and later of the controller firmware.
2 Notes: Publication 20D-UM002C-EN-P - November 2003
Preface Purpose of this Manual This manual guides the development of projects for DriveLogix controllers.
2 Who Should 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 When to Use This Manual 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.
Chapter 1 Getting Started 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. Introduction The DriveLogix controller offers state-of-art control, communications, and I/O elements in a embedded control package.
1-2 Getting Started Connecting Battery Publication 20D-UM002C-EN-P - November 2003 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.
Getting Started Creating and Downloading a Project 1-3 The following diagram illustrates the steps you follow to create and download a project. The remainder of this chapter provides examples of each step.
1-4 Getting Started Creating a project 1. Select File →New. 1 Create a project 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). Select where to store the project (typically use the default directory). Click OK.
Getting Started 1-5 Changing project properties 1. View properties for Controller quick_start. 1 Create a project 2. A. Place the cursor over the Controller quick_start folder. B. Click the right mouse button and select Properties. View the General tab. The screen defaults to the General tab. Verify that the controller settings are correct. Make changes if necessary. Click OK.
1-6 Getting Started Configuring the host PowerFlex 700S Drive 1. Create the PowerFlex 700S Drive module. 2 Refer to Chater 3, "Placing and Configuring the Drive" for more detailed information. 2. A. Place the cursor over the I/O Configuation folder. B. Click the right mouse button and select New Module. Select the Drive module. Select the correct drive type.
Getting Started 1-7 Configuring the host PowerFlex 700S Drive (continued) 3. Identify the drive module. 2 Configure You should enter a name. Describe the module (optional). Select the communication format. Select the minor revision and Specify electronic keying. Click Next 4. Use the Create wizard to configure the drive module. Use default values for this example.
1-8 Getting Started Adding a local input module1 1. Create a new module. 3 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). B. Click the right mouse button and select New Module. 2. Select an input module to add. Select a catalog number. Click OK.
Getting Started 1-9 Adding a local input module (continued) 3. Identify the input module. These screens are specific to the 1794-IB16 input module. 3 Configure You should enter a name. Describe the module (optional). Select the communication format. Specify electronic keying. Click Next 4. Use the Create wizard to configure the input module. Use default values for this example. If you do not want to go through each screen in the Create wizard, click Finish Click Next. Click Finish.
1-10 Getting Started Adding a local output module 1. Create a new module. 3 2. A. Place the cursor over the local DIN rail (FlexBus Local) B. Click the right mouse button and select New Module. Select an output module to add. Select a catalog number. Click OK.
Getting Started 1-11 Adding a local output module (continued) 3. Identify the output module. These screens are specific to the 1794-OB16 output module. 3 Configure You should enter a name. Describe the module (optional). Select the communication format. Specify electronic keying. Click Next. 4. Use the Create wizard to configure the output module. Use default values for this example. If you do not want to go through each screen in the Create wizard, click Click Next. Click Finish.
1-12 Getting Started Adding a local analog module 1. Create a new module. 3 2. A. Place the cursor over the local DIN rail (FlexBus Local) B. Click the right mouse button and select New Module. Select an output module to add. Select a catalog number. For this quick start example, select Click OK.
Getting Started 1-13 Adding a local analog module (continued) 3. Identify the output module. These screens are specific to the 1794-OB16 output module. 3 Configure You should enter a name. Describe the module (optional). Select the communication format. Specify electronic keying. Click Next. 4. Use the Create wizard to configure the output module. Use default values for this example. If you do not want to go through each screen in the Create wizard, click Click Next. Click Finish.
1-14 Getting Started Changing module properties 1. View properties for the module. 3 2. A. Place the cursor over the 1794-IB16 module. B. Click the right mouse button and select Properties. Configure 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.
Getting Started 1-15 Viewing I/O tags 1. View the tags for the controller. 3 Configure 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 1794-IB16 module tags 1794-OB16 module tags 1794-IF2XOF2I module tags Local rail tags Click the Edit Tags tab.
1-16 Getting Started Creating other tags 1. Create a tag. 4 Enter the name of the new tag. 2. Tab to this column and select the data type. Select the data type. Select TIMER. Click OK. The software displays the tag. Click + to display the members of the TIMER structure. You might have to resize the column to see the tag extensions.
Getting Started 1-17 Documenting I/O with alias tags 1. Create an alias tag input_1 for Local:0:I.Data.1. 4 Enter the name of the tag. 2. Create tags Tab here or click in the box. Select an input data word. 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-18 Getting Started Entering logic 1. Use default task, program, and routine. 5 When you created the project, the software automatically created a MainTask, MainProgram, and MainRoutine. Use these defaults for this example. Double-click MainRoutine. The software displays an empty routine. 2. Enter an XIO instruction. Drag and drop the XIO instruction on an empty rung.
Getting Started 1-19 Entering logic (continued) 3. Assign a tag to the XIO instruction. Double-click the tag area of the instruction. 5 Enter logic Use the drop-down menu to select input_1. The software displays an incomplete rung. 4. Enter this logic. 5. To save the project, from the File menu, select Save.
1-20 Getting Started Downloading a project 1. Make a serial connection from the workstation to the controller. 6 2. Configure an RSLinx communication driver: A. In RSLinx software, select Communication →Configure Driver. B. From the Available Driver Types list, select “RS-232 DF1 Devices” and click Add New. C. Select the “Logix5550/CompactLogix serial port” and specify the COM port. Click Autoconfigure to have the software determine the remaining serial settings. 3. 4.
Getting Started 1-21 Viewing program scan time 1. View properties for the MainProgram. 7 2. A. Place the cursor over the MainProgram folder. B. Click the right mouse button and select Properties. View status Select the Configuration tab. The Configuration tab displays the maximum and last scan times for the program.
1-22 Getting Started Viewing controller memory usage 1. View properties for Controller quick_start. 7 2. A. Place the cursor over the Controller quick_start folder. B. Click the right mouse button and select Properties. View status Select the Advanced tab. In addition to other information, the Advanced tab displays controller memory usage. Important: The amount of memory that the software displays includes both the user available memory and the memory reserved for overhead.
Chapter 2 What Is DriveLogix? The DriveLogix controller is part of the Logix environment. The DriveLogix controller provides a distributed control system built on these components: Using This Chapter • DriveLogix controller that supports the Logix instructions. • RSLogix 5000 programming software that supports every Logix controller. • Direct connection to host PowerFlex 700S drive. • FLEX™ I/O modules that provide a compact, DIN-rail mounted I/O system.
2-2 What Is DriveLogix? The controller operating system is a preemptive multitasking system that is IEC 1131-3 compliant.
What Is DriveLogix? 2-3 Defining tasks A task provides scheduling and priority information for a set of one or more programs. You can configure tasks as either continuous or periodic. The DriveLogix controller supports as many as 8 tasks, only one of which can be continuous. A task can have as many as 32 separate programs, each with its own executable routines and program-scoped tags.
2-4 What Is DriveLogix? The following example shows the task execution order for an application with periodic tasks and a continuous task. Task: Priority Level: Task Type: Actual Execution Time: Worst Case Execution Time: 1 5 20ms periodic task 2ms 2ms 2 7 dedicated I/O task 1ms 3ms 5ms fastest RPI 3 10 10ms periodic task 4ms 8ms 4 none (lowest) continuous task 25ms 60ms Task 1 Task 2 Task 3 Task 4 0 5 10 15 20 25 30 35 40 45 50 55 60 65 Notes: A.
What Is DriveLogix? 2-5 Defining programs Each program contains program tags, a main executable routine, other routines, and an optional fault routine. Each task can schedule as many as 32 programs. The scheduled programs within a task execute to completion from first to last. Programs that aren’t attached to any task show up as unscheduled programs. You must specify (schedule) a program within a task before the controller can scan the program.
2-6 What Is DriveLogix? Using the Event Task The event task is available with DriveLogix controllers using firmware version 12.x or greater. Previously, the only tasks available were the continuous task and periodic task. However, the event task offers DriveLogix controller users a task that executes a section of logic immediately when an event occurs. An event task performs a function only when a specific event (trigger) occurs.
What Is DriveLogix? 2-7 Triggering the Event Task To trigger an event task based on conditions in your logic, use the EVENT Instruction trigger. Let an event trigger this task. Let an EVENT instruction trigger the task. No tag is required. The EVENT Instruction Only trigger requires that you use a Trigger Event Task (EVENT) instruction to trigger the task. You can use an EVENT instruction from multiple points in your project. Each time the instruction executes, it triggers the specified event task.
2-8 What Is DriveLogix? Programmatically Determine if an EVENT Instruction Triggered a Task To determine if an EVENT instruction triggered an event task, use a Get System Value (GSV) instruction to monitor the Status attribute of the task. Table 2.2 Status Attribute of the TASK Object Attribute: Data Type: Instruction: Description: Status DINT GSV Provides status information about the task.
What Is DriveLogix? How the DriveLogix System Uses Connections 2-9 The DriveLogix system uses a connection to establish a communication link between two devices. The DriveLogix system has enough internal resources to support a connection to every local I/O module and 32 connections through the daughtercard (e.g. the 1788-ENBT card). However, the daughtercard’s connection limit is the limiting factor when sizing a system.
2-10 What Is DriveLogix? The communication module you select determines the number of connections you have available for I/O and messages: This communication card: Supports this number of connections: 1788-CNx 32 connections–the maiximum number of scheduled connections is dependent on the RPI: RPI (with 5 ms NUT) Max Scheduled Connections 5 ms 3 10 ms 6 20 ms 13 40 ms 20 The remaining connections (or all 32, if you have no scheduled connections) can be used for unscheduled connections 1788-EN
What Is DriveLogix? 2-11 DriveLogix controllers can produce and consume tags over: • a ControlNet network • an EtherNet/IP network. IMPORTANT For two controllers to share produced or consumed tags, both controllers must be attached to the same control network (such as a ControlNet or Ethernet/IP network). You cannot bridge produced and consumed tags over two networks. The total number of tags that can be produced or consumed is limited by the number of available connections and memory.
2-12 What Is DriveLogix? The controller has the following limits on the number of connections that you can cache: If you have this software and firmware revision: 11.x or earlier Then you can cache: • block transfer messages for up to 16 connections • other types of messages up to 16 connections 12.x or later Determining Connections for I/O Modules up to 32 connections The DriveLogix system uses connections to transmit I/O data.
What Is DriveLogix? 2-13 Connections for remote devices To optimize the number of available connections, place remote, digital I/O in the same location and use a rack-optimized connection to the remote adapter that connects the remote I/O to the DriveLogix system. If you have remote analog I/O modules, or want a direct connection to specific remote I/O modules, you do not have to create the rack-optimized connection to the remote adapter.
2-14 What Is DriveLogix? EtherNet/IP ! Rack-optimized connections for I/O modules In this example, assume that each I/O module is configured for a rack-optimized connection to the controller. The following table calculates the connections in this example.
What Is DriveLogix? 2-15 EtherNet/IP ! Connections to remote ControlNet or EtherNet/IP devices A remote device over ControlNet and EtherNet/IP can be configured as either a rack-optimized connection and direct connection. In this example, the DriveLogix controller uses one rack-optimized connection to communicate with the communication adapter to receive data from the digital I/O modules (two in this example) and uses one direct connection to communicate with the analog module.
2-16 What Is DriveLogix? Connections to DeviceNet devices In this example the controller uses two connections (one for status and one for I/O) to communicate with the DeviceNet devices through the 1788-DNBO module. The 1788-DNBO module uses a rack-optimized connection to the DeviceNet devices. DriveLogix controller DeviceNet network PanelView 300 DeviceNet devices The following table calculates the connections in this example.
What Is DriveLogix? 2-17 the controller. However, the controller can use a MSG instruction to get information directly to or from a DeviceNet device. Determining Total Connection Requirements To calculate the total connection requirements for a DriveLogix controller, consider the connections to local I/O modules, the host PowerFlex 700S drive and the connections to remote modules.
2-18 What Is DriveLogix? Remote connections depend on the communication card.
What Is DriveLogix? 2-19 This example system has these details: local rail controller 8 I/O modules extended-local rail ControlNet network 8 I/O modules 8 I/O modules DeviceNet network 4 DeviceNet devices • I/O modules on the local rail are digital, so configure each module for a rack-optimized connection • I/O modules on the extended-local rail are analog, so configure each module for a direct connection • I/O modules on the ControlNet network are 4 digital and 4 analog, so configure each digital mo
2-20 What Is DriveLogix? Downloading Projects In general, you use the programming software to download a project from your programming computer to the controller. The DriveLogix controller, with expanded memory, supports nonvolatile memory for project storage. IMPORTANT Nonvolatile memory stores the contents of user memory at the time that you store the project. • Changes that you make after you store the project are not reflected in nonvolatile memory.
What Is DriveLogix? 3. Click the Load/Store button and specify when you want the controller to load the project from nonvolatile memory. 4. Click the Load button to load the project from nonvolatile memory into the controller.
2-22 What Is DriveLogix? Selecting a System Overhead Percentage 1. The Controller Properties lets you specify a percentage for system overhead. This percentage specifies the percentage of controller time (excluding the time for periodic tasks) that is devoted to communication and background functions View properties for the controller and select the Advanced tab.
What Is DriveLogix? 2-23 The following table shows the ratio between the continuous task and the system overhead functions: At this time slice: The continuous tasks runs for: And then overhead occurs for up to: 10% 9 ms 1 ms 20% 4 ms 1 ms 33% 2 ms 1 ms 50% 1 ms 1 ms At the default time slice of 10%, system overhead interrupts the continuous task every 9ms (of continuous task time). Legend: Task executes. Task is interrupted (suspended).
2-24 What Is DriveLogix? If you increase the time slice to 20%, the system overhead interrupts the continuous task every 4ms (of continuous task time). 1 ms 1 ms 1 ms 1 ms 1 ms system overhead 4 ms 4 ms 4 ms 4 ms 4 ms continuous task 5 10 15 20 25 elapsed time (ms) If you increase the time slice to 50%, the system overhead interrupts the continuous task every 1ms (of continuous task time).
Chapter 3 Placing and Configuring the Drive Using This Chapter For Information about: Understanding the Interface to the Drive Determining When the Controller Updates the Drive Placing and Configuring the Drive Inhibiting the Drive Connection Using DriveExecutive Lite Accessing Drive Data Monitoring Drive Data Understanding the Interface to the Drive See page 3-1 3-3 3-4 3-13 3-15 3-23 3-23 The DriveLogix controller supports a direct connection to the drive consisting of 16 inputs and 16 outputs.
3-2 Placing and Configuring the Drive Mapping for Inputs and Outputs For each of the 16 inputs or 16 outputs, there are two dedicated parameters within the drive for a total of 64 parameters. One parameter is a DINT type and the other is a REAL type. Selecting a communication format defines the data types for each input and selects the correct parameter for each input and output in the communication link. The remaining parameter is not utilized.
Placing and Configuring the Drive DriveLogix Controller Output Word 0 Output Word 1 Output Word 2 Output Word 3 Output Word 4 Output Word 5 Output Word 6 Output Word 7 Output Word 8 Output Word 9 Output Word 10 Output Word 11 Output Word 12 Output Word 13 Output Word 14 Output Word 15 Determining When the Controller Updates the Drive 3-3 PowerFlex 700S Drive Parameter Number Name Data Type 600 Integer In00 DINT 601 Real In00 REAL 602 Integer In01 DINT 603 Real In01 REAL 604 Integer In02 DINT 605 Real In
3-4 Placing and Configuring the Drive You must configure the Requested Packet Interval (RPI) rate for the drive. This setting affects how fast the controller reads and writes the data in the drive interface. TIP If you want data to remain constant throughout one scan, make a copy of the data at the beginning of the scan and use the copy throughout the scan. The Drive consumes data from the DriveLogix controller every 2 milliseconds, and produces data to the controller every 2 milliseconds.
Placing and Configuring the Drive IMPORTANT 3-5 You must select the correct voltage rating for the drive, when adding the drive. You can find this on the drive data nameplate. 3. Configure the drive. Use the module properties wizard to specify characteristics for the module. Click Next 4. Click finish when you are done. The completed module appears in the Controller Organizer. The selection you make for the Comm Format determines the communication format for the connection to the drive.
3-6 Placing and Configuring the Drive Communication Formats The communication format determines the data structure, tag names, and required links for communication to the drive. Each communication format has been structured to meet the requirements of a specific type of application (Speed Control, Position Control, or general purpose), and supports a different data structure. The links within the PowerFlex 700S required to support the selected format are also different.
Placing and Configuring the Drive 3-7 The following tables show the tag names and their relation ship to parameters in the drive. These examples use a module name of “drive_module”. Table 3.1 Mapping for the Velocity Control Communication Format DriveLogix Controller Outputs Tag Name drive_module:O.LogicCommand drive_module:O.SpeedRef1 drive_module:O.TorqueRef1 drive_module:O.SpdTorqModeSel drive_module:O.TorqueStep drive_module:O.SpdRegDroop drive_module:O.UserDefinedRealData[0] drive_module:O.
3-8 Placing and Configuring the Drive Table 3.2 Mapping for the Position Control Communication Format DriveLogix Controller Outputs Tag Name drive_module:O.LogicCommand drive_module:O.SpeedRef1 drive_module:O.TorqueRef1 drive_module:O.SpdTorqModeSel drive_module:O.TorqueStep drive_module:O.SpdRegDroop drive_module:O.PositionControl drive_module:O.CoarsePositTrgt drive_module:O.PtPtPositRef drive_module:O.PositRefSel drive_module:O.PositOffset1 drive_module:O.UserDefinedRealData[0] drive_module:O.
Placing and Configuring the Drive 3-9 Table 3.3 Mapping for the User-Defined Control Communication Format DriveLogix Controller Outputs Tag Name drive_module:O.LogicCommand drive_module:O.UserDefinedRealData[0] drive_module:O.UserDefinedRealData[1] drive_module:O.UserDefinedRealData[2] drive_module:O.UserDefinedRealData[3] drive_module:O.UserDefinedRealData[4] drive_module:O.UserDefinedRealData[5] drive_module:O.UserDefinedRealData[6] drive_module:O.UserDefinedRealData[7] drive_module:O.
3-10 Placing and Configuring the Drive Table 3.4 Mapping for the Motion Control Communication Format DriveLogix Controller Outputs Tag Name drive_module:O.UserDefinedRealData[0] drive_module:O.UserDefinedRealData[1] drive_module:O.UserDefinedRealData[2] drive_module:O.UserDefinedRealData[3] drive_module:O.UserDefinedRealData[4] drive_module:O.UserDefinedRealData[5] drive_module:O.UserDefinedRealData[6] drive_module:O.UserDefinedRealData[7] drive_module:O.UserDefinedRealData[8] drive_module:O.
Placing and Configuring the Drive 3-11 Table 3.5 Mapping for the Custom User-Defined Control Communication Format DriveLogix Controller Outputs Tag Name drive_module:O.LogicCommand drive_module:O.UserDefinedRealData[0] drive_module:O.UserDefinedRealData[1] drive_module:O.UserDefinedRealData[2] drive_module:O.UserDefinedRealData[3] drive_module:O.UserDefinedRealData[4] drive_module:O.UserDefinedRealData[5] drive_module:O.UserDefinedRealData[6] drive_module:O.UserDefinedRealData[7] drive_module:O.
3-12 Placing and Configuring the Drive Not all 32-bits within parameter 151 [Logic Command], are directly visible in the PowerFlex 700S. To view all 32-bits, refer to parameter 152 [Applied LogicCmd]. DriveLogix Controller Outputs Tag Name drive_module:O.LogicCommand drive_module:O.SpdRampDsbl drive_module:O.SpdSCrvEn drive_module:O.TachLossRst drive_module:O.TimeAxisEn drive_module:O.MCAtuneEn drive_module:O.DirCtrlEn drive_module:O.PMOffsetEn drive_module:O.MtrInertEn drive_module:O.
Placing and Configuring the Drive Inhibiting the Drive Connection 3-13 RSLogix 5000 programming software allows you to inhibit the controller’s connection to the drive, in the same way you inhibit its connection to an I/O module. Inhibiting the drive module shuts down the connection from the controller to the drive. When you create the module you can choose to inhibit it. After you have created the module you can inhibit or un-inhibit it by manipulating its properties window.
3-14 Placing and Configuring the Drive To inhibit a module from logic, you must first read the Mode attribute for the module using a GSV instruction. Set bit 2 to the inhibit status (1 to inhibit or 0 to uninhibit). Use a SSV instruction to write the Mode attribute back to the module.
Placing and Configuring the Drive Using DriveExecutive Lite 1. 3-15 In order to launch DriveExecutive Lite from within RSLogix 5000, the drives power rating must be selected. The drive firmware revision must be applied prior to selecting the power rating. If not already done, enter the drive firmware revision. Click the Finish button to apply the revision data 2. In the Controller Organizer, select the PowerFlex 700S drive. Right-click the drive module and select Properties 3. Select the Power tab.
3-16 Placing and Configuring the Drive TIP If your drive’s power rating does not appear as a selection, you do not have the DriveExecutive Lite database file for your drive. To create a database file, connect to the drive with DriveExecutive Lite. This will automatically create the database. You can also download the database file from http://www.ab.com/drives/data.html 5. Once the power rating is selected, apply your changes by selecting the Apply button. 6. Select the Setup tab. 7.
Placing and Configuring the Drive 8. Click the DriveExecutive button to launch DriveExecutive Lite. 9. When asked to create a new DriveExecutive Lite file, select yes.
3-18 Placing and Configuring the Drive Viewing the Communication Interface to the Controller DriveExecutive Lite has a setup screen that details the communication interface between the controller and drive. From this screen, the relationship between drive parameters and controller tags is presented for the selected communication format. You can create additional links within the drive for use with the user-defined tags in the controller. 1.
Placing and Configuring the Drive 3-19 2. To send additional data from the drive to the controller go to the To Controller tab. Click the To Controller tab.Select the desired source for the user-defined tag (Output Voltage in this example). TIP Use a UserDefinedRealData tag for parameters that contain floating point data, and use a UserDefinedIntegerData tag for parameters that contain integer data.
3-20 Placing and Configuring the Drive Parameter 385 [Lgx CommLossData] determines what the drive does with data from the controller when communication is lost. It determines if the drive resets the data to zero or holds the data in its last state. Configure these parameters, using DriveExecutive Lite. Locate them in the Fault/Alm Config group of the Utility file.
Placing and Configuring the Drive 3-21 Using Existing DriveExecutive Lite Files Before using an existing DriveExecutive Lite file, verify the firmware revision, communication format, and power rating in the drive file match the data entered in drive module properties in your DriveLogix application. 1. Select Properties from the Drive menu. 2. View revision and ratings on the General tab of the Properties window. 3.
3-22 Placing and Configuring the Drive 4. TIn RSLogix 5000, go to the Setup tab of the Properties window. Click the Browse button. Select the existing DriveExecutive file (Existing Drive.dno in this example). Click the Open button. 5. Click the Apply button and launch DriveExecutive Lite.
Placing and Configuring the Drive Accessing Drive Data 3-23 Drive data is displayed as structures of multiple tags. The names and data structures are based on the selected communication format. The programming software automatically creates the necessary structures and tags when you configure the drive module. Each tag name follows this format: ModuleName:Type.MemberName.SubMemberName.
3-24 Placing and Configuring the Drive Configuring the Controller’s Response to a Connection Failure You can configure the drive module to generate a major fault in the controller if the drive loses its connection to the controller. Check this box to configure the drive module to generate a major fault if it loses its connection to the controller If you do not configure the major fault to occur, you should monitor the drive module status.
Placing and Configuring the Drive 3-25 Monitoring the drive module Each communication format provides a drive status word that will indicate when a drive fault or alarm occurs. To view this data through the programming software: 1. In the Controller Organizer, select Controller Tags. Right-click the selected icon and select Monitor Tags. 2. Expand the data as necessary. You can write logic to monitor these bits and take appropriate action if a fault or alarm occurs.
3-26 Placing and Configuring the Drive Notes: Publication 20D-UM002C-EN-P - November 2003
Chapter 4 Placing and Configuring Local I/O Using This Chapter For information about: See page Placing local I/O modules 4-2 Determining when the controller updates local I/O 4-3 Configuring a DIN rail 4-5 Configuring local I/O modules 4-6 Inhibiting I/O module operation 4-10 Accessing I/O data 4-13 Monitoring I/O modules 4-16 The DriveLogix controller supports a local DIN rail of as many as 8 I/O modules.
4-2 Placing and Configuring Local I/O Placing Local I/O Modules When you create a project for a DriveLogix controller, the Controller Organizer for that project automatically displays the local DIN rail. You must configure an RPI rate for the DIN rail. This rate applies to all the I/O modules you install on the DIN rail. .
Placing and Configuring Local I/O 4-3 The FlexBus continually scans all the slots (0-7) on the DIN rail. The FlexBus scans the DIN rail, starting with slot 0, then scanning slot 1, and continuing with all the slots, and then repeating the cycle. Even if a module is inhibited or a slot is empty, the FlexBus scans that slot. The FlexBus scan identifies where modules reside and collects module data for the controller scan. The controller scans only those modules that are configured in the Control Organizer.
4-4 Placing and Configuring Local I/O Use the following flowchart to determine when a producer (controller, input module, or ControlNet bridge module) will send data. output input or output data? analog or digital? digital input analog digital analog or digital? remote or local? analog remote RTS ≤RPI? No Yes local Data is sent to the backplane at the RTS. Data is sent to the backplane at the RTS and RPI.
Placing and Configuring Local I/O Configuring a DIN Rail 4-5 When you create a DriveLogix project, the programming software automatically creates the DIN rail for the project. You must configure the DIN rail. 1. In the Controller Organizer, select the local (Local) rail of the controller. Right-click and select Properties. 2. Specify the configuration options for the rail. You must specify these characteristics: • On the General tab, specify the size of the chassis.
4-6 Placing and Configuring Local I/O The communication format for the DIN rail is automatically set for rack-optimized. You cannot change this setting because the controller uses one rack-optimized connection for each DIN rail, whether you configure any I/O modules for rack-optimized or not. Configuring Local I/O Modules Use the programming software to configure the I/O modules for the controller. You can configure I/O modules for the local rail.
Placing and Configuring Local I/O 4-7 3. Configure the module. Use the module wizard to specify characteristics for the module. Click Next to continue through the wizard. The selection you make for the Comm Format determines the connections required for the I/O module. Once you complete adding a module, you cannot change this selection. See page 4-8. IMPORTANT The DriveLogix controller supports FLEX and FLEX Ex I/O modules, but these I/O modules do not behave the same.
4-8 Placing and Configuring Local I/O Keying: Description: compatible module The module must be compatible with the software configuration. These characteristics must match: • module type • catalog number disable keying ATTENTION ! No attributes of the software or hardware are required to match. If a module is configured for a direct connection, changing the RPI and electronic keying selections can cause the connection to the module to be broken and may result in loss of data.
Placing and Configuring Local I/O 4-9 for a rack-optimized connection, so consider configuring all local I/O modules for rack-optimized connections. Use the documentation for the I/O module to determine what data format to use. The listen-only communication format works for remote I/O only. Because of the distributed nature of a DriveLogix system, the DriveLogix controller must own its local I/O modules. No other Logix-based controller can listen to or own the local DriveLogix I/O.
4-10 Placing and Configuring Local I/O communication format: rack optimization (which corresponds to a rack-optimized connection for the I/O module) The rack-optimized tags are created as aliases into the array tag Local:I, which is the array for input modules on the local rail. This array contains one element for each slot on the rail (based on the chassis size you specify when you configure the rail).
Placing and Configuring Local I/O 4-11 When you configure an I/O module, it defaults to being not inhibited. You can change an individual module’s properties to inhibit a module. ATTENTION ! Inhibiting a module causes the connection to the module to be broken and prevents communication of I/O data. The controller and other I/O modules continue to operate based on old data from that module. To avoid potential personal injury and damage to machinery, make sure this does not create unsafe operation.
4-12 Placing and Configuring Local I/O When you select to inhibit a module, the controller organizer displays a yellow attention symbol ! over the module. If you are: Inhibit a module to: offline put a place holder for a module you are configuring The inhibit status is stored in the project. When you download the project, the module is still inhibited. online stop communication to a module If you inhibit a module while you are connected to the module, the connection to the module is closed.
Placing and Configuring Local I/O 4-13 To inhibit a module from logic, you must first read the Mode attribute for the module using a GSV instruction. Set bit 2 to the inhibit status (1 to inhibit or 0 to uninhibit). Use a SSV instruction to write the Mode attribute back to the module. For example: Accessing I/O Data The programming software displays I/O data as structures of multiple tags that depend on the specific features of the I/O module.
4-14 Placing and Configuring Local I/O where: This address variable: Is: Location Identifies network location LOCAL = local DIN rail or chassis ADAPTER_NAME = identifies remote adapter or bridge SlotNumber Slot number of I/O module in its chassis Type Type of data I = input O = output C = configuration S = status MemberName Specific data from the I/O module; depends on the type of data the module can store For example, Data and Fault are possible fields of data for an I/O module.
Placing and Configuring Local I/O 4-15 The following examples show addresses for data in a DriveLogix system. EXAMPLE I/O module on the local DIN rail 7 6 5 4 3 2 1 0 Sample tag names for this example: Location: Example Tag Name: input module in slot 0 of LOCAL Local:0:I.Data Local:0:I.Fault output module in slot 1 of LOCAL Local:1:C.SSData Local:1:I.Fault Local:1:O.Data data for the LOCAL DIN rail Local:I.Data Local:I.Fault Local:O.Data Local:O.
4-16 Placing and Configuring Local I/O Using aliases to simplify tag names An alias lets you create a tag that represents another tag. This is useful for defining descriptive tag names for I/O values. For example: Example: I/O structure Description: Local:0:O.Data.0 The aliases describe the specific I/O points. Local:0:I.Fault.0 alias light_on = Local:0:O.Data.0 light_off = Local:0:I.Fault.
Placing and Configuring Local I/O 4-17 • inputs remain in their last, non-faulted state ATTENTION ! If a module loses its connection to the controller, the controller and other I/O modules continue to operate based on old data from that module. To avoid potential personal injury and damage to machinery, make sure this does not create unsafe operation. Configure critical I/O modules to generate a controller major fault when they lose their connections to the controller.
4-18 Placing and Configuring Local I/O experiences a fault. This example assumes a direct connection for the I/O module. EXAMPLE Publication 20D-UM002C-EN-P - November 2003 Given this I/O configuration, the following logic tests bits of I/O modules to determine status.
Placing and Configuring Local I/O 4-19 Monitoring a rack-optimized connection The controller views the DIN rail as another module in the system. Each DIN rail has its own data. To view this data through the programming software: 1. In the Controller Organizer, select Controller Tags. Right-click to display the Data Monitor. You can write logic to monitor the rack bits and take appropriate action if a fault occurs. For example, the following logic determines whether an error occurs on the Local rail.
4-20 Placing and Configuring Local I/O Notes: Publication 20D-UM002C-EN-P - November 2003
Chapter 5 Configuring DriveLogix Motion Using This Chapter For information about: See page Configuring the Drive 5-1 Programming the Controller 5-5 Supported Motion Commands 5-12 This chapter introduces DriveLogix motion. The steps in this chapter provide the minimum settings required to begin testing of DriveLogix motion. System Requirements • • • • 1 PowerFlex 700S Drive with firmware revision 2.03 or higher DriveLogix controller with firmware revision 12.
5-2 Configuring DriveLogix Motion Configuring the Drive In DriveExecutive software, connect to the drive and access the Peer Communications dialog as shown below: 1. From the File menu, select Peer Communication. 2. Click on the From Controller tab. 3. Select Motion Control from the list of possible Controller Comm Formats.
Configuring DriveLogix Motion 5-3 Next link the appropriate parameters to the words being produced and consumed by the controller. 4. Double click on parameter 632 [Integer Out00], from the linear list view. This opens a dialog window for the parameter. 5. Click on the Link Source tab. 6. Type the parameter number (155) into the Find Parameter Window or Use the Select Parameter list to choose a parameter source.
5-4 Configuring DriveLogix Motion Table 5.1 Required Parameter Links Destination Parameter Source Parameter Description 1003 [Interp SyncInput] 919 [Motn Posit Sync] The drive receives the synchronization pulse from the DriveLogix. This keeps the interpolators in synch. 632 [Integer Out00] 155 [Logic Status] The DriveLogix controller receives the status of the drive. 22 [Speed Trim 2] 318 [Posit Spd Output] This is a default link.
Configuring DriveLogix Motion Programming the Controller 5-5 Using RSLogix 5000, create a new project. . 1. Select File →New. 2. Define the project. Use Revision 12 or higher You must enter a name Click OK 3. Add the drive.
5-6 Configuring DriveLogix Motion 3. Add the drive (continued).
Configuring DriveLogix Motion 5-7 3. Add the drive (continued). Browse for the file you saved in DriveExecutive Click Finish 4. Adding a Motion Group.
5-8 Configuring DriveLogix Motion 5. Add the Axis Right click on the Grouped Axis icon Select New Axis Select AXIS_GENERIC Enter a name Click Configure Set the Axis Configuration to Servo The associated module should be the drive connection from the I/O configuration and the encoder channel being used for feedback. Select Channel 0 IMPORTANT Only Channel 0 will function for a Servo axis. Channel 1 may be used for a Feedback Only axis.
Configuring DriveLogix Motion 5-9 5. Adding the Axis (continued) Determine how many Output Cam execution nodes (instances) are created for a specific axis. The value specified for Execution Target in the MAOC instruction references a specific instance in which a value of zero selects the first instance. Click Next Enter the positioning units. In this example inches are the units. Degrees, pallets, widgets, etc. could be used.
5-10 Configuring DriveLogix Motion 5. Adding the Axis (continued) A B Referring to the tables below, enter the Homing Mode, Homing Position, Offset, and Homing Sequence. C Click Next A Homing Mode Active - the desired homing sequence is selected by specifying whether a home limit switch and/or the encoder marker are used for this axis. Active homing sequences always use the trapezoidal velocity profile.
Configuring DriveLogix Motion 5-11 5. Adding the Axis (continued) Enter the Dymamic Motion variables (Maximum Speed, Acceleration and Deceleration). Do not leave zero values in these varibles. Do not exceed system limits, examine parameter 9 [Total Inertia]. Click Finish 6. Download the project to the controller. ATTENTION ! Running the system without proper tuning can cause unstable and unpredictable operation.
5-12 Configuring DriveLogix Motion Supported Motion Commands The following Logix Motion Instructions are supported by the DriveLogix controller: Motion State • • • • • MSO (Motion Servo On) MSF (Motion Servo Off) MASD (Motion Axis Shutdown) MASR (Motion Axis Shutdown Reset) MAFR (Motion Axis Fault Reset) Motion Move • • • • • • • • • • MAJ (Motion Axis Jog) MAM (Motion Axis Move) MAS (Motion Axis Stop) MAH (Motion Axis Home) MAG (Motion Axis Gearing) MCD (Motion Change Dynamics) MRP (Motion Redine Po
Chapter 6 Communicating with Devices on an EtherNet/IP Link Using This Chapter For information about: Configuring Your System for a EtherNet/IP Link Configuring Your System for a EtherNet/IP Link 6-1 Configuring Remote I/O 6-8 Sending Messages 6-13 Producing and Consuming Data 6-20 Guidelines for Configuring Connections 6-23 Example 1: DriveLogix Controller and Remote I/O 6-23 Example 1: DriveLogix Controller and Remote I/O 6-25 Example 3: DriveLogix Controller to Other Devices 6-29 For
6-2 Communicating with Devices on an EtherNet/IP Link Step 1: Configure the hardware ! EtherNet/IP Before you can connect the DriveLogix system to the Ethernet network, you must configure the 1788-ENBT communication daughtercard and make sure it’s properly installed in the DriveLogix controller. Refer to Access Procedures on page C-1 to understand how to gain access to the NetLinx daughtercard slot on the DriveLogix controller.
Communicating with Devices on an EtherNet/IP Link 6-3 Step 2: Configuring the AB_ETH Driver To configure the AB_ETH Ethernet communication driver perform the following steps: 1. Start RSLinx. 2. From the Communications menu, select Configure Drivers. The following window will open.
6-4 Communicating with Devices on an EtherNet/IP Link 3. Click on the arrow to the right of the Available Driver Types box. The Available Driver Types list will appear. 4. Select Ethernet Devices and click on Add/New. You will be prompted to name the driver. 5. Select the default driver name (e.g., AB_ETH-1) or type in your own name and click on OK. The Configure driver window will appear with the Station Mapping page open. 6. Click on Add New.
Communicating with Devices on an EtherNet/IP Link 6-5 7. Enter the IP address or Host Name of your 1788-ENBT module (e.g., 130.130.130.2, “Pump1”, etc.). Use of the IP address on this screen informs the controller of the daughtercard’s IP address for processes such ladder logic and I/O data exchange.
6-6 Communicating with Devices on an EtherNet/IP Link 10. Click on OK to close the Configure driver window. The new driver will appear in the list of configured drivers. (Your list will display the drivers you have configured on your workstation.) 11.
Communicating with Devices on an EtherNet/IP Link 6-7 Step 3: Configure the daughtercard as part of the system Use RSLogix 5000 programming software (Version 11 or later) to map the 1788-ENBT communication daughtercard as part of the DriveLogix system. In the Controller Organizer, add the communication daughtercard to the I/O Configuration folder. 1. In RSLogix 5000 programming software, select the I/O Configuration folder. 2.
6-8 Communicating with Devices on an EtherNet/IP Link Configuring Remote I/O The DriveLogix controller supports remote I/O over a EtherNet/IP link. Configuring I/O in a remote chassis is similar to configuring local I/O. The difference is that you must also configure the communication daughtercard (1788-ENBT) in the local chassis and the communication module in the remote chassis. Add the FLEX I/O Ethernet Adapter to the I/O Configuration 1.
Communicating with Devices on an EtherNet/IP Link 6-9 Add FLEX I/O Modules to the I/O Configuration 1. In RSLogix 5000 programming software, select 1794-AENT Ethernet adapter. 2 Right-click to select New Module and add the appropriate FLEX I/O module. 3. Specify the appropriate module settings. After you select the appropriate FLEX I/O module, the Module Properties window opens. 4. Configure the module. 5. Add additional modules as needed.
6-10 Communicating with Devices on an EtherNet/IP Link Accessing remote I/O I/O information is presented as a structure of multiple fields, which depend on the specific features of the I/O module. The name of the structure is based on the location of the I/O module in the system. Each I/O tag is automatically created when you configure the I/O module through the programming software. Each tag name follows this format: Location:SlotNumber:Type.MemberName.SubMemberName.
Communicating with Devices on an EtherNet/IP Link Device: Example Tag Names (automatically created by the software): remote adapter “FLEX_adapter” FLEX_adapter:I 6-11 FLEX_adapter:I.SlotStatusBits FLEX_adapter:I.Data FLEX_adapter:O FLEX_adapter:O.Data remote “input1” in slot 0 direct connection FLEX_adapter:0:C FLEX_adapter:0:C.Config FLEX_adapter:0:C.Filter0_00_11 FLEX_adapter:0:C.Filter1_00_11 FLEX_adapter:0:C.Filter2_00_11 FLEX_adapter:0:C.Filter3_12_15 FLEX_adapter:0:C.
6-12 Communicating with Devices on an EtherNet/IP Link Device: Example Tag Names (automatically created by the software): remote “output1” in slot 1 FLEX_adapter:1:C direct connection FLEX_adapter:1:C.SSDate FLEX_adapter:1:I FLEX_adapter:1:I.Fault FLEX_adapter:1:O FLEX_adapter:1:O.Data remote “input2” in slot 2 FLEX_adapter:2:C rack-optimized connection FLEX_adapter:2:C.Config FLEX_adapter:2:C.Filter0_00_11 These tags are created as aliases into the FLEX_adapter:I tag FLEX_adapter:2:C.
Communicating with Devices on an EtherNet/IP Link Sending Messages 6-13 The DriveLogix controller can send MSG instructions to other controllers over an EtherNet/IP link. Each MSG instruction requires you to specify a target and an address within the target.
6-14 Communicating with Devices on an EtherNet/IP Link Connected messages are unscheduled connections on EtherNet/IP. If a MSG instruction uses a connection, you have the option to leave the connection open (cache) or close the connection when the message is done transmitting. If you: Then: Cache the connection The connection stays open after the MSG instruction is done. This optimizes execution time. Opening a connection each time the message executes increases execution time.
Communicating with Devices on an EtherNet/IP Link 6-15 Communicating with other controllers over EtherNet/IP The DriveLogix controller also uses MSG instructions to communicate with PLC and SLC controllers. The MSG instructions differ depending on which controller initiates the instruction.
6-16 Communicating with Devices on an EtherNet/IP Link Type of MSG Instruction: Supported Source File Types: DriveLogix writes In the DriveLogix controller, select one of these data to PLC-2 types: Supported Destination File Types: Use the PLC-2 compatibility file.
Communicating with Devices on an EtherNet/IP Link 6-17 The DriveLogix controller can send typed or word-range commands to PLC-5 controllers. These commands read and write data differently. The following diagrams show how the typed and word-range commands differ.
6-18 Communicating with Devices on an EtherNet/IP Link Mapping addresses The programming software includes a PLC/SLC mapping tool which allows you to make an existing controller array tag in the local controller available to PLC-2, PLC-3, PLC-5, or SLC controllers. To map addresses: 1. From the Logic menu, select Map PLC/SLC Messages. 2. Specify this information: For: In this field: Specify: For example: Type the file number of the data table in the PLC/SLC controller.
Communicating with Devices on an EtherNet/IP Link 6-19 The following table shows example source and destination tags and elements for different controller combinations.
6-20 Communicating with Devices on an EtherNet/IP Link Producing and Consuming Data The DriveLogix controller supports the ability to produce (broadcast) and consume (receive) system-shared tags over an EtherNet/IP link. Produced and consumed data is accessible by multiple controllers over an Ethernet network. The controller sends or receives data at a predetermined RPI rate. Produced and consumed tags must be controller-scoped tags of DINT or REAL data type, or in an array or structure.
Communicating with Devices on an EtherNet/IP Link 6-21 Size limit of a produced or consumed tag A produced or consumed tag can be as large as 488 bytes, but it must also fit within the bandwidth of the EtherNet/IP network. Producing a tag Produced data must be of DINT or REAL data type or a structure. You can use a user-defined structure to group BOOL, SINT, and INT data to be produced. To create a produced tag: 1. You must be programming offline. 2.
6-22 Communicating with Devices on an EtherNet/IP Link Consuming a tag A consumed tag represents data that is produced (broadcast) by one controller and received and stored by the consuming controller. To create a consumed tag: 1. You must be programming offline. 2. In the controller organizer, double-click the Controller Tags folder and then click the Edit Tags tab. 3. Select the tag that you want to consume, or enter a new tag, and display the Tag Properties dialog box. 4.
Communicating with Devices on an EtherNet/IP Link Guidelines for Configuring Connections 6-23 Each 1788-ENBT communication daughtercard supports 32 I/O connections. How you configure these connections determines how many devices the daughtercard can support. If you have two communication daughtercards, use one for communication and the other for remote I/O. While one daughtercard can support both functions, performance can improve by separating these functions onto separate daughtercards.
6-24 Communicating with Devices on an EtherNet/IP Link One chassis can have a combination of some modules configured as a direct connection and others as rack optimized. Example 1: Total connections required by DriveLogix1 The following table calculates the connections used in this example.
Communicating with Devices on an EtherNet/IP Link Example 2: DriveLogix Controller to DriveLogix Controller 6-25 In the following example, one DriveLogix controller communicates with another DriveLogix controller over EtherNet/IP. Each DriveLogix controller has its own local I/O Distributed control EtherNet/IP ! EtherNet/IP ! EtherNet/IP workstation DriveLogix1 DriveLogix2 1,1,2,xxx.xxx.xxx.xxx,1,0 1,1,2,xxx.xxx.xxx.
6-26 Communicating with Devices on an EtherNet/IP Link 3. Configure the MSG instruction. On the Configuration tab: For this item: Specify: Message Type CIP Data Table Read or CIP Data Table Write Source Tag Tag containing the data to be transferred Number of Elements Number of array elements to transfer Destination Tag Tag to which the data will be transferred 4. On the Communication tab, specify the communication path. A communication path requires pairs of numbers.
Communicating with Devices on an EtherNet/IP Link 6-27 Example 2: Producing and consuming tags Produced data must be of DINT or REAL data type or an array or structure. You can use a user-defined structure to group BOOL, SINT, and INT data to be produced. You can produce a base, alias, or consumed tag. The consumed tag must have the same data type as the produced tag in the originating controller. The controller performs type checking to ensure proper data is being received.
6-28 Communicating with Devices on an EtherNet/IP Link Each produced tags requires one connection for the producing controller and an additional connection for each consuming controller. Each consumed tag requires one connection. Example 2: Total connections required by DriveLogix1 The following table calculates the connections used in this example.
Communicating with Devices on an EtherNet/IP Link Example 3: DriveLogix Controller to Other Devices 6-29 In the following example, one DriveLogix controller communicates with a Logix5550 controller and an Ethernet PLC-5 controller over EtherNet/IP.
6-30 Communicating with Devices on an EtherNet/IP Link Type of Logix MSG instruction: Source: Destination: Typed Write SINT or INT tag any integer element (such as B3:0, T4:0.ACC, C5:0.ACC, N7:0, etc.) REAL tag any floating point element (such as F8:0, PD10:0.SP, etc.) Word Range Read any data type (such as B3:0, T4:0, C5:0, R6:0, N7:0, F8:0, etc.) SINT, INT, DINT, or REAL Word Range Write SINT, INT, DINT, or REAL any data type (such as B3:0, T4:0, C5:0, R6:0, N7:0, F8:0, etc.
Chapter 7 Communicating with Devices on a ControlNet Link Using This Chapter Configuring Your System for a ControlNet Link 1 For information about: See page Configuring your system for a ControlNet link 7-1 Configuring remote I/O 7-5 Sending messages 7-11 Producing and consuming data 7-17 Guidelines for configuring connections 7-21 Example 1: DriveLogix controller and remote I/O 7-22 Example 2: DriveLogix controller to DriveLogix controller 7-24 Example 3: DriveLogix controller to othe
7-2 Communicating with Devices on a ControlNet Link Step 1: Configure the hardware Before you can connect the DriveLogix system to the ControlNet network, you must configure the 1788-CNx communication daughtercard and make sure it’s properly installed in the DriveLogix controller.Refer to Access Procedures on page C-1 to understand how to gain access to the NetLinx daughtercard slot on the DriveLogix controller.
Communicating with Devices on a ControlNet Link 7-3 Step 2: Configure the communication driver Use RSLinx software to configure the ControlNet communication driver. Select the appropriate communication driver for the communication daughtercard in your workstation. 1. In RSLinx software, select Configure Driver. Select the appropriate driver. The installation instructions for the communications daughtercard should identify which communication driver to install. 2. Specify the appropriate settings.
7-4 Communicating with Devices on a ControlNet Link Step 3: Configure the daughtercard as part of the system Use RSLogix 5000 programming software to map the 1788-CNx communication daughtercard as part of the DriveLogix system. In the Controller Organizer, add the communication daughtercard to the I/O Configuration folder. 1. In RSLogix 5000 programming software, select the I/O Configuration folder. 2 Right-click to select New Module and add a 1788-CNx communication daughtercard. 4.
Communicating with Devices on a ControlNet Link Configuring Remote I/O 7-5 The DriveLogix controller supports remote I/O over a ControlNet link. Configuring I/O in a remote chassis is similar to configuring local I/O. The difference is that you must also configure the communication daughtercard (1788-CNx) in the local chassis and the communication module in the remote chassis. To configure a remote I/O module: 1. In the Controller Organizer, select the I/O Configuration Folder.
7-6 Communicating with Devices on a ControlNet Link 3. In the Controller Organizer, select the local 1788-CNx communication daughtercard you just added. Add and configure the remote communication module (1794-ACN15 in this example) 5. Add and configure the remote I/O modules on the remote communication module you just added. The local daughtercard becomes the “parent module” to the remote module.
Communicating with Devices on a ControlNet Link 7-7 Accessing remote I/O I/O information is presented as a structure of multiple fields, which depend on the specific features of the I/O module. The name of the structure is based on the location of the I/O module in the system. Each I/O tag is automatically created when you configure the I/O module through the programming software. Each tag name follows this format: Location:SlotNumber:Type.MemberName.SubMemberName.
7-8 Communicating with Devices on a ControlNet Link Device: Example Tag Names (automatically created by the software): remote adapter “FLEX_adapter” FLEX_adapter:I FLEX_adapter:I.SlotStatusBits FLEX_adapter:I.Data FLEX_adapter:O FLEX_adapter:O.Data remote “input1” in slot 0 direct connection FLEX_adapter:0:C FLEX_adapter:0:C.Config FLEX_adapter:0:C.Filter0_00_11 FLEX_adapter:0:C.Filter1_00_11 FLEX_adapter:0:C.Filter2_00_11 FLEX_adapter:0:C.Filter3_12_15 FLEX_adapter:0:C.
Communicating with Devices on a ControlNet Link Device: Example Tag Names (automatically created by the software): remote “output1” in slot 1 FLEX_adapter:1:C direct connection 7-9 FLEX_adapter:1:C.SSDate FLEX_adapter:1:I FLEX_adapter:1:I.Fault FLEX_adapter:1:O FLEX_adapter:1:O.Data remote “input2” in slot 2 FLEX_adapter:2:C rack-optimized connection FLEX_adapter:2:C.Config FLEX_adapter:2:C.Filter0_00_11 These tags are created as aliases into the FLEX_adapter:I tag FLEX_adapter:2:C.
7-10 Communicating with Devices on a ControlNet Link Scheduling the ControlNet Network Use RSNetWorx software to schedule the ControlNet network. The controller project must already be downloaded from RSLogix 5000 programming software to the controller and the controller must be in Program or Remote Program mode. 1. In RSNetWorx software, go online, enable edits, and survey the network. 2. Specify the network update time (NUT) The default NUT is 5ms.
Communicating with Devices on a ControlNet Link Sending Messages 7-11 The DriveLogix controller can send MSG instructions to other controllers over a ControlNet link. Each MSG instruction requires you to specify a target and an address within the target.
7-12 Communicating with Devices on a ControlNet Link Connected messages are unscheduled connections on ControlNet. If a MSG instruction uses a connection, you have the option to leave the connection open (cache) or close the connection when the message is done transmitting. If you: Then: Cache the connection The connection stays open after the MSG instruction is done. This optimizes execution time. Opening a connection each time the message executes increases execution time.
Communicating with Devices on a ControlNet Link 7-13 Communicating with other controllers over ControlNet The DriveLogix controller also uses MSG instructions to communicate with PLC and SLC controllers. The MSG instructions differ depending on which controller initiates the instruction.
7-14 Communicating with Devices on a ControlNet Link Type of MSG Instruction: Supported Source File Types: DriveLogix writes In the DriveLogix controller, select one of these data to PLC-2 types: Supported Destination File Types: Use the PLC-2 compatibility file.
Communicating with Devices on a ControlNet Link 7-15 The DriveLogix controller can send typed or word-range commands to PLC-5 controllers. These commands read and write data differently. The following diagrams show how the typed and word-range commands differ.
7-16 Communicating with Devices on a ControlNet Link 1. From the Logic menu, select Map PLC/SLC Messages. 2. Specify this information: For: In this field: Specify: For example: Type the file number of the data table in the PLC/SLC controller. 10 Tag Name Type the array tag name the local controller uses to refer to the PLC/SLC data table address. The tag must be an integer array (SINT, INT, or DINT) that is large enough for the message data.
Communicating with Devices on a ControlNet Link Type of MSG Instruction: Example Source and Destination: PLC-2 writes to DriveLogix source element 010 destination tag 200 7-17 The destination tag is the three-digit PLC-2 address you specified for PLC-2 mapping.
7-18 Communicating with Devices on a ControlNet Link The producer and consumer must be configured correctly for the specified data to be shared. A produced tag in the producer must be specified exactly the same as a consumed tag in the consumer. If any produced/consumed tag between a producer and consumer is not specified correctly, none of the produced/consumed tags for that producer and consumer will be transferred.
Communicating with Devices on a ControlNet Link 7-19 • For a ControlNet bridge module (CNB) in a remote chassis, select the most efficient communication format for that chassis:. Are most of the modules in the chassis non-diagnostic, digital I/O modules? Then select this communication format for the remote communication module: yes rack optimization no none The Rack Optimization format uses an additional 8 bytes for each slot in its chassis.
7-20 Communicating with Devices on a ControlNet Link The consumed tag in a receiving controller must have the same data type as the produced tag in the originating controller. The controller performs type checking to ensure proper data is being received. Produced tags require connections. The number of connections depends on how many controllers are consuming the tags. The controller requires one connection for the produced tag and the first consumer.
Communicating with Devices on a ControlNet Link 7-21 To consume data from a remote controller, use RSNetWorx software to schedule the connection over the ControlNet network. The produced tag in the originating DriveLogix controller must have the same data type as the consumed tag in the other DriveLogix controller. The DriveLogix controller performs type checking to ensure proper data is being received.
7-22 Communicating with Devices on a ControlNet Link Determining the API The API (actual packets per interval) is related to the RPI for the connection and the NUT of the network.
Communicating with Devices on a ControlNet Link 7-23 Example 1: Controlling remote devices This example has DriveLogix1 controlling the I/O connected to the remote 1794-ACN15 module. The data the DriveLogix controller receives from the remote I/O modules depends on how you configure the remote I/O modules. You can configure each module as a direct connection or as rack optimized. One chassis can have a combination of some modules configured as a direct connection and others as rack optimized.
7-24 Communicating with Devices on a ControlNet Link Example 2: DriveLogix Controller to DriveLogix Controller In the following example, one DriveLogix controller communicates with another DriveLogix controller over ControlNet. Each DriveLogix controller has its own local I/O Distributed control ControlNet workstation DriveLogix1 DriveLogix2 Example 2: Sending a MSG instruction To send a MSG from DriveLogix1 to DriveLogix2: 1.
Communicating with Devices on a ControlNet Link 7-25 3. Configure the MSG instruction. On the Configuration tab: For this item: Specify: Message Type CIP Data Table Read or CIP Data Table Write Source Tag Tag containing the data to be transferred Number of Elements Number of array elements to transfer Destination Tag Tag to which the data will be transferred 4. On the Communication tab, specify the communication path. A communication path requires pairs of numbers.
7-26 Communicating with Devices on a ControlNet Link The consumed tag must have the same data type as the produced tag in the originating controller. The controller performs type checking to ensure proper data is being received.
Communicating with Devices on a ControlNet Link 7-27 Example 2: Total connections required by DriveLogix1 The following table calculates the connections used in this example.
7-28 Communicating with Devices on a ControlNet Link Example 3: DriveLogix Controller to Other Devices In the following example, one DriveLogix controller communicates with a Logix5550 controller and a ControlNet PLC-5 controller over ControlNet.
Communicating with Devices on a ControlNet Link 7-29 Type of Logix MSG instruction: Source: Destination: Typed Write SINT or INT tag any integer element (such as B3:0, T4:0.ACC, C5:0.ACC, N7:0, etc.) REAL tag any floating point element (such as F8:0, PD10:0.SP, etc.) Word Range Read any data type (such as B3:0, T4:0, C5:0, R6:0, N7:0, F8:0, etc.) SINT, INT, DINT, or REAL Word Range Write SINT, INT, DINT, or REAL any data type (such as B3:0, T4:0, C5:0, R6:0, N7:0, F8:0, etc.
7-30 Communicating with Devices on a ControlNet Link Producing and consuming tags with a ControlNet PLC-5 controller depends on the type of data. ControlLogix controller (Control1) ControlNet ControlNet PLC-5 controller (PLC5C1) DriveLogix1 TagA DriveLogix controller (DriveLogix2) DINT Producing a tag to a ControlNet PLC-5 controller To produce a tag that a ControlNet PLC-5 controller can consume: 1. Determine the type of data to produce? If: And you are producing: INT na Then: A.
Communicating with Devices on a ControlNet Link 7-31 2. In RSNetWorx software, open the ControlNet configuration for the target ControlNet PLC-5 controller, insert a Receive Scheduled Message and enter the following Message size: If the produced tag contains: Then, for the Message size, enter: INTs The number of integers in the produced tag DINTs Two times the number of DINTs or REALs in the produced tag. For example, if the produced tag contains 10 DINTs, enter 20 for the Message size. REALs 3.
7-32 Communicating with Devices on a ControlNet Link 4. Create a consumed tag with the following properties: For this tag property: Type or select: Tag Type Consumed Controller The ControlNet PLC-5 that is producing the data Remote Instance The message number from the ControlNet configuration of the ControlNet PLC-5 controller RPI A power of two times the NUT of the ControlNet network. For example, if the NUT is 5ms, select an RPI of 5, 10, 20, 40, etc.
Communicating with Devices on a ControlNet Link 7-33 You can configure the 1756-CNB module to use no connection. This is useful if you configure all direct connections to their associated I/O modules and do not need a rack-optimized connection.
7-34 Communicating with Devices on a ControlNet Link Notes: Publication 20D-UM002C-EN-P - November 2003
Chapter 8 Communicating with Devices on a DeviceNet Link Using This Chapter Configuring Your System for a DeviceNet Link 1 For information about: See page Configuring your system for a DeviceNet link 8-1 Placing DeviceNet devices 8-5 Accessing DeviceNet devices 8-6 Placing the communication card in Run mode 8-9 Example 1: DriveLogix controller and DeviceNet devices 8-10 Example 2: Using a 1788-CN2DN Linking Device 8-11 For the DriveLogix controller to operate on a DeviceNet network, you
8-2 Communicating with Devices on a DeviceNet Link Step 1: Install the hardware Before you can connect the DriveLogix system to the DeviceNet network, you must configure the 1788-DNBO communication card and make sure it’s properly installed in the DriveLogix controller. Refer to Access Procedures on page C-1 to understand how to gain access to the NetLinx daughtercard slot on the DriveLogix controller.
Communicating with Devices on a DeviceNet Link 8-3 Step 2: Configure the daughtercard as part of the system Use RSLogix 5000 programming software to map the 1788-DNBO card as part of the DriveLogix system. In the Controller Organizer, add the card to the I/O Configuration folder. 1. In RSLogix 5000 programming software, select the I/O Configuration folder. 2 Right-click to select New Module and add a 1788-DNBO communication daughtercard. 4. Specify slot number 1 for the communication card.
8-4 Communicating with Devices on a DeviceNet Link Step 3: Define the DeviceNet scanlist Use RSNetWorx for DeviceNet to create a scanlist of the DeviceNet devices connected to the 1788-DNBO card. If the DriveLogix controller is powered-up while connected to the 1788-DNBO card, the controller project does not have to be downloaded from RSLogix 5000 programming software to the controller and the controller must be in Program or Remote Program mode. 1.
Communicating with Devices on a DeviceNet Link Placing DeviceNet Devices 8-5 Use RSNetWorx for DeviceNet to configure a scan list for the 1788-DNBO card. The scanlist and the associated input/output data tables set up the data you want the controller to send to and receive from the card. 1. In RSNetWorx software, go online, enable edits, and survey the network. 2. Double-click the 1788-DNBO card and use the Module tab to configure the card. Upload the network information when prompted. 3.
8-6 Communicating with Devices on a DeviceNet Link Defining the data blocks How you configure the DeviceNet devices determines how many words you use per device. The 1788-DNBO card supports a maximum of: • 124 32-bit words of input data • 123 32-bit words of output data • 32 32-bit words of status data Once you define the scanlist, you define how the data for the devices maps into the input, output, and status data blocks.
Communicating with Devices on a DeviceNet Link 8-7 automatically created when you configure the I/O module through the programming software. Each tag name follows this format: Location:SlotNumber:Type.MemberName.SubMemberName.
8-8 Communicating with Devices on a DeviceNet Link The rack-optimized connection creates a DINT element for mapped data for each DeviceNet module connected to the card “dnet.” The array dnet:I.Data contains the possible input elements; the dnet.O.Data contains the possible output elements. The index number on the array element refers to the same numbered word mapped to the device in RSNetWorx for DeviceNet. Depending on the device, there can be several words mapped to on device.
Communicating with Devices on a DeviceNet Link Placing the Communication Card in Run Mode 8-9 To place the 1788-DNBO daughtercard in Run mode, your program logic needs to set the CommandRegister.Run bit in the output word for the 1788-DNBO card.
8-10 Communicating with Devices on a DeviceNet Link Example 1: DriveLogix Controller and DeviceNet Devices In the following example, one DriveLogix controller controls remote DeviceNet devices through a 1788-DNBO card.
Communicating with Devices on a DeviceNet Link 8-11 In the following example, one DriveLogix controller controls remote DeviceNet devices through a 1788-CN2DN linking device. Example 2: Using a 1788-CN2DN Linking Device 1788-CN2DN linking device ControlNet DriveLogix controller DeviceNet ControlLogix controller with 1756-DNB PanelView terminal 1794-ADN with FLEX I/O modules This example has a DriveLogix controller controlling three DeviceNet devices through the linking device.
8-12 Communicating with Devices on a DeviceNet Link The rack-optimized connection creates a DINT element for mapped data for each DeviceNet module connected to the linking device “cnet_2_dnet.” The array cnet_2_dnet:I.Data contains the possible input elements; the cnet_2_dnet.O.Data contains the possible output elements. The index number on the array element refers to the same numbered word mapped to the device in RSNetWorx for DeviceNet.
Communicating with Devices on a DeviceNet Link 8-13 • RSNetWorx for DeviceNet software to configure the 1788-CN2DN device on the DeviceNet network Placing DeviceNet devices The linking device supports 124, 32-bit words each of input data, output data, and status data. How you configure the DeviceNet devices determines how many words you use per device. Most DeviceNet devices support 16-bit words. Take care how you map these into the 32-bit words used in RSLogix 5000 programming software.
8-14 Communicating with Devices on a DeviceNet Link Notes: Publication 20D-UM002C-EN-P - November 2003
Chapter 9 Communicating with Devices on a Serial Link Using This Chapter For information about: See page Configuring your system for a serial link 9-1 Example 1: workstation directly connected to a DriveLogix controller 9-8 Example 2: workstation remotely connected to a DriveLogix controller 9-9 Example 3: DriveLogix controller communicating with a bar code reader 9-14 IMPORTANT Configuring Your System for a Serial Link 1 Limit the length of serial (RS-232) cables to 15.2m (50 ft.).
9-2 Communicating with Devices on a Serial Link Step 1: Configure the hardware The RS-232 port is an isolated serial port built-in to the front of the controller. Refer to Access Procedures on page C-1 to understand how to gain access to the front of the DriveLogix controller. Serial Port To connect to the serial port: 1. Select the appropriate cable. The 1756-CP3 cable attaches the controller directly to the controller.
Communicating with Devices on a Serial Link 9-3 2. Connect the cable to the serial port on the controller.. TIP Remember to route cable through sliding access panel at the bottom of the Control Assembly.
9-4 Communicating with Devices on a Serial Link Step 2: Configure the serial port of the controller 1. In RSLogix 5000 programming software, select the Controller folder. Right-click to select Properties. 3. On the System Protocol tab, select the appropriate DF1 communication mode for point-to-point or master/slave communications. Or on the User Protocol tab, select ASCII to communicate with an ASCII device.
Communicating with Devices on a Serial Link Characteristic: Description (default is shown in bold): Data bits Specifies the number of bits per message packet. 9-5 Select 8. Stop bits Specifies the number of stop bits to the device with which the controller is communicating. Select 1 or 2. Control line Specifies the mode in which the serial driver operates. Select No Handshake, Full-Duplex, Half-Duplex with Continuous Carrier, or Half-Duplex without Continuous Carrier.
9-6 Communicating with Devices on a Serial Link Use this mode: For: See page: DF1 master mode control of polling and message transmission between the master and slave nodes. 9-11 The master/slave network includes one controller configured as the master node and as many as 254 slave nodes. Link slave nodes using modems or line drivers. A master/slave network can have node numbers from 0-254. Each node must have a unique node address.
Communicating with Devices on a Serial Link 9-7 Step 3: Configure the communication driver Use RSLinx software to configure the serial communication driver. Select the “DF1” driver. 1. In RSLinx software, select Communication →Configure Driver. From the Available Driver Types list, select”RS-232 DF1 Devices“. Click Add New. 2. Specify a name for the driver Click OK. 3. Specify the appropriate communication settings. Click OK.
9-8 Communicating with Devices on a Serial Link Example 1: Workstation Directly Connected to a DriveLogix Controller In the following example, a workstation directly connects to a DriveLogix controller over a serial link. This is useful for downloading a controller project directly to the controller. serial Use RSLogix 5000 programming software to configure the controller’s serial port for the DF1 point-to-point (full-duplex) protocol.
Communicating with Devices on a Serial Link This field: Description: Embedded response Specifies how to enable embedded responses. 9-9 Select Autodetect (enabled only after receiving one embedded response) or Enabled. The default is Autodetect. Error detection Select BCC or CRC error detection. Configure both stations to use the same type of error checking. BCC: the controller sends and accepts messages that end with a BCC byte for error checking.
9-10 Communicating with Devices on a Serial Link the serial port of the controller for either the DF1 master or DF1 slave protocol (both half-duplex). Master/slave communication methods A master station can communicate with a slave station in two ways: Name: This method: Benefits: standard communication mode Initiates polling packets to slave stations according to their position in the polling array(s). This communication method is most often used for point-to-multipoint configurations.
Communicating with Devices on a Serial Link 9-11 Configuring a DF1 slave station This field: Description: Station address The station address for the serial port on the DF1 slave. Enter a valid DF1 address (0-254). Address 255 is reserved for broadcast messages. The default is 0. Transmit retries The number of times the remote station retries a message after the first attempt before the station declares the message undeliverable. Enter a value 0-127. The default is 3.
9-12 Communicating with Devices on a Serial Link This field: Description: Polling mode Select one of these: • Message Based (slave cannot initiate messages) • Message Based (slave can initiate messages) - default • Standard (multiple message transfer per node scan) • Standard (single message transfer per node scan) Master transmit Standard polling modes only Select when the master station sends messages: • between station polls (default) • in polling sequence Normal poll node tag Standard polling m
Communicating with Devices on a Serial Link This field: Description: Active station tag Standard polling modes only 9-13 An array that stores a flag for each of the active stations on the DF1 link. Both the normal poll array and the priority poll array can have active and inactive stations. A station becomes inactive when it does not respond to the master’s poll. Create a single-dimension array of data type SINT that has 32 elements (256 bits). This tag must be controller-scoped.
9-14 Communicating with Devices on a Serial Link Example 3: DriveLogix Controller to a Bar Code Reader Publication 20D-UM002C-EN-P - November 2003 In the following example, a workstation connects to a bar code reader. A bar code reader is an ASCII device, so you configure the serial port differently than in the previous examples. Configure the serial port for user mode, rather than a DF1 mode.
Communicating with Devices on a Serial Link 9-15 Connect the ASCII device to the controller To connect the ASCII device to the serial port of the controller: 1. For the serial port of the ASCII device, determine which pins send signals and which pins receive signals. 2.
9-16 Communicating with Devices on a Serial Link Configuring user mode This field: Description: Buffer size Specify the maximum size (in bytes) of the data array you plan to send and receive. The default is 82 bytes. Termination characters Specify the characters you will use to designate the end of a line. The default characters are ‘$r’ and ‘$FF’. Append characters Specify the characters you will append to the end of a line. The default characters are ‘$r’ and ‘$l’.
Chapter 10 Communicating with Devices on a DH-485 Link Using This Chapter The DH-485 protocol uses RS-485 half-duplex as its physical interface. (RS-485 is a definition of electrical characteristics; it is not a protocol.) You can configure the RS-232 port of the DriveLogix controller to act as an DH-485 interface.
10-2 Communicating with Devices on a DH-485 Link page C-1 to understand how to gain access to the front of the DriveLogix controller. RS-485 port port 2: mini-DIN 8 RS-232 baud rate selector switch port 1: DB-9 RS-232, DTE dc power source selector switch terminals for external 24V dc power supply Connect the serial port of the DriveLogix controller to either port 1 or port 2 of the 1761-NET-AIC converter. Use the RS-485 port to connect the converter to the DH-485 network.
Communicating with Devices on a DH-485 Link 10-3 Step 2: Configure the DH-485 port of the controller 1. In RSLogix 5000 programming software, select the Controller folder. Right-click to select Properties. 3. On the Serial Port tab, specify the appropriate communication settings. The grayed out settings are selections that do not apply to a DH-485 network.
10-4 Communicating with Devices on a DH-485 Link Specify these characteristics on the Serial Port tab (default values are shown in bold): Characteristic: Description (default is shown in bold): Baud Rate Specifies the communication rate for the DH-485 port. All devices on the same DH-485 network must be configured for the same baud rate. Select 9600 or 19200 Kbps. Node Address Specifies the node address of the DriveLogix controller on the DH-485 network. Select a number 1-31 decimal, inclusive.
Communicating with Devices on a DH-485 Link 10-5 If no network activity occurs, the initiator sends the token pass packet again. After two retries (a total of three tries) the initiator attempts to find a new successor. IMPORTANT The maximum address that the initiator searches for before starting again with zero is the value in the configurable parameter “maximum node address.” The default value for this parameter is 31 for all initiators and responders.
10-6 Communicating with Devices on a DH-485 Link The maximum node address should be the same for all devices on a DH-485 network for optimal operation. The best network performance occurs when node addresses start at 0 and are assigned in sequential order. The controller defaults to node address 1 (controllers cannot be node 0). Initiators, such as personal computers, should be assigned the lowest numbered addresses to minimize the time required to initialize the network.
Communicating with Devices on a DH-485 Link 10-7 Single Cable Connection Orange Wire with White Stripe (OR/WH) Shrink Tubing (Recommended) White Wire with Orange Stripe (WH/OR) Belden 3106A or 9842 Cable (3106A Shown) tion ina erm A T 6 ta a 5 D ta B a n 4 D mmo o nd 3 C ield Grou h sis S 2 as h 1C Blue Wire (BU) Drain Wire (Shield) Connections Using Belden 3106 Cable The table and schematic diagram below shows wire/terminal connections for Belden 3106A cable.
10-8 Communicating with Devices on a DH-485 Link Connections Using Belden 9842 Cable The table and schematic diagram below shows wire/terminal connections for Belden 9842 cable.
Communicating with Devices on a DH-485 Link 10-9 Grounding and terminating a DH-485 network You must terminate the network at the first and last PHYSICAL devices, by connecting pin 6 (Termination) to pin 5 (Data A). You must ground the network at the first PHYSICAL device by connecting pin 1 (Chassis Ground) to pin 2 (Shield).
10-10 Communicating with Devices on a DH-485 Link network. In addition, an SLC 5/03 controller uses a 1747-AIC converter to connect to the same DH-485 network. DH-485 Network 1761-NET-AIC 1761-NET-AIC 1747-AIC 1747-CP3 or 1761-CBL-AP00 Cable 1747-CP3 or 1761-CBL-AP00 Cable 1747-C11 Cable SLC 5/503 Controller ControlLogix Controller DriveLogix Controller On the DH-485 network, the DriveLogix controller can send and receive messages to and from other controllers on the network.
11 Chapter Communicating with Devices on a Third-Party Link Using This Chapter Configuring Your System for a Third-Party Link For information about: See page Configuring Your System for a Third-Party Link 9-1 For the DriveLogix controller to operate on a third-party network, you need: • a 1788-MODULE generic module communication daughtercard.
11-2 Communicating with Devices on a Third-Party Link Step 1: Install the hardware Before you can connect the DriveLogix system to the third-party network, you must configure the 1788-MODULE communication card and make sure it is properly installed in the DriveLogix controller. Refer to Access Procedures on page C-1 to understand how to gain access to the NetLinx daughtercard slot on the DriveLogix controller. Remember which slot you use for which communication card.
Communicating with Devices on a Third-Party Link 11-3 1. In RSLogix 5000 programming software, select the I/O Configuration folder. 2 Right-click to select New Module and add a 1788-MODULE communication daughtercard. 3. Specify the appropriate communication settings. 4. Specify the module’s properties. For more information on communications format the connection parameters, see the next section.
11-4 Communicating with Devices on a Third-Party Link Communication Format The Communication Format field chooses a data type for information transmitted between the controller and a remote device connected to the 1788-MODULE communication card. This format creates an array in the controller of whatever data type you choose for the input and output data. Connection Parameters You must set connection parameters to define data identification and connection size.
12 Chapter DriveLogix Back-Up on DeviceNet Using This Chapter For information about: See page How the Back-up Works 12-2 Power-Up and System Start-up 12-4 Developing the DriveLogix Back-Up Application 12-6 Using Indicators to Check Status 12-13 Development and Debugging Tips 12-13 This chapter offers a solution to back-up your DriveLogix controller on DeviceNet.
12-2 DriveLogix Back-Up on DeviceNet How the Back-up Works Figure 11.2 shows an example back-up system. In the back-up system, the following occurs: • Both controllers/scanners simultaneously receive all inputs. • Both controllers execute in parallel but are NOT synchronized. • Only the primary controllers sends output data to the I/O devices. A virtual switch in the 1788-DNBO cards is used to switch outputs between primary and secondary controllers.
DriveLogix Back-Up on DeviceNet 12-3 Requirements of the Back-Up The DriveLogix Back-Up on DeviceNet solution requires that you use the following: • RSLogix 5000, version 10 or higher • 2 DriveLogix controllers, firmware revision 10.x or higher • 2 1788-DNBO communication cards, firmware revision 2.x or higher IMPORTANT Many applications use multiple communications cards in a DriveLogix controller to communicate with several networks.
12-4 DriveLogix Back-Up on DeviceNet Power-Up and System Start-up To configure a DriveLogix Back-up system on DeviceNet, you can take the following steps. Some of these steps are described in greater detail in the rest of the appendix. 1. Install all I/O and operator interfaces that you need to back-up on DeviceNet. We recommend that you reserve node addresses 0 and 1 for the two DriveLogix controllers used in the back-up.
DriveLogix Back-Up on DeviceNet 12-5 9. Connect the other DriveLogix controller with a 1788-DNBO scanner on the network. 10. Set the node address to 0. 11. Power-up the controller and scanner. 12. Use RSNetWorx for DeviceNet to download the same scanlist used in step 5. It may be necessary to browse the network again before downloading the scanlist.
12-6 DriveLogix Back-Up on DeviceNet Developing the DriveLogix Back-Up Application The DriveLogix back-up is enabled from an RSLogix 5000 user program with a few simple ladder rungs (or equivalent).
DriveLogix Back-Up on DeviceNet 12-7 Setting the Heartbeat Constant You can set the heartbeat constant with five rungs of ladder logic. Figure 11.3 shows rungs 0 & 1 and the message set-up used in rung 1. The message in rung 1 uses the INT data type. Figure 11.
12-8 DriveLogix Back-Up on DeviceNet Figure 11.4 shows rung 2 and the message set-up used on it. The message in rung 2 uses the INT data type. Figure 11.
DriveLogix Back-Up on DeviceNet 12-9 Figure 11.5 shows rungs 3 & 4 and the message set-up used on it. The message in rung 3 uses the INT data type. Figure 11.5 Rung 3 message configuration and communication tabs This completes the required portion of ladder logic to enable the DriveLogix back-up on DeviceNet. The following sections describe how to use additional ladder logic to read back-up state and status. However, these sections are not required to complete the back-up solution.
12-10 DriveLogix Back-Up on DeviceNet Reading Back-up State Rung You can read the back-up state of the DeviceNet scanner with a single rung of ladder logic. The back-up state is useful for debug or more sophisticated back-up schemes. The message in this rung uses the SINT data type. Figure 11.6 shows the rung you can use to read the back-up state. Figure 11.
DriveLogix Back-Up on DeviceNet 12-11 Table 11.1 describes the possible values this message may return when reading the back-up state of the DeviceNet scanner. Table 11.1 If the message reads this value: the back-up state of the DeviceNet scanner is: 0 Disabled 1 Primary scanner 2 Back-up scanner 3 Invalid primary node address (e.g. the node address cannot be 62 or 63) 4 Faulted back-up scanner - CRC failure (e.g.
12-12 DriveLogix Back-Up on DeviceNet Reading Back-up Status You can read the back-up status of the DeviceNet scanner with a single rung of ladder logic. The back-up state is useful for debugging or more sophisticated back-up schemes. The message in this rung uses the SINT data type. Figure 11.7 shows the rung you can use to read the back-up state. Figure 11.7 Rung 6 message configuration and communication tabs Table 11.
DriveLogix Back-Up on DeviceNet Using Indicators to Check Status 12-13 The 1788-DNBO card’s status indicators provide useful information (e.g. determining which controller is primary) about back-up scanner status. Table 11.3 lists the indicators to monitor when checking back-up status. Table 11.
12-14 DriveLogix Back-Up on DeviceNet output to momentarily switch between an older and newer value. If you configure the switchover time slower than the program scan and I/O update, the secondary lags behind the primary and eliminates this. • State variables, such as counters or timers are NOT synchronized. The user program must synchronize the primary and secondary controllers, typically over an EtherNet/IP or ControlNet link between controllers.
Appendix A DriveLogix System Specifications Using This Appendix For information about: See page DriveLogix Controller A-1 1756-BA1 Battery A-3 DriveLogix Controller Serial Cables A-4 DriveLogix Controller LEDs A-6 DriveLogix Controller Category: DriveLogix 5720 DriveLogix 5720 with Memory Expansion user memory 256k bytes FLEXBUS Local Rail current output 640 mA maximum @ 5.
A-2 DriveLogix System Specifications Category: DriveLogix 5720 DriveLogix 5720 with Memory Expansion Certifications: The drive is designed to meet the following specifications: (when product is marked) NFPA 70 - US National Electric Code NEMA ICS 3.1 - Safety standards for Construction and Guide for Selection, Installation and Operation of Adjustable Speed Drive Systems. NEMA 250 - Enclosures for Electrical Equipment IEC 146 - International Electrical Code.
DriveLogix System Specifications 1756-BA1 Battery A-3 The DriveLogix controller uses the 1756-BA1 battery: Battery 1756-BA1 0.
A-4 DriveLogix System Specifications DriveLogix Controller Serial Cables The RS-232 port is a non-isolated serial port built-in to the front of the controller. Serial Port To connect to the serial port, determine whether you need an optical isolator. If you connect the controller to a modem or an ASCII device, consider installing an isolator between the controller and modem or ASCII device. An isolator is also recommended when connecting the controller directly to a programming workstation.
DriveLogix System Specifications Are you using an isolator? Use this cable: No The 1756-CP3 cable attaches the controller directly to the controller. 1 CD 1 CD 2 RDX 2 RDX 3 TXD 3 TXD 4 DTR 4 DTR COMMON COMMON 6 DSR 6 DSR 7 RTS 7 RTS 8 CTS 8 CTS 9 9 A-5 If you make your own cable, it must be shielded and the shields must be tied to the metal shell (that surrounds the pins) on both ends of the cable. You can also use a 1747-CP3 cable (from the SLC product family).
A-6 DriveLogix System Specifications DriveLogix Controller LEDs Type Name Daughtercard PORT LEDs MOD NET A NET B NET A Color State Green – Yellow – Red – Red – OFF Description Status of DPI port internal communications (if present). Status of communications module (when installed). Status of network (if connected). Status of secondary network (if connected). No power, Host is faulted, NET B Red Red Green Green OFF Steady Flashing Flashing Steady Host is holding daughtercard in reset.
Appendix B Installing and Maintaining the Battery Using this Appendix Connecting the Battery For information about: See page Installing and Maintaining the Battery B-1 Storing replacement batteries B-2 Estimating battery life B-2 Replacing batteries B-3 Allen-Bradley ships the DriveLogix controller with the battery installed, but disconnected. You must connect the battary while installing the drive: 1.
B-2 Installing and Maintaining the Battery Storing Replacement Batteries Because a battery may leak potentially dangerous chemicals if stored improperly, store batteries as follows: ATTENTION ! Estimating Battery Life Store batteries in a cool, dry environment. We recommend 25° C with 40% to 60% relative humidity. You may store batteries for up to 30 days between -45° to 85° C, such as during transportation. To avoid possible leakage, do not store batteries above 60° C for more than 30 days.
Installing and Maintaining the Battery B-3 2. Determine the percentage of time that the controller is powered off per week. EXAMPLE If a controller is off: • 8 hr/day during a 5-day work week • all day Saturday and Sunday Then the controller is off 52% of the time: 1. total hours per week = 7 x 24 = 168 hours 2. total off hours per week = (5 days x 8 hrs/day) + Saturday + Sunday = 88 hours 3.
B-4 Installing and Maintaining the Battery 1. Remove the front cover of the drive’s control assembly. 2. Upload the controller’s memory and program to a computer with RSLogix 5000 programming software. 3. Turn off power to the DriveLogix controller. 4. Remove the side cover of the drive’s control assembly (not necesary for high power drives). 5. Remove drive’s control assembly, if necessary. 6.
Installing and Maintaining the Battery B-5 10. Secure the new battery by installing a new cable tie. 11. Re-install the control assembly, if removed. 12. Turn on power to the DriveLogix controller. 13. On the front of the controller, is the BATTERY LED off ? If: Then: Yes Go to the next step. No A. Check that the battery is correctly connected to the controller. B. If the BATTERY LED remains on, install another 1756-BA1 battery. C. If the BATTERY LED remains on after you complete Step B.
B-6 Installing and Maintaining the Battery Notes: Publication 20D-UM002C-EN-P - November 2003
Appendix C Access Procedures Using this Appendix 1 For information about: See page Removing Cover(s) C-2 Removing Cover (For High Power Drives) C-3 Replacing Cover(s) C-4 Replacing Cover (For High Power Drives) C-6 Publication 20D-UM002C-EN-P - November 2003
C-2 Access Procedures Removing Cover(s) Task A Description Loosen captive screw B Push down on front cover Pull front cover away from assembly C D Pull side cover forward E Lift side cover off of control assembly B E DRIVE DRIVE ENABLE SYNCHLINK Lang Auto / Man 7 8 9 4 5 1 2 3 . 0 +/- S.M.A.R.T.
Access Procedures Removing Cover (For High Power Drives) Task A Description Remove eight (8) screws B Remove power cover (top cover) C-3 (8 Screws) B A Publication 20D-UM002C-EN-P - November 2003
C-4 Access Procedures Replacing Cover(s) Task A Description Align tabs on side cover with slots on drive B Push side cover down onto control assembly C Push side cover back onto control assembly B C A Publication 20D-UM002C-EN-P - November 2003
Access Procedures Replacing Cover(s) Continued Task D Description Locate tabs on inside of front cover E Align tabs on front cover with slots on flanges F C-5 Push front cover onto drive G Push front cover up into slots H Tighten captive screw D E G F H Publication 20D-UM002C-EN-P - November 2003
C-6 Access Procedures Replacing Cover (For High Power Drives) Task A Description Install power cover (top cover) B Install eight (8) screws B (8 Screws) A Publication 20D-UM002C-EN-P - November 2003
Index Numerics 1756-BA1 B-1 1788-CN2DN 8-11 1788-CNCx 7-1 1788-DNBO 8-1 1788-ENBT 6-1 1788-MODULE 11-1 A adding local analog module 1-12 local output module 1-10 alias defining 4-16 getting started 1-17 analog module adding 1-12 ASCII protocol 9-15 B battery B-1 how to replace B-3 life B-2 storage B-2 when to replace B-2 C changing module properties 1-14 project properties 1-5 commands motion 5-12 motion event 5-12 motion group 5-12 motion move 5-12 motion state 5-12 communicating ControlNet 7-1 DeviceNe
2 accessing remote devices 7-7 communication card 7-4 communication driver 7-3 configuring the system 7-1 connection guidelines 7-21 consuming a tag 7-20 example DriveLogix Controller and Remote I/O 7-22 example DriveLogix Controller to DriveLogix Controller 7-24 example DriveLogix Controller to Other Devices 7-28 hardware 7-2 installing communication card 7-2 mapping address 7-15 message to other controller 7-13 message to other Logix-based controller 7-12 overview 7-1 produced/consumed tag 7-17 produci
3 DH-485 configuration 10-9 DriveLogix controller and remote devices over EtherNet/IP 6-23 DriveLogix Controller and Remote I/O on ControlNet 7-22 DriveLogix Controller to DriveLogix Controller on ControlNet 7-24 DriveLogix Controller to Other Devices on ControlNet 7-28 DriveLogix controller to other devices over EtherNet/IP 6-29 monitoring I/O module 4-18 monitoring rack-optimized connection 4-19 using a 1788-CN2DN linking device 8-11 F fault bit 4-17 G getting started adding a local analog module 1-1
4 controller usage 1-22 nonvolatile 2-20 message sending over ControlNet 7-11 sending over EtherNet/IP 6-13 to other controller 6-15, 7-13 to other Logix-based controller 6-14, 7-12 monitoring example logic for I/O module 4-18 example logic for rack-optmized connection 4-19 I/O module 4-16 rack-optimized connection 4-19 motion configuring 5-1 configuring host drive 5-2 motion event 5-12 motion group 5-12 motion move 5-12 motion state 5-12 programming 5-5 supported commands 5-12 system requirements 5-1 mo
5 overview 9-1 point-to-point 9-8 slave 9-11 slave/master communication 9-10 store batteries B-2 supported motion commands 5-12 system requirements motion 5-1 T tag alias 4-16 consuming 6-22, 7-20 creating 1-16 names 4-13 produced/consumed overview 6-20, 7-17 producing 6-21, 7-19 sample alias 1-17 viewing 1-15 task defining 2-3 priority 2-3 Third Party Link installing communication card 11-2 third party link configuring the system 11-1 Third-Party Link communication card 11-2 third-party link hardware
Publication 20D-UM002C-EN-P - November 2003 1 Supersedes 20D-UM002B-EN-P March 2003 Copyright © 2003 Rockwell Automation. Printed in the U.S.A.
DriveLogix System User Manual
