What causes KUKA Robot alarm KRC0909?

Attempting to assign a non-POS data type (REAL, INT, BOOL, etc.) to a POS variable without proper conversion. Passing an incompatible variable type as a parameter to a function expecting POS data type. Using an undefined or incorrectly initialized variable in a position-related operation. Type mismatch in array element access where a POS array element is being assigned a non-POS value. Incorrect syntax in position declaration or initialization, resulting in wrong data type inference.

How do I fix KUKA Robot alarm KRC0909?

1. Navigate to line 2246 in the KRL program source code and identify the statement causing the type mismatch 2. Verify the data type of the right operand variable using the variable declaration or debugger inspection 3. Ensure the right operand is declared as POS type or convert it using appropriate KUKA conversion functions (e.g., POS(), Frame2Pos()) 4. Check function signatures and parameter definitions to confirm POS type is expected for that parameter position 5. Use explicit type casting or the correct KUKA coordinate transformation functions to ensure compatibility 6. Recompile the KRL program and test execution to confirm the type mismatch is resolved

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0909

KUKA Robot KRC0909 - RIGHT OPERAND NOT EQUAL TO POS, FRAME 2246

This alarm occurs when a KRL program attempts to perform an operation where the right operand is not compatible with or cannot be cast to a POS (position) data type at line 2246. The runtime type mismatch prevents the instruction from executing, typically during assignment, comparison, or parameter passing operations.

KUKA RobotSystemBasic

KRC0909

KUKA Robot KRC0909 - RIGHT OPERAND NOT EQUAL TO POS, FRAME 2246

RIGHT OPERAND NOT EQUAL TO POS, FRAME 2246

Common Causes

Attempting to assign a non-POS data type (REAL, INT, BOOL, etc.) to a POS variable without proper conversion
Passing an incompatible variable type as a parameter to a function expecting POS data type
Using an undefined or incorrectly initialized variable in a position-related operation
Type mismatch in array element access where a POS array element is being assigned a non-POS value
Incorrect syntax in position declaration or initialization, resulting in wrong data type inference

Troubleshooting Steps

1Navigate to line 2246 in the KRL program source code and identify the statement causing the type mismatch
2Verify the data type of the right operand variable using the variable declaration or debugger inspection
3Ensure the right operand is declared as POS type or convert it using appropriate KUKA conversion functions (e.g., POS(), Frame2Pos())
4Check function signatures and parameter definitions to confirm POS type is expected for that parameter position
5Use explicit type casting or the correct KUKA coordinate transformation functions to ensure compatibility
6Recompile the KRL program and test execution to confirm the type mismatch is resolved

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.