140-0021

Access File Management

Press the PGM MGT (Program Management) key to open the file manager and navigate to the directory where the renamed file is located (typically TNC:\ or the working directory shown in the message).

Use the search function in PGM MGT by pressing the 'Find' soft key to quickly locate both the original and renamed files.

Identify Duplicate Files

Look for both filenames mentioned in the message ('%1' and '%2'). Compare file sizes and timestamps to determine which file is the intended version.

Select each file and press 'File Info' soft key to view detailed creation and modification timestamps.

Resolve Naming Conflict

Delete the unwanted duplicate file, or rename one of the files to a unique descriptive name. Select the file, press the 'Rename' soft key, and enter the desired name following TNC naming conventions (no special characters, max 16 characters).

Establish a naming convention with version suffixes (e.g., PART_V1.H, PART_V2.H) to prevent future conflicts.

Verify File Integrity

Open the file in editing mode to verify its content is correct and complete. For NC programs, check the program header and final M30/M02. For tables, verify all data rows are present.

For critical programs, run a test graphics simulation before machining to ensure the correct program version is active.

Check Backup Log

Press MOD key, navigate to 'Backup/Restore', then select 'Log' to review the backup operation details and identify which files were renamed during the restore process.

TNCbackup always creates a detailed log file - review it before deleting any renamed files to understand what was restored.

Compare File Versions

In PGM MGT, locate both the original file and the renamed backup version. Use the file information display (select file, press 'File Info') to compare dates and determine which is more recent or correct.

The system typically appends a number or timestamp to the renamed file (e.g., _001, _002) - the higher number is usually the restored version.

Consolidate Files

After determining the correct version, delete the obsolete file and rename the keeper file to the proper working name. Update any program calls or references if necessary.

Before deleting files restored from backup, ensure the remaining version contains all required content - deleted files cannot be recovered without re-restoring the backup.

Update Tool or Datum Tables

If the renamed object is a tool table (TOOL.T) or datum table (DATUM.D), verify that the active table is the correct one by checking in the respective table management screens (Tool Table or Datum Table editing modes).

The control uses the table file with the exact expected name - if your working table was renamed, copy its content to the correct filename rather than renaming.

Review PLC Program Logic

Access the PLC programming environment (if authorized) by entering the password in MOD mode, then review PLC modules that handle file operations, looking for FUNCTION FILE commands or data object management routines.

Modifying PLC programs requires authorization and proper training - contact your machine tool builder or PLC programmer if you are not qualified to edit PLC code.

Check PLC Error Memory

In MOD function, navigate to 'PLC' then 'Error Memory' to check if the PLC logged any file operation errors or warnings that correlate with the rename event timestamp.

Cross-reference the 'key' value from the alarm message with PLC marker addresses to identify which PLC routine triggered the file operation.

Examine Automated File Generation

If your PLC automatically generates measurement protocols, cycle time logs, or production reports, verify the file naming logic includes unique identifiers (timestamps, serial numbers) to prevent conflicts.

Implement date-time stamps in automatically generated filenames using PLC string formatting to ensure uniqueness (e.g., LOG_YYYYMMDD_HHMMSS.txt).