0% found this document useful (0 votes)

23 views96 pages

1756 sg001f en P

The ControlLogix Selection Guide provides an overview of various Logix controllers, including their characteristics, memory capacities, communication options, and redundancy features. It outlines the modular design of the ControlLogix system, which supports multiple programming languages and integrates with various I/O modules and communication networks. The guide also includes a checklist for selecting components, such as I/O devices, motion control requirements, and software needed for system configuration.

Uploaded by

hamdy nabawy

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

23 views96 pages

1756 sg001f en P

Uploaded by

hamdy nabawy

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 96

ControlLogix

Selection
Guide
1756-L55, 1756-L61, 1756-L62,
1756-L63
Logix Controllers Comparison
PowerFlex 700S® with
Common Characteristics 1756 ControlLogix™ 1769 CompactLogix™ 1789 SoftLogix5800™ 1794 FlexLogix™ DriveLogix
! 1769-L35E: 8 tasks (only 1
controller tasks: continuous)
! 32 tasks (only 1 continuous) ! 32 tasks (only 1 continuous) ! 8 tasks (only 1 continuous) ! 8 tasks (only 1 continuous)
! continuous ! 1769-L20, -L30: 4 tasks (only
! event tasks: supports all event ! event tasks: supports all event ! event tasks: supports EVENT ! event tasks: supports axis and
! periodic 1 continuous)
triggers triggers instruction motion event triggers
! event ! event tasks: supports EVENT
instruction
1756-L55M12 750 Kbytes
1756-L55M13 1.5 Mbytes
1789-L10 2 Mbytes
1756-L55M14 3.5 Mbytes
3 slots
1756-L55M16 7.5 Mbytes
1769-L20 64 Kbytes no motion 256 Kbytes
1756-L55M22 750 Kbytes 1794-L33 64 Kbytes
user memory 1769-L30 256 Kbytes 1789-L30 64 Mbytes 768 Kbytes with memory
1756-L55M23 1. 5 Mbytes 1794-L34 512 Kbytes
1769-L35E 1.5 Mbytes 5 slots expansion
1756-L55M24 3.5Mbytes
1789-L60 64 Mbytes
1756-L61 2 Mbytes
16 slots
1756-L62 4 Mbytes
1756-L63 8 Mbytes
1756-L55M12 none
1756-L55M13 none
1756-L55M14 none
1756-L55M16 none
1769-L20 yes
1756-L55M22 yes 1794-L33 yes
nonvolatile user memory 1769-L30 yes none yes (expansion memory)
1756-L55M23 yes 1794-L34 yes✶
1769-L35E CompactFlash
1756-L55M24 yes
1756-L61 CompactFlash
1756-L62 CompactFlash
1756-L63 CompactFlash
! 1769-L20 has 1 RS-232 serial
port (DF1 or ASCII)
! 1769-L30 has 2 RS-232 ports ! 1 port RS-232 serial ! 1 port RS-232 serial
1 port RS- 232 serial (one DF1 only, other DF1 or (DF1 or ASCII) (DF1 or ASCII)
built-in communication ports depends on personal computer
(DF1 or ASCII) ASCII) ! 2 slots for 1788 ! 1 slot for 1788
! 1769-L35E has 1 EtherNet/IP communication cards communication cards
port and 1 RS-232 serial port
(DF1 or ASCII)
EtherNet/IP
communication options(these ControlNet
EtherNet/IP EtherNet/IP
options have specific DeviceNet EtherNet/IP EtherNet/IP
ControlNet ControlNet
products and profiles for their Data Highway Plus DeviceNet ControlNet
DeviceNet DeviceNet
platform - other options are Universal Remote I/ O serial DeviceNet
serial serial
available via 3rd party products serial DH-485 serial
DH-485 DH-485
and generic profiles) DH-485
SynchLink
controller via ControlNet
controller via DeviceNet
redundancy ControlNet media none ControlNet media ControlNet media
ControlNet media
power supplies
1794 FLEX I/O 1794 FLEX I/O
native I/O 1756 ControlLogix I/O 1769 Compact I/O none
1797 FLEX Ex I/O 1797 FLEX Ex I/O
SERCOS interface
SERCOS interface 1 full servo
motion support analog interface not applicable not applicable
analog interface 1 feedback axis
hydraulic interface
mounting and/or installation panel mount panel mount
1756 chassis none embedded in PowerFlex 700S
options DIN rail DIN rail
! relay ladder
! structured text
! relay ladder ! relay ladder ! relay ladder ! relay ladder
! function block
! structured text ! structured text ! structured text ! structured text
programming languages ! sequential function chart
! function block ! function block ! function block ! function block
! external routines (Windows
! sequential function chart ! sequential function chart ! sequential function chart ! sequential function chart
DLLs developed using
C/C++)

✶Must have a series B controller with firmware revision 11 or greater.

Logix5000™ Rockwell Automation Logix5000 Platforms provide a single integrated control

architecture for discrete, drives, motion, and process control.
Platforms
The Logix platforms provide a common control engine, programming software
environment, and communication support across multiple hardware platforms. All
Logix controllers operate with a multitasking, multiprocessing operating system and
support the same set of instructions in multiple programming languages. One RSLogix
5000 programming software package programs all Logix controllers. And all Logix
controllers incorporate the NetLinx architecture to communicate via EtherNet/IP,
ControlNet, and DeviceNet networks.

ControlLogix System Overview page 2

Layout the System page 3
Selecting ControlLogix I/O Modules page 7
Selecting Motion Control Requirements page 25
Selecting Network Communications page 33
Selecting Controllers page 51
Selecting Chassis page 69
Selecting Power Supplies page 73
Selecting Software page 77
Integrating the ViewAnyWare Strategy page 85
Controlling Automation Machines and Processes page 87
Summary page 89

1756-SG001F-EN-P — June 2003

ControlLogix The ControlLogix system provides sequential, process, motion, and drive control
together with communications and state-of-the-art I/O in a small, cost-competitive
System Overview package. The system is modular, so you can design, build, and modify it efficiently -
What’s New in Version 12: with significant savings in training and engineering. A simple ControlLogix system
1756-L61 and 1756-L62 controllers consists of a stand-alone controller and I/O modules in a single chassis.
1756-IF6CIS, 1756-IT6I2, 1756-IB32/B,
1756-OV32E, 1756-OB16IS, and
1756-HYD02 modules
event-based tasks

Or use the ControlLogix system as a gateway. Include the communication modules you
need for connectivity to other networks. For this use, a controller is not required. The
ControlLogix Gateway integrates into existing PLC-based systems so that users with
existing networks can send or receive messages to or from other networks. For a
more robust system, use:

multiple controllers in a single chassis

multiple controllers joined across networks
I/O in multiple platforms that are distributed in many locations and connected
over multiple I/O links

1756-SG001F-EN-P — June 2003

Layout the System Lay out the system by determining the network configuration and the placement of
components in each location. Decide at this time whether each location will have its
own controller.

Place each controller’s I/O on an isolated network to maximize the performance and
to more easily accommodate future network or system configuration changes. If you
plan to share I/O, make sure the I/O is on a network that each controller can access.

Assume that Location A and Location B both require a controller and its own I/O.
Both controllers interact with time critical information. Panel C does not need a
controller and can be a gateway.

For a ControlLogix controller to control I/O modules, both the controller and the I/O
modules must be directly attached to the same network.
I/O Location Controller in Panel A, Chassis 1 Controller in Panel B, Chassis 1
Panel A, Chassis 1 yes yes
Panel A, Chassis 2 yes no
Panel A, Chassis 3 yes no
Panel B, Chassis 1 yes yes
Panel B, Chassis 2 no yes
Panel C, Chassis 1 yes yes

Evaluate what communications need to occur between controllers. If there is sporadic

information that is not time critical, use a message-based network such as an
EtherNet/IP (the information portion), Data Highway Plus, or the unscheduled portion
of a ControlNet network. If the information is time critical, such as
produced/consumed tags between controllers, use a ControlNet or EtherNet/IP
network.

1756-SG001F-EN-P — June 2003

Laying out a redundant system

The ControlLogix environment offers different levels of redundancy that you can
design into your system. These systems require additional hardware, so plan
accordingly. You can design redundant:
media for ControlNet
power supplies
1756-L55 controller chassis

Redundant ControlNet media

Requires:
1756-CNBR ControlNet modules
two identical ControlNet links

Redundant power supplies

Requires:
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 adapter
user-supplied annunciator wiring to connect the power supplies to the input
modules, if needed

1756-SG001F-EN-P — June 2003

Redundant controller chassis

Requires:
one 1756-L55 controller in each redundant chassis (contact your Rockwell
Automation representative for the specific firmware revision)
at least one, but no more than five, 1756-CNB(R) series D, version 5.23 (or
greater) communication modules in each redundant chassis
one 1757-SRM module in each redundant chassis
no other I/O or communication modules can be in the redundant chassis

All I/O must be remote from the redundant controllers. ControlLogix redundancy
works with remote 1756 I/O, FLEX I/O, drives, operator interfaces, or any other
devices that can communicate with a ControlLogix controller over a ControlNet link.
To connect to other networks, bridge through another ControlLogix chassis (not one
of the redundant controller chassis)

1756-SG001F-EN-P — June 2003

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 See
1 Select I/O devices

Use a spreadsheet to record: I/O module specifications page 7

location of the device Wiring systems page 14
number of points needed Placing I/O modules page 23
appropriate catalog number How I/O modules operate page 24
number of points available per module
number of modules
Motion overview page 25
2 Select motion control and drives requirements
SERCOS interface modules page 27
Analog interface module page 29
To the I/O spreadsheet, add the number of required motion modules.
Hydraulic interface module page 31
Network overview page 33
EtherNet/IP specifications page 35
ControlNet specifications page 37
DeviceNet specifications page 40
DH+/RIO specifications page 41
3 Select communication modules
Fieldbus specifications page 42
Serial specifications page 43
To the I/O spreadsheet, add the number of required communication modules.
DH-485 specifications page 44
SynchLink specifications page 45
AutoMax specifications page 48
Accessing the controller remotely page 49
Connecting to other networks page 50
4 Select controllers
Controller specifications page 51
Determining memory requirements page 53
Select the appropriate controller based on:
Controlling devices page 55
required controller tasks
Communicating with other devices page 56
number of I/O points needed
Communicating with drives page 57
number of communication cards needed
Connection information page 61
required controller memory
5 Select chassis
Chassis specifications page 69
Determine the number of chassis you need.
6 Select power supplies and ensure sufficient power
Power supply specifications page 73
On the module spreadsheet, calculate power requirements.
Available software products page 77
7 Select software Programming software page 78
Communication software page 80
Determine the software products you need to configure and program your application.Based on the Network configuration software page 81
system design, determine the software products you need to configure and program your Emulation software page 82
application. Training software page 83
Visualization software page 85

1756-SG001F-EN-P — June 2003

Step 1 - Select:
I/O modules - some modules have Selecting ControlLogix
diagnostic features, electronic fusing, or
individually isolated inputs/outputs I/O Modules
a remote terminal block (RTB) or
wiring system for each I/O module
The ControlLogix architecture provides a wide range of input and output modules to
PanelConnect modules and cables if span many applications, from high-speed discrete to process control. The
connecting input modules to sensors
ControlLogix architecture uses producer/consumer technology, which allows input
information and output status to be shared among multiple ControlLogix controllers.

Each ControlLogix I/O module mounts in a ControlLogix chassis and requires either
a removable terminal block (RTB) or a 1492 interface module (IFM) to connect all
field-side wiring. RTBs and IFMs are not included with the I/O modules. They must be
ordered separately.
The ControlLogix family of I/O modules includes:
1756 digital I/O modules
1756 analog I/O modules
1756 specialty I/O modules
1492 wiring systems

1756-SG001F-EN-P — June 2003

1756 Digital I/O The 1756 digital I/O modules support:

wide variety of voltage interface capabilities
Modules
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 types of digital I/O modules:

Digital I/O Type Description

These modules provide diagnostic features to the point level. These modules have a “D” at the end of
diagnostic
the catalog number.
These modules have internal electronic fusing to prevent too much current from flowing through the
electronic fusing
module. These modules have an “E” at the end of the catalog number.
These modules have individually isolated inputs or outputs.
individually isolated
These modules have an “I” at the end of the catalog number.

Digital ac input modules

1756-SG001F-EN-P — June 2003

Digital ac output modules

Digital dc input modules

Removable
Voltage, On- Input Delay Current, On- Current, On- Current, Off- Terminal Backplane Backplane Power
Number of State Input, Operating Time, ON to State Input, State Input, State Input, Block Current (mA) Current (mA) Dissipation,
Cat. No. Inputs Nom. Voltage OFF Min. Max. Max. Housing at 5V at 24V Max.
2 ms hardware
12/24V dc + filter time 2.0mA @ 10V 10mA @ 31.2V 1756-TBNH
1756-IB16 16 10...31.2V dc 1.5mA 100 2 5.1W @ 60°C
sink (0, 1, 2, 9, or dc dc 1756-TBSH
18 ms)
4 ms hardware
16 12/24V dc + filter time 13mA @ 30V 1.5mA per 1756-TBCH
1756-IB16D 10...30V dc 2mA @ 10V dc 150 3 5.8W @ 60°C
diagnostic sink (0, 1, 2, 9, or dc Point 1756-TBS6H
18 ms)
4 ms hardware
16
12/24V dc + filter time 10mA @ 30 V 1756-TBCH
1756-IB16I individually 10...30V dc 2mA @ 10V dc 1.5mA 100 3 5W @ 60°C
sink/source (0, 1, 2, 9, or dc 1756-TBS6H
isolated
18 ms)
2 ms hardware
12/24V dc + filter time 1756-TBCH
1756-IB32 32 10...31.2V dc 5.5mA 2.mA 1.5mA 150 2 4.5W @ 60°C
sink (0, 1, 2, 9, or 1756-TBS6H
18 ms)
4 ms hardware
48V dc + filter time 1756-TBNH
1756-IC16 16 30...60V dc 7mA @ 60V dc 2mA @ 30V dc 1.5mA 100 3 5.2W @ 60°C
sink (0, 1, 2, 9, or 1756-TBSH
18 ms)
.25 ms
hardware +
5V dc 1756-TBNH
1756-IG16 16 4.5...5.5V dc filter time (0,   4.1 mA 110 2 1.4W @ 60°C
TTL source 1756-TBSH
1, 2, 9, or 18
ms)
6 ms hardware
16
125V dc + filter time 1 mA @ 90V 3 mA @ 146V 1756-TBCH
1756-IH16I individually 90...146V dc 0.8 mA 125 3 5 W @ 60 °C
sink/source (0, 1, 2, 9, or dc dc 1756-TBS6H
isolated
18 ms)
2 ms hardware
12/24V dc + filter time 2.0mA @ 10V 10mA @ 30V 1756-TBNH
1756-IV16 16 10...30V dc 1.5mA 110 2 5.41W @ 60°C
source (0, 1, 2, 9, or dc dc 1756-TBSH
18 ms)
2 ms hardware
12/24V dc + filter time 3.5mA @ 30V 1756-TBCH
1756-IV32 32 10...30V dc 2mA @ 10V dc 1.5mA 120 2 4.1W @ 60°C
source (0, 1, 2, 9, or dc 1756-TBS6H
18 ms)

1756-SG001F-EN-P — June 2003

Digital dc output modules

Output Current Output Current Removable Backplane Backplane Power
Number of Voltage Operating Rating, per Rating, per Terminal Block Current (mA) at Current (mA) at Dissipation,
Cat. No. Outputs Category Voltage Point, Max. Module, Max. Housing 5V 24V Max.
12/24V dc 1756-TBNH
1756-OB8 8 10...30V dc 2.0A @ 60°C 8.0A @ 60°C 165 2 2.5 W @ 60°C
source 1756-TBSH
8
electronically 16.0A @ 55°C
12/24V dc 1756-TBCH
1756-OB8EI fused, 10...30V dc 2A @ 60°C (Linear derating) 250 2 4.7W @ 60°C
sink/source 1756-TBS6H
individually 10.0A @ 60°C
isolated
2A @ 30°C 8A @ 30°C
16 24V dc (Linear derating) (Linear derating) 1756-TBCH
1756-OB16D 19.2...30V dc 250 140 3.3W @ 60°C
diagnostic source 1A @ 60°C 4A @ 60°C 1756-TBS6H
(Linear derating) (Linear derating)
16
12/24V dc 1756-TBNH
1756-OB16E electronically 10...31.2V dc 1A @ 60°C 8A @ 60°C 250 2 4.1W @ 60°C
source 1756-TBSH
fused
2A @ 30°C 8A @ 30°C
16
12/24V dc (Linear derating) (Linear derating) 1756-TBCH
1756-OB16I individually 10...30V dc 350 3 3.6W @ 60°C
sink/source 1A @ 60°C 4A @ 60°C 1756-TBS6H
isolated
(Linear derating) (Linear derating)
16
2A @ 30°C 8A @ 30°C (linear
individually
12/24V dc (Linear derating) derating) 1756-TBCH
1756-OB16IS isolated; 10...30V dc 350 2.5 3.6W @ 60°C
sink/source 1A @ 60°C 4A @ 60°C (linear 1756-TBS6H
8
(Linear derating) derating)
scheduled
0.5A @ 50°C 16A @ 50°C
12/24V dc 1756-TBCH
1756-OB32 32 10...31.2V dc (Linear derating) (Linear derating) 300 2 4.8W @ 60°C
source 1756-TBS6H
0.35A @ 60°C 10A @ 60°C
48V dc 1756-TBNH
1756-OC8 8 30...60V dc 2.0A @ 60°C 8.0A @ 60°C 165 2 4.9W @ 60°C
source 1756-TBSH
5V dc 1756-TBNH
1756-OG16 16 4.5...5.5V dc 24mA @ 60°C 384mA @ 60°C 210 2.0 1.5W @ 60°C
TTL 1756-TBSH
8
120V dc 1756-TBCH
1756-OH8I individually 90...146V dc 2A @ 60°C 8A @ 60°C 250 2.0 1.12W @ 60°C
sink/source 1756-TBS6H
isolated
16
12/24V dc 1756-TBNH
1756-OV16E electronically 10...30V dc 1A @ 60°C 8A @ 60°C 210 2.0 6.72W @ 60°C
sink 1756-TBSH
fused
32 0.5A @ 50°C 16A @ 50°C
12/24V dc 1756-TBCH
1756-OV32E electronically 10...30V dc (Linear derating) (Linear derating) 390 2.0 5.88W @ 60°C
sink 1756-TBS6H
fused 0.35A @ 60°C 10A @ 60°C

Digital contact output modules

Output Delay Removable Backplane Backplane Power
Number of Time, ON to OFF, Type of Contact Operating Terminal Block Current (mA) at Current (mA) at Dissipation,
Cat. No. Outputs Max. Output Voltage Output Current Housing 5V 24V Max.
2A @ 125/240V ac
16
10...265V ac 2A @ 5-30V dc 1756-TBCH
1756-OW16I individually 10 ms 16 N.O. 150 150 4.5 W @ 60 °C
5...150V dc 0.5A @ 48V dc 1756-TBS6H
isolated
0.25A @ 125V dc
2A @ 125/240V ac
8 1 set of form-C
10...265V ac 2A @ 5-30V dc 1756-TBCH
1756-OX8I individually 13 ms contacts for each 100 100 3.1 W @ 60 °C
5...150V dc 0.5A @ 48V dc 1756-TBS6H
isolated output
0.25A @ 125V dc

1756-SG001F-EN-P — June 2003

1756 Analog I/O The 1756 analog I/O modules support:

on-board data alarming
Modules scaling to engineering units
real-time channel sampling
IEEE 32-bit floating point or 16-bit integer data formats

Removable Backplane Backplane

Number of Sensors Terminal Block Current (mA) at Current (mA) at Power
Cat. No. Number of Inputs Outputs Input Resolution Supported Housing 5V 24V Dissipation, Max.
8 single-ended,
±10.25V
4 differential, or 1756-TBCH 1.73W - Voltage
1756-IF8 — 0...5.125V — 150 40
2 high-speed 1756-TBS6H 2.33W - Current
0...10.25V
differential
6 isolated, 1756-TBNH
1756-IF6CIS  0...21mA Range  250 275 5.1W
current sourcing 1756-TBSH
±10.5V
1756-TBNH 3.7W - Voltage
1756-IF6I 6 isolated — 0...5.25V — 250 100
1756-TBSH 4.3W - Current
0...10.5V
16 single-ended,
±10.25V
8 differential, or 1756-TBCH 2.3W - Voltage
1756-IF16 — 0...5.125V — 150 65
4 high-speed 1756-TBS6H 3.9W - Current
0...10.25V
differential
Inputs
±10.5V
4 high-speed, 0...5.25V
2 high-speed voltage 1756-TBCH 4.3W - Voltage
1756-IF4FXOF2F sub-millisecond, 0...10.5V — 375 100
or current 1756-TBS6H 4.7W - Current
differential
Outputs
±10.5V
Resistance 4…4020
100, 200, 500, Ω
1000Ω Platinum, 100, 200, 500, 1000
alpha=385 Ω Platinum, alpha =
100, 200, 500, 385
1000Ω Platinum, 100, 200, 500, 1000
alpha=3916 Ω Platinum, alpha = 1756-TBNH
1756-IR6I 6 isolated RTD — 250 125 4.3 W
120Ω Nickel, 3916 1756-TBSH
alpha=672 120 Ω Nickel, alpha
100, 120, 200, = 672
500Ω Nickel, 100, 120, 200, 500
alpah=618 Ω Nickel, alpha =
10Ω Copper 618
10 Ω Copper
B, E, J, K, R, S, T, N,
6 isolated
-12 mV... +78 mV C 1756-TBNH
1756-IT6I thermocouple — 250 125 4.3 W
-12 mV... +38 mV Linearization based 1756-TBSH
1 CJC
on ITS-90
6 isolated
-12 mV... +78 mV B, E, J, K, R, S, T, N, 1756-TBNH
1756-IT6I2 thermocouple  250 125 4.3 W
-12 mV... +38 mV C, L, D 1756-TBSH
2 CJC
1756-TBNH 3.25W - 4 channel
1756-OF4 — 4 voltage or current — 150 120
1756-TBSH current
5.5W (0…550Ω
1756-TBNH loads)
1756-OF6CI — 6 isolated — — 250 300
1756-TBSH 6.1W (551…1000Ω
loads)
1756-TBNH
1756-OF6VI — 6 isolated — — 250 175 4.85W
1756-TBSH
1756-TBNH 4.92W - 4 channel
1756-OF8 — 8 voltage or current — — 150 210
1756-TBSH current

1756-SG001F-EN-P — June 2003

1756 Specialty I/O 1756-CFM configurable flow meter

Modules 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 and 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

Number of Inputs per Voltage, Flowmeter Removable Terminal Backplane Current Backplane Current Power Dissipation,
Cat. No. Mode of Operation Channel Input Block Housing (mA) at 5V (mA) at 24V Max.
± 30V - Selectable input
thresholds of 50mV, 1.3V
& 4V:
± 30Vpeak unterminated
Totalizer fill and prover 2 – Flowmeter (F) Input open circuit voltage –
High-Resolution 100KHz – used for all modes Magnetic Pickup
1756-TBNH
1756-CFM max 2 – Gate Input – used in TTL Compatible – Input 300 6 6W @ 60°C
1756-TBSH
Frequency 0.0005Hz Totalizer Mode for Voltage greater than 1.3V
resolution Prover/Store Count DC is Logic 1 and - 0.7V
dc…1.3V dc is Logic 0
12…24V dc powered
preamp output - 4V dc
threshold

1756-SG001F-EN-P — June 2003

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.
Removable Backplane Backplane Power
Mode of Number of Inputs per Number of Terminal Block Current (mA) at Current (mA) at Dissipation,
Cat. No. Operation Counters Counter Count Range Outputs Housing 5V 24V Max.
counter 1MHz max
rate measurement
500KHz max
encoder 250KHz 3 (A, B, Z for 1756-TBCH
1756-HSC 2 0…16, 777, 214 4 300 3 5.6 W @ 60°C
max Gate/Reset) 1756-TBS6H
debounce filter
70Hz max

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.

Removable Terminal Backplane Current Backplane Current Power Dissipation,

Cat. No. Mode of Operation Number of Inputs Number of Outputs Block Housing (mA) at 5V (mA) at 24V Max.
requires 3 contiguous Requires 3 RTBs
25.7W @ 30°C
1756-PLS slots in chassis 16 16 1756-TBNH or 1756- 1000 125
21.3W @ 60°C
TBSH

1756-SG001F-EN-P — June 2003

1756 Removable 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.
Terminal Blocks The type of module determines which RTB you need. You choose screw-clamp or
spring-clamp RTBs.

RTBs are not shipped with I/O modules. You must order them separately. The
standard housing on the front of the wiring arm is not deep enough for 14 AWG
wiring. If you plan to use 14 AWG wiring, also order the extended housing.

Cat. No. Description Weight

1756-TBNH screw-clamp with 20-pin connection 0.1 kg (0.3 lb)
1756-TBSH spring-clamp with 20-pin connection 0.1 kg (0.3 lb)
1756-TBCH screw-clamp with 36-pin connection 0.1 kg (0.3 lb)
1756-TBS6H spring-clamp with 36-pin connection 0.1 kg (0.3 lb)
1756-TBE extended housing; required for additional wiring space if using 14 AWG wiring 0.05 kg (0.1 lb)

1492 Wiring As an alternative to buying RTBs and connecting the wires yourself, you can buy a
wiring system of:
Systems
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.

1756-SG001F-EN-P — June 2003

Feed through IFMs for 20-pin 1756 digital I/O modules

Cat. No. Description IA8D IA16 IB16 IC16 IN16 OA8 OA8D OA8E OA16 OA16E OB8 OB16E OC8 ON8
1492-IFM20F standard U X X X X U U U X U X U U
1492-IFM20FN narrow standard U X X X X U U U X U X U U
1492-IFM20F-2 extra terminals U X X X X U U U X U X U U
3-wire sensor type input
1492-IFM20F-3 X X X X
devices

feed through expander with

1492-XIMF-2 X X
eight feed-through channels✶

Find the column for the digital I/O module. Follow the column down to see what digital IFMs are compatible with the I/O module as indicated by a letter code. When you select the IFM, use the
letter code from this chart to find the compatible cable in the following table for digital pre-wired cabled. The letter code must match the last character of the catalog number for the cable.
✶One expander module is connected to a master to provide a total of 16 outputs. An extender cable is included with each expander to connect it to the master.

LED indicating IFMs for 20-pin 1756 digital I/O modules

Cat. No. Description IA8D IA16 IB16 IC16 IN16 OA8 OA8D OA8E OA16 OA16E OB8 OB16E OC8 ON8
1492-IFM20D24 standard with 24V ac/dc LEDs X X X
narrow standard with 24V
1492-IFM20D24N X X X
ac/dc LEDs
1492-IFM20D120 standard with 120V ac LEDs U X
narrow standard with 120V
1492-IFM20D120N U X X
ac/dc LEDs
24V ac/dc LEDS and extra
1492-IFM20D24-2 X
terminals for outputs
24V ac/dc LEDS and extra
1492-IFM20D24A-2 X X
terminals for inputs
120V ac/dc LEDS and extra
1492-IFM20D120-2 X
terminals for outputs
120V ac LEDs and extra
1492-IFM20D120A-2 U X
terminals for inputs
3-wire sensor with 24V ac/dc
1492-IFM20D24-3 X X
LEDs
isolated with 24/48V ac/dc
1492-IFM20DS24-4 LEDs and 4 terminals for W W W
outputs
isolated with 120V ac LEDs
1492-IFM20DS120-4 W V V
and 4 terminals for outputs
240V ac LEDs and extra
1492-IFM20D240-2
terminals for outputs
240V ac LEDs and extra
1492-IFM20D240A-2
terminals for inputs

1756-SG001F-EN-P — June 2003

Fusible IFMs for 20-pin 1756 digital I/O modules

Cat. No. Description IA8D IA16 IB16 IC16 IN16 OA8 OA8D OA8E OA16 OA16E OB8 OB16E OC8 ON8
1492-IFM20F-F-2 extra terminals for outputs X X
extra terminals with 24V
1492-IFM20F-F24-2 ac/dc blown fuse indicators X
for outputs
extra terminals with 120V ac
1492-IFM20F-F120-2 blown fuse indicators for X
outputs
extra terminals with 240V ac
1492-IFM20F-F240-2 blown fuse indicators for X
outputs
extra terminals with 24V
1492-IFM20F-F24A-2 ac/dc blown fuse indicators X X
for inputs
extra terminals with 120V ac
1492-IFM20F-F120A-2 blown fuse indicators for X
inputs
isolated with extra terminals
1492-IFM20F-FS-2 W V V W W W
for outputs
isolated with extra terminals
1492-IFM20F-FS24-2 and 24V ac/dc blown fuse W W W
indicators for outputs
isolated with 4 terminals and
1492-IFM20F-FS24A-4 24V ac/dc blown fuse
indicators for inputs
isolated with extra terminals
1492-IFM20F-FS120-2 with 120V ac blown fuse W V V
indicators for outputs
isolated with 4 terminals with
1492-IFM20F-FS120-4 120V ac blown fuse indicators W V V
for outputs
isolated with 4 terminals with
1492-IFM20F-FS120A-4 120V ac blown fuse indicators U
for inputs
isolated with 4 terminals with
1492-IFM20F-FS240-4 240V ac blown fuse indicators W
for outputs
expander with eight 24V dc
1492-XIMF-F24-2 channels with blown fuse X
indicators✶
expander with eight 120V ac
1492-XIMF-F120-2 channels with blown fuse X
indicators✶

Relay IFMs for 20-pin 1756 digital I/O modules

Cat. No. Description IA8D IA16 IB16 IC16 IN16 OA8 OA8D OA8E OA16 OA16E OB8 OB16E OC8 ON8
20-pin master with eight 24V
1492-XIM2024-8R X
dc relays
20-pin master with eight 24V
1492-XIM20120-8R X
dc relays
expander with eight 24V dc
1492-XIM24-8R X
relays✶
expander with eight 120V ac
1492-XIM120-8R X
relays✶

1756-SG001F-EN-P — June 2003

Feed through IFMs for 36-pin 1756 digital I/O modules

Cat. No. Description IA16I IB16D IB16I IB32 IH16I IM16I OA16I OB8EI OB16D OB16E OB16I OB32 OH8I OW16I OX8I
1492-IFM40F standard Y Y Y Z Y Y Y Y Y Z Y Y Y
1492-IFM40F-2 extra terminals Y Z Y Z
3-wire sensor type input
1492-IFM40F-3 Z
devices
expander with eight feed-
1492-XIMF-2 X
through channels✶

LED indicating IFMs for 36-pin 1756 digital I/O modules

Cat. No. Description IA16I IB16D IB16I IB32 IH16I IM16I OA16I OB8EI OB16D OB16E OB16I OB32 OH8I OW16I OX8I
standard with 24V ac/dc
1492-IFM40D24 Z Z
LEDs
24V ac/dc LEDs and extra
1492-IFM40D24-2 Z
terminals for outputs
24V ac/dc LEDs and extra
1492-IFM40D24A-2 Z
terminals for inputs
120V ac LEDs and extra
1492-IFM40D120-2
terminals for outputs
120V ac LEDs and extra
1492-IFM40D120A-2
terminals for inputs
3-wire sensor with 24V
1492-IFM40D24-3 Z
ac/dc LEDs for inputs
isolated with 24/48V ac/dc
1492-IFM40DS24-4 LEDs and 4 terminals per Y Y Y Y Y
output
isolated with 24/48V ac/dc
1492-IFM40DS24A-4 LEDs and 4 terminals per Y Y
input
isolated with 120V ac LEDs
1492-IFM40DS120-4 Y Y Y
and 4 terminals per output
isolated with 120V ac LEDs
1492-IFM40DS120A-4 Y
and 4 terminals per input
isolated with 240V ac LEDs
1492-IFM40DS240A-4 Y
and 4 terminals per output

1756-SG001F-EN-P — June 2003

Fusible for 36-pin 1756 digital I/O modules

Cat. No. Description IA16I IB16D IB16I IB32 IH16I IM16I OA16I OB8EI OB16D OB16E OB16I OB32 OH8I OW16I OX8I
1492-IFM40F-F-2 extra terminals for outputs Z
extra terminals with 24V
1492-IFM40F-F24-2 ac/dc blown fuse indicators Z
for outputs
extra terminals with 120V
1492-IFM40F-F120-2 ac blown fuse indicators for
outputs
isolated with extra terminals
1492-IFM40F-FS-2 Y Y Y Y Y Y Y
for outputs
isolated with extra terminals
and 24V ac/dc blown fuse
1492-IFM40F-FS24-2 Y Y Y Y Y
indicators for outputs

isolated with 24V ac/dc

1492-IFM40F-FS24-4 blown fuse indicators and 4 Y Y Y Y Y
terminals per output
isolated with extra terminals
1492-IFM40F-FS120-2 and 120V ac blown fuse Y Y Y Y
indicators for outputs
isolated with 120V ac blown
1492-IFM40F-FS120-4 fuse indicators and 4 Y Y Y
terminals per output
isolated with 240V ac blown
1492-IFM40F-FS240-4 fuse indicators and 4 Y Y Y
terminals per output
isolated with 24V ac/dc
1492-IFM40F-FS24A-4 blown fuse indicators and 4 Y Y
terminals per input
isolated with 120V ac blown
1492-IFM40F-FS120A-4 fuse indicators and 4 Y Y
terminals per input
fusible expander with eight
1492-XIMF-F24-2 24V dc channels with blown X
fuse indicators✶
fusible expander with eight
1492-XIMF-F120-2 120V ac channels with
blown fuse indicators✶

Relay IFMs for 36-pin 1756 digital I/O modules

Cat. No. Description IA16I IB16D IB16I IB32 IH16I IM16I OA16I OB8EI OB16D OB16E OB16I OB32 OH8I OW16I OX8I
40-pin master with eight 24V
1492-XIM4024-8R Z
dc relays
40-pin master with sixteen
1492-XIM40120-16R Z
24V dc relays
relay expander with eight
1492-XIM24-8R X
24V dc relays✶
relay expander with eight
1492-XIM120-8R
120V ac relays✶

1756-SG001F-EN-P — June 2003

Pre-wired cables for digital I/O modules

Cat. No.✶ Number of Conductors Conductor Size Nominal Outer Diameter RTB at the I/O Module End
1492-CABLExU 20 22 AWG 9.0 mm (0.36 in) 1756-TBNH
1492-CABLExV 20 22 AWG 9.0 mm (0.36 in) 1756-TBNH
1492-CABLExW 20 22 AWG 9.0 mm (0.36 in) 1756-TBNH
1492-CABLExX 20 22 AWG 9.0 mm (0.36 in) 1756-TBNH
1492-CABLExY 40 22 AWG 11.7 mm (0.46 in) 1756-TBCH
1492-CABLExZ 40 22 AWG 11.7 mm (0.46 in) 1756-TBCH

I/O-module-ready cables for digital I/O modules

Cat. No.✶ Number of Conductors Conductor Size Nominal Outer Diameter RTB at the I/O Module End
1492-CABLExTBNH 20 18 AWG 11.4 mm (0.45 in) 1756-TBNH
1492-CABLExTBCH 40† 18 AWG 14.1 mm (0.55 in) 1756-TBCH

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)

1756-SG001F-EN-P — June 2003

AIFMs for 1756 analog input modules

Descripti
on IF6I IF6I IF8 single-end IF8 differential IF16 single-end IF16 differential
Type of
Cat. No. AIFM current voltage voltage current voltage current voltage current voltage current IR6I IT6I
4 channels
feed with 3
1492-AIFM4-3
through terminals/c
hannel
6 channels
isolated
feed
1492-AIFM6S-3 with 3-4 X Y Z
through
terminals/c
hannel
8 channels
feed with 3
1492-AIFM8-3 TA TB TC TD UA UB UC UD
through terminals/c
hannel
6 channels
thermo with 3
1492-AIFM6TC-3 Y
couple terminals/c
hannel
8 channels
with 5
1492-AIFM8-F-5 fusible TA TB TC TD
terminals/c
hannel
16
channels
1492-AIFM16-F-3 fusible with 3 UA UB UC UD
terminals/c
hannel
16
channels
1492-AIFM16-F-5 fusible with 5 UA UB UC UD
terminals/c
hannel

Find the column for the analog I/O module. Follow the column own to see what AIFMs are compatible with the I/O module as indicated by a letter code. When you select the AIFM, use the
letter code from this chart to find the compatible cable in the following table for analog pre-wired cable. The letter code must match the last character of the catalog number for the cable.

AIFMs for 1756 analog output modules

Cat. No. Type of AIFM Description IR6I IT6I OF4 (voltage) OF4 (current) OF6CI OF6VI OF8 (voltage) OF8 (current)

4 channels with
1492-AIFM4-3 feed through 3 terminals per VA VB
channel

6 channels
isolated with 3-4
1492-AIFM6S-3 feed through Z Y Y
terminals per
channel

8 channels with
1492-AIFM8-3 feed through 3 terminals per WA WB
channel

6 channels with
1492-AIFM6TC-3 thermocouple 3 terminals per Y
channel

8 channels with
1492-AIFM8-F-5 fusible 5 terminals per
channel

16 channels with
1492-AIFM16-F-3 fusible 3 terminals per
channel

16 channels with
1492-AIFM16-F-5 fusible 5 terminals per
channel

1756-SG001F-EN-P — June 2003

AIFMs for 1757 analog I/O modules

Cat. No. Type of AIFM Description
1492-AIFMPI-3 fusible 8 input/output channels

The letter code for this AIFM is M. Use the letter code M to find the compatible cable in the following table for analog pre-wired cable. The letter code must match the last character of the
catalog number for the cable.

Pre-wired cables for analog I/O modules

Cat. No.✶ Number of Conductors† Conductor Size Nominal Outer Diameter RTB at the I/O Module End
1492-ACABIExM 11 twisted pairs 22 AWG 11.5 mm (0.45 in) 1757-PIM
1492-ACABLExX 9 twisted pairs‡ 22 AWG 6.8 mm (0.27 in) 1756-TBNH
1492-ACABLExY 9 twisted pairs§ 22 AWG 6.8 mm (0.27 in) 1756-TBNH
1492-ACABLExZ 20 conductors♣ 22 AWG 8.4 mm (0.33 in) 1756-TBNH
1492-ACABLExTA 20 conductors 22 AWG 8.4 mm (0.33 in) 1756-TBCH
1492-ACABLExTB 20 conductors 22 AWG 8.4 mm (0.33 in) 1756-TBCH
1492-ACABLExTC 5 twisted pairs 22 AWG 8.4 mm (0.33 in) 1756-TBCH
1492-ACABLExTD 5 twisted pairs 22 AWG 8.4 mm (0.33 in) 1756-TBCH
1492-ACABLExUA 20 conductors 22 AWG 8.4 mm (0.33 in) 1756-TBCH
1492-ACABLExUB 20 conductors 22 AWG 8.4 mm (0.33 in) 1756-TBCH
1492-ACABLExUC 9 twisted pairs 22 AWG 6.8 mm (0.27 in) 1756-TBCH
1492-ACABLExUD 9 twisted pairs 22 AWG 6.8 mm (0.27 in) 1756-TBCH
1492-ACABLExVA 20 conductors 22 AWG 8.4 mm (0.33 in) 1756-TBNH
1492-ACABLExVB 20 conductors 22 AWG 8.4 mm (0.33 in) 1756-TBNH
1492-ACABLExWA 9 twisted pairs 22 AWG 6.8 mm (0.27 in) 1756-TBNH
1492-ACABLExWB 9 twisted pairs 22 AWG 6.8 mm (0.27 in) 1756-TBNH

✶Cables are available in lengths of 0.5m, 1.0m, 2.5m, and 5.0m. To order, insert the code for the desired cable length into the catalog number in place of the x: 005=0.5m, 010=1.0m,
25=2.5m, 050=5m. Build-to-order cable lengths are also available.
†Each cable for analog I/O has an overall shield with a ring lug on a 200mm (8.87 in) exposed drain wire at the I/O module end of the cable.
‡One pair is not connected to the I/O module connector; two additional pairs are not used.
§Two pairs are not used.
♣One conductor is not connected to the I/O module connector; one additional conductor is not used.

For example, a 1756-IF6I in voltage mode uses:

1492-AIFM6S-3 interface module
1492-ACABLExY cable (replace x with the appropriate length)

1756-SG001F-EN-P — June 2003

1492 PanelConnect A PanelConnect module and its sensor connection systems lets you connect as many
as 16 sensors directly to 16-point input modules using convenient pre-built cables
Modules for and connectors.
Connecting Sensors
The PanelConnect module mounts on the enclosure and creates the correct seal for
the entry of the sensor connections. You do not need to seal the opening where the
sensor cables enter the enclosure, create custom connectors, or wire to those custom
connectors.

Connects to These
Cat. No. System Voltage Distribution Boxes Connector Style Connectors LEDs
Allen-Bradley, Brad Harrison
1492-TPMA1008 (Daniel Woodhead), Crouse-Hinds, 10 pin without
and Lumberg
mini-plus (1 1/8 in.)
ac Allen-Bradley, Brad Harrison
1492-TPMA1207 (Daniel Woodhead), Crouse-Hinds, 12 pin with
and Lumberg
1492-TPMA2209 Turck metric M23 12 pin either with or without
Allen-Bradley, Brad Harrison
1492-TPMD1004 (Daniel Woodhead), and Crouse- 10 pin without
Hinds
1492-TPMD1201 Allen-Bradley mini-plus (1 1/8 in.) 12 pin with
1492-TPMD1202 dc Brad Harrison (Daniel Woodhead) 12 pin with
1492-TPMD1203 Lumberg 12 pin with
1492-TPMD2205 Turck 12 pin either with or without
metric M23
1492-TPMD2206 Turck 12 pin either with or without

You can select these PanelConnect modules and cables, depending on the 16-point
input modules in your system:
I/O
Module
✶ 1492-TPMA1008 1492-TPMA1207 1492-TPMA2209 1492-TPMD1004 1492-TPMD1201 1492-TPMD1202 1492-TPMD1203 1492-TPMD2205 1492-TPMD2206
1756-IA16 1492-CABLExX 1492-CABLExX 1492-CABLExX
1756-IB16 1492-CABLExX 1492-CABLExX 1492-CABLExX 1492-CABLExX 1492-CABLExX 1492-CABLExX
1756-IC16 1492-CABLExX 1492-CABLExX 1492-CABLExX
1756-IN16 1492-CABLExX 1492-CABLExX 1492-CABLExX

✶Cables are available in lengths of 0.5m, 1.0m, and 5.0m. To order, insert the code for the desired cable length into the catalog number in place of the x: 005=0.5m, 010=1.0m, 050=5m.

Select a patchcord to connect the PanelConnect module to the sensor distribution

box, depending on the type of connector:

Cat. No.✶ Diameter - mm (in) Wire Rating Connector Type

889N-F10AFNU-x 17 (0.67) 10 pin Mini-Plus (1 18”), straight male
889N-F12AFNU-x 18 (0.71) 16 AWG 12 pin Mini-Plus (1 18”), straight male
600V
889N-F10AFNV-x 17 (0.67) 7A 10 pin Mini-Plus (1 18”), right-angle male
889N-F12AFNV-x 18 (0.71) 12 pin Mini-Plus (1 18”), right-angle male
889N-F10ACNU-x 9 (0.36) 10 pin Mini-Plus (1 18”), straight male
889N-F12ACNU-x 9 (0.36) 18/22 AWG 12 pin Mini-Plus (1 18”), straight male
300V
889N-F10ACNV-x 9 (0.36) 3A 10 pin Mini-Plus (1 18”), right-angle male
889N-F12ACNV-x 9 (0.36) 12 pin Mini-Plus (1 18”), right-angle male

✶Cables are available in lengths of 2m, 3m, 5m, and 10m. To order, insert the code for the desired cable length into the catalog number in place of the x: 2=2m, 3=3m, 5=5m, 10=10m.

1756-SG001F-EN-P — June 2003

Placing 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
ControlLogix I/O I/O modules in the control system determines how the modules exchange data.
Modules
If the I/O module is: And you place the module here: The data exchange method is based on:
change of state
local chassis and / or
digital requested packet interval (cyclic)
remote chassis requested packet interval
real time sample
local chassis and / or
analog 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:

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.

1756-SG001F-EN-P — June 2003

How ControlLogix 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
Modules Operate 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 Placement 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.
local chassis
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
digital input (CPS) instruction to copy the input data from your input tags to another structure and use the data from that structure.
The RPI and COS values still define when the module multicasts data within its own chassis, but only the value of the RPI determines
when the owner controller receives the data over the network.
remote chassis When an RPI value is specified for an input module in a remote chassis, in addition to instructing the module to multicast data within
its own chassis, the RPI also reserves a spot in the stream of data flowing across the control network. The timing of this reserved spot
may or may not coincide with the exact value of the RPI, but the owner-controller will receive data at least as often as the specified RPI.
If the module resides in the same chassis as the owner-controller, the module receives the data almost immediately after the owner-
local chassis
controller sends it. Data is sent after all the programs within each task have completed executing.
digital output 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.
remote 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 output module receives data at least as often as the specified RPI.
The RTS value specifies when the module scans its channels and multicasts the data (update the input data buffer then multicast). The
RPI value specifies when the module multicasts the current contents of the input data buffer without scanning (updating) the channels.
local chassis 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.
analog input If the RTS value is greater than the RPI, the module multicasts at both the RTS rate and the RPI rate.
The RPI and RTS rates still define when the module multicasts data within its own chassis, but only the RPI value determines when the
owner-controller receives the data over the network.
remote 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 controller receives data at least as often as the specified RPI.
The RPI value specifies when the owner-controller broadcasts output data to the module. If the module resides in the same chassis as
local chassis
the owner-controller, the module receives the data almost immediately after the owner-controller sends it.
analog output 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.
remote 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 output module receives data at least as often as the specified RPI.

Selecting Controller In a Logix system, modules multicast data. This means that multiple devices can
receive the same data at the same time from a single device. When you choose a
Ownership communication format for an I/O module, you have to choose whether to establish an
owner or listen-only relationship with the module.
Relationship Description
The controller that creates the primary configuration and communication connection to a module.
owner controller
The owner controller writes configuration data and can establish a connection to the module.
An I/O connection where another controller owns/provides the configuration data for the I/O
module. A controller using a listen-only connection only monitors the module. It does not write
listen-only connection
configuration data and can only maintain a connection to the I/O module when the owner controller
is actively controlling the I/O module.

1756-SG001F-EN-P — June 2003

Step 2 - Select:
size the motion application (use the Selecting Motion Control
Motion Book)
how you want to interface the controller
Requirements
and drives
SERCOS or analog interface
The Logix approach to motion control employs synchronized, distributed processing
associated cable(s) and provides a highly-integrated motion solution. Logix integrates sequential and
a remote terminal block (RTB) - only motion control to bring unmatched flexibility to machine design and unprecedented
needed for 1756-M02AE modules efficiency to the manufacturing floor. RSLogix 5000 Enterprise series software
select drives, motors, and accessories (use supports a comprehensive set of embedded motion instructions that can be
the Motion Book) programmed using the relay ladder, structured text, or sequential function chart
editors. The embedded motion instructions satisfy a wide range of machine control
needs, including independent axis motion, synchronized gearing and camming, and
fully-interpolated motion in three dimensions.

The Logix architecture supports motion components that work in a wide variety of
machine architectures:
The Kinetix integrated motion solution uses the SERCOS™ interface to perform
complex, multi-axis, synchronized motion. With a Kinetix system, you reap the
full benefit of the integrated architecture because the integration doesn’t stop at
the controller. This system integrates the drive, the motor, and even the actuator
at a lower cost per axis of motion.
Logix integrated motion using the analog interface provides connectivity for
traditional closed loop servo and variable frequency drives
Networked motion provides the ability to connect via DeviceNet to a single-axis
drive to perform simple, point to point indexing. You need Ultraware software
for drive and indexing configuration.

Use this selection guide to select the appropriate motion interface. Use the Motion
Book to size your motion application and to select the appropriate drives, motors, and
accessories. The Motion Book is available on The Automation Bookstore
(www.theautomationbookstore.com) and the Rockwell Automation motion website
(www.ab.com/motion/software/motion_book.html).

1756-SG001F-EN-P — June 2003

Selecting a Motion You can communicate directly to a servo drive using a motion interface or over
a network.
Interface
Communicate directly to a servo drive

The controller can control these servo drives through these motion interfaces:
If your application requires: Select this motion interface:
1756-M16SE (16 axes)
Rockwell Automation SERCOS drives
1756-M08SE (8 axes)
analog command signal
1756-M02AE
quadrature encoder feedback
analog command signal
1756-HYD02
linear transducer feedback

Communicate over a network

Some servo drives are supported through communication interface modules. The
controller can communicate with these servo drives over these networks:

Drives✶ EtherNet/IP ControlNet DeviceNet Universal Remote I/O RS-232 Serial DH-485
1394 GMC drive and
no no no yes yes yes
control
1398 ULTRA 100 series
no no yes no no no
drive
2098 Ultra3000 DeviceNet
no no yes no no no
servo drive
2098 Ultra5000 intelligent
no no yes no yes
positioning

✶Each drive has different options you order for its supported communication networks. See the appropriate catalog or selection information for a drive to make sure you select the appropriate
option when specifying a drive for a specific network.

For more information on selecting servo drives, see the Motion Control Selection
Guide, publication GMC-SG001.

1756-SG001F-EN-P — June 2003

SERCOS Interface The 8-axis (1756-M08SE) or 16-axis (1756-M16SE) SERCOS interface servo modules
serve as a link between the ControlLogix platform and intelligent, servo drives.
Modules SERCOS is the IEC 61491 SErial Real-time COmmunication System protocol over a
fiber optic medium. The SERCOS interface is an open, controller-to-digital drive
interface designed for high-speed, real time, serial communications using noise-
immune, fiber-optic cables.

The SERCOS interface modules use a single, digital fiber optic link, which eliminates
up to 18 discrete wires per axis. Detailed drive status information can be sent from
drive to controller and from controller to drive.

The SERCOS interface modules can connect to these servo drives:

2094 Kinetix 6000 servo drive
2098 Ultra3000 SERCOS servo drive
1394C SERCOS drive
8720MC spindle

Maximum Number of
Maximum Number of Axes per ControlLogix Backplane Current (mA) Backplane Current (mA)
Cat. No. Axes per Module Controller Power Dissipation at 5V at 24V SERCOS Data Rate
1756-M08SE 8 4 Mbits per second
32 5.0W 900 mA 2.5 mA
1756-M16SE 16 8 Mbits per second

Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE

1756-SG001F-EN-P — June 2003

Cables for Use with Select one of these fiber optic cables to connect the SERCOS interface module to the
drive:
the SERCOS
Interface Modules
Cat. No. Description
Plastic Fiber Optic Cables✶
1000 µm plastic simplex fiber optic cable
2090-SCEPx-x (no jacket) transmission range of 1-32 meters.
2090-SCVPx-x (standard jacket) Allen-Bradley offers plastic, fiber-optic cable assemblies that come in a variety of jackets:
2090-SCNPx-x (nylon jacket) no jacket (Chlorinated Polyethylene) for use inside an electrical cabinet
a standard jacket (Polyvinyl Chloride) for use outside of electrical cabinets
a nylon jacket for use in harsh environments
Glass Fiber Optic Cables†
200 µm glass fiber optic cable
2090-SCVGx-x transmission range of 1-200 meters
Allen-Bradley offers glass, fiber-optic cable assemblies that come with a standard jacket (Polyvinyl
Chloride) for use in normal environments.

✶The x-x determines the length in meters. Specify 0-1 for 0.1m, 0-3 for 0.3m, 1-0 for 1m, 3-0 for 3m, 5-0 for 5m, 8-0 for 8m, 10-0 for 10m, 15-0 for 15m, 20-0 for 20m, 25-5 for 25m, or 32-0
for 32m.
†The x-x determines the length in meters. Specify 1-0 for 1m, 5-0 for 5m, 8-0 for 8m, 10-0 for 10m, 15-0 for 15m, 20-0 for 20m, 25-0 for 25m, 32-0 for 32m, 50-0 for 50m, 100-0 for 100m,
150-0 for 150m, or 200-0 for 200m.

Both the transmitter and receiver connections use a F-SMA standard plug that
conforms to the F-SMA screw type connector.

1756-SG001F-EN-P — June 2003

Analog Interface The 1756-M02AE analog interface module is a 2-axis, closed-loop servo module that
receives profile information from the ControlLogix controller. The servo module
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 ms using position feedback as the
input and ±10V analog output.

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.

The analog interface can connect to these servo drives:

2098 Ultra3000 analog servo drive
1394C analog drive
1398 ULTRA 100/200 series drive
8720MC spindle

Maximum Number of
Maximum Number of Axes per ControlLogix Backplane Current (mA) Backplane Current (mA) Removable Terminal
Cat. No. Axes per Module Controller Power Dissipation at 5V at 24V Block Housing
1756-TBCH
1756-M02AE 2 32 5.5 W 700 mA 2.5 mA
1756-TBS6H✶

Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE

✶Maximum wire size will require the extended depth RTB housing (1756-TBE).

1756-SG001F-EN-P — June 2003

Cables for Use with Select one of these cables to connect the analog interface module to the drive:

the Analog Interface

Module
Ultra3000 Cables Description
1756-M02AE to an Ultra3000 single-axis, analog servo drive
2090-U3CC-D44xx
xx = 01 for 1m, 03 for 3m
09 for 9m, 15 for 15m, 30 for 30m
1756-M02AE to an Ultra3000 two-axis, analog servo drive
2090-U3AE-D44xx
xx = 01 for 1m, 03 for 3m, 09 for 9m, 15 for 15m, 30 for 30m
1394 Cables Description
1756-M02AE to a 1394 single-axis, analog servo drive
1394-CFLAExx
xx = 01 for 1m, 03 for 3m, 08 for 8m, 15 for 15m
1756-M02AE to a 1394 two-axis, analog servo drive
1394-CCAExx
xx = 01 for 1m, 03 for 3m, 08 for 8m, 15 for 15m
1398 Cables Description
1756-M02AE to a 1398 single-axis, analog servo drive
1398-CFLAExx
xx = 01 for 1m, 03 for 3m, 08 for 8m, 15 for 15m
1756-M02AE to a 1398 two-axis, analog servo drive
1398-CCAExx
xx = 01 for 1m, 03 for 3m, 08 for 8m, 15 for 15m

1756-SG001F-EN-P — June 2003

Hydraulics Interface The 1756-HYD02 hydraulic servo module is a 2-axis, closed-loop control module that
receives profile information from the ControlLogix controller. The hydraulic servo
Module module ensures that the axis follows the profile by monitoring the position feedback
via linear differential transducer (LDT) input and generating an analog command
reference for the actuator. A position and velocity loop is closed using position
feedback as the input and provides ±10V analog output.

The 1756-HYD02 module must be in the same chassis as the ControlLogix controller
that controls the hydraulic servo module. If you distribute motion control that uses the
1756-HYD02 module across different locations, place a ControlLogix controller in
each chassis that has a 1756-HYD02 module.

Power Dissipation, Backplane Current Backplane Current Removable Terminal

Cat. No. Types of Inputs Types of Outputs Number of Axes Max. (mA) at 5V (mA) at 24V Block Housing
LDT input with start/stop
or falling edge servo output with analog
registration input voltage
1756-TBCH
1756-HYD optically isolated, current other outputs with solid- 2 5.5W 700 2.5
1756-TBS6H
sinking state isolated relay
other inputs optically contacts
isolated, current sinking

Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE

1756-SG001F-EN-P — June 2003

Connecting LDTs to The following linear transducer types (LDTs) are recommended for use with the
1756-HYD02 module. Note that there other suppliers with compatible LDTs.
the 1756-HYD02
Temposonics II: RPM or DPM
Module
Balluff: BTL-2-L2 or BTL-2-M2
Santest: GYRP or GYRG
Gemco Quick-Stick II: 951 VP or 951 RS

1756-SG001F-EN-P — June 2003

Step 3 - Select:
networks Selecting Network
communication modules
associated cable(s) and network
Communications
equipment
sufficient modules and cables if you are
Separate communication interface modules are available for different networks. Install
planning a redundant system
multiple communication interface modules into the ControlLogix backplane to
configure a gateway to bridge or route control and information data between the
different networks.

Messages are sent directly from one communication interface module across the
backplane to another. You can route a message through a maximum of 4 chassis (8
communication hops). You do not need a ControlLogix controller in the chassis.

NetLinx architecture
NetLinx open network architecture is the Rockwell Automation strategy of using open
networking technology for seamless, top-floor to shop-floor integration. The networks
in the NetLinx architecture – DeviceNet, ControlNet, and EtherNet/IP – speak a
common language and share a universal set of communication services. NetLinx
architecture, part of the Integrated Architecture, seamlessly integrates all the
components in an automation system from a few devices on one network to multiple
devices on multiple networks including access to the Internet – helping you to
improve flexibility, reduce installation costs, and increase productivity.
EtherNet/IP is an open industrial networking standard that supports implicit
and explicit messaging and uses commercial, off-the-shelf Ethernet equipment
and physical media.
ControlNet allows intelligent, high-speed control devices to share the
information required for supervisory control, work-cell coordination, operator
interface, remote device configuration, programming, and troubleshooting.
DeviceNet offers high-speed access to plant-floor data from a broad range of
plant-floor devices and a significant reduction in wiring.

1756-SG001F-EN-P — June 2003

Selecting a network
You can configure your system for information exchange between a range of devices
and computing platforms and operating systems.
If your application requires: Use this network: Select:
plant management (material handling)
configuration, data collection, and control on a single, high-speed network
time-critical applications with no established schedule EtherNet/IP network 1756-ENBT
data sent regularly
Internet/Intranet connection
high-speed transfer of time-critical data between controllers and I/O devices
deterministic and repeatable data delivery
media redundancy
ControlNet network 1756-CNB, -CNBR
controller redundancy
intrinsic safety
redundant controller systems
connections of low-level devices directly to plant floor controllers, without interfacing them
through I/O modules
data sent as needed DeviceNet network 1756-DNB
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
data sent regularly Data Highway Plus 1756-DHRIO
transfer of information between controllers
connections between controllers and I/O adapters
data sent regularly
Universal Remote I/O network 1756-DHRIO
distributed control so that each controller has its own I/O and communicates with a supervisory
controller
Fieldbus transmitters and actuators
closed-loop control Fieldbus network 1788-CN2FF
process automation
modems built-in serial port
serial network
supervisory control and data acquisition (SCADA) 1756-MVI, -MVID
connections to existing DH-485 networks DH-485 network built-in serial port

For more specialized communication requirements, select:

If your application requires: Use this:
SynchLink fiber optic communications to:
controllers 1756-SYNCH
power distribution systems 1756-DMxxx
PowerFlex 700S
AutoMax DCS network communications 56AMXN
connections to other networks via ControlNet 1203-CN1 and generic MSG instructions

1756-SG001F-EN-P — June 2003

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.

EtherNet/IP product capability

Recipient
1769-L20, -L30
EtherNet/IP PLC-5 1734-AENT PanelView controller with
PLC-5 or SLC processor via Logix 1756-ENBT 1794-AENT FLEX POINT I/O EtherNet/IP RSLinx 1761-NET-ENI
5/05 processor 1785-ENET controller✶ module✶ I/O adapter adapter terminal software interface
EtherNet/IP PLC-5
or SLC 5/05 information information information na not supported not supported information information information
processor
PLC-5 processor
information information information na not supported not supported information information information
via 1785-ENET
information
information
Logix controller✶ information information I/O data I/O data I/O data I/O data information information
I/O data
interlocking
PanelView
information
EtherNet/IP information information na na na na na information
I/O data
terminal
RSLinx software information information information na not supported not supported na information information
1769-L20, -L30
controller with
information information information na not supported not supported information information information
1761-NET-ENI
interface†

✶ For EtherNet/IP control:

a ControlLogix controller requires a 1756-ENBT or 1756-ENET series B module
a FlexLogix controller requires a 1788-ENBT card
a CompactLogix controller must be a 1769-L35E controller with its built-in connection
a SoftLogix controller requires an Ethernet communication card
†To be an originator, the 1761-NET-ENI interface must connect to the other device through that device’s RS-232 port.

1756-SG001F-EN-P — June 2003

1756-ENBT EtherNet/IP communication interface

module

The EtherNet/IP communication modules control I/O over an EtherNet/IP network.

The modules also bridge EtherNet/IP links to route messages to devices on other
networks.

Cat. No. Communication Rate Connections Power Dissipation, Max. Backplane Current (mA) at 5V Backplane Current (mA) at 24V
Each module supports a maximum
of:
64 TCP/IP connections
1756-ENBT 10/100 Mbps 3.65 W 700 3
128 Logix connections (I/O and
information
5000 messages/second

Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM, C-Tick

1756-SG001F-EN-P — June 2003

ControlNet Network The ControlNet communication module bridges ControlNet links to route messages to
devices on other networks. The ControlNet communication module also monitors and
controls 1756 I/O modules located remotely from the ControlLogix controller.

Power Dissipation, Backplane Current Backplane Current

Cat. No. Communication Rate Connections Cable Max. (mA) at 5V (mA) at 24V
1756-CNB RG-6 coaxial cable 5.14 W 970 2
1786-RG6 (shield high flex cable)
1786-RG6F (quad shield high flex coax cable)
1786-XT termination resistor
64 connections per
5 Mbps
1756-CNBR module Choose taps: 5.14 W 1000 2
1786-TPR (T-tap right angle)
1786-TPS (T-tap straight)
1786-TPYR (Y-tap right angle)
1786-TPYS (Y-tap straight)

Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM, C-Tick

1756-SG001F-EN-P — June 2003

Redundant controller systems via ControlNet

You can build a redundant controller system around a ControlNet network. In each
redundant controller chassis, you can have:
one 1756-L55 controller (contact your Rockwell Automation representative for
the specific firmware revision)
at least one, but no more than five, 1756-CNB series D, version 5.23 (or
greater) ControlNet communication modules
one 1757-SRM redundancy module
no other I/O or communication modules can be in the redundant chassis

All I/O must be remote from the redundant controllers. ControlLogix redundancy
works with 1756 I/O, FLEX I/O, drives, operator interfaces, and any other devices that
can communicate with a ControlLogix controller over a ControlNet link. To connect to
other networks, bridge through another ControlLogix chassis (not one of the
redundant controller chassis).

The secondary controller is synchronized with the primary controller to provide a

bumpless switchover for any outputs controlled by logic in the highest priority task.
Switchover occurs within 100msec.

1756-SG001F-EN-P — June 2003

Make sure that your ControlNet network contains at least two nodes in addition to the
redundant chassis pair. And additional node can be:
a second 1756-CNBR module in the same remote chassis or in a different
remote chassis
any ControlNet device
a workstation running RSLinx software

1757-SRM redundancy module

The 1757-SRM redundancy module provides high-speed data transfers between the
primary and secondary chassis. You need one 1757-SRM module per chassis. The
module supports as many as five 1756-CNB modules per chassis.
Backplane Current at Backplane Current (mA) Backplane Current (mA)
Cat. No. Cable Voltage/Current Power Dissipation, Max. 3.3V at 5V at 24V
Choose:
1757-SRC1 (1m)
1757-SRC3 (3m) 30V ac/dc maximum
1757-SRM 0.75 A 1.0 A 0.09 A
1757-SRC10 (10m) 100mA maximum
1757-SRC50 (50m)
1757-SRC100 (100m)

Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM, C-Tick

1756-SG001F-EN-P — June 2003

DeviceNet Network 1756-DNB DeviceNet scanner interface module

The DeviceNet scanner module acts as an interface between DeviceNet devices and a
Logix controller. 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

Power Dissipation, Backplane Current Backplane Current

Cat. No. Communication Rate Connections Cable Max. (mA) at 5V (mA) at 24V
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)
125 Kbps 2 connections to
1485C-P1-A50 (thick, grey, 50 meters)
1756-DNB 250 Kbps dedicated ControlLogix 5.3 W 600 3
1485C-P1-A150 (thick, grey, 150 meters)
500 Kbps controller
1485C-P1-A300 (thick, grey, 300 meters)
1485C-P1-A500 (thick, grey, 500 meters)

1485A-C2 termination resistor

Choose taps:
1485P-P2T5-T5 (2 ports)
1485P-P4T5-T5 (4 ports)
1485P-P8T5-T5 (8 ports)

Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM, C-Tick

1756-SG001F-EN-P — June 2003

DH+ and Universal 1756-DHRIO DH+ and remote I/O communication

Remote I/O interface module
Networks
The DH+ and remote I/O module supports messaging between devices on DH+
networks. The remote I/O functionality enables the module to act as a scanner for
transferring discrete and block-transfer data to and from remote I/O devices.

Power Dissipation, Backplane Current Backplane Current

Cat. No. Communication Rate Connections Cable Max. (mA) at 5V (mA) at 24V
1770-CD
32 connections per DH+ channel
Belden 9463
57.6 Kbps
1756-DHRIO 115.2 Kbps 32 logical rack connections per remote I/O channel 4.5 W 850 2
150Ω and 82Ω
230.4 Kbps 16 block-transfer connections per remote I/O
termination resistors
channel
ship with the module

Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM, C-Tick

Network Typical Configuration

DH+

Universal remote I/O

1756-SG001F-EN-P — June 2003

Fieldbus Network The Foundation Fieldbus linking device adds Foundation Fieldbus support to your
ControlLogix system. You can have one linking device per ControlNet tap. The device
connects to two, independent Fieldbus H1 networks.

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.

Backplane Current (mA)

Cat. No. Communication Rate Connections Cable at 24V
Connects to redundant ControlNet media for each
2 ms over ControlNet 9-pin FieldBus cable
1788-CN2FF H1 network 270 mA @ 24V dc
31.25 Kbps over Fieldbus pins 6 and 7 handle Fieldbus signals
Each linking device supports two H1 networks

Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM, C-Tick

1756-SG001F-EN-P — June 2003

Serial Network The built-in, serial port is compatible with RS-232 serial communication. The serial
port supports the DF1 protocol to communicate with other devices on the serial link.
You can select:
Use this DF1 mode: For:
point to point communication between a controller and other DF1-compatible devices using DF1 full-duplex protocol
DF1 master control of polling and message transmission between the master and each slave using DF1 half-duplex polled protocol
DF1 slave using the controller as a slave station in a master/slave serial network using DF1 half-duplex protocol
user mode (ASCII) communication between a controller and an ASCII device, such as a bar code reader

Use a 1756-CP3 cable to connect to the serial port.

Over the serial port, the ControlLogix controller supports 12 message buffers. At most,
you can have 4 simultaneous connected messages and 8 simultaneous unconnected
messages. Or if all the messages are unconnected, you can have 12 simultaneous
messages. If a message is greater than 250 bytes, it is divided across enough buffers to
carry the message, which reduces the number of buffers remaining for other
simultaneous messages.
1756-MVI, -MVID multi-vendor interface module

The multi-vendor interface module provides additional access to serial devices. The
module is programmable to accommodate devices with unique serial protocols.

Power Backplane Backplane

Communicatio Dissipation, Current (mA) at Current (mA) at
Cat. No. n Rate Connections Cable Max. 5V 24V
1756-MVI 3 serial adapter cables ship with the
configurable, PRT1: RS-232
module the locking-type RJ45
1756-MVID depending on PRT2: RS-232, RS-422, RS-485 4W 800 3
connector installs in the module; the
(1756-MVI module and API software) serial protocol PRT3: RS-232, RS-422, RS-485
other end is a DB-9 male connector

Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM, C-Tick

1756-SG001F-EN-P — June 2003

DH-485 Network On the DH-485 network, the controller can send and receive messages to and from
other controllers on the network. The DH-485 connection does support remote
programming and monitoring via RSLogix 5000 software. However, excess traffic over
a DH-485 connection can adversely affect overall performance and can lead to
timeouts and loss in RSLogix 5000 configuration performance.

Important: Only use Logix controllers on DH-485 networks when you want to add
controllers to an existing DH-485 network. For new applications with Logix
controllers, networks in the NetLinx architecture are the recommended networks.

You need a 1761-NET-AIC+ converter for each controller you want to put on the DH-
485 network. You can have two controllers per one 1761-NET-AIC+ converter, but you
need a different cable for each controller. Connect one controller to port 1 (9-pin
connector) and one controller to port 2 (mini-DIN connector).

If you connect to this port: Use this cable:

1747-CP3
port 1
or
DB-9 RS-232, DTE connection
1761-CBL-AC00
1761-CBL-AP00
port 2
or
mini-DIN 8 RS-232 connection
1761-CBL-PM02

1756-SG001F-EN-P — June 2003

SynchLink SynchLink provides time synchronization and data broadcasting capabilities for
distributed motion and coordinated drive control.
1756-SYNCH SynchLink module

The 1756-SYNCH SynchLink module connects a ControlLogix chassis to a SynchLink

fiber optic communications link. The module:
coordinates CST time across multiple ControlLogix chassis
moves limited amount of data from one chassis to another at a high speed
lets one controller consume motion axes data from a controller in another
chassis
Power Dissipation, Backplane Current Backplane Current
Cat. No. Communication Rate Cable Max. (mA) at 5V (mA) at 24V
200/230 micron Hard Clad Silica (HCS) VersaLink
V-system

operating wavelength: 650nm (red) Order 1403-CF xxx cable or from Lucent
1756-SYNCH data rate: 5Mbps Technologies, Specialty Fiber Technologies 6.19 W 1200 3
baud rate: 5Mbaud division✶

maximum length 300

minimum length 1m

Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE

✶The xxx determines the length. Select 001, 003, 005, 010, 020, 050, 100, or 250 meters.

Topology Example

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

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
ring network

1756-SG001F-EN-P — June 2003

1756-DMxxx module
The 1756-DM drive module lets you update and retrofit Reliance distributed power
system (DPS) installations to ControlLogix-based systems. Each drive module
interfaces with an individual Power Module Interface (PMI) chassis. You can also use
the 1756-DM to modernize existing power bridges from analog to digital control.
Cat. No.✶ Communicates with
1756-DMD30 SD3000 dc drive
1756-DMF30 SF3000 Regen field control
1756-DMA30 SA3000 ac drive
1756-DMA31 SA3100 ac drive

✶The 1756-DM modules are only available through Drive Systems.

Backplane Backplane
Operating Current (mA) Current (mA)
Cat. No. Wavelength Data Rate Cable Maximum Node Count at 5V at 24V
200/230 micron Hard Clad Silica (HCS);
VersaLink V-system
Order 1403-CF xxx power monitoring cable or from
10 daisy chain configuration
1756-DMxxx Lucent Technologies, Specialty Fiber Technologies
650 nM (red) 5 Mbps 256 star configuration with
SynchLink values division✶
multiplexing blocks
maximum length 300m
minimum length 1m
1.35 A 3.0 mA
62.5/125 micron glass; one pair SC Style and one
pair ST Style
Order 1756-DMCF xxx drive communications fiber
1756-DMxxx 820 nM optic cable or breakout cable from Belden 225362
10 Mbps 1 PMI chassis
Drive communications values (infrared) or Mohawk M92021†

maximum length 300m

minimum length 1m

Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE

✶The xxx determines the length. Select 001, 003, 005, 010, 020, 050, 100, or 250 meters.
†The xxx determines the length. Select 001, 003, 010, or 030 meters.

Existing Power Systems Distributed Power Systems

1756-SG001F-EN-P — June 2003

PowerFlex 700S® The Allen-Bradley PowerFlex 700S ac drive with DriveLogix, a version of PowerFlex
700 with embedded Logix, offers optimized integration for the most demanding drive
AC Drive with control and drive system applications.
DriveLogix
Power Backplane Current Backplane Current
Cat. No. Communication Rate Cable Dissipation, Max. (mA) at 5V (mA) at 24V
200/230 micron Hard Clad Silica (HCS) VersaLink V-system

operating wavelength: 650nm (red) Order 1403-CF xxx cable(1) or from Lucent Technologies, Specialty
20D series data rate: 5Mbps Fiber Technologies division 6.19 W 1200 mA 3 mA
baud rate: 5Mbaud
maximum length 300
minimum length 1m

Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE

1756-SG001F-EN-P — June 2003

56AMXN AutoMax The 56AMXN module connects a ControlLogix system to an AutoMax DCS network or
Network and to an AutoMax Remote I/O network. The traditional Reliance Electric Systems solution
is based on an AutoMax controller and architecture. DCSNet is the main
RE Remote I/O communications, data, and control network or “backbone”. RE RIO is the Remote I/O
architecture to network devices such as I/O and MMI or HMI operator stations.

You configure the 56AMXN as a generic module. The module supports scheduled data
up to 250 words of input, 248 words of output, and 250 words of status data. The
module supports RPIs from .2 to 750ms.

As a: The 56AMXN module:

Scans up to 55 drops with 32 words in and 32 words out per drop
DCSNet master Transmits 8 words of global broadcast data every 2.8ms
Maintains standard drop 0 diagnostic counters
Acts as any drop number from 1 to 55, with drop depth from 1 to 55 (“active drops”)
DCSNet slave
Monitors input and output data on other drops on the network (“monitored drops”)
Scans up to 7 drops, with up to 248 words of output data and 250 words of input data
RE remote I/O master
Maintains standard diagnostic counters

Communication
Networks and Power Dissipation, Backplane Current Backplane Current
Cat. No. Supported Modes Cable Max. (mA) at 5V (mA) at 24V
Drop cable (612574-36R, 3ft long with 9-pin D-shell connectors) and passive
DCS network: master or
tap (M/N 57C380, BNC connectors) connects the module to the network cable.
slave
56AMXN 5.0 W 650 75
RE remote I/O network:
For DCS, the network cable can be RG-59/U or RG-11/U.
master
For remote I/O, the cable must be RG-59/U.

Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE

1756-SG001F-EN-P — June 2003

Accessing the A remote access dial-in kit (9300-RADKIT) lets you connect via modem to a remote
site’s network and controller. Once connected, you can monitor the process, collect
Controller Remotely data, and make program changes remotely. Each remote access dial-in kit includes:
pre-configured modem
DH+ communication module (9300-KF2RAD)
DH-485 communication module (9300-KERAD)
DIN rail mounting hardware
associated cables

Each kit also includes a CD-ROM-based installation guide and tutorial that takes you
step-by-step through establishing a remote dial-in connection.

Cat. No. Communication Rate Supported Controllers Power Requirements

ControlLogix, CompactLogix, FlexLogix controllers
8-48V dc
MicroLogix controllers
100 mA at 12V dc
9300-RADKIT phone line speeds up to 56K Enhanced PLC-5 processors
SLC 5/03, 5/04, 5/05 processors
external 100V ac power supply included with each modem
1203-SSS

The modem supports remote configuration, so you can modify the remote network
modem’s command settings through a dial-up connection. This helps you recover
modem communication if a change occurs in the controller’s channel configuration.

The remote access modem also has call-back security which is authenticated with a
password.

1756-SG001F-EN-P — June 2003

Connecting to Other The RSLogix 5000 Enterprise Series software supports a generic ControlNet module
that allows connections to ControlNet nodes for which there is no specific support
Devices via currently available in the programming software. A module configured as a generic
ControlNet 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-CN1module. These
parameters differ depending on the module. See the module’s vendor for module’s
characteristics.
1756-SG001F-EN-P — June 2003
51

Step 4 - Select:
a controller with sufficient memory Selecting Controllers
memory board for each
1756-L55 controller
1756-BATM for larger memory size
The ControlLogix controller provides a scalable controller solution that is capable of
controllers
addressing a large amount of I/O points (128,000 digital maximum / 4000 analog
replacement batteries
maximum).

The ControlLogix controller can be placed into any slot of a ControlLogix I/O chassis
and multiple controllers can be installed in the same chassis. Multiple controllers in
the same chassis communicate with each other over the backplane (just as controllers
can communicate over networks) but operate independently.

ControlLogix controllers can monitor and control I/O across the ControlLogix
backplane, as well as over I/O links. ControlLogix controllers can communicate with
computers or other processors across RS-232-C (DF1/DH-485 protocol), DeviceNet,
DH+, ControlNet, and EtherNet/IP networks. To provide communication for a
ControlLogix controller, install the appropriate communication interface module into
the chassis.

The multi-tasking operating system supports 32 configurable tasks that can be

prioritized. One task can be continuous. The others must be periodic or event tasks.
Each task can have as many as 32 programs, each with its own local data and logic,
allowing virtual machines to operate independently within the same controller.

Specification Description

1756-BA1 (94194801) - comes with the controller

Battery or
1756-BATM (contains a 1756-BATA battery assembly)✶

Programming Cable 1756-CP3 or 1747-CP3 serial cable

Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM, C-Tick, EEx ATEX

✶The battery module is highly recommended for all controllers.

1756-SG001F-EN-P — June 2003

ControlLogix Controllers
Memory
Power Dissipation, Thermal Dissipation, Backplane Current Backplane Current
Cat. No. Data and Logic✶ I/O† Nonvolatile Memory Max. Max. (mA) at 5V (mA) at 24V
1756-L55M12 750 Kbytes 208 Kbytes no 5.6 W 19.1 BTU/hr 1.23 A 0.014 A
1756-L55M13 1.5 Mbytes 208 Kbytes no 5.6 W 19.1 BTU/hr 1.23 A 0.014 A
1756-L55M14 3.5 Mbytes 208 Kbytes no 5.7 W 19.4 BTU/hr 1.25 A 0.014 A
7.5 Mbytes
1756-L55M16 208 Kbytes no 6.3 W 21.5 BTU/hr 1.48 A 0.014 A
≤ 3.5 Mbytes of data
1756-L55M22 750 Kbytes 208 Kbytes yes 5.6 W 19.1 BTU/hr 1.23 A 0.014 A
1756-L55M23 1.5 Mbytes 208 Kbytes yes 5.6 W 19.1 BTU/hr 1.23 A 0.014 A
1756-L55M24 3.5 Mbytes 208 Kbytes yes 5.7 W 19.4 BTU/hr 1.25 A 0.014 A
1756-L61 2 Mbytes 478 Kbytes CompactFlash card† 3.5 W 11.9 BTU/hr 1.20 A 0.014 A
1756-L62 4 Mbytes 478 Kbytes CompactFlash card† 3.5 W 11.9 BTU/hr 1.20 A 0.014 A
1756-L63 8 Mbytes 478 Kbytes CompactFlash card† 3.5 W 11.9 BTU/hr 1.20 A 0.014 A

✶Data and logic memory stores: tags other than I/O, produced, or consumed tags; logic routines; and communication with OPC/DDE tags that use RSLinx software (also uses I/O memory).
†I/O memory stores: I/O tags, produced tags, consumed tags, communication via MSG instructions, communication with workstations, and communication with OPC/DDE tags that use
RSLinx software (also uses data and logic memory).
‡The CompactFlash card is available separately as 1784-CF64.

The 1756-L6x controller executes ladder scans almost twice as fast as the 1756-L55
controllers and executes function block, REAL data type math, and motion instructions
4-5 times faster than the 1756-L55 controllers.

Selecting a controller for a redundant

controller system

If you are designing a redundant controller system, consider:

Redundant controller systems require a Logix5555 controller. (The
Logix5563 controller will support redundancy at a later release.)
Data is buffered in the secondary controller, so twice as much data memory
space is required in the controller.
The redundant controllers must be on a ControlNet network.

1756-SG001F-EN-P — June 2003

Determining The following equations provide an estimate of the memory needed for a controller.
These numbers are rough estimates.
Memory
Controller tasks _____ * 4000 = _____ bytes (minimum 1 task)
Requirements Digital I/O points _____ * 400 = _____ bytes
Analog I/O points _____ * 2600 = _____ bytes
Communication modules✶ _____ * 2000 = _____ bytes
Motion axes _____ * 8000 = _____ bytes

✶When estimating memory use by communication modules, count all the communication modules in the
system, not just those in the local chassis. This includes device connection modules, adapter modules,
and ports on PanelView terminals.

Controller memory boards

The 1756-L55 controllers do not operate stand-alone. Choose one of these memory
boards to come already assembled with the controller. You can also order additional
memory boards either for spare parts or to upgrade existing 1756-L55 controllers.

The 1756-L6x controllers have a fixed RAM size and do not use a memory board. Use
a CompactFlash card for nonvolatile storage. You must remove the controller from the
chassis to access the CompactFlash card.

Catalog Number: Supported Controller: Battery-Backed Static RAM: Nonvolatile RAM:

1756-M12✶ 1756-L55 750 Kbytes none
1756-M13 1756-L55 1.5 Mbytes none
1756-M14 1756-L55 3.5 Mbytes none
7.5 Mbytes
1756-M16 1756-L55 none
3.5 Mbytes for tag data
1756-M22✶ 1756-L55 750 Kbytes 750 Kbytes
1756-M23† 1756-L55 1.5 Mbytes 1.5 Mbytes
1756-M24† 1756-L55 3.5 Mbytes 3.5 Mbytes
same as the battery-backed static RAM limit for
1784-CF64 1756-L6x‡ none
the controller

✶The 1756-L55 controller must have firmware revision 10 or higher.

†The 1756-L55 controller must have firmware revision 8 or higher.
‡You can use CompactFlash with the 1756-L61, -L62, and -L63 controllers. The 1756-L61, -L62 controllers require firmware revision 12 or greater. The 1756-L63 controller requires firmware
revision 11 or higher.

Nonvolatile memory
The nonvolatile memory (flash) lets you permanently store a user program and tag
data 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

The 1756-L55M2x controllers have fixed internal nonvolatile memory.

The 1756-L6x controllers support a removable CompactFlash card for nonvolatile

memory. You install the 1784-CF64 card in the socket in the bottom of the controller.
You must remove the controller from the chassis to install CompactFlash.

On the 1756-L6x controlelrs, the CompactFlash card stores the user program, tag
data, and controller firmware. This lets a you upgrade the firmware on a 1756-L6x
controller without using RSlogx 5000 software or ControlFlash software.

1756-SG001F-EN-P — June 2003

Determining Battery Each controller ships with a 1756-BA1 battery. An externally mounted, higher capacity
battery module is also available (1756-BATM).
Requirements
Cat. No. Description Estimated Worst Case Battery Life @ 25C
with 1756-L55M12: 63 days
with 1756-L55M13: 63 days
Lithium battery (0.59g) installed in each ControlLogix controller.
1756-BA1 with 1756-L55M14: 30 days
Order only if you need a replacement.
with 1756-L55M16: 13 days
with 1756-L6x: 21 days
Externally mounted battery assembly.
Provides longer battery life than the 1756-BA1.

1756-BATM
Contains: with 1756-L55M12: 299 days
one 1756-BATA assembly with 1756-L55M13: 299 days
1m cable to connect housing to controller with 1756-L55M14: 213 days
with 1756-L55M16: 133 days
Highly recommended for all controllers (see chart below). with 1756-L6x: 146 days
Lithium battery assembly (maximum of 5g lithium per each D cell;
1756-BATA assembly contains 2 D cells) included with the 1756-BATM.
Order only if you need a replacement.

The 1756-BATM battery module is recommended for use with all 1756-L55 and
1756-L6x controllers.
If you order this controller: Order a 1756-BATM: Order a 1756-BATA: Order a 1756-BA1:
1756-L55M12 recommended for a replacement for a replacement
1756-L55M13 recommended for a replacement for a replacement
1756-L55M14 highly recommended for a replacement for a replacement
1756-L55M16 highly recommended for a replacement not recommended for long-term use
1756-L55M22✶ recommended for a replacement for a replacement

1756-L55M23✶ recommended for a replacement for a replacement

1756-L55M24✶ highly recommended for a replacement not recommended for long-term use
1756-L61† highly recommended for a replacement not recommended for long-term use
1756-L62† highly recommended for a replacement not recommended for long-term use
1756-L63† highly recommended for a replacement not recommended for long-term use

✶These controllers have nonvolatile memory and can be used without a battery.
†The 1756-L61, -L62, -L63 controllers have nonvolatile memory if you install a 1784-CF64 CompactFlash card. With nonvolatile memory, the controller can be used without a battery. If you do
not use a battery, current tag data will be at the state they were when the nonvolatile memory was saved.

1756-SG001F-EN-P — June 2003

Controlling Devices The ControlLogix controller can control these devices:

I/O Modules EtherNet/IP ControlNet DeviceNet Universal Remote I/O

1756 ControlLogix I/O yes yes no no
1794 FLEX I/O yes yes yes yes
1793 FLEX Integra I/O yes✶ yes✶ yes yes
1797 FLEX Ex I/O no yes no no
1734 POINT I/O yes yes yes no
1734D POINT Block I/O no no yes no
1769 Compact I/O no no yes no
1790 Compact LDX I/O no no yes no
1791 Block I/O no no no yes
1791D CompactBlock I/O no no yes no
1792 ArmorBlock I/O no no yes no
1798 FlexArmor I/O no no yes no
1799 Embedded I/O no no yes no
1747 SLC I/O no no yes
1771 I/O no yes† no yes

✶Requires RSLogix 5000 programming software version 11 or greater. Use the generic FLEX profile.
†Use a 1771-ACN15, -ACNR15 adapter module. Version 10 and later of RSLogix 5000 Enterprise Series software supports 1771 digital, analog, and specialty I/O modules. Previous versions of
the software support only 1771 digital I/O modules.

Universal Remote
Display Devices EtherNet/IP ControlNet DeviceNet DH+ I/O RS-232 (DF1) DH-485
2711P PanelView Plus
yes yes yes yes yes yes no✶
terminal
6182H VersaView CE
yes yes yes yes yes yes no✶
computer
2711 PanelView
yes yes yes yes† yes yes† yes†
terminal
2711 e PanelView
no yes no yes† yes no no
terminal
2705
RediSTATION/RediPANE no no yes no yes no no
L operator module
2706 InView message
yes yes yes yes yes yes yes
display
2706 DL40 Dataliner
no no no no yes yes no
message display
2706 DL, DL50
DataLiner message no no no no no yes no
display
2707 DTAM Plus
no no yes no yes yes† yes†
operator interface

✶These devices support DH-485 communication to FlexLogix and CompactLogix controllers.

†Use PLC/SLC mapping.

1756-SG001F-EN-P — June 2003

Communicating The ControlLogix system takes advantage of several networks to allow communications
with many different controllers and devices. The following table lists which products
with Other the ControlLogix controller can communicate with over which networks.
Controllers and
Communication
Devices
Controller EtherNet/IP ControlNet DeviceNet DH+ RS-232 (DF1) DH-485
1756 ControlLogix
yes yes yes yes yes yes
controller
1769 CompactLogix
yes no yes no yes yes
controller
1789 SoftLogix5800
yes yes yes no yes no
controller
1794 FlexLogix controller yes yes yes no yes yes
5720 PowerFlex 700S with
yes yes yes no yes yes
DriveLogix
1785 PLC-5 controller yes✶† yes yes‡ yes yes na
1747 SLC controller yes§ yes yes♣ yes♣ yes no
1761 MicroLogix controller yes no yes♣ no yes no
1762 MicroLogix controller yes no yes♣ no yes no
1769 MicroLogix controller yes no yes♣ no yes no
1772 PLC-2 controller na na na yes➤ yesz na
1775 PLC-3 controller na na na yesª yesv na
5250 PLC-5/250 controller na na no yes yes na

✶The Ethernet PLC-5 processor must be one of these:

series C, revision N.1 or later
series D, revision E.1 or later
series E, revision D.1 or later
†The 1785-ENET Ethernet communication interface module must be series A, revision D or later.
‡The PLC-5, SLC, and MicroLogix processors appear as I/O points to the Logix controller. Requires 1761-NET-DNI DeviceNet interface.
§Use a 1747-L55x controller with OS501 or greater.
♣Use a 1747-L54x controller.
➤The PLC-2 controller requires a 1785-KA module for DH+ communications.
zThe PLC-2 controller requires a 1771-KG module for serial (DF1) communications.
ªThe PLC-3 controller requires a 1775-S5 module for DH+ communications.
vThe PLC-3 controller requires a 1775-KA module for serial (DF1) communications.

Communication Device EtherNet/IP ControlNet DeviceNet DH+ RS-232 (DF1) DH-485

9355 RSLinx software yes yes no yes yes no
1784-KTC, -KTCx, -KTCx15,
na yes na na na na
-PCIC(S), -PCC
1784-PCIDS, -PCD na na yes na na na
1784-KTX, -KTXD, -PCMK na na na yes na na
1788-CN2DN na yes yes na na na
1788-EN2DN yes na yes na na na
1788-CN2FF na yes na na na na
1203-CN1 ControlNet
na yes✶ na na na na
module
1203-FM1/FB1 SCANport na yes† na na na na

✶Use the generic module configuration to configure the 1203-CN1 module and a CIP generic MSG instruction to communicate with the module.
†Use a CIP generic MSG instruction to communicate with the 1203-FM1 SCANport module on a DIN rail that is remote to the controller. The remote DIN rail also requires a 1794-ACN(R)15
ControlNet adapter module.

1756-SG001F-EN-P — June 2003

Communicating The ControlLogix system takes advantage of several networks to allow communications
with many different drives, both motion (servo) drives and standard drives. The
with Drives following table lists which drives the ControlLogix controller can communicate with
over which networks.

Motion (Servo) Drives✶ EtherNet/IP ControlNet DeviceNet DH+ RS-232 DH-485

1394 GMC drive and
no no no yes yes yes
control
1398 ULTRA 100 series
no no yes no no no
drive
2098 Ultra3000 DeviceNet
no no yes no no no
servo drive
2098 Ultra5000 intelligent
no no yes no yes no
positioning

Standard Drives✶ EtherNet/IP ControlNet DeviceNet DH+ RS-232 DH-485

1305 adjustable frequency
no yes yes yes yes yes
ac drive
1336 adjustable frequency
no yes yes yes yes yes
ac drive
1395 digital dc drive no yes no yes yes no
FlexPak 3000 dc drive no yes yes no yes no
WebPak 3000 dc winder no yes no no yes no
GV3000 ac drive no yes yes no yes no
PowerFlex 40 ac drive no no yes no yes yes
PowerFlex 70, 700, 700S,
yes yes yes yes yes yes
and 7000 ac drive

1756-SG001F-EN-P — June 2003

How a Logix A Logix controller uses three types of tasks. Use the following table to choose the
appropriate type of task for each section of your logic.
System Uses Tasks
If you want to execute a section of your
logic: Then use this type of task: Description:
The continuous task runs in the background. Any CPU time not allocated to other operations (such
as motion, communications, and periodic or event tasks) is used to execute the programs within the
all of the time continuous task.
Continuous Task
The continuous task runs all the time. When the continuous task completes a full scan, it restarts
immediately.
A project does not require a continuous task. If used, there can be only one continuous task.
A periodic task performs a function at a specific period.
Whenever the time for the periodic task expires, the task interrupts any lower priority tasks,
at a constant period (e.g., every 100 ms)
executes one time, and then returns control to where the previous task left off.
multiple times within the scan of your other
Periodic Task. You can configure the time period from 0.1 ms to 2000 msec. The default is 10 ms. It is also
logic
controller and configuration dependent.
The performance of a periodic task depends on the type of Logix controller and on the logic in the
task.
An event task performs a function only when a specific event (trigger) occurs.

The trigger for the event task can be:

change of a digital input
new sample of analog data
certain motion operations
Event Task
immediately when an event occurs consumed tag
EVENT instruction

Whenever the trigger for the event task occurs, the event task:
interrupts any lower priority tasks
executes one time
returns control to where the previous task left off

Event tasks
Several factors affect the closed-loop event throughput:
input module type, filter time, and response time
backplane size and loading
controller type, configuration, and loading
output module type and response time

1756-SG001F-EN-P — June 2003

To use a device to trigger an event task, the device must support event task triggering.
If the device is in a remote location, the associated communication modules must also
support event triggering. These devices support input events:
Category Modules
1756-IA16
1756-IA16I
1756-IA8D
1756-IB16
1756-IB16D
1756-IB16I
1756-IB32/A
Digital I/O modules that support change of state
1756-IB32/B
1756-IC16
1756-IH16I
1756-IM16I
1756-IN16
1756-IV16/A
1756-IV32/A
1756-IF16
1756-IF4FXOF2F/A
1756-IF6CIS
1756-IF6I
Analog I/O modules that support real time sample
1756-IF8
1756-IR6I
1756-IT6I
1756-IT6I2
1756-CFM/A
Specialty I/O modules 1756-HSC
1756-PLS/B
1756-CNB/A
1756-CNB/B
1756-CNB/D
1756-CNBR/A
Communication modules that provide rack-optimized 1756-CNBR/B
connections 1756-CNBR/D
1756-DNB
1756-ENBT/A
1756-SYNCH/A
1784-PCIDS/A
1756-MODULE
Generic I/O modules that conform to CIP event communications
1789-MODULE

When planning for event tasks, consider these recommendations:

Recommendation Details
Placing a module in a remote chassis adds additional network communications and processing to the
Place the module that triggers an event in the same chassis as the controller.
response time.
Limit number of modules in the chassis with the event module and the controller. Additional modules increases the potential for backplane delays.
All inputs on a module trigger a single event so using multiple bits increases the chances of a task
Limit events on digital inputs to a single input bit on a module. overlap. Configure the module to explicitly detect change-of-state on the input and turn off the other
bits.
Setting an event task at a lower priority than a periodic task will force the event task to wait for the
The priority of the event task should be set as the highest priority on the controller.
periodic task to complete execution.
Increasing the number of event tasks reduces the available CPU bandwidth and increases the chance
Limit the number of event tasks.
of a task overlap.
The 1756-IB32/B and 1756-IF4FXOF2F are recommended for digital and analog events. These modules have the best response times.

1756-SG001F-EN-P — June 2003

Estimating event task throughput

To estimate the throughput time from input to output (screw to screw), use the
following worksheet:
Consideration: Value (in µs):
1. What is the input filter time of the module that triggers the event task?

This is typically shown in milliseconds, Convert it to microseconds (µs).

2. What is the hardware response time for the input module that triggers the event task?

Make sure you use the appropriate type of transition (Off to On or On to Off). See the following table.
3. What is the backplane communication time?

If the chassis size is: Use this value (worst case):

4 slot 13 µs
7 slot 22 µs
10 slot 32 µs
13 slot 42 µs
17 slot 54µs
4. What is the total execution time of the programs in the event task?
5. What is the backplane communication time (same value as step 3).
6. What is the hardware response time of the output module?
7. Add steps 1 through 6. This is the minimum estimated throughput, where execution of the motion planner or other tasks do not delay or interrupt the
event task.
8. What is the scan time of the motion group?
9. What is the total scan time of the tasks that have a higher priority than this event task (if any)?
10. Add steps 7 through 9. This is the nominal estimated throughput, where execution of the motion planner or other tasks delay or interrupt the event task.

Use the following table to determine the nominal hardware response time for selected
1756 I/O modules.
Nominal reponse time µs:
25° C 60° C
Module: Off to On On to Off Off to On On to Off
1756-IB16 265 582 265 638
1756-IB16D 303 613 305 673
1756-IB32/B 330 359 345 378
1756-IV16 257 435 254 489
1756-IV32 381 476 319 536
1756-OB16D 48 519 51 573
1756-OB16E 60 290 61 324
1756-OB32 38 160 49 179
1756-OV16E 67 260 65 326
1756-OV32E 65 174 66 210

1756-SG001F-EN-P — June 2003

Determining The controller supports the ability to produce (broadcast) and consume (receive)
system-shared tags. Produced and consumed tags each require connections. Over
Connections for ControlNet, produced and consumed tags are scheduled connections.
Produced and
Consumed Tags
This type of tag: Requires these connections:
A produced tag allows other controllers to consume the tag, which means that a controller can receive the tag data from another controller. The local
controller (producing) uses one connection for the produced tag and one connection for each consumer. The controller’s communication device uses
produced one connection for each consumer.
As you increase the number of controllers that can consume a produced tag, you also reduce the number of connections the controller and
communication device have available for other operations, like communications and I/O.
Each consumed tag requires one connection for the controller that is consuming the tag. The controller’s communication device uses one connection for
consumed
each consumer.

For two controllers to share produced or consumed tags, both controllers must be
attached to the same control network (such as a ControlNet or Ethernet/IP network).
You cannot bridge produced and consumed tags over two networks.

The total number of tags that can be produced or consumed is limited by the number
of available connections. If the controller uses all of its connections for I/O and
communication devices, no connections are left for produced and consumed tags.
ControlLogix controllers can produce and consume tags over:
the ControlLogix backplane
a ControlNet network
an EtherNet/IP network

Maximum number of produced and

consumed tags
The controller supports:
As a: The controller supports:
producer (number of produced tags) ≤ 127
consumer (number of consumed tags) ≤ 250

The total combined consumed and produced tags that a controller supports is (this is
also the maximum number of connections):

(number of produced tags) + (number of consumed tags) ≤ 250

1756-SG001F-EN-P — June 2003

How a Logix A Logix system uses a connection to establish a communication link between two
devices. Connections can be:
System Uses controller to local I/O modules or local communication modules
Connections 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.
Connections are allocations of resources that provide more reliable communications
between devices than unconnected messages. A Logix system supports both scheduled
and unscheduled connections and unconnected messages.

Method Description
A scheduled connection is unique to ControlNet communications. A scheduled connection lets you send and receive data repeatedly at a
predetermined interval, which is the requested packet interval (RPI). For example, a connection to an I/O module is a scheduled
connection because you repeatedly receive data from the module at a specified interval. Other scheduled connections include
scheduled connection
connections to:
level of determinism
communication devices
unique to ControlNet
produced/consumed tags
On a ControlNet network, you must use RSNetWorx for ControlNet to enable all scheduled connections and establish a network update
time (NUT).
unscheduled connection An unscheduled connection is a message transfer between controllers that is triggered by the requested packet interval (RPI) or the
deterministic program (such as a MSG instruction). Unscheduled messaging lets you send and receive data when needed.
used by both ControlNet and EtherNet/IP All EtherNet/IP connections are unscheduled.
unconnected message An unconnected message is a message that does not require connection resources. An unconnected message is sent as a single
least deterministic request/response.

The communication module you select determines the number of connections you
have available for I/O and messages.

This communication module: Supports this number of connections:

64
1756-CNB
(any combination of scheduled and unscheduled)
128
1756-ENBT (any combination of scheduled and unscheduled)
The EtherNet/IP module does not distinguish between scheduled and unscheduled connections.

How you configure connections determines how many remote devices a

communication card can support.

1756-SG001F-EN-P — June 2003

Depending on the type of I/O modules, both direct connections and rack-optimized
connections can be used.
I/O System Supported Connection Type(s):
1756 basic digital I/O in a local chassis direct connection
direct connection
digital I/O in a remote chassis via ControlNet or
rack-optimized connection✶
analog I/O either in a local chassis or in a remote chassis via ControlNet direct connection
direct connection
digital I/O in a remote chassis via EtherNet/IP or
rack-optimized connection✶
analog I/O in a remote chassis via EtherNet/IP direct connection
digital I/O via Universal Remote I/O rack-optimized connection
analog I/O via Universal Remote I/O direct connection via messaging
1771 analog I/O via ControlNet direct connection via messaging
DeviceNet I/O rack-optimized connection

✶Rack-optimized connections for diagnostic and E-fuse modules do not send diagnostic or fuse data to controller.

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. The control network can be either
an EtherNet/IP or ControlNet network.

The local controller in this example uses these connections:

Connection Type Module Quantity Connections per Module Total Connections
controller to local I/O module 2 1 2
controller to remote I/O module 3 1 3
controller to remote communication module✶ 1 0 0
total 5

✶The control network can be an Ethernet/IP or ControlNet network.

Because all the remote I/O modules are configured for direct connections, configure
the remote communication module for “none,” which results in no connection.

1756-SG001F-EN-P — June 2003

Determining Messages transfer data to other devices, such as other controllers or operator
interfaces. Some messages use unscheduled connections to send or receive data.
Connections for These connected messages can leave the connection open (cache) or close the
Messages connection when the message is done transmitting. The following table shows which
messages use a connection and whether or not you can cache the connection:
This type of message: Using this communication method: Uses a connection:
CIP data table read or write CIP ü
CIP
PLC2, PLC3, PLC5, or SLC (all types) CIP with Source ID
DH+ ü
CIP generic CIP your option✶
block-transfer read or write na ü

✶You can connect CIP generic messages, but for most applications we recommend you leave CIP generic messages unconnected.

Connected messages are unscheduled connections on both ControlNet and

EtherNet/IP networks.

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.

Determining A Logix system uses connections to transmit I/O data. These connections can be direct
connections or rack-optimized connections. Over ControlNet, I/O connections are
Connections for I/O scheduled connections:
Modules
Connection 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
direct
module while under power, causes the controller to set fault status bits in the data area associated with the module.
Typically, analog I/O modules and specialty modules require direct connections.
For digital I/O modules, you can select rack optimized communication. A rack optimized connection consolidates connection usage
between the controller and all the digital I/O modules on a rack (or DIN rail). Rather than having individual, direct connections for
rack-optimized
each I/O module, there is one connection for the entire rack (or DIN rail).
The 32-point FLEX I/O modules do not support rack-optimixed connections and require direct connections.

1756-SG001F-EN-P — June 2003

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 remote chassis.

The local controller in this example uses these connections:

Connection Type Module Quantity Connections per Module Total Connections
controller to local I/O module 2 1 2
controller to remote analog I/O module 1 1 1
controller to remote communication module✶
1 1 1
(rack-optimized connection for the digital I/O)
total 4

✶The control network can be an Ethernet/IP or ControlNet network.

Because all the remote I/O modules are configured for direct connections, configure
the remote communication module for “none,” which results in no connection.

Rack-optimized connections for 1756

I/O modules
Using the same configuration as 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 remote connection (EtherNet/IP or ControlNet communication module). 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 Module Quantity Connections per Module Total Connections
controller to local I/O module 2 1 2
controller to remote communication module✶ 1 1 1
total 3

✶The control network can be an Ethernet/IP or ControlNet network.

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.

1756-SG001F-EN-P — June 2003

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 a rack-optimized connection.

The local controller in this example uses these connections:

Connection Type Module Quantity Connections per Module Total Connections

controller to local I/O module 2 1 2
controller to remote communication module 1 1 1
controller to remote 1756-DHRIO module 1 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.

1756-SG001F-EN-P — June 2003

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.

The local controller in this example uses these connections:

Connection Type Module Quantity Connections per Module Total Connections
controller to local I/O module 2 1 2
controller to remote communication module 1 1 1
controller to remote 1756-DNB module
(rack-optimized connection for DeviceNet 1 2 2
devices)
total 5

The 1756-DNB module does not establish connections to its devices; and therefore,
the controller doesn’t establish connections with DeviceNet devices. The 1756-DNB
module acts as a scanner that gathers all the data from its devices and packs that data
together into one image that is passed to the controller. However, the controller can
use a MSG instruction to get information directly to or from a DeviceNet device.

1756-SG001F-EN-P — June 2003

Determining Total The ControlLogix controller supports 250 connections. To calculate the total
connections for a controller, consider the connections to local I/O modules and the
Connection connections to remote modules.
Requirements
Use the following table to tally local connections:
Connection Type Device Quantity Connections per Device Total Connections
local I/O module (always a direct connection) 1
1756-M16SE, -M08SE, -M02AE servo module 3
1756-CNB, -CNBR communication module 0
1756-ENBT communication module 0
1756-DNET communication module 2
1756-DHRIO communication module 1

Regardless of how you configure local I/O modules (rack-optimized or direct

connect), the controller establishes a direct connection for each local I/O module.

Remote connections depend on the communication module. The number of

connections the module itself supports determines how many connections the
controller can access through that module. Use the following table to tally remote
connections for the controller:
Connection Type Device Quantity Connections per Device Total Connections
remote 1756-CNB, -CNBR ControlNet
communication module 0 or
configured as a direct (none) connection 1
configured as a rack-optimized connection
remote I/O module over ControlNet (direct
1
connection)
remote 1756-ENBT Ethernet communication
module 0 or
configured as a direct (none) connection 1
configured as a rack-optimized connection
remote I/O module over EtherNet/IP (direct
1
connection)
remote device over DeviceNet
(accounted for in rack-optimized connection for 0
local 1756-DNB module)
other remote communication adapter 1
produced tag 1
each consumer 1
consumed tag 1
cached message 1
block-transfer message 1
total

1756-SG001F-EN-P — June 2003

Step 5 - Select:
a chassis with sufficient slots Selecting Chassis
1756-N2 filler strips for empty slots

The ControlLogix system is a modular system that requires a 1756 I/O chassis to
contain the various modules. Chassis are available in sizes of 4, 7, 10, 13, and 17
module slots. You can place any module into any slot.

The backplane provides a high-speed communication path between modules. Multiple

controller modules on the backplane can pass messages between one another. With
multiple communication interface modules on the backplane, a message can be sent
from across a link into a port on one module, routed across the backplane and out
another module’s port, and sent across another link to its ultimate destination.

Minimum Cabinet Size Maximum Backplane Current

Cat. No. Slots Weight Dimensions (HxWxD) (HxWxD) Load
137 x 263 x 145 mm 508 x 508 x 203 mm
1756-A4/B 4 0.75 kg (1.7 lb)
(5.4 x 10.4 x 5.8 in) (20 x 20 x 8 in)
137 x 368 x 145 mm 508 x 610 x 203 mm
1756-A7/B 7 1.10 kg (2.4 lb)
(5.4 x 14.5 x 5.8 in) (20 x 24 x 8 in)
4.0A @ 3.3V dc
137 x 483 x 145 mm 508 x 762 x 203 mm
1756-A10/B 10 1.45 kg (3.2 lb) 15.0A @ 5V dc
(5.4 x 19.0 x 5.8 in) (20 x 30 x 8 in)
2.8A @ 24V dc
137 x 588 x 145 mm 610 x 762 x 203 mm
1756-A13/B 13 1.90 kg (4.2 lb)
(5.4 x 23.2 x 5.8 in) (24 x 30 x 8 in)
137 x 738 x 145 mm 762 x 914 x 203 mm
1756-A17/B 17 2.20 kg (4.8 lb)
(5.4 x 29.1 x 5.8 in) (30 x 36 x 8 in)

Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM

All the chassis are designed for back-panel mounting. Use the slot filler module
1756-N2 to fill empty slots.

1756-SG001F-EN-P — June 2003

When you mount a chassis in an enclosure, make sure to meet these minimum
spacing requirements:

Mounting dimensions
right-side view of all chassis

1756-A4 with power supply

1756-SG001F-EN-P — June 2003

1756-A7 with power supply

1756-A10 with power supply

1756-SG001F-EN-P — June 2003

1756-A13 with power supply

1756-A17 with power supply

1756-SG001F-EN-P — June 2003

Step 6 - Select:
one power supply for each chassis Selecting Power Supplies
a power supply bundle if you are planning
a redundant power supply system
ControlLogix power supplies are used with the 1756 chassis to provide 1.2V, 3.3V, 5V,
and 24V dc power directly to the chassis backplane. Non-redundant (1756-PA72, -
PB72, -PA75, -PB75) and redundant (1756-PA75R, -PB75R) power supplies are
available.
Power Supplies Adapter
Specification 1756-PA72 1756-PA75 1756-PA75R 1756-PB72 1756-PB75 1756-PB75R 1756-PSCA
Nominal Input Voltage 120V ac or 220V ac 24V dc
Input Voltage Range 85-265V ac 19.2-32V dc
Maximum Real Input Power 95W 115W 97W 110W
Maximum Apparent Input Power 240VA 120VA na
Maximum Transformer Load 238VA 120VA na
Frequency 47-63 Hz dc
1.5A @ 1.2V dc 1.5A @ 1.2V dc 1.5A @ 1.2V dc 1.5A @ 1.2V dc na
4A @ 3.3V dc 4A @ 3.3V dc 4A @ 3.3V dc 4A @ 3.3V dc
Maximum Backplane Output Current 10A @ 5V dc 13A @ 5V dc 10A @ 5V dc 13A @ 5V dc
2.8A @ 24V dc 2.8A @ 24V dc 2.8A @ 24V dc 2.8A @ 24V dc
75W total 75W total 75W total 75W total

2 cycles
19V dc: 20mS
Hold Up Time✶ 120V ac: 6 cycles
24V dc: 70mS
220V ac: 20 cycles

series A series A
Chassis Compatibility series B series B series B series B series B
series B series B
Location left side of chassis panel mounted† left side of chassis panel mounted† left side of chassis

Certifications: UL, CSA (Class I, Division 2, Group A, B, C, D), CE, FM, C-Tick
✶The hold up time is the time between input voltage removal and dc power failure.
†This can be a maximum of 0.91 cable-metered (3 cable feet) from the ControlLogix chassis.

Selecting a non-redundant power supply

You mount a non-redundant power supply directly on the left end of the chassis,
where it plugs directly into the backplane. The power supply you select can determine
which chassis you can use.

1756-SG001F-EN-P — June 2003

Selecting a redundant power supply

To build a redundant power supply system, you need:

two redundant power supplies (both 1756-PA75R or 1756-PB75R)
one 1756-PSCA chassis adapter module
two 1756-CPR cables to connect the power supplies to the 1756-PSCA chassis
adapter module (3ft maximum length)
user-supplied annunciator wiring to connect the power supplies to the input
modules, as needed

The 1756-PSCA chassis adapter module is a passive device that funnels power from
the redundant power supplies to the single power connector on the ControlLogix
series B chassis backplane.

The redundant power supplies are available in ac (1756-PA75R) and dc (1756-

PB75R) versions. They are also available in bundled systems:
Redundant Power Supply Bundle Contents
two 1756-PA75R power supplies
1756-PAR two 1756-CPR cables
one 1756-PSCA chassis adapter module
two 1756-PB75R power supplies
1756-PBR two 1756-CPR cables
one 1756-PSCA chassis adapter module

1756-SG001F-EN-P — June 2003

Power Each ac-input power supply generates a shutdown signal on the backplane whenever
the ac line voltage drops below its lower voltage limit. It removes the shutdown signal
Requirements and when the line voltage comes back up to the lower voltage limit. This shutdown is
Transformer Sizing necessary to help ensure that only valid data is stored in memory.

The external transformer rating (in VA) of each power supply is greater than its real
input power (in Watts) because a capacitor-input ac/dc supply draws power only from
the peak of the ac voltage wave form. If the transformer is too small, it clips the peak
of the sine wave; when the voltage is still above the lower voltage limit, the power
supply will sense this clipped wave form as low voltage and could prematurely shut
down modules in the chassis.

The following graphs display the backplane power load on the vertical axis. Since
these supplies have multiple outputs, the backplane power load is given in watts.
Use the real power value in watts for determining the amount of heat
dissipation you will have inside the enclosure.
Use the apparent power value in VA for estimating power distribution sizing.
Use the transformer load value in VA of each power supply plus all other loads
on a transformer to determine the required transformer size.

1756-SG001F-EN-P — June 2003

Power load and transformer sizing

1756-SG001F-EN-P — June 2003

Step 7 - Select:
the appropriate package of RSLogix 5000 Selecting Software
Enterprise Series software and any options

other software packages for your Your selection of modules and network configuration determines what software
application packages you need to configure and program your system.

If you have a: You need: Order this catalog number:

1756 ControlLogix controller 9324 series
RSLogix 5000 Enterprise Series software
1756-M16SE, -M08SE, -M02AE motion module (RSLogix 5000 Enterprise Series software)
9324-RLD300NXENE (RSLogix 5000 Enterprise Series software plus
RSNetWorx for ControlNet
RSNetWorx option)
1756-CNB, -CNBR ControlNet communication module (comes with the standard/NetWorx option of RSLogix 5000 Enterprise
or
Series software)
9357-CNETL3 (RSNetWorx for ControlNet)
9324-RLD300NXENE (RSLogix 5000 Enterprise Series software plus
RSNetWorx for DeviceNet
RSNetWorx option)
1756-DNB DeviceNet communication module (comes with the standard/NetWorx option of RSLogix 5000 Enterprise
or
Series software)
9357-DNETL3 (RSNetWorx for DeviceNet)
1756-ENBT, -ENET EtherNet/IP communication module
(set the IP address) RSLinx software
9324 series
(RSLinx Lite and Bootp server come with RSLogix 5000 Enterprise
1756-DHRIO communication module (RSLogix 5000 Enterprise Series software)
Series software)
(define the DH+ routing table)
Foundation Fieldbus Configuration Software 1788-FFCT
1788-CN2FF FoundationFieldbus linking device and and
RSLinx or RSLinx OEM software (RSLinx Lite is not sufficient) 9355-WABENE or 9355-WABOEMENE
RSLinx software 9324 series
communication card in a workstation
(RSLinx Lite comes with RSLogix 5000 Enterprise Series software) (RSLogix 5000 Enterprise Series software)
Logix-based system you want to emulate RSLogix Emulate 5000 9310-WED200ENE
Logix-based system for which you want training RSTrainer 2000 for ControlLogix Fundamentals 9393 series
operator interface RSView Enterprise series software ViewAnyWare products

1756-SG001F-EN-P — June 2003

Programming RSLogix 5000 Enterprise Series software is designed to work with Rockwell
Automation’s Logix platforms. RSLogix 5000 Enterprise Series software is an
Software IEC 61131-3 compliant software package that offers relay ladder, structured text,
function block diagram, and sequential function chart editors for you to develop
application programs. RSLogix 5000 Enterprise Series software also includes axis
configuration and programming support for motion control.

RSLogix 5000 Enterprise Series software requirements

Description Value
Pentium II 450 MHz minimum
personal computer
Pentium 3 733 MHz (or better) recommended
Supported operating systems:
Microsoft Windows XP Professional version 2002 (with Service Pack 1) or XP Home version 2002
software requirements
Microsoft Windows 2000 Professional with Service Pack 1, 2, or 3
Microsoft Windows NT version 4.0 with Service Pack 5 or 6A
128 Mbytes of RAM minimum
RAM
256 Mbytes of RAM recommended
100 Mbytes of free hard disk space
hard disk space
(or more based on application requirements)
256-color VGA graphics adapter
video requirements
800 x 600 minimum resolution (True Color 1024 x 768 recommended)

1756-SG001F-EN-P — June 2003

Selecting the programming package

Select the RSLogix 5000 Enterprise Series software package and options you need:

Service 9324- Standard 9324- Standard/NetWorx Professional 9324-

Available Features RLD000xxE✶† Mini 9324-RLD200xxE† RLD300xxE† 9324-RLD300NXxxE† Full 9324-RLD600ENE‡ RLD700NXxxE†
Logix5000 controllers CompactLogix5300
all all all all all
supported FlexLogix5400
Relay ladder editor§ view only fully supported fully supported fully supported fully supported fully supported
Function block diagram
editor
upload/download only upload/download only upload/download only
(includes ActiveX view only fully supported fully supported
available separately available separately available separately
faceplates)
9324-RLDFBDENE§
Sequential function chart
upload/download only upload/download only upload/download only
editor view only fully supported fully supported
available separately available separately available separately
9324-RLDSFCE§
Structured text editor upload/download only upload/download only upload/download only
view only fully supported fully supported
9324-RLDSTXE§ available separately available separately available separately
Highly-integrated motion view only upload/download only fully supported fully supported fully supported fully supported
Graphical trending fully supported na fully supported fully supported fully supported fully supported
DriveExecutive™ Lite
available separately available separately included included included included
9303-4DTE01ENE
RSView demo (50 tags/2
available separately available separately available separately available separately available separately included
hours)
PIDE autotune
available separately available separately available separately available separately available separately included†
9323-ATUNEENE
RSLinx Lite included Lite included Lite included Lite included Lite included Professional included
RSNetWorx for ControlNet
RSNetWorx for DeviceNet
available separately available separately available separately included available separately included
RSNetWorx for
EtherNet/IP➤
RSLogix Emulate 5000 and
RSTestStand Lite available separately available separately available separately available separately available separately included
9310-WED200ENE
RSMACC support na na na na na available separately
Service to Standard: Mini to Standard:
9324-RLD0U3xxE 9324-RLD2U3xxE
Service to Full: Mini to Full: Standard to Professional: Full to Professional:
Upgrades none♣ na
9324-RLD0U6xxE 9324-RLD2U6xxE 9324-RLD3U7xxE♣ 9324-RLD6U7xxE
Service to Professional: Mini to Professional:
9324-RLD0U7xxE 9324-RLD2U7xxE

✶Available as of RSLogix 5000 programming software version 12.

†Replace “xx” in the catalog number with the appropriate language designation: EN=English, FR=French, DE=German, IT=Italian, PT=Portuguese, and ES=Spanish.
‡Available as of RSLogix 5000 programming software version 10.02.
§A multiple language editor package is available as 9324-RLDMLPE. It contains the function block, sequential function chart, and structured text editors at a reduced price.
♣The multiple language editor package (9324-RLDMLPE) is not the same as an upgrade, but it extends the programming languages to match those in a Full package.
➤RSNetWorx for ControlNet is available as 9357-CNETL3. RSNetWorx for DeviceNet is available as 9357-DNETL3. RSNetworx for EtherNet/IP is available as 9357-ENETL3. They are available
together as 9357-ANETL3.

1756-SG001F-EN-P — June 2003

RSLinx Software RSLinx software (9355 series) is a communication server package that provides plant-
floor device connectivity for a wide variety of applications. RSLinx can support
multiple software applications simultaneously communicating to a variety of devices
on many different networks.

RSLinx provides a user-friendly graphical interface for navigating through your

network. Select a device and click to access a variety of integrated configuration and
monitoring tools. A complete set of communication drivers is provided for your
networking needs, including legacy Allen-Bradley networks.

RSLinx is available in multiple packages to meet the demand for a variety of cost and
functionality requirements.

RSLinx system requirements

Description Value
Pentium100 MHz processor
personal computer
(faster processors will improve performance)
Supported operating systems:
Microsoft Windows XP
Microsoft Windows 2000
operating system
Microsoft Windows NT version 4.0 with Service Pack 3 or greater
Microsoft Windows ME
Microsoft Windows 98
32 Mbytes of RAM minimum
RAM
64 Mbytes or more of RAM recommended
35 Mbytes of free hard disk space
hard disk space
(or more based on application requirements)
16-color VGA graphics display
video requirements
800 x 600 or greater resolution

In most cases, RSLinx Lite software comes bundled with controller programming
software packages.

1756-SG001F-EN-P — June 2003

Network RSNetWorx software for ControlNet (9357-CNETL3) and RSNetWorx software for
DeviceNet (9357-DNETL3) are the configuration and scheduling tools for your
Configuration ControlNet or DeviceNet networks. RSNetWorx software lets you create a graphical
Software representation of your network configuration and configure the parameters that define
your network.

RSNetWorx for ControlNet software schedules network components. The software

automatically calculates network bandwidth for the entire network, as well as the
bandwidth used by each network component. You must have RSNetWorx software to
configure and schedule the ControlNet networks in your ControlLogix system.

RSNetWorx for DeviceNet software configures the DeviceNet I/O devices and creates
the scan list. The DeviceNet scanner stores the configuration information and scan list.

RSNetWorx system requirements

Description ControlNet DeviceNet EtherNet/IP

personal computer Intel Pentium or Pentium-compatible computer
Supported operating systems:
Microsoft Windows XP
Microsoft Windows 2000
operating system Microsoft Windows 2000 Terminal Server
Microsoft Windows NT version 4.0 with Service Pack 6 or greater
Microsoft Windows ME
Microsoft Windows 98
32 Mbytes of RAM minimum
RAM
more memory is required for large networks
minimum: 115 Mbytes (includes program files and minimum: 190 Mbytes (includes program files and minimum: 108 Mbytes (includes program files and
hardware files) hardware files) hardware files)
hard disk space
full support: 168...193 Mbytes (includes program files, full support: 230...565 Mbytes (includes program files, full support: 115...125 Mbytes (includes program files,
online help, tutorial, and hardware files) online help, tutorial, and hardware files) online help, tutorial, and hardware files)
16-color VGA graphics adapter
video requirements 640 x 480 resolution minimum
800 x 600 resolution recommended
other RSLinx Lite 2.4 or later to use RSNetWorx online RSLinx Lite 2.4 or later to use RSNetWorx online RSLinx Lite 2.41 or later to use RSNetWorx online

In most cases, RSNetWorx software comes bundled with controller programming

software packages.

1756-SG001F-EN-P — June 2003

RSLogix Emulate RSLogix Emulate 5000 (9310-WED200ENE) is the software emulation package for the
Logix5000 controllers. RSLogix Emulate 5000 used in conjunction with RSLogix 5000
5000 Software software lets you run and debug your application code while at your computer. In
addition, RSLogix Emulate 5000 also lets you test HMI screens, developed in RSView
for example, without the need to connect to a real controller.

By using RSLogix Emulate 5000, you can eliminate the cost for dedicated test ware,
improve your productivity, and reduce the time to market of your products.

RSLogix Emulate 5000 gives you enhanced debug capabilities. You can set tracepoint
and breakpoint instructions (ladder diagram only) in your application code, use
traces, and also vary the execution speed of the emulator. RSLogix Emulate 5000
supports all the programming languages (ladder diagram, function block diagram,
structured text, and sequential function chart). RSLogix Emulate 5000 does not allow
for control of real I/O.

RSLogix Emulate 5000 system requirements

Description Value
IBM-compatible Intel Pentium II 300 MHz or Celeron 300A
personal computer
(Pentium III 600 MHz recommended)
Supported operating systems:
Microsoft Windows XP with Service Pack 1or greater
operating system
Microsoft Windows 2000 with Service Pack 2 or greater
Microsoft Windows NT version 4.0 with Service Pack 6A or greater
RAM 128 Mbytes of RAM minimum
hard disk space 50 Mbytes of free hard disk space
16-color VGA graphics display
video requirements
800 x 600 or greater resolution

RSLogix Emulate 5000 includes RSTestStand Lite. RSTestStand Lite lets you create
virtual operator consoles that can help test your application code. RSTestStand Lite
can be upgraded to the standard version by ordering catalog number 9310-
TSTNDENE.

RSLogix Emulate 5000 and RSTestStand Lite are included with the RSLogix 5000
Professional edition.

1756-SG001F-EN-P — June 2003

Logix-Based Rockwell Automation offers several different levels of training for your Logix system.
While most of these training aids are ControlLogix specific, the lessons and tools also
Training apply to the other Logix platforms.
instructor-led courses
computer-based training
workstation simulator
job aids

Instructor-led courses
The instructor-led courses are best suited for people new to the Logix architecture
and for those new to programmable controllers.
Course Description
CCP142 Programming Logix5000 motion applications using ladder logic
CCP143 Developing a Logix5000 project using RSLogix 5000 software
CCP144 Configuring advanced communications options on a Logix5000 system
CCP146 Fundamentals of Logix5000 systems
CCP151 Programming Logix5000 applications using basic ladder logic
CCP152 Programming Logix5000 applications using function block diagram
CCP153 Maintaining and troubleshooting Logix5000 sequential applications

Computer-based training
The computer-based training programs are designed to provide the essential
introductory information needed for using the product. Computer-based training is
best used as a resource following an instructor-led course.

Cat. No. Description

9393-RSTCLX ControlLogix Fundamentals (90 day warranty)
9393-RSTPCLX ControlLogix Fundamentals (1 year warranty)
9393-RSTLX5K RSLogix 5000 Programming Software (90 day warranty)
9393-RSTPLX5K RSLogix 5000 Programming Software (1 year warranty)

1756-SG001F-EN-P — June 2003

ControlLogix workstation simulator

The ControlLogix workstation simulator (ABT-TDCL1) is an engineering support tool
that you can integrate into your training and development programs. The simulator
helps you perform sequential, process, drive control, and motion control. This
simulator is also used with most of the available instructor-led course. The simulator
includes:
network hardware (ControlNet, DH+)
control hardware (controller, power supply, digital I/O modules,
analog I/O modules)
programming cable (to connect to your computer)
motion control hardware (motion modules, servo drives, motors)
operator interface panel (pushbuttons, potentiometers, voltmeters)

Job aids
Job aids are useful resources to take back to your facility after completing instructor-
led and computer-based training.

Job Aid Description

ABT1756TSG10 ControlLogix Glossary guide
ABT1756DRG70 ControlLogix Reference guide
ABT1756TSJ50 ControlLogix Procedure guide
ABT1756TSJ20 ControlLogix Troubleshooting guide

1756-SG001F-EN-P — June 2003

ViewAnyWare ViewAnyWare products, together with Logix for control and NetLinx architecture for
communication, make up Rockwell Automation’s Integrated Architecture strategy. The
ViewAnyWare strategy combines Rockwell Automation’s expertise in Allen-Bradley
electronic operator interface and industrialized PC hardware with Rockwell Software’s
supervisory control software. Current ViewAnyWare products include:
RSView Enterprise Series™ software
PanelView Plus™ operator interface
VersaView™ industrial computers and monitors
VersaView CE industrial computer

RSView Enterprise Series software

RSView Enterprise Series from Rockwell Software is a line of HMI software products
designed with a common look, feel, and navigation to help speed HMI application
development and training time. With RSView Enterprise Series 3.0, you can reference
existing Logix data tags. Any changes made to these referenced tags are automatically
inherited by RSView. RSView Enterprise Series software includes:
RSView Studio™ lets you create applications in a single design environment. It
configures Supervisory Edition, Machine Edition, VersaView CE, and PanelView
Plus. It supports editing and reusing projects for improved portability between
embedded machine and supervisory HMI systems, saving development time and
reducing engineering and training costs.
RSView Machine Edition™ (ME) is a machine-level HMI product that supports
both open and dedicated operator interface solutions. It provides a consistent
operator interface across multiple platforms (including Microsoft Windows CE,
Windows 2000/XP, and PanelView Plus solutions), and is ideal for monitoring
and controlling individual machines or small processes.
RSView Supervisory Edition™ (SE) is an HMI software for supervisory-level
monitoring and control application. It has a distributed and scalable
architecture that supports distributed-server/multi-user applications. This highly
scalable architecture can be applied to a stand-alone, one-server/one-user
application or to multiple users interfacing with multiple servers.
The available RSView Enterprise Series products are:
RSView Enterprise Series Product Line Cat. No. Description
9701-VWSTENE RSView Studio for RSView Enterprise Series
RSView Studio
9701-VWSTMENE RSView Studio for Machine Edition
9701-VWMR015AENE RSView ME Station runtime for Windows 2000, 15 displays
RSView Machine Edition 9701-VWMR030AENE RSView ME Station runtime for Windows 2000, 30 displays
9701-VWMR075AENE RSView ME Station runtime for Windows 2000, 75 displays
9701-VWSCWAENE RSView SE client
9701-VWSCRAENE RSView SE view client
9701-VWSS025AENE RSView SE server 25 displays
9701-VWSS100AENE RSView SE server 100 displays
9701-VWSS250AENE RSView SE server 250 displays
RSView Supervisory Edition
9701-VWSS000AENE RSView SE server unlimited display
9701-VWB025AENE RSView SE station 25 displays
9701-VWB100AENE RSView SE station 100 displays
9701-VWB250AENE RSView SE station 250 displays
9701-VWSB000AENE RSView SE station unlimited display

1756-SG001F-EN-P — June 2003

PanelView Plus operator interface

PanelView Plus is ideal for applications with a need to monitor, control, and display
information graphically, allowing operators to quickly understand the status of their
application. PanelView Plus is programmed with RSView Studio and has embedded
RSView Machine Edition functionality. It combines the best features from the popular
Allen-Bradley PanelView Standard and PanelView “e” operator interface products and
adds new functionality including:
multi-vendor communications
trending
expressions
data logging
animation
RSView Studio direct browsing of RSLogix 5000 addresses

VersaView industrial computers and monitors

VersaView is a family of industrial computer and monitor solutions, comprised of
integrated display computers, workstations, non-display computers and flat panel
monitors. VersaView products offer effortless management of changing technology, a
rugged but cost-effective design, and easier product configuration. All VersaView
products provide the latest industrial solution available, optimized for visualization,
control, information processing, and maintenance application. RSView ME, RSView SE
client, and RSView SE server runtimes are installed (separate activation is required).

VersaView CE industrial computers

VersaView CE is an open Windows CE terminal with a Windows desktop environment
- bringing together features of operator interfaces and industrial computers. It is a
high performance computer with a compact flash drive and integrated RSView
Machine Edition runtime (no activation required). There’s no hard disk, no fan, and
no moving parts, which means maximum reliability on the plant floor. Easy to set up
and maintain, VersaView CE means an open system that’s rugged and economical,
offering high functionality in an easy to use package.

1756-SG001F-EN-P — June 2003

Controlling Automation
Machines and Processes

Consider ControlLogix to meet your batch and continuous process applications.

Function block programming with both offline and online editing suits continuous and
web process. Both sequential function chart programming and structured text
programming suit batch process. In addition, ProcessLogix incorporates ControlLogix
to solve distributed process applications.

ProcessLogix distributed process control

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.

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.

1756-SG001F-EN-P — June 2003

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 system’s trending and historian
capabilities. Or you can export the data to external programs or systems for more
detailed analysis.

1756-SG001F-EN-P — June 2003

Summary
Use a spreadsheet to record the amount and type of devices your ControlLogix system
needs. For example, this sample system:

could result in this spreadsheet:

Device Number of Points Needed Cat. No. I/O Points per Module Number of Modules
120V ac digital inputs 73 1756-IA8D 8 10
120V ac digital outputs 25 1756-OA8D 8 4
24V dc digital inputs 43 1756-IB16D 16 3
24V dc digital outputs 17 1756-OB16D 16 2
contact digital outputs 11 1756-OX8I 8 2
4-20mA analog inputs 7 1756-IF6I 6 2
0 (can use remaining points on above
0-10V dc analog inputs 2 1756-IF6I 6
modules)
4-20mA analog outputs 4 1756-OF6CI 6 1
analog servo module 2 axes 1756-M02AE na 1
PanelView terminal na 2711 series na na
ControlNet communication module na 1756-CNB na 3
Remote I/O communication module na 1756-DHRIO na 1
total 29

1756-SG001F-EN-P — June 2003

As you select devices for your ControlLogix system, keep in mind:

ü Step Remember to Select
I/O modules - some modules have diagnostic features, electronic fusing, or individually
isolated inputs/outputs
1 Select I/O devices a remote terminal block (RTB) or wiring system for each I/O module
PanelConnect modules and cables if connecting input modules to sensors

the size of the motion application (use the Motion Book)

how you want to interface the controller and drives
type of motion interface, either SERCOS or analog
2 Select motion control and drives requirements
associated cable(s)
remote terminal block (RTB) - only needed for 1756-M02AE modules
drives, motors, and accessories (use the Motion Book)
networks
communication modules
3 Select communication modules
associated cable(s) and network equipment
sufficient modules and cables if you are planning a redundant system
a controller with sufficient memory
memory board for each 1756-L55 controller
4 Select controllers
1756-BATM for larger memory size controllers
replacement batteries
a chassis with enough slots for the modules you need, with room to spare for
5 Select chassis 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
6 Select power supplies additional growth
the power supply bundles if you are planning a redundant power supply system
the appropriate package of RSLogix 5000 Enterprise Series software and any options
7 Select software
other software packages for your application

As you determine placement of the modules you selected, use the worksheet on the
inside of the back cover to record your choices. Make a copy of this worksheet for
each chassis.

1756-SG001F-EN-P — June 2003

Notes:

1756-SG001F-EN-P — June 2003

Notes:

1756-SG001F-EN-P — June 2003

Controllogix: Selection Guide
No ratings yet
Controllogix: Selection Guide
92 pages
CompactLogix Selection Guide
No ratings yet
CompactLogix Selection Guide
52 pages
ControlLogix System Overview Guide
No ratings yet
ControlLogix System Overview Guide
88 pages
Guia para Selección de PLC
No ratings yet
Guia para Selección de PLC
84 pages
Compactlogix
No ratings yet
Compactlogix
56 pages
1756 sg001 - en P
No ratings yet
1756 sg001 - en P
48 pages
ControlLogix Selection Guide
No ratings yet
ControlLogix Selection Guide
88 pages
How To Make Your PLC System For Dummies
100% (1)
How To Make Your PLC System For Dummies
36 pages
Logix Architecture: (Confidential - For Internal Use Only)
100% (2)
Logix Architecture: (Confidential - For Internal Use Only)
71 pages
Controllogix System: Selection Guide
No ratings yet
Controllogix System: Selection Guide
32 pages
CompactLogix Selection Guide Overview
No ratings yet
CompactLogix Selection Guide Overview
64 pages
AB CLX Standard 4 Day Module1 5C
No ratings yet
AB CLX Standard 4 Day Module1 5C
58 pages
ControlLogix Training Guide
No ratings yet
ControlLogix Training Guide
62 pages
Logix5000 ™ & Rslogix™ 5000 Overview
100% (3)
Logix5000 ™ & Rslogix™ 5000 Overview
75 pages
RW Control Hardware
No ratings yet
RW Control Hardware
35 pages
ControlLogix System Selection Guide
No ratings yet
ControlLogix System Selection Guide
1 page
AB Controller Comparison
No ratings yet
AB Controller Comparison
7 pages
Allen-Bradley 1756-L71: Logix Controllers Comparison
No ratings yet
Allen-Bradley 1756-L71: Logix Controllers Comparison
3 pages
Controllogix System: Selection Guide
No ratings yet
Controllogix System: Selection Guide
26 pages
Modulos de Control
No ratings yet
Modulos de Control
6 pages
Controllogix System: Selection Guide
No ratings yet
Controllogix System: Selection Guide
40 pages
1756-DNB - Allen Bradley - ControlLogix DeviceNet Bridge Scanner Module - Datasheet
No ratings yet
1756-DNB - Allen Bradley - ControlLogix DeviceNet Bridge Scanner Module - Datasheet
4 pages
1756 ControlLogix System
100% (2)
1756 ControlLogix System
40 pages
Controllogix System: Selection Guide
No ratings yet
Controllogix System: Selection Guide
40 pages
ControlLogix Redundancy System
No ratings yet
ControlLogix Redundancy System
147 pages
Integrated Architecture Recommended Literature (Eng)
No ratings yet
Integrated Architecture Recommended Literature (Eng)
10 pages
Especificacion Tecnica Tarjeta de Comunicacion
No ratings yet
Especificacion Tecnica Tarjeta de Comunicacion
36 pages
ESPEC 1756-l73 Controller
No ratings yet
ESPEC 1756-l73 Controller
2 pages
Guia Practica Controllogix
100% (1)
Guia Practica Controllogix
58 pages
02learning RSLogix 5000 Programming Sample Chapter PDF
50% (2)
02learning RSLogix 5000 Programming Sample Chapter PDF
25 pages
Learning RSLogix 5000 Programming - Sample Chapter
86% (7)
Learning RSLogix 5000 Programming - Sample Chapter
25 pages
1756-td003 - ControlLogix Communication Modules Specifications T Echnical Data
No ratings yet
1756-td003 - ControlLogix Communication Modules Specifications T Echnical Data
36 pages
High Availability Systems: Selection Guide
No ratings yet
High Availability Systems: Selection Guide
16 pages
Rockwell Allen Bradley PLC - Controller Quick Reference
100% (4)
Rockwell Allen Bradley PLC - Controller Quick Reference
4 pages
Controllogix System: Selection Guide
No ratings yet
Controllogix System: Selection Guide
40 pages
9324 pp001 - en P
No ratings yet
9324 pp001 - en P
12 pages
Install The System
No ratings yet
Install The System
128 pages
Allen Bradley 1756-CNB Control Net Bridge Module - Burn Only (103 Pages)
No ratings yet
Allen Bradley 1756-CNB Control Net Bridge Module - Burn Only (103 Pages)
203 pages
ControlLogix System and RSLogix 5000 Guide
100% (2)
ControlLogix System and RSLogix 5000 Guide
118 pages
Rockwell PLC
100% (2)
Rockwell PLC
80 pages
RSLogix 5000
86% (7)
RSLogix 5000
36 pages
PLC Programmable Logic Controller: Presented By: Shikha Chittora
No ratings yet
PLC Programmable Logic Controller: Presented By: Shikha Chittora
50 pages
1756 td001 - en e
No ratings yet
1756 td001 - en e
28 pages
1756 L71
No ratings yet
1756 L71
38 pages
RS Logix 5000
No ratings yet
RS Logix 5000
16 pages
Logix5000 Controllers IEC 61131-3 Compliance
No ratings yet
Logix5000 Controllers IEC 61131-3 Compliance
22 pages
Bzware In001 - en P
No ratings yet
Bzware In001 - en P
154 pages
SCADA5
No ratings yet
SCADA5
1 page
MEX10106
No ratings yet
MEX10106
62 pages
LAB20707
No ratings yet
LAB20707
29 pages
Rockwel Power Supply
No ratings yet
Rockwel Power Supply
14 pages
SCADA Systems: Overview and Components
No ratings yet
SCADA Systems: Overview and Components
1 page
Multivariable Control in Instrumentation
No ratings yet
Multivariable Control in Instrumentation
85 pages
1000-2000 Litres Proving Tanks: Technical Particulars
No ratings yet
1000-2000 Litres Proving Tanks: Technical Particulars
1 page
P.Storage and Pressure Vessels
No ratings yet
P.Storage and Pressure Vessels
63 pages
Reverse Osmosis System Design
No ratings yet
Reverse Osmosis System Design
68 pages
LAB20704
No ratings yet
LAB20704
68 pages
1756 In101h en P
No ratings yet
1756 In101h en P
48 pages
PCI10407
No ratings yet
PCI10407
106 pages
LAB20405
No ratings yet
LAB20405
55 pages
Aramco Boiler Scale Guide
No ratings yet
Aramco Boiler Scale Guide
46 pages
LAB20701
No ratings yet
LAB20701
29 pages
LAB10505
No ratings yet
LAB10505
19 pages
Saudi Aramco Boiler Water Guide
No ratings yet
Saudi Aramco Boiler Water Guide
53 pages
LAB20404
No ratings yet
LAB20404
21 pages
Radioactive Scales Guide
No ratings yet
Radioactive Scales Guide
43 pages
Aramco Scale Monitoring Guide
No ratings yet
Aramco Scale Monitoring Guide
23 pages
LAB20303
No ratings yet
LAB20303
77 pages
LAB20402
No ratings yet
LAB20402
48 pages
LAB20401
No ratings yet
LAB20401
72 pages
LAB20309
No ratings yet
LAB20309
22 pages
LAB20310
No ratings yet
LAB20310
23 pages
Lab 10501
No ratings yet
Lab 10501
91 pages
CO2 Valve Technical Specs
No ratings yet
CO2 Valve Technical Specs
2 pages
Maintain Instrumented Protection Systems
No ratings yet
Maintain Instrumented Protection Systems
4 pages
Generative AI For Business Leaders Linkedin Q&A
No ratings yet
Generative AI For Business Leaders Linkedin Q&A
19 pages
MTD361 - JAN - 2016 - Exam Paper - 1465526633545
No ratings yet
MTD361 - JAN - 2016 - Exam Paper - 1465526633545
4 pages
Software Eng. Exam Prep Guide
No ratings yet
Software Eng. Exam Prep Guide
9 pages
QP - by WWW - EasyEngineering
No ratings yet
QP - by WWW - EasyEngineering
2 pages
Application for Internship at MOHA
100% (1)
Application for Internship at MOHA
6 pages
Eng CD 2203772 B
No ratings yet
Eng CD 2203772 B
1 page
Library Classes
No ratings yet
Library Classes
5 pages
Quarter 1 Tle 7 Learning Plan
No ratings yet
Quarter 1 Tle 7 Learning Plan
11 pages
Diverse Online Resources Guide
No ratings yet
Diverse Online Resources Guide
22 pages
Peter Lalovsky Learn Microsoft SQL Server Intuitively. Transact SQL The Solid Basics
100% (1)
Peter Lalovsky Learn Microsoft SQL Server Intuitively. Transact SQL The Solid Basics
289 pages
Context Engineering Whitepaper
No ratings yet
Context Engineering Whitepaper
23 pages
LST Pre-Internship Program and Internship Details
No ratings yet
LST Pre-Internship Program and Internship Details
13 pages
Palo Alto Firewall Initial Setup Guide
No ratings yet
Palo Alto Firewall Initial Setup Guide
11 pages
Computer Systems Servicing: Mensuration & Calculation
No ratings yet
Computer Systems Servicing: Mensuration & Calculation
16 pages
Opentext Po Appworks en
No ratings yet
Opentext Po Appworks en
5 pages
Ai Unit III Notes
No ratings yet
Ai Unit III Notes
47 pages
AEC119
No ratings yet
AEC119
8 pages
PentestTools SubdomainFinder Report
No ratings yet
PentestTools SubdomainFinder Report
2 pages
Garmin GTX330 Installation Manual
100% (1)
Garmin GTX330 Installation Manual
86 pages
Constant-Time Synchronous Binary Counter With Minimal Clock Period
No ratings yet
Constant-Time Synchronous Binary Counter With Minimal Clock Period
5 pages
Main Report
No ratings yet
Main Report
19 pages
IT Plan
No ratings yet
IT Plan
1 page
A RAD RIC-155 Fast Ethernet Over STM-1:OC-3 Converter
No ratings yet
A RAD RIC-155 Fast Ethernet Over STM-1:OC-3 Converter
2 pages
Assignment1 SU24 SE07203 VuDangKhoi BS01129
No ratings yet
Assignment1 SU24 SE07203 VuDangKhoi BS01129
30 pages
Introduction to Microcomputers
No ratings yet
Introduction to Microcomputers
21 pages
Inverter Documents-OM Textiles 4MW Rev00
100% (1)
Inverter Documents-OM Textiles 4MW Rev00
18 pages
Event Registration System With QR Code: 1) Background/ Problem Statement
No ratings yet
Event Registration System With QR Code: 1) Background/ Problem Statement
16 pages
Configuring Promiscuous Mode On A Virtual Switch or Portgroup (1004099)
No ratings yet
Configuring Promiscuous Mode On A Virtual Switch or Portgroup (1004099)
1 page
User Manual
No ratings yet
User Manual
20 pages
OKI - CONSUMABLES - NON EU - HR Single - tcm70-209703 PDF
No ratings yet
OKI - CONSUMABLES - NON EU - HR Single - tcm70-209703 PDF
40 pages