120-001F

Identify the calling line

Press INTERNAL STOP if program is running. Note the block number displayed with the alarm. Open the active NC program and locate the CALL PGM or CYCL CALL statement that references the missing file.

Use the Search function in the editor (GOTO key) to quickly find all CALL PGM statements in large programs.

Verify filename and path syntax

Check that the filename in the CALL statement matches exactly - Heidenhain is case-sensitive. Verify path format: use TNC:\ for internal memory, or full network path like \\SERVER\SHARE\FILE.H. Common error is using relative paths incorrectly.

Heidenhain expects forward slash notation in newer controls or backslash with drive prefix. Avoid mixed separators.

Search for the missing file

Press PGM MGT key, then use the search function (soft key SEARCH or MOD function) to locate the filename across all drives. Check TNC:\, network drives, and USB if connected.

The file may exist but in a different directory than expected. Note the actual location for path correction.

Correct the reference or restore file

Either edit the CALL statement to reference the correct path where file exists, or copy/transfer the missing file to the expected location. If file is completely missing, restore from backup or recreate it.

Always verify program logic after changing CALL paths - ensure tool compensation and coordinate system context remain correct.

Check cycle definition or table selection

Review the NC program for CYCL DEF statements or SEL TABLE commands. Common tables include point tables for drilling patterns, pallet tables, and preset tables. Note the exact filename referenced.

Point tables for SYS CYCLE 12 DRILLING PATTERN typically stored in TNC:\TABLE\POINT directory by convention.

Verify table file location

Navigate to expected table directory using PGM MGT. Standard locations: TNC:\TABLE for .TAB files, TNC:\TABLE\POINT for .PNT files. Check if file exists with correct extension and name.

Use MOD function FILE MANAGER settings to verify default search paths for table files on your specific control generation.

Restore or recreate table file

If table was deleted, restore from TNC:\BACKUP directory or external backup. If unavailable, create new table using appropriate editor (Table key for .TAB, or text editor for .PNT with correct format).

Point table format is critical - must contain correct header and coordinate structure or cycles will fail even if file exists.

Update program or table location

Either move the table file to the expected location or edit the program to reference the actual table location. Ensure path syntax matches control requirements.

Some shops standardize table locations in TNC.SYS to avoid path specification in programs - review with machine setup documentation.

Access system configuration

Press MOD key, enter system password (typically service level required), and select SYSTEM FILES or CONFIG DATA. Examine TNC.SYS file for file path references that might match the missing filename.

Modifying TNC.SYS incorrectly can prevent control startup. Document current settings before making changes.

Review recent system changes

Check if alarm appeared after software update, machine parameter changes, or system restore. Compare current TNC.SYS with backup version in SYS:\BACKUP or TNC:\SYSTEM\BACKUP.

Control creates automatic backups of TNC.SYS before updates - look for dated versions to identify what changed.