120-0028

Identify the affected configuration file

Record the complete alarm message including the file name shown in the '%1' parameter. Common files include machine.sys, sysconfig.sys, or axis configuration files. This determines the scope of the problem.

Take a photo of the alarm screen - the exact file path helps Heidenhain service provide targeted support

Access MOD function diagnostic mode

Restart the control while holding the CE key to enter MOD function. Navigate to 'System Diagnosis' and check the system log files for additional error messages related to file access failures.

MOD function provides low-level access - only navigate to diagnostic menus, do not modify system settings without Heidenhain guidance

Attempt configuration file restoration

From MOD function, navigate to 'Backup/Restore' and check if an automatic system backup exists. If available, restore the most recent backup that predates the alarm occurrence.

The control automatically creates backups in TNC:\system\backup\ - these can be invaluable for recovery

Verify file system integrity

In MOD function, run 'Check File System' utility to scan the storage medium for errors. Allow the check to complete and note any errors reported. The system may automatically repair minor file system inconsistencies.

File system repair can take 10-30 minutes depending on storage size - do not interrupt this process

Check storage media health indicators

Boot into MOD function and navigate to 'System Information' > 'Storage Device'. Check the SMART status (if available) and look for indicators of media errors, bad sectors, or read failures.

On TNC 620/640 controls, SMART data provides early warning of impending storage failure

Perform storage media read test

In MOD function diagnostic tools, run a surface scan or read test on the storage device. Multiple read errors or slow access times indicate failing media that requires replacement.

A failing storage device can cause intermittent issues - replace it before complete failure causes data loss

Create emergency backup if possible

If the control can boot partially, immediately create a full system backup to external USB media using the TNC backup function. Navigate to MOD > Backup/Restore > Full System Backup.

Even with errors present, attempt the backup - partial data recovery is better than none

Replace storage media and restore system

Obtain genuine Heidenhain replacement CF card or SSD with correct part number for your control model. Install new media and restore from backup, or perform fresh installation using Heidenhain installation media.

Use only Heidenhain-approved storage media - generic cards may lack required specifications and cause ongoing issues

Verify software installation completeness

Check the control software version in MOD function > System Information. Compare against the intended version. Look for indicators like 'installation incomplete' or version mismatches between NC kernel and system components.

Version string format should be complete (e.g., '340 590 07') - truncated versions indicate installation problems

Review installation log files

In MOD function, navigate to log file viewer and open the software installation log (typically install.log or update.log). Look for errors during the configuration file migration or setup phase.

Installation logs show exact step where the process failed - critical information for support calls

Re-run configuration setup wizard

If the software installed but configuration data failed to migrate, access MOD > Setup > System Configuration. Re-run the initial configuration wizard, which may regenerate missing configuration files using default templates.

This may reset machine-specific parameters - have your machine manufacturer's configuration data available

Perform clean software reinstallation

Using Heidenhain installation media (USB or network source), perform a complete software reinstallation. Select the option to preserve user data if possible, then restore machine configuration from backup after installation completes.

Contact your machine tool builder for the specific machine configuration files before reinstalling - they may have custom parameters