What causes KUKA Robot alarm KRC0659?

Insufficient memory or heap space available for task creation. Corrupted or invalid KRL program file or module object. Missing or unresolved function/module dependencies in the program. Task priority configuration conflict or invalid scheduling parameters. Interrupted or incomplete program compilation or download to controller.

How do I fix KUKA Robot alarm KRC0659?

1. Check the teach pendant or diagnostic logs for the specific object name (@P1@) mentioned in the full alarm message 2. Verify the KRL program syntax and recompile the affected module using KRC compiler or KRC IDE 3. Ensure all dependent modules and functions are properly linked and available in the controller memory 4. Restart the KUKA controller (soft reboot) and attempt to reload the program to clear any corrupted cache 5. Review system memory status in the controller diagnostics and free up resources if necessary 6. If the issue persists, reload the program via USB or network transfer and verify file integrity before re-download

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0659

KUKA Robot KRC0659 - ERROR DURING TASK START 1613

This alarm indicates a failure occurred while attempting to start a task or program execution in the KUKA control system, specifically related to internal error code 1613. The robot controller was unable to initialize the requested task due to a system-level issue preventing proper task instantiation or resource allocation.

KUKA RobotSystemBasic

KRC0659

KUKA Robot KRC0659 - ERROR DURING TASK START 1613

ERROR DURING TASK START 1613

Common Causes

Insufficient memory or heap space available for task creation
Corrupted or invalid KRL program file or module object
Missing or unresolved function/module dependencies in the program
Task priority configuration conflict or invalid scheduling parameters
Interrupted or incomplete program compilation or download to controller

Troubleshooting Steps

1Check the teach pendant or diagnostic logs for the specific object name (@P1@) mentioned in the full alarm message
2Verify the KRL program syntax and recompile the affected module using KRC compiler or KRC IDE
3Ensure all dependent modules and functions are properly linked and available in the controller memory
4Restart the KUKA controller (soft reboot) and attempt to reload the program to clear any corrupted cache
5Review system memory status in the controller diagnostics and free up resources if necessary
6If the issue persists, reload the program via USB or network transfer and verify file integrity before re-download

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.