What causes KUKA Robot alarm KRC0536?

Pressing a softkey that is not available or permitted in the current program mode or safety state. Attempting to execute an invalid key command while the robot is in motion or executing a running program. Using restricted navigation keys (e.g., cursor movement, menu navigation) during automatic operation mode. Pressing keys during a critical program phase where user input is disabled for safety compliance. Operating the teach pendant in a mode where certain softkey functions are intentionally locked or disabled by the program logic.

How do I fix KUKA Robot alarm KRC0536?

1. Verify the current operational mode displayed on the KRC controller (Manual, Automatic, Test) and ensure you are attempting the correct key input for that mode 2. Check if the robot is actively executing a program; if so, allow the program to complete or use emergency stop (E-Stop) to halt execution before attempting other inputs 3. Review the program structure and user interface configuration to identify which softkeys are permitted in the current operational state 4. Consult the teach pendant documentation and KRC software manual to confirm which keys are valid for your specific mode and program phase 5. If the alarm persists, perform a controller restart (warm or cold boot) to reset the input state and clear any temporary restrictions 6. Contact KUKA support or your system integrator if the alarm recurs after troubleshooting, as it may indicate a configuration issue with program permissions or teach pendant mapping

KUKA Robot codes

axismd.ai

KUKA Robot Controller

System · Basic

Alarm KRC0536

KUKA Robot KRC0536 - Key not allowed

This alarm indicates that an impermissible key or softkey was pressed during textual operation mode on the KUKA KRC controller. The controller restricts certain input commands based on the current operational state, safety mode, or program execution phase to prevent unintended robot movements or parameter modifications. When a prohibited key is detected, the system triggers this alarm to halt the invalid input and maintain system integrity.

KUKA RobotSystemBasic

KRC0536

KUKA Robot KRC0536 - Key not allowed

Key not allowed

Common Causes

Pressing a softkey that is not available or permitted in the current program mode or safety state
Attempting to execute an invalid key command while the robot is in motion or executing a running program
Using restricted navigation keys (e.g., cursor movement, menu navigation) during automatic operation mode
Pressing keys during a critical program phase where user input is disabled for safety compliance
Operating the teach pendant in a mode where certain softkey functions are intentionally locked or disabled by the program logic

Troubleshooting Steps

1Verify the current operational mode displayed on the KRC controller (Manual, Automatic, Test) and ensure you are attempting the correct key input for that mode
2Check if the robot is actively executing a program; if so, allow the program to complete or use emergency stop (E-Stop) to halt execution before attempting other inputs
3Review the program structure and user interface configuration to identify which softkeys are permitted in the current operational state
4Consult the teach pendant documentation and KRC software manual to confirm which keys are valid for your specific mode and program phase
5If the alarm persists, perform a controller restart (warm or cold boot) to reset the input state and clear any temporary restrictions
6Contact KUKA support or your system integrator if the alarm recurs after troubleshooting, as it may indicate a configuration issue with program permissions or teach pendant mapping

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.