1756-RM ControlLogix Standard Redundancy Firmware

Redundancy Module Catalog Numbers

1756-RM2, 1756-RM2XT, 1756-RM, 1757-SRM

Controller Catalog Numbers

1756-L61, 1756-L62, 1756-L63, 1756-L64

Communication Module Catalog Numbers

1756-CNB/D, 1756-CNB/E, 1756-CNBR/D, 1756-CNBR/E, 1756-ENBT, 1756-EWEB

Table 1 - Required Series and Firmware Bundle Revisions for Components Used in a Redundancy

System, Revisions 16.057_kit1, 16.057_Aug, 16.057, 16.056, 16.053, and 16.050

Cat. No. Module Description Series Firmware Revision

1756-CNB ControlLogix® ControlNet™ bridge module D 7.016

1756-CNBR ControlLogix redundant ControlNet bridge

module

1756-CNB ControlLogix ControlNet bridge module E 11.005

1756-CNBR ControlLogix redundant ControlNet bridge

module

1756-ENBT ControlLogix EtherNet/IP bridge module Any 6.006

1756-EWEB ControlLogix EtherNet/IP web server module Any 4.016

1756-L61 ControlLogix5561 controller Any 16.057

1756-L62 ControlLogix5562 controller

1756-L63 ControlLogix5563 controller

1756-L64 ControlLogix5564 controller

1756-RM2 ControlLogix redundancy module A 20.004

1756-RM2XT ControlLogix redundancy module

1756-RM ControlLogix redundancy module A, B 2.006

1757-SRM ControlLogix system redundancy module A, B 5.004

Fault handlers can be defined at the controller and program scope levels. These fault handlers are typically used to handle major recoverable faults that can

occur during runtime execution of an application due to programming errors. A typical example of this would be handling indirect addressing that has gone

out of range; MyTag[index], where index is larger than the size of the array.

Faults can also be handled by the controller during pre-scan of the controller program on the transition to Run mode. Again, for example, the handling of

indirect addressing that has gone out of range.

There is an anomaly when these methods attempt to handle a fault.

These are the possible ways the anomaly can manifest itself:

• The controller will experience a major non-recoverable fault. I/O goes to their configured safe state, and the user application is cleared from memory. At

this point, a Code 1 Type 60 or 61 major recoverable fault will be logged in the controller. This requires you to redownload the application.

• Tag data corruption.

• Online saving or uploading failures.

• Anomalous program execution.

For example, if a rung is being scanned false and there is an instruction that has false execution, the fault handler executes so the remainder of the rung

will scan true. In the example below, the OTE instruction has an index out of range. After returning from the fault handler, the ADD instruction will execute,

even though the rung input conditions are false.

MDB03-2D20-T

DSDO115A

25-120-000735

TP188M

DI821 3BSE008550R1

INNPM12

DS200ADGIH1AAA

3HAC17346-1/01

CC-PCNTOX

3HAC024144-001

IC754CSL12CTD

IC670PBI001

RELIANCEUAZ3455/3475

UR6EV

UCD240A101

DSDP140B

5SGY35L4510

07KR31

UR6DH

015-0407-00

H14-88

IC698CRE040

NU8976A99

14-50-2UH

216VC62A

SB822

64711245C

CP-40A-33-F002B-SP

CSF-14-50-GH-J2BAD

IC660BBD022

GEN300/GEN04

HE693THM884M

RELIANCE0-57C402-C

MSR04X1

DSPC172

CI867K01

AplhaTP50

DASA110

RMIO-01C