ControlLogix - PLC Compare
ControlLogix selguide cov.qxd7/27/00ControlLogixSelection Guide3:45 PMPage 2
Introducing ControlLogix for High Performance ControlControlLogix provides a high performance control platform for multiple types of control. You canperform sequential, process, drive or motion control - in any combination - with this single platform. Because the platform is modular, you can design, build, and modify it efficiently - with significant training and engineering savings. Engineering Productivity is increased with advancedconfiguration tools, memory structure and symbolic programming that requires less programmingand memory. And your investment inControlLogix is assured through with such features as flash-upgradable firmware. The flexibleControlLogix platform permits multiple processors, networks, and I/O to be mixed withoutrestrictions. As your application grows, you canuse the NetLinx architecture for control and configuration of devices and collection of informationacross Ethernet, ControlNet, DeviceNet andFoundation Fieldbus networks.Take Control with LogixRockwell Automation’s Logix offer users compatibility of control in a variety of platforms, including: ControlLogix , a high-performance, multi-processing platform ProcessLogix , a cost-effective distributed control system (DCS) forprocess applications SoftLogix , PC-based control from the PLC leader FlexLogix , FLEX I/O expanded to include distributed control CompactLogix , value-focused compact modular I/O coupled withmachine control.Rockwell Automation’s Logix Platforms offer users compatibility ofcontrol in a variety of formats within the NetLinx open network architecture for Ethernet, ControlNet and DeviceNet.
The RSLogix 5000 programming environment and/or NetLinx open network architecture arecommon to these Logix platforms. The RSLogix 5000 environment offers an easy-to-use IEC1131-3 compliant interface, symbolic programming with structures and arrays for increased productivity, and an instruction set that serves sequential, motion, process and drives applications.The NetLinx open network architecture offers common communication tools for use with a variety of networks such as Ethernet, ControlNet and DeviceNet.The ControlLogix control platform is:seamlessenables easy integration with existing PLC-based systems. Users on existing networks can send or receive messages to/from program controllers on other networkstransparently.fastthe ControlLogix platform provides high-speed data-transfers across the backplaneand the ControlLogix5550 controller provides a high-speed control platform.scalableprovides a modular approach to control. Add as many or as few controllers andcommunication modules as you need. You can have multiple controllers in thesame chassis. Select the controller memory size that meets your application.industrialoffers a hardware platform designed to withstand the vibrations, thermal extremes,and electrical noise associated with harsh industrial settings.integratedestablishes a platform that integrates multiple technologies, including sequential,motion, drive, and process applications.compactmeets the needs of many applications where control is highly distributed and panelTable of ContentsSelecting a ControlLogix System . . . . . . . . 4Selecting ControlLogix I/O Modules . . . . . . 19Planning Motion . . . . . . . . . . . . . . . . .33Planning Network Communications . . . . . . . 39Selecting a Controller . . . . . . . . . .Selecting a Chassis . . . . . . .Selecting a Power Supply . . . . .Selecting Software . . . . . . . . . . . . . . . . . . .57.73. 77. . 79Implementing a DCS Control System . . . . . . . . 85As one of the next generation of Allen-Bradley control systems, ControlLogixintegrates sequential, process, drive and motion control together with communications and state-of-the-art I/O in a small, cost-competitive platform.Because ControlLogix is modular, you can design, build, and modify it efficiently - with significant training and engineering savings.
4Selecting a ControlLogix SystemSelecting a ControlLogix SystemThe ControlLogix system architecture provides sequential, process, andmotion control together with communications and state-of-the-art I/O in asmall, cost-competitive package. The system is modular, so you can design,build, and modify it efficiently - with significant savings in trainingand engineering.A ControlLogix system can be anything from a simple chassis to ahighly-distributed system consisting of multiple chassis and networksworking together.A simple ControlLogix system consists of a stand-alone controller andI/O modules in a single chassis.ControlLogix controller1756 I/O modules in thesame chassis as theControlLogix controller41775Or you can use the ControlLogix system as a gateway. Include thecommunication modules you need for connectivity to other networks. Forthis use, a controller is not required. The ControlLogix Gateway integratesinto existing PLC-based systems so that users with existing networks cansend or receive messages to or from other networks.1756-SG001A-US-P July 2000
Selecting a ControlLogix System5For a more robust system, use: multiple controllers in a single chassis multiple controllers joined across networks I/O in multiple platforms that is distributed in many locations andconnected over multiple I/O linksControlNet linkControlLogixcontrollercommunication interfacemodules in the samechassis as theControlLogix controllerDeviceNet link}remoteI/O modulesUniversal Remote I/O link1756 I/O modules in thesame chassis as theControlLogix controllerRS-232 linkEthernet linkControlNet linkDH linkcomputersother controllers417761756-SG001A-US-P July 2000
6Selecting a ControlLogix SystemUse the following example as a guide to completing your own systemspecification. The inside of the back cover of this selection guide is aworksheet you can use to record your selections. Complete one worksheetfor each chassis.Follow these steps as you specify your ControlLogix system:Step 1Determine theI/O devicesStep 2See page 7Determine motionrequirementsStep 3See page 8Lay out the system andselect communicationmodulesStep 4Determine controllerrequirementsStep 5See page 11Determine the numberof chassisStep 6Select power suppliesand ensure sufficientpowerStep 7See page 12See page 13Verify communicationsStep 81756-SG001A-US-P July 2000See page 9See page 14Select softwareSee page 18
7Step 1:Determine the I/O DevicesUse a spreadsheet to record the amount and type of I/O devices theControlLogix system needs. Record the: location of the devicenumber of points neededappropriate 1756 catalog numbernumber of points available per modulenumber of modulesTo determine the number of modules you need, divide the “number ofpoints needed” by the “I/O points per module.” For example:I/O device:Location:Number ofpoints needed:Catalognumber:I/O points permodule:Number ofmodules:120V ac digital inputsA731756-IA8D810120V ac digital outputsA251756-OA8D8424V dc digital inputsA431756-IB16D16324V dc digital outputsA171756-OB16D162contact digital outputsA111756-OX8I824-20mA analog inputsA71756-IF6I620-10V dc analog inputsA21756-IF6I60 (use the remainingpoints from the above1756-IF6I module)4-20mA analog outputsA41756-OF6CI61PanelView terminalAna2711 seriesnanaLocation A subtotal 24120V ac digital inputsB351756-IA8D85120V ac digital outputsB151756-OA8D8224V dc digital inputsB231756-IB16D16224V dc digital outputsB131756-OB16D161contact digital outputsB51756-OX8I814-20mA analog inputsB31756-IF6I630-10V dc analog inputsB11756-IF6I604-20mA analog outputsB21756-OF6CI61PanelView terminalBna2711 seriesnanaLocation B subtotal 15RSView on a personal computerCna9301 seriesnanaLocation C subtotal 0For more information about ControlLogix I/O modules and how theyoperate, see page 19.1756-SG001A-US-P July 2000
8Step 2:Determine the MotionRequirementsThe ControlLogix controller executes ladder motion commands andgenerates position and velocity profile information. Each controller andchassis can control up to 16 1756-M02AE servo modules (for a total of32 axes). Each 1756-M02AE servo module must be in the same localchassis as its ControlLogix controller.The 1756-M02AE servo module connects to a servo drive and closes ahigh-speed position and velocity loop. Each 1756-M02AE module cancontrol up to two axes.Use the same spreadsheet to record motion servo modules. For example:I/O device:Location:Number ofpoints needed:Catalognumber:I/O points permodule:Number ofmodules:120V ac digital inputsA731756-IA8D810120V ac digital outputsA251756-OA8D8424V dc digital inputsA431756-IB16D16324V dc digital outputsA171756-OB16D162contact digital outputsA111756-OX8I824-20mA analog inputsA71756-IF6I620-10V dc analog inputsA21756-IF6I604-20mA analog outputsA41756-OF6CI61analog servo moduleA2 axis1756-M02AEna1PanelView terminalAna2711 seriesnanaLocation A subtotal 25120V ac digital inputsB351756-IA8D85120V ac digital outputsB151756-OA8D8224V dc digital inputsB231756-IB16D16224V dc digital outputsB131756-OB16D161contact digital outputsB51756-OX8I814-20mA analog inputsB31756-IF6I630-10V dc analog inputsB11756-IF6I604-20mA analog outputsB21756-OF6CI61PanelView terminalBna2711 seriesnanaLocation B subtotal 15RSView on a personal computerCna9301 seriesnanaLocation C subtotal 0For more information about planning for motion, see page 33.1756-SG001A-US-P July 2000
9Step 3:Lay Out the SystemLay out the system by determining the network configuration and theplacement of components in each location. Decide at this timewhether each location will have its own controller.Place each controller’s I/O on an isolated network to maximize theperformance and to more easily accommodate future network orsystem configuration changes. If you plan to share I/O, make sure theI/O is on a network that each controller can access.For example, assume that Location A and Location B both require acontroller. Each controller’s I/O is isolated on its own network. Bothcontrollers must interact with time critical information. Panel C doesnot require a controller and can be a ControlLogix gateway.RSViewEthernetControlNet network CPanel CControlNet network BControlNet network APanel Achassis 1Panel Achassis 2Panel Achassis 3Panel Bchassis 1Universal Remote I/OPanel Bchassis 2Universal Remote I/OPanelViewPanelViewFor a ControlLogix controller to control I/O modules, both thecontroller and the I/O modules must be directly attached to the sameControlNet network. This table lists which controllers in the aboveexample can control which I/O modules.I/O location:Controller inPanel A, chassis 1Controller inPanel B, chassis 1Panel A, chassis 1yesyesPanel A, chassis 2yesnoPanel A, chassis 3yesnoPanel B, chassis 1yesyesPanel B, chassis 2noyesPanel C, chassis 1yesyesFor more information about placing I/O modules, see page 30.1756-SG001A-US-P July 2000
10You also need to evaluate what communications need to occur between thecontrollers. If there is sporadic information that is not time critical, use amessage-based network such as an Ethernet, Data Highway Plus, or theunscheduled portion of a ControlNet network. If the information is timecritical, such as produced/consumed tags between controllers, use aControlNet network.Placing communication modulesDetermine the number of communication modules. You can use multiplecommunication modules in a chassis and divide communications betweenthose modules. Some communication modules have multiple channels, soyou don’t necessarily need one communication module for each link. Thisexample assumes one communication module for each link.Add the communication modules to the spreadsheet:I/O device:Location:Number ofpoints needed:Catalognumber:I/O points permodule:Number ofmodules:120V ac digital inputsA731756-IA8D810120V ac digital outputsA251756-OA8D8424V dc digital inputsA431756-IB16D16324V dc digital outputsA171756-OB16D162contact digital outputsA111756-OX8I824-20mA analog inputsA71756-IF6I620-10V dc analog inputsA21756-IF6I604-20mA analog outputsA41756-OF6CI61analog servo moduleA2 axis1756-M02AEna1PanelView terminalA12711 seriesnanaControlNet communication module Ana1756-CNBna4Remote I/O communication module Ana1756-DHRIOna1Location A subtotal 30For more information about networks and communication modules, seepage 39.1756-SG001A-US-P July 2000
11Step 4:Determine the ControllerRequirementsThe following equations provide an estimate of the memory neededfor a controller. Each of these numbers includes a rough estimate ofthe associated user programming. Depending on the complexity ofyour application, you might need more or less memory.Controller tasks* 4000 bytes (minimum 1 needed)Discrete I/O points* 400 bytesAnalog I/O points* 2600 bytesCommunication modules * 2000 bytesMotion axis* 8000 bytesTotal bytesFor example, the following table lists the configurations forLocation A and Location B:Location A:Location B:Controller tasks:1 continuous1 periodic (STI)1 continuous2 periodic (STI)Digital I/O points73 25 43 17 11 16935 15 23 13 5 91Analog I/O points:7 2 4 133 1 2 6Communication modules:4 1756-CNB modules1 1756-DHRIO module3 1756-CNB modules1 1756-DHRIO moduleMotion axis:2 axisnoneThen estimate memory to help choose the controller:Location A (bytes):Controller tasks:Location B (bytes):(2 x 4000) 8000(3 x 4000) 12,000Digital I/O points:(169 x 400) 67,600(91 x 400) 36,400Analog I/O points:(13 x 2600) 33,800(6 x 2600) 15,600Communication modules:(5 x 2000) 10,000(4 x 2000) 8000Motion axis:(2 x 8000) 16,000(0 x 8000) 0Total bytes:135,40072,000Selected controller:1756-L1M11756-L1M1If an estimate is close to the next memory size, select thelarger memory. For example, Location B uses 83% of the 160K bytesin a 1756-L1 controller. Use a 1756-L1M1 controller instead.For more information about selecting a controller, see page 57.1756-SG001A-US-P July 2000
12Step 5:Determine the Numberof ChassisUse another spread sheet to determine the number of chassis you need foreach location in your system. Include additional space in each chassis toaccommodate future growth. For example:Location:Module slots used:Spare slots (20% ofslots used)Total slotsneeded:Chassis catalog 132C2131756-A41Important: Use the slot filler module 1756-N2 to fill empty slots. Two slotfiller modules are included in each 1756-N2 catalog number.For more information about selecting a chassis, see page 73.1756-SG001A-US-P July 2000
13Step 6:Select Power Supplies and EnsureSufficient PowerUse the worksheet on the inside of the back cover of this selectionguide to record your module selections and calculate powerrequirements. Complete one worksheet for each chassis.Chassis: Catalog nt5.1V(amps):Backplane Modulecurrent 24V 6-DHRIO1756-L1M11756-CNB1756-CNBFor example:I/O termination: 400mAmaximum10,000mAmaximum2800mAmaximumcan’t exceed75W @ 60 mA1.7mA4.38W4spare (1756-N2)5spare 250mA6.89W15415mA658.6mA43.46W5totals: 0mADirectRack2If your power consumption exceeds the maximum, move somemodules to another chassis and recalculate the power requirements.For more information about selecting a power supply, see page 77.1756-SG001A-US-P July 2000
14Step 7:Verify CommunicationsThe ControlLogix controller supports 250 connections. The following tableshows how many connections the controller uses for these differentcommunication configurationsControlLogix Connection to:ConnectionsUsed by theControllerper Module:1130local I/O moduleremote I/O module (direct connection only)1756-MO2AE servo modulelocal 1756-CNB moduleremote ControlNet communication moduleconfigured as a direct (none) connectionconfigured as a rack-optimized connection1756-DHRIO module1756-ENET module1756-DNB moduleUniversal Remote I/O adapter moduleproduced tagproduced tag and one consumereach additional consumer of the tagconsumed tagblock-transfer messageother message0 or1102111111For example, to calculate the connections for the controller in Panel A,Chassis 1 in the configuration example, add the connections: for data transferin Panel A, Chassis 1to remote 1756-CNB in Panel A, Chassis 2to remote 1756-CNB in Panel A, Chassis 3Data transfer connectionsFor example, the controller in Panel A, Chassis 1 can use thesecommunication methods for transferring data:1756-SG001A-US-P July 2000Connection Type:Quantity:produced tagsproduced tageach consumer of the tagconsumed tagsblock-transfer messagesother messages244212TotalConnections:64212total 24
15Connections for Panel A, Chassis 1Chassis: Catalog nt5.1V(amps):Backplane Modulecurrent 24V power(amps):(watts):I/O termination: can’t exceed75W @ 60 mA850mA1.7mA4.38W024spare (1756-N2)5spare A175mA250mA6.89W115415mA658.6mA43.46W5totals: 0mAa.292The controller uses 1 connection for the 1756-DHRIO module and 1 additional connection for each logical rack connected to the 1756-DHRIO module. In thisexample, a PanelView terminal is connected to the 1756-DHRIO module, using only 1 logical rack.The controller always uses one direct connection for each I/O modulein its local chassis. The controller does not use any connection for a1756-CNB module in its local chassis.For more information about how the controller uses connections forI/O modules, see page 62.1756-SG001A-US-P July 2000
16Connections for Panel A, Chassis 2The controller in Panel A, Chassis 1 has a direct connection to everyI/O module in Panel A, Chassis 2.Chassis: Catalog nt5.1V(amps):Backplane Modulecurrent 24V power(amps):(watts):I/O termination: ��t exceed75W @ 60 spare (1756-N2)2695mA1106.7mA40.33W6totals: 0mARack11111116120The controller always uses a direct connection for an analog I/O module,regardless of whether the analog I/O module is local or remote tothe controller.The digital I/O modules in this chassis are remote to the controller, so youcan select a direct connection or a rack-optimized connection. However, totake advantage of the diagnostic capabilities of the digital I/O modules inthis chassis (note the “D” at the end of the catalog number), you mustconfigure a direct connection between the controller and the I/O module.1756-SG001A-US-P July 2000
17Connections for Panel A, Chassis 3The controller in Panel A, Chassis 1 has a rack connection tothe 1756-IA8D and 1756-OA8D I/O modules. The controllerhas a direct connection to the remaining I/O modules.Chassis: Catalog nt5.1V(amps):Backpla
chassis can control up to 16 1756-M02AE servo modules (for a total of 32 axes). Each 1756-M02AE servo module must be in the same local chassis as its ControlLogix controller. The 1756-M02AE servo module connects to a servo drive and closes a high-speed position and velocity loop. Each 1756-M02AE module can control up to two axes.
1756 ControlLogix Controllers 1756 ControlLogix-XT Controllers The ControlLogix-XT controllers function in the same way as the traditional ControlLogix controllers. The ControlLogix-XT products include control and communication system components that are conformally coated for extended protection in harsh, corrosive environments:
1756 ControlLogix Controllers 1756 ControlLogix-XT Controllers The ControlLogix-XT controllers function in the same way as the traditional ControlLogix controllers. The ControlLogix-XT products include control and communication system components that are conformally coated for extended protection in harsh, corrosive environments: † When .
ControlLogix Communication Modules 1756 ControlLogix System Step 4 ControlLogix Controllers Step 5 ControlLogix Chassis Step 6 ControlLogix Power Supplies Select: I/O modules—Some modules have field-side diagnostics, electronic fusing, or individually isolated inputs/outputs A remote terminal block (RTB) or wiring system for each I/O .
1756-PA75/A, -PB75/A ControlLogix Power Supply Installation Instructions 1756-5.78 1756-A4, -A7, -A10, -A13, -A17 ControlLogix Chassis Installation Instructions 1756-5.80 1756 Series ControlLogix System User Manual 1756-UM001 ControlLogix Digital I/O Modules User Manual 1756-6.5.8 ControlLogix Analog I/O Modules User Manual 1756-6.5.9
8 Rockwell Automation Publication 1756-RM100C-EN-P - November 2015 Chapter 1 Replacement Considerations Product Comparison The ControlLogix 5580 controllers operate similar to the ControlLogix 5570 controllers, with these differences. Table 1 - Technical Specifications Attribute ControlLogix 5580 Controll er ControlLogix 5570 Controller
ControlLogix controllers can monitor and control I/O across the ControlLogix backplane, and over I/O links. ControlLogix controllers can communicate over EtherNet/IP, ControlNet, DeviceNet, DH , Remote I/O, and RS-232-C (DF1/DH-485 protocol) networks and . 1756 ControlLogix I/O Workstation 1715 Redundant I/O PowerFlex 755 Drive
The ControlLogix controller is part of the Logix5000 family of controllers. A ControlLogix system includes: the ControlLogix contro ller is available in different combinations of user memory. RSLogix 5000 programming software. 1756 ControlLogix I/O modules that reside in a 1756 chassis.
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 memory: RSLogix 5000 programming software 1756 ControlLogix I/O modules that reside in 1756 chassis
