Heidenhain codes
HeidenhainSystemIntermediate30-120 minutes

130-0136

HEIDENHAIN 130-0136 -

The control cannot start because required objects are absent. This usually points to corrupted or incomplete system data.

Root Cause Summary

This alarm specifically indicates that essential system objects required for the TNC control's operation are missing or inaccessible during the boot sequence. The most common root cause is an incomplete or corrupted NC software installation, though hardware failures affecting the storage medium can also prevent proper object loading. The control's self-diagnostic routine detects this incomplete system state and prevents startup to avoid unpredictable behavior.

Safety

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

Causes and Fixes

  1. 1

    Access Service Mode

    Power off the control completely. Power on while holding the MOD key to enter Service Mode. This bypasses normal startup and allows access to recovery functions.

    If MOD key access fails, the system partition itself may be damaged and require Heidenhain service intervention.

  2. 2

    Check System Log Files

    In Service Mode, navigate to System > Log Files. Review the startup log (syslog.txt) and look for specific object names or initialization failures that caused the 130-0136 alarm.

    Take photos or notes of specific missing object names - this information is critical for determining if a full reinstall is needed.

  3. 3

    Attempt System Restore

    From Service Mode menu, select 'Restore System' if a recovery partition exists. Choose the most recent stable system restore point before the failed update or installation.

    System restore will revert to the previous software version and may lose recent configuration changes not backed up.

  4. 4

    Reinstall NC Software

    If restore fails, perform complete NC software reinstallation using Heidenhain installation media (USB or DVD). Boot from installation media and select 'Complete Installation' option. Follow prompts to reinstall all system objects.

    Ensure you have machine parameters and PLC program backups before reinstalling. Machine-specific data must be reloaded after fresh installation.

  5. 5

    Restore Machine Configuration

    After successful reinstallation, restore machine parameters from TNC:\system\backup or external backup media. Reload PLC program and cycle definitions specific to your machine.

    Use MOD > File System to verify all required files in TNC:\system\objects directory are present with valid timestamps after installation.

Service Recommendedmedium confidence

Call a technician if:

  • ·System recovery fails to resolve alarm
  • ·Hardware inspection reveals damaged servo modules
  • ·No parameter backup available and machine-specific configuration unknown

Prevention

  • Regularly backup machine parameters and system software
  • Monitor system memory usage monthly
  • Perform annual servo cable inspection
  • Keep system software updated per Heidenhain recommendations

Common Mistakes

  • Attempting to modify system files directly
  • Ignoring memory warnings before they cause startup failures
  • Not backing up parameters before software updates
  • Mixing parameter sets from different machine 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.