What causes KUKA Robot alarm KRC0563?

Attempting to run a program in Automatic mode while the controller is in Manual or Test mode. Program execution mode setting in the WorkVisual project does not match the actual controller mode capability. Safety-related interlock preventing execution in the selected mode due to open safety gates or disabled enabling switches. Incompatible program type or structure attempting to execute in a mode that requires different program format or syntax. Controller firmware or software version mismatch between program configuration and current KRC system.

How do I fix KUKA Robot alarm KRC0563?

1. Verify the current controller operating mode on the teach pendant display and confirm it matches the intended program execution mode 2. Check the program configuration in WorkVisual under 'Program Execution' settings to ensure the mode is compatible with current system state 3. Inspect all safety interlocks and enabling devices (e-stop, safety gates, enabling switch) to confirm they are in proper working condition and activated 4. Review the program header and execution settings to verify that no mode restrictions or incompatible directives are specified in the source code 5. Attempt to manually switch modes on the teach pendant to verify the controller can transition between modes without triggering the alarm 6. If the issue persists, update the controller software to the latest version compatible with the program and restart the KRC system

KUKA Robot codes

axismd.ai

KUKA Robot Controller

Program/G-code · Basic

Alarm KRC0563

KUKA Robot KRC0563 - Program exec. mode inadmissible

This alarm occurs when an attempt is made to execute a program in a mode that is not permitted for the current operational state or program configuration. The KRC controller prevents execution because the selected mode (such as Automatic, Manual, or Test) conflicts with safety requirements, system state, or program specifications.

KUKA RobotProgram/G-codeBasic

KRC0563

KUKA Robot KRC0563 - Program exec. mode inadmissible

Program exec. mode inadmissible

Common Causes

Attempting to run a program in Automatic mode while the controller is in Manual or Test mode
Program execution mode setting in the WorkVisual project does not match the actual controller mode capability
Safety-related interlock preventing execution in the selected mode due to open safety gates or disabled enabling switches
Incompatible program type or structure attempting to execute in a mode that requires different program format or syntax
Controller firmware or software version mismatch between program configuration and current KRC system

Troubleshooting Steps

1Verify the current controller operating mode on the teach pendant display and confirm it matches the intended program execution mode
2Check the program configuration in WorkVisual under 'Program Execution' settings to ensure the mode is compatible with current system state
3Inspect all safety interlocks and enabling devices (e-stop, safety gates, enabling switch) to confirm they are in proper working condition and activated
4Review the program header and execution settings to verify that no mode restrictions or incompatible directives are specified in the source code
5Attempt to manually switch modes on the teach pendant to verify the controller can transition between modes without triggering the alarm
6If the issue persists, update the controller software to the latest version compatible with the program and restart the KRC system

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.