What causes KUKA Robot alarm KRC0887?

Assigning a non-STAT_T variable to a STAT_T variable without proper casting or conversion. Using an incompatible data type in a function call that expects STAT_T parameter. Incorrect variable declaration missing the STAT_T type specification. Attempting to perform operations between STAT_T and primitive types (INT, REAL, BOOL) without conversion. Using a structure or custom type where STAT_T is explicitly required by the instruction.

How do I fix KUKA Robot alarm KRC0887?

1. Review the KRL source code at the line indicated in the error message for type mismatches 2. Verify that all variables assigned to STAT_T types are properly declared with STAT_T data type 3. Check function signatures and ensure arguments passed match the expected STAT_T parameter types 4. Use explicit type conversion functions if mixing STAT_T with other data types in expressions 5. Consult the KRL variable declarations section to confirm STAT_T definitions and structures are correct 6. Recompile the program after corrections and verify the alarm no longer appears during syntax checking

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0887

KUKA Robot KRC0887 - EXPRESSION TYPE NOT EQUAL TO STAT_T 2223

This alarm occurs when a KRL expression type does not match the expected STAT_T data type during program compilation or execution. The system detected a type mismatch where a value or variable of one type was used in a context requiring STAT_T (status/state type) compatibility.

KUKA RobotSystemBasic

KRC0887

KUKA Robot KRC0887 - EXPRESSION TYPE NOT EQUAL TO STAT_T 2223

EXPRESSION TYPE NOT EQUAL TO STAT_T 2223

Common Causes

Assigning a non-STAT_T variable to a STAT_T variable without proper casting or conversion
Using an incompatible data type in a function call that expects STAT_T parameter
Incorrect variable declaration missing the STAT_T type specification
Attempting to perform operations between STAT_T and primitive types (INT, REAL, BOOL) without conversion
Using a structure or custom type where STAT_T is explicitly required by the instruction

Troubleshooting Steps

1Review the KRL source code at the line indicated in the error message for type mismatches
2Verify that all variables assigned to STAT_T types are properly declared with STAT_T data type
3Check function signatures and ensure arguments passed match the expected STAT_T parameter types
4Use explicit type conversion functions if mixing STAT_T with other data types in expressions
5Consult the KRL variable declarations section to confirm STAT_T definitions and structures are correct
6Recompile the program after corrections and verify the alarm no longer appears during syntax checking

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.