ControlLogix

Selection Guide

Introducing ControlLogix for High Performance Control

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

Take Control with Logix

Rockwell Automations Logix offer users compatibility of control in a variety of platforms, including: ControlLogix, a high-performance, multi-processing platform ProcessLogix, a cost-effective distributed control system (DCS) for process applications SoftLogix, PC-based control from the PLC leader FlexLogix, FLEX I/O expanded to include distributed control CompactLogix, value-focused compact modular I/O coupled with machine control. Rockwell Automations Logix Platforms offer users compatibility of control in a variety of formats within the NetLinx open network architecture for Ethernet, ControlNet and DeviceNet.

The RSLogix 5000 programming environment and/or NetLinx open network architecture are common to these Logix platforms. The RSLogix 5000 environment offers an easy-to-use IEC 1131-3 compliant interface, symbolic programming with structures and arrays for increased productivity, and an instruction set that serves sequential, motion, process and drives applications. The NetLinx open network architecture offers common communication tools for use with a variety of networks such as Ethernet, ControlNet and DeviceNet. The ControlLogix control platform is: seamless enables easy integration with existing PLC-based systems. Users on existing networks can send or receive messages to/from program controllers on other networks transparently. fast scalable the ControlLogix platform provides high-speed data-transfers across the backplane and the ControlLogix5550 controller provides a high-speed control platform. provides a modular approach to control. Add as many or as few controllers and communication modules as you need. You can have multiple controllers in the same chassis. Select the controller memory size that meets your application. industrial integrated compact offers a hardware platform designed to withstand the vibrations, thermal extremes, and electrical noise associated with harsh industrial settings. establishes a platform that integrates multiple technologies, including sequential, motion, drive, and process applications. meets the needs of many applications where control is highly distributed and panel

Table of Contents
Selecting a ControlLogix System . . . . Selecting ControlLogix I/O Modules . . . . . . . 4 . . . . . 19 33

Planning Motion . . . . . . . . . . . . . . . . . Planning Network Communications . . . . . Selecting a Controller . . . . . . . . . .

. . . 39 . . . 57 73 . 77 . . 79

Selecting a Chassis . . . . . . . Selecting a Power Supply . . . . . Selecting Software . . . . . . .

. . . . . . . . . . . . . . .

Implementing a DCS Control System . . . . . . . . 85

As one of the next generation of Allen-Bradley control systems, ControlLogix integrates sequential, process, drive and motion control together with communications and state-of-the-art I/O in a small, cost-competitive platform. Because ControlLogix is modular, you can design, build, and modify it efficiently - with significant training and engineering savings.

Selecting a ControlLogix System

Selecting a ControlLogix System

The ControlLogix system architecture provides sequential, process, and motion control together with communications and state-of-the-art I/O in a small, cost-competitive package. The system is modular, so you can design, build, and modify it efficiently - with significant savings in training and engineering. A ControlLogix system can be anything from a simple chassis to a highly-distributed system consisting of multiple chassis and networks working together. A simple ControlLogix system consists of a stand-alone controller and I/O modules in a single chassis.

ControlLogix controller

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

41775

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

1756-SG001A-US-P July 2000

Selecting a ControlLogix System

For a more robust system, use: multiple controllers in a single chassis multiple controllers joined across networks I/O in multiple platforms that is distributed in many locations and connected over multiple I/O links

ControlNet link communication interface modules in the same chassis as the ControlLogix controller

ControlLogix controller

DeviceNet link

}
41776

remote I/O modules

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

RS-232 link Ethernet link ControlNet link DH+ link

computers other controllers

1756-SG001A-US-P July 2000

Selecting a ControlLogix System

Use the following example 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. Complete one worksheet for each chassis. Follow these steps as you specify your ControlLogix system:
Determine the I/O devices

Step 1

See page 7

Step 2

Determine motion requirements

See page 8

Step 3

Lay out the system and select communication modules

See page 9

Step 4

Determine controller requirements

See page 11

Step 5

Determine the number of chassis

See page 12

Step 6

Select power supplies and ensure sufficient power

See page 13

Step 7

Verify communications See page 14

Step 8

Select software See page 18

1756-SG001A-US-P July 2000

Step 1: Determine the I/O Devices

Use a spreadsheet to record the amount and type of I/O devices the ControlLogix system needs. Record the: location of the device number of points needed appropriate 1756 catalog number number of points available per module number of modules

To determine the number of modules you need, divide the number of points needed by the I/O points per module. For example:
I/O device: 120V ac digital inputs 120V ac digital outputs 24V dc digital inputs 24V dc digital outputs contact digital outputs 4-20mA analog inputs 0-10V dc analog inputs Location: A A A A A A A Number of points needed: 73 25 43 17 11 7 2 Catalog number: 1756-IA8D 1756-OA8D 1756-IB16D 1756-OB16D 1756-OX8I 1756-IF6I 1756-IF6I I/O points per module: 8 8 16 16 8 6 6 Number of modules: 10 4 3 2 2 2 0 (use the remaining points from the above 1756-IF6I module) 1 na

4-20mA analog outputs PanelView terminal

A A

4 na

1756-OF6CI 2711 series

6 na

Location A subtotal 24 120V ac digital inputs 120V ac digital outputs 24V dc digital inputs 24V dc digital outputs contact digital outputs 4-20mA analog inputs 0-10V dc analog inputs 4-20mA analog outputs PanelView terminal B B B B B B B B B 35 15 23 13 5 3 1 2 na 1756-IA8D 1756-OA8D 1756-IB16D 1756-OB16D 1756-OX8I 1756-IF6I 1756-IF6I 1756-OF6CI 2711 series 8 8 16 16 8 6 6 6 na 5 2 2 1 1 3 0 1 na

Location B subtotal 15 RSView on a personal computer C na 9301 series na na

Location C subtotal 0

For more information about ControlLogix I/O modules and how they operate, see page 19.

1756-SG001A-US-P July 2000

Step 2: Determine the Motion Requirements

The ControlLogix controller executes ladder motion commands and generates position and velocity profile information. Each controller and chassis can control up to 16 1756-M02AE servo modules (for a total of 32 axes). Each 1756-M02AE servo module must be in the same local chassis as its ControlLogix controller. The 1756-M02AE servo module connects to a servo drive and closes a high-speed position and velocity loop. Each 1756-M02AE module can control up to two axes. Use the same spreadsheet to record motion servo modules. For example:

I/O device: 120V ac digital inputs 120V ac digital outputs 24V dc digital inputs 24V dc digital outputs contact digital outputs 4-20mA analog inputs 0-10V dc analog inputs 4-20mA analog outputs analog servo module PanelView terminal

Location: A A A A A A A A A A

Number of points needed: 73 25 43 17 11 7 2 4 2 axis na

Catalog number: 1756-IA8D 1756-OA8D 1756-IB16D 1756-OB16D 1756-OX8I 1756-IF6I 1756-IF6I 1756-OF6CI 1756-M02AE 2711 series

I/O points per module: 8 8 16 16 8 6 6 6 na na

Number of modules: 10 4 3 2 2 2 0 1 1 na

Location A subtotal 25 120V ac digital inputs 120V ac digital outputs 24V dc digital inputs 24V dc digital outputs contact digital outputs 4-20mA analog inputs 0-10V dc analog inputs 4-20mA analog outputs PanelView terminal B B B B B B B B B 35 15 23 13 5 3 1 2 na 1756-IA8D 1756-OA8D 1756-IB16D 1756-OB16D 1756-OX8I 1756-IF6I 1756-IF6I 1756-OF6CI 2711 series 8 8 16 16 8 6 6 6 na 5 2 2 1 1 3 0 1 na

Location B subtotal 15 RSView on a personal computer C na 9301 series na na

Location C subtotal 0

For more information about planning for motion, see page 33.

1756-SG001A-US-P July 2000

Step 3: Lay Out the System

Lay out the system by determining the network configuration and the placement of components in each location. Decide at this time whether each location will have its own controller. Place each controllers I/O on an isolated network to maximize the performance and to more easily accommodate future network or system configuration changes. If you plan to share I/O, make sure the I/O is on a network that each controller can access. For example, assume that Location A and Location B both require a controller. Each controllers I/O is isolated on its own network. Both controllers must interact with time critical information. Panel C does not require a controller and can be a ControlLogix gateway.
RSView Ethernet

ControlNet network C

Panel C

ControlNet network A

ControlNet network B

Panel A chassis 1

Panel A chassis 2

Panel A chassis 3

Panel B chassis 1

Panel B chassis 2

Universal Remote I/O PanelView

Universal Remote I/O PanelView

For a ControlLogix controller to control I/O modules, both the controller and the I/O modules must be directly attached to the same ControlNet network. This table lists which controllers in the above example can control which I/O modules.
I/O location: Panel A, chassis 1 Panel A, chassis 2 Panel A, chassis 3 Panel B, chassis 1 Panel B, chassis 2 Panel C, chassis 1 Controller in Panel A, chassis 1 yes yes yes yes no yes Controller in Panel B, chassis 1 yes no no yes yes yes

For more information about placing I/O modules, see page 30.

1756-SG001A-US-P July 2000

10

You also need to evaluate what communications need to occur between the controllers. If there is sporadic information that is not time critical, use a message-based network such as an Ethernet, 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 network.

Placing communication modules

Determine the number of communication modules. You can use multiple communication modules in a chassis and divide communications between those modules. Some communication modules have multiple channels, so you dont necessarily need one communication module for each link. This example assumes one communication module for each link. Add the communication modules to the spreadsheet:
I/O device: 120V ac digital inputs 120V ac digital outputs 24V dc digital inputs 24V dc digital outputs contact digital outputs 4-20mA analog inputs 0-10V dc analog inputs 4-20mA analog outputs analog servo module PanelView terminal Location: A A A A A A A A A A Number of points needed: 73 25 43 17 11 7 2 4 2 axis 1 na na Catalog number: 1756-IA8D 1756-OA8D 1756-IB16D 1756-OB16D 1756-OX8I 1756-IF6I 1756-IF6I 1756-OF6CI 1756-M02AE 2711 series 1756-CNB 1756-DHRIO I/O points per module: 8 8 16 16 8 6 6 6 na na na na Number of modules: 10 4 3 2 2 2 0 1 1 na 4 1

ControlNet communication module A Remote I/O communication module A

Location A subtotal 30

For more information about networks and communication modules, see page 39.

1756-SG001A-US-P July 2000

11

Step 4: Determine the Controller Requirements

Controller tasks Discrete I/O points Analog I/O points Motion axis

The following equations provide an estimate of the memory needed for a controller. Each of these numbers includes a rough estimate of the associated user programming. Depending on the complexity of your application, you might need more or less memory. _____ * 4000 = _____ bytes (minimum 1 needed) _____ * 400 = _____ bytes _____ * 2600 = _____ bytes _____ * 8000 = _____ bytes Total = _____ bytes For example, the following table lists the configurations for Location A and Location B:
Location A: Location B: 1 continuous 2 periodic (STI) 35 + 15 + 23 + 13 + 5 = 91 3+1+2=6 3 1756-CNB modules 1 1756-DHRIO module none

Communication modules _____ * 2000 = _____ bytes

Controller tasks: Digital I/O points Analog I/O points: Communication modules: Motion axis:

1 continuous 1 periodic (STI) 73 + 25 + 43 + 17 + 11 = 169 7 + 2 + 4 = 13 4 1756-CNB modules 1 1756-DHRIO module 2 axis

Then estimate memory to help choose the controller:

Location A (bytes): Controller tasks: Digital I/O points: Analog I/O points: Communication modules: Motion axis: Total bytes: Selected controller: (2 x 4000) = 8000 (169 x 400) = 67,600 (13 x 2600) = 33,800 (5 x 2000) = 10,000 (2 x 8000) = 16,000 135,400 1756-L1M1 Location B (bytes): (3 x 4000) = 12,000 (91 x 400) = 36,400 (6 x 2600) = 15,600 (4 x 2000) = 8000 (0 x 8000) = 0 72,000 1756-L1M1

If an estimate is close to the next memory size, select the larger memory. For example, Location B uses 83% of the 160K bytes in a 1756-L1 controller. Use a 1756-L1M1 controller instead. For more information about selecting a controller, see page 57.

1756-SG001A-US-P July 2000

12

Step 5: Determine the Number of Chassis

Location: A B C

Use another spread sheet to determine the number of chassis you need for each location in your system. Include additional space in each chassis to accommodate future growth. For example:
Spare slots (20% of slots used) 5 4 1 Total slots needed: 31 21 3 Chassis catalog Chassis number: quantity: 1756-A13 1756-A13 1756-A4 3 2 1

Module slots used: 25 17 2

Important: Use the slot filler module 1756-N2 to fill empty slots. Two slot filler modules are included in each 1756-N2 catalog number. For more information about selecting a chassis, see page 73.

1756-SG001A-US-P July 2000

13

Step 6: Select Power Supplies and Ensure Sufficient Power

Use the worksheet on the inside of the back cover of this selection guide to record your module selections and calculate power requirements. Complete one worksheet for each chassis. For example:

1756-CNB

1756-CNB

1756-DHRIO

1756-M02AE

1756-OF6VI

Chassis: Catalog Number: A1 rack power 0 1 2 3 4 5 6 7 8 9 10 11 12 1756-A13 1756-PA72 1756-CNB 1756-CNB 1756-L1M1 1756-DHRIO spare (1756-N2) spare (1756-N2) 1756-IF6I 1756-OF6VI 1756-OX8I 1756-M02AE 1756-IA8D 1756-IA8D 1756-OA8D

Backplane current 3.3V (amps):

1756-L1M1

Backplane current 5.1V (amps):

Backplane Module current 24V power (amps): (watts):

I/O termination: Connections: 20-pin 36-pin Direct Rack

400mA maximum

10,000mA maximum

2800mA maximum

cant exceed 75W @ 60C)

0mA 0mA 0mA 0mA

970mA 970mA 950mA 850mA

1.7mA 1.7mA 20mA 1.7mA

4.98W 4.98W 5.33W 4.38W

0mA 0mA 0mA 0mA 0mA 0mA 0mA totals: 0mA

250mA 250mA 100mA 700mA 100mA 100mA 175mA 5415mA

100mA 175mA 100mA 2.5mA 3mA 3mA 250mA 658.6mA

3.7W 5.5W 2.91W 3.63W 0.58W 0.58W 6.89W 43.46W

1 1 1 1 1 1 1 5 2

If your power consumption exceeds the maximum, move some modules to another chassis and recalculate the power requirements. For more information about selecting a power supply, see page 77.

1756-OA8D

1756-IAD

1756-IF6I

1756-OX8I

1756-IAD

1756-N2

1756-N2

1756-SG001A-US-P July 2000

14

Step 7: Verify Communications

The ControlLogix controller supports 250 connections. The following table shows how many connections the controller uses for these different communication configurations
ControlLogix Connection to: Connections Used by the Controller per Module: 1 1 3 0 0 or 1 1 0 2 1 1 1 1 1 1

local I/O module remote I/O module (direct connection only) 1756-MO2AE servo module local 1756-CNB module remote ControlNet communication module configured as a direct (none) connection configured as a rack-optimized connection 1756-DHRIO module 1756-ENET module 1756-DNB module Universal Remote I/O adapter module produced tag produced tag and one consumer each additional consumer of the tag consumed tag block-transfer message other message

For example, to calculate the connections for the controller in Panel A, Chassis 1 in the configuration example, add the connections: for data transfer in Panel A, Chassis 1 to remote 1756-CNB in Panel A, Chassis 2 to remote 1756-CNB in Panel A, Chassis 3

Data transfer connections

For example, the controller in Panel A, Chassis 1 can use these communication methods for transferring data:
Connection Type: produced tags produced tag each consumer of the tag consumed tags block-transfer messages other messages Quantity: Total Connections:

2 4 4 2 12

6 4 2 12 total 24

1756-SG001A-US-P July 2000

15

Connections for Panel A, Chassis 1

Chassis: Catalog Number: A1 rack power 0 1 2 3 4 5 6 7 8 9 10 11 12 1756-A13 1756-PA72 1756-CNB 1756-CNB 1756-L1M1 1756-DHRIOa spare (1756-N2) spare (1756-N2) 1756-IF6I 1756-OF6VI 1756-OX8I 1756-M02AE 1756-IA8D 1756-IA8D 1756-OA8D 0mA 0mA 0mA 0mA 0mA 0mA 0mA totals: 0mA
a. 400mA maximum 10,000mA maximum 2800mA maximum cant exceed 75W @ 60C)

Backplane current 3.3V (amps):

Backplane current 5.1V (amps):

Backplane Module current 24V power (amps): (watts):

I/O termination: Connections: 20-pin 36-pin Direct Rack

0mA 0mA 0mA 0mA

970mA 970mA 950mA 850mA

1.7mA 1.7mA 20mA 1.7mA

4.98W 4.98W 5.33W 4.38W

0 0

0 0

250mA 250mA 100mA 700mA 100mA 100mA 175mA 5415mA

100mA 175mA 100mA 2.5mA 3mA 3mA 250mA 658.6mA

3.7W 5.5W 2.91W 3.63W 0.58W 0.58W 6.89W 43.46W

1 1 1 1 1 1 1 5 2

1 1 1 3 1 1 1 9 2

The controller uses 1 connection for the 1756-DHRIO module and 1 additional connection for each logical rack connected to the 1756-DHRIO module. In this example, a PanelView terminal is connected to the 1756-DHRIO module, using only 1 logical rack.

The controller always uses one direct connection for each I/O module in its local chassis. The controller does not use any connection for a 1756-CNB module in its local chassis. For more information about how the controller uses connections for I/O modules, see page 62.

1756-SG001A-US-P July 2000

16

Connections for Panel A, Chassis 2

The controller in Panel A, Chassis 1 has a direct connection to every I/O module in Panel A, Chassis 2.
Chassis: Catalog Number: A2 rack power 0 1 2 3 4 5 6 7 8 9 10 11 12 1756-A13 1756-PA72 1756-CNB 1756-IF6I 1756-OX8I 1756-OB16D 1756-IB16D 1756-IB16D 1756-OA8D 1756-OA8D 1756-OA8D 1756-IA8D 1756-IA8D 1756-IA8D spare (1756-N2) totals: 0mA 2695mA 1106.7mA 40.33W 6 6 12 0
400mA maximum 10,000mA maximum 2800mA maximum cant exceed 75W @ 60C)

Backplane current 3.3V (amps):

Backplane current 5.1V (amps):

Backplane Module current 24V power (amps): (watts):

I/O termination: Connections: 20-pin 36-pin Direct Rack

0mA 0mA 0mA 0mA 0mA 0mA 0mA 0mA 0mA 0mA 0mA 0mA

970mA 250mA 100mA 250mA 150mA 150mA 175mA 175mA 175mA 100mA 100mA 100mA

1.7mA 100mA 100mA 140mA 3mA 3mA 250mA 250mA 250mA 3mA 3mA 3mA

4.99W 3.7W 2.91W 4.64W 0.84W 0.84W 6.89W 6.89W 6.89W 0.58W 0.58W 0.58W 1 1 1 1 1 1 1 1 1 1 1 1

1 1 1 1 1 1 1 1 1 1 1 1

The controller always uses a direct connection for an analog I/O module, regardless of whether the analog I/O module is local or remote to the controller. The digital I/O modules in this chassis are remote to the controller, so you can select a direct connection or a rack-optimized connection. However, to take advantage of the diagnostic capabilities of the digital I/O modules in this chassis (note the D at the end of the catalog number), you must configure a direct connection between the controller and the I/O module.

1756-SG001A-US-P July 2000

17

Connections for Panel A, Chassis 3 The controller in Panel A, Chassis 1 has a rack connection to the 1756-IA8D and 1756-OA8D I/O modules. The controller has a direct connection to the remaining I/O modules.
Chassis: Catalog Number: A3 rack power 0 1 2 3 4 5 6 7 8 9 10 11 12 1756-A13 1756-PA72 1756-CNB spare (1756-N2) spare (1756-N2) 1756-OB16D 1756-IB16D spare (1756-N2) 1756-OA8D 1756-IA8D 1756-IA8D 1756-IA8D 1756-IA8D 1756-IA8D spare (1756-N2) totals: 0mA 2045mA 409.7mA 20.26W 4 4 3 1 0mA 0mA 0mA 0mA 0mA 0mA 175mA 100mA 100mA 100mA 100mA 100mA 250mA 3mA 3mA 3mA 3mA 3mA 6.89W 0.58W 0.58W 0.58W 0.58W 0.58W 1 1 1 1 1 1 0 0 0 0 0 0 0 0mA 0mA 250mA 150mA 140mA 3mA 4.64W 0.84W 1 1 1 1
400mA maximum 10,000mA maximum 2800mA maximum cant exceed 75W @ 60C)

Backplane current 3.3V (amps):

Backplane current 5.1V (amps):

Backplane Module current 24V power (amps): (watts):

I/O termination: Connections: 20-pin 36-pin Direct Rack

0mA

970mA

1.7mA

4.99W

The digital I/O modules in this chassis are configured for a rack-optimized connection, which consolidates connection use between the controller and the I/O modules. However, a rack-optimized connection reduces the diagnostic information that is available to the controller, which does not take advantage of the diagnostic capabilities of the discrete modules.

Total connections
Based on the example worksheets, the controller in Panel A, Chassis 1 needs these connections:
Location: Panel A, Chassis 1 Panel A, Chassis 2 Panel A, Chassis 3 Data transfer Total Connections: 11 12 4 24 total 51

1756-SG001A-US-P July 2000

18

Step 8: Select Software

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

If you have: 1756 ControlLogix controller 1756-M02AE motion module 1756-CNB, -CNBR ControlNet communication module

You need: RSLogix 5000 programming software

Order this catalog number: 9324 series (RSLogix 5000 programming software)

RSNetWorx for ControlNet 9324-RLD300NXENE (RSLogix 5000 (comes with RSLogix 5000 programming software programming software plus RSNetWorx option) and RSNetWorx for ControlNet bundle) or 9357-CNETL3 (RSNetWorx for ControlNet) RSNetWorx for DeviceNet 9324-RLD300NXENE (RSLogix 5000 programming software plus RSNetWorx option) or 9357-DNETL3 (RSNetWorx for DeviceNet) 9324 series (RSLogix 5000 programming software) or 1756-GTWY (ControlLogix Gateway Configuration software)

1756-DNB DeviceNet communication module

1756-ENET Ethernet communication module (set the IP address) 1756-DHRIO communication module (define the DH+ routing table) 1788-CN2FF Foundation Fieldbus linking device

RSLinx software (RSLinx Lite comes with RSLogix 5000 programming software) or ControlLogix Gateway software (comes with RSLogix 5000 programming software) Foundation Fieldbus Configuration Software and RSLinx or RSLinx OEM software (RSLinx Lite is not sufficient) RSLinx software (RSLinx Lite comes with RSLogix 5000 programming software) RSView32 software PanelBuilder software

1788-FFCT and 9355-WABENE or 9355-WABOEMENE 9324 series (RSLogix 5000 programming software) 9301 series 2711-ND3 for PanelBuilder 900 or 2711E-ND1 for PanelBuilder 1400e

communication card in a workstation workstation dedicated for operator interface PanelView terminal

For more information about selecting software packages, see page 79.

1756-SG001A-US-P July 2000

19

Selecting ControlLogix I/O Modules

The ControlLogix architecture provides a wide range of input and output modules to span many applications, from high-speed discrete to process control. The ControlLogix architecture uses producer/consumer technology, which allows input information and output status to be shared among multiple ControlLogix controllers.
Producer/Consumer I/O Model
DC INPUT POWER
ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K BAT

AC INPUT

DC INPUT

Logix5550
RUN I/O RS232 OK

Logix5550
RUN I/O RS232 BAT OK

DC OUTPUT
ST 0 1 2 3 4 5 6 7 FLT 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K FLT 8 9 10 11 12 13 14 15

AC OUTPUT

ST 0 1 2 3 4 5 6 7 O FLT 0 1 2 3 4 5 6 7 K

RUN

REM

PROG

RUN

REM

PROG

DIAGNOSTIC

DIAGNOSTIC

Input Modules

Logix5500 Output Modules Controllers

Commonly Shared Data

30672

When planning I/O communications, consider:

Considerations when planning I/O: which ControlLogix I/O modules to use where to place ControlLogix I/O modules how ControlLogix I/O modules operate selecting controller ownership See page: 20 30 31 32

The ControlLogix I/O modules offer a rich set of features, including: built-in module and wire diagnostics alarming scaling of values electronic fusing time stamping electronic module identification

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:
Product: 1756 digital I/O modules 1756 analog I/O modules 1756 specialty I/O modules 1756 removable terminal blocks 1492 wiring systems See page: 20 23 24 25 25

1756-SG001A-US-P July 2000

20

1756 Digital I/O Modules

The 1756 digital I/O modules support: removal and insertion under power (RIUP) producer/consumer based communications module-level fault reporting and field side diagnostics time stamping of data choice of direct-connect or rack-optimized communications In addition, you can select these type of digital I/O modules:
Digital I/O Type: diagnostic electronic fusing Description: These modules provide diagnostic features to the point level. These modules have a D at the end of the catalog number. These modules have internal electronic fusing to prevent too much current from flowing through the module. These modules have an E at the end of the catalog number. These modules have individually isolated inputs or outputs. These modules have an I at the end of the catalog number.

individually isolated

Digital ac input modules

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

1756-IA16

120V ac

74-132V ac

2.5mA

1756-IA16I

120V ac

79-132V ac

2.5mA

1756-IM16I

240V ac

159-265V ac 10-30V ac

2.5mA

1756-IN16

24V ac

2.75mA

1756-SG001A-US-P July 2000

21

Digital dc input modules

Catalog number: 1756-IB16 Number of inputs: 16 (2 sets of 8) 16 (4 sets of 4) 16 (individually isolated) 32 (2 sets of 16) 16 (2 sets of 8) 16 (individually isolated) Voltage category: 24V dc sink Operating voltage: 10-31.2V dc Maximum signal delay (programmable): on=1, 2, or 3ms off=2, 3, 4, 11, or 20ms on=1, 2, or 3ms off=4, 5, 13, or 22ms on=1, 2, or 3ms off=4, 5, 6, 13, or 22ms on=1, 2, or 3ms off=2,3,4,11, or 20ms on=1, 2, or 3ms off=4, 5, 6, 13, or 22ms on=2, 3, or 4 ms off=6, 7, 8,15, or 24ms Removable terminal block: 1756-TBNH 1756-TBSH (20 pins) 1756-TBCH 1756-TBS6H (36 pins) 1756-TBCH 1756-TBS6H (36 pins) 1756-TBCH 1756-TBS6H (36 pins) 1756-TBNH 1756-TBSH (20 pins) 1756-TBCH 1756-TBS6H (36 pins) Maximum on state current: 10V dc 2mA 31.2V dc 10mA 10V dc 30V dc 10V dc 30V dc 2mA 13mA 2mA 10mA Maximum off state current: 1.5mA Backplane current: 100mA @ 5V 2mA @ 24V 0.56W 150mA @ 5V 3mA @ 24V 0.84W 100mA @ 5V 3mA @ 24V 0.45W 150mA @ 5V 2mA @ 24V 0.81W 100mA @ 5V 3mA @ 24V 0.58W 125mA @ 5V 3mA @ 24V 0.71W

1756-IB16D

24V dc sink

10-30V dc

1.5mA

1756-IB16I

24V dc source or sink 24V dc sink

10-30V dc

1.5mA

1756-IB32

10-31.2V dc

10V dc 2mA 31.2V dc 5.5mA 30V dc 60V dc 90V dc 146V dc 2mA 7mA 1mA 3mA

1.5mA

1756-IC16

48V dc sink

30-60V dc

1.5mA

1756-IH16I

125V dc source or sink

90-146V dc

0.8mA

Digital ac output modules

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

1756-OA8D

120V ac

74-132V ac

1.0A @ 30C 0.5A @ 60C 2A @ 60C (4A/set @ 30C 2A/set @ 60C) 0.5A @ 60C (2A/set @ 60C) 2A @ 30C 1A @ 60C 2A @ 60C

1756-OA8E

120V ac

74-132V ac

1756-OA16

120/240V ac

74-265V ac

1756-OA16I

120/240V ac

74-265V ac

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

1756-ON8

24V ac

10-30V ac

1756-SG001A-US-P July 2000

22

Digital dc output modules

Catalog number: 1756-OB8 Number of outputs: 8 (2 sets of 4) 8 (individually isolated) 16 (2 sets of 8) 16 (2 sets of 8) 16 (individually isolated) Voltage category: 12/24V dc source 12/24V dc source or sink 24V dc source Operating voltage: 10-30V dc Removable terminal block: 1756-TBNH 1756-TBSH (20 pins) 1756-TBCH 1756-TBS6H (36 pins) 1756-TBCH 1756-TBS6H (36 pins) 1756-TBNH 1756-TBSH (20 pins) 1756-TBCH 1756-TBS6H (36 pins) Maximum current per point: 2A @ 60C Maximum current per module: 8A @ 60C Backplane current: 165mA @ 5V 2mA @ 24V 0.89W 250mA @ 5V 2mA @ 24V 1.32W 250mA @ 5V 140mA @ 24V 4.64W 250mA @ 5V 2mA @ 24V 1.32W 350mA @ 5V 2.5mA @ 24V 1.85W

1756-OB8EI

10-30V dc

2A @ 60C

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

1756-OB16D

19.2-30V dc

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

1756-OB16E

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

10-31.2V dc

1756-OB16I

10-30V dc

resistive: 2A @ 30C 1A @ 60C inductive: 1A @ 60C 0.5A @ 50C 0.35A @ 60C 2A @ 60C

8A @ 30C 4A @ 60C

1756-OB32

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

12/24V dc source 48V dc source

10-31.2V dc

1756-TBCH 1756-TBS6H (36 pins) 1756-TBNH 1756-TBSH (20 pins) 1756-TBCH 1756-TBS6H (36 pins)

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

300mA @ 5V 2.5mA @ 24V 1.58W 165mA @ 5V 2mA @ 24V 0.89W 250mA @ 5V 2mA @ 24V 1.12W

1756-OC8

30-60V dc

1756-OH8I

120V dc source or sink

90-146V dc

2A @ 60C

8A @ 60C

Digital contact output modules

Catalog number: 1756-OW16I Number of outputs: 16 (individually isolated) Type of contact outputs: 16 N.O. Removable terminal block: 1756-TBCH 1756-TBS6H (36 pins) 1756-TBCH 1756-TBS6H (36 pins) Operating voltage: 10-265V ac 5-150V dc Output current: 2A @ 125/240V ac 2A @ 5-30V dc 0.5A @ 48V dc 0.25A @ 125V dc 2A @ 125/240V ac 2A @ 5-30V dc 0.5A @ 48V dc 0.25A @ 125V dc Backplane current: 150mA @ 5V 150mA @ 24V 4.37W 100mA @ 5V 100mA @ 24V 2.91W

1756-OX8I

8 (individually isolated)

1 set of form-C contacts for each output

10-265V ac 5-150V dc

1756-SG001A-US-P July 2000

23

1756 Analog I/O Modules

The 1756 analog I/O modules support: removal and insertion under power (RIUP) producer/consumer based communications rolling time stamp of data system time stamp of data IEEE 32-bit floating point or 16-bit integer data formats direct-connect communications
Current range: 0-20.5mA Removable terminal block: 1756-TBCH 1756-TBS6H (36 pins) 1756-TBNH 1756-TBSH (20 pins) 1756-TBCH 1756-TBS6H (36 pins) 1756-TBNH 1756-TBSH (20 pins) Backplane current: 150mA @ 5V 40mA @ 24V 2.33W 250mA @ 5V 100mA @ 24V 3.7W 150mA @ 5V 65mA @ 24V 2.33W 250mA @ 5V 125mA @ 24V 4.25W

Catalog number: 1756-IF8

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

Number of outputs: none

Voltage range: user configurable 10.25V 0-5.125V 0-10.25V user configurable 10.5V 0-5.25V 0-10.5V user configurable 10.25V 0-5.125V 0-10.25V

1756-IF6I

none

0-21mA

1756-IF16

16 single-ended, 8 differential, or 4 high-speed differential 6 isolated RTD

none

0-20.5mA

1756-IR6I

none

RTD sensors supported: 100, 200, 500, 1000 Platinum, alpha=385 100, 200, 500, 1000 Platinum, alpha=3916 120 Nickel, alpha=672 100, 120, 200, 500 Nickel, alpha=618 10 Copper -12mV to 78mV -12mV to 30mV Thermocouples supported: Type B: 250 to 1820C (482 to 3308F) Type C: 0 to 2315C (23 to 4199F) Type E: -270 to 1000C (-454 to 1832F) Type J: -210 to 1200C (-346 to 2192F) Type K: -270 to 1372C (-454 to 2502F) Type N: -270 to 1300C (-454 to 2372F) Type R: -50 to 1768C (-58 to 3214F) Type S: -50 to 1768C (-58 to 3214F) Type T: -270 to 400C (-454 to 752F) 10.4V 0-21mA

1756-IT6I

6 isolated thermocouple 1 cold junction temperature

none

1756-TBNH 1756-TBSH (20 pins)

250mA @ 5V 125mA @ 24V 4.3W

1756-OF4

none

4 voltage or current 6 isolated

1756-TBNH 1756-TBSH (20 pins) 1756-TBNH 1756-TBSH (20 pins)

150mA @ 5V 120mA @ 24V 3.65W 250mA @ 5V 225mA @ 24V 6.7W (0-550loads) or 250mA @ 5V 300mA @ 24V 8.5W (>550loads) 250mA @ 5V 175mA @ 24V 5.5W 150mA @ 5V 210mA @ 24V 5.8W

1756-OF6CI

none

na

0-21mA

1756-OF6VI

none

6 isolated

10.5

na

1756-TBNH 1756-TBSH (20 pins) 1756-TBNH 1756-TBSH (20 pins)

1756-OF8

none

8 voltage or current

10.4

0-21mA

1756-SG001A-US-P July 2000

24

1756 Specialty I/O Modules

The 1756 series of I/O modules includes these specialty I/O modules:

1756-HSC high speed counter

The 1756-HSC module provides 4 high-speed, output-switching, ON-OFF windows. The module uses pulses for counting and frequency. The module interfaces with pulse devices and encoders, such as: photoswitch series 10,000 photoelectric sensors bulletin 872 3-wire DC proximity sensors bulletin 845 incremental encoders

The 1756-HSC module can update data every 2ms. The module is most effective when you use a single sensor for each of the two channels on the module. If necessary, you can connect a single sensor to multiple channels or modules.
Mode of operation: counter rate measurement encoder debounce filter 1 MHz maximum 500KHz maximum 250KHz maximum 70Hz maximum Input data: Output data: Backplane current: 300mA @ 5V 3mA @ 24V 1.6W

2 counters, each with A, B, and Z inputs 4 outputs (2 outputs/common) 5V dc and 12-24V dc 2 on/off preset values per output 16,777,216 maximum counts 20mA @4.5-5.5V dc 1A @10-31.2V dc

1756-PLS programmable limit switch

The 1756-PLS module supports enhanced packaging applications where you require: deterministic module operation for operations up to 1500 parts per minute (PPM) detection of 1.08 degrees of rotation at 1800 RPM fast switching of ON-OFF windows multi-turn capabilities using resolvers direct drive on most pneumatic solenoid or glue guns The module accepts any R3-style resolver, such as the bulletin 846 resolvers. The module provides excitation to the resolver at 5K Hz @ 7.0V ac and directly connects to the sine and cosine outputs of the resolver.
Module configuration: requires 3 contiguous slots in chassis Input/Output data: left section: 2 groups of 4 outputs and 4 inputs each center section: resolver interface and I/O control right section: 2 groups of 4 outputs and 4 inputs each Removable terminal block: requires 3 RTBs 1756-TBNH or 1756-TBSH (20 pins) Backplane current: 1A @ 5V 1A @ 125V 130W

1756-SG001A-US-P July 2000

25

1756 Removable Terminal Blocks

Removable terminal blocks (RTBs) provide a flexible interconnection between your plant wiring and 1756 I/O modules. The RTB plugs into the front of the I/O module. The type of I/O module determines which RTB you need. You choose screw-clamp or spring-clamp RTBs. RTBs are not shipped with I/O modules. You must order them separately. The standard housing on the front of the wiring arm is not deep enough for 14 AWG wiring. If you plan to use 14 AWG wiring, also order the extended housing.
Catalog number: 1756-TBNH 1756-TBSH 1756-TBCH 1756-TBS6H 1756-TBE Description: screw-clamp with 20-pin connection spring-clamp with 20-pin connection screw-clamp with 36-pin connection spring-clamp with 36-pin connection extended housing; required for additional wiring space if using 14 AWG wiring Weight: 0.1 kg (0.3lb) 0.1 kg (0.2lb) 0.1 kg (0.3lb) 0.1 kg (0.2lb) 0.05 kg (0.1 lb)

1492 Wiring Systems

As an alternative to buying RTBs and connecting the wires yourself, you can buy a wiring system of: interface modules (IFMs) that mount on DIN rails and have pre-wired cables. One end of the cable assembly plugs into the IFM. The other end is an RTB that plugs into the front of the I/O 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. See the following tables for the available IFMs and cables.

1756-SG001A-US-P July 2000

26

IFMs for 20-pin 1756 digital I/O modules

Catalog number: Type of IFM: Description: OB16E OA8D OA8E OA16 IA8D IN16 IA16 IB16 IC16 ON8 U U U W W W OB8 OC8 U U U W W W OA8 U U U

1492-IFM20F 1492-IFM20FN 1492-IFM20F-2 1492-IFM20F-3 1492-IFM20D24 1492-IFM20D24N 1492-IFM20D120 1492-IFM20D24-2 1492-IFM20D24A-2 1492-IFM20D120-2 1492-IFM20D120A-2 1492-IFM20D24-3 1492-IFM20DS24-4 1492-IFM20DS120-4 1492-IFM20F-F-2 1492-IFM20F-F24-2 1492-IFM20F-F120-2 1492-IFM20F-F240-2 1492-IFM20F-F24A-2 1492-IFM20F-F120A-2 1492-IFM20F-FS-2 1492-IFM20F-FS24-2 1492-IFM20F-FS24A-4 1492-IFM20F-FS120-2 1492-IFM20F-FS120-4 1492-IFM20F-FS120A-4 1492-IFM20F-FS240-4

feed through feed through feed through feed through LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating fusible fusible fusible fusible fusible fusible fusible fusible fusible fusible fusible fusible fusible

standard narrow standard extra terminals 3-wire sensor type input devices standard with 24V ac/dc LEDs narrow standard with 24V ac/dc LEDs standard with 120V ac LEDs 24V ac/dc LEDS and extra terminals for outputs 24V ac/dc LEDS and extra terminals for inputs 120V ac LEDs and extra terminals for outputs 120V ac LEDs and extra terminals for inputs 3-wire sensor with 24V ac/dc LEDs isolated with 24/48V ac/dc LEDs and 4 terminals for outputs isolated with 120V ac LEDs and 4 terminals for outputs extra terminals for outputs extra terminals with 24V ac/dc blown fuse indicators for outputs extra terminals with 120V ac blown fuse indicators for outputs extra terminals with 240V ac blown fuse indicators for outputs extra terminals with 24V ac/dc blown fuse indicators for inputs extra terminals with 120V ac blown fuse indicators for inputs isolated with extra terminals for outputs isolated with extra terminals and 24V ac/dc blown fuse indicators for outputs isolated with 4 terminals and 24V ac/dc blown fuse indicators for inputs isolated with extra terminals with 120V ac blown fuse indicators for outputs isolated with 4 terminals with 120V ac blown fuse indicators for outputs isolated with 4 terminals with 120V ac blown fuse indicators for inputs isolated with 4 terminals with 240V ac blown fuse indicators for outputs

U U U

X X X X

X X X X X X

X X X X

X X X X X X

U U U

U U U

X X X

U U U

X X X

X X

X X X X X

X X X W W V V X X X X X X X W V V W W X

U W W U W V V V V

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

1756-SG001A-US-P July 2000

27

IFMs for 36-pin 1756 digital I/O modules

Catalog number: Type of IFM: Description: OB16D OW16I Y Y Y Y Y Y Y Y Y Y IB16D OB8EI OB16I OA16I IM16I OB32 IB16I IH16I OH8I OX8I Y Y Y Y Y Y Y Y Y IB32 Z Z Z Z Z Z Z IA6I 1492-IFM40F 1492-IFM40F-2 1492-IFM40F-3 1492-IFM40D24 1492-IFM40D24-2 1492-IFM40D24A-2 1492-IFM40D120-2 1492-IFM40D120A-2 1492-IFM40D24-3 1492-IFM40DS24-4 1492-IFM40DS24A-4 1492-IFM40DS120-4 1492-IFM40DS120A-4 1492-IFM40DS240A-4 1492-IFM40F-F-2 1492-IFM40F-F24-2 1492-IFM40F-F120-2 1492-IFM40F-FS-2 1492-IFM40F-FS24-2 feed through feed through feed through LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating LED indicating fusible fusible fusible fusible fusible standard extra terminals 3-wire sensor type input devices standard with 24V ac/dc LEDs 24V ac/dc LEDs and extra terminals for outputs 24V ac/dc LEDs and extra terminals for inputs 120V ac LEDs and extra terminals for outputs 120V ac LEDs and extra terminals for inputs 3-wire sensor with 24V ac/dc LEDs for inputs isolated with 24/48V ac/dc LEDs and 4 terminals per output isolated with 24/48V ac/dc LEDs and 4 terminals per input isolated with 120V ac LEDs and 4 terminals per output isolated with 120V ac LEDs and 4 terminals per input isolated with 240V ac LEDs and 4 terminals per output extra terminals for outputs extra terminals with 24V ac/dc blown fuse indicators for outputs extra terminals with 120V ac blown fuse indicators for outputs isolated with extra terminals for outputs isolated with extra terminals and 24V ac/dc blown fuse indicators for outputs isolated with 24V ac/dc blown fuse indicators and 4 terminals per output isolated with extra terminals and 120V ac blown fuse indicators for outputs isolated with 120V ac blown fuse indicators and 4 terminals per output isolated with 240V ac blown fuse indicators and 4 terminals per output isolated with 24V ac/dc blown fuse indicators and 4 terminals per input isolated with 120V ac blown fuse indicators and 4 terminals per input Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Z Z Y Y Y Z Y Y Y Y

Y Y

Y Y

Z Z

1492-IFM40F-FS24-4 1492-IFM40F-FS120-2

fusible fusible

1492-IFM40F-FS120-4 1492-IFM40F-FS240-4 1492-IFM40F-FS24A-4 1492-IFM40F-FS120A-4

fusible fusible fusible fusible

Y Y

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

1756-SG001A-US-P July 2000

28

Pre-wired cables for digital I/O modules

Catalog number:1 1492-CABLExU 1492-CABLExV 1492-CABLExW 1492-CABLExX 1492-CABLExY 1492-CABLExZ Number of conductors: 20 20 20 20 40 40 Conductor size: 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG Nominal outer diameter: 9.0 mm (0.36 in) 9.0 mm (0.36 in) 9.0 mm (0.36 in) 9.0 mm (0.36 in) 11.7 mm (0.46 in) 11.7 mm (0.46 in) RTB at the I/O module end: 1756-TBNH 1756-TBNH 1756-TBNH 1756-TBNH 1756-TBCH 1756-TBCH

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

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

Catalog number:1 1492-CABLExTBNH 1492-CABLExTBCH Number of conductors: 20 40
2

Conductor size: 18 AWG 18 AWG

Nominal outer diameter: 9.0 mm (0.36 in) 11.7 mm (0.46 in)

RTB at the I/O module end: 1756-TBNH 1756-TBCH

1. Cables are available in lengths of 0.5m, 1.0m, 2.5m, and 5.0m. To order, insert the code for the desired cable length into the catalog number in place of the x: 005=0.5m, 010=1.0m, 025=2.5m, 050=5m. 2. Four conductors are not connected to the RTB.

For example, a 1756-OB32 that requires LEDs and extra terminals uses: 1492-IFM40D24-2 interface module 1492-ACABLExZ cable (replace x with the appropriate length)

IFMs for 1756 analog I/O modules

IF16 (differential voltage) IF16 (differential current) Catalog number: IF16 (single-end voltage) IF16 (single-end current) IF8 (differential voltage) IF8 (differential current) IF8 (single-end voltage) IF8 (single-end current) Type of IFM: Description:

OF8 (voltage) WA

OF4 (voltage)

OF4 (current)

1492-AIFM4-3 1492-AIFM6S-3

feed through feed through feed through thermo couple fusible fusible fusible

4 channel with 3 terminals/channel 6 channel isolated with 3-4 terminals/channel 8 channel with 3 terminals/channel 6 channel with 3 terminals/channel 8 channel with 5 terminals/channel 16 channel with 3 terminals/channel 16 channel with 5 terminals/channel TA TB TC TC UA UA UB UB UC UC UD UD X Y Z

VA

VB Y Y

1492-AIFM8-3 1492-AIFM6TC-3 1492-AIFM8-F-5 1492-AIFM16-F-3 1492-AIFM16-F-5

TA

TB

TC

TD

UA

UB

UC

UD Y

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

1756-SG001A-US-P July 2000

OF8 (current) WB

IF6I (voltage)

IF6I (current)

OF6CI

OF6VI

IR6I

IT6I

29

Pre-wired cables for analog I/O modules

Catalog number:1 1492-ACABLExX 1492-ACABLExY 1492-ACABLExZ 1492-ACABLExTA 1492-ACABLExTB 1492-ACABLExTC 1492-ACABLExTD 1492-ACABLExUA 1492-ACABLExUB 1492-ACABLExUC 1492-ACABLExUD 1492-ACABLExVA 1492-ACABLExVB 1492-ACABLExWA 1492-ACABLExWB Number of conductors:2 9 twisted pair3 9 twisted pair4 20 conductors5 20 conductors 20 conductors 5 twisted pair 5 twisted pair 20 conductors 20 conductors 9 twisted pair 9 twisted pair 20 conductors 20 conductors 9 twisted pair 9 twisted pair Conductor size: 24 AWG 24 AWG 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG 22 AWG 24 AWG 24 AWG 22 AWG 22 AWG 24 AWG 24 AWG Nominal outer diameter: 6.8 mm (0.27 in) 6.8 mm (0,27 in) 8.4 mm (0.33 in) 8.4 mm (0.33 in) 8.4 mm (0.33 in) 8.4 mm (0.33 in) 8.4 mm (0.33 in) 8.4 mm (0.33 in) 8.4 mm (0.33 in) 6.8 mm (0.27 in) 6.8 mm (0.27 in) 8.4 mm (0.33 in) 8.4 mm (0.33 in) 6.8 mm (0.27 in) 6.8 mm (0.27 in) RTB at the I/O module end: 1756-TBNH 1756-TBNH 1756-TBNH 1756-TBCH 1756-TBCH 1756-TBCH 1756-TBCH 1756-TBCH 1756-TBCH 1756-TBCH 1756-TBCH 1756-TBNH 1756-TBNH 1756-TBNH 1756-TBNH

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

For example, a 1756-IF6I in voltage mode uses: 1492-AIFM6S-3 interface module 1492-ACABLExY cable (replace x with the appropriate length)

1756-SG001A-US-P July 2000

30

Placing ControlLogix I/O Modules

The producer/consumer model multicasts messages. This means that multiple nodes can consume the same data at the same time from a single device. Where you place I/O modules in the control system determines how the modules exchange data.
And you place the module here:
local chassis

If the I/O module is:

digital

The data exchange method is based on:

change of state and / or requested packet interval (cyclic)

remote chassis analog local chassis

requested packet interval real time sample and / or requested packet interval

remote chassis

requested packet interval

For a ControlLogix controller to control 1756 I/O, it must be either in the same chassis as the controller or on a ControlNet network that is local to that controller. Scheduled communication cannot be bridged between two 1756-CNB modules over a ControlLogix backplane. For example:
Chassis A Chassis B

Chassis C

41779

The ControlLogix controller in 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-SG001A-US-P July 2000

31

How ControlLogix I/O Modules Operate

Module Type: digital input Placement: local chassis

The type of module and where you place the module determines how the module operates:
Operation: The RPI specifies the rate at which a module multicasts its data. The time ranges from 200 microseconds to 750 milliseconds. When the specified time frame elapses, the module will multicast data (also called cyclic data exchange). If a change of state (COS) does not occur within the RPI timeframe, the module multicasts data at the rate specified by the RPI. Because the RPI and COS functions are asynchronous to the logic scan, it is possible for an input to change state during program scan execution. If this is a concern, buffer input data so your logic has a stable copy of data during its scan. Copy the input data from your input tags to another structure and use the data from that structure.

remote chassis

The RPI and COS values still define when the module multicasts data within its own chassis, but only the value of the RPI determines when the owner controller receives the data over the network. When an RPI value is specified for an input module in a remote chassis, in addition to instructing the module to multicast data within its own chassis, the RPI also reserves a spot in the stream of data flowing across the ControlNet network. The timing of this reserved spot may or may not coincide with the exact value of the RPI, but the owner-controller will receive data at least as often as the specified RPI.

digital output

local chassis

If the module resides in the same chassis as the owner-controller, the module receives the data almost immediately after the owner-controller sends it. Data is sent at the end of each program scan. If an output module resides in a chassis other than that of the owner-controller (i.e. a remote chassis connected via ControlNet), the owner-controller sends data to the output module only at the RPI rate. The RPI also reserves a spot in the stream of data flowing across the ControlNet network. The timing of this reserved spot may or may not coincide with the exact value of the RPI, but the output module receives data at least as often as the specified RPI.

remote chassis

1756-SG001A-US-P July 2000

32

Module Type: analog input

Placement: local chassis

Operation: The RTS value specifies when the module scans its channels and multicasts the data (update the input data buffer then multicast). The RPI value specifies when the module multicasts the current contents of the input data buffer without scanning (updating) the channels. The module resets the RPI timer each time an RTS transfer occurs. If the RTS value is less than or equal to the RPI value, each multicast of data from the module has newly updated channel data. The module only multicasts at the RTS rate. If the RTS value is greater than the RPI, the module multicasts at both the RTS rate and the RPI rate.

remote chassis

The RPI and RTS rates still define when the module multicasts data within its own chassis, but only the RPI value determines when the owner-controller receives the data over the network. The RPI also reserves a spot in the stream of data flowing across the ControlNet network. The timing of this reserved spot may or may not coincide with the exact value of the RPI, but the controller receives data at least as often as the specified RPI.

analog output

local chassis

The RPI value specifies when the owner-controller broadcasts output data to the module. If the module resides in the same chassis as the owner-controller, the module receives the data almost immediately after the owner-controller sends it. If an output module resides in a chassis other than that of the owner-controller (i.e. a remote chassis connected via ControlNet), the owner-controller sends data to the output module only at the RPI rate. The RPI also reserves a spot in the stream of data flowing across the ControlNet network. The timing of this reserved spot may or may not coincide with the exact value of the RPI, but the output module receives data at least as often as the specified RPI.

remote chassis

Selecting Controller Ownership Every I/O module in the ControlLogix system must be owned by a
ControlLogix controller. The owner controller stores configuration data for every I/O module that it owns and can be local or remote in regard to the I/O modules position. The owner controller sends the I/O configuration data to define the I/O modules behavior and to start the I/O modules operation within the control system. Each ControlLogix I/O module must continuously maintain communication with its owner controller to operate normally. Typically, each I/O module has only one owner. Because listen-only controllers lose their connections to modules when communications with the owner controller stop, you can define more than one owner for an input module. If multiple controllers own the same input module, each controller must maintain identical configuration for that input module. An output module is limited to one owner.

1756-SG001A-US-P July 2000

Planning Motion

33

Planning Motion
The ControlLogix system takes a new approach to integrating motion and sequential control. The ControlLogix system performs both these functions within the ControlLogix controller.

1.

Place 2-axis servo module(s) in the ControlLogix chassis and wire to field devices.
2 AXIS SERVO
Logix5550
RUN I/O RS232

4.

Download the application to the ControlLogix controller and run.

ControlNET POWER

ETHERNET

DH+/RIO

DC OUTPUT
ST 0 1 2 3 4 5 6 7

AC OUTPUT

BAT

OK
ST 0 1 2 3 4 5 6 7 O

A#24
OK B A RXD TXD OK

B#15
CH A CH B OK

FLT 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K FLT 8 9 10 11 12 13 14 15

RUN

REM

PROG

FLT 0 1 2 3 4 5 6 7 K

DIAGNOSTIC

DIAGNOSTIC

2.

Use RSLogix5000 software to name and configure each motion axis.

3.

Use RSLogix5000 software to develop a motion application.

30676

The ControlLogix controller executes the ladder motion commands. Each controller and chassis can control up to 16 1756-M02AE servo modules (for a total of 32 axes). The 1756-M02AE servo modules must be in the same local chassis as its ControlLogix controller. The 1756-M02AE servo module connects to a servo drive and closes a high-speed position and velocity loop. Each 1756-M02AE module can control up to two axes. RSLogix 5000 programming software provides complete axis configuration and motion programming support.
RSLogix5000 Software Integrated Motion Programming ControlLogix Controller Program Execution 1756-M02AE Servo Module Drive Position Velocity Motor Feedback Drive Position Velocity Motor Feedback
41383

Axis Configuration

Motion Trajectory Planner Position Velocity

1756-SG001A-US-P July 2000

34

Planning Motion

1756-M02AE Servo Module

The servo module is a 2-axis, closed-loop servo module that receives profile information from the ControlLogix controller. The servo module makes sure that the actuator (motor) follows the profile by monitoring the position feedback via the quadrature encoder input and generating an analog command reference for the drive. A position and velocity loop is closed every 200 s using position feedback as the input and 10V analog output. Important: The servo module must be in the same chassis as the ControlLogix controller that controls the servo module. If you distribute motion control across different locations, place a ControlLogix controller in each chassis that has a servo module.
Description: number of axes per ControlLogix controller number of axes per module power dissipation backplane current Value: 32 axes maximum 2 axes maximum 5.5W maximum 700 mA @ 5V dc 2.5 mA @ 24V dc 3.56W 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 95% noncondensing coarse update rate: 2 ms 3 ms 4 ms 5 ms 6 ms 7 ms 8 ms 9 ms 10 ms 11 ms 12 ms 13 ms 14 ms 15 ms 16 ms 17 ms 18 ms 19 ms 20 ms 21 ms 22 ms 23 ms 24 ms maximum number of axes: 2 3 4 6 7 8 10 11 13 14 15 17 18 20 21 22 24 25 26 28 29 30 32

operating temperature storage temperature relative humidity maximum number of axes per coarse update rate The coarse update rates assume that the servo is on for each axis and that each axis has an active trapezoidal move.

servo loop type gain resolution absolute position range rate encoder input type mode rate electrical interface voltage range input impedance

nested PI digital position and velocity servo 32-bit floating point 1,000,000,000 encoder counts 5 kHz incremental AB quadrature with marker 4X quadrature 4 MHz counts per second maximum optically isolated 5V differential 3.4V to 5.0V differential 531 Ohms differential

1756-SG001A-US-P July 2000

Planning Motion
Description: registration inputs type 24V input voltage maximum minimum on maximum off 5V input voltage maximum minimum on maximum off input impedance 24V input 5V input response time all other inputs type input voltage maximum minimum on maximum off input impedance servo output type isolation voltage range voltage resolution load maximum offset gain error all other outputs type operating voltage maximum operating current removable terminal block (RTB) RTB screw torque (cage clamp) conductors wire size category agency certification (when product or packaging is marked)1 Value: optically isolated, current sourcing input +24V dc nominal 26.4V 18.5V 3.5 +5V dc nominal 5.5V 3.7V 1.5V 1.2 kOhms 9.5 kOhms 1s optically isolated, current sinking input +24V dc nominal 26.4V 17.0V 8.5V 7.5 kOhms analog voltage 200 kOhms 10V 16 bits 5.6 kOhms resistive minimum 25 mV 4% solid-state isolated relay contacts +24V dc nominal (Class 2 source) 26.4V 75 mA 1756-TBCH 1756-TBSH6 5lb-in. (0.5 Nm) maximum 14 gauge (2mm2) stranded maximum2 3/64 inch (1.2 mm) insulation maximum 23 marked for all applicable directives FM approved

35

1. CSA certification - Class I Division 2, Group A, B, C, D or nonhazardous locations. 2. Maximum wire size will require the extended depth RTB housing (1756-TBE). 3. Use this conductor category information for planning conductor routing as described in the system level installation manual. See the Programmable Controller Wiring and Grounding Guidelines, publication number 1770-4.1.

1756-SG001A-US-P July 2000

36

Planning Motion

Motion Cables
Catalog Number: 1394-CCAExx xx = 01 for 1 meter
03 for 3 meter 08 for 8 meter 15 for 15 meter
Enable/Drive Fault

If you connect the 1756-M02AE module to a 1394 or 1398 series servo drive, choose one of these cables:
Description: 1756-M02AE to a 1394 two-axis, analog servo module
Enable/Drive Fault 7 12 1 Axis 0 6
36 34 32 30 28 26 24 22 20 18 16 14 12 10 8 6 4 2

+5V AX0

System OK 7 12 1 Axis 1 6

1756-M02AE

35

33

31

29

27

25

23

21

19

17

15

13

11

+5V AX1

1398-CCAExx xx = 01 for 1 meter

03 for 3 meter 08 for 8 meter 15 for 15 meter

1756-M02AE to a 1398 two-axis, analog servo module

Axis 0 - J1
36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

24V - AX0 Brake - AX0 Reset - AX0

Axis 1 - J1

Reset - AX1 Brake - AX1 24V - AX1

1394-CFLAExx xx = 01 for 1 meter

03 for 3 meter 08 for 8 meter 15 for 15 meter

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

ENABLE/DRIVE FAULT - AXIS 0

Individually Jacketed Pairs

AXIS 0 1394-CFLAE 1756-M02AE 5V ENC PWR - AXIS 0

7
3.0 in.

1 6
M02AE - OK

12

1.0 in. 5.0 in.

1398-CFLAExx xx = 01 for 1 meter

03 for 3 meter 08 for 8 meter 15 for 15 meter

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

1.0 in.
24V

Individually Jacketed pairs

BRAKE RESET 1398-CFLAE J1

5.0 in.

1756-SG001A-US-P July 2000

Planning Motion

37

Developing a Motion Application

The ControlLogix system combines the controller, servo module, and programming software into a working motion application. You need only one programming software package to develop sequential and motion logic. The ControlLogix controller executes the motion functions. The dedicated servo modules perform the position and velocity loop closure. The ControlLogix backplane feature of coordinated system time (CST) synchronizes the controllers and the servo modules and facilitates passing command and status information. To develop a motion application:

Task: Specify the coordinated system time

Description: You must configure one ControlLogix controller, in the same chassis as the motion module, to be the master controller for coordinated system time. You can compare CST data from modules within a single chassis to determine the relative time between data samples.

Add a motion module

Add the motion modules you need to the configuration of the master ControlLogix controller. The motion module must reside in the same chassis as the controller to be synchronized with that controllers coordinated system time. For each motion module you add, name each axis you configure for the module. Each module can support as many as 2 axes. You specify the type of axis and the axis positioning. You can also assign axes to a motion group.

Name and configure each axis

Run hookup diagnostics and auto tuning

After you add all the motion modules and configure all the axes, run the hookup diagnostics and auto tuning utilities to make sure the motion modules are ready to operate. The ControlLogix system includes a common programming software package that you can use to program your motion logic, as well as your sequential logic.

Develop the motion control logic

1756-SG001A-US-P July 2000

38

Planning Motion

Calculating Coarse Update Rates

To calculate the coarse update rate for the number of motion modules and axes in your ControlLogix system, use this formula (see below for definitions of the variables):

Baseline task time

(Actions for axis 1)

(Actions for axis 2)

(Actions for axis n)

Execution time

Defining baseline task time

The baseline task time is the time it takes to update the motion modules. The task time increases as the number of modules increases:
Number of modules: 1 (2 axes maximum) 2 (4 axes maximum) 3 (6 axes maximum) 4 (8 axes maximum) 5 (10 axes maximum) 6 (12 axes maximum) 7 (14 axes maximum) 8 (16 axes maximum) Baseline task time in s: 415 590 765 940 1115 1290 1465 1640 Number of modules: 9 (18 axes maximum) 10 (20 axes maximum) 11 (22 axes maximum) 12 (24 axes maximum) 13 (26 axes maximum) 14 (28 axes maximum) 15 (30 axes maximum) 16 (32 axes maximum) Baseline task time in s: 1815 1960 2165 2340 2515 2690 2865 3040

Defining action timing

An axis can perform these actions:
Action: Turning the module on Performing a trapezoidal move Performing an S-curve move Performing a trapezoidal jog Performing an S-curve jog Performing an actual position gear Performing a command position gear Action execution time in s: 60 440 180 70 80 440 320

1756-SG001A-US-P July 2000

Ethern

et

Con

trolNet et

Dev

iceN

Planning Network Communications

39

Planning Network Communications

Interfacing with communication networks is modular, except for the RS-232 serial (DF1 protocol) port built into the front of the ControlLogix controller. Separate communication interface modules are available for interfacing the backplane with Ethernet, ControlNet, DeviceNet, DH+, and Universal Remote I/O networks. If you place multiple communication interface modules in a ControlLogix backplane, you can configure a gateway to bridge and route control and information data between networks. A ControlLogix controller communicates across the backplane with 1756 I/O modules in the local chassis. A ControlLogix controller can also communicate across the backplane with communication interface modules to monitor and control I/O on ControlNet, DeviceNet, and the Universal Remote I/O networks and to monitor Foundation Fieldbus data. General communication messages can be sent from or received by ControlLogix controllers across Ethernet, ControlNet, DeviceNet, DH+, Universal Remote I/O, and RS-232 serial (DF1 protocol) networks. Messages are sent directly from one communication interface module to another across the backplane. You can route a message through a maximum of 4 chassis (8 communication hops). You determine your communication architecture based on your networking needs. There are three main types of networks:

Information networks

41760

An information network: provides a link between the plant floor and manufacturing systems connects to multiple vendors host computers has the capacity to transfer large data files supports standard network management and troubleshooting tools A control network: offers real-time performance is deterministic and repeatable supports peer-to-peer messaging connects to programmable controllers, personal computers, man-machine interface devices, drives, motion devices, etc. support programming and device configuration A device network: reduces wiring costs because devices do not need to be directly wired to a programmable controller supports device-level diagnostics connects to multiple vendors devices

Control networks

41761

Device networks

41762

1756-SG001A-US-P July 2000

Ethern

et

40

Planning Network Communications

Con

trolNet et

Dev

iceN

You can configure your system for information exchange between a range of devices and computing platforms and operating systems. You select the communication interface module(s) for the network(s) that meet your needs:
If your application requires: high-speed transfer of time-critical data between controllers and I/O devices deterministic and repeatable data delivery program maintenance media redundancy or intrinsic safety options connections between controllers and I/O adapters distributed controllers so that each controller has its own I/O and communicates with a supervisory controller connections of low-level devices directly to plant floor controllers, without the need to interface them through I/O modules more diagnostics for improved data collection and fault detection less wiring and reduced start-up time than a traditional, hard-wired system Fieldbus transmitters and actuators closed-loop control process automation recommended medium for plant-wide sharing of data high-speed data transfer between information systems and/or a large quantity of controllers Internet/Intranet connection program maintenance plantwide and cell-level data sharing with program maintenance modems supervisory control and data acquisition (SCADA) Use this network: ControlNet network see page 43 Type:

control and information network

Universal Remote I/O network see page 52 DeviceNet network see page 47

control network

device network

Fieldbus network see page 49 Ethernet network see page 45

device network

information network

Data Highway Plus see page 51 serial network see page 54

information network serial network

Connecting Devices Across Multiple Platforms

You can use your ControlLogix system to bridge and route control and information data. Communication does not depend on a controller in the chassis. You can bridge across these networks: DH+ network Ethernet network ControlNet network

1756-SG001A-US-P July 2000

Ethern

et

Con

trolNet et

Dev

iceN

Planning Network Communications

41

Bridging between devices

DH+/RIO POWER

ETHERNET

ControlNET

B#15
CH A CH B OK RXD TXD OK

A#24
OK B A

ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

ControlLogix system
B A

DH+ network

ControlNet network Ethernet network

PLC-5 processor

PLC-5E processor

PLC-5C processor

SLC controller

workstation with RSLinx

workstation with RSLinx

workstation with RSLinx

20902

Reply Origin

DH+ network PLC-5 processor SLC 5/04 processor yes yes yes yes yes yes yes RSLinx software yes yes na yes na yes na

Ethernet network PLC-5E processor yes yes yes yes yes yes yes RSLinx software yes yes na yes na yes na

ControlNet network PLC-5C processor yes yes yes yes yes yes yes RSLinx processor yes yes na yes na yes na

DH+ network

PLC-5 processor SLC-5/04 processor RSLinx software

yes yes yes yes yes yes yes

Ethernet network

PLC-5E processor RSLinx software

ControlNet network

PLC-5C processor RSLinx software

1756-SG001A-US-P July 2000

Ethern

et

42

Planning Network Communications

Con

trolNet et

Dev

iceN

Distributed DH+ bridging

DH+ network ControlNet network Ethernet network
DH+/RIO ControlNET ETHERNET POWER DH+/RIO ControlNET ETHERNET

ControlLogix system

POWER

B#15
CH A CH B OK

A#24
OK B A RXD TXD OK

ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

B#15
CH A CH B OK

A#24
OK B A RXD TXD OK

ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

ControlLogix system

SLC controller PLC-5 processor workstation with RSLinx PLC-5 processor

SLC controller workstation with RSLinx

20902

Reply Origin

DH+ network PLC-5 processor SLC 5/04 processor yes yes yes RSLinx software yes yes na

DH+ network

PLC-5 processor SLC-5/04 processor RSLinx software

yes yes yes

Distributed ControlNet bridging

DH+ network ControlNet network Ethernet network
DH+/RIO POWER ControlNET ETHERNET POWER DH+/RIO ControlNET ETHERNET

B#15

A#24
OK B A RXD TXD OK

ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

B#15
CH A CH B OK

A#24
OK B A RXD TXD OK

ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

ControlLogix system

CH A CH B OK

ControlLogix system

PLC-5 processor

workstation with RSLinx

PLC-5 processor

workstation with RSLinx

20899

Reply Origin

ControlNet network PLC-5 processor RSLinx software yes na

ControlNet network

PLC-5 processor RSLinx software

yes yes

1756-SG001A-US-P July 2000

Ethern

et

Con

trolNet et

Dev

iceN

Planning Network Communications

43

ControlNet Network

The ControlNet network is an open, high-speed, and deterministic network used for transmitting time-critical information. It provides real-time control and messaging services for peer-to-peer communication. As a high-speed link between controllers and I/O devices, a ControlNet network combines the capabilities of existing Universal Remote I/O and DH+ networks. You can connect a variety of devices to a ControlNet network, including personal computers, controllers, operator interface devices, drives, I/O modules, and other devices with ControlNet connections. At the control layer, a ControlNet network combines the functionality of an I/O network and a peer-to-peer messaging network. This open network provides the performance required for critical control data, such as I/O updates and controller-to-controller interlocking. ControlNet also supports transfers of non-critical data, such as program uploads, downloads, and messaging.
workstation running programming software with 1784-KTCx

ControlNet

PanelView 1200 operator terminal ControlLogix Gateway or ControlLogix controller PLC-5/40C controller
41393

1395 drive

1756-CNET ControlNet statistics

Rates: transmission: 5 Mbps network update time: 2-100ms Cable lengths: 1000m (3,280 ft.) with 2 devices 250m (820 ft.) with a maximum of 48 devices tap drop cable length fixed at 1m (3 ft.) maximum distance 6km with repeaters Maximum number of nodes: 99

1756-SG001A-US-P July 2000

Ethern

et

44

Planning Network Communications

Con

trolNet et

Dev

iceN

1756-CNB, -CNBR ControlNet communication interface module

The ControlNet communication module bridges ControlNet links to route messages to devices on other networks, such as Ethernet, ControlNet, and Data Highway Plus networks. The ControlNet communication module also monitors and controls 1756 I/O modules located remotely from the ControlLogix controller. You can use the ControlNet communication module with a ControlLogix controller in the same chassis or in a ControlLogix Gateway (without a controller).
Description: communication rate connections cable Value: 5 Mbps 64 connections per module RG-6 coaxial cable 1786-RG6 (shield high flex cable) 1786-RG6F (quad shield high flex coax cable) 1786-XT Choose: 1786-TPR (T-tap right angle) 1786-TPS (T-tap straight) 1786-TPYR (Y-tap right angle) 1786-TPYS (Y-tap straight) 1756-CNB 970mA @ 5V dc 1.7mA @ 24V dc 4.98W 2 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 95% noncondensing 10 to 150 Hz 5.0 G maximum peak acceleration 30G peak for 11ms 50G peak for 11ms 1756-CNB 1756-CNBR 0.3 kg (0.6 lb) 0.3 kg (0.7 lb) 1756-CNBR 1000mA @ 5V dc 1.7mA @ 24V dc 5.14W

termination resistor tap

backplane current

conductor category operating temperature storage temperature relative humidity vibration operating shock storage shock weight agency certification1

Class I Division 2 Hazardous marked for all applicable directives

1. CSA certification - Class I Division 2, Group A, B, C, D or nonhazardous locations.

1756-SG001A-US-P July 2000

Ethern

et

Con

trolNet et

Dev

iceN

Planning Network Communications

45

Ethernet Network

The TCP/IP Ethernet network is a local area network designed for the high-speed exchange of information between computers and related devices. With its high bandwidth (10Mbps), an Ethernet network allows many computers, controllers, and other devices to communicate over vast distances. At the information layer, an Ethernet network provides enterprise-wide systems access to plant-floor data. With an Ethernet network you have many possibilities because you can maximize communication between the great variety of equipment available from many vendors. TCP/IP is the protocol used by the Internet.
laptop

Internet

modem gateway

server personal computer workstation HP 9000 or VAX computer ControlLogix controller SLC-5/05 controller

Ethernet

ControlLogix Gateway or ControlLogix controller PLC-5 controller with Ethernet sidecar module

Ethernet Gateway

PLC-5 controller

Data Highway Plus ControlNet

41763

1756-ENET Ethernet statistics

Cable options: 10Base5 10Base2 10BaseT 10BaseFL 10 Mbps Data transmission rate: Maximum cable length: 500m 185m 100m 2000m Maximum drop cable length: 50m 50m na na Maximum number of nodes: 100 30 2 peer-to-peer 2 peer-to-peer Maximum length with repeaters: 2.5km 925m na na

1756-SG001A-US-P July 2000

Ethern

et

46

Planning Network Communications

Con

trolNet et

Dev

iceN

1756-ENET Ethernet communication interface module

The Ethernet communication module bridges Ethernet links to route messages to devices on other networks, such as ControlNet, DeviceNet, and Data Highway Plus networks.
Description: communication rate connections Value: 10 Mbps 64 TCP/IP connections 48 ControlLogix connections maximum per 1 TCP/IP connection 128 ControlLogix connections maximum per module The Ethernet module also supports 128 in and 128 out unscheduled ControlLogix connections. Unscheduled connections within a TCP/IP connection do not count to the total of 48 possible ControlLogix connections. cable Choose: 1756-TC02 (low-profile 2-meter transceiver cable) 1756-TC15 (low-profile 15-meter transceiver cable) Choose: 1785-TR10B2 (thin wire) 1785-TR10B5 (thick wire) 1785-TR10BF (fiber optic) 1785-TR10BT (twisted pair) 900mA @ 5V dc 350mA @ 24V dc 12.99W 2 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 95% noncondensing 10 to 150 Hz 5.0 G maximum peak acceleration 30G peak for 11ms 50G peak for 11ms 0.3 kg (0.6 lb)

transceiver

backplane current

conductor category operating temperature storage temperature relative humidity vibration operating shock storage shock weight agency certification1

Class I Division 2 Hazardous marked for all applicable directives

1. CSA certification - Class I Division 2, Group A, B, C, D or nonhazardous locations.

1756-SG001A-US-P July 2000

Ethern

et

Con

trolNet et

Dev

iceN

Planning Network Communications

47

DeviceNet Network

A DeviceNet network is an open, low-level communication link that provides connections between simple, industrial devices (such as sensors and actuators) and high-level devices (such as controllers). Based on standard Controller Area Network (CAN) technology, this open network offers interoperability between devices from multiple vendors. A DeviceNet network provides:
Benefit: simple devices from multiple vendors that meet DeviceNet standards are interchangeable, giving you flexibility and choice an open network provides common, end-user solutions, and reduces the need to support a wide variety of device networks you can remove and replace devices without disrupting other devices a networked device installation is more cost-effective than traditional I/O wiring because one wire supplies both communications and 24V power

Feature: interoperability common network lower maintenance costs cost-effective wiring

At the device layer, a DeviceNet network can connect low-level devices directly to plant-floor controllers.
PLC-5 controller with 1771-SDN scanner module

ControlLogix controller with 1756-DNB module

DeviceNet

other devices laptop motor starter

sensor pushbutton cluster

input/output devices drive

bar code scanner indicator lights

41394

1756-DNET DeviceNet statistics

Data transmission rate: 125 Kbps 250 Kbps 500 Kbps Cable trunk length: 500m (1,640 ft.) 250m (820 ft.) 100m (328 ft.) Cumulative drop length: 125m (512 ft.) 78m (256 ft.) 39m (128 ft.) 6 m (20 ft.) 64 Maximum drop length: Maximum number of nodes:

1756-SG001A-US-P July 2000

Ethern

et

48

Planning Network Communications

Con

trolNet et

Dev

iceN

1756-DNB DeviceNet scanner interface module

The DeviceNet scanner module acts as an interface between DeviceNet devices and a ControlLogix chassis. The scanner module communicates with DeviceNet devices over the network to: read and write inputs and outputs to and from a device download configuration data to a device monitor operational status of a device The scanner module communicates with a ControlLogix controller in a ControlLogix chassis to provide I/O data, status information and configuration data.
Description: communication rate connections cable Value: 125 Kbps, 250 Kbps, or 500 Kbps 2 connections to a dedicated ControlLogix controller Choose: 1485C-P1-C50 (thin, yellow, chemical resist, 50 meters) 1485C-P1-C150 (thin, yellow, chemical resist, 150 meters) 1485C-P1-C300 (thin, yellow, chemical resist, 300 meters) 1485C-P1-C600 (thin, yellow, chemical resist, 600 meters) 1485C-P1-A50 (thick, grey, 50 meters) 1485C-P1-A150 (thick, grey, 150 meters) 1485C-P1-A300 (thick, grey, 300 meters) 1485C-P1-A500 (thick, grey, 500 meters) 1485A-C2 Choose: 1485P-P2T5-T5 (2 ports) 1485P-P4T5-T5 (4 ports) 1485P-P8T5-T5 (8 ports) 600mA @ 5V dc 3mA @ 24V dc 3.13W 2 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 95% noncondensing 10 to 150 Hz 5.0 G maximum peak acceleration 30G peak for 11ms 50G peak for 11ms 0.3 kg (0.6 lb)
1

termination resistor tap

backplane current

conductor category operating temperature storage temperature relative humidity vibration operating shock storage shock weight agency certification

Class I Division 2 Hazardous marked for all applicable directives

1. CSA certification - Class I Division 2, Group A, B, C, D or nonhazardous locations.

1756-SG001A-US-P July 2000

Ethern

et

Con

trolNet et

Dev

iceN

Planning Network Communications

49

Fieldbus Network

A Foundation Fieldbus network is a standard-based network designed to handle process automation applications. Fieldbus interconnects measurement and control equipment, such as sensors, actuators, and controllers. The Fieldbus environment is the base level network in the hierarchy of plant networks. At the device layer, a Fieldbus network can connect low-level devices directly to plant-floor controllers.

laptop ControlNet

ControlLogix controller with 1756-CNB module

Fieldbus linking device

transmitter actuator display

transmitter

transmitter digital mux actuator analog mux

1756-SG001A-US-P July 2000

Ethern

et

50

Planning Network Communications

Con

trolNet et

Dev

iceN

1788-CN2FF Foundation Fieldbus Linking Device

The Foundation Fieldbus linking device facilitates distributed control by adding Foundation Fieldbus support to your ControlLogix system. You can have one linking device per ControlNet tap. The linking device: connects to two, independent Fieldbus H1 networks mounts on a 35mm DIN rail supports closed-loop control Process variables published on Foundation Fieldbus are subscribed by the linking device and then produced on the ControlNet network at the network update time. Scheduled data from a linking device can go to a ControlLogix controller every 2 milliseconds. Conversely, process variables produced by a ControlNet device can be consumed by the linking device and subscribed by other Foundation Fieldbus devices.
Description: communication rate connections cable power requirements conductor category operating temperature storage temperature relative humidity vibration operating shock storage shock weight agency certification
1

Value: 2 ms over ControlNet 31.25 Kbps over Fieldbus to redundant ControlNet media for each H1 network each linking device supports two H1 networks 9-pin FieldBus cable pins 6 and 7 handle Fieldbus signals 11-30V dc 270 mA @ 24V dc (typical) 2 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 90% noncondensing 10-500Hz per IEC 68-2-6 2.0 G maximum peak acceleration 30G peak for 11ms 50G peak for 11ms 0.4 kg (13.5 oz.)

Class I Division 2 Hazardous marked for all applicable directives

1. CSA certification - Class I Division 2, Group A, B, C, D or nonhazardous locations.

1756-SG001A-US-P July 2000

Ethern

et

Con

trolNet et

Dev

iceN

Planning Network Communications

51

DH+ Network

The Data Highway Plus network is a local area network designed to support remote programming and data acquisition for factory-floor applications. You can also use DH+ communication modules to implement a small peer-to-peer network. You can use a DH+ network for data transfer to other controllers or high-level computers and as a link for programming multiple controllers. A ControlLogix controller can communicate over a DH+ network with other controllers and with a workstation. The DH+ network supports daisy chain and trunkline-dropline configurations.
PLC-5 controller workstation with RSLogix 5000 software workstation

Data Highway Plus

SLC-5/04 controller

ControlLogix chassis with 1756-DHRIO module

41764

1756-DHRIO DH+ statistics

Data transmission rate: Maximum cable length: 57.6 Kbps 3,048m (10,000 ft.) Maximum number of nodes: 64 per link

1756-SG001A-US-P July 2000

Ethern

et

52

Planning Network Communications

Con

trolNet et

Dev

iceN

Universal Remote I/O Network

The strength and versatility of the Universal Remote I/O network comes from the breadth of products it supports. In addition to 1771 I/O, the Universal Remote I/O network supports many Allen-Bradley and third-party devices. Typical applications range from simple I/O links with controllers and I/O modules, to links with a variety of other devices. You connect devices through remote I/O adapter modules or built-in remote I/O adapters.

workstation with PanelBuilder software

ControlNet, Ethernet, or DH+ network

ControlLogix chassis

Universal remote I/O link

FLEX I/O adapter 1791 I/O block PLC-5 controller in adapter mode PanelView 1200 operator terminal
41765

Universal remote I/O statistics

Data transmission rate: 57.6 Kbps 115.2 Kbps 230.4 Kbps Maximum cable length: 3,048m (10,000 ft.) 1,524m (5,000 ft.) 762m (2,500 ft.) 1 scanner 32 adapters Maximum number of nodes:

1756-SG001A-US-P July 2000

Ethern

et

Con

trolNet et

Dev

iceN

Planning Network Communications

53

1756-DHRIO Data Highway Plus and remote I/O communication interface module
The Data Highway Plus and remote I/O module supports messaging between devices on Data Highway Plus networks and devices on other networks, such as Ethernet, ControlNet, and DeviceNet networks. The remote I/O functionality enables the module to act as a scanner for transferring discrete and block-transfer data to and from remote I/O devices.
Description: communication rate connections Value: DH+: 57.6 Kbps Universal Remote I/O: 57.6 Kbps, 115 Kbps, or 230 Kbps 32 connections per DH+ channel 32 logical rack connections per remote I/O channel 16 block-transfer connections per remote I/O channel cable termination resistor backplane current 1770-CD Belden 9463 150 Ohm and 82 Ohm resistors ship with the 1756-DHRIO module 850mA @ 5V dc 1.7mA @ 24V dc 4.38W 2 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 95% noncondensing 10 to 150 Hz 5.0 G maximum peak acceleration 30G peak for 11ms 50G peak for 11ms 0.3 kg (0.6 lb)

conductor category operating temperature storage temperature relative humidity vibration operating shock storage shock weight agency certification1

Class I Division 2 Hazardous marked for all applicable directives

1. CSA certification - Class I Division 2, Group A, B, C, D or nonhazardous locations.

1756-SG001A-US-P July 2000

Ethern

et

54

Planning Network Communications

Con

trolNet et

Dev

iceN

Serial Network

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

Use this DF1 mode: point to point DF1 master DF1 slave user mode (ASCII)

DH+ Ethernet RS-232 RS-232

RS-232

modem

modem

modem

41766

The ControlLogix controller uses a 1756-CP3 cable to connect to the serial port. Or you can make a 9-pin cable using these pinouts:
1 CD 2 RDX 3 TXD 4 DTR 5 COMMON 6 DSR 7 RTS 8 CTS 9 RI straight cable end 1 CD 2 RDX 3 TXD 4 DTR 5 COMMON 6 DSR 7 RTS 8 CTS 9 RI right-angle cable end

40046

The cable is shielded and tied to the connector housing at both ends.

1756-SG001A-US-P July 2000

Ethern

et

Con

trolNet et

Dev

iceN

Planning Network Communications

55

1756-MVI, -MVID multi-vendor interface module

The multi-vendor interface module provides additional access to serial devices. The module is user programmable to accommodate devices with unique serial protocols. The module has three ports:
Port: PRT1 (console) PRT2 PRT3 Description: Connect a programming device via a RS-232 interface. Connect to other devices via a RS-232, RS-422, or RS-485 interface.

Use the application programming interface (API) software to access the ControlLogix backplane and module serial ports. Develop applications for the module using industry-standard DOS programming tools and the appropriate API components.
Description: options communication rate connections cable Value: 1756-MVI 1756-MVID module by itself module and API software

configurable, depending on serial protocol 1 3 serial adapter cables ship with the module the locking-type RJ45 connector installs in the module; the other end is a DB-9 male connector 800mA @ 5V dc 3mA @ 24V dc 4W 2 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 95% noncondensing 10 to 150 Hz 5.0 G maximum peak acceleration 30G peak for 11ms 50G peak for 11ms

backplane current

conductor category operating temperature storage temperature relative humidity vibration operating shock storage shock agency certification
1

Class I Division 2 Hazardous marked for all applicable directives

1. CSA certification - Class I Division 2, Group A, B, C, D or nonhazardous locations.

1756-SG001A-US-P July 2000

Ethern

et

56

Planning Network Communications

Con

trolNet et

Dev

iceN

Other Networks

The RSLogix 5000 programming software supports a generic ControlNet module that allows connections to ControlNet nodes for which there is no specific support currently available in the programming software. A module configured as a generic ControlNet module communicates with the controller in the form of input, output, status, and configuration tags. These tags and their characteristics vary depending on the type of module. For example, use the generic module configuration to set up communications between a ControlLogix controller and a 1203-CN1 ControlNet communications module.

Then use the CIP generic MSG instruction type to send and receive messages from the 1203-CN1 module.

The screens above show the connection parameters for the 1203-CN1 module. These parameters differ depending on the module. See the modules vendor for modules characteristics.

1756-SG001A-US-P July 2000

57

Selecting a Controller
The ControlLogix controller provides a scalable controller solution that is capable of addressing a large amount of I/O points (128,000 digital maximum / 4000 analog maximum). The controller can control local I/O as well as remote I/O across ControlNet, DeviceNet, and Universal Remote I/O networks. You can place multiple ControlLogix controllers in a single ControlLogix chassis. Multiple controllers can read input values from all inputs. A single controller can communicate over multiple communication modules and multiple controllers can share the same communication module.

1756 ControlLogix Controller

Description: Value: 1756-L1 user available memory1 backplane current +5V dc +24V dc average power dissipation average thermal dissipation operating temperature storage temperature relative humidity vibration operating shock storage shock weight programming cable battery agency certification2 64 Kbytes 0.65A 0.02A 3.0W 10.2 BTU/hr 1756-L1M1 512 Kbytes 0.95A 0.02A 3.75W 12.8 BTU/hr 1756-L1M2 1 Mbyte 1.05A 0.02A 4.0W 13.7 BTU/hr 1756-L1M3 2 Mbytes 1.20A 0.02A 4.25W 14.5 BTU/hr 1756-L55M134 1.5 Mbytes 1.15A 0.02A 4.50W 15.4 BTU/hr 1756-L55M143 3.5 Mbytes 1.25A 0.02A 4.75W 16.2 BTU/hr 1756-L55M163 7.5 Mbytes 1.40A 0.02A 5.0W 17.1 BTU/hr

0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5% to 95% noncondensing 10 to 500 Hz 2.0 G maximum peak acceleration 30G peak for 11ms 50G peak for 11ms 10.0 oz. 12.5 oz. 12.5 oz. 12.7 oz. 12.5 oz. 12.8 oz. 13.4 oz.

1756-CP3 or 1747-CP3 serial cable category 33 1756-BA1 (PROMARK Electronics 94194801) 0.59g lithium

Class I Division 2 Hazardous marked for all applicable directives marked for applicable acts
N223

1. 2. 3. 4.

Available user memory is the amount of memory available to the user after RSLogix 5000 programming software is connected and a null program is loaded. CSA certification - Class I Division 2, Group A, B, C, D or nonhazardous locations. See the Programmable Controller Wiring and Grounding Guidelines, publication 1770-4.1. The Logix5555 controller will be available fall/winter 2000. These specifications are planned characteristics for the controllers and are subject to change.

1756-SG001A-US-P July 2000

58

The following equations provide an estimate of the memory needed for a controller. Each of these numbers includes a rough estimate of the associated user programming. Depending on the complexity of your application, you might need additional memory. Controller tasks Discrete I/O points Analog I/O points Motion axis _____ * 4000 = _____ bytes (minimum 1 needed) _____ * 400 = _____ bytes _____ * 2600 = _____ bytes _____ * 8000 = _____ bytes Total = _____ bytes

Communication modules _____ * 2000 = _____ bytes

Logix5550 Memory Boards

If you have a 1756-L1 controller, you can install one of these memory boards in the Logix5550 controller: 1756-M1 (512 Kbytes expansion memory) 1756-M2 (1 Mbytes expansion memory) 1756-M3 (2 Mbytes expansion memory) The 1756-L55 controller does not operate stand-alone. Choose one of these memory boards to come already assembled with the Logix5555 controller: 1756-M13 (1.5 Mbytes memory) 1756-M14 (3.5 Mbytes memory) 1756-M16 (7.5 Mbytes memory)

1756-SG001A-US-P July 2000

59

1756-BA1 Battery

The ControlLogix controller comes with one 1756-BA1 battery:

Description: battery Value: 1756-BA1 0.59g lithium

Important: Only order a battery if you need a replacement.

top middle bottom

no connection black lead (-) red lead (+)

30167

ControlLogix Controller Connections

The ControlLogix controller supports 250 connections. The following table shows how many connections the controller uses for these different communication configurations
ControlLogix Connection Type to: Connections Used by the Controller per Module: 1 1 3 0 1 0 or 1 1 0 2 1 1 1 1 1 1

local I/O module remote I/O module (direct connection only) 1756-MO2AE servo module local 1756-CNB module remote ControlNet communication module remote 1756-CNB module through local 1756-CNB configured as a direct (none) connection configured as a rack-optimized connection 1756-DHRIO module 1756-ENET module 1756-DNB module Universal Remote I/O adapter module produced tag produced tag number of consumers consumed tag block-transfer message other message

1756-SG001A-US-P July 2000

60

Determining Connections for Produced and Consumed Tags

The ControlLogix controller supports the ability to produce (broadcast) and consume (receive) system-shared tags. System-shared data is accessible by multiple controllers over the ControlLogix backplane or over a ControlNet network. Produced and consumed tags each require connections.

ControlLogix chassis with two ControlLogix controllers

ControlNet network

ControlLogix chassis with one ControlLogix controller

1771 chassis with one PLC-5C controller

41029

Maximum number of produced and consumed tags

The following table shows the total number of produced and consumed tags a controller supports:
As a: producer consumer The controller supports:

(number of produced tags) 127 (number of consumed tags) 250

If your controller consumes 250 tags, these tags must come from more than one controller. A controller can only produce as many as 127 tags.

Each produced tag uses one connection for the tag and the first consumer. The produced tag uses and additional connection for each additional consumer. The total combined consumed and produced tags that a controller supports is (this is also the maximum number of connections): (number of produced tags) + (number of consumed tags) 250 As the number of consumed tags increases, the number of available produced tags decreases. You increase the number of consumed tags either by creating consumed tags or by adding additional consumers to a produced tag. Important: The total number of tags that can be produced or consumed is limited by the number of available connections. If the controller uses all of its connections for I/O and communication devices, no connections are left for produced and consumed tags.

1756-SG001A-US-P July 2000

61

Planning your system to support produced and consumed tags

Before the ControlLogix controller can share produced or consumed tags, the producing controller must be configured as part of the system for the consuming controller.
You can share data between: ControlLogix controller and local ControlLogix controller
ControlBus backplane

Over this network: ControlLogix backplane

ControlLogix chassis with two Logix5550 controllers

41774

ControlLogix controller and remote ControlLogix controller

ControlLogix chassis with one Logix5550 controller ControlLogix chassis with one Logix5550 controller

ControlNet network

ControlNet network

41773

ControlLogix controller and PLC-5 ControlNet processor

1771 chassis with one PLC-5C controller ControlLogix chassis with one Logix5550 controller

ControlNet network

ControlNet network

41772

Important: For two controllers that share produced or consumed tags, both controllers must be attached to the same ControlNet network. You cannot bridge produced and consumed tags between two networks.

Connections for produced tags

By default, a produced tag allows two other controllers to consume the tag, which means that each consumer simultaneously receives the tag data. The local controller (producing) must have one connection for the produced tag and the first consumer and one more connection for each additional consumer. The default produced tag requires two connections. As you increase the number of controllers that can consume a produced tag, you also reduce the number of connections the controller has available for other operations, such as communications and I/O.

Connections for consumed tags

Each consumed tag requires one connection for the controller that is consuming the tag.

1756-SG001A-US-P July 2000

62

Determining Connections for Messaging

The ControlLogix controller uses connections to perform messaging, including block-transfers. When your logic uses a message instruction to read or write information to or from another module, that instruction requires one connection for the duration of the transmission. Depending on how you configure the message instruction, the connection remains open (cached) until the controller stops executing the logic or the connection is closed (uncached) after the message transmission. Message instructions that execute repeatedly should keep the connection open (cache the connection) to optimize execution time. Opening a connection each time to execute an instruction would increase execution time. Message instructions that operate infrequently can close connections upon completion to free up connections for other uses.

Determining Connections for I/O Modules

The information passed between the ControlLogix controller and an I/O module varies depending on the type of I/O module. The following diagram illustrates the general types of data that I/O modules and controllers pass between themselves. The size and content of the data passed between an I/O module and the ControlLogix controller helps determine the type of communications that can be used.
output module

input module module and input status module status and data echo

ControlLogix controller data the module uses for its configuration and notification that the controller is running and receiving input data

41767

data the module uses for its configuration and to control its outputs

For the ControlLogix controller to send or receive information from I/O modules, a communication link, or connection, must be established from the ControlLogix controller to the module. The ControlLogix controller establishes a communication connection to an I/O module either directly or indirectly by communicating to a communication module in the system. A direct connection occurs when the ControlLogix controller establishes a real-time, data-transfer link directly with the module. A direct connection lets you tailor the system to meet specific timing or information needs of certain modules. Direct connections provide the greatest system flexibility, but require extra system bandwidth and capacity.

1756-SG001A-US-P July 2000

63

In addition to direct connections, the 1756-CNB module can consolidate the data for multiple, digital I/O modules, in the same chassis as the communication module, into a single, rack-optimized connection. With a rack-optimized connection, the ControlLogix controller establishes a single connection to a communication module. The communication module then establishes a connection to each of the appropriate modules. The communication module gathers the data from the digital I/O modules and packs it together to send over the network. By doing this, the communication module reduces the: number of message packets that must be sent on the network amount of processing time required by each communication module and ControlLogix controller receiving the information system communications overhead and capacity needs number of connections used by the ControlLogix controller Depending on the type of I/O modules in the ControlLogix system, both direct connections and rack-optimized connections can be used. The following table lists several of the I/O systems and the available connections types.
I/O System: 1756 basic digital I/O in a local chassis 1756 digital I/O in a remote chassis via a ControlNet network Supported Connection Type(s): direct connection direct connection or rack-optimized connection1 direct connection direct connection or rack-optimized connection direct connection rack-optimized connection direct connection via messaging rack-optimized connection

1756 analog I/O either in a local chassis or via a ControlNet network in a remote chassis FLEX digital I/O via a ControlNet network

FLEX analog I/O either in a local chassis or via a ControlNet network in a remote chassis digital I/O via a Universal Remote I/O network analog I/O via a Universal Remote I/O network all DeviceNet I/O

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

1756-SG001A-US-P July 2000

64

Direct connections for 1756 I/O modules

A direct connection is a real-time, data-transfer link between the controller and an I/O module. The controller maintains and monitors the connection between the controller and the I/O module. Any break in the connection, such as a module fault or the removal of a module from the chassis while under power, causes the controller to set fault status bits in the data area associated with the module. If a controller has a module configuration that references a slot in the control system, the controller periodically checks for the presence of a device in that slot. When a devices presence is detected there, the controller automatically sends the module configuration. If the module configuration is appropriate for the I/O module found in the slot, a connection is made and operation begins. If the module configuration is not appropriate, the connection is rejected. Module configuration can be inappropriate for any of a number of reasons. For example, a mismatch in electronic keying that prevents normal operation. In this example, the owner controller has three direct connections with the 1756 I/O modules in the remote chassis.
Using Direct Connections with ControlLogix I/O in a Remote Chassis
Local chassis Remote chassis

Slot 1 RPI = 5mS I N P U T O U T P U T I N P U T O U T P U T I N P U T

Slot 2 RPI = 50mS

Slot 3 RPI = 25mS

ControlNet
41020

Owner controller

ControlNet bridge module

ControlNet bridge module

The local controller in this example uses these connections:

Connection Type: controller to local I/O module controller to remote I/O module controller to remote 1756-CNB module Module Quantity: 2 3 1 Connections per Module: 1 1 1 Total Connections: 2 3 1 total 6

1756-SG001A-US-P July 2000

65

Rack-optimized connections for 1756 I/O modules

When a 1756 digital I/O module is located in a remote chassis (with respect to its owner), you can select rack-optimized communication. A rack-optimized connection consolidates connection usage between the owner and the digital I/O in the remote chassis. Rather than having individual, direct connections for each I/O module, there is one connection for the entire chassis. In this example, the owner controller communicates with all the digital I/O in the remote chassis but uses only one connection. The data from all three modules is sent together simultaneously at a rate specified by the 1756-CNB connection. This option eliminates the need for the three separate connections shown in the previous example.
Using a Rack-Optimized Connection with ControlLogix I/O in a Remote Chassis
Local chassis Remote chassis

I N P U T

O U T P U T

Rack-optimized connection for all I/O

I N P U T

O U T P U T

I N P U T

ControlNet
41021

Owner controller

ControlNet bridge module

ControlNet bridge module

The local controller in this example uses these connections:

Connection Type: controller to local I/O module controller to remote 1756-CNB module Module Quantity: 2 1 Connections per Module: 1 1 Total Connections: 2 1 total 3

The rack-optimized connection conserves ControlNet 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-SG001A-US-P July 2000

66

To configure an I/O module for a rack-optimized connection, you select the Rack Optimization communication format when you configure the I/O module through the programming software. Most of the digital I/O modules support a rack-optimized connection. If this option does not appear when you are selecting communication format for an I/O module, the module does not support a rack-optimized connection.

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 uses a rack-optimized connection to communicate with two digital I/O modules. The owner controller also uses a direct connection to communicate with an analog module in the same chassis.
Using a Rack-Optimized Connection and a Direct Connection with I/O in a Remote ControlLogix Chassis
Local chassis Remote chassis

I N P U T

O U T P U T

Rack-optimized connection

I N P U T

Slot 3 RPI = 25mS ControlNet

O U T P U T

A N A L O G

41030

Owner controller

ControlNet bridge module

ControlNet bridge module

The local controller in this example uses these connections:

Connection Type: controller to local I/O module controller to remote analog I/O module controller to remote 1756-CNB module (includes the remote, digital I/O) Module Quantity: 2 1 1 Connections per Module: 1 1 1 Total Connections: 2 1 1 total 4

1756-SG001A-US-P July 2000

67

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 1756-DHRIO module, using one connection (a rack-optimized connection).
Connections for 1771 I/O with a 1756-DHRIO Module in a Local ControlLogix Chassis

Local chassis

ControlLogix controller

DH+/Remote I/O bridge module

1771 chassis

41768

The local controller in this example uses these connections:

Connection Type: controller to local I/O module controller to 1771 I/O through 1756-DHRIO module Module Quantity: 2 1 Connections per Module: 1 1 Total Connections: 2 1 total 3

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-SG001A-US-P July 2000

68

In this example the controller has a direct connection to each digital I/O module in the local chassis. The controller also communicates with the 1771 chassis, through the remote 1756-DHRIO module, using one connection (a rack-optimized connection).
Connections for 1771 I/O with a 1756-DHRIO Module in a Remote ControlLogix Chassis
Local chassis Remote chassis

ControlLogix controller

ControlNet bridge module ControlNet bridge module DH+/Remote I/O bridge module

1771 chassis

41769

The local controller in this example uses these connections:

Connection Type: controller to local I/O module controller to remote 1756-CNB module controller to remote 1756-DHRIO module Module Quantity: 2 1 1 Connections per Module: 1 1 1 Total Connections: 2 1 1 total 4

The controller makes the connection through the remote 1756-DHRIO module to the adapter module in the 1771 chassis. The controller requires one connection for each logical rack. In addition, the controller uses one connection for each message to a 1771 block-transfer module.

1756-SG001A-US-P July 2000

69

Connections to DeviceNet 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 DeviceNet devices, through the 1756-DNB module, using two connections. The 1756-DNB module supports only a rack-optimized connection to its DeviceNet devices.
Connections to Devices with a 1756-DNB Module in a Local ControlLogix Chassis

Local chassis
I N P U T O U T P U T

ControlLogix controller

DeviceNet I/O bridge module

DeviceNet devices
41770

The local controller in this example uses these connections:

Connection Type: controller to local I/O module controller to local 1756-DNB module (includes DeviceNet devices) Module Quantity: 2 1 Connections per Module: 1 2 Total Connections: 2 2 total 4

The 1756-DNB module does not establish connections to its DeviceNet I/O modules; and therefore, the controller doesnt establish connections with DeviceNet I/O modules. 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 module.

1756-SG001A-US-P July 2000

70

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 DeviceNet devices through a remote 1756-DNB module, using two connections. The 1756-DNB module supports only a rack-optimized connection to its devices.
Connections to Devices I/O with a 1756-DNB Module in a Remote ControlLogix Chassis

Local chassis

Remote chassis

I N P U T

O U T P U T

ControlLogix controller

ControlNet bridge module

ControlNet bridge module

DeviceNet bridge module

DeviceNet devices
41771

The local controller in this example uses these connections:

Connection Type: controller to local I/O module controller to remote 1756-CNB module controller to remote 1756-DNB module (includes DeviceNet devices) Module Quantity: 2 1 1 Connections per Module: 1 1 2 Total Connections: 2 1 2 total 5

1756-SG001A-US-P July 2000

71

Communicating with I/O Products

In addition to 1756 I/O modules, the ControlLogix controller can communicate with and control other types of I/O products. The following table lists the I/O products the ControlLogix controller can control over which networks:
DeviceNet network: no no yes yes no yes yes no yes no no no no yes yes5 no yes10 yes12 yes yes Universal RS-232 (DF1) Remote I/O link: serial link: no yes yes yes no no no yes no yes yes yes yes yes yes6 yes4 no no yes no no limited no no no no no no no no no no no yes yes7 no yes yes no no DH-485 network: no no no no no no no no no no no no no no no no no no no no

I/O Product: ControlLogix I/O (1756 series) SLC I/O (1746 series) FLEX Integra I/O (1793 series) FLEX I/O (1794 series) FLEX Ex I/O (1797 series) 1734 POINT I/O Compact I/O (1769 series) Block I/O (1791 series) ArmorBlock I/O (1792 series) 1771 I/O PanelView terminals (2711 series) RediPANEL modules (2705 series) Dataliners (2706 series) DTAM (2707 series) 1336T FORCE ac drives 1395 digital dc drives FlexPak 3000 dc drives GV3000 ac drives 1394 ac servo drives 1398 ULTRA series ac drives

ControlNet network: yes no limited1,2 yes1 yes no no no no yes3 yes no no no yes4 yes8 yes9 yes11 no no

1. Use a 1794-ACN15, -ACNR15 adapter module. Check with your Rockwell Automation representative for availability of support for the 1794-VHSC module. RSLogix 5000 programming software does not currently support the 1794-IR8, 1794-IT8, 1794-ID2, or 1794-IP4 modules. See the next footnote for how to configure FLEX Integra modules. 2. Configure the ControlLogix controller for the comparable FLEX I/O module (1794) and disable electronic keying. 3. Use a 1771-ACN15, -ACNR15 adapter module. 4. Use a 1336T drive with a direct connection to ControlNet (option board 1336T-3TGEN). 5. You need the DeviceNet module (catalog number 1203-GU6). 6. You need the remote I/O module (catalog number 1203-GD1). 7. Your need the serial adapter (catalog number 1203-GD2 or 1203-SSS AnaCANda). 8. Use a 1395 drive with a direct connection to ControlNet. (option board 1395-KP54EN) 9. You need the ControlNet communication card (model 915FK2101). 10. You need the DeviceNet communication card (model 915FK1100). 11. You need the ControlNet network board (model 2CN3000). 12. You need the DeviceNet network board (model 2DV3000).

1756-SG001A-US-P July 2000

72

Communicating with Other Controllers and Devices

The ControlLogix system takes advantage of several networks to allow communications with many different controllers and devices. The following table lists which products the ControlLogix controller can communicate with over which networks.
DeviceNet network (1756-DNB): no no no no yes5 yes5 yes5 n/a n/a no no no n/a n/a yes n/a yes n/a DH+ network RS-232 (DF1) DH-485 (1756-DHRIO): network: network: yes no yes yes4 n/a n/a n/a yes6 yes8 yes yes yes n/a yes n/a yes n/a n/a yes yes yes yes yes yes yes yes7 yes9 yes no yes n/a n/a n/a n/a n/a n/a no no n/a no no no no n/a n/a n/a no no n/a n/a n/a n/a n/a n/a

The ControlLogix controller can communicate with a: 1756 ControlLogix controller 1794 FlexLogix controller 1785 PLC-5 controller 1747 SLC controller 1761 MicroLogix 1000 controller 1762 MicroLogix 1200 controller 1769 MicroLogix 1500 controller 1772 PLC-2 controller 1775 PLC-3 controller 5250 PLC-5/250 controller 2711 PanelView 9355 RSLinx software 1784-KTC, -KTCx 1784-KT, -KTx 1784-PCD 1784-PCMK 1788-CN2DN 1788-CN2FF

Ethernet ControlNet network network (1756-ENET): (1756-CNB): yes no yes1,2 yes3 n/a n/a n/a n/a n/a no no yes n/a n/a n/a n/a n/a n/a yes yes yes yes n/a n/a n/a n/a n/a n/a limited yes yes n/a n/a n/a yes yes

1. The Ethernet PLC-5 processor must be one of these: series C, revision N.1 or later series D, revision E.1 or later series E, revision D.1 or later 2. The 1785-ENET Ethernet communication interface module must be series A, revision D or later. 3. Use a 1747-L55x controller with OS501 or greater 4. Use a 1747-L54x controller. 5. The MicroLogix controller appears as I/O points to the ControlLogix controller. Requires 1761-NET-DNI DeviceNet interface. 6. The PLC-2 controller requires a 1785-KA module for DH+ communications. 7. The PLC-2 controller requires a 1771-KG module for serial (DF1) communications. 8. The PLC-3 controller requires a 1775-S5 module for DH+ communications 9. The PLC-3 controller requires a 1775-KA module for serial (DF1) communications.

1756-SG001A-US-P July 2000

DC INPUT POWER
ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

AC INPUT

DC INPUT

Logix5550
RUN I/O RS232 BAT OK

Logix5550
RUN I/O RS232 BAT OK

DC OUTPUT
ST 0 1 2 3 4 5 6 7 FLT 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K FLT 8 9 10 11 12 13 14 15

AC OUTPUT

ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

ST 0 1 2 3 4 5 6 7 O FLT 0 1 2 3 4 5 6 7 K

RUN

REM

PROG

RUN

REM

PROG

DIAGNOSTIC

DIAGNOSTIC

73

Selecting a Chassis
The ControlLogix system is a modular system that requires a 1756 I/O chassis. You can place any 1756 module in any slot. The backplane provides a high-speed communication path between modules. Multiple controllers on the backplane can pass messages between each other. With multiple communication interface modules on the backplane, a message can be sent from across a link into a port on one module, routed across the backplane out another modules port, and sent across another link to its ultimate destination.
Catalog number: 1756-A4 1756-A7 1756-A10 1756-A13 1756-A17 Number of slots: 4 7 10 13 17 Weight: 0.75 kg (1.7 lb) 1.10 kg (2.0 lb) 1.45 kg (3.2 lb) 1.90 kg (3.2 lb) 2.20 kg (4.8 lb) Minimum cabinet size: (H x W x D) 507 x 507 x 203 mm (20 x 20 x 8 in) 700 x 507 x 203 mm (24 x 20 x 8 in) 507 x 761 x 203 mm (20 x 30 x 8 in) 700 x 761 x 203 mm (24 x 30 x 8 in) 507 x 822 x 203 mm (30 x 36 x 8 in) Type of mounting: backpanel mounting Environmental conditions: operating temperature: 0 to 60 C (32 to 140 F) storage temperature: -40 to 85 C (-40 to 185 F) relative humidity 5 to 95% (without condensation)

Important: Use the slot filler module 1756-N2 to fill empty slots. Two slot filler modules are included in each 1756-N2 catalog number.

1756-SG001A-US-P July 2000

DC INPUT POWER
ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

AC INPUT

DC INPUT

Logix5550
RUN I/O RS232 BAT OK

Logix5550
RUN I/O RS232 BAT OK

DC OUTPUT
ST 0 1 2 3 4 5 6 7 FLT 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K FLT 8 9 10 11 12 13 14 15

AC OUTPUT

ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

ST 0 1 2 3 4 5 6 7 O FLT 0 1 2 3 4 5 6 7 K

RUN

REM

PROG

RUN

REM

PROG

DIAGNOSTIC

DIAGNOSTIC

74

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

> 15.3 cm (6.0 in)

Enclosure

allow 15.3 to 20 cm (6.0 to 8.0 in) between chassis and heat source allow 5.1 cm (2.0 in) between wireway and top or bottom of chassis
> 10.2 cm (4.0 in) 15.3 to 20 cm (6.0 to 8.0 in)

> 15.3 cm (6.0 in)

7.7 to 10.2 cm (3.0 to 4.0 in)

> 10.2 cm (4.0 in)

20230

Mounting dimensions
right-side view of all chassis
16.9 cm (6.65 in) with extended depth housing (1756-TBE)

14.5 cm (5.8 in) 16.0 cm (6.3 in)

41780

1756-A4 with power supply

1.1 cm Dia. (0.433 in)

7.0 cm (2.76 in)

0.55 cm Dia (0.217 in)

15.8 cm (6.22 in)

16.9 cm (6.65 in) 13.7 cm (5.39 in)

0.55 cm Dia (0.217 in)

4.5 cm (1.77 in) 26.3 cm (10.35 in)

1.2 cm (0.472 in)

41781

1756-SG001A-US-P July 2000

DC INPUT POWER
ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

AC INPUT

DC INPUT

Logix5550
RUN I/O RS232 BAT OK

Logix5550
RUN I/O RS232 BAT OK

DC OUTPUT
ST 0 1 2 3 4 5 6 7 FLT 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K FLT 8 9 10 11 12 13 14 15

AC OUTPUT

ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

ST 0 1 2 3 4 5 6 7 O FLT 0 1 2 3 4 5 6 7 K

RUN

REM

PROG

RUN

REM

PROG

DIAGNOSTIC

DIAGNOSTIC

75

Mounting dimensions (continued)

1756-A7 with power supply

1.1 cm Dia. (0.433 in)

17.5 cm (6.89 in)

.55 cm Dia (0.217 in)

15.8 cm (6.22 in)

16.9 cm (6.65 in) 13.7 cm (5.39 in) 4.5 cm (1.77 in)

0.55 cm Dia (0.217 in)

36.8 cm (14.49 in)

1.2 cm (0.472 in)

41782

1756-A10 with power supply

1.1 cm Dia. (0.433 in) 0.55 cm Dia (0.217 in) 14.0 cm (5.51 in) 5.5 cm (2.17 in)

15.8 cm (6.22 in)

16.9 cm (6.65 in) 13.7 cm (5.39 in)

0.55 cm Dia (0.217 in)

14.0 cm (5.51 in) 48.3 cm (19.02 in)

1.2 cm (0.472 in)

41783

1756-SG001A-US-P July 2000

DC INPUT POWER
ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

AC INPUT

DC INPUT

Logix5550
RUN I/O RS232 BAT OK

Logix5550
RUN I/O RS232 BAT OK

DC OUTPUT
ST 0 1 2 3 4 5 6 7 FLT 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K FLT 8 9 10 11 12 13 14 15

AC OUTPUT

ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

ST 0 1 2 3 4 5 6 7 O FLT 0 1 2 3 4 5 6 7 K

RUN

REM

PROG

RUN

REM

PROG

DIAGNOSTIC

DIAGNOSTIC

76

Mounting dimensions (continued)

1756-A13 with power supply

1.1 cm Dia. (0.433 in)

10.5 cm (4.13 in) .55 cm Dia (0.217 in)

14.0 cm (5.51 in)

5.5 cm (2.17 in)

15.8 cm (6.22 in)

16.9 cm (6.65 in) 13.7 cm (5.39 in)

0.55 cm Dia (0.217 in)

14.0 cm (5.51 in)

58.8 cm (23.15 in)

1.2 cm (0.472 in)

41784

1756-A17 with power supply

1.1 cm Dia. (0.433 in)

0.55 cm Dia (0.217 in)

13.3 cm (5.24 in)

14.0 cm (5.51 in)

13.3 cm (5.24 in)

4.4 cm (1.73 in)

15.8 cm (6.22 in)

16.9 cm (6.65 in) 13.7 cm (5.39 in)

73.8 cm (29.06 in)

1.2 cm (0.472 in)

41785

1756-SG001A-US-P July 2000

77

Selecting a Power Supply

The ControlLogix power supplies are used with the 1756 chassis to provide 1.2V, 3.3V, 5V, and 24V dc power directly to the chassis backplane. The power supply attaches to the left end of the chassis.

Description: normal input voltage input voltage range maximum real input power maximum apparent input power maximum transformer load frequency maximum output power

1756-PA72 120V ac or 220V ac 85-265V ac 95W 240VA 238VA 47-63Hz series A power supply: 70W @ 40 C 55W @ 60 C series B power supply 75W @ 60 C

1756-PA75 120V ac or 220V ac 85-265V ac 95W 240VA 238VA 47-63Hz series B power supply 75W @ 60 C

1756-PB72 24V dc 19.2-32V dc 97W na na dc series A power supply: 70W @ 40 C 55W @ 60 C series B power supply 75W @ 60 C

1756-PB75 24V dc 19.2-32V dc 97W na na dc series B power supply 75W @ 60 C

maximum backplane output current

1.5A @ 1.2V dc 4A @ 3.3V dc 10A @ 5V dc 2.8A @ 24V dc

1.5A @ 1.2V dc 4A @ 3.3V dc 13A @ 5V dc 2.8A @ 24V dc

1.5A @ 1.2V dc 4A @ 3.3V dc 10A @ 5V dc 2.8A @ 24V dc

1.5A @ 1.2V dc 4A @ 3.3V dc 13A @ 5V dc 2.8A @ 24V dc

fuse dimension (H x W x D) weight operating temperature storage temperature relative humidity

none 140 x 112 x 145 mm (5.5 x 4.4 x 5.7 in) 1.0 kg (2.5 lb) 0 to 60 C (32 to 140 F) -40 to 85 C (-40 to 185 F) 5 to 95% (without condensation)

1756-SG001A-US-P July 2000

78

Power requirements and transformer sizing

Each power supply generates a shutdown signal on the backplane whenever the ac line voltage drops below its lower voltage limit. It removes the shutdown signal when the line voltage comes back up to the lower voltage limit. This shutdown is necessary to 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 senses this clipped wave form as low voltage and could prematurely shut down modules in the chassis. The graphs that follow display backplane power load. Use the real power value to determine the amount of heat dissipation you have inside the enclosure. Use the apparent power value to estimate power cost. Use the transformer load value plus all other loads on a transformer to determine the required transformer size.

1756-PA72 1756-PA75 ac

backplane power load (Watts)

75 60 45 30 15 0 0 20 40 60 80 100

75 60 45 30 15 0 0 20 40 60 80 100

75 60 45 30 15 0 0 20 40 60 80 100

real power (Watts)

75 60 45 30 15 0 0 20 40 60 80 100

apparent power (Watts)

transformer load (VA) = real power (Watts) x 2.5

1756-PB72 1756-PB75 dc

backplane power load (Watts)

real power (Watts)

41777

1756-SG001A-US-P July 2000

79

Selecting Software
Your selection of modules and network configuration determines what software packages you need to configure and program your system.
If you have: 1756 ControlLogix controller 1756-M02AE motion module 1756-CNB, -CNBR ControlNet communication module You need: RSLogix 5000 programming software Order this catalog number: 9324 series (RSLogix 5000 programming software)

RSNetWorx for ControlNet 9324-RLD300NXENE (RSLogix 5000 (comes with RSLogix 5000 programming software programming software plus RSNetWorx option) and RSNetWorx for ControlNet bundle) or 9357-CNETL3 (RSNetWorx for ControlNet) RSNetWorx for DeviceNet 9324-RLD300NXENE (RSLogix 5000 programming software plus RSNetWorx option) or 9357-DNETL3 (RSNetWorx for DeviceNet) 9324 series (RSLogix 5000 programming software) or 1756-GTWY (ControlLogix Gateway Configuration software)

1756-DNB DeviceNet communication module

1756-ENET Ethernet communication module (set the IP address) 1756-DHRIO communication module (define the DH+ routing table) 1788-CN2FF Foundation Fieldbus linking device

RSLinx software (RSLinx Lite comes with RSLogix 5000 programming software) or ControlLogix Gateway software (comes with RSLogix 5000 programming software) Foundation Fieldbus Configuration Software and RSLinx or RSLinx OEM software (RSLinx Lite is not sufficient) RSLinx software (RSLinx Lite comes with RSLogix 5000 programming software) RSView32 software PanelBuilder software

1788-FFCT and 9355-WABENE or 9355-WABOEMENE 9324 series (RSLogix 5000 programming software) 9301 series 2711-ND3 for PanelBuilder 900 or 2711E-ND1 for PanelBuilder 1400e

communication card in a workstation workstation dedicated for operator interface PanelView terminal

1756-SG001A-US-P July 2000

80

Programming Software

RSLogix 5000 programming software is IEC 1131-3 compliant software that supports the ControlLogix controller. Operating on Microsofts Windows NT 32-bit operating system, the software maximizes performance, saves development time, and improves productivity. RSLogix 5000 is part of the RSLogix family of software products, offering the same reliable functionality. RSLogix 5000 programming software also includes axis configuration and programming support for motion control. One hardware and software platform is all you need for your combined sequential and motion needs. Select the programming package based on the functionality you need:

This catalog number: 9324-RLD300 9324-RLD300NXENE 9324-RLD700

Includes this functionality standard programming software (relay ladder logic) standard programming software (relay ladder logic) RSNetWorx for ControlNet and DeviceNet software standard programming software (relay ladder logic) support for function block programming RSNetWorx for ControlNet and DeviceNet software

Description: personal computer software requirements RAM hard disk space video requirements

Value: IBM-compatible Pentium 90 MHz or greater Microsoft Windows NT version 4.0 with Service Pack 4 RSLinx software must be installed 32 Mbytes of RAM minimum 64 Mbytes of RAM recommended 40 Mbytes of free hard disk space (or more based on application requirements) 16-color VGA graphics adapter 640 x 480 or greater resolution (256-color 800 x 600 minimum for optimal resolution)

1756-SG001A-US-P July 2000

81

Network Configuration Software

ControlNET

ControlNET

ControlNET

ControlNET

A#24
OK A

A#24
OK A

A#24
OK A

A#24
OK A

RSNetWorx software for ControlNet (9357-CNETL3) and RSNetWorx software for DeviceNet (9357-DNETL3) are the configuration and scheduling tools for your ControlNet or DeviceNet networks. RSNetWorx software lets you create a graphical representation of your network configuration and configure the parameters that define your network. RSNetWorx software also performs a scheduling function for all network components. For example, each network scanner has its own scan list and memory mapping. This information is stored in the configurations files in the scanner. When changes are made to the scan lists, RSNetWorx software automatically calculates network bandwidth for the entire network, as well as the bandwidth used by each network component. Important: You must have RSNetWorx software to configure and schedule the ControlNet networks in your ControlLogix system.

PLC-5/40C

ControlNET

A#24
OK A

Description: personal computer operating system RAM hard disk space video requirements

Value: IBM-compatible 120MHz minimum (Pentium recommended) Microsoft Windows 95, Windows 98, or Windows NT version 4.0 (with Service Pack 2 or later) 32 Mbytes of RAM minimum 48 Mbytes or more of RAM recommended 14 Mbytes of free hard disk space (or more based on application requirements) 16-color VGA graphics adapter 640 x 480 or greater resolution (256-color 800 x 600 minimum for optimal resolution)

1756-SG001A-US-P July 2000

82

Gateway Configuration Software

Use a ControlLogix Gateway to bridge and route control and information data through: ControlNet networks Ethernet networks DH+ networks With the ControlLogix Gateway configuration software (1756-GTWY), you can: configure IP and network addresses for a 1756-ENET module. configure a routing table in the 1756-DHRIO module to allow communications with devices on ControlNet, Ethernet, and DH+ networks. configure the default processor slot for a 1756-DHRIO to forward DH+ messages sent to the module. monitor module diagnostics for 1756-CNB, -CNBR, 1756-ENET, and 1756-DHRIO modules. monitor ControlLogix backplane status and diagnostics.

Description: personal computer operating system RAM hard disk space video requirements

Value: IBM-compatible 66MHz minimum (Pentium recommended) Microsoft Windows NT version 4.0 or later 16 Mbytes of RAM minimum 10 Mbytes of free hard disk space 16-color VGA graphics adapter 640 x 480 or greater resolution

1756-SG001A-US-P July 2000

83

Converting PLC-5 or SLC 500 Logic to Logix5550 Logic

The RSLogix5000 programming software includes a translation tool that converts a PLC-5 or SLC 500 import/export file (.PC5 or .SLC extension) into a complete Logix5550 import/export file (.L5K extension). Currently, the translation tool converts only ladder instructions. SFC and structured text files are not converted.

Comparing PLC-5 and SLC 500 architecture to Logix5550 architecture

Because of the architectural differences between a PLC-5 or SLC 500 processor and a Logix5550 controller, you must rework a converted Logix5550 project to make sure it operates properly. Some of the most significant differences in architecture are:
Architectural issue: CPU Comparison: The PLC-5 and SLC 500 processor is based on 16-bit operations. The Logix5550 controllers uses 32-bit operations. The translation tool converts the legacy logic into its 32-bit equivalent. The PLC-5 and SLC 500 processors support individual program files that can be configured as selectable timed interrupts (STIs) or input interrupts (DIIs/PIIs). In addition, the PLC-5 processor supports multiple main control programs (MCPs). The Logix5550 controller combines these into its task, program, and routine organization. The translation tool converts the legacy program types into appropriate Logix5550 tasks. The PLC-5 and SLC 500 processors use an S data file to store processor status. The Logix5550 controller stores data differently. Instead of accessing different locations within a file, use Get System Value (GSV) and Set System Value (SSV) instructions to specify the status information you want. This is a significant difference that requires rework once the converted logic is imported into the Logix5550 controller. The PLC-5 and SLC 500 processors also use bits in S:0 for the arithmetic status flags. For example, S:0/03 stores sign status. The Logx5550 controller uses keywords to reference these flags. For example, instead of referencing a bit address to monitor a sign operation, you use the keyword S:N. input and outputs The PLC-5 and SLC 500 processor map I/O memory into I and O data table files. The I/O data is updated synchronously to the program scan so you know you have current values each time the processor begins a scan. The Logix5550 controller references I/O which is updated asynchronously to the logic scan. For the Logix5550 controller, you might consider creating an I/O data buffer to use for static values during logic execution and update the buffer as needed. After the conversion is complete, you must add instructions to copy the I/O data into the I and O arrays. Do this at the beginning or ending of a program to buffer the data so that it is presented synchronously to the program scan. data The PLC-5 and SLC 500 processors store all data in global data tables. You access this data by specifying the address of the data you want. The Logix5550 controller supports data that is local to a program and data that is global to all the tasks within the controller. The Logix5550 controller can also share data with other controllers, and instead of addresses, you use tags to access the data you want. Each PLC-5 and SLC 500 data table file can store several words of related data. The Logix5550 controller uses arrays to store related data. The translation tool converts the PLC-5 and SLC 500 data table files into Logix5550 arrays.

operating system

1756-SG001A-US-P July 2000

84

Architectural issue: timers

Comparison: The PLC-5 and SLC 500 timers are based on 16-bit architecture and can have different time bases. The Logix5550 controller is based on 32-bit architecture and only supports a 1 msec time base. The translation tools converts the legacy timers as they best fit into the Logix5550 architecture. Converted timers require rework to operate properly. The PLC-5 processor supports block-transfer read and write (BTR and BTW) instructions, ControlNet I/O (CIO), and message (MSG) instructions. The SLC 500 processor supports MSG instructions. The Logix5550 controller supports MSG instructions. The translation tool converts the legacy BTR, BTW, and MSG instructions into Logix5550 MSG instructions. Any CIO instructions are not converted. Once you import the converted logic, you must configure the MSG instructions so that they work properly and rework any CIO instructions.

communications

Reworking converted logic

You must rework a converted Logix5550 project file to make sure it operates properly.
Task: Rework PCE instructions Rework UNK instructions Description: The translation tool process inserts a PCE (Possible Conversion Error) instruction to identify possible errors. Delete each PCE instruction and replace it with the appropriate logic. The translation tool converts some PLC-5 and SLC 500 instructions that have no equivalent in the RSLogix5000 architecture. Once you import these instructions into a Logix5550 project, they appear as UNK instructions. Delete each UNK instructions and replace it with the appropriate logic. Use the Controller Properties dialog to assign the chassis size and slot number of the controller. Then use the Controller Organizer to specify I/O modules and other devices. The file structure in the Logix5550 controller is tag-based. The translation tool creates tags and arrays of tags to align and map the PLC-5 files. The tags created for physical I/O are empty at the end of the conversion process. Use the programming software to add the I/O modules to the tree structure for the Logix5550 controller. Then, program instructions to map the Logix5550 I/O tags to the converted tags. Complete MSG configuration The translation tool only partially converts MSG instructions. You must use the programming software to configure each MSG instruction by completing the information on the Communications tab.

Configure the controller and the chassis Map I/O

1756-SG001A-US-P July 2000

85

Implementing a DCS Control System Using the ControlLogix Architecture

The ProcessLogix Process Control System is a fully-integrated, server-based, process control solution designed to provide process engineers with the features and functions they require from a state-of-the-art distributed control system (DCS). And since the ProcessLogix system is based on economical ControlLogix and ControlNet components, it is also a cost-effective solution.

Meeting Your Process Control Requirements

Because the ProcessLogix system comes with an extensive library of functions and has the ability to communicate with ControlLogix controllers, it can help automate a broad range of batch and continuous process applications across several industries, including consumer products, pulp and paper, petroleum, metals, and pharmaceuticals. ControlNet communications provide the primary link between ProcessLogix servers, controllers, and I/O. Ethernet communications support connections between operator workstations and ProcessLogix servers.
Ethernet network operator stations

ProcessLogix servers ControlNet network

ControlNET POWER

DEVICENET

ETHERNET

Logix5550
RUN I/O RS232 BAT OK
ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

ControlNET POWER

ControlNET

DEVICENET

ETHERNET

ControlNET

Logix5550
RUN I/O RS232 BAT OK
ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

A#24
OK B A RXD TXD OK

A#24
OK B A

A#24
OK B A RXD TXD OK

A#24
OK B A

RUN

REM

PROG

RUN

REM

PROG

ProcessLogix controllers

ControlNet network
ControlNET POWER
ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K ST 0 1 2 3 4 5 6 7 O ST 8 9 10 11 12 13 14 15 K

A#24
OK B A

ProcessLogix I/O modules

B A

30584

1756-SG001A-US-P July 2000

86

Developing a ProcessLogix Application

The ProcessLogix development environment offers control functions that you access and link using a function block editor. A library of templates, called function blocks, provide the logic for continuous, logic, sequence, and basic batch functions. The ProcessLogix system supports: regulatory, computational, and compensation requirements with continuous functions boolean, selection, and comparison requirements with logic functions action handling and conditional logic with sequential functions, including sequential function charts basic batch requirements with Batch Level 1 and 2 type control functions The ProcessLogix system software includes configuration and runtime components. Once you develop and test your application, the ProcessLogix system provides operators with smart displays, including operational procedures and built-in documentation. You can also implement a comprehensive set of alarms to help provide timely notification of any deviation in your process. And while it controls your process, the ProcessLogix system is constantly accumulating data in the ProcessLogix system server, which you can analyze using the systems trending and historian capabilities. Or you can export the data to external programs or systems for more detailed analysis.

41389

ControlLogix, Logix5550, FlexLogix, ProcessLogix, PLC-5, PLC-3, PLC-2, SLC, DH+, Allen-Bradley, RSLogix, RSNetWorx, and Rockwell Software are trademarks of Rockwell Automation. ControlNet is a trademark of ControlNet International, Ltd. DeviceNet is a trademark of the Open DeviceNet Vendor Association. Ethernet is a trademark of Digital Equipment Corporation, Intel, and Xerox Corporation.

1756-SG001A-US-P July 2000

10

11

12

13

14

15

16

Chassis:

Catalog Number:

Backplane current 3.3V (amps):

Backplane current 5.1V (amps):

Backplane current 24V (amps):

Module power (watts):

I/O termination: 20-pin

Connections:

36-pin

Direct

Rack

rack power 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

totals:

Publication 1756-SG001A-US-PJuly 2000 Supersedes Publication 1756-2.7June 1999

PN 957259-69