What causes KUKA Robot alarm KRC0888?

Using a complex data type (struct, array, or custom type) where a primitive type is required. Attempting to assign or pass a non-primitive return value from a function to a primitive variable. Type mismatch in conditional statements, function parameters, or array indices. Incorrectly accessing object properties or array elements that return incompatible types. Missing explicit type casting or conversion for expressions in arithmetic or logical operations.

How do I fix KUKA Robot alarm KRC0888?

1. Review the line of code referenced in the alarm message and identify the expression causing the type mismatch 2. Verify the data type of all variables, function return values, and expressions involved in the statement 3. Check if explicit type casting is needed using KUKA KRL conversion functions (INT(), REAL(), etc.) 4. Ensure function parameters match expected primitive types and that return types are compatible 5. Consult the KRL type system documentation to confirm supported type conversions and implicit casting rules 6. Modify the expression to use only primitive types or add appropriate type conversion functions before recompiling

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0888

KUKA Robot KRC0888 - EXPRESSION TYPE NOT EQUAL TO INT, REAL, CHAR, BOOL, ENUM 2224

This alarm occurs when a KRL expression is used in a context that requires a primitive data type (INT, REAL, CHAR, BOOL, or ENUM), but the expression evaluates to an incompatible or unsupported data type. The compiler cannot perform implicit type conversion for the expression at the specified location in the program.

KUKA RobotSystemBasic

KRC0888

KUKA Robot KRC0888 - EXPRESSION TYPE NOT EQUAL TO INT, REAL, CHAR, BOOL, ENUM 2224

EXPRESSION TYPE NOT EQUAL TO INT, REAL, CHAR, BOOL, ENUM 2224

Common Causes

Using a complex data type (struct, array, or custom type) where a primitive type is required
Attempting to assign or pass a non-primitive return value from a function to a primitive variable
Type mismatch in conditional statements, function parameters, or array indices
Incorrectly accessing object properties or array elements that return incompatible types
Missing explicit type casting or conversion for expressions in arithmetic or logical operations

Troubleshooting Steps

1Review the line of code referenced in the alarm message and identify the expression causing the type mismatch
2Verify the data type of all variables, function return values, and expressions involved in the statement
3Check if explicit type casting is needed using KUKA KRL conversion functions (INT(), REAL(), etc.)
4Ensure function parameters match expected primitive types and that return types are compatible
5Consult the KRL type system documentation to confirm supported type conversions and implicit casting rules
6Modify the expression to use only primitive types or add appropriate type conversion functions before recompiling

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.