Controllogix: Selection Guide

ControlLogix
Selection Guide
Introducing ControlLogix for High Performance Control

A ControlLogix system provides a high performance control platform for multiple types of control. You can perform sequential, process, drive or motion control - in any combination - with this single platform. Because the platform is modular, you can design, build, and modify it efficiently - with significant training and engineering savings. Engineering Productivity is increased with advanced configuration tools, memory structure and symbolic programming that requires less programming and memory. And your investment in ControlLogix is assured through with such features as flash-upgradable firmware. The flexible ControlLogix platform permits multiple processors, networks, and I/O to be mixed without restrictions. As your application grows, you can use the NetLinx architecture for control and configuration of devices and collection of information across EtherNet/IP, ControlNet, and DeviceNet networks.
Take Control with Logix

Rockwell Automations Logix platforms offer users compatibility of control in a variety of platforms, including: ProcessLogix, a cost-effective distributed control system (DCS) for process applications SoftLogix5800, PC-based control from the PLC leader FlexLogix, FLEX I/O expanded to include distributed control CompactLogix, station-level control using Compact I/O DriveLogix, embedded Logix combined with PowerFlex for distributed drive control. Rockwell Automations Logix platforms offer users compatibility of control in a variety of formats within the NetLinx open network architecture for EtherNet/IP, ControlNet and DeviceNet.
The RSLogix 5000 Enterprise Series programming environment offers an easy-to-use IEC 1131-3 compliant interface, symbolic programming with structures and arrays for increased productivity, and an instruction set that serves sequential, motion, process and drives applications. The NetLinx open network architecture offers common communication tools for use with a variety of networks such as Ethernet, ControlNet, and DeviceNet. The ControlLogix control platform is: seamless enables easy integration with existing PLC-based systems. Users on existing networks can send or receive messages to/from program controllers on other networks transparently. fast As one of the next generation of Allen-Bradley control systems, ControlLogix integrates sequential, process, drive and motion control together with communications and state-of-the-art I/O in a small, cost-competitive platform. Because ControlLogix is modular, you can design, build, and modify it efficiently - with significant training and engineering savings. the ControlLogix platform provides high-speed data-transfers across the backplane and the ControlLogix5550 controller provides a high-speed control platform. provides a modular approach to control. Add as many or as few controllers and communication modules as you need. You can have multiple controllers in the same chassis. Select the controller memory size that meets your application. industrial offers a hardware platform designed to withstand the vibrations, thermal extremes, and electrical noise associated with harsh industrial settings. establishes a platform that integrates multiple technologies, including sequential, motion, drive, and process applications. meets the needs of many applications where control is highly distributed and panel space is limited.
scalable
integrated
compact
Flexible relay ladder and function block diagram editors let you create application programs with ease. In both the ladder editor and the function block diagram editor, youll find a standard, easy-to-use, intuitive programming interface. RSLogix 5000 Enterprise Series software provides built-in, highly-integrated motion support. A single hardware and software platform meets your combined motion and programmable controller needs.
Selecting a ControlLogix System

The ControlLogix system architecture provides sequential, process, and motion 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 ControlLogix system can be anything from a simple chassis to a highly-distributed system consisting of multiple chassis and networks working together. A simple ControlLogix system consists of a stand-alone controller and I/O modules in a single chassis.
ControlLogix controller
1756 I/O modules in the same chassis as the ControlLogix controller
Or you can 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.
1756-SG001D-EN-P November 2001
For a more robust system, use: multiple controllers in a single chassis multiple controllers joined across networks I/O in multiple platforms that is distributed in many locations and connected over multiple I/O links
EtherNet/IP link
communication interface modules in the same chassis as the ControlLogix controller
ControlNet link
DeviceNet link
remote I/O modules
1756 I/O modules in the same chassis as the ControlLogix controller
Universal Remote I/O link
RS-232 link
EtherNet/IP link ControlNet link DH+ link
computers other controllers
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 controllers 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. For example, assume that Location A and Location B both require a controller. Each controllers I/O is isolated on its own network. Both controllers must interact with time critical information. Panel C does not require a controller and can be a ControlLogix gateway.
RSView EtherNet/IP
Network C
Panel C
Network A
Network B
Panel A chassis 1
Panel A chassis 2
Panel A chassis 3
Panel B chassis 1
Panel B chassis 2
Universal Remote I/O PanelView
Universal Remote I/O PanelView
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: Panel A, chassis 1 Panel A, chassis 2 Panel A, chassis 3 Panel B, chassis 1 Panel B, chassis 2 Panel C, chassis 1 Controller in Panel A, chassis 1 yes yes yes yes no yes Controller in Panel B, chassis 1 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.
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:
Redundancy: media for ControlNet communications Example: Requirements: 1756-CNBR ControlNet communication module two identical ControlNet links
ControlNet node
ControlLogix chassis with 1756-CNBR module
redundant media
ControlNet node
power supplies
1756-PA75R or 1756-PB75R 1756-PA75R or 1756-PB75R
1756-CPR cable ControlLogix chassis with 1756-PSCA module
annunicator wiring 1756 input module
two redundant power supplies, any combination of 1756-PA75R and 1756-PB75R 1756-PSCA chassis adapter module, in place of the standard power supply two 1756-CPR cables to connect the power supplies to the 1756-PSCA chassis adapter user-supplied annunicator wiring to connect the power supplies to the input modules, if needed
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.
Step:
For more information, see page: I/O module specifications..............................page 9 Wiring systems .............................................page 16 Placing I/O modules ......................................page 24 How I/O modules operate..............................page 25
Determine the I/O devices Use a spreadsheet to record: location of the device number of points needed appropriate catalog number number of points available per module number of modules
Determine motion requirements To the I/O spreadsheet, add the number of required motion modules.
Motion overview ...........................................page 27 Motion specifications ....................................page 28
Select communication modules To the I/O spreadsheet, add the number of required communication modules.
Network overview .........................................page 37 EtherNet/IP specifications .............................page 42 ControlNet specifications ..............................page 46 DeviceNet specifications ...............................page 48 Fieldbus specifications..................................page 53 DH+/RIO specifications .................................page 50 Serial specifications ......................................page 55 DH-485 specifications...................................page 57 Other networks .............................................page 58 Controller specifications................................page 59 Connection information .................................page 63 Communicating with other I/O products ........page 71 Communicating with other devices ...............page 72
Determine controller requirements Select the appropriate controller based on: required controller tasks number of I/O points needed number of communication cards needed required controller memory
Determine the number of chassis Based on the system design, determine the number of chassis you need.
Chassis specifications...................................page 73
6 7
Select power supplies and ensure sufficient power On the module spreadsheet, calculate power requirements. Select software Based on the system design, determine the software products you need to configure and program your application.
Power supply specifications ..........................page 77
Available software products ..........................page 79 Programming software..................................page 80 Network configuration software ....................page 84
9 Step 1 - Select: I/O modules - some modules offer diagnostic features, electronic fusing, or individually isolated inputs or outputs either a remote terminal block (RTB) or 1492 wiring system for each I/O module
Selecting ControlLogix I/O Modules

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.
Producer/Consumer I/O Model
DC INPUT POWER
ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K BAT
AC INPUT
DC INPUT
Logix5550
RUN I/O RS232 OK
Logix5550
RUN I/O RS232 BAT OK
DC OUTPUT
ST 0 1 2 3 4 5 6 7 FLT 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K FLT 8 9 10 11 12 13 14 15
AC OUTPUT
ST 0 1 2 3 4 5 6 7 O FLT 0 1 2 3 4 5 6 7 K
RUN
REM
PROG
RUN
REM
PROG
DIAGNOSTIC
DIAGNOSTIC
Input Modules
Logix5500 Output Modules Controllers
Commonly Shared Data
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. The ControlLogix I/O modules offer a rich set of features, including: removal and insertion under power (RIUP) data transfer on change of state or at periodic intervals built-in module and field-wiring diagnostics time stamping electronic keying and module identification flash upgrades
When planning I/O communications, consider:

Considerations when planning I/O: which ControlLogix I/O modules to use where to place ControlLogix I/O modules how ControlLogix I/O modules operate selecting controller ownership See: page 10 page 24 page 25 page 26
The ControlLogix family of I/O modules includes:

Product: 1756 digital I/O modules 1756 analog I/O modules 1756 specialty I/O modules 1756 removable terminal blocks 1492 wiring systems See page: page 10 page 13 page 14 page 16 page 16
10
1756 Digital I/O Modules
The 1756 digital I/O modules support: wide variety of voltage interface capabilities isolated and non-isolated module types point-level output fault states choice of direct-connect or rack-optimized communications field-side diagnostics on select modules In addition, you can select these type of digital I/O modules:
Digital I/O Type: diagnostic electronic fusing Description: These modules provide diagnostic features to the point level. These modules have a D at the end of the catalog number. 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. These modules have individually isolated inputs or outputs. These modules have an I at the end of the catalog number.
individually isolated
Digital ac input modules

Catalog number: 1756-IA8D Number of inputs: 8 (2 sets of 4) 16 (2 sets of 8) 16 (individually isolated) 16 (individually isolated) 16 (2 sets of 8) Voltage category: 120V ac Operating voltage: 79-132V ac Maximum signal delay (programmable): on=11 or 12 ms off=17 or 26ms on=11 or 12 ms off=17 or 26ms on=11 or 12 ms off=17 or 26ms on=11 or 12 ms off=17 or 26ms on=10, 11, or 12ms off=19 or 28ms Removable terminal block: 1756-TBNH 1756-TBSH (20 pins) 1756-TBNH 1756-TBSH (20 pins) 1756-TBCH 1756-TBS6H (36 pins) 1756-TBCH 1756-TBS6H (36 pins) 1756-TBNH 1756-TBSH (20 pins) Maximum on state current: 79V ac 132V ac 74V ac 132V ac 79V ac 132V ac 159V ac 265V ac 10V ac 30V ac 5mA 16mA 5mA 13mA 5mA 15mA 5mA 13mA 5mA 1.2mA Maximum off state current: 2.5mA Backplane current: 100mA @ 5V 3mA @ 24V 0.58W 105mA @ 5V 2mA @ 24V 0.58W 125mA @ 5V 3mA @ 24 V 0.71W 100mA @ 5V 3mA @ 24V 0.58W 100mA @ 5V 2mA @ 24 V 0.56W
1756-IA16
120V ac
74-132V ac
2.5mA
1756-IA16I
120V ac
79-132V ac
2.5mA
1756-IM16I
240V ac
159-265V ac 10-30V ac
2.5mA
1756-IN16
24V ac
2.75mA
11
Digital ac output modules

Catalog number: 1756-OA8 Number of outputs: 8 (2 sets of 4) 8 (2 sets of 4) 8 (2 sets of 4) 16 (2 sets of 8) 16 (individually isolated) 8 (2 sets of 4) Voltage category: 120/240V ac Operating voltage: 74-265V ac Removable terminal block: 1756-TBNH 1756-TBSH (20 pins) 1756-TBNH 1756-TBSH (20 pins) 1756-TBNH 1756-TBSH (20 pins) 1756-TBNH 1756-TBSH (20 pins) 1756-TBCH 1756-TBS6H (36 pins) 1756-TBNH 1756-TBSH (20 pins) Maximum current per point: 2A @ 60C Maximum current per module: 5A @ 30C 4A @ 60C 8A @ 30C 4A @ 60C 8A @ 30C 4A @ 60C 4A @ 60C Backplane current: 200mA @ 5V 2mA @ 24V 1.07W 175mA @ 5V 250mA @ 24V 6.89W 200mA @ 5V 250mA @ 24V 7.02W 400mA @ 5V 2mA @ 24V 2.09W 300mA @ 5V 2.5mA @ 24V 1.6W 200mA @ 5V 2mA at 24V 1.07W
1756-OA8D
120V ac
74-132V ac
1.0A @ 30C 0.5A @ 60C 2A @ 60C (4A/set @ 30C 2A/set @ 60C) 0.5A @ 60C (2A/set @ 60C) 2A @ 30C 1A @ 60C 2A @ 60C
1756-OA8E
120V ac
74-132V ac
1756-OA16
120/240V ac
74-265V ac
1756-OA16I
120/240V ac
74-265V ac
5A @ 30C 4A @ 60C 5A @ 30C 4A @ 60C
1756-ON8
24V ac
10-30V ac
Digital dc input modules

Catalog number: 1756-IB16 Number of inputs: 16 (2 sets of 8) 16 (4 sets of 4) 16 (individually isolated) 32 (2 sets of 16) 16 (2 sets of 8) 16 (individually isolated) 16 (2 sets of 8) 32 (2 sets of 16) Voltage category: 12/24V dc sink 12/24V dc sink 12/24V dc source or sink 12/24V dc sink 48V dc sink Operating voltage: 10-31.2V dc Maximum signal delay (programmable): on=1, 2, or 3ms off=2, 3, 4, 11, or 20ms on=1, 2, or 3ms off=4, 5, 13, or 22ms on=1, 2, or 3ms off=4, 5, 6, 13, or 22ms on=1, 2, or 3ms off=2,3,4,11, or 20ms on=1, 2, or 3ms off=4, 5, 6, 13, or 22ms on=2, 3, or 4ms off=6, 7, 8,15, or 24ms on=1, 2, or 3ms off=2, 3, 4, 11, or 20ms on=1, 2, or 3ms off=2, 3, 4, 11, or 20ms Removable terminal block: 1756-TBNH 1756-TBSH (20 pins) 1756-TBCH 1756-TBS6H (36 pins) 1756-TBCH 1756-TBS6H (36 pins) 1756-TBCH 1756-TBS6H (36 pins) 1756-TBNH 1756-TBSH (20 pins) 1756-TBCH 1756-TBS6H (36 pins) 1756-TBNH 1756-TBSH (20 pins) 1756-TBCH 1756-TBS6H (36 pins) Maximum on state current: 10V dc 2mA 31.2V dc 10mA 10V dc 30V dc 10V dc 30V dc 2mA 13mA 2mA 10mA Maximum off state current: 1.5mA Backplane current: 100mA @ 5V 2mA @ 24V 0.56W 150mA @ 5V 3mA @ 24V 0.84W 100mA @ 5V 3mA @ 24V 0.45W 150mA @ 5V 2mA @ 24V 0.81W 100mA @ 5V 3mA @ 24V 0.58W 125mA @ 5V 3mA @ 24V 0.71W 110mA @ 5V 2mA @ 24V 0.61W 120mA @ 5V 2mA @ 24V 0.66W
1756-IB16D
10-30V dc
1.5mA
1756-IB16I
10-30V dc
1.5mA
1756-IB32
10-31.2V dc
10V dc 2mA 31.2V dc 5.5mA 30V dc 60V dc 90V dc 146V dc 10V dc 30V dc 10V dc 30V dc 2mA 7mA 1mA 3mA 2mA 10mA 2mA 3.5mA
1.5mA
1756-IC16
30-60V dc
1.5mA
1756-IH16I
125V dc source or sink 12/24V dc source 12/24V dc source
90-146V dc
0.8mA
1756-IV16
10-30V dc
1.5mA
1756-IV32
10-30V dc
1.5mA
12
Digital dc output modules

Catalog number: 1756-OB8 Number of outputs: 8 (2 sets of 4) 8 (individually isolated) 16 (2 sets of 8) 16 (2 sets of 8) 16 (individually isolated) Voltage category: 12/24V dc source 12/24V dc source or sink 24V dc source Operating voltage: 10-30V dc Removable terminal block: 1756-TBNH 1756-TBSH (20 pins) 1756-TBCH 1756-TBS6H (36 pins) 1756-TBCH 1756-TBS6H (36 pins) 1756-TBNH 1756-TBSH (20 pins) 1756-TBCH 1756-TBS6H (36 pins) Maximum current per point: 2A @ 60C Maximum current per module: 8A @ 60C Backplane current: 165mA @ 5V 2mA @ 24V 0.89W 250mA @ 5V 2mA @ 24V 1.32W 250mA @ 5V 140mA @ 24V 4.64W 250mA @ 5V 2mA @ 24V 1.32W 350mA @ 5V 2.5mA @ 24V 1.85W
1756-OB8EI
10-30V dc
2A @ 60C
16A @ 55C 10A @ 60C 8A @ 30C 4A @ 60C 8A @ 60C
1756-OB16D
19.2-30V dc
2A @ 30C 1A @ 60C 1A @ 60C
1756-OB16E
12/24V dc source 12/24V dc source or sink
10-31.2V dc
1756-OB16I
10-30V dc
resistive: 2A @ 30C 1A @ 60C inductive: 1A @ 60C 0.5A @ 50C 0.35A @ 60C 2A @ 60C
8A @ 30C 4A @ 60C
1756-OB32
32 (2 sets of 16) 8 (2 sets of 4) 8 (individually isolated) 16 (2 sets of 8)
12/24V dc source 48V dc source
10-31.2V dc
1756-TBCH 1756-TBS6H (36 pins) 1756-TBNH 1756-TBSH (20 pins) 1756-TBCH 1756-TBS6H (36 pins) 1756-TBNH 1756-TBSH (20 pins)
16A @ 50C 10A @ 60C 8A @ 60C
300mA @ 5V 2.5mA @ 24V 1.58W 165mA @ 5V 2mA @ 24V 0.89W 250mA @ 5V 2mA @ 24V 1.12W 210mA @ 5V 2mA @ 24V 1.12W
1756-OC8
30-60V dc
1756-OH8I
120V dc source or sink 12/24V dc sink
90-146V dc
2A @ 60C
8A @ 60C
1756-OV16E
10-30V dc
1A @ 60C
8A @ 60C
Digital contact output modules

Catalog number: 1756-OW16I Number of outputs: 16 (individually isolated) Type of contact outputs: 16 N.O. Removable terminal block: 1756-TBCH 1756-TBS6H (36 pins) 1756-TBCH 1756-TBS6H (36 pins) Operating voltage: 10-265V ac 5-150V dc Output current: 2A @ 125/240V ac 2A @ 5-30V dc 0.5A @ 48V dc 0.25A @ 125V dc 2A @ 125/240V ac 2A @ 5-30V dc 0.5A @ 48V dc 0.25A @ 125V dc Backplane current: 150mA @ 5V 150mA @ 24V 4.37W 100mA @ 5V 100mA @ 24V 2.91W
1756-OX8I
8 (individually isolated)
1 set of form-C contacts for each output
10-265V ac 5-150V dc
13
1756 Analog I/O Modules
The 1756 analog I/O modules support: on-board data alarming scaling to engineering units real-time channel sampling IEEE 32-bit floating point or 16-bit integer data formats
Current range: 0-20.5mA Removable terminal block: 1756-TBCH 1756-TBS6H (36 pins) 1756-TBNH 1756-TBSH (20 pins) 1756-TBCH 1756-TBS6H (36 pins) 1756-TBCH 1756-TBS6H (36 pins) Backplane current: 150mA @ 5V 40mA @ 24V 2.33W 250mA @ 5V 100mA @ 24V 3.7W 150mA @ 5V 65mA @ 24V 2.33W 350mA @ 5V 110mA @ 24V 4.43W
Catalog number: 1756-IF8
Number of inputs: 8 single-ended, 4 differential, or 2 high-speed differential 6 isolated
Number of outputs: Voltage range: none user configurable 10.25V 0-5.125V 0-10.25V user configurable 10.5V 0-5.25V 0-10.5V user configurable 10.25V 0-5.125V 0-10.25V Inputs (user configurable) 10.5V 0-10.5V 0-5.25V Outputs 10.5V
1756-IF6I
none
0-21mA
1756-IF16
16 single-ended, 8 differential, or 4 high-speed differential 4 high-speed differential (<1ms update)
none
0-20.5mA
1756-IF4FxOF2F
2 high-speed voltage or current (<1ms update)
Inputs: 0-21mA Outputs: 0-21mA
1756-IR6I
6 isolated RTD
none
RTD sensors supported: 100, 200, 500, 1000 Platinum, alpha=385 100, 200, 500, 1000 Platinum, alpha=3916 120 Nickel, alpha=672 100, 120, 200, 500 Nickel, alpha=618 10 Copper -12mV to 78mV -12mV to 30mV Thermocouples supported: Type B: 250 to 1820C (482 to 3308F) Type C: 0 to 2315C (23 to 4199F) Type E: -270 to 1000C (-454 to 1832F) Type J: -210 to 1200C (-346 to 2192F) Type K: -270 to 1372C (-454 to 2502F) Type N: -270 to 1300C (-454 to 2372F) Type R: -50 to 1768C (-58 to 3214F) Type S: -50 to 1768C (-58 to 3214F) Type T: -270 to 400C (-454 to 752F) 10.4V 0-21mA
1756-TBNH 1756-TBSH (20 pins)
250mA @ 5V 125mA @ 24V 4.25W
1756-IT6I
6 isolated thermocouple 1 cold junction temperature
none
1756-TBNH 1756-TBSH (20 pins)
250mA @ 5V 125mA @ 24V 4.3W
1756-OF4
none
4 voltage or current
1756-TBNH 1756-TBSH (20 pins) 1756-TBNH 1756-TBSH (20 pins)
150mA @ 5V 120mA @ 24V 3.65W 250mA @ 5V 225mA @ 24V 6.7W (0-550loads) or 250mA @ 5V 300mA @ 24V 8.5W (>550loads) 250mA @ 5V 175mA @ 24V 5.5W 150mA @ 5V 210mA @ 24V 5.8W
1756-OF6CI
none
6 isolated
na
0-21mA
1756-OF6VI
none
6 isolated
10.5
na
1756-TBNH 1756-TBSH (20 pins) 1756-TBNH 1756-TBSH (20 pins)
1756-OF8
none
8 voltage or current
10.4
0-21mA
14
1756 Specialty I/O Modules
1756-CFM configurable flow meter

The 1756-CFM module provides totalizer mode for metering applications, or high-speed 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. These high-current outputs can be triggered on: flow or frequency acceleration full flow state trickle flow state prover run state prover range state
The module interfaces devices such as: magnetic pickup flow meters 4-40V dc pulses (TTL compatible) proximity probes
Mode of Operation: Totalizer fill prover Input/Output data: 2 input channels 50mV, mag pickup 1.3V, TTL 4V, Preamp 2 outputs 20mA @ 4.5-5.5V dc 1A @ 10-31.2V dc Removable terminal block: 1756-TBNH or 1756-TBSH (20 pins) Backplane current: 300mA @ 5V 6mA @ 24V 1.7W
High-Resolution 100KHz max Frequency 0.0005 Hz resolution
15
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: photoswitch series 10,000 photoelectric sensors bulletin 872 3-wire DC proximity sensors 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 operation: counter rate measurement encoder debounce filter 1 MHz maximum 500KHz maximum 250KHz maximum 70Hz maximum Input data: 2 counters, each with A, B, and Z inputs 5V dc and 12-24V dc 16,777,216 maximum counts Output data: 4 outputs (2 outputs/common) 2 on/off preset values per output 20mA @4.5-5.5V dc 1A @10-31.2V dc Removable terminal block: 1756-TBCH or 1756-TBS6H (36 pins) Backplane current: 300mA @ 5V 3mA @ 24V 1.6W
1756-PLS programmable limit switch

The 1756-PLS module supports enhanced packaging applications where you require: deterministic module operation for operations up to 1500 parts per minute (PPM) detection of 1.08 degrees of rotation at 1800 RPM fast switching of ON-OFF windows multi-turn capabilities using resolvers 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.
Module configuration: requires 3 contiguous slots in chassis Input/Output data: left section: 2 groups of 4 outputs and 4 inputs each center section: resolver interface and I/O control right section: 2 groups of 4 outputs and 4 inputs each Removable terminal block: requires 3 RTBs 1756-TBNH or 1756-TBSH (20 pins) Backplane current: 1A @ 5V 1A @ 125V 130W
16
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.
Catalog number: 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 Weight: 0.1 kg (0.3lb) 0.1 kg (0.2lb) 0.1 kg (0.3lb) 0.1 kg (0.2lb) 0.05 kg (0.1 lb)
1492 Wiring Systems
As an alternative to buying RTBs and connecting the wires yourself, you can buy a wiring system of: 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. 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.
17
IFMs for 20-pin 1756 digital I/O modules

Catalog number: Type of IFM: Description: OB16E OA16E OA8D OA8E OA16 IA8D IN16 IA16 IB16 IC16 ON8 U U U W W W OB8 OC8 U U U W W W OA8 U U U
1492-IFM20F 1492-IFM20FN 1492-IFM20F-2 1492-IFM20F-3 1492-IFM20D24 1492-IFM20D24N 1492-IFM20D120 1492-IFM20D120N 1492-IFM20D24-2 1492-IFM20D24A-2 1492-IFM20D120-2 1492-IFM20D120A-2 1492-IFM20D24-3 1492-IFM20DS24-4 1492-IFM20DS120-4 1492-IFM20D240-2 1492-IFM20D240A-2 1492-IFM20F-F-2 1492-IFM20F-F24-2 1492-IFM20F-F120-2 1492-IFM20F-F240-2 1492-IFM20F-F24A-2 1492-IFM20F-F120A-2 1492-IFM20F-FS-2 1492-IFM20F-FS24-2
feed through feed through feed through feed through LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating fusible fusible fusible fusible fusible fusible fusible fusible
standard narrow standard extra terminals 3-wire sensor type input devices standard with 24V ac/dc LEDs narrow standard with 24V ac/dc LEDs standard with 120V ac LEDs narrow standard with 120V ac LEDs 24V ac/dc LEDS and extra terminals for outputs 24V ac/dc LEDS and extra terminals for inputs 120V ac LEDs and extra terminals for outputs 120V ac LEDs and extra terminals for inputs 3-wire sensor with 24V ac/dc LEDs isolated with 24/48V ac/dc LEDs and 4 terminals for outputs isolated with 120V ac LEDs and 4 terminals for outputs 240V ac LEDs and extra terminals for outputs 240V ac LEDs and extra terminals for inputs 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 extra terminals with 240V ac blown fuse indicators for outputs extra terminals with 24V ac/dc blown fuse indicators for inputs extra terminals with 120V ac/dc blown fuse indicators for inputs isolated with extra terminals for outputs isolated with extra terminals and 24V ac/dc blown fuse indicators for outputs isolated with 4 terminals and 24V ac/dc blown fuse indicators for inputs
U U U
X X X X
X X X X X X
X X X X
X X X X X X
U U U
U U U
X X X
U U U
X X X
X X
U U
X X X X X X X
X X X W W V V
X X
X X X X W V V W W X
1492-IFM20F-FS24A-4
fusible
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.
18
Catalog number: Type of IFM: Description: OB16E OA16E OA8D OA8E OA16 IA8D IN16 IA16 IB16 IC16 ON8 OB8 OA8 OC8
1492-IFM20F-FS120-2
fusible
isolated with extra terminals with 120V ac blown fuse indicators for outputs isolated with 4 terminals with 120V ac blown fuse indicators for outputs isolated with 4 terminals with 120V ac blown fuse indicators for inputs isolated with 4 terminals with 240V ac blown fuse indicators for outputs 20-pin master with eight 24V dc relays 20-pin master with eight 24V ac relays expander with eight 24V dc relays1 expander with eight 120V ac relays1 expander with eight 24V dc channels with blown fuse indicators1 expander with eight 120V ac channels with blown fuse indicators1 expander with eight feed-through channels1 U
1492-IFM20F-FS120-4 1492-IFM20F-FS120A-4 1492-IFM20F-FS240-4 1492-XIM2024-8R 1492-XIM20120-8R 1492-XIM24-8R 1492-XIM120-8R 1492-XIMF-F24-2 1492-XIMF-F120-2 1492-XIMF-2
fusible fusible fusible relay master relay master relay expander relay expander fusible expander fusible expander feed-through expander
W X X X X 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. 1. 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.
19
IFMs for 36-pin 1756 digital I/O modules

Catalog number: Type of IFM: Description: OB16D OB16E OW16I Y Y Y Y Y Y Y Y Y IB16D OB8EI OB16I OA16I IM16I OB32 IA16I IB16I IH16I OH8I OX8I Y Y Y Y Y Y Y Y Y IB32 Z Z Z Z Z Z Z
1492-IFM40F 1492-IFM40F-2 1492-IFM40F-3 1492-IFM40D24 1492-IFM40D24-2 1492-IFM40D24A-2 1492-IFM40D120-2 1492-IFM40D120A-2 1492-IFM40D24-3 1492-IFM40DS24-4 1492-IFM40DS24A-4 1492-IFM40DS120-4 1492-IFM40DS120A-4 1492-IFM40DS240A-4 1492-IFM40F-F-2 1492-IFM40F-F24-2 1492-IFM40F-F120-2 1492-IFM40F-FS-2 1492-IFM40F-FS24-2
feed through feed through feed through LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating fusible fusible fusible fusible fusible
standard extra terminals 3-wire sensor type input devices standard with 24V ac/dc LEDs 24V ac/dc LEDs and extra terminals for outputs 24V ac/dc LEDs and extra terminals for inputs 120V ac LEDs and extra terminals for outputs 120V ac LEDs and extra terminals for inputs 3-wire sensor with 24V ac/dc LEDs for inputs isolated with 24/48V ac/dc LEDs and 4 terminals per output isolated with 24/48V ac/dc LEDs and 4 terminals per input isolated with 120V ac LEDs and 4 terminals per output isolated with 120V ac LEDs and 4 terminals per input isolated with 240V ac LEDs and 4 terminals per output 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 and 120V ac blown fuse indicators for outputs isolated with 120V ac blown fuse indicators and 4 terminals per output isolated with 240V ac blown fuse indicators and 4 terminals per output
Y Y
Y Y
Z Z
Z Y Y Y Y Y Y Z Z Y Y
Y Y
Y Y
Y Y
1492-IFM40F-FS24-4
fusible
1492-IFM40F-FS120-2
fusible
1492-IFM40F-FS120-4
fusible
1492-IFM40F-FS240-4
fusible
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.
20
Catalog number: Type of IFM: Description: OB16D OB16E OW16I IB16D OB8EI OB16I OA16I IM16I OB32 IA16I IB16I IH16I OH8I OX8I IB32
1492-IFM40F-FS24A-4
fusible
isolated with 24V ac/dc blown fuse indicators and 4 terminals per input isolated with 120V ac blown fuse indicators and 4 terminals per input 40-pin master with eight 24V dc relays 40-pin master with sixteen 24V dc relays expander with eight 24V dc relays1 expander with eight 120V ac relays1 expander with eight 24V dc channels with blown fuse indicators1 expander with eight 120V ac channels with blown fuse indicators1 expander with eight feed-through channels1 Y
1492-IFM40F-FS120A-4
fusible
1492-XIM4024-8R 1492-XIM40120-16R 1492-XIM24-8R 1492-XIM120-8R 1492-XIMF-F24-2
relay master relay master relay expander relay expander fusible expander fusible expander feed-through expander
Z Z X
1492-XIMF-F120-2
1492-XIMF-2
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. 1. 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.
21
Pre-wired cables for digital I/O modules

Catalog number:1 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
1. 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

Catalog number:1 1492-CABLExTBNH 1492-CABLExTBCH Number of conductors: 20 40
2
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
1. 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. 2. Four conductors are not connected to the RTB.
For example, a 1756-OB32 that requires LEDs and extra terminals uses: 1492-IFM40D24-2 interface module 1492-ACABLExZ cable (replace x with the appropriate length)
22
AIFMs for 1756 analog I/O modules

IF16 (differential voltage) IF16 (differential current) Catalog number: IF16 (single-end voltage) IF16 (single-end current) IF8 (differential voltage) IF8 (differential current) IF8 (single-end voltage) IF8 (single-end current) Type of IFM: Description:
OF4 (voltage)
OF8 (voltage) WA
OF4 (current)
1492-AIFM4-3 1492-AIFM6S-3
feed through feed through feed through thermo couple fusible fusible fusible
4 channel with 3 terminals/channel 6 channel isolated with 3-4 terminals/channel 8 channel with 3 terminals/channel 6 channel with 3 terminals/channel 8 channel with 5 terminals/channel 16 channel with 3 terminals/channel 16 channel with 5 terminals/channel TA TB TC TC UA UA UB UB UC UC UD UD X Y Z
VA
VB Y Y
1492-AIFM8-3 1492-AIFM6TC-3 1492-AIFM8-F-5 1492-AIFM16-F-3 1492-AIFM16-F-5
TA
TB
TC
TD
UA
UB
UC
UD Y
Find the column for the analog I/O module. Follow the column down to see what analog 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 analog pre-wired cable. The letter code must match the last character of the catalog number for the cable.
AIFMs for 1757 modules

Catalog number: 1492-AIFMPI-3 Type of IFM: 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.
OF8 (current) WB
IF6I (voltage)
IF6I (current)
OF6CI
OF6VI
IR6I
IT6I
23
Pre-wired cables for analog I/O modules

Catalog number:1 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:2 11 twisted pairs 9 twisted pairs3 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
9 twisted pairs4 20 conductors5 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
1. 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. 2. 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. 3. One pair is not connected to the I/O module connector; two additional pairs are not used. 4. Two pairs are not used. 5. 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: 1492-AIFM6S-3 interface module 1492-ACABLExY cable (replace x with the appropriate length)
24
Placing ControlLogix I/O Modules
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
If the I/O module is:

digital
The data exchange method is based on:

change of state and / or requested packet interval (cyclic)
remote chassis analog local chassis
requested packet interval real time sample and / or requested packet interval
remote chassis
requested packet interval
For a ControlLogix controller to control 1756 I/O, the I/O must be: in the same chassis as the controller or on a ControlNet network that is local to that controller or on an Ethernet/IP network that is local to that controller For example:
Chassis A
Chassis B
Chassis C
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.
25
How ControlLogix I/O Modules Operate
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. The type of module and where you place the module determines how the module operates:
Module Type: digital input
Placement: local chassis
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.
remote chassis
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.
digital output
local chassis
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.
remote chassis
26
Module Type: analog input
Placement: local chassis
Operation: 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.
remote chassis
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.
analog output
local chassis
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.
remote chassis
Selecting Controller Ownership Every I/O module in the ControlLogix system must be owned by a
ControlLogix controller. The owner controller stores configuration data for every I/O module that it owns and can be local or remote in regard to the I/O modules position. The owner controller sends the I/O configuration data to define the I/O modules behavior and to start the I/O modules operation within the control system. Each ControlLogix I/O module must continuously maintain communication with its owner controller to operate normally. Typically, each I/O module has only one owner. Because listen-only controllers lose their connections to modules when communications with the owner controller stop, you can define more than one owner for an input module. If multiple controllers own the same input module, each controller must maintain identical configuration for that input module. An output module is limited to one owner.
Planning Motion Step 2 - Select: motion modules associated cable(s) a remote terminal block (RTB) for each 1756-M02AE servo module
27
Planning Motion
The Logix approach to motion control employs synchronized, distributed processing to provide a motion solution offering heightened performance and integration. The ControlLogix controller executes ladder-based motion commands and a motion trajectory planner while the servo module executes a fine planner and closes a position and velocity loop. This modular approach provides: Modular processing, including the ability to add ControlLogix controllers for additional processing power Control of multiple axes from a single ControlLogix controller application program
1.
Place module(s) in the chassis and wire to field devices.
4.
Download the application to the controller and run.
2 AXIS SERVO
Logix5550
RUN I/O RS232
ControlNET POWER
ETHERNET
DH+/RIO
DC OUTPUT
ST 0 1 2 3 4 5 6 7
AC OUTPUT
BAT
OK
ST 0 1 2 3 4 5 6 7 O
A#24
OK B A RXD TXD OK
B#15
CH A CH B OK
FLT 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K FLT 8 9 10 11 12 13 14 15
RUN
REM
PROG
FLT 0 1 2 3 4 5 6 7 K
DIAGNOSTIC
DIAGNOSTIC
2.
Use RSLogix5000 software to name and configure each motion axis.
3.
Use RSLogix5000 software to develop a motion application.
Each controller and chassis can control as many as 32 axes. RSLogix 5000 Enterprise Series software provides complete axis configuration and motion programming support.
RSLogix5000 Software Integrated Motion Programming ControlLogix Controller Program Execution 1756-M02AE Servo Module Drive Position Velocity Motor Feedback Drive Position Velocity Motor Feedback Axis Configuration
Motion Trajectory Planner Position Velocity
28
Planning Motion
1756-M08SE SERCOS Interface Module
The 1756-M08SE SERCOS interface module is an 8-axis module that serves as a link between the ControlLogix platform and 1394 SERCOS drive systems with 1 to 8 axes operating in either position or velocity mode. The communication link between the module and the drive(s) uses the IEC 61491 SErial Real-time COmmunication System (SERCOS) protocol over a fiber optic medium. The SERCOS interface is the only internationally approved, digital open standard with the performance required to synchronize multi-axis motion control. It is designed to focus on the efficient transfer of data specifically for servo control. The SERCOS interface uses a ring topology with one master and multiple slaves (axes). The fiber optical ring starts and ends with the master (1786-M08SE module).
ControlLogix controller with 1756-M08SE module
1394 SERCOS drives
Supported SERCOS drives

Catalog Number: 1394C-SJT05-D 1394C-SJT10-D 1394C-SJT22-D Description: 5kW Multi-Axis Servo Drive System 10kW Multi-Axis Servo Drive System 22kW Multi-Axis Servo Drive System
Planning Motion
29
1756-M08SE module specifications

Description: maximum number of axes per ControlLogix controller maximum number of axes per module power dissipation backplane current Value: 32 axes 8 axes 3.2W maximum 600 mA @ 5V dc 2.5 mA @ 24V dc x.xxW 1- 200 meters 200 m 4 m 230 m + 0/ 10 m 6.0 dB/ km @ 820nm 2.5 cm -20 to 85 C F- SMA standard screw- type connector 1- 200 meters 200 m 4 m 230 m + 0/ 10 m 6.0 dB/ km @ 820nm 2.5 cm -20 to 85 C F- SMA standard screw- type connector Class B (position or velocity) 4 Mbits per second 1 ms for 1- 4 axes 2 ms for 5- 8 axes 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 95% noncondensing 5g @ 10- 50Hz per IEC 68- 2- 6
UL508 - Industrial Control Equipment UL1604 - Class I, Division 2, Group A, B, C, D Hazardous Location Marked for all applicable directives IEC 1491 -Class B
plastic fiber optic cable transmission range core diameter cladding diameter cable attenuation minimum bend radius operating temperature connector glass fiber optic cable transmission range core diameter cladding diameter cable attenuation minimum bend radius operating temperature connector SERCOS interface class data rate operating cycle operating temperature storage temperature relative humidity vibration agency certification
UL
R
US
30
Planning Motion
Cables for Use with the 1756-M08SE Module
The fiber optic transmitter for the module uses 650nm wavelength.This wavelength produces a visible light from the port. You can use either plastic optical fiber (POF) and Hard Clad Silica (HCS ) cables. Both the transmitter and receiver connections use a F-SMA standard plug that conforms to the F-SMA screw type connector.
bottom of the 1756-M08SE module receiver
transmitter
Select one of these fiber optic cables to connect the SERCOS interface module to 1394 drives:
Catalog Number: 2090-SCEPx-01 (no jacket) 2090-SCVPx-0 (standard jacket) 2090-SCNPx-0 (nylon jacket) 2090-SCVGx-02 Description: Plastic Fiber Optic Cables You can use a 1000 m plastic simplex fiber optical cable. Plastic fiber optic cables have a transmission range of 1-32 meters. Allen-Bradley offers plastic, fiber-optic cable assemblies that come in a variety of jackets. The cable is available with: 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 You can use a 200 m glass fiber optical cable. Glass fiber optic cables have a transmission range of 1-200 meters to 200 meters. Allen-Bradley offers glass, fiber-optic cable assemblies that come with a standard jacket (Polyvinyl Chloride) for use in normal environments.
1. The x determines the length in meters. Select 1, 3, 5, 8, 10, 15, 20, 25, or 32 meters. 2. The x determines the length in meters. Select 1, 3, 5, 8, 10, 15, 20, 25, 32, 50, 100, 150, or 200 meters.
Planning Motion
31
1756-M02AE Servo Module
The servo module is a 2-axis, closed-loop servo module that receives profile information from the ControlLogix controller. The servo module makes sure that the actuator (motor) follows the profile by monitoring the position feedback via the quadrature encoder input and generating an analog command reference for the drive. A position and velocity loop is closed every 200 s using position feedback as the input and 10V analog output. Important: The servo module must be in the same chassis as the ControlLogix controller that controls the servo module. If you distribute motion control across different locations, place a ControlLogix controller in each chassis that has a servo module.
1756-M02AE module specifications

Description: number of axes per ControlLogix controller number of axes per module power dissipation backplane current Value: 32 axes maximum 2 axes maximum 5.5W maximum 700 mA @ 5V dc 2.5 mA @ 24V dc 3.56W 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 95% noncondensing nested PI digital position and velocity servo 5 kHz incremental AB quadrature with marker 4 MHz counts per second maximum optically isolated, current sourcing input 1 s optically isolated, current sinking input analog voltage solid-state isolated relay contacts 1756-TBCH 1756-TBSH6 14 gauge (2mm2) stranded maximum1 3/64 inch (1.2 mm) insulation maximum category 22
Listed Industrial Control Equipment Certified Process Control Equipment Certified Class I, Division 2, Group A, B, C, D Marked for all applicable directives
operating temperature storage temperature relative humidity servo loop type rate encoder input type rate registration inputs type response time all other inputs servo output all other outputs removable terminal block (RTB) conductors
agency certification
1. Maximum wire size will require the extended depth RTB housing (1756-TBE). 2. Use this conductor category information for planning conductor routing as described in the system level installation manual. See the Programmable Controller Wiring and Grounding Guidelines, publication number 1770-4.1.
32
Planning Motion
Cables for Use with the 1756-M02AE Module

Catalog Number: 1394-CCAExx xx = 01 for 1 meter
03 for 3 meter 08 for 8 meter 15 for 15 meter
Enable/Drive Fault
If you connect the 1756-M02AE module to a 1394 or 1398 series servo drive, choose one of these cables:
Description: 1756-M02AE to a 1394 two-axis, analog servo module

Enable/Drive Fault 7 12 1 Axis 0 6
36 34 32 30 28 26 24 22 20 18 16 14 12 10 8 6 4 2
+5V AX0
System OK 7 12 1 Axis 1 6
1756-M02AE
35
33
31
29
27
25
23
21
19
17
15
13
11
+5V AX1
1398-CCAExx xx = 01 for 1 meter

1756-M02AE to a 1398 two-axis, analog servo module
Axis 0 - J1
36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
24V - AX0 Brake - AX0 Reset - AX0
Axis 1 - J1
Reset - AX1 Brake - AX1 24V - AX1
1394-CFLAExx xx = 01 for 1 meter

1756-M02AE to a 1394 single-axis, analog servo module

ENABLE/DRIVE FAULT - AXIS 0
7 12
1
AXIS 0 1394-CFLAE 1756-M02AE 5V ENC PWR - AXIS 0
6
M02AE - OK
1398-CFLAExx xx = 01 for 1 meter

1756-M02AE to a 1398 single-axis, analog servo module
24V BRAKE RESET 1398-CFLAE J1
Planning Motion
33
1756-SYNCH SynchLink Module
The 1756-SYNCH SynchLink module connects a ControlLogix chassis to a SynchLink fiber optic communications link. SynchLink provides time synchronization and data broadcasting capabilities for distributed motion and coordinated drive control. These devices support SynchLink: 1756-SYNCH SynchLink module 1756-DM drive module PowerFlex 700s drive The 1756-SYNCH module performs three functions: coordinate CST time across multiple ControlLogix chassis move limited amount of data from one chassis to another at a high speed let one controller consume motion axes data from a controller in another chassis
1756-SYNCH module specifications

Description: operating wavelength SynchLink data rate baud rate connecting cable Value: 650nm (red) 5Mbps 5Mbaud 200/230 micron Hard Clad Silica (HCS) VersaLink V-system Order 1403-CFxxx power monitoring cable2 or from Lucent Technologies, Specialty Fiber Technologies division maximum length 300m minimum length 1m star configuration hub 1751-SLBA (SynchLink base unit) plug up to 1751-SL4SP (SynchLink 4-port splitters) 256 devices on star 1200mA @ 5.1V dc 3mA @ 24V dc 6.19W 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 95% noncondensing tested 2.0 G @ 10-500Hz per IEC 68-2-6 30G peak for 11ms 50G peak for 11ms
Class I Division 2 Hazardous marked for all applicable directives
backplane current
operating temperature storage temperature relative humidity vibration operating shock storage shock agency certification1
1. CSA certification - Class I Division 2, Group A, B, C, D or nonhazardous locations. 2. The xxx determines the length. Select 001, 003, 005, 010, 020, 050, 100, or 250 meters.
34
Planning Motion
SynchLink is a uni-directional system that can be configured in star, daisy chain, or ring topologies:
Topology: Star 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 Example: The star configuration transfers data from a master node through hubs to end nodes.
ControlNet master node
SynchLink
hub
end node
hub
hub
end node
end node
end node
end node
end node
Daisy Chain Optional: 1751-SLBP bypass switch block Supports: 10 nodes (including master and end nodes) per daisy chain network Ring Optional: 1751-SLBP bypass switch block Supports: 10 nodes (including master and end nodes) per daisy chain network
In a daisy chain configuration, the SynchLink network starts at the master node and ends at the end node.
master node
center node
center node
end node
SynchLink
ControlNet
The ring configuration is a permutation of the daisy chain configuration. In the ring configuration, the SynchLink network starts and ends at the master node.
master node
center node
center node
center node
SynchLink
ControlNet
Planning Motion
35
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. Each version of the drive communicates with a unique distributed power module:
Catalog Number:1 1756-DMD30 1756-DMF30
2
Communicates with: SD3000/3100 dc drives SF3000 Regen field control
1. The 1756-DM modules are only available through Drive Systems. 2. Check with Drive Systems for product availability.
distributed power system
PMI chassis
RSLogix 5000 software Drive Tools software RSView software
ControlLogix system with four 1756-DM modules
36
Planning Motion
1756-DMxxx module specifications

Description: operating wavelength data rate connecting cable SynchLink Value: 650 nM (red) 5 Mbps 200/230 micron Hard Clad Silica (HCS) VersaLink V-system Order 1403-CFxxx power monitoring cable1 or from Lucent Technologies, Specialty Fiber Technologies division maximum length 300m minimum length 1m maximum node count backplane current power dissipation temperature relative humidity vibration operating shock agency certification
Listed Industrial Control Equipment Certified Process Control Equipment Certified Class I, Division 2, Group A, B, C, D Marked for all applicable directives Approved Class I, Division 2, Group A, B, C, D
Drive Communications Value: 820 nM (infrared) 10 Mbps 62.5/125 micron glass one pair SC Style and one pair ST Style Order 1756-DMCFxxx drive communications fiber optic cable2 or breakout cable from Belden 225362 or Mohawk M92021 maximum length 300m minimum length 1m 1 PMI chassis
10 daisy chain configuration 256 star configuration with multiplexing blocks 1.35A @ 5V dc 3.0mA @ 24V dc 6.96W 23.7 BTU/hr operating 0 to 60 C (32 to 140 F storage -40 to 85 C (-40 to 185 F) 5% to 95% noncondensing 5g @ 10- 50Hz per IEC 68- 2- 6 operating 30G peak for 11ms storage 50G peak for 11ms
1. The xxx determines the length. Select 001, 003, 005, 010, 020, 050, 100, or 250 meters. 2. The xxx determines the length. Select 001, 003, 010, or 030 meters.
Planning Network Communications Step 3 - Select: communication modules associated cable(s) and network equipment sufficient modules and cables if you are planning a redundant ControlNet system
37
Planning Network Communications

A ControlLogix controller communicates across the backplane with 1756 modules in the local chassis. A ControlLogix controller can also communicate across the backplane with communication interface modules to monitor and control I/O on EtherNet/IP, ControlNet, DeviceNet, and the Universal Remote I/O networks and to monitor Foundation Fieldbus data. General communication messages can be sent from or received by ControlLogix controllers across EtherNet/IP, ControlNet, DeviceNet, DH+, Universal Remote I/O, RS-232 serial (DF1 protocol), and DH-485 networks. Messages are sent directly from one communication interface module to another across the backplane. You can route a message through a maximum of 4 chassis (8 communication hops). You determine your communication architecture based on your networking needs. There are three main types of networks:
Information networks
An information network: provides a link between the plant floor and manufacturing systems connects to multiple vendors host computers has the capacity to transfer large data files supports standard network management and troubleshooting tools A control network: offers real-time performance is deterministic and repeatable supports peer-to-peer messaging connects to programmable controllers, personal computers, man-machine interface devices, drives, motion devices, etc. support programming and device configuration A device network: reduces wiring costs because devices do not need to be directly wired to a programmable controller supports device-level diagnostics connects to multiple vendors devices
Control networks
Device networks
38
NetLinx architecture
NetLinx architecture is the foundation for three open networks that support ControlLogix devices: DeviceNet, ControlNet, and EtherNet/IP. The NetLinx architecture combines network services with CIP (control and information protocol) and open software interfaces. The NetLinx architecture is designed to include device, control, and information networks. You can mix and match one, two, or all three of the networks, based on your specific application. You can seamlessly move data among the networks without additional programming, configuration, or creation of routing tables. NetLinx is wire independent. This means that you select components and media according to your specific application. With choices like EtherNet/IP based on EtherNet TCP/IP, for information and control, ControlNet for deterministic control, and DeviceNet at the device level, you can design a control solution that integrates the most up-to-the-minute technology with the most advanced functionality. To further develop your system, NetLinx architecture incorporates open technologies like OLE for Process Control (OPC) and RSLinx and IOLinx from Rockwell Software for a seamless interface to your computer systems with commercially available hardware and software components.
39
Selecting a network
You can configure your system for information exchange between a range of devices and computing platforms and operating systems. You select the communication interface module(s) for the network(s) that meet your needs:
If your application requires: recommended medium for plant-wide sharing of data high-speed transfer of time-critical data between controllers and I/O devices high-speed data transfer between information systems and/or a large quantity of controllers Internet/Intranet connection program maintenance high-speed transfer of time-critical data between controllers and I/O devices deterministic and repeatable data delivery program maintenance media redundancy intrinsic safety controller redundancy connections of low-level devices directly to plant floor controllers, without the need to interface them through I/O modules more diagnostics for improved data collection and fault detection less wiring and reduced start-up time than a traditional, hard-wired system plantwide and cell-level data sharing with program maintenance transfer of information between controllers plantwide and cell-level data sharing with program maintenance transfer of information between controllers connections between controllers and I/O adapters distributed controllers so that each controller has its own I/O and communicates with a supervisory controller Fieldbus transmitters and actuators closed-loop control process automation modems supervisory control and data acquisition (SCADA) Use this network: EtherNet/IP network see page 42 Type:
control and information network NetLinx architecture
ControlNet network see page 46
control and information network NetLinx architecture
DeviceNet network see page 48
device network NetLinx architecture
Data Highway Plus see page 50 DH-485 network see page 57 Universal Remote I/O network see page 51 Fieldbus network see page 53 serial network see page 55
information network
information network
control network
device network
information network
Connecting Devices Across Multiple Platforms
You can use your ControlLogix system to bridge and route control and information data. Communication does not depend on a controller in the chassis. You can bridge across these networks: DH+ network EtherNet/IP network ControlNet network
40
Bridging between devices
DH+/RIO POWER
ETHERNET
ControlNET
B#15
CH A CH B OK RXD TXD OK
A#24
OK B A
ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K
ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K
ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K
ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K
ControlLogix system
B A
DH+ network
ControlNet network
EtherNet/IP network
PLC-5 processor
PLC-5E processor
PLC-5C processor
SLC controller
workstation with RSLinx
Reply Origin
DH+ network PLC-5 processor SLC 5/04 processor yes yes yes yes yes yes yes RSLinx software yes yes na yes na yes na
EtherNet/IP network PLC-5E processor yes yes yes yes yes yes yes RSLinx software yes yes na yes na yes na
ControlNet network PLC-5C processor yes yes yes yes yes yes yes RSLinx processor yes yes na yes na yes na
DH+ network
PLC-5 processor SLC-5/04 processor RSLinx software
yes yes yes yes yes yes yes
EtherNet/IP network
PLC-5E processor RSLinx software
ControlNet network
PLC-5C processor RSLinx software
41
Distributed DH+ bridging

DH+ network ControlNet network EtherNet/IP network
DH+/RIO POWER ControlNET ETHERNET POWER DH+/RIO ControlNET ETHERNET
B#15
A#24
OK B A RXD TXD OK
ControlLogix system
ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K
B#15
CH A CH B OK
A#24
OK B A RXD TXD OK
ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K
CH A CH B OK
ControlLogix system
SLC controller PLC-5 processor workstation with RSLinx PLC-5 processor
SLC controller workstation with RSLinx
Reply Origin
DH+ network PLC-5 processor SLC 5/04 processor yes yes yes RSLinx software yes yes na
DH+ network
PLC-5 processor SLC-5/04 processor RSLinx software
yes yes yes
Distributed ControlNet bridging

DH+ network ControlNet network EtherNet/IP network
DH+/RIO POWER ControlNET ETHERNET POWER DH+/RIO ControlNET ETHERNET
B#15
CH A CH B OK
A#24
OK B A RXD TXD OK
ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K
B#15
CH A CH B OK
A#24
OK B A RXD TXD OK
ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K
ControlLogix system
B A B A
ControlLogix system
PLC-5 processor
PLC-5 processor

20899
Reply Origin
ControlNet network PLC-5 processor RSLinx software yes na
ControlNet network
PLC-5 processor RSLinx software
yes yes
42
EtherNet/IP Network
Ethernet Industrial Protocol (EtherNet/IP) is an open industrial networking standard that supports implicit messaging (real-time I/O messaging), explicit messaging (messaging exchange), or both and uses commercial off-the-shelf Ethernet communication chips and physical media. The EtherNet/IP standard uses: IEEE 802.3 Physical and Data Link standard Ethernet TCP/IP protocol suite (Transmission Control Protocol/Internet Protocol), the Ethernet industry standard Control and Information Protocol (CIP), the protocol that provides real-time I/O messaging and information/peer-to-peer messaging.
firewall/router ControlLogix chassis with controller and Ethernet module PC running RSLinx software PanelView
Ethernet switch
FLEX I/O system with Ethernet adapter Ethernet switch
ControlLogix gateway
to ControlNet network
to DeviceNet network to DH+ network
Ethernet to RS-232-C interface ControlLogix I/O with Ethernet module MicroLogix controller Ethernet switch Ethernet SLC 5/05 Processor Ethernet PLC-5 Processor
Powermonitor 3000 master with Ethernet communication card
Powermonitor II with Ethernet communication card
43
Typically, an EtherNet/IP network uses an active star topology in which groups of devices are connected point-to-point to a switch. Switches provide virtual connections that help to control collisions and reduce traffic on the network. In a control application, in which real-time data access is critical, network switches are recommended instead of hubs. The benefit of a star topology is in its support of both 10 and 100 Mbps products. You can mix 10 and 100 Mbps devices, and the ethernet switch will negotiate the speed. Also, the star topology offers you connections that are simple to wire, easy to debug or find failures, and easy to maintain. The use of full duplex equipment and switches further increases the determinism of an Ethernet network by reducing packet collisions and enabling the equipment to send and receive data simultaneously. All EtherNet/IP real-time control equipment designed and manufactured by Rockwell Automation supports full duplex.
EtherNet/IP product capability

Recipient
EtherNet/IP PLC-5 processor EtherNet/IP SLC 5/05 processor PLC-5 processor via 1785-ENET ControlLogix controller with 1756-ENBT or 1756-ENET1 1794-AENT EtherNet/IP FLEX I/O adapter 2711 standard PanelView on EtherNet/IP RSLinx software
Originator
EtherNet/IP PLC-5 processor EtherNet/IP SLC 5/05 processor PLC-5 processor via 1785-ENET ControlLogix controller with 1756-ENBT or 1756-ENET1 2711 standard PanelView on EtherNet/IP RSLinx software
1. Series B or later.
information
information
information
information
not supported
information
information
information information
not supported not supported
information
information
information
information I/O data interlocking information
information I/O data
information
information
information
information
information
not supported
information
information
information
information
information
information
information
information
information
44
1756-ENBT EtherNet/IP communication interface module

The EtherNet/IP communication module controls I/O over an EtherNet/IP network. The module also bridges EtherNet/IP links to route messages to devices on other networks. Important: The 1756-ENBT module is currently under development. Check with your Rockwell Automation representative for availability.
Description: communication rate connections Value:1 10/100 Mbps Each module allows a maximum of: 64 TCP/IP connections 128 ControlLogix connections (I/O and information data) twisted pair RJ-45 700mA @ 5V dc 10mA @ 24V dc 4W 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 95% noncondensing 10 to 150 Hz 5.0 G maximum peak acceleration 30G peak for 11ms 50G peak for 11ms 0.3 kg (0.6 lb)
Listed Industrial Control Equipment Certified Process Control Equipment Certified Class I, Division 2, Group A, B, C, D Approved Class I, Division 2, Group A, B, C, D Marked for all applicable directives Marked for all applicable acts N223
cable backplane current1
operating temperature storage temperature relative humidity vibration operating shock storage shock weight1 agency certification
1. These specifications are planned characteristics for the module and are subject to change.
45
1756-ENET EtherNet/IP communication interface module

The EtherNet/IP communication module bridges EtherNet/IP links to route messages to devices on other networks, such as ControlNet, DeviceNet, and Data Highway Plus networks. Series B (and greater) of the module can also control I/O modules.
Description: communication rate connections Value: 10 Mbps Each module allows a maximum of: 64 TCP/IP connections 128 ControlLogix connections (I/O and information data) Choose: 1756-TC02 (low-profile 2-meter transceiver cable) 1756-TC15 (low-profile 15-meter transceiver cable) Choose: 1785-TR10B2 (thin wire) 1785-TR10B5 (thick wire) 1785-TR10BF (fiber optic) 1785-TR10BT (twisted pair) 900mA @ 5V dc 350mA @ 24V dc 12.99W 2 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 95% noncondensing 10 to 150 Hz 5.0 G maximum peak acceleration 30G peak for 11ms 50G peak for 11ms 0.3 kg (0.6 lb)
cable
transceiver
backplane current
conductor category operating temperature storage temperature relative humidity vibration operating shock storage shock weight agency certification
46
ControlNet Network
A ControlNet network is a real-time, control network that provides high-speed transport of both time-critical I/O data and messaging data, including upload/download of programming and configuration data and peer-to-peer messaging, all on one, single physical media link. A ControlNet network is highly deterministic because it has the ability to reliably predict when data will be delivered. You can connect a variety of devices to a ControlNet network, including personal computers, controllers, operator interface devices, drives, I/O modules, and other devices with ControlNet connections. A ControlNet network is an open network that provides the performance required for critical control data, such as I/O updates and controller-to-controller interlocking.
workstation running programming software with 1784-KTCx
ControlNet
PWR
STS
PORT MOD NET A NET B
PanelView terminal
ControlLogix chassis
PLC-5/40C controller
PowerFlex 700S drive
ControlNet statistics
Rates: transmission: 5 Mbps network update time: 2-100ms Cable lengths: 1000m (3,280 ft.) with 2 devices 250m (820 ft.) with a maximum of 48 devices tap drop cable length fixed at 1m (3 ft.) maximum distance 6km with repeaters Maximum number of nodes: 99
47
1756-CNB, -CNBR ControlNet communication interface module

The ControlNet communication module bridges ControlNet links to route messages to devices on other networks, such as EtherNet/IP, ControlNet, and Data Highway Plus networks. The ControlNet communication module also monitors and controls 1756 I/O modules located remotely from the ControlLogix controller.
Description: communication rate connections cable Value: 5 Mbps 64 connections per module RG-6 coaxial cable 1786-RG6 (shield high flex cable) 1786-RG6F (quad shield high flex coax cable) 1786-XT Choose: 1786-TPR (T-tap right angle) 1786-TPS (T-tap straight) 1786-TPYR (Y-tap right angle) 1786-TPYS (Y-tap straight) 1756-CNB 970mA @ 5V dc 1.7mA @ 24V dc 4.98W 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 95% noncondensing 10 to 150 Hz 5.0 G maximum peak acceleration 30G peak for 11ms 50G peak for 11ms 1756-CNB 1756-CNBR 0.3 kg (0.6 lb) 0.3 kg (0.7 lb) 1756-CNBR 1000mA @ 5V dc 1.7mA @ 24V dc 5.14W
termination resistor tap
backplane current
operating temperature storage temperature relative humidity vibration operating shock storage shock weight agency certification
48
DeviceNet Network
A DeviceNet network is an open, low-level communication link that provides connections between simple, industrial devices (such as sensors and actuators) and high-level devices (such as controllers). Based on standard Controller Area Network (CAN) technology, this open network offers interoperability between devices from multiple vendors. A DeviceNet network provides:
Benefit: simple devices from multiple vendors that meet DeviceNet standards are interchangeable, giving you flexibility and choice an open network provides common, end-user solutions, and reduces the need to support a wide variety of device networks you can remove and replace devices without disrupting other devices a networked device installation is more cost-effective than traditional I/O wiring because one wire supplies both communications and 24V power
Feature: interoperability common network lower maintenance costs cost-effective wiring
At the device layer, a DeviceNet network can connect low-level devices directly to plant-floor controllers.
PLC-5 controller with 1771-SDN scanner module ControlLogix controller with 1756-DNB module
DeviceNet
other devices PanelView terminal motor starter laptop

PORT MOD NET A NET B PWR STS
sensor pushbutton cluster
input/output devices drive
bar code scanner indicator lights
DeviceNet statistics
Data transmission rate: 125 Kbps 250 Kbps 500 Kbps Cable trunk length: 500m (1,640 ft.) 250m (820 ft.) 100m (328 ft.) Cumulative drop length: 125m (512 ft.) 78m (256 ft.) 39m (128 ft.) 6 m (20 ft.) 64 Maximum drop length: Maximum number of nodes:
49
1756-DNB DeviceNet scanner interface module

The DeviceNet scanner module acts as an interface between DeviceNet devices and a ControlLogix chassis. The scanner module communicates with DeviceNet devices over the network to: read and write inputs and outputs to and from a device download configuration data to a device monitor operational status of a device The scanner module communicates with a ControlLogix controller in a ControlLogix chassis to provide I/O data, status information and configuration data.
Description: communication rate connections cable Value: 125 Kbps, 250 Kbps, or 500 Kbps 2 connections to a dedicated ControlLogix controller Choose: 1485C-P1-C50 (thin, yellow, chemical resist, 50 meters) 1485C-P1-C150 (thin, yellow, chemical resist, 150 meters) 1485C-P1-C300 (thin, yellow, chemical resist, 300 meters) 1485C-P1-C600 (thin, yellow, chemical resist, 600 meters) 1485C-P1-A50 (thick, grey, 50 meters) 1485C-P1-A150 (thick, grey, 150 meters) 1485C-P1-A300 (thick, grey, 300 meters) 1485C-P1-A500 (thick, grey, 500 meters) 1485A-C2 Choose: 1485P-P2T5-T5 (2 ports) 1485P-P4T5-T5 (4 ports) 1485P-P8T5-T5 (8 ports) 600mA @ 5V dc 3mA @ 24V dc 3.13W 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 95% noncondensing 10 to 150 Hz 5.0 G maximum peak acceleration 30G peak for 11ms 50G peak for 11ms 0.3 kg (0.6 lb)
termination resistor tap
backplane current
50
DH+ Network
The Data Highway Plus network is a local area network designed to support remote programming and data acquisition for factory-floor applications. You can also use DH+ communication modules to implement a small peer-to-peer network. You can use a DH+ network for data transfer to other controllers or high-level computers and as a link for programming multiple controllers. A ControlLogix controller can communicate over a DH+ network with other controllers and with a workstation. The DH+ network supports daisy chain and trunkline-dropline configurations.
PLC-5 controller PanelView terminal workstation with RSLogix 5000 software workstation
Data Highway Plus
SLC-5/04 controller
ControlLogix chassis with 1756-DHRIO module
DH+ statistics
Data transmission rate: Maximum cable length: 57.6 Kbps 230.4 Kbps 3,048m (10,000 ft.) 762 m (2,500 ft) Maximum number of nodes: 64 per link
51
Universal Remote I/O Network
The strength and versatility of the Universal Remote I/O network comes from the breadth of products it supports. In addition to 1771 I/O, the Universal Remote I/O network supports many Allen-Bradley and third-party devices. Typical applications range from simple I/O links with controllers and I/O modules, to links with a variety of other devices. You connect devices through remote I/O adapter modules or built-in remote I/O adapters.
workstation with PanelBuilder software
ControlNet, EtherNet/IP, or DH+ network
ControlLogix chassis
Universal remote I/O link
FLEX I/O adapter 1791 I/O block PLC-5 controller in adapter mode PanelView terminal
Universal remote I/O statistics

Data transmission rate: 57.6 Kbps 115.2 Kbps 230.4 Kbps Maximum cable length: 3,048m (10,000 ft.) 1,524m (5,000 ft.) 762m (2,500 ft.) 1 scanner 32 adapters Maximum number of nodes:
52
1756-DHRIO Data Highway Plus and remote I/O communication interface module
The Data Highway Plus and remote I/O module supports messaging between devices on Data Highway Plus networks and devices on other networks, such as EtherNet/IP, ControlNet, and DeviceNet 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.
Description: communication rate connections Value: DH+: 57.6 or 230.4 Kbps Universal Remote I/O: 57.6 Kbps, 115.2 Kbps, or 230 Kbps 32 connections per DH+ channel 32 logical rack connections per remote I/O channel 16 block-transfer connections per remote I/O channel cable termination resistor backplane current 1770-CD Belden 9463 150 Ohm and 82 Ohm resistors ship with the 1756-DHRIO module 850mA @ 5V dc 1.7mA @ 24V dc 4.38W 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 95% noncondensing 10 to 150 Hz 5.0 G maximum peak acceleration 30G peak for 11ms 50G peak for 11ms 0.3 kg (0.6 lb)
53
Fieldbus Network
A Foundation Fieldbus network is a standard-based network designed to handle process automation applications. Fieldbus interconnects measurement and control equipment, such as sensors, actuators, and controllers. The Fieldbus environment is the base level network in the hierarchy of plant networks. At the device layer, a Fieldbus network can connect low-level devices directly to plant-floor controllers.
laptop ControlNet
ControlLogix controller with 1756-CNB module
Fieldbus linking device
transmitter actuator display
transmitter
transmitter digital mux actuator analog mux
54
1788-CN2FF Foundation Fieldbus Linking Device

The Foundation Fieldbus linking device facilitates distributed control by adding Foundation Fieldbus support to your ControlLogix system. You can have one linking device per ControlNet tap. The linking device: connects to two, independent Fieldbus H1 networks mounts on a 35mm DIN rail supports closed-loop control Process variables published on Foundation Fieldbus are subscribed by the linking device and then produced on the ControlNet network at the network update time. Scheduled data from a linking device can go to a ControlLogix controller every 2 msecs. Conversely, process variables produced by a ControlNet device can be consumed by the linking device and subscribed by other Foundation Fieldbus devices.
Description: communication rate connections cable power requirements operating temperature storage temperature relative humidity vibration operating shock storage shock weight agency certification Value: 2 ms over ControlNet 31.25 Kbps over Fieldbus to redundant ControlNet media for each H1 network each linking device supports two H1 networks 9-pin FieldBus cable pins 6 and 7 handle Fieldbus signals 11-30V dc 270 mA @ 24V dc (typical) 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 90% noncondensing 10-500Hz per IEC 68-2-6 2.0 G maximum peak acceleration 30G peak for 11ms 50G peak for 11ms 0.4 kg (13.5 oz.)
55
Serial Network
The ControlLogix serial port is compatible with RS-232 serial communication. The serial port supports the DF1 protocol to communicate with others devices on the serial link. You can select a DF1 mode:
For: 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
Use this DF1 mode: point to point DF1 master DF1 slave user mode (ASCII)
DH+ Ethernet RS-232 RS-232
RS-232
modem
modem
modem
The ControlLogix controller uses a 1756-CP3 cable to connect to the serial port. Or you can make a 9-pin cable using these pinouts:
1 CD 2 RDX 3 TXD 4 DTR 5 COMMON 6 DSR 7 RTS 8 CTS 9 RI straight cable end 1 CD 2 RDX 3 TXD 4 DTR 5 COMMON 6 DSR 7 RTS 8 CTS 9 RI right-angle cable end
The cable is shielded and tied to the connector housing at both ends.
56
1756-MVI, -MVID multi-vendor interface module

The multi-vendor interface module provides additional access to serial devices. The module is user programmable to accommodate devices with unique serial protocols. The module has three ports:
Port: PRT1 (console) PRT2 PRT3 Description: Connect a programming device via a RS-232 interface. Connect to other devices via a RS-232, RS-422, or RS-485 interface.
Use the application programming interface (API) software to access the ControlLogix backplane and module serial ports. Develop applications for the module using industry-standard DOS programming tools and the appropriate API components.
Description: options communication rate connections cable Value: 1756-MVI 1756-MVID module by itself module and API software
configurable, depending on serial protocol 1 3 serial adapter cables ship with the module the locking-type RJ45 connector installs in the module; the other end is a DB-9 male connector 800mA @ 5V dc 3mA @ 24V dc 4W 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 95% noncondensing 10 to 150 Hz 5.0 G maximum peak acceleration 30G peak for 11ms 50G peak for 11ms
backplane current
operating temperature storage temperature relative humidity vibration operating shock storage shock agency certification
57
DH-485 Networks
The DH-485 protocol uses RS-485 half-duplex as its physical interface. (RS-485 is a definition of electrical characteristics; it is not a protocol.) You can configure the RS-232 port of the ControlLogix controller to act as an DH-485 interface.
1761-CBL-AP00 or 1761-CBL-PM02
connection from ControlLogix controller to port 1 or port 2

1747-CP3 or 1761-CBL-AC00
1761-NET-AIC+ DH-485 network 1747-AIC
SLC 5/03 controller
On the DH-485 network, the ControlLogix controller can send and receive messages to and from other controllers on the network. Currently, the DH-485 support does not include remote programming or monitoring through RSLogix 5000 Enterprise Series software. You need a 1761-NET-AIC+ converter for each controller you want to put on the DH-485 network. You can have two controllers per one 1761-NET-AIC+ converter, but you would 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). The cable you use to connect the controller depends on the port you use on the 1761-NET-AIC+ converter.
If you connect to this port: port 1 DB-9 RS-232, DTE connection port 2 mini-DIN 8 RS-232 connection Use this cable: 1747-CP3 or 1761-CBL-AC00 1761-CBL-AP00 or 1761-CBL-PM02
58
Connecting to Other Networks 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.
The screens above show the connection parameters for the 1203-CN1 module. These parameters differ depending on the module. See the modules vendor for modules characteristics.
59 Step 4 - Select: a controller with sufficient memory 1756-BATM for each 1756-L55M16 controller replacement batteries
Selecting a Controller
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 controller can control local I/O, as well as remote I/O across Ethernet/IP, ControlNet, DeviceNet, and Universal Remote I/O networks. You can place multiple ControlLogix controllers in a single ControlLogix chassis. Multiple controllers can read input values from all inputs. A single controller can communicate over multiple communication modules and multiple controllers can share the same communication module.
ControlLogix Controllers
Description:
Logix5555 controller specifications

Controller: 1756-L55M12 1756-L55M13 1.5 Mbytes 1756-L55M14 3.5 Mbytes 1756-L55M162 7.5 Mbytes total (3.5 Mbytes maximum for data) 1.40A 0.02A 5.0W 17.1 BTU/hr 13.4 oz.
available user memory1
750 Kbytes
backplane current +5V dc +24V dc average power dissipation average thermal dissipation weight Description:
1.15A 0.02A 4.50W 15.4 BTU/hr 12.5 oz. Controller: 1756-L55M22
1.15A 0.02A 4.50W 15.4 BTU/hr 12.5 oz.
1.25A 0.02A 4.75W 16.2 BTU/hr 12.8 oz.
1756-L55M23 1.5 Mbytes plus 1.5 Mbytes nonvolatile memory 1.15A 0.02A 4.50W 15.4 BTU/hr 12.5 oz.
1756-L55M24 3.5 Mbytes plus 3.5 Mbytes nonvolatile memory 1.25A 0.02A 4.75W 16.2 BTU/hr 12.8 oz.
available user memory1
750 Kbytes plus 750 Kbytes nonvolatile memory 1.15A 0.02A 4.50W 15.4 BTU/hr 12.5 oz.
backplane current +5V dc +24V dc average power dissipation average thermal dissipation weight
1. Available user memory is the amount of memory available to the user after RSLogix 5000 Enterprise Series software is connected and a null program is loaded. 2. Check with your Rockwell Automation representative for details on the memory restrictions of the 1756-L55M16 controller
60
Common ControlLogix controller specifications

Description: operating temperature storage temperature relative humidity vibration operating shock storage shock programming cable battery Value 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 95% noncondensing 10 to 500 Hz 2.0 G maximum peak acceleration 30G peak for 11ms 50G peak for 11ms 1756-CP3 or 1747-CP3 serial cable category 31 1756-BA1 (94194801) or 1756-BATM (containing a 1756-BATA battery assembly)2 Class I Division 2 Hazardous marked for all applicable directives marked for applicable acts
N223
agency certification
1. See the Programmable Controller Wiring and Grounding Guidelines, publication 1770-4.1. 2. Strongly recommended for the 1756-L55M16 controller; recommended for the 1756-L55M14 and 1756-L55M24 controllers.
Note: The 1756-L55 controllers are the most current ControlLogix controllers. While the original 1756-L1 controllers are still available, the current controllers execute motion instructions and function blocks approximately 30% faster than 1756-L1 controllers and the current controllers support more memory than the 1756-L1 controllers
61
The following equations provide an estimate of the memory needed for a controller. Each of these numbers includes a rough estimate of the associated user programming. Depending on the complexity of your application, you might need additional memory. Controller tasks Discrete I/O points Analog I/O points _____ * 4000 = _____ bytes (minimum 1 needed) _____ * 400 = _____ bytes _____ * 2600 = _____ bytes
Communication modules1 _____ * 2000 = _____ bytes Motion axis

1
_____ * 8000 = _____ bytes Total = _____ bytes
When considering 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.
ControlLogix 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:
This memory board: 1756-M12 1756-M13 1756-M14 1756-M16 1756-M22 1756-M23 1756-M24 Supports: 750 Kbytes memory 1.5 Mbytes memory 3.5 Mbytes memory 7.5 Mbytes of user memory with a maximum of 3.5 Mbytes for tag data storage 750 Kbytes memory plus 750 Kbytes nonvolatile memory 1.5 Mbytes memory plus 1.5 Mbytes nonvolatile memory 3.5 Mbytes memory plus 3.5 Mbytes nonvolatile memory
In addition to standard memory (RAM), the 1756-M22, 1756-M23, and 1756-M24 memory boards also support nonvolatile memory storage (flash) so you can permanently store a program on a controller. You can: manually trigger the controller to save to or load from nonvolatile memory configure the controller to load from nonvolatile memory on power up
62
Controller Batteries
1756-BA1 battery
The ControlLogix controller comes with one 1756-BA1 battery. Only order a battery if you need a replacement.
top middle bottom
no connection black lead (-) red lead (+)
1756-BATM battery module

The battery module is an externally-mounted housing that contains a battery assembly (1756-BATA) and provides longer battery life than the 1756-BA1 battery. Order replacement battery assemblies as needed. You can replace the battery assembly within the battery housing.
Use 1M cable that comes with the 1756-BATM to connect to the battery connector on the controller
Externally mount the 1756-BATM on a panel within 1m of the controller.
The battery module is highly recommended for the 1756-LxxM16 controllers and can be used on smaller memory controllers to extend backup time.
Battery specifications
Description: 1756-BA1 battery 1756-BATM battery module (houses the battery assembly) 1756-BATA battery assembly Value: 0.59g lithium contains: one 1756-BATA assembly 1m cable to connect housing to controller maximum of 5g lithium per each D cell; assembly contains 2 D cells
Estimated battery life

Battery: 1756-BA1 Estimated Worst Case Battery Life @ 25C: with 1756-L55M12: 63 days with 1756-L55M13: 63 days with 1756-L55M14: 30 days with 1756-L55M16: 13 days with 1756-L55M12: 299 days with 1756-L55M13: 299 days with 1756-L55M14: 213 days with 1756-L55M16: 133 days
1756-BATM (contains 1756-BATA)
63
ControlLogix Controller Connections
The ControlLogix system uses a connection to establish a communication link between two devices. Connections can be: controller to local I/O modules or local communication modules controller to remote I/O or remote communication modules controller to remote I/O (rack optimized) modules produced and consumed tags messages
You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system. The ControlLogix system supports both scheduled and unscheduled connections.
Connection: scheduled Description: A scheduled connection identifies a specific device and lets you send and receive data repeatedly at a predetermined rate, 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. Other scheduled connections include connections to: communication devices produced/consumed tags You must use RSNetWorx for ControlNet to enable all scheduled connections and establish a network update time (NUT) for the network. An unscheduled connection is a message transfer between controllers that is triggered by the program (i.e., the MSG instruction). Unscheduled messaging lets you send and receive data when needed.
unscheduled
Determining Scheduled Connections for Produced and Consumed Tags

This type of tag: produced
The ControlLogix controller can produce (broadcast) and consume (receive) system-shared tags. Produced and consumed tags each require scheduled connections.
Requires these connections: The local controller (producing) uses one connection for the produced tag and its first consumer and one connection for each additional consumer. As you increase the number of controllers that can consume a produced tag, you also reduce the number of connections the controller has available for other operations, such as communications and I/O. Each consumed tag requires one connection for the controller that is consuming the tag.
consumed
Controllers can produce and consume tags over: the ControlLogix backplane a ControlNet network an Ethernet/IP network. Important: 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.
64
Maximum number of produced and consumed tags

The controller supports:
As a: producer consumer The controller supports:
(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 As the number of consumed tags increases, the number of available produced tags decreases. Important: 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.
Determining Unscheduled Connections for Messages
Unscheduled connections are used for transferring data to other devices, such as other controllers or operator devices. Some messages use an unscheduled connection to send or receive data. Some messages also have the option of leaving the connection open (cache) or closing the connection when the message is done transmitting. The following table shows which messages use a connection:
Using this communication method: CIP CIP CIP with Source ID DH+ Uses a connection: Which you can cache:
This type of message: CIP data table read or write PLC2, PLC3, PLC5, or SLC (all types)
CIP generic
N/A
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. 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.
65
Determining Scheduled Connections for I/O Modules

Connection: direct
The ControlLogix system uses scheduled connections to transmit I/O data. These connections can be either direct or rack-optimized.
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. 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).
rack-optimized
Depending on the type of I/O modules in the ControlLogix system, both direct connections and rack-optimized connections can be used.
I/O System: 1756 basic digital I/O in a local chassis 1756 digital I/O in a remote chassis via a control network1 Supported Connection Type(s): direct connection direct connection or rack-optimized connection2 direct connection direct connection or rack-optimized connection direct connection rack-optimized connection direct connection via messaging direct connection via messaging rack-optimized connection
1756 analog I/O either in a local chassis or via a control network in a remote chassis FLEX digital I/O via a ControlNet network
FLEX analog I/O either in a local chassis or via a control network in a remote chassis digital I/O via a Universal Remote I/O network analog I/O via a Universal Remote I/O network 1771 analog I/O via a ControlNet network all DeviceNet I/O
1. The control network can be an Ethernet/IP or ControlNet network. 2. Rack-optimized connections for diagnostic and E-fuse modules do not send diagnostic or fuse data to controller.
66
Direct connections for 1756 I/O modules

In this example, the owner controller (local chassis) has three direct connections with the 1756 I/O modules in the remote chassis.
Local chassis Remote chassis
control network
The local controller in this example uses these connections:

Connection Type: controller to local I/O module controller to remote I/O module controller to remote communication module1 Module Quantity: 2 3 1 Connections per Module: 1 1 1 Total Connections: 2 3 1 total 6
1. The control network can be an Ethernet/IP or ControlNet network.
Rack-optimized connections for 1756 I/O modules

Using the same configuration in the first example, the owner controller (local chassis) uses one connection to communicate with all the digital I/O in the remote chassis. The data from all three modules is sent simultaneously at a rate specified by the 1756-CNB connection. This option eliminates the need for the three separate connections shown in the previous example. The local controller in this example uses these connections:
Connection Type: controller to local I/O module controller to remote communication module1 Module Quantity: 2 1 Connections per Module: 1 1 Total Connections: 2 1 total 3
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.
67
Combining direct and rack-optimized connections

A remote ControlLogix chassis can have both a rack-optimized connection and direct connections. In this example, the owner controller (local chassis) uses one rack-optimized connection to communicate with two digital I/O modules and uses one direct connection to communicate with an analog module in the same chassis.
control network

Connection Type: controller to local I/O module controller to remote analog I/O module controller to remote communication module1 (includes the remote, digital I/O) Module Quantity: 2 1 1 Connections per Module: 1 1 1 Total Connections: 2 1 1 total 4
68
Connections to 1771 I/O

In this example the controller has a direct connection to each digital I/O module in the local chassis. The controller also communicates with the 1771 chassis, through the remote 1756-DHRIO module, using one connection (a rack-optimized connection).
DH+ or Universal remote I/O network ControlNet network 1771 chassis

Connection Type: controller to local I/O module controller to remote 1756-CNB module controller to remote 1756-DHRIO module Module Quantity: 2 1 1 Connections per Module: 1 1 1 Total Connections: 2 1 1 total 4
The controller makes the connection through the 1756-DHRIO module to the adapter module in the 1771 chassis. The controller requires 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.
69
Connections to DeviceNet devices

In this example the controller has a direct connection to each digital I/O module in the local chassis. The controller uses two connections to communicate with the DeviceNet devices through the 1756-DNB module. The 1756-DNB module supports only a rack-optimized connection to its DeviceNet devices.
ControlNet network DeviceNet network
DeviceNet devices

Connection Type: controller to local I/O module controller to remote 1756-CNB module controller to remote 1756-DNB module (includes DeviceNet devices) Module Quantity: 2 1 1 Connections per Module: 1 1 2 Total Connections: 2 1 2 total 5
The 1756-DNB module does not establish connections to its devices; and therefore, the controller doesnt 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.
70
Determining Total Connection Requirements
The ControlLogix controller supports 250 connections. To calculate the total connection requirements for a ControlLogix 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: local I/O module (always a direct connection) 1756-M02AE, -M08SE servo module 1756-CNB, -CNBR communication module 1756-ENBT, -ENET communication module 1756-DNET communication module 1756-DHRIO communication module
Device Quantity:
Connections per Device: 1 3 0 0 2 1

total
Total Connections:
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:
Connection Type: remote 1756-CNB, -CNBR ControlNet communication module1 configured as a direct (none) connection configured as a rack-optimized connection remote 1756-ENBT, -ENET Ethernet communication module2 configured as a direct (none) connection configured as a rack-optimized connection remote I/O module over ControlNet (direct connection) other remote communication adapter produced and consumed tag produced tag and one consumer each additional consumer consumed tag cached message block-transfer message Device Quantity: Connections per Device: 0 or 1 0 or 1 1 1 1 1 1 1 1
total
1. See the ControlNet specifications on page 47 for details on how many connections the module supports. 2. See the Ethernet specifications on page 44 for details on how many connections the module supports.
Total Connections:
71
Communicating with Devices

I/O Modules: ControlLogix I/O (1756 series) SLC I/O (1746 series) FLEX Integra I/O (1793 series) FLEX I/O (1794 series)1 FLEX Ex I/O (1797 series) 1734 POINT I/O Compact I/O (1769 series) Block I/O (1791 series) ArmorBlock I/O (1792 series) 1771 I/O Display Devices: 2711 PanelView terminal 2711 e PanelView terminal RediPANEL module (2705 series) Dataliner (2706 series) DTAM (2707 series) Drives:3 1305 adjustable frequency ac drive 1336 adjustable frequency ac drive 1394 GMC drive and control 1394 analog servo drive 1394 SERCOS servo drive 1395 digital dc drive 1398 ULTRA series ac drive 2098 analog servo drive 2098 SERCOS servo drive4 FlexPak 3000 dc drive WebPak 3000 dc winder drive GV3000 ac drive PowerFlex 700S ac drive PowerFlex 700 ac drive PowerFlex 70 ac drive 1.
4
The ControlLogix controller can communicate with these devices:

ControlNet: yes no no yes yes no no no no yes2 ControlNet: yes yes no no no ControlNet: yes yes no no no yes no no no yes yes yes yes yes yes DeviceNet: no no yes yes no yes yes no yes no DeviceNet: yes no no no yes DeviceNet: yes yes yes no no no yes yes no yes no yes yes yes yes Universal Remote I/O: no yes yes yes no no no yes no yes Universal Remote I/O: yes yes yes yes yes Universal Remote I/O: yes yes yes no no yes no no no no no no yes yes yes RS-232 (DF1) serial: no limited no no no no no no no no RS-232 (DF1) serial: yes no no no yes RS-232 (DF1) serial: yes yes yes no yes yes yes yes yes yes yes yes yes yes yes DH-485: no no no no no no yes no no no DH-485: yes no no no yes DH-485: yes yes yes no no no no no no no no no no no no
Ethernet/IP: yes no no yes yes no no no no no Ethernet/IP: yes no no no no Ethernet/IP: no no no no no no no no no no no no no no no
The 1794-VHSC module is supported only as remote ControlNet I/O for every Logix controller. You cannot place a 1794-VHSC module (or any other modules that use extended data types) on the local or extended-local DIN rails of a FlexLogix controller. 2. 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. 3. Unless otherwise indicated, 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. 4. These drives are also supported on SERCOS and SynchLink links.
72
Communicating with Other Controllers and Communication Devices

The ControlLogix controller can communicate with a: 1756 ControlLogix controller 1769 CompactLogix controller 1789 SoftLogix5800 controller 1794 FlexLogix controller 5720 PowerFlex 700S DriveLogix controller 1785 PLC-5 controller 1747 SLC controller 1761 MicroLogix 1000 controller 1762 MicroLogix 1200 controller 1769 MicroLogix 1500 controller 1772 PLC-2 controller 1775 PLC-3 controller 5250 PLC-5/250 controller 2711 PanelView 2711 e PanelView 9355 RSLinx software 1784-KTC, -KTCx 1784-KT, -KTx 1784-PCD 1784-PCMK 1788-CN2DN 1788-CN2FF 1203-CN1 ControlNet module 1203-FM1/FB1 SCANport Ethernet network: yes no yes no no yes1,2 yes3 n/a n/a n/a n/a n/a no yes no yes n/a n/a n/a n/a n/a n/a n/a n/a
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.
ControlNet network: yes no yes yes yes yes yes n/a n/a n/a n/a n/a n/a yes yes yes yes n/a n/a n/a yes yes yes10 yes11 DeviceNet network: no no yes no no no no yes5 yes5 yes5 n/a n/a no yes no no n/a n/a yes n/a yes n/a n/a n/a DH+ network: yes no no no no yes yes4 n/a n/a n/a yes6 yes8 yes yes yes yes n/a yes n/a yes n/a n/a n/a n/a RS-232 (DF1) network: yes yes yes yes yes yes yes yes yes yes yes7 yes9 yes yes no yes n/a n/a n/a n/a n/a n/a n/a n/a DH-485 network: yes yes no yes no n/a no no no no n/a n/a n/a yes no no n/a n/a n/a n/a n/a n/a n/a n/a
1. 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 2. The 1785-ENET Ethernet communication interface module must be series A, revision D or later. 3. Use a 1747-L55x controller with OS501 or greater 4. Use a 1747-L54x controller. 5. The MicroLogix controller appears as I/O points to the ControlLogix controller. Requires 1761-NET-DNI DeviceNet interface. 6. The PLC-2 controller requires a 1785-KA module for DH+ communications. 7. The PLC-2 controller requires a 1771-KG module for serial (DF1) communications. 8. The PLC-3 controller requires a 1775-S5 module for DH+ communications 9. The PLC-3 controller requires a 1775-KA module for serial (DF1) communications. 10. Use the generic module configuration to configure the 1203-CN1 module and a CIP generic MSG instruction to communicate with the module. 11. 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.
73 Step 5 - Select: a chassis with sufficient slots 1756-N2 filler strips for
Selecting a Chassis
The ControlLogix system is a modular system that requires a 1756 I/O chassis. You can place any 1756 module in any slot. The backplane provides a high-speed communication path between modules. Multiple controllers on the backplane can pass messages between each other. 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 out another modules port, and sent across another link to its ultimate destination.
empty slots
Catalog number: 1756-A4 1756-A7 1756-A10 1756-A13 1756-A17
Number of slots: 4 7 10 13 17
Weight: 0.75 kg (1.7 lb) 1.10 kg (2.4 lb) 1.45 kg (3.2 lb) 1.90 kg (4.2 lb) 2.20 kg (4.8 lb)
Minimum cabinet size: (H x W x D) 50.7 x 50.7 x 20.3 cm (20 x 20 x 8 in) 50.7 x 70.0 x 20.3 cm (20 x 24 x 8 in) 76.2 x 50.7 x 20.3 cm (30 x 20 x 8 in) 76.2 x 70.0 x 20.3 cm (30 x 24 x 8 in) 82.2 x 76.2 x 20.3 cm (36 x 30 x 8 in)
Type of mounting: backpanel mounting
Environmental conditions: operating temperature: 0 to 60 C (32 to 140 F) storage temperature: -40 to 85 C (-40 to 185 F) relative humidity 5 to 95% (without condensation)
Important: Use the slot filler module 1756-N2 to fill empty slots. When you mount a chassis in an enclosure, make sure to meet these minimum spacing requirements:
> 15.3 cm (6.0 in)
Enclosure
allow 15.3 to 20 cm (6.0 to 8.0 in) between chassis and heat source allow 5.1 cm (2.0 in) between wireway and top or bottom of chassis
> 10.2 cm (4.0 in) 15.3 to 20 cm (6.0 to 8.0 in)
> 15.3 cm (6.0 in)
7.7 to 10.2 cm (3.0 to 4.0 in)
> 10.2 cm (4.0 in)
74
Mounting dimensions
right-side view of all chassis
16.9 cm (6.65 in) with extended depth housing (1756-TBE)
14.5 cm (5.8 in) 16.0 cm (6.3 in)
1756-A4 with power supply
1.1 cm dia. (0.433 in)
7.0 cm (2.76 in)
0.55 cm dia (0.217 in)
15.8 cm (6.22 in)
16.9 cm (6.65 in) 14.5 cm (5.71 in)
0.55 cm dia (0.217 in)
4.5 cm (1.77 in) 26.3 cm (10.35 in) 18.54 cm (7.30 in)
0.78 cm (0.31 in) dimension with a 1756-PSCA chassis adapter installed, rather than a power supply
75
Mounting dimensions (continued)

1.1 cm dia. (0.433 in) 17.5 cm (6.89 in) 0.55 cm dia (0.217 in)
15.8 cm (6.22 in)
16.9 cm (6.65 in) 14.5 cm (5.71 in) 4.71 cm (1.85 in)
0.55 cm dia (0.217 in)
36.8 cm (14.49 in)
29.04 cm (11.44 in)

0.55 cm dia (0.217 in) 1.1 cm dia. (0.433 in)
14.0 cm (5.51 in)
14.0 cm (5.51 in)
5.71 cm (2.25 in)
15.8 cm (6.22 in)
16.9 cm (6.65 in) 14.5 cm (5.71 in)
0.55 cm dia (0.217 in) 48.3 cm (19.02 in) 40.54 cm (15.96 in)
0.78 cm (0.31 in)
dimension with a 1756-PSCA chassis adapter installed, rather than a power supply
76
Mounting dimensions (continued)

0.55 cm dia (0.217 in) 1.1 cm Dia. (0.433 in)
14.0 cm (5.51 in)
10.5 cm (4.13 in)
14.0 cm (5.51 in)
5.71 cm (2.25 in)
15.8 cm (6.22 in)
16.9 cm (6.65 in) 14.5 cm (5.71 in)
0.55 cm dia (0.217 in)
58.8 cm (23.15 in) 51.04 cm (20.10 in)
0.55 cm dia (0.217 in)
1.1 cm dia. (0.433 in)
14.0 cm (5.51 in)
13.3 cm (5.24 in)
14.0 cm (5.51 in)
13.3 cm (5.24 in)
4.7 cm (1.85 in)
15.8 cm (6.22 in)
16.9 cm (6.65 in) 14.5 cm (5.71 in)
73.8 cm (29.06 in) 66.04 cm (26.0 in)
0.78 cm (0.31 in)
dimension with a 1756-PSCA chassis adapter installed, rather than a power supply
77 Step 6 - Select: a power supply for each chassis a power supply bundle if you are planning a redundant power supply system
Selecting a Power Supply
The 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. The power supply attaches to the left end of the chassis.
Description: normal input voltage input voltage range maximum real input power maximum apparent input power maximum transformer load frequency range maximum output power 1756-PA72 120V ac or 220V ac 85-265V ac 95W 240VA 238VA 47-63Hz series A: 70W @ 40 C 55W @ 60 C series B: 75W @ 60 C maximum backplane output current 1.5A @ 1.2V dc 4A @ 3.3V dc 10A @ 5V dc 2.8A @ 24V dc @60 Hz: 85V ac: 2 cycles 120V ac: 6 cycles 200V ac: 20 cycles 112 x 140 x 145 mm (4.41 x 5.51 x 5.71 in) 1.0 kg (2.5 lb) 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5 to 95% (without condensation) 144 x 137 x 175 mm (5.67 x 5.4 x 6.89 in) 1.28 kg (3.2 lb) 1.5A @ 1.2V dc 4A @ 3.3V dc 13A @ 5V dc 2.8A @ 24V dc 75W @ 60 C 95W 240VA 238VA 115W 120VA 120VA 1756-PA75 1756-PA75R 1756-PB72 24V dc 19.2-32V dc 97W na na dc series A: 70W @ 40 C 55W @ 60 C series B: 75W @ 60 C 1.5A @ 1.2V dc 4A @ 3.3V dc 10A @ 5V dc 2.8A @ 24V dc 19V dc: 20 mS 24V dc: 70 mS 1.5A @ 1.2V dc 4A @ 3.3V dc 13A @ 5V dc 2.8A @ 24V dc 75W @ 60 C 97W 110W 1756-PB75 1756-PB75R
hold up time1
dimension (H x W x D) weight operating temperature storage temperature relative humidity
112 x 140 x 145 mm (4.41 x 5.51 x 5.71 in) 1.0 kg (2.5 lb)
144 x 137 x 175 mm (5.67 x 5.4 x 6.89 in) 1.28 kg (3.2 lb)
1. The hold up time is the time between input voltage removal and dc power failure.
Redundant power supplies

The redundant power supplies are available in ac (1756-PA75R) and dc (1756-PB75R) versions. They can be mixed when used in tandem. Or you can purchase bundled systems:
Bundled Catalog Number: 1756-PAR Contains: two 1756-PA75R power supplies two 1756-CPR cables one 1756-PSCA chassis adapter module two 1756-PB75R power supplies two 1756-CPR cables one 1756-PSCA chassis adapter module
1756-PBR
78
To build a redundant power supply system, you need: two redundant power supplies one 1756-PSCA chassis adapter module 1756-CPR cables to connect the power supplies to the 1756-PSCA chassis adapter module (3ft maximum length) user-supplied annunicator wiring to connect the power supplies to the input modules, as needed
1756-PA75R or 1756-PB75R 1756-PA75R or 1756-PB75R
1756-CPR cable 1756-PSCA module
annunicator wiring 1756 input module
The 1756-PSCA chassis adapter module is a passive device designed to funnel power from redundant power supplies to the single power connector on the ControlLogix series B chassis backplane.
Power requirements and transformer sizing

The graphs that follow display backplane power load. Use the real power value to determine the amount of heat dissipation you have inside the enclosure. Use the apparent power value to estimate power cost. Use the transformer load value plus all other loads on a transformer to determine the required transformer size.
1756-PA72 1756-PA75 ac
backplane power load (Watts)
75 60 45 30 15 0 75 60 45 30 15 0 75 60 45 30 15 0
20
40
60
80
100
20
40
60
80
100
50
100
150
200
250
real power (Watts)

75 60 45 30 15 0 0 20 40 60 80 100 120
apparent power (Watts)

75 60 45 30 15 0
transformer load (VA) = real power (Watts) x 2.5

75 60 45 30 15 0
1756-PA75R ac
20
40
60
80
100
50
100
150
200
250
real power (Watts)

75 60 45 30 15 0 0 20 40 60 80 100
apparent power (Watts)

75 60 45 30 15 0 0 20
transformer load (VA) = real power (Watts) x 2.5
1756-PB72 1756-PB75 dc
1756-PB75R dc
40
60
80
100
120
real power (Watts)
real power (Watts)
79 Step 7 - Select: the appropriate bundle of RSLogix 5000 Enterprise Series software other software packages for your application
Selecting Software
Your selection of modules and network configuration determines what software packages you need to configure and program your system.
If you have: 1756 ControlLogix controller 1756-M08SE, -M02AE motion module 1756-CNB, -CNBR ControlNet communication module RSNetWorx for ControlNet (comes with RSLogix 5000 Enterprise Series software and RSNetWorx for ControlNet bundle) RSNetWorx for DeviceNet You need: RSLogix 5000 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)
1756-DNB DeviceNet communication module
1756-ENBT, -ENET Ethernet/IP communication module (set the IP address) 1756-DHRIO communication module (define the DH+ routing table) 1788-CN2FF Foundation Fieldbus linking device
RSLinx software (RSLinx Lite comes with RSLogix 5000 Enterprise Series software)
Foundation Fieldbus Configuration Software and RSLinx or RSLinx OEM software (RSLinx Lite is not sufficient) RSLinx software (RSLinx Lite comes with RSLogix 5000 Enterprise Series software) RSView32 software PanelBuilder software
1788-FFCT and 9355-WABENE or 9355-WABOEMENE 9324 series (RSLogix 5000 Enterprise Series software) 9301 series 2711-ND3 for PanelView Standard or 2711E-ND1 for PanelView Enhanced
communication card in a workstation workstation dedicated for operator interface PanelView terminal
80
Programming Software
RSLogix 5000 Enterprise Series software is designed to work with Rockwell Automations Logix Platforms and the Logix5000 family of controllers. RSLogix 5000 Enterprise Series software also includes axis configuration and programming support for motion control. RSLogix 5000 Enterprise Series functionality includes: online help, including overview, procedural, screen, and reference information and online books, including related reference manuals and user manuals in an electronic format ease of configuration, including a graphical controller organizer, I/O configuration dialogs, a motion configuration tool, and point-and-click methods of configuration sophisticated data handling, using arrays and user-defined structures, to provide the flexibility necessary for the application rather than forcing it to fit the particular memory structure as defined by the controllers data table memory easy-to-use I/O addressing methods a free-form ladder editor that lets you modify multiple rungs of logic simultaneously, as well as enter logic either from the point-and-click interface or via an ASCII entry prompt a flexible, easy-to-use function block diagram editor drag-and-drop editing and navigation to quickly move data elements from one data file to another, rungs from one subroutine or project to another, or instructions from rung to rung or function block diagram to function block diagram within a project an instruction set that includes relay ladder and function block instructions diagnostic monitoring capability, including a status display of the controller, a program verification feature, and a robust data monitor.
81
Additional utilities and tools

In addition to configuring and programming your control system, RSLogix 5000 Enterprise Series software includes:
Functionality: RSLinx software Description: The programming software includes a Lite version of RSLinx software. RSLinx software can upload tags from an RSLogix 5000 project and make them available to other software packages such as RSView32 software. RSLinx software version 2.20 lets you access tags online a controller; RSLinx software version 2.30 lets you access tags offline directly from the .ACD file. The motion configuration wizard streamlines the servo module setup process by leading you through the various parameters associated with an axis of motion. While online with a controller, you can use the built-in marker test, direction test, and servo auto-tune features to reduce your axis setup time. You can force I/O values. You can: set forces on individual bits and entire values monitor forces in the tag monitor for minimized tag, individual bits, or entire value monitor forces in the ladder editor for both bit and block instructions The import/export utility lets you develop your programs offline in a text file. If import/export an entire project, the text file (.L5K extension) contains tag definitions, data, program logic, I/O configuration information, and controller configuration information. If you import/export tags, the text file contains only tag definitions and tag comments. The translation tool converts a PLC-5 or SLC 500 import/export file (.PC5 or .SLC extension) into a complete import/export file (.L5K extension). Currently, the translation tool converts only ladder instructions. SFC and structured text files are not converted. The RSView32 TrendX provides graphical, real-time data histograms for diagnostic and monitoring functions. This feature supports trending of as many as eight separate values simultaneously. There are ActiveX faceplates for function block instructions that commonly require operator interface display so you can monitor and configure your program graphically. You can configure an open-loop autotuner built in to the PIDE function block instruction. Once configured, you can autotune the loop from the PIDE property dialog screens, from the PIDE ActiveX faceplate, or from a custom screen on an operator interface station, such as a PanelView terminal.
motion configuration wizard
force utility
import/export utility
conversion tool
RSView32 TrendX component ActiveX faceplates PIDE autotuner
82
Select the RSLogix 5000 Enterprise Series software package based on the functionality you need:
Available Features Logix5000 controllers supported Mini 9324-RLD200xxE1 CompactLogix5300 FlexLogix5400 Standard 9324-RLD300xxE1 CompactLogix5300 FlexLogix5400 ControlLogix5500 DriveLogix5700 SoftLogix5800 fully supported upload/download only available separately2 available separately3 fully supported fully supported Lite included available separately4 Lite included available separately Standard to Professional: 9324-RLD3U7xxE Standard/NetWorx 9324-RLD300NXxxE1 CompactLogix5300 FlexLogix5400 ControlLogix5500 DriveLogix5700 SoftLogix5800 fully supported upload/download only available separately2 available separately3 fully supported fully supported Lite included included Lite included available separately Standard to Professional: 9324-RLD3U7xxE Professional 9324-RLD700xxE1 CompactLogix5300 FlexLogix5400 ControlLogix5500 DriveLogix5700 SoftLogix5800 fully supported fully supported available separately3 fully supported fully supported Lite included included Professional included included na
Ladder diagram editor Function block diagram editor Loop tuner for the PIDE function block Highly-integrated motion Graphical trending DriveExecutive RSNetWorx for ControlNet and RSNetWorx for DeviceNet software RSLinx software 1756-MVI development toolkit Upgrades
fully supported upload/download only available separately2 available separately3 upload/download only na available separately available separately4 Lite included available separately Mini to Standard: 9324-RLD2U3xxE Mini to Professional 9324-RLD2U7xxE 9324-RLD200xxS 9324-RLD200xxR
RSLogix 5000 support renewal reinstate

1. 2. 3. 4. 5.
9324-RLD300xxS 9324-RLD300xxR
9324-RLD300xxS5 9324-RLD300xxR5
9324-RLD700xxS5 9324-RLD700xxR5
Replace xx in the catalog number with the appropriate language designation: EN=English, FR=French, DE=German, IT=Italian, PT=Portuguese, and ES=Spanish. Function block programming is available separately as 9324-RLDFBDxxE. The loop tuner for the PIDE function block is available separately as 9323-ATUNEENE. RSNetWorx for ControlNet and RSNetWorx for DeviceNet are available together as 9357-ANETL3. A separate support agreement is required for RSNetWorx software and for RSLinx Professional software.
RSLogix 5000 Enterprise Series software requirements

Description: personal computer software requirements Value: IBM-compatible Pentium 150 MHz or greater 200 MHz recommended Microsoft Windows NT version 4.0 with Service Pack 5 or Microsoft Windows 2000 with Service Pack 1 64 Mbytes of RAM minimum 128 Mbytes of RAM recommended 50 Mbytes of free hard disk space (or more based on application requirements) 16-color VGA graphics adapter 800 x 600 or greater resolution
RAM hard disk space video requirements
83
Protecting Your Application
Depending on what needs to be secure, RSLogix 5000 Enterprise Series software offers different security options.
Rockwell Software security server

The security server offers multiple-user, multiple-level password protection to your controller both online and offline. This option restricts access to all the routines in a controller and blocks access to all data from RSLogix 5000 Enterprise Series software. You assign passwords to allow users one of these levels: full controller access read only access code read and data read/write access RSLogix 5000 Enterprise Series software comes with a stand-alone version of the security server. A network version (9324-RSECSENE) is available separately to provide centralized management of system security.
Source protection
The source protection functionality within RSLogix 5000 Enterprise Series software offers protection for your intellectual property both online and offline. You can restrict individual routines from viewing, editing, printing, and exporting. This option does not secure the data associated with the protected routines.
84
Network Configuration Software
RSNetWorx software for ControlNet (9357-CNETL3) and RSNetWorx software for DeviceNet (9357-DNETL3) are the configuration and scheduling tools for your ControlNet or DeviceNet networks. RSNetWorx software lets you create a graphical representation of your network configuration and configure the parameters that define your network. RSNetWorx software also performs a scheduling function for all network components. For example, each network scanner has its own scan list and memory mapping. This information is stored in the configurations files in the scanner. When changes are made to the scan lists, RSNetWorx 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 the ControlNet networks in your ControlLogix system.
ControlNET
ControlNET
ControlNET
ControlNET
A#24
OK A
A#24
OK A
A#24
OK A
A#24
OK A
PLC-5/40C
ControlNET
A#24
OK A
System requirements
Description: personal computer operating system Value: IBM-compatible 120MHz minimum (Pentium recommended) Microsoft Windows 95, Windows 98, or Windows NT version 4.0 with Service Pack 2 or greater, or Microsoft Windows 2000 with Service Pack 1 or greater 32 Mbytes of RAM minimum 48 Mbytes or more of RAM recommended 14 Mbytes of free hard disk space (or more based on application requirements) 16-color VGA graphics adapter 640 x 480 or greater resolution (256-color 800 x 600 minimum for optimal resolution)
RAM hard disk space video requirements
85
Implementing a DCS Control System Using the Logix Architecture

The ProcessLogix Process Control System is a fully-integrated, server-based, process control solution designed to provide process engineers with the features and functions they require from a state-of-the-art distributed control system (DCS). And since the ProcessLogix system is based on economical ControlLogix and ControlNet components, it is also a cost-effective solution.
Meeting Your Process Control Requirements
Because the ProcessLogix system comes with an extensive library of functions and has the ability to communicate with ControlLogix controllers, it can help automate a broad range of batch and continuous process applications across several industries, including consumer products, pulp and paper, petroleum, metals, and pharmaceuticals. ControlNet communications provide the primary link between ProcessLogix servers, controllers, and I/O. Ethernet/IP communications support connections between operator workstations and ProcessLogix servers.
operator stations Ethernet/IP network ProcessLogix servers ControlNet network ProcessLogix controllers
ControlNet network ProcessLogix I/O modules
86
Developing a ProcessLogix Application
The ProcessLogix development environment offers control functions that you access and link using a function block editor. A library of templates, called function blocks, provide the logic for continuous, logic, sequence, and basic batch functions. The ProcessLogix system supports: regulatory, computational, and compensation requirements with continuous functions boolean, selection, and comparison requirements with logic functions action handling and conditional logic with sequential functions, including sequential function charts basic batch requirements with Batch Level 1 and 2 type control functions The ProcessLogix system software includes configuration and runtime components. Once you develop and test your application, the ProcessLogix system provides operators with smart displays, including operational procedures and built-in documentation. You can also implement a comprehensive set of alarms to help provide timely notification of any deviation in your process. And while it controls your process, the ProcessLogix system is constantly accumulating data in the ProcessLogix system server, which you can analyze using the systems trending and historian capabilities. Or you can export the data to external programs or systems for more detailed analysis.
87
Monitoring and Controlling Automation Machines and Processes

Integrating HMI Products
RSView32 software is an integrated, component-based HMI for monitoring and controlling automation machines and processes. RSView32 offers preferred compatibility to the Logix family of products. Use RSView32 software with RSLinx software to capture, control, and convey plant floor data. With RSView32 software, build your own customized suite, choosing only those products that best serve the needs of your unique applications. For example, select RSLogix 5000 ladder tags right from within RSView32. You can also share data with Microsoft products. RSView32 tag configuration, alarm configuration, and logged data are all ODBC compliant. Log data directly to an ODBC data source such as Microsoft SQL Server, Oracle, or SyBase, and graphically view the data in a trend. RSView32 expands your view with open technologies that provide unprecedented connectivity to other Rockwell Software products, Microsoft products, and third-party applications.
Integrating the ViewAnyWare Strategy
The ViewAnyWare strategy, together with Logix for control and NetLinx Open Architecture for communication, make up Rockwell Automations Integrated Architecture strategy. Common design-time environment, application reuse, and scalable architecture across the entire operator interface continuum are clearly competitive differentiators of the ViewAnyWare strategy. The ViewAnyWare strategy combines Rockwell Automations expertise in Allen-Bradley electronic operator interface and industrialized PC hardware with Rockwell Softwares supervisory control software. The result is a common development environment across platforms, offering faster development and implementation, better productivity and flexibility, and overall lower costs. This means that solutions support an operator interface that closely matches the application, offer integration capabilities for lower cost and better performance, provide backward compatibility and forward-friendly features, and act as a single source of accountability for hardware, software, and networking portions of the application.
88
Current ViewAnyWare Products Current ViewAnyWare products include:

RSView Machine Edition Rockwell Software has developed the RSView Enterprise Series, a new line of HMI software products that supports the ViewAnyWare strategy. The first product release from this new series is RSView Machine Edition. RSView Machine Edition is a machine level HMI product that supports both open and embedded operator interface solutions to monitor and control individual machines or small processes. It enables a consistent operator interface across multiple platforms, including Microsoft Windows CE and Windows 2000 solutions.
Components of RSView Machine Edition include: RSView Studio (9701-VWSTMENE) lets you create displays that give a visual representation of your process and lets users interact with the process. Designed for the Windows 2000 operating system, RSView Studio provides an easy-to-use development environment to simplify application design and reduce development time. RSView ME Station (9701-VWMR075AENE) runs projects developed with RSView Studio. Flexible runtime choices include Allen-Bradley RAC6182 Windows CE computers and Windows 2000 platforms.
RAC6182 Windows CE Computer Designed exclusively for Microsoft Windows CE, the RAC6182 family of computers is ideal for OEMs and end-users developing HMI solutions for the factory floor. The RAC6182 combines the Windows CE platform with a rugged, full-featured industrial computer to deliver a computing solution that supports HMI, soft control, programming, information management, and remote terminal applications.
The RAC6182 is a family of full-featured industrial computers with 12-inch TFT or 7.7-inch STN LCD flat panel displays and non-display options. The non-display RAC6182 computer can perform the same tasks as the 12- and 7.7-inch versions using an external monitor, touch screen, and keyboard. The RAC6182 also can be used as a stand-alone control or data collection engine.
Future Products
Future ViewAnyWare products will include: RSView Supervisory Edition (RSView SE), an HMI for supervisory-level monitoring and control applications. It has a distributed and scalable architecture that supports multi-server/multi-client applications. PanelView Plus, the next generation of PanelView products. The PanelView Plus 700 has a 6.4" VGA flat panel active matrix display in keypad and touch versions. The PanelView Plus 1250 has a 12.1" SVGA flat panel active matrix display, with keypad and touch versions.
89
Summary
Use a spreadsheet to record the amount and type of devices your ControlLogix system needs. For example, this sample system:
ControlNet network
Panel A chassis 1
Panel A chassis 2
Panel A chassis 3
Universal Remote I/O network PanelView
could result in this spreadsheet:

Device: 120V ac digital inputs 120V ac digital outputs 24V dc digital inputs 24V dc digital outputs contact digital outputs 4-20mA analog inputs 0-10V dc analog inputs 4-20mA analog outputs analog servo module PanelView terminal ControlNet communication module Remote I/O communication module Location: A A A A A A A A A A A A Number of points needed: 73 25 43 17 11 7 2 4 2 axis na na na Catalog number: 1756-IA8D 1756-OA8D 1756-IB16D 1756-OB16D 1756-OX8I 1756-IF6I 1756-IF6I 1756-OF6CI 1756-M02AE 2711 series 1756-CNB 1756-DHRIO I/O points per module: 8 8 16 16 8 6 6 6 na na na na Number of modules: 10 4 3 2 2 2 0 1 1 na 3 1
Location A subtotal 29
90
As you select devices for your ControlLogix system, keep in mind:
Step:
Remember to select: the appropriate I/O modules - some modules offer additional diagnostic features, electronic fusing, or individually isolated inputs or outputs either a remote terminal block (RTB) or 1492 wiring system for each I/O module the appropriate motion module(s) the associated cable(s), based on the drives youll be connecting to the motion module(s) a remote terminal block (RTB) if you are using a 1756-M02AE servo module the appropriate communication module(s) the associated cables and network equipment sufficient modules and cables if you are planning a redundant ControlNet system Some networks have companion documents to help in selecting appropriate network equipment. See your Rockwell Automation representative for information.
Selecting I/O devices
Selecting motion modules
Selecting communication modules
Selecting a controller
a controller with enough memory for your application, with room to spare for additional growth 1756-BATM battery module for a 1756-L55M16 controller replacement batteries - the controller comes with one 1756-BA1 battery 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 bundle of RSLogix 5000 Enterprise Series software to program your controller
5 6
Selecting a chassis
Selecting power supplies
Selecting software
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. After you make your module selections, see the Master Price List, publication number CIG-3.0 to determine pricing.
ControlLogix, Logix5550, FlexLogix, CompactLogix, DriveLogix, ProcessLogix, PowerFlex, SoftLogix5800, PLC-5, PLC-3, PLC-2, SLC, DH+, Allen-Bradley, RSLogix, RSLogix 5000 Enterprise Series, RSNetWorx, and Rockwell Software 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 NT, and Windows 2000 are registered trademarks of Microsoft in the U.S. and other countries.
0
Chassis: 400mA maximum 1756-PA/PB72 10,000mA 1756-PA/PB75 13,000mA 1756-PA/PB75R 13,000mA Catalog Number: Backplane current 3.3V (amps): Backplane current 5.1V (amps): maximums:
10
11
12
Module power (watts):
13
14
15
16
Backplane current 24V (amps): 2800mA maximum
I/O termination: 20-pin
Connections:
36-pin
Direct
Rack
rack power 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
totals:
Publication 1756-SG001D-EN-P November 2001

Supersedes 1756-SG001C-EN-E August 2001 and 1756-SG001B-EN-P June 2001
PN 957603-84
Copyright 2001 Rockwell Automation. All rights reserved. Printed in USA

Controllogix: Selection Guide

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Controllogix: Selection Guide

Transféré par

Droits d'auteur :

Formats disponibles

ControlLogix

Introducing ControlLogix for High Performance Control

Take Control with Logix

Selecting a ControlLogix System

Selecting a ControlLogix System

1756 I/O modules in the same chassis as the ControlLogix controller

1756-SG001D-EN-P November 2001

Selecting a ControlLogix System

communication interface modules in the same chassis as the ControlLogix controller

remote I/O modules

1756 I/O modules in the same chassis as the ControlLogix controller

Universal Remote I/O link

EtherNet/IP link ControlNet link DH+ link

computers other controllers

1756-SG001D-EN-P November 2001

Selecting a ControlLogix System

Layout the System

Universal Remote I/O PanelView

Universal Remote I/O PanelView

1756-SG001D-EN-P November 2001

Selecting a ControlLogix System

Laying out a redundant system

ControlLogix chassis with 1756-CNBR module

1756-CPR cable ControlLogix chassis with 1756-PSCA module

annunicator wiring 1756 input module

1756-SG001D-EN-P November 2001

Selecting a ControlLogix System

Motion overview ...........................................page 27 Motion specifications ....................................page 28

Power supply specifications ..........................page 77

1756-SG001D-EN-P November 2001

Selecting ControlLogix I/O Modules

Logix5500 Output Modules Controllers

Commonly Shared Data

When planning I/O communications, consider:

The ControlLogix family of I/O modules includes:

1756-SG001D-EN-P November 2001

1756 Digital I/O Modules

Digital ac input modules

1756-SG001D-EN-P November 2001

Digital ac output modules

5A @ 30C 4A @ 60C 5A @ 30C 4A @ 60C

Digital dc input modules

125V dc source or sink 12/24V dc source 12/24V dc source

1756-SG001D-EN-P November 2001

Digital dc output modules

16A @ 55C 10A @ 60C 8A @ 30C 4A @ 60C 8A @ 60C

2A @ 30C 1A @ 60C 1A @ 60C

12/24V dc source 12/24V dc source or sink

32 (2 sets of 16) 8 (2 sets of 4) 8 (individually isolated) 16 (2 sets of 8)

12/24V dc source 48V dc source

16A @ 50C 10A @ 60C 8A @ 60C

120V dc source or sink 12/24V dc sink

Digital contact output modules

1 set of form-C contacts for each output

1756-SG001D-EN-P November 2001

1756 Analog I/O Modules

Catalog number: 1756-IF8

Number of inputs: 8 single-ended, 4 differential, or 2 high-speed differential 6 isolated

16 single-ended, 8 differential, or 4 high-speed differential 4 high-speed differential (<1ms update)

2 high-speed voltage or current (<1ms update)

Inputs: 0-21mA Outputs: 0-21mA

1756-TBNH 1756-TBSH (20 pins)