What causes KUKA Robot alarm KRC0397?

Tool or end-effector frame referenced in the program has not been defined or calibrated in the system. Workspace or coordinate frame identifier does not exist in the active configuration. Data variable or array index is out of bounds or has been deleted. Program references a file, macro, or subroutine that is not loaded or accessible. Communication failure or corrupted configuration preventing object initialization on startup.

How do I fix KUKA Robot alarm KRC0397?

1. Review the active program and identify which object is being referenced when the alarm occurs 2. Verify that all required tools and frames are properly defined in the System > Frames and Tools configuration menu 3. Check that data variables and arrays are declared with correct scope and have been properly initialized before use 4. Confirm that all referenced files, macros, and subroutines exist and are accessible in the project directory 5. Perform a system restart or reload the configuration to ensure all objects are properly loaded into memory 6. If the object is required, recreate or recalibrate the missing tool or frame, then reload and retest the program

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0397

KUKA Robot KRC0397 - <object> NOT AVAILABLE

This alarm occurs when the KRC controller attempts to access or reference an object (such as a tool, frame, or data structure) that does not exist in the system's configuration or memory. The controller cannot proceed with program execution until the missing object is resolved or properly defined.

KUKA RobotSystemBasic

KRC0397

KUKA Robot KRC0397 - <object> NOT AVAILABLE

Common Causes

Tool or end-effector frame referenced in the program has not been defined or calibrated in the system
Workspace or coordinate frame identifier does not exist in the active configuration
Data variable or array index is out of bounds or has been deleted
Program references a file, macro, or subroutine that is not loaded or accessible
Communication failure or corrupted configuration preventing object initialization on startup

Troubleshooting Steps

1Review the active program and identify which object is being referenced when the alarm occurs
2Verify that all required tools and frames are properly defined in the System > Frames and Tools configuration menu
3Check that data variables and arrays are declared with correct scope and have been properly initialized before use
4Confirm that all referenced files, macros, and subroutines exist and are accessible in the project directory
5Perform a system restart or reload the configuration to ensure all objects are properly loaded into memory
6If the object is required, recreate or recalibrate the missing tool or frame, then reload and retest the program

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.