What causes KUKA Robot alarm KRC0897?

Attempting to compare or operate on a REAL variable with an INT or CHAR operand. Using a BOOL, AXIS, or FRAME variable in an arithmetic comparison operation. Mixing incompatible data types in conditional statements (IF, WHILE, etc.). Passing incorrect variable types to a function expecting INT or CHAR parameters. String manipulation or comparison with non-CHAR data types.

How do I fix KUKA Robot alarm KRC0897?

1. Navigate to line 2233 in the KRL source file and identify the operands involved in the comparison or operation 2. Verify the data type declarations of both operands using the variable declaration section or hover inspection 3. Convert operands to compatible types using explicit type casting (e.g., INT(), CHAR()) if type conversion is needed 4. Ensure both operands are declared as INT or CHAR types, or modify the operation logic to use compatible data types 5. Review the function signature if the alarm occurs at a function call to confirm parameter types match arguments 6. Recompile the KRL program and test the corrected code on the KUKA teach pendant or simulation environment

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0897

KUKA Robot KRC0897 - BOTH OPERANDS NOT EQUAL TO INT, CHAR 2233

This alarm occurs when a KRL program attempts a comparison or operation between two operands where at least one operand is not of INT or CHAR data type. The compiler or runtime environment expects both operands to be compatible INT or CHAR types for the operation at line 2233 in the referenced source file.

KUKA RobotSystemBasic

KRC0897

KUKA Robot KRC0897 - BOTH OPERANDS NOT EQUAL TO INT, CHAR 2233

BOTH OPERANDS NOT EQUAL TO INT, CHAR 2233

Common Causes

Attempting to compare or operate on a REAL variable with an INT or CHAR operand
Using a BOOL, AXIS, or FRAME variable in an arithmetic comparison operation
Mixing incompatible data types in conditional statements (IF, WHILE, etc.)
Passing incorrect variable types to a function expecting INT or CHAR parameters
String manipulation or comparison with non-CHAR data types

Troubleshooting Steps

1Navigate to line 2233 in the KRL source file and identify the operands involved in the comparison or operation
2Verify the data type declarations of both operands using the variable declaration section or hover inspection
3Convert operands to compatible types using explicit type casting (e.g., INT(), CHAR()) if type conversion is needed
4Ensure both operands are declared as INT or CHAR types, or modify the operation logic to use compatible data types
5Review the function signature if the alarm occurs at a function call to confirm parameter types match arguments
6Recompile the KRL program and test the corrected code on the KUKA teach pendant or simulation environment

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.