What causes KUKA Robot alarm KRC0967?

Attempting to access a position component on a non-position variable (e.g., REAL, INT, BOOL instead of POS). Incorrect syntax when referencing position sub-components (X, Y, Z, A, B, C, E1-E6). Using an undefined or incorrectly declared position variable in motion commands. Type mismatch between expected position format and the actual variable type passed as parameter. Corrupted or incomplete position data structure in memory or program logic.

How do I fix KUKA Robot alarm KRC0967?

1. Verify the variable declaration in the KRL program matches the expected POS data type (e.g., DECL AXIS homePos or DECL FRAME target) 2. Check the syntax of position component access - ensure proper use of dot notation (variable.X, variable.Y, etc.) 3. Confirm that position variables are properly initialized before use in motion commands 4. Review the function or motion instruction call to ensure correct parameter types are being passed 5. Search the program for any variable reassignments that may have changed the data type from POS to another type 6. Consult the KRL source code listing and cross-reference variable definitions against their usage in the program

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0967

KUKA Robot KRC0967 - NOT A POS COMPONENT 2304

This alarm indicates that a KRL program object or variable referenced in the code is not a valid position (POS) data type component. The system expected a position-related component but encountered an incompatible data type or malformed position structure instead.

KUKA RobotSystemBasic

KRC0967

KUKA Robot KRC0967 - NOT A POS COMPONENT 2304

NOT A POS COMPONENT 2304

Common Causes

Attempting to access a position component on a non-position variable (e.g., REAL, INT, BOOL instead of POS)
Incorrect syntax when referencing position sub-components (X, Y, Z, A, B, C, E1-E6)
Using an undefined or incorrectly declared position variable in motion commands
Type mismatch between expected position format and the actual variable type passed as parameter
Corrupted or incomplete position data structure in memory or program logic

Troubleshooting Steps

1Verify the variable declaration in the KRL program matches the expected POS data type (e.g., DECL AXIS homePos or DECL FRAME target)
2Check the syntax of position component access - ensure proper use of dot notation (variable.X, variable.Y, etc.)
3Confirm that position variables are properly initialized before use in motion commands
4Review the function or motion instruction call to ensure correct parameter types are being passed
5Search the program for any variable reassignments that may have changed the data type from POS to another type
6Consult the KRL source code listing and cross-reference variable definitions against their usage in the program

Seeing Multiple Alarms?

Seeing another alarm with this one? Enter the code.

Get machine-aware diagnosis

AxisMD logs alarms against your actual machines, tracks patterns, and gives AI context your manual doesn't have.

Start free

Was this guide helpful?

Always verify with your machine manual or a certified technician before performing service procedures.