Heidenhain codes
HeidenhainSystemIntermediate30-120 minutes

140-0020

HEIDENHAIN 140-0020 - Module name missing or unknown

Module name missing or unknown

An internal software error occurred where a module failed to provide or provided an incorrect identification during a request.

Root Cause Summary

The control's module loader cannot locate or identify a required software component during system initialization or runtime loading. This typically stems from missing PLC module files, configuration file mismatches, or incomplete software installations where the control expects a module that is either absent, incorrectly named, or corrupted in the file system.

Safety

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

Causes and Fixes

  1. 1

    Identify missing module name

    Note the exact module name shown in '%1' parameter. Press the HELP key while alarm is active to see full alarm details including the complete module name.

    Module names are case-sensitive on Heidenhain controls. 'Module.mod' is different from 'module.mod'.

  2. 2

    Check PLC directory contents

    Press PGM MGT key, navigate to TNC:\system\plc directory. Compare files present against the module name from the alarm. Look for similar names with spelling differences or incorrect file extensions.

    Use the 'Show all files' option in File Manager to ensure hidden or system files are visible.

  3. 3

    Review PLC configuration

    Open the PLC configuration file (commonly plc.sys or project-specific .plc file) and search for the missing module name. Verify if this module is essential for machine operation.

    Do not modify PLC configuration files without understanding machine PLC logic or having backup copies available.

  4. 4

    Obtain or restore missing module

    If module is required, restore from backup or obtain correct module file from machine builder or Heidenhain service. Copy to TNC:\system\plc directory and perform controlled restart (MOD → System → Restart).

    Always verify module file compatibility with your specific TNC software version before copying.

DIY Feasiblemedium confidence

Call a technician if:

  • ·Servo drive hardware replacement needed
  • ·HSCI communication issues persist after cable replacement
  • ·Software reinstallation required

Prevention

  • Regular backup of machine parameters
  • Periodic HSCI cable inspection
  • Keep TNC software updated
  • Monitor servo drive temperatures

Common Mistakes

  • Ignoring HSCI cable routing requirements
  • Using non-Heidenhain HSCI cables
  • Modifying servo parameters without backup
  • Interrupting software updates

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.