Controllogix® Controller and Memory Board: Installation Instructions

Installation Instructions
ControlLogix® Controller and Memory Board

Product Catalog Number Series
ControlLogix5550 controller 1756-L1, 1756-L1M1, 1756-L1M2, 1756-L1M3 A
ControlLogix5555 controller 1756-L55, 1756-L55M12, 1756-L55M13, A
1756-L55M14, 1756-L55M16, 1756-L55M22,
1756-L55M23, 1756-L55M24
ControlLogix5561 controller 1756-L61 A, B
ControlLogix5550 memory 1756-M1, 1756-M2, 1756-M3 A
board
ControlLogix5555 memory 1756-M12, 1756-M13, 1756-M14, 1756-M16, A
board 1756-M22, 1756-M23, 1756-M24
Industrial CompactFlash 1784-CF64 n/a
card
Are You Replacing a Controller That has Failed?

For abbreviated steps, see page 4.
WARNING An electrical arc can occur if you:

• insert or remove the CompactFlash card
• insert or remove the controller while backplane power is on
• connect or disconnect the battery
• connect or disconnect the serial cable with power applied to this
module or the serial device on the other end of the cable
This could cause an explosion in hazardous location installations. Make sure
that power is removed or the area is nonhazardous before proceeding.
Publication 1756-IN101J-EN-P - November 2004

2 ControlLogix® Controller and Memory Board
Important User Information

Solid state equipment has operational characteristics differing from those of
electromechanical equipment. Safety Guidelines for the Application, Installation and
Maintenance of Solid State Controls (Publication SGI-1.1 available from your local Rockwell
Automation sales office or online at http://www.ab.com/manuals/gi) describes some
important differences between solid state equipment and hard-wired electromechanical
devices. Because of this difference, and also because of the wide variety of uses for solid
state equipment, all persons responsible for applying this equipment must satisfy
themselves that each intended application of this equipment is acceptable.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or
consequential damages resulting from the use or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes.
Because of the many variables and requirements associated with any particular installation,
Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on
the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of
information, circuits, equipment, or software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission
of Rockwell Automation, Inc. is prohibited.
Throughout this manual, when necessary we use notes to make you aware of safety
considerations.
WARNING Identifies information about practices or circumstances that can cause an explosion in a
hazardous environment, which may lead to personal injury or death, property damage, or
economic loss.
Identifies information that is critical for successful application and understanding of the
IMPORTANT
product.
ATTENTION Identifies information about practices or circumstances that can lead to personal injury or
death, property damage, or economic loss. Attentions help you:
• identify a hazard
• avoid a hazard
• recognize the consequence
SHOCK HAZARD Labels may be located on or inside the equipment (e.g., drive or motor) to alert people
that dangerous voltage may be present.
BURN HAZARD Labels may be located on or inside the equipment (e.g., drive or motor) to alert people
that surfaces may be dangerous temperatures.

ControlLogix® Controller and Memory Board 3
Table of Contents
Replace a Suspected Failed Controller . . . . . . . . . . . . . . . . . . . . . 4
Avoid These Common Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Make Sure that You Have All the Components . . . . . . . . . . . . . . . 8
Make Sure You Have the Correct Memory Board . . . . . . . . . . . . 10
Determine Which Firmware Revisions to Use . . . . . . . . . . . . . . . 10
Prepare the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Remove the Controller from the Chassis, If Required . . . . . . . . . . 12
Install a Memory Board on a ControlLogix5550 or ControlLogix5555
Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Install a 1784-CF64 Industrial CompactFlash Card in a
ControlLogix5561, ControlLogix5562, ControlLogix5563 Controller 19
Connect a Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Install the Controller into the Chassis . . . . . . . . . . . . . . . . . . . . . 25
Check the BAT LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Check the OK LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Update the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Connect a Serial Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Interpret Controller LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Clear a Major Fault. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Choose the Operating Mode of the Controller . . . . . . . . . . . . . . . 39
Specifications: ControlLogix Controllers - Sheet 1 of 2 . . . . . . . . . 40
Specifications: ControlLogix Controllers - Sheet 2 of 2 . . . . . . . . . 41
Specifications - 1784-CF64 Industrial CompactFlash Card . . . . . . 44
Certifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Environment and Enclosure Information . . . . . . . . . . . . . . . . . . . 48
European Hazardous Location Approval . . . . . . . . . . . . . . . . . . . 49
North American Hazardous Location Approval . . . . . . . . . . . . . . 50

Replace a Suspected Failed Controller
1. Cycle the power to the 2. Make sure the OK LED is solid red.
chassis. If the OK LED is not solid red, the
controller does not require
replacement.
3. Match the catalog numbers of the

controllers and memory boards.
ControlLogix
CAT. NO./SERIES
1756-M… Catalog number of the memory board,
if one is installed
ControlLogix
CAT. NO./SERIES
1756-L… Catalog number of the controller
4. Install the battery.
series A series B
COMPACT
FLASH
1-DCD
DSR-6 2-RXD
RTS-7 3-TXD
CTS-8 4-DTR
N/C-9 5-GND
RS232
1 To
Insert 1
2 To Eject
1+2
UP 2
BATTERY
DATE
BATTERY
PORT
42523
20880
5. Insert the key and turn it to 6. Insert the controller into the chassis.
the PROG position.
7. Use ControlFlash software to update the firmware of

the controller.
8. Download the RSLogix 5000 project to the controller.

ATTENTION Preventing Electrostatic Discharge

This equipment is sensitive to electrostatic discharge,
which can cause internal damage and affect normal
operation. Follow these guidelines when you handle this
equipment:
• Touch a grounded object to discharge potential static.
• Wear an approved grounding wriststrap.
• Do not touch connectors or pins on component
boards.
• Do not touch circuit components inside the
equipment.
• If available, use a static-safe workstation.
• When not in use, store the equipment in appropriate
static-safe packaging.
ATTENTION Personnel responsible for the application of safety-related

programmable electronic systems (PES) shall be aware of
the safety requirements in the application of the system
and shall be trained in using the system.

Avoid These Common Errors
If you have this Make sure that you:

controller:
all Update the firmware of the controller to the revision that is
compatible with your RSLogix 5000 software. Controllers ship with
firmware that lets you only update them.
ControlLogix5550 Make sure you use the correct memory board (one per controller). See
page 10.
ControlLogix5555 • If you purchased a ControlLogix5555 controller without a
memory board, you must install a memory board.
• Make sure you use the correct memory board (one per
controller). See page 10.
• Before you change a memory board, update the controller to
IMPORTANT
a revision that is compatible with the memory board that
you intend to install.
• Make sure you use the correct firmware revision. See
page 10.
ControlLogix5561 • Do not install a memory board.
ControlLogix5562
• Make sure you use the correct firmware revision. See
ControlLogix5563 page 10.

Make Sure that You Have All the Components

These components ship with the controller:
Component: Description:
Series A controllers: 1756-BA1 battery
Series B controllers: 1756-BA2 battery
key
You may also use these components with the controller:
If you want to: And you have this Then use this component:
controller:
connect a device to the 1756-CP3 serial cable
serial port of the controller
(e.g., connect a computer to
the controller)
increase the memory of the ControlLogix5550 memory board

controller ControlLogix5555
For the correct memory board,

see page 10.
ControlLogix5561 NOT available for this
ControlLogix5562 controller
ControlLogix5563

If you want to: And you have this Then use this component:
controller:
add nonvolatile memory ControlLogix5550 NOT available for this
controller
ControlLogix5555 memory board
For the correct memory board,

see page 10.
ControlLogix5561 1784-CF64 Industrial
ControlLogix5562 CompactFlash card
ControlLogix5563
31376-M
maintain memory longer ControlLogix5550 NOT available for this

than is available with the controller
battery
ControlLogix5555 1756-BATM ControlLogix
ControlLogix5561 Series A battery module
Important: This option
ControlLogix5562 Series A
maintains memory only
ControlLogix5563 Series A
while the controller is in the
chassis
31298
ControlLogix5561 Series B NOT available for this

ControlLogix5562 Series B controller(1)
ControlLogix5563 Series B
(1) Series B controllers use the battery differently than previous controllers. Battery life
depends on chassis temperature, project size, and how often you cycle power. Battery life
no longer depends on whether or not the controller has power.

Make Sure You Have the Correct Memory Board

If you have this And you want: Use one of these memory boards:
controller:
ControlLogix5550 1756-M1, 1756-M2, 1756-M3
ControlLogix5555 NO nonvolatile memory 1756-M12, 1756-M13, 1756-M14,
1756-M16
nonvolatile memory 1756-M22, 1756-M23, 1756-M24
ControlLogix5561 Do not install a memory board.
Determine Which Firmware Revisions to Use

To update the firmware of a controller, first install a firmware upgrade
kit.
• An upgrade kit ships on a supplemental CD along with
RSLogix 5000 software.
• To download an upgrade kit, go to www.ab.com. Choose
Product Support. Choose Firmware Updates.

Use the following table to determine which firmware revisions to use

with your controller and memory board combination:
For this controller And this And: Use this revision OR

and memory board: series: later:
1756-L1 any
1756-L1M1 any
1756-L1M2 any
1756-L1M3 any
1756-L55M12 10.x or later
1756-L61 A 12.x or later
B 13.40 or later
1756-L62 A 12.x or later
B 13.40 or later
1756-L63 A NO CompactFlash card 10.x or later
CompactFlash card 11.x or later
B 13.40 or later
Make sure that the firmware revision is compatible with your revision
of RSLogix 5000 software.

Prepare the Chassis

Before you install a controller, do these preliminary steps:
✓ Install a ControlLogix chassis.
✓ Install a ControlLogix power supply.
Remove the Controller from the Chassis, If Required

You can install or remove a controller while chassis power is on and
the system is operating. If you remove the controller, all the devices
owned by the controller go to their configured fault state.
WARNING When you insert or remove the module while backplane

power is on, an electrical arc can occur. This could cause
an explosion in hazardous location installations. Be sure
that power is removed or the area is nonhazardous
before proceeding.
Repeated electrical arcing causes excessive wear to contacts on both

the module and its mating connector. Worn contacts may create
electrical resistance that can affect module operation.
1. On the top and bottom of the controller, press the locking

tabs.
2. Slide the controller out of the chassis.
20880

Install a Memory Board on a ControlLogix5550 or ControlLogix5555

Controller
ATTENTION Before you install or replace the memory board,
disconnect the battery from the controller. Otherwise,
you may damage the memory board.
If your ControlLogix5550 or ControlLogix5555 controller requires a

different memory board, install or replace the board as follows:
Tools that You Need
✓ #2 phillips screwdriver
✓ grounding wriststrap
Determine If You Must Update the Controller Firmware Before You Replace
the Board.
If you have this And you are replacing the Then:

controller: memory board with a:
ControlLogix5550 No update is required at this time.
ControlLogix5555 same catalog number of No update is required at this time.
memory board
different catalog number of Before you replace the board:
memory board • Update the firmware of the
controller to a revision that is
For example, you are replacing a compatible with the memory
1756-M13 memory board with a board that you will install.
1756-M23 memory board.
• See “Update the Controller” on
page 29.

Remove the Side Plate of the Controller
1. Lay the controller on its side with the label facing up.
2. While wearing a grounding wriststrap, remove the two screws

that attach the side plate to the controller.
3. Rotate the side plate up and unhook it from the controller.
side plate
front of controller
40017

Remove the Existing Memory Board (If Any)
memory board
42527
1. Does the controller already have a memory board?
If: Then:
No Go to “Install the Memory Board” on page 17.
Yes Go to step 2.

2. Pull the plastic back edge of the controller out slightly to clear
the tabs on the memory board.
tab
tab
42526
3. Gently separate and remove the memory board from the

controller.

Install the Memory Board
1. Place the memory board over the connector and slide the
memory board into the controller.
memory board
tab
tab
slot
slot
40018
2. Pull the plastic back edge of the controller out slightly to clear
the tabs of the memory board.
3. Line up the connectors.
4. Place your hands on the boards over the connectors and

gently squeeze them together.
5. Make sure that the tabs on the memory board extend through
the slots on the plastic housing of the controller.

Replace the Side Plate
side plate
40019
1. Line up the hinge tabs on the side plate with the slots in the
plastic housing of the controller.
2. Gently press the side plate against the controller.
3. Replace the screws.
Attach Labels
To identify which memory board is installed, place the memory board

label on the side of the controller.
40019

Install a 1784-CF64 Industrial CompactFlash Card in a

ControlLogix5561, ControlLogix5562, ControlLogix5563 Controller
A 1784-CF64 Industrial CompactFlash card provides nonvolatile
memory for a ControlLogix5561, ControlLogix5562, ControlLogix5563
controller.
Install a CompactFlash Card in a Series A Controller
2. Raise the locking clip all the

way up.
1. Lay the controller on its side with the front

facing to the left.
3. Insert the CompactFlash card into

the socket at the bottom of the
controller.
4. Pull the clip forward and then

downward until it snaps into place over
the card.

Install a CompactFlash Card in a Series B Controller
WARNING When you insert or remove the CompactFlash card an

electrical arc can occur. This could cause an explosion in
hazardous location installations. Be sure that power is
removed or the area is nonhazardous before proceeding.
ATTENTION If you are NOT sure of the contents of the CompactFlash

card, before you install the card turn the keyswitch of the
controller to the PROG position. Depending on the
contents of the card, a power cycle or fault could cause
the card to load a different project into the controller.
1. Turn the keyswitch to

the PROG position.
2. Open the door of the controller.
3. Push the CompactFlash latch

to the left. COMPACT
FLASH
1-DCD
DSR-6 2-RXD
RTS-7 3-TXD
CTS-8 4-DTR
N/C-9 5-GND
RS232
1 To
Insert 1
2 To Eject
1+2
2
UP
BATTERY
DATE
1
BATTERY
PORT
4. Insert the CompactFlash card.

The A-B logo points left.
5. Release the latch and make sure it slides

over the CompactFlash card.

Remove a CompactFlash Card from a Series B Controller
WARNING When you insert or remove the CompactFlash card an

electrical arc can occur. This could cause an explosion in
1. If the OK LED is
flashing green, wait
until it turns solid
2. Open the door of the controller. green.
3. Push and hold the

CompactFlash latch to the left.
4. Push the eject button and
remove the card.
COMPACT
FLASH
1-DCD
DSR-6 2-RXD
RTS-7 3-TXD
CTS-8 4-DTR
N/C-9 5-GND
RS232
1 To
Insert 1
2 To Eject
1+2
2
UP
BATTERY
DATE
1
BATTERY
PORT
5. Release the latch.

Connect a Battery
WARNING When you connect or disconnect the battery an electrical
arc can occur. This could cause an explosion in
For Safety information on the handling of lithium
batteries, including handling and disposal of leaking
batteries, see Guidelines for Handling Lithium Batteries,
publication AG 5-4.
ATTENTION To prevent possible battery leakage, even if the BAT LED

is off, replace a 1756-BA1 or 1756-BA2 battery according
to the following schedule:
If the temperature 1 in. Replace the battery within:

below the chassis is:
0° … 35° C No required replacement
36° … 40° C 3 years
41° … 45° C 2 years
46° … 50° C 16 months
51° … 55° C 11 months
56° … 60° C 8 months
ATTENTION Store batteries in a cool, dry environment. We

recommend 25°C with 40%…60% relative humidity. You
may store batteries for up to 30 days between
-45°…85°C, such as during transportation. To avoid
leakage or other hazards, do not store batteries above
60°C for more than 30 days.

Install a Battery in a Series A Controller
ATTENTION For a series A controller, connect only a 1756-BA1 battery

or a 1756-BATM battery module. Other batteries may
damage the controller.
1. Insert and connect the battery

as shown.
top no connection
middle black lead (-)
bottom red lead (+)
DATE
2. Write on the battery label the date you

install the battery.
3. Attach the label to the inside of the

controller door.

Install a Battery in a Series B Controller
ATTENTION For a series B controller, connect only a 1756-BA2

battery. Other batteries may damage the controller.
1. Insert the battery with the arrow

pointing up as shown.
COMPACT
FLASH
1-DCD
DSR-6 2-RXD
RTS-7 3-TXD
CTS-8 4-DTR
N/C-9 5-GND
RS232
1 To
Insert 1
2 To Eject
1+2
2. Connect the battery.

UP 2
BATTERY
DATE + red
1
2 - black
BATTERY
PORT
DATE
3. Write on the battery label the date you install
the battery.
4. Attach the label to the inside of the controller

door.

Install the Controller into the Chassis

When you install a ControlLogix controller, you can:
• place the controller in any slot
• use multiple controllers in the same chassis
You can install or remove a ControlLogix controller while chassis
power is on and the system is operating.
WARNING When you insert or remove the module while backplane

power is on, an electrical arc can occur. This could cause
an explosion in hazardous location installations. Be sure
that power is removed or the area is nonhazardous
before proceeding.
Repeated electrical arcing causes excessive wear to contacts on both

the module and its mating connector. Worn contacts may create
electrical resistance that can affect module operation.
1. Insert the key into the

controller.
2. Turn the key to the PROG position.
3. Align the circuit board with the top

and bottom guides in the chassis.
4. Slide the module into the chassis. Make sure it is flush with the power supply
or other modules and the top and bottom latches are engaged.

Check the BAT LED

1. Turn on the chassis power.
BAT LED
42525
2. Is the BAT LED off?
If: Then:
Yes Go to “Determine Which Firmware Revisions to Use” on page 10.
No Go to step 3.
3. Check that the battery or battery module is correctly

connected to the controller.
4. If the BAT LED remains on, install another battery.
5. If the BAT LED remains on after you complete step 4, contact

your Rockwell Automation representative or local distributor.

Check the OK LED
OK LED
42525
1. What color is the OK LED?
If: Then: Actions:

solid green The controller is OK and its No further actions are required.
firmware has been updated. However, the revision of firmware
must be compatible with your
revision of RSLogix 5000 software.
flashing red The controller is OK but it requires a Go to “Determine Which Firmware
firmware update. Revisions to Use” on page 10.
solid red The memory board of the controller Go to step 2.
may not be compatible with the
revision of firmware.
2. Is this a ControlLogix5555 controller?
If: Then:
No The controller is not operational. Contact your Rockwell
Automation representative or local distributor.
Yes Go to step 3.

3. Did you replace a memory board with a memory board that

has a different catalog number?!For example, did you replace
a 1756-M13 memory board with a 1756-M23 memory board?
If: Then:
No The controller is not operational. Contact your Rockwell
Yes Go to step 4.
4. Re-install the previous memory board.
5. Update the firmware of the controller to a revision that is

compatible with the memory board that you intend to install.
See “Determine Which Firmware Revisions to Use” on
page 10.
6. Install the new memory board.
7. What color is the OK LED?
If: Then:
solid green No further actions are required. However, the revision of
firmware must be compatible with your revision of RSLogix 5000
software.
solid red The controller is not operational. Contact your Rockwell

Update the Controller
TIP RSLogix 5000 software, revision 10.0 or later, lets

you update the firmware of a controller as part of
the download sequence. To update the controller,
download your project and follow the prompts of
the software.
1. Connect the controller or chassis to the same network as your

workstation.
2. Start ControlFLASH software.
3. Choose Next >.
4. Select the catalog number of the controller and choose Next >.
5. Expand the network until you see the controller.
IMPORTANT If the required network is not shown, first

configure a driver for the network in RSLinx
software.
To expand a network one level, do − Workstation

one of the following:
+ Linx Gateways, Ethernet
• Double-click the network.
• Select the network and
− driver
press the → key. − communication module

• Click the + sign.
− backplane
+ controller

6. Select the controller and choose OK.
42900
7. Select the revision level to which you want to update the

controller and choose Next >.
IMPORTANT If the Revision list is empty, download a new

upgrade kit. Some older upgrade kits do not work
with new controllers.
8. To start the update of the controller, choose Finish and

then Yes.
After the controller is updated, the status box displays Update

complete.
9. Choose OK.
10. To close ControlFLASH software, choose Cancel and then Yes.

Connect a Serial Cable

WARNING If you connect or disconnect the serial cable with power
applied to this module or the serial device on the other
end of the cable, an electrical arc can occur. This could
cause an explosion in hazardous location installations.
Make sure that power is removed or the area is
nonhazardous before proceeding.
Use the serial port for RS-232 communication.
COMPACT
FLASH
1-DCD
DSR-6 2-RXD
RTS-7 3-TXD
CTS-8 4-DTR
N/C-9 5-GND
RS232
1 To
Insert 1
2 To Eject
1+2
UP 2
BATTERY
DATE
BATTERY
PORT

To connect a workstation to the serial port, use one of these cables:

• 1756-CP3 serial cable
• 1747-CP3 cable from the SLC product family (If you use this
cable, the controller door may not close.)
workstation end
controller end
42576
If you make your own serial cable:

• Limit the length to 15.2m (50 ft).
• Wire the connectors as follows:
Workstation Controller
1 CD 1 CD
2 RDX 2 RDX
3 TXD 3 TXD
4 DTR 4 DTR
COMMON COMMON
6 DSR 6 DSR
7 RTS 7 RTS
8 CTS 8 CTS
9 9 42231
• Attach the shield to both connectors

Interpret Controller LEDs
RUN Indicator
Color Description Recommended Action

off The controller is in Program or Test See “Choose the Operating
mode. Mode of the Controller” on
page 39.
solid green The controller is in Run mode.
I/O Indicator

off Either:
• There are no devices in the I/O • Add the required devices to
configuration of the controller. the I/O configuration of the
controller.
• The controller does not contain a • Download the project to the
project (controller memory is empty). controller.
solid green The controller is communicating with None
all the devices in its I/O configuration.
flashing One or more devices in the I/O Go online with RSLogix 5000
green configuration of the controller are not software and check the I/O
responding. configuration of the controller.
flashing red The chassis is bad. Replace the chassis.

FORCE Indicator

off • No tags contain I/O force values. None
• I/O forces are inactive (disabled).
solid amber • I/O forces are active (enabled). USE CAUTION if you install (add)
• I/O force values may or may not a force. If you install (add) a
exist. force, it IMMEDIATELY takes
effect.
flashing One or more input or output addresses USE CAUTION if you enable
amber have been forced to an On or Off state, I/O forces. If you enable
but the forces have not been enabled. I/O forces, ALL existing I/O
forces also take effect.
RS232 Indicator

off There is no activity. None
solid green Data is being received or transmitted None

BAT Indicator

off The battery supports memory. None
solid green If the Then:
controller is:
series A The controller does None
NOT show this
indication.
series B During power-down, None
the controller is
saving the project to
its internal
nonvolatile memory. If
the BAT LED is solid
red before you turn
off the power, the BAT
LED remains solid red
even during the save.
solid red Either the battery is:
• not installed. Install a battery.
• 95% or more discharged Replace the battery.

OK Indicator

off No power is applied. When ready, turn on power
to the controller.
flashing If the controller is: Then:
red
a new controller The controller requires a See “Update the
(just out of the box) firmware update. Controller” on page 29.
NOT a new Major fault occurred. See “Clear a Major Fault”
controller on page 37.
(previously in
operation)
solid red The controller detected a non-recoverable fault, See “Clear a
so it cleared the project from memory. Non-Recoverable Fault” on
page 38.
solid The controller is OK None
green
flashing The controller is storing or loading a project to or If the controller has a
green from nonvolatile memory. CompactFlash card, leave
the card in the controller
until the OK LED turns solid
green.

Clear a Major Fault

1. Go online with RSLogix 5000 software and get the fault code.
2. Determine what to do next:
Fault Type Fault Code Action

1 60 A. Clear the fault.
B. Download the project to the controller.
C. Return the controller to the run/remote run mode.
If the problem persists:
A. Before you cycle power to the controller, record the state
of the OK and RS232 LEDs.
B. Contact Rockwell Automation support. See the back of this
publication.
1 61 A. To get diagnostic information about the fault, see
Knowledgebase document A92558072. To get the
document, see the back of this publication.
B. Clear the fault.
C. Download the project to the controller.
D. Return the controller to the run/remote run mode.
none of the none of the A. Clear the fault.
above above B. Correct the reason for the fault.
To use the keyswitch of the controller to clear a major fault, turn the keyswitch in the
following sequence:
1. PROG
2. RUN
3. PROG

Clear a Non-Recoverable Fault
1. Cycle power to the chassis.
2. Determine what to do next:
If the OK LED is: Then:

solid green A. Download the project to the controller.
B. Return the controller to the run/remote run mode.
flashing red A. Go online with RSLogix 5000 software and clear the major fault.
B. Download the project to the controller.
solid red Contact your Rockwell Automation representative or local distributor.
If the problem persists:
1. Before you cycle power to the controller, record the state of

the OK and RS232 LEDs.
2. Contact Rockwell Automation support. See the back of this

publication.

Choose the Operating Mode of the Controller
Important • All modes send and receive data in response to a message from another controller.
• All modes produce and consume tags.
A
Do you need to schedule a Do you want to prevent No Turn the keyswitch to PROG
Yes
ControlNet network? RSLogix 5000 software from and then to REM
changing the mode? (Remote Program mode).
No
Yes A
Turn the keyswitch to PROG
B
Do you want to execute the No (Program mode).
logic in the controller?
Turn the keyswitch to RUN
Do you want to prevent No
and then to REM
Yes RSLogix 5000 software from: (Remote Run mode).
• changing the mode
Do you want the logic to Yes • downloading a project
control the output devices? • performing online edits Yes Turn the keyswitch to RUN
(Run mode).
No A
1. Turn the keyswitch to REM.
2. Go online with
A Outputs revert to their configured state for Program mode. RSLogix 5000 software and
choose Test mode.
B This includes Message (MSG) instructions.

Specifications: ControlLogix Controllers - Sheet 1 of 2
Catalog Memory Nonvolatile Backplane Current Power Thermal Weight
Number Memory Dissipation Dissipation
Data and I/O(2) @ 5.1V @ 24V dc
Logic(1) dc
1756-L1 64K bytes No 0.65A 0.02A 3.3W 11.3 BTU/hr 0.28 kg (10.0 oz)
1756-L1M1 500K bytes 150K bytes No 0.95A 0.02A 4.6W 15.6 BTU/hr 0.35 kg (12.5 oz)
1756-L1M2 1M bytes 150K bytes No 1.05A 0.02A 4.8W 16.4 BTU/hr 0.35 kg (12.5 oz)
1756-L1M3 2M bytes 150K bytes No 1.20A 0.02A 5.4W 18.4 BTU/hr 0.36 kg (12.7 oz)
1756-L55M12 750K bytes 208K bytes No 1.23A 0.014A 5.6W 19.1 BTU/hr 0.35 kg (12.5 oz)
1756-L55M13 1.5M bytes 208K bytes No 1.23A 0.014A 5.6W 19.1 BTU/hr 0.35 kg (12.5 oz)

(≤ 3.5M of data)
(1) Data and logic memory stores: tags other than I/O, produced, or consumed tags; logic routines; and communication with OPC/DDE tags
that use RSLinx software (also uses I/O memory)
(2) I/O memory stores: I/O tags, produced tags, consumed tags, communication via Message (MSG) instructions, communication with
workstations, and communication with OPC/DDE tags that use RSLinx software (also uses data and logic memory).
Specifications: ControlLogix Controllers - Sheet 2 of 2
Catalog Memory Nonvolatile Backplane Current Power Thermal Weight
Number Memory Dissipation Dissipation
Data and I/O(2) @ 5.1V @ 24V dc
Logic(1) dc
1756-L55M22 750K bytes 208K bytes Yes 1.23A 0.014A 5.6W 19.1 BTU/hr 0.35 kg (12.5 oz)
1756-L55M23 1.5M bytes 208K bytes Yes 1.23A 0.014A 5.6W 19.1 BTU/hr 0.35 kg (12.5 oz)
1756-L55M24 3.5M bytes 208K bytes Yes 1.25A 0.014A 5.7W 19.4 BTU/hr 0.36 kg (12.8 oz)
1756-L61/A 2M bytes 478K bytes Yes(3) 1.20A 14mA 3.5W 11.9 BTU/hr 0.32 kg (11.3 oz)
1756-L62/A 4M bytes 478K bytes
1756-L63/A 8M bytes 478K bytes
1756-L61/B 2M bytes 478K bytes Yes(3) 1.20A 14mA 3.5W 11.9 BTU/hr 0.35 kg (12.4 oz)
1756-L62/B 4M bytes 478K bytes
1756-L63/B 8M bytes 478K bytes
(1)
Data and logic memory stores: tags other than I/O, produced, or consumed tags; logic routines; and communication with OPC/DDE tags
that use RSLinx software (also uses I/O memory)
(2) I/O memory stores: I/O tags, produced tags, consumed tags, communication via Message (MSG) instructions, communication with
workstations, and communication with OPC/DDE tags that use RSLinx software (also uses data and logic memory).
(3) Requires a 1784-CF64 Industrial CompactFlash card.

The following specifications apply to all ControlLogix controllers:
Description: Value:
Operating Temperature IEC 60068-2-1 (Test Ad, Operating Cold),

IEC 60068-2-2 (Test Bd, Operating Dry Heat),
IEC 60068-2-14 (Test Nb, Operating Thermal Shock):
• 0° … 60° C (32 … 140° F)
Storage Temperature IEC 60068-2-1 (Test Ab, Un-packaged Non-operating Cold),

IEC 60068-2-2 (Test Bb, Un-packaged Non-operating Dry Heat),
IEC 60068-2-14 (Test Na, Un-packaged Non-operating Thermal Shock):
• -40° … 85° C (-40 … 185° F)
Relative Humidity IEC 60068-2-30 (Test Db, Un-packaged Non-operating

Damp Heat):
• 5% … 95% noncondensing
Vibration IEC60068-2-6 (Test Fc, Operating):

• 2g @ 10-500Hz
Operating Shock IEC60068-2-27 (Test Ea, Unpackaged Shock):

• 30g
Non-Operating Shock IEC60068-2-27 (Test Ea, Unpackaged Shock):

• 50g
Emissions CISPR 11:

• Group 1, Class A
ESD Immunity IEC 61000-4-2:

• 6kV contact discharges
• 8kV air discharges
Radiated RF Immunity IEC 61000-4-3:

• 10V/m with 1kHz sine-wave 80%AM from 30MHz … 2000MHz
• 10V/m with 200Hz 50% Pulse 100%AM at 900Mhz
EFT/B immunity IEC 61000-4-4:

• ±4kV at 5kHz on power ports
• ±4kV at 5kHz on communications ports
Surge Transient Immunity IEC 61000-4-5:

• ±1kV line-line(DM) and ±2kV line-earth(CM) on AC power ports
• ±2kV line-earth(CM) on communications ports
Conducted RF Immunity IEC 61000-4-6:

• 10Vrms with 1kHz sine-wave 80%AM from 150kHz … 80MHz

Description: Value:
Enclosure Type Rating none (open-style)
Isolation Voltage 30V

Series A controllers: Tested to withstand 500V ac for 60 seconds
Series B controllers: Tested to withstand 720V dc for 60 seconds
Wiring Category(1) category 3 on communications ports
Programming Cable 1756-CP3 or 1747-CP3 serial cable
Replacement Battery For this component: Use this battery:
1756-L1, 1756-L1M1, 1756-L1M2, 1756-BA1 (0.59g lithium)

1756-L1M3
1756-L55, 1756-L55M12, 1756-BA1 (0.59g lithium)

1756-L55M13, 1756-L55M14,
1756-L55M16, 1756-L55M22,
1756-L55M23, 1756-L55M24
1756-L61/A, 1756-L62/A, 1756-L63/A 1756-BA1 (0.59g lithium)
1756-L61/B, 1756-L62/B, 1756-L63/B 1756-BA2 (0.50g lithium)
1756-BATM battery module 1756-BATA (10g lithium)
(1)
Use this Conductor Category information for planning conductor routing. Refer to Publication 1770-4.1,
Industrial Automation Wiring and Grounding Guidelines.

Specifications - 1784-CF64 Industrial CompactFlash Card
Description Value
User Available Memory 64M bytes
Nonvolatile Memory Yes
Weight 14.2 g (0.5 oz).
Operating Temperature IEC 60068-2-1 (Test Ad, Operating Cold),

IEC 60068-2-2 (Test Bd, Operating Dry Heat),
IEC 60068-2-14 (Test Nb, Operating Thermal Shock):
• 0 … 60°C (32 … 140°F)
Storage Temperature IEC 60068-2-1 (Test Ab, Un-packaged Non-operating Cold),

IEC 60068-2-2 (Test Bb, Un-packaged Non-operating Dry Heat),
IEC 60068-2-14 (Test Na, Un-packaged Non-operating Thermal Shock):
• -40 … 85°C (-40 … 185°F)
Relative Humidity IEC 60068-2-30 (Test Db, Un-packaged Non-operating

Damp Heat):
• 5% … 95% noncondensing
Vibration IEC60068-2-6 (Test Fc, Operating):

• 2g @ 10-500Hz
Operating Shock IEC60068-2-27 (Test Ea, Unpackaged Shock):

• 30g
Non-Operating Shock IEC60068-2-27 (Test Ea, Unpackaged Shock):

• 50g
Emissions CISPR 11:

• Group 1, Class A
ESD Immunity IEC 61000-4-2:

• 4kV contact discharges
• 8kV air discharges
Radiated RF Immunity IEC 61000-4-3:

• 10V/m with 1kHz sine-wave 80%AM from 30MHz…2000MHz

Description Value
EFT/B immunity IEC 61000-4-4:

• ±4kV at 5kHz on power ports
Conducted RF Immunity IEC 61000-4-6:

• 10Vrms with 1kHz sine-wave 80%AM from 150kHz … 80MHz
Enclosure Type Rating none (open-style)
Certifications
When marked, the components have the following certifications. See
the Product Certification link at www.ab.com for Declarations of
Conformity, Certificates, and other certification details.
Catalog Number Certification Description
1756-L1 UL UL Listed Industrial Control Equipment
CSA CSA Certified Process Control Equipment
CSA Certified Process Control Equipment for Class I, Division 2

CSA
Group A,B,C,D Hazardous Locations
European Union 89/336/EEC EMC Directive, compliant with:

• EN 50082-2; Industrial Immunity
CE • EN 61326; Meas./Control/Lab., Industrial Requirements
• EN 61000-6-2; Industrial Immunity
• EN 61000-6-4; Industrial Emissions
Australian Radiocommunications Act, compliant with:

C-Tick
AS/NZS CISPR 11; Industrial Emissions
European Union 94/9/EC ATEX Directive, compliant with:

EEx EN 50021; Potentially Explosive Atmospheres, Protection "n"
(Zone 2)


CSA


C-Tick

(Zone 2)
TÜV Certified for Functional Safety

TÜV 1oo2D (AK 1-6, SIL 1-3, according to DIN V 19250 and IEC 61508
respectively)

1756-L62
1756-L63
CSA
FM Approved Equipment for use in Class I Division 2 Group

FM
A,B,C,D Hazardous Locations


C-Tick

(Zone 2)

1756-M1, UR UL Recognized Component Industrial Control Equipment

1756-M2
CSA CSA Accepted Component for Process Control Equipment
1756-M3
1756-M12 CSA Accepted Component for Process Control Equipment in
CSA
1756-M13 Class I, Division 2 Group A,B,C,D Hazardous Locations
1756-M14
1756-M16
1756-M22
1756-M23
1756-M24

C-Tick
European Union 94/9/EEC ATEX Directive, compliant with:

EEx
EN 50021; Potentially Explosive Atmospheres, Protection “n”
1784-CF64 CE European Union 89/336/EEC EMC Directive, compliant with:

• EN 61326; Meas./Control/Lab., Industrial Requirements
• zEN61000-6-4; Industrial Emissions

C-Tick

Environment and Enclosure Information

ATTENTION Environment and Enclosure
This equipment is intended for use in a Pollution Degree 2 industrial
environment, in overvoltage Category II applications (as defined in IEC
publication 60664-1), at altitudes up to 2000 meters without derating.
This equipment is considered Group 1, Class A industrial equipment
according to IEC/CISPR Publication 11. Without appropriate precautions,
there may be potential difficulties ensuring electromagnetic
compatibility in other environments due to conducted as well as radiated
disturbance.
This equipment is supplied as “open type” equipment. It must be
mounted within an enclosure that is suitably designed for those specific
environmental conditions that will be present and appropriately
designed to prevent personal injury resulting from accessibility to live
parts. The interior of the enclosure must be accessible only by the use of
a tool. Subsequent sections of this publication may contain additional
information regarding specific enclosure type ratings that are required to
comply with certain product safety certifications.
NOTE: See NEMA Standards publication 250 and IEC publication 60529,
as applicable, for explanations of the degrees of protection provided by
different types of enclosure. Also, see the appropriate sections in this
publication, as well as the Allen-Bradley publication 1770-4.1
(“Industrial Automation Wiring and Grounding Guidelines”), for
additional installation requirements pertaining to this equipment.

European Hazardous Location Approval
European Zone 2 Certification (The following applies when the product bears the
EEx Marking)
This equipment is intended for use in potentially explosive atmospheres as defined by
European Union Directive 94/9/EC.
The LCIE (Laboratoire Central des Industries Electriques) certifies that this equipment has
been found to comply with the Essential Health and Safety Requirements relating to the
design and construction of Category 3 equipment intended for use in potentially explosive
atmospheres, given in Annex II to this Directive. The examination and test results are
recorded in confidential report No. 28 682 010.
Compliance with the Essential Health and Safety Requirements has been assured by
compliance with EN 50021.
IMPORTANT • This equipment is not resistant to sunlight or other sources

of UV radiation.
• The secondary of a current transformer shall not be
open-circuited when applied in Class I, Zone 2 environments.
• Equipment of lesser Enclosure Type Rating must be installed
in an enclosure providing at least IP54 protection when
applied in Class I, Zone 2 environments.
• This equipment shall be used within its specified ratings
defined by Allen-Bradley.
• Provision shall be made to prevent the rated voltage from
being exceeded by transient disturbances of more than 40%
when applied in Class I, Zone 2 environments.

North American Hazardous Location Approval

The following information applies when Informations sur l'utilisation de cet équipement
operating this equipment in hazardous en environnements dangereux:
locations:
Products marked "CL I, DIV 2, GP A, B, C, D" are Les produits marqués "CL I, DIV 2, GP A, B, C, D" ne
suitable for use in Class I Division 2 Groups A, B, conviennent qu'à une utilisation en environnements
C, D, Hazardous Locations and nonhazardous de Classe I Division 2 Groupes A, B, C, D dangereux et
locations only. Each product is supplied with non dangereux. Chaque produit est livré avec des
markings on the rating nameplate indicating the marquages sur sa plaque d'identification qui
hazardous location temperature code. When indiquent le code de température pour les
combining products within a system, the most environnements dangereux. Lorsque plusieurs
adverse temperature code (lowest "T" number) produits sont combinés dans un système, le code de
may be used to help determine the overall température le plus défavorable (code de température
temperature code of the system. Combinations le plus faible) peut être utilisé pour déterminer le
of equipment in your system are subject to code de température global du système. Les
investigation by the local Authority Having combinaisons d'équipements dans le système sont
Jurisdiction at the time of installation. sujettes à inspection par les autorités locales
qualifiées au moment de l'installation.
WARNING EXPLOSION HAZARD AVERTISSEMENT RISQUE D'EXPLOSION

• Do not disconnect • Couper le courant ou
equipment unless power s'assurer que
has been removed or the l'environnement est classé
area is known to be non dangereux avant de
nonhazardous. débrancher l'équipement.
• Do not disconnect • Couper le courant ou
connections to this s'assurer que
equipment unless power l'environnement est classé
has been removed or the non dangereux avant de
area is known to be débrancher les
nonhazardous. Secure any connecteurs. Fixer tous les
external connections that connecteurs externes
mate to this equipment by reliés à cet équipement à
using screws, sliding l'aide de vis, loquets
latches, threaded coulissants, connecteurs
connectors, or other filetés ou autres moyens
means provided with this fournis avec ce produit.
product. • La substitution de
• Substitution of composants peut rendre
components may impair cet équipement inadapté à
suitability for Class I, une utilisation en
Division 2. environnement de Classe I,
• If this product contains Division 2.
batteries, they must only • S'assurer que
be changed in an area l'environnement est classé
known to be non dangereux avant de
nonhazardous. changer les piles.

This product may contain licensed technology which is the subject of one or more of the following
Microsoft Corporation patents:
• US Patent No. 5,579,517
• DE Patent No. 618540
• FR Patent No. 615840
• GB Patent No. 615840

Rockwell Automation Support
Rockwell Automation provides technical information on the web to assist you
in using its products. At http://support.rockwellautomation.com, you can find
technical manuals, a knowledge base of FAQs, technical and application
notes, sample code and links to software service packs, and a MySupport
feature that you can customize to make the best use of these tools.
For an additional level of technical phone support for installation,

configuration and troubleshooting, we offer TechConnect Support programs.
For more information, contact your local distributor or Rockwell Automation
representative, or visit http://support.rockwellautomation.com.
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours
of installation, please review the information that's contained in this manual.
You can also contact a special Customer Support number for initial help in
getting your module up and running:
United States 1.440.646.3223 Monday – Friday, 8am – 5pm EST
Outside United States Please contact your local Rockwell Automation representative for any
technical support issues.
New Product Satisfaction Return

Rockwell tests all of its products to ensure that they are fully operational when
shipped from the manufacturing facility. However, if your product is not
functioning and needs to be returned:
United States Contact your distributor. You must provide a Customer Support case number
(see phone number above to obtain one) to your distributor in order to
complete the return process.
Outside United States Please contact your local Rockwell Automation representative for return
procedure.
Back Cover
!
ö
!
Publication 1756-IN101J-EN-P - November 2004 PN 957944-30

Supersedes Publication 1756-IN101I-EN-P - November 2004 Copyright © 2004 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.
Release Notes
ControlLogix® Controller Revision 13
Cat. No. 1756-L1, 1756-L1M1, 1756-L1M2, 1756-L1M3, 1756-L55,

1756-L55M12, 1756-L55M13, 1756-L55M14, 1756-L55M16,
1756-L55M22, 1756-L55M23, 1756-L55M24, 1756-L61, 1756-L62,
1756-L63
IMPORTANT • Do not use this revision of firmware in a redundant controller

system (ControlLogix Redundancy system).
• If you have a 1756-L55 controller, you must install a memory board.
For more information, see the ControlLogix Controller and Memory
Board Installation Instructions, publication 1756-IN101.
When to Use These Release These release notes correspond to the following revisions of the
ControlLogix family of controllers:
Notes
Controller: Catalog number: Revision:
ControlLogix®5550 1756-L1, -L1Mx 13.31
ControlLogix®5555 1756-L55, -L55Mxx 13.31
ControlLogix®5561 1756-L61 13.40
These release notes include the changes and corrected anomalies of

earlier revisions of 13.x firmware.
Compatible Revisions To use this controller revision, update your system as follows:
Update this: To this revision or Update this: To this revision or

later: later:
1756-HYD02 module 13.2 RSLinx® software 2.42
1756-M02AE module 13.2 RSLogix™ 5000 software 13.0
1756-M02AS module 13.6 RSNetWorx™ for ControlNet™ software 4.21
1756-M03SE module 13.7 RSNetWorx™ for DeviceNet™ software 4.21
1756-M08SE module 13.7 RSNetWorx™ for EtherNet/IP software 4.21
1756-M16SE module 13.7
1 Publication 1756-RN603E-EN-E - November 2004

2 ControlLogix® Controller Revision 13
What Is In These Release These release notes provide the following information:
Notes
For information about: See this section: On this page:
preliminary actions to take before you use this revision Before You Update Your System 2
new features for ControlLogix controllers Enhancements 3
changes to existing features in ControlLogix controllers Changes 7
restrictions that no longer apply to ControlLogix controllers Corrected Anomalies 9
restrictions for ControlLogix controllers Restrictions 14
additional memory required to update to this revision Additional Memory Requirements 17
Before You Update Your Before you update your controller to this revision, do the following
preliminary actions:
System
If: Then:
You have a 1756-L55M23 or -L55M24 See if all three of these conditions apply to the controller:
controller. • Is the firmware revision of the controller 9.x or earlier?
• Does the nonvolatile memory of the controller contain a project?
• Is the Load Image property of the nonvolatile memory set to On Power Up or On
Corrupt Memory?
If you answered yes to all of the questions, do the following before you update the firmware
of the controller:
1. In the Load Image drop-down list, select User Initiated.
2. Store the project to the nonvolatile memory of the controller.
Other Load Image selections cause the update of the controller to fail. (You are able to
successfully update the controller the second time.)
Your controller meets both of these Take these precautions:
conditions:
• It has nonvolatile memory. If the controller: Then:
• It is currently at revision 11.x or does not use a Save the project to an offline file. When you update the firmware
earlier. CompactFlash card of the controller, you erase the contents of the nonvolatile
memory (revision 10.x or later).
uses a CompactFlash Either:
card • Remove the CompactFlash card from the controller.
• Check the Load Image option of the CompactFlash card. If
it is set to On Power Up or On Corrupt Memory, first store
the project with the Load Image option set to User
Initiated.
Otherwise, you may get a major fault when you update the
firmware of the controller. This occurs because the On Power Up
or On Corrupt Memory options cause the controller to load the
project from nonvolatile memory. The firmware mismatch after
the load then causes a major fault.
Publication 1756-RN603E-EN-E - November 2004

ControlLogix® Controller Revision 13 3
If: Then:
Your controller is close to its limits of This revision may require more memory than previous revisions.
memory. • To see what components of your current project require more memory, see page 17.
• RSLogix 5000 software revision 13.0 or later lets you estimate the memory
requirements of the controller offline. See page 5.
To upgrade to this revision, you may have to add an expansion memory card to the controller
or use a larger memory card.
Your controller is connected to a DH-485 Disconnect it from the DH-485 network before you update the firmware of the controller. If
network. you update the firmware of a controller while it is connected to a DH-485 network,
communication on the network may stop.
Enhancements ControlLogix controllers have these new features:
ControlLogix5561, ControlLogix5562, ControlLogix5563 Rev 13.40
Enhancement: Description
Series B of these controllers: What’s new about series B controllers?
• ControlLogix5561 With Series B controllers, you:
• ControlLogix5562 • get to the CompactFlash card from the front of the controller
• ControlLogix5563 • have longer battery life
See Maintain the Battery of a ControlLogix Series B Controller, publication
1756-AP014, for details.
Important: Use only a 1756-BA2 battery in a series B controller.
Are there any new precautions?

Take these precautions with CompactFlash cards:
1. Put the keyswitch in the PROG position before you insert a card. Do this for any card
except one that you know is blank.
Suppose you insert a card that already has a project that is configured to load on
power up. If a power cycle happens before you store another project, the card loads
the earlier project and firmware into the controller. It’s also possible that the
controller starts running the project.
2. Make sure that you hold the CompactFlash latch to the left before you remove the
card. If you push the eject button without moving the latch out of the way, it’s
possible to damage the CompactFlash socket.
Which firmware do I use for my series B controllers?

You must use revision 13.40 or later firmware for series B controllers.
Do I use the same firmware for both series A and series B controllers?
Yes. You use the same firmware for series A and series B of ControlLogix5561,
ControlLogix5562, ControlLogix5563 controllers.

Earlier ControlLogix Revision 13 Firmware
Enhancement: Description:
Online Edits of Sequential Function Charts This revision lets you perform online editing of Sequential Function Chart (SFC) and
(SFC) and Structured Text (ST) Structured Text (ST) routines. Like the Function Block Diagrams (FBD), online editing of SFC
and ST routines is done at a routine level.
Finalize All Edits in a Program The Finalize All Edits in Program option lets you make an online change to your logic
without testing the change.
Finalize All Edits in Program
When you choose Finalize All Edits in Program:

• All edits in the program (pending and test), immediately download to the controller
and begin execution.
• The original logic is permanently removed from the controller.
• Outputs that were in the original logic stay in their last state unless executed by the
new logic (or other logic).
• If your edits include an SFC:
• The SFC resets to the initial step.
• Stored actions turn off.
Motion Calculate Slave Value (MCSV) Use the MCSV instruction in the following applications:
Instruction • Position cam: electronic camming between two axes according to a specified cam
profile
• Time cam: electronic camming of an axis as a function of time, according to a
specified cam profile
The MCSV instruction returns the slave value within a specified cam profile for a given
master value. The master value can be master position or time. Use that information to
re-synchronize motion after a fault or to calculate dynamic phase corrections.

Estimate Memory Information Offline To estimate how much controller memory your project requires, use the Memory tab of the
View Memory Information Online controller properties dialog box. For each of the memory areas of your controller, it lets you
estimate number of bytes of:
• free (unused) memory
• used memory
• largest free contiguous block of memory
When online with a controller, the Memory tab shows the actual memory usage of the
controller. The tab includes a Max Used entry for each type of memory. The Max Used
values show the peak of memory usage as communications occur.
Improved Performance of Simple Structured The controller now executes simple structured text (ST) assignments and comparisons
Text Statements faster than previous revisions.
For this: This is simple: This is NOT simple:

assignment A := B; A := -B;
A := B + C;
A := sin(B);
comparison (=, <, <=, >, >=, A>B A > -B
<>) A=B A > (B + C)
A > sin(B)
Embedded EDS Support ControlLogix controllers now include their electronic data sheet (EDS) file as part of their
firmware. This lets RSNetWorx software 5.x or later upload and register the EDS file
directly from the controller. In previous revisions, you had to find the file on a CD or a web
site and manually install the EDS file.

For Some Non-Recoverable Faults, the If the controller detects a non-recoverable fault that was not caused by its hardware, the
Controller Produces a Major Fault and May controller now responds as follows:
Be Able to Log Diagnostic Information.
If the controller: Then:
has a CompactFlash socket The controller clears the project from its memory and
• ControlLogix5561 produces a major fault (flashing red OK LED)
• ControlLogix5562
• ControlLogix5563
has no CompactFlash socket The controller initially shows a solid red OK LED.
• ControlLogix5550 After you cycle power to the controller, it produces a
• ControlLogix5555 major fault (flashing red OK LED).
In either case, the controller still clears the project from memory. The fault code that it
displays depends on whether you have installed a CompactFlash card in the controller.
Type Code Cause Recovery Method

1 60 For a controller with no 1. Clear the fault.
CompactFlash card installed, the 2. Download the project.
controller: 3. Change to remote run/run
• detected a non-recoverable mode.
fault If the problem persists:
• cleared the project from 1. Before you cycle power to the
memory controller, record the state of
the OK and RS232 LEDs.
2. Contact Rockwell Automation
support. See the back of this
publication.
1 61 For a controller with a 1. Clear the fault.
CompactFlash card installed, the 2. Download the project.
controller: 3. Change to remote run/run
• detected a non-recoverable mode.
fault If the problem persists, contact
• wrote diagnostic Rockwell Automation support. See the
information to the back of this publication.
CompactFlash card
• cleared the project from
memory
In previous revisions:
• The controller would not go to faulted mode or display a fault code for the type of
situation described above.
• Controllers with a CompactFlash socket showed a solid red OK LED.

Changes Changes are organized by the firmware revision in which the change
occurred:
ControlLogix5550 Rev 13.27

ControlLogix5561, 5562, 5563 Rev 13.28
Change: Description:
In a Message (MSG) Instruction, You Cannot Do not set or clear the following members of a Message (MSG) instruction:
Set or Clear Certain Status Bits. • EW
• ER
• DN
• ST
• Flags
Important: If your logic currently manipulates any of the above members of a MSG
instruction, your controller may operate differently when you update to this revision.
If you set or clear one of those bits, RSLogix 5000 software displays the change. But the
MSG instruction ignores the change and continues to execute based on the
internally-stored value of those bits.
Motion Planner No Longer Waits for The motion planner now begins execution immediately, regardless of whether or not it is
Consumed Data to Start Flowing receiving data via a consumed axis.
In previous revisions, a consumed axis caused the motion planner to delay its execution
until data started flowing from the producing controller. Under the following combination of
circumstances, the motion task of the controller failed to start at all:
• The system included 2 ControlLogix controllers in the same chassis.
• Each controller produced an axis for the other controller.
Lgx00031365
For Function Block Instructions That Use If your function block instruction uses the periodic timing mode, the controller no longer
Periodic Timing, DeltaT Now Includes the truncates the fractional portion of a task’s period to produce the delta time (DeltaT).
Fractional Portion of the Task’s Period. In previous revisions, the controller truncated the fractional portion of the task’s period.
Lgx00036282
While in Program Mode, a Motion Group As an option, you can configure a motion group to produce a major fault any time the group
Fault No Longer Produces a Major Fault detects a motion fault.
With this revision, a motion group that is configured to produce a major fault produces a
major fault only if the controller is in run/remote run mode.
In previous revisions, the motion group could produce a major fault while the controller was
in program/remote program mode. For example, a store to nonvolatile memory interrupts
the execution of the motion planner, which produces a fault.
Lgx00036957

Change: Description:
Out-of-Range Subscript No Longer Produces During prescan, the controller automatically clears any faults due to an array subscript that
a Fault During Prescan is beyond the range of the array (out of range).
In previous revisions, this produced a major fault.
Lgx00040220
AutoTune Now Uses a Non-Integrating When you autotune an Enhanced PID (PIDE) function block with the Process Type =
Process Model for Temperature Processes Temperature, autotune now uses a non-integrating process model to estimate tuning
constants. This gives better tuning constants for most application.
In previous revisions, autotune used an integrating process model.

Lgx00041638
You Must Place a Label (LBL) Instruction At If your logic includes a Label (LBL) instruction, make sure the instruction is the first
the Start of a Rung. instruction on the rung. If it is not, move the LBL instruction to the beginning of the rung.
Otherwise, the routine will not verify.
In previous revisions, RSLogix 5000 software let you place the LBL instruction elsewhere on
the rung. But the controller always executed the instruction as if it were at the beginning of
the rung.
Lgx00042691
Reduction in the Prescan Time of Projects During a prescan, the controller no longer prescans a routine more than once. Once it
with Many Jump to Subroutine (JSR) prescans a routine, the controller does not prescan the routine again during that prescan.
Instructions In previous revisions, the controller would prescan a routine as often as it was called in
logic. For projects with many calls to subroutines, this could produce a very long prescan
and cause a watchdog timeout fault.
Lgx00043977

Corrected Anomalies The corrected anomalies are organized by the firmware revision that
corrected them.
Corrected anomaly: Description:

MAOC Instruction Left Output Bit On When Under the following conditions, the Motion Arm Output Cam (MAOC) instruction left the
Enable Bit Turned Off output bit on when the bit should’ve turned off.
• Unlatch type = Position and Enable

• The enable bit turned off at the same time the
position passed through the unlatch (right) position.
1
enable bit
0
1
output bit
0
position
unlatch (right)
position
Lgx00048145
Some 1756-L63 Controllers Reported the Some 1756-L63 controllers reported the wrong memory size information. This does not
Wrong Memory Size Information affect most customers. However, if you use the controller in a redundant system, both
controllers must report the same information so that the controllers can synchronize.
The controller firmware now checks to make sure the correct memory information is
reported.
Lgx00049895



A Non-Recoverable Fault Occurred When A non-recoverable fault (memory clear) occurred when you attempted to run an 8th trend.
You Attempted to Run More Than 7 Trends This occurred because the controller could not allocate the required system resources.
Lgx00046058
Certain Conditions Could Generate an Under these conditions, RSLogix 5000 software displayed an unknown major fault after an
Unknown Major Fault When a Motion Axis axis fault occurred:
Fault Occurred
• UID/UIE instruction in an event, periodic, or continuous task
• the motion group is configured to trigger major faults in response to axis faults
• fault handler routine responds to axis faults and clears the axis fault code
• an axis fault occurs while the user task is in the UID section of code
Lgx00046070
Loss of UID/UIE Behavior if a Fault Routine The controller uses an internal count to keep track of nesting UID/UIE instructions. When
Executed a UID is scanned, the count increments by one; when a UIE is scanned, the count
decrements by one. The count is set to zero when a program completes execution.
If a fault routine executed when the UID/UIE count was not zero, at the end of the fault
routine, the controller set the UID/UIE count back to zero. Control was returned to the
program with interrupts enabled when they should still be disabled.
Lgx00046070
Memory Allocations for HMI OPC For HMI OPC applications, memory normally allocated to “Data and Logic” memory was
Applications Were Made in I/O Memory being allocated to “I/O” memory. This could cause the controller to run out of I/O memory
Rather Than Data and Logic Memory where in previous versions it did not. This could also cause messaging and other HMI OPC
applications to not respond or time out. This did not affect I/O based connections.
Lgx00047148
Backplane Errors Caused Loss of Input Data Errors that occur for certain backplane-noise conditions caused the data being received by
the controller to stop flowing into the data table of the controller. The controller did not
detect when this happened and the connection status and I/O LED indicators still indicated
that everything was working.
Lgx00047199
Subroutines Invoked from SFC Actions Were A subroutine invoked from an SFC action was not properly postscanned when the SFC was
Not Properly Postscanned configured for automatic reset. Instructions and assignments may not have set their data to
postscan values. For example, an Output Energize (OTE) instruction may not have cleared its
data during postscan.
Lgx00047407
In SFCs Configured for Auto Reset, Stored When an SFC was configured for Automatic Reset and an Action used a stored qualifier (S,
Actions Were Not Properly Postscanned SD, SL, DS), when a reset action (R) executed, the action being reset was not postscanned.
Lgx00047935



Uni-Directional Homing Failed to Complete A Motion Axis Home (MAH) instruction sometime failed to complete (IP bit remained on)
under the following axis configuration:
• Return Speed = 0
• uni-directional homing (forward or reverse)
Lgx00032632
Unconditional MDR Instruction Did Not A Motion Disarm Registration (MDR) instruction failed to repeatedly execute under the
Re-Execute following circumstances:
• You placed the MDR instruction in a structured text routine.
• You did not provide any conditions to control the execution of the instruction. (I.e.,
you programed it to execute continuously.)
In those circumstances, the EN bit might have been left on after the first execution and the
instruction no longer executed again.
Important: In structured text, we recommend that you condition the instruction so that it
only executes on a transition.
Lgx00037634


Blended Moves Produce Smoother, More This revision improves the response of the axes when you blend the execution of Motion
Accurate Motion Coordinated Linear Move (MCLM) and Motion Coordinated Circular Move (MCCM)
instructions.
• If the Termination Type = command tolerance (2) or no decel (3), axes

change more smoothly and follow the intended path more closely.
• If the Termination Type = command tolerance (2) or no decel (3) and the
program path direction is reversed, the instruction will exceed the
specified acceleration/deceleration for the MCLM or MCCM instruction.
Termination Type
0 = actual tolerance
1 = no settle
2 = command tolerance
3 = no decel
Lgx00038048, Lgx00041461
Large Message (MSG) Instructions Might The following configuration of a Message (MSG) instruction might have produced a
Have Caused a Non-Recoverable Fault non-recoverable fault:
• Message type = CIP Data Table Read or Write

• The instruction transferred > 240 bytes.
• Communication was through the serial port.
When the controller experiences a non-recoverable fault, it clears the project from memory.
Lgx00040892
During Power Up, the Controller Erroneously During power up, the controller sometimes showed a flashing red I/O LED when there was
Showed a Red I/O LED. no problem
Lgx00040151
AutoTune Produced Unnecessary Warnings When you completed an autotune of an Enhanced PID (PIDE) function block instruction, the
Autotune Status field sometimes showed warning messages that were incorrect (did not
apply).
Lgx00041613


Ramp/Soak (RMPS) Instruction Failed to On download, a Ramp/Soak (RMPS) Instruction now initializes to Operator Manual mode
Initialize to the Correct Mode unless some other mode is requested.
In previous revisions, the instruction failed to initialize to the correct mode. This lack of
initialization could have caused the RMPS instruction to ignore the soak time for the first
ramp/soak segment.
Lgx00043665
Remote Output Module Momentarily The following combination of circumstances occasionally caused an output module to drop
Dropped Its Connection its connection to the controller and then re-establish the connection:
• The module was in a remote chassis.
• The module used a Rack Optimization communication format.
• The controller also executed a Message (MSG) instruction that bridged across the
backplane of that same remote chassis to another communication module.
Occurred most frequently if the MSG instruction was not cached.
Lgx00043674
Non-recoverable Fault Occurred when A non-recoverable fault occurred on some motion moves when the speed was set to zero.
Motion Speed Set to Zero This occurred because planning calculations divided by 0.
Lgx00045079

Restrictions This revision of ControlLogix controllers has the following restrictions:
Restriction: Description:
In a Tag of a User-Defined Data Type, an If you write too much data to an array that is within a user-defined data type, some
Instruction May Write Past the End of an instructions write beyond the array and into other members of the tag.
Array.
Example 1: Instruction If the length is greater than the number
Stops at the End of the Array of elements in the destination array…
…the instruction stops at the end of

the array.

Writes Beyond the Array of elements in the destination array…
…the instruction writes data beyond

the end of the array into other members
of the tag. Regardless of the length
specified for the instruction, it stops
writing if it reaches the end of the tag.
The following instructions write beyond the array into other members of the tag:
BSL FBC LFL

BSR FFL LFU
COP FFU SQL
CPS FLL SRT
DDT GSV SSV
This restriction also applies to all previous revisions.
To prevent writing beyond the limits of the destination array, make sure the length operand
of the instruction is less than or equal to the number of elements in the array.
Lgx00033747

In Circular Center Programming Mode, a If you configure a Motion Coordinated Circular Move (MCCM) instruction as shown below,
Motion Coordinated Circular Move (MCCM) the instruction may not produce a move to the specified end points.
Instruction May Fail to Reach the Specified
End Point of a 180 Degree Arc If the Circle
Center Is Miss-Programmed.
2-dimensional circle (2 axes)
end points are specified to produce an arc of

180 degrees
Circle Type = 1 (center) or 3 (center

incremental).
user-defined center is not correct but within the

current % radius deviation allowance
To work around this restriction, enter the correct circle center.

Lgx00044813
Blended Path Contour May Deviate Beyond In some very unique circumstances, when either changing velocity profile types or having
the Confines of the Programmed Path drastically different acceleration and/or deceleration values on the two moves comprising a
blended contour, the resultant blended path contour may deviate beyond the confines of the
programmed path.
Lgx00045400
1756-L55M16 controllers—Guidelines for You cannot download a project that has very large routines to a 1756-L55M16 controller.
the Size of Routines During the download, RSLogix 5000 software indicates that the controller is out of memory.
(While online, you may be able to create a very large routine, but once offline you will be
unable to download the project.)
To avoid creating routines that are too large, take these precautions:
• Limit the number of rungs in a routine to less than 2500. (Use a series of smaller
routines.)
• If you are entering a large number of rungs in a routine, do this offline.
• As you enter rungs, periodically download the project. If the project successfully
downloads, then your routines are within limits.

1756-L55M16 controllers—3.5M Byte Limit You cannot download a project that has more than 3.5M bytes of tags to a 1756-L55M16
of Tags controller. During the download, RSLogix 5000 software indicates that the controller is out
of memory.
To stay within the 3.5M byte limit, use the Memory tab of the Controller Properties
window.:
In general, the data and logic memory

represents the 3.5M byte limit for tags.
As you develop your project, periodically go to

this tab and click the Estimate button.
Keep your used memory within the green area.

Once the used memory is in the yellow, the
controller may not have enough memory for
runtime communication.
For a detailed description of how the controller

organizes its memory, see Logix5000
Controllers Common Procedures, publication
1756-PM001.

Additional Memory Revision 13.0 or later may require more memory than previous
revisions (e.g., 10.x, 11.x). To estimate the additional memory that
Requirements your project may require, use the following table:
Table 1 Additional memory requirements when you convert a project to revision 13 (Sheet 1 of 2)
If you have this Then add the following memory requirements to your project: Which comes from this
firmware revision type of memory:
(add all that apply):
Component Increase per I/O Data and Logic
instance (base) (expansion)
12.x or earlier I/O module with a comm format = Rack Optimization 90 bytes ✔
I/O module with a comm format = something other than 144 bytes ✔
Rack Optimization (i.e., direct connection)
CompactLogix 1769 I/O module 170 bytes ✔
bridge module with a comm format = None 160 bytes ✔
bridge module with a comm format = Rack Optimization 220 bytes ✔
11.x or earlier tag that uses the MOTION_INSTRUCTION data type 4 bytes ✔
tag for an axis
If the data type is: And the tag is:
AXIS_CONSUMED !!!!!!!!! 264 bytes ✔
AXIS_SERVO produced for another controller 264 bytes ✔
not produced for another controller 264 bytes ✔
AXIS_SERVO_DRIVE produced for another controller 288 bytes ✔
AXIS_VIRTUAL produced for another controller 264 bytes ✔
output cam execution targets 648 bytes ✔
user-defined data type: 128 bytes ✔
• number of user-defined data types in the controller
organizer ! Data Types folder ! User-Defined
folder
• not the use of that data type in tags
indirect address (using a tag as the subscript for an array in (-60 bytes) ✔
an instruction, e.g., Array_A[Tag_B]). This memory change
applies only if the array:
• uses a structure as its data type
• does not use one of these data types: CONTROL,
COUNTER, PID, or TIMER
• has only one dimension (e.g., UDT_1[5])

Table 1 Additional memory requirements when you convert a project to revision 13 (Sheet 2 of 2)
If you have this Then add the following memory requirements to your project: Which comes from this
firmware revision type of memory:
(add all that apply):
Component Increase per I/O Data and Logic
instance (base) (expansion)
10.x or earlier project for a ControlLogix5555 controller 1200 bytes ✔
project for a ControlLogix5563 controller 1200 bytes ✔
programs 12 bytes ✔
routines 16 bytes ✔
9.x or earlier project for a ControlLogix5550 controller 1200 bytes ✔
tag that uses the MESSAGE data type 376 bytes ✔
8.x or 9.x produced or consumed axis (-21.6K bytes) ✔
axis that is not produced or consumed (-21.6K bytes) ✔
8.x or earlier output cam execution targets 5,404 bytes ✔
motion group 32 bytes ✔
7.x or earlier project 1050 bytes ✔
tags 0.55 bytes ✔
messages that: 2000 bytes ✔
• transfer more than 500 bytes of data
and
• target a controller in the same chassis
This memory is allocated only when the MSG instruction is
enabled. To estimate, count the number of these messages
that are enabled and/or cached at one time.
6.x or earlier base tags 24 bytes ✔
alias tags 16 bytes ✔
produced and Data type Bytes per tag
consumed tags
DINT 4 12 bytes ✔
REAL 4 12 bytes ✔
3 x bytes per tag ✔
3 x bytes per tag ✔
6.x routines 68 bytes ✔
5.x or earlier routines 116 bytes ✔

Notes:

Rockwell Automation provides technical information on the web to assist you in using our products. At
http://support.rockwellautomation.com, you can find technical manuals, a knowledge base of FAQs, technical and
application notes, sample code and links to software service packs, and a MySupport feature that you can customize
to make the best use of these tools.
For an additional level of technical phone support for installation, configuration and troubleshooting, we offer
TechConnect Support programs. For more information, contact your local distributor or Rockwell Automation
If you experience a problem with a hardware module within the first 24 hours of installation, please review the
information that's contained in this manual. You can also contact a special Customer Support number for initial help
in getting your module up and running:
United States 1.440.646.3223

Monday – Friday, 8am – 5pm EST
Outside United States Please contact your local Rockwell Automation representative for any technical support issues.
Rockwell tests all of our products to ensure that they are fully operational when shipped from the manufacturing
facility. However, if your product is not functioning and needs to be returned:
United States Contact your distributor. You must provide a Customer Support case number (see phone number
above to obtain one) to your distributor in order to complete the return process.
Outside United States Please contact your local Rockwell Automation representative for return procedure.
ControlNet is a trademark of ControlNet International, Ltd.
DeviceNet is a trademark of the Open DeviceNet Vendor Association.

Back Cover
Publication 1756-RN603E-EN-E - November 2004 20 PN 957944-37

Supersedes Publication 1756-RN603D-EN-E - August 2004 Copyright © 2004 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.
Application Solution
Maintain the Battery of a ControlLogix

Series B Controller
Catalog Number 1756-L61/B, 1756-L62/B, 1756-L63/B, 1756-BA2
When to Use this Document Use this document to make sure your 1756-BA2 battery:
• has enough capacity to hold the memory of the controller
• doesn’t leak or cause other hazards
Use the following table to see if this document is for your controller:
If you have this controller And this series Then

ControlLogix5550 ! STOP! Your controller uses a 1756-BA1 battery. See ControlLogix System User
ControlLogix5555 Manual, publication 1756-UM001, for that battery.
ControlLogix5560M03SE
ControlLogix5561 A STOP! Your controller uses a 1756-BA1 battery. See ControlLogix System User
ControlLogix5562 Manual, publication 1756-UM001, for that battery.
ControlLogix5563 B YES, your controller uses a 1756-BA2 battery. Use this publication for that battery.
How to Use this Document This document gives you the following information:
If you want to: Then see this section: On this page:

Learn how the controller uses the battery About the 1756-BA2 Battery 1-3
Learn what effects battery life
See if your battery is low See If the Battery Is Low 1-3
See why the BAT light is red
Decide when to replace your battery Estimate When the Battery Becomes 1-4
Low
See how long the battery will last
See how long you have after the battery is low Estimate Warning Time 1-5
Change a depleted battery Replace a Battery 1-6
Store spare batteries Store Batteries 1-8
1 Publication 1756-AP014A-EN-E - November 2004

2 Maintain the Battery of a ControlLogix Series B Controller
Important User Information Solid state equipment has operational characteristics differing from those of
electromechanical equipment. Safety Guidelines for the Application,
Installation and Maintenance of Solid State Controls (Publication SGI-1.1
available from your local Rockwell Automation sales office or online at
http://www.ab.com/manuals/gi) describes some important differences
between solid state equipment and hard-wired electromechanical devices.
Because of this difference, and also because of the wide variety of uses for
solid state equipment, all persons responsible for applying this equipment
must satisfy themselves that each intended application of this equipment is
acceptable.
In no event will Rockwell Automation, Inc. be responsible or liable for
indirect or consequential damages resulting from the use or application of
this equipment.
The examples and diagrams in this manual are included solely for illustrative
purposes. Because of the many variables and requirements associated with
any particular installation, Rockwell Automation, Inc. cannot assume
responsibility or liability for actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to
use of information, circuits, equipment, or software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without
written permission of Rockwell Automation, Inc. is prohibited.
Throughout this manual, when necessary we use notes to make you aware of
safety considerations.
Identifies information about practices or circumstances

WARNING
that can cause an explosion in a hazardous environment,
which may lead to personal injury or death, property
damage, or economic loss.
Identifies information that is critical for successful

IMPORTANT
application and understanding of the product.
Identifies information about practices or circumstances

ATTENTION
that can lead to personal injury or death, property
damage, or economic loss. Attentions help you:
• identify a hazard
• avoid a hazard
• recognize the consequence
SHOCK HAZARD Labels may be located on or inside the equipment (e.g.,

drive or motor) to alert people that dangerous voltage may
be present.
BURN HAZARD Labels may be located on or inside the equipment (e.g.,

drive or motor) to alert people that surfaces may be
dangerous temperatures.
Publication 1756-AP014A-EN-E - November 2004

Maintain the Battery of a ControlLogix Series B Controller 3
About the 1756-BA2 Battery This section gives you some general information about the 1756-BA2
battery:
How does the controller use the Series B of the ControlLogix5561, ControlLogix5562, and ControlLogix5563 controllers use
battery? the battery to:
• store a copy of your project when you power down the controller. The controller
stores the copy in its internal nonvolatile memory. This memory is built into the
controller and is separate from the CompactFlash card.
• keep its internal clock running when the controller is without power
What effects battery life? In series B of the ControlLogix5561, ControlLogix5562, and ControlLogix5563 controllers,
battery life depends primarily on:
• chassis temperature
• project size
• how often you cycle power
In addition, there is always a small constant drain on the battery. The drain is the same
whether or not the controller has power.
See If the Battery Is Low When the battery is about 95% discharged, the controller gives the
following low-battery warnings:
• The BAT light turns solid red.

• A minor fault occurs (type 10, code 10).
BAT light
ATTENTION To prevent your battery from leaking potentially dangerous chemicals,

replace your battery according to the following schedule. Replace the
battery EVEN IF the BAT light is off:
If the temperature 1 in. below the Replace the battery within:

chassis is:
0° … 35° C No required replacement
36° … 40° C 3 years
41° … 45° C 2 years
46° … 50° C 16 months
51° … 55° C 11 months
56° … 60° C 8 months

Estimate When the Battery Use the following table to estimate how long before the battery
becomes low (BAT light = solid red).
Becomes Low
Maximum Temperature (° C) 1 in. Power Cycles Battery Life Before the BAT Light Turns Red (Worst-Case
Below the Chassis. Estimate)
Project Size
1M bytes 2M bytes 4M bytes 8M bytes
0°…40° C 3 per day 3 years 3 years 26 months 20 months
2 per day or less 3 years 3 years 3 years 31 months
41°…45° C 3 per day 2 years 2 years 2 years 20 months
2 per day or less 2 years 2 years 2 years 2 years
46°…50° C 3 per day or less 16 months 16 months 16 months 16 months
EXAMPLE Under the following conditions…

• The maximum temperature 1 in. below the chassis = 45º C.
• You cycle power to the controller 3 times per day.
• The controller contains an 8M byte project.
…the battery will last at least 20 months before the BAT light turns
red.

Estimate Warning Time Use the following table to estimate the battery life after the low-battery
warning (BAT light = solid red). Use these times whether or not the
controller has power. There is always a small constant drain on the
battery.
IMPORTANT When you power up the controller, see if there is a low-battery

warning. If you get a low-battery warning for the first time, you have
less battery life than this table shows. While powered down, the
controller still drains the battery but it can’t give the low-battery
warning.
Maximum Temperature (° C) 1 in. Power Cycles Battery Life After the BAT Light Turns Red (Worst Case)
Below the chassis.
Project Size
1M bytes 2M bytes 4M bytes 8M bytes
0°…20° C 3 per day 26 weeks 18 weeks 12 weeks 9 weeks
1 per Day 26 weeks 26 weeks 26 weeks 22 weeks
1 per Month 26 weeks 26 weeks 26 weeks 26 weeks
EXAMPLE Under the following conditions…

• The maximum temperature 1 in. below the chassis = 45º C.
• You cycle power to the controller 3 times per day.
• The controller contains an 8M byte project.
…the battery is good for another 6 weeks after the BAT light turns
red.

Replace a Battery To replace a battery:
When you connect or disconnect the battery an electrical arc can occur. This could cause an
WARNING
explosion in hazardous location installations. Be sure that power is removed or the area is
nonhazardous before proceeding.
For Safety information on the handling of lithium batteries, including handling and disposal
of leaking batteries, see Guidelines for Handling Lithium Batteries, publication AG 5-4.
Install only a 1756-BA2 battery. Other batteries could damage the controller.
ATTENTION
Step: Details:
1. Remove the old battery. A. Is the old battery leaking or damaged?
• If YES, continue with step B.
• If NO, go to step C.
B. Look in Guidelines for Handling Lithium Batteries, publication AG-5.4, and read the
information on how to handle damaged or leaking batteries.
C. Decide if the controller needs power while you change the battery:
If you need to keep the Then

current setting of the controller's clock Turn on the chassis power.
information about non-recoverable faults Turn on the chassis power.
neither of the above Leave the chassis power on or off.
D. Remove the old battery.

2. Install a new 1756-BA2 battery.
A. Insert the battery with the arrow pointing up as

shown.
COMPACT
FLASH
1-DCD
DSR-6 2-RXD
RTS-7 3-TXD
CTS-8 4-DTR
N/C-9 5-GND
RS232
1 To
Insert 1
2 To Eject
1+2
B. Connect the battery.

UP 2
BATTERY
+ red
DATE
BATTERY
PORT - black
Continued on next page.

Step: Details:
3. Make sure the new battery A. Turn on the chassis power if it’s not already on.
is OK.
B. What color is the BAT light?
BAT light • If it is OFF, then the battery is OK. Go to step 4.

• If it is RED, then continue with step C.
C. Make sure you correctly connected the battery.
D. What color is the BAT light now?

• If it is OFF, then the battery is OK. Go to step 4.
• If it is RED, then continue with step E.
E. Try another 1756-BA2 battery.
F. What color is the BAT light now?

• If it is OFF, then this battery is OK but the earlier battery is also depleted. Go to
step 4.
• If it is RED, then contact your Rockwell Automation representative or local
distributor.
4. Write down when you installed
the new battery.
COMPACT
FLASH
1-DCD
DSR-6 2-RXD
RTS-7 3-TXD
CTS-8 4-DTR
N/C-9 5-GND
RS232
1 To
Insert 1
2 To Eject
1+2
2
A. Find the small rectangular label that comes with the
UP
BATTERY
DATE
1
new battery.
2
BATTERY
PORT
B. Write today’s date on the label.
C. Attach the label to the inside of the controller door.

DATE
5. Safely dispose the depleted To dispose of depleted batteries, see Guidelines for Handling Lithium Batteries, publication
battery or batteries. AG 5-4. That publication comes with the new battery.

Store Batteries
ATTENTION Follow these general rules to store your batteries:

• Store batteries in a cool, dry environment. We recommend 25°C
with 40%…60% relative humidity.
• You may store batteries for up to 30 days between -45°…85°C,
such as during transportation.
• To avoid leakage or other hazards, DO NOT store batteries above
60°C for more than 30 days.
For detailed guidelines on how to store your batteries, see Guidelines

for Handling Lithium Batteries, publication AG 5-4. That publication
comes with your new battery.
Back Cover
ö
!
Publication 1756-AP014A-EN-E - November 2004 8 PN 957944-27
Supersedes Publication - Copyright © 2004 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.
Release Notes
ControlLogix® Redundancy System

Revision 13
Cat. No. 1756-CNB/D, 1756-CNBR/D, 1756-ENBT, 1756-EWEB,

1756-L55, 1756-L55M12, 1756-L55M13, 1756-L55M14,
1756-L55M16, 1756-L55M22, 1756-L55M23, 1756-L55M24,
1756-L61, 1756-L62, 1756-L63, 1757-SRM
IMPORTANT If you have a 1756-L55 controller, you must install a memory board.
For more information, see the ControlLogix Controller and Memory
Board Installation Instructions, publication 1756-IN101.
When to Use These Release These release notes correspond to the following modules when used
in a ControlLogix® redundancy system:
Notes
IMPORTANT For a module in a redundant controller chassis, make sure the catalog revision of the
module is greater than or equal to the catalog revision shown in the following table.
Otherwise, the secondary chassis will not synchronize with the primary chassis.
Ethernet/IP 10/100 Mb/s To determine the catalog revision of a module, look at the
ControlLogix COMMUNICATIONS BRIDGE
label on the side of the module or box.
CAT. NO./SERIES CAT. REV.
1756-ENBT/A E01
catalog revision
Module: Catalog number: Catalog revision (or greater) Firmware revision:

ControlLogix5555™ controller 1756-L55Mxx any 13.53
ControlLogix5561 controller 1756-L61 any 13.53
ControlNet™ bridge module 1756-CNB/D or -CNBR/D any 5.45
1756 10/100 Mbps EtherNet/IP 1756-ENBT E01 (e.g., E01, E02, …, F01, etc.) 3.4
Bridge, Twisted Pair Media
1756 10/100 Mbps EtherNet/IP 1756-EWEB any 2.2
Bridge w/ Enhanced Web Services
redundancy module 1757-SRM/A or -SRM/B any 3.37
1 Publication 1756-RN608D-EN-E - December 2004

2 ControlLogix® Redundancy System Revision 13
Compatible Revisions To use this revision, update your system as follows:
Update this software: To this revision Notes:

or later:
RSLinx® 2.42 • This revision of RSLinx software automatically installs 1757-SRM System
Redundancy Module Configuration tool revision 2.5.
• See Restrictions on page 10.
RSLinx Enterprise 3.0 Required only for certain HMI software such as:
• PanelView Plus™ terminal
• RSView® Supervisory Edition software
• VersaView™ industrial computer running a Windows® CE operating system
1757-SRM System 2.6 If you install: Then:
Redundancy Module
RSLinx software Before you install 1757-SRM System Redundancy Module
Configuration Tool
revision 2.42 Configuration tool revision 2.6, see Restrictions on
page 10.
To install 1757-SRM System Redundancy Module

Configuration tool revision 2.6, see Knowledgebase
document G92234770. To access Rockwell Automation’s
Knowledgebase, go to
http://support.rockwellautomation.com
RSLinx software RSLinx software revision 2.43 automatically installs
revision 2.43 1757-SRM System Redundancy Module Configuration tool
(available in the future) revision 2.6.
To see which revision of the 1757-SRM System Redundancy Module Configuration tool is currently
installed:
1. In RSLinx software, browse to a SRM module.
2. Right-click the SRM module and choose Module Configuration.
3. Right-click the title bar of the configuration tool and choose About…
RSLogix™ 5000 13.0
RSNetWorx™ for ControlNet™ 4.21
RSNetWorx™ for DeviceNet™ 4.21
Publication 1756-RN608D-EN-E - December 2004

ControlLogix® Redundancy System Revision 13 3
What Is In These Release These release notes provide the following information about the
components of the redundancy system:
Notes
For information about: See this section: On this page:
order in which to update your system How to Update Your Firmware 3
new features Enhancements 4
restrictions that no longer apply Corrected Anomalies 7
restrictions to your redundancy system Restrictions 9
For more information on the ControlLogix redundancy system, see the

ControlLogix Redundancy System User Manual, publication
1756-UM523.
How to Update Your Update your firmware in the following order:

Firmware
1. Update the SRM module firmware.

ATTENTION
It takes several minutes to update a 1757-SRM/A or -SRM/B
! module. Do not interrupt the process. Make sure you wait until
the SRM module displays REV 3.37 on its four-character display.
If you interrupt the process, the module may become
inoperative.
When you update the module, it performs the following

sequence:
• Two downloads (ERAS/PROG on display twice)
• Reset to rev. 2.20 (FLSH UPDT REQD)
• Two more downloads (ERAS/PROG on display twice)
• Second reset before the update is complete
If the OK LED on the SRM module is red flashing and the

4-character display is blank, then the firmware update has failed.
Do not cycle the power to the module. Leave the power on and
update the firmware of the module again.
2. Update the CNB, ENBT, and EWEB module firmware.
3. Update the controller firmware.

Enhancements This revision contains the following enhancements that are specific to
a redundant system. For the list of enhancements that apply to both
redundant and non-redundant systems, see the following release
notes:
• ControlLogix Controller Revision 12 Release Notes, publication
1756-RN601
• ControlLogix Controller Revision 13 Release Notes, publication
1756-RN603
ControlLogix5555, 5561, 5562, 5563 Rev 13.53
Sequential Function Charts This revision lets you use the sequential function chart (SFC) programming language to program your
redundancy system.
More Stable Scan Times This revision reduces the jumps in program scan time that may have occurred in previous revisions. The
jumps were caused by programs with fast scan times or large crossloads that flooded the 1757-SRM
module with data, which increased the crossload time.
One ControlLogix5561, 5562, This revision lets you place a ControlLogix5561, 5562, or 5563 controller in a redundant chassis:
5563 Controller in a • Use only 1 ControlLogix5561, 5562, or 5563 controller in a redundant chassis
Redundant Chassis
• Use an identical controller in the same slot in the partner chassis.
• Do not mix ControlLogix5561, 5562, or 5563 controllers in the same chassis with
ControlLogix5555 controllers.
The program scan time improvement when using one of these controllers in a redundant system is less
than in a non-redundant system.
• Even though the ControlLogix5561, 5562, and 5563 controllers execute logic faster, they must
still crossload data.
• Given the same project and redundant system, a ControlLogix5561, 5562, or 5563 controller is
up to 30% faster than a ControlLogix5555 controller.
Up to 2 ControlLogix5555 This revision lets you place up to 2 ControlLogix5555 controllers in a redundant chassis:
Controllers in the Same • Use identical controllers in the same slots in the partner chassis.
Redundant Chassis
• Do not mix ControlLogix5555 controllers in the same chassis with ControlLogix5561, 5562, or
5563 controllers
• Use separate ControlNet bridge modules for each controller. See Restrictions on page 9.
1756-EWEB module in a local Place 1756-EWEB modules in a redundant chassis pair:
redundant chassis Important: If you use RSLinx Enterprise software revision 2.0, put your 1756-ENBT or 1756-EWEB
modules in a non-redundant chassis and bridge the communication over a ControlNet network to the
redundant chassis.
• Place an EWEB module in the same slot in each redundant chassis. (The modules in each
redundant chassis must match each other slot-by-slot.)
• Place up to 2 EtherNet/IP modules in each redundant chassis.
• Use any mix of ENBT or EWEB modules.
• The remaining communication modules must be either 1756-CNB or -CNBR modules, for a
total of 5 communication modules per redundant chassis.
• In a redundant system, use an EtherNet/IP network only for HMI/workstation communication
and messaging. Do not use an EtherNet/IP network for:
• communication with I/O modules
• communication between devices via produced/consumed tags

Duplicate IP Address Detection 1756-ENBT and 1756-EWEB modules now detect if their IP address conflicts with another device on the
EtherNet/IP network. How the modules respond to the conflict depends on the following conditions:
If: And: The:

Both devices have One of the devices is in a • The device in the redundant chassis uses
duplicate IP address redundant chassis. the IP address.
detection. • The other device stops communicating
on the network.
Both devices are outside of • The second device to access the network
a redundant chassis. uses the IP address.
• The other device stops communicating
on the network.
One of the devices does The other device is in a Both devices try to communicate at that
not have duplicate IP redundant chassis. IP address.
address detection.
Both devices are outside of • The device without duplicate IP address
a redundant chassis. detection uses the IP address.
• The other device stops communicating
on the network.
In a redundant chassis, an ENBT or EWEB module uses duplicate IP address detection to swap its IP
address with its partner during a switchover. See “Automatic IP Address Swapping” on page 5.
Automatic IP Address Swapping During a switchover, 1756-ENBT and 1756-EWEB modules now swap their IP addresses with their
partner modules in the other redundant chassis. This lets you use the same IP address to communicate
with a primary module regardless of which chassis is primary.
• Typically, you no longer need to use ControlLogix Redundancy Alias Topic Switcher software to
manage the IP addresses. If your application still requires alias topics to manage IP addresses,
see ControlLogix Redundancy System User Manual, publication 1756-UM523.
• During a switchover, communication over an EtherNet/IP network with other controllers or HMI
may freeze for up to a minute, depending on network topology. If you need bumpless
communication with controllers/HMIs, use a separate ControlNet network that is dedicated to
communication with those devices.
Important: Make sure to connect the 1757-SRCx cable to both 1757-SRM modules of the redundant
chassis pair. Otherwise, the ENBT and EWB modules will show a duplicate IP address.
To let the modules swap IP addresses during a switchover:
1. Allocate 2 consecutive IP addresses for each set of ENBT or EWEB modules (one in each
chassis). For example, 10.10.10.10 and 10.10.10.11.
2. Give the same IP address, gateway address, and subnet mask to both modules in the redundant
pair. (E.g., Set both IP address = 10.10.10.10.)
The module in the primary chassis uses the IP address to which it is configured
(e.g., 10.10.10.10).
The module in the secondary chassis uses the IP address of the primary +1 in the last address
segment (e.g., 10.10.10.11).

Set the Clock of a 1757-SRM Requires 1757-SRM System Redundancy Module configuration tool, revision 2.6 or later. See
Module to the Workstation Restrictions on page 10.
Clock
To send the currently running

workstation (PC) time to the SRM
module, click this button.
Event Log Provides More Requires 1757-SRM System Redundancy Module configuration tool, revision 2.6 or later. See
Information Restrictions on page 10.
Export file includes extended information in text format
See events in both SRM

modules at the same time
See extended information

in text format

Corrected Anomalies This revision corrects the following anomalies:
ControlLogix5555, 5561, 5562, 5563 Rev 13.53
Anomaly: Description:
RSLinx Enterprise Software and Local If you use Then
Ethernet Modules
RSLinx Enterprise Put your 1756-ENBT or 1756-EWEB modules in the redundant
software revision 3.0 chassis pair.
RSLinx Enterprise Put your 1756-ENBT or 1756-EWEB modules in a non-redundant
software revision 2.0 chassis and bridge the communication over a ControlNet network
to the redundant chassis.
Product Service Advisory ACIG Revision 5.45 of the 1756-CNB and 1756-CNBR module corrects the following issue:
2004-11-002
Continuous operation prevented additional unconnected communications
After 497 days of uninterrupted continuous operation, the unconnected buffer resources soon
became unavailable. The result of the ControlNet module's unconnected buffers being unavailable
was that you could no longer communicate with the module via unconnected messaging. Some
examples of how module services were affected included:
• Unconnected message connections that were passed to or through the ControlNet module
failed
• Any attempt to go online with a controller through the ControlNet module failed (i.e.,
programming terminal connection failed)
• Establishing or re-establishing I/O connections failed
• Browsing to or through the module via RSLinx failed
• CPU % utilization reading quickly went to 100% and stayed there
Lgx00052277
Secondary Chassis Synchronized with Revision 3.4 of the 1756-ENBT module corrects the following issue:
ENBT Module NOT Connected
A secondary chassis synchronized even if a 1756-ENBT module wasn’t connected to the
EtherNet/IP network. For example, the chassis synchronized when you unplugged or broke the
ethernet cable of the ENBT module.
Lgx00035956
ENBT Module Erroneously Reported a Revision 3.4 of the 1756-ENBT module corrects the following issue:
Duplicate IP Address
It was possible for an ENBT module to erroneously report a duplicate IP address under these
conditions:
• high HMI traffic
• secondary chassis was powering up (depended on your configuration)
This resulted in a failure to synchronize.

Anomaly: Description:
Online Memory Information Was
Incorrect While online, RSLogix 5000
software showed incorrect values
for the memory usage of the
controller.
Lgx00042913
Modules Incorrectly Indicated Primary A module in a primary chassis incorrectly indicated Primary with Disqualified Secondary under the
with Disqualified Secondary After the following conditions:
Secondary Module Was Removed 1. The secondary module was present but disqualified
2. While the secondary module was disqualified, you removed it from the chassis.
Both the software and hardware showed the incorrect redundancy state of the module.
Lgx00045469
Connections Prematurely Timed-Out A connection prematurely timed-out under the following combination of circumstances:
• RPI of the connection was approximately 15 to 25 ms.
• CPU usage of the CNB module was close to 98 - 100%.
Lgx00045470
Switchover Extended Task Period If the period of a periodic task expired during a switchover, the task might have delayed its
execution 2 times the specified period. After this extended period, it returned to its specified
period.
Lgx00045661
After a Switchover, the Maximum After a switchover, a periodic task might have shown a maximum interval time that was
Interval Time for a Periodic Task approximately 1 second longer than the actual value.
Might Have Been Incorrect Lgx00046215
After a Switchover, Watchdog Timer If the period of a periodic task expired during a switchover, the watchdog timer for the task might
May Have Been Temporarily Inactive not have been active during the first execution after the switchover. On subsequent executions,
the timer became active again.
Lgx00046229

Restrictions This revision contains the following restrictions:
IMPORTANT In a redundant system, use an EtherNet/IP network only for

HMI/workstation communication and messaging.
Do not use an EtherNet/IP network for:
• communication with I/O modules
• communication between devices via produced/consumed tags
Use a Separate ControlNet Bridge Do you have 2 ControlLogix5555 controllers in the SAME redundant chassis?
Module for Each ControlLogix5555
• YES — Read this restriction.
Controller
• NO — This restriction doesn’t apply to you.
Use a separate 1756-CNB or 1756-CNBR module for each ControlLogix5555 controller in a

redundant chassis. If you have 2 controllers in a chassis:
• You must have at least 2 ControlNet bridge modules in the chassis.
• Use each ControlNet bridge module for the communication of only ONE controller. DON’T
share a ControlNet bridge module between controllers.
Example
Suppose you have 2 ControlLogix5555 controllers in each redundant chassis. In that case:
1. Put at least 2 ControlNet bridge modules in each redundant chassis.
2. Use one of the ControlNet bridge modules for the I/O, interlocking, and messages of one
of the controllers.
3. Use the OTHER ControlNet bridge module for the I/O, interlocking, and messages of the
OTHER controller.
Communication stops through the ControlNet bridge module if you don’t follow this restriction.
Communication stops under these circumstances:
1. The secondary chassis becomes disqualified.
2. The secondary chassis synchronizes again.
3. A switchover happens.
Lgx00052928
Secondary Chassis Synchronizes with A secondary chassis synchronizes even if a 1756-EWEB module isn’t connected to the EtherNet/IP
EWEB Module NOT Connected network. For example, if you unplug or break the ethernet cable of the EWEB module, then:
• The EWEB module shows Link lost.
• The secondary chassis synchronizes.
Lgx00035956

EWEB Module Erroneously Reports a It is possible for a 1756-EWEB module to erroneously report a duplicate IP address under these
Duplicate IP Address conditions:
• high HMI traffic
• secondary chassis is powering up (depends on your configuration)
This results in a failure to synchronize.
If this happens, cycle power to the secondary chassis.

1757-SRM System Redundancy If you use revision 2.5 of the 1757-SRM System Redundancy Module Configuration Tool in a
Module Configuration Tool Revision revision 13.x redundancy system, the event log lists any 1756-L6x controller or 1756-EWEB
2.5 Does Not Recognize Some module as “Unknown Device Code 5.”. This does not affect the operation of the redundant
Devices system.
Do Not Use 1757-SRM System If you also connect your computer to ControlLogix redundancy systems revision 11.x or earlier, do
Redundancy Module Configuration not install 1757-SRM System Redundancy Module Configuration Tool revision 2.6.
Tool Revision 2.6 with ControlLogix • Revision 2.6 is compatible only with revision 13.x or later ControlLogix redundancy
Redundancy Systems Revision 11.x or systems. Using revision 2.6 of the tool with an earlier revision of ControlLogix redundancy
earlier
systems could cause the 1757-SRM module to fault.
• Keep in mind that the following enhancements are available only in revision 2.6 or later of
the configuration tool:
• Set the Clock of a 1757-SRM Module to the Workstation Clock, listed on page 6
• Event Log Provides More Information, listed on page 6
When RSLinx software revision 2.43 becomes available, it will contain revision 2.6 of the
configuration tool.
Simultaneous Power of Redundant Under the following combination of conditions (all must apply), duplicate IP addresses on your
Chassis Pair May Bump Another EtherNet/IP network will cause you to lose communication with a redundant chassis pair over that
Redundant Chassis Pair Off the EtherNet/IP network:
EtherNet/IP Network • You have multiple pairs of redundant chassis on the same EtherNet/IP network. For
example, pair 1 and pair 2.
• The IP addresses of one pair of redundant chassis is the same as another pair of redundant
chassis. For example, pair 1 = 10.10.10.10 and pair 2 = 10.10.10.10.
• A redundant chassis pair with the conflict (both chassis that make up the pair)
simultaneously powers up. For example, both chassis of pair 2 power up at the same time.
When this occurs the newly powered up chassis use the IP address. The redundant chassis pair
that was previously communicating at that IP address stops communicating on the network. For
example, when pair 2 powers up at 10.10.10.10, pair 1 stops communicating on the network.
Recommended Minimum Scan Time The minimum attainable scan time for a ControlLogix redundancy project is approximately 20
milliseconds. At very low scan times, the processing of crossload data causes a greater
performance burden; this burden effectively limits the minimum scan time.
Do Not Use Event Tasks in the
Redundant Controllers In a redundant controller, do not
configure a task as an Event task.

Do Not Inhibit Any Tasks in the
Redundant Controllers
In a redundant controller, leave all

your tasks uninhibited.
Continued on next page.

In a Tag of a User-Defined Data Type, If you write too much data to an array that is within a user-defined data type, some instructions
an Instruction May Write Past the write beyond the array and into other members of the tag.
End of an Array.
Stops at the End of the Array of elements in the destination array…
…the instruction stops at the end of

the array.

Writes Beyond the Array of elements in the destination array…
…the instruction writes data beyond

the end of the array into other members
of the tag. Regardless of the length
specified for the instruction, it stops
writing if it reaches the end of the tag.
The following instructions write beyond the array into other members of the tag:
BSL FBC LFL

BSR FFL LFU
COP FFU SQL
CPS FLL SRT
DDT GSV SSV
This restriction also applies to all previous revisions.
To prevent writing beyond the limits of the destination array, make sure the length operand of the
instruction is less than or equal to the number of elements in the array.
Lgx00033747

Switchover Always Triggers an Event A switchover triggers an event task under the following combination of circumstances:
Task in a Remote, Non-Redundant • The event task is in non-redundant controller. (An Event task is not permitted in a
Controller redundant controller.)
• A redundant controller triggers the event task via a produced tag.
This occurs regardless of how you configure the produced tag.
Both configurations always trigger an

event task during a switchover.
Lgx00045349
If You Finalize All Edits in a Program When you finalize all edits in a program, the controller automatically removes the original logic. If
and the Edits Produce a Major Fault, the changes cause a switchover due to a major fault, the new primary controller also faults. This
both the Primary and Secondary occurs because there in no original logic to revert back to. (I.e., The new primary cannot untest the
Controller Experience the Fault. edits.)
Finalize All Edits in Program
This occurs even if you configure the

controller to untest edits on a
switchover.
Lgx00044659

Store a Redundant Project to Use the following procedure to store a project to the nonvolatile memory of a pair of redundant
NonVolatile Memory controllers. (Otherwise, the project may not correlate when you go online after the store
operation.)
1. Place the primary controller in program mode (program or remote program).
2. In the Module Configuration properties for one of the 1757-SRM modules, set the
Auto-Synchronization option = Conditional.
3. Disqualify the secondary chassis.
4. In the primary controller, store the project.
Important: Do not go back online to the primary controller until you complete the rest of
the steps in this procedure.
For step-by-step procedures on how to store a project, see Logix5000 Controllers Common
Procedures, publication 1756-PM001.
5. Go online to the secondary controller and store the project.
6. Synchronize the controllers.
7. In the Module Configuration properties for one of the 1757-SRM modules, set the
Auto-Synchronization option = the desired option.
Lgx00044659
Simultaneous Branch Delays the
Execution of a Higher Priority Task
In an SFC, each path of a simultaneous branch delays

the execution of a higher priority task by 25 µs.
Lgx00045471
Communication Module Occasionally After a switchover or simultaneous power cycle (both chassis cycle power at the same time), a
Uses a Duplicate Address 1756-CNB, 1756-ENBT, or 1756-EWEB module may try to use a duplicate address.
• When this occurs, the module displays DUPL NODE or DUPLICATE IP ADDRESS.
• This condition prevents you from communicating with the module and leaves the
secondary chassis disqualified (unsynchronized).
• Sometimes, an ENBT or EWEB module may show a duplicate IP address due to this
condition but the chassis still synchronize.
If this occurs cycle the power to the chassis with the module that has the duplicate address.
Lgx00047086

HMIs May Stop Communicating with Occasionally, HMIs that connect to a redundant controller via a 1756-ENBT or 1756-EWEB module
the Controller via EtherNet/IP may stop communicating with the controller after several switchovers. To recover, either:
Network After Several Switchovers
• If the secondary chassis is synchronized, switchover to that chassis.
• If the ENBT or EWEB module is in your RSLogix 5000 project, use the Properties window
for the module to reset the module.
• Remove the ENBT or EWEB module from the primary chassis and reinsert it into the
primary chassis.
Lgx00050497
High CNB Module Usage May You may not be able to store a project to the nonvolatile memory of a redundant controller under
Prevent a Store to Nonvolatile the following conditions:
Memory
• Your computer is connected to the controller via a CNB module.
• The CPU usage of the CNB module is greater than 75%.
Online Editing During a Switchover In some instances, RSLogix 5000 software may not let you perform additional online edits of a
function block, SFC, or structured text routine. This may occur if you edit the routine while online
and the system is switching over and synchronizing.
If this occurs:
1. Close and then open RSLogix 5000 software.
2. Upload the RSLogix 5000 project from the primary controller.
Deleting a Task Online If you delete a task while online with the controller, the secondary chassis may disqualify and
then synchronize.
Motion Control You cannot use the ControlLogix redundancy system in applications that require motion control.
(I.e., You cannot use a 1756-HYD02, 1756-M02AE, 1756-M02AS, 1756-M03SE, 1756-M08SE, or
1756-M16SE module.)
ASCII Instructions May Prevent the After you download a project that contains ASCII instructions (e.g., ABL, ACB) to a pair of
Secondary Controller From redundant controllers, the secondary controller may disqualify and fail to synchronize. If this
Synchronizing occurs, turn off both controllers (primary and secondary) and then turn the controllers back on.
Controller May Momentarily Drop Its In rare instances, if a tap to a 1756-CNB module is disconnected or breaks, the primary controller
Connection to a Digital I/O Module may momentarily drop its connection to a digital I/O module in local or remote chassis. The
connection automatically re-establishes.
To minimize this, use redundant ControlNet media. Redundant ControlNet media prevents a loss
of communication if a trunkline or tap is severed or disconnected.

Communication Loss When Bridging The following combination of modules in a remote chassis could cause a temporary
Through a 1756-CNB/B or -CNBR/B communication loss with the chassis:
Module
• 1756-CNB/B or -CNBR/B module
• 1756-DHRIO module that is connected to a remote I/O network.
redundant chassis
pair
L C S
5 N R
5 B M
M
x
1756-CNB/B or -CNBR/B module

remote
chassis
C D
N H
B other modules R
/ I
B O
remote I/O
On the first switchover after you download a project to the controller, you may
temporarily lose communications with these devices.
The loss of communication occurs on the first switchover after you download the project to the
redundant controller.
• You lose communication with the remote chassis and any devices to which you were
bridging via the chassis, such as the remote I/O modules.
• During the communication loss, the I/O modules go to their configured state for a
communication fault.
• The communication loss is temporary. Communications restore themselves.
To prevent this situation, use 1756-CNB/D or -CNBR/D modules.

If the Lowest Node Is a 1756-CNB/B If the lowest node on a ControlNet network is a 1756-CNB/B or -CNBR/B module, all
or -CNBR/B Module, Removing a Tap communications over the network could stop if:
or Breaking a Cable Could Stop All
• A tap to the 1756-CNB/B or -CNBR/B module is disconnected or breaks and then is
Communications over the Network
replaced while power is still applied to the 1756-CNB/B or -CNBR/B module
If a tap to a 1756-CNB/B or -CNBR/B module becomes disconnected or broken, take these actions:
1. Turn off the power to the 1756-CNB/B or -CNBR/B module.
2. Replace the tap.
If a communication failure occurs because of a disconnected or broken tap, cycle power to each
primary controller on the network.
To prevent this situation, use a 1756-CNB/D or -CNBR/D module as your lowest node on the
network.
1756-L55M16 controllers— You cannot download a project that has very large routines to a 1756-L55M16 controller. During
Guidelines for the Size of Routines the download, RSLogix 5000 software indicates that the controller is out of memory. (While
online, you may be able to create a very large routine, but once offline you will be unable to
download the project.)
To avoid creating routines that are too large, take these precautions:
• Limit the number of rungs in a routine to less than 2500. (Use a series of smaller routines.)
• If you are entering a large number of rungs in a routine, do this offline.
• As you enter rungs, periodically download the project. If the project successfully
downloads, then your routines are within limits.
1756-L55M16 controllers—3.5M You cannot download a project that has more than 3.5M bytes of tags to a 1756-L55M16
Byte Limit of Tags controller. During the download, RSLogix 5000 software indicates that the controller is out of
memory.
To stay within the 3.5M byte limit, use the Memory tab of the Controller Properties window.:
In general, the data and logic memory

represents the 3.5M byte limit for tags.
As you develop your project, periodically go to

this tab and click the Estimate button.
Keep your used memory within the green area.

Once the used memory is in the yellow, the
controller may not have enough memory for
runtime communication.
For a detailed description of how the controller

organizes its memory, see Logix5000
Controllers Common Procedures, publication
1756-PM001.

Rockwell Automation provides technical information on the web to assist you in using our products. At
http://support.rockwellautomation.com, you can find technical manuals, a knowledge base of FAQs, technical and
application notes, sample code and links to software service packs, and a MySupport feature that you can customize
to make the best use of these tools.
For an additional level of technical phone support for installation, configuration and troubleshooting, we offer
TechConnect Support programs. For more information, contact your local distributor or Rockwell Automation
If you experience a problem with a hardware module within the first 24 hours of installation, please review the
information that's contained in this manual. You can also contact a special Customer Support number for initial help
in getting your module up and running:
United States 1.440.646.3223

Monday – Friday, 8am – 5pm EST
Outside United States Please contact your local Rockwell Automation representative for any technical support issues.
Rockwell tests all of our products to ensure that they are fully operational when shipped from the manufacturing
facility. However, if your product is not functioning and needs to be returned:
United States Contact your distributor. You must provide a Customer Support case number (see phone number
above to obtain one) to your distributor in order to complete the return process.
Outside United States Please contact your local Rockwell Automation representative for return procedure.
ControlNet is a trademark of ControlNet International, Ltd.
DeviceNet is a trademark of the Open DeviceNet Vendor Association.
Back Cover
Publication 1756-RN608D-EN-E - December 2004 18 PN 957944-43

Supersedes Publication 1756-RN608C-EN-E - September 2004 Copyright © 2004 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.

Controllogix® Controller and Memory Board: Installation Instructions

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Controllogix® Controller and Memory Board: Installation Instructions

Uploaded by

Copyright:

Available Formats

Installation Instructions

ControlLogix® Controller and Memory Board

Are You Replacing a Controller That has Failed?

WARNING An electrical arc can occur if you:

Publication 1756-IN101J-EN-P - November 2004

Important User Information

Publication 1756-IN101J-EN-P - November 2004

Publication 1756-IN101J-EN-P - November 2004

Replace a Suspected Failed Controller

3. Match the catalog numbers of the

4. Install the battery.

7. Use ControlFlash software to update the firmware of

8. Download the RSLogix 5000 project to the controller.

Publication 1756-IN101J-EN-P - November 2004

ATTENTION Preventing Electrostatic Discharge

ATTENTION Personnel responsible for the application of safety-related

Publication 1756-IN101J-EN-P - November 2004

Avoid These Common Errors

If you have this Make sure that you:

Publication 1756-IN101J-EN-P - November 2004

Make Sure that You Have All the Components

You may also use these components with the controller:

increase the memory of the ControlLogix5550 memory board

For the correct memory board,

Publication 1756-IN101J-EN-P - November 2004

For the correct memory board,

maintain memory longer ControlLogix5550 NOT available for this

ControlLogix5561 Series B NOT available for this

Publication 1756-IN101J-EN-P - November 2004

Make Sure You Have the Correct Memory Board

Determine Which Firmware Revisions to Use

Publication 1756-IN101J-EN-P - November 2004

Use the following table to determine which firmware revisions to use

For this controller And this And: Use this revision OR

Publication 1756-IN101J-EN-P - November 2004

Prepare the Chassis

✓ Install a ControlLogix chassis.

✓ Install a ControlLogix power supply.

Remove the Controller from the Chassis, If Required

WARNING When you insert or remove the module while backplane

Repeated electrical arcing causes excessive wear to contacts on both

1. On the top and bottom of the controller, press the locking

Publication 1756-IN101J-EN-P - November 2004

Install a Memory Board on a ControlLogix5550 or ControlLogix5555

If your ControlLogix5550 or ControlLogix5555 controller requires a

Tools that You Need

If you have this And you are replacing the Then:

Publication 1756-IN101J-EN-P - November 2004

Remove the Side Plate of the Controller

2. While wearing a grounding wriststrap, remove the two screws

3. Rotate the side plate up and unhook it from the controller.

Publication 1756-IN101J-EN-P - November 2004

Remove the Existing Memory Board (If Any)

1. Does the controller already have a memory board?

Publication 1756-IN101J-EN-P - November 2004

3. Gently separate and remove the memory board from the

Publication 1756-IN101J-EN-P - November 2004

Install the Memory Board

3. Line up the connectors.

4. Place your hands on the boards over the connectors and

Publication 1756-IN101J-EN-P - November 2004

Replace the Side Plate

2. Gently press the side plate against the controller.