Heidenhain codes
HeidenhainSpindleIntermediate30-120 minutes

230-042F

HEIDENHAIN 230-042F - Unbalance monitoring: spindle parameter or index is faulty

Unbalance monitoring: spindle parameter or index is faulty

The unbalance monitoring configuration has an invalid spindle index or incorrect spindle settings. The configuration in CfgUnbalance may be faulty.

Root Cause Summary

This alarm is triggered by an inconsistency between the unbalance monitoring configuration and the spindle parameter structure in the Heidenhain TNC control. The control cannot locate valid spindle parameters using the provided index, indicating either incorrect parameter entry, missing spindle configuration data, or an index reference that points to a non-existent or improperly configured spindle.

Safety

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

Causes and Fixes

  1. 1

    Verify Configured Spindle Count

    Access MOD function, navigate to Machine Parameters, and check MP3591 (number of spindles). Note the configured spindle count (typically 1-4).

    Spindle indexing in Heidenhain typically starts at 0 or 1 depending on the control generation and configuration - verify your specific machine's convention.

  2. 2

    Check Unbalance Configuration File

    Access the TNC:systemCfgSpindleUnbalance.sys file via the file manager (PGM MGT key). Review the spindle index parameter entries and ensure they reference valid spindle numbers (0 to n-1 or 1 to n).

    Modifying system configuration files requires appropriate access level and incorrect changes can disable spindle functionality.

  3. 3

    Correct Index Assignment

    Edit the CfgSpindleUnbalance.sys file to match the spindle index with your actual configured spindle (typically spindle 0 for single spindle machines). Save changes and perform a control restart.

    Always create a backup copy of configuration files before editing by copying to TNC:ackup directory.

DIY Feasiblehigh confidence

Call a technician if:

  • ·PLC program modifications required
  • ·Hardware sensor replacement needed
  • ·Parameter corruption persists after restore

Prevention

  • Regular parameter backups
  • Periodic unbalance system calibration
  • Monitor sensor condition during PM
  • Validate configuration after software updates

Common Mistakes

  • Confusing spindle number with spindle index (off-by-one error)
  • Modifying CfgUnbalance without checking hardware compatibility
  • Ignoring related spindle parameter dependencies
  • Not restarting spindle system after parameter changes

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.