130-0002

Access Error Logging

Navigate to TNC:\sys\Log\ directory using the file manager (PGM MGT key). Open ErrorLog.txt to identify specific system error codes and timestamps that correlate with alarm 130-0002.

Copy error log files to USB drive before performing any system recovery procedures—these logs are invaluable for Heidenhain service diagnostics.

Verify Software Version Integrity

Press MOD key, select 'System Information' and document the NC software number (e.g., 340590 XX). Cross-reference with the software label on the control cabinet to verify correct installation.

Mismatched software versions between main control and expansion modules can cause system errors.

Check PLC Program Status

Access MOD > 'PLC' > 'Program Information' to verify PLC program compilation status. A corrupted or improperly compiled PLC program can cause system resource conflicts.

If PLC program shows errors, restore from backup (.PLC or .H file) from TNC:\plc\backup\ directory.

Perform Software Recovery

If corruption is suspected, initiate NC software reinstallation using the Heidenhain installation media. Boot from USB/DVD into installation mode and select 'Repair Installation' option to preserve machine parameters.

Always backup TNC:\sys\par\ directory and machine parameters (OEM cycle) before software reinstallation.

Perform Hardware Diagnostic Boot

Power off control completely. Hold MOD key while powering on to enter Service Mode. Select 'Hardware Diagnostics' from the service menu to run automated component tests.

Service Mode access may require service password depending on control configuration.

Check System Component Status

In MOD function, navigate to 'System' > 'Diagnosis' > 'Hardware Components'. Verify all listed components (CPU, RAM, storage, interfaces) show green status indicators without fault codes.

Red or yellow indicators on CC (Control Computer) or IPC (Industrial PC) modules indicate hardware requiring replacement.

Test Memory Integrity

From Service Mode, select 'Memory Test' option if available. This performs comprehensive RAM testing. Note any reported memory address failures for service documentation.

Memory tests can take 15-30 minutes depending on installed RAM capacity.

Inspect Control Cabinet Environment

Check ambient temperature inside control cabinet (should be below 45°C). Verify cooling fans operate correctly. Inspect CPU board for physical damage, bulging capacitors, or dust accumulation.

Thermal cycling from poor ventilation is a common cause of intermittent system errors on older TNC controls.

Check File System Integrity

Boot into Service Mode (MOD key during power-up) and select 'File System Check' or 'Disk Check' option. Allow the system to scan and repair any corrupted sectors on the system partition.

Do not interrupt file system check once started—interruption can cause additional corruption.

Review System Partition Space

In normal operation, access MOD > 'System' > 'Storage Information'. Verify SYS: partition has at least 20% free space. Full system partitions prevent proper logging and temporary file creation.

Delete old log files from TNC:\sys\Log\ directory if system partition is near capacity, keeping only recent 30 days.

Restore System Configuration

If file corruption is confirmed, restore system configuration from backup. Navigate to TNC:\sys\par\ and restore .CFG files from TNC:\backup\ directory if available.

Heidenhain controls automatically create configuration backups—check file dates in backup directory before restoring.

Perform Clean Boot Test

Temporarily rename the PLC program file (TNC:\plc\plc.h) to disable PLC execution. Reboot control to determine if PLC program is corrupting system resources. If alarm clears, PLC program requires debugging.

Machine functionality will be limited without PLC program—perform only for diagnostic purposes.