What causes KUKA Robot alarm KRC0956?

Attempting to declare a variable or object with an undefined or misspelled data type name. Missing or incorrect type definition in the source code or included files. Using a data type from an external library or module that was not properly imported or included. Scope issue where the data type is defined in a different program context that is not accessible. Syntax error in the data type declaration causing the compiler to fail recognition.

How do I fix KUKA Robot alarm KRC0956?

1. Review the KRL source code at the location indicated by the alarm to identify the problematic object name and data type reference 2. Verify that all custom data type definitions are correctly declared before use and check for spelling errors in type names 3. Confirm that all required include files (.src) or library modules containing the data type definitions are properly referenced with #INCLUDE statements 4. Check the scope of the data type declaration and ensure it is accessible from the location where it is being instantiated 5. Consult the KUKA KRL language documentation to verify correct syntax for the data type definition and object creation 6. Recompile the program after correcting the data type reference and verify that all dependencies are available in the project workspace

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0956

KUKA Robot KRC0956 - NO DATA TYPE NAME: CREATION NOT ALLOWED 2293

This alarm occurs when the KRL compiler encounters an attempt to create or instantiate a data type that has not been properly defined or declared in the program. The compiler cannot proceed with object creation because the referenced data type name does not exist or is inaccessible in the current scope.

KUKA RobotSystemBasic

KRC0956

KUKA Robot KRC0956 - NO DATA TYPE NAME: CREATION NOT ALLOWED 2293

NO DATA TYPE NAME: CREATION NOT ALLOWED 2293

Common Causes

Attempting to declare a variable or object with an undefined or misspelled data type name
Missing or incorrect type definition in the source code or included files
Using a data type from an external library or module that was not properly imported or included
Scope issue where the data type is defined in a different program context that is not accessible
Syntax error in the data type declaration causing the compiler to fail recognition

Troubleshooting Steps

1Review the KRL source code at the location indicated by the alarm to identify the problematic object name and data type reference
2Verify that all custom data type definitions are correctly declared before use and check for spelling errors in type names
3Confirm that all required include files (.src) or library modules containing the data type definitions are properly referenced with #INCLUDE statements
4Check the scope of the data type declaration and ensure it is accessible from the location where it is being instantiated
5Consult the KUKA KRL language documentation to verify correct syntax for the data type definition and object creation
6Recompile the program after correcting the data type reference and verify that all dependencies are available in the project workspace

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.