Heidenhain codes
HeidenhainSystemIntermediate30-120 minutes

130-0132

HEIDENHAIN 130-0132 -

The control could not boot because certain necessary objects are unavailable at startup.

Root Cause Summary

This alarm fundamentally indicates that the TNC control's operating system cannot complete its boot sequence because one or more critical software objects—which could be NC kernel components, system libraries, configuration databases, or PLC objects—are either missing, corrupted, or inaccessible. The root cause is almost always related to storage media issues, incomplete software updates, or file system corruption that prevents the control from loading all necessary components for operation.

Safety

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

Causes and Fixes

  1. 1

    Access Service Mode

    Power cycle the control while holding the MOD key to enter Service Mode. This bypasses normal startup and allows access to diagnostic functions.

    On some TNC models, you may need to press MOD+7 during the boot sequence to access recovery options.

  2. 2

    Check System Log

    Navigate to TNCdiag utility and examine the system boot log (bootlog.txt) and error log files to identify which specific objects failed to load. Look for entries with 'object not found' or 'load failed' messages.

    The log files are typically located in TNC:\system\log or accessible directly through TNCdiag's log viewer interface.

  3. 3

    Run File System Check

    From Service Mode, execute the file system check utility on the TNC: partition. Select 'Check and Repair' option to attempt automatic correction of file system errors.

    Ensure the control has stable power during this operation. A power loss during file system repair can cause further damage.

  4. 4

    Restore from Backup or Recovery

    If file system check fails or objects remain corrupted, boot into Recovery Mode and select 'Restore Factory Settings' or restore from a previously created system backup if available. Navigate to System > Restore in the recovery menu.

    If you have a recent TNCbackup file, use the 'Restore from Archive' option to preserve machine parameters and PLC customizations.

Service Recommendedmedium confidence

Call a technician if:

  • ·Software corruption confirmed
  • ·Hardware communication failures
  • ·License validation required
  • ·System restore needed

Prevention

  • Regular system backups
  • Proper shutdown procedures
  • Environmental protection from power fluctuations
  • Regular software updates

Common Mistakes

  • Attempting software reinstallation without proper backups
  • Ignoring hardware LED status indicators
  • Modifying system files without documentation
  • Power cycling repeatedly without diagnosis

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.