What causes KUKA Robot alarm KRC0914?

Using a non-boolean variable or expression in an IF, WHILE, or UNTIL condition statement. Attempting to assign a non-boolean value to a boolean variable without proper casting. Missing or incorrect logical operators (AND, OR, NOT) in conditional expressions. Passing a non-boolean argument to a function parameter that expects BOOL type. Using arithmetic or string expressions where boolean logic is required.

How do I fix KUKA Robot alarm KRC0914?

1. Review the line of code referenced in the alarm message and identify the expression causing the type mismatch 2. Verify that all conditional statements (IF, WHILE, UNTIL) contain proper boolean expressions with relational operators (==, !=, , =) 3. Check variable declarations to ensure boolean variables are properly typed as BOOL in KRL 4. Add explicit type casting or logical operators to convert the expression to boolean format if necessary 5. Consult the KRL program's function signatures to confirm parameter types match the arguments being passed 6. Recompile the program after corrections and verify the alarm no longer appears during execution

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0914

KUKA Robot KRC0914 - EXPRESSION NOT EQUAL TO BOOL 2251

This alarm indicates a type mismatch in KRL program logic where an expression is being evaluated in a context that requires a BOOL (boolean) data type, but the expression does not evaluate to a boolean value. The compiler or runtime cannot implicitly convert the <object name> expression to a BOOL, preventing program execution.

KUKA RobotSystemBasic

KRC0914

KUKA Robot KRC0914 - EXPRESSION NOT EQUAL TO BOOL 2251

EXPRESSION NOT EQUAL TO BOOL 2251

Common Causes

Using a non-boolean variable or expression in an IF, WHILE, or UNTIL condition statement
Attempting to assign a non-boolean value to a boolean variable without proper casting
Missing or incorrect logical operators (AND, OR, NOT) in conditional expressions
Passing a non-boolean argument to a function parameter that expects BOOL type
Using arithmetic or string expressions where boolean logic is required

Troubleshooting Steps

1Review the line of code referenced in the alarm message and identify the expression causing the type mismatch
2Verify that all conditional statements (IF, WHILE, UNTIL) contain proper boolean expressions with relational operators (==, !=, <, >, <=, >=)
3Check variable declarations to ensure boolean variables are properly typed as BOOL in KRL
4Add explicit type casting or logical operators to convert the expression to boolean format if necessary
5Consult the KRL program's function signatures to confirm parameter types match the arguments being passed
6Recompile the program after corrections and verify the alarm no longer appears during execution

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.