Heidenhain codes
HeidenhainServo/AxisIntermediate30-120 minutes

230-0021

HEIDENHAIN 230-0021 - Axis cannot be activated

Axis cannot be activated

This TNC7/TNC 640 error indicates an issue with 230-0021. The value configured under CfgAxis-axisHw prohibits this activation command.

Root Cause Summary

HEIDENHAIN alarm 230-0021 occurs when the axis hardware configuration parameter CfgAxis-axisHw contains a value that prevents the requested axis activation. This typically indicates a mismatch between the configured axis type and the actual hardware present, or incorrect axis enable settings in the TNC configuration.

Safety

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

Causes and Fixes

  1. 1

    Access Machine Parameters

    Navigate to MOD function → Machine Parameters → CfgAxis group to view current axis hardware configuration.

    Document current settings before making changes for easy rollback if needed.

  2. 2

    Verify Hardware Type Setting

    Check CfgAxis-axisHw parameter value against actual servo drive model and encoder type installed on the problematic axis.

    Incorrect hardware type settings can cause permanent damage to servo drives.

  3. 3

    Correct Configuration

    Set CfgAxis-axisHw to match actual hardware: 0=no axis, 1=analog servo, 2=digital servo, 3=stepper motor, 4=spindle drive.

    Consult machine documentation or servo drive nameplate for exact hardware specifications.

  4. 4

    Restart Control

    Perform complete TNC restart to activate new configuration and attempt axis activation.

    Ensure all axes are in safe position before restart.

DIY Feasiblehigh confidence

Call a technician if:

  • ·Servo drive hardware failure suspected
  • ·Safety system modifications required
  • ·Multiple axes affected simultaneously
  • ·Parameter corruption persists after restoration

Prevention

  • Regular backup of machine parameters
  • Periodic verification of servo drive communication status
  • Proper shutdown procedures to prevent parameter corruption
  • Regular inspection of communication cables and connections

Common Mistakes

  • Changing CfgAxis-axisHw without understanding hardware implications
  • Ignoring safety system status when troubleshooting
  • Not backing up parameters before making changes
  • Assuming all axes use identical hardware configurations

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.