Rockwell Automation Allen-Bradley DriveLogix 5730 User Manual
  1. Manuals
  2. Brands
  3. Rockwell Automation Manuals
  4. Controller
  5. Allen-Bradley DriveLogix 5730
  6. User manual
Rockwell Automation Allen-Bradley DriveLogix 5730 User Manual

Rockwell Automation Allen-Bradley DriveLogix 5730 User Manual

Or powerflex 700s drives with phase ii control
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
DriveLogix™ 5730
Controller
®
for PowerFlex
700S Drives
with Phase II Control
Firmware Version
13.XX
User Manual

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Allen-Bradley DriveLogix 5730 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Rockwell Automation Allen-Bradley DriveLogix 5730

Summary of Contents for Rockwell Automation Allen-Bradley DriveLogix 5730

  • Page 1 DriveLogix™ 5730 Controller ® for PowerFlex 700S Drives with Phase II Control Firmware Version 13.XX User Manual...
  • Page 2 In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.

  • Page 3: Table Of Contents

    Table of Contents Important User Information ..........1-2 Preface Overview Who Should Use This Manual .
  • Page 4 Chapter 4 Configuring DriveLogix Motion De-energizing the Drive to Connect or Disconnect a Cable ..... . . 4-1 About this Chapter............4-1 System Requirements .
  • Page 5 Chapter 9 Communicating with Devices on a DH485 Link De-energizing the Drive to Connect or Disconnect a Cable ..... . . 9-1 Understanding How the DriveLogix5730 Controller Supports DH485 Communications 9-1 Configuring Your System for a DH-485 Link.

  • Page 7: Preface

    Preface Overview Who Should Use This This manual is intended for qualified personnel. You must be able to program and operate Adjustable Frequency AC Drive devices and Manual programmable controllers. Purpose of this Manual This manual guides the development of projects for DriveLogix controllers. It provides procedures on how to establish communications: •...

  • Page 8: Related Documentation

    Related Documentation Allen-Bradley publications are available on the internet at www.rockwellautomation.com/literature. These core documents address the Logix5000 family of controllers: If you are: Use this publication: a new user of a Logix5000 controller Logix5000 Controllers Quick Start publication 1756-QS001 This quick start provides a visual, step-by-step overview of the basic steps you need to complete to get your controller configured and running.

  • Page 9: Controller Firmware Revision

    Controller Firmware This revision on the DriveLogix 5730 User Manual corresponds to the following: Revision • version 13 and later controller firmware • version 13 and later RSLogix 5000 programming software • version 3.02 and later DriveExecutive programming software General Precautions Class 1 LED Product ATTENTION: Hazard of permanent eye damage exists when using optical transmission equipment.
  • Page 10 Notes:...

  • Page 11: Chapter 1 What Is Drivelogix5730

    Chapter What is DriveLogix5730? The DriveLogix controller is part of the Logix environment. The DriveLogix controller provides a distributed control system built on these components: • The DriveLogix5730 controller has one RS-232 port. The controller supports the Logix instructions. • RSLogix 5000 programming software that supports every Logix controller.

  • Page 12: Loading Controller Firmware

    What is DriveLogix5730? Loading Controller De-energizing the Drive to Connect or Disconnect a Cable Firmware ATTENTION: Severe injury or death can result from electrical shock or burn. Verify that the voltage on the bus capacitors has discharged before connecting to the communication ports. Measure the DC bus voltage at the +DC &...
  • Page 13 What is DriveLogix5730? The controller’s EtherNet/IP configuration settings are maintained during a flash process. If you load firmware via an EtherNet/IP connection, browse through the network port, across the virtual backplane, and select the appropriate controller. Using ControlFlash to load firmware You can use ControlFlash to load firmware through either an Ethernet connection (an IP address must already be assigned to the Ethernet port) or a serial connection.
  • Page 14 What is DriveLogix5730? Using AutoFlash to load firmware You can use AutoFlash to load firmware through either an Ethernet connection (an IP address must already be assigned to the Ethernet port) or a serial connection. 1. Make sure the appropriate network connection is made before starting. 2.

  • Page 15: Using Compactflash

    What is DriveLogix5730? Using CompactFlash The 1784-CF64 CompactFlash card provides nonvolatile memory storage for the DriveLogix5730 controller. The card stores the contents of the controller memory (program logic and tag values) and the controller firmware at the time that you store the project. Storing information to the CompactFlash card is like storing a snapshot of controller memory at a given time.

  • Page 16: Developing Programs

    What is DriveLogix5730? Developing Programs The controller operating system is a preemptive multitasking system that is IEC 1131-3 compliant. This environment provides: • tasks to configure controller execution • programs to group data and logic • routines to encapsulate executable code written in a single programming language control application controller fault handler...
  • Page 17 What is DriveLogix5730? Specifying task priorities Each task in the controller has a priority level. The operating system uses the priority level to determine which task to execute when multiple tasks are triggered. You can configure periodic tasks to execute from the lowest priority of 15 up to the highest priority of 1.
  • Page 18 What is DriveLogix5730? Task 1 Task 2 Task 3 Task 4 Time (ms) Notes: A. The highest priority task interrupts all lower priority tasks. B. The dedicated I/O task can be interrupted by tasks with priority levels 1 to 6. The dedicated I/O task interrupts tasks with priority levels 8 to 15. This task runs at the selected RPI rate scheduled for the DriveLogix5730 system (2ms in this example).

  • Page 19: Selecting A System Overhead Percentage

    What is DriveLogix5730? Each program has a main routine. This is the first routine to execute when the controller triggers the associated task and calls the associated program. Use logic, such as the Jump to Subroutine (JSR) instruction, to call other routines.
  • Page 20 1-10 What is DriveLogix5730? execute the continuous task. While increasing the system overhead percentage decreases execution time for the continuous task, it does increase communications performance. However, increasing the system overhead percentage also increases the amount of time it takes to execute a continuous task - increasing overall scan time.

  • Page 21: Understanding The Virtual Backplane

    What is DriveLogix5730? 1-11 If you increase the time slice to 20%, the system overhead interrupts the continuous task every 4 ms (of continuous task time). 1 ms 1 ms 1 ms 1 ms 1 ms system overhead 4 ms 4 ms 4 ms 4 ms...
  • Page 22 1-12 What is DriveLogix5730? Notes:...

  • Page 23: Chapter 2 Placing And Configuring The Drive

    Chapter Placing and Configuring the Drive De-energizing the Drive to Connect or Disconnect a ATTENTION: Severe injury or death can result from electrical Cable shock or burn. Verify that the voltage on the bus capacitors has discharged before connecting to the communication ports. Measure the DC bus voltage at the +DC &...

  • Page 24: Determining When The Controller Updates The Drive

    Placing and Configuring the Drive protected and must be present. If the associated links are not present, or are deleted, the communication connection between the controller and drive will be broken. The user-defined tags are made up of a fixed number of REAL (floating point) and DINT (double integer) data types.

  • Page 25: Placing And Configuring The Drive

    Placing and Configuring the Drive Placing and Configuring the When you create a project for the DriveLogix controller in RSLogix 5000, the Controller Organizer automatically displays the local DIN rail for Flex Drive I/O. You must add the PowerFlex 700S drive to the configuration, in a manner similar to adding an I/O module.
  • Page 26 Placing and Configuring the Drive Select the Major Revision. Configure the drive. Use the module properties wizard to specify characteristics for the module. Click Next to continue through the wizard. Name the drive and specify the Comm Format. Click finish when you are done. The completed module appears in the Controller Organizer.
  • Page 27 Placing and Configuring the Drive Revision You must enter the correct drive VPL firmware revision, in order to launch DriveExecutive and create the appropriate links for the selected communication format. Determine the firmware revision by viewing parameter 314 [VPL Firmware Rev] in the drive. Communication Formats The communication format determines the data structure, tag names, and required links for communication to the drive.
  • Page 28 Placing and Configuring the Drive Speed Control format. The tag structure for this example’s drive connection has the tag name of “drive_module”. 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”.
  • Page 29 Placing and Configuring the Drive Table 2.B Mapping for Position Control Communication Format Controller Output Tag Element Drive Parameter Linked Parameter LogicCommand 602 [FromDriveLogix00] 151 [Logic Command] SpeedRef1 603 [FromDriveLogix01] 10 [Speed Ref 1] PositionControl 604 [FromDriveLogix02] 740 [Position Control] CoarsePositTrgt 605 [FromDriveLogix03] 748 [CoarsePosit Trgt]...
  • Page 30 Placing and Configuring the Drive Table 2.C Mapping for Motion Control Communication Format Controller Output Tag Element Drive Parameter Linked Parameter UserDefinedRealData[0] 602 [FromDriveLogix00] User Defined UserDefinedRealData[1] 603 [FromDriveLogix01] User Defined UserDefinedRealData[2] 604 [FromDriveLogix02] User Defined UserDefinedRealData[3] 605 [FromDriveLogix03] User Defined UserDefinedRealData[4] 606 [FromDriveLogix04] User Defined...
  • Page 31 Placing and Configuring the Drive Table 2.D Mapping for User-Defined 1 Communication Format Controller Output Tag Element Drive Parameter Linked Parameter LogicCommand 602 [FromDriveLogix00] 151 [Logic Command] UserDefinedRealData[0] 603 [FromDriveLogix01] User Defined UserDefinedRealData[1] 604 [FromDriveLogix02] User Defined UserDefinedRealData[2] 605 [FromDriveLogix03] User Defined UserDefinedRealData[3] 606 [FromDriveLogix04]...
  • Page 32 2-10 Placing and Configuring the Drive Table 2.E Mapping for User-Defined 2 Communication Format Controller Output Tag Element Drive Parameter Linked Parameter LogicCommand 602 [FromDriveLogix00] 151 [Logic Command] UserDefinedRealData[0] 603 [FromDriveLogix01] User Defined UserDefinedRealData[1] 604 [FromDriveLogix02] User Defined UserDefinedRealData[2] 605 [FromDriveLogix03] User Defined UserDefinedRealData[3] 606 [FromDriveLogix04]...

  • Page 33: Inhibiting The Drive Connection

    Placing and Configuring the Drive 2-11 Inhibiting the Drive 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 Connection module. Inhibiting the drive module shuts down the connection from the controller to the drive.

  • Page 34: Using Driveexecutive Lite

    2-12 Placing and Configuring the Drive inhibit or 0 to uninhibit). Use a SSV instruction to write the Mode attribute back to the module. For example: Using DriveExecutive Lite In order to launch DriveExecutive Lite from within RSLogix 5000, the drives power rating must be selected.
  • Page 35 Placing and Configuring the Drive 2-13 In the Controller Organizer, select the PowerFlex 700S drive. Right-click the drive module and select Properties. Select the Power tab. Select the correct Drive Rating. This data can be found on the PowerFlex 700S data nameplate. 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.
  • Page 36 2-14 Placing and Configuring the Drive Once the power rating is selected, apply your changes by selecting the Apply button. Select the Setup tab. Enter the file name for your DriveExecutive Lite parameter file, then click the Apply button. Click the DriveExecutive button to launch DriveExecutive Lite.
  • Page 37 Placing and Configuring the Drive 2-15 When asked to create a new DriveExecutive Lite file, select yes. DriveExecutive will then launch and open the newly created file...
  • Page 38 2-16 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.
  • Page 39 Placing and Configuring the Drive 2-17 To send additional data from the drive to the controller, go to the To DriveLogix tab. Click the button in front of the UserDefinedRealData[0] tag Select the desired source (parameter 307 [Output Voltage] in this example) in the resulting window. Configuring the Drive’s Response to a Connection Failure or Controller Mode Change The drive contains several parameters that allow you to configure the drive’s...
  • Page 40 2-18 Placing and Configuring the Drive Cnfg] configures the drive’s response to a general connection failure as detected by the drive. Parameter 388 [Lgx Closed Cnfg] configures the drive’s response to the controller closing the connection. All of these parameters configure the drive’s response to these exception events in the following ways: ignore, alarm, fault and coast to stop, fault and ramp to stop, fault and stop in current limit.
  • Page 41 Placing and Configuring the Drive 2-19 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. Select Properties from the Drive menu.
  • Page 42 2-20 Placing and Configuring the Drive In RSLogix 5000, go to the Setup tab o the Properties window. Click the Browse button. Select the existing DriveExecutive file (Existing Drive.dno in this example). Click the open button. Click the Apply button and then launch DriveExecutive.

  • Page 43: Accessing Drive Data

    Placing and Configuring the Drive 2-21 Accessing Drive Data 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.Bit where:...

  • Page 44: Configuring The Controller's Response To A Connection Failure

    2-22 Placing and Configuring the Drive Configuring the Controller’s You can configure the drive module to generate a major fault in the controller if the drive loses its connection to the controller. Response to a Connection Failure 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...
  • Page 45 Placing and Configuring the Drive 2-23 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: In the Controller Organizer, select Controller Tags. Right-click on the selected icon and select Monitor Tags. Expand the data as necessary.
  • Page 46 2-24 Placing and Configuring the Drive You can write logic to monitor these bits and take appropriate action if a fault or alarm occurs. For example, you may want a drive alarm to turn on a warning lamp and a drive fault to sound an alarm and set the motor brake. Example: Energizing Alarm Lamp, Siren and Brake in Response to Fault and Alarm Status Bits Given this configuration, the following logic checks the fault and alarm...

  • Page 47: Recommended Programming Techniques

    Placing and Configuring the Drive 2-25 Recommended Naming Tags Programming Techniques Use a convention when naming tags and consistently follow it. The following convention is used internally at Allen-Bradley: <prefix>_<function>_<suffix> Prefix - identifies the machine section in multi section programs Prefix examples: Sct1 = Section 1 Fan2 = Fan 2...
  • Page 48 2-26 Placing and Configuring the Drive Use Aliasing for all Communication Format Connections Between DriveLogix and the PowerFlex 700S Using aliases for the tags in the Communication Format (i.e. Speed Control, Motion Control, Position Control, User-Defined 1 and User-Defined 2) has the following benefits: •...

  • Page 49: Chapter 3 Placing And Configuring Local I/O

    Chapter Placing and Configuring Local I/O De-energizing the Drive to Connect or Disconnect a ATTENTION: Severe injury or death can result from electrical Cable shock or burn. Verify that the voltage on the bus capacitors has discharged before connecting to the communication ports. Measure the DC bus voltage at the +DC &...

  • Page 50: Placing Local I/O Modules

    Placing and Configuring Local I/O Placing Local I/O Modules Refer to the Compact I/O Selection Guide, publication 1769-SG001, for information about selecting Compact I/O modules. Use the 20D-DL2-CR3 or 20D-DL2-CL3 cables to connect a DriveLogix5730 controller to a bank of Compact I/O. Use 1769-CRR1/-CRR3 or 1769-CRL1/-CRL3 expansion cable to connect banks of I/O modules.

  • Page 51: Validating I/O Layout

    Placing and Configuring Local I/O A 1769-CRL1/-CRL3 connects the left side of one bank of Compact I/O to the right side of another. This facilitates a horizontal I/O orientation. 20D-DL2-CL3 1769-CRLX 1769-CRLX 20D-DL2-CR3 A 1769-CLL1/-CLL3 connects the left side of one bank of Compact I/O to the left side of another.

  • Page 52: Estimating Rpi

    Placing and Configuring Local I/O Estimating RPI As you install modules, the minimum backplane RPI increases. The RPI (request packet interval) defines the frequency at which the controller sends and receives all I/O data on the backplane. There is one RPI for the entire 1769 backplane.

  • Page 53: Configuring The Compactbus

    Placing and Configuring Local I/O Configuring the When you create a DriveLogix5730 project, the programming software automatically creates the local CompactBus. You must configure the CompactBus CompactBus. In the Controller Organizer, select CompactBus Local icon. Right click and select Properties.
  • Page 54 Placing and Configuring Local I/O On the General tab, specify the size of the chassis. Enter the number of modules you plan to install. Include the DriveLogix5730 controller and drive in this total, along with a maximum of 16 I/O modules, not including the power supply.

  • Page 55: Configuring Local I/O Modules

    Placing and Configuring Local I/O Configuring Local I/O Use your programming software to configure the I/O modules for the controller. Modules In the Controller Organizer, select CompactBus Local icon. Right click and select New Module. Select the new module (1769-IA16 in this example). Configure the module, using the module wizard to specify characteristics.
  • Page 56 Placing and Configuring Local I/O Communication Formats The communication format determines the data structure the I/O module uses. Each format supports a different data structure. Presently, the DriveLogix5730 controller supports two data formats: • Input Data – INT (for 1769 input modules) •...
  • Page 57 Placing and Configuring Local I/O RSLogix 5000 software creates tags for modules when you add them to the I/O configuration. The 1769 module tags define configuration (C) data type members which may include attributes for alternate outputs. DriveLogix5730 does not enable local modules to use the alternate outputs. Do not configure the attributes listed below: For digital output modules: For analog output modules:...
  • Page 58 3-10 Placing and Configuring Local I/O On the Connection tab of the Module Properties dialog, you can select to inhibit that specific module. TIP: To easily inhibit all local I/O modules, you can inhibit the CompactBus, which in turn inhibits all the modules on that bus. See Configuring the CompactBus on page 3-5.
  • Page 59 Placing and Configuring Local I/O 3-11 inhibit or 0 to uninhibit). Use a SSV instruction to write the Mode attribute back to the module. For example: The GSV instruction gets the current status of the module named “input_module.” The SSV instruction sets the state of “input_module” as either inhibited or uninhibited.

  • Page 60: Accessing I/O Data

    3-12 Placing and Configuring Local I/O Configuring the Controller’s Response to a Connection Failure In a DriveLogix5730 system, the controller’s response to a CompactBus connection failure is fixed to always fault the controller. The CompactBus setting supersedes the individual module’s setting. Important: The controller’s response to a connection failure of any I/O module is fixed to always fault the controller.
  • Page 61 Placing and Configuring Local I/O 3-13 This address variable: 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. Data is the common name for values that are sent to or received from I/O points.

  • Page 62: Direct Connections For I/O Modules

    3-14 Placing and Configuring Local I/O Sample tag names for this example: Location: Example Tag Name: input module in slot 1, LOCAL Bank 1 Local:1:C Local:1:I output module in slot 2, LOCAL Bank 1 Local:2:C Local:2:I Local:2:O analog input module in slot 3, LOCAL Bank 2 Local:3:C Local:3:I analog output module in slot 4, LOCAL Bank 2...

  • Page 63: Monitoring I/O Modules

    Placing and Configuring Local I/O 3-15 Monitoring I/O Modules The DriveLogix5730 controller offers different levels at which you can monitor I/O modules. You can: • use the programming software to display fault data (See Displaying Fault Data on page 3-15) •...
  • Page 64 3-16 Placing and Configuring Local I/O The display for the fault data defaults to decimal. Change it to Hex to read the fault code. If the module faults, but the connection to the controller remains open, the controller tags database displays the fault value 16#0E01_0001. The fault word uses this format: Fault_Code_Value reserved...

  • Page 65: Configuring I/O Modules Using The Generic 1769-Module

    Placing and Configuring Local I/O 3-17 End-cap Detection and Module Faults If a module that is not adjacent to an end cap experiences a fault and the connection to the controller is not broken, only the module enters the fault state.
  • Page 66 3-18 Placing and Configuring Local I/O 3.Configure the module, using the module wizard to specify characteristics. Click Next to advance the wizard. Click Finish when you are done. The completed module will appear in the Controller Organizer. The generic module requires you to specify more parameters of the module.
  • Page 67 Placing and Configuring Local I/O 3-19 Entering the Configuration Information for the Module Once you configure a module using the generic 1769-MODULE, you must enter the configuration information for the module into the tag database. The configuration information is downloaded to the module at program download, power up, and whenever a module is inhibited and then uninhibited.
  • Page 68 3-20 Placing and Configuring Local I/O Notes:...

  • Page 69: Chapter 4 Configuring Drivelogix Motion

    Chapter Configuring DriveLogix Motion De-energizing the Drive to Connect or Disconnect a ATTENTION: Severe injury or death can result from electrical Cable shock or burn. Verify that the voltage on the bus capacitors has discharged before connecting to the communication ports. Measure the DC bus voltage at the +DC &...

  • Page 70: Programming The Controller

    Configuring DriveLogix Motion Programming the Controller In RSLogix 5000, create a new project. From the File Menu, select New. Define the project. Use Revision 13 or You must enter a Name. Click OK.
  • Page 71 Configuring DriveLogix Motion In the Controller Organizer, select the I/O Configuration folder. Right-click the selected folder and select New Module. Select the drive (PowerFlex 700S-400V in this example). Click OK. Select the Major Revision. Configure the drive. Use the module properties wizard to specify characteristics for the module.
  • Page 72 Configuring DriveLogix Motion Change the RPI to 3.0 ms. Click Next. Click New Axis, to assign a channel to an axis. Create new tag structures for Axis00 and Axis01. Type Axis00 in the Name field and click OK. Repeat for Axis01.
  • Page 73 Configuring DriveLogix Motion Return to configuring the new drive. Assign the new axes to the channels. Click Next. Select the proper Drive Rating. Click Finish. Create a new Motion Group. Right click on Select New Motion Group. Motion Groups...
  • Page 74 Configuring DriveLogix Motion Create a new Motion Group continued… Enter a Name for the Motion Group. Click Configure. Move each axis to the Assigned side by clicking on the axis and then clicking Add. Move both axes. Click Next. Set the Coarse Update Period to 4 ms, this is the minimum time usable with DriveLogix motion.
  • Page 75 Configuring DriveLogix Motion Configure Axis00. Right click on the axis you want to configure (Axis00 in this example). Select Properties. On the General tab: Associate the module with the drive. Match the Module name with the drive’s name in the I/O Configuration. Set the Channel to the channel being used for the encoder.
  • Page 76 Configuring DriveLogix Motion Configure Axis00 continued... On the Motion Planner tab: 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.
  • Page 77 Configuring DriveLogix Motion Configure Axis00 continued... On the Dynamics tab: Define the limits for speed, acceleration and deceleration. Important: Do not exceed the system dynamics. Click Apply and OK when you have completely defined the axis. On the Homing tab: .Setup the Homing Mode, Position, Offset and Sequence.
  • Page 78 4-10 Configuring DriveLogix Motion Homing 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 Mode homing sequences always use the trapezoidal velocity profile. Passive - homing redefines the absolute position of the axis on the occurrence of a home switch or encoder marker event. Passive homing is most commonly used to calibrate uncontrolled axes, although it can also be used with controlled axes to create a custom homing sequence.

  • Page 79: Launching Driveexecutive From Rslogix

    Configuring DriveLogix Motion 4-11 Launching DriveExecutive Next open the drive properties window and launch DriveExecutive drive programming software. from RSLogix In the Controller Organizer, select the PowerFlex 700S drive. Right-click the drive module and select Properties That will launch the Module Properties Window for the drive. Click on the Setup tab.
  • Page 80 4-12 Configuring DriveLogix Motion Type the desired DriveExecutive filename or browse for an existing one. Then click Apply. Click the Launch DriveExecutive button to launch DriveExecutive Lite.

  • Page 81: Configuring The Drive With Driveexecutive Software

    Configuring DriveLogix Motion 4-13 Configuring the Drive with In DriveExecutive software, connect to the drive and access the Display DriveLogix dialog as shown below: DriveExecutive Software From the Drive Menu, select Display DriveLogix. Click on the From DriveLogix tab. Verify the Communication Format is set to Motion Control.
  • Page 82 4-14 Configuring DriveLogix Motion Next link the appropriate parameters to the words being produced and consumed by the controller. On the Links view, double-click on the desired Sink parameter. Click on the Link Source tab. Type or select the desired Source parameter.
  • Page 83 Configuring DriveLogix Motion 4-15 Create the links in the table below: Destination (Sink) Parameter Source Parameter Description 12 [Speed Ref 2] 751 [Interp Speed Ref] Speed reference from the Coarse to Fine Interpolator, to Speed Ref 2 22 [Speed Trim 2] 318[Posit Spd Output] This is a default link.
  • Page 84 4-16 Configuring DriveLogix Motion Type the desired value. Make the parameter settings shown in the table below: Parameter Value Description 13 [Spd Ref2 Multi] Speed Ref 2 scale value 24 [Spd Trim 3 Scale] 0.003 Speed Trim 3 scale value 27 [Speed Ref Sel] Select Speed Ref 2 as the speed reference 151 [Logic Command]...

  • Page 85: Downloading The Settings And Links To The Drive

    Configuring DriveLogix Motion 4-17 Downloading the Settings and Links to the Drive From the Drive Menu, select Display Download. Using the resulting windows and RSLinx navigate to the drive and download the settings and links. Additional Testing and The steps in this chapter provide the minimum settings required to begin testing DriveLogix motion.

  • Page 86: Supported Motion Commands

    4-18 Configuring DriveLogix Motion Supported Motion The following Logix Motion Instructions are supported by the DriveLogix controller: Commands Motion State • MSO (Motion Servo On) • MSF (Motion Servo Off) • MASD (Motion Axis Shutdown) • MASR (Motion Axis Shutdown Reset) •...

  • Page 87: Chapter 5 Communicating With Devices On A Serial Link

    Chapter Communicating with Devices on a Serial Link De-energizing the Drive to Connect or Disconnect a ATTENTION: Severe injury or death can result from electrical Cable shock or burn. Verify that the voltage on the bus capacitors has discharged before connecting to the communication ports. Measure the DC bus voltage at the +DC &...
  • Page 88 Communicating with Devices on a Serial Link Configuring the Hardware The RS-232 port is an isolated serial port built-in to the front of the Main Control Board. Refer to Opening Door Over Power Structure and Main Control Board on page B-2.
  • Page 89 Communicating with Devices on a Serial Link Configuring the Serial Port of the Controller In the Controller Organizer, select the Controller folder. Right-click the selected folder and select Properties. On the Serial tab, specify serial port characteristics. Characteristic: Description (default is shown in bold): Mode Select System (for DF1 communication) or User mode (for ASCII communication).
  • Page 90 Communicating with Devices on a Serial Link On the System Protocol tab, select the appropriate DF1 communication mode for point-to-point or master/slave communications. Or use the User Protocol tab to specify ASCII protocol to communicate to an ASCII device. Use this mode: For: See page: DF1 point-to-point...
  • Page 91 Communicating with Devices on a Serial Link Configuring the Communication Driver Use RSLinx software to configure the serial communication driver. Select the “DF1” driver. In the Communications menu, select the Configure Driver. From the Available Driver Type list select the DF1 Driver, then click Configure.

  • Page 92: Example 1: Workstation Directly Connected To A Drivelogix Controller

    Communicating with Devices on a Serial Link Example 1: Workstation In the following example, a workstation directly connects to a DriveLogi5730 controller over a serial link. This is useful for downloading Directly Connected to a a controller project directly to the controller. DriveLogix Controller Use RSLogix 5000 programming software to configure the controller’s serial port for the DF1 point-to-point (full-duplex) protocol.

  • Page 93: Example 2: Workstation Remotely Connected To A Drivelogix Controller

    Communicating with Devices on a Serial Link Example 2: Workstation In the following example, a workstation remotely connects to a DriveLogix controller over s serial link. A modem is connected to the controller to Remotely Connected to a provide remote access. DriveLogix Controller modem modem...
  • Page 94 Communicating with Devices on a Serial Link Master/Slave Communication Methods A master station can communicate with a slave station in two ways: Name: This method: Benefits: standard Initiates polling packets to slave stations This communication method is most often used for point-to-multipoint communication mode according to their position in the polling array(s).
  • Page 95 Communicating with Devices on a Serial Link Configuring a DF1 Master Station This field: Description: Station address The station address for the serial port on the DF1 master. Enter a valid DF1 address (0-254). Address 255 is reserved for broadcast messages. The default is 0. Transmit retries Specifies the number of times a message is retried after the first attempt before being declared undeliverable.

  • Page 96: Example 3: Drivelogix Controller To A Bar Code Reader

    5-10 Communicating with Devices on a Serial Link If you choose one of the standard polling modes The master station polls the slave stations in this order: 1. all stations that are active in the priority poll array 2. one station that is inactive in the priority poll array 3.
  • Page 97 Communicating with Devices on a Serial Link 5-11 1. For the serial port of the ASCII device, determine which pins send signals and which pins receive signals. 2. Connect the sending pins to the corresponding receiving pins and attach jumpers: If the communications: Then wire the connectors as follows: handshake...
  • Page 98 5-12 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.

  • Page 99: Communicating With Devices On An Ethernet/Ip Link

    Chapter Communicating with Devices on an EtherNet/IP Link De-energizing the Drive to Connect or Disconnect a ATTENTION: Severe injury or death can result from electrical Cable shock or burn. Verify that the voltage on the bus capacitors has discharged before connecting to the communication ports. Measure the DC bus voltage at the +DC &...

  • Page 100: Communicating Through The Embedded Ethernet/Ip Option

    Communicating with Devices on an EtherNet/IP Link Communicating Through For the DriveLogix controller to operate on an Ethernet network, you need: the Embedded EtherNet/IP • a workstation with an appropriate EtherNet/IP communication Option daughtercard • RSLinx software to configure the EtherNet/IP communication driver •...
  • Page 101 Communicating with Devices on an EtherNet/IP Link Assigning Network Parameters with BOOTP/DHCP The EtherNet/IP Option board ships with BOOTP enabled. You must assign an IP address to the Ethernet port in order for the controller to communicate over an EtherNet/IP network. The BOOTP/DHCP utility is a stand alone program that is located in the: •...
  • Page 102 Communicating with Devices on an EtherNet/IP Link In the Request History panel you see the hardware addresses of devices issuing BOOTP requests. Double-click on the hardware address of the device you want to configure. 5. The New Entry window appears with the device’s Ethernet Address (MAC). Enter the Ethernet address, IP address, subnet mask, and gateway.
  • Page 103 If you use the Rockwell Software BOOTP or DHCP server in an up-linked subnet where an enterprise DHCP server exists, a module may get an address from the enterprise server before the Rockwell Automation utility even sees the module. You might have to disconnect from the uplink to set the address and have the module remember its static address before reconnecting to the uplink.
  • Page 104 Communicating with Devices on an EtherNet/IP Link Using RSLinx Software to Set the IP Address Via the Controller Serial Port You need RSLinx software version 2.41 or higher. 1. Make sure the controller that uses the IP address is installed and running. 2.
  • Page 105 Communicating with Devices on an EtherNet/IP Link Using RSLogix 5000 Software to Set the IP Address Create a new offline project, with the drive and any other necesary componenents. In the Controller Organizer, select the I/O Configuration folder. Right-click the selected folder and select New Module. Important: You must create an offline project and download it to the controller before going online.
  • Page 106 Communicating with Devices on an EtherNet/IP Link To go online with the controller in RSLogix 5000 programming software, select Who Active from the Communications menu. Then highlight the controller and click the Download button. If the controller is already programmed click Go Online instead.
  • Page 107 Communicating with Devices on an EtherNet/IP Link In the Controller Organizer, right click on the icon for the port and select Properties. Select the Port Configuration tab and enter the proper data. Uncheck the Enable Bootp checkbox. Click Set, Apply and OK to make changes.
  • Page 108 6-10 Communicating with Devices on an EtherNet/IP Link Configuring the EtherNet/IP Communications Driver Important: EtherNet/IP only works within the local subnet and with EtherNet/IP devices (not Ethernet control products). To configure the AB_ETH Ethernet communication driver perform the following steps in RSLinx: From the Communications menu, select Configure Drivers.

  • Page 109: Controller Connections Over Ethernet/Ip

    Communicating with Devices on an EtherNet/IP Link 6-11 Select where the EtherNet/IP devices reside. The software locates valid IP addresses. Click OK. The driver is now available and you can select the EtherNet/IP port in RSLogix 5000. Controller Connections A Logix system uses a connection to establish a communication link between two devices.

  • Page 110: Configuring Distributed I/O

    6-12 Communicating with Devices on an EtherNet/IP Link Connections are allocations of resources that provide more reliable communications between devices than unconnected messages. All EtherNet/IP connections are unscheduled. An unscheduled connection is a message transfer between controllers that is triggered by the requested packet interval (RPI) or the program (such as a MSG instruction).
  • Page 111 Communicating with Devices on an EtherNet/IP Link 6-13 Accessing Distributed 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.
  • Page 112 6-14 Communicating with Devices on an EtherNet/IP Link Example Tag Names (automatically created by the Device: software): remote adapter FLEX_io_adapter:I “FLEX_io_adapter” FLEX_io_adapter:I.SlotStatusBits FLEX_io_adapter:I.Data FLEX_io_adapter:O FLEX_io_adapter:O.Data remote “input_module” in slot 0 FLEX_io_adapter:0:C rack-optimized connection FLEX_io_adapter:0:C.Config FLEX_io_adapter:0:C.DelayTime_0 FLEX_io_adapter:0:C.DelayTime_1 FLEX_io_adapter:0:C.DelayTime_2 FLEX_io_adapter:0:C.DelayTime_3 FLEX_io_adapter:0:C.DelayTime_4 FLEX_io_adapter:0:C.DelayTime_5 FLEX_io_adapter:0:I remote “output_module”...

  • Page 113: Adding A Remote Controller

    Communicating with Devices on an EtherNet/IP Link 6-15 Adding a Remote Controller If you want to add the controller as a remote consumed controller to the I/O configuration, you first add the EtherNet/IP port and then the controller. To Add a Remote Controller Build the I/O Configuration in this Order Add the remote EtherNet/IP port or bridge to the local EtherNet/IP port.
  • Page 114 6-16 Communicating with Devices on an EtherNet/IP 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.
  • Page 115 Communicating with Devices on an EtherNet/IP Link 6-17 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.
  • Page 116 6-18 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.
  • Page 117 Communicating with Devices on an EtherNet/IP Link 6-19 MSG instruction to keep the connection open (cache) or to close it after sending the message. Using this communication Uses a Which you This type of MSG: method: connection: can cache: CIP data table read or write PLC-2, PLC-3, PLC-5, or SLC (all types) CIP with Source ID...
  • Page 118 6-20 Communicating with Devices on an EtherNet/IP Link For MSG instructions originating from a DriveLogix5730 controller to a PLC or SLC controller: Type of MSG Instruction: Supported Source File Types: Supported Destination File Types: DriveLogix5730 In the DriveLogix5730 controller, specify the source data type Specify the destination file type based on the writes to PLC-5 or based on the destination device:...
  • Page 119 Communicating with Devices on an EtherNet/IP Link 6-21 The DriveLogix5730 controller can process messages initiated from PLC or SLC controllers. These messages use data table addresses. In order for these controllers to access tags within the DriveLogix5730 controller, you map tags to data table addresses.
  • Page 120 6-22 Communicating with Devices on an EtherNet/IP Link The following table shows example source and destination tags and elements for different controller combinations. Type of MSG Instruction: Example Source and Destination: PLC-5 writes to DriveLogix5730 source element N7:10 destination tag “array_1”...

  • Page 121: Using A Msg Instruction To Send An Email

    Communicating with Devices on an EtherNet/IP Link 6-23 Using a MSG Instruction to The controller is an email client that uses a mail relay server to send email. The DriveLogix5730 controller can execute a generic CIP message that Send an Email sends an email message to an SMTP mail relay server using the standard SMTP protocol.
  • Page 122 6-24 Communicating with Devices on an EtherNet/IP Link Creating String Tags On the Edit tab of the Controller Tags window, create three tags: • one to identify the mail server (use STRING data type for this tag) • one for the email text (use EMAILSTRING data type for this tag) •...
  • Page 123 Communicating with Devices on an EtherNet/IP Link 6-25 In the String Browser for EmailConfig, enter the IP address for your facility’s SMTP server. Click Apply. Click OK. Important: Obtain this address from your company’s systems administrators. Repeat this process for EmailText. Click on this button...
  • Page 124 6-26 Communicating with Devices on an EtherNet/IP Link To include “To:”, “From:”, and “Subject:” fields in the email, use <CR><LF> symbols to separate each of these fields. The “To:” and “From”” fields are required; the “Subject:” field is optional. Use a second set of <CR><LF>...
  • Page 125 Communicating with Devices on an EtherNet/IP Link 6-27 Configuring the MSG Instruction that Identifies the Mail Relay Server On the Configuration tab of the Message Configuration, fill out the following fields: In this field: Enter: Service Type Set Attribute Single Instance Class Attribute...
  • Page 126 6-28 Communicating with Devices on an EtherNet/IP Link Configuring the MSG Instruction that Transmits the Email On the Configuration tab of the Message Configuration, fill out the following fields: In this field: Enter: Service Type Custom Service Code Instance Class Attribute Source Element the tag that contains the email text...
  • Page 127 Communicating with Devices on an EtherNet/IP Link 6-29 On the Communication tab of the Message Configuration, set the Path in the same manner as in the MSG that identifies the mail relay server. Click Apply. Click OK. Understanding Email Status Codes Examine the destination element of the email MSG to see whether the email was successfully delivered to the mail relay server.
  • Page 128 6-30 Communicating with Devices on an EtherNet/IP Link Extended-Error Code Error Code (hex): (hex): Description: 0xFF 0x0100 Error returned by email server; check the Destination string for reason. The email message was not queued for delivery. 0x0101 SMTP mail server not configured. Attribute 5 was not set with a SMTP server address. 0x0102 “To:”...

  • Page 129: Example 1: Drivelogix5730 Controller And Distributed I/O

    Communicating with Devices on an EtherNet/IP Link 6-31 Example 1: DriveLogix5730 In the following example, one DriveLogix5730 controller controls distributed I/O through a 1794-AENT module. Controller and Distributed I/O DriveLogix5730 controller (DriveLogix1) EtherNet/IP 1794-AENT with distributed I/O (Remote1) Controlling Distributed I/O This example has DriveLogix1 controlling the I/O connected to the remote 1794-AENT module.

  • Page 130: Example 2: Controller To Controller

    6-32 Communicating with Devices on an EtherNet/IP Link Example 2: Controller to In the following example, one EtherNet/IP DriveLogix5730 controller communicates with another EtherNet/IP DriveLogix5730 controller over Controller EtherNet/IP. Each controller has its own local I/O. EtherNet/IP DriveLogix1 DriveLogix2 workstation Producing and Consuming Tags Produced data must be of DINT or REAL data type or an array or structure.
  • Page 131 Communicating with Devices on an EtherNet/IP Link 6-33 This example shows DriveLogix1 producing tagA and consuming tagB:...
  • Page 132 6-34 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. Sending a MSG instruction To send a MSG from DriveLogix1 to DriveLogix2: 1.
  • Page 133 Communicating with Devices on an EtherNet/IP Link 6-35 Total Connections Required by DriveLogix1 The following table calculates the connections used in this example. Connection: Amount: connected, cached MSG from DriveLogix1 to DriveLogix2 produced tagA produced from DriveLogix1 to DriveLogix2 other consumer (2 are configured) consumed tagB total connections used: 4 Receiving a MSG Instruction...
  • Page 134 6-36 Communicating with Devices on an EtherNet/IP Link Notes:...

  • Page 135: Communicating With Devices On An Controlnet Link

    Chapter Communicating with Devices on an ControlNet Link De-energizing the Drive to Connect or Disconnect a ATTENTION: Severe injury or death can result from electrical Cable shock or burn. Verify that the voltage on the bus capacitors has discharged before connecting to the communication ports. Measure the DC bus voltage at the +DC &...
  • Page 136 Communicating with Devices on an ControlNet Link sure it’s properly installed in the DriveLogix controller. Refer to Installing the Communications Daughtercard on page B-9. You’ll need to configure the communication daughtercard slot number to 1 in the RSLogix 5000 programming software. The DriveLogix controller uses slot 0 for the Communication Format with the local drive.
  • Page 137 Communicating with Devices on an ControlNet Link Configuring Your Daughtercard as Part of the System Use RSLogix 5000 programming software to map the 1788-CNx communication daughtercard as part of the DriveLogix5730 system. In the Controller Organizer, add the communication daughtercard to the I/O Configuration folder.

  • Page 138: Configuring Distributed I/O

    Communicating with Devices on an ControlNet Link Configuring Distributed I/O The DriveLogix5730 controller supports distributed I/O over a ControlNet link. Configuring I/O in a remote chassis is similar to configuring local I/O. You create the remote communication module and distributed I/O modules on the local ControlNet daughtercard.
  • Page 139 Communicating with Devices on an ControlNet Link Accessing Distributed 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.
  • Page 140 Communicating with Devices on an ControlNet Link Example Tag Names (automatically created by the Device: software): remote adapter FLEX_io_adapter:I “FLEX_io_adapter” FLEX_io_adapter:I.SlotStatusBits FLEX_io_adapter:I.Data FLEX_io_adapter:O FLEX_io_adapter:O.Data remote “input_module” in slot 0 FLEX_io_adapter:0:C rack-optimized connection FLEX_io_adapter:0:C.Config FLEX_io_adapter:0:C.DelayTime_0 FLEX_io_adapter:0:C.DelayTime_1 FLEX_io_adapter:0:C.DelayTime_2 FLEX_io_adapter:0:C.DelayTime_3 FLEX_io_adapter:0:C.DelayTime_4 FLEX_io_adapter:0:C.DelayTime_5 FLEX_io_adapter:0:I remote “output_module”...

  • Page 141: Scheduling The Controlnet Network

    Communicating with Devices on an ControlNet Link Scheduling the ControlNet Use RSNetWorx software to schedule the ControlNet network. The controller project must already be downloaded from RSLogix 5000 Network programming software to the controller and the controller must be in Program or Remote Program mode.
  • Page 142 Communicating with Devices on an ControlNet Link In the Network menu, select Properties. Edit the parameters as desired. Click Apply. Click OK. In the File menu, select Save.

  • Page 143: Sending Messages

    Communicating with Devices on an ControlNet Link Enter a name and path for the network configuration. Click OK to optimize and reschedule the connections. Sending Messages The DriveLogix5730 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.
  • Page 144 7-10 Communicating with Devices on an ControlNet Link MSG instruction to keep the connection open (cache) or to close it after sending the message. This type of message: And this communication method: Uses a connection: CIP data table read or write PLC2, PLC3, PLC5, or SLC (all types) CIP with Source ID CIP generic...
  • Page 145 Communicating with Devices on an ControlNet Link 7-11 Communicating with Another Logix-Based Controller All Logix-based controllers can use MSG instructions to communicate with each other. The following examples show how to use tags in MSG instructions between Logix-based controllers. Type of MSG Instruction: Example Source and Destination: Logix-based controller writes to Logix-based source tag...
  • Page 146 7-12 Communicating with Devices on an ControlNet Link Type of MSG Instruction: Supported Source File Types: Supported Destination File Types: DriveLogix writes In the DriveLogix controller, select one of these data types: Use the PLC-2 compatibility file. to PLC-2 SINT, INT, DINT, or REAL Example source element: array_1 Example destination tag: 010 DriveLogix reads...
  • Page 147 Communicating with Devices on an ControlNet Link 7-13 To map addresses: 1. From the Logic menu, select Map PLC/SLC Messages. 2. Specify this information: For: In this field: Specify: For example: PLC-3, PLC-5, and File Number Type the file number of the data table in the PLC/SLC controller. 10 SLC controllers Tag Name Type the array tag name the local controller uses to refer to the...

  • Page 148: Producing And Consuming Data

    7-14 Communicating with Devices on an ControlNet Link Type of MSG Instruction: Example Source and Destination: PLC-5 reads from DriveLogix5730 source tag “array_1” destination element N7:10 SLC reads from DriveLogix5730 SLC 5/05 The PLC-5, PLC-3, and SLC controllers support logical ASCII addressing so you do not have to SLC 5/04 OS402 and above map a compatibility file for MSG instructions initiated by a PLC-5, PLC-3, or SLC controller.
  • Page 149 Communicating with Devices on an ControlNet Link 7-15 Maximum Number of Produced and Consumed Tags The maximum number of produced/consumed tags that you can configure depends on the connection limits of the communication device that transfers the produced/consumed data. Each produced tag uses one connection for the tag and the first configured consumer of the tag.
  • Page 150 7-16 Communicating with Devices on an ControlNet Link Producing a Tag 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.

  • Page 151: Guidelines For Configuring Connections

    Communicating with Devices on an ControlNet Link 7-17 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.

  • Page 152: Example 1: Drivelogix Controller And Remote I/O

    7-18 Communicating with Devices on an 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. Use this table to select the API to enter in the above worksheet: Enter this value for the API: RPI ≥...

  • Page 153: Example 2: Drivelogix5730 Controller To Drivelogix5730 Controller

    Communicating with Devices on an ControlNet Link 7-19 Example 1: Total Connections Required by DriveLogix1 The following table calculates the connections used in this example. Connection: Amount: DriveLogix1 controller to 3 local I/O modules rack-optimized connection for the DIN rail direct connection for each I/O module DriveLogix1 controller to remote 1794-ACNR15 DriveLogix1 to 4 remote I/O modules (through 1794-ACNR15)
  • Page 154 7-20 Communicating with Devices on an ControlNet 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...
  • Page 155 Communicating with Devices on an ControlNet Link 7-21 This example shows DriveLogix1 producing tagA and consuming tagB:...

  • Page 156: Example 3: Drivelogix Controller To Other Devices

    7-22 Communicating with Devices on an ControlNet 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. Connection: Amount: DriveLogix1 controller to 3 local I/O modules...
  • Page 157 Communicating with Devices on an ControlNet Link 7-23 Example 3: Sending MSG Instructions You configure a MSG instruction to a Logix5550 controller the same as you do for a DriveLogix controller. All Logix-based controllers follow the same MSG configuration requirements. See Example 2 above. Configuring a MSG instruction for a PLC-5 controller depends on the originating controller.
  • Page 158 7-24 Communicating with Devices on an ControlNet Link Producing and consuming tags with a ControlNet PLC-5 controller depends on the type of data. ControlNet DriveLogix5730 Controller ControlLogix Controller ControlNet PLC5 DriveLogix5730 Controller (DriveLogix1) (Control1) Controller (DriveLogix2) (PLC5C1) tagA DINT Producing a Tag to a ControlNet PLC-5 controller To produce a tag that a ControlNet PLC-5 controller can consume: 1.
  • Page 159 Communicating with Devices on an ControlNet Link 7-25 The ControlNet PLC-5 controller stores floating-point data, which requires 32-bits regardless of the type of controller, as follows: – The first integer contains the upper (left-most) bits of the value. – The second integer contains the lower (right-most) bits of the value. To re-construct the floating point data within the ControlNet PLC-5 controller, first reverse the order of the integers and then copy them to a floating-point file.
  • Page 160 7-26 Communicating with Devices on an ControlNet Link Example 3: Total Connections Required by DriveLogix1 The following table calculates the connections used in this example. Connection: Amount: DriveLogix1 controller to 3 local I/O modules rack-optimized connection for the DIN rail direct connection for each I/O module DriveLogix1 controller to local 1788-CNC DriveLogix1 controller to remote 1756-CNB...

  • Page 161: Chapter 8 Communicating With Devices On An Devicenet Link

    Chapter Communicating with Devices on an DeviceNet Link De-energizing the Drive to Connect or Disconnect a ATTENTION: Severe injury or death can result from electrical Cable shock or burn. Verify that the voltage on the bus capacitors has discharged before connecting to the communication ports. Measure the DC bus voltage at the +DC &...

  • Page 162: Example: Controlling I/O Over Devicenet

    Communicating with Devices on an DeviceNet Link For the DriveLogix controller to operate on a DeviceNet link, you need: • a workstation with an appropriate DeviceNet interface card • RSLinx software to configure the DeviceNet communication driver • RSLogix 5000 programming software (Version 13 or later) to configure the DeviceNet communication daughtercard or local 1769-SDN DeviceNet scanner module as part of the DriveLogix system •...
  • Page 163 Communicating with Devices on an DeviceNet Link Configuring the 1769-ADN Adapter In RSNetWorx for DeviceNet, select Online from the Network menu. Choose the appropriate driver depending on whether the computer is directly connected to DeviceNet or you are accessing the network through a controller’s backplane and using a different port. continued...
  • Page 164 Communicating with Devices on an DeviceNet Link The software then prompts you to either upload or download. Choose upload. RSNetWorx will then browse the network and obtain their settings. Right click on the 1769-ADN and choose Properties. Click on the I/O Bank 1 Configuration tab, then choose upload when prompted. The actual 1769-ADN I/O layout appears. From this screen you can configure the I/O modules in the 1769-ADN system by simply clicking on the slot number box associated with each I/O module.
  • Page 165 Communicating with Devices on an DeviceNet Link TIP: Configuration changes made to the adapter or any of its I/O modules with RSNetWorx will not be saved or downloaded to the adapter once the adapter is configured in a scanner’s scanlist. To make configuration changes, the controller must be placed into the Program mode and the adapter must be temporarily removed from the scanner’s scanlist.
  • Page 166 Communicating with Devices on an DeviceNet Link Click on the adapter, then click on the single arrow pointing to the right. This moves the adapter from Available Devices to the scanner’s scanlist. Verify that the Input Size and Output Size are correct. The Output and Input sizes correspond to the total number of output and input bytes noted from the adapter’s summary page.
  • Page 167 Communicating with Devices on an DeviceNet Link Mapping starts at word 0 for both the input and the output data image. The input status and output configuration words are no longer included with the I/O data scanlist. Use the status and configuration tags created in RSLogix 5000 software to read status or set configuration bits.
  • Page 168 Communicating with Devices on an DeviceNet Link Module Command Array The module command array is the primary control interface between your control program and the module. In RSLogix 5000 software, the CommandRegister tag structure is as follows: Output Word Description Behavior This bit controls when the module scans its mapped slave devices.
  • Page 169 Communicating with Devices on an DeviceNet Link Creating a Project for the DriveLogix5730 Controller In the Controller Organizer, select the I/O Configuration folder. Right-click the selected folder and select New Module. Select the 1788-DNBO DeviceNet Scanner from the list of possible communication devices.
  • Page 170 8-10 Communicating with Devices on an DeviceNet Link If you are using a 1769-SDN Scanner Module, add it to the local CompactBus: In the Controller Organizer, select the I/O Configuration folder. Right-click the selected Local CompactBus and select New Module. Select the 1769-SDN DeviceNet Scanner from the list of possible communication devices.
  • Page 171 Communicating with Devices on an DeviceNet Link 8-11 All tags for I/O modules are automatically created when the profiles for these modules are configured. Double click on Controller Tags in the controller organizer to view these tags. Each I/O module slot has Input, Output and Configuration tags created, if they apply.
  • Page 172 8-12 Communicating with Devices on an DeviceNet Link Entering Program Logic The program for this example consists of a single rung that is used to place the scanner into the RUN mode.

  • Page 173: Chapter 9 Communicating With Devices On A Dh485 Link

    Chapter Communicating with Devices on a DH485 Link De-energizing the Drive to Connect or Disconnect a ATTENTION: Severe injury or death can result from electrical Cable shock or burn. Verify that the voltage on the bus capacitors has discharged before connecting to the communication ports. Measure the DC bus voltage at the +DC &...

  • Page 174: Configuring Your System For A Dh-485 Link

    Communicating with Devices on a DH485 Link Configuring Your System for For the DriveLogix5730 controller to operate on a DH-485 network, you need: a DH-485 Link a 1761-NET-AIC interface converter for each DriveLogix5730 controller you want to put on the DH-485 network. You can have two controllers per one 1761-NET-AIC converter, but you need a different cable for each controller.
  • Page 175 Communicating with Devices on a DH485 Link The cable you use to connect the controller depends on the port you use on the 1761-NET-AIC converter. If you connect to this port: Use this cable: port 1 1747-CP3 DB-9 RS-232, DTE connection 1761-CBL-AC00 port 2 1761-CBL-AP00...

  • Page 176: Planning A Dh-485 Network

    Communicating with Devices on a DH485 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.
  • Page 177 Communicating with Devices on a DH485 Link The allowable range of the node address of an initiator is 0 to 31. The allowable address range for all responders is 1 to 31. There must be at least one initiator on the network. Network Initialization The network requires at least one initiator to initialize it.

  • Page 178: Installing A Dh-485 Network

    Communicating with Devices on a DH485 Link Installing a DH-485 Network A DH-485 network consists of a number of cable segments daisy-chained together. The total length of the cable segments cannot exceed 1219 m (4000 ft). Important: Use shielded, twisted-pair cable - either Belden 3106A or Belden 9842. A daisy-chained network is recommended.
  • Page 179 Communicating with Devices on a DH485 Link Connections Using Belden 3106 Cable The table and schematic diagram below shows wire/terminal connections for Belden 3106A cable. Termination OR/WH Data A WH/OR Data B Common Shield Chassis Ground ahw0604.eps For this Wire/Pair Connect this Wire To this Terminal white/orange...
  • Page 180 Communicating with Devices on a DH485 Link 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).

  • Page 181: Browsing A Dh-485 Network Remotely

    Communicating with Devices on a DH485 Link Browsing a DH-485 Network To improve performance when browsing a DH-485 network, configure the DH-485 network properties in RSLinx software to display only those nodes Remotely that actually exist on the network. 1. In RSLinx software, right-click on the DH-485 network you plan to browse and select Properties. 2.
  • Page 182 9-10 Communicating with Devices on a DH485 Link Notes:...

  • Page 183: Appendix A Drivelogix5730 Controller Specifications

    Appendix DriveLogix5730 Controller Specifications DriveLogix5730 Controller Category Specification Specifications serial port (CH0 -RS-232) RS-232, fully isolated DF1, DH-485, ASCII 38.4 Kbits/s maximum optional embedded EtherNet/IP RJ-45 or 100BaseT 10/100 Mbytes/sec • NetLinx communication daughtercards connectivity options (these options require the Logix (ControlNet, EtherNet/IP, DeviceNet, Third Party) •...

  • Page 184: Drivelogix5730 Certifications

    DriveLogix5730 Controller Specifications DriveLogix5730 Certification Description Certifications c-UL-us UL Listed for Class I, Division 2 Group A,B,C,D Hazardous Locations, certified for U.S. and Canada European Union 89/336/EEC EMC Directive, compliant with: • EN 50082-2; Industrial Immunity • EN 61326; Meas./Control/Lab., Industrial Requirements •...

  • Page 185: Controller Leds

    DriveLogix5730 Controller Specifications Controller LEDs ATTENTION: The controller LEDs are only operational when the drive is energized, and only visible with the drive door open. Servicing energized equipment can be hazardous. Severe injury or death can result from electrical shock, burn or unintended actuation of controlled equipment.
  • Page 186 The controller detected a non-recoverable fault, so it cleared the project from memory. To recover: Cycle power to the chassis. Download the project. Change to Run mode. If the OK LED remains solid red, contact your Rockwell Automation representative or local distributor. solid green Controller is OK. flashing green...
  • Page 187 DriveLogix5730 Controller Specifications CompactFlash card LED ATTENTION: The CompactFlash LED is only operational when the drive is energized, and only visible with the drive door open. Servicing energized equipment can be hazardous. Severe injury or death can result from electrical shock, burn or unintended actuation of controlled equipment.

  • Page 188: Embedded Ethernet/Ip Option Leds

    DriveLogix5730 Controller Specifications Embedded EtherNet/IP Option LEDs ATTENTION: The Embedded EtherNet/IP Option LEDs are only operational when the drive is energized, and only visible with the drive door open. Servicing energized equipment can be hazardous. Severe injury or death can result from electrical shock, burn or unintended actuation of controlled equipment.
  • Page 189 DriveLogix5730 Controller Specifications Condition: Status: Indicates: Recommended Action: solid red held in reset The controller is holding the port in reset or the Clear the controller fault. controller is faulted. Replace the controller. self-test The port is performing its power-up self-test. Normal operation during power-up.

  • Page 190: Battery Life

    DriveLogix5730 Controller Specifications Battery Life Time ON/OFF at 25° C (77° F) at 40° C (104° F) at 60° C (140° F) Always OFF 14 months 12 months 9 months ON 8 hours per day 18 months 15 months 12 months 5 days per week ON 16 hours per day 26 months...

  • Page 191: Appendix B Access Procedures

    Appendix Access Procedures Removing Power from Drive and Compact I/O ATTENTION: To avoid an electric shock hazard, verify that the voltage on the bus capacitors has discharged before performing any work on the drive. Measure the DC bus voltage at the +DC & –DC terminals of the Power Terminal Block.

  • Page 192: Opening Door Over Power Structure And Main Control Board

    Access Procedures Opening Door Over Power Structure and Main Control Board Frames 1-4 Locate the slot in the upper left corner. Slide the locking tab up and swing the cover open. Special hinges allow cover to move away from drive and lay on top of adjacent drive (if present).

  • Page 193: Removing The Outside Covers

    Access Procedures Removing the Outside Covers Proper tightening torque for Task Description reassembly is 7-10 lb.-in. Loosen screws on face of front cover and remove the cover Loosen screws on side of rear cover and remove the cover Removing the Inside Cover Task Description Loosen screws on face of front cover and remove...

  • Page 194: Connecting The Battery

    Access Procedures Connecting the Battery Allen-Bradley ships the DriveLogix controller with the battery installed, but disconnected. You must connect the battery while installing the drive. Battery Plug and socket Battery clip Storing the Battery ATTENTION: Store batteries in a cool, dry environment. We recommend 25°...

  • Page 195: Replacing The Battery

    Access Procedures Replacing the Battery ATTENTION: Servicing energized equipment can be hazardous. Severe injury or death can result from electrical shock, burn or unintended actuation of controlled equipment. Follow Safety related practices of NFPA 70E, ELECTRICAL SAFETY FOR EMPLOYEE WORKPLACES. DO NOT work alone on energized equipment! ATTENTION: The controller uses a lithium battery, which contains potentially dangerous chemicals.
  • Page 196 B. If the BATTERY LED remains on, install another 1769-BA battery. C. If the BATTERY LED remains on after you complete Step B., contact your Rockwell Automation representative or local distributor. 13.Download the controller’s memory and program from the computer with RSLogix 5000 programming software.

  • Page 197: Installing The Embedded Ethernet/Ip Option Board

    Access Procedures Installing the Embedded EtherNet/IP Option Board Task Description Install and tighten standoffs (7-10 lb.-in.) Align connector on Embedded EtherNet/IP Option Board with connector on Main Control Board Place Embedded EtherNet/IP Option Board on the Main Control Board Install and tighten screws (7-10 lb.-in.) Installing the DriveLogix5730 Expansion Board...

  • Page 198: Installing The Compact I/O Cable

    Access Procedures Installing the Compact I/O Cable Task Description Remove screws Install clips on controller end of cable Plug controller end of cable into mating connector on the Logix Expansion Board Install and tighten screws (7-10 lb.-in.) Route and secure cable Use cable tie to anchor cable to slots on this flange for strain relief...

  • Page 199: Installing The Communications Daughtercard

    Access Procedures Installing the Communications Daughtercard Task Description Align circuit board in Communications Daughtercard with rail on Daughtercard slot Insert the Communications Daughtercard Tighten screws (7-10 lb.-in.) Important: This procedure can be performed without removing the cassette, if the Logix Expansion Board is already installed.
  • Page 200 B-10 Access Procedures Notes:...
  • Page 201 Index Numerics clock accuracy A-2 1769-ADN adapter 8-3 communicating 1769-CRL1/-CRL3 cable 3-2 master/slave serial methods 5-8 1769-CRR1/-CRR3 cable 3-2 to non-Logix controller over ControlNet 1788-DNBO DeviceNet scanner 8-5 7-11 20D-DL2-CL3 cable 3-2 communication format 2-1, 2-5, 3-8 20D-DL2-CR3 cable 3-2 Motion Control 2-8 Position Control 2-7 Speed Control 2-6...
  • Page 202 Index-2 ControlFlash 1-3 ControlNet Email accessing distributed I/O 7-5 using an EtherNet/IP msg 6-23 communicating to non-Logix controllers EtherNet/IP 7-11 accessing distributed I/O 6-13 configuring communications driver 7-2 configuring communications driver 6-10 configuring system for 7-1 configuring network settings with consuming tags 7-16 BOOTP/DHCP 6-3 daughtercard 7-3...
  • Page 203 Index-3 mapping 7-12 accessing data 3-12 addresses EtherNet/IP communication to non-Logix controllers 6-21 accessing distributed on ControlNet 7-5 Motion Control communication format accessing distributed on EtherNet/IP 6-13 Position Control communication format configuring local 3-7 ControlNet 7-4 Speed Control communication format DeviceNet 8-2 direct connections 3-14 User-Defined 1 communication format...
  • Page 204 Index-4 replacing Turning Drive Off 1-2, 2-1, 3-1, 4-1, 5-1, 6-1, 7-1, 8-1, 9-1, B-1 battery B-5 routines defining 1-8 RPI 3-4, 3-6 User-Defined 1 RS-232 5-1 communication format 2-9 RSLinx User-Defined 2 configuring EtherNet/IP network communication format 2-10 parameters 6-6 RSLogix 5000 configuring network parameters 6-7 virtual backplane 1-11...
  • Page 208 Americas: Rockwell Automation, 1201 South Second Street, Milwaukee, WI 53204-2496 USA, Tel: (1) 414.382.2000, Fax: (1) 414.382.4444 Europe/Middle East/Africa: Rockwell Automation SA/NV, Vorstlaan/Boulevard du Souverain 36, 1170 Brussels, Belgium, Tel: (32) 2 663 0600, Fax: (32) 2 663 0640 Asia Pacific: Rockwell Automation, 27/F Citicorp Centre, 18 Whitfield Road, Causeway Bay, Hong Kong, Tel: (852) 2887 4788, Fax: (852) 2508 1846 Headquarters for Dodge and Reliance Electric Products Americas: Rockwell Automation, 6040 Ponders Court, Greenville, SC 29615-4617 USA, Tel: (1) 864.297.4800, Fax: (1) 864.281.2433...

This manual is also suitable for:

Drivelogix 5730

Table of Contents