Kuka KSS 8.3 Operating & Programming Manual

16 fault codes documented

0x1011

Error loading high precision model (Robot moved)

The positionally accurate robot model could not be loaded during an update process because the robot moved unexpectedly. Any movement during this critical operation can corrupt the model loading, requiring a retry.

0x1012

Error loading high precision model (Robot moved during loading)

The positionally accurate robot model could not be accepted during its loading process because the robot moved. This unexpected motion interferes with the integrity of the model integration, preventing successful acceptance.

0x1013

Error loading high precision model (Memory allocation failure)

The positionally accurate robot model could not be accepted because the system was unable to allocate the necessary memory. This prevents the model from being initialized and becoming operational.

1100

Stopped {(Axis number)}

This message indicates that an axis, specified by {(Axis number)}, has stopped, likely triggered by the standstill monitoring function. This fault occurs if the robot enters an unexpected standstill state or if standstill conditions are not met during a programmed move.

1105

Positioning monitoring {(Axis number)}

This message indicates that positioning monitoring has been triggered for a specific axis, {(Axis number)}. This fault occurs when the actual position of the axis deviates excessively from its commanded target during a positioning move, implying an issue with the axis's ability to reach or maintain its target.

1422

Specific Runtime Error (Program)

This numeric code identifies a specific runtime error message that can occur during program execution. When triggered, the system variable $ERR is populated with detailed information, including this message number ($ERR.number) and the line of code that caused it ($ERR.line_nr). This particular error can be programmatically suppressed using the ON_ERROR_PROCEED statement in conjunction with SWITCH ... ENDSWITCH logic. If not suppressed, the error message would typically be displayed to the user.

1446

Value assignment inadmissible

An invalid or out-of-range value was assigned to a system variable such as $SPEED.ORI1 (e.g., ≤ 0.0 or >$SPEED_MA.ORI1), or to system objects like $BASE or $TOOL. This prevents the system from correctly processing the assigned parameters, potentially halting program execution.

26009

Motor blocked ({Drive})

The motor associated with the specified drive ({Drive}) has been detected as blocked. This indicates a physical obstruction, mechanical binding, or an issue preventing the motor from rotating freely, potentially causing excessive current draw and motor stress.

26024

Max. following error exceeded ({Drive})

The deviation between the commanded position and the actual position for the specified drive ({Drive}) has exceeded the maximum allowable limit. This often occurs in torque mode operations if regular monitoring functions are not appropriately deactivated, or due to external mechanical resistance.

272

No robot number programmed

The file ROBOTINFO.XML is missing on the RDC (Robot Data Controller), potentially after an exchange of the RDC memory chip. This prevents the robot from being properly identified and configured, leading to operational issues.

276

Wrong machine data for this robot type

The machine data currently loaded in the robot controller does not correspond to the specific type of robot. Moving the robot is not permitted in this state, as it could lead to incorrect operation, unexpected behavior, or damage.

2972

Checksum error File %1

An error has been detected in the file indicated by '%1', likely due to data corruption or an incorrect file version. As a result, the parameters within this file cannot be applied by the system.

2973

Precision Robot Model Parameterfile wrong Serial-number

The XPid file, specifically PREC_ROBXXXXXXXXXX.XML, contains a serial number that does not match the robot's actual serial number. This mismatch prevents the positionally accurate robot model from being correctly initialized, impacting precision operations.

2974

Precision robot: Model parameter not consistent with machine data

The machine data loaded on the robot controller has been modified, resulting in an inconsistency with the positionally accurate robot model. This state prevents the precision robot model from being initialized correctly.

384

Not enough memory: Cannot load precision robot model

The system failed to create the positionally accurate robot model due to insufficient memory capacity. This issue prevents the robot from operating with enhanced positioning accuracy, affecting tasks that require high precision.

417

Absolute accuracy model not active

The positionally accurate robot model has been deactivated. This status means the robot is not utilizing its precision model, which can impact applications requiring high absolute accuracy.