Heidenhain codes
HeidenhainServo/AxisIntermediate30-120 minutes

231-9530

HEIDENHAIN 231-9530 - 9530 DRIVE-CLiQ axis is still active

9530 DRIVE-CLiQ axis is still active

This TNC 640 error indicates an internal control fault. The issue relates to When an axis is deactivated in a DRIVE-CLiQ system, the asso.

Root Cause Summary

The control has detected that axis %1 is still in an active operational state (enabled, referenced, or engaged by NC/PLC) while attempting to modify its DRIVE-CLiQ component configuration. DRIVE-CLiQ topology changes require all affected axes to be completely inactive to prevent drive communication errors and ensure safe reconfiguration.

Safety

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

Causes and Fixes

  1. 1

    Access Machine Operating Mode

    Switch to Manual mode by pressing the Manual Operation key. Ensure the control is not in Automatic or Program Run mode.

  2. 2

    Disable all axes

    In the Machine menu, verify all axis enable indicators are OFF (grey, not green). If any are active, use the axis disable function or ensure the PLC enable signals are deactivated.

    On TNC 640 and newer, check the status bar at bottom of screen - all axis indicators should show grey background when disabled.

  3. 3

    Verify PLC enable signals

    Press MOD key, select PLC > PLC Status. Check markers M4000-M4008 (standard axis enable outputs) to confirm they are all FALSE for the affected axis.

    Standard Heidenhain PLC configuration uses M4000+axis_number for enable signals. Custom machine builders may use different markers - check machine documentation.

  4. 4

    Attempt configuration again

    Return to MOD > System Parameters > Drive Configuration and retry the DRIVE-CLiQ modification with all axes confirmed disabled.

    Do not force any configuration changes while this alarm is active - resolve the active state first to prevent drive communication errors.

DIY Feasiblehigh confidence

Call a technician if:

  • ·DRIVE-CLiQ hardware replacement needed
  • ·Multiple axis configuration corruption
  • ·Persistent communication errors after parameter correction

Prevention

  • Always use TNC axis configuration wizard when adding/removing axes
  • Maintain synchronized backup of machine parameters
  • Document DRIVE-CLiQ topology changes
  • Perform controlled shutdowns when modifying axis configurations

Common Mistakes

  • Changing only TNC parameters without considering DRIVE-CLiQ hardware
  • Forgetting to clear residual parameter entries
  • Not verifying DRIVE-CLiQ communication status after changes
  • Mixing up physical port numbers with logical axis assignments

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.