KRC0625

Common Causes

• KRL task encountered an unhandled exception, such as division by zero, null pointer dereference, or invalid memory access during execution
• Insufficient heap or stack memory allocated to the KRL task caused memory exhaustion or corruption of the task control block
• Real-time scheduler deadlock or priority inversion occurred when multiple KRL tasks competed for access to shared resources or communication channels
• KRL interpreter detected an infinite loop, stack overflow, or recursive call depth that exceeded safe limits in the core system
• Hardware watchdog timer or safety system detected that the KRC4 control loop missed a deadline, indicating system overload or task hang

Troubleshooting Steps

1. 1Immediately press the Emergency Stop button on the KUKA smartPAD and note the exact time and error number displayed on the teach pendant
2. 2Power cycle the KRC4 controller by switching off the main power supply for 30 seconds, then restart and observe if the error recurs
3. 3Access the KRC system log files via the file system to retrieve the full error stack trace and identify which KRL task crashed and why
4. 4Review recent changes to KRL programs or configuration that may have introduced infinite loops, recursion, or memory leaks before the error appeared
5. 5Reduce the workload by disabling non-essential KRL tasks or modules in the startup configuration, then attempt to restart the system incrementally
6. 6Contact KUKA service with the complete system log, error number, originating task name, and reproduction steps to obtain diagnostic support or firmware updates