KUKA Robot codes
AxisMD

axismd.ai

KUKA Robot Controller

Parameter · Basic

Alarm KRC0359

KUKA Robot KRC0359 - ACKN. WRONG DRIVES PARAMETER <axis number> **

This alarm indicates that the drive parameters for the specified axis have been acknowledged but contain incorrect or incompatible values in the robot controller's system configuration. The drive parameters may have failed validation against the expected hardware specifications, firmware version, or controller settings during the initialization or configuration phase.

KUKA RobotParameterBasic

KRC0359

KUKA Robot KRC0359 - ACKN. WRONG DRIVES PARAMETER <axis number> **

ACKN. WRONG DRIVES PARAMETER <axis number> **

This alarm indicates that the drive parameters for the specified axis have been acknowledged but contain incorrect or incompatible values in the robot controller's system configuration. The drive parameters may have failed validation against the expected hardware specifications, firmware version, or controller settings during the initialization or configuration phase.

Common Causes

  • Drive parameter values do not match the actual hardware configuration or axis specifications
  • Firmware version mismatch between the controller and the drive module
  • Corrupted or incomplete parameter data in the controller's configuration files
  • Incorrect axis assignment or drive module type selection in the system setup
  • Parameter values exceed the valid range or contain incompatible settings for the specified axis

Troubleshooting Steps

  1. 1Identify the affected axis number from the alarm message and note the drive type and controller model
  2. 2Verify that the physical drive hardware matches the configured drive type in the system parameters
  3. 3Check the drive parameter values in the KRC configuration files against the hardware specifications and valid parameter ranges
  4. 4Compare the firmware version of the drive module with the compatible firmware versions supported by the KRC controller
  5. 5Reload the default drive parameters for the affected axis and reconfigure them according to the hardware documentation
  6. 6If the issue persists, perform a controller backup, then restore factory settings for the affected axis and reconfigure the system parameters from scratch

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.