Kuka KRC2 KSS System Message

A short circuit has been detected at either outputs 1 to 8 or outputs 9 to 16. This will result in maximum braking of the system.

This is a follow-up message to the 'POST Error: Parameter table checksum fault' status message, indicating an issue with the parameter table integrity. The fault leads to maximum braking and inhibition of all active commands.

This is a follow-up message to the 'POST Error: Encoder FPGA loopback fault' status message, indicating an issue with the encoder's FPGA loopback. The fault leads to maximum braking and inhibition of all active commands.

This is a follow-up message to the 'Power board FPGA fault' status message. It indicates a critical error on the power board's FPGA, leading to maximum braking and inhibition of all active commands.

This is a follow-up message to the 'POST Error: A/D fault' status message. It indicates an analog-to-digital converter fault, resulting in maximum braking and inhibition of all active commands.

This is a follow-up message to the 'POST Error: A/D offset fault' status message. It indicates an offset error in the analog-to-digital converter, leading to maximum braking and inhibition of all active commands.

This is a follow-up message to the 'POST Error: Invalid parameter fault' status message. It indicates an invalid parameter fault, resulting in maximum braking and inhibition of all active commands.

This occurs during program or command execution when the KRL program or command has insufficient task stack available for execution. This will cause ramp-down braking and inhibit all active commands.

Too many messages have been generated cyclically, indicating a potential system overload or rapid fault cycling. This will result in ramp-down braking and inhibit all active commands.

The intermediate circuit current monitoring safeguard has triggered due to an overcurrent condition. This will cause maximum braking and inhibit all active commands.

The brake cable monitoring device has detected a short-circuit, overloading, or a break in the brake cable connection. This will result in path-maintaining braking and stop program execution.

The internal servo output stage is not ready due to an undervoltage condition. This will cause maximum braking and inhibit all active commands.

This is a follow-up message to the 'FAILURE OF MOTOR TEMPERATURE SENSOR' status message, indicating a sensor malfunction.

This is a follow-up message to the 'WRONG DRIVES PARAMETER' status message, indicating an incorrect drive parameter setting.

This is a follow-up message to the 'ERROR SYNC. INPUT DRIVE' status message, indicating an error with the drive's synchronization input.

This is a follow-up message to the 'SYNCHRONISATION ERROR DRIVE' status message, indicating a synchronization error within the drive.

This is a follow-up message to the '... WITHOUT POWER' status message, indicating that the specified axis is not receiving power.

A channel in the safety loop has failed, or more than one enabling switch has been pressed simultaneously. This will cause path-maintaining braking and inhibit all active commands.

The brake has excessive wear or is defective. This results in maximum braking and inhibits all active commands. Under certain circumstances, it may not be possible to brake the axis.

A fault has occurred in the control loop. Possible causes include interchanged motor cables between two axes, an error in axis assignment, a defective power module, or an unmastered resolver. This fault causes maximum braking and inhibits all active commands.

The safety fence is currently open, which prevents safe operation of the equipment.

The trace has been incorrectly defined in the 'TRACE.DEF' file, preventing proper trace functionality.

The 'TRACE.DEF' file could not be read at the start of trace recording, preventing the recording from being carried out.

An error or malfunction has occurred in data transmission on the Interbus. This will stop data transmission on the Interbus and reset all outputs.

A malfunction has occurred in the specified Interbus module. This condition will cause the outputs to be reset.

There is a battery fault in the encoder of the specified axis. This is an acknowledgement message for the encoder battery fault.

The fan in the cabinet is defective, which can lead to overheating of the hardware within the cabinet.

This is a cyclic follow-up message to the 'Encoder cable failure ext. posinput' status message. It indicates a failure in the external position input encoder cable, resulting in path-maintaining braking and inhibition of all active commands, with the $ALARM_STOP 0 signal activated.

The IPO_MODE TCP was set while 'MDR base' was active. This configuration is not permitted and will cause the robot to stop.

This is a follow-up message to the 'Force controller error' indicating that the force sensor signal does not match the motion. Error type 1: Actual force changes but position remains constant. Error type 2: Position changes but actual force remains constant. Error type 3: The gun opens further than the position corresponding to FORCE_LIM. These monitoring functions are only active during force control, resulting in dynamic braking, inhibition of active commands, and the 'ALARM_STOP' signal at level 0.

A battery fault has been detected in the encoder of the specified axis, indicating a need for battery replacement.

The fan in the cabinet is defective. This condition can lead to overheating of the hardware within the cabinet.

An error occurred while reading the configuration file in the MADA directory for a force-controlled axis. Error codes include: 1 (File could not be opened), 2 (Missing entry), or 3 (Inconsistent data). This fault prevents force control from being activated.

Force mode is activated, but the RDC (Robot Drive Controller) does not have the required plug-on card for multiplex operation. Consequently, force mode will not be activated.

The specified parameter is invalid. This condition results in maximum braking and inhibits all active commands.

A mismatch has been detected in the firmware versions between components. This will cause maximum braking and inhibit all active commands.