Home

ControlLogix Controllers

1. x ria CET f 1769 L35E CompactLogix with 1769 SDN Module H L EE IDEE b EtherNet IP Network m Ii FlexLogix with 1788 DNBO Daughtercard Workstation ControlLogix Controller with 1756 ENBT and 1756 DNB Modules The ControlLogix controller in this example uses these connections Example Connection Types Connection Type Device Connections Total Quantity per Device Connections Controller to local 1 0 modules 4 1 1 Controller to 1756 ENBT module 0 0 Controller to 1756 DNB module 2 2 Controller to RSLogix 5000 programming software 1 1 Message to CompactLogix controller 2 1 2 Produced tag 1 1 Consumed by FlexLogix controller 1 1 Total 8 56 Publication 1756 UM001H EN P July 2008 Chapter 5 Introduction Select 1 0 Modules Place Local 1 0 Modules Publication 1756 UMO001H EN P July 2008 Place Configure and Monitor 1 0 Modules This chapter explains how to place configure and monitor I O modules Topic Page Select I O Modules 57 Place Local 1 0 Modules 57 Configure I O 59 Configure Distributed I O on an EtherNet IP Networ
2. HART network 1 0 Platform Produce consume interlock data between controllers i DMA o e j i EtherNet IP network a ControlLogix Controller ControlNet network d ais Control Network Other Logix5000 Controller Send and receive messages to and from other devices This includes access to the controller via RSLogix 5000 programming software EtherNet IP network ControlNet network DeviceNet to devices only network serial network Other Remote DH network Devices DH 485 network Publication 1756 UMO001H EN P July 2008 21 Chapter3 Communicate over Networks Topic Page EtherNet IP Network Communication 22 ControlNet Network Communication 25 DeviceNet Network Communication 28 Serial Network Communication 31 DH 485 Network Communication 41 DH Network Communication 45 Universal Remote I O Communication 46 Foundation Fieldbus 49 HART Highway Addressable Remote Transducer Protocol 50 EtherN et IP Network The EtherNet IP network offers a full suite of control configuration and Communication data collection services by layering the Common Industrial Protocol CIP over the standard Internet protocols such as TCP IP and UDP This combination of well accepted standards provides the capability required to both sup
3. Identical Pair of J ControlLogix Chassis that E ean oo Control Your Machine or ontro Net Nodes Process ji o tat 3 l Computer That Is Connected to the Network Access Port of a Remote Node Redundancy requires no additional programming and is transparent to any devices connected over an EtherNet IP or ControlNet network It uses 1757 SRM modules to maintain communication between the pair of redundant chassis Depending on how you organize your RSLogix 5000 project outputs may or may not experience a change in state bump during a switchover During the switchover outputs that are controlled by the highest ptiority task will experience a bumpless switchover For example outputs will not revert to a previous state Outputs in lower priority tasks may experience a change of state The switchover time of a redundant system depends on the type of failure and the network update time NUT of the ControlNet network For a NUT of 10 ms the switchover time is approximately 80 220 ms 116 Publication 1756 UM001H EN P July 2008 Configure Redundancy Chapter 9 Build a Redundant System To build a typical redundant system perform this procedure 1 2 Start with any ControlLogix chassis Add a 1756 L55 1756 L61 1756 L62 1756 L63 1756 L64 or 1756 L65 controller Add one or more ControlNet 1756 CNB 1756 CNBR or EtherNet IP 1756 ENBT communication
4. Controller n Controller E u un U qd DH Network DH Network H Gi i EL Lm BEBE E LJ famme Glee J DE Z v Z gh Ex e PLC 5 Processor SLC 500 Controller RSView Station PLC 5 Controller SLC 500 Controller RSView Station Publication 1756 UM001H EN P July 2008 45 Chapter3 Communicate over Networks Universal Remote 1 0 Communication 46 Communicate over a DH Network For the controller to communicate to a workstation or other device over a DH network use RSLinx software to specify a unique link ID for each ControlLogix backplane and additional network in the communication path configure the routing table for the 1756 DHRIO module The 1756 DHRIO module can route a message through up to four communication networks and three chassis This limit applies only to the routing of a message and not to the total number of networks or chassis in a system Additional Resources For additional information consult the ControlLogix Data Highway Plus Universal Remote I O Module User Manual publication 1756 UM514 For universal remote I O communication use a 1756 DHRIO module Functions Required Module Establish connections between controllers and I O adapters 1756 DHRIO Send data regularly Distribute control so that each controller has its own 0 Communicate with a supervisory controller Use an RIO scanner 1757 ABRIO Communicate with as many as 32
5. Workstation Controller mH 1 CD Li CD 2 RDX 2 RDX 3 TXD 3 TXD 4 DTR 4 DTR COMMON COMMON 6 DSR 6 DSR pu 7 RTS 7 RTS 8 CTS 8 CTS 9 9 Attach the shield to both connectors 2 Connect the cable to the controller and to your workstation m o NS S CES EEN WS MEN sea MESA EAN EAN gN Y NEN EM SERM EE CP3 Cable zN EN hJ 16 Publication 1756 UM001H EN P July 2008 Directly Connect to the Controller via the Serial Port Chapter 2 Configure the Serial Driver Publication 1756 UMO001H EN P July 2008 To configure the driver perform this procedure Configure Drivers X RSLinx Professional File Edit view Menm e Station DDE OPC Security 5 al g n Configure Shortcuts m The Configure Drivers dialog appears Configure Drivers r Available Driver Types RS 232 DF1 devices R5 232 DF1 devices Ethernet devices Ethemet IP Driver 1784 KT KTX D PK TX D PCMK for DH DH 485 devices 1784 KTC X for ControlNet devices DF1 Polling Master Driver 1784 PCC for ControlNet devices 1784 PCIC S for ControlNet devices 1747 PIC AIC Driver DF1 Slave Driver 5 8 SD SD2 for DH devices Virtual Backplane SoftLogix58xx DeviceNet Drivers 1784 PCD PCIDS 1770 KFD SDNPT drivers PLC 5 DH Emulator driver SLC 500 DH485 Emulator driver SoftLogix5 driver Remote Devices
6. Motor Starter Cluster Input output Lem Indicator Devices PowerFlex Lights ac Drive Publication 1756 UMO001H EN P July 2008 Bar Code Scanner 29 Chapter 3 30 Communicate over Networks Connections over DeviceNet The ControlLogix controller requires two connections for each 1756 DNB module One connection is for module status and configuration The other connection is a rack optimized connection for the device data The 1756 DNB module has fixed sections of memory for the input and output data of the DeviceNet devices on the network Each device on your network requires either some input or output memory of the scanner Some devices both send and receive data so they need both input and output memory The 1756 DNB module supports up to 124 DINTS of input data 123 DINTS of output data Additional Resources Por more information consult these publications DeviceNet Modules in Logix5000 Control Systems User Manual publication DNET UM004 Logix5000 Controllers Design Considerations Reference Manual publication 1756 RM094 Publication 1756 UM001H EN P July 2008 Communicate over Networks Chapter 3 Serial Network The ControlLogix controller has one built in RS 232 port Communication i Functions Required Communicates between a controller and other Built in serial port Mode DFI point to point DF1 compatible devices using
7. 133 Chapter 12 Maintain the Battery Notes 134 Publication 1756 UM001H EN P July 2008 Introduction Condition Off Appendix A Status Indicators This appendix explains the LED indicators for ControlLogix controllers Topic Page RUN LED Indicator 135 1 0 LED Indicator 135 FORCE LED Indicator 136 RS232 LED Indicator 136 BAT LED Indicator 136 OK LED Indicator 137 RUN LED Indicator The controller is in Program or Test mode Change the controller mode Solid green The controller is in Run mode 1 0 LED Indicator Off Either there are no devices in the 1 0 Add the required devices to the 1 0 configuration of the configuration of the controller controller The controller does not contain a project Download the project to the controller controller memory is empty Solid green The controller is communicating with all the None devices in its I O configuration Flashing green One or more devices in the 1 0 configuration of the controller are not responding Go online with RSLogix 5000 programming software and check the 1 0 configuration of the controller Flashing red The chassis is bad Publication 1756 UMO001H EN P July 2008 Replace the chassis 135 Appendix A X Status Indicators FORCE LED Indicator Color Description Recommended Action Off No tags contain I O force values None 1 0 forces are inactive disabled Solid amber
8. The DH 485 protocol uses RS 485 half duplex as its physical interface RS 485 is a definition of electrical characteristics not a protocol You can configure the RS 232 port of the ControlLogix controller to act as a DH 485 interface By using a 1761 NET AIC converter and the appropriate RS 232 cable 1756 CP3 or 1747 CP3 a ControlLogix controller can send and receive data on a DH 485 network 41 Chapter 3 42 Communicate over Networks ControlLogix DH 485 Network Communication Overview ControlLogix Controller Connection from ControlLogix Controller to Port 1 or Port 2 1761 NET AIC Converter 1747 AlC Programmable DH 485 Network Controller Isolated Link Coupler SLC 5 03 Controller On the DH 485 netwotk the ControlLogix controller can send and receive messages to and from other controllers A DH 485 network consists of multiple cable segments Limit the total length of all the segments to 1219 m 4000 ft For the controller to operate on a DH 485 network you need a 1761 NET AIC interface converter for each controller you want to put on the DH 485 netwotk You can have two controllers for each 1761 NET AIC converter but you need a separate cable for each controller 1 Connect the serial port of the controller to either port 1 or port 2 of the 1761 NET AIC converter 2 Use the RS 485 port to connect the converter to the DH 485 network Publication 1756 UM001
9. Additional Resources For more information consult Data Highway Data Highway Plus Data Highway II Data Highway 485 Cable Installation Manual publication 1770 6 2 2 For DH network communication use a 1756 DHRIO module to exchange DH Network g information between Communication PLC controllers and SLC controllers ControlLogix controllers and PLC or SLC controllers ControlLogix controllers Functions Required Module Share data with program maintenance on a plantwide and 1756 DHRIO cell level basis Send data regularly Transfer information between controllers You can connect a maximum of 32 stations to a single DH link Channel A supports 57 6 Kbps 115 2 Kbps and 230 4 Kbps Channel B supports 57 6 Kbps and 115 2 Kbps ControlLogix DH Network Communication Overview Data Collection and r Workstation J Recipe Management LJ Ss gt EtherNet IP Network 8 8 8X 8 Im o rss T o pee H aH ControlLogix Ham ControlLogix H
10. Introduction SIL 2 Overview Publication 1756 UMO001H EN P July 2008 SIL 2 Certification This chapter explains how ControlLogix system components are type approved and certified for use in SIL 2 applications according to IEC 61508 and AK4 applications in line with DIN V19250 SIL requirements are based on the standards current at the time of certification Topic Page SIL 2 Overview 121 SIL 2 Application 122 IMPORTANT For a list of ControlLogix system components that meet SIL 2 requirements see Using ControlLogix in Sil 2 Applications Reference Manual publication 1765 RM001 A Safety Integration Level SIL is a numeric designator assigned to a safety system that indicates that system s ability to perform its safety function The SIL 2 TYPE certification of ControlLogix products by TUV an internationally recognized and accredited test laboratory certification center assures the suitability of ControlLogix products for use in up to a SIL 2 safety application TUV certification is based primarily on compliance with IEC 61508 Functional Safety of Electrical Electronic Programmable Electronic Safety Related Systems requirements It also includes a number of application independent standards DIN V 19250 and VDE 0801 application dependent standards prEN 50156 for ESD applications DIN EN 54 for fire and gas application and environmental and electrical safety standards IEC 61131 2 EN 50178 EN 50081 2 and EN 61000 2 2000
11. SERCOS Irieafecee Iru Mudule infu Backplane Dota Mate Cycle Time Transmit Power Transition To Phase f4 zl Status Offline 2 Click the SERCOS Interface tab 3 From the Data Rate pull down menu choose Auto Detect 99 Chapter 8 Develop Motion Applications 4 From the Cycle Time pull down menu choose the cycle time Baud Rate Number of Drives Type of Drive Cycle Time of Drive on Ring 4 MB 10r2 Kinetix 6000 0 5 ms 3or4 1 ms 5 8 2 ms 9 16 Not possible You must have 2 motion modules 1 4 Not Kinetix 6000 1 ms 5 8 2 ms 9 16 Not possible You must have 2 motion modules 8 MB 1 4 Kinetix 6000 0 5 ms 5 8 1 ms 9 16 2 ms 1 8 Not Kinetix 6000 1 ms 9 16 2 ms 5 Click OK 100 Publication 1756 UM001H EN P July 2008 Develop Motion Applications Chapter 8 Add the Motion Group You can add a motion group to set up the motion planner Motion Planner Part of the controller that takes care of position and velocity information for your axes Coarse Update Period How often the motion planner runs When the motion planner runs it interrupts all other tasks regardless of their priority Motion Planner Scans of your code System overhead and so on 0 ms 10 ms 20 ms 30 ms 40 ms In this example the coarse update period 10 ms Every 10 ms the controller stops scanni
12. You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system Connections are allocations of resources that provide more reliable communication between devices compared to unconnected messages ControlNet Connections Connection Definition Scheduled A scheduled connection is unique to ControlNet communication A scheduled connection lets you send and receive data repeatedly at a predetermined interval which is the requested packet interval RPI For example a connection to an 1 0 unique toa module is a scheduled connection because you repeatedly receive data from the module at a specified interval Other ControlNet scheduled connections include connections to network communication devices produced consumed tags On a ControlNet network you must use RSNetWorx for ControlNet software to enable all scheduled connections and establish a network update time NUT Scheduling a connection reserves network bandwidth to specifically handle the connection 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 you need to Unscheduled connections use the remainder of network bandwidth after scheduled connections are allocated Publication 1756 UMO001H EN P Ju
13. 1756 UM058 ControlLogix Analog I O Modules User Manual publication 1756 UM009 Publication 1756 UM001H EN P July 2008 Place Configure and Monitor 0 Modules Chapter 5 Configure 1 0 Configuration Option Requested Packet Interval RPI To communicate with an I O module in your system add the module to the I O Configuration folder of the controller in RSLogix 5000 programming software Addition of 1 0 Modules Motion Groups 3 Ungrouped Axes E Trends Data Types Cj User Defined Cg Strings E Predefined Cg Module Defined Add I O modules to the gt ameme 1756 Backplane 1756 410 1756 backplane fa 0 1756 L61 dnet_example When you add a module you also define a specific configuration for the module While the configuration options vary from module to module there are some common options that you typically configure Configuration Options Description The RPI specifies the period at which data updates over a connection For example an input module sends data to a controller at the RPI that you assign to the module Typically you configure an RPI in milliseconds ms The range is 0 2 750 ms f a ControlNet network connects the devices the RPI reserves a slot in the stream of data flowing across the ControlNet network The timing of this slot may not coincide with the exact value of the RPI but the control system guarantees that the data transfers at least
14. Norvolatie Memory Mem General Serial Pot System Protocol User Protocol Mape Fouts Minor Fouts Date Time Error Detechon Protocet DFI Redo Modem v BC C CRC Station Addins o Enable Store and Forward Publication 1756 UMO001H EN P July 2008 35 Chapter3 Communicate over Networks Setting Station Address 3 From the Protocol pull down menu choose DF1 Radio Modem 4 Specify DF1 Radio Modem system protocol settings Description Specifies the node address of the controller on the serial network Select a number 1 254 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 Error Detection Click one of the radio buttons to specify the error detection scheme used for all messages BCC the processor sends and accepts messages that end with a BCC byte CRC the processor sends and accepts messages with a 2 byte CRC Enable Store and Forward 36 Check the Enable Store and Forward check box if you want to enable the store and forward functionality When enabled the destination address of any received message is compared to the Store and Forward tag table If there is a match the message is then forwarded re broadcasted out the port From the Store and Forward Tag pull down menu choose an integ
15. Tone Each AGIS Cere rie ioo aUbi n es d n aie neges 110 Additional ReSOUEGeS ves xd xoc iR EA C ade Ad 111 Obtain Axis InfosmidltOD oig capelle cs o d x ea s ata Red 112 Proeram MouotCODtTOL eio oer ated gure re eO roce b e 113 Additional Resources s 22a stes Dee Er Ue ol cas s dans 114 7 Table of Contents Configure Redundancy SIL 2 Certification Maintain Nonvolatile Memory Maintain the Battery Status Indicators Index Chapter 9 Iibvoductiotie cx Vu e doo Rt e od p A AE RUE RUE d Rd ke 115 Additonal Resources b 63d er vica wor Re E CP ph acera Ried 115 ControlLogix Redundancy Overview oos Ce oes 115 Build a Redundant Systetiio3 2 4d be van de A OG dde S 117 System GonsiderattOBset ec Pa bad er d DAL de apes iis 118 ControlNet Considerations in Redundant Systems 118 EtherNet IP Considerations in Redundant Systems 119 IP Address Swapping ssc side t RR a ORCI OR 119 Redundancy and Scan Time pi dai oko xe OHPATP R Ce RS 119 Minimum System Requirements eeu eed pet d eee 120 Chapter 10 TIitvod dc Hoe arta e lod Re nda EU A RU o edat aS 121 SLE 2 OVETVIEW tts aee Latest o ra te LUC eb ol See 121 SIE 2 PAP CAMO Arak se misaine act rtm dedu ote besa hea ORs 122 Chapter 11 ETO CTO s oe mado ae oe ros rti es pacta a ll lake 123 Choose a Controller That Has Nonvolatile Memory 124 Prevent a Major Fault During a Load sociis tete 124 Use a CompactFlash Reader vie choir eset hae
16. s Contr J New Module 8c Copy Ctrl C Offline Cross Reference Ctri E Properties Alt Enter Ll The Module Properties dialog appears E Module Properties Local 1 1756 CNB D 5 1 General Connection RSNetworx Module Info Backplane i Type 1756 CNB D 1756 ControlNet Bridge Change Type Vendor Allen Bradley Name LocalCNB Node 5 ala Description Slot Revision 5 wlell ES Electronic Keying Compatible Keying Status Offline Cancel Help 2 Reconfigure the 1 O module 3 Click OK 68 Publication 1756 UM001H EN P July 2008 Place Configure and Monitor I O Modules Chapter 5 Reconfigure an I O Module via a MSG Instruction Use a MSG instruction of type Module Reconfigure to send new configuration information to an I O module During the reconfiguration input modules continue to send input data to the controller output modules continue to control their output devices To reconfigure an I O module perform this procedure 1 Set the required member of the configuration tag of the module to the new value 2 Send a Module Reconfigure message to the module EXAMPLE Reconfigure an 1 0 module When reconfigure 5 is on the MOV instruction sets the high alarm to 60 for the local module in slot 4 The Module Reconfigure message then sends the new alarm value to the module The ONS instruction prevents the rung from sending multiple
17. which frees up that connection for other uses 53 Chapter4 Manage Controller Communication Additional Resources For additional information consult these publications Logix5000 Controllers General Instructions Reference Manual publication 1756 RM003 Logix5000 Controllers Common Procedures Programming Manual publication 1756 PM001 Calculate Connection Use The total connection requirements of a ControlLogix system include both local and remote connections Local Connections Local Connection Type Device Connections Total Quantity per Device Connections Local I O module always a direct connection 1 1756 M16SE 1756 MO08SE 1756 MO2AE servo module 3 1756 CNB 1756 CNBR ControlNet communication module 0 1756 ENBT EtherNet IP communication module 0 1756 EWEB EtherNet IP web server module 0 1756 DNET DeviceNet communication module 2 1756 DHRIO DH Universal remote I O communication module 1 Total 54 Publication 1756 UM001H EN P July 2008 Manage Controller Communication Chapter 4 The number of connections the module itself supports determines how many remote connections the controller can access through that module Remote Connections Remote Connection Type Device Connections Total Quantity per Device Connections Remote ControlNet communication module 1 0 configured as direct connection none 0 or 1 0 configured as rack optimized connection 1 Remote 1 0 module over a Contr
18. 10 code 10 Check the BAT LED Indicator To check the BAT LED indicator perform this procedure 1 Turn on the chassis power BAT LED gt BAT 2 ok 132 RUN Vo FORCE CO CO RS232 RUN REM PROG Publication 1756 UM001H EN P July 2008 Store Batteries Publication 1756 UMO001H EN P July 2008 Maintain the Battery Chapter 12 Is the BAT LED off If Then Yes The battery module is correctly installed No Go to step 3 Check that the battery module is correctly connected to the controller Check that the battery assembly is correctly connected to the battery module Ifthe BAT LED remains on install another battery assembly catalog number 1756 BATA If the BAT LED remains on after you complete step 5 contact your Rockwell Automation representative or local distributor ATTENTION Follow these general rules to store your batteries Store batteries in a cool dry environment We recommend A 25 C 77 F with 40 60 relative humidity You may store batteries for up to 30 days in temperatures from 45 85 C 49 185 F such as during transportation To avoid leakage or other hazards do not store batteries above 60 C 140 F for more than 30 days Additional Resources For detailed guidelines on how to store batteries see Guidelines for Handling Lithium Batteries publication AG 5 4 which comes with the battery
19. 1756 UM523 ControlLogix Redundancy Redundancy provides for higher system availability by switching control to a Overview secondary controller chassis if anything in the primary controller chassis fails The redundant system switches from primary to secondary due to power loss to primary chassis hardware or firmware failure of any module in the primary chassis a major fault in the user program on the primary controller disconnection of a ControlNet tap or ControlNet cable to a 1756 CNB module in the primary chassis disconnection of an Ethernet patch cable from a 1756 ENBT or 1756 EWEB module in the primary chassis removal of any module in the primary chassis a uset command that causes a switchover Publication 1756 UMO001H EN P July 2008 115 Chapter9 Configure Redundancy ControlLogix Redundancy System Overview Network 1 EtherNet IP or ControlNet network for HMI Communication Network 2 ControlNet Network for I 0 Communication
20. Assigned Add gt lt Remove Cancel Finish Help 6 Click Next 102 Publication 1756 UM001H EN P July 2008 Develop Motion Applications Chapter 8 The Motion Group Wizard Attributes dialog appears Motion Group Wizard My_Motion_Group Attribute Coarse Update Period ms in 0 5 increments Auto Tag Update Enabled IM General Fault Type Non Major Fault v Scan Times elapsed time Max us Last us Cancel Finish Help 7 In the Coarse Update Period box enter the intervals at which you want to run your motion planner 8 Click Finish Publication 1756 UMO001H EN P July 2008 103 Chapter 8 Develop Motion Applications Add Your Axes To add an axis for each of your drives perform this procedure 1 Decide which data type to use Motion Module Data Type 1756 MO3SE AXIS_SERVO_DRIVE 1756 M08SE 1756 M16SE 1756 L60MO3SE 1756 MO8SEG AXIS_GENERIC_DRIVE 2 In Motion Groups within RSLogix 5000 programming software right click My Motion Group and select New Axis and then the type of axis you want to add SERCOS Interface Analog S Motion Groups C3 Ungrouped A New Axis AXIS CONSUMED 73 Add On Instructii New Coordinate System XIS SERVO 3 Data Types CUN S AU AXIS SERVO DRIVE Defi onitor Group Tag amp Gi User Defined AXIS GENERIC x Strings Cg Add On Defiy Fault Help AXIS GENERIC DRIVE E Predefined M jp Fault AXIS
21. Connection Nt 4 Modem A Jl Modem Modem To configure the controller for DF1 communication perform this procedure 1 In the Controller Organizer of RSLogix 5000 programming software right click your controller and select Properties O BJ 7 1756 PLS E Properties N Alt Enter 32 Publication 1756 UM001H EN P July 2008 Communicate over Networks Chapter 3 2 3 4 5 The Controller Properties dialog appears fa Controller Properties Pl SSampleProject Date Time Advanced SFC Execution Fie Redundancy Nonvolatie Memory General Seiad Port Mode Baud Rate Data Bits z Ponty lone Stop Bits Control Line 4 ATS Send Delay RTS Off Delay DCD Weit Delay System 7 nh No Handshake System Protocol User Protocol Mayor Faults Minor Faults Jeseromevuuu Way d x20 ms x20 ma fd sec Cancel oK Click the Serial Port tab From the Mode pull down menu choose System Specify DF1 communication settings Click the System Protocol tab PLSSampleProject f Controller Properties Date Time Advanced General Sena Port Protocol Stalion Address NAK Flecesve Lent SFC Execution File Redundancy Nonvolatiie Memory Memory System Protocol User Protocol Major Faits Mince Fouts Enor Detection BCC C CRC DF Point to Point
22. DF1 protocols Uses modems Controls SCADA applications Controls ASCII devices Requires additional RS 232 connections 1756 MVI Requires RS 422 and or RS 485 connections 1756 MVID Limit the length of RS 232 serial cables to 15 2 m 50 ft DF1 Modes for Logix5000 Controllers Functions Communication between the controller and one other DF1 protocol compatible device This is the default system mode Default parameters are Baud Rate 19200 Data Bits 8 Parity None Stop Bits 1 Control Line No Handshake RTS send Delay 0 RTS Off Delay 0 This mode is typically used to program the controller through its serial port DF1 master Control of polling and message transmission between the master and slave nodes mode The master slave network includes one controller configured as the master node and up to 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 one master and one slave station being the two nodes DF1 slave Using a controller as a slave station in a master slave serial communication network When there are multiple slave stations on the network link slave stations using modems or line drivers to the master When you have a single slave station on the network you do not need a modem to connect the slave
23. EN P July 2007 PLEASE FASTEN HERE DO NOT STAPLE Other Comments PLEASE FOLD HERE BUSINESS REPLY MAIL FIRST CLASS MAIL PERMIT NO 18235 CLEVELAND OH POSTAGE WILL BE PAID BY THE ADDRESSEE Rockwell Automation 1 ALLEN BRADLEY DR MAYFIELD HEIGHTS OH 44124 9705 NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES PLEASE REMOVE Rockwell Automation Support www rockwellautomation com Rockwell Automation provides technical information on the Web to assist you in using its products At http support rockwellautomation com you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect support programs For more information contact your local distributor or Rockwell Automation representative or visit http support rockwellautomation com Installation Assistance If you experience a problem within the first 24 hours of installation please review the information that s contained in this manual You can also contact a special Customer Support number for initial help in getting your product up and running United States 1 440 646 3434 Monday Friday 8am 5pm EST Outside United P
24. Has Timed Out with a Specific TO Module eer rt e e tem E Ae Pe ae 81 Interrupt the Execution of Logic and Execute the Fault Handler 82 Select a System Overhead Percentage os cue v e er 83 Chapter7 Introductions Sots oh rr a CIE CARD s ACER UICE n dle Sd 87 Additional ResoufGEs unde a eme ach deg rhe ono eh rone dei 87 PhaseManager Overview ours us oro eese des sonde ares Mu eda 87 State Model Oven Ww o cae ts fu AUREOS CURRO CI ST eA AERA 89 How Equipment Changes States qu Pre ay aR REL 90 Manually Change States e ero e ACH E trees dor 91 Compare PhaseManager to Other State Models 91 Minimum System Requirements 5 oce eU I E E ei b RES 92 Equipment Phase Instructions 11e n mee ebat Se em prio 92 Chapter 8 pttOQU e LOEL ues ood ex e pee sb GE ga Ob a ptus 93 Make the Controller the CST Master 34d waa ate RP ea 94 Multiple Controllers in the Chassis erre Een 94 Add the Motion Modules a i ide t doas oce Os 95 Additional Dforiablot ieu ha e in 0 C Eee OCDE d tet 96 Add SERCOS Interface Dives ii ipo por ERN Eds 97 Additional Resources iy 2i sisse ed ona edie ea aaa RON C od 98 Set Up Each SERCOS Interface Module cc cece eee es 99 Add the Motion Group issu ei a o S Ds Bi SE OS 101 Add YOU AXES Gea irt ri ae pee ak Ta ta ue ra E me ry 104 Set Up Each Iss Vera P Maui Me pee fo uc eure eet i 105 Check the Wiring of Each Dives c co ux re Re ec S 108 Additional Resout6esa vire d paci toes Precio darte 109
25. I Enable Duphcate Detection ENQ Transmit Limit ACK Timeout 50 120 ms Embedded Responses Autodetect R oK Cornel Hee 6 From the Protocol pull down menu choose DF1 Point to Point 7 Specify DF1 system protocol settings 8 Publication 1756 UM001H EN P July 2008 Click OK 33 Chapter3 Communicate over Networks DF1 Radio Modem Support Your ControlLogix controller includes a driver that allows it to communicate over the DF1 Radio Modem protocol This driver implements a protocol optimized for use with radio modem networks that is a hybrid between DF1 full duplex protocol and DF 1 half duplex protocol and therefore is not compatible with either of these protocols The DFI radio modem driver should only be used among devices that support and are configured for the DF1 radio modem protocol Additionally there are some radio modem network configurations that will not work with the DF1 radio modem driver In these configurations continue to use DF1 half duplex protocol LJ N EtherNet IP RS 232 Modem RE Modem B3 Modem Like DF1 full duplex protocol DF1 radio modem allows any node to initiate to any other node at any time if the radio modem network supports full duplex data port buffering and radio transmission collision avoidance Like DF1 half duplex protocol a node ignor
26. In Motion Groups within RSLogix 5000 programming software click motion_group and then right click an axis and select Properties Motion Groups Ca motion group ome 155 axis Module 3 Ungrour Add On Inst Monitor Axis Tag amp Data Types Cg User De Fault Help oe Strings Cg Add On Of Predefir Cut Ctrl x Oi Module Copy Ctrl C 53 Trends 3 1 0 Configui e fi 1768 Bu Delete Del ERI rei u Motion Direct Commands e Cross Reference Ctrl E cription s State Print gt lule Name l innel HERE aad Alt Enter The Axis Properties dialog appears Axis Properties My Axis X General Motion Planner Units Drive Motor Motor Feedback Aux Feedback Conversion Homing Hookup Tune Dynamics Gains Output Limits Offset Fault Actions Tag Travel Limit 1 0 Revs Start Tuning Speed 10 0 Revs s DANGER This tuning procedure may cause axis H sears Torque Force 100 0 Rated doccia COM Direction Forward Uni directional Damping Factor 0 8 Tune Position Error Integrator Velocity Error Integrator Friction Compensation Velocity Feedforward Acceleration Feedforward D Output Filter OK Cancel Help 110 Publication 1756 UMO001H EN P July 2008 Develop Motion Applications Chapter 8 2 Click the Tune tab 3 In the Travel Limit box type the number of revolutions to which you want to limit your axis during its tunin
27. Publication 1756 UM001H EN P July 2008 DH 485 Network Communication Publication 1756 UMO001H EN P July 2008 Communicate over Networks Chapter 3 Additional Resources For additional information consult these publications Logix5000 Controllers General Instructions Reference Manual publication 1756 RM003 Logix5000 Controllers Common Procedures Programming Manual publication 1756 PM001 Modbus Support To use Logix5000 controllers on the Modbus protocol establish a serial port connection and execute a specific ladder logic routine The controller project is available with RSLogix 5000 programming software Additional Resources For additional information consult Using Logix5000 Controllers as Masters or Slaves on Modbus Application Solution publication CIG AP129 Por DH 485 communication use the serial port of the controller The controller can send and receive messages to and from other controllers on a DH 485 network The DH 485 connection supports remote programming and monitoring via RSLogix 5000 programming software However excessive traffic over a DH 485 connection can adversely affect overall performance and lead to timeouts and decreased RSLogix 5000 configuration performance Miata Use Logixs000 controllers on DH 485 networks only when you want to add controllers to an existing DH 485 network For new applications with Logix5000 controllers we recommend you use networks in the NetLinx open architecture
28. RIO adapters Support HART Highway Addressable Remote Transducer devices Use scheduled connections to update data on a ControlLogix controller When a channel on the 1756 DHRIO module is configured for remote I O the module acts as a scanner for a universal remote I O network The controller communicates to the module to send and receive the I O on the universal remote I O netwotk Publication 1756 UM001H EN P July 2008 Publication 1756 UMO001H EN P July 2008 Communicate over Networks Chapter 3 ControlLogix Universal Remote I O Communication Overview ControlLogix Controller 1771 ASB and 1 0 Modules LTHRHEHRHHA DB d uu piono I H ru 1746 2 and VO Modules dis B EE Universal Remote 1 0 Network PLC 5 Controller in Adapter Mode TUR 1794 ASB and 1 0 Modules 47 Chapter3 Communicate over Networks Communicate over a Universal Remote 1 0 Network For the controller to control I O over a universal remote I O network you must perform this procedure 1 2 3 4 Configure the remote I O adapter Lay out the remote I O network cable Connect the remote I O network cable Configure the scanner channel As you design
29. RSLogix 5000 programming software right click the controller and select Properties 0 1756 L55 Ch l EU 1 1756 CNB D zm ControlNet B 517564 B 617564 9 175i e B 717854 meme Properties Alt Enter The Controller Properties dialog appears f Controller Properties CNET messaging General Serial Port System Protocol User Protocol Major Faults Minor Faults Date Time Seed SFC Execution File Redundancy Nonvolatile Memory Memory none Controller Fault Handler Power Up Handler none System Overhead rz O Time Slice 10 1 4 During unused System Overhead Time Slice Run Continuous Task Reserve for System Tasks eg Communications Security t Match Project to Controller Serial Number Cancel Help 2 Click the Advanced tab 3 Specify the system overhead settings System overhead functions include communication with programming and HMI devices such as RSLogix 5000 programming software responding to messages transmission of messages 83 Chapter 6 Develop Applications 4 Click OK 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 is no communication fo
30. State Routine How to add ee Drain Phase a a l NET Ds Gas SPC Ez Space Parts Phase Y Y Eg MainProgram Equipment phase instructions control the transitions between states and handle faults PSC POVR PCLF PRNP PATT PCMD PFL PXRQ PPD PDET L_ Cs My Equipment Program Other code controls the specific actions of your equipment Water Feed Conveyor Enable Axes L e a e 88 Publication 1756 UM001H EN P July 2008 State Model Overview Configure PhaseManager Chapter 7 A state model defines what your equipment does under different conditions such as run hold and stop PhaseManager States State Description Acting Does something or several things for a certain time or until certain conditions are met An acting state runs once or repeatedly Waiting Shows that certain conditions are met and the equipment is waiting for the signal to go to the next state PhaseManager State Transitions Start Running Resetting Hold Hold Restarting Your equipment can go from any state in the box to the stopping or aborting state Restart Acting states represent the things your Reset Reset Stopping Aborting
31. VIRTUAL Oma tine The New Tag dialog appears Name My Axis 2 Description Usage Type Base m Eon Alias For E Data Type AXIS SERVO DRIVE gu Scope 3g My Controller Style Open AXIS_SERVO_DRIVE Configuration 3 In the Name box enter the name of your new axis 4 Leave Open AXIS_SERVO_DRIVE Configuration unchecked 5 Click OK 104 Publication 1756 UM001H EN P July 2008 Develop Motion Applications Chapter 8 Set Up Each Axis Publication 1756 UMO001H EN P July 2008 To set up the axis of a SERCOS interface drive perform this procedure 1 In Motion Groups within RSLogix 5000 programming software click motion group and then right click an axis and select Properties Motion Groups 3 motion group omm NN i axis Goto Module Ungroup Add On Inst Monitor Axis Tag x Data Types Cg User De Fault Help Cg Strings ar d i Cy Add On Of Predefir Cut Ctrl x Gi Module Copy Ctrl C Trends p E x 1 0 Configu F Paste SU 1768 Bu Delete Del RI rei dl Motion Direct Commands e Cross Reference Ctrl E cription 5 State Print le lule Name md The Axis Properties Dialog appears e Axis Properties TEST 5j x Homing Hookup Tune Dynamics Gains Output Limits Offset Fault Actions Tag General Motion Planner Units Drive Motor MotorFeedback AuxFeedback Conversion Axis Configur
32. application The ControlNet network is highly deterministic and repeatable and remains unaffected as devices are connected or disconnected from the network This robust quality results in dependable synchronized and coordinated real time performance The ControlNet network often functions as a substitute replacement for the remote I O RIO network because the ControlNet network adeptly handles large numbers of I O points a backbone to multiple distributed DeviceNet networks a peer interlocking network For ControlNet communication you have two communication modules from which to choose ControlNet Communication Modules Functions Required Module Control 1 0 modules 1756 CNB Require an adapter for distributed 1 0 on ControlNet links Communicate with other ControlNet devices messages Share data with other Logix5000 controllers produce consume Bridge ControlNet links to route messages to devices on other networks Perform same functions as a 1756 CNB module 1756 CNBR Support redundant ControlNet media Publication 1756 UMO001H EN P July 2008 25 Chapter3 Communicate over Networks Required Software for ControlNet Communication Software Functions Requirement RSLogix 5000 Configure ControlLogix projects Define ControlNet communication RSNetWorx Configure ControlNet devices by IP addresses for ControlNet and or host names Yes Schedule a network RSLinx Con
33. as often as the RPI Change of State COS Digital 1 0 modules use COS to determine when to send data to the controller If a COS does not occur within the RPI the module multicasts data at the rate specified by the RPI Because the RPI and COS functions are asynchronous to the logic scan it is possible for an input to change state during program scan execution If this is a concern buffer input data so your logic has a stable copy of data during its scan Use the Synchronous Copy CPS instruction to copy the input data from your input tags to another structure and use the data from that structure Communication Format Many I O modules support different formats The communication format that you choose also determines data structure of tags connections network usage ownership whether the module returns diagnostic information Electronic Keying When you configure a module you specify the slot number for the module However it is possible to purposely or accidentally place a different module in that slot Electronic keying lets you protect your system against the accidental placement of the wrong module in a slot The chosen keying option determines how closely any module in a slot must match the configuration for that slot before the controller opens a connection to the module Keying options differ depending on your application needs Publication 1756 UMO001H EN P July 2008 59 Chapterb Place Co
34. behave the same way PhaseManager Transition Commands Command Done No command Use PSC instruction instead Start Hold Your equipment can go from any state in Running Holding the box to the stopping or aborting state Hold Restart CDEN Stop Abort Fault specific use of the abort Host Abort command Stopping Aborting Reset Stopped Aborted Type of Transition Description Command A command tells the equipment to do something For example the operator pushes the start button to begin production and the stop button to halt production PhaseManager uses these commands Reset Stop Restart Start Hold Abort Done Equipment goes to a waiting state when it is finished with what it is doing You do not give the equipment a command Instead you set up your code to signal when the equipment is finished Fault A fault tells you that something out of the ordinary has happened You set up your code to look for faults and take action if it finds any If you want to shut down your equipment as quickly as possible when it detects a fault set up your code to look for that fault and give the abort command if it finds it 90 Publication 1756 UM001H EN P July 2008 Configure PhaseManager Chapter 7 Manually Change States With RSLogix 5000 programming software you can manually change an equipment phase To manually change a PhaseManager state perform this procedure
35. card The CompactFlash card stores the firmware for projects gt 12 0 Depending on the current revision of the controller you may be able to use the CompactFlash card to update the firmware of the controller and load the project Publication 1756 UM001H EN P July 2008 Use a CompactFlash Reader Publication 1756 UMO001H EN P July 2008 Maintain Nonvolatile Memory Chapter 11 If the revision of the project or projects on your CompactFlash card are 2 12 then the card is formatted using the FAT16 file system You do not have to manage the files on a CompactFlash card The card automatically loads the project that you most recently stored For additional flexibility the file system also lets you manually change which project loads from the CompactFlash card manually change the load parameters for a project A sample controller project that reads and writes a CompactFlash card is available with RSLogix 5000 Enterprise programming software See the section Sample Controller Projects on page 75 Additional Resources For additional information consult the Logix5000 Controllers Common Procedures Programming Manual 1756 PM001 125 Chapter 11 Maintain Nonvolatile Memory Notes 126 Publication 1756 UM001H EN P July 2008 Chapter 12 Maintain the Battery Introduction This chapter explains how to maintain the batteries supported by ControlLogix controllers Controller Series Supported Battery ControlLog
36. commands as unscheduled messages Support asset management software to HART device Spectrum analog 1 0 modules 1756sc IF8H 1756sc OF8H Contain analog and HART in one module Provide instrumentation in hazardous locations FLEX Ex Transmit HART commands as unscheduled messages Directly connect asset management software to HART devices 1794 FLEX 1 0 modules 1794 IEBH 1794 0E8H 1797 FLEX Ex I O modules 1797 IEBH 1797 0E8H The HART protocol combines digital signals with analog signals to ready the digital signal for the process variable PV The HART protocol also provides diagnostic data from the transmitter HART Protocol Overview 0 ControlLogix Controller with 1756SC IF8H or 1756SC OF8H Modules L2 E HART Field Devices Additional Resources For additional information consult these resources FLEX Ex HART Analog Modules User Manual publication 1797 6 5 3 Encompass website at http automation rockwell encompass 50 Publication 1756 UM001H EN P July 2008 Chapter 4 Manage Controller Communication Introduction This chapter explains how to manage controller communication Topic Page Connection Overview 51 Produce and Consume Interlock Data 52 Send and Receive Messages 53 Calculate Connection Use 54 Connection Overview A Logix5000 system uses a connection to establish a communication link between two devices
37. messages to the module while the reconfigure 5 is on reconfigure 5 reconfigure 5 MOV ONS Move Source 60 Dest Local4 C ChOConfig HAlarmLimit 75 06 MSG Type Module Reconfigure f Message Control change_Halarm E h gt change_Halarm EN Publication 1756 UMO001H EN P July 2008 69 Chapterb Place Configure and Monitor 1 0 Modules Notes 70 Publication 1756 UM001H EN P July 2008 Chapter 6 Develop Applications Introduction This chapter explains how to develop applications Topic Page Manage Tasks 71 Develop Programs 72 Organize Tags 76 Select a Programming Language 77 Monitor Controller Status 79 Monitor Connections 80 Select a System Overhead Percentage 83 Additional Resources For additional general information consult these publications Logix5000 Controllers Common Procedures Programming Manual publication 1756 PM001 Logix5000 Controllers Design Considerations Reference Manual publication 1756 RM094 M anage Tasks A Logix5000 controller lets you use multiple tasks to schedule and prioritize the execution of your programs based on specific criteria This multitasking allocates the controller s processing time among the different operations in your application The controller executes only one task at a time One task can interrupt another execution and take control In any given task only one program executes at a
38. module 68 redundancy considerations 118 ControlNet 118 EtherNet IP 119 example system 116 overview 115 requirements 117 switchover 116 redundant media 115 relay ladder 77 requested packet interval 59 RIO see universal remote I O 46 RPI 59 RS 232 DF1 Device driver 17 S safety integration level see SIL 2 121 sample controller projects 75 scheduled connections 27 select programming language 77 system overhead percentage 83 send messages 53 sequential function chart 77 SERCOS interface drive add to controller 97 SERCOS interface modules choose 95 set up 99 serial cable 15 communicate with ASCII device ASCII device 38 communicate with DF1 device 32 controller communication 31 controller connection 15 DH 485 network configuration 41 driver 17 Modbus support 41 select controller path 19 set up axis 105 SERCOS module 99 SFC 77 SIL 2 certification example application 122 overview 121 SSV instruction 79 ST 77 state model 89 overview 89 status 79 structured text 77 system overhead percentage 83 system requirements PhaseManager 92 T tag organize 76 task 71 tune axis 110 U universal remote I 0 module capability 48 overview 46 unscheduled connections 27 update 67 Publication 1756 UMO001H EN P July 2008 How Are We Doing Your comments on our technical publications will help us serve you better in the future Thank you for taking the time to provide us feedback You can complete this for
39. number DINT Storage Bit replace bit BOOL Counter d M HH running hours COUNTER Timer 9 running_seconds TIMER start BOOL Digital I O Device A stop BOOL Monitor Tags Edit Tags 4 When you create a tag you assign these properties to the tag tag type data type Scope 76 Publication 1756 UM001H EN P July 2008 Develop Applications Chapter 6 Select a Programming Language Required Language Ladder diagram LD The ControlLogix controller supports these programming languages both online and offline Logix5000 Programming Languages Programs Continuous or parallel execution of multiple operations not sequenced Boolean or bit based operations Complex logical operations Message and communication processing Machine interlocking Operations that service or maintenance personnel may have to interpret in order to troubleshoot the machine or process Function block diagram FBD Sequential function chart SFC Structured text ST Publication 1756 UMO001H EN P July 2008 Continuous process and drive control Loop control Calculations in circuit flow High level management of multiple operations Repetitive sequence of operations Batch process Motion control using structured text State machine operations Complex mathematical operations Specialized array or table loop processing ASCII string handling
40. programming software to select the controller path perform this procedure 1 Open an RSLogix 5000 project for the controller 2 From the Communications pull down menu choose Who Active 3 Expand the communication driver to the level of the controller ioii MV Autobrowse RENES E workstation USMAYHMILLS d Linx Gateways Ethernet zx AB DF1 1 DF1 Upload EEO 1756 L62 Le y Controller AB_ETH 1 Ethernet Download G a AB ETH 2 Ethernet Update Firmware Close Help Path AB DF1 1 Set Project Path Path in Project none lear Project Path 4 Select the controller To Choose Monitor the project in the controller Go Online Transfer a copy of the project from the controller to Upload RSLogix 5000 software Transfer the open project to the controller Download Publication 1756 UMO001H EN P July 2008 19 Chapter 2 Notes 20 Directly Connect to the Controller via the Serial Port Publication 1756 UM001H EN P July 2008 Chapter 3 Communicate over Networks Introduction This chapter explains over what networks you can communicate Network Support Example Control distributed remote 1 0 FtherNet IP network ControlLogix Controller ControlNet network DeviceNet network Control Network Universal remote I O network Foundation Fieldbus network Distributed remote
41. 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 DF1 Radio Compatible with SLC 500 and MicroLogix 1500 controllers Modem This mode supports master and slave and store and forward modes Publication 1756 UMO001H EN P July 2008 31 Chapter3 Communicate over Networks Mode Functions User Communication with ASCII devices This requires your program to use ASCII instructions to read and write data from and to an ASCII device DH 485 Communication with other DH 485 devices multi master token passing network allowing programming and peer to peer messaging Communicate with DF1 Devices You can configure the controller as a master or slave on a serial communication network Use serial communication to get information to and from remote controllers stations when the system contains three or more stations communication occurs on a regular basis and requires leased line radio or power line modems ControlLogix DF1 Device Communication DO rm 2 i a a EtherNet IP 9 Network RS 232 Connection RS 232 Connection RS 232
42. time Publication 1756 UMO001H EN P July 2008 n Chapter 6 Develop Applications Develop Programs The controller operating system is a preemptive multitasking system that is TEC 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 Program Development Overview 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 72 Publication 1756 UM001H EN P July 2008 Develop Applications Chapter 6 Define 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 Types of ControlLogix Controller Tasks Task Execution Task Type Description All of the time Continuous The continuous task runs in the background Any CPU time not allocated to other operations such as motion communication and other tasks is used to execute the programs in the continuous task The continuous task runs constantly When the continuous task completes a full scan it restarts immediately A project does not require a continuous task If used there c
43. wetting Stop Abort equipment does at a given time Abort Waiting states represent the condition of your equipment when it is between acting states Stopped Aborted Publication 1756 UMO001H EN P July 2008 With a state model you define the behavior of your equipment PhaseManager State Models State Question to be asked Stopped What happens when you turn on power Resetting How does the equipment get ready to run Idle How do you tell that the equipment is ready to run Running What does the equipment do to make product Holding How does the equipment temporarily stop making product without making scrap Held How do you tell if the equipment is safely holding Restarting How does the equipment resume production after holding Complete How do you tell when the equipment is done with what it had to do Stopping What happens during a normal shutdown Aborting How does the equipment shut down if a fault or failure occurs Aborted How do you tell if the equipment is safely shut down 89 Chapter7 Configure PhaseManager Transition How Equipment Changes States The state model s arrows show the states through which your equipment progresses Each arrow is called a transition A state model lets the equipment make only certain transitions This restriction standardizes the equipment s behavior so that other equipment using the same model will
44. 0 F 98 days 204 days 11 104 days 25 C 77 F 146 days 268 days 5 157 days 0 C 32 F 105 days 222 days 6 113 days Estimate 1756 BA2 Use this table to estimate how much time will elapse before the battery Battery Life becomes low BAT LED solid red on 1756 L6x series B controllers 1756 L6x series B controllers only Worst case Estimates of 1756 BA2 Battery Life Temperature 2 54 cm 1 in Power Cycles Battery Life Before the BAT LED Turns Red Below the Chassis Max Project Size 1 MB 2MB 4 MB 8 MB 16 MB 2 per day or less 3 years 3 years 3 years 31 months 16 months 2 per day or less 2 years 2 years 2 years 2 years 16 months 46 50 C 105 8 113 F 3 per day or less 16 months 16 months 16 months 16 months 10 months 51 55 C 123 8 131 F 3 per day or less 11 months 11 months 11 months 11 months 10 months 56 60 C 132 8 140 F 3 per day or less 8 months 8 months 8 months 8 months 8 months 130 Publication 1756 UM001H EN P July 2008 Estimate Warning Time Maintain the Battery Chapter 12 Use this table to estimate the battery life after the low battery warning BAT LED solid red Use these times whether or not the controller has power There is always a small drain on the battery IMPORTANT When you power up the controller see if there is a low battery warning If you get a low battery warning for the first time you have less batte
45. 08 107 Chapter 8 Develop Motion Applications Check the Wiring of Each Use these tests to check a drive s wiring Drive Test Function Notes Test marker Verify that the encoder A B and Z You must manually move the channels are connected and phased axis for this test properly for marker detection Test feedback Verify the polarity of the feedback You must manually move the axis for this test Test command Verify the polarity of the drive and feedback ATTENTION These tests move the axis even with the controller in Remote Program mode A Before you do the tests make sure no one is in the path of the axis Do not change the polarity after you do the tests or you may cause an axis runaway condition To check the wiring of each drive perform this procedure 1 In Motion Groups within RSLogix 5000 programming software click motion_group and then right click an axis and select Properties i axis E Ungrour G Add On Inst Monitor Axis Tag 3 pata Types x Cg User De Fault Help Motion Groups motion group oe Strings C Add On x Predefir amp Cut Ctrl x Oy Module Copy Ctrl C Trends m x 1 0 Configut 1768 Bu Delete Del ERI rm ll Motion Direct Commands e Cross Reference Ctrl E cription s State Print id lule Name mnel EEE Alt Enter 108 Publication 1756 UMO001H EN P July 2008 Develop Motion Applications Chapter 8 Publication 1756 UM00
46. 1H EN P July 2008 The Axis Properties Dialog appears Axis Properties My Axis X General Motion Planner Units Drive Motor Motor Feedback Aux Feedback Conversion Homing Hookup Tune Dynamics Gains Output Limits Offset Fault Actions Tag Test Increment 1 0 Revs Test Marker Test Feedback Test Command amp Feedback Drive Polarity program mode Modifying polarity determined after executing the Test DANGER These tests may cause axis motion with the controller in A Command amp Feedback test may cause axis runaway condition Cancel Apply Help 2 Click the Hookup tab 3 Inthe Test Increment box type the number of revolutions you want the axis to turn during each test 4 Click Test Marker to check the channels for proper connection and phasing 5 Click Test Feedback to test the polarity of the feedback 6 Click Test Command amp Feedback to test the drive s polarity 7 Click OK Additional Resources Por additional information consult the Logix5000 Motion Module User Manual publication 1756 UM006 109 Chapter 8 Develop Motion Applications Tune Each Axis You need to tune each axis ATTENTION When you tune an axis it moves even with the controller in Remote Program mode In that mode your code is not in control of the axis Before you tune an axis make sure no one is in its path To tune each axis perform this procedure 1
47. Chapter 6 Develop Applications Interrupt the Execution of Logic and Execute the Fault Handler To interrupt the execution of logic and execute the fault handler perform this procedure 1 In the Controller Organizer of RSLogix 5000 programming software right click the module and select Properties t s S contr Pj New Module 8c Copy Ctrl C Offline Cross Reference Ctri E Properties Alt Enter Bum The Module Properties dialog appears lil Module Properties Local 1 1756 CNB D 5 1 General Connection RSNetworx Module Info Backplane Requested Packet Interval RPI ms ri I Major Fault On Controller If Connection Fails While in Run Mode Module Fault Status Offline Cancel Help 2 Click the Connection tab 3 Select the Major Fault If Connection Fails While in Run Mode check box 4 Develop a routine for the Controller Fault Handler 82 Publication 1756 UM001H EN P July 2008 Develop Applications Chapter 6 Select a System Overhead Percentage Publication 1756 UMO001H EN P July 2008 The Controller Properties dialog lets you specify a percentage for the system overhead or time slice The system overhead time slice specifies the percentage of controller time excluding the time for periodic tasks devoted to communication and background functions To select a system overhead percentage slice perform this procedure 1 In the Controller Organizer of
48. ControlLogix Controllers User Manual Catalog Numbers 1756 L55M12 1756 L55M13 1756 L55M14 1756 L55M16 1756 L55M22 1756 L55M23 1756 L55M24 1756 L61 1756 L62 1756 L63 1756 L64 1756 L65 1756 L60MO3SE Rockwell ALLEN BRADLEY ROCKWELL SOFTWARE Automation 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 literature rockwellautomation com 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 liabil
49. Current Equipment Phase fY Equipment Phase Monitor My Phase quipment Phases ner s RSLogix 5000 1 hy Phase Res du E Restarting 1 Take ownership of the equipment phase 2 Give a command Stop Abort Complete Stopping Aborting Stopped Aborted Pause Compare PhaseManager to You can compare PhaseManager state models to other state models Other State Models Publication 1756 UM001H EN P July 2008 S88 PackML PhaseManager Idle Starting Ready Resetting Idle Running Complete Producing Running Complete Pausing Paused Standby Subroutines or breakpoints Holding Held Holding Held Holding Held Restarting None Restarting Stopping Stopped Stopping Stopped Stopping Stopped Aborting Aborted Aborting Aborted Aborting Aborted 91 Chapter7 Configure PhaseManager Minimum System Requirements Equipment Phase Instructions 92 To develop PhaseManager programs you need a ControlLogix controller firmware revision 16 0 or later a communication path to the controller RSLogix 5000 software version 16 0 or later To enable PhaseManager support you need the full or professional editions of RSLogix 5000 programming software or RSLogix 5000 with PhaseManager software 9324 RLDPMENE The controller supports several equipment phase ladder diagram LD and structured text ST instructions PhaseManager Instructions Instruction Instruction Functio
50. H EN P July 2008 Cable Selection Connection Port 1 DB 9 RS 232 DTE connection Communicate over Networks Chapter 3 Required Cable 1747 CP3 or 1761 CBL ACOO Port 2 Mini DIN 8 RS 232 connection 1761 CBL APO0 or 1761 CBL PMO02 To communicate with DH 485 devices perform this procedure 1 In the Controller Organizer of RSLogix 5000 programming software right click your controller and select Properties B 7 1756 Pisj 0 Properties Alt Enter The Controller Properties dialog appears fa Controller Properties Pl SSampleProject Date Time Advanced SFC Execution Fie Redundancy Nonvolatie Memory Memory General Seti Port SystemProtocol User Protocol Majo Fauls Minor Faults eros Mode System Fed Baud Rate wa v Data Bits 8 zi Ponty None Stop Bits 1 X Control Line No Handshake r RTS Send Delay 0 20 ms RTS Olf Dely O 20 ma DCD Wat Delay x1 sec OK 2 Click the Serial Port tab Cancel Help 3 From the Mode pull down menu choose System Publication 1756 UMO001H EN P July 2008 43 Chapter 3 Communicate over Networks 4 Specify communication settings From the Baud Rate pull down menu choose 9600 or 19200 kbps The 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 5 Click the System Protoco
51. IP Network You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system Connections are allocations of resources that provide more reliable communication between devices compared to unconnected messages All EtherNet IP connections are unscheduled An unscheduled connection is triggered by the requested packet interval RPI for I O control or the program such as a MSG instruction Unscheduled messaging lets you send and receive data when needed The 1756 EtherNet IP communication modules support 128 CIP Common Industrial Protocol connections over an EtherNet IP network Publication 1756 UM001H EN P July 2008 Communicate over Networks Chapter 3 Additional Resources Por additional information consult these publications EtherNet IP Modules in Logix5000 Control Systems User Manual publication ENET UMO01 Logix5000 Controllers Design Considerations Reference Manual publication 1756 RM094 ControlNet Network The ControlNet network is a real time control network that provides hangi high speed transport of both time critical I O and interlocking data and Communication messaging data including uploading and downloading of programming and configuration data on a single physical media link The ControlNet network s highly efficient data transfer capability significantly enhances I O performance and peer to peer communication in any system or
52. L6x install a 1784 CF64 or 1784 128 CompactFlash card for nonvolatile memory See the chapter Maintain Nonvolatile Memory connect the battery See the chapter Maintain the Battery install the controller in the chassis make serial connections See the chapter Directly Connect to the Controller via the Serial Port load controller firmware make additional network connections See the chapter Communicate over Networks 14 Publication 1756 UM001H EN P July 2008 Introduction Connect the Controller to via the Serial Port __ Publication 1756 UMO001H EN P July 2008 Chapter 2 Directly Connect to the Controller via the Serial Port This chapter explains how to connect the controller to the serial port and how to upload and download a project to the controller Topic Page Connect the Controller to via the Serial Port 15 Configure the Serial Driver 17 Select the Controller Path 19 To connect a serial cable perform this procedure 1 Obtain a 1756 CP3 serial cable You can also use a 1747 CP3 cable from the SLC product family but once the cable is connected you cannot close the controller door 15 Chapter2 Directly Connect to the Controller via the Serial Port TIP If you make your own serial cable Limit the length to 15 2m 50 ft Wire the connectors this way
53. O forces are active enabled Use caution if you install add a force If you install add a force it 0 force values may or may not exist immediately takes effect Hashing amber One or more input or output addresses have been forced to an On or Off state but the Use caution if you enable 1 0 forces If you enable 1 0 forces ALL existing I O forces also take effect forces have not been enabled RS232 LED Indicator Description Recommended Action Off There is no activity No action is required Solid green Data is being received or transmitted No action is required BAT LED Indicator Color Description Recommended Action Off The battery supports memory None Solid green If the Then controller is Series A The controller does not None show this indication Series B During power down the None controller is saving the project to its internal nonvolatile memory If the BAT LED is solid red before you turn off the power the BAT LED remains solid red even during the save Solid red Either the battery is not installed Install a battery 95 or more discharged Replace the battery 136 Publication 1756 UM001H EN P July 2008 Status Indicators Appendix A OK LED Indicator Color Description Recommended Action Off No power is applied When ready turn on power to the controller Flashing red If the controller is Then a new controller The controller requires a Updat
54. The types of connections include controller to local I O modules or local communication modules controller to remote I O or remote communication modules controller to remote I O rack optimized modules produced and consumed tags messages controller access by RSLogix 5000 programming software controller access by RSLinx software for HMI or other applications Additional Resources For additional information consult Logix5000 Controllers Design Considerations Reference Manual publication 1756 RM094 Publication 1756 UMO001H EN P July 2008 51 Chapter4 Manage Controller Communication Produce and Consume The controller supports the ability to produce broadcast and consume receive system shared tags over ControlNet or EtherNet IP networks Produced and consumed tags each require connections Over a ControlNet network produced and consumed tags are scheduled connections Tag Types Description A produced tag lets other controllers to consume the tag which means that a controller can receive the tag data from another controller The producing controller uses one connection for the produced tag and one connection for each consumer The controllers communication device uses one connection for each consumer As you increase the number of controllers that can consume a produced tag you also reduce the number of connections the controller and communication device have available for other operations such as commu
55. These requirements consist of mean time between failures MTBF probability of failure failure rates diagnostic coverage and safe failure fractions that fulfill SIL 2 criteria The results make the ControlLogix system suitable up to and including SIL 2 When the ControlLogix system is in maintenance or programming mode the user is responsible for maintaining a safe state For support in the creation of programs the PADT Programming and Debugging Tool is required The PADT for ControlLogix is RSLogix 5000 programming software per IEC 61131 3 and this Safety Reference Manual 121 Chapter 10 SIL 2 Certification SIL2 Application In obtaining SIL 2 certification for a ControlLogix system Rockwell Sensor 122 Automation did not need to create a special line of products to meet stringent SIL 2 requirements Sophisticated diagnostics and high levels of reliability are standard in ControlLogix processors I O modules and communication products It is that same standard design that readily provides the reliability needed to achieve SIL 2 certification A typical ControlLogix SIL loop includes the overall safety loop the ControlLogix portion of the safety loop how other devices for example HMI connect to the loop while operating outside the loop SIL 2 Application Overview Programming Software HMI For SIL applications a programming For Diagnostics and Visualization read only terminal is not norm
56. ally connected access to controllers in the safety loop Plant wide Ethernet Serial Network Actuator ControlNet Network p Safety l related l To Other ControlLogix Remote 1 0 Chassis ControlNet Network a To Nonsafety related Systems Outside the ControlLogix Portion of the SIL2 certified Loop Publication 1756 UM001H EN P July 2008 Chapter 11 Maintain Nonvolatile Memory Introduction This chapter explains how to maintain nonvolatile memory The 1756 L6x controllers support the 1784 CF64 and 1784 CF128 CompactFlash cards for nonvolatile memory The 1756 L55M22 1756 M23 and 1756 M24 controllers have built in nonvolatile memory Nonvolatile memory lets you keep a copy of your project on the controller The controller does not need power to keep this copy You can load the copy from nonvolatile memory to the controllet s user memory each time you apply power whenever there is no project in the controller and you apply power at any time via RSLogix 5000 programming software Topic Page Choose a Controller That Has Nonvolatile Memory 124 Use a CompactFlash Reader 125 IMPORTANT Me memory stores the contents of the user memory when you store the project Changes made after storing a project are not reflected in nonvolatile memory If you change to the project but do not store those changes you overwrite them
57. an be only one continuous task Atasetinterval Periodic A periodic task performs a function at a specific interval such as every 100 ms Whenever the time for the periodic task expires the task interrupts any lower priority tasks Multiple times executes once and then returns control to where the previous task left off within the scan You can configure the time period from 0 1 2000 us The default is of your other 10 ms It is also controller and configuration dependent logic The performance of a periodic task depends on the type of Logix5000 controller and on the logic in the task Immediately when Event An event task performs a function only when a specific event trigger occurs The trigger for the event an event occurs task can be a consumed tag trigger an EVENT instruction an axis trigger a motion event trigger The ControlLogix controller supports up to 32 tasks only one of which can be continuous A task can have up to 100 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 Specify Task Priorities Each task in the controller has a priority level The operating system uses the priority level to determine which task to execute when multiple tasks are
58. ation X Motion Group miongo e Bl m Associated Module Module e xz Module Type none Node From the Module pull down menu choose the name that you gave to the drive for this axis Click the Units tab Axis Properties TEST Homing Hookup Tune Dynamics Gains Output Limits Offset FaukActions Tag General Motion Planner Units Position Units Drive Motor MotorFeedback AuxFeedback Conversion Average Velocity Timebase ozs Seconds In the Position Units box enter the units of measure such as revolutions revs degrees inches or millimeters 105 Chapter 8 Develop Motion Applications 5 Click the Drive Motor tab KO Axis Properties TEST 5j E3 Homing Hookup Tune Dynamics Gains Output Limits Offset FaukActons Tag General Motion Planner Units Drive Motor Motor Feedback Aux Feedback Conversion Amie at Niner Motor Catalog Number knon Change Catalog Loop Configuration Posionsevo x Drive Resolution o Drive Counts per MotorRev x Calculate M Drive Enable Input Checking Diive Eriable Iriput Fault Real Time Axis Information Attribute 1 none m Attribute 2 lt none gt 6 From the Amplifier Catalog Number pull down menu choose the catalog number of your drive 7 To select your motor s catalog number click Change Catalog 8 Click the Conversion tab e Axis Properties TEST EX Homing Hoo
59. blication 1756 UM001H EN P July 2008 Communicate over Networks Chapter 3 DF1 Radio Modem System Limitations The following questions need to be answered in order to determine if you can implement the new DF1 radio modem driver in your radio modem network If all of the devices on the network are ControlLogix controllers you must configure them with the DF1 radio modem driver using RSLogix 5000 version 17 or later If not then make sure that all of the nodes can support the DF1 radio modem protocol If each node receives the radio transmissions of every other node being both within radio transmission reception range and on a common receiving frequency either via a Simplex radio mode or via a single common full duplex repeater the radio modems must handle full duplex data port buffering and radio transmission collision avoidance If this is the case you can take full advantage of the peer to peer message initiation capability in every node for example the ladder logic in any node can trigger a MSG instruction to any other node at any time If not all modems can handle full duplex data port buffering and radio transmission collision avoidance you may still be able to use the DF1 radio modem driver but only if you limit MSG instruction initiation to a single master node whose transmission can be received by every other node If not all nodes receive the radio transmission of every other node you may still be able to u
60. connection open cache or close the connection when the message is done transmitting Each message uses one connection regardless of how many devices are in the message path To conserve connections configure one message to read from or write to multiple devices Message Types Message Type Communication Connected Message Can Method Message Be Cached CIP data table read or write N A Yes Yes PLC 2 PLC 3 PLC 5 or SLC CIP No No all types CIP with Source ID No No DH Yes Yes CIP generic N A Optional Yes Block transfer read or write N A Yes Yes You can connect CIP generic messages However for most applications we recommend you leave CIP generic messages unconnected 2 Consider caching only if the target module requires a connection Each message uses one connection regardless of how many devices are in the message path You can programmatically change the target of a MSG instruction to optimize message transfer time Determine Whether to Cache Message Connections When you configure a MSG instruction you can choose whether or not to cache the connection Caching Message Connections Message Function Execution Repeatedly Cache the connection This keeps the connection open and optimizes execution time Opening a connection each time the message executes increases execution time Infrequently Do not cache the connection This closes the connection upon completion of the message
61. crease the time slice to 50 the system overhead interrupts the continuous task every millisecond 1ms System Overhead B Bi B NE EN B ni B n Bl Bi n 1ms Continuous Task B E E B E E E E H E w BI E 5 10 15 20 25 Elapsed Time ms If the controller only contains periodic tasks the system overhead time slice value has no effect System overhead runs whenever a periodic task is not running Periodic Task 5 10 15 20 25 Continuous Task Elapsed Time ms Publication 1756 UMO001H EN P July 2008 85 Chapter 6 Develop Applications Notes 86 Publication 1756 UM001H EN P July 2008 Chapter Introduction PhaseManager Overview Term Description Configure PhaseManager This chapter explains how to configure PhaseManager Within RSLogix 5000 programming software PhaseManager provides a state model for your equipment Topic Page PhaseManager Overview 87 State Model Overview 89 Compare PhaseManager to Other State Models 91 Minimum System Requirements 92 Equipment Phase Instructions 92 Additional Resources For more information consult PhaseManager User Manual publication LOGIX UMO001 PhaseManager lets you add equipment phases to your controller An equipment phase helps you lay out your code in sections that are easier to wtite find follow and change PhaseManager Terms Equipment phase As with a program an equipment phase is run in a task and is given a set o
62. d or host names Provide bandwidth status RSLinx Configure communication devices Yes Provide diagnostics Establish communication between devices The EtherNet IP communication modules support messaging produced consumed tags HMI and distributed I O encapsulate messages within standard TCP UDP IP protocol share a common application layer with ControlNet and DeviceNet networks connect via RJ45 cable support half full duplex 10 MB or 100 MB operation support standard switches In this example The controllers produce and consume tags The controllers initiate MSG instructions that send and receive data or configure devices The personal computer uploads and downloads projects to the controllers The personal computer configures devices on an EtherNet IP network 23 Chapter3 Communicate over Networks CompactLogix Controller with Integrated EtherNet IP Port PowerFlex 700S AC Drive with DriveLogix EtherNet IP Network Overview FlexLogix Controller with 1788 ENBT Module CUTEM Distributed 1 0 J ControlLogix 1756 ENBT Module as an adapter with 1756 P 1 0 Modules 1756 ENBT Module 1794 AENT Adapter with 1794 0 Modules mi 1734 AENT Adapter with 17341 0 Modules 24 Workstation Connections over an EtherNet
63. dditional information consult the Logix5000 Controllers General Instructions Reference Manual publication 1756 RM003 79 Chapter 6 Develop Applications Monitor Connections If communication with a device in the I O configuration of the controller does not occur for 100 ms or 4 times the RPI whichever is less the communication times out and the controller produces these warnings The I O LED on the front of the controller flashes green A A shows over the I O configuration folder and over the devices that have timed out A module fault code is produced which you can access via the Module Properties dialog a GSV instruction Determine if Communication Has Timed Out with Any Device If communication times out with at least one device module in the I O configuration of the controller the I O LED on the front of the controller flashes green The GSV instruction gets the status of the I O LED and stores it in the I O LED tag I I O LED equal 2 the controller has lost communication with at least one device GSV EQU Get System Value Equal CIP Object Class MODULE Source A O LED CIP Object Name Attribute Name LedStatus Source B 2 Dest O LED where I O LED is a DINT tag that stores the status of the I O LED on the front of the controller 80 Publication 1756 UM001H EN P July 2008 Develop Applications Chapter 6 Determine if Communication Has Timed Out w
64. e New Module dialog appears New Module Type 2094 AC05 MUT Kinetix 6000 230VAC IAM 3kw PS 3A Cont 174 Peak Vendor Allen Bradley Name Node Description Revision m 1 Electronic Keying Compatible Keying Open Module Properties Cancel Help 5 In the Name box type the name of the new drive 6 In the Node box select the node number of the drive in the SERCOS ring 7 Click OK Additional Resources For additional information consult these publications Motion Analyzer Selection Guide publication PST SG003 ControlLogix Selection Guide publication 1756 SG001 Logix5000 Motion Module User Manual publication 1756 UM006 98 Publication 1756 UM001H EN P July 2008 Develop Motion Applications Chapter 8 Set Up Each SERCOS Interface Module Publication 1756 UMO001H EN P July 2008 To set the data rate and cycle time for each SERCOS interface module in your project perform this procedure 1 In the I O configuration tree in RSLogix 5000 programming software right click your module and select Properties A 6 1 0 Configuration 9 1756 Backplane 1756 413 fa 0 1756 L55 My Controller at ol Els SERCOS Network P New Module l 1 2094 ACO9 M02 M l 2 2094 AMO1 My Dr Copy Ctrl C Cross Reference Ctri E The Module Properties dialog appears lil Module Properties Local 5 1756 MOOSL 15 1 Gerri Curnmevtiun SERCOS Interfaco
65. e buffer contains termination characters ACB Count the characters in the buffer ACL Clear the buffer Clear out ASCII Serial Port instructions that are currently executing or are in the queue AHL Obtain the status of the serial port control lines Turn on or off the DTR signal Turn on or off the RTS signal ARD Read a fixed number of characters ARL Read a varying number of characters up to and including the first set of termination characters AWA Send characters and automatically append one or two additional characters to mark the end of the data AWT Send characters Create and Modify Strings of ASCII Characters Instruction Code Command CONCAT Add characters to the end of a string DELETE Delete characters from a string FIND Determine the starting character of a sub string INSERT Insert characters into a string MID Extract characters from a string Convert Data to or from ASCII Characters Instruction Code Command STOD Convert the ASCII representation of an integer value to a SINT INT DINT or REAL value STOR Convert the ASCII representation of a floating point value to a REAL value DTOS Convert a SINT INT DINT or REAL value to a string of ASCII characters RTOS Convert a REAL value to a string of ASCII characters UPPER Convert the letters in a string of ASCII characters to upper case LOWER Convert the letters in a string of ASCII characters to lower case
66. e componmes change locaticnr ce make cther modificazcas ar necemary Yora cani une the RSLegjx SWO Compase utliey factaded on your RSLogix SW softwase CD to compene the sample project Sle with an emper ie new pecject fle Tha wil help yos to identify the components yos need to modify Reser o the online hp incinsed with the RSLogex 50 0 Compare walry for amre informanon on peroccasg the compatpan Sample Projects Cig oc any of te ndadal vendee nace to vee the bet of umple peoyece they have poceided Soc d release Additional Resources For more information consult Logix5000 Controllers Design Considerations Reference Manual publication 1756 RM094 Publication 1756 UMO001H EN P July 2008 75 Chapter 6 Develop Applications Organize Tags With a Logix5000 controller you use a tag alphanumeric name to address data variables In Logix5000 controllers there is no fixed numeric format The tag name itself identifies the data This lets you organize your data to mirror your machinery document your application as you develop it Tag Organization Overview Program Tags MainProgram Scope MainProgram Show Show All v Sot Tag Nar Alias For Type Base Tag north tank mix BOOL north_tank_pressure REAL Analog 0 Device 3 north tank temp REAL cone shots DINT recipe TANK 3 Integer Value recipe
67. e maximum temperature 2 54 cm 1 in below the chassis 45 C 113 F You cycle power to the controller 3 times per day The controller contains an 8 MB project Publication 1756 UMO001H EN P July 2008 Under these conditions the battery will last at least 20 months before the BAT light turns red 131 Chapter 12 Maintain the Battery Maintain a 1756 BATM Battery Module higher memory controllers Use the 1756 BATM battery module with any 1756 L55Mx or 1756 L6x series A controller The battery module is highly recommended for the Controller Project 1756 BATM Battery Module 1756 L55M12 p gt Permitted 1756 L55M13 gt Permitted 1756 L55M14 pr Highly recommended 1756 L55M16 p gt Highly recommended 1756 L55M22 Stored in nonvolatile memory Not required but permitted Not stored in nonvolatile memory Permitted 1756 L55M23 Stored in nonvolatile memory Not required but permitted Not stored in nonvolatile memory Permitted 1756 L55M24 Stored in nonvolatile memory Not required but permitted Not stored in nonvolatile memory Highly recommended 1756 163 Stored in nonvolatile memory Not required but permitted requires a 1784 CF64 Industrial CompactFlash card Not stored in nonvolatile memory Highly recommended When the 1756 BATA battery is about 50 discharged the controller provides these warnings Solid red BAT LED Minor fault type
68. e the controller with the correct firmware just out of the box firmware update NOT a new controller Major fault occurred Clear the fault previously in operation Solid red The controller detected a non recoverable fault so it Clear the fault cleared the project from memory Solid green The controller is OK None Hashing green The controller is storing or loading a project to or from nonvolatile memory Publication 1756 UMO001H EN P July 2008 If the controller has a CompactFlash card leave the card in the controller until the OK LED turns solid green 137 Appendix A X Status Indicators Notes 138 Publication 1756 UM001H EN P July 2008 Numerics 1756 HYD02 add to controller 95 1756 M02AE add to controller 95 1756 M02AS add to controller 95 1756 M03SE add to controller 95 set up 99 1756 M08SE add to controller 95 set up 99 1756 M16SE add to controller 95 set up 99 A add axes 104 add motion group 101 add motion modules 95 add SERCOS drives 97 add on instructions 77 address data 64 AOI 77 ASCII characters 40 axis check wiring 108 set up 105 axis information obtain 112 battery catalog number 127 check if low 128 estimate 1756 BA1 128 estimate 1756 BA2 130 maintain 1756 BATM 132 storage 133 build redundant system 117 C cable serial 15 cache message 53 calculate connection use 54 catalog number 12 change Publication 1756 UMO001H EN P July 2008 Index e
69. ee RSA as 125 Additional Resources 2 Ce oae tod Pes Ded t et 125 Chapter 12 Haltadueliotiaa seer ech quoti ee vr t et Perte oe s ra 127 Check If the Battery Is LOW uoo eec edoee ote aS 128 Estimate 1756 BA1 Battery Life oe se er HOD e a 128 Estimate 1756 BA2 Battery Life 1756 L6x series B controllers only et be cote mtm 130 Estimate Warning Lifecos voces uve ep CRY BRA 131 Maintain a 1756 BATM Battery Module 0000 152 Check the BAT LED Indicator ewe tk oer work tea 132 Store BAtteriES sve yee o Pe SS ded ibo s 133 Additional Resources o 658 eo du eee Ded D ae eA 133 Appendix A IotfotdelloEles diee tr tuit a EA ete MC epa Eod 135 Publication 1756 UMO001H EN P July 2008 About This Publication Who Should Use This Publication Purpose of This Manual Publication 1756 UM001H EN P July 2008 Preface Use this manual to become familiar with the ControlLogix controller and its features This version of the manual cotresponds to controller firmware tevision 17 This manual describes the necessary tasks to install configure program and operate a ControlLogix system In some cases this manual includes references to additional documentation that provides the more comprehensive details These core documents address the Logix5000 family of controllers Catalog Number Tite Publication 1756 L55Mx Logixb000Controllers Quick Start 1756 08001 oer Logix5000 Controllers Common Procedur
70. er INT 16 tag Each bit represents a station address If this controller reads a message destined for a station that has its bit set in this table it forwards the message 5 Click OK Advantage of Using DF1 Radio Modem The primary advantage of using DF1 radio modem protocol for radio modem networks is in transmission efficiency Each read write transaction command and reply requires only one transmission by the initiator to send the command and one transmission by the responder to return the reply This minimizes the number of times the radios need to key up to transmit which maximizes tadio life and minimizes radio power consumption In contrast DF1 half duplex protocol requires five transmissions for the DF1 master to complete a read write transaction with a DF1 slave three by the master and two by the slave The DF1 radio modem driver can be used in a pseudo master slave mode with any radio modems as long as the designated master node is the only node initiating MSG instructions and as long as only one MSG instruction is triggered at a time For modern serial radio modems that support full duplex data port buffering and radio transmission collision avoidance the DF1 radio modem driver can be used to set up a masterless peer to peer radio network where any node can initiate communication to any other node at any time as long as all of the nodes are within radio range so that they receive each other s transmissions Pu
71. es 1756 PM001 Programming Manual Logix5000 Controllers System Reference 1756 QR107 Logix5000 Process Control and Drives Instructions 1756 RM003 Reference Manual Logix5000 Process Control and Drives Instructions 1756 RM006 Reference Manual Logix5000 Controllers Motion Instructions 1756 RM007 To view or download manuals visit http literature rockwellautomation com To obtain a hard copy of a manual contact your local Rockwell Automation distributor or sales representative Preface 10 Publication 1756 UM001H EN P July 2008 Chapter 1 Introduction For a more flexible system use ControlLogix System Overview ControlLogix Controller 1756 1 0 Modules in the Same Chassis as the ControlLogix Controller multiple controllers in a single chassis ControlLogix System Overview This chapter provides an overview of the ControlLogix system The ControlLogix system provides sequential process motion and drive control together with communication and I O in a chassis based system A simple ControlLogix system consists of a stand alone controller and I O modules in a single chassis 1756 1 0 modules in the Same chassis as the ControlLogix Controller multiple controllers joined across networks I O from multiple platforms that is distributed in many locations and connected over multiple I O links Chassis as the EtherNet IP Link ControlNe
72. es any packets received that have a destination address other than its own with the exception of broadcast packets and passthru packets Unlike either DF1 full duplex or DF1 half duplex protocols DF1 radio modem protocol does not include ACKs NAKs ENQs or poll packets Data integrity is ensured by the CRC checksum 34 Publication 1756 UM001H EN P July 2008 Communicate over Networks Chapter 3 Using the DF1 Radio Modem The DF1 radio modem driver can be configured as the system mode driver using RSLogix 5000 version 17 or later To configure the controller for DF1 Radio Modem communication perform this procedure 1 In the Controller Organizer of RSLogix 5000 programming software right click your controller and select Properties ee B 711756 Pis e New Modul Properties Alt Enter The Controller Properties dialog ipeum 5 Controller Properties Pl SSampleProject Date Time Advanced SFC Execution Fie Redundancy Nonvolatie Memory Memory General Seti Port SystemProtocol User Protocol Majo Fauls Minor Faults Mode z Baud Rate 19200 Data Bits 8 Panty None Stop Bis 1 X Control Line No Handshake r RTS Send Delay 0 x20 ms RTS Off Delay O 20 ma DCD Wat Delay x1 sec OK Cancel Help 2 Click the System Protocol tab fe Controller Properties Example for ControlLogix controller Advanced SFCExecuton Fie Redundancy
73. et Network ControlNet bridge ControINet adapter and I O modules to the I O Configuration folder of the controller Within the I O Configuration folder organize the modules into a hierarchy of tree branch and parent child Configuring 1 0 on a ControINet Network For a typical distributed 1 0 network Local Controller Communication Module Remote 1 0 Adapter Module Device you build the 1 0 configuration in this order fea Controller cnet_example Controller Tags 2 Controller Fault Handler EI Power Up Handler E3 Tasks MainTask Cg MainProgram EI Unscheduled Programs Motion Groups 5 Ungrouped Axes 3 Trends Data Types Cj User Defined ER Strings E Predefined 4 Module Defined 23 1 0 Configuration 9 1756 Backplane 1756 410 fa 0 1756 L61 cnet_example P 1 1756 CNB E cnb1 ControlNet BJ 1 1756 CNBJE cnb1 2 1794 ACN15 C flex adapter FlexBus amp 0 1794 1A8 A inputi 1 1794 OB16 A outputi amp 2 1794 IF4I A analog 1 Add the local communication module bridge 2 Add the remote adapter for the distributed 1 0 chassis or DIN rail 3 Add the 1 0 module Additional Resources For additional information consult ControlNet Modules in Logix5000 Control Systems User Manual publication CNET UM001 62 Publication 1756 UM001H EN P July 2008 Place Configure and Monitor O Modules Chapter 5 Configure D
74. etwork Publication 1756 UMO001H EN P July 2008 65 Chapter 5 Place Configure and Monitor 1 0 Modules EtherNet IP 1 0 Considerations When you add EtherNet IP I O at runtime the EtherNet IP I O modules you add at runtime use can be added to existing rack optimized connections added to new rack optimized connections added as direct connections You can create new rack optimized connections when adding EtherNet IP I O modules at runtime you can add I O modules until you teach the limits of the communication module Module Type Pulses per TCP Second Max Connections Max 1756 ENBT 4500 1756 ENET 810 3 Series B Additional Resources 66 CIP Connected Messages Max 128 160 Connected Bridged Messages Max 128 Connected End Node Messages Max 32 Unconnected Messages Max 256 64 For additional information consult the EtherNet IP Performance Application Guide publication ENET AP001 Publication 1756 UM001H EN P July 2008 Determine When Data Is Updated Input or Output Data Place Configure and Monitor I O Modules ControlLogix controllers update date asynchronously with the execution of logic Use this flowchart to determine when a producer such as a controller input module or bridge module will send data Overview Updating Data Output n Analog or Digital Digital p gt Analog o
75. f routines and tags Unlike a program an equipment phase runs by a state model and lets you do one activity State model Astate model divides the operating cycle of your equipment into a series of states Fach state is an instant in the operation of the equipment the actions or conditions of the equipment at a given time The state model of an equipment phase resembles that of the S88 and PackML state models State machine An equipment phase includes an embedded state machine that calls the main routine state routine for an acting state manages the transitions between states with minimal coding makes sure that the equipment goes from state to state along an allowable path PHASE tag When you add an equipment phase RSLogix 5000 programming software makes a tag for the equipment phase The Publication 1756 UMO001H EN P July 2008 tag uses the PHASE data type 87 Chapter7 Configure PhaseManager PhaseManager Overview A PHASE tag gives you the status of an equipment phase a Controller Name Data Type 8m Controller Tags Add Water PHASE Add_Water State DINT zz Tasks Add Water Running BOOL N fia MainTask _ Add Water Holding BOOL m Add Water Reestarting BOOL An equipment phase directs one activity of your equipment E Add Water Phase A state model divides the activity into a series of states C LOC XC OOS i Mix Phase f Running
76. figure communication devices Provide diagnostics Establish communication between devices The 1756 CNB and 1756 CNBR ControlNet communication modules support messaging produced consumed tags and distributed I O share a common application layer with DeviceNet and EtherNet IP networks require no routing tables support the use of coax and fiber repeaters for isolation and increased distance support redundant media 1756 CNBR module only In this example the controllers produce and consume tags the controllers initiate MSG instructions that send and receive data or configure devices the personal computer uploads and downloads projects to the controllers the personal computer configures devices on a ControlNet network and it can configure the netwotk itself 26 Publication 1756 UM001H EN P July 2008 Communicate over Networks Chapter 3 ControlNet Network Overview Workstation Distributed 1 0 PowerFlex 700S AC Drive with DriveLogix CompactLogix Controller as an adapter with 1756 1 0 Modules P ControlNet Network FlexLogix Controller with Fup paned EA E Su wi odules 1788 CNC Card Hi t PanelView Terminal A K i FEE 1734 ACNR Adapter with FEES 1734 1 0 Modules PLC 5 40C Controller E n Connections over a ControlNet Network
77. g 4 In the Speed box type the number of revolutions per second to which you want to limit your axis during its tuning 5 Click Start Tuning 6 Click OK Additional Resources Por additional information consult the Logix5000 Motion Module User Manual publication 1756 UM006 Publication 1756 UMO001H EN P July 2008 111 Chapter 8 Develop Motion Applications Obtain Axis Information You can obtain axis information through any one of several methods To obtain axis information take any one or all of these steps Obtaining Axis Information Use the Axis Properties dialog window to configure the axis fs RSLogix 5000 My Controller in Inhibit_Axis ACD 1 756 L60MO3SE MainProgram Inhibit Axes DAR Ef File Edit View Search Logic Communications Tools Window Help i 8 X losa S slale oe oos z mE T ESI T me aal No Forces l OK M BAT No Edits amp m jn z 7 Pecar 3 a 4 a avorites Bit Timer Counter nput Output ompare Compute Ma zi 53 Controller My Controller ij E s 3 Controller Tags 3 Controller Fault Handler 3 Power Up Handler My Axis X Llninhibit Cmd SSY H E Tasks Te Pm Value o ny lass Name Fan 88 v pts G Instance Name My Axis X A Y_otion_Sroup Attribute Name Inhibit amp xis X My Axis X Source Zero i My Axis Y 0 H E Ungrouped Axes v Type AXIS SERVO DRIVE Description My_Axis_X In
78. hbutton on and the axis off My Axis X ServoActionStatus off then The MSO instruction turns on the axis Initialiee Pushbutton My Axis X Servo amp ctionStatus p Y MSO Motion Servo On Axis My Axis X E Motion Control My Axis X n If Home Pushbutton on and the axis hasn t been homed My Axis X AxisHomedStatus off then The MAH instruction homes the axis Home Pushbutton My Axis X AxisHomedStatus E 3 MAH Motion Axis Home Axis My Axis X E Motion Control My Axis X Home Publication 1756 UMO001H EN P July 2008 113 Chapter 8 Develop Motion Applications If Jog_Pushbutton on and the axis on My_Axis_X ServoActionStatus on then The MAJ instruction jogs the axis forward at 8 units second Jog Pushbutton My Axis X Servo amp ctionStatus MAJ E d Motion Axis Jog EN Axis My Axis X E CONS Motion Control My Axis X Jog ER2 Direction My Axis X Jog Direction P3 oe Speed My_Axis_X_SetUp ManuallogSpeed amp 0e Speed Units Units per sec More gt gt If Jog_Pushbutton off then The MAS instruction stops the axis at 100 units second2 Make sure that Change Decel is Yes Otherwise the axis decelerates at its maximum speed Jog_Pushbutton MAS Motion Axis Stop EN Axis My Axis X E PCDN2 Motion Control My Axis X MAS ER2 Stop Type Jog IP25 Change Decel Yes PCo Decel Rate My Axis X Setlp Ma
79. hibitStatus My_Axis_X SefvoActionStatus My Axis X OK Axis State di i _ _ Drive Name My_Axis_X Node 1 Axis Fault he v Use a Get System Value GSV instruction or Set System Value SSV Use the Quick View pane to see the state instruction to read or change the configuration at run time and faults of an axis Use the tag of the axis for status and faults 112 Publication 1756 UMO001H EN P July 2008 Develop Motion Applications Chapter 8 Program Motion Control The controller gives you a set of motion control instructions for your axes and uses these instructions just like the rest of the Logix5000 instructions You can program motion control in these programming languages Ladder Diagram LD Structured Text ST Sequential Function Chart SFC each motion instruction works on one or more axes each motion instruction needs a motion control tag The tag uses a MOTION INSTRUCTION data type and stores the instruction s information status Motion Control Instruction MSO Motion Servo On N35 Axis mt No Motion Control Tag Motion control R Use the tag for the motion control operand of motion instruction only once Unintended operation of the control variables may happen if you reuse of the same motion control tag in other instructions Example Here s an example of a simple ladder diagram that homes jogs and moves an axis If Initialize_Pus
80. hours 0 C 32 F 24 days 48 days 17 30 hours 1756 L55M16 60 C 140 F 15 days 30 days 23 18 hours 25 C 77 F 13 days 27 days 17 16 hours 0 C 32 F 6 days 12 days 36 7 hours 1756 L55M22 Use the values for the 1756 L55M13 controller 1756 L55M23 1756 L55M24 Use the values for the 1756 L55M14 controller 1756 L63 60 C 140 F 22 days 43 days 23 6 hours 25 C 77 F 21 days 42 days 17 28 hours 0 C 32 F 14 days 28 days 17 2 5 days Publication 1756 UMO001H EN P July 2008 129 Chapter 12 Maintain the Battery Worst case Estimates of 1756 BATA Battery Life Controller Temperature Time Before BAT LED Turns On TimeafterBATLEDturson Power off 100 Power off 50 Yearly ann rowers NDN decrease 1756 L55M12 60 C 140 F 190 days 396 days 11 190 days 1756 155M13 25 C 77 F 299 days 562 days 5 299 days 0 C 32 F 268 days 562 days 6 268 days 1756 L55M14 60 C 140 F 130 days 270 days 11 139 days 25 C 77 F 213 days 391 days 5 228 days 0 C 32 F 180 days 381 days 6 193 days 1756 L55M16 60 C 140 F 71 days 160 days 1396 76 days 25 C 77 F 133 days 253 days 5 142 days 0 C 32 F 105 days 220 days 6 112 days 1756 L55M22 Use the values for the 1756 L55M13 controller 1756 L55M23 1756 L55M24 Use the values for the 1756 L55M14 controller 1756 L63 60 C 14
81. ht click the SERCOS network and select New Module IO Configuration 9 1756 Backplane 1756 417 fa 0 1756 L55 Kinetix600 f 13 1756 MossE Ma st as EE nevra h NI The Select Module dialog appears L Select Module Description Vendor 1394C SJTOS D 1394 460VAC SERCOS System Module SKW PS Allen Bradley 1394C SJT10 D 1394 460VAC SERCOS System Module 10kW PS Allen Bradley 1394C 5 T22 D 1394 460VAC SERCOS System Module 22kW PS Allen Bradley Kinetix 6000 230VAC IAM 3kW P5 94 Cont 17A Peak Allen Bradley 2094 ACOS MP5 Kinetix 6000 230VAC IAM 3KW PS 5A Cont 10A Peak Allen Bradley 2094 ACOS MO2 Kinetix 6000 230VAC IAM 6KW PS 15A Cont 304 Peak Allen Bradley 2094 AC16 M03 Kinetix 6000 230VAC IAM 15kW PS 244 Cont 494P Allen Bradley 2U934 AC32 IMUS Kinetix amp UUU Z3UVAC 1AM Z3kw PS 49A Cont YAP Allen Bradley ZUJ4 AMUI Kinetix 6UUU Z3UVAC AM YA Cont 1 A Peak Allen Bradley 2094 AMOZ Kinetix 6000 230vAC AM 15A Cont 308 Peak Allen Bradley 2094 AM03 Kinetix 6000 230 AC AM 24A Cont 498 Peak Allen Bradley 2094 AMOS Kir iix 6000 230VAC AM 49A Cuil 98A Peck Aller Bradley 5 gt Find Add Favorite BvCategoy ByVendor_ _ Favorites OK Cancel Help 2 Double click Other 3 Select your drive Choose from these SERCOS interface drives 1394 Kinetix 6000 Ultra3000 8720MC Click OK 97 Chapter 8 Develop Motion Applications Th
82. istributed 1 0 On To communicate with the I O modules over a DeviceNet network add the DeviceNet bridge to the I O Configuration folder of the controller You a DeviceNet Network define a scanlist within the DeviceNet scanner to communicate data between devices and the controller Configuring Distributed 1 0 on a DeviceNet Network For a typical distributed 1 0 network Single Network Controller Scanner Device Device Device Device Device Several Smaller Distributed Networks subnets Controller Linking Linking Device Device Device Device Device Device Device Device you build the 1 0 configuration in this order zc Controller dnet_example A Controller Tags Controller Fault Handler Power Up Handler 3 Tasks MainTask CE MainProgram EI Unscheduled Programs 3 Motion Groups 5 Ungrouped Axes C3 Trends Data Types Cg User Defined Cg Strings E Predefined C Module Defined 3 1 0 Configuration amp 1756 Backplane 1756 410 fa 0 1756 L61 dnet_example BJ 1 1756 DNB dnb1 zz DeviceNet Add the local communication module bridge Additional Resources For additional information consult DeviceNet Communication Modules in Logix5000 Control Systems User Manual publication DNET UM004 Publicati
83. ith a Specific 1 0 Module If communication times out with a device module in the I O configuration of the controller the controller produces a fault code for the module The GSV instruction gets the fault code for Io Module and stores it in the Module_Status tag If Module Status is any value other than 4 the controller is not communicating with the module This rung is used to check the status of an I O connection We look at the entry status of the connection if the value returned is anything other than 4 The connection is not functioning properly When an error is detected the error code and and info is trapped on a one shot basis This is becuase the controller will try and re establish the connect and when it does this you will loss the true error SV BTD Get System Value Bit Field Distribute Class Name MODLILE Source Module Status Instance Name lo Module 0 Attribute Name EntryStatus Source Bit 12 Dest Module_Status Dest Module_Status_Easy 0 Dest Bit Lenath 4 EQ Check ONS SY Not Equal ONS Get System Value Source 4 Module_Status_Easy Class Name MODULE 0 Instance Name lo_Module Source B 4 Attribute Name FaultCode Dest Module Fault Code Get System Value Class Name MODULE Instance Name lo Module Attribute Name Fauttinfo Dest Module Fault Info Module Connection Error QU Module_Connection_Error Equal Source amp Module Status Easy Source B 4 Publication 1756 UMO001H EN P July 2008 81
84. ity is assumed by Rockwell Automation Inc with respect to use of information circuits equipment or software described in this manual Reproduction of the contents of this manual in whole or in part without written permission of Rockwell Automation Inc is prohibited Throughout this manual when necessary we use notes to make you aware of safety considerations Identifies information about practices or circumstances that can cause an explosion in a hazardous environment which may lead to personal injury or death property damage or economic loss IMPORTANT Identifies information that is critical for successful application and understanding of the product Identifies information about practices or circumstances that can lead to personal injury or death property damage or economic loss Attentions help you identify a hazard avoid a hazard and recognize the consequence ATTENTION INA awa Labels may be on or inside the equipment for example a drive or motor to alert people that dangerous voltage may be present FITLTETLVZUCDE Labels may be on or inside the equipment for example a drive or motor to alert people that surfaces may reach dangerous temperatures gt gt eiie Allen Bradley ControlLogix Logix5000 Rockwell Automation RSLogix 5000 and TechConnect are trademarks of Rockwell Automation Inc Trademarks not belonging to Rockwell Automation are property of their respective companies I
85. ix5550 1756 BA1 ControlLogix5555 ControlLogix5560M03SE ControlLogix5561 A 1756 BA1 ControlLogix5562 ControlLogix5563 ControlLogix5561 B 1756 BA2 ControlLogix5562 ControlLogix5563 ControlLogix5564 ControlLogix5565 Topic Page Check If the Battery Is Low 128 Estimate 1756 BA1 Battery Life 128 Estimate 1756 BA2 Battery Life 1756 L6x series B controllers 130 only Maintain a 1756 BATM Battery Module 132 Store Batteries 133 Publication 1756 UMO001H EN P July 2008 127 Chapter 12 Maintain the Battery Check If the Battery Is Low BAT LED Estimate 1756 BA1 Battery Life 128 When the battery is about 95 discharged the controller gives these low battery warnings Solid red BAT LED Minor fault type 10 code 10 To prevent possible battery leakage even if the BAT LED is off replace a battery according to this schedule 1 in below the chassis is 0 35 C 32 95 F 3 years 36 40 C 96 8 104 F 3 years 41 45 C 105 8 113 F 2 years 46 50 C 114 8 122 F 16 months 51 55 C 123 8 131 F 11 months 56 60 C 132 8 140 F 8 months To estimate how long a 1756 BA1 battery will support controller memory on 1756 L55Mx all series and 1756 L6x series A controllers perform this procedure 1 Determine the temperature 2 54 cm 1 in below the chassis 2 Determine the weekly percentage of time that the contro
86. k 61 Configure Distributed I O on a ControlNet Network 62 Configure Distributed I O on a DeviceNet Network 63 Address I O Data 64 Add 1756 1 0 at Runtime 65 Determine When Data Is Updated 67 Reconfigure an 1 0 Module 68 When selecting 1756 I O modules select specialty I O modules when appropriate Some modules have field side diagnostics electronic fusing or individually isolated inputs outputs 1756 remote terminal blocks RTBs or 1492 wiring systems for the I O modules 1492 PanelConnect modules and cables to connect input modules to sensors Additional Resources Por additional information consult the ControlLogix Selection Guide publication 1756 SG001 Your choice of 1756 chassis determines how many local I O modules you can use You can fill your chassis slots with any combination of controllers communication modules and I O modules 57 Chapter 5 58 Place Configure and Monitor 1 0 Modules Available Chassis Slots Chassis Available Slots 1756 A4 4 1756 A7 7 1756 A10 10 1756 A13 13 1756 A17 17 For empty slots use the 1756 N2 slot filler module The ControlLogix controller also supports distributed remote I O via these networks EtherNet IP ControlNet DeviceNet Universal remote I O Additional Resources Por additional information consult these publications ControlLogix Digital I O Modules User Manual publication
87. kup Tune Dynamics Gains Output Limits Offset FaukActions Taa General Motion Planner Units Drive Motor Motor Feedback Aux Feedback Conversion Pnsilinning Made Conversion Constant 200000 0 Based on 200000 Counts Motor Rev oa 5 Drive Counts Unwind Position Unwind 200000 Based on 200000 Counts Motor Rev 9 From the Positioning Mode pull down menu choose rotary or linear 10 In the Conversion Constant box type the number of drive counts per rotary or linear revolution 11 For a rotary axis only in the Position Unwind box type the number of feedback counts needed to automatically unwind the axis 106 Publication 1756 UM001H EN P July 2008 Develop Motion Applications Chapter 8 12 Click the Homing tab Axis Properties axis x BE Dynamics Gains Output Limis Offset FaukActins Tag General MotionPlanner Units Servo Feedback Conversion Homing Hookup Tune Mode Active E Position 0 0 Revs offset DO Res Sequence Maker o dj Active Home Sequence Group Direction Forward Bi directional Speed 0 625 Revs s Retum Speed 0 3125 Revs s 13 From the Sequence pull down menu choose one of these types of homing sequences Immediate Switch Marker Switch Marker 14 Within Active Home Sequence Group in the Speed and Return Speed boxes type the homing speeds 15 Click OK Publication 1756 UMO001H EN P July 20
88. l tab fo Controller Properties PLSSampleProject Date Time Advanced SFC Execution Fie Redundancy Norvelatile Memory Memo General SerialPort System Protocol User Protocol Maice Fauts Mince Fouts ar Ence Detechon Protocot Ce crc Max Station Address 31 1 Token Hold Factor ae me om or 6 From the Protocol pull down menu choose DH485 7 Specify the DH485 settings Characteristic Description Station Address Specifies the node address of the 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 it receives the token Enter a value between 1 4 The default is 1 Maximum Station Specifies the maximum node address of all the devices on the DH 485 network Select a number 1 31 Address decimal inclusive 44 To optimize network performance make sure the maximum node address is the highest node being used on the network that all the devices on the same DH 485 network have the same maximum node address 8 Click OK Publication 1756 UM001H EN P July 2008 Communicate over Networks Chapter 3
89. l version of RSLogix 5000 software for redundancy Only controllers 1756 CNB and 1756 CNBR modules 1756 ENBT modules and one 1757 SRM redundancy module can reside in a redundant controller chassis As many as two EtherNet IP modules can reside in a redundant chassis As many as five communication modules can reside in a redundant chassis such as two EtherNet IP modules and three ControlNet modules To connect to other networks bridge through another ControlLogix chassis Use a separate network for HMI and 1 0 communication 1 0 modules All 1 0 is remote from the redundant controller chassis Redundant power supplies The 1756 PA75R and 1756 PB75R redundant power supplies provide reliable chassis power ControlNet Considerations You can have as many as five ControlNet communication modules in a redundant chassis You can use 1756 CNB and 1756 CNBR Controlnet in Redundant Systems Modules 118 You must have at least two ControlNet nodes external to the redundant controller chassis to avoid timeouts on switchover The lowest ControlNet node must be outside the redundant controller chassis Publication 1756 UM001H EN P July 2008 EtherNet IP Considerations in Redundant Systems Redundancy and Scan Time Publication 1756 UMO001H EN P July 2008 Configure Redundancy Chapter 9 You can have as many as two EtherNet IP modules in the redundant chassis You can use 1756 ENBT EtherNet IP and 1756 EWEB E
90. lease contact your local Rockwell Automation representative for any States technical support issues New Product Satisfaction Return Rockwell Automation tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning and needs to be returned follow these procedures United States Contact your distributor You must provide a Customer Support case number call the phone number above to obtain one to your distributor in order to complete the return process Outside United Please contact your local Rockwell Automation representative for the States return procedure 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 1756 UM001H EN P July 2008 Supersedes Publication 1756 UM001G EN P January 2007 Copyright 2008 Rockwell Automation Inc All rights reserved Printed in the U S A
91. ller is turned on EXAMPLE If a controller is off either 8 hr day during a 5 day work week all day Saturday and Sunday Then the controller is off 5296 of the time Total hours per week 7 x 24 168 hours Total off hours per week 5 days x 8 hr day Saturday Sunday 88 hours Percentage off time 88 168 52 3 Determine the estimated worst case battery life before and after the BAT LED turns on For each year of battery life decrease the time before the BAT LED turns on by the percentage that is shown in the table Publication 1756 UM001H EN P July 2008 Maintain the Battery Chapter 12 Do not decrease the time after the BAT LED turns on IMPORTANT If the BAT LED turns on when you apply power to the controller the remaining battery life may be less than this table indicates Some of the battery life may have been used up while the controller was off and unable to turn on the BAT LED Worst case Estimates of 1756 BA1 Battery Life Controller Temperature Time Before BAT LED Turns On Time after BAT LED turns on Power off 100 Power off 50 Yearly ame Powers ean decrease 1756 L55M12 60 C 140 F 57 days 110 days 23 69 hours Mapes 25 C 77 F 63 days 123 days 17 76 hours 0 C 32 F 60 days 118 days 17 73 hours 1756 L55M14 60 C 140 F 29 days 57 days 23 35 hours 25 C 77 F 30 days 61 days 17 37
92. ly 2008 27 Chapter3 Communicate over Networks DeviceNet Network Communication 28 The 1756 CNB and 1756 CNBR communication modules support 64 CIP connections over a ControlNet network However for optimal performance only configure 48 connections for each module Additional Resources Por additional information consult these publications ControlNet Modules in Logix5000 Control Systems User Manual publication CNET UMO001 Logix5000 Controllers Design Guidelines Reference Manual publication 1756 RM094 The DeviceNet network uses the Common Industrial Protocol CIP to provide the control configuration and data collection capabilities for industrial devices The DeviceNet network uses the proven Controller Area Network CAN technology which lowers installation costs and decreases installation time and costly downtime A DeviceNet network provides access to the intelligence present in your devices by letting you connect devices directly to plant floor controllers without having to hard wire each device into an I O module DeviceNet communication requires a 1756 DNB DeviceNet communication module The DeviceNet network uses the Common Industrial Protocol CIP to provide the control configuration and data collection capabilities for industrial devices Functions Required Module Control 1 0 modules 1756 DNB Require an adapter for distributed 1 0 on DeviceNet links Communicate with other DeviceNet devices me
93. m and mail or fax it back to us or email us at RADocumentComments ra rockwell com Pub Title Type ControlLogix Controllers Cat No 1756 L55Mx 1756 L6x Pub No 1756 UMOO1H EN P Pub Date July 2008 PartNo NA Not shipped with 1756 L60M03SE Product Please complete the sections below Where applicable rank the feature 1 needs improvement 2 satisfactory and 3 outstanding Overall Usefulness 1 2 3 How can we make this publication more useful for you 2 3 Can we add more information to help you Completeness all necessary information procedure step illustration feature is provided My example guideline other explanation definition Technical Accuracy 1 Zn 3 Can we be more accurate all provided information is correct text illustration Clarity 1 2 3 How can we make things clearer all provided information is easy to understand Other Comments You can add additional comments on the back of this form Your Name Your Title Function Would you like us to contact you regarding your comments Location Phone No there is no need to contact me Yes please call me Yes please email me at Yes please contact me via Return this form to Rockwell Automation Technical Communications 1 Allen Bradley Dr Mayfield Hts OH 44124 9705 Fax 440 646 3525 Email RADocumentComments ra rockwell com Publication ClG C0521D
94. modules Add one 1757 SRM redundancy module Set up a second chassis that is identical to the first chassis Connect the 1757 SRM redundancy modules in both chassis Add I O modules operator interfaces and other devices to the ControlNet network Redundant System Primary Controller Secondary Controller Publication 1756 UM001H EN P July 2008 HMI Device Remote Controller 117 Chapter9 Configure Redundancy Items in Primary and Secondary Chassis ControlLogix controller Communication modules System Considerations Consideration As of firmware revision 13 you can use these combinations of ControlLogix controllers in a redundant chassis one 1756 55 controller two 1756 L55 controllers one 1756 L6x controller When configured for redundancy the secondary controller automatically receives and buffers data A redundant controller uses twice as much data memory and I O memory space as a nonredundant controller The controllers synchronize data transfers to support a bumpless switchover A redundant controller has a significantly longer scan time than a nonredundant controller The scan time can affect high speed processes requiring fast lt 50 ms program scans Minimize the scan time impact by packing data into arrays and structures so the data transfer from primary to secondary controller is more efficient You do not need a specia
95. mples only and muse be ured with case uses to the Disclaimer at the end of thir document and to the Find Uner License Ageeemenz RULA incuded is the R3Logoc S000 Releane Notes foe additonal infomation Foe addition sesana vodeng wth sample pioen in general plear contact pour Techencal Support segeeserzazve for specific zuestionm relates 1o vendor v sample piara please conti the parnookat verdos foc amneunce Remember thet as with any sew pocggam yos thon tea the eample peogras to make orrtan diat if weeks weh pour applxaaon bescer actually e piemesneg itn pour scum operations Mewe irtee te te snc vecti Woskng With Sample Proper Se ir oemauen ans recocsnendanoer os how so effectreety une there sample peces Working With Sample Projects Imponane Hefore you begin wing a tampir pocjoct make a copy of she pecyect save st with anew name asd make any edite you need to make to dus enamed pacyect By dong thet you ase matang certam that you have a backup copy of the anginal sample project that will be poeserved for fume sse SSLogeeS000 sample projects may include a number of components that you wil need to copy mdachaby in coder for the sample piect components to functen propesy a your appicaten These Say incinde but are not berated oc Y pou are opang ines an eenig ponyen confir may occu with omp aene thar deeady exis ces the location oc tre of modules does not match the location anramed in the sample poea n that case yon may need to sezam
96. n PSC Signal a phase that the state routine is complete and to proceed to the next state PCMD Change the state or substate of a phase PFL Signal a failure for a phase PCLF Clear the failure code of a phase PXRO Initiate communication with RSBizWare Batch software PRNP Clear the NewInputParameters bit of a phase PPD Set up breakpoints within the logic of a phase PATT Take ownership of a phase to either prevent another program or RSBizWare Batch software from commanding a phase make sure another program or RSBizWare Batch software does not already own a phase PDET Relinquish ownership of a phase POVR Override a command Publication 1756 UM001H EN P July 2008 Chapter 8 Introduction Develop Motion Applications This chapter explains how to configure a motion control program Topic Page Make the Controller the CST Master 94 Add the Motion Modules 95 Add SERCOS Interface Drives 97 Set Up Each SERCOS Interface Module 99 Add the Motion Group 101 Add Your Axes 104 Set Up Each Axis 105 Check the Wiring of Each Drive 108 Tune Each Axis 110 Obtain Axis Information 112 Program Motion Control 113 Overview of Motion Control Configuration 1756 Analog Motion Module Drive Position Velocity Motor l C5 Feedback Drive RSLogix 5000 Programming Position Velocity Software ControlLogix Controller Motor l CO Feedback Integrated Program Execution A
97. nfigure and Monitor 1 0 Modules Connection Type Direct 1 0 Connections A Logix5000 system uses connections to transmit I O data Description A direct connection is a real time data transfer link between the controller and an 1 0 module The controller maintains and monitors the connection between the controller and the 1 0 module Any break in the connection such as a module fault or the removal of a module while under power causes the controller to set fault status bits in the data area associated with the module Typically analog I O modules diagnostic I O modules and specialty modules require direct connections Rack optimized For digital 1 0 modules you can select rack optimized communication A rack optimized connection consolidates connection usage between the controller and all of the digital 1 0 modules on a rack or DIN rail Rather than having individual direct connections for each I O module there is one connection for the entire rack or DIN rail 60 Additional Resources For additional information consult these publications Logix5000 Controllers Common Procedures Programming Manual publication 1756 PM001 Logix5000 Controllers Design Considerations Reference Manual publication 1756 RM094 Publication 1756 UM001H EN P July 2008 Place Configure and Monitor I O Modules Chapter 5 Configure Distributed 1 0 On To communicate with distributed I O modules over an EtherNet IP network an E
98. ng your code and whatever else it is doing and runs the motion planner Add only one motion group for the project RSLogix 5000 software does not let you add more than one motion group To add a motion group to set up the motion planner perform this procedure 1 Choose your coarse update period IMPORTANT The coarse update period is the interval between updating your axes positions and scanning your code a Set the coarse update period to 10 ms b Leave at least half the controller s time for the scanning of all your code c Set the coarse update period to a multiple of the cycle time of the motion module Example If the cycle time is 2 ms set the coarse update period to 8 ms 10 ms 12 ms and so on 2 In RSLogix 5000 programming software right click Motion Groups and select New Motion Group nme ad Ur New k Group Add O Data T Ep Us Cg Sti fam ad Publication 1756 UMO001H EN P July 2008 101 Chapter 8 Develop Motion Applications The New Tag dialog appears Description Cancel Help Usage mm i Type Base v Connectior Alias For Data Type M OTION GROUP Bl Scope g My Controller Style 7 M Open MOTION_GROUP Configuration 3 In the Name box enter the tag name 4 From the Data Type pull down menu choose MOTION_GROUP 5 Click OK The Motion Group Wizard dialog appears Motion Group Wizard My_Motion_Group Axis Assignment Unassigned
99. nication and 1 0 Interlock Data Tag Type Produced Consumed 52 Each consumed tag requires one connection for the controller that is consuming the tag The controller s communication device uses one connection for each consumer For two controllers to share produced or consumed tags both must be attached to the same network You cannot bridge produced and consumed tags over two networks The number of available connections limits the number of tags that can be produced or consumed If the controller uses all of its connections for I O and communication devices no connections are left for produced and consumed tags Available Connections Device Supported Connections ControlLogix controller 250 1756 ENBT module 128 1756 EWEB module 1756 CNB module 64 SATa CNBR Toig 48 is the recommended maximum Additional Resources For additional information consult these publications Logix5000 Controllers Common Procedures Programming Manual publication 1756 PM001 Logix5000 Controllers Design Considerations Reference Manual publication 1756 RM094 Publication 1756 UM001H EN P July 2008 Manage Controller Communication Chapter 4 Send and Receive Messages Publication 1756 UMO001H EN P July 2008 Messages transfer data to other devices such as other controllers or operator interfaces Some messages use unscheduled connections to send or receive data These connected messages can leave the
100. ntroduction Updated Information Publication 1756 UM001H EN P July 2008 Summary of Changes The release of this document contains new and updated information To find new and updated information look for change bars as shown next to this paragraph This document contains the following changes Topic Page New information about the 1756 L65 controller Throughout the manual New information about the 1784 CF128 CompactFlash card Throughout the manual IMPORTANT As you use this manual you should consider the following e 1756 L55Mx controllers are only supported with RSLogix 5000 version 16 and earlier o e 1756 L61 1756 L62 1756 L63 and 1756 L64 controllers are supported with RSLogix 5000 version 17 and earlier e 1756 L65 controllers are supported with RSLogix 5000 version 17 and greater Summary of Changes Notes 4 Publication 1756 UM001H EN P July 2008 Preface ControlLogix System Overview Directly Connect to the Controller via the Serial Port Communicate over Networks Publication 1756 UM001H EN P July 2008 Table of Contents About This Publication lees 9 Who Should Use This Publication lees 9 P rpose of This Manuals ous P Pei Pera RII BEP SPER OCIS 9 Chapter 1 Tntto ductiOB tin tino sede ted toad dh eta vod etui oed s 11 Desin roo iuc ts Qut debit Sete Cebu icd ous Shu Sarita deg i pt 13 Install ETatdwWate 5 3 ere Mfr e cm ao ore PIE S 13 Chapte
101. nuallogDecel 100 0 Decel Units Units per sec2 If Move Command on and the axis on My Axis X ServoActionStatus on then The MAM instruction moves the axis The axis moves to the position of 10 units at 1 unit second Move Command My Axis X Servo amp ctionStatus AM Motion Axis Move EN Axis My Axis x E EDN Motion Control My Axis X Move ER2 Move Type 0 P3 l Position 10 Speed My Axis X Setllp AutoSpeedCommand 10 Speed Units Units per sec Additional Resources For additional information consult these publications Logix5000 Controllers Common Procedures Programming Manual publication 1756 PM001 Logix5000 Controllers Motion Instructions Reference Manual publication 1756 RM007 Logix5000 Controllers General Instructions Reference Manual publication 1756 RM003 114 Publication 1756 UM001H EN P July 2008 Chapter 9 Configure Redundancy Introduction This chapter explains how the ControlLogix redundancy system uses an identical pair of ControlLogix chassis to keep your machine or process running if a problem occurs with any equipment in a redundant chassis Topic Page ControlLogix Redundancy Overview 115 Build a Redundant System 117 ControlNet Considerations in Redundant Systems 118 Redundancy and Scan Time 119 Minimum System Requirements 120 Additional Resources Por additional information consult the ControlLogix Redundancy System User Manua publication
102. olNet network direct connection 1 Remote EtherNet IP communication module 1 0 configured as direct connection none 0 or 1 0 configured as rack optimized connection 1 Remote I O module over a EtherNet IP network direct connection 1 Remote device over a DeviceNet network accounted for in rack optimized connection for local 1756 DNB 0 Other remote communication adapter Produced tag Each consumer Consumed tag Message depending on type Block transfer message Total Publication 1756 UMO001H EN P July 2008 55 Chapter4 Manage Controller Communication Connections Example In this example system the 1756 ControlLogix controller controls local digital I O modules in the same chassis controls remote I O devices on a DeviceNet network sends and receives messages to and from a CompactLogix controller on an EtherNet IP network produces one tag that the 1794 FlexLogix controller consumes is programmed via RSLogix 5000 programming software Redistation Series 9000 Photoeye logo i sea 1769 ADN Adapter with Compact 1 0 Modules DeviceNet Network
103. on 1756 UMO001H EN P July 2008 63 Chapterb Place Configure and Monitor 1 0 Modules Address 1 0 Data I O information is presented as a set of tags Each tag uses a structure of data The structure depends on the specific features of the I O module The name of the tags is based on the location of the I O module in the system An I O address follows this format Location Slot Type Member SubMember jr te Optional Where Definition Location Network location LOCAL same chassis or DIN rail as the controller ADAPTER NAME identifies remote communication adapter or bridge module Slot Slot number of O module in its chassis or DIN rail Type Type of data input 0 output C configuration S status Member Specific data from the I O module depends on what type of data the module can store For a digital module a Data member usually stores the input or output bit values For an analog module a Channel member CH usually stores the data for a channel SubMember Specific data related to a Member Bit Specific point on a digital 1 0 module depends on the size of the I O module 0 31 for a 32 point module 64 Publication 1756 UM001H EN P July 2008 Place Configure and Monitor I O Modules Chapter 5 Add 1756 0 at Runtime With RSLogix 5000 programming software version 16 you can only add 1756 I O modules to the C
104. ons Access devices directly via an OPC server Connect via low speed serial H1 connections 1788 CN2FF Bridge a ControlNet network to a Foundation Fieldbus Support redundant ControlNet media Foundation Fieldbus distributes and executes control in the device The Foundation Fieldbus linking device bridges from an Ethernet IP network to an H1 connection accepts either HSE or EtherNet IP messages and converts them to the H1 protocol Foundation Fieldbus Overview ControlLogix Controller with a 1756 ENBT Module RSFieldbus 24V dc 1757 FFLD Linking Device Power Field Device Additional Resources For additional information consult these devices RSFieldbus User Manual publication RSFBUS UM001 Foundation Fieldbus Linking Device User Manual publication 1757 UM010 49 Chapter3 Communicate over Networks HART Highway Addressable Remote Transducer Protocol Functions Acquire data or control application with slow update requirements such as a tank farm Does not require external hardware to access HART signal Does not provide a direct connection to asset management software HART is an open protocol designed for process control instrumentation Required Device Prosoft interface MVI56 HART Contain analog and HART in one module Does not require external hardware to access HART signal Transmit HART
105. ontroller Organizer at runtime can remotely add the 1756 I O modules to the local chassis via the unscheduled portion of a ControlNet network can remotely add the 1756 I O modules to the local chassis via the unscheduled portion of an EtherNet IP netwotk ControlNet 1 0 Considerations When you add ControlNet I O at runtime remember that the ControINet I O modules you add can be added to existing rack optimized connections or added as direct connections You cannot create new rack optimized connections when adding ControlNet I O modules at runtime disable the Change of State COS feature on digital input modules because it can cause inputs to be sent mote quickly than the RPI dedicate one ControlNet network to I O communication only On the dedicated I O network make sure there is no HMI traffic no MSG traffic no programming workstations RPIs faster than 25 ms for unscheduled modules will overload the 1756 CNB or 1756 CNBR communication module so use a NUT if 10 ms or more keep the SMAX and UMAX values as small as possible you can add I O modules until you reach 75 utilization of the 1756 CNB or 1756 CNBR communication module a utilization increase of 1 4 for each I O module you add depending on the RPI 48 connections on the 1756 CNB or 1756 CNBR communication module lt 350 000 bytes as the remaining unscheduled bandwidth on the ControlNet n
106. or protocol processing Add On Instructions With version 16 of RSLogix 5000 programming software you can design and configure sets of commonly used instructions to increase project consistency Similar to the built in instructions contained in Logix5000 controllers these instructions you create are called Add On Instructions Add On Instructions reuse common control algorithms With them you can ease maintenance by animating logic for a single instance protect intellectual property with locking instructions reduce documentation development time You can use Add On Instructions across multiple projects You can define your instructions obtain them from somebody else ot copy them from another project 71 Chapter 6 Develop Applications 78 Once defined in a project Add On Instructions behave similarly to the built in instructions in Logix5000 controllers They appear on the instruction tool bar for easy access as do internal RSLogix 5000 software instructions Save Time With Add On Instructions you can combine your most commonly used logic into sets of reusable instructions You save time when you create instructions for your projects and then share them with others Add On Instructions increase project consistency since commonly used algorithms all work in the same manner regardless of who implements the project Use Standard Editors You create Add On Instructions by using one of three RSLogix 5000 sof
107. port information data exchange and control applications The EtherNet IP network also uses commercial off the shelf Ethernet components and physical media providing you with a cost effective plant floor solution For EtherNet IP network communication you have several communication modules from which to choose EtherNet IP Communication Modules Functions Control 1 0 modules Require an adapter for distributed 1 0 on EtherNet IP links Communicate with other EtherNet IP devices messages Share data with other Logix5000 controllers produce consume Bridge EtherNet IP links to route messages to devices on other networks Required Module 1756 ENBT Require remote access via Internet browser to tags in a local ControlLogix controller Communicate with other EtherNet IP devices messages BridgesEtherNet IP links to route messages to devices on other networks Does not support 1 0 or produced consumed tags 1756 EWEB 22 Publication 1756 UM001H EN P July 2008 Publication 1756 UMO001H EN P July 2008 Communicate over Networks Chapter 3 Required Software for EtherNet IP Communication Software Functions Requirement RSLogix 5000 Configure ControlLogix projects Yes Define EtherNet IP communication RSLogix 5000 Assign IP addresses to devices on an BOOTP DHCP Utility EtherNet IP network RSNetWorx for Configure EtherNet IP devices by IP M EtherNet IP addresses an
108. quipment phase 91 change of state 59 chassis 57 coarse update period set 101 communication ControlNet network 25 determine timeout with any device 80 determine timeout with 1 0 module 81 DeviceNet network 28 DH network 45 DH 485 network 41 EtherNet IP network 22 format 59 Foundation Fieldbus 49 HART 50 serial 31 universal remote 1 0 46 CompactFlash load considerations 124 overview 123 reader 125 supported controller 124 configuration folder 59 configure ControllVet 1 0 module 62 DeviceNet I O module 63 I O module 59 PhaseManager 87 SERCOS interface modules 99 serial driver 17 connect DeviceNet network 28 DH network 45 DH 485 network 41 EtherNet IP network 22 Foundation Fieldbus 49 HART 50 RIO 46 serial 15 31 connection calculate use 54 consume data 52 ControlNet network 27 determine timeout with any device 80 determine timeout with 1 0 module 81 DeviceNet network 30 EtherNet IP network 24 1 0 module 60 monitor 80 produce data 52 connections example 56 139 Index 140 consume data connection use 52 overview 21 control distributed 1 0 overview 21 controller battery module 132 catalog number 12 check battery 128 CompactFlash 124 consume data 21 control distributed 0 21 design 13 estimate battery life 128 130 fault handler 82 install 13 message 21 monitor status 79 nonvolatile memory 124 path 19 produce data 21 redundancy 115 serial connection 15 status 79 controller communication 51 Con
109. r 2 Introduci n rose a how edP DERE YA a XA 15 Connect the Controller to via the Serial Pott 0005 15 Configure the Serial Driver uc esi ey o ue RNs See a4 17 Select the Controller Path llle 19 Chapter 3 nttoducttODa sd as La e deep heres Rv ee Rer aces 21 EtherNet IP Network Communication eese 22 Connections over an EtherNet IP Network 24 Additional Resources 0 0 cc een eens 25 ControlNet Network Communication llle 25 Connections over a ControlNet Network 0005 27 Additional Resources lese 28 DeviceNet Network Communication llle 28 Connections over DeviceNet 0 0 0 ccc eee ee 30 Additional Resources 00 cence eens 30 Serial Network Communication 0 0000 cc ccc cence ee 31 Communicate with DF1 Devices 0 00 0 ccc ee eee 32 DF1 Radio ModenubupDOoEE uus cei ae aee e dU rbd 34 Communicate with ASCII Devices lees 38 Modbus SUpport e e ees o cep reos bod ote gt do io 41 DH 485 Network Communication s nsss 00 ccc eee 41 Additional Resources llis 45 DH Network Communication lisse 45 Communicate over a DH Network 0 0 0 00 002 eee 46 Universal Remote I O Communication 0 0000 ce ee eee 46 Communicate over a Universal Remote I O Netwotk 48 Foundation Fieldbus 0 0 0 c cc ccc cnet en eens 49 Additional Resources lese 49 HART Highway Addressable Remote T
110. r Digital Digital Analog Y RTS RPI NY Yes Y Data is sent to the backplane Data is sent to the backplane at at the RTS the RTS and RPI COS for Any Point on the No Module Yes Y Data is sent to the backplane at the RPI and at the change of a specified point Analog Remote or Local Remote Local Y ua Y RPI Data is sent to the backplane at the interval the RPI Over a ControlNet network remote data is sent at the actual packet Over an EtherNet IP network remote data is usually sent close to Publication 1756 UMO001H EN P July 2008 Y Chapter 5 Data is sent to the backplane at the RPI and at the end of every task 67 Chapterb Place Configure and Monitor 1 0 Modules Reconfigure an 1 0 Module f an 1 0 module supports reconfiguration you can reconfigure the module via RSLogix 5000 programming software a MSG instruction in program logic WARNING Use care when changing the configuration of an I O module You could inadvertently cause the 1 0 module to operate incorrectly Reconfigure a Module via RSLogix 5000 Programming Software To reconfigure a module perform this procedure 1 In RSLogix 5000 programming software right click a module in the I O Configuration tree and select Properties WE
111. r the controller to manage the controller uses the communication time to execute the continuous task While increasing the system overhead percentage does increase communication performance it also increases the amount of time it takes to execute a continuous task increasing overall scan time Ratio between the Continuous Task and System Overhead Functions Time Slice Continuous Task Length Max Overhead Function Time 10 ams ms 2096 4 ms ms 33 2ms ms 50 1 ms ms Ata time slice of 10 system overhead interrupts the continuous task every 9 ms of continuous task time Legend Task executes Task is interrupted suspended Periodic 1ms ms System Overhead Bm i 9 ms 9 ms 0 5 10 15 20 25 Elapsed Time ms 84 Publication 1756 UM001H EN P July 2008 Develop Applications Chapter 6 The interruption of a periodic task increases the elapsed time clock time between the execution of system overhead functions 1ms ms ms 1 ms 1 ms Periodic Task mn E B m lm 1 ms 1 ms System Overhead icu B 9 ms of Continuous Task Time 9 ms of Continuous Task Time Continuous Task ce c1 c on N N c1 Elapsed Time ms If you use the default time slice of 20 the system overhead interrupts the continuous task evety 4 ms 1 ms ms ms 1 ms 1 ms System Overhead BE E Bl E 4 ms 4 ms 4 ms 4 ms 4 ms 5 10 15 20 25 Elapsed Time ms If you in
112. ransducer Protocol 50 Additional Resoutces s sober p RE Awd rn eg 50 5 Table of Contents Manage Controller Communication Place Configure and Monitor 1 0 Modules Develop Applications Chapter 4 IntroductiOD o vs vix ARN LH BARRA E TRA age 51 Connection Ovetview elis pe vut we VELLERA Y eee ES 51 Additional Reso tces i oe e RR eer ROO IS 51 Produce and Consume Interlock Data 00 00 00 0c eee 52 Additional Resources 0 cee teenies 52 Send and Receive Messages ics peace mk reda et aoctor aah waar ded 53 Determine Whether to Cache Message Connections 53 Calculate Connection Use ert ea cc a A 54 Connections Examples det ert e ta xS REPETI see nak e Pees 56 Chapter 5 Introduction ie sascha e GU M a REA CEN PERCENT 57 Select L O Modules eter ee HA 57 Additional Resources ce A 57 Place Local I O Modules 0 0 0 ec RI 57 Additional Resources eee 58 Contieute Joi eth vp ba vica o iate Ned d rop e o eet ad 59 T O Connectoren e e v RPEIUeDE ET E PEL 60 Additional Resoutces 432 psssubreUr bee AT eS ELS 60 Configure Distributed I O on an EtherNet IP Network 61 Additional Reso rces Mb ae aes es OE Re ROSY SS 61 Configure Distributed I O on a ControlNet Network 62 Additional Resources eee 62 Configure Distributed I O on a DeviceNet Network 63 Additional Resources 63 Addes T O Data 2 1 te eC DER ag 64 Add 1756 T Chal I OPE EHE Ls o tre
113. re faulted Cancel 2 Click the Date Time tab 3 Select the Make this controller the Coordinated System Time master check box 4 Click OK Multiple Controllers in the Chassis If you have more than one controller in the chassis designate one controller as the CST master You cannot have more than one CST master for the chassis 94 Publication 1756 UM001H EN P July 2008 Add the Motion Modules Publication 1756 UMO001H EN P July 2008 Develop Motion Applications Chapter 8 Each ControlLogix controller controls up to 16 motion modules IMPORTANT For your motion modules use the firmware revision that matches that of your controller See the release notes for your controller s firmware revision Required Motion Modules Used with Equipment Feedback Type Rockwell Automation SERCOS interface drives Required Motion Module 1756 MOS3SE 3 axes 1756 MO8SE 8 axes 1756 M16SE 16 axes 1756 L60MOSSE 3 axes Quadrature feedback LDT feedback SSI feedback Analog command signal 1756 MO2AE 1756 HYD02 1756 M02AS To add motion modules perform this procedure 1 In the Controller Organizer of RSLogix 5000 programming software right click your module and select New Module 1756 Backnlane 1756 A7 BEI fa to 17 New Module N 8 ui The Select Module dialog appears L Select Module E3 Module Description Vendor Analog Communication
114. ry life than this table shows While powered down the controller still drains the battery but it cannot give the low battery warning Temperature 254 cm Power Cycles Battery Life After the BAT LED Turns Red Worst Case E ME Project Size 1 MB 2MB 4 MB 8 MB 16 MB 0 20 C 32 68 F 3 per day 26 weeks 18 wee 12 wee 9 weeks 5 weeks 1 per Day 26 weeks 26 wee 26 wee 22 weeks 13 weeks 1 per Month 26 weeks 26 wee 26 wee 26 weeks 26 weeks 21 40 C 69 8 104 F 3 per day 18 weeks 14 wee 10 wee 8 weeks 5 weeks 1 per Day 24 weeks 21 wee 18 wee 16 weeks 11 weeks 1 per Month 26 weeks 26 wee 26 wee 26 weeks 26 weeks 41 45 C 105 8 113 F 3 per day 12 weeks 10 wee 7 weeks 6 weeks 4 weeks 1 per Day 15 weeks 14 wee 12 wee 11 weeks 8 weeks 1 per Month 17 weeks 17 wee 17 wee 17 weeks 16 weeks 46 50 C 105 8 113 F 3 per day 10 weeks 8 weeks 6 weeks 6 weeks 3 weeks 1 per Day 12 weeks 11 wee 10 wee 9 weeks 7 weeks 1 per Month 12 weeks 12 wee 12 wee 12 weeks 12 weeks 51 55 C 123 8 131 F 3 per day 7 weeks 6 weeks 5 weeks 4 weeks 3 weeks 1 per Day 8 weeks 8 weeks 7 weeks 7 weeks 5 weeks 1 per Month 8 weeks 8 weeks 8 weeks 8 weeks 8 weeks 56 60 C 132 8 140 F 3 per day 5 weeks 5 weeks 4 weeks 4 weeks 2 weeks 1 per Day 6 weeks 6 weeks 5 weeks 5 weeks 4 weeks 1 per Month 6 weeks 6 weeks 6 weeks 6 weeks 6 weeks Th
115. s Controllers Digital Drives Motion 1756 HYDO2 2 Axis Hydraulic Servo Allen Bradley 1756 MO2AE 2 Axis Analog Encoder Servo Allen Bradley 1756 M0245 2 Axis Analog SSI Servo Allen Bradley 1756 MO3SE 3 Axis SERCOS Interface Allen Bradley 1756 M SSE 8 Axis SERCOS Interface 1756 MO8SEG 8 Axis Generic SERCOS Interface Allen Bradley 1756 M165E 16 Axis SERCOS Interface Allen Bradley Y 4 gt Find _ Add Favorite By Category Favorites Cancel Help 2 Double click Motion 3 Select the motion module you want to add 95 Chapter 8 Develop Motion Applications 4 Click OK The New Module dialog appears 5 In the Name box type the name of the new module 6 In the Slot box enter the slot the new module will occupy 7 Leave Open Module Properties unchecked 8 Click OK Additional Information For additional information consult these publications Motion Analyzer Selection Guide publication PST SG003 ControlLogix Selection Guide publication 1756 SG001 96 Publication 1756 UM001H EN P July 2008 Develop Motion Applications Chapter 8 Add SERCOS Interface Drives Publication 1756 UMO001H EN P July 2008 With the addition of SERCOS interface modules to a controller s I O configuration you can use RSLogix 5000 programming software to set up the modules To add SERCOS interface modules perform this procedure 1 In the I O configuration tree in RSLogix 5000 programming software rig
116. s 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 Publication 1756 UM001H EN P July 2008 Develop Applications Chapter 6 Sample Controller Projects RSLogix 5000 Enterprise programming software includes sample projects that you can copy and then modify to fit your application To obtain a list of sample projects perform this procedure 1 In RSlogix 5000 programming software from the Help menu choose Vendor Sample Projects Contents Instruction Help Release Notes Online Books Vendor Sample Projects n 2 Scroll down to select the appropriate set of sample projects RSLogix 5000 Programming Software Vendor Sample Projects About the RSLogix 5000 Sample Projects Your RS Log S000 sofware comer vesh many sample poojects yrs can one oo male it easier to conate your cur projects if you wath Por inrtance you can we them as examples 90 follow when coating your ows peojects You cas we them ar a Haring pam ec your ows applicators by cenarrang them and then adding your own apphration onde Or you can umg y copy end posta poje componmum from oce pecject so amcthez Along wet the sample peojects peorided by Rockwell Auttcenazces are man prred by other vendan that may aeri yos c rtateg piech 9 wee wte that paratas vesdios r produce Sample poojects ace puoreded ax exa
117. s PLSSampleProject Date Time Advanced SFC Execution Fie Redundancy Nonvolatile Memory Memory General Serial Pon SyuemProtocol User Protocol Mayor Faults Minor Faults Mode z Baud Rate 79200 Data Bits u iy Panty Noe Stop Bits 1 E Control Line No Handshake r RTS Send Delay 0 x20 ms AIS Ol Delay 0 X20 ms OCO Wak Delay T x1 sec cen em w e 2 Click the Serial Port tab 38 Publication 1756 UM001H EN P July 2008 Publication 1756 UMO001H EN P July 2008 Communicate over Networks Chapter 3 3 From the Mode pull down menu choose User Specify ASCII communication settings 5 Click the User Protocol tab fs Controller Properties Pl SSampleProject Date Time Advanced SFC Execution Fie Redundancy Nonvolatile Memory Memory General SenaPor System Protocol User Protocol Major Faults Minor Faults Protocol Read wnte Butter Size Terminahon Charactes 1 Append Character 1 XON XOFF Echo Mode Delete Mode Ignore C CRT C Printer z 82 Bytes m ofr _ fse e is R tee cued Ae 6 Specify ASCII user protocol settings 7 Click OK 39 Chapter 3 40 Communicate over Networks The controller supports several ladder diagram LD and structured text ST instructions to manipulate ASCII characters Read and Write ASCII Characters Instruction Code ABL Command Determine when th
118. s ARCU RD Dco Ne doe M at 65 ControlNet I O Considerations eese 65 EtherNet IP I O Considerations ee eee 66 Determine When Data Is Updated 1 4 2e ete xA 67 Reconfigure an I O Module 22 4 at i pr be boe Robo bane os 68 Reconfigure a Module via RSLogix 5000 Programming Software 4 eet rel sopor eMe Sy 68 Reconfigure an I O Module via a MSG Instruction 69 Chapter 6 TattOduction ica a o s dna oe RUE PV P RN wsh io eva uS RECS 71 Additional Resources io RR ERE LER GE Os 71 Manage DasEs d omes rg es CR RT e AU e om ad OS wal 7 DevelopProctanis 2 ce cte etis Ue deett bue b teenies 72 Define Tasks ise eeece erat icit do tete et etes 73 Define PrOPTADYS ouo seed otel Cir dede tu a c uos a Mey 74 Define Routines sisie oe eke cask Nerd e DI REG Ne o e da 74 Sample ontroller Projectsaa ecesa xe wer tide urs PUES 75 Publication 1756 UM001H EN P July 2008 Configure PhaseManager Develop Motion Applications Publication 1756 UMO001H EN P July 2008 Table of Contents Additional Resources lise 75 Oroanize Tars er sieut tides eub ees a CU ar ders 76 Select a Programming Language oboe s eb da ep en ed AT Add On Instt ctiots 3455 so es oe dte teo deti bere TE Additional Resources lille 79 Monitor Controller Status llle 79 Additional Resources niee ue Y PERN GO OE 79 Monitor Connections llis 80 Determine if Communication Has Timed Out with Any Device 80 Determine if Communication
119. s on how much data the primary controller has to crossload The primary controller crossloads any tag to which an instruction wrote a value even the same value since the last crossload 119 Chapter 9 Configure Redundancy Minimum System Requirements 120 Quantity 2 Crossloading also requires a small amount of overhead time to tell the secondary controller which program the primary controller is executing Ata minimum a ControlLogix redundancy system must contain these items Item ControlLogix chassis Notes Both chassis must be the same size 2 ControlLogix power supply 2 ControlLogix controller ControlLogix ControlNet communication module Use either 1756 L55 1756 L61 1756 L62 1756 163 1756 L64 or 1756 L65 controllers Use the same catalog number and memory size controllers in each chassis Use series D modules ControlLogix 10 100 Mbps Ethernet IP communication module Optional You can use a second pair of 1756 ControllVet communication modules for HMI workstation communication 1757 system redundancy module 1757 system redundancy cable Standard lengths are available Additional ControlNet nodes Place all 1 0 in remote chassis or din rails Use a ControlNet network for all 1 0 Add at least 2 nodes to each ControlNet network in addition to the redundant chassis pair Publication 1756 UM001H EN P July 2008 Chapter 10
120. se the DF1 radio modem driver but only if you limit MSG instruction initiation to the node connected to the master radio modem whose transmissions can be received by every other radio modem in the network Youcan take advantage of the ControlLogix controller channel to channel passthru to remotely program the other nodes using RSLinx and RSLogix 5000 running on a personal computer connected to a local ControlLogix controller via DH 485 DH or Ethernet Additional Resources For additional information consult these publications Logix5000 Controllers General Instructions Reference Manual publication 1756 RM003 SCADA System Application Guide publication AG UM008 Publication 1756 UMO001H EN P July 2008 37 Chapter3 Communicate over Networks Communicate with ASCII Devices When you configure the serial port for user mode you can use it to read ASCII characters from a weigh scale module or bat code reader send and receive messages from an ASCII triggered device such as a Message View terminal a9 RA CJ mise GOBEGG0R00008 To communicate with ASCH devices perform this procedure 1 In the Controller Organizer of RSLogix 5000 programming software right click your controller and select Properties ERE 8 liens Properties Alt Enter The Controller Properties dialog appears fo Controller Propertie
121. ssages Link an EtherNet IP network to a DeviceNet network 1788 EN2DN Require multiple networks Link a ControlNet network to a DeviceNet network 1788 CN2DN Require multiple networks Publication 1756 UM001H EN P July 2008 Communicate over Networks Chapter 3 Required Software for DeviceNet Communication Software RSLogix 5000 Functions Configure ControlLogix projects Define EtherNet IP communication Requirement RSNetWorx for DeviceNet Configure DeviceNet devices Define the scan list for those devices Yes RSLinx Configure communication devices Provide diagnostics Establish communication between devices The DeviceNet communication module supports messaging to devices not controller to controller shares a common application layer with ControlNet and EtherNet IP netwotks offers diagnostics for improved data collection and fault detection requires less wiring than traditional hardwired systems ControlLogix DeviceNet Network Overview ff ff HE ControlLogix Controller with 1756 ENBT Module ie EtherNet IP Network Linking FLEX Adapter and 1 0 i Devices Personal Computer CompactLogix Controller uy 0000 0000 D Sensor Pushbut
122. t Link SERCOS Link DH Link RS 232 Link Computers SERCOS Drives Other Controllers HMI devices Publication 1756 UMO001H EN P July 2008 Communication Interface Modules in the Same ControlLogix Controller Universal remote 1 0 Link etworks via third party devices such as Remote 1 0 Modules Drives Li ee Sensors Highway Addressable Remote Transducer 11 Chapter 1 ControlLogix System Overview The ControlLogix controller is part of the Logix5000 family of controllers A ControlLogix system includes the ControlLogix controller is available in different combinations of user memoty Controller Memory for Data 1 0 Nonvolatile and Logic Back up Memory 1756 L55M12 750 KB 208 KB No 1756 L55M13 1 5 MB 208 KB No 1756 L55M14 3 5 MB 208 KB No 1756 L55M16 7 5 MB 208 KB No lt 3 5 MB of data 1756 L55M22 750 KB 208 KB Integrated 1756 L55M23 1 5 KB 208 KB Integrated 1756 L55M24 3 5 KB 208 KB Integrated 1756 L61 2 MB 478 KB Com pactFlash card 1796 L62 4 MB 478 KB CompactFlash card 1756 L63 8 MB 478 KB Com pactFlash card 1756 L64 16 MB 478 KB CompactFlash card 1756 165 32 MB 478 KB CompactFlash card 1756 L60MO3SE 750 KB 478 KB CompactFlash card n CompactFlash is optional and does not come with the controller RSLogix 5000 programming software 1756 ControlLogix I O modules that reside in a 1756 chassis different communication mod
123. therNet IP Network add an EtherNet IP adapter and I O modules to the I O Configuration folder of the controller Within the I O Configuration folder organize the modules into a hierarchy of tree branch and parent child Configuring 1 0 on an EtherNet IP Network For a typical distributed 1 0 network 1768 ENBT Remote Controller Module Adapter you build the 1 0 configuration in this order i Controller Tags L Controller Fault Handler 3 Power Up I landler 3 Tasks 4e MainTask C mainProgram 73 Iinschediled Programs 3 Motion Groups L Ungrouped Axes Trends 38 Data Types Lih User Defined strings ji Predefined i Module Defined E 10 Configuration 9 1756 Backplane 1756 A10 fa 0 1756 161 example B 1 1756 ENBT A enet 1 e Albert BJ 1756 ENBT A enet 1 1794 AENT A flex adapter amp d FlexBus amp 0 1794 1A3 A input amp 1 1794 OB8EP A output1 amp 2 1794 IF4I A analog 1 Add the remote adapter for the distributed 1 0 chassis or DIN rail 2 Add the distributed 1 0 modules Additional Resources For additional information consult EtherNet IP Communication Modules in Logix5000 Control Systems User Manual publication ENET UM001 Publication 1756 UMO001H EN P July 2008 61 Chapterb Place Configure and Monitor 1 0 Modules Configure Distributed 0 On To communicate with the I O modules over a ControINet network add a a ControlN
124. therNet IP Web Server modules In a redundant system use EtherNet IP for HMI communication or inter controller messaging only HMI can talk directly to the primary controller You no longer need RSLinx Alias Topics Redundancy does not support EtherNet IP for I O control or producing and consuming data IP Address Swapping Firmware version 13 supports IP address swapping in redundant systems Configure the primary and secondary EtherNet IP modules with the same IP address The primary EtherNet IP module takes the IP address the secondary module takes that address plus one in the last address segment DE Primary Chassis e aje IP Address Secondary Chassis IP Address On switchover the EtherNet IP modules swap IP addresses HMI devices automatically continue to communicate with the primary controller Because of the way EtherNet IP modules work during a switchover communication between the controller and an HMI device halts for several seconds typically less than a minute while the IP address propagates Use a dedicated ControlNet network instead of an EtherNet IP network if you need a bumpless HMI connection The primary controller stops at the end of every program to crossload fresh data to the secondary controller This keeps the secondary controller up to date and ready to take over It also increases the scan time when compared to a nonredundant system The amount of time a crossload consumes depend
125. 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 or event task Publication 1756 UMO001H EN P July 2008 73 Chapter 6 74 Develop Applications Define Programs Each program contains program tags a main executable routine other routines and an optional fault routine Each task can schedule as many as 100 programs The scheduled programs within a task execute to completion from first to last Programs that aren t attached to any task show up as unscheduled programs You must specify schedule a program within a task before the controller can scan the program Unscheduled programs within a task ate downloaded to the controller with the entire project The controller verifies unscheduled programs but does not execute them Define Routines A routine is a set of logic instructions in a single programming language such as Ladder Diagram 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 processor Each program has a main routine This is the first routine to execute when the controller triggers the associated task and calls the associated program Use logic such as the Jump to Subroutine JSR instruction to call other routine
126. trolLogix redundancy 115 ControlLogix system overview 11 ControlNet module capability 26 redundancy considerations 118 ControlNet network connection use 27 distributed 1 0 62 overview 25 required software for communication 26 scheduled 27 unscheduled 27 coordinated system time master set 94 COS 59 CST master 94 See coordinated system time master D define programs 74 routines 74 tasks 73 design 13 develop applications 71 motion applications 93 programs 72 develop application fault handler 82 monitor connection 80 monitor status 79 overview 71 programming language 77 tag 76 task 71 DeviceNet distributed 1 0 63 DeviceNet network connection use 30 overview 28 DF1 device 32 DH module capability 46 network overview 45 DH network example configuration 45 DH 485 network example configuration 41 overview 41 direct connection 60 distributed 1 0 ControlNet network 62 DeviceNet 63 overview 21 drive add SERCOS interface drive 97 check wiring 108 E electronic keying 59 EtherNet IP redundancy considerations 119 EtherNet IP network connection use 24 overview 22 example configuration DH 485 network 41 F fault handler 82 FBD 77 Foundation Fieldbus 49 function block diagram 77 G GSV instruction 79 Publication 1756 UMO001H EN P July 2008 H HART 50 Highway Addressable Remote Transducer see HART 50 1 0 address data 64 chassis 57 communication format 59 configuration folder 59 config
127. tware programming editors Standard Ladder Function Block Diagram Structured Text Once you have created instructions you can use them in any RSLogix 5000 editor Export Add On Instructions You can export Add On Instructions to other projects as well as copy and paste them from one project to another Give each instruction a unique name so that you don t accidentally overwrite another instruction of the same name Use Context Views Context views let you visualize an instruction s logic for a specific instant simplifying online troubleshooting of your Add On Instructions Each instruction contains a revision a change history and an auto generated help page Create Custom Help When you create an instruction you enter information for the description fields in software dialogs information that becomes what is known as Custom Help Custom Help makes it easier for users to get the help they need when implementing the instructions Apply Source Protection As the creator of Add On Instructions you can limit users of your instructions to read only access or you can bar access to the internal logic or local Publication 1756 UM001H EN P July 2008 Monitor Controller Status GSV Get System Value Class name Instance name Attribute Name Dest SV Set System Value Class name Instance name Attribute Name Source Publication 1756 UMO001H EN P July 2008 Develop Applications Chapter 6 parameters used b
128. ules for EtherNet IP ControlNet DeviceNet DH and Universal remote I O networks other networks via third party devices such as Foundation Fieldbus and the Highway Addressable Remote Transducer HART a built in serial port on every ControlLogix controller 12 Publication 1756 UMOO1H EN P July 2008 ControlLogix System Overview Chapter 1 The ControlLogix controller divides resources between a Logix CPU and a backplane CPU Logix CPU and Backplane CPU Logic and Data Memory 1 0 Memory Program Source Code 1 0 Data Logix E Backplane Tag Data CPU 1 0 Force Tables CPU RSLinx Tag Group Lists Message Buffers Produced consumed Tags The Logix CPU executes application code and messages The backplane CPU communicates with I O and sends and receives data from the backplane This CPU operates independently from the Logix CPU so it sends and receives I O information asynchronous to program execution Design When you design a ControlLogix system select I O devices motion control and drives requirements communication modules controllers chassis power supplies software Publication 1756 UMO001H EN P July 2008 13 Chapter 1 ControlLogix System Overview Install H ardware To install a ControlLogix controller install memory options ona 1756 L55 install a memory board for additional memory on a 1756
129. ure 57 connection use 60 COS 59 determine update 67 direct connection 60 distributed via ControlNet 62 distributed via DeviceNet 63 electronic keying 59 module capability 57 monitor 57 monitor connection 81 place 57 rack optimized 60 reconfigure module 68 RPI 59 install 13 L ladder diagram 77 language 77 LED Indicator BAT 136 FORCE 136 1 0 135 OK 137 RS232 136 RUN 135 M maintain battery 127 make controller CST master 94 manage controller communication 51 tasks 71 message cache 53 overview 21 Publication 1756 UM001H EN P July 2008 Index reconfigure I O module 69 Modbus support 41 monitor connections 80 controller status 79 motion applications 93 motion control choose a motion module 95 coarse update period 101 execution 101 overview 93 program 113 set the coordinated system time master 94 motion group set up 101 motion instructions overview 113 motion planner set period 101 network communication 21 networks overview 21 nonvolatile memory load considerations 124 overview 123 supported controller 124 0 obtain axis information 112 organize tags 6 P PhaseManager 87 change states 91 compare to other state models 91 equipment phase instructions 92 minimum system requirements 92 state models 89 produce data connection use 52 overview 21 program motion control 113 programming language 77 141 Index 142 rack optimized connection 60 receive messages 53 reconfigure I O
130. via Linx Gatewa Use RSLinx software to configure the RS 232 DF1 Device driver for serial communication 1 From the Communications pull down menu in RSLinx software choose Add New Status DF1 Device driver 3 Click Add New 2 From the Available Driver Types pull down menu choose the RS 232 The Add New RSLinx Driver dialog appears Add New RSLinx Driver Choose a name for the new driver 15 characters maximum AB_DF1 1 4 Type the driver name and click OK 17 Chapter2 Directly Connect to the Controller via the Serial Port 5 Specify the serial port settings a From the Comm Port pull down menu choose the serial port on the workstation to which the cable is connected b From the Device pull down menu choose Logix 5550 Serial Port c Click Auto Configure Configure RS 232 DF1 Devices Device Name AB_DF1 2 Comm Port COM1 v Device Logix 5550 CompactLogix fhd Baud Rate 19200 Station Number ng Decimal Parity None v Error Checking BCC m Stop Bits 1 X Protocol Full Duplex v Auto Configure Use Modem Dialer Cancel Delete Help 6 Was the auto configuration successful Click OK No Go to step 5 and verify that you selected the correct Comm Port 7 Click Close 18 Publication 1756 UM001H EN P July 2008 Directly Connect to the Controller via the Serial Port Chapter 2 Select the Controller Path In RSLogix 5000
131. when you load the project from nonvolatile memory If this occurs you have to upload or download the project to go online f you want to store changes such as online edits tag values or a ControlNet network schedule store the project again after you make the changes Publication 1756 UMO001H EN P July 2008 123 Chapter 11 Choose a Controller That Has Nonvolatile Memory Maintain Nonvolatile Memory These ControlLogix controllers have nonvolatile memory ControlLogix Controllers and Nonvolatile Memory Industrial CompactFlash memory card 1756 L55M23 8 x or later No ControlLogixb560MO3SE 1756 L60MO3SE 13 x or later Yes ControlLogix5561 1756 L61 12 x or later Yes ControlLogix5562 1756 L62 12 x or later Yes ControlLogix5563 1756 L63 11 x or later Yes ControlLogix5564 1756 L64 16 or later Yes ControlLogix5565 1756 L65 17 or later Yes 124 Controller Does not use a CompactFlash card Prevent a Major Fault During a Load If the major and minor revisions of the project in nonvolatile memory do not match the major and minor revisions of the controller a major fault may occur during a load Consequences Make sure that the major and minor revisions of the project in nonvolatile memory match the major and minor revisions of the controller The nonvolatile memory of the controller stores only the project It does not store the firmware for the controller Uses a CompactFlash
132. xis Motion Configuration Programming H Motion Planner Position Velocity Publication 1756 UM001H EN P July 2008 Position Velocity SERCOS Interface Drive 1756 SERCOS Interface Module 93 Chapter 8 Develop Motion Applications Make the Controller the You must make one module in the chassis the master clock for motion CST Master control This module is called the coordinated system time CST master Motion modules set their clocks to the master In most cases make the controller the CST master To make the controller the CST master perform this procedure 1 In RSLogix 5000 programming software right click the controller and select Properties Controller CNET maccanina Contre EP Verify Contre Power Generate Report Tasks Print L A mainte Eh me Properties Alt Enter The Controller Properties dialog appears f Controller Properties My Controller General Serial Port System Protocol User Protocol Major Faults Minor Faults Date Time Advanced SFC Execution File Redundancy Nonvolatile Memory Memory ae ee e lv Make this controller the Coordinated A DANGER If CST master is cleared online System Time master active axes in any controller in this chassis or chassis synchronized by SynchLink may Is the master experience unexpected motion Synchronized with a master Duplicate master detected Timer hardwa
133. y the instructions This source protection lets you prevent unwanted changes to your instructions and protects your intellectual property Additional Resources For additional information consult the Logix5000 Controllers Execution Time and Memory Use Reference Manual publication 1756 RM087 The ControlLogix controller uses Get System Value GSV and Set System Value SSV instructions to get and set change controller data The controller stores system data in objects There is no status file as in the PLC 5 processor The GSV instruction retrieves the specified information and places it in the destination The SSV instruction sets the specified attribute with data from the source When you enter a GSV SSV instruction the programming software displays the valid object classes object names and attribute names for each instruction For the GSV instruction you can get values for all the available attributes For the SSV instruction the software displays only those attributes you are allowed to set Some object types appear repeatedly so you may have to specify the object name For example there can be several tasks in your application Each task has its own TASK object that you access by the task name You can access these object classes AXIS MODULE CONTROLLER MOTIONGROUP CONTROLLERDEVICE PROGRAM CST ROUTINE DF1 SERIALPORT FAULTLOG TASK MESSAGE WALLCLOCKTIME Additional Resources For a
134. your remote I O network remember that all devices connected to a remote I O network must communicate using the same communication rate These rates ate available for remote I O 57 6 Kbps 115 2 Kbps 230 4 Kbps you must assign unique partial and full racks to each channel used in remote I O scanner mode Both channels of a 1756 DHRIO module cannot scan the same partial or full rack address Both module channels can communicate to 00 37 octal or 40 77 octal but each channel can only communicate with one address at a time in whichever of these two ranges it falls a channel can have up to 32 rack numbers with 32 physical devices connected to it a channel can have a maximum of 16 block transfer connections Additional Resources For additional information consult these publications 48 ControlLogix Data Highway Plus Universal Remote I O Module User Manual publication 1756 UM514 Process Remote I O Interface Module User Manual publication 1757 UM007 Publication 1756 UM001H EN P July 2008 Foundation Fieldbus Publication 1756 UMO001H EN P July 2008 Communicate over Networks Chapter 3 Foundation Fieldbus is an open interoperable fieldbus designed for process control instrumentation Application Required Linking Device Bridge an EtherNet IP network to Foundation Fieldbus 1757 FFLD Connect via a low speed serial H1 and high speed Ethernet HSE network connecti

ControlLogix Controllers

Contents

Download Pdf Manuals

Related Search

Related Contents