What causes KUKA Robot alarm KRC0737?

Attempting to convert an incompatible data type (e.g., AXIS, FRAME, or custom structure) to text without proper casting. Using a variable or parameter with wrong type in a string concatenation or text assignment operation. Passing an object of incorrect type to a function expecting TEXT or STRING type. Mismatched type declaration where the actual object type differs from the declared parameter type. Using an array or complex data structure where a primitive text type is required.

How do I fix KUKA Robot alarm KRC0737?

1. Review the KRL source code at the line indicated in the alarm message to identify which object is causing the type incompatibility 2. Verify the declared type of the object (@P1@) matches the expected type for the text operation being performed 3. Check function or subroutine signatures to confirm the correct parameter types are being passed 4. Use explicit type conversion functions (e.g., CHAR, INT_TO_CHAR, REAL_TO_CHAR) if converting complex types to text 5. Ensure all variable declarations in the program header match their usage throughout the KRL code 6. Recompile the program after making corrections and verify the syntax in the IDE before downloading to the robot controller

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0737

KUKA Robot KRC0737 - TYPENAME INCOMPATIBLE WITH TEXT 2073

This alarm indicates a type mismatch error where a KRL program object is being used with an incompatible data type in a text operation or string conversion context. The compiler or runtime cannot convert or match the specified object's type with the expected text/string type required by the operation.

KUKA RobotSystemBasic

KRC0737

KUKA Robot KRC0737 - TYPENAME INCOMPATIBLE WITH TEXT 2073

TYPENAME INCOMPATIBLE WITH TEXT 2073

Common Causes

Attempting to convert an incompatible data type (e.g., AXIS, FRAME, or custom structure) to text without proper casting
Using a variable or parameter with wrong type in a string concatenation or text assignment operation
Passing an object of incorrect type to a function expecting TEXT or STRING type
Mismatched type declaration where the actual object type differs from the declared parameter type
Using an array or complex data structure where a primitive text type is required

Troubleshooting Steps

1Review the KRL source code at the line indicated in the alarm message to identify which object is causing the type incompatibility
2Verify the declared type of the object (@P1@) matches the expected type for the text operation being performed
3Check function or subroutine signatures to confirm the correct parameter types are being passed
4Use explicit type conversion functions (e.g., CHAR, INT_TO_CHAR, REAL_TO_CHAR) if converting complex types to text
5Ensure all variable declarations in the program header match their usage throughout the KRL code
6Recompile the program after making corrections and verify the syntax in the IDE before downloading to the robot controller

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.