1756-RD001B-EN-P

Logix 5000 Controller and I/O Fault Codes and Syslog Messages

About This Publication This publication lists the fault codes for Logix 5000™ controllers and the syslog messages for ControlLogix® 5580 controllers and 1756-EN4TR
communication modules.
For more information, see the following resources:
Logix 5000 Controllers Major, Minor, and I/O Faults Programming Manual 1756-PM014
ControlLogix 5580 and GuardLogix 5580 Controllers User Manual 1756-UM543
CompactLogix 5380 and Compact GuardLogix 5380 Controllers User Manual 5069-UM001

CompactLogix 5480 Controllers User Manual 5069-UM002

Important: Rockwell Automation is not responsible for any content or format changes made by other parties after downloading this spreadsheet file. The original file can be re-downloaded at any time.

TIP: When you search for information in a spreadsheet, set the search options to search the workbook, rather than the current sheet (tab).

Your comments help us serve your documentation needs better. If you have any suggestions on how to improve our content, complete the form at: rok.auto/docfeedback

Allen-Bradley, Compact I/O, CompactLogix, ControlLogix, ControlBus, DriveGuard, expanding human possibility, GuardLogix, GuardMotion, DH+, FLEX, Logix 5000, PLC-5, POINTBus, POINT I/O, Rockwell Automation, RSLinx,
RSLogix 5000, RsNetWorx, and Studio 5000 Logix Designer are trademarks of Rockwell Automation, Inc.
CIP, CIP Motion, CIP Sync, ControlNet, and EtherNet/IP are trademarks of ODVA, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.

1756-RD001C-EN-P - April 2022 Copyright © 2022 Rockwell Automation Inc. All Rights Reserved. Printed in USA.
Supersedes Publication 1756-RD001D-EN-P - March 2022
Summary of Changes

Date Changes

November 2022 • Added safety fault codes

• Added Logix 5000 controller Minor Fault Type 19 Code 1
• Added Logix 5000 controller Minor Fault Type 19 Code 2
• Added Logix 5000 controller Minor Fault Type 19 Code 3
• Revised Logix 5000 controller Major Fault Type 14
• Added CIP Security I/O fault codes

September 2022 • Added syslog messages

• Added Logix 5000 controller Minor Fault Type 19 Code 4
• Added link to 1756-PM014 to the Introduction Tab
• Added link to the Documentation Feeback Form to the Introduction Tab

March 2022 • Added Logix 5000 controller Major Fault Type 3 Code 32
• Added Logix 5000 controller Minor Fault Type 3 Code 94
• Added I/O faults Fault Code 0x0817

August 2021 First release as an Excel spreadsheet

Rockwell Automation recognizes that some of the terms that are currently used in our industry and in this publication are not in alignment
with the movement toward inclusive language in technology. We are proactively collaborating with industry peers to find alternatives to
such terms and making changes to our products and content. Please excuse the use of such terms in our content while we implement
these changes.
 A B C D E F G
1
2 Logix 5000™ Controller and I/O Fault Codes
3
4 For more information, see the following resource:
5 Logix 5000 Controllers Major, Minor, and I\O Faults Programming Manual, 1756-PM014
6
Fault Type Fault Code Studio 5000 Logix Designer® Application Fault Corrective Action Major/Minor Fault Type Name
7 Display Text
1 1 Major Fault T01:C01 - Power-up Fault: Power The controller that is powered on is in Run mode. Execute the power-up handler. Major Power Up
8 lost and restored in RUN mode.
1 2 Minor Fault T01:C02 - Power-up Fault: AC AC power loss detected. Chassis active until DC power cannot be Legacy. Now an unused fault code. Minor Power Up
9 power loss detected. Chassis active until DC maintained.
power cannot be maintained.
1 15 Minor Fault T01:C15 - Power-up Fault: I/O A 1769 power supply is connected directly to the controller’s 1768 Remove the power supply from the 1768 CompactBus and cycle power to Minor Power Up
Power fault detected. CompactBus with an invalid configuration. the system.
10 The 1768 power supply that provides power to the controller has failed. Replace the power supply.

1 16 Major Fault T01:C16 - Power-up Fault: I/O I/O communication configuration fault detected. (CompactLogix™ 1768- Reconfigure the number of communication modules on the 1768 bus side Major Power-up
Communications Configuration fault detected. L4x controllers only.) of the controller:
• 1768-L43 has a maximum of two modules.
•1768-L45 has a maximum of four modules.
11
• Up to four Sercos modules
• Up to two NetLinx communication modules

1 29 Minor Fault T01:C29 - Power-up Fault: Voltage Voltage has exceeded operating limits. Legacy. Now an unused fault code. Minor Power Up
12 has exceeded operating limits.
1 40 Major Fault T01:C40 - Power-up Fault: Energy If the controller uses a battery, the battery does not contain enough For controllers that use a battery, replace the battery. Major Power Up
Storage Module/Battery failed during power charge to save the user program on power-down. For controllers that use an ESM (Energy Storage Module):
down. • Allow the ESM to charge fully before powering down the controller.
If the controller uses an ESM (Energy Storage Module), the ESM does not • Replace the ESM if the ESM is removable, or replace the controller if the
13
contain enough charge to save the user program on power-down. ESM is not removable.
If the problem persists, contact Rockwell Automation support.

1 60 Major Fault T01:C60 - Power-up Fault: Non- For a controller with no memory card installed, the controller: 1. Clear the fault. Major Power Up
recoverable Fault. - Detected a nonrecoverable fault. 2. Download the project.
- Cleared the project from memory. 3. Change to Remote Run or Run mode.

Follow these steps if the fault persists.

14 1. Before you cycle power to the controller, record the state of the OK and
RS-232 status indicators.
2. Contact Rockwell Automation support.

1 61 Major Fault T01:C61 - Power-up Fault: Non- For a controller with a memory card installed, the controller: 1. Clear the fault. Major Power Up
recoverable Fault with saved Diagnostic • Detected a nonrecoverable fault. 2. Download the project.
15 Information. • Wrote diagnostic information to the memory card. 3. Change to Remote Run or Run mode.
• Cleared the project from memory. If the fault persists, contact Rockwell Automation support.

1 62 Major Fault T01:C62 - Power-up Fault: Non- For a controller with a Secure Digital (SD) card installed, the controller: 1. Clear the fault. Major Power Up
recoverable Fault with saved diagnostic • Detected a nonrecoverable fault. 2. Download the project.
16 information and stored user program. • Wrote diagnostic information to the memory card. 3. Change to Remote Run or Run mode.
If the fault persists, contact Rockwell Automation support.
When in this state, the controller does not open any connections or allow
a transition to Run mode.
3 0 Minor Fault T3:C0 - I/O Fault: Compact I/O end Compact I/O™ end cap missing. Install the end cap. Minor I/O
17 cap missing.
3 1 Minor Fault T03:C01 - I/O Fault: PointBus POINTBus™ backplane bus off condition. The connections between the Complete these steps to identify the source of the BUS OFF fault: Minor I/O
backplane bus off. controller and the I/O modules are broken. 1. The number of local expansion modules in the project matches the
number of modules that are physically installed in the system.
2. All mounting bases are locked and I/O modules are securely installed on
mounting bases.
3. All 1734 POINT I/O™ modules are configured to use the Autobaud rate.
18
If these steps do not remedy the fault condition, contact Rockwell
Automation support.

3 16 Major Fault T03:C16 - I/O Fault: I/O module A required I/O module connection failed. Verify the following: Major I/O
connection failed on required module. • I/O module is in the chassis.
• Electronic keying requirements.
19 • Controller Properties Major Fault tab and the Module Properties
Connection tab for more information about the fault.

3 20 Major Fault T03:C20 - I/O Fault: Unable to read Possible fault with the chassis. Not recoverable. Replace the chassis. Major I/O
20 ControlBus™ chassis information. Chassis may
be bad.
3 21 Major Fault T03:C21 - I/O Fault: Unable to read Possible fault with the chassis. Not recoverable. Replace the chassis. Major I/O
21
ControlBus chassis information. Chassis may
be bad.

3 23 Major Fault T03:C23 - I/O Fault: At least one At least one required connection was not established before going to Run Wait for the controller I/O light to turn green before changing to Run mode. Major I/O
required connection not established before mode.
22 going into RUN mode.

3 32 Major Fault T03:C32 - I/O Fault: Controller The controller failed to open an I/O connection to a fault-tolerant I/O • Make sure that the redundancy module is correctly inserted and Major I/O
failed to open an I/O connection to a fault- module because its partner controller is in a Primary state. connected.
23 tolerant I/O module because its partner • Synchronize the redundancy controllers so that only one controller is in
controller is in a Primary state. the Primary state.
 A B C D E F G
3 94 Minor Fault T03:C94 - I/O Fault: Module RPI The current RPI update of an I/O module overlaps with its previous RPI Set the RPI rate of the I/O modules to a higher numerical value. Rockwell Minor I/O
overlap detected. update. Automation recommends that the CompactLogix™ 5370 L2 and
24 CompactLogix 5370 L3 control systems do not run with Module RPI Overlap
faults.

3 100 Minor Fault T03:C100 - I/O Fault: I/O module The I/O module does not support data integrity. Legacy. Now an unused fault code. Minor I/O
does not support data integrity.
25

4 4 Minor Fault T04:C04 - Program Fault: The result of an arithmetic operation is out of range. Examine the arithmetic operations (order) or adjust the values. Minor Program
26 Arithmetic overflow. Result of an arithmetic
instruction out of range.
4 5 Minor Fault T04:C05 - Program Fault: GSV/SSV In a GSV/SSV instruction, the specified instance was not found. Check the instance name. Minor Program
27 object address invalid.
4 6 Minor Fault T04:C06 - Program Fault: GSV/SSV In a GSV/SSV instruction, either the: Check the Class name and Attribute name. Minor Program
28 operand invalid. • Specified Class name is not supported.
• Specified Attribute name is not valid.
4 7 Minor Fault T04:C07 - Program Fault: GSV/SSV The GSV/SSV destination tag was too small to hold the data. Fix the destination so it has enough space. Minor Program
29 destination tag too small to hold all data.

4 16 Major Fault T04:C16 - Program Fault: Unknown Unknown instruction encountered. Remove the unknown instruction. This probably happened due to a Major Program
30 instruction encountered. program conversion process.
4 20 Major Fault T04:C20 - Program Fault: Array The array subscript is too large or the control data type .POS or .LEN Adjust the value to be within the valid range. Do not exceed the array size Major Program
31 subscript too large, or CONTROL data type POS value is invalid. or go beyond the dimensions defined.
or LEN invalid.
4 21 Major Fault T04:C21 - Program Fault: Control structure .LEN or .POS < 0. Adjust the value so it is > 0. Major Program
32 CONTROL data type LEN or POS less than 0.
4 24 Major Fault T04:C24 - Program Fault: Unknown Unknown data type passed to subroutine. Legacy. Now an unused fault code. Major Program
33 data type passed to subroutine.
4 30 Minor Fault T04:C30 - Program Fault: ASCII An ASCII instruction failed. Bad parameters passed through to the ASCII Verify the ASCII configuration settings. Minor Program
34 instruction failed. port.
4 31 Major Fault T04:C31 - Program Fault: JSR or The parameters of the JSR instruction do not match those of the Pass the appropriate number of parameters. If you pass too many Major Program
35 RET did not pass as many parameters as associated SBR or RET instruction. parameters, the extra ones are ignored without any error.
expected.
4 32 Minor Fault T04:C32 - Program Fault: Routine Routine type not supported. Legacy. Now an unused fault code. Minor Program
36 type not supported.
4 34 Major Fault T04:C34 - Program Fault: A timer A timer instruction has a negative preset or accumulated value. Fix the program so that it cannot load a negative value into the timer preset Major Program
37 instruction had a negative value for its PRE or or accumulated value.
ACC.
38 4 35 PID delta time was less than 0. PID delta time less than zero. Adjust the PID delta time so that it is > 0. Minor Program
39 4 36 PID setpoint out of range for target module. PID setpoint out of range. Adjust the setpoint so that it is within range. Minor Program
4 42 Major Fault T04:C42 - Program Fault: JMP to a JMP to a label that did not exist or was deleted. Correct the JMP target or add the missing label. Major Program
40 label that did not exist or was deleted.
4 51 Minor Fault T04:C51 - Program Fault: LEN The .LEN value of the string tag is greater than the DATA size of the string 1. Check that no instruction is writing to the LEN member of the string tag. Minor Program
value outside DATA limit. tag. 2. In the LEN value, enter the number of characters that the string contains.
41

4 52 Minor Fault T04:C52 - Program Fault: Defined The output string is larger than the destination. Create a string data type that is large enough for the output string. Use the Minor Program
42 string size is invalid. new string data type as the data type for the destination.

4 53 Minor Fault T04:C53 - Program Fault: Numeric The output number is beyond the limits of the destination data type. Either: Minor Program
43 result cannot fit in destination. • Reduce the size of the ASCII value.
• Use a larger data type for the destination.
4 54 Minor Fault T04:C54 - Program Fault: BufferSize value reduced amount of data. Legacy. Now an unused fault code. Minor Program
44 BufferSize value reduced amount of data.
4 55 Minor Fault T04:C55 - Program Fault: SerialPort Control .LEN value was incorrect. Legacy. Now an unused fault code. Minor Program
45 SerialPort Control Len value was incorrect.
4 56 Minor Fault T04:C56 - Program Fault: Invalid The Start or Quantity value is invalid. Check the following: Minor Program
Start and/or Quantity value. • The Start value is between 1 and the DATA size of the Source.
46 • The Start value plus the Quantity Value is less than or equal to the DATA
size of the Source.

4 57 Minor Fault T04:C57 - Program Fault: Cannot The AHL instruction failed to execute because the serial port is set to no Either: Minor Program
47 execute AHL when SerialPort set to handshaking. • Change the Control Line setting of the serial port.
NoHandshaking. • Delete the AHL instruction.
4 82 Major Fault T04:C82 - Program Fault: Could A sequential function chart (SFC) called a subroutine and the subroutine Remove the jump back to the calling SFC. Major Program
48 not re-enter an executing SFC routine. tried to jump back to the calling SFC. This occurs when the SFC uses
either a JSR or FOR instruction to call the subroutine.
4 83 Major Fault T04:C83 - Program Fault: Value out The data tested was not inside the required limits. This occurs with array Adjust the value to be within the valid range. Do not exceed the array size Major Program
49 of range. subscripts used with Boolean arrays and bit level addressing. or go beyond the dimensions defined.
4 84 Major Fault T04:C84 - Program Fault: Stack Stack overflow. Reduce the subroutine-nesting levels or the number of parameters passed. Major Program
50 overflow. Stack too small to perform
operation.
4 85 Major Fault T04:C85 - Program Fault: Invalid Invalid routine type. Use a valid routine type. Major Program
51 routine type.
4 86 Minor Fault T04:C86 - Program Fault: Access Access violation in user program. Contact Rockwell Automation Technical Support. Minor Program
52 violation in user program.
4 87 Minor Fault T04:C87 - Program Fault: External External routine DLL load failed. DLL missing or malformed. Confirm and adjust. Minor Program
routine DLL load failed. Perhaps a DLL on
53 which it depends is missing.

4 88 Minor Fault T04:C88 - Program Fault: Exception in external routine DLL. Troubleshoot the external routine DLL. Minor Program
54 Exception in external routine DLL.
4 89 Major Fault T04:C89 - Program Fault: Target In an SFR instruction, the target routine does not contain the target step. Correct the SFR target or add the missing step. Major Program
55 step does not exist in specified routine.
 A B C D E F G
4 90 Major Fault T04:C90 - Program Fault: A safety A safety instruction occured outside a safety task. Only use the instruction in a safety task. Major Program
56 instruction occurs outside a safety task.

4 91 Major Fault T04:C91 - Program Fault: Equipment Phase instruction is being called from outside an Equipment Only use the instruction in an Equipment Phase program. Major Program
57 Equipment phase instruction cannot be called Phase program.
from a program.
4 94 Major Fault T04:C94 - Program Fault: Nesting Nesting limits exceeded. Restructure the project to reduce the subroutine-nesting levels. Major Program
58 limits exceeded.
4 990 Major Fault T04:C990 - Program Fault: User- User-defined major fault. User-defined action. Major Program
59 defined fault.
4 991 Major Fault T04:C991 - Program Fault: User- User-defined major fault. User-defined action. Major Program
60 defined fault.
4 992 Major Fault T04:C992 - Program Fault: User- User-defined major fault. User-defined action. Major Program
61 defined fault.
4 993 Major Fault T04:C993 - Program Fault: User- User-defined major fault. User-defined action. Major Program
62 defined fault.
4 994 Major Fault T04:C994 - Program Fault: User- User-defined major fault. User-defined action. Major Program
63 defined fault.
4 995 Major Fault T04:C995 - Program Fault: User- User-defined major fault. User-defined action. Major Program
64 defined fault.
4 996 Major Fault T04:C996 - Program Fault: User- User-defined major fault. User-defined action. Major Program
65 defined fault.
4 997 Major Fault T04:C997 - Program Fault: User- User-defined major fault. User-defined action. Major Program
66 defined fault.
4 998 Major Fault T04:C998 - Program Fault: User- User-defined major fault. User-defined action. Major Program
67 defined fault.
4 999 Major Fault T04:C999 - Program Fault: User- User-defined major fault. User-defined action. Major Program
68 defined fault.
6 1 Major Fault T06:C01 - Watchdog Fault: Task User task has not completed in the specified period. A program error Take one or more of these steps: Major Watchdog
watchdog expired. May have been caused by caused an infinite loop, or the program is too complex to run as quickly as • Increase the task watchdog.
an infinite loop, a complex program, or a specified, or a higher priority task is keeping this task from finishing. • Shorten the execution time.
69 higher priority task. • Make the priority of this task higher.
• Simplify higher priority tasks.
• Move some code to another controller.

6 2 Minor Fault T06:C02 - Watchdog Fault: Periodic task overlap. Make changes, such as simplify programs, lengthen the period, or raise the Minor Watchdog
70 Periodic task overlap. Task scheduled again The task was scheduled again before it finished executing. relative priority.
before it finished executing.
6 3 Minor Fault T06:C03 - Watchdog Fault: Event Event task overlap. Make changes such as simplify programs, lengthen the period, raise the Minor Watchdog
71 task overlap. Task triggered again before it The task triggered again before it finished executing. relative priority, or slow the triggering event.
finished executing.
7 40 Major Fault T07:C40 - Nonvolatile Fault: Store Store to nonvolatile memory failed. 1. Try again to store the project to nonvolatile memory. Major Flash Save
to nonvolatile memory failed. 2. If the project fails to store to nonvolatile memory, replace the memory
72 card. If you are using a 1756-L7x controller, verify that the SD card is
unlocked.

7 41 Major Fault T07:C41 - Nonvolatile Fault: Load Load from nonvolatile memory failed due to controller type mismatch. Change to a controller of the correct type or download the project and Major Flash Save
73 from nonvolatile memory failed due to store it on the memory card.
controller type mismatch.
7 42 Major Fault T07:C42 - Nonvolatile Fault: Load Load from nonvolatile memory failed because the firmware revision of Update the controller firmware to the same revision level as the project Major Flash Save
74 from nonvolatile memory failed due to the project in nonvolatile memory does not match the firmware revision that is in nonvolatile memory.
controller revision mismatch. of the controller.
7 43 Major Fault T07:C43 - Nonvolatile Fault: Load Load from nonvolatile memory failed due to bad checksum. Contact Rockwell Automation support. Major Flash Save
75 from nonvolatile memory failed due to bad
checksum.
7 44 Major Fault T07:C44 - Nonvolatile Fault: Failed Failed to restore controller memory. Contact Rockwell Automation support. Major Flash Save
76 to restore processor memory.
7 49 Minor Fault T07:C49 - Nonvolatile Fault: When the controller loads a project from nonvolatile memory, it logs this Clear the fault. Minor Flash Save
77 Controller was loaded from nonvolatile minor fault and sets the FaultLog object, MinorFaultBits attribute, bit 7.
memory.
7 50 Major Fault T07:C50 - Nonvolatile Fault: The log file certificate cannot be verified. When the controller starts up, it Clear the fault and power cycle the controller. If the problem persists, Major Flash Save
Security certificate invalid. attempts to verify the log file key/certificate combination. Depending on contact Rockwell Automation support.
the verification, the controller takes one of the following actions:
• If the controller verifies the existing log file certificate, the controller
continues with the existing log directory.
• If the existing certificate cannot be verified, the controller logs a major
fault and attempts to create a new certificate.
• If the controller successfully creates a certificate, it creates a backup log
subdirectory, moves the existing files to that directory, and continues
78 logging and signing with the new verification key and log file certificate.
• If the controller cannot create a certificate, the controller writes log
entries to the existing log directory, but does not update signature files in
that directory.

8 1 Major Fault T8:C1 - Mode Change Fault: Mode Attempted to place controller in Run mode with keyswitch during Wait for the download to complete and clear the fault. Major Mode Change
79 Change inhibited due to download in progress. download.

9 0 Minor Fault T09:C00 - Serial Port Fault: Unknown error while servicing the serial port. Contact Rockwell Automation Technical Support. Minor Serial Port
80 Unknown error while servicing serial port.
9 1 Minor Fault T09:C01 - Serial Port Fault: The CTS line is not correct for the current configuration. Disconnect and reconnect the serial port cable to the controller. Make sure Minor Serial Port
81 Problem with hardware control lines. that the cable is wired correctly.
 A B C D E F G
9 2 Minor Fault T09:C02 - Serial Port Fault: Poll list error. Check for the following errors in the poll list. Minor Serial Port
Contents of poll list tag incorrect. A fault was detected with the DF1 master’s poll list, such as specifying - Total number of stations is greater than the space in the poll list tag.
more stations than the size of the file, specifying more than 255 stations, - Total number of stations is greater than 255.
82 trying to index past the end of the list, or polling the broadcast address - Current station pointer is greater than the end of the poll list tag.
(STN #255). - A station number greater than 254 was encountered.

9 3 Minor Fault T09:C03 - Serial Port Fault: Master The RS-232 DFI Master Active Station tag is unspecified. Specify a tag to be used for the Active Station Tag in the System Protocol Minor Serial Port
83 protocol missing Active Station File. tab of the Controller Properties.
9 5 Minor Fault T09:C05 - Serial Port Fault: DF1 DF1 slave poll timeout. Determine and correct delay for polling. Minor Serial Port
84 slave poll timeout. The poll watchdog has timed out for slave. The master has not polled this
controller in the specified amount of time.
9 9 Minor Fault T09:C09 - Serial Port Fault: Modem contact lost. Correct modem connection to the controller. Minor Serial Port
85 Modem contact lost. DCD or DSR control lines are not being received in proper sequence or
state.
9 10 Minor Fault T09:C10 - Serial Port Fault: Serial Data has been dropped or lost from the serial port. Slow down the rate at which the initiator is sending data. Minor Serial Port
86 Port is unable to keep up with incoming data.
9 11 Minor Fault T09:C11 - Serial Port Fault: ACL A channel operand in an ACL instruction channel is not a valid port. Correct the channel specified in the ACL instruction. Minor Serial Port
87 instruction channel operand is not a valid port.

10 10 Minor Fault T10:C10 - Battery Fault: Battery The battery is missing or must be replaced. Install a new battery. Minor Battery
88 missing or needs to be replaced.
10 11 Minor Fault T10:C11 - Battery Fault: Safety The battery for the safety partner is missing or must be replaced. Install a new battery. Minor Battery
89 partner battery missing or needs to be
replaced.
10 12 Minor Fault T10:C12 - Energy Storage Fault: The energy storage module is not installed. Install an ESM in the controller. Minor Battery
90 Energy Storage Module not present. If the controller is powered-down, the WallClockTime attribute and
program are not maintained.
10 13 Minor Fault T10:C13 - Energy Storage Fault: The installed energy storage module is not compatible with the Replace the installed ESM with one that is compatible with the controller. Minor Battery
91 Energy Storage Module incompatible with controller.
controller type.
10 14 Minor Fault T10:C14 - Energy Storage Fault: The energy storage module must be replaced due to a hardware fault. Replace the ESM. Minor Battery
Energy Storage Module hardware failure. It is not capable of maintaining the WallClockTime attribute or controller
92 program at power down.

10 15 Minor Fault T10:C15 - Energy Storage Fault: The energy storage module cannot store enough energy to maintain the Replace the ESM. Minor Battery
93 Energy Storage Module energy low. WallClockTime attribute or the controller program at power-down.

10 16 Minor Fault T10:C16 - UPS Fault: UPS missing The uninterruptible power supply is missing or not ready. Either: Minor Battery
or not ready. • Install the UPS.
94 • Check the UPS to make sure it is adequately charged to provide backup
power if there is a power loss.

10 17 Minor Fault T10:C17 - UPS Fault: UPS battery The uninterruptible power supply battery has failed and must be Replace the battery in the UPS. Minor Battery
95 failure. replaced.
11 1 Major Fault T11:C01 - Motion Fault: Actual Actual position of the axis has exceeded the positive overtravel limit. Move axis in negative direction until position is within overtravel limit and Major Motion
96 position of axis exceeded positive overtravel then execute Motion Axis Fault Reset.
limit.
11 2 Major Fault T11:C02 - Motion Fault: Actual Actual position of the axis has exceeded the negative overtravel limit. Move axis in positive direction until position is within overtravel limit and Major Motion
97 position of axis exceeded negative overtravel then run Motion Axis Fault Reset.
limit.
11 3 Major Fault T11:C03 - Motion Fault: Actual Actual position the axis has exceeded the position error tolerance. Move the position within tolerance, then run Motion Axis Fault Reset. Major Motion
98 position exceeded position error tolerance.
11 4 Major Fault T11:C04 - Motion Fault: Encode Encoder channel A, B, or Z connection is broken. Reconnect the encoder channel, then run Motion Axis Fault Reset. Major Motion
99 channel A, B, or Z connection failed.
11 5 Major Fault T11:C05 - Motion Fault: Encoder Encoder noise event detected or the encoder signals are not in the Fix encoder cabling, then run Motion Axis Fault Reset. Major Motion
100 noise event detected, or encoder signals not in quadrature.
quadrature.
11 6 Major Fault T11:C06 - Motion Fault: Drive Drive fault detected. Clear Drive Fault then run Motion Axis Fault Reset. Major Motion
101 fault.
11 7 Major Fault T11:C07 - Motion Fault: Synchronous connection to the servo module failed. Try these steps: Major Motion
Synchronous connection to servo module 1. First, run Motion Axis Fault Reset.
102 failed. 2. If that does not work, pull out the servo module and plug it back in.
3. If this does not work, replace the servo module.

11 8 Major Fault T11:C08 - Motion Fault: Hardware Hardware failure detected in the servo module. Replace the module. Major Motion
103 failure in servo module.
11 9 Major Fault T11:C09 - Motion Fault: Asynchronous connection to the servo module failed. Try these steps: Major Motion
Asynchronous connection to servo module 1. First, run Motion Axis Fault Reset.
104 failed. 2. If that does not work, pull out the servo module and plug it back in.
3. If this does not work, replace the servo module.

11 10 Major Fault T11:C10 - Motion Fault: Motor Motor fault detected. See the DriveFaults axis tag for more information. Major Motion
105 fault detected.
11 11 Major Fault T11:C11 - Motion Fault: Motor Motor thermal fault detected. See the DriveFaults axis tag for more information. Major Motion
106 thermal fault detected.
11 12 Major Fault T11:C12 - Motion Fault: Drive Drive thermal fault detected. See the DriveFaults axis tag for more information. Major Motion
107 thermal fault detected.
11 13 Major Fault T11:C13 - Motion Fault: SERCOS SERCOS communication fault detected. Verify the integrity of the SERCOS fiber-optic ring network and the devices Major Motion
108 comm fault detected. on it.
11 14 Major Fault T11:C14 - Motion Fault: Drive Drive enable input was inactive during an attempt to enable the drive or Re-enable the drive enable input and clear the fault. Major Motion
Enable Input 1) was inactive prior during an transitioned to inactive while the drive was enabled.
attempt to enable the drive, or 2) transitioned
109 to inactive while the drive was enabled.
 A B C D E F G
11 15 Major Fault T11:C15 - Motion Fault: Drive Drive phase loss fault detected. Restore full power connection to the drive and clear the fault. Major Motion
110 Phase Loss fault detected.
11 16 Major Fault T11:C16 - Motion Fault: A Guard DriveGuard® fault detected. See the GuardFaults axis tag for more information. Major Motion
111 Fault has been detected by the drive.
11 32 Major Fault T11:C32 - Motion Fault: Motion The motion task experienced an overlap. The coarse update rate is too The group’s course update rate is too high to maintain correct operation. Major Motion
112 Task overlap. Coarse update rate too high. high. Clear the group fault tag, raise the group’s update rate, and then clear the
major fault.
11 33 Major Fault T11:C33 - Motion Fault: Coordinated System Time reference has been lost. Check the condition of the CST master in the backplane. Major Motion
113 Coordinated System Time reference has been
lost.
12 32 Major Fault T12:C32 - Safety Fault: Disqualified A disqualified secondary controller cycled power and no partner chassis Verify the following items. Major Redundancy
secondary became primary. or controller was found upon power-up. • A partner chassis is connected.
• Power is applied to both redundant chassis.
114 • Partner controllers have the same catalog number, slot number, and
firmware revision.

12 33 Major Fault T12:C33 - Safety Fault: No partner An unpartnered controller has been identified in the new primary chassis Either: Major Redundancy
found after switchover. after a switchover. • Remove the unpartnered controller and troubleshoot the cause of the
switch over.
115 • Add a partner controller to the secondary chassis, troubleshoot the cause
of the switch over, and synchronize the system.

12 34 Major Fault T12:C34 - Safety Fault: Keyswitch Just after a switchover occurs, the keyswitch positions of the primary and Either: Major Redundancy
Positions of Primary and Secondary Controllers secondary controllers are mismatched. • Change the keyswitches from Run to Program to Run mode twice to clear
Mismatched The old primary controller is in Program mode and the new primary the fault.
116 controller is in Run mode. • Use the Logix Designer application to go online with the controllers. Then,
clear the faults and change both the controller's mode to Run.

13 21 Minor Fault T13:C21 - Real Time Clock Fault: The WallClockTime is out of range. Verify the WallClockTime is set to the correct date/time. Minor Real Time Clock
117 Wall Clock Time out of range.
14 1 Major Fault T14:C01 - Safety Task Fault: Task The task watchdog expired because of these reasons: For ControlLogix 5580 and Compact GuardLogix 5380 controllers: Major Safety
watchdog expired. May have been caused by • The user task did not complete in a specified period of time. Clear the fault.
infinite loop, complex program, higher priority • A program error caused an infinite loop. Safety memory is reinitialized and the safety task begins executing.
task, or removal of Safety partner. • The program is too complex to execute as quickly as specified. Reinsert the safety partner if it was removed.
• A higher priority task is keeping this task from finishing.
• The safety partner has been removed. For ControlLogix 5570 and Compact GuardLogix 5370 controllers:
Clear the fault.
118 If a safety task signature exists, safety memory is reinitialized and the safety
task begins executing.
If a safety task signature does not exist, you must redownload the program
to allow the safety task to run.
Reinsert the safety partner if it was removed.

14 2 Major Fault T14:C02 - Safety Task Fault: An An error exists in a routine of the safety task. Correct the error in the user-program logic. Major Safety
119 error exists in a routine of the Safety task.
14 3 Major Fault T14:C03 - Safety Task Fault: Safety The safety partner is missing. Install a compatible safety partner and clear the fault. A download may be Major Safety
120 partner is missing. required.

14 4 Major Fault T14:C04 - Safety Task Fault: Safety The safety partner is unavailable. Install a compatible safety partner and clear the fault. A download may be Major Safety
121 partner is unavailable. required.

14 5 Major Fault T14:C05 - Safety Task Fault: Safety The safety partner hardware is incompatible. Install a compatible safety partner and clear the fault. A download may be Major Safety
122 partner hardware is incompatible. required.

14 6 Major Fault T14:C06 - Safety Task Fault: Safety The safety partner firmware is incompatible. Update the safety partner so that the firmware major and minor revision Major Safety
123 partner firmware is incompatible. matches the primary controller. A download may be required.

14 7 Major Fault T14:C07 - Safety Task Fault: Safety The safety task is inoperable. This fault occurs when the safety logic is For ControlLogix 5580 and Compact GuardLogix 5380 controllers: Major Safety
task is inoperable. invalid, such as for these reasons: Clear the fault.
• A mismatch in logic exists between the primary controller and safety Download the application.
partners.
• A watchdog timeout occurs. For ControlLogix 5570 and Compact GuardLogix 5370 controllers:
• Memory is corrupt. Clear the fault.
If a safety task signature exists, safety memory is reinitialized via the safety
task signature and the safety task begins executing.
124
If a safety task signature does not exist, you must download the program
again to allow the safety task to run.

14 8 Major Fault T14:C08 - Safety Task Fault: Safety (ControlLogix 5570 controllers only). Coordinated system time (CST) not For ControlLogix 5570 and Compact GuardLogix 5370 controllers: Major Safety
125 partner's time is not synchronized with found. The safety partner's time is not synchronized with the primary. Clear the fault. Configure a device to be the CST master.
primary.
14 9 Major Fault T14:C09 - Safety Task Fault: A non- The safety partner has a nonrecoverable controller fault. Clear the fault and download the application. If the problem persists, Major Safety
126 recoverable fault has occurred in Safety replace the safety partner.
Partner.
14 12 Minor Fault T14:C12 - Safety Fault: Safety (ControlLogix 5580 controllers only). The safety partner detected when For ControlLogix 5580 and Compact GuardLogix 5380 controllers: Minor Safety
partner detected when the project safety level the project safety level is SIL2/PLd. If your desired safety level is SIL2/PLd, remove the safety partner (since it
is SIL2/PLd. does not participate in a SIL2/PLd configuration).
If your desired safety level is SIL3/PLe, change the project safety level to
127 SIL3/PLe.
 A B C D E F G
17 0 Minor Fault T17:C00 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
128 contact technical support with the fault type
and fault code.

17 1 Minor Fault T17:C01 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
129 contact technical support with the fault type
and fault code.

17 2 Minor Fault T17:C02 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
130 contact technical support with the fault type
and fault code.

17 3 Minor Fault T17:C03 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
131 contact technical support with the fault type
and fault code.

17 4 Minor Fault T17:C04 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
132 contact technical support with the fault type
and fault code.

17 5 Minor Fault T17:C05 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
133 contact technical support with the fault type
and fault code.

17 6 Minor Fault T17:C06 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
134 contact technical support with the fault type
and fault code.

17 7 Minor Fault T17:C07 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
135 contact technical support with the fault type
and fault code.

17 8 Minor Fault T17:C08 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
136 contact technical support with the fault type
and fault code.

17 9 Minor Fault T17:C09 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
137 contact technical support with the fault type
and fault code.

17 10 Minor Fault T17:C10 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
138 contact technical support with the fault type
and fault code.

17 11 Minor Fault T17:C11 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
139 contact technical support with the fault type
and fault code.

17 12 Minor Fault T17:C12 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
140 contact technical support with the fault type
and fault code.

17 13 Minor Fault T17:C13 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
141 contact technical support with the fault type
and fault code.

17 14 Minor Fault T17:C14 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
142 contact technical support with the fault type
and fault code.

17 15 Minor Fault T17:C15 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
143 contact technical support with the fault type
and fault code.

17 16 Minor Fault T17:C16 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
144 contact technical support with the fault type
and fault code.

17 17 Minor Fault T17:C17 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
145 contact technical support with the fault type
and fault code.

17 18 Minor Fault T17:C18 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
146 contact technical support with the fault type
and fault code.

17 19 Minor Fault T17:C19 - Diagnostic Fault: A An internal controller diagnostic failed. Upload and save program before Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please controller is powered down. fault code logged.
147 contact technical support with the fault type
and fault code.
 A B C D E F G
17 20 Minor Fault T17:C20 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
148 contact technical support with the fault type
and fault code.

17 21 Minor Fault T17:C21 - Diagnostic Fault: A An internal controller diagnostic failed. Upload and save program before Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please the controller is powered down. fault code logged.
149 contact technical support with the fault type
and fault code.

17 22 Minor Fault T17:C22 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
150 contact technical support with the fault type
and fault code.

17 23 Minor Fault T17:C23 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
151 contact technical support with the fault type
and fault code.

17 24 Minor Fault T17:C24 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
152 contact technical support with the fault type
and fault code.

17 25 Minor Fault T17:C25 - Diagnostic Fault: A An internal controller diagnostic failed. Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please fault code logged.
153 contact technical support with the fault type
and fault code.

17 26 Minor Fault T17:C26 - Diagnostic Fault: A An internal controller diagnostic failed. Upload and save program before Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please the controller is powered down. fault code logged.
154 contact technical support with the fault type
and fault code.

17 27 Minor Fault T17:C27 - Diagnostic Fault: A An internal controller diagnostic failed. Upload and save program before Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please the controller is powered down. fault code logged.
155 contact technical support with the fault type
and fault code.

17 28 Minor Fault T17:C28 - Diagnostic Fault: A An internal controller diagnostic failed. Upload and save program before Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please the controller is powered down. fault code logged.
156 contact technical support with the fault type
and fault code.

17 29 Minor Fault T17:C29 - Diagnostic Fault: A An internal controller diagnostic failed. Upload and save program before Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please the controller is powered down. fault code logged.
157 contact technical support with the fault type
and fault code.

17 30 Minor Fault T17:C30 - Diagnostic Fault: A An internal controller diagnostic failed. Upload and save program before Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please the controller is powered down. fault code logged.
158 contact technical support with the fault type
and fault code.

17 31 Minor Fault T17:C31 - Diagnostic Fault: A An internal controller diagnostic failed. Upload and save program Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please beforethe controller is powered down. fault code logged.
159 contact technical support with the fault type
and fault code.

17 32 Minor Fault T17:C31 - Diagnostic Fault: A An internal controller diagnostic failed. Upload and save program before Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please the controller is powered down. fault code logged.
160 contact technical support with the fault type
and fault code.

17 33 Minor Fault T17:C33 - Diagnostic Fault: A An internal controller diagnostic failed. Upload and save program before Contact Rockwell Automation Technical Support with the fault type and Minor Diagnostic
runtime diagnostic failed to complete, please the controller is powered down. fault code logged.
161 contact technical support with the fault type
and fault code.

17 34 Major Fault T17:C34 - Diagnostic Fault: Controller internal temperature has exceeded the operating limit. Take measures to reduce the ambient temperature of the module. Follow Major Diagnostic
162 Controller internal temperature has exceeded the recommended limits for the ambient (inlet) temperature and apply the
operating limit. required clearance around the chassis.
17 35 Minor Fault T17:C35 - Diagnostic Fault: Controller internal temperature is approaching the operating limit. Take measures to reduce the ambient temperature of the module. Follow Minor Diagnostic
163 Controller internal temperature is approaching the recommended limits for the ambient (inlet) temperature and apply the
operating limit. required clearance around the chassis.
17 36 Minor Fault T17:C36 - Diagnostic Fault: A fan A fan has been removed, or is not maintaining the desired speed. Applies to CompactLogix 5480 Controllers. Check the device fans for Minor Diagnostic
164 has been removed, or is not maintaining connection or maintenance issues.
desired speed.
17 37 Major Fault T17:C37 - Diagnostic Fault: Controller has recovered from an internal temperature fault. Generated when the controller recovers from automatic shutdown. Major Runtime Diagnostic
Controller has recovered from an internal Shutdown occurs when the module temperature exceeds the temperature
temperature fault. threshold of the preservation fault. When the temperature decreases to a
165 suitable level, this re-enables the controller voltages and generates the
Type 17, Code 37 fault.

18 1 Major Fault T18:C01 - CIP Motion Fault: A The drive did not initialize correctly. To determine corrective action, see the Initialization Fault attributes. The Major Integrated motion on the
standard Initialization Fault has been detected corresponding bit indicates the cause of the fault. EtherNet/IP™ network
by the drive. 1: Boot Block Checksum Fault
166 2: Main Block Checksum Fault
3: Nonvolatile Memory Checksum Fault
 A B C D E F G
18 2 Major Fault T18:C02 - CIP Motion Fault: A The drive did not initialized correctly. This fault indicates a manufacturer- To determine corrective action, see the Initialization Fault Mfg attributes. Major CIP Motion
manufacturer specific Initialization Fault has specific initialization fault. The corresponding bit indicates the cause of the fault.
been detected by the drive. 1: Feedback Data Corruption
2: Feedback Data Range
3: Feedback Communication Startup
4: Feedback Absolute Overspeed
5: Feedback Absolute Power Off Travel
6: Feedback Absolute Startup Speed
7: Commutation Offset Uninitialized
12: Invalid FPGA Image
14: Invalid Safety Firmware
15: Power Board
167 16: Illegal Option Card
17: Option Storage Checksum
19: Module Voltage Mismatch
20: Unknown Module
21: Factory Configuration Error
22: Illegal Address
23: Series Mismatch
24: Open Slot

18 3 Major Fault T18:C03 - CIP Motion Fault: A There is a fault on the physical axis. To determine corrective action, see the Axis Fault attributes. The Major CIP Motion
168 standard Axis Fault has been detected by the corresponding bit indicates the cause of the fault.
drive.
18 4 Major Fault T18:C04 - CIP Motion Fault: A There is a fault on the physical axis. This fault indicates a manufacturer- To determine corrective action, see the Axis Fault Mfg attributes. The Major CIP Motion
169 manufacturer specific Axis Fault has been specific axis fault corresponding bit indicates the cause of the fault.
detected by the drive.
18 5 Major Fault T18:C05 - CIP Motion Fault: A A motion fault detected. To determine corrective action, see the Motion Fault attribute and Motion Major CIP Motion
170 Motion Fault has been detected by the drive. Fault bits for details about the fault that occurred.
18 6 Major Fault T18:C06 - CIP Motion Fault: A A motion drive fault detected. Reconfigure the faulted motion module to correct the fault. Major CIP Motion
171 Module Fault has been detected by the drive. Usually the fault affects all axes that are associated with the module and
all of the associated axes are shut down.
18 7 Major Fault T18:C07 - CIP Motion Fault: Group A motion group fault detected. Reconfigure the entire motion subsystem to correct the fault. Major CIP Motion
Fault Usually the fault affects all axes that are associated with a motion group. See the Group Fault attribute if details about the fault are needed.
172

18 8 Major Fault T18:C08 - CIP Motion Fault: A A fault occurred during the configuration of a motion drive. To determine the corrective action, see the Configuration Fault in the Major CIP Motion
173 Configuration Fault has been detected by the Typically, this fault occurs when an attempt to update an axis Attribute Error Code and Attribute Error ID attributes associated with the
drive. configuration attribute of a drive was unsuccessful. motion or 1756-ENxT module.
18 9 Major Fault T18:C09 - CIP Motion Fault: A An Absolute Position Recovery (APR) fault occurred and the absolute To determine the corrective action, see the APR Fault attributes. The Major CIP Motion
standard APR Fault has been detected by the position of the axis cannot be recovered. corresponding bit indicates the cause of the fault.
drive. 1: Memory Write Error
2: Memory Read Error
3: Feedback Serial Number Mismatch
174 4: Buffer Allocation Fault
5: Scaling Configuration Changed
6: Feedback Mode Changed
7: Feedback Integrity Loss

18 10 Major Fault T18:C10 - CIP Motion Fault: A An Absolute Position Recovery (APR) Fault occurred and the absolute To determine the corrective action, see the APR Fault Mfg attributes. The Major CIP Motion
175 manufacturer specific APR Fault has been position of the axis cannot be recovered. This fault indicates a corresponding bit indicates the cause of the fault.
detected by the drive. manufacturer-specific APR fault.
19 1 Minor Fault T19:C01 - Ethernet Port Fault The controller detected that another device on the network already has Do one of the following: Minor Ethernet Port
the IP address of the controller. • Identify the device with the same IP address as the controller and change
its IP addess.
176 • Change the IP address of the controller, so that it does not conflict with
any other device.

177 19 2 Minor Fault T19:C02 - Ethernet Port Fault The DHCP server replied with an invalid IP address. Check the DHCP server configuration. Minor Ethernet Port
178 19 3 Minor Fault T19:C03 - Ethernet Port Fault The DHCP lease was lost or its renewal failed. Check the DHCP server availability and configuration. Minor Ethernet Port
19 4 Minor Fault T19:C04 - Ethernet Port Fault An EtherNet/IP data storm is detected. Investigate network traffic on the Ethernet port and clear the fault. If Minor Ethernet Port
179 problems persist, contact Rockwell Automation Technical Support for
further assistance.
20 1 Major Fault T20:C01 - License Fault: License is A required license is missing or expired during the transition to Run or Insert a CmCard which contains all licenses required by the project in the Major License Protection
180 missing or invalid. Test mode. controller.
20 2 Minor Fault T20:C02 - License Fault: License The License Based Execution Protection license that is stored on the Obtain a CmCard with the correct unexpired license and insert it into the Minor License Protection
181 has expired. CmCard has the correct license, but it has expired. controller.
21 1 Minor Fault T21:C01 - Alarm Fault: Evaluating Evaluating alarms exceeded the evaluation period. If the fault occurs for a controller that experiences a regular active alarm Minor Alarm
alarms exceeded the evaluation period. rate (not alarm burst) for tag-based alarms during system commissioning,
then reduce the number of the alarms in the project. Otherwise, the fault is
182 an indicator for the operator that tag-based alarm state information can be
older than the evaluation period (only 500 ms evaluation period).

21 2 Minor Fault T21:C02 - Alarm Fault: Alarm set Alarm set highest severity alarm data may be inaccurate. If the fault occurs for a controller that experiences a regular active alarm Minor Alarm
highest severity alarm data may be inaccurate. rate (not alarm burst) for tag-based alarms during the system
commissioning, then reduce the number of the alarms in the project.
Otherwise, the fault is an indicator for the operator that information about
183
the Alarm Set highest severity can be older than 2 seconds.

184
185
186
187
Logix 5000™ Safety Controller and I/O Fault Codes

For more information, see the following resource:

Logix 5000 Controllers Major, Minor, and I\O Faults Programming Manual, 1756-PM014

Fault Type Fault Code Studio 5000 Logix Designer®

Application Display Text

14 1 Task Watchdog Expired

14 2
14 3 Safety Partner Missing

14 4 Safety Partner Unavailable

14 5 Hardware Incompatible

14 6 Firmware Incompatible

14 7 Safety Task Inoperable

14 8 Major Fault T14:C08 - Safety
Task Fault: Safety partner's
time is not synchronized
with primary.

14 9 Safety Partner Hard Fault

14 12 Minor Fault T14:C12 - Safety

Fault: Safety partner
detected when the project
safety level is SIL2/PLd.
 Codes

ource:
O Faults Programming Manual, 1756-PM014

Fault

The task watchdog expired because of these reasons:

• The user task did not complete in a specified period of time.
• A program error caused an infinite loop.
• The program is too complex to execute as quickly as specified.
• A higher priority task is keeping this task from finishing.
• The safety partner has been removed.

An error exists in a routine of the safety task.

The safety partner is missing.

The safety partner is unavailable.

The safety partner hardware is incompatible.

The safety partner firmware is incompatible.

The safety task is inoperable. This fault occurs when the safety logic
is invalid, such as for these reasons:
• A mismatch in logic exists between the primary controller and
safety partners.
• A watchdog timeout occurs.
• Memory is corrupt.
(ControlLogix 5570 controllers only). Coordinated system time (CST)
not found. The safety partner's time is not synchronized with the
primary.

The safety partner has a nonrecoverable controller fault.

(ControlLogix 5580 controllers only). The safety partner detected

when the project safety level is SIL2/PLd.
Corrective Action

For ControlLogix 5580 and Compact GuardLogix 5380 controllers:

Clear the fault.
Safety memory is reinitialized and the safety task begins executing.
Reinsert the safety partner if it was removed.

For ControlLogix 5570 and Compact GuardLogix 5370 controllers:

Clear the fault.
If a safety task signature exists, safety memory is reinitialized and the safety task
begins executing.
If a safety task signature does not exist, you must redownload the program to
allow the safety task to run.
Reinsert the safety partner if it was removed.

Correct the error in the user-program logic.

Install a compatible safety partner and clear the fault.
A download may be required.
Install a compatible safety partner and clear the fault.
A download may be required.
Install a compatible safety partner and clear the fault.
A download may be required.
Update the safety partner so that the firmware major and minor revision
matches the primary controller.
A download may be required.

For ControlLogix 5580 and Compact GuardLogix 5380 controllers:

Clear the fault.
Download the application.

For ControlLogix 5570 and Compact GuardLogix 5370 controllers:

Clear the fault.
If a safety task signature exists, safety memory is reinitialized via the safety task
signature and the safety task begins executing.
If a safety task signature does not exist, you must download the program again
to allow the safety task to run.
For ControlLogix 5570 and Compact GuardLogix 5370 controllers:
Clear the fault. Configure a device to be the CST master.

Clear the fault and download the application. If the problem persists, replace the
safety partner.

For ControlLogix 5580 and Compact GuardLogix 5380 controllers:

If your desired safety level is SIL2/PLd, remove the safety partner (since it does
not participate in a SIL2/PLd configuration).
If your desired safety level is SIL3/PLe, change the project safety level to
SIL3/PLe.
Major/Minor Fault Type Name

Major Nonrecoverable

Major Recoverable
Major Nonrecoverable

Major Nonrecoverable

Major Nonrecoverable

Major Nonrecoverable

Major Nonrecoverable
Major Safety

Major Nonrecoverable

Minor Safety
 A B C D E F
1
2 Logix 5000™ Controller and I/O Fault Codes
3 These are controller-generated faults for I/O modules that the controller owns.
4 For more information, see the following resource:
5 Logix 5000 Controllers Major, Minor, and I\O Faults Programming Manual, 1756-PM014
6
Fault Type Fault Code Studio 5000 Logix Designer® Application Display Text Fault Corrective Action
7 (I/O Map Object
Attribute 5)
8 I/O 0x0001 Connection failure A connection to a module failed. Extended status codes in these ranges provide more detail as to the connection failure.
I/O 0x0002 Resource unavailable. Possible causes include the following. • Check the connection use of the controller or communication module. If all connections are used, try to free some of the used connections or
• There are not enough connections available either for the controller or for add another module to route the errant connection through.
the communication module being used to connect through. • Check the I/O memory available and make program or tag changes if needed.
• The I/O memory limits of the controller are exceeded. • Check the number of controllers making a connection to this I/O module and verify that the number of connections is within the limits of the I/O
9 • The I/O module that is targeted does not have enough connections available. module.

I/O 0x0003 Invalid value in an object specific data parameter of a A parameter that is associated with the request was invalid. Possible causes include the following:
service request •The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the
connection or service to fail.
• The fault may occur even when the module passes the electronic keying test. This may result when Disable Keying or Compatible Keying options
were used in the module configuration instead of the Exact Match option.
10 • Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in
the I/O configuration tree and does not support the connection or service being attempted.
• Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of Logix Designer application. For
more information about electronic keying, see the user manual for the module you are using.

I/O 0x0004 Connection Request Error: Bad Segment. IOI segment error on connection request. The target module does not like one of the parameters in the connection request. This may occur if improper module keying is being used or if the
11 wrong map type attribute is set in the map entry.
I/O 0x0005 Connection Request Error: Bad Class The controller is attempting to make a connection to the module and has Possible causes include the following:
received an error. • The configured address for the connection to the module is incorrect.
• The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the
connection or service to fail.
The fault may occur even when the module passes the electronic keying test. This may result when Disable Keying or Compatible Keying options
were used in the module configuration instead of the Exact Match option.
Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in
12 the I/O configuration tree and does not support the connection or service being attempted.
Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of Logix Designer application. For
more information about electronic keying, see the user manual for the module you are using.
If you are using a 1756-DHRIO module, verify that the Channel type selected in the software (DH+™ or remote I/O network) matches the module’s
rotary switch settings.

I/O 0x0006 Partial data transferred. Only part of the expected data was transferred. Possible causes include the following.
• The response buffer is too small to handle the response data.
• The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the
connection or service to fail.
The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Keying options
were used in the module configuration instead of the Exact Match option.
13 Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in
the I/O configuration tree and does not support the connection or service being attempted.
Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of Logix Designer application. For
more information about electronic keying, see the user manual for the module you are using.

14 I/O 0x0007 Messaging connection lost. The messaging connection was lost. A service request is unconnected, but should be connected.
I/O 0x0008 Service Request Error: Unsupported Service The controller is attempting to request a service from the module that is not Possible causes include the following:
supported by the module. • The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the
connection or service to fail.
• The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Keying options
were used in the module configuration instead of the Exact Match option.
• Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in
15
the I/O configuration tree and does not support the connection or service being attempted.
• Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of Logix Designer application. For
more information about electronic keying, see the user manual for the module you are using.

I/O 0x0009 Module Configuration Rejected: Parameter Error. The configuration for the module is invalid. The module configuration may • Additional Fault Information for this fault will be displayed as a hex code on the Connection Tab. If available for the module, open the
have been changed in the Data Monitor or programmatically. Connections tab of the Module Properties dialog box for the additional fault code. The additional fault code indicates the configuration parameter
that is causing the fault. You may have to correct multiple parameters before this fault is cleared and the module is connected.
16 • Verify that the configuration is valid by using the module configuration software to validate your configuration. Consult the module
documentation for a list of fault codes to determine the configuration parameter that is in error.

I/O 0x000A An attribute in the Get_Attributes_List or Possible causes include the following. If an object attribute or tag is invalid, export the Logix Designer application file, then re-import it. Reschedule the ControlNet® network after re-
Set_Attributes_List has a non-zero status. • A connection is being created where the connection type is invalid. importing if applicable.
17 • An object attribute or tag value is invalid.

18 I/O 0x000B Object already in requested mode or state The object is already in the mode/state being requested by the service. You do not have to request a mode/state because the object is already in the requested mode/state.
I/O 0x000C Service Request Error: Invalid mode or state for service The controller is attempting to request a service from the module and has First, verify that the module is not faulted.
request. received an error. For an I/O module, this may indicate that the module has one of the following conditions:
• Limited communication is possible, but the module has a Major Fault.
19 • A firmware update needs to be completed or is currently being completed.
Refer to the Module Info tab to determine the exact cause.

20 I/O 0x000D Object Already Exists An object instance is created where the instance already exists. Use a different object instance number.
I/O 0x000E Attribute value not settable. A MSG instruction is configured to change an attribute that cannot be changed. See the device user manual for available programming options.
21

I/O 0x000F Access permission denied for requested service. A MSG instruction has been configured to delete a map object that cannot be See the device user manual for available programming options.
22 deleted.
I/O 0x0010 Mode or state of module does not allow object to The state of the device prevents a service request from being handled. See the device user manual for available programming options.
23 perform requested service.
I/O 0x0011 Reply data too large. The reply to a message has a data size that is too large for the destination. Change the destination to a tag that can handle the data size and type being returned.
24

I/O 0x0012 Requested service specifies an operation that is going to The service specified an operation that is going to fragment a primitive data The size of the data being read or written must be rounded to the next primitive data type size.
25 fragment a primitive data value. value, i.e. half a REAL data type. The service is operating on data that is too large for the underlying communication size limits.
I/O 0x0013 Module Configuration Rejected: Data size too small. The configuration for the module is invalid. Not enough configuration data was Verify that the correct module is being targeted.
26 sent.

27 I/O 0x0014 Undefined or unsupported attribute. A MSG instruction is configured to change an attribute that does not exist. See the device user manual for available programming options.
 A B C D E F
I/O 0x0015 Module Configuration Rejected: Data size too large. The configuration for the module is invalid. Too much configuration data was Verify that the correct module is being targeted.
28 sent.

I/O 0x0100 Connection Request Error: Module in Use. The connection being accessed is already in use. Check for these conditions:
• The controller is attempting to make a specific connection to a module and the module cannot support more than one of these connections.
29 • The target of a connection recognizes that the owner is attempting to remake a connection that is already running.

I/O 0x0103 Service Request Error: CIP™ transport class not This indicates that the controller is requesting a transport class that is not Check for these conditions:
supported. supported by the module. • The controller is requesting services not supported by the module.
• The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the
connection or service to fail.
The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Keying options
were used in the module configuration instead of the Exact Match option.
30 Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in
the I/O configuration tree and does not support the connection or service being attempted.
Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of Logix Designer application.
For more information about electronic keying, see the user manual for the module you are using.

I/O 0x0106 Connection Request Error: Module owned and An ownership conflict occurred for the connection. Check for these conditions:
configured by another controller. Module may accept • The Connection Request to this module has been rejected due to an Ownership conflict with another Owner (for example, another Controller).
only one connection if Unicast is used. This may occur with modules, such as output modules, that allow only one Owner to configure and control its outputs.
This fault may also occur if the module is configured as Listen Only and supports only one connection.
• If the Owner is connected to the module with a Unicast connection over EtherNet/IP™ network, other connections to the module may fail
31 because the Owner controls the one connection.
• If the Owner is connected to the module with a Multicast connection over EtherNet/IP network, Unicast connections to the module may fail
because the Owner controls the one connection.
Configure both the Owner and the Listen Only connection as Multicast.

I/O 0x0107 Connection Request Error: Target Connection Not Found. A connection being accessed was not found. Check for these conditions:
• The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the
connection or service to fail.
• The fault may occur even when the module passes the electronic keying test. This may result when Disable Keying or Compatible Keying options
are used in the module configuration instead of the Exact Match option.
Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in
the I/O configuration tree and does not support the connection or service being attempted.
32 Check the module in use and verify that it matches the module specified in the I/O configuration tree of the Logix Designer application. For more
information about electronic keying, see the user manual for the module you are using.
• You have configured a consumed tag or module to use a Unicast connection over EtherNet/IP network, but the producer does not support
Unicast connections.

I/O 0x0108 Connection Request Error: Connection type The controller is requesting a connection type that is not supported by the Check for these conditions:
(Multicast/Unicast) not supported. module. • The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the
connection or service to fail.
• The fault may occur even when the module passes the electronic keying test. This may result when Disable Keying or Compatible Keying options
are used in the module configuration instead of the Exact Match option.
Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in
the I/O configuration tree and does not support the connection or service being attempted.
33 Check the module in use and verify that it matches the module specified in the I/O configuration tree of the Logix Designer application. For more
information about electronic keying, see the user manual for the module you are using.
• You have configured a consumed tag or module to use a Unicast connection over EtherNet/IP network, but the producer does not support
Unicast connections.

I/O 0x0109 Connection Request Error: Invalid connection size. The connection size is inconsistent with the expected size. Additional Error Information for this fault will be displayed as the tag name associated with the connection instance number that has the fault.
Check for these conditions:
• The controller is attempting to set up a connection with the module and cannot because the size of the connection is invalid.
• The controller may be attempting to connect to a tag in a producing controller whose size does not match the tag in this controller.
• The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the
connection or service to fail.
• The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Keying options
were used in the module configuration instead of the Exact Match option.
Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in
34
the I/O configuration tree and does not support the connection or service being attempted.
Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application. For
more information about electronic keying, see the user manual for the module you are using.
If the module is a 1756 ControlNet module, verify that the chassis size is correct. For remote I/O adapters, verify that the rack size and rack density
is correct.

I/O 0x0110 Connection Request Error: Module not configured. The controller is attempting to set up a Listen Only connection with the module This controller is not an Owner of this module because it is attempting to establish a Listen Only connection, which requires no module
35 and cannot because the module has not been configured and connected to by configuration. The controller cannot connect until an Owner configures and connects to the module first.
an Owner (for example, another controller).
I/O 0x0111 Requested Packet Interval (RPI) out of range. RPI not supported. Check for these conditions:
• The Requested Packet Interval (RPI) specified is invalid for this module or for a module in the path to this module.
• The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the
connection or service to fail.
The fault may occur even when the module passes the electronic keying test. This may result when Disable Keying or Compatible Keying options
are used in the module configuration instead of the Exact Match option.
Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in
the I/O configuration tree and does not support the connection or service being attempted.
36 Check the module in use and verify that it matches the module specified in the I/O configuration tree of the Logix Designer application. For more
information about electronic keying, see the user manual for the module you are using.
• For Listen Only connections: the RPI set by the owner of this module is slower than the one requested. Either increase the requested RPI or
decrease the RPI the owner controller is using.
See the Connection tab for valid RPI values.

I/O 0x0113 Connection Request Error: Module connection limit The number of connections is greater than what is available on the module. To reduce the number of connections:
exceeded. The number of connections must be reduced or the hardware must be • Change the FLEX™ I/O communication adapter Comm Format from Input or Output configuration to Rack Optimization. When the Comm Format
upgraded. changes, the adapter must be removed and recreated in the I/O configuration tree.
37 • If the configuration uses messaging over ControlNet, sequence the messages to reduce the number that are executing at the same time, or
reduce the number of messages. Messages (MSG instructions) also use connections.

I/O 0x0114 Electronic Keying Mismatch: Electronic keying product The Product Code of the actual module hardware does not match the Product Electronic Keying failed for this module. You may have a mismatch between the module that is created in the software and the actual module
38 code and/or vendor ID mismatch. Code of the module created in the software. hardware.

I/O 0x0115 Electronic Keying Mismatch: Electronic Keying product The Product Type of the actual module hardware does not match the Product Electronic Keying failed for this module. You may have a mismatch between the module created in the software and the actual module hardware.
39 type mismatch. Type of the module created in the software.
 A B C D E F
I/O 0x0116 Electronic Keying Mismatch: Major and/or Minor The Major or Minor revisions of the module do not match the Major or Minor Electronic Keying failed for this module.
40 revision invalid or incorrect. revisions of the module created in the software. • Verify that you have specified the correct Major and Minor Revision if you have chosen Compatible Module or Exact Match keying.
• You may have a mismatch between the module created in the software and the actual module hardware.
I/O 0x0117 Connection Request Error: Invalid Connection Point. The connection is to an invalid port or port that is already in use. Additional Error Information for this fault appears as the tag name associated with the controller to controller (C2C) that has the fault.
Check for these conditions:
• Another controller owns this module and has connected with a Communications Format different than the one chosen by this controller. Verify
that the Communications Format chosen is identical to that chosen by the first owner controller of the module.
• The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the
connection or service to fail.
The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Keying options
were used in the module configuration instead of the Exact Match option.
41 Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in
the I/O configuration tree and does not support the connection or service being attempted.
Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application. For
more information about electronic keying, see the user manual for the module you are using.
• The controller may be attempting to connect to a nonexistent tag in a producing controller.

I/O 0x0118 Module Configuration Rejected: Format error. An invalid configuration format was used. Check for these conditions:
• The configuration class specified does not match the class supported by the module.
• The connection instance is not recognized by the module.
• The path specified for the connection is inconsistent.
• The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the
connection or service to fail.
The fault may occur even when the module passed the electronic keying test. This may result when Disable Keying or Compatible Keying options
42 were used in the module configuration instead of the Exact Match option.
Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in
the I/O configuration tree and does not support the connection or service being attempted.
Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application. For
more information about electronic keying, see the user manual for the module you are using.

I/O 0x0119 Connection Request Error: Module not owned. The controlling connection is not open. Where a Listen Only connection is requested, the controlling connection is not open.
43

I/O 0x011A Connection Request Error: Out of Connection Resources The controller is attempting to set up a connection with the module and • If the module is a 1756 ControlNet module, up to five controllers can make Rack Optimization connections to the module. Verify that this
cannot because required resources are unavailable. number has not been exceeded.
44 • If the module is a 1794-ACN15, 1794-ACNR15, or 1797-ACNR15 adapter, only one controller can make a Rack Optimization connection to the
module. Verify that this number has not been exceeded.

I/O 0x0203 Connection timed out. The owner or originator recognizes that the target device is on the network or The target can be reached, but its response is not as expected. For example, this fault may be indicated where multicast Ethernet packets are not
backplane. However, I/O data and messages are not being responded to. returned.
45 When this fault occurs, the controller usually attempts to continuously remove and remake the connection. If you use FLEX I/O modules, verify
that you are using the correct terminal device.

I/O 0x0204 Connection Request Error: Connection request timed The controller is attempting to make a connection; however, the target module To recover, take the following steps.
out. is not responding. The device also appears to be missing from the backplane or • Verify that the module has not been removed and is still functioning and receiving power.
network. • Verify that the correct slot number has been specified.
46 • Verify that the module is properly connected to the network.
If you are using FLEX I/O modules, verify that the correct terminal block is in use.

I/O 0x0205 Connection Request Error: Invalid parameter. The controller is attempting to set up a connection with the module and has The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the
received an error (a parameter is in error). connection or service to fail.
The fault may occur even when the module passes the electronic keying test. This may result when Disable Keying or Compatible Keying options
are used in the module configuration instead of the Exact Match option.
Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in
47 the I/O configuration tree and does not support the connection or service being attempted.
Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application. For
more information about electronic keying, see the user manual for the module you are using.

I/O 0x0206 Connection Request Error: Requested size too large. The controller is attempting to set up a connection with the module and has Either:
received an error - the request size is too large. • Verify that the path to this module is sufficiently close to the controller.
• The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the
connection or service to fail.
The fault may occur even when the module passes the electronic keying test. This may result when Disable Keying or Compatible Keying options
are used in the module configuration instead of the Exact Match option.
48 Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in
the I/O configuration tree and does not support the connection or service being attempted.
Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application. For
more information about electronic keying, see the user manual for the module you are using.

I/O 0x0301 Connection Request Error: Out of buffer memory. The controller is attempting to set up a connection with the module and has Check for these conditions:
received an error: a module in the path is out of memory. • The controller may be attempting to connect to a tag in a producing controller that is not marked as being produced.
• The controller may be attempting to connect to a tag in a producing controller. That tag may not be configured to allow enough consumers.
• The size or number of connections through this module needs to be reduced.
• One of the network modules between the module and the controller may be out of memory. Check network configuration of the system.
• The module may be out of memory. Check the system configuration and capabilities of the module.
• The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the
connection or service to fail.
The fault may occur even when the module passes the electronic keying test. This may result when Disable Keying or Compatible Keying options
49
are used in the module configuration instead of the Exact Match option.
Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in
the I/O configuration tree and does not support the connection or service being attempted.
Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application. For
more information about electronic keying, see the user manual for the module you are using.

I/O 0x0302 Connection Request Error: Out of communication The controller is attempting to set up a connection with the module and has Increase the Requested Packet Interval (RPI) and reconfigure your network with RSNetWorx™ software. Distribute the load on another bridge
50 bandwidth. received an error: a module in the path has exceeded its communication module.
bandwidth capacity.
I/O 0x0303 Connection Request Error: No bridge available. The controller is attempting to set up a connection with the module and has Distribute the load on another bridge module.
51 received an error: a module in the path has exceeded its communication
bandwidth capacity.
52 I/O 0x0304 Not configured to send scheduled data. The ControlNet module is not scheduled to send data. Use RSNetWorx™ for ControlNet software to schedule or reschedule the ControlNet network.
I/O 0x0305 Connection Request Error: ControlNet configuration in The ControlNet configuration in the controller does not match the Use RSNetWorx for ControlNet software to reschedule the connections.
controller does not match configuration in bridge. configuration in the bridge module. This may occur because a ControlNet
53 module was changed after the network was scheduled, or because a new
control program has been loaded into the controller.
 A B C D E F
I/O 0x0306 ControlNet Keeper not available.. The ControlNet Configuration Master (CCM) cannot be found. The 1756-CNB Verify that a 1756-CNB modules or PLC-5® ControlNet processor is at node 1 and is functioning properly.
module and PLC-5® ControlNet processor are the only devices capable of being
a CCM and the CCM must be node 1.
54
This fault may temporarily occur when the system is powered up and is being
cleared when the CCM is located.

I/O 0x0311 Connection Request Error: Invalid port. The controller is attempting to set up a connection with the module and has Verify that all modules in the I/O Configuration tree are the correct modules.
55 received an error.
I/O 0x0312 Connection Request Error: Invalid link address. The controller is attempting to set up a connection with the module and has • Verify that the chosen slot number for this module is not greater than the size of the rack.
received an error: an invalid link address has been specified. A link address can • Verify that the ControlNet node number is not greater than the maximum node number configured for the network in RSNetWorx for
be a slot number, a network address, or the remote I/O chassis number and ControlNet software.
56 starting group.

I/O 0x0315 Connection Request Error: Invalid segment type. The segment type or route is invalid. Either:
• The controller is attempting to set up a connection with the module and has received an error: the connection request is invalid.
• The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the
connection or service to fail.
The fault may occur even when the module passes the electronic keying test. This may result when Disable Keying or Compatible Keying options
are used in the module configuration instead of the Exact Match option.
57 Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in
the I/O configuration tree and does not support the connection or service being attempted.
Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application. For
more information about electronic keying, see the user manual for the module you are using.

I/O 0x0317 Connection Request Error: Connection not scheduled. The controller is attempting to set up a ControlNet connection with the module Use RSNetWorx for ControlNet software to schedule or reschedule the connection to this module.
58 and has received an error.
I/O 0x0318 Connection Request Error: Invalid link address - cannot The controller is attempting to set up a connection with the module and has Verify that the associated ControlNet module has the correct slot or node number selected.
59 route to self. received an error: the link address is invalid.
I/O 0x0319 Connection Request Error: No secondary resources The controller is attempting to set up a connection with the module and has Reduce the size or number of connections through this module or add another controller or ControlNet module to the system.
available in redundant chassis. received an error: the redundant module does not have the necessary
60 resources to support the connection.

I/O 0x031B Connection Request Error: Rack Connection Refused. The controller is attempting to set up a Direct connection with the module and A rack-optimized connection has already been established to this module through the 1756-CNB/R in the same chassis.
has received an error. • Connect to this module via the 1756-CNB/R in the same chassis.
• Connect to this module via a different 1756-CNB/R to use a Direct connection.
61 • Change the first connection from rack-optimized to Direct, and then re-establish the second direct connection.
• Connect to this module from a controller in the same chassis as the module (do not connect via 1756-CNB/R.

I/O 0x031E Connection Request Error: Cannot consume tag. The controller is attempting to connect to a tag in a producing controller and • The controller is attempting to connect to a tag in a producing controller and that tag has already been used by too many consumers.
62 has received an error. • Increase the maximum number of consumers on the tag.
63 I/O 0x031F Connection Request Error: Tag not published. The consume tag was not configured to be produced in the target module. Make sure the name of the tag being consumed is spelled correctly in both the consumer and producer.
I/O 0x0322 Connection Request Error: Data format for requested A new connection requested does not match the existing connection. Check the controllers that are using the connection and verify that all configurations are identical.
64 connection does not match data format of connection
already established.
I/O 0x032D CIP Security session error: No matching ingress rule. A request is rejected due to failure to match an ingress rule. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
65 error persists, contact your security administrator or technical support.
I/O 0x032E CIP Security session error: Ingress rule deny. A request is rejected due to matching an ingress rule with action DENY. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
66 error persists, contact your security administrator or technical support.
I/O 0x032F CIP Security session error: Ingress rule deny non-secure. A request is rejected due to matching an ingress rule with action Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
67 ALLOW_INGRESS_SECURE, but the request was through a non CIP Security error persists, contact your security administrator or technical support.
port.
I/O 0x0330 CIP Security session error: No matching egress rule. A request is rejected due to failure to match an egress rule. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
68 error persists, contact your security administrator or technical support.
I/O 0x0331 CIP Security session error: Egress rule deny. A request is rejected due to matching an egress rule with action DENY. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
69 error persists, contact your security administrator or technical support.
I/O 0x0332 CIP Security session error: Egress rule cipher not allowed. A request is rejected due to matching an egress rule with action ALLOW, but Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
70 the CIPHER_LIST does not include an allowed cipher suite. error persists, contact your security administrator or technical support.
I/O 0x0800 Network link in path to module is offline. A bridge module in the path to the target module is offline. It is either not physically connected to the network (media disconnected) or otherwise unable to forward the request onto the destination network.
71

I/O 0x0801 Incompatible Multicast RPI A connection has already been established to the target module at a different • Configure the tag as unicast.
72 RPI and it cannot be changed to accommodate the RPI specified. • Adjust RPI so that all multicast consumers of the tag use the same RPI.
• Configure the RPI so that is in the range allowed by the producer.
I/O 0x0810 No target application data available. The controlling application has not initialized the data to be produced by the For the target device associated with the "Send Data" connection reporting this connection error, start the controlling application and perform at
target device. This may be caused when "Send Data" connections are least one write of data. See the documentation for the target device and its controlling application for information on how to do this.
73 configured in a target device and the controlling application for that target
device has not initialized the data to be produced.

74 I/O 0x0814 Connection Request Error: Data Type Mismatch. Given data type does not match Produce tag data type in target module. Make sure both data types match.
I/O 0x0817 Connection Request Error: Module no longer configured The controller is configured with redundancy enabled but has lost redundancy • Reinsert the redundancy module into the rack.
within a synchronized controller redundancy system. status information. The redundancy module was either removed from the • Clear the fault on the redundancy module.
75
system or faulted.

I/O 0x0900 CIP Security session error: (D) TLS Alert 0: Close Notify 1. One side of the (D)TLS connection has requested that the connection be closed. Check that your model matches the actual communications flow.
Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
76
error persists, contact your security administrator or technical support.

I/O 0x0901 CIP Security session error: (D) TLS Alert 10: Unexpected An unexpected CIP Security protocol fault occurred. Check that your model matches the actual communications flow.
Message. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
77
error persists, contact your security administrator or technical support.

I/O 0x0902 CIP Security session error: (D) TLS Alert 20: Bad Record An unexpected CIP Security protocol fault occurred. Contact technical support.
MAC. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
78
error persists, contact your security administrator or technical support.

I/O 0x0903 CIP Security session error: (D)TLS Alert 22: Record An unexpected CIP Security protocol fault occurred. Please contact technical support.
Overflow. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
79
error persists, contact your security administrator or technical support.

I/O 0x0904 CIP Security session error: (D)TLS Alert 30: An unexpected CIP Security protocol fault occurred. Contact technical support.
Decompression Failure. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
80
error persists, contact your security administrator or technical support.

I/O 0x0905 CIP Security session error: (D)TLS Alert 40: Handshake An unexpected CIP Security protocol fault occurred. Check your configuration.
Failure. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
81
error persists, contact your security administrator or technical support.
 A B C D E F
I/O 0x0906 CIP Security session error: (D)TLS Alert 42: Bad An unexpected CIP Security protocol fault occurred. Contact technical support.
Certificate. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
82
error persists, contact your security administrator or technical support.

I/O 0x0907 CIP Security session error: (D)TLS Alert 43: Unsupported An unexpected CIP Security protocol fault occurred. Contact technical support.
Certificate. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
83
error persists, contact your security administrator or technical support.

I/O 0x0908 CIP Security session error: (D)TLS Alert 44: Certificate An unexpected CIP Security protocol fault occurred. Contact technical support.
Revoked. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
84
error persists, contact your security administrator or technical support.

I/O 0x0909 CIP Security session error: (D)TLS Alert 45: Certificate An unexpected CIP Security protocol fault occurred. Contact technical support.
Expired. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
85
error persists, contact your security administrator or technical support.

I/O 0x090A CIP Security session error: (D)TLS Alert 46: Certificate An unexpected CIP Security protocol fault occurred. Check that your model matches the actual communications flow.
Unknown. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
86
error persists, contact your security administrator or technical support.

I/O 0x090B CIP Security session error: (D)TLS Alert 47: Illegal An unexpected CIP Security protocol fault occurred. Please contact technical support.
Parameter. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
87
error persists, contact your security administrator or technical support.

I/O 0x090C CIP Security session error: (D)TLS Alert 48: Unknown CA. An unexpected CIP Security protocol fault occurred. Check that your model matches the actual communications flow.
Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
88
error persists, contact your security administrator or technical support.

I/O 0x090D CIP Security session error: (D)TLS Alert 49: Access An unexpected CIP Security protocol fault occurred. Check that your model matches the actual communications flow.
Denied. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
89
error persists, contact your security administrator or technical support.

I/O 0x090E CIP Security session error: (D)TLS Alert 50: Decode Error. An unexpected CIP Security protocol fault occurred. Contact technical support.
Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
90
error persists, contact your security administrator or technical support.

I/O 0x090F CIP Security session error: (D)TLS Alert 51: Decrypt Error. An unexpected CIP Security protocol fault occurred. Contact technical support.
Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
91
error persists, contact your security administrator or technical support.

I/O 0x0910 CIP Security session error: (D)TLS Alert 70: Protocol An unexpected CIP Security protocol fault occurred. Contact technical support.
Version. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
92
error persists, contact your security administrator or technical support.

I/O 0x0911 CIP Security session error: (D)TLS Alert 71: Insufficient An unexpected CIP Security protocol fault occurred. Check the cipher suites that you configured in your model that every target an originator has a matching cipher suite allowed.
Security. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
93
error persists, contact your security administrator or technical support.

I/O 0x0912 CIP Security session error: (D)TLS Alert 80: Internal Error. An unexpected CIP Security protocol fault occurred. Contact technical support.
Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
94
error persists, contact your security administrator or technical support.

I/O 0x0913 CIP Security session error: (D)TLS Alert 86: Inappropriate An unexpected CIP Security protocol fault occurred. Contact technical support.
Fallback. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
95
error persists, contact your security administrator or technical support.

I/O 0x0914 CIP Security session error: (D)TLS Alert 110: An unexpected CIP Security protocol fault occurred. Contact technical support.
Unsupported Extension. Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
96
error persists, contact your security administrator or technical support.

I/O 0x0915 CIP Security session error: (D)TLS Alert: Unknown PSK An unexpected CIP Security protocol fault occurred. Check that your model matches the actual communications flow.
Identity Verify that you are addressing the correct device and that the project configuration includes devices supported by your CIP Security Policy. If this
97
error persists, contact your security administrator or technical support.

I/O 0xFD01 Connection Request Error: Bad Backplane EEPROM. This controller‘s last redundancy state at the time an operational RM was Replace the backplane.
98 present implies that a partner controller may exist which is currently Primary
and also attempting to open the same concurrent connection.
I/O 0xFD02 Connection Request Error: No error code is supplied by No error code is supplied by an I/O module to describe an I/O fault. See the user manual for your device.
99 an I/O module to describe an I/O fault.
I/O 0xFD03 Connection Request Error: Required Connection missing The controller is attempting to set up a connection with the module and has This module requires a particular set of connections and connection types, and one of those connection types is missing.
100 received an error.
I/O 0xFD04 Connection Request Error: No CST Master Detected The controller is attempting to set up a connection with the module and has Configure a module (typically a controller) in this chassis to be the CST master.
101 received an error - this module requires a CST master in the chassis.
I/O 0xFD05 Connection Request Error: No Axis or Group Assigned. The controller is attempting to set up a connection with the module and has Assign a Group or Axis.
102 received an error - this module requires an axis or group table assigned.
I/O 0xFD06 SERCOS Transition Fault The controller command to transition the SERCOS ring to a new phase Check for duplicate Drive Nodes.
103 returned an error from the module.
104 I/O 0xFD07 Connection Request Error: SERCOS Init Ring Fault. An attempt to configure the SERCOS ring failed. The baud rate for all devices must be the same and supported by the drives and the SERCOS module.
I/O 0xFD08 SERCOS Comm Fault Mainly two sets of faults may cause this fault, physical and interface faults. Check for these sources of physical faults:
• Broken ring
Interface errors are encountered when you are configuring third-party drives. • Loose connector
• Fiber optics not clean
• Electrical noise due to improper drive grounding
• Too many nodes on the ring

105 Check for these potential interface errors:

• No SERCOS MST (Protocol Error).
• Missed AT (drive did not send data when expected).
• SERCOS timing error in phase 3.
• Error in drive data that is returned to SERCOS module.

I/O 0xFD09 SERCOS Node Initialization Fault The SERCOS module defected a problem during the Init Node Comm service. There is a problem with the IDNs being configured. Check the general and extended error codes and refer to their definition SERCOS
106 documentation.
I/O 0xFD0A Axis Attribute Error - See Faulted Axis. The analog servo motion module rejected an attribute update. Ensure all attributes are set to valid values.
107 See Analog axis attribute documentation.
I/O 0xFD0C The end device has a different Grandmaster than the The drive detected a different PTP Grandmaster than the controller. Ensure that the drive and the controller can synchronize to the same CIP Sync™ grandmaster clock.
108 controller See the Time Synchronization page for the drive and the controller.
 A B C D E F
I/O 0xFD1F Bad Safety Protocol Format. An error occurred adding the safety network segment to a route. • The module in use is different than the module specified in the I/O configuration tree and is therefore causing the connection or service to fail.
The fault may occur even when the module passes the electronic keying test. This may result when Disable Keying or Compatible Keying options
are used in the module configuration instead of the Exact Match option.
Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in
the I/O configuration tree and does not support the connection or service being attempted.
109 Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application. For
more information about electronic keying, see the user manual for the module you are using.

110 I/O 0xFD20 No safety task running in local controller. No safety task appears to be running. Safety modules require that a safety task be present and running in the controller originating the connection.
I/O 0xFD22 POINTBus Fault: The configured number of expansion When the expected chassis size does not match the discovered chassis size, I/O Verify the number of physical expansion I/O modules configured for the controller and then update the number of modules selected from the
111 I/O modules does not match the number of physical connections are prevented. Expansion I/O list on the General page in the Controller Properties dialog.
modules detected.
I/O 0xFD23 POINTBus Fault: Expansion modules detected beyond This error can happen when you put more modules in a chassis than what the To verify the number of physical expansion I/O the controller supports, open the Controller Properties dialog and expand the Expansion I/O list on
the number allowed for this controller type. product catalog supports. You cannot detect the extra modules using a tool the General page.
112 like RSLinx® as that only lets you browse up to the chassis size. When you try to Configure the number of physical expansion I/O modules to match the selection in the Expansion I/O list.
establish I/O connections, I/O connections are prevented.

I/O 0xFE01 Connection Request Error: An invalid configuration An invalid configuration format was encountered. The connection type configured by the profile is not appropriate for this module.
113 format was encountered.
114 I/O 0xFE02 Requested Packet Interval (RPI) out of range. The Requested Packet Interval (RPI) specified is invalid for this module. See the Connection tab for valid RPI values.
I/O 0xFE03 Connection Request Error: The input connection point Invalid input connection point. The input connection point is 0 and is not allowed to be 0.
115 has not been set.
116 I/O 0xFE04 Connection Request Error: Invalid input data pointer. Module entry in the controller incorrect. Contact Rockwell Automation Support.
117 I/O 0xFE05 Connection Request Error: Invalid input data size. Module entry in the controller incorrect. Contact Rockwell Automation Support.
I/O 0xFE06 Connection Request Error: The input force pointer has Module entry in the controller incorrect. Contact Rockwell Automation Support.
118 not been set.
I/O 0xFE07 Connection Request Error: The output connection point Module entry in the controller incorrect. Contact Rockwell Automation Support.
119 has not been set.
120 I/O 0xFE08 Connection Request Error: Invalid output data pointer. Module entry in the controller incorrect. Contact Rockwell Automation Support.
121 I/O 0xFE09 Connection Request Error: Invalid output data size. Module entry in the controller incorrect. Contact Rockwell Automation Support.
I/O 0xFE0A Connection Request Error: The output force pointer has Module entry in the controller incorrect. Contact Rockwell Automation Support.
122 not been set.
123 I/O 0xFE0B Invalid Symbol String Module entry in the controller incorrect. Contact Rockwell Automation Support.
I/O 0xFE0C Invalid PLC-5 instance number. The controller is attempting to set up a connection with the PLC-5 controller Verify that the instance number specified has been properly specified in the PLC-5 controller.
124 and has received an error.
125 I/O 0xFE0D Tag does not exist in peer controller. Module entry in the controller incorrect. Contact Rockwell Automation Support.
126 I/O 0xFE0E Automatic Firmware Update in progress. The module is currently being updated. This is not an error, but an information code
I/O 0xFE0F Automatic Firmware Update Failed: Firmware file The firmware supervisor has attempted to update an unsupported module. Either:
127 incompatible with the module. This occurs when there is no NVS file on the SD card for the module revision • Update Module firmware file on SD card with proper module revision.
specified in the project. • Change module revision in the module properties in the project.
I/O 0xFE10 Automatic Firmware Update Failed: Firmware file not The firmware file to update the module cannot be found. The project has a Either:
found. module that needs a specific firmware revision that is not on the SD card. • Manually update the module's firmware.
128 • Copy the correct revision of module firmware to the SD card.
• Change the module revision in the project to match the revision on the module.

I/O 0xFE11 Automatic Firmware Update Failed: Firmware file invalid. The firmware file is corrupted. Either:
129 • Use a different SD card.
• Copy the correct revision of module firmware to the SD card.
130 I/O 0xFE12 Automatic Firmware Update Failed. An error has occurred while updating the module. Check the module status indicators, and troubleshoot the module.
I/O 0xFE13 Automatic Firmware Update Failed: Detected Active An active connection could not be made to the target module. There is an active connection already made to the target module from some other originator, thereby disallowing a flash update from occurring.
131 Connections.
I/O 0xFE14 Automatic Firmware Update pending: Searching NVS file The firmware file is currently being read. Firmware Supervisor is searching NVS File for identity info. This is not an error, but an information code.
132 for appropriate module identity.
I/O 0xFE22 Connection Request Error: Invalid input network Module entry in the controller incorrect. Contact Rockwell Automation Support.
133 connection type.
I/O 0xFE23 Connection Request Error: input connection does not Module entry in the controller incorrect. Contact Rockwell Automation Support.
134 specify whether unicast is allowed.
I/O 0xFF00 Connection Request Error: No connection instance. The controller is attempting to set up a connection with the module and has • Verify that the physical module is the same module type (or is a compatible module) as created in the software.
received an error. • If the module is a 1756-DHRIO module in a remote chassis (connected via a ControlNet network), verify that the network has been scheduled
with RSNetWorx software.
135 • Even after the network has been scheduled with RSNetWorx for ControlNet software, if you are online and if the 1756-DHRIO module is
configured for DH+™ network only, a 0xff00 Module Fault (no connection instance) may occur. The module is properly communicating even
though Faulted is displayed as its Status on the Module Properties dialog box. Disregard the error message and fault status and continue.

I/O 0xFF01 Connection Request Error: Path to module too long. The controller is attempting to set up a connection with the module and has Verify that the path to this module is a valid length.
136 received an error.
I/O 0xFF04 Connection Request Error: The controller's map instance The remote controller’s map instance attempted to access a connection while Go offline with the controller and make the change and then download the modified project to the controller.
137 attempted to access a connection while being in an in an invalid state. An attempt was made to initiate the reconfiguration of a
invalid state. device that is not supported by the controller
I/O 0xFF08 Connection Request Error: Invalid path to module. The controller is attempting to set up a connection with the module and has Verify that the path to this module is a valid length.
138 received an error.
I/O 0xFF0B Module Configuration Rejected: Bad format. Invalid configuration format. Either:
• The configuration for the module is invalid.
• The module in use (that is, the physical module) is different than the module specified in the I/O configuration tree and is therefore causing the
connection or service to fail.
The fault may occur even when the module passes the electronic keying test. This may result when Disable Keying or Compatible Keying options
are used in the module configuration instead of the Exact Match option.
139 Despite passing the electronic keying test, the module being connected to does not have the same features or settings as the module specified in
the I/O configuration tree and does not support the connection or service being attempted.
Check the module in use and verify that it exactly matches the module specified in the I/O configuration tree of the Logix Designer application. For
more information about electronic keying, see the user manual for the module you are using.

I/O 0xFF0E Connection Request Error: No connections accepted to The controller is attempting to set up a connection with a ControlNet bridge ControlNet bridge modules should not have connections to them.
140 bridge. module and has received an error.
 A B C D
1
2 Syslog Messages
3
4 These syslog messages apply to ControlLogix® 5580 controllers and 1756-EN4TR communication modules.
5 For more information, see these resources:
6 ControlLogix 5580 and GuardLogix® 5580 Controllers User Manual, 1756-UM543
7 ControlLogix EtherNet/IP™ Network Devices User Manual, 1756-UM004
8 CIP Security with Rockwell Automation Products Application Technique, SECURE-AT001
9
10 Type ID Message Guidance
Backup backup_generated Backup was generated to %dst% by %username% on Product backup was successfully generated.
%src% Where:
%username% = The username that initiated the backup operation.
11 %src% = The source that the backup request originated from.
%dst% = The destination that the backup was written to. If the backup was created locally, then this should specify
*localhost*, the hostname, fully-qualified domain name or IP address of the product.

Backup backup_failed Backup to %dst% by %username% on %src% failed! Product backup failed.
Error=%err% Where:
%username% = The username that initiated the backup operation.
%src% = The source that the backup request originated from.
12 %dst% = The destination that the backup was attempted to. If the backup was created locally, then this should specify
*localhost*, the hostname, fully-qualified domain name or IP address of the product.
%err% = The error code that indicates the underlying cause of the failure.

Backup backup_restored Backup was restored from %dst% by %username% on Product was restored from a backup.
%src% Where:
%username% = The username that initiated the restore operation.
13 %src% = The source that the backup request originated from.
%dst% = The location that the restore was being read from. If the restore is local to the product, then this should specify
*localhost*, the hostname, fully-qualified domain name or IP address of the product.

Backup backup_restore_failed Backup could not be restored from %dst% by Failed attempt to restore a product from a backup.
%username% on %src% Where:
%username% = The username that initiated the restore operation.
%src% = The source that the backup request originated from.
14 %dst% = The location that the restore was being read from. If the restore is local to the product, then this should specify
*localhost*, the hostname, fully-qualified domain name or IP address of the product.
%err% = The error code that indicates the underlying cause of the failure.

CIP Security™ cipsec_dtls_client_session_failed Failed to start CIP Security I/O session with %dst%. CIP Security enabled connection originator fails to establish a secure I/O session with a target device.
Error=%err% Where:
15 %dst% = The target device that could not support the secure session.
%err% = The error code that indicates the underlying cause of the failure.

CIP Security cipsec_dtls_client_session_started Started CIP Security I/O session with %dst% CIP Security enabled connection originator successfully establishs a secure I/O session with a target device.
16 Where:
%dst% = The target device that could not support the secure session.
CIP Security cipsec_dtls_server_session_failed %src% failed to start CIP Security I/O session. Error= CIP Security enabled target fails the establishment of a secure I/O session.
%err% Where:
17 %src% = The source device that attempted to establish the secure session.
%err% = The error code that indicates the underlying cause of the failure.

CIP Security cipsec_dtls_server_session_started %src% started CIP Security I/O session CIP Security enabled target successfully establishes a secure I/O session.
18 Where:
%src% = The source device that established the secure session.
CIP Security cipsec_new_crl_configured A new CRL for CIP Security was received from CIP Security enabled endpoint is deployed a new Certificate Revocation List (CRL).
%username% at %src% Where:
19 %username% = The user name associated with the identity that deployed the new CRL.
%src% = The source device that deployed the CRL.

CIP Security cipsec_new_identity_configured A new CIP Security identity was received from CIP Security enabled endpoint is deployed a new active certificate in the EtherNet/IP CIP security object.
%username% at %src% Where:
20 %username% = The user name associated with the identity that deployed the new identity.
%src% = The source device that deployed the new identity.
 A B C D
CIP Security cipsec_new_identity_failed A new CIP Security identity failed to be accepted from CIP Security enabled endpoint fails to accept a new active certificate in the EtherNet/IP CIP security object.
%username% at %src% Where:
21 %username% = The user name associated with the identity that attempted to deploy the new identity.
%src% = The source device that attempted to deploy the new identity.

CIP Security cipsec_new_policy A new policy for %name% was configured by CIP Security enabled endpoint successfully deployed new policies that can affect the CIP Security configuration.
%username% at %src% Where:
%username% = The user name associated with the identity that deployed the new policy.
22 %src% = The source device that deployed the new policy.
%name% = The identifier for the policy that was changed. See the preceding table for a list of known policies.

CIP Security cipsec_identity_expiring The CIP Security identity at %src% is expiring on %time CIP Security enabled endpoint detects that its identity certificate is nearing expiration.
%
This is a repeating event that should begin 30 days before the expiration of the certificate and repeat every 24 hours until
the certificate is renewed, replaced, or expired.
This event will not be generated if the certificate cannot expire because the endpoint does not have a real time clock.
23
Where:
%src% = The endpoint that has the expiring certificate.
%time% = The time the certificate will expire.

CIP Security cipsec_identity_expired The CIP Security identity at %src% expired on %time% CIP Security enabled endpoint detects that its identity certificate has expired.

This is a repeating event that should begin as soon as the expired certificate is detected and repeat every 24 hours until the
certificate is renewed or replaced.
This event will not be generated if the certificate cannot expire because the endpoint does not have a real time clock.
24
Where:
%src% = The endpoint that has the expired certificate.
%time% = The time the certificate expired.

CIP Security cipsec_tls_client_session_failed Failed to start CIP Security messaging session with %dst CIP Security enabled connection originator fails to establish a secure messaging session with a target device.
%. Error=%err% Where:
25 %dst% = The target device that could not support the secure session.
%err% = The error code that indicates the underlying cause of the failure.

CIP Security cipsec_tls_client_session_started Started CIP Security messaging session with %dst% CIP Security enabled connection originator successfully establishs a secure messing session with a target device.
26 Where:
%dst% = The target device that could not support the secure session.
CIP Security cipsec_tls_server_session_failed %src% failed to start CIP Security messaging session. CIP Security enabled target fails the establishment of a secure messaging session.
Error=%err% Where:
27 %src% = The source device that attempted to establish the secure session.
%err% = The error code that indicates the underlying cause of the failure.

CIP Security cipsec_tls_server_session_started %src% started CIP Security messaging session CIP Security enabled target successfully establishes a secure messaging session.
28 Where:
%src% = The source device that established the secure session.
CIP Security cipsec_trust_modified CIP Security trust was modified by %username% at %src CIP Security enabled endpoint is deployed a new trusted certificate in the EtherNet/IP CIP security object.
% Where:
%username% = The user name associated with the identity that deployed the new policy.
29 %src% = The source device that deployed the new policy.
%name% = The identifier for the policy that was changed. See the preceding table for a list of known policies.

Configuration config_critical_change Configuration in subsystem %subsystem% was modified Critical configuration change successfully takes place.
by user %username% from source %src% Any configuration change that is normally guarded by an implicit or explicit protection mode and not covered by a more
specific event is considered a critical configuration change.
30 Where:
%username% = The username that made the configuration change.
%src% = The source that the change was requested from.
 A B C D
Configuration config_critical_change_failed Failed configuration change subsystem %subsystem% Critical configuration change is rejected.
by user %username% from source %src%. Error=%err% Any configuration change that is normally guarded by an implicit or explicit protection mode and not covered by a more
specific event is considered a critical configuration change.
31 Where:
%username% = The username that requested the configuration change.
%src% = The source that the change was requested from.

Configuration config_network_change Network configuration was modified by user Network related configuration change successfully takes place.
%username% from source %src% Where:
32 %username% = The username that made the configuration change.
%src% = The source that the change was requested from.

Configuration config_network_change_failed Failed to modify network configuration by user Network configuration change is rejected.
%username% from source %src%. Error=%err% Where:
33 %username% = The username that requested the configuration change.
%src% = The source that the change was requested from.

Discovery discovery_generic_error Discovery agent failure on %src%. Error=%err% Discovery strategy agents that are integrated with the CAT Topology service in response to detected discovery errors.
This is a generic event that is fired when there is not a more specific discovery error.

34 Where:
%src% = The source of the discovery error.
%err% = An error code that indicates the source of the underlying error.

System sys_firmware_update_failed Failed to update firmware by %username% at %src%. Product firmware update fails.
Error=%err% Where:
%username% = The username of the identity that attempted the firmware update.
35 %src% = The source that originated the firmware update.
%err% = The error code that indicates the underlying cause of the failure.

System sys_firmware_update_started Firmware update started by %username% at %src% Product firmware update begins.
Where:
36 %username% = The username of the identity that performed the firmware update.
%src% = The source that originated the firmware update.

System sys_firmware_update_completed Firmware updated by %username% at %src% Product firmware update completes successfully.
Where:
37 %username% = The username of the identity that performed the firmware update.
%src% = The source that originated the firmware update.

System sys_powerdown Powered down by %username% Product is requested to power down.

38 Where:
%username% = The username of the identity that initiated the power down.
39 System sys_powerup Powered up Product is powered up.
System sys_reset %type% reset by %username% from %src% Product is successfully requested to be restarted.
Where:
%type% = The type of the reset that was requested. This may be "Power cycle", "Factory", "Factory without
40 communications", "Secure", or a product specific value.
%username% = The username of the identity that initiated the reset.
%src% = The source the reset request was initiated from.

System sys_reset_failed %type% reset by %username% from %src% failed. Product is requested to be restarted by the request fails or is rejected.
Error=%err% Where:
%type% = The type of the reset that was requested. This may be "Power cycle", "Factory", "Factory without
communications", "Secure", or a product specific value.
41 %username% = The username of the identity that initiated the reset.
%src% = The source the reset request was initiated from.
%err% = The error code the identifies the underlying cause of the error.

System sys_powerloss Power lost Fired when a product loses power.

This event can be fired immediately upon detection of power loss, if the product still has energy to issue the event.
42 Alternatively, if the product can detect a previous power loss during its power up sequence, it may fire this event prior to
firing its sys_powerup event.

System sys_clock_start Clock started by %username% System clock is started.

43 Where:
%username% = The username of the identity that started the system clock
 A B C D
System sys_clock_stop Clock stopped by %username% System clock is stopped.
44 Where:
%username% = The username of the identity that stopped the system clock
System sys_clock_sync_lost Clock synchronization with %source% has been lost The protocol that synchronizes the product clock with a time source authority has failed.
45 Where:
%src% = The time source authority that the product clock would synchronize with.
System sys_clock_synced Clock is now synchronized with %source% The protocol that synchronizes the product clock with a time source authority has been established.
46 Where:
%src% = The time source authority that the product clock is synchronized with.
System sys_clock_time_change Clock time changed by %username% The product clock has been changed by a mechanism other than the typical time synchronization protocol.
47 Where:
%username% = The user name of the identity that changed the time.
Log log_config_change Log service configuration changed by %username% A configuration change was made to the products log system.
from %src% Where:
48 %username% = The username of the identity that made the change
%src% = The source that originated the configuration change.

Log log_config_change_failed Failed to change log service configuration by A configuration change to the product's log system was requested but could not bechanged.
%username% from %src%. Error=%err% Where:
%username% = The username of the identity that made the change.
49 %src% = The source that originated the configuration change.
%err% = The error code that indicates the underlying cause of the failure.

Log log_dtls_client_session_failed Failed to start secure datagram connection with log A DTLS session cannot be created with the Syslog collector.
service at %dst%. Error=%err% Where:
50 %dst% = The destination Syslog collector.
%err% = The error code that indicates the underlying cause of the failure.

Log log_dtls_client_session_started Started secure datagram connection with log service at A DTLS session is successfully established with the Syslog collector.
51 %dst% Where:
%dst% = The destination Syslog collector.
Log log_messages_overrun %count% log messages could not be sent and have Event messages could not be delivered to a destination.
been lost. Error=%err%
The event can also occur when a logging subsystem must overwrite unread messages due to a capacity limit.
This may occur due to an event flood that exceeds the buffering resources of the product or because a prolonged service
outage that prevents events from being delivered.
52
Where:
%count% = The number of events that haveen been dropped.
%err% = The error code that identifies the underlying root cause that the messages were dropped.

Log log_tcp_client_session_failed Failed to start connection with log service at %dst%. A TCP session cannot be created with the Syslog collector.
Error=%err% Where:
53 %dst% = The destination Syslog collector.
%err% = The error code that indicates the underlying cause of the failure.

Log log_tcp_client_session_started Started connection with log service at %dst% A TCP session is successfully established with the Syslog collector.
54 Where:
%dst% = The destination Syslog collector.
Log log_tls_client_session_failed Failed to start secure connection with log service at A TLS session cannot be created with the Syslog collector.
%dst%. Error=%err% Where:
%dst% = The destination Syslog collector.
55 %err% = The error code that indicates the underlying cause of the failure.

Log log_tls_client_session_started Started secure connection with log service at %dst% A TLS session is successfully established with the Syslog collector.
56 Where:
%dst% = The destination Syslog collector.
Log log_storage_almost_full Log storage at %src% is near capacity A local logging capacity has reached 80% of its total capacity.
57 Where:
%src% = The source that is nearing capacity.
Log log_unknown_event An undefined event was generated. ID=%id% Context= The product attempts to originate an event, but no definition of the event exists.
%ctx% Where:
58 %id% = The numeric identifier of the event that the product attempts to generate.
%ctx% = A formatted string of the context values associated with the event.
 A B C D
Log log_user_read %name% log was read by %username% A user was granted access to read a log.
Where:
%name% = The name of the log that access was granted to. Note that if the product has a single log, then this should be
59 provided as name "system".
%username% = The username of the identity that was granted access.

Log log_started %name% log was started by %username% A user starts the logging process of the product.
Where:
%name% = The name of the log that access was started. Note that if the product has a single log, then this should be
60 provided as name "system".
%username% = The username of the identity that started the log.

Log log_stopped %name% log was stopped by %username% A user stops the logging process of the product.
Where:
%name% = The name of the log that access was stopped. Note that if the product has a single log, then this should be
61 provided as name "system".
%username% = The username of the identity that stopped the log.

Log log_config_change Log service configuration changed by %username% A configuration change was made to the products log system.
from %src% Where:
62 %username% = The username of the identity that made the change
%src% = The source that originated the configuration change.

Log log_config_change_failed Failed to change log service configuration by A configuration change to the product's log system was requested but could not bechanged.
%username% from %src%. Error=%err% Where:
%username% = The username of the identity that made the change.
63 %src% = The source that originated the configuration change.
%err% = The error code that indicates the underlying cause of the failure.

Log log_dtls_client_session_failed Failed to start secure datagram connection with log A DTLS session cannot be created with the Syslog collector.
service at %dst%. Error=%err% Where:
64 %dst% = The destination Syslog collector.
%err% = The error code that indicates the underlying cause of the failure.

Log log_dtls_client_session_started Started secure datagram connection with log service at A DTLS session is successfully established with the Syslog collector.
65 %dst% Where:
%dst% = The destination Syslog collector.
Log log_messages_overrun %count% log messages could not be sent and have Event messages could not be delivered to a destination.
been lost. Error=%err%
The event can also occur when a logging subsystem must overwrite unread messages due to a capacity limit.
This may occur due to an event flood that exceeds the buffering resources of the product or because a prolonged service
outage that prevents events from being delivered.
66
Where:
%count% = The number of events that haveen been dropped.
%err% = The error code that identifies the underlying root cause that the messages were dropped.

Log log_tcp_client_session_failed Failed to start connection with log service at %dst%. A TCP session cannot be created with the Syslog collector.
Error=%err% Where:
67 %dst% = The destination Syslog collector.
%err% = The error code that indicates the underlying cause of the failure.

Log log_tcp_client_session_started Started connection with log service at %dst% A TCP session is successfully established with the Syslog collector.
68 Where:
%dst% = The destination Syslog collector.
Log log_tls_client_session_failed Failed to start secure connection with log service at A TLS session cannot be created with the Syslog collector.
%dst%. Error=%err% Where:
69 %dst% = The destination Syslog collector.
%err% = The error code that indicates the underlying cause of the failure.

Log log_tls_client_session_started Started secure connection with log service at %dst% A TLS session is successfully established with the Syslog collector.
70 Where:
%dst% = The destination Syslog collector.
Log log_storage_almost_full Log storage at %src% is near capacity A local logging capacity has reached 80% of its total capacity.
71 Where:
%src% = The source that is nearing capacity.
 A B C D
Log log_unknown_event An undefined event was generated. ID=%id% Context= The product attempts to originate an event, but no definition of the event exists.
%ctx% Where:
72 %id% = The numeric identifier of the event that the product attempts to generate.
%ctx% = A formatted string of the context values associated with the event.

Log log_user_read %name% log was read by %username% A user was granted access to read a log.

The event occurs the first time the user is granted access to a log for the purpose of reading, regardless of how many log
records the user is granted access to. The event should occur again if the read session is closed and subsequently reopned.

Where:
73 %name% = The name of the log that access was granted to. Note that if the product has a single log, then this should be
provided as name "system".
%username% = The username of the identity that was granted access.

Log log_started %name% log was started by %username% A user starts the logging process of the product.
Where:
%name% = The name of the log that access was started. Note that if the product has a single log, then this should be
74 provided as name "system".
%username% = The username of the identity that started the log.

Log log_stopped %name% log was stopped by %username% A user stops the logging process of the product.
Where:
%name% = The name of the log that access was stopped. Note that if the product has a single log, then this should be
75 provided as name "system".
%username% = The username of the identity that stopped the log.