What causes KUKA Robot alarm KRC0881?

Attempting to use a variable or function name where a label (GOTO target) is required. Incorrect declaration of a label in the KRL source code. Name collision between a label and another symbol type (variable, function, or module). Corrupted or malformed symbol table entry from a previous compilation. Using a reserved keyword or system symbol as a label name.

How do I fix KUKA Robot alarm KRC0881?

1. Identify the object name @P1@ from the alarm message and locate it in the KRL source code 2. Verify that all GOTO statements reference valid labels defined with colon syntax (e.g., 'LabelName:') 3. Check for duplicate symbol names that may conflict between labels and variables/functions 4. Review the KRL program syntax to ensure labels are properly declared before being referenced 5. Delete the compiled output files (.src.o or similar) and perform a clean recompilation 6. If the issue persists, extract and review the symbol table file or contact KUKA support with the affected program source

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0881

KUKA Robot KRC0881 - ENTRY IN SYMBOL TABLE IS NOT LABEL 2217

This alarm indicates that a symbol table entry referenced in the KRL program is not a valid label as expected by the compiler. The referenced object @P1@ exists in the symbol table but does not have the label type required for the current operation, typically occurring during program compilation or linking.

KUKA RobotSystemBasic

KRC0881

KUKA Robot KRC0881 - ENTRY IN SYMBOL TABLE IS NOT LABEL 2217

ENTRY IN SYMBOL TABLE IS NOT LABEL 2217

Common Causes

Attempting to use a variable or function name where a label (GOTO target) is required
Incorrect declaration of a label in the KRL source code
Name collision between a label and another symbol type (variable, function, or module)
Corrupted or malformed symbol table entry from a previous compilation
Using a reserved keyword or system symbol as a label name

Troubleshooting Steps

1Identify the object name @P1@ from the alarm message and locate it in the KRL source code
2Verify that all GOTO statements reference valid labels defined with colon syntax (e.g., 'LabelName:')
3Check for duplicate symbol names that may conflict between labels and variables/functions
4Review the KRL program syntax to ensure labels are properly declared before being referenced
5Delete the compiled output files (.src.o or similar) and perform a clean recompilation
6If the issue persists, extract and review the symbol table file or contact KUKA support with the affected program source

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.