Allen-Bradley Logix 5000

The scanner did not receive a block-transfer response from the block-transfer module within 3.5 seconds of the request. This indicates a communication timeout, resulting in an unknown error.

The checksum received from the read response did not match the checksum of the data stream. This indicates data corruption or a transmission error during the block-transfer read operation.

The scanner requested either a read or write operation, but the block-transfer module responded with the opposite type of operation. This indicates a protocol mismatch or incorrect module behavior.

The scanner requested a specific data length, but the block-transfer module responded with a different length. This indicates an inconsistency in the data transfer size.

The scanner received a response from the block-transfer module indicating that the write request failed. This means the data could not be successfully written to the module.

The scanner was not configured to communicate with the rack that contains the block-transfer module. This configuration error prevents proper communication with the module.

The specified logical slot is not available for the given rack size. This indicates a mismatch between the configured slot and the physical or logical capacity of the rack.

A block-transfer request is currently in progress, and a response is required before another request can be initiated. This indicates an attempt to start a new transfer before the previous one completed.

The size of the block-transfer request is not consistent with valid block-transfer size requirements. This indicates an incorrect payload size for the transfer operation.

The type of block-transfer request is not consistent with the expected BT_READ or BT_WRITE types. This indicates an incorrect command type was issued for the block transfer.

This fault occurs when a 1769 power supply is connected directly to the controller's 1768 CompactBus with an invalid configuration, or if the 1768 power supply powering the controller has failed. This affects the controller's power integrity.

An unpartnered controller was identified in the new primary chassis following a switchover event. This indicates a configuration mismatch in the redundant system.

Immediately after a switchover, the keyswitch positions of the primary and secondary controllers are mismatched. Specifically, the old primary is in Program mode and the new primary is in Run mode.

The safety task has not completed within its specified period of time. This can be due to a program error causing an infinite loop, the program's complexity exceeding execution speed, a higher priority task blocking it, or the safety partner being removed.

An error has been detected within a routine of the safety task. This indicates an issue with the user-program logic that requires correction.

The required safety partner controller or module is not present or detected. The system requires a compatible safety partner to operate correctly.

The safety partner is not available, possibly due to a connection issue or it being offline. The system requires a compatible safety partner to operate correctly.

The installed safety partner hardware is not compatible with the current system configuration. Ensure the correct hardware is installed for proper operation.

The firmware revision of the installed safety partner is not compatible with the current system. Ensure the safety partner has the correct and compatible firmware version.

The safety logic is invalid, which can be caused by a logic mismatch between the primary controller and safety partner, a watchdog timeout, or memory corruption. This prevents the safety task from executing correctly and may require re-downloading the program.

The Coordinated System Time Master (CST) device required for system synchronization was not found or is not configured. This prevents proper time coordination across the system.

A nonrecoverable fault has occurred within the safety partner controller, indicating a serious issue. If the fault persists after clearing and re-downloading, hardware replacement may be necessary.

The internal temperature of the controller module has risen above its safe operating limit, indicating potential overheating conditions. This can lead to module shutdown if not addressed.

This fault indicates that the controller has successfully recovered from an automatic shutdown caused by exceeding its internal temperature threshold. The module's temperature has decreased to a suitable level, re-enabling controller voltages.

The CIP Motion drive failed to initialize correctly. Specific details about the initialization fault are available in the Initialization Faults Attributes, which should be consulted for corrective action.

A manufacturer-specific Absolute Position Recovery (APR) fault has occurred, and the absolute position of the axis cannot be recovered. Consult manufacturer-specific attributes for diagnostic information.

A fault specific to the Guard Motion safety function has occurred. This fault is only applicable when using a drive with Guard Safety functionality and indicates a safety integrity issue.

A manufacturer-specific initialization fault has occurred on the CIP Motion drive. Further details are required from manufacturer-specific attributes (CIP Initialization Fault - Mfg attributes) to determine the corrective action.

The Physical Axis Fault bit is active, indicating a fault on the physical axis. More information about the specific fault can be found in the CIP Axis Fault attributes.

The Physical Axis Fault bit is active due to a manufacturer-specific axis fault. Further details about the specific fault are required from manufacturer-specific attributes (CIP Initialization Fault - Mfg attributes).

A general motion fault has occurred within the system. More specific information to diagnose the issue is available in the Motion Fault attribute and Motion Fault bits.

A fault has occurred in a CIP Motion Drive, typically affecting all axes associated with the module and causing them to shut down. This requires reconfiguring the motion module.

A fault has occurred within a motion group, typically affecting all axes associated with that group. This requires reconfiguring the entire motion subsystem.

A fault occurred during the configuration of a CIP Motion Drive, often after an unsuccessful attempt to update an axis configuration attribute. This indicates an issue with the configuration parameters.

An Absolute Position Recovery (APR) fault has occurred, and the absolute position of the axis cannot be recovered. This impacts the accuracy and safety of motion control.

A required license is either missing or has expired during the controller's transition to run or test mode. This prevents the controller from entering an operational state.

A 'Bus off' condition is detected, indicating that the connections between the controller and the I/O modules are broken. This prevents communication and operation of connected I/O.

The current RPI (Requested Packet Interval) update of an I/O module overlaps with its previous RPI update. This indicates that the update rate is too fast for the module to handle, potentially causing data integrity issues.

A request could not be completed because the situation changed during a multipacket operation, indicating a timing or state issue. The system's state altered unexpectedly during a communication sequence.

The data or file being processed is too large to handle, or system memory is unavailable to complete the requested operation. This indicates a resource limitation.

The target processor is unable to put the requested information into packets for transmission. This indicates a communication or internal processing issue on the target device.

Access to the requested function or resource was denied due to insufficient privileges. This is a security or access control related error.

The function requested is not available on the device or in the current operational mode. This could indicate an incorrect command or an unsupported feature.

The submitted request is redundant, meaning it duplicates a previous or active request. This fault indicates an unnecessary or repeated command.

The command sent to the device cannot be executed, possibly due to the current state or invalid parameters. The device is unable to process the instruction.

An overflow condition has occurred, specifically noted as a histogram overflow. For PLC-3 systems, this indicates a histogram overflow that has exceeded its capacity.

Access to the requested resource or operation is denied. This indicates a general access restriction.

The data type requested does not match the data available, indicating a type conversion or definition error. This prevents proper data handling.

The parameters provided with the command are incorrect or invalid for the requested operation. Review the command syntax and parameter values.

An address reference exists that points to a memory area that has been deleted. This indicates an invalid memory access attempt.

The command execution failed for an unknown reason. This generic error indicates an unhandled exception during command processing.

An error occurred during the conversion of data from one format or type to another. This prevents correct data processing.

The scanner is not available to communicate with a 1771 rack adapter. This disrupts I/O communication with the specified rack.

The adapter is not available to communicate with the module. This prevents the module from sending or receiving data.

The 1771 module responded with an invalid message or data. This indicates a communication protocol issue or a fault within the 1771 module itself.

A duplicate label has been detected in the program or configuration. This usually indicates a naming conflict that needs to be resolved.

The file is currently in use by an owner and cannot be accessed or modified. This indicates a resource lock.

Someone is currently downloading or editing online, making the program unavailable for other operations. This is a temporary access restriction during programming activities.

The disk file is write-protected or otherwise not accessible, specifically when operating offline. This prevents modifications or updates to the file.

The disk file is currently being used by another application, preventing an update when operating offline. This indicates a conflict with another software process.