KUKA Robot codes
AxisMD

axismd.ai

KUKA Robot Controller

Parameter · Basic

Alarm KRC0455

KUKA Robot KRC0455 - PARAMETER NOT PROCESSED

A RUN command containing parameters was executed for a KRL program that has already been selected and loaded in the current execution context. The parameter cannot be processed because the program is already active. Parameters must be passed during initial program selection, not after activation. This prevents parameter conflicts and undefined runtime behavior.

KUKA RobotParameterBasic

KRC0455

KUKA Robot KRC0455 - PARAMETER NOT PROCESSED

PARAMETER NOT PROCESSED

A RUN command containing parameters was executed for a KRL program that has already been selected and loaded in the current execution context. The parameter cannot be processed because the program is already active. Parameters must be passed during initial program selection, not after activation. This prevents parameter conflicts and undefined runtime behavior.

Common Causes

  • RUN command with parameter issued while target program is still executing or paused from previous execution cycle
  • Multiple consecutive RUN commands with different parameters sent to same program without intermediate STOP or SELECT command
  • External interface (OPC UA, TOPS, or socket communication) sending RUN with parameters to already-active program
  • Program selection retained from previous job and RUN command with new parameters attempted without explicit program reload
  • KRL logic containing loop that repeatedly executes RUN with parameters on already-selected program

Troubleshooting Steps

  1. 1Stop the currently running program completely using STOP command on KUKA smartPAD before issuing new RUN command with parameters
  2. 2Verify program execution state in the KRC4 status display shows IDLE or STOPPED before sending subsequent RUN commands
  3. 3If using external interfaces (OPC UA, socket API), implement state checking logic to confirm program ready status before parameter passing
  4. 4Review KRL source code for any embedded RUN statements and ensure target program is released to IDLE state before parameter-based restart
  5. 5Clear the alarm and use SELECT followed by parameter initialization before issuing the RUN command on the reloaded program
  6. 6Implement command queuing and state machine logic in calling program to serialize RUN operations and prevent parameter conflicts

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.