What causes KUKA Robot alarm KRC0799?

Misspelled or undefined custom data type name in object declaration. Attempting to use a KRL object that has not been properly imported or included in the program. Incorrect syntax when defining or referencing a structure, array, or custom type. Using an obsolete or unsupported object type from a different KRC software version. Missing type definition library or module that contains the referenced object type.

How do I fix KUKA Robot alarm KRC0799?

1. Review the KRL source code around the error location and verify all object type names are spelled correctly 2. Check that all required include files and libraries containing type definitions are properly imported at the program start 3. Verify the object declaration syntax matches KUKA KRL standards for the current KRC software version 4. Compare the object type definition against the KUKA KRL reference documentation to ensure it is a valid, supported type 5. Recompile the program after correcting type declarations and ensure there are no remaining syntax errors 6. If using custom types, confirm the type definition exists and is accessible within the program's scope and visibility rules

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0799

KUKA Robot KRC0799 - OBJECT TYPE NOT VALID 2135

This alarm indicates that an object type referenced in the KRL program is invalid or not recognized by the KRC system. The compiler or runtime environment encountered an object declaration or usage that does not match any valid KUKA data type or object definition.

KUKA RobotSystemBasic

KRC0799

KUKA Robot KRC0799 - OBJECT TYPE NOT VALID 2135

OBJECT TYPE NOT VALID 2135

Common Causes

Misspelled or undefined custom data type name in object declaration
Attempting to use a KRL object that has not been properly imported or included in the program
Incorrect syntax when defining or referencing a structure, array, or custom type
Using an obsolete or unsupported object type from a different KRC software version
Missing type definition library or module that contains the referenced object type

Troubleshooting Steps

1Review the KRL source code around the error location and verify all object type names are spelled correctly
2Check that all required include files and libraries containing type definitions are properly imported at the program start
3Verify the object declaration syntax matches KUKA KRL standards for the current KRC software version
4Compare the object type definition against the KUKA KRL reference documentation to ensure it is a valid, supported type
5Recompile the program after correcting type declarations and ensure there are no remaining syntax errors
6If using custom types, confirm the type definition exists and is accessible within the program's scope and visibility rules

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.