Home

20D-UM003 - Rockwell Automation

1. OOOOOCOOOOCO0O Tg Condition Status Indicates Recommended Action off no power The controller does not have power Check the controller power supply flashing green standby The port does not have an IP address and is Verify that the BOOTP server is running operating in BOOTP mode solid green OK The port is operating correctly Normal operation No action required DriveLogix5730 Controller Specifications A 7 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 No action required major fault An unrecoverable fault has occurred Cycle power to the controller Replace the controller flashing red updating firmware The port firmware is being updated Normal operation during firmware update No action required Network Status NS indicator Condition Status Indicates Recommended Action off not initialized The port does not have an IP address and is Verify that the BOOTP server is running operating in BOOTP mode flashing green no CIP The port has an IP address but no CIP connections Normal
2. C Controller Fault Handler communication devices C3 Power Up Handler Click OK a Tasks 5 69 MainTask 2 OB arrora xl LI Unscheduled Programs Motion Groups Type f1769 SDNe Ou dA Ingrouped Axes Description CI Trends l Data Types 1769 MODULE Generic 1769 Module CR User Defined 1769 0416 16 Point 100V 240V AC Output E Strings 1769 048 8 Point 100V 240V AC Output 4 Predefined 1769 0816 16 Point 24V DC Output Source Module Defined 1769 0B16P 16 Point 24V DC Protected Output 1 0 Configuration 1769 0832 32 Point High Density 24V DC Output 2 PowerFlex 7005 2 400 Drive 1769 088 8 Point High Current 24V DC Output T 1769 0F2 2 Channel Current Voltage Analog Output Trice tai NEN Moda 1763 016 16 Point 24V DC Output Sink fi 2 1769 0a1 1769 0W16 16 Point AC DC Relay Output amp 1769 0W8 8 Point AC DC Relay Output Cut Ctrl x Copy Ctrl C 1769 0W8I 8 Point Isolated AC DC Relay Output f Paste Ctrl 1769 Scanner DeviceNet Delete Del 1769 SDN B 7 Show Vendor fal 7 IV Other IV Specialty 1 0 Select All IV Analog IV Digital MV Communication IV Motion IV Controller Clear All Cross Reference Ctrl E Properties Cancel Help Module Properties Local 3 1769 SDN B 2 1 f xl Type 1769 SDN B 1769 Scanner DeviceNet Vendor Allen Bradley N
3. 2 2 4 3 3 3 4 4 The word range commands fill the destination tag contiguously Data structure and value change depending on the destination data type 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 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 For In this field PLC 3 PLC 5 and File Number Communicating with Devices on a ControlNet Link 7 13 To map addresses 1 From the Logic menu select Map PLC SLC Messages xi PLC 3 5 2 SLC Mapping rammer farer men Help PLC 2 Mapping Tag Name 2 Specify this information Specify For example 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 tothe array 1 PLC SLC data table address The tag must be an integer array SINT INT or DINT that is large enough for the message data PLC 2 controllers Tag Name Type the tag name to be the PLC 2 compatibility file 200 gt Type of MSG Instruction
4. EHF 6 Type or select the desired Source parameter m Link Source C No Link Parameter Configuring DriveLogix Motion 4 17 Total Inertia Speed Ref 1 Spd Refi Divide Speed Ref 2 Spd Ref2 Multi Preset Speed 1 Preset Speed 2 Preset Speed 3 Preset Speed 4 Preset Speed 5 Preset Speed 6 Preset Speed 7 Speed Trim 1 Speed Trim 2 Speed Trim 3 SpdTrim 3 Scale STrim2 Filt Gain SpdTrim2 Filt BW Speed Ref A Sel Speed Ref B Sel Jog Speed 1 Accel Time 1 Decel Time 1 S Curve Time SpdRef Filt Gain SpdRef Filt BW Spd Ref Bypass Speed Ref Scale Jog Speed 2 Spd Ref Bypass2 Inertia SpeedRef InertiaAccelGain InertiaDecelGain 318 43 47 43 Parameter 12 Speed Ref 2 Properties VERE Link Source Link Sinks Documentation Attributes Find Parameter 751 Next Selected Parameter CoarsePosit Trgt a Interp Position Coarse Spd Trgt Interp Speed Function Block Block Node 7 Available Drive Links 183 Total Drive Links 200 Parameter Help Source N Posit Spd Output Ramped Spd Ref SpdRef SpdTrmi Ramped Spd Ref 4 18 Configuring DriveLogix Motion 7 On the Parameters view double click on the desired parameter Create the links in the table below Table 4 A Parameter Links for DriveLogix Motion Configuration Destination Sink Parameter Source Parameter Description 12 Speed Ref
5. 1 Do not confuse the Drive Run LED with the DriveLogix Run LED The Drive Run LED indicates a drive function NOT a DriveLogix function leel 20000000 A 4 DriveLogix5730 Controller Specifications Indicator Color Description RUN off The controller is in Program or Test mode solid green The controller is in Run mode FORCE off No tags contain I O force values I O forces are inactive disabled solid amber I O forces are active enabled I O force values may or may not exist flashing amber One or more input or output addresses have been forced to an On or Off state but the forces have not been enabled BAT off The battery supports memory solid red Either the battery is not installed 95 discharged and should be replaced I O off Either There are no devices in the I O configuration of the controller The controller does not contain a project controller memory is empty solid green The controller is communicating with all the devices in its I O configuration flashing green One or more devices in the I O configuration of the controller are not responding flashing red The controller is not communicating to any devices The controller is faulted COM off No RS 232 activity flashing green RS 232 activity OK off No power is applied flashing red If the controller is Then a new controller the controller
6. i i Chapala aha Shae DriveLogix controller Ee CC with 1788 DNBO g Communications 7 LJ co Daughtercard CPP oP Oo T ST 1769 ADN Scanner Module installed in a bank of DeviceNet Compact I O Communicating with Devices on a DeviceNet Link 8 3 Configuring the 1769 ADN Adapter 1 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 DeviceNet RSNetWorx for DeviceNet Eite Edit View Network Device Diagnostics Tools Help als ullals ERE al Ele JE Hardware x DeviceNet FFF FFF EH Limit Switch Modular DPI Devices Motor Overload C Motor Starter Photoelectric Sensor Rockwell Automation miscel CO SCANport Adapter O Smart MCC Specialty 1 0 Unknown Device Type 126 vendor Rockwell Automation Aller Rockwell Automation Dodi Rockwell Automation Elect Rockwell Automation Reliz Rockwell Automation Entek w KI 4 gt bi Graph Spreadsheet i Master Slave Configuration i D
7. When cutting cable segments make them long enough to route them from one link coupler to the next with sufficient slack to prevent strain on the connector Allow enough extra cable to prevent chafing and kinking in the cable Figure 9 1 Single Cable Connection gi Orange Wire FUN Shrink Tubing with White Stripe pat f OR WH Recommended i 4 pairon White Wire 4 300 id gro Belden 3106A or 9842 Cable with Orange Stripe D pos 3106A Shown WH OR Blue Wire BU Drain Wire Shield Connections Using Belden 3106 Cable Communicating with Devices on a DH485 Link 9 7 The table and schematic diagram below shows wire terminal connections for Belden 3106A cable z gt gt 6 Termination OR WH i ki gt 5 Data A xX WHIOR i gt 4 DataB BU i gt gt 3 Common DL gt gt 2 Shield gt gt 1 Chassis Ground For this Wire Pair Connect this Wire To this Terminal white orange orange with white stripe 5 Data A white with orange stripe 4 Data B blue blue 3 Common shield drain non jacketed 2 Shield Connections Using Belden 9842 Cable The table and schematic diagram below shows wire terminal connections for Belden 9842 cable gt gt 6 Termination OX OR WH E gt gt 5 Data A WH OR i gt gt 4 Data B BUWH i gt 3 Common WEBU 4 2 Shield gt gt 1
8. Use RSLogix 5000 programming software to configure the controller s serial port for the DF1 point to point full duplex protocol This type of protocol supports simultaneous transmission between two devices in both directions The DF1 point to point protocol controls message flow detects and signals errors and retries if errors are detected Configuring a DF1 Point to Point Station Description The station address for the serial port on the DF1 point to point network Enter a valid DF1 address 0 254 Address 255 is reserved for broadcast messages The default is 0 NAK receive limit Specifies the number of NAKs the controller can receive in response to a message transmission Enter a value 0 127 The default is 3 ENQ transmit limit Specifies the number of inquiries ENQs you want the controller to send after an ACK timeout Enter a value 0 127 The default is 3 ACK timeout Specifies the amount of time you want the controller to wait for an acknowledgment to its message transmission Enter a value 0 32767 Limits are defined in 20ms intervals The default is 50 1000ms Embedded response Specifies how to enable embedded responses 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 accept
9. Cancel Apply Help Creating String Tags Communicating with Devices on an EtherNet IP Link 6 25 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 one for the email transmission status use EMAILSTRING data type for this tag Controller Tags EtherNetIP_IO_Example controller 4 Scope JEtherNetIP_1O_Exar 7 Show Show Al x Sort Tag Name z o x P Tag Name AB PF700S_2_SP AB PF700S_2_SP AB 1756_ENET_ AB 1794_DI_Dela Flex_io_adapter Flex_io_adapter l INT Binary 4B 1794_D016 C 0 Flex_io_adapter 0 Flex_io_adapter 0 INT Binary Flex io adapter 2 C AB 1794 IFZXOF Flex_io_adapter 2 1 AB 1794_IF2XOF Flex_io_adapter 2 0 AB 1794_IF2XOF Flex_io_adapter AB 1794_AEN_8 Flex_io_adapter 0 AB 1794_AEN_8 EmailContig STRING EmailT ext EMAILSTRING EmailStatus Monitor Tags 4 ay Entering String Data On the Monitor Tags tab of the Controller Tags window click the button in the Value column to launch the String Browser for each tag 1 On the Monitor Tags tab of the Controller Tags window click the button in the Value column to launch the String Browser Click on this
10. Cancel Apply Help Characteristic Description default is shown in bold Mode Select System for DF1 communication or User mode for ASCII communication Baud rate Specifies the communication rate for the serial port Select a baud rate that all devices in your system support Select 110 300 600 1200 2400 4800 9600 19200 or 38400 Kbps Parity Specifies the parity setting for the serial port Parity provides additional message packet error detection Select None or Even Data bits Specifies the number of bits per message packet 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 If you are not using a modem select No Handshake If both modems in a point to point link are full duplex select Full Duplex for both controllers 5 4 Communicating with Devices on a Serial Link 3 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 Controller Properties Serial_Example 5 oj xj Date Time Advanced SFC Execution File Nonvolatile Memory Memory General SerialPort System Pr
11. 2 PowerFlex 7005 2 400Y drive module S CompactBus Local 1 1769 1416 4 input_module_1 g 2 1769 0416 4 output module 2 J 3 1769 MODULE module 3 Controller Tags quick start controller Scope quick_stat cortiobes Shove Show All Sot TagName 3 ABPF7O0S 2 SP FAN AB PF 005_2 SP PES 148 1789 DN6L0 vi 1481768 001600 j AB 1763 _ 0161 0 Ag 1769_D016 0 0 E t 1481769 MODUL Locat Fauk Decimal iNT Floca 31 Daa I KEN oes Dooma mn Ve J Loost 3C mz Al EA AB 1769_MOOUL Fr Locek IC Reverved Decimal DINT Hf Local 3C Data I PEE len Hex E a gt N Monitor Tays A Eat Tags 7 Ta j T The generic module was added to slot 3 so you want to enter configuration data into the Local 3 C tags RSLogix 5000 programming software automatically create tags for configured I O modules All local I O addresses are preceded by the word Local These addresses have the following format e Input Data Local s I e Output Data Local s O e Configuration Data Local s C Where s is the slot number assigned the I O module Open the configuration tag for that module by clicking on the plus sign to the left of its configuration tag in the tag database The configuration information depends on the module See the documentation on the I O module for the appropriate configuration information 3 20 Placing and Configuring Local I O Notes De energizing the Drive to C
12. Communicating with Devices on an EtherNet IP Link 6 3 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 e BOOTP DHCP Server folder in the Rockwell Software program folder on the Start menu the utility is automatically installed when you install RSLinx software e Tools directory on the RSLogix 5000 installation CD The computer running the BOOTP DHCP utility and the DriveLogix5730 controller must be on the same EtherNet IP network To use the BOOTP DHCP utility 1 Start the BOOTP DHCP software 2 From the Tools menu select Network Settings File Tools Help Ni tings Request History gt erry ee Relation List ra _Ethernet Address MA Note If you have not run the BOOTP DHCP program before it will automatically launch the Network Settings window Network Settings xl gt r Defaults Subnet Mask 255 255 255 0 Gateway 010 091 013 001 PimayDNS 0 0 0 0 3 Enter the required data Secondary DNS os O 5225 Domain Name mia Cancel Click OK 6 4 Communicating with Devices on an EtherNet IP Link 4 In the Request History panel you see the hardware addresses of devices issuing BOOTP requests Double click on the
13. 2x J 1769 4DN Compact 1 0 Adapter Name DN Compact 1 0 Adapter Description Address 21 ml Device Identity Primary Vendo RiockwellAutomation AllenBradey 1 Type Communication Adapter Device I7E3ADN Compact 1 0 Adapter 69 Catalog fi 769 4DN A Revision id LJ Cancel Apply Help 4 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 5 When the I O modules are configured click on the Summary tab Note the number of bytes of input and output data This will be used later when adding the adapter to the 1769 SDN s scanlist 6 Click Apply then OK to save the configuration and download it to the adapter Communicating with Devices on a DeviceNet Link 8 5 p 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 Setting Up the 1788 DNBO DeviceNet Scanner Scanlist 1 Right click on the 1788 DNBO and choose Properties General Module Scaniist Input Output ADR Sum
14. De energizing the Drive to Connect or Disconnect a Cable Understanding the Interface to the Drive Chapter 2 Placing and Configuring the Drive 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 amp DC terminals on the Power Terminal Block The voltage must be zero N ATTENTION Severe injury or death can result from electrical During the process of placing and configuring the drive you will need to connect or disconnect a programming or network cable at the controller You should do this only if the drive is de energized 1 Turn off and lock out input power Wait five minutes 2 Verify that there is no voltage at the drive s input power terminals 3 Measure the DC bus voltage at the DC amp DC terminals on the Power Terminal Block The voltage must be zero 4 Connect or disconnect the programming or network cable 5 Turn power back on and proceed with placing and configuring the drive The DriveLogix controller supports a direct connection to the drive consisting of 21 inputs and 21 outputs The tag names and data types associated with the inputs and outputs are determined by the communication format selection Currently the following five communications formats are available Speed Control for typical speed regulated applications Position Control for typical positioning applications Motion Co
15. What is DriveLogix5730 Legend The controller performs system overhead functions for up to 1 ms at a time If the controller completes the overhead functions in less than 1 ms it resumes the continuous task As the system overhead percentage increases time allocated to executing the continuous task decreases If there are no communications for the controller to manage the controller uses the communications time to 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 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 9ms 1ms 20 4ms 1ms 33 2ms 1ms 50 1 ms 1ms TIP For typical DriveLogix applications a setting of 20 33 is recommended At the default time slice of 10 system overhead interrupts the continuous task every 9 ms of continuous task time as illustrated below a Task executes periodic Task is interrupted suspended system overhead 1 ms 1 ms continuous task 9 ms 9 ms 0 5 10 15 20 25 elapsed time ms What is DriveLogix5730 1 11 The interruption of a pe
16. ITT Enable Bootp Duplex require module reset MM Enable DHCP DHCP must be configured to return a fixed address IV Enable DNS IV Auto Negotiate Port Speed and Duplex __Refesh TT Status Running Cancel Apply Help 6 9 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 1 From the Communications menu select Configure Drivers 2y RSLinx Gateway File Edit View Communications Station DDE OPC Secur g a S SY Configure Client Applications Configure CIP Options Configure Gateway Driver Diagnostics CIP Diagnostics Gateway Diagnostics 2 Select EtherNet IP Driver from the list of Available Driver Types Then Click Add New Available Driver Types Close Ethernet devices z Add New R5 232 DFI devices Help Ethernet devices fee E themet IP Driver 1784 KT KTX D PKTX D PCMK for DH DH 485 devices 1784 KTCfX for ControlNet devices DF1 Polling Master Driver 1784 PCC for ControlNet devices 1784 PCIC S for ControlNet devices 1747 PIC 2 AIC Driver Startup DF1 Slave Driver 5 5 SD SD2 for DH devices Start Virtual Backplane SoftLogix58xx DeviceNet Drivers 1784 PCD PCIDS 1770 KFD
17. Message Configuration SendeMaiText xi Configuration Communication Tag Path Embedded_EtherNet_Port Browse Embedded_EtherNet_Port Communication Method CIP DH Channel T Destination Lint 0 F Gc l IP ith Source Link ji Destination Node 0 Octal 7OUTCE J J Connected Z Cache Connectior e O Enable Enable Waiting Start Done Done Length 0 Error Code Extended Error Code J Timed Out Error Path Error Text 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 This indicates that the mail relay server placed the email message in a queue for delivery It does not mean the intended recipient successfully received the email message Possible codes that could be in this destination element are Extended Error Code Error Code hex hex Description 0x00 none Delivery successful to the mail relay server 0x02 none Resource unavailable The email object was unable to obtain memory resources to initiate the SMTP session 0x08 none Unsupported Service Request Make sure the service code is 0x4B and the Class is 0x32F 0x11 none Reply data too large The Destination string must reserve space for the SMTP server reply message The maximum reply can be 470 bytes 0x13 none Configuration data size too short The Source Length is less than the Source Element string siz
18. e Click on the OK button 13 In the Motion Group Wizard dialog move each axis from the Unassigned box to the Assigned box by clicking on the axis name and then clicking the Add button 14 Click the Next button Motion Group Wizard Grouped Axis Axis Assignment x Motion Group Wizard Grouped_Axis Axis Assignment x Unassigned d Axis01 Unassigned Assigned AxisOO Add gt lt Remove Cancel Cancel Bac Next gt Finish Help Configuring DriveLogix Motion 4 9 15 Finish creating the new Motion Group a Set the Coarse Update Period to 4ms for version 13 xx or lower or to 2ms for version 15 xx or higher This is the minimum time usable with DriveLogix motion b Set the Auto Tag Update to Enabled c Set the General Fault Type to Non Major Fault d Click the Finish button Motion Group Wizard Grouped Axis Attribute Coarse Update Period A j ms in 0 5 increments Auto Tag Update Enabled X General Fault Type Non Major Fault vv Scan Times elapsed time Max us Last us Cancel Finish Help 16 Configure Axis00 a Right click on the axis you want to configure Axis00 in this example b Select Properties in the menu 3 5 Motion Groups amp Grouped_Axis XD axis Goto Module a Ungroup Trends Monitor Axis Tag E Data Types User De Fault Help Ep Strings ER Predefir E Module amp Cut Ctrl x 1 0 Configu Copy Ctrl C Backplat e
19. v 5ft OvrTrviCnfg Alarm Sft OvrTrviCnfg Alarm Hrd OvrTrviCnfg Alarm Hrd OvrTrviCnfg Alarm Position ErrCnfg Alarm 13 0500 Amps Ox4150C mSec 200 0x3F800 NENNNBE Bee O ee ee FI Al Al Fi Al 1 Al Al Al Al Fi FI Fi tCoastStop Ignore Ignore arm arm tCoastStop arm 0000 Ignore arm arm arm arm tCoastStop tCoastStop tCoastStop Last State tCoastStop Last State 10 0000 20 Ignore Ignore Ignore Ignore Ignore Ignore Ignore 0 1000 Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore Zero Data Ignore Zero Data 200 0000 400 tCoastStop ItCoastStop tCoastStop tCurLimStp tCurLimStp tCurLimStp tCurLimStp 000 0000 tCoastStop tCurLimStp tCurLimStp tCoastStop tCurLimStp tCurLimStp tCoastStop tCoastStop ast State tCurLimStp ast State me a N a ea M a N Fi FI FI FI FI FI FI Al F Al Al Al Al Al tCoastStop tCoastStop tCoastStop tCoastStop tCoastStop tCoastStop tCoastStop arm tCoastStop arm arm arm arm arm Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore Ignore tCurLimStp tCurLimStp tCurLimStp tCurLimStp tCurLimStp tCurLimStp tCurLimStp tCoastStop tCoastStop tCurLimStp tCurLimStp tCurLimStp tCurLimStp tCurLimStp Parameter color descriptions Changeable Run Read Only Read Only Linked 7 Placing and Configuring the Drive 2 19 Using Exist
20. 15 x or earlier tag that uses the COORDINATE SYSTEM data type 60 bytes Vv 13 x or earlier program 12 bytes Y task 4 bytes Y user defined data type 4 bytes Y I O module 16 bytes Y Y 8 bytes 8 bytes produced or consumed tag 8 bytes Y Restrictions Restriction Forcing is not supported between the PowerFlex 700S and DriveLogix This firmware version has these restrictions Description The forcing values can be set for the controller inputs and outputs However these values will not be used by the Logix program nor will they be transmitted to the PowerFlex 700S Unsupported Motion Commands The following Logix Motion Instructions are not intended for use with DriveLogix and the PowerFlex 700S Motion State for 1756 MO2AE Only e MDO Motion Direct Drive On e MDF Motion Direct Drive Off Motion Configuration for tuning SERCOS cards only e MAAT Motion Apply Axis Tuning e MRAT Motion Run Axis Tuning e MAHD Motion Apply Hookup Diagnostics e MRHD Motion Run Hookup Diagnostics Power down banks of local I O when the controller is powered down When powering down the controller the host drive also power down any banks of local I O modules Leaving additional banks of I O modules powered on may result in major fault code 22 during the power up process of the controller C 2 Application Restrictions Restriction In a Tag of a User defined Data Type an Instruction May Write Past t
21. 3 0 ms E Module Properties Controller 2 PowerFlex 700S 2 400V 3 1 General Connection Associated Axes Module Info Power Setup Requested Packet Interval RPI mm ms 1 0 100 0 ms I Inhibit Module I Major Fault On Controller If Connection Fails While in Run Mode r Module Fault Status Offline Cancel Apply Help b Click on the Associated Axis tab and click the New Axis button to assign a channel to Axis00 E Module Properties Controller 2 PowerFlex 700S 2 400V 3 1 General Connection Associated Axes Module Info Power Setup Servo Update Period us Associated Axes Channel O Primary 2 gt New Axis Channel 1 Auxiliary lt none gt d f Status Offline Cancel Apply Help c In the New Tag dialog create a new tag structure for Axis00 by typing Axis00 in the Name field and clicking the OK button d Onthe Associated Axis tab click the New Axis button to assign a channel to Axis01 Configuring DriveLogix Motion e In the New Tag dialog create a new tag structure for Axis01 by typing Axis01 in the Name field and clicking the OK button x Description Cancel Help Usage r 3 v Type Base v Alias For z Data Type AXIS_GENERIC EA Scope 5 Motion_Drive X Style I Open AXIS_GENERIC Configuration On the Associated Axis tab click the drop down arrow next to Channel 0 Primary and select Axis00 On the Associate
22. Chassis Ground For this Wire Pair Connect this Wire To this Terminal white orange orange with white stripe 5 Data A white with orange stripe 4 Data B blue white white with blue stripe cut back no connection blue with white stripe 3 Common shield drain non jacketed 2 Shield To prevent confusion when insta immediately after the insulation ling the communication cable cut back the white with blue stripe wire jacket is removed This wire is not used by DH 485 9 8 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 Add jumpers to connect pin 6 Termination to pin 5 Data A on the first and last PHYSICAL devices Termination 6x AORA Oie gt 6 Termination DataA 5 i i t 7 gt 5 Data A DataB 4 WH OR xX xX WH OR gt 4 DataB I I Common 3 lt H BU BU z gt gt 3 Common Shield 2 lt L gt 2 Shield Chassis Ground 1x gt gt 1 Chassis Ground Add jumper to connect pin 1 Chassis Ground to pin 2 Shield on the first PHYSICAL device Important A device s physical location may be independent of its node address Make sure you ground and terminate the proper PHY
23. Communication Tag Message Type CIP Generic is Sene Set Attribute Sne x Source Element fEmaiConfig Source Length po a Bytes ag fio Hex Class ER Hex Deere F Instance D Attributef5 Hex Wea Enable Enable Waiting Start Done Done Length 0 Error Code Extended Error Code IT Timed Out Error Path Error Text Cancel Apply Help In this field Enter Service Type Set Attribute Single Instance 1 Class 32f Attribute 5 Source Element the STRING tag that contains the IP address or host name of the mail relay server In this example enter EmailContfig Source Length the number of characters in the IP address or host name of the mail server plus 4 In this example enter 17 13 characters in the IP address 10 88 128 111 4 2 On the Communication tab of the Message Configuration set the Path e g browse for the Embedded EtherNet Port Click Apply Click OK Message Configuration SetupEMailServer P xl Configuration Communication Tag Path Embedded_EtherNet_Port Embedded EtherNet Port Communication Method CIP C DH Channel co CIP with Source ID I Connected J Cache Connections O Enable Enable Waiting Start Done Done Length 0 Error Code Extended Error Code I Timed Gut Error Path Error Text OK Cancel Apply Help 6 28 Communicating with Devices on an EtherNet IP Link C
24. ES ControlNet RSNetWorx for ControlNet Eile Edit View Network Device Diagnostics Tools Help S W Single Pass Browse xj Continuous Browse IV Edits Ends Onine F10 gt NetworkUp Enable Edits chedulec oa 2 Unschedule Cancel ede Schedule z Upload from Network Download to Network Hardware Download Minimum to Network E Controle Keeper Status lex 5 Categ Scanner Signature Status Communication Adapter 5 ControlNet to SCANport a DC Drive No Drive Object E3 DPI to ControlNet Lh imaan Machina Takaefacn 7 7 7 8 3 Communicating with Devices on a ControlNet Link In the Network menu select Properties ControlNet RSNetWorx for ControlNet Eie Edit View Network Device Diagnostics Tools Help E W Single Pass Browse Gontinuous Browse F Edits Ene 255 Online F10 Network Up Enable Edits Unschedule Sree Network Usag x Upload from Network Download to Network Download Minimum to Network Keeper Status Scanner Signature Status Hardware Properties Communication Adapter ControlNet to SCANport PE DC Drive No Drive Object DPI to ControlNet Lh inan Rlachina Inka ann Net
25. PLC 5 writes to DriveLogix5730 SLC writes to DriveLogix5730 SLC 5 05 SLC 5 04 OS402 and above SLC 5 03 OS303 and above TIP You can map as many tags as you want to a PLC 3 PLC 5 or SLC controller You can map only one tag to a PLC 2 controller The following table shows example source and destination tags and elements for different controller combinations Example Source and Destination source element N7 10 destination tag array 1 The PLC 5 PLC 3 and SLC controllers support logical ASCII addressing so you do not have to map a compatibility file for MSG instructions initiated by a PLC 5 PLC 3 or SLC controller Place the DriveLogix5730 tag name in double quotes You could optionally map a compatibility file For example if you enter 70 for the compatibility file you enter N10 0 for the destination tag PLC 2 writes to DriveLogix5730 source element 010 destination tag 200 The destination tag is the three digit PLC 2 address you specified for PLC 2 mapping 7 14 Communicating with Devices on a ControlNet Link Type of MSG Instruction PLC 5 reads from DriveLogix5730 SLC reads from DriveLogix5730 SLC 5 05 SLC 5 04 OS402 and above SLC 5 03 OS303 and above Example Source and Destination source tag array 1 destination element N7 10 The PLC 5 PLC 3 and SLC controllers support logical ASCII addressing so you do not have to map a compatibility file for MSG instructions initiated by a PLC 5 PLC 3
26. Specific point on the I O module depends on the size of the I O module 0 31 for a 32 point module The following examples show addresses for data in a DriveLogix5730 system Example I O module on the local CompactBus utilizing two banks 2 3 45 al 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 1 output module in slot 2 LOCAL Bank 1 Local 2 C Local 2 1 Local 2 0 analog input module in slot 3 LOCAL Bank 2 Local 3 C Local 3 1 analog output module in slot 4 LOCAL Bank 2 Local 4 C Local 4 1 Local 4 0 analog input module in slot 5 LOCAL Bank 2 Local 5 C Local 5 1 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 Description I O structure Local 1 I Data 0 0 The aliases describe the specific I O Local 1 1 Fault 0 points alias light on Local 1 I Data 0 0 module failed Local 1 1 Fault 0 Direct Connections for I O Each local I O module uses a direct connection to the DriveLogix5730 Modules controller A direct connection is a real time data transfer link between the controller and an I O module The controller maintains and monitors the connection between the controller and the I O module Any break in the connection such as
27. This product emits intense light and invisible radiation Do not look into module ports or fiber optic cable connectors ATTENTION This drive contains ESD Electrostatic Discharge sensitive parts and assemblies Static control precautions are required when installing testing servicing or repairing this assembly Component damage may result if ESD control procedures are not followed If you are not familiar with static control procedures reference A B publication 8000 4 5 2 Guarding Against Electrostatic Damage or any other applicable ESD protection handbook ATTENTION Only qualified personnel familiar with the PowerFlex 700S Drive and associated machinery should plan or implement the installation start up and subsequent maintenance of the system Failure to comply may result in personal injury and or equipment damage 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 amp DC terminals of the Power Terminal Block The voltage must be zero p 4 Overview Notes Chapter 1 What is DriveLogix5730 The DriveLogix controller is part of the Logix environment The DriveLogix controller provides a distributed control system built on these components e The DriveLogix5730 controller has one RS 232 port The controller supports the Logix instructions e RSLogix 5000 programming software
28. You could optionally map a compatibility file For example if you enter 70 for the compatibility file you enter N10 0 for the source tag PLC 2 reads from DriveLogix5730 source tag 200 destination element 010 The source tag is the three digit PLC 2 address you specified for PLC 2 mapping When the DriveLogix5730 controller initiates messages to PLC or SLC controllers you do not have to map compatibility files You enter the data table address of the target device just as you would a tag name SLC 5 05 controllers SLC 5 04 controllers OS402 and above and SLC 5 03 controllers OS303 and above support logical ASCII addressing and support PLC SLC mapping see the examples above For all other SLC or MicroLogix1000 controllers you must map a PLC 2 compatibility file see the PLC 2 examples above 6 24 Communicating with Devices on an EtherNet IP Link Using a MSG Instruction to Send an Email 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 sends an email message to an SMTP mail relay server using the standard SMTP protocol Some mail relay servers require a domain name be provided during the initial handshake of the SMTP session For these mail relay servers make sure you specify a domain name when you configure the network settings See 6 3 for information on configuring the network settings of the controller and specify
29. hardware address of the device you want to configure Ex File Tools Help r Request History Clear History Add to Relation List hr min sec Type Ethernet Address MAC 11 21 01 BOOTP 00 00 BC 07 00 74 11 20 59 BOOTP 00 00 BC 23 40 1F 4 3 BOOTP 0 Hostname m Relation List New Delete Enable BOOTE Enable SACE Disable BOOTR DHOP Ethemet Address MAC Type IP Address Hostname Description r Status Entries Unable to service BOOTP request from 00 00 BC 07 00 74 0 of 256 5 The New Entry window appears with the device s Ethernet Address MAC Enter the Ethernet address IP address subnet mask and gateway x Ethernet Address MAC 00 00 BC 23 A0 1F IP Address 010 091 013 210 Hostname H10 Embedded Description H10 Embedded Cancel Click OK Note The selected controller will verify that the IP address that has been assigned in this dialog does not belong to another device on the network If the IP address exists a warning message will display FEE File Tools Help r Request History Clear History Add to Relation List Ethernet Address MAC 11 21 01 BOOTP 00 00 8C 07 00 74 11 20 59 BOOTP 00 00 BC 23 40 1F 11 19 35 BOOTP 00 00 BC 23 40 1F Hostname The new entry then appears in the Relation List m Relation List New Delete e Enable DHCP Ethemet Addre
30. or SLC controller Place the DriveLogix5730 tag name in double quotes You could optionally map a compatibility file For example if you enter 70 for the compatibility file you enter N10 0 for the source tag PLC 2 reads from DriveLogix5730 source tag 200 destination element 010 The source tag is the three digit PLC 2 address you specified for PLC 2 mapping Producing and Consuming Data When the DriveLogix5730 controller initiates messages to PLC or SLC controllers you do not have to map compatibility files You enter the data table address of the target device just as you would a tag name SLC 5 05 controllers SLC 5 04 controllers OS402 and above and SLC 5 03 controllers OS303 and above support logical ASCII addressing and support PLC SLC mapping see the examples above For all other SLC or MicroLogix1000 controllers you must map a PLC 2 compatibility file see the PLC 2 examples above The DriveLogix5730 controller supports the ability to produce broadcast and consume receive system shared tags over a ControlNet link Produced and consumed data is accessible by multiple controllers over a ControlNet network Produced and consumed data are scheduled connections because 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 Tag type Description Specify produced These are
31. or software described in this manual Reproduction of the contents of this manual in whole or in part without written permission of Rockwell Automation Inc is prohibited Throughout this manual when necessary we use notes to make you aware of safety considerations circumstances that can cause an explosion in a hazardous environment which may lead to personal injury or death property damage or economic loss WARNING Identifies information about practices or Important Identifies information that is critical for successful application and understanding of the product circumstances that can lead to personal injury or death property ATTENTION Identifies information about practices or damage or economic loss Attentions help you e identify a hazard e avoid the hazard e recognize the consequences Shock Hazard labels may be located on or inside the equipment A e g drive or motor to alert people that dangerous voltage may be present Burn Hazard labels may be located on or inside the equipment e g drive or motor to alert people that surfaces may be at dangerous temperatures PowerFlex is a registered trademark of Rockwell Automation Inc DriveExplorer DriveExecutive and SCANport are trademarks of Rockwell Automation Inc PLC is a registered trademark of Rockwell Automation Inc Manual Updates Summary of Changes This information summarizes the changes to the DriveLogix5730 Controller for Power
32. 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 Data is the common name for values the are sent to or received from I O points SubMemberName Specific data related to a MemberName Bit optional Specific point on the I O module depends on the size of the I O module 0 31 for a 32 point module Example B E O Configuration Drivelogix5730 Ethernet Port Embedded EtherNet Port B 1794 AENT A Flex jo adapter SS 0 1794 141674 input module ER 1 1794 0616 4 output module ER 2 1794 IF280F2176 combo analog fesse on 2 PowerFlex 7005 2 400 Drive 6 14 Communicating with Devices on an EtherNet IP Link Device remote adapter FLEX io adapter Example Tag Names automatically created by the software FLEX_io_adapter FLEX_io_adapter SlotStatusBits FLEX_io_adapter Data FLEX_io_adapter O FLEX_io_adapter O Data remote input module in slot 0 rack optimized connection FLEX_io_adapter 0 C 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 remote output module in slot 1 rack optimized connection FLEX_io_adapter 1 C FLEX_io_adapter 1 C SSData F
33. the communication format 2 20 5 Placing and Configuring the Drive 4 In 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 E Module Properties Controller 2 PowerFlex 7005 2 400 1 5 General Connection Associated Axes Module Info Power Se Drive File New Drive dno Browse Found In lt File not found gt Launch DriveExecutive Q View and edit the parameter and link data associated with this drive ren REE 2x Fr Look in fa Projects amp ck e Samples Status Offline New Drive dno File name ExistingDivedno Files of type Drive Node Files dno gt Cancel TF Open as read only y A E Module Properties Controller 2 PowerFlex 7005 2 400 1 5 General Connection Associated Axes Module Info Power is Drive File C RASLogix 5000 Projects E xisting Drive dno Browse Found In C RSLogix 5000 Projects Click the Apply button Launch DriveE xecutive and then launch DriveExecutive amp View and edit the parameter and link data associated with this drive DriveE xecutive cannot be launched until pending edits are applied Status Offline Cancel Apply Help E Module Properties Controller 2 PowerFlex 7005 2 400 1 5 E xl General C
34. 2 751 Interp Speed 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 It connects the position regulator in the drive to the velocity loop 23 Speed Trim 3 55 Speed Comp This setup is for speed compensation to reduce position error 626 To DriveLogix00 155 Logic Status The status of the drive is sent to the DriveLogix 693 Intrep Synclnput 700 Motn Posit Sync The drive receives the synchronization pulse from the DriveLogix This keeps the interpolators synchronized 748 CoarsePosit Trgt 698 Motn Posit Cmmd The position interpolator of the drive receives the coarse position target from the DriveLogix Motion Interpolator 750 Coarse Spd Trgt 699 Motn Mx Pos Trvl The Speed loop of the drive receives the coarse velocity target from the DriveLogix Motion Interpolator Next make the appropriate parameter settings ie 7005 DriveLogix5730 Motion dno lt PowerFlex 7005 2 gt 5 Undefined Node 0 PowerFlex 7005 2 Linear List Ca Monitor Ca Motor Control Ca Dynamic Control Ca Speed Control C3 Torque Control C3 Process Control C3 Position Control Speed Posit Fdbk C3 utility Ca Communication A A A 5 3 User Functions Ca Default Custom Linear List _ Parameter Na _ alue_ Un Min Spd
35. 2 400 1 5 General Connection Associated Axes Module Info Power Setup Firmware Version 1 005 Drive Rating asov 2 14 7 Status Offline Cancel Apply Help 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 2 14 Placing and Configuring the Drive 5 Once the power rating is selected apply your changes by selecting the Apply button E Module Properties Controller 2 PowerFlex 7005 2 400 1 5 General Connection Associated Axes Module Info Power Setup Firmware Version 1 005 Drive Rating Status Offline Cancel Apply Help 6 Select the Setup tab 7 Enter the file name for your DriveExecutive Lite parameter file then click the Apply button E Module Properties Controller 2 PowerFlex 7005 2 400 1 5 General Connection Associated Axes Module Info Power Setup Drive File New Drive dnd Browse Found In lt File not found gt Launch DriveExecutive amp View and edit the parameter and link data associated with this drive DriveExecutive cannot be launched until pending edits are applied Status Offline Cancel Apply Help 8 Click the DriveExecu
36. 5000 create a new project 1 From the File menu select New fa RSLogix 5000 GGF Edit View Search Logic Co B new Ctrl N Open Ctrl O New Component la 2 In the New Controller dialog define the project a Use Revision 15 or higher b Enter a Name for the project e g Motion_Drive c Click the OK button New Controller Vendor Allen Bradley Type PowerFlex 7005 2 DriveLogix5730 Controller gt LK Revision Cancel Help Name Motion_Drive Description Create In c ASLogix 5000 Projects Browse Configuring DriveLogix Motion 3 In the Controller Organizer a Right click on the I O Configuration folder b Select New Module from the menu 5 8 Controller Motion Drive Controller Tags Controller Fault Handler G Power Up Handler 5 6 Tasks MainTask G MainProgram FH Unscheduled Programs Phases 5 8 Motion Groups Ungrouped Axes Trends 5 6 Data Types ER User Defined El Eg Strings E E Predefined Ga Module Defined g i SR Bacil J New Module 4 In the Select Module dialog click the plus sign next to Drives to expand the selection E Select Module mmunications Drives Motion Other By Category By Vendor Favorites 4 3 4 4 Configuring DriveLogix Motion 5 Select the desired drive PowerFlex 700S 2 400V in this example and click the OK button E Select Module Module Description Vendor Communicati
37. Arm Watch MDW Motion Disarm Watch MAR Motion Arm Registration MDR Motion Disarm Registration MAOC Motion Arm Output Cam MDOC Motion Disarm Output Cam Motion Group MGS Motion Group Stop MGSD Motion Group Shutdown MGSR Motion Group Shutdown Reset MGSP Motion Group Strobe Position 4 22 Configuring DriveLogix Motion Notes De energizing the Drive to Connect or Disconnect a Cable Configuring Your System for a Serial Link Chapter 5 Communicating with Devices on a Serial Link 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 amp DC terminals on the Power Terminal Block The voltage must be zero N ATTENTION Severe injury or death can result from electrical During the process of configuring serial communication you will need to connect or disconnect a programming or network cable at the controller You should do this only if the drive is de energized 1 Turn off and lock out input power Wait five minutes 2 Verify that there is no voltage at the drive s input power terminals 3 Measure the DC bus voltage at the DC amp DC terminals on the Power Terminal Block The voltage must be zero 4 Connect or disconnect the programming or network cable 5 Turn power back on and proceed with configuring serial communication For the DriveLogix controller to operate on a serial network
38. Bridge w Enhanced Web Services 1 788 MODULE Generic 1788 Module Drivelogix5730 Ethernet 10 100 Mbps Ethernet Port on DriveLogix5730 Show Vendor fa z IV Other IV Specialty 1 0 Select All Clear All IV Analog IV Digital IW Communication IV Motion IV Controller Cancel Help Module Properties Controller 4 1788 DNBO A 2 1 xl Type 1788 DNBO A 1788 DeviceNet Scanner Vendor Allen Bradley Name Devicen et Scanner Slot 4 a Description Revision Pra gt Input Size fi 24 a 32 bit utput Size bit 0 Size 123 Sj B2bit Status Size 32 x 32 bit Electronic Keying Compatible Module x Cancel lt Back Next gt Finish gt gt Help Enter a Name for the port and make sure it is assigned to slot 4 Click Finish 8 10 Communicating with Devices on a DeviceNet Link If you are using a 1769 SDN Scanner Module add it to the local CompactBus 1 In the Controller Organizer select the I O Configuration folder Right click the selected Local CompactBus and select New Module fg RSLogix 5000 DeviceNet Example PowerFlex 7005 2 File Edit View Search Logic Communications Tools Window alga a sale fT Offline 0 E RUN l Path No Forces b E Ok E NoEds 3 se Aik W yf Fave 2 Select the 1769 SDN DeviceNet Scanner from the list of possible EJ Controller DeviceNet_Example A Controller Tags
39. Defined UserDefinedIntegerData 0 617 FromDriveLogix15 User Defined UserDefinedIntegerData 1 618 FromDriveLogix16 User Defined UserDefinedIntegerData 2 619 FromDriveLogix17 User Defined UserDefinedIntegerData 3 620 FromDriveLogix18 User Defined UserDefinedIntegerData 4 621 FromDriveLogix19 User Defined UserDefinedIntegerData 5 622 FromDriveLogix20 User Defined Controller Input Tag Element Drive Parameter Linked Parameter LogicStatus 626 To DriveLogix00 155 Logic Status UserDefinedRealData 0 627 To DriveLogix01 User Defined UserDefinedRealData 1 628 To DriveLogix02 User Defined UserDefinedRealData 2 629 To DriveLogix03 User Defined UserDefinedRealData 3 630 To DriveLogix04 User Defined UserDefinedRealData 4 631 To DriveLogix05 User Defined UserDefinedRealData 5 632 To DriveLogix06 User Defined UserDefinedRealData 6 633 To DriveLogix07 User Defined UserDefinedRealData 7 634 To DriveLogix08 User Defined UserDefinedRealData 8 635 To DriveLogix09 User Defined UserDefinedRealData 9 636 To DriveLogix10 User Defined UserDefinedRealData 1 0 637 To DriveLogix1 1 User Defined UserDefinedRealData 1 1 638 To DriveLogix12 User Defined UserDefinedIntegerData 0 639 To DriveLogix13 User Defined UserDefinedIntegerData 1 640 To DriveLogix14 User Defined UserDefinedIntegerData 2 641 To DriveLogix15 User Defined UserDefinedIntegerData 3 642 To DriveLogix16 User Defined UserDefinedIntegerData 4 643 To DriveLogix17 User Defin
40. Driv Pow Delete Del SRF Con Motion Direct Commands Cross Reference Ctrl E Print Properties 4 10 Configuring DriveLogix Motion 17 On the General tab a Associate the module with the drive Match the Module name with the drive s name in the I O Configuration b Set the Channel to the channel being used for the encoder Channel 0 must be selected for the Servo axis and Channel 1 can be used only for feedback 5 Axis Properties Axis00 General Motion Planner Units Conversion Homing Dynamics Tag Axis Configuration Servo i Motion Group Grouped_Axis x El Associated Module Module Module Type PowerFlex 7005 2 400V Channel 0 X 18 On the Motion Planner tab determine how many Output Cam execution nodes instances are created for a specific axis The value specified for Output Cam Execution Target in the MAOC instruction references a specific instance in which a value of zero selects the first instance 5 Axis Properties Axis00 General Motion Planner Units Conversion Homing Dynamics Tag Output Cam Execution Targets Program Stop Action Fast Stop S IV Master Delay Compensation I Enable Master Position Filter m Cancel Help Configuring DriveLogix Motion 4 11 19 On the Units tab define the Position Units In this example the Position Units are revs revolutions Position Units can be almost anything e g degrees radia
41. INT DINT or REAL Example source element array_1 Specify the destination file type based on the destination device PLC 5 typed read S B N or F PLC 5 word range read S B N F I O A or D SLC B N or F Example source element N7 10 Communicating with Devices on an EtherNet IP Link 6 21 Supported Destination File Types Use the PLC 2 compatibility file Example destination tag 010 In the DriveLogix5730 controller specify the destination data type based on the destination device PLC 5 SINT INT DINT or REAL SLC INT REAL Example destination tag array_1 DriveLogix5730 reads from PLC 2 Use the PLC 2 compatibility file Example source element 010 In the DriveLogix5730 controller select one of these data types SINT INT DINT or REAL Example destination tag array_1 Typed read command 16 bit words in PLC 5 controller The typed commands maintain data structure and value The DriveLogix5730 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 32 bit words in DriveLogix5730 controller C gt 16 bit words in PLC 5 controller Word range read command 32 bit words in DriveLogix5730 controller 1 2 1 C gt The word range commands fill the
42. 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 The module s outputs turn off If you inhibit a module but a connection to the module was not established perhaps due to an error condition or fault the module is inhibited The module status information changes to indicate that the module is inhibited and not faulted If you uninhibit a module clear the check box and no fault condition occurs a connection is made to the module and the module is dynamically reconfigured with the configuration you created for that module If you uninhibit the module and a fault condition occurs a connection is not made to the module The module status information changes to indicate the fault condition 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 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
43. Names automatically created by the software FLEX_io_adapter FLEX_io_adapter SlotStatusBits FLEX_io_adapter Data FLEX_io_adapter O FLEX_io_adapter O Data remote input module in slot 0 rack optimized connection FLEX_io_adapter 0 C 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 remote output module in slot 1 rack optimized connection FLEX_io_adapter 1 C FLEX_io_adapter 1 C SSData FLEX_io_adapter 1 0 FLEX_io_adapter 1 0 Data remote combo analog in slot 2 direct connection FLEX_io_adapter 2 C FLEX_io_adapter 2 C InputFllter FLEX_io_adapter 2 C InputConfiguration FLEX_io_adapter 2 C OutputConfiguration FLEX_io_adapter 2 C RTSInterval FLEX_io_adapter 2 C SSChOOuputData FLEX_io_adapter 2 C SSCH1OutputData FLEX_io_adapter 2 Scheduling the ControlNet Network 1 In the Network menu select Online Communicating with Devices on a ControlNet Link 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 2 ControlNet RSNetWorx for ControlNet Eile Edit View Network Device Diagnostics Tools Help ale m
44. OS402 and above SLC 5 03 OS303 and above TIP You can map as many tags as you want to a PLC 3 PLC 5 or SLC controller You can map only one tag to a PLC 2 controller The following table shows example source and destination tags and elements for different controller combinations Example Source and Destination source element N7 10 destination tag array_1 The PLC 5 PLC 3 and SLC controllers support logical ASCII addressing so you do not have to map a compatibility file for MSG instructions initiated by a PLC 5 PLC 3 or SLC controller Place the DriveLogix5730 tag name in double quotes You could optionally map a compatibility file For example if you enter 70 for the compatibility file you enter N10 0 for the destination tag PLC 2 writes to DriveLogix5730 source element 010 destination tag 200 The destination tag is the three digit PLC 2 address you specified for PLC 2 mapping Type of MSG Instruction PLC 5 reads from DriveLogix5730 SLC reads from DriveLogix5730 SLC 5 05 SLC 5 04 OS402 and above SLC 5 03 OS303 and above Communicating with Devices on an EtherNet IP Link 6 23 Example Source and Destination source tag array_1 destination element N7 10 The PLC 5 PLC 3 and SLC controllers support logical ASCII addressing so you do not have to map a compatibility file for MSG instructions initiated by a PLC 5 PLC 3 or SLC controller Place the DriveLogix5730 tag name in double quotes
45. SDNPT drivers PLC 5 DH Emulator driver Stop SLC 500 DH485 Emulator driver SoftLogix5 driver Remote Devices via Linx Gatewar EEL ER Configure xl 3 Select the default driver name i e AB ETHIP 1 or Choose a name for the new driver type in your own name 15 characters maximum aB_ETHIP 1 Cancel Then Click OK After you create the driver configure it to correspond to the Ethernet port on the Embedded EtherNet IP option board Communicating with Devices on an EtherNet IP Link 6 11 4 Select where the EtherNet IP devices reside The software locates valid IP addresses Configure driver AB_ETHIP 1 2 x Ethernet IP Settings Browse Remote Subnet IP Address Subnet Mask Click OK m Available Driver Types Close Ethemet IP Driver x Help m Configured Drivers Name and Description Status AB_ETHIP 1 A B Ethernet RUNNING Running Configure Startup Start Stop EEREL ER Delete 5 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 Over EtherNet IP between two devices Connections can be e controller to distributed I O or remote communication modules e produced and consumed tags e messages You indirectly determine the number of connections
46. UserDefinedIntegerData 4 618 FromDriveLogix16 User Defined UserDefinedIntegerData 5 619 FromDriveLogix17 User Defined UserDefinedIntegerData 6 620 FromDriveLogix18 User Defined UserDefinedIntegerData 7 621 FromDriveLogix19 User Defined UserDefinedIntegerData 8 622 FromDriveLogix20 User Defined Controller Input Tag Element Drive Parameter Linked Parameter LogicStatus 626 To DriveLogix00 155 Logic Status UserDefinedRealData 0 627 To DriveLogix01 User Defined UserDefinedRealData 1 628 To DriveLogix02 User Defined UserDefinedRealData 2 629 To DriveLogix03 User Defined UserDefinedRealData 3 630 To DriveLogix04 User Defined UserDefinedRealData 4 631 To DriveLogix05 User Defined UserDefinedRealData 5 632 To DriveLogix06 User Defined UserDefinedRealData 6 633 To DriveLogix07 User Defined UserDefinedRealData 7 634 To DriveLogix08 User Defined UserDefinedRealData 8 635 To DriveLogix09 User Defined UserDefinedRealData 9 636 To DriveLogix10 User Defined UserDefinedIntegerData 0 637 To DriveLogix11 User Defined UserDefinedintegerData 1 638 To DriveLogix12 User Defined UserDefinedIntegerData 2 639 To DriveLogix13 User Defined UserDefinedIntegerData 3 640 To DriveLogix14 User Defined UserDefinedIntegerData 4 641 To DriveLogix15 User Defined UserDefinedIntegerData 5 642 To DriveLogix16 User Defined UserDefinedIntegerData 6 643 To DriveLogix17 User Defined UserDefinedIntegerData 7 644 To DriveLogix18 User Defined UserDefinedIntege
47. Zero Speed Zero Speed 14000 0000 14000 0000 14000 0000 0 0100 0 0100 0 0000 5 0000 0 0000 14000 0000 705 2000 0000 500 0000 30000 3500 0000 kw 40 655 0000 2200000000 0000 2200000000 0000 2200000000 0000 2200000000 0000 14000 0000 14000 0000 14000 0000 14000 0000 14000 0000 14000 0000 14000 0000 14000 0000 14000 0000 14000 0000 1000 0000 15 0000 1000 0000 DPI Port 5 DPI Port 5 14000 0000 14000 0000 14000 0000 6553 5000 6553 5000 4 0000 5 0000 500 0000 Parameter color descriptions Changeable Run Read Only Read Only Linked 7 2 15 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 You can create additional links within the drive for use with the user defined tags in the controller 1 To view the setup screen select Display DriveLogix from the Drive drop down menu Then select the From DriveLogix tab poriveExecutive c RSLogix 5000 Projects New Drive dno lt Po 5 File Edit View Drive Peripheral Tools Window Help De W amp Connect to Drive Undefined Nod ea
48. a module fault causes the controller to set fault status bits in the input data area associated with the module Removal and Insertion Under Power RIUP While the DriveLogix5730 system is under power e any break in the connection between the power supply and the controller i e removing the power supply controller or an I O module may subject the logic circuitry to transient conditions above the normal design thresholds and may result in damage to system components or unexpected behavior e removing an end cap or an I O module may fault the controller and may also result in damage to system components ATTENTION The DriveLogix5730 controller does not support Monitoring I O Modules Placing and Configuring Local I O The DriveLogix5730 controller offers different levels at which you can monitor I O modules You can e use the programming software to display fault data See Displaying Fault Data on page 3 15 e program logic to monitor fault data so you can take appropriate action Refer to Logix5000 Controllers Common Procedures Programming Manual publication number 1756 PM001 for examples Displaying Fault Data Fault data for certain types of module faults can be viewed through the programming software To view this data select Controller Tags in the Controller Organizer Right click to select Monitor Tags Controller Tags quick_start controller Scope quick_start controlle z Show S
49. ad BPS ee By a Seg ee ea gle ee ee ER 3 1 Placing Local VO Modules soere hee ee Ae ee a a be ee de 3 2 Validating VO Layout 0 0 re ae eee E e ERE DER 3 3 Estimating RPD 69 6 aty spin a e rete deg Ege aden aliens ad SERGE AE Ghee fa Hoes ae 3 4 Determining When the Controller Updates I O 2 0 eee eee eee 3 4 Configuring the CompactBus 0 0 cece eee eee eee en ees 3 5 Configuring Local I O Modules 0 0 eee ee 3 7 Accessing VO Data sic ornare aia DPS Geet Oa Get Ooo eGo ag aaa 3 12 Direct Connections for I O Modules 00 c eee eee teens 3 14 Monitoring I O Modules 0 0 cece eee eens 3 15 Configuring I O Modules Using the Generic 1769 MODULE 3 17 Chapter 4 Chapter 5 Chapter 6 Chapter 7 Chapter 8 Configuring DriveLogix Motion De energizing the Drive to Connect or Disconnect a Cable 000 4 1 About this Chapter sic ea EM an E A a a ie west 4 1 System Requirements 0 0 cece ccc cece cence retreto 4 1 Programming the Controller 0 0 cece cen eee eens 4 2 Launching DriveExecutive from RSLogix 0 00 eee eee eee 4 14 Configuring the Drive with DriveExecutive Software 0 0 0 cece eee eee 4 16 Downloading the Settings and Links to the Drive 0 000000000 4 20 Additional Testing and Programming is Necessary 0 00 0 eee eee eee ee 4 20 Supported Motion Commands 0 0 0 cece
50. and Destination Logix based controller writes to Logix based source tag array_1 controller CIP Data Table Write destination tag array_2 Logix based controller reads from source tag array_1 Logix based controller CIP Data Table Read destination tag array_2 The source and destination tags e must be controller scoped tags e can be of any data type except for AXIS MESSAGE or MOTION_GROUP Communicating with other controllers over EtherNet IP The DriveLogix5730 controller also uses MSG instructions to communicate with PLC and SLC controllers The MSG instructions differ depending on which controller initiates the instruction 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 destination device SLC PLC 5 SINT INT DINT or REAL PLC 5 typed write S B N or F SLC INT REAL PLC 5 word range write S B N F I O A or D SLC B N or F Example source element array_1 Example destination tag N7 10 Type of MSG Instruction DriveLogix5730 writes to PLC 2 DriveLogix5730 reads from PLC 5 or SLC Supported Source File Types In the DriveLogix5730 controller select one of these data types SINT
51. button nox Scope Ethernet P 10 Exar 7 Show Show All z Sort Tag Name 7 Tag Name amp Value Force Mask Style Type Description a FDrive l REJ ino AB PF700S 2 SP _ Drive 0 ees eet AB PF700S 2 SP E H EtherNet_Bridge l Meret ist AB 1756_ENET_ EH H Flex io adapter 0 C Fre Rg AB 1794_DI_Dela 4 Flex_io_adapter 0 1 2 0000_000 Binary INT E F Flex io adapter 1 C titted keart AB 1794_D016 C 0 E 4 Flex_io_adapter 1 0 2 0000_000 Binary INT E H Flex io adapter 2 C Comat DE AB 1794_IF2XOF A Flex_io_adapter 2 1 AAS 535 AB 1794_IF2XOF A H Flex io adapter 2 0 ina Svart AB 1794_IF2ZXOF 4 Flex_io_adapter ES BER AB 1794_AEN_8 5 H Flex io adapter 0 fore fa 4B 1794 AEN 8 gt F EmailConfig n STRING EmailText A n EN EMAILSTRING F Em iStatus n CEY EMAILSTRING a gt Monitor Tags Edit Tags 7 6 26 Communicating with Devices on an EtherNet IP Link To include To From and Subject fields in the email use lt CR gt lt LF gt symbols to separate each of these fields The To and From fields are required the Subject field is optional Use a second set of lt CR gt lt LF gt symbols after the last one of these fields you enter For example To email address of recipient r 1 From email address of sender r 1 Su
52. connection has the tag name of drive module Controller Tags example controller Scope example controller x Show Show All z Sort Tag Name ha amp Value Force Mask gt Edive module o O E F drive_module 0 e Style sf AB PF7005_2 ser AB PF 00S_2 The following tables show the tag names and their relationship to parameters in the drive These examples use a module name of drive module Table 2 A Mapping for Speed Control Communication Format Controller Output Tag Element Drive Parameter Linked Parameter T ype LogicCommand 602 FromDriveLogix00 151 Logic Command SpeedRef1 603 FromDriveLogix01 10 Speed Ref 1 TorqueRef1 604 FromDriveLogix02 111 Torque Ref 1 SpdTorqModeSelect 605 FromDriveLogix03 110 Speed TorqueMode TorqueStep 606 FromDriveLogix04 116 Torque Step SpdRegDroop 607 FromDriveLogix05 86 Spd Reg Droop UserDefinedRealData 0 608 FromDriveLogix06 User Defined UserDefinedRealData 1 609 FromDriveLogix07 User Defined UserDefinedRealData 2 610 FromDriveLogix08 User Defined UserDefinedRealData 3 611 FromDriveLogix09 User Defined UserDefinedRealData 4 612 FromDriveLogix10 User Defined UserDefinedRealData 5 613 FromDriveLogix1 1 User Defined UserDefinedRealData 6 614 FromDriveLogix12 User Defined UserDefinedRealData 7 615 FromDriveLogix13 Us
53. ee eee A 1 DriveLogix5730 Certifications 00 knee ennen A 2 Real Time Clock Accuracy gl annen ei eect eee SE sod A 2 Controller LEDS 3 55 5 26 s ence Sig eas See ES eek go ek eee Be A 3 Embedded EtherNet IP Option LEDs 1 0 0 0 0 eee eee eee A 6 Battery Lieve cic neha hewn cows a Se eee ag howe aioe eh era we ae A 8 Access Procedures Removing Power from Drive and Compact VO 1 1 ee eee eee B 1 Opening Door Over Power Structure and Main Control Board B 2 Removing the Control Cassette from Frame 1 6 Size Drives 04 B 2 Removing the Outside Covers 1 0 0 cece teen eee n ees B 3 Removing the Inside Cover as getand nnm a ani e aa i B 3 Connecting the Battery s esr enina een Ea r seeds dan eee Seeded ae dae ee B 4 Replacing the Battery 0 2 cence nen nen eens B 5 Installing the Embedded EtherNet IP Option Board 0 000005 B 7 Installing the DriveLogix5730 Expansion Board 0 cece eee eee eee B 7 Installing the Compact I O Cable 0 0 0 ene ees B 8 Installing the Communications Daughtercard 00 cece eee eee B 9 Application Restrictions Additional Memory Requirements 0 0 cece cece cece eee eee C1 Restrictions sisean hos Gos Ae oh Rigs a eis Wega vg da Wee SR at ae oS C 1 Hold Last State and User Defined Safe State Not Supported C 3 Who Should Use This Manual Purpose of this Ma
54. eect enna 4 21 Communicating with Devices on a Serial Link De energizing the Drive to Connect or Disconnect a Cable 200 5 1 Configuring Your System for a Serial Link 2 0 0 0 cece eee eee 5 1 Example 1 Workstation Directly Connected to a DriveLogix Controller 5 6 Example 2 Workstation Remotely Connected to a DriveLogix Controller 5 7 Example 3 DriveLogix Controller to a Bar Code Reader 04 5 10 Communicating with Devices on an EtherNet IP Link De energizing the Drive to Connect or Disconnect a Cable 0004 6 1 Communicating Through the Embedded EtherNet IP Option 6 2 Controller Connections Over EtherNet IP 0 0 0 0 eee eee eee 6 11 Configuring Distributed I O 0 cee eee nee 6 12 Adding a Remote Controller css 0 eee cece eee enna 6 15 Producing and Consuming Data 0 ccc eee eens 6 15 Using a MSG Instruction to Send an Email 2 2 eee eee ee 6 24 Example 1 DriveLogix5730 Controller and Distributed VO wes s se eri od etd eases ee aa eae ne Sea ae gale eee sees 6 31 Example 2 Controller to Controller 62 0 eee cece cee eens 6 32 Communicating with Devices on a ControlNet Link De energizing the Drive to Connect or Disconnect a Cable 000 7 1 Configuring Your System for a ControlNet Link 0 0 0 eee eee eee eee 7 1 Configuring Distributed I O 0 0 urane nee
55. 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 For example if a DriveLogix5730 controller is consuming three tags that another controller consumes but the first tag is specified incorrectly none of the tags are transferred to the consuming DriveLogix5730 controller However one consumer failing to access shared data does not affect other consumers accessing the same data For example if the producing DriveLogix5730 controller from the previous example also produced tags for other consuming controllers but did so correctly those tags are still transferred to the additional consuming controllers 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 Ethernet port on the controller You can have a maximum of 32 connections through the Ethernet port Each produced tag uses one connection for the tag and the first configured consumer of the tag Each consumer thereafter uses an additional connection If you have a lot of data to produce or consume organize that data into an array An array is treated as one tag so it uses only one connection An array can be as large as 488 bytes which is also the limit of a produced or consumed tag Size Limit of a Produced o
56. fa 7 IV Other IV Specialty 1 0 Select All IV Analog IV Digital Clear All IV Communication IV Motion IV Controller Ctrl x Ctrl C Cancel Help Ctrl Del Cross Reference Ctrl E Module Fault Properties New Module 1769 1416 16 Point 120 AC Input General Connection Type 17691416 16 Point 120V AC Input Vendor Allen Bradley Parent Local Name finput_moduld Slot 1 Description m Module Definition Series Change Revision nE Electronic Keying Compatible Module Connection Input Data Format Integer Status Creating Cancel Help 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 3 8 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 e Input Data INT for 1769 input modules e Data INT for 1769 output modules gt TIP The DriveLogix5730 controller must own its local I O modules No other Logix based controller can own the local Compact I O The communication format determines the tag structure that is created for the module Assume that a 1769 IA16 Input module is in
57. in the table below Table 4 B Parameter Settings for DriveLogix Motion Configuration Parameter Value Description 13 Spd Ref2 Multi 1 Speed Ref 2 scale value 24 Spd Trim 3 Scale 0 003 Speed Trim 3 scale value 27 Speed Ref A Sel 2 Select Speed Ref 2 as the speed reference 146 FW TaskTime Self Jo Firmware Task Time Selection 147 FW Functions En 16 1 Position Control enabled 151 Logic Command BitO 1 Bit 0 bypasses the speed ramp in the drive Bit10 1 Bit 10 enables Inertia Comp Bit13 1 Bit 13 enables the position loop within the drive 222 Motor Fdbk Sel Pri 0 6 Select the Motor Speed Feedback being used This is also the feedback for the Servo Axis in DriveLogix Motion Group 600 Lgx Comm Format 19 This selects the format of the commands coming from DriveLogix 686 Motn Config Bits 0 2 Bit 0 Change the polarity of the feedback only feedback axis Bit 1 Enable Software Overtravel Limits Bit 2 Enable Hardware Overtravel Limits 701 FdbkAxis FdbkSel 1 10 This selects the feedback channel used for the Feedback Only axis in the Motion Group in DriveLogix Encoders Optional Feedback and SynchLink selections See User Manual for details 740 Position Control Bit1 1 This sets the position regulator to work with the DriveLogix Bit6 0 configuration and enables the Integral part of the regulator Bit 2 1 Bit 8 0 742 Position Ref Sel 0 This configures the drive position
58. loses its connection to the controller Or monitor the status of the drive module 1 2 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 J RSLogix 5000 example PowerFlex 7005 2 File Edit View Search Logic Communications Tools Bie 5 aale ele __ Offline i No Forces Be No Edits 2 F RUN FT ok F BAT EL Im M 1 0 T C3 Trends Expand the data as necessary E Data Types Oma Controller example CH Controle New Tag Ctrl FH Power U Sr H E Tasks ag MainTasl Edit Tags Main Verify Unsched Export Tags Motion Grouy AN U Ungroup Print gt ea Scope examplefcontroller x Show Show All 7 Sort Tas Name gt gD drive_module a 4 drive_module LogicStatus 2 0000_000 drive_module Active drive_module Running drive_module CommandDir drive_module ActualDir drive_module Accelerating drive_module Decelerating drive_module Jogging drive_module Faulted drive_module Alarm drive_module FlashMode _ odive_modu
59. members of the tag BSL FBC LFL BSR FFL LFU COP FFU SQL CPS FLL SRT DDT GSV SSV This restriction also applies to all previous revisions To prevent writing beyond the limits of the destination array make sure that the length operand of the instruction is less than or equal to the number of elements in the array Hold Last State and User Defined Safe State Not Supported Application Restrictions When 1769 Compact I O modules are used as local I O modules in a DriveLogix5730 system the local I O modules do not support the Hold Last State or User Defined Safe State features even though you can configure these options in the programming software e Ifa local I O module fails such that its communication to the controller is lost or if any module is disconnected from the system bus while under power the controller will go into the fault mode All outputs turn off when the system bus or any module faults e 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 e ProgToFaultEn e ProgMode e ProgValue e FaultMode e FaultValue For analog output modules e CHxProgToFaultEn e CHxProgMode e CHxFaultMode e wh
60. network You can have two controllers per one 1761 NET AIC converter but you need a different cable for each controller Connect one controller to port 1 9 pin connector and one controller to port 2 mini DIN connector RSLogix 5000 programming software to configure the serial port of the controller for DH 485 communications When attempting to go online or upload download a program using the Communications Who Active window in RSLogix 5000 software disable the Autobrowse feature to minimize traffic from RSLogix 5000 software on the DH 485 network Step 1 Configure the Hardware The RS 232 port is built in to the front of the DriveLogix5730 controller The 1769 L31 controller has two serial ports Connect the serial port to an RS 232 to RS 485 interface converter One possible converter is the 1761 NET AIC interface converter port 2 mini DIN 8 RS 232 p lt q dc power source selector switch Meter C O lt q terminals for external 24V dc power supply i Connect the serial port of the DriveLogix5730 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 DH485 Link 9 3 The cable you use to connect the controller depends
61. operation if no connections are connections are established configured No action required established If connections are configured check connection originator for connection error code solid green CIP connections The port has an IP address and CIP connections Normal operation No action required established Class 1 or Class 3 are established solid red duplicate IP The port has detected that the assigned IP address is Verify that all IP addresses are unique address already in use flashing red green self test The port is performing its power up self test Normal operation during powerup Link Status LNK indicator Condition Status Indicates Recommended Action off no link The port is not connected to a powered Ethernet Verify that all Ethernet cables are connected device Verify that Ethernet switch is powered The port cannot communicate on Ethernet flashing green self test The port is performing its power up self test Normal operation during powerup data transmission The port is communicating on Ethernet Normal operation and reception No action required solid green link OK The port is connected to a powered Ethernet device The port can communicate on Ethernet Normal operation No action required A 8 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
62. other routines You can also specify an optional program fault routine The controller executes this routine if it encounters an instruction execution fault within any of the routines in the associated program The Controller Properties dialog 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 1 View properties for the controller and select the Advanced fg RSLogix 5000 example PowerFlex 7005 2 File Edit View Search Logic Communications Te alem al PESI e lt 2 cal fS Controller Properties example Ioj x Offline fl M RUN General Serial Port System Protocol User Protocol Major Faults Minor Faults No Forces pi F Ok T Date Time Advanced SFC Execution Fie Nonvolatile Memory Memory NoEds 8 M BAT BEES E 1 0 1 D Controller Fault Handler 670753 faites Controller exam Power Up Handler lt none gt hd A Controller Te Ey Verity C3 Controller Fe System Overhead 2 A CH Power Up He TLLA Time Slice zp 2 Prin mea Tes n een Security None F rese s MainPro Cancel Help System overhead functions include e communicating with programming and HMI devices such as RSLogix 5000 software responding to messages e sending messages 1 10
63. power Wait five minutes Verify that there is no voltage at the drive s input power terminals Measure the DC bus voltage at the DC amp DC terminals on the Power Terminal Block The voltage must be zero B 2 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 Frame 5 Slide the locking tab up loosen the right hand cover screw and remove Frame 6 Loosen 2 screws at bottom of drive cover Carefully slide bottom cover down amp out Loosen the 2 screws at top of cover and remove Removing the Control Cassette from Frame 1 6 Size Drives 9 Task Description Q Open the door of the power structure and disconnect the cables that connect to the main board fB Loosen screws on face of cassette Remove the cassette RRVVREE Access Procedures Removing the Outside Covers Task Description Proper tightening torque for Q Loosen screws on face of front cover and remove O reassembly is 7 10 Ib in the cover Loosen screws on side of rear cover and remove the cover 2 2 2 2 2 2 2 2 Removing the Inside Cover Task Description Loosen screws on face of front cover and r
64. requires a firmware update not anew controller A major fault occurred To clear the fault either Turn the key switch from PROG to RUN to PROG Go online with RSLogix 5000 software solid red 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 The controller is storing or loading a project to or from nonvolatile memory Indicator CF Color off DriveLogix5730 Controller Specifications A 5 CompactFlash card LED A A 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 Follow Safety related practices of NFPA 70E ELECTRICAL SAFETY FOR EMPLOYEE WORKPLACES DO NOT work alone on energized equipment ATTENTION Do not remove the CompactFlash card while the controller is reading from or writing to the card as indicated by a flashing green CF LED This could corrupt the data on the card or in the controller as well as corrupt the latest firmware in the controller Description No activity flashin
65. selecting a faster RPI has no affect specialty e full sized 1769 SDN modules add 1 5 ms per module e 1769 HSC modules add 0 5 ms per module You can always select an RPI that is slower than listed above These considerations show how fast modules can be scanned not how fast an application can use the data The RPI is asynchronous to the program scan Other factors such as program execution duration affect I O throughput Determining When the The controller continually scans the control logic One scan is the time it Controller Updates I O takes the controller to execute the logic once Input data transfers to the controller and output data transfers to output modules are asynchronous to the logic scan gt TIP If you need to ensure that the I O values being used during logic execution are from one moment in time such as at the beginning of a ladder program use the Synchronous Copy instruction CPS to buffer I O data Refer to the Logix5000 Controllers Common Procedures Programming Manual publication number 1756 PMO001 for examples of I O buffering or to the Logix5000 Controllers General Instruction Set Reference Manual publication number 1756 RM003 for information on the CPS instruction Placing and Configuring Local I O 3 5 Configuring the When you create a DriveLogix5730 project the programming software CompactBus automatically creates the local CompactBus You must configure the CompactBus 1 Inthe Controller O
66. surrounds the pins on both ends of the cable You can also use a 1747 CP3 cable from the SLC product family This cable has a taller right angle connector housing than the 1756 CP3 cable 2 Connect the cable to the serial port on the controller Communicating with Devices on a Serial Link 5 3 Configuring the Serial Port of the Controller 1 In the Controller Organizer select the Controller folder Right click the selected folder and select Properties AJ RSLogix 5000 Serial Example PowerFlex 7005 2 File Edit View Search Logic Communications Tools W alala S VEF ol Offline fl M RUN No Forces a Ok No Edits a E SN EJ Hr 2 On the Serial tab specify serial port characteristics dE IF Pa PS D 5 fa Controller Properties Serial Example oj xj Date Time Advanced SFC Execution File Nonvolatile Memory Memory General Serial Port System Protocol User Protocol Major Faults Minor Faults Controller Tags Q verify l l l C3 Controller Fault Ha m Mode Sosem Show Offline Values 3 Power Up Handler SEE Report System Show Offline Values E E Tasks Print Baud Rate 19200 Eig MainTask 33 8 MainProgram Data Bits fe 7 2 Unscheduled Programs Pai None E Stop Bits 1 a Control Line No Handshake 7 I Continuous Carrier RTS Send Delay fo x20 ms ATS Off Delay fo x20 ms
67. tags that the controller produced for Enabled for producing other controllers to consume How many consumers allowed consumed These are tags whose values are produced by Controller name that owns the tag that the local controller wants another controller to consume Tag name or instance that the controller wants to consume Data type of the tag to consume Update interval of how often the local controller consumes the tag 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 However other consumers can still access their shared tags as long as their tags are specified correctly One consumer failing to access shared data does not affect other consumers accessing the same data Communicating with Devices on a 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 Each consumer thereafter uses an additional connection Size Limit of a Produced or Cons
68. the controller uses by configuring the controller to communicate with other devices in the system 6 12 Communicating with Devices on an EtherNet IP Link Configuring Distributed I O 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 Unscheduled messaging lets you send and receive data when needed The DriveLogix5730 controller supports 32 CIP connections over an EtherNet IP network The DriveLogix5730 controller supports distributed I O over a EtherNet IP 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 Ethernet port To communicate with distributed I O modules you add a remote adapter and I O modules to the I O Configuration folder of the controller To Add Distributed I O Build the I O Configuration in this Order 1 Add the remote adapter to the embedded EtherNet IP port of the controller 2 Add the I O modules to the remote adapter E RSLogix 5000 EtherNetIP_IO_Example PowerFlex 7005 2 File Edit View Search Logic Communications Tools Window H alala S yae elo Offline 0 E RUN Path kno No
69. the desired offset if any in position units the axis is to move upon completion of the homing sequence to reach the home position In most cases this value will be zero Sequence Select the event that will cause the Home Position to be set Sequence Type Description Immediate Sets the Home Position to the present actual position without motion Switch Sets the Home Position when axis motion encounters a home limit switch Marker Sets the Home Position when axis encounters an encoder marker Switch Marker Sets the Home Position when axis first encounters a home limit switch then encounters an encoder marker Important Selecting a Homing Sequence event will configure parameters 825 Dig In1 Sel and 826 Dig In2 Sel in the host PowerFlex 700S drive Limit If a limit switch is used indicate the normal state of that switch i e before being engaged by the axis during the homing sequence Switch Normally Open Normally Closed Direction For active homing sequences except for the Immediate Sequence type select the desired homing direction Forward The axis jogs in the positive axial direction until a homing event switch or marker is encountered then continues Uni directional in the same direction until axis motion stops after decelerating or moving the Offset distance Forward The axis jogs in the positive axial direction until a homing event switch or marker is encountered then r
70. uninhibited GSY Get System Value Class name MODULE Instance name Input module ttribute Name Mode Dest input mod mode 0 When on inhibits the module When off uninhibits the module SSV state input mod mode 2 SSY Set System Value Class name MODULE Instance name Input module ttribute Name Mode Source input mod mode 0 Sending Module Configuration Information The controller sends module configuration information once module connections are established ATTENTION If you make a configuration change to any A module in the system do one of the following to resend module configuration data e cycle power to the controller e inhibit and then uninhibit the bus e inhibit and then uninhibit the individual module e send a MSG instruction of type Module Reconfigure for information on configuring a MSG to send configuration data see the Logix5000 Controllers General Instructions Reference Manual publication 1756 RM003 3 12 Accessing I O Data 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 dependant on the setting of the individual compact I O modules Important The controller s response to a connection failure of any I O module is dependant on the configuration of the I O modules If any I O module has the Major Fault On Controller If Connection Fails W
71. xj Date Time Advanced SFC Execution File Nonvolatile Memory General Serial Port System Protocol User Protocol Major Faults Minor Faults The grayed out settings are selections Mode System Show Offline Values that do not apply to a DH 485 network Baud Rate hsm z Data Bits fe E Parity None id Stop Bits 1 fer Control Line No Handshake id FT Continuous Carrier RTS Send Delay fo x20 ms ATS Off Delay fo x20 ms Cancel Apply Help 9 4 Communicating with Devices on a DH485 Link Characteristic Specify these characteristics on the Serial Port tab default values are shown in bold 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 To optimize network performance assign node addresses in sequential order Initiators such as personal computers should be assigned the lowest address numbers to minimize the time required to initialize the network Token Hold Factor Number of transmissions plus retries that a node holding a token can send onto the data link each time that it receives the token Enter a value between 1 4 The default is 1 Maximum Node Address Specif
72. you load flash controller firmware via the ControlFlash or AutoFlash utilities you need a serial or EtherNet IP connection to the controller Flashing via an EtherNet IP connection is faster than the serial connection What is DriveLogix5730 1 3 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 HEA d fle Edt Yew Communications Staton QDE OPC Security Window Hep la x S amp 53 Bile x Not Browsing net Port 1769L35E Ethenet Poat S Fa Channa 0 OF1 Ej For Help press F1 NUM 8 11 03 65 13 AM 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 1 Make sure the appropriate network connection is made before starting 2 Start the ControlFlash utility Click Next when the Welcome screen appears 3 Select the catalog number of the controller and click Next 4 Expand the network until you see the controller If the required network is not shown first configure a driver for the network in RSLinx software If you use an Ethernet connection to load the firmware which is much faster than the serial connection the utility will require a valid IP address before c
73. you need e a workstation with a serial port e RSLinx software to configure the serial communication driver e RSLogix 5000 programming software to configure the serial port of the controller Important Limit the length of serial RS 232 cables to 15 2m 50 ft 5 2 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 a M q Serial Port rr oa EEZSSSe 8828 os s90000990000t To connect to the serial port 1 Select the appropriate cable The 1756 CP3 cable attaches the controller directly to the controller 1CD 1CD 2 RDX 2 RDX 3 TXD 3 TXD 4DTR 4DTR COMMON COMMON 6 DSR 6 DSR 7RTS 7RTS 8CTS 8 CTS 9 9 If you make your own cable it must be shielded and the shields must be tied to the metal shell that
74. 1 2 RDX 2 RDX 3TXD lt 3TXD __ 4DTR 4DTR COMMON COMMON __ 6DSR 6DSR 7RTS 7 8 CTS 8 9 9 3 Attach the cable shield to both connectors and tie the cable to both connectors 4 Connect the cable to the controller and the ASCII device The following table lists the default serial port configuration settings for the ASCII protocol You specify these settings on the User Protocol tab under Controller Properties 5 12 Communicating with Devices on a Serial Link This field Buffer size Configuring User Mode Description 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 I XON XOFF Select whether or not to regulate the flow of incoming data The default is disabled Echo mode Select whether or not to echo data back to the device from which it was sent The default is disabled Delete mode Select Ignore CTR or Printer for the delete mode The default is Ignore Programming ASCII instructions The controller supports ASCII instructions to communicate with ASCII devices Your RSLogix 5000 programming software CDROM includes programming examples using AS
75. 17 FromDriveLogix15 User Defined UserDefinedIntegerData 1 618 FromDriveLogix16 User Defined UserDefinedIntegerData 2 619 FromDriveLogix17 User Defined UserDefinedIntegerData 3 620 FromDriveLogix18 User Defined UserDefinedIntegerData 4 621 FromDriveLogix19 User Defined UserDefinedIntegerData 5 622 FromDriveLogix20 User Defined Controller Input Tag Element Drive Parameter Linked Parameter LogicStatus 626 To DriveLogix00 155 Logic Status FilteredSpdFdbk 627 To DriveLogix01 71 Filtered SpdFdbk OutputCurrent 628 To DriveLogix02 308 Output Current LocallOStatus 629 To DriveLogix03 824 Local I O Status PositionStatus 630 To DriveLogix04 741 Position Status PositionFdbk 631 To DriveLogix05 762 Position Fdbk PositionActual 632 To DriveLogix06 763 Position Actual PositionError 633 To DriveLogix07 769 Position Error UserDefinedRealData 0 634 To DriveLogix08 User Defined UserDefinedRealData 1 635 To DriveLogix09 User Defined UserDefinedRealData 2 636 To DriveLogix10 User Defined UserDefinedRealData 3 637 To DriveLogix1 1 User Defined UserDefinedRealData 4 638 To DriveLogix12 User Defined UserDefinedRealData 5 639 To DriveLogix13 User Defined UserDefinedIntegerDatal 640 To DriveLogix14 User Defined UserDefinedIntegerData 641 To DriveLogix15 User Defined UserDefinedIntegerDatal 642 To DriveLogix16 Use
76. 2 Type the desired DriveExecutive filename or browse for an existing one Then click Apply E Module Properties Controller 2 PowerFlex 7005 2 400 1 5 E Module Properties Controller 2 PowerFlex 7005 2 400 1 5 3 Click the Launch DriveExecutive button to launch DriveExecutive Lite 4 16 Configuring DriveLogix Motion Configuring the Drive with In DriveExecutive software connect to the drive and access the Display DriveExecutive Software DriveLogix dialog as shown below 1 From the Drive Menu select Display DriveLogix pdriveExecutive c RSLogix 5000 Projects 7005S DriveLog EL File Edit View Drive Peripheral Tools Window Help D W amp Connect to Drive Undefined Nod Seem ee Gonnect to Last 0 PowerF Linear Upload From 0 PowerFlex 7005 2 La Monito Download 0 PowerFlex 7005 2 Motor a Dynam Device Web Page 2 Speed Display Datalinks 2 Torque Display SynchLink 22 Proces Dis ogix 1 3 Positioi Speed Faults Events and Alarms 8 Utility Jr fii de 18 Comme em 8 Inputs 23 User Fi ER Defaull De 2 Click on the From DriveLogix tab Preset Speed 5 1a Dracat Cnaad A DriveLogix Setup PowerFlex 7005 2 xl From DriveLogix To DriveLogix 3 Verify that the Communication Format 18 gt _ Co
77. 240V AC Output gt Show Vendor fa 7 IV Other IV Specialty 1 0 Select All IV Analog IV Digital IY Communication IV Motion IV Controller Clear All Module Fault Cross Reference Ctrl E Properties Cancel Help 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 Controller Organizer The completed module will appear in the Type 1769 MODULE Generic 1769 Module Parent Local p Connection Parameters Assembly y Instance Size Name I Input 101 1 16 bit Description aj Output 104 u zi Configuration 102 0 a 16 bit Comm Format Input Data INT Slot 3 Module Properties Local 3 1769 MODULE 1 1 E xl Cancel Back Next gt The generic module requires you to specify more parameters of the module Important The values you enter for these parameters are device specific See the documentation for the device to determine which values to enter On the generic module screen you define the parameters of the module In this field Specify Name name of the module Description optional provide more details about the module Comm Format communication format 1769 analog output modules digital output modules analog combination modules and digital combination modules use Data INT 1769 analog inp
78. 5 o Decimal BOOL support the Hold Last State or User Defined Safe State features even though you can configure these options in the programming software Precautions should be taken to ensure that these settings do not create a hazard of injury or equipment damage When a compact I O module is configured to do so it will cause the controller to go into a faulted mode when the compact I O module fails and communication to the controller is lost or the compact I O module is Placing and Configuring Local I O 3 9 disconnected from the system bus while under power All outputs turn off when the system bus or any module faults 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 e ProgToFaultEn e CHxProgToFaultEn e ProgMode e CHxProgMode e ProgValue e CHxFaultMode e FaultMode e where CHx the channel number e FaultValue Any 1769 Compact I O modules used as remote I O modules in a DriveLogix5730 system do support the Hold Last State and User Defined Safe State features Inhibiting I O Module Operation In some situations such as when initially commissioning a system it is useful to disable portion
79. 5730 Controller Communicating with Devices on a 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 1 direct connection for each I O module 3 DriveLogix1 controller to remote 1794 ACNR15 1 DriveLogix1 to 4 remote I O modules through 1794 ACNR15 4 all I O modules configured as direct connection no connection to the 1794 ACNR15 total connections used 9 If you configured the remote I O modules as rack optimized you would only need a rack optimized connection to the 1794 ACNR15 reducing the above example by 3 connections In the following example one DriveLogix5730 controller communicates with another DriveLogix5730 controller over ControlNet Each DriveLogix controller has its own local I O DriveLogix5730 Controller DriveLogix1 FH 5 DriveLogix5730 Controller DriveLogix2 ea aaria Je o ControlNet count send count_msg EN i i lt n UF FY OF OP E OY oF oo workstation Example 2
80. 6 33 This example shows DriveLogix1 producing tagA and consuming tagB Ej DINT Decimal H E Predefined E Module Defined aa 1 0 Configuration ei e Drivelogix5730 Ethernet Port EtherNetIP_f Port fg Tag Properties tagB f Tag Properties tagA 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 For DriveLogix1 create a controller scoped tag and select the MESSAGE data type 2 Enter a MSG instruction In this example logic a message is sent when a specific condition is met When count_send is set the ladder logic sends the count_msg MSG count send count msg EN MSG JE 3 E Type Unconfigured Message Control count msg a 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 Use the Browse button to select the device that will receive the MSG instruction The communicati
81. B Allen Bradley DriveLogix 5730 Controller for PowerFlex 700S Drives with Phase II Control Firmware Version 15 04 User Manual Automation ban i NAMI Important User Information Solid state equipment has operational characteristics differing from those of electromechanical equipment Safety Guidelines for the Application Installation and Maintenance of Solid State Controls Publication SGI 1 1 available from your local Rockwell Automation sales office or online at http www rockwellautomation com literature describes some important differences between solid state equipment and hard wired electromechanical devices Because of this difference and also because of the wide variety of uses for solid state equipment all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable In no event will Rockwell Automation Inc be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment The examples and diagrams in this manual are included solely for illustrative purposes Because of the many variables and requirements associated with any particular installation Rockwell Automation Inc cannot assume responsibility or liability for actual use based on the examples and diagrams No patent liability is assumed by Rockwell Automation Inc with respect to use of information circuits equipment
82. CII instructions For information about using these examples see the Logix5000 Controllers Reference Manual publication 1756 RMO001 De energizing the Drive to Connect or Disconnect a Cable Chapter 6 Communicating with Devices on an EtherNet IP Link 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 amp DC terminals on the Power Terminal Block The voltage must be zero ATTENTION Severe injury or death can result from electrical During the process of configuring EtherNet IP communication you will need to connect or disconnect a programming or network cable at the controller You should do this only if the drive is de energized 1 Turn off and lock out input power Wait five minutes 2 Verify that there is no voltage at the drive s input power terminals 3 Measure the DC bus voltage at the DC amp DC terminals on the Power Terminal Block The voltage must be zero 4 Connect or disconnect the programming or network cable 5 Turn power back on and proceed with configuring EtherNet IP communication 6 2 Communicating with Devices on an EtherNet IP Link Communicating Th rough For the DriveLogix controller to operate on an Ethernet network you need the Embedded EtherNet IP Option a workstation with an appropriate EtherNet IP communication daughtercard RSLinx software to configure the EtherNet I
83. CRR1 CRR3 connects the right side of one bank of Compact I O to the right side of another This facilitates a vertical I O orientation Do ooo Cir lial or O oe MENN DEE gg 20D DL2 CL3 20D DL2 CR3 cama na al all al a als Ca FE Teor oP oro oF oP oP ESET Ee ER EERTE Re 1769 CRRX 1769 CLLX Validating I O Layout To validate your planned I O layout consider these requirements e Each module in a Compact I O system uses a set amount of backplane memory in addition to the data that the module stores or transfers As you add modules the minimum backplane RPI increases e The I O modules must be distributed such that the current consumed from the left or right side of the power supply never exceeds 2 0A at 5V de and 1 0A at 24V dc 3 4 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 Consider these guidelines when installing modules Type of Module Considerations digital and analog e 1 4 modules can be scanned in 1 0 ms any mix e 5 16 modules can be scanned in 1 5 ms e some input modules have a fixed 8 0 ms filter so
84. Controller Firmware Revision 0 00000 eee eee eee eee eens P 3 General Precautions 4 0 d Ae ree atk PAG eG Mesa ee a es oe E P 3 What is DriveLogix5730 Loading Controller Firmware 2 0 0 0 eee teen eens 1 2 Using CompactFlash 0 0 ccc enn nee nee enn eve 1 5 Developing Programs 5 25 hss ee ee ee be peed bee ea bese EEE 1 6 Selecting a System Overhead Percentage 0 eee eee eee 1 9 Understanding the Virtual Backplane 1 2 0 0 0 cece eee eee eee 1 12 Placing and Configuring the Drive De energizing the Drive to Connect or Disconnect a Cable 004 2 1 Understanding the Interface to the Drive 0 0 2 eee eee nee 2 1 Determining When the Controller Updates the Drive 0 000008 2 2 Placing and Configuring the Drive 0 0 eee eee ees 2 3 Inhibiting the Drive Connection 0 eee cece eee 2 11 Using DriveExecutive Lite senisesse ee cnet teenies 2 12 Accessing Drive Data is 15 4 9 sccntuat bod cnet bbs Gah Oia EO oS theta eed 2 21 Monitoring Drive Dat icc ses neela an Minin Ween wie dn ER 2 21 Configuring the Controller s Response to a Connection Failure 2 22 Recommended Programming Techniques 0 0 00 cece eee ee eens 2 25 Placing and Configuring Local I O De energizing the Drive to Connect or Disconnect a Cable 0004 3 1 Understanding How the DriveLogix5730 Supports VOdo SANDE Pee
85. DINTs Two times the number of DINTs or REALs in the produced tag REALs For example if the produced tag contains 10 DINTs enter 20 for the Message size 3 In the RSNetWorx software reschedule save the network The ControlNet PLC 5 controller does not perform type checking Make sure the PLC 5 data type can correctly receive the DriveLogix produced tag to ensure proper data is being received When a ControlNet PLC 5 controller consumes a tag that is produced by a Logix5000 controller it stores the data in consecutive 16 bit integers Communicating with Devices on a 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 Consuming a Tag from a ControlNet PLC 5 Controller To consume a tag from a ControlNet PLC 5 controller 1 In RSNetWorx software open the ControlNet configuration of the ControlNet PLC 5 controller insert a Send Scheduled Message 2 In RSLogix 5000 software add the ControlNet PLC 5 controller to the Controller Organizer 3 Create a user defined data type that contains these members Data type D
86. 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 task 8 task 1 configuration status watchdog program 32 program 1 program local main routine tags fault routine other routines controller global tags 1 0 data system shared data Defining tasks A task provides scheduling and priority information for a set of one or more programs You can configure tasks as continuous periodic or event Only one task can be continuous The DriveLogix5730 controller supports as many as eight tasks A task can have as many as 32 separate programs each with its own executable routines and program scoped tags Once a task is triggered activated all the programs assigned to the task execute in the order in which they are grouped Programs can only appear once in the Controller Organizer and cannot be shared by multiple tasks What is DriveLogix5730 1 7 Specifying task priorities Each task in the controller has a priority level The operat
87. DriveLogix15 User Defined UserDefinedIntegerData 1 642 To DriveLogix16 User Defined UserDefinedIntegerData 2 643 To DriveLogix17 User Defined UserDefinedIntegerData 3 644 To DriveLogix18 User Defined UserDefinedIntegerData 4 645 To DriveLogix19 User Defined UserDefinedIntegerData 5 646 To DriveLogix20 User Defined Placing and Configuring the Drive Table 2 B Mapping for Position Control Communication Format Controller Output Tag Element LogicCommand Drive Parameter 602 FromDriveLogix00 Linked Parameter 151 Logic Command 2 7 SpeedRef1 603 FromDriveLogix01 10 Speed Ref 1 PositionControl 604 FromDriveLogix02 740 Position Control CoarsePositTrgt 605 FromDriveLogix03 748 CoarsePosit Trgt PtPtPositRef 606 FromDriveLogix04 758 Pt Pt Posit Ref PositOffset1 607 FromDriveLogix05 753 Posit Offset 1 UserDefinedRealData 0 608 FromDriveLogix06 User Defined UserDefinedRealData 1 609 FromDriveLogix07 User Defined UserDefinedRealData 2 610 FromDriveLogix08 User Defined UserDefinedRealData 3 611 FromDriveLogix09 User Defined UserDefinedRealData 4 612 FromDriveLogix10 User Defined UserDefinedRealData 5 613 FromDriveLogix1 1 User Defined UserDefinedRealData 6 614 FromDriveLogix12 User Defined UserDefinedRealData 7 615 FromDriveLogix13 User Defined UserDefinedRealData 8 616 FromDriveLogix14 User Defined UserDefinedIntegerData 0 6
88. E 5 Electronic Keying Compatible Module h The selection you make for the Comm Format determines the communication format for the connection to the drive This determines the tag names and data types See page 2 5 Once you complete adding a module you cannot change this selection coct eo ra e Electronic Keying Electronic keying has no effect on drive module However the default setting Compatible Module is recommended Module Properties Controller 2 PowerFlex 7005 2 400 1 1 xl Type PowerFlex 7005 2 400V Drive Interface 400V Vendor Allen Bradley Parent Controller Name drive module Slot p Description i is the local PowerFlex 7005 4 Comm Format Speed Control X Revision E fi a Electronic Keying Compatible Module X Compatible Module Disable Keying Exact Match Cancel Back Next gt Finish gt gt Help Selecting Compatible Module allows you to enter the drive firmware minor revision Placing and Configuring the Drive 2 5 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 Module Properties Controller 2 PowerFlex 700S 2 400 1 5 J xl Type PowerFlex 700S 2 400V Drive Interface 400V Vendor Allen Bradley Parent Controller Name drive modu
89. Flex 700S Drives with Phase II Control publication 20D UM003 since the July 2004 release Change See Page Added information for contacting Technical Support and updated Controller Firmware Preface 2 Revision information Updated information and example for specifying task priorities 1 7 Updated information on controller fault response settings 3 2 3 6 3 8 and 3 1 Updated the System Requirements for configuring DriveLogix Motion 4 1 Updated the Coarse Update Period setting from 4ms to 2ms 4 9 Updated the tables for parameter links and parameter settings for configuring 4 18 and DriveLogix Motion 4 19 Updated the Communicating with Devices on an EtherNet IP Link procedures to reflect 6 4 the support of duplicate IP address detection Added information regarding updated MSG packet size 6 19 Added information regarding updated MSG packet size 7 9 Added a new Appendix for application restrictions soc 2 Summary of Changes Preface Chapter 1 Chapter 2 Chapter 3 Table of Contents Important User Information 0 cece ee neces 1 2 M nual Updates ide i tcl nan abn Be aM oak Gace Beare Mahe i 1 Overview Who Should Use This Manual 0 0 0 0 000 ccc eee eee eee P 1 Purpose of this Mantial ss yees pct oie andrea EN aoe ei en di ede P 1 Related Documentation o ss sneen aed eh eee eh ase Panes eee P 2 Contacting Tech Support 0 0 2c cette eee e ene neanes P 2
90. Forces pa OK a H BAT NoEds Bl rin 4 Ble D 4 gt Favorite J Controller EtherNetIP_IO_Example Controller Tags C3 Controller Fault Handler 9 Power Up Handler Tasks MainTask EH cy MainProgram 2 Unscheduled Programs Motion Groups FH Ungrouped Axes 1 Trends Data Types ER User Defined oe Strings H jh Predefined H E Module Defined J 1 0 Configuration e Drivelogix5730 Ethernet Port Embedded_EtherNet_Port 1794 AENT A Flex io adapter amp 0 1794 1416 4 input module amp 1 1794 0B16 4 output module Sr 2 1794 IF2XOF21 4 combo analog 2 PowerFlex 7005 2 400 Drive CompactBus Local Description Status Module Fault 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 Each tag name follows this format Location SlotNumber Type MemberName SubMemberName Bit 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 input O
91. LEX_io_adapter 1 0 FLEX_io_adapter 1 0 Data remote combo analog in slot 2 direct connection FLEX_io_adapter 2 C FLEX_io_adapter 2 C InputFllter FLEX_io_adapter 2 C InputConfiguration FLEX_io_adapter 2 C OutputConfiguration FLEX_io_adapter 2 C RTSInterval FLEX_io_adapter 2 C SSChOOuputData FLEX_io_adapter 2 C SSCH1OutputData FLEX_io_adapter 2 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 fg RSLogix 5000 EtherNetIP_IO_Example PowerFlex 7005 File Edit View Search Logic Communications Tools Window rc gt Cu EE Offline D M RUN Path No Forces b E ok Fre No Edits a aac Ki H k DB lro B Controller EtherNetIP_IO_Example A Controller Tags C3 Controller Fault Handler LI Power Up Handler 3 Tasks EG MainTask w MainProgram LI Unscheduled Programs B Motion Groups LI Ungrouped Axes I Trends lS Data Types ER User Defined H E Strings E Predefined E Module Defined B E 1 0 Configuration EH Td Drivelogix5730 Ethernet Port Embedded_EtherNet_Port amp 1794 AENT A Flex io adapter amp 0 1794 1416 4 input module amp 1 1794 0B16 4 output module amp 2 1794 IF2XOF21 A combo analog 0 1756 ENET B EtherNet_B
92. OOL SINT INT DINT or REAL you can select a display style This display style defines how the tag value will be displayed in the data monitor and ladder editor The display style does not have to match the display style of the tag in the remote controller Guidelines for Configuring Connections All consumed tags are automatically controller scope 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 Important If a consumed tag connection fails all of the other tags being consumed from that remote controller stop receiving data The 1788 CNx communication daughtercard supports 9 scheduled connections How you configure these connections determines how many devices the daughtercard can support The NUT and RPI also play a part in determining how many connections a 1788 CNx can support in a given application assuming the RPIs will be the same for all connections You must also make sure that you do not exceed the maximum number of bytes per NUT e With the NUT 5ms the limit is 3 connections e With the NUT 10ms the limit is 7connections e With the NUT gt 20ms the limit is 9 connections 7 18 Communicating with Devices on a C
93. P communication driver RSLogix 5000 programming software Version 13 or later to configure the embedded EtherNet IP option or NetLinx EtherNet IP communication daughtercard as part of the DriveLogix system an embedded EtherNet IP option card installed on the DriveLogix controller refer to Installing the Embedded EtherNet IP Option Board on page B 7 or a 1788 ENBT EtherNet IP communication daughtercard installed on the DriveLogix controller refer to Installing the Communications Daughtercard on page B 9 DriveLogix controller DriveLogix controller with with 1788 ENBT Embedded EtherNet IP Communications E Option Card Daughtercard d o Ja or UI G EtherNet IP EtherNet IP Determining Network Settings Before configuring the system you must determine several network settings 1 In the Run dialog box of Windows type cmd 3 Type the name of a program folder document or Internet resource and Windows will open it for you Open cmd x al 2 At the Command Prompt type ipconfig and note the values for the network settings pa Ie C WINNT system32 cmd exe C gt ipconf ig Cancel Browse Windows 2000 IP Configuration Ethernet adapter Local Area Connection Connection specific DNS Suffix domain com IP Address co ocs aao oa 210 91 13 12 Subnet Mask 255 255 255 0 Default Gateway 16 91 13 1
94. Parent Controller Name Hive module Slot gt 4 Description ik is the local PowerFlex 7005 4 Comm Format Sedeta LL Revision m fe a Electronic Keying Compatible Module v Status Offline Cancel Army Hep 2 3 4 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 Krig RSLogix 5000 example PowerFlex 7005 2 File Edit View Search Logic Communications Tools Window Help alela a see ool af Offline il No Forces b ae No Edits a F RUN w Path lt rone gt af HI fie 4 Evo o 4 H Favorites AEK Tir E Tasks Trends E Controller example Controller Tags C3 Controller Fault Handler C3 Power Up Handler ER MainTask E8 MainProgram 9 Unscheduled Programs Motion Groups 9 Ungrouped Axes S Data Types ER User Defined Ci Strings Cip Predefined Cip Module Defined ER 1 0 Configuration 2 PowerFlex 700 S CompactBus Local this is the local PowerFlex 700S ff New Module amp Cut Ctrl X Copy Ctrl C E Paste Ctrl V Delete Del Cross Reference Ctrl E E Module Properties Controller 2 PowerFlex 7005
95. Ref Lim Max Spd Ref Lim Accel Time 1 Decel Time 1 S Curve Time iL Motor NP Volts 460 Volt 460 2 Motor NP FLA 22 0000 Amps 0x41B0 3 Motor NP Hertz 60 0000 Hz 0x4270 4 Motor NP RPM 1750 RPM 1750 5 Motor NP Power 30 0000 Hp 0x41F0 6 Mtr NP Pwr Units Hp vf 0 7 Motor Poles 4 Pole 4 9 Total Inertia 2 0000 Sec 0x4000 10 Speed Ref 1 0 0000 0x0000 11 Spd Refi Divide 1 0000 Ox3F80 12 Speed Ref 2 0 0000 0x0000 13 Spd Ref2 Multi 0x3F80 14 Preset Speed1 0 0000 RPM 0x0000 15 Preset Speed2 0 0000 RPM 0x0000 16 Preset Speed3 0 0000 RPM 0x0000 17 Preset Speed4 0 0000 RPM 0x0000 18 Preset SpeedS 0 0000 RPM 0x0000 19 Preset Speed6 0 0000 RPM 0x0000 20 Preset Speed 0 0000 RPM Ox0000 21 Speed Trim 1 0 0000 RPM 0x0000 22 Speed Trim 2 0 0000 RPM 0x0000 23 Speed Trim 3 0 0000 RPM 0x0000 24 SpdTrim 3 Scale 1 0000 0 25 STrim2 Filt Gain 1 0000 26 SpdTrim2 Filt BW 200 0000 R S 27 Speed Ref A Sel Spee xl 28 Speed Ref B Sel Spee x 1 Jog Speed 1 0 0000 RPM 0x0000 2187 5 RPM 2187 50 RPM 10 0000 Sec 10 0000 Sec 8 Type the desired value Parameter 13 Spd Ref2 Multi Properties Value Link Source Link Sinks Documentation Attributes 4 19 Configuring DriveLogix Motion Value gt Internal Value fi 065353216 Parameter Help Dec C Hex C Bin Range Value Internal Value Minimum 2200000000 0000 821878442 Maximum 2200000000 0000 1325605206 Default 1 0000 1065353216 Make the parameter settings shown
96. SG configuration requirements See Example 2 above Configuring a MSG instruction for a PLC 5 controller depends on the originating controller For MSG instructions originating from the DriveLogix controller to the ControlNet PLC 5 controller Source Destination any integer element such as B3 0 T4 0 ACC SINT INT or DINT tag C5 0 ACC N7 0 etc any floating point element such as F8 0 REAL tag PD10 0 SP etc 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 SINT INT DINT or REAL N7 0 F8 0 etc Word Range Write SINT INT DINT or REAL any data type such as B3 0 T4 0 C5 0 R6 0 Type of MSG Instruction PLC 5 writes to DriveLogix PLC 5 reads from DriveLogix N7 0 F8 0 etc The PLC 5 controller supports logical ASCII addressing so you do not have to map a compatibility file for MSG instructions initiated by a PLC 5 controller Place the DriveLogix tag name in double quotes Example Source and Destination source element N7 10 destination tag array_1 source tag array_1 destination element N7 10 Example 3 Producing and Consuming Tags You can produce and consume tags with any Logix controller the same as you do with a DriveLogix controller All Logix controllers follow the same requirements fo
97. SICAL locations Communicating with Devices on a DH485 Link 9 9 Browsing a DH 485 Network To improve performance when browsing a DH 485 network configure the Remotely DH 485 network properties in RSLinx software to display only those nodes 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 On the Browse Addresses tab specify the lowest and highest addresses that exist on the DH 485 network AB DF1 1 Properties 2 x Browse Addresses Advanced Browse Settings IV Browse only the specified addresses Lowest address decimal 0 Highest address decimal 31 Cancel Apply Help If you do not specify a specific range of addresses on the DH 485 network the RSWho function in RSLinx software attempts to locate a device at every node address Trying to locate devices that do not exist adds considerable time to displaying the RSWho window for the network 9 10 Communicating with Devices on a DH485 Link Notes DriveLogix5730 Controller Specifications DriveLogix5730 Environmental Specifications Appendix A DriveLogix5730 Controller Specifications Category serial port CHO RS 232 Specification 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 connectivity options these options require the Logix Expansion Board and Expanded C
98. Sending a MSG Instruction To send a MSG from DriveLogix1 to DriveLogix2 1 For DriveLogix1 create a controller scoped tag and select the MESSAGE data type 2 Enter a MSG instruction In this example logic a message is sent when a specific condition is met When count_send is set the ladder logic sends the count_msg MSG 3 E END count msg EJ H lt DN gt t lt ER gt 7 20 Communicating with Devices on a 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 Tag to which the data will be transferred 4 On the Communication tab specify the communication path A communication path requires pairs of numbers The first number in the pair identifies the port from which the message exits The second number in the pair designates the node address of the next device For this item Specify Communication Path 1 4 2 27 1 0 where 1 is the virtual backplane of DriveLogix1 4 is 1788 CNC daughtercard in slot 1 2 is the ControlNet port 27 is the ControlNet node of DriveLogix2 1 is the virtual backplane of DriveLogix2 0 is the controller slot of DriveLogix2 Example 2 Producing and Consuming Tags Produced data must be of DINT or REAL data type or an array or structu
99. a DE 4 lz 0 PowerF Gonmect to Last 8 Linear Upload From 0 PowerFlex 7005 2 H a Monito Download 0 PowerFlex 7005 2 T 23 Motor 2a Dynam Device Web Page 1750 41 12 Speed Display Datalinks 30 0000 Ca Torque Display SynchLink OS Proces C3 Positior C2 Speed 2 Utility 2 Comme i ire Groups 0 0000 Ca Default Properties 0 0000 Refresh Node FS Preset Speed 5 19 Preset Speed6 0 0000 20 Preset Speed 0 0000 21 Speed Trim 1 0 0000 22 Speed Trim 2 0 0000 23 Speed Trim 3 0 0000 25 STrim2 Filt Gain 1 0000 From DriveLogix To DriveLogix Communication Format Speed Control x source Drwetoga Tag Vee Used By Parameter UserDetinedintegerData 0 UserDefinedintegerData 1 UserDefinedintegerData 2 UserDefinedintegerData 3 UserDefinedintegerData 4 UserDefinedintegerData 5 UserDefinedintegerData 6 UserDefinedintegerData 7 LogicCommand 0000000000000000 151 Logic Command Fas SpeedRef1 0 0000 10 Speed Ref 1 l TorqueRef1 0 0000 111 Torque Ref1 SpdTorgModeSelect Zero Torque 110 Speed TorqueMode TorqueStep 0 0000 P U 116 Torque Step SpdRegDroop 0 0000 P U 86 Spd Reg Droop l UserDefinedRealData 0 l UserDefinedRealData 1 cu UserDefinedRealData 2 f UserDefinedRealData 3 cu UserDefinedRealData 4 cu UserDefinedRealData 5 f UserDefinedRealData 6 cu Soon DriveLogix Connection Status Undetermined OK Cancel Apply Placi
100. alization 9 5 network planning 9 4 nodes 9 5 terminating 9 8 token rotation 9 4 DriveExecutive 2 12 E Email using an EtherNet IP msg 6 24 EtherNet IP accessing distributed I O 6 13 configuring communications driver 6 10 configuring network settings with BOOTP DHCP 6 3 configuring network settings with RSLinx 6 6 configuring network settings with RSLogix 5000 6 7 consuming tags 6 18 controller connections 6 11 controller to controller communication 6 31 determining network settings 6 2 distributed I O 6 12 6 31 Email 6 24 messages 6 19 producing and consuming data 6 15 producing tags 6 17 specifications A 1 F fault data 3 15 firmware loading 1 2 loading with AutoFlash 1 4 loading with CompactFlash 1 4 loading with ControlFlash 1 3 forcing values C 1 G Grounding DH 485 network 9 8 H Hold Last State and User Defined Safe State Not Supported C 3 0 accessing data 3 12 accessing distributed on ControlNet 7 5 accessing distributed on EtherNet IP 6 13 configuring local 3 7 ControlNet 7 4 DeviceNet 8 2 direct connections 3 14 distributed over EtherNet I P 6 12 6 31 end cap detections 3 15 generic 1769 MODULE 3 17 hold last state 3 8 inhibiting 3 9 layout 3 3 max modules A 1 max number banks A 1 module faults 3 15 monitoring 3 15 placing 3 2 update 3 4 user defined safe state 3 8 inhibiting 1 0 3 9 the drive connection 2 11 installing Compact I O cable B 8 daughtercar
101. all and tighten screws 7 10 lb in MAARA B 8 Access Procedures Installing the Compact I O Cable 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 Ib in Route and secure cable Use cable tie to anchor cable to slots on this flange for strain relief Installing the Communications Daughtercard Task Description Q Align circuit board in Communications Daughtercard with rail on Daughtercard slot fB Insert the Communications Daughtercard Tighten screws 7 10 Ib in Important This procedure can be performed without removing the cassette if the Logix Expansion Board is already installed Access Procedures AUUUUUUUNNNNNNNUNN VVVVVVVG B 9 B 10 Access Procedures Notes Additional Memory Requirements Appendix C Application Restrictions Revision 15 0 or later may require more memory than previous revisions e g 10 x 11 x To estimate the additional memory that your project may require use the following table Which comes from this type of it you have this firmware Then add the following memory requirements to your project memory revision Increase per Data and Logic add all that apply Component instance I O base expansion
102. ame DeviceNet_Seanned Slot 3 a Description Input Size 90 j 32bit zi Output Size foo a 32 bit Bevision E fi 4 Electronic Keying Compatible Module 7 Cancel lt Back Next gt Help 3 Enter a Name for the port and make sure it is assigned to appropriate I O slot Click Finish Communicating with Devices on a 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 These tags are structured as Tag Definition Local s s is the slot number represents Input Data Local s O O represents Output Data Local s C C represents Configuration Data If the 1769 SDN is in slot 1 the input addresses for the scanner are Tag Definition Local 1 1 Data 0 1769 ADN Status Information Local 1 1 Data 1 Input Data from 1769 IA16 Local 1 1 Data 1 Input output echo Data from 1769 0B16 Local 1 1 Data 2 through Local 3 1 Data 4 Input Data from 1769 IF4 Local 1 I Data 5 through Local 3 1 Data 6 Input Data from 1769 OF2 This output addresses for the scanner are Tag Definition Local 1 0 Data 0 Output data for 1769 OB16 Local 1 0 Data 0 through Local 3 0 Data 1 Output data for 1769 OF2 The controller uses the CommandRegister Local 1 0 CommandRegister
103. ane PowerFlex 7005 AP DriveLgx f 00 DriveLogix5730 0 Ethernet Port 4 Ethernet 1 H Remove J 02 PowerFlex 03 Local 1769 Bus Adapter 41769 4 04 1788 ENBT A 1788 ENBT A Driver Diagnostics 2s AB_ETHIP 1 Ethernet Configure Driver a AB_PCIC 1 ControlNet a TCP 1 Ethernet HB Device Properties Module Statistics Module Configuration 5 Select the Port Configuration tab choose Static Network Configuration type and enter the IP address network subnet mask and gateway address if needed You must leave the Static radio button selected to permanently assign this configuration to the port If you select Dynamic the controller clears its IP configuration and sends BOOTP requests on every power cycle and drive reset Click OK x Note The selected controller will General Port Configuration verify that the IP address that has BIER SEECESEE ED Type 3 i re Static Dynamic been assigned in this dialog does ii not belong to another device on the Use DHCP to obtain configuration network If the IP address exists a Use BOOTP to obtain network configuration warning message will display IP Address 10 91 13 210 Network Mask 255 255 255 0 Gateway Address 10 Si 13 1 Primary Name career 0 0 0 0 Secondary Name 0 0 0 0 Server z Domain Name Host Name Status Network Interface Configured Commun
104. as produced or consumed tags e Separate the tag into two or more smaller tags Group the data according to similar update rates For example you could create one tag for data that is critical and another tag for data that is not as critical Assign a different RPI to each tag e Create logic to transfer the data in smaller sections packets 7 16 Communicating with Devices on a 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 To create a produced 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 produce or enter a new tag and display the Tag Properties dialog box 4 Make sure the tag is controller scope 5 Select the Produce this tag check box Specify how many controllers can consume the tag You can produce a base alias or consumed tag 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
105. assette e NetLinx communication daughtercards ControlNet EtherNet IP DeviceNet Third Party e Compact I O connection e CompactFlash memory card user memory 1 5 Mbyte nonvolatile memory 1784 CF64 CompactFlash maximum number of I O banks 2 maximum number of I O modules 16 8 modules per bank or 4 max on either side of the power supply battery 1769 BA serial cable 1756 CP3 directly to controller 1747 CP3 directly to controller Compact I O Cable Category operating temperature 20D DL2 CR3 20D DL2 CL3 Specification storage temperature relative humidity vibration shock emissions Electrical EMC CISPA11 Group 1 Class A ESD Immunity IEC61000 4 2 The unit has passed testing at the following levels Radiated RF Immunity 4 kV contact discharges 8 kV air discharges IEC61000 4 3 Surge Transient Immunity 10V M with 1kHz sine wave 80 AM from 30MHz to 2000MHz IEC61000 4 5 10V m with 200Hz 50 Pulse 100 AM at 900MHz Conducted RF Immunity IEC61000 4 6 1 kV line line DM and 2 kV line earth CM on signal ports A 2 DriveLogix5730 Controller Specifications DriveLogix5730 aaa aaaaaaaaaaaaaaaaaaaaasuuuuuusssssssaiaiassssssss sps 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 CEN European Union 89 336 EEC EMC Directive co
106. ast 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 Specify In this field Type or select Tag Type Select Consumed Controller Select the name of the other controller You must have already created the controller in the controller organizer for the controller name to be available Remote Tag Name Remote Instance Type a name for the tag in the other controller you want to consume Important The name must match the name in the remote controller exactly or the connection faults RPI requested packet interval Type the amount of time in msec between updates of the data from the remote controller The local controller will receive data at least this fast Virtual backplane controllers such as DriveLogix5730 CompactLogix and FlexLogix controllers only produce data at RPIs in powers of two milliseconds such as 2 4 8 16 32 64 etc or when triggered by an IOT instruction Display Style If you are creating a consumed tag that refers to a tag whose data type is BOOL SINT INT DINT or REAL you can select a display style This display style defines how the tag value will be displayed in the data monitor and
107. bject subject of message r 1 r 1 body of email message Use the From address to specify where the mail relay server can send an undeliverable email message The maximum length of an email message is 474 characters An additional 4 byte string length value is added to the tag As a result the maximum source length is 478 characters Entering Ladder Logic You need two MSG instructions One MSG instruction configures the mail server This only needs to be executed once The second MSG instruction triggers the email transmission This can be executed as often as needed Important Be careful to write the ladder logic to ensure the MSG instructions are not continuously triggered to send email messages This is an example of the basic MSG logic You can build more complex logic that automatically manages the Source Lengths within the MSG blocks Refer to Using Ladder Logic to Dynamically_ Configure Messages on page 6 30 Configure EMail MSG JE ured END i SetupEMailServer E lt DND ER Send EMail MSG JE Type Unconfigured END Message Control SendEMailText J H lt DN gt ER mo Odd omom Communicating with Devices on an EtherNet IP Link 6 27 Configuring the MSG Instruction that Identifies the Mail Relay Server 1 On the Configuration tab of the Message Configuration fill out the following fields Message Configuration SetupEMailServer xl Configuration
108. cap terminator must be used on the last I O bank opposite of the expansion cable Only the local DriveLogix5730 controller can scan the local Compact I O ATTENTION The Compact I O system does not support A Removal and Insertion Under Power RIUP While the DriveLogix Compact I O is under power e any break in the connection between the power supply and the controller i e removing the power supply controller or an I O module may subject the logic circuitry to transient conditions above the normal design thresholds and may result in damage to system components or unexpected behavior e removing an end cap or a module fault may fault the controller A 20D DL2 CL3 cable connects the controller to the left side of an I O bank A 20D DL2 CR3 cable connects the controller to the right side of an I O bank i ke a Aa Taney en ee OO mu 20D DL2 CL3 20D DL2 CR3 Placing and Configuring Local I O 3 3 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 t he lad basil EEC 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 A 1769
109. cated parameter within the drive for a total of 42 parameters Selecting a communication format defines the data types for each input and output It also determines the data type for the dedicated parameter in the drive The selection also configures parameters 601 From DL DataType and 625 To DL DataType which indicate the data types for each dedicated parameter within the drive The DriveLogix controller follows a producer consumer model for the drive connection similar to the interface to an I O module The drive acts as both an input module producing data for the controller and an output module consuming data from the controller Although the producer consumer model multi casts data all data in the drive connection is exclusive to the DriveLogix controller The controller updates the input and output data in the drive connection asynchronously to the logic scan consistent with the way it handles other I O data All input data from the drive is read in a single block and all output data is written to the drive in a single block 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 pr
110. cessary nodes such as a second programming terminal that is not being used slow the data transfer rate The maximum number of nodes on the network is 32 If the node addresses for controllers are assigned in sequence starting at node 1 with node 0 left for a programming terminal it is as efficient to leave the maximum node address at 31 as it is to decrease it to the highest node address on the network Then adding devices to the network at a later time will not require modifying the maximum node address in every device on the network 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 9 6 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 Star connections are not recommended
111. ch as online edits or changes to tag values you must store the project to the CompactFlash card again after you make changes Otherwise your changes are not saved and you will lose those changes on the next power cycle to the controller Tag values stored in flash are a snapshot at the time of the store During a program restore the processor tag values will be equal to tag data stored on flash The locking tab on the front of the controller helps hold the CompactFlash card in its socket A ATTENTION Do not remove the CompactFlash card while the controller is reading from or writing to the card as indicated by a flashing green CF LED This could corrupt the data on the card or in the controller as well as corrupt the latest firmware in the controller The CompactFlash card supports removal and insertion under power A ATTENTION When you insert or remove the card while backplane power is on an electrical arc can occur This could cause an explosion in hazardous location installations Be sure that power is removed or the area is nonhazardous before proceeding Repeated electrical arcing causes excessive wear to contacts on both the module and its mating connector Worn contacts may create electrical resistance that can affect module operation See the Logix5000 Controllers Common Procedures Programming Manual publication 1756 PM001 for steps on storing an image on the CompactFlash card 1 6 What is DriveLogix5730
112. chassis is similar to configuring local I O You create the remote communication module and distributed I O modules on the local ControlNet daughtercard To communicate with distributed I O modules you add a remote adapter and I O modules to the I O Configuration folder of the controller To Add Distributed I O Build the I O Configuration in this Order 1 Add the remote adapter to the ControlNet daughtercard of the controller 2 Add the I O modules to the remote adapter J RSLogix 5000 ControlNet_Example PowerFlex 7 File Edit View Search Logic Communications Tools al la a salej JT Offline 0 E RUN aa Fd No Forces b F oK M BAT No Edits a E vo ELS al B 65 Controller ControlNet_Example Controller Tags C3 Controller Fault Handler EH Power Up Handler EJ Tasks EG MainTask E MainProgram FH Unscheduled Programs B Motion Groups C3 Ungrouped Axes C3 Trends B E Data Types ER User Defined ER Strings ty Predefined ir Cg Module Defined 3 6 YO Configuration 2 PowerFlex 7005 2 400 Drive g CompactBus Local E 1 1788 CNC A ControlNet_Daughtercard 2 1794 ACN15 C Flex io adapter D 0 1794 1416 4 input module amp 1 1794 0B16 4 output module F21 A combo analog Communicating with Devices on a ControlNet Link 7 5 Accessing Distributed I O I O information is presented as a structure of multiple fields w
113. consumer Then the controller requires an additional connection for each subsequent consumer 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 Communicating with Devices on a 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 4 Specify In this field Type or select Tag Type Select Consumed Controller Select the name of the other controller You must have already created the controller in the controller organizer for the controller name to be available Remote Tag Name Remote Instance Type a name for the tag in the other controller you want to consume Important The name must match the name in the remote controller exactly or the connection faults If the remote controller is a ControlNet PLC 5 this field is Remote Instance Select the instance number 1 128 of the data on the remote controller RPI requested packet interval Type the amount of time in msec between updates of the data from the remote controller The local controller will receive data at least this fast Display Style If you are creating a consumed tag that refers to a tag whose data type is B
114. d Axis tab click the drop down arrow next to Channel 1 Auxiliary and select Axis01 E Module Properties Controller 2 PowerFlex 700S 2 400V 3 1 General Connection Associated Axes Module Info Power Setup Servo Update Period z 2000 us Associated Axes Channel 0 Primary Axis00 HE New Axis Channel 1 Auxiliary Status Offline Cancel Apply Help Configuring DriveLogix Motion 4 7 9 Click on the Power tab and select the proper Drive Rating E Module Properties Controller 2 PowerFlex 700S 2 400V 2 4 General Connection Firmware Version 2 004 Drive Rating 480V 114 x Status Offline Cancel Apply Help 10 Click the Apply button 11 Click the OK button 12 Create a new Motion Group a In the Controller Organizer right click on Motion Groups b Select New Motion Group from the menu Controller Motion Drive Controller Tags Controller Fault Handler FH Power Up Handler Sj Tasks MainTask G MainProgram Unscheduled Programs Phases F SE New Motion Group Tr Da fF E 4 8 Configuring DriveLogix Motion c Enter a Name for the Motion Group Grouped_Axis in this example en Grouped As StC CS Ok Description Cancel Help Usage T Type Base X Alias For Data Type MOTION GROUP Ej Scope 5 Motion_Drive Style d Verify that the Open MOTION_GROUP Configuration box is checked
115. d B 9 DH 485 network 9 6 DriveLogix5730 Expansion Board B 7 Embedded EtherNet IP Option B 7 new battery B 5 K keying 2 4 L loading firmware 1 2 firmware with AutoFlash 1 4 firmware with CompactFlash 1 4 firmware with ControlFlash 1 3 local I O C 1 Index 3 M mapping 7 12 addresses EtherNet IP communication to non Logix controllers 6 22 Motion Control communication format 2 8 Position Control communication format 2 7 Speed Control communication format 2 6 User Defined 1 communication format 2 9 User Defined 2 communication format 2 10 master slave communication methods 5 8 memory specifications A 1 messages ControlNet 7 9 EtherNet IP 6 19 Motion Control communication format 2 8 N network settings EtherNet IP 6 2 P placing drive 2 3 I O 3 2 Position Control communication format 2 7 Powering Down 1 2 2 1 3 1 4 1 5 1 6 1 7 1 8 1 9 1 B 1 producing and consuming data ControlNet 7 14 7 20 7 23 EtherNet IP 6 15 programming ASCII instructions 5 12 programs defining 1 8 developing 1 6 R remote connection serial link 5 7 Index 4 replacing battery B 5 routines defining 1 9 RPI 3 4 3 6 RS 232 5 1 RSLinx configuring EtherNet IP network parameters 6 6 RSLogix 5000 configuring network parameters 6 7 S scheduling ControlNet 7 7 serial link ASCII device 5 11 configuring communications driver 5 5 configuring serial port 5 3 configuring system for 5 1 DF1 point to
116. d be included Use Periodic Tasks to optimize processor utilization Name periodic tasks to identify the update time e g Periodic_O20ms_P9 20ms task with priority 9 Set the periodic task time appropriate programming requirements Important Remember that tasks with faster the task times consume more processor bandwidth than those with slower task times Set the priority of each task to coincide with the task speed Set faster tasks to higher priority Important Remember lower priority numbers define higher priorities e g a task with a priority number of 9 has a higher priority than one with a priority of 10 Important Do not set the priority number lower than 8 the recommended priority range is 8 15 This will provide I O scanning with optimal updating Flex I O and Compact I O are coded as priority 7 for DriveLogix De energizing the Drive to Connect or Disconnect a Cable Understanding How the DriveLogix5730 Supports I O Chapter 3 Placing and Configuring Local I O 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 amp DC terminals on the Power Terminal Block The voltage must be zero N ATTENTION Severe injury or death can result from electrical During the process of placing and configuring I O you will need to connect or disconnect a programming or network cable at the controller You
117. day 18 months 15 months 12 months 5 days per week ON 16 hours per day 26 months 22 months 16 months 5 days per week Always ON There is almost no drain on the battery when the controller is always ON Battery duration after the LED turns on The battery indicator BAT warns you when the battery is low These durations are the amounts of time the battery will retain controller memory from the time the controller is powered down after the LED first turns on Temperature Duration 60 C 8 days 25 C 25 days Removing Power from Drive and Compact I O Appendix B Access Procedures A 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 amp DC terminals of the Power Terminal Block The voltage must be zero Remove power before making or breaking cable connections When you remove or insert a cable connector with power applied an electrical arc may occur An electrical arc can cause personal injury or property damage by e sending an erroneous signal to your system s field devices causing unintended machine motion e causing an explosion in a hazardous environment Electrical arcing causes excessive wear to contacts on both the module and its mating connector Worn contacts may create electrical resistance Task Description Q Turn off and lock out input
118. destination tag contiguously Data structure and value change depending on the destination data type 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 6 22 Communicating with Devices on an EtherNet IP Link For In this field PLC 3 PLC 5 and File Number 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 x PLC 3 5 2 SLC Mapping _ Fie Number Cancel Help Delete Map PLC 2 Mapping Tag Name 2 Specify this information Specify For example Type the file number of the data table in the PLC SLC controller 10 L troll SLC controllers Tag Name Type the array tag name the local controller uses to refer tothe array 1 PLC SLC data table address The tag must be an integer array SINT INT or DINT that is large enough for the message data PLC 2 controllers Tag Name Type the tag name to be the PLC 2 compatibility file 200 gt Type of MSG Instruction PLC 5 writes to DriveLogix5730 SLC writes to DriveLogix5730 SLC 5 05 SLC 5 04
119. dress gt to insure the mail server is reachable from your network Also try telnet lt mail server address gt 25 which attempts to initiate a SMTP session with the mail server via telnet over port 25 If you connect then enter QUIT 0x0105 Communication error with SMTP mail server An error occurred after the initial connection with the SMTP mail server See the ASCII text following the error code for more details as to the type of error 0x0106 SMTP mail server host name DNS query did not complete A previous send service request with a host name as the SMTP mail server address did not yet complete Note that a timeout for a DNS lookup with an invalid host name can take up to 3 minutes Long timeouts can also occur if a domain name or name server is not configured correctly Using Ladder Logic to Dynamically Configure Messages Use ADD instructions to calculate the MSG Source Length Configure Email ADD MSG i vpe CIP Gene END EmailContig LEN SetupE MailServer K lt DND gt 136 R gt Source B 4 Dest SetupEMailServer REQ LEN 17 Send_EMail ADD MSG JE Add Type CIP Generic SEND Source A EmailT ext LEN Message Control SendEMailText E lt DND 110 ER Source B 4 Dest SendEMailT ext REQ_LEN 1146 Wo Communicating with Devices on an EtherNet IP Link 6 31 Example 1 DriveLogix5730 In the following example one Dr
120. dule is inhibited and not faulted If you uninhibit the drive clear the check box and no fault condition occurs a connection is made to 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 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 The GSV instruction gets the current status of the drive named drive module The SSY instruction sets the state of drive module as either inhibited or uninhibited GSV Get System Value Class Name MODULE Instance Name drive module Attribute Name Mode Dest drive_mod_mode 0e SSY state drive mod mode 2 c gt SY Set System Value Class Name MODULE Instance Name drive module Attribute Name Mode Source drive_mod_mode o Using DriveExecutive Lite 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 1 If not already done enter the drive firmware revision Click the Finish button to apply the revision data E Module Properties Controller 2 PowerFlex 7005 2 400 1 6 General Connection Associated Axes Module Info Power Setup Type PowerFlex 7005 2 400 Drive Interface 400V Vendor Allen Bradley
121. e controller is already programmed click Go Online instead fg RSLogix 5000 EtherNetIP_Example PowerFlex 7005 2 File Edit View Search Logic Communications Tools Window F alsia S sa wroacve Select Recent Path Offline fl E RUN PE E AS A aN No Forces b ve Go Online Reas Upload No Edits a T Vo Download Program Mode EJ Controller EtherNetIP_Ex Run Mode Controller Tags STAF 2 Controller Fault Handl Test Mode J Power Up Handler z Lp S Controller g MainTask Clear Faults E8 MainProgram E 23 Unscheduled Program ca torau E Motion Groups Fi nar med ives DI x IV Autobrowse Refresh Workstation USMEQISTO38 Go Online Linx Gateways Ethernet 1784 PCIDS 1 DeviceNet Upload AB_DF1 1 Data Highway Plus 2s AB DF1 2 DF1 Download E 01 DriveLogix i et test gt Backplane PowerFlex 7005 AP Drivelgx Update Firmware AB_ETHIP 1 Ethernet Clee AB_PCIC 1 ControlNet a TCP 1 Ethernet Help Path AB_DF1 2 1 Set Project Path Path in Project lt none gt Clear Project Path 5 Communicating with Devices on an EtherNet IP Link In the Controller Organizer right click on the icon for the port and select Properties E SLogix 5000 13_H10 PowerF
122. e operation ATTENTION Inhibiting a drive module breaks the controller s On the Connection tab during creation or in the Properties window E Module Properties Controller 2 PowerFlex 7005 2 400 1 2 i General Connection Associated Axes Module Info Power Setup Check the inhibit box to Requested Packet Interval RPI 4054 ms 3 0 100 0 ms inhibit the connection to I Inhibit Module the drive HF Major Fault On Controller If Connection Fails While in Run Mode Module Fault Status Offline Cancel Apply Help When you inhibit the drive module the Controller Organizer displays a yellow attention symbol over the module If you are Inhibit the drive module to offline put a place holder for the drive module to indicate that configuration is not yet complete The inhibit status is stored in the project When you download the project the module is still inhibited online stop communication to the drive If you inhibit the drive while you are connected to the module the connection to the module is closed By default the PowerFlex 700S drive will fault The data inputs to the drive will either hold last state or reset to zero data based on the setting of parameter 385 Lgx CommLossData If you inhibit the drive but a connection to the module was not established perhaps due to an error condition or fault the module is inhibited The module status information changes to indicate that the mo
123. e plus the 4 byte length The Source Length must equal the Source Element string size 4 0x15 none Configuration data size too large The Source Length is greater than the Source Element string size plus the 4 byte length The Source Length must equal the Source Element string size 4 0x19 none Data write failure An error occurred when attempting to write the SMTP server address attribute 4 to non volatile memory 6 30 Communicating with Devices on an EtherNet IP Link Error Code hex OxFF Extended Error Code hex 0x0100 Description 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 address not specified Attribute 1 was not set with a To address AND there is not a To field header in the email body 0x0103 From address not specified Attribute 2 was not set with a From address AND there is not a From field header in the email body 0x0104 Unable to connect to SMTP mail server set in Attribute 5 If the mail server address is a hostname make sure that the device supports DNS and that a Name Server is configured If the hostname is not fully qualified i e mailhost and not mailhost xx yy com then the domain must be configured as xx yy com Try ping lt mail server ad
124. eNet communication 8 2 Communicating with Devices on a DeviceNet Link For the DriveLogix controller to operate on a DeviceNet link you need e a workstation with an appropriate DeviceNet interface card e RSLinx software to configure the DeviceNet communication driver e 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 e aNetLinx DeviceNet communication daughtercard installed on the DriveLogix controller refer to Installing the Communications Daughtercard on page B 9 or e 1769 SDN DeviceNet scanner module installed on the a bank of local Compact I O controlled by the DriveLogix controller i DriveLogix controller with 5 1769 SDN Scanner Module installed in a bank of Compact I O or DriveLogix controller ect oC ies with 1788 DNBO Communications E Daughtercard OP OP Oo oo DeviceNet DeviceNet Example Controlling 10 This example uses a NetLinx DeviceNet communication daughtercard Over DeviceNet installed on the DriveLogix controller to control a bank of I O attached to a 1769 ADN adapter module
125. ed UserDefinedIntegerData 5 644 To DriveLogix18 User Defined UserDefinedIntegerData 6 645 To DriveLogix19 User Defined UserDefinedIntegerData 7 646 To DriveLogix20 User Defined 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 User Defined UserDefinedRealData 4 607 FromDriveLogix05 User Defined UserDefinedRealData 5 608 FromDriveLogix06 User Defined UserDefinedRealData 6 609 FromDriveLogix07 User Defined UserDefinedRealData 7 610 FromDriveLogix08 User Defined UserDefinedRealData 8 611 FromDriveLogix09 User Defined UserDefinedRealData 9 612 FromDriveLogix10 User Defined UserDefinedRealData 10 613 FromDriveLogix1 1 User Defined UserDefinedIntegerData 0 614 FromDriveLogix12 User Defined UserDefinedIntegerData 1 615 FromDriveLogix13 User Defined UserDefinedIntegerData 2 616 FromDriveLogix14 User Defined UserDefinedIntegerData 3 617 FromDriveLogix15 User Defined
126. emove the cover Proper tightening torque for reassembly is 7 10 lb in WEEREENS B 3 B 4 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 ELETTY Plug and socket Storing the Battery ATTENTION 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 Replacing the Battery Access Procedures B 5 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 Servicing energized equipment can be contains potentially dangerous chemicals Before handling or disposing a battery review Guidelines for Handling Lithium Batteries publication AG 5 4 ATTENTION The controller uses a lithium battery which Open the drive door and connect to the appropriate communication port on the controller while the drive and the DriveLogix5730 controller are energized Upload the controller s memory and program to a com
127. ends and accepts messages with a 2 byte CRC for error checking CRC is a more complete method Enable duplicate detection Select whether or not the controller should detect duplicate messages The default is duplicate detection enabled This field Station address Communicating with Devices on a Serial Link 5 9 Configuring a DF1 Master Station Description 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 Enter a value 0 127 The default is 3 ACK timeout Specifies the amount of time you want the controller to wait for an acknowledgment to its message transmission Enter a value 0 32767 Limits are defined in 20ms intervals The default is 50 1000ms Reply message wait Message based polling mode only Specifies the amount of time the master station waits after receiving an ACK to a master initiated message before polling the slave station for a reply Enter a value 0 65535 Limits are defined in 20ms intervals The default is 5 100ms Polling mode Select one of these e Message Based slave cannot initiate messages e Message Based slave can initiate messages default e Standard multiple message transfer per node scan e Standard single message transfe
128. ent Applications Configure CIP Options Configure Gateway a Linx Gatewa H ds Linx Ess TCP Driver Diagnostics CIP Diagnostics Gateway Diagnostics T T Et Configure Drivers Available Driver Types Close Add New Help m Configured Drivers Name and Description Status TCP 1 to on 13112001132 27 ERROR Running Configure Startup Start Stop Delete HERE EEE Specify a name for the driver and click OK Add New RS Linx Driver xi Choose a name for the new driver 15 characters maximum Cancel i n i 7 i AB DF1 1 mea 3 Specify the appropriate communication settings Device Name AB_DF1 1 Comm Pott com x Device PLC CHO x Baud Rate 19200 x thee moo ctal Parity None x Error Checking BCC Be Stop Bits fi x Protocol Full Duplex x Auto Configure I Use Modem Dialer 5 6 Communicating with Devices on a Serial Link Example 1 Workstation Directly Connected to a DriveLogix Controller This field Station address In the following example a workstation directly connects to a DriveLogi5730 controller over a serial link This is useful for downloading a controller project directly to the controller
129. er 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 array_1 controller CIP Data Table Write destination tag array_2 Logix based controller reads from source tag array_1 Logix based controller CIP Data Table Read destination tag array_2 The source and destination tags e must be controller scoped tags e can be of any data type except for AXIS MESSAGE or MOTION_GROUP Communicating with Other Controllers Over ControlNet The DriveLogix5730 controller also uses MSG instructions to communicate with PLC and SLC controllers The MSG instructions differ depending on which controller initiates the instruction 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 DriveLogix writes In the DriveLogix controller specify the source data type Specify the destination file type based on the to PLC 5 or SLC based on the destination device destination device PLC 5 SINT INT DINT or REAL PLC 5 typed write S B N or F SLC INT PLC 5 word range write S B N F I O A or D SLC B or N Example source element array_1 Example destination tag N7 10 7 12 Type of MSG Instruction DriveLogix writes to PLC 2 DriveLogix reads f
130. er Defined UserDefinedRealData 8 616 FromDriveLogix14 User Defined UserDefinedRealData 9 617 FromDriveLogix15 User Defined UserDefinedIntegerData 0 618 FromDriveLogix16 User Defined UserDefinedIntegerData1 619 FromDriveLogix17 User Defined UserDefinedIntegerData 2 620 FromDriveLogix18 User Defined UserDefinedIntegerData 3 621 FromDriveLogix19 User Defined UserDefinedIntegerData 4 622 FromDriveLogix20 User Defined Controller Input Tag Element Drive Parameter Linked Parameter LogicStatus 626 To DriveLogix00 155 Logic Status FilteredSpdFdbk 627 To DriveLogix01 71 Filtered SpdFdbk MotorTorqueRef 628 To DriveLogix02 303 Motor Torque Ref OutputCurrent 629 To DriveLogix03 308 Output Current MCStatus 630 To DriveLogix04 555 MC Status LocallOStatus 631 To DriveLogix05 824 Local I O Status UserDefinedRealData 0 632 To DriveLogix06 User Defined UserDefinedRealData 1 633 To DriveLogix07 User Defined UserDefinedRealData 2 634 To DriveLogix08 User Defined UserDefinedRealData 3 635 To DriveLogix09 User Defined UserDefinedRealData 4 636 To DriveLogix10 User Defined UserDefinedRealData 5 637 To DriveLogix11 User Defined UserDefinedRealData 6 638 To DriveLogix12 User Defined UserDefinedRealData 7 639 To DriveLogix13 User Defined UserDefinedRealData 8 640 To DriveLogix14 User Defined UserDefinedIntegerData 0 641 To
131. ere CHx the channel number Any 1769 Compact I O modules used as remote I O modules in a DriveLogix5730 system do support the Hold Last State and User Defined Safe State features C 4 Application Restrictions Notes Numerics 1769 ADN adapter 8 3 1769 CRL1 CRL3 cable 3 2 1769 CRR1 CRR3 cable 3 2 1788 DNBO DeviceNet scanner 8 5 20D DL2 CL3 cable 3 2 20D DL2 CR3 cable 3 2 A accessing distributed I O on ControlNet 7 5 distributed I O on EtherNetl P 6 13 I O data 3 12 Additional Memory Requirements C 1 addresses ControlNet communication to non Logix controllers 7 12 aliases 3 14 arrays C 2 ASCII device 5 11 instructions 5 12 AutoFlash 1 4 battery connecting B 4 disposing B 6 LED A 4 life A 8 replacing B 5 specification A 1 storing B 4 BOOTP DHCP configuring network parameters 6 3 C cable 1769 CRL1 CRL3 3 3 20D DL2 CL3 3 2 20D DL2 CR3 3 2 Belden 3106 9 7 Belden 9842 9 7 Compact I O A 1 installing Compact I O B 8 serial A 1 Index certifications A 2 clock accuracy A 2 communicating master slave serial methods 5 8 to non Logix controller over ControlNet 7 11 communication format 2 1 2 5 3 8 Motion Control 2 8 Position Control 2 7 Speed Control 2 6 User Defined 1 2 9 User Defined 2 2 10 communications driver configuring for serial link 5 5 ControlNet 7 2 EtherNet IP 6 10 CompactBus configuring 3 5 CompactFlash 1 4 1 5 configuring 1769 ADN adapter 8 3 communications driver for serial
132. escription DINT Status F INT x where x is the output size of the data Data produced by a ControlNet PLC 5 controller from the ControlNet PLC 5 controller If you are consuming only one INT no dimension is required 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 Data Type The user defined data type that you created 5 In the RSNetWorx for ControlNet software reschedule save the network 7 26 Communicating with Devices on a 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 1 direct connection for each I O module 3 DriveLogix1 controller to local 1788 CNC 0 DriveLogix1 controller to remote 1756 CNB 1 DriveLogix1 controller to remote ControlNet PLC 5 1 connected cached MSG from DriveLogix1 to Control1 1 connected cached MSG from DriveLogix1 to PLC5C1 1 Produced TagA produced from DriveLogix1 to DriveLogix2 1 con
133. et Bridge Twisted Pair Media 1 788 EWEB A 1788 10 100 Mbps Ethernet Bridge w Enhanced Web Services 1788 MODULE Generic 1788 Module Drivelogix5730 Ethernet 10 100 Mbps Ethernet Port on DriveLogix5 730 Drive Interface 200V Drive Interface 400 Drive Interface 600V Drive Interface 200V Drive Interface 400V PowerFlex 700Se2 400 Drive Interface 400 xi Show Vendor fal x IV Other IV Specialty 1 0 Select All IV Analog IV Digital IV Communication IV Motion IV Controller Clear All Cancel Help Important You must select the correct voltage rating for the drive when adding the drive You can find this on the drive data nameplate 2 4 Placing and Configuring the Drive 3 Select the Major Revision Select Major Revision x Select Major Rev for PowerFlex 7005 2 400 Module Profile being Created Major Revision e d 4 Configure the drive Use the module properties wizard to specify characteristics for the module Click Next to continue through the wizard 5 Name the drive and specify the Comm Format Click finish when you are done The completed module appears in the Controller Organizer Module Properties Controller 2 PowerFlex 7005 2 400 1 5 E xl Type PowerFlex 700S 2 400V Drive Interface 400V Vendor Allen Bradley Parent Controller Name five module Slot Description this is the local PowerFlex 7005 E Comm Format Speed Control E Bevision
134. everses Bi directional direction until motion stops after decelerating or moving the Offset distance Reverse The axis jogs in the negative axial direction until a homing event switch or marker is encountered then continues Uni directional in the same direction until axis motion stops after decelerating or moving the Offset distance Reverse The axis jogs in the negative axial direction until a homing event switch or marker is encountered then reverses Bi directional direction until motion stops after decelerating or moving the Offset distance 25 When you have completed defining the axis click the Apply then the OK button 26 Configure Axis01 by repeating the tasks in Steps 16 25 Important Only Channel 0 will function for a Servo axis Channel 1 may be used for a Feedback Only axis 27 Save the RSLogix 5000 project and download it to the controller cause unstable and unpredictable operation To avoid potential personal injury and damage to machinery determine the proper values for system dynamics and tune the system before beginning operation ATTENTION Running the system without proper tuning can 4 14 Configuring DriveLogix Motion Launching DriveExecutive Next open the drive properties window and launch DriveExecutive drive from RSLogix programming software 1 In the Controller Organizer select the PowerFlex 700S drive Right click the drive module and select Properties Krig RSLogix 5000 Motion D
135. ew Drive Peripheral Tools Window Help 16 x D 0 2 2 19 Linear List Ca Monitor Ca Motor Control C3 Dynamic Control C3 Speed Control C3 Torque Control C3 Process Control C3 Position Control C3 Speed Posit Fdbk CA utility Drive Memory Diagnostics Fault Alm Config Test Points Peak Detection Trending Ca Communication Ca Inputs amp Outputs Ca User Functions ER Default Custom For Help press F1 S Hi S o S OA RR Undefined Node B 0 PowerFlex 7005 2 Fault Alm Config Group Parameters _ Parameter Na alue_ Uni internal Source Comment Defaut mn mx 13 0500 200 HiHp GndFlt Cur HiHp GndFlt Dly 200 FdbkLsCnfg Pri FitCo v Fdbk LsCnfg Alt Fdbk LsCnfgPosit Brake OL Cnfg HiHp InPhsLs Cfg Alarm Mtr OL Trip Cnfg Fito Mtr OL Pend Cnfg Alarm Motor Stall Time 1 0000 Sec Motor Stall Cnfg Inv OT Pend Cnfg Alarm Inv OL Pend Cnfg Alarm Inv OL Trip Cnfg Alarm Interp Fit Cnfg Alarm Ext Fit Alm Cnfg Fito PreChrg Err Cnfg FitCo MC Cmd Lim Cnfg FitCo SL CommLoss Data Last S SL CommLoss Cnfg FitCo v Lax CommLossD La Lax OutOfRunChfd2 FitCoastStop Alarm S oa m lelelelelelelelele Lax Timeout Cnfa 0 Ignore Lae Closed rg Lox LinkChngCnfo PAMARE TISA SL Muter Cfo DPI CommLoss CFgt4 lt FitCurLimStp NetLoss DPI Cnfg FitCo v BusUndervoltCnfg Alarm v VoltFdbkLossCnfg FitCo
136. g green The controller is reading from or writing to the CompactFlash card flashing red CompactFlash card does not have a valid file system A 6 DriveLogix5730 Controller Specifications Embedded EtherNet IP Option LEDs Module Status MS Network Status NS Link Status LNK only operational when the drive is energized and only visible ATTENTION The Embedded EtherNet IP Option LEDs are 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 Follow Safety related practices of NFPA 70E ELECTRICAL SAFETY FOR EMPLOYEE WORKPLACES DO NOT work alone on energized equipment Module Status MS indicator Ot opde og uF xl TERI loc WTF H r V12 ALT pooooonai myam
137. gins with word 0 of the output tag in the controller as follows Location Description Word 0 1769 OB16 module s output word Words 0 1 1769 OF2 module s output words 8 8 Communicating with Devices on a DeviceNet Link Output Word 0 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 Local 1 1 H Local 1 0 Local 1 0 CommandR egister Local 1 0 CommandRegister Run Locat l 0 CommandRegister Fault Local 1 0 CommandReaister DisableNetwork Local 1 0 CommandRegister HaltS canner Local 1 0 CommandRegister Reset Local1 0 Data Bit Description Behavior 0 Run This bit controls when the module scans its mapped slave devices When set 1 the scanner will process I O data as defined by its scanlist To actually scan the network the Fault and Disable Network command bits must be clear 0 1 Fault When set the scanner s I O mode will be Halt messaging will still operate The fault bit is primarily used to artificially set the slave devices into a fault state due to some event or condition within the control program 2 Disable Network When set the scanner is functionally removed from the network 3 HaltScanner When set the scanner stops scanning its mapped slave devices 4 Reset Res
138. hat is inactive in the priority poll array 3 the specified number normal poll group size of active stations in the normal poll array 4 one inactive station after all the active stations in the normal poll array have been polled Use the programming software to change the display style of the active station array to binary so you can view which stations are active 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 scanner Communicating with Devices on a Serial Link 5 11 Connecting 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 Connect the sending pins to the corresponding receiving pins and attach jumpers If the communications Then wire the connectors as follows handshake ASCII Device Controller 1CD 1 2 RDX 2 RDX 3TXD gt lt 3TXD 4DTR FR lt 4DTR COMMON COMMON 6DSR 6 DSR 7RTS 7 __ 8CTS 8 9 9 do not handshake ASCII Device Controller 1CD
139. he End of an Array Description If you write too much data to an array that is within a user defined data type some instructions write beyond the array and into other members of the tag Example 1 Instruction Stops at the End of the Array co Copy File Source MyTaq 1 0 Dest MyTag_2 0 Length 10 If the length is greater than the number of elements in the destination array Program Tags MainProgram1 Scope MainProgramt 7 Show sh amp Type then the instruction stops at the end of the array E MyTag 2 DINT 5 MyTagq_2 0 DINT FH MyT ag 2 1 DINT MyTaq_ 2 2 DINT MyTag_2 3 DINT MyTag_2 4 DINT E MyTag3 DINT Example 2 Instruction Writes Beyond the Array co Copy File Source MyTag_1 4 0 Dest MyTag_2 4 0 10 Length If the length is greater than the number of elements in the destination array Program Tags MainProgram Scope MainProgram 7 Show Sho Tag Name Type BG then the instruction writes data beyond the end of El MyTag_2 My Data Type the array into other members of the tab Regardless of HMyTag 2A DINTI5 the length specified for the instruction it stops writing if MyTag 2B DINT it reaches the end of the tag MyTag_2 C DINT F MyTag_3 DINT The following instructions write beyond the array into other
140. he high priority tasks and the dedicated I O task approaches 2 ms no CPU time is left for low priority tasks 8 to 15 TIP For example if your program needs to react to inputs and control outputs at a deterministic rate configure a periodic task with a priority higher than 7 i e 1 through 6 This keeps the dedicated I O task from affecting the periodic rate of your program However if your program contains a large amount of math and data manipulation place this logic in a task with priority lower than 7 i e 8 through 15 such as the continuous task so that the dedicated I O task is not adversely affected by your program Important When using a DriveLogix5730 controller with Compact I O all application program tasks must have an assigned priority of 8 through 15 in order that they do not interfere with the proper operation of the Compact I O 1 8 What is DriveLogix5730 The following example shows the task execution order for an application with two periodic tasks and one continuous task Example Worst Case Task Priority Level Task Type Execution Time Completion Time 1 5 periodic task executes every 20 ms 2 ms 2ms 2 7 dedicated I O task 5 ms RPI 1ms 3ms 3 10 periodic task executes every 10 ms 4 ms 8 ms 4 none lowest continuous task 25 ms 60 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 t
141. hether the connection to the module is open 0 or closed 1 If the connection is closed 1 the Fault_Bit it set 1 Connection_Closed You can also view module fault data on the Connection tab of the Module Properties screen fa Module Properties Local 1 1769 1A16 A 1 1 a JO x General Connection Requested Packet Interval RPI 2054 ms I Major Fault Gn Controller If Connection Fails While in Run Mode Module Fault Status Offline Cancel Apply Help See your 1769 module s user documentation for a description of module faults To recover from module faults correct the module fault condition and send new data to the module by downloading the user program with configuration data inhibiting and then uninhibiting the module or cycling power 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 If a module that is adjacent to an end cap experiences a fault the module will fault and the controller may fault Configuring I O Modules Use the Generic 1769 Module only when a 1769 I O module does not Using the Generic appear in the list of modules to add to the Controller Organizer To 1769 MODULE configure a 1769 I O module for a DriveLogix5730 controller using the generic 1769 MODULE 1 In the Controller Orga
142. hich 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 Bit 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 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 Data is the common name for values the are sent to or received from I O points SubMemberName Specific data related to a MemberName Bit optional Specific point on the I O module depends on the size of the I O module 0 31 for a 32 point module Example t g O Configuration l 1 1788 ONC18 ControlNet Daughtercard Foose on 2 PowerFlex 7005 2 400 Drive FE CompactBus Local Sie 2 1794 4CN150C Flex jo adapter g 0 1794 141674 input module ER 1 1794 0616 4 output module ER 2 1794 IF280F2176 combo analog 7 6 Communicating with Devices on a ControlNet Link Device remote adapter FLEX io adapter Example Tag
143. hile in Run Mode checkbox selected the controller will fault on any I O fault E Module Properties Local 1 1769 1416 A 1 1 oj xj General Connection Requested Packet Interval RPI 20 ms J Major Fault On Controller If Connection Fails While in Run Mode Module Fault Status Offline Cancel Apply Help The I O modules respond to a connection failure by turning off output that depend on the specific features of the I O module The names of the data structures are based on the location of the I O module The programming software automatically creates the necessary structures and tags when you configure the module Each tag name follows this format Location SlotNumber Type MemberName SubMemberName Bit The programming software displays I O data as structures of multiple tags where This address variable Is Location Identifies network location LOCAL local chassis SlotNumber Slot number of I O module in its chassis Type Type of data input O output C configuration Placing and Configuring Local I O 3 13 This address variable Is 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 SubMemberName Specific data related to a MemberName Bit optional
144. how All Y Sot Tag Name x drive_module Force Mask AB PF700S_2_SP drive_module 0 AB PF700S_2_SP Local 1 1 Local 2 C Local 2 C Contig AB 1763_DI16 1 0 4B 1763_D016 C 0 280000 000 Binary INT ocal 2 C ProgT oF aultEn Decimal BOOL Local 2 C ProgMode 280000 000 Binary INT F Local 2 C ProgValue 2 0000_000 Binary INT Local 2 C FaultMode 240000 000 Binary INT Local 2 C FaultValue 2 0000 000 Binary INT Local 2 eee AB 1763_D016 1 0 Local 2 0 ees AB 1769_D016 0 0 Monitor Tags A Edt Tags 7 Tags 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 31 27 23 19 15 11 7 3 0 Fault_Code_Value reserved aultCode FaultInfo 0 connection OPER Connection Closed 1 connection closed Fault Bit Where Description This bit indicates that at least one bit in the fault word is set 1 If all the bits in the fault word are cleared 0 this bit is cleared 0 Fault Bit This bit indicates w
145. iagnostics iz continued 8 4 Communicating with Devices on a DeviceNet Link 2 The software then prompts you to either upload or download Choose upload RSNetWorx will then browse the network and obtain their settings Eile Edit View Network Device Diagnostics Tools Help als ulls gt er Hardware xl DPI to DeviceNet DeviceNet to SCANport Dodge EZLINK a General Purpose Discrete I 7 Generic Device Human Machine Interface Inductive Proximity Switch J Limit Switch Modular DPI Devices Motor Overload l Motor Starter Photoelectric Sensor O Rockwell Automation miscel SCANport Adapter Smart MCC Specialty 1 0 O Unknown Device Type 126 HHH E Rockwell Automation Aller Rockwell Automation Dodi Rockwell Automation Elect Rockwell Automation Reliz Rockwell Automation Entek w FEE EEG AA AAA ale EI Jala Hl 1788 DNBO 1769 ADN Compact I O Adapter 05 21 H 4 gt M Graph Spreadsheet Master Slave Configuration Diagnostics J 4 3 Right click on the 1769 ADN and choose Properties Ce 1769 ADN Compact I O Adapter General 170 Bank 1 Configuration 170 Bank 2 Configuration 170 Bank 3 Configuration Reset Summary
146. icating 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 necessary components In the Controller Organizer select the I O Configuration folder Right click the selected folder and select New Module E RSLogix 5000 EtherNetIP_Example PowerFlex File Edit View Search Logic Communications Tools alsia z sie fT Offline J F RUN er weal 9 No Forces gt E ok i NoEdts 4 mat 4 ma EJ Controller EtherNetIP_Example Controller Tags C3 Controller Fault Handler CH Power Up Handler E Tasks A fa MainTask C8 MainProgram FH Unscheduled Programs ER Motion Groups C3 Ungrouped Axes FH Trends E Data Types i User Defined Oa Strings FO Predefined 4 Module Defined amp s 2 PowerFl CompactBu m Cut Ctrl x B3 Ctrl C l Ctrl 6 7 Important You must create an offline project and download it to the controller before going online If the controller is already programmed skip these first three steps 3 Select a DriveLogix5730 Ethernet Port from the list of possible communication devices Click OK Select Module Type xl Type Drivelogix5730 Ethernet Pr Description 1788 ControlNet Bridge Coax Media 1788 ControlNet Bridge Redundant Coax Media 1788 ControlNet Bridge Fiber Media 1788 C
147. ies the maximum node address of all the devices on the DH 485 network Select a number 1 31 decimal inclusive To optimize network performance make sure the maximum node address is the highest node number being used on the network that all the devices on the same DH 485 network have the same selection for the maximum node address Planning a DH 485 Network The DH 485 network offers interconnection of 32 devices multi master capability token passing access control the ability to add or remove nodes without disrupting the network maximum network length of 1219 m 4000 ft The DH 485 protocol supports two classes of devices initiators and responders All initiators on the network get a chance to initiate message transfers The DH 485 protocol uses a token pass algorithm to determine which initiator has the right to transmit DH 485 Token Rotation A node holding the token can send any valid packet onto the network Each node gets only one transmission plus two retries each time it receives the token After a node sends one message packet it attempts to give the token to its successor by sending a token pass packet to its successor 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 co
148. iguration bits TIP The input and output data being exchanged by the scanner and adapter is packed data This means that there is no special structure to it that makes it obvious which I O module it is associated with To establish which data is from which module you must list the number of input and output words each module has Then based on its position in the I O bank you can determine where any module s data is in the controller s I O tags Transferring Data There are 28 bytes of input data and 6 bytes of output data for this example The I O modules in the adapter s system are Module Input Output ADN Status Information 1 DINT word 0 words added by the 1769 ADN 1769 1A16 1 2 DINT word 0 words 1769 0B16 1 2 DINT word 1 2 DINT word 1769 IF4 3 DINT words 0 words 1769 OF2 2 DINT words 1 DINT word Total Words 7 DINT words 1 1 2 DINT words Total Bytes 28 bytes 6 bytes The total is 7 DINT words or 28 input bytes The first DINT word is adapter status leaving 6 DINT words 24 bytes for data The input data maps to the controller s input data tag at the following word locations Location Description Word 0 1769 ADN status information Word 1 1769 IA16 module s input word Word 1 1769 OB16 module s input data output data echo Words 2 4 1769 IF4 module s input data Words 5 6 1769 OF2 module s input data The output data can be determined in a similar manner This data be
149. ined J 7 ontrolNet Bridge Coax Media R Strings 1 788 CNCR A 1788 ControlNet Bridge Redundant Coax Media Predefined 1 788 CNF A 1788 ControlNet Bridge Fiber Media Module Defined 1 788 CNFR A 1788 ControlNet Bridge Redundant Fiber Media Fy 1 788 DNBO A 1788 DeviceNet Scanner wears PowerFl 1788 ENBT A 1788 10 100 Mbps Ethernet Bridge Twisted Pair Media GH CompactBu SS ER 1788 EWEBZA 1788 10 100 Mbps Ethemet Bridge w Enhanced Web Services de Cut Ctrl x 1788 MODULE Generic 1788 Module B3 Copy Ctrl C Drivelogix5730 Ethernet 10 100 Mbps Ethernet Port on DriveLogix5730 f Paste Ctrl V Show Vendor fa z IV Other IV Specialty 1 0 Select All IV Analog M Digital IV Communication IV Motion IV Controller Clear All Cancel Help Module Properties Controller 4 1788 CNC A 1 1 i xl Type 1788 CNC A 1788 ControlNet Bridge Coax Media Vendor Allen Bradley Name ControtNet_D aughtercard Node 1 Description Slot 4 z This must be slot 4 Revision w fi a Electronic Keying Compatible Module gt Cancel Back Next gt Finish gt gt Help 3 Enter a Name for the daughtercard and the desired Click Finish Do not change the slot number 7 4 Communicating with Devices on a ControlNet Link Configuring Distributed I O The DriveLogix5730 controller supports distributed I O over a ControlNet link Configuring I O in a remote
150. ing 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 poriveExecutive c RSLogix 5000 Projects New Drive dnd EL File Edit View Drive Peripheral Tools Window Help De H SR 9 4 9 4 _ Node PowerFlex 7005 2 Port Upload From 0 PowerFlex 7005 2 Download 0 PowerFlex 7005 2 Glear Faults Glear Alarms FA tile Memory Display Datalinks Display SynchLink Display DriveLogix Display Faults amp Alarms D E Print Print Preview Print Setup Page Setup Groups 2 View the revision and ratings on the General tab of the Properties window x General Status and Feedback Component Details Product PowerFlex 700S 2 400V User Defined Text fi Configuration asov 214 Database Source SP Language English Protocol Support DPI i DB Created Using DPI Series A Last Upload Unknown Revision fi 005 Connection Unknown File Path ic RSLogix S000 Projects New Drive dno Harmony Path Cancel 3 Refer to Viewing the Communication Interface to the Controller on page 2 16 to view
151. ing a domain name Important Be careful to write the ladder logic to ensure the MSG instructions are not continuously triggered to send email messages Creating String Type for Email String Data Type The tags for the email text and transmission status can contain as many as 474 characters For these tags you must create a user defined STRING data type that is larger than the default For example create a STRING data type named EMAILSTRING 1 While offline in the Controller Organizer right click on the folder for Strings and select New String Type fg RSLogix 5000 EtherNetIP_IO_Example PowerFlex 7005 2 File Edit View Search Logic Communications Tools Window El elal 8l ES L ofja Offline D E RUN n Fd Path lt No Forces b KUE NoEdts 8 E iin 4 HJE 2 Enterthe Name e g EMAILSTRING and the maximum number of JE dr Kro characters e g 520 Ga H E D Control Control a Controller EtherNetIP_IO_Example ler Tags ler Fault Handler EH Power Up Handler Ely Tasks B 48 MainTask 3 MainProgram Unscheduled Programs B E Motion Groups Ungrouped Axes C3 Trends eq Data Types 4 User Defined Predef y Lg Module 3 63 1 0 Configi Copy Drivelo I Paste 179 Click Apply then OK Name EMAILSTRING Description Cut Maximum Characters 520
152. ing 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 A higher priority task will interrupt any lower priority task The continuous task has the lowest priority and is always interrupted by a periodic task The DriveLogix5730 controller uses a dedicated periodic task at priority 7 to process I O data This periodic task executes at the Requested Packet Interval RPI you configure for the CompactBus which can be as fast as once every 1 ms Its total execution time is as long as it takes to scan the configured I O modules How you configure your tasks affects how the controller receives I O data Tasks at priorities 1 to 6 take precedence over the dedicated I O task Tasks in this priority range can impact I O processing time If you configure the I O RPI at Ims and you configure a task of priority 1 to 6 that requires 500 us to execute and is scheduled to run every millisecond this leaves the dedicated I O task 500 us to complete its job of scanning the configured I O However if you schedule two high priority tasks 1 to 6 to run every millisecond and they both require 500 us or more to execute no CPU time would be left for the dedicated I O task Furthermore if you have so much configured I O that the execution time of the dedicated I O task approaches 1 ms or the combination of t
153. ion when it is executed You can configure the 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 datatablereadorwite S ya PLC2 PLC3 PLC5 or SLC all types CIP CIP with Source ID DH X CIP generic CIP Optional block transfer read or write X You can connect CIP generic messages but for most applications we recommend you leave CIP generic messages unconnected 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 Do not cache the The connection closes after the MSG instruction is done This frees up connection that connection for other uses The controller has the following limits on the number of connections that you can cache If you have this software Then you can cache and firmware revision 12 x or later up to 32 connections Communicating with Devices on a ControlNet Link 7 11 Communicating with Another Logix Based Controller All Logix based controllers can use MSG instructions to communicate with each oth
154. it Switch Normally Open Closed Active Home Sequence Group Direction EAE EE Y Speed Return Speed 0 1 rev s 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 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 Passive homing for a given home sequence works similar to the corresponding active homing sequence except that no motion is commanded the controller just waits for the switch and marker events to occur Position Type the desired absolute position in position units for the axis after the specified homing sequence has been completed In most cases this position will be set to zero although any value within the software travel limits can be used After the homing sequence is complete the axis is left in this position If the Positioning Mode set in the Conversion tab of the axis is Linear then the home position should be within the travel limits if enabled If the Positioning Mode is Rotary then the home position should be less than the unwind distance in position units Configuring DriveLogix Motion 4 13 Offset Type
155. iveLogix5730 controller controls Controller and distributed I O through a 1794 AENT module Distributed I O DriveLogix5730 controller DriveLogix1 EtherNet IP 1794 AENT with distributed I O Remote Controlling Distributed I O This example has DriveLogix1 controlling the I O connected to the remote 1794 AENT module The data the DriveLogix5730 controller receives from the distributed I O modules depends on how you configure the 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 All analog modules require direct connections Diagnostic modules support rack optimized connections but require direct connections to take full advantage of their diagnostic features Total Connections Required by DriveLogix1 The following table calculates the connections used in this example Connection Amount DriveLogix1 to 4 distributed I O modules through 1794 AENT 4 all I O modules configured as direct connection no connection to the 1794 AENT total connections used 4 If you configured the distributed I O modules as rack optimized you would only need a rack optimized connection to the 1794 AENT reducing the above example by 3 connections 6 32 Communicating with Devices on an EtherNet IP Link Exam ple 2 Controller
156. ladder editor The display style does not have to match the display style of the tag in the remote controller All consumed tags are automatically controller scope The produced tag in the originating DriveLogix5730 controller must have the same data type as the consumed tag in the consuming controller The DriveLogix5730 controller performs type checking to make sure proper data is being received Important If a consumed tag connection fails none of the tags are transferred from the producing controller to the consuming controller Communicating with Devices on an EtherNet IP Link 6 19 Sending Messages The DriveLogix5730 controller can send MSG instructions to other controllers and devices over an EtherNet IP link Each MSG instruction requires you to specify a target and an address within the target Important Revision 15 xx of DriveLogix firmware adds more stringent range checks when reading to or writing from tags Message packets are limited to 240 bytes This could cause some MSG instructions that worked in previous firmware revisions to not work in revision 15 xx firmware For example use a CIP Generic MSG instruction to perform a Get Attribute Single service The attribute is 4 bytes in length Assume the destination tag is an INT data type 2 bytes in length In revision 13 xx firmware the MSG instruction places the first 2 bytes of the attribute in the destination tag In revision 15 xx firmware the MSG instruction er
157. le Ready Monitor Tags A Edit Tags KTS ojojojojojojojojojojo 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 drive status bits J I O Configuration a 2 PowerFlex 7005 2 400 drive module 889 CompactBus Local WE 1769 OW8 B Outputd Local Drive Alarm Unwind Drive Alarm 1 Alarm Indicating Lamp drive_module Alarm Local 1 0 Data 0 0 J lt gt Local Drive Fault Unwind Drive Fault 1 Fault Siren drive_module Faulted Local 1 0 Data 1 1 JE lt gt Local Drive Fault 1 Fault drive_module Faulted Unwind Drive Brake 0 Brake Set Local 1 0 Data 2 Recommended Programming Techniques Placing and Configuring the Drive 2 25 Naming Tags Use a convention when naming tags and consistently follow it The following convention is used internally at Allen Bradley lt prefix gt _ lt function gt _ lt suffix gt Prefix identifies the machine section in multi section programs Prefix examples Sct1 Section 1 Fan2 Fan 2 RewA Re
158. le Slot p Description this is the local PowerFlex 7005 Comm Format Speed Control X Revision fr E a Electronic Keying Compatible Module x Cancel Back Next gt Help 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 Any of the available communication formats create one direct connection to the drive You select the communication format when you configure the drive module Module Properties Controller 2 PowerFlex 7005 2 400 1 1 E xl Type PowerFlex 700S 2 400V Drive Interface 400V Vendor Allen Bradley Parent Controller Name drive module Slot B Description this is the local PowerFlex 700S El Comm Format Speed Control Motion Control Revision ntrol Position 5 ntrol User Defined 1 User Defined 2 Cancel Back Next gt Help The default communication format for the drive is Speed Control The tags are created as controller scoped tags The following tag structure shows the 2 6 Placing and Configuring the Drive Speed Control format The tag structure for this example s drive
159. lex 7005 2 Fie Edit View Search Logic Communications Tools Window Help aaa a ase Ae Rem Prog No Forces b FT Controller OK FE No Edits a Battery OK D M Program Mode ra F 1 0 Not Responding w D HER Pan eorn Path as DFT 2 1 a See Bi 4 gt Favorites AEK EJ Controller 13_H10 Controller Tags C3 Controller Fault Handler CH Power Up Handler H E Tasks ER Motion Groups C3 Trends ea Data Types YO Configuration CompactBus Local 5 Ethernet Port E12 FJ 2 PowerFlex 7005 2 400V H12 Af New Module 1788 ENBT A NetLinxENet amp Cut Ctrl X Copy Ctrl C E Paste Ctrl Y Delete Del Cross Reference Ctrl E 6 Select the Port Configuration tab and enter the proper data Uncheck the Enable Bootp checkbox Click Set Apply and OK to make changes E Module Properties Controller 1 Drivelogix5730 Ethernet Port 1 1 General Connection ASNetWore Module Info Port Configuration Port Diagnostics IP Address 10 91 13 210 ra hls Must Match IP Address on General Tab DENENA Subnet Mask Gateway Address 10 9 13 1 Primary DNS 255 255 255 O Select Port Speed J z Current Port Speed 100 Mbps Server Address 0 0 0 0 Select Duplex z Secondary DNS fo o 0 0 Server Address 0 0 0 0 Current Duplex Full Duplex Changes to Port Speed and
160. line with the RSLogix 5000 software 6 7 controller that communicates to or through the EtherNet IP module 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 6 6 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 Make a serial connection to the controller via the CHO serial connector You might also need to use RSLinx software to create a DF1 driver for the workstation See Chapter 5 for more information 3 Start RSLinx Open the RSWho window Navigate in RSWho to the Ethernet network 4 Right click on the Ethernet port not the controller and select Module Configuration RYRSLinx Gateway RSWho 1 File Edit View Communications Station DDE OPC Security Window Help 2 2 8 Blk x ERswho 1 IV Autobrowse Workstation USMEQISTO38 s Linx Gateways Ethernet r 5 1784 PCIDS 1 DeviceNet 2s AB_DF1 1 Data Highway Plus s AB_DF1 2 DF1 El ff 01 DriveLogix5730 13_H10 Backpl
161. link 5 5 CompactBus 3 5 controller response to connection failure 3 12 ControlNet daughtercard 7 3 DF1 master 5 9 DF1 point to point station 5 6 DF1 slave 5 8 DH 485 port 9 3 drive 2 3 EtherNet IP communications driver 6 10 generic 1769 MODULE 3 17 local I O 3 7 network parameters with BOOTP DHCP 6 3 network parameters with RSLinx 6 6 network parameters with RSLogix 5000 6 7 remote connection via serial link 5 7 system for ControlNet 7 1 system for DH 485 9 2 system for serial link 5 1 the serial port 5 3 connecting ASCII device 5 11 battery B 4 Index 2 connection failure configuring controller response to 3 12 ControlFlash 1 3 ControlNet accessing distributed I O 7 5 communicating to non Logix controllers 7 11 configuring communications driver 7 2 configuring system for 7 1 consuming tags 7 16 daughtercard 7 3 1 0 7 4 mapping addresses communication to non Logix controllers 7 12 messages 7 9 producing and consuming data 7 14 7 20 7 23 producing tags 7 16 scheduling network 7 7 D daughtercard ControlNet 7 3 installing B 9 De energizing the Drive 1 2 2 1 3 1 4 1 5 1 6 1 7 1 8 1 9 1 B 1 DeviceNet 1769 ADN adapter 8 3 1788 DNBO DeviceNet scanner 8 5 I O 8 2 DF1 master 5 9 point to point station 5 6 slave 5 8 DH 485 Belden 3106 cable 9 7 Belden 9842 cable 9 7 browsing 9 9 configuring port 9 3 configuring system for 9 2 configuring the port 9 3 grounding 9 8 installing network 9 6 network initi
162. ll Logix5000 controllers DriveLogix specific information is also available For Read this document Document number Information on the DriveLogix Instruction Set Logix5000 Controllers General Instruction Set Reference 1756 RM003 Manual Information on function block programming Logix controllers Logix5000 Controllers Process Control Drives Instruction 1756 RMO06 Set Reference Manual Execution times and memory use for instructions Logix5000 Controllers Execution Time and Memory Use 1756 RM087 Reference Manual Information on selecting CompactLogix and Compact I O Compact I O Selection Guide 1769 SG001 components and modules Information on installing configuring and using Compact Compact I O Analog Modules User Manual 1769 UM002 Analog I O modules Information on installing configuring and using PowerFlex PowerFlex 700S Phase II User Manual 20D UMO006 7008 drives Information on the DriveLogix Motion Control Instruction Set _ Logix Controller Motion Instruction Set 1756 RM007 Information on installing an ControlNet communications ControlNet Communications Daughtercard Installation 1788 IN002 daughtercard Coax Instructions Information on installing an ControlNet communications ControlNet Communications Daughtercard Installation 1788 IN005 daughtercard Fiber Instructions Information on installing an EtherNet IP communications EtherNet IP Communications Daugh
163. loop to receive position commands from DriveLogix via the Interpolator 824 Local I O Status Bit0 0 Eliminate erroneous physical axis faults Bit 1 1 904 SL Node Cnfg 7 Bit0 1 This sets up the SynchLink as the time keeper This is used Changes to these parameters require a dr Reset Req d on the status line to synchronize the Drive and DriveLogix ive reset before the changes will take effect The HIM will indicate 4 20 Configuring DriveLogix Motion Downloading the Settings and Links to the Drive 1 From the Drive Menu select Display Download podriveExecutive c RSLogix 5000 Projects 700S DriveLogi B Fie Edit View Drive Peripheral Tools Window Help De W amp Connect to Drive Undefined Nod GERE Be EB o Power TYEFF FF EA Linear Upload From 0 PowerFlex 7005 2 ERS Download 0 PowerFlex 7005 2 La Motor 2a Dynam DEVICE Web Page Ea Speed Display Datalinks 3 Torque Display SynchLink H C2 Proces Display DriveLogix H a Positiot CA Speed Faults Events and Alarms Ha Utility Won oletile menor 23 Comme Display Diagnostic Itens 22 Inputs C3 User Fi Ca Default Groups Properties Refresh Node STrim2 Filt Gain 2 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 Programming is Nece
164. ls on the Power Terminal Block The voltage must be zero 4 Connect or disconnect the programming or network cable 5 Turn power back on and proceed with configuring DH485 communication When using a DriveLogix5730 controller it is recommended that you use NetLinx networks EtherNet IP ControlNet or DeviceNet because excessive traffic on a DH 485 network may make it impractical to connect to a DriveLogix5730 controller with RSLogix 5000 programming software DriveLogix5730 processors fully support the DH 485 protocol but using the recommended NetLinx networks is more practical 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 DriveLogix5730 controller to act as a DH 485 interface By using a 1761 NET AIC and the appropriate RS232 cable 1756 CP3 or 1747 CP3 a DriveLogix5730 controller can send and receive data on a DH 485 network Important A DH 485 network consists of multiple cable segments Limit the total length of all the segments to 1219m 4000 ft 9 2 Communicating with Devices on a DH485 Link Configuring Your System for a DH 485 Link RS 485 port baud rate selector switch port 1 DB 9 RS 232 DTE For the DriveLogix5730 controller to operate on a DH 485 network you need a 1761 NET AIC interface converter for each DriveLogix5730 controller you want to put on the DH 485
165. make 7 2 Communicating with Devices on a 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 For more information about configuring a 1788 CNx communication daughtercard see For this card See this document 1788 CNC CNCR 1788 IN002 1788 CNF CNFR 1788 IN005 Configuring 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 5 RSLinx Gateway File Edit View Communications Station DDE OPC 2 S S RSWho x aixi Configure Configure Shortcuts Configure Client Applications Configure CIP Options Configure Gateway Close Available Driver Types 1784 KTCR for ContralNet devices x Add New r Configured Drivers Help Name and Description Status Driver Diagnostics CIP Diagnostics Gateway Diagnostics Configure Startup Start p Ae ER The installation instructions for the communications daughte
166. mary l 17e8 DNB0 Name 1 788 DNBO Description Address E Device Identity Primary Vendor RockwellAutomation AllenBradey 1 Type Communication Adapteri o Device fi788DNBO BI SSS Catalog sono s lt Ss Revision Ao 2 Click the Scanlist tab then click Upload when prompted The area on the left is called Available Devices and the area on the right is called Scanlist The 1769 ADN adapter should be on the left General Module Scanlist Input Output ADR Summary Available Devices Scanlist 171 1763 ADN Compact I gt gt lt lt REE IV Automap on Add FE Node Active ic Ke Upload from Scanner F perni Ra Download to Scanner Edit 1 0 Parameters 8 6 Communicating with Devices on a DeviceNet Link 3 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 Then click on the Edit I O Parameters button 2 x General Module Scanlist Input Output ADR Summary Available Devices Scanlist J 21 1769 4DN Compact I zl IF Automap on Add IV Node Active Edit 1 0 Parameters 21 1769 ADN Compact 1 0 Ada te 2 x immer Electronic Key load from Scanner VISSE SSS ee IV Vendor g F a Download to Scanner 7 Product Code Input Size p 4 Bytes Change of State Cyclic Edit 1 0 Para
167. meters Minean Danae E Edil arameters Rey sete Use Wutput Br FM Minot I or higher Input Size E 3 Bytes Poles Ouputsie O byes Input Size 14 Bytes Heartbeat Rate 250 i msec Output Size ig Bytes sy Poll Rate Every Scan x Cancel Restore 1 0 Sizes 4 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 In this example the scanner transmits 6 bytes to the adapter output data and receives 28 bytes from the adapter input data Click OK when finished with this screen General Module Scanlist Input Output ADR Summary 5 Click on the Input tab AutoMap Then click Apply and OK 21 176 Polled B apee Unmap Advanced Options Memory Assembly Data x Start DWord 0 3 Download when prompted Bits 31 0 1 Datal2 lt lt at T Papas Daab J o o Daa PT 1 1 Datal81 Cancel Apply Help Communicating with Devices on a DeviceNet Link 8 7 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 conf
168. mmunication Format IESeMReeinst s set to Motion Control Source oriwvetoga Tao value Used By Parameter UserDefinedRealData 0 a UserDefinedRealDatal1 UserDefinedRealData 2 f l UserDefinedRealData 3 mi UserDefinedRealData 4 UserDefinedRealData 5 UserDefinedRealData 6 i UserDefinedRealData 7 F UserDefinedRealData 8 UserDefinedRealData 9 UserDefinedRealData 10 UserDefinedRealDeta 11 E UserDefinedintegerData 0 O UserDetinedintegerData 1 0 UserDefinedintegerData 2 i 0 UserDefinedintegerData 3 0 UserDetinedintegerData 4 0 UserDefinedintegerData 5 i 0 UserDefinedintegerData 6 0 UserDefinedintegerData 7 0 UserDefinedintegerData 3 i 0 DriveLogix Connection Status Undetermined Refresh Value ee Click OK to apply and close the DriveLogix Setup Dialog Next link the appropriate parameters to the words being produced and consumed by the controller 4 Onthe Links view double click on the desired Sink parameter 5 Click on the Link Source tab ie 7005 DriveLogix5730 Moti Undefined Node B 0 Powerflex 7005 2 19 Linear List Ca Monitor 3 Motor Control R C3 Speed Control C3 Torque Control C3 Process Control C3 Position Control C3 Speed Posit Fdbk CZ utility Ca Communication OZ Inputs amp Outputs C3 User Functions ER Default Custom
169. mple 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 rack optimized connection for the DIN rail direct connection for each I O module DriveLogix1 controller to local 1788 CNC ojoj wr DriveLogix1 controller to remote 1788 CNC connected cached MSG from DriveLogix1 to DriveLogix2 1 produced tagA produced from DriveLogix1 to DriveLogix2 1 other consumer 2 are configured 1 produced tagA produced from DriveLogix1 to DriveLogix2 1 other consumer 2 are configured 1 consumed TagB 1 total connections used 10 If you configured the local I O modules as rack optimized you would only need the DIN rail connection to the I O modules reducing the above example by 3 connections In the following example one DriveLogix controller communicates with a Logix5550 controller and a ControlNet PLC 5 controller over ControlNet 8 SUUDAN Q DriveLogix5730 Controller ControlLogix Controller ControlNet PLC5 DriveLogix5730 Controller DriveLogix1 Control1 Controller DriveLogix2 PLC5C1 Type of Logix MSG instruction Typed Read Communicating with Devices on a 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 M
170. mpliant with e EN 50082 2 Industrial Immunity e EN 61326 Meas Control Lab Industrial Requirements e EN 61000 6 2 Industrial Immunity e EN 61000 6 4 Industrial Emissions C Tick Australian Radio communications Act compliant with Pending at time of printing e AS NZS CISPR 11 Industrial Emissions EtherNet IP ODVA conformance tested to EtherNet IP specifications c UL us UL Listed for Class Division 2 Group A B C D Hazardous Locations certified for U S and Canada See the Product Certification link at www ab com for Declarations of Conformity Certificates and other certification details Real Time Clock Accuracy Ambient C Accuracy 0 C 54 to 56 seconds month 259C 9 to 124 seconds month 40 C 84 to 234 seconds month 55 C 228 to 394 seconds month 60 C 287 to 459 seconds month DriveLogix5730 Controller Specifications A 3 Controller LEDs 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 Follow Safety related practices of NFPA 70E ELECTRICAL SAFETY FOR EMPLOYEE WORKPLACES DO NOT work alone on energized equipment ATTENTION The controller LEDs are only operational when RUN Drive RUN DriveLogix FORCE 1 0 COM BAT OK
171. n are the two nodes DF1 slave mode using a controller as a slave station in a master slave serial communication network 5 8 When there are multiple slave stations on the network link slave stations using modems or line drivers When you have a single slave station on the network you do not need a modem to connect the slave station to the master you can configure the control parameters for no handshaking You can connect 2 255 nodes to a single link In DF1 slave mode a controller uses DF1 half duplex protocol One node is designated as the master and it controls who has access to the link All the other nodes are slave stations and must wait for permission from the master before transmitting User mode communicating with ASCII devices 5 12 This requires your program logic to use the ASCII instructions to read and write data from and to an ASCII device Important Half Duplex settings do not work as with other Logix controllers RTS and CTS are not functional Communicating with Devices on a Serial Link 5 5 Configuring the Communication Driver Use RSLinx software to configure the serial communication driver Select the DF1 driver 1 In the Communications menu select the Configure Driver From the Available Driver Type list select the DF1 Driver then click Configure RY RSLinx Gateway RSWho 1 File Edit View Se i tert Station DDE OPC Security Window Help Configure Shortcuts Configure Cli
172. nedIntegerData 2 616 FromDriveLogix14 User Defined UserDefinedIntegerData 3 617 FromDriveLogix15 User Defined UserDefinedIntegerData 4 618 FromDriveLogix16 User Defined UserDefinedIntegerData 5 619 FromDriveLogix17 User Defined UserDefinedIntegerData 6 620 FromDriveLogix18 User Defined UserDefinedIntegerData 7 621 FromDriveLogix19 User Defined UserDefinedIntegerData 8 622 FromDriveLogix20 User Defined Linked Parameter LogicStatus 626 To DriveLogix00 155 Logic Status UserDefinedRealData 0 627 To DriveLogix01 User Defined UserDefinedRealData 1 628 To DriveLogix02 User Defined UserDefinedRealData 2 629 To DriveLogix03 User Defined UserDefinedRealData 3 630 To DriveLogix04 User Defined UserDefinedRealData 4 631 To DriveLogix05 User Defined UserDefinedRealData 5 632 To DriveLogix06 User Defined UserDefinedRealData 6 633 To DriveLogix07 User Defined UserDefinedRealData 7 634 To DriveLogix08 User Defined UserDefinedRealData 8 635 To DriveLogix09 User Defined UserDefinedRealData 9 636 To DriveLogix10 User Defined UserDefinedRealData 1 0 637 To DriveLogix1 1 User Defined UserDefinedRealData 1 1 638 To DriveLogix12 User Defined UserDefinedIntegerData 0 639 To DriveLogix13 User Defined UserDefinedIntegerData 1 640 To DriveLogix14 User Defined UserDefinedIntegerData 2 641 To DriveLogix15 User Defined UserDefinedIntegerDa
173. nfigurable parameter maximum node address The default value for this parameter is 31 for all initiators and responders Communicating with Devices on a DH485 Link 9 5 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 Network initialization begins when an initiator on the network detects a period of inactivity that exceeds the time of a link dead timeout When the link dead timeout is exceeded usually the initiator with the lowest address claims the token When an initiator has the token it will begin to build the network Building a network begins when the initiator that claimed the token tries to pass the token to the successor node If the attempt to pass the token fails or if the initiator has no established successor for example when it powers up it begins a linear search for a successor starting with the node above it in the addressing When the initiator finds another active initiator it passes the token to that node which repeats the process until the token is passed all the way around the network to the first node At this point the network is in a state of normal operation Number of Nodes and Node Addresses The number of nodes on the network directly affects the data transfer time between nodes Unne
174. ng and Configuring the Drive 2 17 2 To send additional data from the drive to the controller go to the To DriveLogix tab DriveLogix Setup PowerFlex 7005 2 q xl From DriveLagix To DriveLogix Communication Format speed Control z 155 Logic Status 000000000000000000 LogicStatus 71 Filtered SpdFdbk 0 0000 RPM i FilteredSpdFdbk 303 Motor Torque Ref 0 0000 P U i MotorTorqueRet 308 Output Current 0 00 Amps i OutputCurrent 555 MC Status 000000000000000000 MCStatus Click the button in front of the 824 Local I O Status 000000000000000000 LocallOStatus UserDefinedRealData 0 UserDefinedRealData 1 UserDefinedRealData 2 UserDefinedRealData 3 UserDefinedRealData 4 i UserDefinedRealData 5 UserDefinedRealData 6 UserDetinedintegerData 0 UserDefinedintegerData 1 i UserDefinedintegerData 2 UserDefinedintegerData 3 UserDetinedintegerData 4 UserDefinedintegerData 5 i UserDefinedintegerData 6 UserDefinedintegerData 7 UserDefinedRealData 0 tag a fe es Ses fey R E es es DriveLogix Connection Status Undetermined Refresh Value OK Cancel Apply Find 207 rev gt Next 305 Mtr Trq Curr Ref 306 DC Bus Voltage k Output Voltage Output Current 310 Output Freq xl Select Cancel 3 Select the desired source parameter 307 Output Voltage in this example in the resulting window Configuring the Drive s Respon
175. ng to the communication ports Measure the DC bus voltage at the DC amp DC terminals on the Power Terminal Block The voltage must be zero ATTENTION Severe injury or death can result from electrical During the process of configuring ControlNet communication you will need to connect or disconnect a programming or network cable at the controller You should do this only if the drive is de energized 1 Turn off and lock out input power Wait five minutes 2 Verify that there is no voltage at the drive s input power terminals 3 Measure the DC bus voltage at the DC amp DC terminals on the Power Terminal Block The voltage must be zero 4 Connect or disconnect the programming or network cable 5 Turn power back on and proceed with configuring ControlNet communication For the DriveLogix5730 controller to operate on a ControlNet network you need e a workstation with an appropriate ControlNet communication daughtercard e a1788 CNx communication daughtercard installed in the DriveLogix communication slot e RSLinx software to configure the ControlNet communication driver RSLogix 5000 programming software to configure the 1788 CNx communication daughtercard as part of the DriveLogix system e RSNetWorx software to schedule the DriveLogix system on the network Configuring the Hardware Before you can connect the DriveLogix system to the ControlNet network you must configure the 1788 CNx communication daughtercard and
176. nizer select CompactBus Local icon Right click and select New Module File Edit View Search Logic Communications Tools Wine alata a VER HS Offline J E RUN ll P4 o F ok Eg X meee DAT No Edits a Evo a Ki IO AG EJ Controller quick start A controller Tags C3 Controller Fault Handler C3 Power Up Handler 3 6 Tasks 5 8 MainTask H E MainProgram C3 Unscheduled Programs B E Motion Groups C3 Ungrouped Axes CH Trends Data Types C User Defined H E Strings Ca Predefined FL Module Defined 2 Select the 1769 MODULE Generic 1769 Module E 1 0 Configuration x TET EES xl 2 PowerFlex 7005 2 400 drive module Type f1763 MODULE Satie CompactBus Loc Description n763H5C High Speed Counter ob Cut Ctri x 1769 1416 16 Point 120V AC Input Ba Copy Ctrl C 17531481 8 Point Isolated 120V AC Input k Paste Ctrl 1759F4 4 Channel Current Voltage Analog Input Delete Del 17891F4X0F2 4 Channel Input 2 Channel Output Low Resolution Analog 17631M12 12 Point 240V AC Input 1769 1016 16 Point 24V DC Input Sink Source 1769 1016F 16 Point 24V DC High Speed Input 1769 1032 32 Point High Density 24V DC Input 1769 IQB lt OW4 6 Point 24V DC Sink Source Input 4 Point AC DC Relay Output 1769 IR6 6 Channel RTD Direct Resistance Analog Input 1769 IT6 6 Channel Thermocouple m Analog Input fr Generic 1769 Module 1769 0416 16 Point 100V
177. ns pallets widgets etc 20 Define Average Velocity Timebase as the sample rate that is used for the Average Velocity tag in the controller tags Axis Properties Axis00 General Motion Planner Units Conversion Homing Dynamics Tag Position Units re Average Velocity Timebase 0 25 Seconds Cancel Apply Help 21 On the Conversion tab setup the Positioning Mode for Linear to Rotary 22 The Conversion Constant is the number of feedback counts per Position Unit se Axis Properties Axis00 General Motion Planner Units Conversion Homing Dynamics Tag Positioning Mode Rotary 7 Conversion Constant 4096 0 Feedback Counts 1 0 rev Position Unwind 4096 Feedback Counts Unwind 4 12 Mode Configuring DriveLogix Motion 23 On the Dynamics tab define the limits for speed acceleration and deceleration Important Do not exceed the system dynamics 5 Axis Properties Axis00 General Motion Planner Units Conversion Homing Dynamics Tag Maximum Speed 29 rev s Maximum Acceleration 100 rev s 2 Maximum Deceleration rev s 2 Cancel Apply Help 24 On the Homing tab setup the Homing Mode Position Offset and Sequence values Refer to the following tables f Axis Properties Axis00 General Motion Planner Units Conversion Homing Dynamics Tag Mode Active z Position rev Offset rev Sequence Switch Lim
178. ntrol for use with Logix motion commands User Defined 1 for general use as required User Defined 2 for general use as required Each communication format contains a number of pre defined tags and user defined tags The pre defined tag names and data types correspond with the associated parameters within the drive s firmware that are necessary to support the selected communications format Links must be established in the firmware using DriveExecutive software to support the pre defined tags Linking is a software mechanism that configures data flow within the drive s firmware The links within the firmware to support the pre defined tags are protected 2 2 Placing and Configuring the Drive Determining When the Controller Updates the Drive and must be present If the associated links are not present or are deleted the communication connection between the controller and drive will be lost The user defined tags are made up of a fixed number of REAL floating point and DINT double integer data types Links are not required within the drive s firmware to support these tags Therefore links may be created and deleted as desired without having an affect on the communication connection between the controller and the drive The user defined tags may be used to address application specific data needs not covered by the pre defined tags Mapping for Inputs and Outputs For each of the 21 inputs and 21 outputs there is a dedi
179. nual Preface Overview This manual is intended for qualified personnel You must be able to program and operate Adjustable Frequency AC Drive devices and programmable controllers This manual guides the development of projects for DriveLogix controllers It provides procedures on how to establish communications e with the following networks ControlNet DeviceNet EtherNet IP serial e with the following devices PowerFlex 700S drive controllers I O workstations PanelView terminals p 2 Overview Related Documentation www rockwellautomation com literature Allen Bradley publications are available on the internet at These core documents address the Logix5000 family of controllers If you are 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 an experienced user of Logix5000 controllers Logix5000 Controllers System Reference publication 1756 QR107 This system reference provides a high level listing of configuration information controller features and instructions ladder relay function block diagram and structured text any user of a Logix5000 controller Logix5000 Controllers Common Procedures publication 1756 PM001 This common procedures manual explains the common features and functions of a
180. o 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 C The continuous task runs at the lowest priority and is interrupted by all other tasks D A lower priority task can be interrupted multiple times by a higher priority task E When the continuous task completes a full scan it restarts immediately unless a higher priority task is running 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 are not 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 Selecting a System Overhead Percentage What is DriveLogix5730 1 9 Defining routines A routine is a set of logic instructions in a single programming language such as ladder logic Routines provide the executable code for the project in a controller A routine is similar to a program file or subroutine in a PLC or SLC controller 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
181. oduces data to the controller every 2 milliseconds The drive updates the inputs and outputs to the controller asynchronous to both the program scan and I O scan of the controller Placing and Configuring the Drive 2 3 Placing and Configuring the When you create a project for the DriveLogix controller in RSLogix 5000 Drive 1 the Controller Organizer automatically displays the local DIN rail for Compact I O You must add the PowerFlex 700S drive to the configuration in a manner similar to adding an I O module The Controller Organizer automatically places the drive in slot two In the Controller Organizer select the I O Configuration folder Right click the selected folder and select New Module 3 6 Controller Motion Drive Controller Tags Controller Fault Handler Power Up Handler Tasks i re a MainTask 2 Select the drive PowerFlex 700S 2 400V in this example amp MainProgram G Unscheduled Programs Phases Motion Groups Select Module Type x Ungrouped Axes Trends Type Powerflex 700S 2 400V 2 Data Types Cy User Defined Oa Strings Oi Predefined Description 11 788 CNC A 1788 ControlNet Bridge Coax Media 1 788 CNCR A 1788 ControlNet Bridge Redundant Coax Media 1788 CNF A 1788 ControlNet Bridge Fiber Media Gig Madule Defined 1788 CNFR A 1788 ControlNet Bridge Redundant Fiber Media Sie ej 1788 DNBO 4 1788 DeviceNet Scanner m New Module 1 788 ENBT 4 1788 10 100 Mbps Ethern
182. on path in this example is For this item Specify Communication Path 1 1 2 XXX XXX XXX XXX 1 0 where 1 is the virtual backplane of DriveLogix1 1 is the slot of the Ethernet port in the controller note the 1 1 displays as LocalENB 2 is the EtherNet IP network 100 100 115 11 is the IP address of DriveLogix2 1 is the virtual backplane of DriveLogix2 0 is the controller slot of DriveLogix2 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 1 produced tagA produced from DriveLogix1 to DriveLogix2 1 other consumer 2 are configured 1 consumed tagB 1 total connections used 4 Receiving a MSG Instruction When other devices send messages to the DriveLogix5730 controller the path for the message must identify the controller Configure a CIP type message in the originating device Specify the path the DriveLogix5730 controller as XXX XXX XXX XXX 1 1 IP Address Sd virtual backplane slot 1 6 36 Communicating with Devices on an EtherNet IP Link Notes De energizing the Drive to Connect or Disconnect a Cable Configuring Your System for a ControlNet Link Chapter 7 Communicating with Devices on a ControlNet Link shock or burn Verify that the voltage on the bus capacitors has discharged before connecti
183. 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 or 1761 CBL AC00 port 2 1761 CBL AP00 mini DIN 8 RS 232 connection or 1761 CBL PM02 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 2 On the System Protocol tab specify the appropriate serial communication configuration I RSLogix 5000 quick start PowerFlex 7005 fg Controller Properties quick start lol x File Edit View Search Logic Communications Too Date Time Advanced SFC Execution File Nonvolatile Memory jz J gt bel 8 ob Ese 5j General SerialPort System Protocol User Protocol Major Faults Minor Faults 5 E Offline D RUN LA ki Error Detection irea b SE 4 Protocol DF1 Point to Point pec C crc 4 T Nees a E 0 w SO ESS w IV Enable Duplicate Detection i gt NAK Receive Limit 3 ERE Controller quick star ENQ Transmit Limit g veril G Controler Tags OWY ACK Timeout 0 20m Controller Fault print Ctrl P E Power Up Handle Embedded Responses Autodetect 7 B E Tasks H A MainTask Cancel Apply Help 3 On the Serial Port tab specify the appropriate communication settings FE Controller Properties quick start 5 oj
184. onfiguring the MSG Instruction that Transmits the Email 1 On the Configuration tab of the Message Configuration fill out the following fields Message Configuration SendEMailText E xl Configuration Communication Tag Message Type CIP Generic Be Service Custom Source Element EmaiTest 7 Type Source Length 114 Bytes Service fab p Code 4b Hex Class 32f Hex Destination EmailStatus X Instance 1 Attribute 0 Hex New Tag Enable Error Code Error Path Error Text Enable Waiting Start O Done Done Length 0 Extended Error Code I Timed Out Cancel Apply Help In this field Enter Service Type Custom Service Code 4b Instance 1 Class 32f Attribute 0 Source Element the tag that contains the email text This tag is of the STRING data type you created to contain the email text In this example EmailText Source Length the number of characters in the email text plus 4 In this example enter 114 110 characters in the email 4 Destination a tag to contain the status of the email transmission This tag is also of the STRING data type you created to contain the email text In this example EmailStatus Communicating with Devices on an EtherNet IP Link 6 29 2 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
185. onnect or Disconnect a Cable About this Chapter System Requirements Chapter 4 Configuring DriveLogix Motion 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 amp DC terminals on the Power Terminal Block The voltage must be zero N ATTENTION Severe injury or death can result from electrical During the process of configuring DriveLogix motion you will need to connect or disconnect a programming or network cable at the controller You should do this only if the drive is de energized 1 Turn off and lock out input power Wait five minutes 2 Verify that there is no voltage at the drive s input power terminals 3 Measure the DC bus voltage at the DC amp DC terminals on the Power Terminal Block The voltage must be zero 4 Connect or disconnect the programming or network cable 5 Turn power back on and proceed with configuring DriveLogix motion This chapter introduces DriveLogix5730 motion The steps in this chapter provide the minimum settings required to begin testing DriveLogix motion PowerFlex 700S Phase II Drive with firmware revision 2 XX or higher DriveLogix5730 Controller with firmware revision 15 XX or higher DriveExecutive programming software version 3 02 or higher RSLogix 5000 programming software version 15 or higher 4 2 Configuring DriveLogix Motion Programming the Controller In RSLogix
186. onnecting to the controller 5 Select the controller and click OK 6 Select the revision level to which you want to update the controller and click Next 7 To start the update of the controller click Finish and then click Yes 8 After the controller is updated the status box displays Update complete Click OK 9 To close ControlFlash software click Cancel and then click Yes 1 4 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 2 Make sure the appropriate network connection is made before starting Use RSLogix 5000 programming software to download a controller project If the processor firmware does not match that project revision AutoFlash automatically launches Select the catalog number of the controller and click Next Expand the network until you see the controller If the required network is not shown first configure a driver for the network in RSLinx software If you use an Ethernet connection to load the firmware which is much faster than the serial connection the utility will ask for a valid IP address before connecting to the controller Select the controller and click OK Select the revision level to which you want to update the controller and click Next To start the update of the controller click Fini
187. onnection Associated Axes Module Info Power Drive File C ASLogix 5000 Projects E xisting Drive dno Browse Found In C RSLogix SO00 Projects Launch DriveExecutive Q View and edit the parameter and link data associated with this drive Status Offline Accessing Drive Data Monitoring Drive Data Placing and Configuring the Drive 2 21 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 This address variable Is ModuleName Identifies the module name entered during the drive module configuration Type Type of data input O output MemberName Specific data from the drive depends on the selected communication format For tags associated with pre defined data links this name will be the same as the corresponding parameter name in the drive SubMemberName Specific data related to a MemberName Bit optional Specific bit of a DINT data value Refer to Communication Formats on page 2 5 for sample tag names The DriveLogix controller offers different levels at which you can monitor the drive module You can e configure the drive module so that the controller faults if the drive loses its c
188. onnection to the controller e use the programming software to display fault data e program logic to monitor fault data so you can take appropriate action 2 22 Placing and Configuring the Drive Configuring the Controller s You can configure the drive module to generate a major fault in the Response to a Connection controller if the drive loses its connection to the controller Failure fa Module Properties Controller 2 PowerFlex 7005 2 400 1 5 xl General Connection Associated Axes Module Info Power Setup Requested Packet Interval RPI 4044 ms 3 0 100 0 ms Check this box to configure the drive I Inhibit Module module to generate a major fault if it loses i its connection to the controller Module Fault Status Offline Cancel Apply Help If you do not configure the major fault to occur you should monitor the drive module status If the drive loses its connection to the controller e Outputs remain in their last e Inputs remain in their last state e By default the drive will fault the controller and other I O modules continue to operate based on old data from the drive and the drive can continue to operate based on old data from the controller To avoid potential personal injury and damage to machinery make sure this does not create unsafe operation ATTENTION If a drive loses its connection to the controller Configure the drive to generate a controller major fault when the drive
189. ons Drives PowerFlex 7005 2 2004 PowerFlex 7005 2 400 PowerFlex 7005 2 600 PowerFlex 700Se2 200 PowerFlex 700Se2 400V PowerFlex 700Se2 600 Drive Interface 200V Drive Interface 400 Drive InterFace 6004 Drive InterFace 2004 Drive InterFace 400V Drive InterFace 6004 Allen Bradl 4llen Bradl llen Bradl Allen Bradl llen Bradl Motion Other gt Eind Add Favorite By Category Favorites 0K Cancel Help 6 In the Major Revision dialog a Select the Major Revision number and click the OK button Select Major Revision Select major revision for new PowerFlex 700S 2 400V module being created Major Revision z Cancel Help 7 Configure the Drive by specifying the characteristics of the module using the New Module dialog a Enter a name for the drive in the Name field Drive Axis in this example a Select Motion Control in the Comm Format box b Verify that the Open Module Properties box is checked c Click the OK button New Module Type PowerFlex 7005 2 400V Drive Interface 400V Vendor Allen Bradley Parent Controller Name Drive_Axis Slot Description Comm Format Motion Contr o r Revision ay 4 Electronic Keying Compatible Keying E IV Open Module Properties Cancel Help Configuring DriveLogix Motion 4 5 8 On the Connections tab of the Modules Properties dialog a Change the value on the Requested Packet Interval RPI box to
190. ontrolNet Bridge Redundant Fiber Media 1788 DeviceNet Scanner 1788 10 100 Mbps Ethernet Bridge Twisted Pair Media 1788 10 100 Mbps Ethernet Bridge w Enhanced Web Services Generic 1788 Module 10 100 Mbps Ethernet Port on DriveLogix5730 1788 CNC A 1 788 CNCR A 1788 CNF A 1 788 CNFR A 1 788 DNBO A 1 788 ENBT A Ethernet Port Show Vendor fa gt IV Other IV Specialty 1 0 Select All Clear All IV Analog IV Digital IY Communication IV Motion IV Controller Cancel Help Module Properties Controller 1 Drivelogix5730 Ethernet Port 1 1 Type Drivelogix5730 Ethernet Port 10 100 Mbps Ethernet Port on DriveLogix5730 Vendor Allen Bradley Parent Controller Address Host Name Name Drivel ogix5730_Ethemet_Por Description 0 0 eg IPAddress 010 090 013 210 Host Name Slot fi 4 Major Revision E Cancel Back Next gt Finish gt gt Help 4 Enter a Name for the port and the desired address Click Finish Note The selected controller will verify that the IP address that has been assigned in this dialog does not belong to another device on the network If the IP address exists a warning message will display 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 th
191. ontrolNet 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 lf Enter this value for the API RPI gt NUT and RPI lt 2 NUT NUT RPI gt 2 NUT and RPI lt 4 NUT 2 NUT RPI gt 4 NUT and RPI lt 8 NUT 4 NUT RPI gt 8 NUT and RPI lt 16 NUT 8 NUT RPI gt 16 NUT and RPI lt 32 NUT 16 NUT RPI gt 32 NUT and RPI lt 64 NUT 32 NUT RPI gt 64 NUT and RPI lt 128 NUT 64 NUT RPI gt 128 NUT 128 NUT Exam ple 1 DriveLogix In the following example one DriveLogix5730 controller controls remote Controller and Remote I O I O through a 1794 ACN15 module DriveLogix5730 Controller DriveLogix1 SE pp OF FY OF g ControlNet 1794 ACN with remote I O Remote1 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 Example 2 DriveLogix5730 Controller to DriveLogix
192. ot including the power supply The Comm Format for the CompactBus is automatically set to Rack Optimized and cannot be changed Using the Connection tab you can specify the RPI for the systems and choose to inhibit or uninhibit the CompactBus E Module Properties Controller 3 CompactBus 13 1 om oj xj General Connection Requested Packet Interval RPI 2 0 ms 1 0 750 0 IV Inhibit Module J Major Fault Gn Controller If Connection Fails While in Run Mode r Module Fault Status Offline Cancel Apply Help The RPI you specify here is the RPI for every 1769 module on this controller s local CompactBus Specify an RPI from 1 750ms for the system You do not specify individual RPI values for each module By inhibiting and uninhibiting the CompactBus you can write new configuration data to the entire system at once The controller s response to a CompactBus connection failure is dependant upon the Compact I O modules configuration The checkbox which indicates that the controller will fault should be ignored for the CompactBus adapter Furthermore if any Compact I O module is configured to fault the module on connection loss any Compact I O module fault will cause the controller to fault Configuring Local I O Modules Placing and Configuring Local I O Use your programming software to configure the I O modules for the controller 1 In the Controller Organizer select Compac
193. otocol User Protocol Major Faults Minor Faults r Error Detection BCC C CRC Protocol DF1 Paint to Point J Controller Properties Serial Example 5 oj xj Station Address fo s 3 IV Enable Duplicate Detectior D 5 z ee Bb ate Time Advanced SFC Execution File Nonvyolatile Memory Memory NAK Receive Limit General SerialPort System Protocol User Protocol Major Faults Minor Faults ENQ Transmit Limit E ACK Timeout 50 x20 ms Protocol Embedded R gt a odete Read Write Buffer Size Bytes e2 Termination Character 1 sr 2 SFF Append Character 1 sr 2 Js TF XON XOFF I Echo Mode Delete Mode Ignore CRT Printer Cancel Apply Cancel Apply Help Use this mode For See page DF1 point to point communication between the controller and one other DF1 protocol compatible device 5 6 This is the default system mode This mode is typically used to program the controller through its serial port DF1 master mode control of polling and message transmission between the master and slave nodes 5 9 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 Also at least 2 nodes must exist to define your link as a network 1 master and 1 slave statio
194. pdTrim2 Filt Bw Speed Ref A Sel Speed Ref B Sel Jog Speed 1 Min Spd Ref Lim Max Spd Ref Lim Accel Time 1 Decel Time 1 S Curve Time SpdRef Filt Gain SpdRef Filt BW Spd Ref Bypass 60 0000 Hz 1750 RPM 30 0000 Hp Hp 4 2 0000 0 0000 1 0000 0 0000 1 0000 0 0000 0 0000 0 0000 0 0000 0 0000 0 0000 0 0000 0 0000 0 0000 0 0000 1 0000 1 0000 zi Pole Sec 200 0000 R S 2187 5 RPM 2187 50 RPM 10 0000 Sec 10 0000 Sec 0 5000 1 0000 0 0000 0 0000 Sec RIS 0x42700 1750 0x41F00 0 0 0 4 0 0x40000 0 0x00000 603 0x3F800 0 0x00000 0 0x3F800 0 0x00000 0 0x00000 0 0x00000 0 0x00000 0 0x00000 0 0x00000 0 0x00000 0 0x00000 0 0x00000 318 0x00000 0 0x3F800 0x3F800 0x43480 1 0x00000 0xBFA00 Ox3FA00 0x41200 0 0x41200 0 0x3F000 0 Ox3F800 0 0x00000 0 0x00000 43 460 2 0000 0 0000 1 0000 0 0000 1 0000 0 0000 0 0000 0 0000 0 0000 0 0000 0 0000 0 0000 0 0000 0 0000 0 0000 1 0000 1 0000 200 0000 Speed Ref 1 Speed Ref 1 0 0000 2187 5000 2187 5000 10 0000 10 0000 0 5000 1 0000 0 0000 0 0000 mn 75 0 1000 2 0000 1 0 2500 Hp 2 0 0100 2200000000 0000 2200000000 0000 2200000000 0000 2200000000 0000 14000 0000 14000 0000 14000 0000 14000 0000 14000 0000 14000 0000 14000 0000 14000 0000 14000 0000 14000 0000 1000 0000 15 0000 0 0000
195. point station 5 6 master 5 9 master station 5 9 master slave 5 8 remote connection 5 7 slave 5 8 specifications A 1 specifications A 1 electrical A 1 environmental A 1 EtherNet IP A 1 memory A 1 serial port A 1 Speed Control communication format 2 6 system overhead percentage 1 9 T tags aliases 3 14 consuming ControlNet 7 16 consuming EtherNet IP 6 18 producing ControlNet 7 16 producing EtherNet IP 6 17 tasks defining 1 6 task priorities 1 7 Turning Drive Off 1 2 2 1 3 1 4 1 5 1 6 1 7 1 8 1 9 1 B 1 U Unsupported Motion Commands C 1 User Defined 1 communication format 2 9 User Defined 2 communication format 2 10 user defined data types C 2 V virtual backplane 1 12 H www rockwellautomation com Power Control and Information Solutions Headquarters 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 Vorstlaan Boulevard du Souverain 36 1170 Brussels Belgium Tel 32 2 663 0600 Fax 32 2 663 0640 Asia Pacific Rockwell Automation Level 14 Core F Cyberport 3 100 Cyberport Road Hong Kong Tel 852 2887 4788 Fax 852 2508 1846 Publication 20D UM003B EN P January 2006 Supersedes 20D UM003A EN P July 2004 Copyright 2006 Rockwell Automation Inc All rights reserved Printed in USA Allen Bradley DriveLogix 5730 Controller User Manual
196. presentative or local distributor 13 Download the controller s memory and program from the computer with RSLogix 5000 programming software 14 Remove power from the drive and the DriveLogix5730 controller 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 amp DC terminals of the Power Terminal Block The voltage must be zero 15 Disconnect from the communication port 16 Re install the cover s 17 Dispose the old battery according to state and local regulations ATTENTION Do not incinerate or dispose lithium batteries A in general trash collection They may explode or rupture violently Follow state and local regulations for disposal of these materials You are legally responsible for hazards created while your battery is being disposed Access Procedures B 7 Installing the Embedded EtherNet IP Option Board Description Install and tighten standoffs 7 10 Ib 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 SURT fy Installing the DriveLogix5730 Expansion Board Task Description Q Align connector on DriveLogix5730 Expansion Board with connector on Main Control Board B Place DriveLogix5730 Expansion Board on the Main Control Board Inst
197. puter with RSLogix 5000 programming software Remove power from the drive and the DriveLogix5730 controller 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 amp DC terminals of the Power Terminal Block The voltage must be zero Remove control cassette Does the existing battery show signs of leakage or damage If Then Yes Before handling the battery review Guidelines for Handling Lithium Batteries publication AG 5 4 9 1 1 No Go to the next step Remove the old battery by unplugging the battery and opening the clip which secures the battery Install a new 1769 BA battery by plugging the battery lead into the socket ATTENTION Only install a 1769 BA battery If you install A a different battery you may damage the controller Attach the battery label Write on the battery label the date you install the battery Secure the new battery in the battery clip 0 Re install the control cassette 1 Energize the drive and the DriveLogix5730 controller B 6 Access Procedures 12 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 1769 BA battery C If the BATTERY LED remains on after you complete Step B contact your Rockwell Automation re
198. r 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 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 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 produce or enter a new tag and display the Tag Properties dialog box 4 Make sure the tag is controller scope 5 Select the Produce this tag check box Specify how many controllers can consume the tag You can produce a base alias or consumed tag 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 Then the controller requires an additional connection for each subsequent consumer 6 18 Communicating with Devices on an EtherNet IP Link Consuming a Tag A consumed tag represents data that is produced broadc
199. r Defined UserDefinedIntegerDatal 643 To DriveLogix17 User Defined UserDefinedIntegerDatal 644 To DriveLogix18 User Defined UserDefinedIntegerDatal 645 To DriveLogix19 User Defined DO AlN o UserDefinedIntegerDatal 646 To DriveLogix20 User Defined 2 8 Placing and Configuring the Drive Table 2 C Mapping for Motion Control Communication Format Controller Output Tag Element Drive Parameter Linked Parameter Controller Input Tag Element Drive 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 UserDefinedRealData 5 607 FromDriveLogix05 User Defined UserDefinedRealData 6 608 FromDriveLogix06 User Defined UserDefinedRealData 7 609 FromDriveLogix07 User Defined UserDefinedRealData 8 610 FromDriveLogix08 User Defined UserDefinedRealData 9 611 FromDriveLogix09 User Defined UserDefinedRealData 10 612 FromDriveLogix10 User Defined UserDefinedRealData 1 1 613 FromDriveLogix1 1 User Defined UserDefinedIntegerData 0 614 FromDriveLogix12 User Defined UserDefinedIntegerData 1 615 FromDriveLogix13 User Defined UserDefi
200. r per node scan Master transmit Standard polling modes only Select when the master station sends messages e between station polls default e in polling sequence Normal poll node tag Standard polling modes only An integer tag array that contains the station addresses of the slave stations Create a single dimension array of data type INT that is large enough to hold all the normal station addresses The minimum size is three elements This tag must be controller scoped The format is list 0 contains total number of stations to poll list 1 contains address of station currently being polled list 2 contains address of first slave station to poll list 3 contains address of second slave station to poll list n contains address of last slave station to poll Normal poll group size Standard polling modes only The number of stations the master station polls after polling all the stations in the priority poll array Enter 0 default to poll the entire array Priority poll node tag Standard polling modes only An integer tag array that contains the station addresses of the slave stations you need to poll more frequently Create a single dimension array of data type INT that is large enough to hold all the priority station addresses The minimum size is three elements This tag must be controller scoped The format is list 0 contains total number of stations to be polled list 1 contains address of station cur
201. r producing and consuming tags See Example 2 above 7 24 Communicating with Devices on a ControlNet Link Producing and consuming tags with a ControlNet PLC 5 controller depends on the type of data CoH SUNT g ControlNet DriveLogix5730 Controller ControlLogix Controller ControlNet PLC5 DriveLogix5730 Controller DriveLogix1 Control1 Controller DriveLogix2 tagA DINT PLC5C1 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 Then INT na Create a user defined data type that contains an array of INTs with an even number of elements such as INT 2 When you produce INTs you must produce two or more Create a produced tag and select the user defined data type you created DINT or REAL Only one DINT or REAL value Create a produced tag and select the DINT or REAL data type as appropriate More than one DINT or REAL Create a user defined data type that contains an array of DINTs or REALs as appropriate Create a produced tag and select the user defined data type you created 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
202. rData 8 645 To DriveLogix19 User Defined UserDefinedIntegerData 9 646 To DriveLogix20 User Defined For each of the communication formats drive_module O LogicCommand and drive_module I LogicStatus are provided as DINT data types In addition to these tags the control bits for each are also available as Boolean values with tag names that correspond to the control bits in the drive This gives you the option of programming the Logic Command and Status words at the Boolean level or as an integer value 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 Placing and Configuring the Drive 2 11 Inhibiting the Drive RSLogix 5000 programming software allows you to inhibit the controller s Connection 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 connection to the drive In this situation the controller can neither start or stop the drive nor read the status of the drive The drive can continue to operate based on its parameter settings and inputs To avoid potential personal injury and damage to machinery make sure this does not create unsaf
203. rcard should identify which communication driver to install 2 Specify the appropriate settings For example If you are using this device 1784 KTCx card Specify this information memory address which must match the switch setting on the card I O base address which must match the switch setting on the card ControlNet node address 1784 PCC card ControlNet node address MAC ID 1784 PCIC card ControlNet node address MAC ID Communicating with Devices on a 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 In the Controller Organizer select the I O Configuration folder Right click the selected folder and select New Module File Edit View Search Logic Communications Tools alela EVERETT Offline J E RUN E E No Forces b an i i NoEdts lp in KI ma Controller EtherNetIP_Example 2 Select the proper ControlNet Controller Tags C3 Controller Fault Handler daughtercard from the list of C3 Power Up Handler possible communication devices J E Tasks i Ej fal MainTask Click OK 4 MainProgram 3 6 Motion Groups E Ungrouped Axes Type 1788 CNC7A L Trends Data Types Description Lig User Def
204. re 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 Asiaa z q E ControlNet DriveLogix1 DriveLogix2 controllerb workstation tagA DINT tagA DINT tagB Real tagB Real Communicating with Devices on a ControlNet Link 7 21 This example shows DriveLogix1 producing tagA and consuming tagB Diets o o Decimal ee ooo S BEA Float O I 2 PowerFlex 7005 2 400 Drivel CompactBus Local 1 1788 CNC A ControlNet_Daughtercard 2 1788 CNC A Remote_ControlNet_Daughtercard fg Tag Properties tagB f Tag Properties tagA 7 22 Communicating with Devices on a ControlNet Link Example 3 DriveLogix Controller to Other Devices ControlNet Each produced tags requires one connection for the producing controller and an additional connection for each consuming controller Each consumed tag requires one connection Exa
205. rently being polled list 2 contains address of first slave station to poll list 3 contains address of second slave station to poll list n contains address of last slave station to poll Active station tag Standard polling modes only 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 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 BCC is quicker and easier to implement in a computer driver This is the default CRC the controller sends and accepts messages with a 2 byte CRC for error checking CRC is a more complete method Enable duplicate detection Select whether or not the controller should detect duplicate messages The default is duplicate detection enabled 5 10 Communicating with Devices on a Serial Link Example 3 DriveLogix Controller to a Bar Code Reader 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 t
206. rganizer select CompactBus Local icon Right click and select Properties S RSLogix 5000 quick start PowerFlex 7005 2 File Edit View Search Logic Communications Tools Wine aleja 8 Hele olf Offline I E RUN E Fd Patt No Forces gt ae as No Edits Ale ve aa o ANE ha Module Properties Controller 3 CompactBus 13 1 FEEL E Controller quick start General Connection Controller Tags A 5 C Controller Fault Handler Type CompactBus 1769 Virtual Backplane Adapter FH Power Up Handler Vendor Allen Bradley B Tasks Parent Controller E8 MainTask aah i a Local st 3 z MainProgram ame ocal lol 9 Unscheduled Programs Description r Maxi Motion Groups 70 Count FH Ungrouped Axes z EH Trends Data Types Cy User Defined Revision C Strings Predefined i Module Defined E 140 Configuration 2 PowerFlex 7005 2 400 drive_module faii ECompactBus Local P New Module Status Offline Ctrl x Ctrl C Ctrl V Delete Del Module Fault Cross Reference Ctrl E 3 6 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 n
207. ridge WE 1 1756 L63 ControlLogix5563 2 PowerFlex 7005 2 400 Drive S CompactBus Local 1 Add the remote EtherNet IP port or bridge to the local EtherNet IP port 2 Add the remote controller to the remote EtherNet IP port Producing and Consuming The DriveLogix5730 controller supports the ability to produce broadcast Data 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 This is the recommended method of communication between Logix controllers Produced and consumed tags must be controller scoped tags of DINT or REAL data type or in an array or structure Tag type Description Specify produced These are tags that the controller produced for Enabled for producing other controllers to consume How many consumers allowed consumed These are tags whose values are produced by Controller name that owns the tag that the local controller wants another controller to consume Tag name or instance that the controller wants to consume Data type of the tag to consume Update interval of how often the local controller consumes the tag 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
208. riodic task increases the elapsed time clock time between the execution of system overhead as shown below 1 ms 1 ms 1 ms 1 ms Ims periodic task p ER A ia i 1 ms 1 ms system overhead 9 ms of continuous task time 9 ms of continuous task time continuous task BE RER RER HE El 0 5 10 15 20 25 elapsed time ms 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 E 4 ms 4 ms 4 ms 4 ms 4 ms 5 10 15 20 25 system overhead elapsed time ms If you increase the time slice to 50 the system overhead interrupts the continuous task every 1 ms of continuous task time 1 ms continuous task 1 ms periodic task Soe elapsed time ms If the controller only contains a periodic task s the system overhead timeslice value has no effect System overhead runs whenever a periodic task is not running system overhead continuous task 5 10 15 20 25 elapsed time ms 1 12 What is DriveLogix5730 Understanding the Virtual The DriveLogix5730 system has a five slot virtual backplane The Backplane controller drive and other components occupy different assigned slots on the backplane Virtual Backplane Slot 0 Slot 1 Slot 2 Slot 3 Slot 4 DrvieLogix5730 Embedded PowerFlex 700S Compact I O NetLinx Controller EtherNet Option Drive Daughtercard
209. rive PowerFlex 7005 2 File Edit View Search Logic Communications Tools Window Help alela alle mi Offline fl M RUN KEA Path lt rone gt No Forces b Eo NoEds a KEE seb JE lN Favorites KBE Te EJ Controller Motion Drive Controller Tags C3 Controller Fault Handler C3 Power Up Handler S E Tasks 5 63 MainTask Eg MainProgram C3 Unscheduled Programs E Motion Groups Grouped_Axes gt axisoo XD Axis01 FH Ungrouped Axes FH Trends 5 5 Data Types ER User Defined oa Strings ery Predefined Module Defined E 1 0 Configuration 2 PowerFlex 7005 2 400 Drive Af FED CompactBus Local i fovea cut Ctrl X Copy Ctrl C E paste S Delete oe Module Fault Cross Reference Ctrl E That will launch the Module Properties Window for the drive E Module Properties Controller 2 PowerFlex 7005 2 400 1 5 General Connection Associated Axes Module Info Power Setup Type PowerFlex 7005 2 400 Drive Interface 400V Vendor Allen Bradley Parent Controller Name prive Axis Slot E4 El Comm Format Motion Control v Revision mi fs a Electronic Keying Compatible Module he Description Status Offline Cancel Amy Heb Click on the Setup tab Configuring DriveLogix Motion 4 15
210. rn 7 4 Scheduling the ControlNet Network 0 0 0 cece cece cece 7 7 Sending Messages nii Scere pee nee ee wee See ee eae es 7 9 Producing and Consuming Data 2 0 cece cece ee enna 7 14 Guidelines for Configuring Connections 0 0 0 0 0 cece eee eee eee 7 17 Example 1 DriveLogix Controller and Remote O 0 0 0 0 02 eee ee 7 18 Example 2 DriveLogix5730 Controller to DriveLogix5730 Controller 7 19 Example 3 DriveLogix Controller to Other Devices 0000000 eee 7 22 Communicating with Devices on a DeviceNet Link De energizing the Drive to Connect or Disconnect a Cable 000 8 1 Example Controlling I O Over DeviceNet 0 0 c eee eee eee nes 8 2 Chapter 9 Appendix A Appendix B Appendix C Index Communicating with Devices on a DH485 Link De energizing the Drive to Connect or Disconnect a Cable 0 004 9 1 Understanding How the DriveLogix5730 Controller Supports DH485 Communications 9 1 Configuring Your System for a DH 485 Link 0 0 eee eee eee 9 2 Planning a DH 485 Network 00 cence eee e eens 9 4 Installing a DH 485 Network 0 0 cece e eee 9 6 Browsing a DH 485 Network Remotely 0 0 cece eee eee eee 9 9 DriveLogix5730 Controller Specifications DriveLogix5730 Controller Specifications 0 0 0 eee eee eee A 1 DriveLogix5730 Environmental Specifications 2 0 0 cece eee
211. rom PLC 5 or SLC Communicating with Devices on a ControlNet Link Supported Source File Types In the DriveLogix controller select one of these data types SINT INT DINT or REAL Example source element array 1 Specify the destination file type based on the destination device PLC 5 typed read S B N or F PLC 5 word range read S B N F I O A or D SLC B or N Example source element N7 10 Supported Destination File Types Use the PLC 2 compatibility file Example destination tag 010 In the DriveLogix controller specify the destination data type based on the destination device PLC 5 SINT INT DINT or REAL SLC INT Example destination tag array_1 DriveLogix reads from PLC 2 Use the PLC 2 compatibility file Example source element 010 In the DriveLogix controller select one of these data types SINT INT DINT or REAL Example destination tag array 1 Typed read command 16 bit words in PLC 5 controller The typed commands maintain data structure and value c gt The DriveLogix5730 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 32 bit words in DriveLogix5730 controller 16 bit words in PLC 5 controller Word range read command 32 bit words in DriveLogix5730 controller 1 2 1
212. rors because the destination tag is not large enough To correct this error change the destination tag to a DINT data type MSG instructions are unscheduled The type of MSG determines whether or not it requires a connection If the MSG instruction requires a connection it opens the needed connection when it is executed You can configure the 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 CIP X X PLC 2 PLC 3 PLC 5 or SLC CIP X X FA iypes CIP with Source ID X X DH X CIP generic CIP x X block transfer read or write na X X You can connect CIP generic messages but for most applications we recommend you leave CIP generic messages unconnected The update time of local I O modules may increase when the controller is bridging messages Important Bridging over the DriveLogix5730 controller should be targeted toward applications that are not real time dependent such as RSLogix 5000 program downloads and ControlFlash updates 6 20 Communicating with Devices on an EtherNet IP Link 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
213. s messages that end with a BCC byte for error checking BCC is quicker and easier to implement in a computer driver This is the default CRC the controller sends and accepts messages with a 2 byte CRC for error checking CRC is a more complete method Enable duplicate detection Select whether or not the controller should detect duplicate messages The default is duplicate detection enabled Communicating with Devices on a Serial Link 5 7 Exam ple 2 Workstation In the following example a workstation remotely connects to a DriveLogix Remotely Connected to a controller over s serial link A modem is connected to the controller to DriveLogix Controller provide remote access TITITTITITI modem ce If you use a modem to remotely connect the controller to one workstation use RSLogix 5000 programming software to configure the serial port of the controller for the DF1 point to point full duplex protocol as in the previous example If the controller is part of a master slave serial network configure the serial port of the controller for either the DF1 master or DF1 slave protocol both half duplex 5 8 Communicating with Devices on a Serial Link Name standard communication mode Master Slave Communication Methods A master station can communicate with a slave station in two ways This method Benefi
214. s of a control system and enable them as you wire up the control system The controller lets you inhibit individual modules or groups of modules which prevents the controller from trying to communicate with these modules Inhibiting a module shuts down the connection from the controller to that module When you create an I O module it defaults to being not inhibited You can change an individual module s properties to inhibit a module 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 injury and damage to machinery make sure this does not create unsafe operation ATTENTION Inhibiting a module causes the connection to the 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 E Module Properties Local 1 1769 IA16 A 1 1 i ioj x General Connection Requested Packet Interval RPI 20 gt ms IZ Major Fa ntroller If Connection Fails While in Run Mode r Module Fault Status Offline 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 When you select to inhibit a module the controller organizer displays a yellow circle symbol over the module
215. se to a Connection Failure or Controller Mode Change The drive contains several parameters that allow you to configure the drive s response to communication loss to the controller From the drive s perspective a communication loss can come in the following two forms e The controller closes the connection for example the connection is inhibited e A general failure occurs causing the connection to time out Parameter 386 Lgx OutofRunCnfg configures the drive s response to the controller is removed from the Run Mode Parameter 387 Lgx Timeout 2 18 PDriveExecutive Placing and Configuring the Drive SLogix 5000 Projects New Drive dno lt PowerFlex 7005 2 gt 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 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 15 x EL File Edit Vi
216. sh and then click Yes After the controller is updated the status box displays Update complete Click OK To close AutoFlash software click Cancel and then click Yes Using a CompactFlash card to load firmware If you have an existing DriveLogix5730 controller that is already configured and has firmware loaded you can store the current controller user program and firmware on CompactFlash and use that card to update other controllers 1 Store the controller user program and firmware of a currently configured DriveLogix5730 controller to the CompactFlash card Make sure to select Load Image On Power up when you save to the card Remove the card and insert it into a DriveLogix5730 controller that you want to have the same firmware and controller user program When you power up the second DriveLogix5730 controller the image stored on the CompactFlash card is loaded into the controller Using CompactFlash What is DriveLogix5730 1 5 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 A ATTENTION If you configured the CompactFlash card to restore on power up and you make changes to a project su
217. should do this only if the drive is de energized 1 Turn off and lock out input power Wait five minutes 2 Verify that there is no voltage at the drive s input power terminals 3 Measure the DC bus voltage at the DC amp DC terminals on the Power Terminal Block The voltage must be zero 4 Connect or disconnect the programming or network cable 5 Turn power back on and proceed with placing and configuring the I O The DriveLogix5730 controller supports up to 2 banks of modules with a maximum of 8 modules per bank You must distribute the modules within each bank so that no more than 4 modules are on either side of the power supply Power Module E I O Modules I O Modules a ro AE J PE a e 3 2 Placing and Configuring Local I O Placing Local 10 Modules Refer to the Compact I O Selection Guide publication 1769 SGO001 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 You can split a bank right after the power supply or after any I O module Each bank must contain one power supply An end
218. slot 1 The software creates the appropriate tags using the slot number to differentiate the tags for this example module from any other module Controller Tags quick start controller Scope quick_start controlle x Show Show All Sort Tag Name Hold Last State and User Defined Safe State Not Supported A ATTENTION Risk of injury or equipment damage exists When 1769 Compact I O modules are used as local I O modules in a DriveLogix5730 system the local I O modules do not e e drive module scans z AB PF700S 2 SP BS drive_module 0 Ea SE AB PF700S 2 SP E Local 1 Cea Sk 4B 1769_DI16 1 0 F Locat1 1 Fault 2 0000_000 Binary DINT Para E 000 Binay INT E L Locat 1 1 Data 0 o Decimal BOOL Local 1 1 Data 1 o Decimal BOOL Ed Local 1 1 Data 2 0 Decimal BOOL E HLocal 1 1 Data 3 o Decimal BOOL E HE Local 1 1 Data 4 0 Decimal BOOL m Local 1 1 Data 5 o Decimal BOOL m Local 1 1 Data 6 o Decimal BOOL Local 1 1 Data 7 0 Decimal BOOL Local 1 1 Data 8 0 Decimal BOOL Local 1 1 Data 3 0 Decimal BOOL E Local 1 1 Data 10 0 Decimal BOOL Local 1 1 Data 11 0 Decimal BOOL i Local 1 1 Data 12 0 Decimal BOOL m Local 1 1 Data 13 0 Decimal BOOL Local 1 1 Data 14 0 Decimal BOOL Local 1 1 Data 1
219. ss MAC Type IP Address Hostname Description _ r Status Entries Unable to service BOOTP request from 00 00 BC 07 00 74 E of 256 Communicating with Devices on an EtherNet IP Link 6 5 6 To permanently assign this configuration to the device highlight the device and click on the Disable BOOTP DHCP button When power is recycled the device uses the configuration you assigned and not issue a BOOTP request Important If you do not select the Disable BOOTP DHCP button on a power cycles and drive resets the controller clears the current IP configuration and will again begin sending BOOTP requests FEE File Tools Help r Request History Clear History Add to Relation List Ethernet Address MAC 9 36 48 BOOTP 00 00 BC 07 00 74 9 36 47 BOOTP 00 00 BC 23 40 1F 10 91 13 210 H10 Embedded IP Address Hostname Relation List New Delete Enable BOOTP Enable DHCP i Laie i Click ENE m Disable BOOTP 00 00 BC 23 40 1F BOOTP 10 91 13 210 H10 Embe H10 Embedded DHCP r Status Entries Disable BOOTP Command successful E of 256 Other methods to assign network parameters include If you are working in these conditions Use this method for assigning network See page parameters e a BOOTP server is not available RSLinx software 6 6 e the EtherNet IP module is connected to another NetLinx network e the RSLogix 5000 project is on
220. ssary testing DriveLogix motion cause unstable and unpredictable operation To avoid potential personal injury and damage to machinery determine the proper values for system dynamics and tune the system before beginning operation ATTENTION Running the system without proper tuning can You must perform testing to determine the actual system dynamics and tune the drive In addition you must create ladder logic that uses the Logix Motion Instructions Refer to Supported Motion Commands on page 4 21 and publication 1756 RM007 Reference Manual Logix Controller Motion Instruction Set this system To avoid potential personal injury and damage to machinery detect Position Error faults by using parameter links and ladder logic ATTENTION There is no default Position Error Fault logic in Supported Motion Commands Configuring DriveLogix Motion 4 21 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 Redefine Position MCCP Motion Calculate Position Profile MAPC Motion Axis Position Cam MATC Motion Axis Time Cam Motion Event MAW Motion
221. st be zero ATTENTION Severe injury or death can result from electrical During the process of loading controller firmware you will need to connect or disconnect a programming or network cable at the controller You should do this only if the drive is de energized 1 Turn off and lock out input power Wait five minutes 2 Verify that there is no voltage at the drive s input power terminals 3 Measure the DC bus voltage at the DC amp DC terminals on the Power Terminal Block The voltage must be zero 4 Connect or disconnect the programming or network cable 5 Turn power back on and proceed with loading firmware Loading Firmware The controller ships with working firmware You may decide to upgrade the firmware To load firmware you can use e ControlFlash utility that ships with RSLogix 5000 programming software e AutoFlash that launches through RSLogix 5000 software when you download a project to a controller that does not have the current firmware e a 1784 CF64 CompactFlash card with valid memory already loaded The firmware is available with RSLogix 5000 software or you can download it from the support website 1 Go to http support rockwellautomation com 2 In the left column frame select Firmware Updates under Technical Support 3 Select the desired firmware revision The download process will require you to enter the serial number of your RSLogix 5000 programming software If
222. struction requires you to specify a target and an address within the target The number of messages that a device can support depends on the type of message and the type of device Support this many Support this many This device unconnected messages connected messages 1756 CNB or 1756 CNBR module 20 64 for a Logix5550 controller 1788 CNx daughtercard 5 32 for a DriveLogix controller with a maximum of 9 scheduled ControlNet PLC 5 controller 32 128 Important Revision 15 xx of DriveLogix firmware adds more stringent range checks when reading to or writing from tags Message packets are limited to 240 bytes This could cause some MSG instructions that worked in previous firmware revisions to not work in revision 15 xx firmware For example use a CIP Generic MSG instruction to perform a Get Attribute Single service The attribute is 4 bytes in length Assume the destination tag is an INT data type 2 bytes in length In revision 13 xx firmware the MSG instruction places the first 2 bytes of the attribute in the destination tag In revision 15 xx 7 10 Communicating with Devices on a ControlNet Link firmware the MSG instruction errors because the destination tag is not large enough To correct this error change the destination tag to a DINT data type MSG instructions are unscheduled The type of MSG determines whether or not it requires a connection If the MSG instruction requires a connection it opens the needed connect
223. sumed by PLC5C1 1 Consumed TagB from DriveLogix2 1 Consumed INT from PLC5C1 1 total connections used 12 If you configured the local I O modules as rack optimized you would only need the DIN rail connection to the I O modules reducing the above example by 3 connections 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 De energizing the Drive to Connect or Disconnect a Cable Chapter 8 Communicating with Devices on a DeviceNet Link 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 amp DC terminals on the Power Terminal Block The voltage must be zero ATTENTION Severe injury or death can result from electrical During the process of configuring DeviceNet communication you will need to connect or disconnect a programming or network cable at the controller You should do this only if the drive is de energized 1 Turn off and lock out input power Wait five minutes 2 Verify that there is no voltage at the drive s input power terminals 3 Measure the DC bus voltage at the DC amp DC terminals on the Power Terminal Block The voltage must be zero 4 Connect or disconnect the programming or network cable 5 Turn power back on and proceed with configuring Devic
224. tBus Local icon Right click and select New Module 2 Select the new module 1769 IA16 in this example fg RSLogix 5000 quick start PowerFlex 7005 2 File Edit View Search Logic Communications Tools Wine FEET al sales mme ii po Offline fl M RUN CA No Forces gt Se No Edits FE io bend Patt EJ Controller quick start Controller Tags 9 Controller Fault Handler 5 Power Up Handler 3 6 Tasks 5 63 MainTask ER MainProgram Type 17681416 Description High Speed Counter 16 Point 12 8 Point Isolated 120V AC Input 4 Channel Current Voltage Analog Input 4 Channel Input 2 Channel Output Low Resolution Analog 3 7 k C3 Unscheduled Programs 1 769 1M12 12 Point 240V AC Input 9 Motion Groups 17691016 16 Point 24V DC Input Sink Source LI Ungrouped Axes 1769 1016F 16 Point 24V DC High Speed Input L Trends 1769 1032 32 Point High Density 24V DC Input 9 Data Types 1769 106X0W4 6 Point 24V DC Sink Source Input 4 Point AC DC Relay Output L User Defined ea 1769 IR6 6 Channel RTD Direct Resistance Analog Input H Oe Strings 1769 IT6 6 Channel Thermocouple m Analog Input H C Predefined 1769 MODULE Generic 1769 Module E ER Module Defined 1769 0A16 16 Point 100V 240V AC Output xl a 1 0 Configuration Show 2 PowerFlex 7005 2 400 drive module CompactBu Vendor
225. ta 3 642 To DriveLogix16 User Defined UserDefinedIntegerData 4 643 To DriveLogix17 User Defined UserDefinedIntegerData 5 644 To DriveLogix18 User Defined UserDefinedIntegerData 6 645 To DriveLogix19 User Defined UserDefinedIntegerData 7 646 To DriveLogix20 User Defined Placing and Configuring the Drive 2 9 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 User Defined UserDefinedRealData 4 607 FromDriveLogix05 User Defined UserDefinedRealData 5 608 FromDriveLogix06 User Defined UserDefinedRealData 6 609 FromDriveLogix07 User Defined UserDefinedRealData 7 610 FromDriveLogix08 User Defined UserDefinedRealData 8 611 FromDriveLogix09 User Defined UserDefinedRealData 9 612 FromDriveLogix10 User Defined UserDefinedRealData 10 613 FromDriveLogix1 1 User Defined UserDefinedRealData 1 1 614 FromDriveLogix12 User Defined UserDefinedRealData 1 2 615 FromDriveLogix13 User Defined UserDefinedRealData 13 616 FromDriveLogix14 User
226. tarts access to the DeviceNet network 1 Communicating with Devices on a DeviceNet Link 8 9 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 J RSLogix 5000 DeviceNet_Example PowerFlex 700 File Edit View Search Logic Communications Tools VW alga 2 ele Soft Offline M RUN r No Forces Z E ok e NoEdts g e ea El si Controller DeviceNet_Example A Controller Tags C3 Controller Fault Handler C3 Power Up Handler B E Tasks aa MainTask L MainProgram CI Unscheduled Programs E Motion Groups EH Ungrouped Axes C3 Trends 5 9 Data Types ER User Defined O Strings Predefined Oy Module Defined i 2 PowerFlex CompactBus L 5 69 Cut Ctrl x Ctrl C m Ctrl 2 Select the 1788 DNBO DeviceNet Scanner from the list of possible communication devices Click OK x Type 1788 DNBO A Description 1788 ControlNet Bridge Coax Media 1788 ControlNet Bridge Redundant Coax Media 1788 ControlNet Bridge Fiber Media 1788 ControlNet Bridge Redundant Fiber Media 1 788 CNCR A 1 788 CNF A 1 788 CNFR A 1788 DNBO 4 evic e er 1788 10 100 Mbps Ethernet Bridge Twisted Pair Media 1 788 EWEB A 1788 10 100 Mbps Ethernet
227. te terminal units RTUs the message after waiting a user configured period of time The waiting period gives the slave station time to formulate a reply and prepare the reply for transmission After all of the messages in the master s message out queue are transmitted the slave to slave queue is checked for messages to send This field Station address Configuring a DF1 Slave Station Description 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 Slave poll timeout Specifies the amount of time the slave station waits to be polled by a master before indicating a fault Enter a value 0 32767 Limits are defined in 20ms intervals The default is 3000 60 000ms EOT suppression Select whether or not to suppress sending EOT packets in response to a poll The default is not to suppress sending EOT packets 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 BCC is quicker and easier to implement in a computer driver This is the default CRC the controller s
228. tercard Installation 1788 IN054 daughtercard Instructions Information on installing an DeviceNet communications DeviceNet Communications Daughtercard Installation 1788 IN053 daughtercard Instructions Information on installing 1769 SDN DeviceNet Scanner Compact I O 1769 SDN DeviceNet Scanner Module 1769 INO60 Module Information on using 1769 SDN DeviceNet Scanner Module Compact I O 1769 SDN DeviceNet Scanner Module 1769 UMO009 Information on converting from Phase PowerFlex 700S and PowerFlex 700S Conversion Guide 20D AT001 DriveLogix5720 to Phase II PowerFlex 700S and Phase to Phase II Control DriveLogix5730 Information on the basic installation of PowerFlex 700S drives Quick Start PowerFlex 700S High Performance AC Drive 20D QS001 and DriveLogix5730 controllers Contacting Tech Support Title For Automation and Control Technical Support Online at Rockwell Automation Technical Support _ http support rockwellautomation com knowledgebase Controller Firmware Revision General Precautions Overview p 3 This revision on the DriveLogix 5730 User Manual corresponds to the following e Version 15 04 and later controller firmware e Version 15 xx and later RSLogix 5000 programming software e Version 3 02 and later DriveExecutive programming software Class 1 LED Product A LN gt gt ATTENTION Hazard of permanent eye damage exists when using optical transmission equipment
229. that supports every Logix controller e Direct connection to host PowerFlex 700S drive e Compact I O modules that provide a compact DIN rail or panel mounted I O system e Embedded EtherNet IP option provides communication over an EtherNet IP network e 1788 communication daughtercard that provides communication over a standards based ControlNet EtherNet IP DeviceNet or third party network The newer DriveLogix5730 controller offers significant performance and capacity improvements over the DriveLogix5720 controller It offers e increased user memory up to 1 5 Mbytes e CompactFlash for non volatile memory storage e extended I O capacity up to 16 I O modules e integrated EtherNet IP support including control of distributed I O e Run Rem Prog switch Remote D Work Station EtherNet IP ao oO ae DriveLogix with Local I O ControlLogix F Controller ee ControlNet tle Li PanelView 1 2 What is DriveLogix5730 Loading Controller Firmware De energizing the Drive to Connect or Disconnect a 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 amp DC terminals on the Power Terminal Block The voltage mu
230. tive button to launch DriveExecutive Lite E Module Properties Controller 2 PowerFlex 7005 2 400 1 5 General Connection Associated Axes Module Info Power 5 Drive File New Drive dno Browse Found In lt File not found gt Launch DriveExecutive View and edit the parameter and link data associated with this drive Status Offline Cancel Apply Help 9 When asked to create a new DriveExecutive Lite file select yes File does not exist Create c RSLogix 5000 Projects New Drive dno DriveExecutive will then launch and open the newly created file owerFlex 7005 2 Placing and Configuring the Drive Undefined Node SB 0 PowerFlex 7005 2 Linear List C3 Monitor Ca Motor Control C3 Dynamic Control CQ Speed Control C3 Torque Control C3 Process Control E3 Position Control C3 Speed Posit Fdbk CA utility 3 Communication CA Inputs amp Outputs 23 User Functions Ca Default Custom For Help press F1 Linear List _ Parameter Na value UnifInternal Source Comment Default Motor NP Volts Motor NP FLA Motor NP Hertz Motor NP RPM Motor NP Power Mtr NP Pwr Units Motor Poles Total Inertia Speed Ref 1 Spd Ref Divide Speed Ref 2 Spd Ref2 Multi Preset Speed 1 Preset Speed 2 Preset Speed 3 Preset Speed 4 Preset Speed 5 Preset Speed 6 Preset Speed 7 Speed Trim 1 Speed Trim 2 Speed Trim 3 SpdTrim 3 Scale STrim2 Filt Gain S
231. to In the following example one EtherNet IP DriveLogix5730 controller Controller communicates with another EtherNet IP DriveLogix5730 controller over 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 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 EtherNet IP DriveLogix1 DriveLogix2 controllerb workstation tagA DINT tagA DINT tagB Real tagB Real Communicating with Devices on an EtherNet IP Link
232. to send commands to the scanner Local 1 1 H Local 1 0 Local 1 0 CommandReaister i Local t D CommandRegister Run Local 0 CommandRegister Fault Local 1 0 CommandRegister DisableN etwork Ie be H Local 1 0 CommandRegister HaltScanner Al L Locat 1 0 CommandR egister Reset Local 1 0 Data 8 12 Communicating with Devices on a 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 Local 1 0 CommandR egister Run De energizing the Drive to Connect or Disconnect a Cable Understanding How the DriveLogix5730 Controller Supports DH485 Communications Chapter 9 Communicating with Devices on a DH485 Link 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 amp DC terminals on the Power Terminal Block The voltage must be zero N ATTENTION Severe injury or death can result from electrical During the process of configuring DH485 communication you will need to connect or disconnect a programming or network cable at the controller You should do this only if the drive is de energized 1 Turn off and lock out input power Wait five minutes 2 Verify that there is no voltage at the drive s input power terminals 3 Measure the DC bus voltage at the DC amp DC termina
233. ts Initiates polling packets to slave stations This communication method is most often used for point to multipoint according to their position in the polling array s configurations Polling packets are formed based on the contents This method provides these capabilities of the normal poll array and the priority poll array slave stations can send messages to the master station polled report by exception e slave stations can send messages to each other via the master e master maintains an active station array The poll array resides in a user designated data file You can configure the master e to send messages during its turn in the poll array or e for between station polls master transmits any message that it needs to send before polling the next slave station In either case configure the master to receive multiple messages or a single message per scan from each slave station message based communication mode initiates communication to slave stations using If your application uses satellite transmission or public only user programmed message MSG switched telephone network transmission consider choosing instructions message based communication Communication to a slave station Each request for data from a slave station must can be initiated on an as needed basis be programmed via a MSG instruction Also choose this method if you need to communicate with The master polls the slave station for a reply to non intelligent remo
234. umed Tag A produced or consumed tag can be as large as 488 bytes but it must also fit within the bandwidth of the ControlNet network e As the number of connections over a ControlNet network increases several connections including produced or consumed tags may need to share a network update e Since a ControlNet network can only pass 500 bytes in one update the data of each connection must be less than 488 bytes to fit into the update If a produced or consumed tag is too large for your ControlNet network make one or more of the following adjustments e Reduce the Network Update Time NUT At a faster NUT less connections have to share an update slot e Increase the Requested Packet Interval RPI of all connections At a higher RPI connections can take turns sending data during an update slot e 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 Then select this communication format for non diagnostic digital I O modules the remote communication module yes rack optimization no none The Rack Optimization format uses an additional 8 bytes for each slot in its chassis Analog modules or modules that are sending or getting diagnostic fuse or timestamp data require direct connections and cannot take advantage of the rack optimized form Selecting None frees up the 8 bytes per slot for other uses such
235. ut modules and digital input modules use Input Data INT Slot slot placement of the module on the CompactBus Connection Parameters connection information unique to the module Input The documentation for module should list the assembly instance and size numbers for the input Output output and configuration parameters Configuration 1 2 In the Controller Organizer double Edit the tags for the module so that 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 click on Controller Tags the tags contain the appropriate configuration J RSLogix 5000 quick start PowerFlex 7005 2 File Edit View Search Logic Communications Too gt Offline J M RUN N E No Forces b fe im NoEdts A i 4 Bs EJ Controller quick start ller Tags ler Fault Handler 5 Power Up Handler EJ Tasks E3 Control Eid MainTask 4 MainProgram 9 Unscheduled Programs 5 Motion Groups LI Ungrouped Axes C3 Trends EF Data Types a User Defined Ca Strings CR Predefined Eih Module Defined E 140 Configuration
236. wind A Function describes the function or signal Function examples SpdRef Speed Reference FaultState Status of a fault Suffix identifies the units of the signal or control status Suffix examples Rpm Rotations per Minute Ok status OK Off contact Off Full tag examples Sct2_SpdRef_Fpm Speed Reference in feet per minute on Section 2 Fan5_FaultState_OK Status of fault where 1 OK on Fan 5 TIP Add descriptions for each tag when creating the tag 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 e Improves program portability over processors and through upgrades to DriveLogix PowerFlex 700S and RSLogix 5000 firmware e Allows real names to be applied to the User Defined tags of the static assembly e Allows new functions of DriveLogix and the PowerFlex 700S to be clearly named in the program even if RSLogix 5000 has not been updated e Allows long tag names in RSLogix 5000 to be shortened for easier program viewing e Allows tags to be named using the above naming convention to identify machine section association Apply aliases to all external connections including the PowerFlex 700S Communication Format and I O All defined bits shoul
237. work Parameters Media Configuration General Network Update Time ms Max Scheduled Address Max Unscheduled Address E Only defaut Media Redundancy Network Name m Pending m y 2x A Edit the parameters as desired Click Apply Click OK coe tow e 5 In the File menu select Save ControlNet RSNetWorx for ControlNet a E eea ea 3 5 Current Pending BL Save asi 5 00 5 00 Avg Scheduled i Generate Report 573610 362253 Peak Scheduled Print Setup a Print Preview E print Ctrl P Recent File PowerFlex 700S 2 400v Exit bject Communication Adapter ControlNet to SCANport DC Drive No Drive Object DPI to ControlNet Liman Machina Takaefacn Communicating with Devices on a ControlNet Link 7 9 6 Enter a name and path for the network configuration SS 2x Savein JNewoks EE Ee File name ControlNet xc Save as type Contro et Files xc 7 Cancel A Save Configuration 2 x Either of the following choices will save the updated schedule ox to the file and to the online network if you are online a Cancel E Help c 7 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 in
238. xl Gontinu F IT Edits En ee POs ale Enable Edits Tocreate at Cancel Edits al E z Upload from Network p Download to Network Hardware Download Minimum to Network Controle Keeper Status 5 Categ Scanner Signature Status AC AC Properties Communication Adapter ControlNet RSNet Worx for ControlNet 2 Survey the network Enable Edits Eile Edit View Network Device Diagnostics Tools Help Ae OS Belle ale FEE Edits Enabled Network Update Time ms Network Usag kt Unscheduled Bytes Per Sec Pending Pending Current Pending Current Optimized Edits Merged Edits 5 00 15 00 Avg Scheduled Band 0 26 0 34 0 34 573610 466141 Peak Scheduled Band 1 06 1 37 1 37 Hardware ControlNet Category AC Drive DPI to ControlNet vendor 3 In the Network menu select Properties AC Drive No Drive Object Communication Adapter ControlNet to SCANport DC Drive No Drive Object Human Machine Interface Programmable Logic Controller Rockwell Automation miscellan Rockwell Automation Allen Br Rockwell Automation Reliancq PowerFlex 1784 PCIC PowerFlex 7008 2 400V 7008 2 400 1 Flex 8 slot chassis

20D-UM003 - Rockwell Automation

Contents

Download Pdf Manuals

Related Search

Related Contents