What causes KUKA Robot alarm KRC0915?

Attempting to assign a non-POS data type (REAL, INT, BOOL, etc.) directly to a POS variable without proper conversion. Expression result dimensions or structure do not match the expected POS format (missing X, Y, Z, A, B, C components). Using an incompatible frame or coordinate system that cannot be converted to POS format. Referencing an undefined or incorrectly typed variable in the expression being assigned to POS. Syntax error in the expression causing incorrect type evaluation before assignment.

How do I fix KUKA Robot alarm KRC0915?

1. Locate frame 2252 in the KRL source code and identify the line performing the POS assignment 2. Verify that the expression on the right side of the assignment is actually a POS type or convertible to POS format 3. Check that all variables referenced in the expression are properly declared with compatible data types 4. Ensure the expression includes all required position components (X, Y, Z, A, B, C) if using direct structure initialization 5. Use explicit type casting or conversion functions (e.g., POS() constructor) if converting from other data types 6. Recompile the KRL program and verify syntax highlighting in the KUKA development environment for type errors

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0915

KUKA Robot KRC0915 - EXPRESSION NOT EQUAL TO POS, FRAME 2252

This alarm indicates a type mismatch or incompatibility when attempting to assign an expression result to a POS (position) variable at the specified frame location in the KRL program. The system detected that the expression being evaluated cannot be properly converted to or stored in the POS data type, preventing program execution.

KUKA RobotSystemBasic

KRC0915

KUKA Robot KRC0915 - EXPRESSION NOT EQUAL TO POS, FRAME 2252

EXPRESSION NOT EQUAL TO POS, FRAME 2252

Common Causes

Attempting to assign a non-POS data type (REAL, INT, BOOL, etc.) directly to a POS variable without proper conversion
Expression result dimensions or structure do not match the expected POS format (missing X, Y, Z, A, B, C components)
Using an incompatible frame or coordinate system that cannot be converted to POS format
Referencing an undefined or incorrectly typed variable in the expression being assigned to POS
Syntax error in the expression causing incorrect type evaluation before assignment

Troubleshooting Steps

1Locate frame 2252 in the KRL source code and identify the line performing the POS assignment
2Verify that the expression on the right side of the assignment is actually a POS type or convertible to POS format
3Check that all variables referenced in the expression are properly declared with compatible data types
4Ensure the expression includes all required position components (X, Y, Z, A, B, C) if using direct structure initialization
5Use explicit type casting or conversion functions (e.g., POS() constructor) if converting from other data types
6Recompile the KRL program and verify syntax highlighting in the KUKA development environment for type errors

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.