What causes KUKA Robot alarm KRC0011?

Recursive subroutine calls where a program calls itself directly or indirectly without proper exit condition. Excessive nesting of SRC files with multiple FOLD structures exceeding 64 levels deep. Interrupt routines (INTERRUPT DECL) triggering additional interrupt calls creating cascading stack buildup. Corrupted SRC or DAT files with malformed loop structures or missing return statements. Multiple BASE programs running simultaneously with deep subroutine nesting in each task.

How do I fix KUKA Robot alarm KRC0011?

1. Step 1: Acknowledge alarm and note the exact program line and module name shown in error log on smartPAD 2. Step 2: Open the faulting SRC file in editor and trace back all subroutine calls to identify recursive patterns or excessive nesting depth 3. Step 3: Check Navigator -> Log -> Archive for stack trace details showing the complete call hierarchy at fault moment 4. Step 4: Simplify program structure by breaking deep nested subroutines into parallel calls or reducing FOLD nesting levels below 50 5. Step 5: Review all INTERRUPT declarations in Submit interpreter and verify no interrupt can trigger itself or create circular calling pattern 6. Step 6: If structure appears correct, reload a backup version of program files from archive or KRL source control and retest execution path

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Intermediate

Alarm KRC0011

KUKA Robot KRC0011 - Program Stack Overflow

The KRL program interpreter has exceeded the maximum call stack depth of 64 levels during program execution. This occurs when nested subroutine calls, loops, or interrupt routines create excessive recursion beyond the controller memory allocation. The robot motion stops immediately and the program halts at the fault location.

KUKA RobotSystemIntermediate

KRC0011

KUKA Robot KRC0011 - Program Stack Overflow

Program Stack Overflow

Common Causes

Recursive subroutine calls where a program calls itself directly or indirectly without proper exit condition
Excessive nesting of SRC files with multiple FOLD structures exceeding 64 levels deep
Interrupt routines (INTERRUPT DECL) triggering additional interrupt calls creating cascading stack buildup
Corrupted SRC or DAT files with malformed loop structures or missing return statements
Multiple BASE programs running simultaneously with deep subroutine nesting in each task

Troubleshooting Steps

1Step 1: Acknowledge alarm and note the exact program line and module name shown in error log on smartPAD
2Step 2: Open the faulting SRC file in editor and trace back all subroutine calls to identify recursive patterns or excessive nesting depth
3Step 3: Check Navigator -> Log -> Archive for stack trace details showing the complete call hierarchy at fault moment
4Step 4: Simplify program structure by breaking deep nested subroutines into parallel calls or reducing FOLD nesting levels below 50
5Step 5: Review all INTERRUPT declarations in Submit interpreter and verify no interrupt can trigger itself or create circular calling pattern
6Step 6: If structure appears correct, reload a backup version of program files from archive or KRL source control and retest execution path

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.