Heidenhain codes
HeidenhainServo/AxisIntermediate30-120 minutes

120-002E

HEIDENHAIN 120-002E - Path not found

Path not found

This TNC7/TNC 640 error (120-002E) relates to 'Path not found'. A required drive or directory was not found.

Root Cause Summary

This alarm occurs exclusively when the TNC file system cannot resolve a path reference made by NC programs, PLC operations, or system configuration files. The root cause is always a mismatch between expected and actual file system structure, either due to deleted directories, incorrect path syntax, unmounted network drives, or removed storage media that was referenced in active operations.

Safety

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

Causes and Fixes

  1. 1

    Identify Referenced Path

    Press PGM MGT key and open the NC program that was running when alarm occurred. Search for CALL PGM, FN18:, or SEL CYCLE commands and note the exact path string shown in '%1' from error message.

    Use FIND function (GOTO key) and search for 'TNC:/' or 'SYS:/' to quickly locate all path references in program

  2. 2

    Verify Directory Structure

    Navigate in PGM MGT to the parent directory of the referenced path. Check if all subdirectories exist exactly as spelled in program (Heidenhain paths are case-sensitive).

    TNC:/ is the user partition, SYS:/ is system partition - ensure you're checking the correct root directory

  3. 3

    Correct Path or Create Directory

    Either edit the NC program to reference correct existing path, or create the missing directory using NEW DIRECTORY soft key in PGM MGT. Copy required files to new location if needed.

    Do not create directories in SYS:/ partition without machine manufacturer authorization as this may affect system configuration

  4. 4

    Test Program Execution

    Reset control with CE key, restart NC program in single block mode (SINGLE BLOCK key active) and verify path access works correctly when reaching CALL or FN18 command.

DIY Feasiblehigh confidence

Call a technician if:

  • ·File system corruption requires Windows-level repair
  • ·Hardware drive failure suspected
  • ·Network infrastructure issues beyond machine scope

Prevention

  • Regular backup of tool tables and configuration files
  • Monitor network connectivity stability
  • Perform periodic file system integrity checks

Common Mistakes

  • Editing file paths without understanding TNC directory structure
  • Deleting system files during cleanup operations
  • Ignoring network drive mapping after system 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.