ControlLogix Selection Guide 1756-L55, 1756-L61, 1756-L62, 1756-L63, 1756-L60M03SE Logix Controllers Comparison Common Characteristics controller tasks: ! continuous ! periodic ! event user memory nonvolatile user memory 1756 ControlLogix™ ! 32 tasks (only 1 continuous) ! event tasks: supports all event triggers 1756-L55M12: 750 Kbytes 1756-L55M13: 1.5 Mbytes 1756-L55M14: 3.5 Mbytes 1756-L55M16: 7.5 Mbytes 1756-L55M22: 750 Kbytes 1756-L55M23: 1. 5 Mbytes 1756-L55M24: 3.5Mbytes 1756-L61: 2 Mbytes 1756-L62: 4 Mbytes 1756-L63: 8 Mbytes 1756-L55M12: none 1756-L55M13: none 1756-L55M14: none 1756-L55M16: none 1756-L55M22: yes 1756-L55M23: yes 1756-L55M24: yes 1756-L61: CompactFlash 1756-L62: CompactFlash 1756-L63: CompactFlash 1769 CompactLogix™ 1789 SoftLogix5800™ ! ! ! ! ! 1769-L35E: 8 tasks 1769-L32E: 6 tasks ! 32 tasks (only 1 1769-L31: 4 tasks continuous) 1769-L20, -L30: 4 tasks ! event tasks: supports all only 1 task can be event triggers, plus continuous outbound and Windows ! event tasks: supports events consumed tag trigger and EVENT instruction 1789-L10: 1769-L20: 1769-L30: 1769-L31: 1769-L32E: 1769-L35E: 64 Kbytes 256 Kbytes 512 Kbytes 750 Kbytes 1.5 Mbytes 1769-L20: 1769-L30: 1769-L31: 1769-L32E: 1769-L35E: yes yes CompactFlash none CompactFlash CompactFlash 1789-L30: 1789-L60: 2 Mbytes 3 slots no motion 64 Mbytes 5 slots 64 Mbytes 16 slots 1794 FlexLogix™ PowerFlex 700S® with DriveLogix ! 8 tasks (only 1 ! 8 tasks (only 1 continuous) continuous) ! event tasks: supports ! event tasks: supports axis consumed tag trigger and and motion event triggers EVENT instruction 1794-L33: 1794-L34: 64 Kbytes 512 Kbytes 256 Kbytes 768 Kbytes with memory expansion 1794-L33: 1794-L34: yes yes yes (expansion memory) built-in communication ports 1 port RS- 232 serial (DF1 or ASCII) ! 1769-L20 has 1 RS-232 serial port (DF1 or ASCII) ! 1769-L30, -L31 has 2 RS232 ports (one DF1 only, depends on personal computer other DF1 or ASCII) ! 1769-L32E, -L35E has 1 EtherNet/IP port and 1 RS-232 serial port (DF1 or ASCII) communication options(these options have specific products and profiles for their platform - other options are available via 3rd party products and generic profiles) EtherNet/IP ControlNet DeviceNet Data Highway Plus Universal Remote I/ O serial Modbus via ladder routine DH-485 SynchLink EtherNet/IP DeviceNet serial Modbus via ladder routine DH-485 EtherNet/IP ControlNet DeviceNet serial controller redundancy full redundancy support not applicable not applicable native I/O 1756 ControlLogix I/O 1769 Compact I/O none stepper servo via DeviceNet analog ac drive SERCOS interface analog interface hydraulic interface SSI interface stepper servo via DeviceNet analog ac drive stepper servo via DeviceNet analog ac drive not applicable SERCOS interface analog interface not applicable 1 full servo 1 feedback axis none panel mount DIN rail embedded in PowerFlex 700S ! ! ! ! ! ! ! ! simple motion integrated motion mounting and/or installation options 1756 chassis panel mount DIN rail programming languages ! ! ! ! ! ! ! ! relay ladder structured text function block sequential function chart relay ladder structured text function block sequential function chart ! ! ! ! ! relay ladder structured text function block sequential function chart external routines (Windows DLLs developed using C/C++) ! 1 port RS-232 serial (DF1 or ASCII) ! 2 slots for 1788 communication cards ! 1 port RS-232 serial (DF1 or ASCII) ! 1 slot for 1788 communication cards EtherNet/IP ControlNet DeviceNet serial Modbus via ladder routine DH-485 EtherNet/IP ControlNet DeviceNet serial Modbus via ladder routine DH-485 controller hot backup via DeviceNet 1794 FLEX I/O 1797 FLEX Ex I/O stepper servo via DeviceNet analog ac drive relay ladder structured text function block sequential function chart not applicable 1794 FLEX I/O 1797 FLEX Ex I/O stepper servo via DeviceNet analog ac drive relay ladder structured text function block sequential function chart 1 Logix Platforms Allen-Bradley Logix platforms provide a single integrated control architecture for discrete, drives, motion, and process control. The Logix platforms provide a common control engine, programming software environment, and communication support across multiple hardware platforms. All Logix controllers operate with a multitasking, multiprocessing operating system and support the same set of instructions in multiple programming languages. One RSLogix™ 5000 programming software package programs all Logix controllers. And all Logix controllers incorporate the NetLinx Open Network Architecture to communicate via EtherNet/IP, ControlNet, and DeviceNet networks. ControlLogix System Overview Layout the System Selecting ControlLogix I/O Modules Selecting Motion Control Requirements Selecting Network Communications Selecting Controllers Selecting Chassis Selecting Power Supplies Selecting Software Summary page page page page page page page page page page 2 3 7 25 31 47 63 67 71 81 1756-SG001G-EN-P — March 2004 2 ControlLogix System Overview What’s New in Version 13: y 1756-IB16ISOE and 1756-IH16ISOE modules The ControlLogix® system provides sequential, process, motion, and drive control together with communications and state-of-the-art I/O in a small, cost-competitive package. The system is modular, so you can design, build, and modify it efficiently with significant savings in training and engineering. A simple ControlLogix system consists of a stand-alone controller and I/O modules in a single chassis. to record sequence of events y 1756-IG16 and 1756-OG16 TTL I/O modules y 1756-IA32 high-density, ac input module y 1756-EWEB enhanced web server module y 1756-M03SE 3-axes SERCOS module and 1756-L60M03SE controller with embedded SERCOS interface y 1756-M02AS SSI feedback motion module y redundant controller systems now support two 1756-L55 controllers or one 1756-L6x controller y redundant controller systems now support the 1756-ENBT module y 1756-PSCA2 adapter module and 1756-CPR2 cable for redundant power supplies 1756-SG001G-EN-P — March 2004 Or use the ControlLogix system as a gateway. Include the communication modules you need for connectivity to other networks. For this use, a controller is not required. The ControlLogix Gateway integrates into existing PLC-based systems so that users with existing networks can send or receive messages to or from other networks. For a more robust system, use: y multiple controllers in a single chassis y multiple controllers joined across networks y I/O in multiple platforms that is distributed in many locations and connected over multiple I/O links 3 Layout the System Lay out the system by determining the network configuration and the placement of components in each location. Decide at this time whether each location will have its own controller. Place each controller’s I/O on an isolated network to maximize the performance and to more easily accommodate future network or system configuration changes. If you plan to share I/O, make sure the I/O is on a network that each controller can access. Assume that Location A and Location B both require a controller and its own I/O. Both controllers interact with time critical information. Panel C does not need a controller and can be a gateway. For a ControlLogix controller to control I/O modules, both the controller and the I/O modules must be directly attached to the same network. I/O Location Controller in Panel A, Chassis 1 Controller in Panel B, Chassis 1 Panel A, Chassis 1 Panel A, Chassis 2 Panel A, Chassis 3 Panel B, Chassis 1 Panel B, Chassis 2 Panel C, Chassis 1 yes yes yes yes no yes yes no no yes yes yes Evaluate what communications need to occur between controllers. If there is sporadic information that is not time critical, use a message-based network such as an EtherNet/IP (the information portion), Data Highway Plus, or the unscheduled portion of a ControlNet network. If the information is time critical, such as produced/consumed tags between controllers, use a ControlNet or EtherNet/IP network. 1756-SG001G-EN-P — March 2004 4 Laying out a redundant system The ControlLogix environment offers different levels of redundancy that you can design into your system. These systems require additional hardware, so plan accordingly. You can design redundant: y media for ControlNet y power supplies y controller chassis Redundant ControlNet media Requires: y 1756-CNBR ControlNet modules y two identical ControlNet links Redundant power supplies Requires: y two redundant power supplies, any combination of 1756-PA75R and 1756-PB75R y 1756-PSCA2 chassis adapter module, in place of the standard power supply y two 1756-CPR2 cables to connect the power supplies to the 1756-PSCA adapter y user-supplied annunicator wiring to connect the power supplies to the input modules, if needed 1756-SG001G-EN-P — March 2004 5 Redundant controller chassis Requires: y one or two 1756-L55 controllers or one 1769-L6x controller in each redundant chassis (contact your Rockwell Automation representative for the specific firmware revision) y at least one, but no more than five, 1756-CNB(R) series D, version 5.23 (or greater) communication modules in each redundant chassis y one 1757-SRM module in each redundant chassis y the redundant chassis can contain a 1756-ENBT communication module, but no other I/O or communication modules can be in the redundant chassis All I/O must be remote from the redundant controllers. ControlLogix redundancy works with remote 1756 I/O, FLEX I/O, drives, operator interfaces, or any other devices that can communicate with a ControlLogix controller over a ControlNet link. To connect to other networks, bridge through another ControlLogix chassis (not one of the redundant controller chassis) 1756-SG001G-EN-P — March 2004 6 Use the following checklist as a guide to completing your own system specification. The inside of the back cover of this selection guide is a worksheet you can use to record your selections. 9 See Step 1 Select I/O devices Use a spreadsheet to record: y location of the device y number of points needed y appropriate catalog number y number of points available per module y number of modules 2 Select motion control and drives requirements To the I/O spreadsheet, add the number of required motion modules. 3 Select communication modules To the I/O spreadsheet, add the number of required communication modules. 4 Select controllers Select the appropriate controller based on: y required controller tasks y number of I/O points needed y number of communication cards needed y required controller memory 5 I/O module specifications Wiring systems Placing I/O modules How I/O modules operate Selecting controller ownership page 8 page 14 page 23 page 24 page 24 Motion overview SERCOS interface modules Analog interface modules page 25 page 27 page 29 Network overview EtherNet/IP specifications ControlNet specifications DeviceNet specifications DH+/RIO specifications Foundation Fieldbus specifications Serial specifications DH-485 specifications SynchLink specifications AutoMax specifications Accessing the controller remotely Controller specifications Determining memory requirements Determining battery requirements Controlling devices Communicating with other devices Communicating with drives How a Logix system uses tasks How a Logix system uses connections page 31 page 33 page 35 page 38 page 39 page 40 page 40 page 42 page 43 page 45 page 46 page 47 page 49 page 50 page 51 page 52 page 53 page 54 page 57 Chassis specifications page 63 Power supply specifications page 67 Available software products Programming software Communication software Network configuration software Emulation software Training software Visualization software and products page 71 page 72 page 74 page 75 page 76 page 77 page 79 Select chassis Determine the number of chassis you need. 6 Select power supplies On the module spreadsheet, calculate power requirements. 7 Select software Determine the software products you need to configure and program your application.Based on the system design, determine the software products you need to configure and program your application. 1756-SG001G-EN-P — March 2004 7 Step 1 - Select: y I/O modules - some modules have field-side diagnostics, electronic fusing, or individually isolated inputs/outputs Selecting ControlLogix I/O Modules y a remote terminal block (RTB) or wiring system for each I/O module y PanelConnect modules and cables if connecting input modules to sensors The ControlLogix architecture provides a wide range of input and output modules to span many applications, from high-speed discrete to process control. The ControlLogix architecture uses producer/consumer technology, which allows input information and output status to be shared among multiple ControlLogix controllers. Each ControlLogix I/O module mounts in a ControlLogix chassis and requires either a removable terminal block (RTB) or a 1492 interface module (IFM) to connect all field-side wiring. RTBs and IFMs are not included with the I/O modules. They must be ordered separately. 1756 Digital I/O Modules The 1756 digital I/O modules support: y wide variety of voltage interface capabilities y isolated and non-isolated module types y point-level output fault states y choice of direct-connect or rack-optimized communications y field-side diagnostics on select modules In addition, you can select these types of digital I/O modules: Digital I/O Type diagnostic Description These modules provide diagnostic features to the point level. These modules have a “D” at the end of the catalog number. electronic fusing These modules have internal electronic fusing to prevent too much current from flowing through the module. These modules have an “E” at the end of the catalog number. individually isolated These modules have individually isolated inputs or outputs. These modules have an “I” at the end of the catalog number. 1756-SG001G-EN-P — March 2004 8 Digital ac input modules Cat. No. Number of Inputs Voltage, OnState Input, Nom. Operating Voltage 1756-IA8D 8 diagnostic 120V ac 79...132V ac 1756-IA16 16 120V ac 74...132V ac 120V ac 79...132V ac 120V ac 74...132V ac 16 1756-IM16I individually isolated 240V ac 159...265V ac 1756-IN16 16 24V ac 10...30V ac 16 1756-IA16I individually isolated 1756-IA32 32 Input Delay Time, ON to OFF Programmable filter: 9 ms & 18 ms Programmable filter: 9 ms & 18 ms Programmable filter: 9 ms & 18 ms Programmable filter: 9ms & 18 ms Programmable filter: 9 ms or 18 ms Programmable filter: 9 ms or 18 ms Removable Terminal Block Housing Current, OnState Input, Min. Current, OnState Input, Max. 5 mA @ 79V ac 16 mA @ 132V 2.5 mA ac 1756-TBNH 1756-TBSH 100 mA 3 mA 4.5 W @ 60 °C 5 mA @ 74V ac 13 mA @ 132V 2.5 mA ac 1756-TBNH 1756-TBSH 105 mA 2 mA 5.8 W @ 60 °C 5 mA @ 79V ac 47…63Hz 15 mA @ 132V 2.5 mA ac, 47…63HZ 1756-TBCH 1756-TBS6H 125 mA 3 mA 4.9 W @ 60 °C 5 mA @ 74V ac 10 mA @ 132V 2.5 mA ac 1756-TBCH 1756-TBS6H 165 mA 2 mA 6.1 W @ 60°C 5 mA @ 159V ac, 60Hz 13 mA @ 265V 2.5 mA ac, 60Hz 1756-TBCH 1756-TBS6H 100 mA 3 mA 5.8 W @ 60 °C 5 mA @ 10V ac, 60 Hz 1.2 mA @ 30V 2.75 mA ac, 60 Hz 1756-TBNH 1756-TBSH 100 mA 2 mA 5.1 W @ 60 °C Current, OffState Input, Max. Backplane Backplane Power Current (mA) Current (mA) Dissipation, at 5V at 24V Max. Digital ac output modules Output Current Rating, per Point, Max. Output Current Rating, per Module, Max. 5 A @ 30 °C (Linear derating) 4 A @ 60 °C (Linear derating) 8 A @ 30 °C (Linear derating) 4 A @ 60 °C (Linear derating) 8 A @ 30 °C (Linear derating) 4 A @ 60 °C (Linear derating) Cat. No. Number of Outputs Voltage Category Operating Voltage 1756-OA8 8 120/240V ac 74...265V ac 2 A @ 60 °C (Linear derating) 1756-OA8D 8 diagnostic 120V ac 74...132V ac 1 A @ 30 °C (Linear derating) 0.5 A @ 60 °C (Linear derating) 1756-OA8E 8 electronic fusing 120V ac 74...132V ac 2 A @ 60 °C 1756-OA16 16 120/240V ac 74...265V ac 0.5 A @ 60 °C 4 A @ 60 °C 16 1756-OA16I individually isolated 120/240V ac 74...265V ac 2 A @ 30 °C (Linear derating) 1 A @ 60 °C (Linear derating) 240V ac 10...30V ac 2 A @ 60 °C 5 A @ 30 °C (Linear derating) 4 A @ 60 °C (Linear derating) 5 A @ 30 °C 4 A @ 60 °C (Linear derating) 1756-ON8 8 1756-SG001G-EN-P — March 2004 Removable Terminal Block Housing Backplane Current (mA) at 5V Backplane Current (mA) at 24V Power Dissipation, Max. 1756-TBNH 1756-TBSH 200 mA 2 mA 5.1 W @ 60 °C 1756-TBNH 1756-TBSH 175 mA 250 mA 5.3 W @ 60 °C 1756-TBNH 1756-TBSH 200 mA 250 mA 5.5 W @ 60 °C 1756-TBNH 1756-TBSH 400 mA 2 mA 6.5 W @ 60 °C 1756-TBCH 1756-TBS6H 300 mA 3 mA 5.5 W @ 60 °C 1756-TBNH 1756-TBSH 200 mA 2 mA 5.1 W @ 60 °C 9 Digital dc input modules Voltage, OnState Input, Operating Nom. Voltage Cat. No. Number of Inputs 1756-IB16 16 12/24V dc sink 10...31.2V dc 1756-IB16D 16 diagnostic 12/24V dc sink 10...30V dc 1756-IB16I 16 individually isolated 12/24V dc sink/source 10...30V dc 1756-IB16ISOE✶ 16 individually isolated; sequence of events 24/48V dc sink/source 10...55V dc 1756-IB32 32 12/24V dc sink 10...31.2V dc 1756-IC16 16 48V dc sink 30...60V dc 1756-IG16 16 (8 5V dc points/commo TTL source n) 4.5...5.5V dc 1756-IH16I 16 individually isolated 125V dc sink/source 90...146V dc 1756-IH16ISOE✶ 16 individually isolated; sequence of events 125V dc sink/source 90...140V dc 1756-IV16 16 12/24V dc source 10...30V dc 1756-IV32 32 12/24V dc source 10...30V dc Input Delay Time, ON to OFF 2 ms hardware + filter time (0, 1, 2, 9, or 18 ms) 4 ms hardware + filter time (0, 1, 2, 9, or 18 ms) 4 ms hardware + filter time (0, 1, 2, 9, or 18 ms) 50 µs hardware + filter time (0...50 ms) 420 µs + filter time (0, 1, 2, 9, or 18 ms) 4 ms hardware + filter time (0, 1, 2, 9, or 18 ms) .25 ms hardware + filter time (0, 1, 2, 9, or 18 ms) 6 ms hardware + filter time (0, 1, 2, 9, or 18 ms) 75 µs hardware + filter time (0...50 ms) 2 ms hardware + filter time (0, 1, 2, 9, or 18 ms) 2 ms hardware + filter time (0, 1, 2, 9, or 18 ms) Removable Current, On- Current, On- Current, Off- Terminal State Input, State Input, State Input, Block Min. Housing Max. Max. 2.0 mA @ 10V 10 mA @ dc 31.2V dc 2 mA @ 10V dc 1.5 mA 13 mA @ 30V 1.5 mA/point dc Backplane Current (mA) at 5V Backplane Current (mA) at 24V Power Dissipation, Max. 1756-TBNH 1756-TBSH 100 mA 2 mA 5.1 W @ 60 °C 1756-TBCH 1756-TBS6H 150 mA 3 mA 5.8 W @ 60 °C 10 mA @ 30 V 2 mA @ 10V dc dc 1.5 mA 1756-TBCH 1756-TBS6H 100 mA 3 mA 5 W @ 60 °C 5.5 mA @ 55V 2 mA @ 10V dc dc 1.5 mA 1756-TBCH 1756-TBS6H 275 mA 2 mA 5.5 W @ 60 °C 5.5 mA 2 mA 1.5 mA 1756-TBCH 1756-TBS6H 120 mA 2 mA 6.2 W @ 60 °C 7 mA @ 60V dc 2 mA @ 30V dc 1.5 mA 1756-TBNH 1756-TBSH 100 mA 3 mA 5.2 W @ 60 °C 4.1 mA @ 5V dc 4.1 mA 1756-TBNH 1756-TBSH 110 mA 2 mA 1.4 W @ 60 °C 1 mA @ 90V dc 3 mA @ 146V 0.8 mA dc 1756-TBCH 1756-TBS6H 125 mA 3 mA 5 W @ 60 °C 1.15 mA @ 90V dc 1.85 mA @ 140V dc 1756-TBCH 1756-TBS6H 275 mA 2 mA 5.5 W @ 60 °C 2.0 mA @ 10V 10 mA @ 30V 1.5 mA dc dc 1756-TBNH 1756-TBSH 110 mA 2 mA 5.41 W @ 60 °C 3.5 mA @ 30V 2 mA @ 10V dc dc 1756-TBCH 1756-TBS6H 120 mA 2 mA 4.1 W @ 60 °C 0.3 mA 1.5 mA ✶If you use 1756-IB16ISOE or 1756-IH16ISOE modules in a remote rack, you must use a 1756-SYNCH SynchLink module to coordinate system time. 1756-SG001G-EN-P — March 2004 10 Digital dc output modules Cat. No. Number of Outputs Voltage Category 12/24V dc source Operating Voltage Output Current Rating, per Point, Max. Output Current Rating, per Module, Max. 10...30V dc 2.0 A @ 60 °C 8.0 A @ 60 °C Removable Terminal Block Housing 1756-TBNH 1756-TBSH Backplane Current (mA) at 5V Backplane Current (mA) at 24V Power Dissipation, Max. 165 mA 2 mA 2.5 W @ 60 °C 1756-OB8 8 1756-OB8EI 8 electronically fused, individually isolated 12/24V dc sink/source 10...30V dc 2 A @ 60 °C 16.0 A @ 55 °C (Linear derating) 10.0 A @ 60 °C 1756-TBCH 1756-TBS6H 250 mA 2 mA 4.7 W @ 60 °C 1756-OB16D 16 diagnostic 24V dc source 19.2...30V dc 2 A @ 30 °C (Linear derating) 1 A @ 60 °C (Linear derating) 8 A @ 30 °C (Linear derating) 4 A @ 60 °C (Linear derating) 1756-TBCH 1756-TBS6H 250 mA 140 mA 3.3 W @ 60 °C 12/24V dc source 10...31.2V dc 1 A @ 60 °C 8 A @ 60 °C 1756-TBNH 1756-TBSH 250 mA 2 mA 4.1 W @ 60 °C 16 individually isolated 12/24V dc sink/source 10...30V dc 2 A @ 30 °C (Linear derating) 1 A @ 60 °C (Linear derating) 8 A @ 30 °C (Linear derating) 4 A @ 60 °C (Linear derating) 1756-TBCH 1756-TBS6H 350 mA 3 mA 3.6 W @ 60 °C 16 individually 1756-OB16IS isolated; 8 scheduled 12/24V dc sink/source 10...30V dc 2 A @ 30 °C 1 A @ 60 °C (Linear derating) 8 A @ 30 °C 4 A @ 60 °C (Linear derating) 1756-TBCH 1756-TBS6H 250 mA 3 mA 3.6 W @ 60 °C 12/24V dc source 10...31.2V dc 0.5 A @ 50 °C (Linear derating) 0.35 A @ 60 °C 16 A @ 50 °C (Linear derating) 10 A @ 60 °C 1756-TBCH 1756-TBS6H 300 mA 2 mA 4.8 W @ 60 °C 30...60V dc 2.0 A @ 60 °C 8.0 A @ 60 °C 165 mA 2 mA 4.9 W @ 60 °C 4.5...5.5V dc 24 mA @ 60 °C 384 mA @ 60 °C 210 mA 2 mA 1.5 W @ 60 °C 120V dc sink/source 90...146V dc 2 A @ 60 °C 8 A @ 60 °C 1756-TBCH 1756-TBS6H 210 mA 2 mA 3.3 W @ 60 °C 12/24V dc sink 10...30V dc 1 A @ 60 °C 8 A @ 60 °C 1756-TBNH 1756-TBSH 210 mA 2 mA 6.72 W @ 60 °C 12/24V dc sink 10...30V dc 0.5 A @ 50 °C (Linear derating) 0.35 A @ 60 °C 16.0 A @ 50 °C (Linear derating) 10.0 A @ 60 °C 1756-TBCH 1756-TBS6H 390 mA 2 mA 5.88 W @ 60 °C 16 1756-OB16E electronically fused 1756-OB16I 1756-OB32 32 1756-OC8 8 1756-OG16 16 8 individually isolated 16 1756-OV16E electronically fused 32 1756-OV32E electronically fused 1756-OH8I 48V dc source 5V dc TTL 1756-TBNH 1756-TBSH 1756-TBNH 1756-TBSH Digital contact output modules Cat. No. Number of Outputs Output Delay Time, ON to OFF, Type of Contact Max. Output Operating Voltage 16 1756-OW16I individually isolated 10 ms 16 N.O. 10...265V ac 5...150V dc 8 individually isolated 13 ms 1 set of form-C contacts for each output 10...265V ac 5...150V dc 1756-OX8I 1756-SG001G-EN-P — March 2004 Output Current 2 A @ 5…30V dc 0.5 A @ 48V dc 0.25 A @ 125V dc 2 A @ 125/240V ac 2 A @ 5…30V dc 0.5 A @ 48V dc 0.25 A @ 125V dc 2 A @ 125/240V ac Removable Terminal Block Housing Backplane Current (mA) at 5V Backplane Current (mA) at 24V Power Dissipation, Max. 1756-TBCH 1756-TBS6H 150 mA 150 mA 4.5 W @ 60 °C 1756-TBCH 1756-TBS6H 100 mA 100 mA 3.1 W @ 60 °C 11 1756 Analog I/O Modules The 1756 analog I/O modules support: y on-board data alarming y scaling to engineering units y real-time channel sampling y IEEE 32-bit floating point or 16-bit integer data formats Cat. No. 1756-IF8 1756-IF6CIS Number of Number of Inputs Outputs 8 single-ended, 4 differential, 2 high- speed differential 6 isolated, current sourcing Input Resolution, Bits ±10.25V 0...5.125V 0...10.25V Sensors Supported Removable Terminal Block Housing Backplane Current (mA) at 5V Backplane Current (mA) at 24V 1756-TBCH 1756-TBS6H 150 mA 40 mA 1.73 W - Voltage 2.33 W - Current 0...21mA Range 1756-TBNH 1756-TBSH 250 mA 275 mA 5.1 W @ 60 °C 1756-TBNH 1756-TBSH 250 mA 100 mA 3.7 W - Voltage 4.3 W - Current 1756-TBCH 1756-TBS6H 150 mA 65 mA 2.3 W - Voltage 3.9 W - Current 1756-TBCH 1756-TBS6H 375 mA 100 mA 4.3 W - Voltage 4.7 W - Current ±10.5V 0...5.25V 0...10.5V 8 differential, 4 high±10.25V speed differential, 16 0...5.125V 1756-IF16 single-ended 0...10.25V Inputs ±10.5V 4 high-speed, sub0...5.25V 2 high-speed voltage 0...10.5V 1756-IF4FXOF2F millisecond, or current differential Outputs ±10.5V 1756-IF6I 1756-IR6I 1756-IT6I 1756-IT6I2 6 isolated 6 isolated RTD 6 isolated thermocouple 1 CJC 6 isolated thermocouple 2 CJC Power Dissipation, Max. 100, 200, 500, 1000Ω Platinum, alpha=385 100, 200, 500, 1000Ω Platinum, alpha=3916 120Ω Nickel, alpha=672 100, 120, 200, 500Ω Nickel, alpah=618 10Ω Copper Resistance 4…4020 Ω 100, 200, 500, 1000 Ω Platinum, alpha = 385 100, 200, 500, 1000 Ω Platinum, alpha = 1756-TBNH 3916 1756-TBSH 120 Ω Nickel, alpha = 672 100, 120, 200, 500 Ω Nickel, alpha = 618 10 Ω Copper 250 mA 125 mA 4.3 W -12 mV... +78 mV -12 mV... +38 mV B, E, J, K, R, S, T, N, C 1756-TBNH 1756-TBSH 250 mA 125 mA 4.3 W -12 mV... +78 mV -12 mV... +38 mV B, E, J, K, R, S, T, N, C, L, D 1756-TBNH 1756-TBSH 200 mA 120 mA 3.9 W 1756-TBNH 1756-TBSH 150 mA 120 mA 250 mA 300 mA† 250 mA 175 mA 4.85 W 150 mA 210 mA 4.92 W - 4 channel current 1756-OF4 4 voltage or current 1756-OF6CI 6 isolated 1756-TBNH 1756-TBSH 1756-OF6VI 6 isolated 1756-OF8 8 voltage or current 1756-TBNH 1756-TBSH 1756-TBNH 1756-TBSH 3.25 W - 4 channel current 5.5 W (0…550 Ω loads) 6.1 W (551…1000 Ω loads) 1756-SG001G-EN-P — March 2004 12 1756 Specialty I/O Modules 1756-CFM configurable flow meter The 1756-CFM module provides totalizer mode for metering applications, or highspeed frequency measurements for speed or rate control applications, on two channels connected to flowmeters. Both Fill and Prover functions are supported within resettable or nonresettable totalizer mode. A 12-segment K-factor correction table makes it easy to scale any turbine flowmeter and AGA 7 compensation is available. The module supports two configurable outputs that can be connected to one or both channels and can be triggered on: y flow or frequency y acceleration y full flow state y trickle flow state y prover run state y prover range state The module interfaces devices such as: y magnetic pickup flow meters y 4-40V dc pulses (TTL compatible) y proximity probes Number of Inputs per Voltage, Flowmeter Channel Input ± 30V - Selectable input thresholds of 50 mV, 1.3V & 4V: ± 30V peak unterminated open Totalizer fill and prover 2 – Flowmeter (F) Input circuit voltage – High-Resolution 100 kHz – used for all modes Magnetic Pickup 2 – Gate Input – used in 1756-CFM max. TTL Compatible – Input Frequency 0.0005 Hz Totalizer Mode for Voltage greater than 1.3V resolution Prover/Store Count dc is Logic 1 and - 0.7V dc…1.3V dc is Logic 0 12…24V dc powered preamp output - 4V dc threshold Cat. No. Mode of Operation 1756-SG001G-EN-P — March 2004 Removable Terminal Block Housing Backplane Current (mA) at 5V Backplane Current (mA) at 24V Power Dissipation, Max. 1756-TBNH 1756-TBSH 300 mA 6 mA 6 W @ 60°C 13 1756-HSC high speed counter The 1756-HSC module provides 4 high-speed, output-switching, ON-OFF windows. The module uses pulses for counting and frequency. The module interfaces with pulse devices and encoders, such as: y photoswitch series 10,000 photoelectric sensors y bulletin 872 3-wire DC proximity sensors y bulletin 845 incremental encoders The 1756-HSC module can update data every 2ms. The module is most effective when you use a single sensor for each of the two channels on the module. If necessary, you can connect a single sensor to multiple channels or modules. Mode of Number of Cat. No. Operation Counters Counter - 1 MHz max. Rate Measurement - 500 kHz max. 2 1756-HSC Encoder - 250 kHz max. Debounce filter 70 Hz max. Inputs per Counter 3 (A, B, Z for Gate/Reset) Count Range Number of Outputs 0…16, 777, 214 4 Removable Terminal Block Housing Backplane Current (mA) at 5V Backplane Current (mA) at 24V Power Dissipation, Max. 1756-TBCH 1756-TBS6H 300 mA 3 mA 5.6 W @ 60°C 1756-PLS programmable limit switch The 1756-PLS module supports enhanced packaging applications where you require: y deterministic module operation for operations up to 1500 parts per minute (PPM) y detection of 1.08 degrees of rotation at 1800 RPM y fast switching of ON-OFF windows y multi-turn capabilities using resolvers y direct drive on most pneumatic solenoid or glue guns The module accepts any R3-style resolver, such as the bulletin 846 resolvers. The module provides excitation to the resolver at 5K Hz @ 7.0V ac and directly connects to the sine and cosine outputs of the resolver. Cat. No. Mode of Operation Number of Inputs Number of Outputs 1756-PLS Requires 3 contiguous slots in chassis 16 16 Removable Terminal Block Housing Requires 3 RTBs 1756-TBNH or 1756TBSH Backplane Current (mA) at 5V Backplane Current (mA) at 24V Power Dissipation, Max. 1000 mA 125 mA 25.7 W @ 30 °C 21.3 W @ 60 °C 1756-SG001G-EN-P — March 2004 14 1756 Removable Terminal Blocks Removable terminal blocks (RTBs) provide a flexible interconnection between your plant wiring and 1756 I/O modules. The RTB plugs into the front of the I/O module. The type of module determines which RTB you need. You choose screw-clamp or spring-clamp RTBs. RTBs are not shipped with I/O modules. You must order them separately. The standard housing on the front of the wiring arm is not deep enough for 14 AWG wiring. If you plan to use 14 AWG wiring, also order the extended housing. Cat. No. 1756-TBNH 1756-TBSH 1756-TBCH 1756-TBS6H 1756-TBE Description screw-clamp with 20-pin connection spring-clamp with 20-pin connection screw-clamp with 36-pin connection spring-clamp with 36-pin connection extended housing; required for additional wiring space if using 14 AWG wiring 1492 Wiring Systems Weight 0.1 kg (0.3 lb) 0.1 kg (0.3 lb) 0.1 kg (0.3 lb) 0.1 kg (0.3 lb) 0.05 kg (0.1 lb) As an alternative to buying RTBs and connecting the wires yourself, you can buy a wiring system of: y interface modules (IFMs) that mount on DIN rails provide the output terminal blocks for the I/O module. Use the IFMs with the pre-wired cables that match the I/O module to the interface module. y I/O-module-ready cables. One end of the cable assembly is an RTB that plugs into the front of the I/O module. The other end has individually color-coded conductors that connect to a standard terminal block. 1756-SG001G-EN-P — March 2004 15 Feed through IFMs for 20-pin 1756 digital I/O modules Cat. No. 1492-IFM20F 1492-IFM20FN 1492-IFM20F-2 Description standard narrow standard extra terminals 3-wire sensor type input 1492-IFM20F-3 devices 1492-XIMF-2 IA8D U U U IA16 X X X IB16 X X X IC16 X X X IN16 X X X X X X X OA8 U U U OA8D U U U OA8E U U U feed through expander with eight feed-through channels✶ OA16 X X X OA16E OB8 U U U X OB16E X X X OC8 U U U ON8 U U U X Find the column for the digital I/O module. Follow the column down to see what digital IFMs are compatible with the I/O module as indicated by a letter code. When you select the IFM, use the letter code from this chart to find the compatible cable in the following table for digital pre-wired cabled. The letter code must match the last character of the catalog number for the cable. ✶One expander module is connected to a master to provide a total of 16 outputs. An extender cable is included with each expander to connect it to the master. LED indicating IFMs for 20-pin 1756 digital I/O modules Cat. No. 1492-IFM20D24 Description standard with 24V ac/dc LEDs narrow standard with 24V 1492-IFM20D24N ac/dc LEDs 1492-IFM20D120 standard with 120V ac LEDs narrow standard with 120V 1492-IFM20D120N ac/dc LEDs 24V ac/dc LEDS and extra 1492-IFM20D24-2 terminals for outputs 24V ac/dc LEDS and extra 1492-IFM20D24A-2 terminals for inputs 120V ac/dc LEDS and extra 1492-IFM20D120-2 terminals for outputs 120V ac LEDs and extra 1492-IFM20D120A-2 terminals for inputs 3-wire sensor with 24V ac/dc 1492-IFM20D24-3 LEDs isolated with 24/48V ac/dc 1492-IFM20DS24-4 LEDs and 4 terminals for outputs isolated with 120V ac LEDs 1492-IFM20DS120-4 and 4 terminals for outputs 240V ac LEDs and extra 1492-IFM20D240-2 terminals for outputs 240V ac LEDs and extra 1492-IFM20D240A-2 terminals for inputs IA8D IA16 U X U X IB16 X X IC16 IN16 X OA8 OA8D OA8E OA16 OA16E OB8 X OB16E X OC8 ON8 W W X X X X X X U X X X W W V V Find the column for the digital I/O module. Follow the column down to see what digital IFMs are compatible with the I/O module as indicated by a letter code. When you select the IFM, use the letter code from this chart to find the compatible cable in the following table for digital pre-wired cabled. The letter code must match the last character of the catalog number for the cable. 1756-SG001G-EN-P — March 2004 16 Fusible IFMs for 20-pin 1756 digital I/O modules Cat. No. 1492-IFM20F-F-2 Description IA8D extra terminals for outputs extra terminals with 24V 1492-IFM20F-F24-2 ac/dc blown fuse indicators for outputs extra terminals with 120V ac 1492-IFM20F-F120-2 blown fuse indicators for outputs extra terminals with 240V ac 1492-IFM20F-F240-2 blown fuse indicators for outputs extra terminals with 24V 1492-IFM20F-F24A-2 ac/dc blown fuse indicators for inputs extra terminals with 120V ac 1492-IFM20F-F120A-2 blown fuse indicators for inputs isolated with extra terminals 1492-IFM20F-FS-2 for outputs isolated with extra terminals 1492-IFM20F-FS24-2 and 24V ac/dc blown fuse indicators for outputs isolated with 4 terminals and 1492-IFM20F-FS24A-4 24V ac/dc blown fuse indicators for inputs isolated with extra terminals 1492-IFM20F-FS120-2 with 120V ac blown fuse indicators for outputs isolated with 4 terminals with 1492-IFM20F-FS120-4 120V ac blown fuse indicators for outputs isolated with 4 terminals with 1492-IFM20F-FS120A-4 120V ac blown fuse indicators U for inputs isolated with 4 terminals with 1492-IFM20F-FS240-4 240V ac blown fuse indicators for outputs expander with eight 24V dc 1492-XIMF-F24-2 channels with blown fuse indicators✶ expander with eight 120V ac 1492-XIMF-F120-2 channels with blown fuse indicators✶ IA16 IB16 IC16 IN16 OA8 OA8D OA8E OA16 X OA16E OB8 OB16E X OC8 ON8 W W W W W W X X X X X X W V V W V V W V V W X X Find the column for the digital I/O module. Follow the column down to see what digital IFMs are compatible with the I/O module as indicated by a letter code. When you select the IFM, use the letter code from this chart to find the compatible cable in the following table for digital pre-wired cabled. The letter code must match the last character of the catalog number for the cable. ✶One expander module is connected to a master to provide a total of 16 outputs. An extender cable is included with each expander to connect it to the master. Relay IFMs for 20-pin 1756 digital I/O modules Cat. No. Description 20-pin master with eight 24V dc relays 20-pin master with eight 24V 1492-XIM2024-8R dc relays expander with eight 24V dc 1492-XIM24-8R relays✶ expander with eight 120V ac 1492-XIM120-8R relays✶ IA8D IA16 IB16 IC16 IN16 OA8 OA8D OA8E OA16 OA16E 1492-XIM2024-8R OB8 OB16E OC8 ON8 X X X X Find the column for the digital I/O module. Follow the column down to see what digital IFMs are compatible with the I/O module as indicated by a letter code. When you select the IFM, use the letter code from this chart to find the compatible cable in the following table for digital pre-wired cabled. The letter code must match the last character of the catalog number for the cable. ✶One expander module is connected to a master to provide a total of 16 outputs. An extender cable is included with each expander to connect it to the master. 1756-SG001G-EN-P — March 2004 17 Feed through IFMs for 36-pin 1756 digital I/O modules Cat. No. Description 1492-IFM40F standard 1492-IFM40F-2 extra terminals 3-wire sensor type input 1492-IFM40F-3 devices expander with eight feed1492-XIMF-2 through channels✶ IA16I Y IB16D Y Y IB16I Y IB32 Z Z IH16I Y IM16I OA16I Y OB8EI Y OB16D OB16E Y Y OB16I Y OB32 Z Z OH8I Y OW16I OX8I Y Y Z X Find the column for the digital I/O module. Follow the column down to see what digital IFMs are compatible with the I/O module as indicated by a letter code. When you select the IFM, use the letter code from this chart to find the compatible cable in the following table for digital pre-wired cabled. The letter code must match the last character of the catalog number for the cable. ✶One expander module is connected to a master to provide a total of 16 outputs. An extender cable is included with each expander to connect it to the master. LED indicating IFMs for 36-pin 1756 digital I/O modules Cat. No. Description standard with 24V ac/dc 1492-IFM40D24 LEDs 24V ac/dc LEDs and extra 1492-IFM40D24-2 terminals for outputs 24V ac/dc LEDs and extra 1492-IFM40D24A-2 terminals for inputs 120V ac LEDs and extra 1492-IFM40D120-2 terminals for outputs 120V ac LEDs and extra 1492-IFM40D120A-2 terminals for inputs 3-wire sensor with 24V 1492-IFM40D24-3 ac/dc LEDs for inputs isolated with 24/48V ac/dc 1492-IFM40DS24-4 LEDs and 4 terminals per output isolated with 24/48V ac/dc 1492-IFM40DS24A-4 LEDs and 4 terminals per input isolated with 120V ac LEDs 1492-IFM40DS120-4 and 4 terminals per output isolated with 120V ac LEDs 1492-IFM40DS120A-4 and 4 terminals per input isolated with 240V ac LEDs 1492-IFM40DS240A-4 and 4 terminals per output IA16I IB16D IB16I IB32 IH16I IM16I OA16I OB8EI OB16D OB16E OB16I Z OB32 OH8I OW16I OX8I Z Z Z Z Y Y Y Y Y Y Y Y Y Y Y Y Find the column for the digital I/O module. Follow the column down to see what digital IFMs are compatible with the I/O module as indicated by a letter code. When you select the IFM, use the letter code from this chart to find the compatible cable in the following table for digital pre-wired cabled. The letter code must match the last character of the catalog number for the cable. 1756-SG001G-EN-P — March 2004 18 Fusible IFMs for 36-pin 1756 digital I/O modules Cat. No. 1492-IFM40F-F-2 1492-IFM40F-F24-2 1492-IFM40F-F120-2 1492-IFM40F-FS-2 1492-IFM40F-FS24-2 Description IA16I extra terminals for outputs extra terminals with 24V ac/dc blown fuse indicators for outputs extra terminals with 120V ac blown fuse indicators for outputs isolated with extra terminals for outputs isolated with extra terminals and 24V ac/dc blown fuse indicators for outputs isolated with 24V ac/dc blown fuse indicators and 4 terminals per output isolated with extra terminals 1492-IFM40F-FS120-2 and 120V ac blown fuse indicators for outputs isolated with 120V ac blown 1492-IFM40F-FS120-4 fuse indicators and 4 terminals per output isolated with 240V ac blown 1492-IFM40F-FS240-4 fuse indicators and 4 terminals per output isolated with 24V ac/dc 1492-IFM40F-FS24A-4 blown fuse indicators and 4 terminals per input isolated with 120V ac blown 1492-IFM40F-FS120A-4 fuse indicators and 4 Y terminals per input fusible expander with eight 1492-XIMF-F24-2 24V dc channels with blown fuse indicators✶ fusible expander with eight 1492-XIMF-F120-2 120V ac channels with blown fuse indicators✶ IB16D IB16I IB32 IH16I IM16I OA16I OB8EI OB16D OB16E OB16I OB32 Z OH8I OW16I OX8I Y Y Y Z Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y 1492-IFM40F-FS24-4 Y Y Y Y Y X Find the column for the digital I/O module. Follow the column down to see what digital IFMs are compatible with the I/O module as indicated by a letter code. When you select the IFM, use the letter code from this chart to find the compatible cable in the following table for digital pre-wired cabled. The letter code must match the last character of the catalog number for the cable. ✶One expander module is connected to a master to provide a total of 16 outputs. An extender cable is included with each expander to connect it to the master. 1756-SG001G-EN-P — March 2004 19 Relay IFMs for 36-pin 1756 digital I/O modules Cat. No. Description IA16I 40-pin master with eight 24V 1492-XIM4024-8R dc relays 40-pin master with sixteen 1492-XIM4024-16R 24V dc relays expander with eight 24V dc 1492-XIM24-8R relays✶ expander with eight 120V ac 1492-XIM120-8R relays✶ IB16D IB16I IB32 IH16I IM16I OA16I OB8EI OB16D OB16E OB16I OB32 OH8I OW16I OX8I Z Z X Find the column for the digital I/O module. Follow the column down to see what digital IFMs are compatible with the I/O module as indicated by a letter code. When you select the IFM, use the letter code from this chart to find the compatible cable in the following table for digital pre-wired cabled. The letter code must match the last character of the catalog number for the cable. ✶One expander module is connected to a master to provide a total of 16 outputs. An extender cable is included with each expander to connect it to the master. Pre-wired cables for digital I/O modules Cat. No.✶ 1492-CABLExU 1492-CABLExV 1492-CABLExW 1492-CABLExX 1492-CABLExY 1492-CABLExZ Number of Conductors 20 20 20 20 40 40 Conductor Size 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG Nominal Outer Diameter 9.0 mm (0.36 in) 9.0 mm (0.36 in) 9.0 mm (0.36 in) 9.0 mm (0.36 in) 11.7 mm (0.46 in) 11.7 mm (0.46 in) RTB at the I/O Module End 1756-TBNH 1756-TBNH 1756-TBNH 1756-TBNH 1756-TBCH 1756-TBCH ✶Cables are available in lengths of 0.5m, 1.0m, 2.5m, and 5.0m. To order, insert the code for the desired cable length into the catalog number in place of the x: 005=0.5m, 010=1.0m, 025=2.5m, 050=5m. I/O-module-ready cables for digital I/O modules Cat. No.✶ Number of Conductors 1492-CABLExTBNH 20 1492-CABLExTBCH 40† Conductor Size 18 AWG 18 AWG Nominal Outer Diameter 11.4 mm (0.45 in) 14.1 mm (0.55 in) RTB at the I/O Module End 1756-TBNH 1756-TBCH ✶Cables are available in lengths of 0.5m, 1.0m, 2.5m, and 5.0m. To order, insert the code for the desired cable length into the catalog number in place of the x: 005=0.5m, 010=1.0m, 025=2.5m, 050=5m. Build-to-order cable lengths are also available. †Four conductors are not connected to the RTB. For example, a 1756-OB32 that requires LEDs and extra terminals uses: y 1492-IFM40D24-2 interface module y 1492-ACABLExZ cable (replace x with the appropriate length) 1756-SG001G-EN-P — March 2004 20 AIFMs for 1756 analog input modules Cat. No. Type of AIFM 1492-AIFM4-3 feed through 1492-AIFM6S-3 feed through 1492-AIFM8-3 feed through 1492-AIFM6TC-3 thermo couple 1492-AIFM8-F-5 fusible 1492-AIFM16-F-3 fusible 1492-AIFM16-F-5 fusible Descripti on IF6I current 4 channels with 3 terminals/c hannel 6 channels isolated with 3-4 X terminals/c hannel 8 channels with 3 terminals/c hannel 6 channels with 3 terminals/c hannel 8 channels with 5 terminals/c hannel 16 channels with 3 terminals/c hannel 16 channels with 5 terminals/c hannel IF6I voltage IF8 single-end voltage current IF8 differential voltage current IF16 single-end voltage current IF16 differential voltage current Y IR6I IT6I Z TA TB TC TD UA UB UC UD Y TA TB TC TD UA UB UC UD UA UB UC UD Find the column for the analog I/O module. Follow the column own to see what AIFMs are compatible with the I/O module as indicated by a letter code. When you select the AIFM, use the letter code from this chart to find the compatible cable in the following table for analog pre-wired cable. The letter code must match the last character of the catalog number for the cable. AIFMs for 1756 analog output modules Cat. No. Type of AIFM 1492-AIFM4-3 feed through 1492-AIFM6S-3 feed through 1492-AIFM8-3 feed through 1492-AIFM6TC-3 thermocouple 1492-AIFM8-F-5 fusible 1492-AIFM16-F-3 fusible 1492-AIFM16-F-5 fusible Description IR6I 4 channels with 3 terminals/chann el 6 channels isolated with 3-4 Z terminals/chann el 8 channels with 3 terminals/chann el 6 channels with 3 terminals/chann el 8 channels with 5 terminals/chann el 16 channels with 3 terminals/chann el 16 channels with 5 terminals/chann el IT6I OF4 (voltage) OF4 (current) VA VB OF6CI OF6VI Y Y OF8 (voltage) OF8 (current) WA WB Y Find the column for the analog I/O module. Follow the column own to see what AIFMs are compatible with the I/O module as indicated by a letter code. When you select the AIFM, use the letter code from this chart to find the compatible cable in the following table for analog pre-wired cable. The letter code must match the last character of the catalog number for the cable. 1756-SG001G-EN-P — March 2004 21 AIFMs for 1757 analog I/O modules Cat. No. Type of AIFM 1492-AIFMPI-3 fusible Description 8 input/output channels The letter code for this AIFM is M. Use the letter code M to find the compatible cable in the following table for analog pre-wired cable. The letter code must match the last character of the catalog number for the cable. Pre-wired cables for analog I/O modules Cat. No.✶ 1492-ACABIExM 1492-ACABLExX 1492-ACABLExY 1492-ACABLExZ 1492-ACABLExTA 1492-ACABLExTB 1492-ACABLExTC 1492-ACABLExTD 1492-ACABLExUA 1492-ACABLExUB 1492-ACABLExUC 1492-ACABLExUD 1492-ACABLExVA 1492-ACABLExVB 1492-ACABLExWA 1492-ACABLExWB Number of Conductors† 11 twisted pairs 9 twisted pairs‡ 9 twisted pairs§ 20 conductors♣ 20 conductors 20 conductors 5 twisted pairs 5 twisted pairs 20 conductors 20 conductors 9 twisted pairs 9 twisted pairs 20 conductors 20 conductors 9 twisted pairs 9 twisted pairs Conductor Size 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG Nominal Outer Diameter 11.5 mm (0.45 in) 6.8 mm (0.27 in) 6.8 mm (0.27 in) 8.4 mm (0.33 in) 8.4 mm (0.33 in) 8.4 mm (0.33 in) 8.4 mm (0.33 in) 8.4 mm (0.33 in) 8.4 mm (0.33 in) 8.4 mm (0.33 in) 6.8 mm (0.27 in) 6.8 mm (0.27 in) 8.4 mm (0.33 in) 8.4 mm (0.33 in) 6.8 mm (0.27 in) 6.8 mm (0.27 in) RTB at the I/O Module End 1757-PIM 1756-TBNH 1756-TBNH 1756-TBNH 1756-TBCH 1756-TBCH 1756-TBCH 1756-TBCH 1756-TBCH 1756-TBCH 1756-TBCH 1756-TBCH 1756-TBNH 1756-TBNH 1756-TBNH 1756-TBNH ✶Cables are available in lengths of 0.5m, 1.0m, 2.5m, and 5.0m. To order, insert the code for the desired cable length into the catalog number in place of the x: 005=0.5m, 010=1.0m, 25=2.5m, 050=5m. Build-to-order cable lengths are also available. †Each cable for analog I/O has an overall shield with a ring lug on a 200mm (8.87 in) exposed drain wire at the I/O module end of the cable. ‡One pair is not connected to the I/O module connector; two additional pairs are not used. §Two pairs are not used. ♣One conductor is not connected to the I/O module connector; one additional conductor is not used. For example, a 1756-IF6I in voltage mode uses: y 1492-AIFM6S-3 interface module y 1492-ACABLExY cable (replace x with the appropriate length) 1756-SG001G-EN-P — March 2004 22 1492 PanelConnect Modules for Connecting Sensors A PanelConnect module and its sensor connection systems lets you connect as many as 16 sensors directly to 16-point input modules using convenient pre-built cables and connectors. The PanelConnect module mounts on the enclosure and creates the correct seal for the entry of the sensor connections. You do not need to seal the opening where the sensor cables enter the enclosure, create custom connectors, or wire to those custom connectors. Cat. No. Connects to These Distribution Boxes Allen-Bradley, Brad Harrison (Daniel Woodhead), Crouse-Hinds, and Lumberg Allen-Bradley, Brad Harrison (Daniel Woodhead), Crouse-Hinds, and Lumberg Turck Allen-Bradley, Brad Harrison (Daniel Woodhead), and CrouseHinds Allen-Bradley Brad Harrison (Daniel Woodhead) Lumberg Turck Turck System Voltage 1492-TPMA1008 ac 1492-TPMA1207 1492-TPMA2209 1492-TPMD1004 1492-TPMD1201 1492-TPMD1202 dc 1492-TPMD1203 1492-TPMD2205 1492-TPMD2206 Connector Style Connectors LEDs 10 pin without 12 pin with 12 pin either with or without 10 pin without 12 pin 12 pin 12 pin 12 pin 12 pin with with with either with or without either with or without mini-plus (1 1/8 in.) metric M23 mini-plus (1 1/8 in.) metric M23 You can select these PanelConnect modules and cables, depending on the 16-point input modules in your system: I/O Module 1492-TPMA1008 ✶ 1756-IA16 1492-CABLExX 1756-IB16 1756-IC16 1756-IN16 1492-CABLExX 1492-TPMA1207 1492-CABLExX 1492-TPMA2209 1492-CABLExX 1492-TPMD1004 1492-TPMD1201 1492-TPMD1202 1492-TPMD1203 1492-TPMD2205 1492-TPMD2206 1492-CABLExX 1492-CABLExX 1492-CABLExX 1492-CABLExX 1492-CABLExX 1492-CABLExX 1492-CABLExX 1492-CABLExX 1492-CABLExX 1492-CABLExX 1492-CABLExX ✶Cables are available in lengths of 0.5m, 1.0m, and 5.0m. To order, insert the code for the desired cable length into the catalog number in place of the x: 005=0.5m, 010=1.0m, 050=5m. Select a patchcord to connect the PanelConnect module to the sensor distribution box, depending on the type of connector: Cat. No.✶ 889N-F10AFNU-x 889N-F12AFNU-x 889N-F10AFNV-x 889N-F12AFNV-x 889N-F10ACNU-x 889N-F12ACNU-x 889N-F10ACNV-x 889N-F12ACNV-x Diameter - mm (in) 17 (0.67) 18 (0.71) 17 (0.67) 18 (0.71) 9 (0.36) 9 (0.36) 9 (0.36) 9 (0.36) Wire Rating 16 AWG 600V 7A 18/22 AWG 300V 3A Connector Type 10 pin Mini-Plus (1 18”), straight male 12 pin Mini-Plus (1 18”), straight male 10 pin Mini-Plus (1 18”), right-angle male 12 pin Mini-Plus (1 18”), right-angle male 10 pin Mini-Plus (1 18”), straight male 12 pin Mini-Plus (1 18”), straight male 10 pin Mini-Plus (1 18”), right-angle male 12 pin Mini-Plus (1 18”), right-angle male ✶Cables are available in lengths of 2m, 3m, 5m, and 10m. To order, insert the code for the desired cable length into the catalog number in place of the x: 2=2m, 3=3m, 5=5m, 10=10m. 1756-SG001G-EN-P — March 2004 23 Placing ControlLogix I/O Modules If the I/O module is: digital The producer/consumer model multicasts messages. This means that multiple nodes can consume the same data at the same time from a single device. Where you place I/O modules in the control system determines how the modules exchange data. And you place the module here: local chassis remote chassis analog The data exchange method is based on: change of state and / or requested packet interval (cyclic) requested packet interval real time sample and / or requested packet interval requested packet interval local chassis remote chassis For a ControlLogix controller to control 1756 I/O, the I/O must be: y in the same chassis as the controller or y on a ControlNet network that is local to that controller or y on an Ethernet/IP network that is local to that controller For example, assume that the network links in this example are either ControlNet or Ethernet/IP links. Both links can be the same, or one link can be a ControlNet link and the other can be an Ethernet/IP link. Chassis A can control the 1756 I/O modules in Chassis A and in Chassis B, but not in Chassis C. The ControlLogix controller in Chassis A can only send messages to the devices in Chassis C. Selecting Controller Ownership Relationship owner controller listen-only connection In a Logix system, modules multicast data. This means that multiple devices can receive the same data at the same time from a single device. When you choose a communication format for an I/O module, you have to choose whether to establish an owner or listen-only relationship with the module. Description The controller that creates the primary configuration and communication connection to a module. The owner controller writes configuration data and can establish a connection to the module. An I/O connection where another controller owns/provides the configuration data for the I/O module. A controller using a listen-only connection only monitors the module. It does not write configuration data and can only maintain a connection to the I/O module when the owner controller is actively controlling the I/O module. 1756-SG001G-EN-P — March 2004 24 How ControlLogix Modules Operate Module Type Placement local chassis digital input remote chassis local chassis digital output remote chassis local chassis analog input remote chassis local chassis analog output remote chassis 1756-SG001G-EN-P — March 2004 In a ControlLogix system, I/O updates occur asynchronous to the execution of logic. This lets your application receive updated data as soon as possible. If your application needs synchronous I/O updates, use the synchronous copy (CPS) instruction to buffer I/O data at the beginning of each scan. Operation The RPI specifies the rate at which a module multicasts its data. The time ranges from 200 microseconds to 750 milliseconds. When the specified time frame elapses, the module will multicast data (also called cyclic data exchange). If a change of state (COS) does not occur within the RPI timeframe, 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. The RPI and COS values still define when the module multicasts data within its own chassis, but only the value of the RPI determines when the owner controller receives the data over the network. When an RPI value is specified for an input module in a remote chassis, in addition to instructing the module to multicast data within its own chassis, the RPI also reserves a spot in the stream of data flowing across the control network. The timing of this reserved spot may or may not coincide with the exact value of the RPI, but the owner-controller will receive data at least as often as the specified RPI. If the module resides in the same chassis as the owner-controller, the module receives the data almost immediately after the owner-controller sends it. Data is sent after all the programs within each task have completed executing. If an output module resides in a chassis other than that of the owner-controller (i.e. a remote chassis connected via ControlNet or Ethernet/IP), the owner-controller sends data to the output module only at the RPI rate. The RPI also reserves a spot in the stream of data flowing across the control network. The timing of this reserved spot may or may not coincide with the exact value of the RPI, but the output module receives data at least as often as the specified RPI. The RTS value specifies when the module scans its channels and multicasts the data (update the input data buffer then multicast). The RPI value specifies when the module multicasts the current contents of the input data buffer without scanning (updating) the channels. The module resets the RPI timer each time an RTS transfer occurs. If the RTS value is less than or equal to the RPI value, each multicast of data from the module has newly updated channel data. The module only multicasts at the RTS rate. If the RTS value is greater than the RPI, the module multicasts at both the RTS rate and the RPI rate. The RPI and RTS rates still define when the module multicasts data within its own chassis, but only the RPI value determines when the owner-controller receives the data over the network. The RPI also reserves a spot in the stream of data flowing across the control network. The timing of this reserved spot may or may not coincide with the exact value of the RPI, but the controller receives data at least as often as the specified RPI. The RPI value specifies when the owner-controller broadcasts output data to the module. If the module resides in the same chassis as the owner-controller, the module receives the data almost immediately after the owner-controller sends it. If an output module resides in a chassis other than that of the owner-controller (i.e. a remote chassis connected via ControlNet or Ethernet/IP), the owner-controller sends data to the output module only at the RPI rate. The RPI also reserves a spot in the stream of data flowing across the control network. The timing of this reserved spot may or may not coincide with the exact value of the RPI, but the output module receives data at least as often as the specified RPI. 25 Step 2 - Select: ! size the motion application (use Motion Book) ! how you want to interface the controller Selecting Motion Control Requirements and drives ! a SERCOS or analog interface module ! associated cable(s) ! a removable terminal block (RTB) - only needed for the analog interface modules ! select drives, motors, and accessories (use Motion Book) The Logix approach to motion control employs synchronized, distributed processing and provides a highly-integrated motion solution. Logix integrates sequential and motion control to bring unmatched flexibility to machine design and unprecedented efficiency to the manufacturing floor. RSLogix 5000 Enterprise series software supports a comprehensive set of embedded motion instructions that can be programmed using the relay ladder, structured text, or sequential function chart editors. The embedded motion instructions satisfy a wide range of machine control needs, including independent axis motion, synchronized gearing and camming, and fully-interpolated motion in three dimensions. The Logix architecture supports motion components that work in a wide variety of machine architectures: ! The Kinetix integrated motion solution uses a SERCOS interface™ module to perform complex, multi-axis, synchronized motion. With a Kinetix system, you reap the full benefit of the integrated architecture because the integration doesn’t stop at the controller. This system integrates the drive, the motor, and even the actuator at a lower cost per axis of motion. ! Logix integrated motion using the analog family of servo modules for controlling drives/actuators that do not support the SERCOS interface. The analog family of servo modules provide a ±10 voltage analog output and can interface with a variety of feedback device types including rotary/linear absolute and incremental. ! Networked motion provides the ability to connect via DeviceNet to a single-axis drive to perform simple, point to point indexing. You need Ultraware™ software for drive and indexing configuration. Use this selection guide to select the appropriate motion interface. For more information, use: ! Motion Book to size your motion application and to make final component selection. Motion Book is available on The Automation Bookstore (www.theautomationbookstore.com) and the Rockwell Automation motion website (www.ab.com/motion/software/motion_book.html) ! the Motion Control Selection Guide, publication GMC-SG001, to verify drive, motor, and accessory specifications 1756-SG001G-EN-P — March 2004 26 Selecting a Motion Interface You can communicate directly to a servo drive using a motion interface or over a network. Communicate directly to a servo drive The controller can control these servo drives through these motion interfaces: If your application requires: Select this motion interface: ! Rockwell Automation SERCOS interface drives ! ! ! ! ! ! ! ! ! ! analog command signal quadrature feedback analog command signal LDT feedback analog command signal SSI feedback 1756-M16SE (16 axes) 1756-M08SE (8 axes) 1756-M03SE (3 axes) 1756-L60M03SE (3 axes) 1756-M02AE 1756-HYD02 1756-M02AS Communicate over a network Some servo drives are supported through communication interface modules. The controller can communicate with these servo drives over these networks: Drives✶ 1394 GMC drive and control 2098 Ultra3000 DeviceNet servo drive 2098 Ultra5000 intelligent positioning EtherNet/IP ControlNet DeviceNet Universal Remote I/O RS-232 Serial DH-485 no no no yes yes yes no no yes no no no no no yes no yes no ✶Each drive has different options you order for its supported communication networks. See the appropriate catalog or selection information for a drive to make sure you select the appropriate option when specifying a drive for a specific network. For more information on drives, motors, and accessories, see the Motion Control Selection Guide, publication GMC-SG001. 1756-SG001G-EN-P — March 2004 27 SERCOS Interface Modules The SERCOS interface servo modules serve as a link between the ControlLogix platform and intelligent, servo drives. SERCOS is the IEC 61491 SErial Real-time COmmunication System protocol over a fiber optic medium. The SERCOS interface is an open, controller-to-digital drive interface designed for high-speed, real time, serial communications using noise-immune, fiber-optic cables. The SERCOS interface modules use a single, digital fiber optic link, which eliminates up to 18 discrete wires per axis. Detailed drive status information can be sent from drive to controller and from controller to drive. The modules are compatible with the RSLogix 5000 motion instructions set (38 motion instructions) and axis configuration utilities. The motion instructions provide a wide range of motion capability, including point-point positioning, gearing, position and time-based camming, and multi-axis linear and circular motion. The SERCOS interface modules can connect to these servo drives: ! 2094 Kinetix 6000 servo drive ! 2098 Ultra3000 SERCOS servo drive ! 1394C SERCOS drive ! 8720MC spindle Cat. No. 1756-M03SE 1756-L60M03SE✶ 1756-M08SE 1756-M16SE Number of Axes, per Module, Max. 3 3 SERCOS axes included 6 axes total with addition of another motion module 8 16 Number of Axes, per Controller, Max. 32 Power Dissipation 5.0 W Backplane Current (mA) Backplane Current (mA) at 5V at 24V SERCOS Data Rate 900 mA 2.5 mA 32 8.5 W 1960 mA 16.5 mA 32 5.0 W 900 mA 2.5 mA 4 Mbits or 8 Mbits per second Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE ✶The 1756-L60M03SE is a 1756-L60 ControlLogix controller with an embedded 1756-M03SE SERCOS interface. This is a 2-slot module. 1756-SG001G-EN-P — March 2004 28 Cables for Use with the SERCOS Interface Modules Cat. No. 2090-SCEPx-x (no jacket) 2090-SCVPx-x (standard jacket) 2090-SCNPx-x (nylon jacket) 2090-SCVGx-x Select one of these fiber optic cables to connect the SERCOS interface module to the drive: Description Plastic Fiber Optic Cables✶ 1000 µm plastic simplex fiber optic cable transmission range of 1-32 meters. Allen-Bradley offers plastic, fiber-optic cable assemblies that come in a variety of jackets: ! no jacket (Chlorinated Polyethylene) for use inside an electrical cabinet ! a standard jacket (Polyvinyl Chloride) for use outside of electrical cabinets ! a nylon jacket for use in harsh environments Glass Fiber Optic Cables† 200 µm glass fiber optic cable transmission range of 1-200 meters Allen-Bradley offers glass, fiber-optic cable assemblies that come with a standard jacket (Polyvinyl Chloride) for use in normal environments. ✶The x-x determines the length in meters. Specify 0-1 for 0.1m, 0-3 for 0.3m, 1-0 for 1m, 3-0 for 3m, 5-0 for 5m, 8-0 for 8m, 10-0 for 10m, 15-0 for 15m, 20-0 for 20m, 25-5 for 25m, or 32-0 for 32m. †The x-x determines the length in meters. Specify 1-0 for 1m, 5-0 for 5m, 8-0 for 8m, 10-0 for 10m, 15-0 for 15m, 20-0 for 20m, 25-0 for 25m, 32-0 for 32m, 50-0 for 50m, 100-0 for 100m, 150-0 for 150m, or 200-0 for 200m. Both the transmitter and receiver connections use a F-SMA standard plug that conforms to the F-SMA screw type connector. 1756-SG001G-EN-P — March 2004 29 Analog Interface Modules The ControlLogix family of analog servo modules is a cost effective option for closedor open-loop motion control of devices that support an analog interface. The analog servo modules provide an ±10 volt analog output command reference and support a variety of different position feedback devices. As many as two axes can be controlled per module, and multiple modules can be used to provide as many as 32 axes of control per ControlLogix controller. The modules are compatible with the RSLogix 5000 motion instructions set (38 motion instructions) and axis configuration utilities. The motion instructions provide a wide range of motion capability, including point-point positioning, gearing, position and time-based camming, and multi-axis linear and circular motion. Select the appropriate analog interface module: This interface module: 1756-M02AE 1756-HYD02 1756-M02AS Offers: The 1756-M02AE is a two-axis servo module optimized for control of drives/actuators which require an ±10 volt velocity or torque reference input. The 1756-M02AE provides a quadrature position feedback output and is compatible with a wide range of quadrature output rotary and linear transducers. The 1756-HYD02 is a two-axis servo module optimized for control of hydraulic actuators which require an ±10 volt velocity reference input. The 1756-HYD02 provides an LDT feedback input. Typical actuators include hydraulic motors and hydraulic cylinders. The 1756-HYD02 is compatible with a wide range of magnostrictive linear transducers (LDT) feedback devices. Compatible LDTs include: ! Temposonics II: RPM or DPM ! Balluff: BTL-2-L2 or BTL-2-M2 ! Santest: GYRP or GYRG ! Gemco Quick-Stick II: 951 VP or 951 RS The 1756-M02AS is a two-axis servo module optimized for control of drives/actuators which require an ±10 volt velocity or torque reference input. The 1756-M02AS provides a Serial Synchronous Input (SSI) position feedback output and is compatible with a wide range of quadrature output rotary and linear transducers. SSI devices are available in many versions: ! linear absolute and incremental encoders ! rotary absolute and incremental encoders ! linear absolute glass scales ! linear magnostrictive ! linear laser distance 1756-SG001G-EN-P — March 2004 30 Cat. No. Number of Axes, per Module, Max. Number of Axes, per Controller, Max. 1756-M02AE 1756-HYD02 2 32 1756-M02AS Power Dissipation Backplane Current (mA) at 5V Backplane Current (mA) at 24V 5.5 W 700 mA 2.5 mA 5.5 W 700 mA 2.5 mA 5.5 W 700 mA 2.5 mA Removable Terminal Block Housing 1756-TBCH 1756-TBS6H✶ 1756-TBCH 1756-TBS6H✶ 1756-TBCH 1756-TBS6H✶ Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE ✶Maximum wire size will require the extended depth RTB housing (1756-TBE). The following example shows a sample configuration using the 1756-HYD02 analog interface module. 1756-SG001G-EN-P — March 2004 31 Step 3 - Select: y networks y communication modules y associated cable(s) and network equipment Selecting Network Communications y sufficient modules and cables if you are planning a redundant system Separate communication interface modules are available for different networks. Install multiple communication interface modules into the ControlLogix backplane to configure a gateway to bridge or route control and information data between the different networks. Messages are sent directly from one communication interface module across the backplane to another. You can route a message through a maximum of 4 chassis (8 communication hops). You do not need a ControlLogix controller in the chassis. NetLinx Open Network Architecture NetLinx Open Network Architecture is the Rockwell Automation strategy of using open networking technology for seamless, top-floor to shop-floor integration. The networks in the NetLinx architecture – DeviceNet, ControlNet, and EtherNet/IP – speak a common language and share a universal set of communication services. NetLinx architecture, part of the Integrated Architecture, seamlessly integrates all the components in an automation system from a few devices on one network to multiple devices on multiple networks including access to the Internet – helping you to improve flexibility, reduce installation costs, and increase productivity. y EtherNet/IP is an open industrial networking standard that supports implicit and explicit messaging and uses commercial, off-the-shelf Ethernet equipment and physical media. y ControlNet allows intelligent, high-speed control devices to share the information required for supervisory control, work-cell coordination, operator interface, remote device configuration, programming, and troubleshooting. y DeviceNet offers high-speed access to plant-floor data from a broad range of plantfloor devices and a significant reduction in wiring. 1756-SG001G-EN-P — March 2004 32 Selecting a network You can configure your system for information exchange between a range of devices and computing platforms and operating systems. If your application requires: y plant management (material handling) y configuration, data collection, and control on a single, high-speed network y time-critical applications with no established schedule y data sent regularly y Internet/Intranet connection y high-speed transfer of time-critical data between controllers and I/O devices y deterministic and repeatable data delivery y media redundancy y controller redundancy y intrinsic safety y redundant controller systems y connections of low-level devices directly to plant floor controllers, without interfacing them through I/O modules y data sent as needed y more diagnostics for improved data collection and fault detection y less wiring and reduced start-up time than a traditional, hard-wired system y plantwide and cell-level data sharing with program maintenance y data sent regularly y transfer of information between controllers y connections between controllers and I/O adapters y data sent regularly y distributed control so that each controller has its own I/O and communicates with a supervisory controller y Fieldbus transmitters and actuators y closed-loop control y process automation y modems y supervisory control and data acquisition (SCADA) y connections to existing DH-485 networks Use this network: Select: EtherNet/IP network 1756-ENBT 1756-EWEB ControlNet network 1756-CNB, -CNBR DeviceNet network 1756-DNB Data Highway Plus 1756-DHRIO Universal Remote I/O network 1756-DHRIO Fieldbus network 1788-CN2FF built-in serial port 1756-MVI, -MVID built-in serial port serial network DH-485 network For more specialized communication requirements, select: If your application requires: SynchLink fiber optic communications to: y controllers y power distribution systems y PowerFlex 700S AutoMax DCS network communications remote access to controllers 1756-SG001G-EN-P — March 2004 Use this: 1756-SYNCH 1756-DMxxx 56AMXN 9300-RADKIT 33 EtherNet/IP Network Ethernet Industrial Protocol (EtherNet/IP) is an open industrial networking standard that supports both real-time I/O messaging and message exchange. It emerged due to the high demand for using the Ethernet network for control applications. EtherNet/IP uses off-the-shelf Ethernet communication chips and physical media. Because Ethernet technology has been used since the mid 1970s and is widely accepted throughout the world, Ethernet products serve a large community of vendors. EtherNet/IP product capability Recipient EtherNet/IP PLC-5 or SLC 5/05 processor PLC-5 processor via 1785-ENET Logix controller✶ 1756-ENBT module✶ 1734-AENT 1794-AENT FLEX POINT I/O I/O adapter adapter PanelView EtherNet/IP terminal RSLinx software CompactLogix controller with 1761-NET-ENI interface information na not supported not supported information information information information information na not supported not supported information information information information information I/O data interlocking I/O data I/O data I/O data information I/O data information information information information I/O data na na na na na information information information na not supported not supported na information information information information na not supported not supported information information information EtherNet/IP PLC-5 or SLC 5/05 processor PLC-5 processor Logix via 1785-ENET controller✶ information information information information PanelView EtherNet/IP information terminal RSLinx information software CompactLogix controller with information 1761-NET-ENI interface† ✶ For EtherNet/IP control: y a ControlLogix controller requires a 1756-ENBT or 1756-ENET series B module y a FlexLogix controller requires a 1788-ENBT card y a CompactLogix controller must be a 1769-L32E or 1769-L35E controller y the PC for a SoftLogix5800 controller requires appropriate hardware for Ethernet communications †To be an originator, the 1761-NET-ENI interface must connect to the other device through that device’s RS-232 port. 1756-SG001G-EN-P — March 2004 34 Ethernet interfaces Select the appropriate Ethernet interface: If your application does this: Select this interface: Description: y controls I/O modules y requires an adapter for disibuted I/O on EtherNet/IP links 1756-ENBT y communicates with other EtherNet/IP devices (messages) y bridges EtherNet/IP links to route messages to devices on other networks The EtherNet/IP communication module: y control I/O over an EtherNet/IP network y acts as an adapter for disitributed I/O on remote EtherNet/IP links y bridge EtherNet/IP links to route messages to devices on other networks y requires remote access via Internet browser to tags in a local ControlLogix controller y communicates with other EtherNet/IP 1756-EWEB devices (messages) y bridges EtherNet/IP links to route messages to devices on other networks The enhanced web server module provides Internet browser access to ControlLogix controllers so you can monitor and modify data remotely via XML web pages. The web server module supports: y data access (read and write) to ControlLogix controllers y bridging and routing of messages y custom web pages y email capability Cat. No. Communication Rate 1756-ENBT 1756-EWEB 10/100 Mbps ConnectionsConnections Each module supports a maximum of: y 64 TCP/IP connections y 128 Logix connections (I/O and information y 5000 messages/second Power Dissipation, Max. 3.65 W Backplane Current (mA) at 5V 700 mA Backplane Current (mA) at 24V 3 mA 3.65 W 700 mA 3 mA Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM, C-Tick ETHERNET RS232 FAUL AULT NET TX/RX TX/RX IP PWR CABLE EXTERNAL 1756-SG001G-EN-P — March 2004 35 ControlNet Network The ControlNet network is an open, state-of-the-art control network that meets the demands of real-time, high-throughput applications. The ControlNet network uses the proven Common Industrial Protocol (CIP) to combine the functionality of an I/O network and a peer-to-peer network providing high-speed performance for both functions. The ControlNet network gives you deterministic, repeatable transfers of all missioncritical control data in addition to supporting transfers of non-time-critical data. I/O updates and controller-to-controller interlocking always take precedence over program uploads and downloads and messaging. Cat. No. 1756-CNB 1756-CNBR Communication Rate Connections 5 Mbps 64 connections per module Cable RG-6 coaxial cable 1786-RG6 (shield high flex cable) 1786-RG6F (quad shield high flex coax cable) 1786-XT termination resistor Choose taps: y 1786-TPR (T-tap right angle) y 1786-TPS (T-tap straight) y 1786-TPYR (Y-tap right angle) y 1786-TPYS (Y-tap straight) Power Dissipation, Max. 5.14 W Backplane Current (mA) at 5V 970 mA Backplane Current (mA) at 24V 2 mA 5.14 W 1000 mA 2 mA Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM, C-Tick 1756-SG001G-EN-P — March 2004 36 Redundant controller systems via ControlNet You can build a redundant controller system around a ControlNet network. In each redundant controller chassis, you can have: y one or two 1756-L55 controllers or one 1756-L6x controller in each redundant chassis y at least one, but no more than five, 1756-CNB(R) series D, version 5.23 (or greater) communication modules in each redundant chassis y one 1757-SRM module in each redundant chassis y the redundant chassis can contain a 1756-ENBT communication module, but no other I/O or communication modules can be in the redundant chassis All I/O must be remote from the redundant controllers. ControlLogix redundancy works with remote 1756 I/O, FLEX I/O, drives, operator interfaces, or any other devices that can communicate with a ControlLogix controller over a ControlNet link. To connect to other networks, bridge through another ControlLogix chassis (not one of the redundant controller chassis) The secondary controller is synchronized with the primary controller to provide a bumpless switchover for any outputs controlled by logic in the highest priority task. Switchover occurs within 100msec. 1756-SG001G-EN-P — March 2004 37 Make sure that your ControlNet network contains at least two nodes in addition to the redundant chassis pair. And additional node can be: y a second 1756-CNBR module in the same remote chassis or in a different remote chassis y any ControlNet device y a workstation running RSLinx software 1757-SRM redundancy module The 1757-SRM redundancy module provides high-speed data transfers between the primary and secondary chassis. You need one 1757-SRM module per chassis. The module supports as many as five 1756-CNB modules per chassis. Cat. No. Cable Choose: y 1757-SRC1 (1m) y 1757-SRC3 (3m) 1757-SRM y 1757-SRC10 (10m) y 1757-SRC50 (50m) y 1757-SRC100 (100m) Voltage/Current 30V ac/dc maximum 100 mA maximum Current Capacity (Amps) Power Dissipation, Max. at 3.3V 0.75 A Backplane Current (mA) at 5V Backplane Current (mA) at 24V 1.0 A 0.09 A Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM, C-Tick Connecting to other devices via ControlNet The RSLogix 5000 Enterprise Series software supports a generic ControlNet module that allows connections to ControlNet nodes for which there is no specific support currently available in the programming software. A module configured as a generic ControlNet module communicates with the controller in the form of input, output, status, and configuration tags. These tags and their characteristics vary depending on the type of module. For example, use the generic module configuration to set up communications between a ControlLogix controller and a 1203-CN1 ControlNet communication module. Then use the CIP generic MSG instruction type to send and receive messages from the 1203-CN1 module. 1756-SG001G-EN-P — March 2004 38 DeviceNet Network Cat. No. Communication Rate y 125 Kbps 1756-DNB y 250 Kbps y 500 Kbps Connections 2 connections to dedicated ControlLogix controller Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM, C-Tick 1756-SG001G-EN-P — March 2004 The DeviceNet network is an open low-level network that provides connections between simple industrial devices (such as sensors and actuators) and higher-level devices (such as PLC controllers and computers). The DeviceNet network uses the proven Common Industrial Protocol (CIP) to provide the control, configure, and data collection capabilities for industrial devices. The DeviceNet network is a flexible network that works with devices from multiple vendors. Cable Choose: y KwikLink™ flat media y thick trunk round media y thin trunk round media Power Dissipation, Max. Backplane Current (mA) at 5V Backplane Current (mA) at 24V 5.3 W 600 mA 3 mA 39 DH+ and Universal Remote I/O Networks Cat. No. The DH+ and remote I/O module supports messaging between devices on DH+ networks. The remote I/O functionality enables the module to act as a scanner for transferring discrete and block-transfer data to and from remote I/O devices. Communication Rate Connections 32 connections per DH+ channel y 57.6 Kbps 1756-DHRIO y 115.2 Kbps y 230.4 Kbps Cable 1770-CD Belden 9463 32 logical rack connections per remote I/O channel 150Ω and 82Ω 16 block-transfer connections per remote I/O termination resistors channel ship with the module Power Dissipation, Max. Backplane Current (mA) at 5V Backplane Current (mA) at 24V 4.5 W 850 mA 2 mA Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM, C-Tick DH+ example configuration Universal remote I/O example configuration 1756-SG001G-EN-P — March 2004 40 Foundation Fieldbus Network Foundation Fieldbus™ is a communications network created by the Fieldbus Foundation. It is a protocol designed for robust, distributed control of process control applications. Devices connected by a Foundation Fieldbus network can be used for sophisticated, highly-distributed process control. Select the appropriate Foundation Fieldbus interface: If your application bridges to Foundation Fieldbus from: Select this interface: ControlNet 1788-CN2FF EtherNet/IP 1757-FFLD Cat. No. 1788-CN2FF Communication Rate 2 ms over ControlNet 31.25 Kbps over Fieldbus 1757-FFLD2 10/100 Mbps over EtherNet/IP 1757-FFLD4 31.25 Kbps over Fieldbus Description: The 1788-CN2FF linking device adds Foundation Fieldbus support to your ControlLogix system. You can have one linking device per ControlNet tap. The device connects to two, independent Fieldbus H1 networks. The 1756-FFLD linking device bridges from Ethernet to H1. It accepts either HSE or EtherNet/IP messages and converts them to the H1 protocol. By supporting H1, HSE and EtherNet/IP protocols, the 1756-FFLD is capable of providing bridging capability of Rockwell Automation products and Foundation Fieldbus products on Ethernet to products on H1 links. Connections Backplane Current (mA) at 24V two H1 networks 270 mA two H1 networks four H1 networks 300 mA 300 mA Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM, C-Tick 1788-CN2FF example configuration 1757-FFLD example configuration FOUN DATION Fieldbus H1-1H1 H1-2H1 FOUN DATION Fieldbus Linking Device H1-3H1 H1-4H1 STATUS WDO G B AT T NS 1 MODE Serial Network The serial port is compatible with RS-232 serial communication. The serial port supports the DF1 protocol to communicate with other devices on the serial link. You can select: Use this DF1 mode: For: point to point communication between a controller and other DF1-compatible devices using DF1 full-duplex protocol control of polling and message transmission between the master and each slave using DF1 half-duplex polled protocol using the controller as a slave station in a master/slave serial network using DF1 half-duplex protocol communication between a controller and an ASCII device, such as a bar code reader DF1 master DF1 slave user mode (ASCII) 1756-SG001G-EN-P — March 2004 41 Use a 1756-CP3 cable to connect to the serial port. Over the serial port, the ControlLogix controller supports 12 message buffers. At most, you can have 4 simultaneous connected messages and 8 simultaneous unconnected messages. Or if all the messages are unconnected, you can have 12 simultaneous messages. If a message is greater than 250 bytes, it is divided across enough buffers to carry the message, which reduces the number of buffers remaining for other simultaneous messages. 1756-MVI, -MVID multi-vendor interface module The multi-vendor interface module provides additional access to serial devices. The module is programmable to accommodate devices with unique serial protocols. Cat. No. 1756-MVI Communicatio n Rate Connections Configurable, depending on 1756-MVID (1756-MVI module and API software) serial protocol PRT1: RS-232 PRT2: RS-232, RS-422, RS-485 PRT3: RS-232, RS-422, RS-485 Power Dissipation, Max. Cable 3 serial adapter cables ship with the module. At one end of the cables is a locking4W type RJ-45 connector to the module; at the other end is a DB-9 male connector. Backplane Backplane Current (mA) at Current (mA) at 5V 24V 800 mA 3 mA Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM, C-Tick Modbus support To use Logix5000 controllers on Modbus, you connect through the serial port and execute a specific ladder logic routine. The ladder logic routine is available on the CD for RSLogix 5000 Enterprise programming software. For more information, see Using Logix5000 Controllers as Masters or Slaves on Modbus Application Solution, publication CIG-AP129A-EN-P. 1756-SG001G-EN-P — March 2004 42 DH-485 Network On the DH-485 network, the controller can send and receive messages to and from other controllers on the network. The DH-485 connection does support remote programming and monitoring via RSLogix 5000 software. However, excess traffic over a DH-485 connection can adversely affect overall performance and can lead to timeouts and loss in RSLogix 5000 configuration performance. Important: Only use Logix controllers on DH-485 networks when you want to add controllers to an existing DH-485 network. For new applications with Logix controllers, networks in the NetLinx architecture are the recommended networks. You need a 1761-NET-AIC+ converter for each controller you want to put on the DH485 network. You can have two controllers per one 1761-NET-AIC+ converter, but you need a different cable for each controller. Connect one controller to port 1 (9-pin connector) and one controller to port 2 (mini-DIN connector). If you connect to this port: port 1 DB-9 RS-232, DTE connection port 2 mini-DIN 8 RS-232 connection 1756-SG001G-EN-P — March 2004 Use this cable: 1747-CP3 or 1761-CBL-AC00 1761-CBL-AP00 or 1761-CBL-PM02 43 SynchLink SynchLink provides time synchronization and data broadcasting capabilities for distributed motion and coordinated drive control. 1756-SYNCH SynchLink module The 1756-SYNCH SynchLink module connects a ControlLogix chassis to a SynchLink fiber optic communications link. The module: y coordinates CST time across multiple ControlLogix chassis y moves limited amount of data from one chassis to another at a high speed y lets one controller consume motion axes data from a controller in another chassis Cat. No. Communication Rate operating wavelength: 650 nm (red) 1756-SYNCH data rate: 5 Mbps baud rate: 5 Mbps Cable Order 1403-CF xxx cable or from Lucent Technologies, Specialty Fiber Technologies division✶ Power Dissipation, Max. Backplane Current (mA) at 5V Backplane Current (mA) at 24V 6.19 W 1200 mA 2.5 mA maximum length 200/230 micron Hard Clad Silica (HCS) Versalink V-System300 m minimum length 1 m Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE ✶The xxx determines the length. Select 001, 003, 005, 010, 020, 050, 100, or 250 meters. Star configuration Requires: 1751-SLBA base block 1751-SL4SP 4-port splitter block Supports: 2 layers of hubs 16 end nodes per hub 257 nodes (including master node) per star network Daisy chain configuration Optional: 1751-SLBP bypass switch block Supports: 10 nodes (including master and end nodes) per daisy chain network Ring configuration Optional: 1751-SLBP bypass switch block Supports: 10 nodes (including master and end nodes) per ring network 1756-SG001G-EN-P — March 2004 44 1756-DMxxx module The 1756-DM drive module lets you update and retrofit Reliance distributed power system (DPS) installations to ControlLogix-based systems. Each drive module interfaces with an individual Power Module Interface (PMI) chassis. You can also use the 1756-DM to modernize existing power bridges from analog to digital control. Cat. No.✶ Communicates with 1756-DMD30 1756-DMF30 1756-DMA30 1756-DMA31 SD3000 dc drive SF3000 Regen field control SA3000 ac drive SA3100 ac drive ✶The 1756-DM modules are only available through Drive Systems. Cat. No. 1756-DMxxx SynchLink values Operating Wavelength Data Rate 650 nM (red) 5 Mbps 820 nM 1756-DMxxx Drive communications values (infrared) 10 Mbps Cable Maximum Node Count 200/230 micron Hard Clad Silica (HCS); VersaLink Vsystem Order 1403-CF xxx power monitoring cable or from 10 daisy chain configuration Lucent Technologies, Specialty Fiber Technologies 256 star configuration with division✶ multiplexing blocks maximum length 300m minimum length 1m 62.5/125 micron glass; one pair SC Style and one pair ST Style Order 1756-DMCF xxx drive communications fiber optic cable or breakout cable from Belden 225362 or Mohawk M92021† 1 PMI chassis maximum length 300m minimum length 1m Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE ✶The xxx determines the length. Select 001, 003, 005, 010, 020, 050, 100, or 250 meters. †The xxx determines the length. Select 001, 003, 010, or 030 meters. Existing power systems 1756-SG001G-EN-P — March 2004 Distributed power systems Backplane Current (mA) at 5V Backplane Current (mA) at 24V 1.35 A 3.0 mA 45 56AMXN AutoMax Network and RE Remote I/O The 56AMXN module connects a ControlLogix system to an AutoMax DCS network or to an AutoMax Remote I/O network. The traditional Reliance Electric Systems solution is based on an AutoMax controller and architecture. DCSNet is the main communications, data, and control network or “backbone”. RE RIO is the Remote I/O architecture to network devices such as I/O and MMI or HMI operator stations. You configure the 56AMXN as a generic module. The module supports scheduled data up to 250 words of input, 248 words of output, and 250 words of status data. The module supports RPIs from .2 to 750ms. As a: The 56AMXN module: y y y y y y y DCSNet master DCSNet slave RE remote I/O master Cat. No. 56AMXN Communication Networks and Supported Modes DCS network: master or slave RE remote I/O network: master Scans up to 55 drops with 32 words in and 32 words out per drop Transmits 8 words of global broadcast data every 2.8ms Maintains standard drop 0 diagnostic counters Acts as any drop number from 1 to 55, with drop depth from 1 to 55 (“active drops”) Monitors input and output data on other drops on the network (“monitored drops”) Scans up to 7 drops, with up to 248 words of output data and 250 words of input data Maintains standard diagnostic counters Cable Drop cable (612574-36R, 3ft long with 9-pin D-shell connectors) and passive tap (M/N 57C380, BNC connectors) connects the module to the network cable. Power Dissipation, Max. Backplane Current (mA) at 5V Backplane Current (mA) at 24V 5.0 W 650 mA 75 mA For DCS, the network cable can be RG-59/U or RG-11/U. For remote I/O, the cable must be RG-59/U. Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE 1756-SG001G-EN-P — March 2004 46 Accessing the Controller Remotely Remote access dial-in kits let you connect via modem to a remote site’s network and controller. Once connected, you can monitor the process, collect data, and make program changes remotely. Each remote access dial-in kit includes: y pre-configured modem y communication module y DIN rail mounting hardware y associated cables Each kit also includes a CD-ROM-based installation guide and tutorial that takes you step-by-step through establishing a remote dial-in connection. Cat. No. Communication Supported Controllers 9300-RADES 56K modem connection to devices on Ethernet 9300-RADKIT 56K modem connection to devices on DH+ or DH-485 y y y y y ControlLogix, CompactLogix, FlexLogix controllers MicroLogix controllers Enhanced PLC-5 processors SLC 5/03, 5/04, 5/05 processors 1203-SSS Power Requirements 8-48V dc 200 mA at 24V dc 8-48V dc 100 mA at 12V dc The modem supports remote configuration, so you can modify the remote network modem’s command settings through a dial-up connection. This helps you recover modem communication if a change occurs in the controller’s channel configuration. The remote access modem also has call-back security which is authenticated with a password. 1756-SG001G-EN-P — March 2004 47 Step 4 - Select: y a controller with sufficient memory Selecting Controllers y memory board for each 1756-L55 controller y 1756-BATM for larger memory size 1756-L55 controllers and all 1756-L6x controllers y replacement batteries The ControlLogix controller provides a scalable controller solution that is capable of addressing a large amount of I/O points (128,000 digital maximum / 4000 analog maximum). The ControlLogix controller can be placed into any slot of a ControlLogix I/O chassis and multiple controllers can be installed in the same chassis. Multiple controllers in the same chassis communicate with each other over the backplane (just as controllers can communicate over networks) but operate independently. ControlLogix controllers can monitor and control I/O across the ControlLogix backplane, as well as over I/O links. ControlLogix controllers can communicate with computers or other processors across RS-232-C (DF1/DH-485 protocol), DeviceNet, DH+, ControlNet, and EtherNet/IP networks. To provide communication for a ControlLogix controller, install the appropriate communication interface module into the chassis. The multi-tasking operating system supports 32 configurable tasks that can be prioritized. One task can be continuous. The others must be periodic or event tasks. Each task can have as many as 32 programs, each with its own local data and logic, allowing virtual machines to operate independently within the same controller. Specification Battery Programming Cable Description 1756-BA1 (94194801) - comes with the controller or 1756-BATM (contains a 1756-BATA battery assembly)✶ 1756-CP3 or 1747-CP3 serial cable Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM (1756-L6x controllers only), C-Tick, EEx ATEX ✶The battery module is highly recommended for all controllers. 1756-SG001G-EN-P — March 2004 48 ControlLogix Controllers Memory Cat. No. 1756-L55M12 1756-L55M13 1756-L55M14 Data and Logic✶ 750 K bytes 1.5 Mbytes 3.5 Mbytes 7.5 Mbytes 1756-L55M16 ≤ 3.5 Mbytes of data 750 K bytes 1756-L55M22 1.5 Mbytes 1756-L55M23 3.5 Mbytes 1756-L55M24 2 Mbytes 1756-L61 4 Mbytes 1756-L62 8 Mbytes 1756-L63 1756-L60M03SE§ 750 Kbytes I/O† 208 Kbytes 208 Kbytes 208 Kbytes Nonvolatile Memory no no no Power Dissipation, Max. 5.6 W 5.6 W 5.7 W Thermal Dissipation, Max. 19.1 BTU/hr 19.1 BTU/hr 19.4 BTU/hr Backplane Current (mA) at 5V 1.23 A 1.23 A 1.25 A Backplane Current (mA) at 24V 0.014 A 0.014 A 0.014 A 208 Kbytes no 6.3 W 21.5 BTU/hr 1.48 A 0.014 A 208 Kbytes 208 Kbytes 208 Kbytes 478 Kbytes 478 Kbytes 478 Kbytes 478 Kbytes yes yes yes CompactFlash card† CompactFlash card† CompactFlash card† CompactFlash card† 5.6 W 5.6 W 5.7 W 3.5 W 3.5 W 3.5 W 8.5 W 19.1 BTU/hr 19.1 BTU/hr 19.4 BTU/hr 11.9 BTU/hr 11.9 BTU/hr 11.9 BTU/hr 11.9 BTU/hr 1.23 A 1.23 A 1.25 A 1.20 A 1.20 A 1.20 A 1.96 A 0.014 A 0.014 A 0.014 A 0.014 A 0.014 A 0.014 A 0.0165 A ✶Data and logic memory stores: tags other than I/O, produced, or consumed tags; logic routines; and communication with OPC/DDE tags that use RSLinx software (also uses I/O memory). †I/O memory stores: I/O tags, produced tags, consumed tags, communication via MSG instructions, communication with workstations, and communication with OPC/DDE tags that use RSLinx software (also uses data and logic memory). ‡The CompactFlash card is available separately as 1784-CF64. §The 1756-L60M03SE is a 1756-L60 ControlLogix controller with an embedded 1756-M03SE SERCOS interface. This is a 2-slot module. The 1756-L6x controller executes ladder scans almost twice as fast as the 1756-L55 controllers and executes function block, REAL data type math, and motion instructions 4-5 times faster than the 1756-L55 controllers. The 1756-L60M03SE controller combines a 1756-L6x controller and a SERCOS motion module in a two-slot module. This controller is ideal for small motion systems and can control 3 SERCOS axes with the included interface. This controller can control as many as 6 axes if you add an additional motion module. Selecting a controller for a redundant controller system If you are designing a redundant controller system, consider: y Redundant controller systems support one or two 1756-L55 controllers or one 1756-L6x controller in each redundant chassis. y Data is buffered in the secondary controller, so twice as much data memory space is required in the controller. y The redundant controllers must be on a ControlNet network. 1756-SG001G-EN-P — March 2004 49 Determining Memory Requirements The following equations provide an estimate of the memory needed for a controller. These numbers are rough estimates. Controller tasks _____ * 4000 = Digital I/O points Analog I/O points Communication modules✶ Motion axes _____ * 400 _____ * 2600 _____ * 2000 _____ * 8000 = = = = _____ bytes (minimum 1 task) _____ bytes _____ bytes _____ bytes _____ bytes ✶When estimating memory use by communication modules, count all the communication modules in the system, not just those in the local chassis. This includes device connection modules, adapter modules, and ports on PanelView terminals. Controller memory boards The 1756-L55 controllers do not operate stand-alone. Choose one of these memory boards to come already assembled with the controller. You can also order additional memory boards either for spare parts or to upgrade existing 1756-L55 controllers. The 1756-L6x controllers have a fixed RAM size and do not use a memory board. Use a CompactFlash card for nonvolatile storage. You must remove the controller from the chassis to access the CompactFlash card. Catalog Number: Supported Controller: Battery-Backed Static RAM: Nonvolatile RAM: 1756-M12✶ 1756-M13 1756-M14 1756-L55 1756-L55 1756-L55 none none none 1756-M16 1756-L55 1756-M22✶ 1756-M23† 1756-M24† 1756-L55 1756-L55 1756-L55 750 Kbytes 1.5 Mbytes 3.5 Mbytes 7.5 Mbytes 3.5 Mbytes for tag data 750 Kbytes 1.5 Mbytes 3.5 Mbytes 1784-CF64 1756-L6x‡ none none 750 Kbytes 1.5 Mbytes 3.5 Mbytes same as the battery-backed static RAM limit for the controller ✶The 1756-L55 controller must have firmware revision 10 or higher. †The 1756-L55 controller must have firmware revision 8 or higher. ‡You can use CompactFlash with the 1756-L61, -L62, -L63, and -L60M03SE controllers. The 1756-L61, -L62 controllers require firmware revision 12 or greater. The 1756-L63 controller requires firmware revision 11 or higher. The 1756-L60M03SE controller requires firmware revision 13 or higher. Non-volatile memory The nonvolatile memory (flash) lets you permanently store a user program and tag data on a controller. You can: y manually trigger the controller to save to or load from nonvolatile memory y configure the controller to load from nonvolatile memory on power up The 1756-L55M2x controllers have fixed internal nonvolatile memory. The 1756-L6x controllers support a removable CompactFlash card for nonvolatile memory. You install the 1784-CF64 card in a socket in the controller. You must remove the controller from the chassis to install CompactFlash. The CompactFlash card stores the user program, tag data, and controller firmware. This lets you upgrade firmware on a 1756-L6x controller without using RSLogix 5000 or ControlFlash software. 1756-SG001G-EN-P — March 2004 50 Determining Battery Requirements Each controller ships with a 1756-BA1 battery. An externally mounted, higher-capacity battery module is also available (1756-BATM). Cat. No. Description Estimated Worst Case Battery Life @ 25C 1756-BA1 Lithium battery (0.59g) installed in each ControlLogix controller. Order only if you need a replacement. y y y y y with 1756-L55M12: 63 days with 1756-L55M13: 63 days with 1756-L55M14: 30 days with 1756-L55M16: 13 days with 1756-L6x: 21 days y y y y y with 1756-L55M12: 299 days with 1756-L55M13: 299 days with 1756-L55M14: 213 days with 1756-L55M16: 133 days with 1756-L6x: 146 days Externally mounted battery assembly. Provides longer battery life than the 1756-BA1. 1756-BATM 1756-BATA Contains: y one 1756-BATA assembly y 1m cable to connect housing to controller Highly recommended for all controllers (see chart below). Lithium battery assembly (maximum of 5g lithium per each D cell; assembly contains 2 D cells) included with the 1756-BATM. Order only if you need a replacement. The 1756-BATM battery module is recommended for use with all 1756-L55 and 1756-L6x controllers. If You Order This Controller 1756-BATM 1756-BATM 1756-BA1 1756-L55M12 1756-L55M13 1756-L55M14 recommended recommended highly recommended for a replacement for a replacement for a replacement 1756-L55M16 highly recommended for a replacement 1756-L55M22✶ recommended for a replacement for a replacement for a replacement for a replacement not recommended for long-term use for a replacement 1756-L55M23✶ recommended for a replacement 1756-L55M24✶ highly recommended for a replacement 1756-L61† highly recommended for a replacement 1756-L62† highly recommended for a replacement 1756-L63† highly recommended for a replacement for a replacement not recommended for long-term use not recommended for long-term use not recommended for long-term use not recommended for long-term use ✶These controllers have nonvolatile memory and can be used without a battery. †The 1756-L6x controllers have nonvolatile memory if you install a 1784-CF64 CompactFlash card. With nonvolatile memory, the controller can be used without a battery. If you do not use a battery, current tag data will be at the state they were when the nonvolatile memory was saved. 1756-SG001G-EN-P — March 2004 51 Controlling Devices The ControlLogix controller can control these devices: I/O Modules EtherNet/IP ControlNet DeviceNet Universal Remote I/O 1756 ControlLogix I/O 1794 FLEX I/O 1793 FLEX Integra I/O 1797 FLEX Ex I/O 1734 POINT I/O 1734D POINT Block I/O 1769 Compact I/O 1790 Compact LDX I/O 1791 Block I/O 1791D CompactBlock I/O 1792 ArmorBlock I/O 1798 FlexArmor I/O 1799 Embedded I/O 1747 SLC I/O 1771 I/O yes yes yes✶ no yes no no no no no no no no yes yes yes✶ yes yes no no no no no no no no no yes† no yes yes no yes yes yes yes no yes yes yes yes no no no yes yes no no no no no yes no no no no yes yes no ✶Requires RSLogix 5000 programming software version 11 or greater. Use the generic FLEX profile. †Use a 1771-ACN15, -ACNR15 adapter module. Version 10 and later of RSLogix 5000 Enterprise Series software supports 1771 digital, analog, and specialty I/O modules. Previous versions of the software support only 1771 digital I/O modules. Display Devices 2711P PanelView Plus terminal 6182H VersaView CE computer 2711 PanelView terminal 2711 e PanelView terminal 2705 RediSTATION/Re diPANEL operator module 2706 InView message display 2706 DL40 Dataliner message display 2706 DL, DL50 DataLiner message display 2707 DTAM Plus operator interface EtherNet/IP ControlNet DeviceNet DH+ Universal Remote I/O RS-232 (DF1) DH-485 yes yes yes yes yes yes no✶ yes yes yes yes yes yes no✶ yes yes yes yes† yes yes† yes† no yes no yes† yes no no no no yes no yes no no yes yes yes yes yes yes yes no no no no yes yes no no no no no no yes no no no yes no yes yes† yes† ✶These devices support DH-485 communication to FlexLogix and CompactLogix controllers. †Use PLC/SLC mapping. 1756-SG001G-EN-P — March 2004 52 Communicating with Other Controllers and Communication Devices The ControlLogix system takes advantage of several networks to allow communications with many different controllers and devices. The following table lists which products the ControlLogix controller can communicate with over which networks. Controller EtherNet/IP ControlNet DeviceNet DH+ RS-232 (DF1) DH-485 1756 ControlLogix 1769 CompactLogix 1789 SoftLogix5800 1794 FlexLogix 5720 PowerFlex 700S with DriveLogix 1785 PLC-5 1747 SLC 1761 MicroLogix 1762 MicroLogix 1769 MicroLogix 1772 PLC-2 1775 PLC-3 5250 PLC-5/250 yes yes yes yes yes yes yes no yes no yes yes yes yes yes no yes no yes yes yes no yes yes yes yes yes no yes yes yes✶† yes§ yes yes yes na na na yes yes no no no na na na yes‡ yes♣ yes♣ yes♣ yes♣ na na no yes yes♣ no no no yes➤ yes yes yes yes yes yesa yes yes na no no no no na na na yes yes ✶The Ethernet PLC-5 processor must be one of these: series C, revision N.1 or later series D, revision E.1 or later series E, revision D.1 or later †The 1785-ENET Ethernet communication interface module must be series A, revision D or later. ‡The PLC-5, SLC, and MicroLogix processors appear as I/O points to the Logix controller. Requires 1761-NET-DNI DeviceNet interface. §Use a 1747-L55x controller with OS501 or greater. ♣Use a 1747-L54x controller. ➤The PLC-2 controller requires a 1785-KA module for DH+ communications. aThe PLC-2 controller requires a 1771-KG module for serial (DF1) communications. The PLC-3 controller requires a 1775-S5 module for DH+ communications. The PLC-3 controller requires a 1775-KA module for serial (DF1) communications. Communication Device EtherNet/IP 9355 RSLinx software 1784-KTC, -KTCx, KTCx15, -PCIC(S), -PCC 1784-PCIDS, -PCD 1784-KTX, -KTXD, -PCMK 1788-CN2DN 1788-EN2DN 1788-CN2FF 1203-CN1 ControlNet module 1203-FM1/FB1 SCANport ControlNet DeviceNet DH+ RS-232 (DF1) DH-485 yes yes no yes yes no na yes na na na na na na yes na na na na na na yes na na na yes na yes na yes yes yes na na na na na na na na na na na yes✶ na na na na na yes† na na na na ✶Use the generic module configuration to configure the 1203-CN1 module and a CIP generic MSG instruction to communicate with the module. †Use a CIP generic MSG instruction to communicate with the 1203-FM1 SCANport module on a DIN rail that is remote to the controller. The remote DIN rail also requires a 1794-ACN(R)15 ControlNet adapter module. 1756-SG001G-EN-P — March 2004 53 Communicating with Drives Motion (Servo) Drives✶ EtherNet/IP 1394 GMC drive and control 1398 ULTRA 100 series drive 2098 Ultra3000 DeviceNet servo drive 2098 Ultra5000 intelligent positioning The ControlLogix system takes advantage of several networks to allow communications with many different drives, both motion (servo) drives and standard drives. The following table lists which drives the ControlLogix controller can communicate with over which networks. ControlNet DeviceNet DH+ RS-232 DH-485 no no no yes yes yes no no yes no no no no no yes no no no no no yes no yes no ✶Each drive has different options you order for its supported communication networks. See the appropriate catalog or selection information for a drive to make sure you select the appropriate option when specifying a drive for a specific network. Standard Drives✶ 1305 adjustable frequency ac drive 1336 adjustable frequency ac drive 1395 digital dc drive FlexPak 3000 dc drive WebPak 3000 dc winder GV3000 ac drive PowerFlex 40 ac drive PowerFlex 70, 700, 700S, and 7000 ac drive EtherNet/IP ControlNet DeviceNet DH+ RS-232 DH-485 no yes yes yes yes yes no yes yes yes yes yes no yes no yes yes no no yes yes no yes no no yes no no yes no no yes yes no yes no no no yes no yes yes yes yes yes yes yes yes ✶Each drive has different options you order for its supported communication networks. See the appropriate catalog or selection information for a drive to make sure you select the appropriate option when specifying a drive for a specific network. 1756-SG001G-EN-P — March 2004 54 How a Logix System Uses Tasks If you want to execute a section of your logic: all of the time A Logix controller uses three types of tasks. Use the following table to choose the appropriate type of task for each section of your logic. Then use this type of task: Continuous Task y at a constant period (e.g., every 100 ms) y multiple times within the scan Periodic Task. of your other logic immediately when an event occurs Description: The continuous task runs in the background. Any CPU time not allocated to other operations (such as motion, communications, and periodic or event tasks) is used to execute the programs within the continuous task. y The continuous task runs all the time. When the continuous task completes a full scan, it restarts immediately. y A project does not require a continuous task. If used, there can be only one continuous task. A periodic task performs a function at a specific period. y Whenever the time for the periodic task expires, the task interrupts any lower priority tasks, executes one time, and then returns control to where the previous task left off. y You can configure the time period from 0.1 ms to 2000 msec. The default is 10 ms. It is also controller and configuration dependent. y The performance of a periodic task depends on the type of Logix controller and on the logic in the task. An event task performs a function only when a specific event (trigger) occurs. The trigger for the event task can be: y change of a digital input y new sample of analog data y certain motion operations y consumed tag y EVENT instruction Event Task Whenever the trigger for the event task occurs, the event task: y interrupts any lower priority tasks y executes one time y returns control to where the previous task left off Event tasks Several factors affect the closed-loop event throughput: y input module type, filter time, and response time y backplane size and loading y controller type, configuration, and loading y output module type and response time 1756-SG001G-EN-P — March 2004 55 To use a device to trigger an event task, the device must support event task triggering. If the device is in a remote location, the associated communication modules must also support event triggering. These devices support input events: Category Modules Digital I/O modules that support change of state Analog I/O modules that support real time sample Specialty I/O modules Communication modules that provide rack-optimized connections Generic I/O modules that conform to CIP event communications 1756-IA8D 1756-IA16I 1756-IB16 1756-IB16I 1756-IB32/A 1756-IC16 1756-IH16I 1756-IM16I 1756-IV16/A 1756-IF16 1756-IF6CIS 1756-IF8 1756-IT6I 1756-CFM/A 1756-PLS/B 1756-CNB/A 1756-CNB/D 1756-CNBR/B 1756-DNB 1756-SYNCH/A 1756-MODULE 1789-MODULE 1756-IA16 1756-IA32 1756-IB16D 1756-IB16ISOE 1756-IB32/B 1756-IG16 1756-IH16ISOE 1756-IN16 1756-IV32/A 1756-IF4FXOF2F/A 1756-IF6I 1756-IR6I 1756-IT6I2 1756-HSC 1756-CNB/B 1756-CNBR/A 1756-CNBR/D 1756-ENBT/A 1784-PCIDS/A When planning for event tasks, consider these recommendations: Recommendation Details Place the module that triggers an event in the same chassis as the Placing a module in a remote chassis adds additional network controller. communications and processing to the response time. Limit number of modules in the chassis with the event module and the Additional modules increases the potential for backplane delays. controller. All inputs on a module trigger a single event so using multiple bits increases the chances of a task overlap. Configure the module to Limit events on digital inputs to a single input bit on a module. explicitly detect change-of-state on the input and turn off the other bits. The priority of the event task should be set as the highest priority on Setting an event task at a lower priority than a periodic task will force the controller. the event task to wait for the periodic task to complete execution. Increasing the number of event tasks reduces the available CPU Limit the number of event tasks. bandwidth and increases the chance of a task overlap. The 1756-IB32/B and 1756-IF4FXOF2F are recommended for digital These modules have the best response times. and analog events. 1756-SG001G-EN-P — March 2004 56 Estimating event task throughput To estimate the throughput time from input to output (screw to screw), use the following worksheet: Value (in µs): Consideration: 1. What is the input filter time of the module that triggers the event task? This is typically shown in milliseconds, Convert it to microseconds (µs). 2. What is the hardware response time for the input module that triggers the event task? Make sure you use the appropriate type of transition (Off to On or On to Off). See the following table. 3. What is the backplane communication time? If the chassis size is: Use this value (worst case): 4 slot 13 µs 7 slot 22 µs 10 slot 32 µs 13 slot 42 µs 17 slot 54µs 4. What is the total execution time of the programs in the event task? 5. What is the backplane communication time (same value as step 3). 6. What is the hardware response time of the output module? 7. Add steps 1 through 6. This is the minimum estimated throughput, where execution of the motion planner or other tasks do not delay or interrupt the event task. 8. What is the scan time of the motion group? 9. What is the total scan time of the tasks that have a higher priority than this event task (if any)? 10. Add steps 7 through 9. This is the nominal estimated throughput, where execution of the motion planner or other tasks delay or interrupt the event task. Use the following table to determine the nominal hardware response time for selected 1756 I/O modules. Nominal reponse time µs: 1756-SG001G-EN-P — March 2004 Module: 25° C Off to On On to Off 60° C Off to On On to Off 1756-IB16 1756-IB16D 1756-IB32 1756-IV16 1756-IV32 1756-OB16D 1756-OB16E 1756-OB32 1756-OV16E 1756-OV32E 265 303 330 257 381 48 60 38 67 65 582 613 359 435 476 519 290 160 260 174 265 305 345 254 319 51 61 49 65 66 638 673 378 489 536 573 324 179 326 210 57 How a Logix System Uses Connections A Logix system uses a connection to establish a communication link between two devices. Connections can be: y controller to local I/O modules or local communication modules y controller to remote I/O or remote communication modules y controller to remote I/O (rack optimized) modules y produced and consumed tags y messages 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 communications between devices than unconnected messages. A Logix system supports: Method scheduled connection y level of determinism y unique to ControlNet unscheduled connection y deterministic y used by both ControlNet and EtherNet/IP unconnected message y least deterministic Description A scheduled connection is unique to ControlNet communications. 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 I/O module is a scheduled connection because you repeatedly receive data from the module at a specified interval. Other scheduled connections include connections to: y communication devices y produced/consumed tags On a ControlNet network, you must use RSNetWorx for ControlNet to enable all scheduled connections and establish a network update time (NUT). An unscheduled connection is a message transfer between controllers that is triggered by the requested packet interval (RPI) or the program (such as a MSG instruction). Unscheduled messaging lets you send and receive data when needed. All EtherNet/IP connections are unscheduled. An unconnected message is a message that does not require connection resources. An unconnected message is sent as a single request/response. The communication module you select determines the number of connections you have available for I/O and messages. This communication module: 1756-CNB 1756-ENBT Supports this number of connections: 64 (any combination of scheduled and unscheduled) 128 (any combination of scheduled and unscheduled) The EtherNet/IP module does not distinguish between scheduled and unscheduled connections. How you configure connections determines how many remote devices a communication card can support. 1756-SG001G-EN-P — March 2004 58 Determining Connections for Produced and Consumed Tags This type of tag: produced consumed 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 ControlNet, produced and consumed tags are scheduled connections. Requires these connections: A produced tag allows other controllers to consume the tag, which means that a controller can receive the tag data from another controller. The local controller (producing) uses one connection for the produced tag and one connection for each consumer. The controller’s 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, like communications and I/O. 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 controllers must be attached to the same control network (such as a ControlNet or Ethernet/IP network). You cannot bridge produced and consumed tags over two networks. The total number of tags that can be produced or consumed is limited by the number of available connections. If the controller uses all of its connections for I/O and communication devices, no connections are left for produced and consumed tags. Maximum number of produced and consumed tags The controller supports: As a: The controller supports: producer consumer (number of produced tags) ≤ 127 (number of consumed tags) ≤ 250 The total combined consumed and produced tags that a controller supports is (this is also the maximum number of connections): (number of produced tags) + (number of consumed tags) ≤ 250 1756-SG001G-EN-P — March 2004 59 Determining Connections for Messages 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 connection open (cache) or close the connection when the message is done transmitting. The following table shows which messages use a connection and whether or not you can cache the connection: This type of message: Using this communication method: Uses a connection: CIP data table read or write CIP CIP CIP with Source ID DH+ CIP na 9 PLC2, PLC3, PLC5, or SLC (all types) CIP generic block-transfer read or write 9 your option✶ 9 ✶You can connect CIP generic messages, but for most applications we recommend you leave CIP generic messages unconnected. Connected messages are unscheduled connections on both ControlNet and EtherNet/IP networks. Each message uses one connection, regardless of how many devices are in the message path. To conserve connections, you can configure one message to read from or write to multiple devices. If a message executes repeatedly, cache the connection. This keeps the connection open and optimizes execution time. Opening a connection each time the message executes increases execution time. If a message executes infrequently, do not cache the connection. This closes the connection upon completion of the message, which frees up that connection for other uses. A Logix system uses connections to transmit I/O data. These connections can be direct connections or rack-optimized connections. Determining Connections for I/O Modules Connection direct rack-optimized A Logix system uses connections to transmit I/O data. These connections can be direct connections or rack-optimized connections. Description A direct connection is a real-time, data transfer link between the controller and an I/O module. The controller maintains and monitors the connection between the controller and the I/O module. Any break in the connection, such as 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 and specialty modules require direct connections. For digital I/O modules, you can select rack optimized communication. A rack optimized connection consolidates connection usage between the controller and all the digital I/O 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). 1756-SG001G-EN-P — March 2004 60 Depending on the type of I/O modules, both direct connections and rack-optimized connections can be used. I/O System Supported Connection Type(s): 1756 basic digital I/O in a local chassis direct connection direct connection or rack-optimized connection✶ digital I/O in a remote chassis via ControlNet analog I/O either in a local chassis or in a remote chassis via ControlNet direct connection direct connection or rack-optimized connection✶ direct connection rack-optimized connection direct connection via messaging direct connection via messaging rack-optimized connection digital I/O in a remote chassis via EtherNet/IP analog I/O in a remote chassis via EtherNet/IP digital I/O via Universal Remote I/O analog I/O via Universal Remote I/O 1771 analog I/O via ControlNet DeviceNet I/O ✶Rack-optimized connections for diagnostic and E-fuse modules do not send diagnostic or fuse data to controller. Considerations: Connection configuration Direct connections to 1756 I/O modules Rack-optimized connections to 1756 I/O modules Combining direct and rack-optimized connections Connections to DeviceNet devices Connections to 1771 I/O modules 1756-SG001G-EN-P — March 2004 Details The controller can have a direct connection to every I/O module in a remote chassis on an EtherNet/IP or ControlNet network. Because all the remote I/O modules are configured for direct connections, configure the remote communication module for “none,” which results in no connection. Rather than one connection to each remote I/O module, use one connection to communicate with all the digital I/O in the remote chassis (each analog I/O module requires a direct connection). The data from all the digital I/O modules is sent simultaneously at a rate specified by the remote connection through the EtherNet/IP or ControlNet communication module. The rack-optimized connection conserves connections and bandwidth. However, because the connections are condensed into one rack connection, the optimized digital I/O can no longer send all of its status and diagnostic data. A remote ControlLogix chassis can have both a rack-optimized connection and direct connections. Use a rack-optimized connection to consolidate all the digital I/O modules. Use a direct connection for each analog I/O module. The controller uses two connections to communicate with the 1756-DNB module. The 1756DNB module does not establish connections to its devices; and therefore, the controller doesn’t establish connections with DeviceNet devices. The 1756-DNB module acts as a scanner that gathers all the data from its devices and packs that data together into one image that is passed to the controller. However, the controller can use a MSG instruction to get information directly to or from a DeviceNet device. The controller communicates with a 1771 chassis through a 1756-DHRIO module to the adapter module of the 1771 chassis. The controller uses one connection for each logical rack. The addressing mode (1/2 slot, 1 slot, or 2 slot) of the 1771 chassis determines the number of logical racks, which determines the total number of connections. In addition, the controller uses one connection for each message to a 1771 block-transfer module. 61 In this example system the 1756 ControlLogix controller: y controls local (in the same chassis) digital I/O modules Connections Example y controls remote I/O devices on DeviceNet y sends and receives messages to/from the 1769-L35E CompactLogix controllers on EtherNet/IP y produces one tag that the the 1794 FlexLogix controller consumes y is programmed via RSLogix 5000 programming software The 1756 ControlLogix controller in this example uses these connections: Connection Type controller to local I/O modules (rack-optimized) controller to 1756-ENBT module (rack-optimized) controller to 1756-DNB module controller to RSLogix 5000 programming software message to 1769-L35E CompactLogix controller produced tag consumed by 1794 FlexLogix controller total Module Quantity Connections per Module Total Connections 4 1✶ 1 1 0 0 1 2 2 1 1 1 1 1 1 1 1 1 6 ✶A rack-optimized connection uses 1 connection for all the associated modules. 1756-SG001G-EN-P — March 2004 62 Determining Total Connection Requirements The ControlLogix controller supports 250 connections. To calculate the total connections for a controller, consider the connections to local I/O modules and the connections to remote modules. Use the following table to tally local connections: Connection Type Device Quantity local I/O module (always a direct connection) 1756-M16SE, -M08SE, -M02AE servo module 1756-CNB, -CNBR communication module 1756-ENBT communication module 1756-DNET communication module 1756-DHRIO communication module Connections per Device Total Connections 1 3 0 0 2 1 Regardless of how you configure local I/O modules (rack-optimized or direct connect), the controller establishes a direct connection for each local I/O module. Remote connections depend on the communication module. The number of connections the module itself supports determines how many connections the controller can access through that module. Use the following table to tally remote connections for the controller: Connection Type remote 1756-CNB, -CNBR ControlNet communication module configured as a direct (none) connection configured as a rack-optimized connection remote I/O module over ControlNet (direct connection) remote 1756-ENBT Ethernet communication module configured as a direct (none) connection configured as a rack-optimized connection remote I/O module over EtherNet/IP (direct connection) remote device over DeviceNet (accounted for in rack-optimized connection for local 1756-DNB module) other remote communication adapter produced tag each consumer consumed tag cached message block-transfer message total 1756-SG001G-EN-P — March 2004 Device Quantity Connections per Device 0 or 1 1 0 or 1 1 0 1 1 1 1 1 1 Total Connections 63 Selecting Chassis Step 5 - Select: y a chassis with sufficient slots y 1756-N2 filler strips for empty slots The ControlLogix system is a modular system that requires a 1756 I/O chassis to contain the various modules. Chassis are available in sizes of 4, 7, 10, 13, and 17 module slots. You can place any module into any slot. The backplane provides a high-speed communication path between modules. Multiple controller modules on the backplane can pass messages between one another. With multiple communication interface modules on the backplane, a message can be sent from across a link into a port on one module, routed across the backplane and out another module’s port, and sent across another link to its ultimate destination. Cat. No. Slots Weight 1756-A4 4 0.75 kg (1.7 lb) 1756-A7 7 1.10 kg (2.4 lb) 1756-A10 10 1.45 kg (3.2 lb) 1756-A13 13 1.90 kg (4.2 lb) 1756-A17 17 2.20 kg (4.8 lb) Dimensions (HxWxD) 137 x 263 x 145 mm (5.4 x 10.4 x 5.8 in) 137 x 368 x 145 mm (5.4 x 14.5 x 5.8 in) 137 x 483 x 145 mm (5.4 x 19.0 x 5.8 in) 137 x 588 x 145 mm (5.4 x 23.2 x 5.8 in) 137 x 738 x 145 mm (5.4 x 29.1 x 5.8 in) Minimum Cabinet Size (HxWxD) 508 x 508 x 203 mm (20 x 20 x 8 in) 508 x 610 x 203 mm (20 x 24 x 8 in) 508 x 762 x 203 mm (20 x 30 x 8 in) 610 x 762 x 203 mm (24 x 30 x 8 in) 762 x 914 x 203 mm (30 x 36 x 8 in) Maximum Backplane Current Load 4.0A @ 3.3V dc 15.0A @ 5V dc 2.8A @ 24V dc Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM All the chassis are designed for back-panel mounting. Use the slot filler module 1756-N2 to fill empty slots. 1756-SG001G-EN-P — March 2004 64 When you mount a chassis in an enclosure, make sure to meet these minimum spacing requirements: Mounting dimensions right-side view of all chassis 1756-A4 with power supply 1756-SG001G-EN-P — March 2004 65 1756-A7 with power supply 1756-A10 with power supply 1756-SG001G-EN-P — March 2004 66 1756-A13 with power supply 1756-A17 with power supply 1756-SG001G-EN-P — March 2004 67 Selecting Power Supplies Step 6 - Select: y one power supply for each chassis y a power supply bundle if you are planning a redundant power supply system ControlLogix power supplies are used with the 1756 chassis to provide 1.2V, 3.3V, 5V, and 24V dc power directly to the chassis backplane. Non-redundant (1756-PA72, -PB72, -PA75, -PB75) and redundant (1756-PA75R, -PB75R) power supplies are available. Selecting a standard power supply You mount a standard power supply directly on the left end of the chassis, where it plugs directly into the backplane. The power supply you select can determine which chassis you can use. Specification Nominal Input Voltage Input Voltage Range Maximum Real Input Power Maximum Apparent Input Power Maximum Transformer Load Input Frequency Maximum Backplane Output Current Hold Up Time✶ Chassis Compatibility Location Power Supplies 1756-PA72 120V ac or 220V ac 85…265V ac 95 W 240 VA 238 VA 47…63 Hz 1.5A @ 1.2V dc 4A @ 3.3V dc 10A @ 5V dc 2.8A @ 24V dc 75W total 60 Hz 85V ac: 2 cycles 120V ac: 6 cycles 220V ac: 20 cycles series A series B left side of chassis 1756-PA75 1.5A @ 1.2V dc 4A @ 3.3V dc 13A @ 5V dc 2.8A @ 24V dc 75W total 1756-PB72 24V dc 19…32V dc 97 W na na dc 1.5A @ 1.2V dc 4A @ 3.3V dc 10A @ 5V dc 2.8A @ 24V dc 75W total 1756-PB75 1.5A @ 1.2V dc 4A @ 3.3V dc 13A @ 5V dc 2.8A @ 24V dc 75W total 20ms @ 19V dc 70ms @ 24V dc series B series A series B left side of chassis series B 1756-PC75 48V dc 30...60V dc 98 W na na dc 1.5A @ 1.2V dc 4A @ 3.3V dc 13A @ 5V dc 2.8A @ 24V dc 75W total 1756-PH75 125V dc 90...143V dc 95 W na na dc 1.5A @ 1.2V dc 4A @ 3.3V dc 13A @ 5V dc 2.8A @ 24V dc 75W total 50 ms @ 30...60V dc 50ms @ 90...143V dc series B series B left side of chassis left side of chassis Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM, C-Tick ✶The hold up time is the time between input voltage removal and dc power failure. †This can be a maximum of 0.91 cable-metered (3 cable feet) from the ControlLogix chassis. 1756-SG001G-EN-P — March 2004 68 Selecting a redundant power supply To build a redundant power supply system, you need: y two redundant power supplies (both 1756-PA75R or 1756-PB75R) y one 1756-PSCA2 chassis adapter module y two 1756-CPR2 cables to connect the power supplies to the 1756-PSCA2 chassis adapter module (3 ft length) y user-supplied annuniciator wiring to connect the power supplies to the input modules, as needed Specification Nominal Input Voltage Input Voltage Range Maximum Real Input Power Maximum Apparent Input Power Maximum Transformer Load Input Frequency Maximum Backplane Output Current Hold Up Time✶ Chassis Compatibility Location Power Supplies 1756-PA75R 120V/220V ac 85…265V ac 115 W 120 VA 120 VA 47…63 Hz 1.5A @ 1.2V dc 4A @ 3.3V dc 13A @ 5V dc 2.8A @ 24V dc 75W total 60 Hz 85V ac: 2 cycles 120V ac: 6 cycles 220V ac: 20 cycles series B panel mounted† 1756-PB75R 24V dc 19…32V dc 110 W na na dc 1.5A @ 1.2V dc 4A @ 3.3V dc 13A @ 5V dc 2.8A @ 24V dc 75W total Adapter 1756-PSCA2 na 20ms @ 19V dc 70ms @ 24V dc series B panel mounted† series B left side of chassis Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM, C-Tick ✶The hold up time is the time between input voltage removal and dc power failure. †This can be a maximum of 0.91 cable-metered (3 cable feet) from the ControlLogix chassis. The 1756-PSCA2 chassis adapter module is a passive device that funnels power from the redundant power supplies to the single power connector on the ControlLogix series B chassis backplane. The redundant power supplies are available in ac (1756-PA75R) and dc (1756-PB75R) versions. They are also available in bundled systems: Redundant Power Supply Bundle 1756-PAR2 1756-PBR2 1756-SG001G-EN-P — March 2004 Contents y y y y y y two 1756-PA75R power supplies two 1756-CPR2 cables one 1756-PSCA2 chassis adapter module two 1756-PB75R power supplies two 1756-CPR2 cables one 1756-PSCA2 chassis adapter module 69 Power Requirements and Transformer Sizing Each ac-input power supply generates a shutdown signal on the backplane whenever the ac line voltage drops below its lower voltage limit. It removes the shutdown signal when the line voltage comes back up to the lower voltage limit. This shutdown is necessary to help ensure that only valid data is stored in memory. The external transformer rating (in VA) of each power supply is greater than its real input power (in Watts) because a capacitor-input ac/dc supply draws power only from the peak of the ac voltage wave form. If the transformer is too small, it clips the peak of the sine wave; when the voltage is still above the lower voltage limit, the power supply will sense this clipped wave form as low voltage and could prematurely shut down modules in the chassis. The following graphs display the backplane power load on the vertical axis. Since these supplies have multiple outputs, the backplane power load is given in watts. y Use the real power value in watts for determining the amount of heat dissipation you will have inside the enclosure. y Use the apparent power value in VA for estimating power distribution sizing. y Use the transformer load value in VA of each power supply plus all other loads on a transformer to determine the required transformer size. 1756-SG001G-EN-P — March 2004 70 Power load and transformer sizing 1756-SG001G-EN-P — March 2004 71 Step 7 - Select: y the appropriate package of RSLogix 5000 Selecting Software Enterprise Series software and any options y other software packages for your application Your selection of modules and network configuration determines what software packages you need to configure and program your system. If you have a: You need: 1756 ControlLogix controller 1756 SERCOS or analog motion module RSLogix 5000 Enterprise Series software RSNetWorx for ControlNet 1756-CNB, -CNBR ControlNet communication (comes with the standard/NetWorx option of module RSLogix 5000 Enterprise Series software) RSNetWorx for DeviceNet 1756-DNB DeviceNet communication module (comes with the standard/NetWorx option of RSLogix 5000 Enterprise Series software) 1756-ENBT, -ENET EtherNet/IP communication module RSLinx software (set the IP address) (RSLinx Lite and Bootp server come with RSLogix 5000 Enterprise Series software) 1756-DHRIO communication module (define the DH+ routing table) Foundation Fieldbus Configuration Software and 1788-CN2FF FoundationFieldbus linking device RSLinx or RSLinx OEM software (RSLinx Lite is not sufficient) 1757-FFLD FoundationFieldbus linking device RSFieldbus configuration software RSLinx software communication card in a workstation (RSLinx Lite comes with RSLogix 5000 Enterprise Series software) Logix-based system you want to emulate RSLogix Emulate 5000 Logix-based system for which you want RSTrainer 2000 for ControlLogix Fundamentals training operator interface RSView Enterprise series software Order this catalog number: 9324 series (RSLogix 5000 Enterprise Series software) 9324-RLD300NXENE (RSLogix 5000 Enterprise Series software plus RSNetWorx option) or 9357-CNETL3 (RSNetWorx for ControlNet) 9324-RLD300NXENE (RSLogix 5000 Enterprise Series software plus RSNetWorx option) or 9357-DNETL3 (RSNetWorx for DeviceNet) 9324 series (RSLogix 5000 Enterprise Series software) 1788-FFCT and 9355-WABENE or 9355-WABOEMENE 9324-RSFBC 9324 series (RSLogix 5000 Enterprise Series software) 9310-WED200ENE 9393 series ViewAnyWare products 1756-SG001G-EN-P — March 2004 72 Programming Software RSLogix 5000 Enterprise Series software is designed to work with Rockwell Automation’s Logix platforms. RSLogix 5000 Enterprise Series software is an IEC 61131-3 compliant software package that offers relay ladder, structured text, function block diagram, and sequential function chart editors for you to develop application programs. RSLogix 5000 Enterprise Series software also includes axis configuration and programming support for motion control. RSLogix 5000 Enterprise Series software requirements Description personal computer software requirements RAM hard disk space video requirements 1756-SG001G-EN-P — March 2004 Value Pentium II 450 MHz minimum Pentium III 733 MHz (or better) recommended Supported operating systems: y Microsoft Windows XP Professional version 2002 (with Service Pack 1) or XP Home version 2002 y Microsoft Windows 2000 Professional with Service Pack 1, 2, or 3 y Microsoft Windows NT version 4.0 with Service Pack 5 or 6A 128 Mbytes of RAM minimum 256 Mbytes of RAM recommended 100 Mbytes of free hard disk space (or more based on application requirements) 256-color VGA graphics adapter 800 x 600 minimum resolution (True Color 1024 x 768 recommended) 73 Selecting the programming package fully supported Standard/ NetWorx Edition Mini Edition 9324- Lite Edition 9324- Standard Edition 9324RLD200xxE✶ RLD250xxE✶ 9324-RLD300xxE✶ RLD300NXxxE✶ CompactLogix5300 CompactLogix5300 all all FlexLogix5400 FlexLogix5400 fully supported fully supported fully supported fully supported upload/download upload/download upload/download only only only fully supported editor available editor available editor available separately separately separately upload/download editor upload/download only upload/download only fully supported editor available only editor available separately available separately separately upload/download upload/download upload/download only only only fully supported editor available editor available editor available separately separately separately upload/download upload/download fully supported fully supported only only na na fully supported fully supported fully supported fully supported available separately available separately available separately included included included included available separately available separately available separately available separately available separately available separately included available separately available separately available separately available separately available separately available separately included na included included included included na included included included included na included included included included na included included included included na included included included included na included included included included Lite included Lite included Lite included Lite included Lite included Lite included available separately included included included included Professional included➤ available separately available separately available separately available separately included➤ available separately included➤ included included included included available separately Service to Standard: 9324-RLD0U3xxE Service to Full: 9324-RLD0U6xxE Service to Professional: 9324-RLD0U7xxE included included included included available separately included included included included available separately included included included included available separately included included included included available separately included included included included available separately included included included included included Mini to Standard: 9324-RLD2U3xxE Mini to Full: 9324-RLD2U6xxE Mini to Professional: 9324-RLD2U7xxE Lite to Full: 9324-RLD25U6xxE Lite to Professional: 9324-RLD25U7xxE Standard to Professional: Multi-language pack 9324-RLD3U7xxE Full to Professional: extends Standard to Multi-language pack 9324-RLD6U7xxE Full♣ extends Standard to Full♣ Available Features Service Edition 9324RLD000xxE✶† Logix5000 controllers supported all Relay ladder editor§ view only Function block diagram editor 9324-RLDFBDENE§ view only Sequential function chart editor 9324-RLDSFCE§ view only Structured text editor 9324-RLDSTXE§ view only Highly-integrated motion view only Graphical trending DriveExecutive™ Lite 9303-4DTE01ENE PIDE autotune 9323-ATUNEENE RSLogix Emulate 5000 and RSTestStand Lite 9310-WED200ENE RSMACC audit support Logix CPU security tool Routine source protection tool RSMACC authenticate (security server) client Standalone security server explorer RSLinx RSNetWorx for ControlNet RSNetWorx for DeviceNet RSNetWorx for EtherNet/IPa FBD ActiveX faceplates Tag data upload/download tool RSLogix 5000 project compare tool Tag custom data monitor tool RSView demo (50 tags/2 hours) Upgrades Professional Full Edition 9324- Edition 9324RLD700NXxxE✶ RLD600xxE✶‡ all all fully supported fully supported fully supported fully supported fully supported fully supported fully supported fully supported fully supported fully supported na ✶Replace “xx” in the catalog number with the appropriate language designation: EN=English, FR=French, DE=German, IT=Italian, PT=Portuguese, and ES=Spanish. †Available as of RSLogix 5000 programming software version 12. ‡Available as of RSLogix 5000 programming software version 10.02. §A multiple language editor package is available as 9324-RLDMLPE. It contains the function block, sequential function chart, and structured text editors at a reduced price. ♣The multiple language editor package (9324-RLDMLPE) is not the same as an upgrade, but it extends the programming languages to match those in a Full package. ➤Bundled RSNetWorx and RSLinx Professional packages use the RSLogix 5000 activation and must be installed on the same PC. aRSNetWorx for ControlNet is available as 9357-CNETL3. RSNetWorx for DeviceNet is available as 9357-DNETL3. RSNetWorx for EtherNet/IP is available as 9357-ENETL3. They are available together as 9357-ANETL3. 1756-SG001G-EN-P — March 2004 74 RSLinx Software RSLinx software (9355 series) is a communication server package that provides plantfloor device connectivity for a wide variety of applications. RSLinx can support multiple software applications simultaneously communicating to a variety of devices on many different networks. RSLinx provides a user-friendly graphical interface for navigating through your network. Select a device and click to access a variety of integrated configuration and monitoring tools. A complete set of communication drivers is provided for your networking needs, including legacy Allen-Bradley networks. RSLinx is available in multiple packages to meet the demand for a variety of cost and functionality requirements. RSLinx system requirements Description personal computer operating system RAM hard disk space video requirements Value Pentium100 MHz processor (faster processors will improve performance) Supported operating systems: y Microsoft Windows XP y Microsoft Windows 2000 y Microsoft Windows NT version 4.0 with Service Pack 3 or greater y Microsoft Windows ME y Microsoft Windows 98 32 Mbytes of RAM minimum 64 Mbytes or more of RAM recommended 35 Mbytes of free hard disk space (or more based on application requirements) 16-color VGA graphics display 800 x 600 or greater resolution In most cases, RSLinx Lite software comes bundled with controller programming software packages. 1756-SG001G-EN-P — March 2004 75 Network Configuration Software RSNetWorx software is the configuration tool for your control network. With RSNetWorx software you can create a graphical representation of your network configuration and configure the parameters that define your network. Use RSNetWorx for: y ControlNet to schedule network components. The software automatically calculates network bandwidth for the entire network, as well as the bandwidth used by each network component. You must have RSNetWorx software to configure and schedule ControlNet networks. y DeviceNet to configure DeviceNet I/O devices and create a scan list. The DeviceNet scanner stores the configuration information and scan list. y EtherNet/IP to configure EtherNet/IP devices using IP addresses or host names. RSNetWorx system requirements ControlNet Description DeviceNet personal computer Intel Pentium or Pentium-compatible computer Supported operating systems: y Microsoft Windows XP y Microsoft Windows 2000 operating system y Microsoft Windows 2000 Terminal Server y Microsoft Windows NT version 4.0 with Service Pack 6 or greater y Microsoft Windows ME y Microsoft Windows 98 32 Mbytes of RAM minimum RAM more memory is required for large networks minimum: 115 Mbytes (includes program files and minimum: 190 Mbytes (includes program files and hardware files) hardware files) hard disk space full support: 168...193 Mbytes (includes program files, full support: 230...565 Mbytes (includes program files, online help, tutorial, and hardware files) online help, tutorial, and hardware files) 16-color VGA graphics adapter video requirements 640 x 480 resolution minimum 800 x 600 resolution recommended other RSLinx Lite 2.4 or later to use RSNetWorx online RSLinx Lite 2.4 or later to use RSNetWorx online EtherNet/IP minimum: 108 Mbytes (includes program files and hardware files) full support: 115...125 Mbytes (includes program files, online help, tutorial, and hardware files) RSLinx Lite 2.41 or later to use RSNetWorx online In most cases, RSNetWorx software comes bundled with controller programming software packages. 1756-SG001G-EN-P — March 2004 76 RSLogix Emulate 5000 Software RSLogix Emulate 5000 (9310-WED200ENE) is the software emulation package for the Logix5000 controllers. RSLogix Emulate 5000 used in conjunction with RSLogix 5000 software lets you run and debug your application code while at your computer. In addition, RSLogix Emulate 5000 also lets you test HMI screens, developed in RSView for example, without the need to connect to a real controller. You can set tracepoint and breakpoint instructions (ladder diagram only) in your application code, use traces, and also vary the execution speed of the emulator. RSLogix Emulate 5000 supports all the programming languages (ladder diagram, function block diagram, structured text, and sequential function chart). RSLogix Emulate 5000 does not allow for control of real I/O. RSLogix Emulate 5000 system requirements Description personal computer operating system RAM hard disk space video requirements Value IBM-compatible Intel Pentium II 300 MHz or Celeron 300A (Pentium III 600 MHz recommended) Supported operating systems: y Microsoft Windows XP with Service Pack 1or greater y Microsoft Windows 2000 with Service Pack 2 or greater y Microsoft Windows NT version 4.0 with Service Pack 6A or greater 128 Mbytes of RAM minimum 50 Mbytes of free hard disk space 16-color VGA graphics display 800 x 600 or greater resolution RSLogix Emulate 5000 includes RSTestStand Lite. RSTestStand Lite lets you create virtual operator consoles that can help test your application code. RSTestStand Lite can be upgraded to the standard version by ordering catalog number 9310-TSTNDENE. RSLogix Emulate 5000 and RSTestStand Lite are included with the RSLogix 5000 Professional edition. 1756-SG001G-EN-P — March 2004 77 Logix-Based Training Rockwell Automation offers several different levels of training for your Logix system. While most of these training aids are ControlLogix specific, the lessons and tools also apply to the other Logix platforms. y instructor-led courses y computer-based training y workstation simulator y job aids Instructor-led courses The instructor-led courses are best suited for people new to the Logix architecture and for those new to programmable controllers. Course Description CCP142 CCP143 CCP144 CCP146 CCP151 CCP152 CCP153 Programming Logix5000 motion applications using ladder logic Developing a Logix5000 project using RSLogix 5000 software Configuring advanced communications options on a Logix5000 system Fundamentals of Logix5000 systems Programming Logix5000 applications using basic ladder logic Programming Logix5000 applications using function block diagram Maintaining and troubleshooting Logix5000 sequential applications Computer-based training The computer-based training programs are designed to provide the essential introductory information needed for using the product. Computer-based training is best used as a resource following an instructor-led course. Cat. No. Description 9393-RSTCLX 9393-RSTPCLX 9393-RSTLX5K 9393-RSTPLX5K ControlLogix Fundamentals (90 day warranty) ControlLogix Fundamentals (1 year warranty) RSLogix 5000 Programming Software (90 day warranty) RSLogix 5000 Programming Software (1 year warranty) 1756-SG001G-EN-P — March 2004 78 ControlLogix workstation simulator The ControlLogix workstation simulator (ABT-TDCL1) is an engineering support tool that you can integrate into your training and development programs. The simulator helps you perform sequential, process, drive control, and motion control. This simulator is also used with most of the available instructor-led course. The simulator includes: y network hardware (ControlNet, DH+) y control hardware (controller, power supply, digital I/O modules, analog I/O modules) y programming cable (to connect to your computer) y motion control hardware (motion modules, servo drives, motors) y operator interface panel (pushbuttons, potentiometers, voltmeters) Job aids Job aids are useful resources to take back to your facility after completing instructorled and computer-based training. 1756-SG001G-EN-P — March 2004 Job Aid Description ABT1756TSG10 ABT1756DRG70 ABT1756TSJ50 ABT1756TSJ20 ControlLogix Glossary guide ControlLogix Reference guide ControlLogix Procedure guide ControlLogix Troubleshooting guide 79 ViewAnyWare ViewAnyWare products, together with Logix for control and NetLinx architecture for communication, make up Rockwell Automation’s Integrated Architecture strategy. The ViewAnyWare strategy combines Rockwell Automation’s expertise in Allen-Bradley electronic operator interface and industrialized PC hardware with Rockwell Software’s supervisory control software. Current ViewAnyWare products include: y RSView Enterprise Series™ software y PanelView Plus™ operator interface y VersaView™ industrial computers and monitors y VersaView CE industrial computer y MobileView™ portable HMI RSView Enterprise Series software RSView Enterprise Series from Rockwell Software is a line of HMI software products designed with a common look, feel, and navigation to help speed HMI application development and training time. With RSView Enterprise Series 3.0, you can reference existing Logix data tags. Any changes made to these referenced tags are automatically inherited by RSView. RSView Enterprise Series software includes: y RSView Studio™ lets you create applications in a single design environment. It configures Supervisory Edition, Machine Edition, VersaView CE, and PanelView Plus. It supports editing and reusing projects for improved portability between embedded machine and supervisory HMI systems. y RSView Machine Edition™ (ME) is a machine-level HMI product that supports both open and dedicated operator interface solutions. It provides a consistent operator interface across multiple platforms (including Microsoft Windows CE, Windows 2000/XP, and PanelView Plus solutions), and is ideal for monitoring and controlling individual machines or small processes. y RSView Supervisory Edition™ (SE) is an HMI software for supervisory-level monitoring and control applications. It has a distributed and scalable architecture that supports distributed-server/multi-user applications. This highly scalable architecture can be applied to a stand-alone, one-server/one-user application or to multiple users interfacing with multiple servers. RSView Enterprise Series Product Line RSView Studio RSView Machine Edition RSView Supervisory Edition Cat. No. 9701-VWSTENE 9701-VWSTMENE 9701-VWMR015AENE 9701-VWMR030AENE 9701-VWMR075AENE 9701-VWSCWAENE 9701-VWSCRAENE 9701-VWSS025AENE 9701-VWSS100AENE 9701-VWSS250AENE 9701-VWSS000AENE 9701-VWB025AENE 9701-VWB100AENE 9701-VWB250AENE 9701-VWSB000AENE Description RSView Studio for RSView Enterprise Series RSView Studio for Machine Edition RSView ME Station runtime for Windows 2000, 15 displays RSView ME Station runtime for Windows 2000, 30 displays RSView ME Station runtime for Windows 2000, 75 displays RSView SE client RSView SE view client RSView SE server 25 displays RSView SE server 100 displays RSView SE server 250 displays RSView SE server unlimited display RSView SE station 25 displays RSView SE station 100 displays RSView SE station 250 displays RSView SE station unlimited display 1756-SG001G-EN-P — March 2004 80 PanelView Plus operator interface PanelView Plus is ideal for applications with a need to monitor, control, and display information graphically, allowing operators to quickly understand the status of their application. PanelView Plus is programmed with RSView Studio and has embedded RSView Machine Edition functionality. It combines the best features from the popular Allen-Bradley PanelView Standard and PanelView “e” operator interface products and adds new functionality including: y multi-vendor communications y trending y expressions y data logging y animation y RSView Studio direct browsing of RSLogix 5000 addresses VersaView industrial computers and monitors VersaView is a family of industrial computer and monitor solutions, comprised of integrated display computers, workstations, non-display computers and flat panel monitors. VersaView products offer effortless management of changing technology, a rugged but cost-effective design, and easier product configuration. All VersaView products provide the latest industrial solution available, optimized for visualization, control, information processing, and maintenance application. RSView ME, RSView SE client, and RSView SE server runtimes are installed (separate activation is required). VersaView CE industrial computers VersaView CE is an open Windows CE terminal with a Windows desktop environment bringing together features of operator interfaces and industrial computers. It is a high performance computer with a compact flash drive and integrated RSView Machine Edition runtime (no activation required). There’s no hard disk, no fan, and no moving parts, which means maximum reliability on the plant floor. Easy to set up and maintain, VersaView CE means an open system that’s rugged and economical, offering high functionality in an easy to use package. MobileView portable HMI The MobileView family of portable HMI products lets personnel move around a machine or down a production line throughout the entire plant, resulting in greater worker and plant productivity. The MobileView interfaces let manufacturers have information and machine control wherever it is required. MobileView Machine and Guard terminals are available with RSView Machine Edition running locally, eliminating the need for a server. Or, MobileView terminals act as thin clients to computer applications, such as RSView Supervisory Edition, to easily integrate into new or existing control architectures. 1756-SG001G-EN-P — March 2004 81 Summary Use a spreadsheet to record the amount and type of devices your ControlLogix system needs. For example, this sample system: could result in this spreadsheet: Device Number of Points Needed Cat. No. I/O Points per Module Number of Modules 120V ac digital inputs 120V ac digital outputs 24V dc digital inputs 24V dc digital outputs contact digital outputs 4-20mA analog inputs 73 25 43 17 11 7 1756-IA8D 1756-OA8D 1756-IB16D 1756-OB16D 1756-OX8I 1756-IF6I 8 8 16 16 8 6 0-10V dc analog inputs 2 1756-IF6I 6 4-20mA analog outputs analog servo module PanelView terminal ControlNet communication module Remote I/O communication module total 4 2 axes na 1756-OF6CI 1756-M02AE 2711 series 6 na na 10 4 3 2 2 2 0 (can use remaining points on above modules) 1 1 na na 1756-CNB na 3 na 1756-DHRIO na 1 29 1756-SG001G-EN-P — March 2004 82 As you select devices for your ControlLogix system, keep in mind: 9 Step 1 2 3 Remember to Select y I/O modules - some modules have diagnostic features, electronic fusing, or individually isolated inputs/outputs y a remote terminal block (RTB) or wiring system for each I/O module y PanelConnect modules and cables if connecting input modules to sensors Select I/O devices Select motion control and drives requirements Select communication modules 4 Select controllers 5 Select chassis y y y y y y y y y y y y y y y y y 6 Select power supplies 7 Select software y y y the size of the motion application (use the Motion Book) how you want to interface the controller and drives type of motion interface, either SERCOS or analog associated cable(s) remote terminal block (RTB) - only needed for the analog interface modules drives, motors, and accessories (use the Motion Book) networks communication modules associated cable(s) and network equipment sufficient modules and cables if you are planning a redundant system a controller with sufficient memory memory board for each 1756-L55 controller 1756-BATM for larger memory size controllers replacement batteries a chassis with enough slots for the modules you need, with room to spare for additional growth 1756-N2 filler strips for empty slots a power supply with sufficient power for the modules you need, with room to spare for additional growth the power supply bundles if you are planning a redundant power supply system the appropriate package of RSLogix 5000 Enterprise Series software and any options other software packages for your application As you determine placement of the modules you selected, use the worksheet on the inside of the back cover to record your choices. Make a copy of this worksheet for each chassis. ControlLogix, Logix5550, FlexLogix, CompactLogix, DriveLogix, ProcessLogix, PowerFlex, SoftLogix5800, MicroLogix, PLC-5, PLC-3, PLC-2, SLC, DH+, Allen-Bradley, MobileView, RSLogix, RSLogix 5000 Enterprise Series, RSNetWorx, RSView Enterprise Series, RSView32, Rockwell Software, VersaView are trademarks of Rockwell Automation. ControlNet is a trademark of ControlNet International, Ltd. DeviceNet is a trademark of the Open DeviceNet Vendor Association. Ethernet is a trademark of Digital Equipment Corporation, Intel, and Xerox Corporation. Windows, Windows CE, Windows NT, Windows 2000, and Windows XP are registered trademarks of Microsoft in the U.S. and other countries. 1756-SG001G-EN-P — March 2004 83 Notes: 1756-SG001G-EN-P — March 2004 84 Notes: 1756-SG001G-EN-P — March 2004 1756-SG001G-EN-P — March 2004 Supercedes 1756-SG001F-EN-P — June 2003 PN 957859-73 Copyright © 2004 Rockwell Automation. All rights reserved. Printed in USA.
* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project
advertisement
© 2021