Heidenhain codes
HeidenhainServo/AxisIntermediate30-120 minutes

230-0460

HEIDENHAIN 230-0460 - Error in configuration of axis

Error in configuration of axis

The axis configuration contains errors in power supply or motor settings. Incorrect parameters for supply module, power stage, or motor supply may be present.

Root Cause Summary

This alarm is triggered by the TNC control's internal parameter validation routines detecting logical inconsistencies within an axis configuration. The control performs comprehensive cross-checking of interdependent parameters during initialization, and this alarm prevents operation when the axis configuration does not meet the required logical framework for safe and proper machine operation.

Safety

  • Refer to Heidenhain service manual
  • Ensure qualified technician performs repairs

Causes and Fixes

  1. 1

    Access Machine Parameters

    Press MOD key, enter machine parameter mode (requires keyswitch position 2 or password depending on TNC model), navigate to General → CfgAxes → Axis [affected axis]

    Working in machine parameters requires proper authorization and documentation. Incorrect changes can damage machine or control.

  2. 2

    Verify MP100 Axis Type

    Check MP100 for the affected axis. Valid values: 0=not used, 1=linear axis, 2=rotary axis display ±180°, 3=rotary axis display 0-360°, 4=modulo axis. Ensure value matches physical axis configuration.

    Cross-reference with MP110 (axis designation) to ensure logical consistency between axis type and its assigned letter (X/Y/Z for linear, A/B/C for rotary).

  3. 3

    Validate Dependent Parameters

    After confirming MP100, verify MP101-109 (display resolution, monitoring windows) and MP200-202 (software limit switches) are appropriate for the defined axis type.

    Linear axes require software limits in MP200/201, while modulo axes (MP100=4) should have these set to 0 or undefined.

  4. 4

    Restart Control and Test

    Save all parameter changes, perform a complete control restart (power cycle), and verify the axis configuration loads without alarm during POST sequence.

DIY Feasiblehigh confidence

Call a technician if:

  • ·CFG file corruption requires restoration from backup
  • ·Hardware replacement needed
  • ·Multiple axes affected simultaneously

Prevention

  • Regular parameter backups
  • Document all configuration changes
  • Verify parameters after hardware replacement
  • Use parameter comparison tools during setup

Common Mistakes

  • Copying parameters between different axis types
  • Not updating parameters after encoder replacement
  • Ignoring parameter validation warnings
  • Mixing imperial and metric scaling factors

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.