Heidenhain codes
HeidenhainSpindleIntermediate30-120 minutes

230-042E

HEIDENHAIN 230-042E - Unbalance monitoring: spindle is not configured

Unbalance monitoring: spindle is not configured

The unbalance monitor cannot find the spindle configuration. Required parameters for the spindle are missing from the configuration.

Root Cause Summary

Alarm 230-042E occurs when the unbalance monitoring function is enabled but the required spindle configuration parameters are missing or incorrectly set in the machine parameters. The TNC control cannot establish proper communication with the spindle drive system for unbalance detection.

Safety

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

Causes and Fixes

  1. 1

    Access machine parameter menu

    Press MOD key, select 'Machine Parameters', enter password if required.

    Ensure machine is in safe state before accessing parameters

  2. 2

    Check spindle axis assignment

    Navigate to MP7500.x (Spindle data) and verify MP7501 AXIS_ASSIGN is set to correct spindle axis (typically 'S' or 'S1').

    Use search function in parameter menu by typing '7501' directly

  3. 3

    Verify spindle configuration

    Check MP7502 SPINDLE_TYPE is correctly configured for your spindle drive system.

    Common values: 0=frequency converter, 1=servo spindle, 2=main spindle with encoder

  4. 4

    Save and restart control

    Save parameters with CTRL+S, perform control restart to activate changes.

    Control restart will interrupt any running programs

DIY Feasiblehigh confidence

Call a technician if:

  • ·Drive communication errors persist after parameter verification
  • ·Encoder hardware issues detected
  • ·Parameter changes cause other system malfunctions

Prevention

  • Regular backup of machine parameters
  • Document all parameter changes
  • Verify unbalance monitoring setup after any spindle maintenance
  • Monitor encoder signal quality during preventive maintenance

Common Mistakes

  • Forgetting control restart after parameter changes
  • Setting threshold values too low causing false alarms
  • Incorrect encoder resolution causing speed calculation errors
  • Not verifying drive communication before enabling monitoring

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.