What causes KUKA Robot alarm KRC0738?

Attempting to use a variable of incorrect data type (e.g., REAL, INT, BOOL) where FRAME or POS is expected. Referencing a function or module that returns an incompatible data type instead of FRAME or POS. Typo or incorrect variable name that resolves to a wrong object. Mixing up similar variable names where one is FRAME/POS and another is a different type. Missing type conversion or casting between incompatible data types in frame/position operations.

How do I fix KUKA Robot alarm KRC0738?

1. Identify the exact line number and object name from the alarm message and locate it in the KRL source code 2. Verify the data type declaration of the referenced object; it must be explicitly declared as FRAME or POS 3. Check variable names for typos and ensure the correct variable is being referenced 4. Review function return types if the object is a function call; confirm it returns FRAME or POS 5. Use explicit type casting or conversion functions if data type mismatch is intentional 6. Recompile the KRL program after corrections and verify the alarm no longer appears

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0738

KUKA Robot KRC0738 - COMPONENT NEITHER PART OF “FRAME” OR “POS” 2074

This alarm indicates that a KRL program object referenced in the code is neither a FRAME nor a POS data type, but the syntax or context requires one of these types. The compiler or interpreter encountered an invalid object type when processing a frame or position-related operation.

KUKA RobotSystemBasic

KRC0738

KUKA Robot KRC0738 - COMPONENT NEITHER PART OF “FRAME” OR “POS” 2074

COMPONENT NEITHER PART OF “FRAME” OR “POS” 2074

Common Causes

Attempting to use a variable of incorrect data type (e.g., REAL, INT, BOOL) where FRAME or POS is expected
Referencing a function or module that returns an incompatible data type instead of FRAME or POS
Typo or incorrect variable name that resolves to a wrong object
Mixing up similar variable names where one is FRAME/POS and another is a different type
Missing type conversion or casting between incompatible data types in frame/position operations

Troubleshooting Steps

1Identify the exact line number and object name from the alarm message and locate it in the KRL source code
2Verify the data type declaration of the referenced object; it must be explicitly declared as FRAME or POS
3Check variable names for typos and ensure the correct variable is being referenced
4Review function return types if the object is a function call; confirm it returns FRAME or POS
5Use explicit type casting or conversion functions if data type mismatch is intentional
6Recompile the KRL program after corrections and verify the alarm no longer appears

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.