130-0190

Perform extended power cycle

Power off the complete control system including the main power supply. Wait minimum 30 seconds to allow all capacitors to discharge and volatile memory to clear completely. This ensures all process structures are cleared from system memory.

For persistent issues, disconnect the battery backup on NC software controls (if present) during the power-off period to force complete memory clearing.

Verify clean startup

Power on and observe the boot sequence. Watch for the Heidenhain logo and normal progression through boot screens. The control should reach the operating mode selection screen without errors.

If the alarm reappears immediately, this indicates the issue is not orphaned processes but likely file system or software corruption.

Check system process status

Enter Service Manager mode (hold down key while booting). Navigate to System Diagnostics and review active process list to verify no duplicate or zombie processes exist.

Service Manager mode provides elevated access - do not modify settings unless instructed by Heidenhain service.

Access TNCdiag diagnostics

From the control operating mode, press MOD function key. Navigate to TNCdiag using the file manager. Open TNCdiag.txt located in the TNC:\ root directory to review current system resource utilization.

Look specifically for memory utilization percentages and any warnings about shared memory or IPC resources near the end of the TNCdiag file.

Check disk space availability

In Programming and Editing mode, access the file manager (PGM MGT key). Review available space on the TNC:\ partition. Ensure at least 20% free space remains for system operations and temporary file creation.

Never delete system files or folders you do not recognize. Only remove user-created NC programs, tool tables, or backup files.

Reduce memory load

Close any open NC programs not currently needed. Remove excessively large programs from the Selected contour buffer. Restart the control to clear program memory cache and reset resource allocation.

Programs with extensive point tables or complex 3D contours can consume significant memory even when not actively running.

Review background services

Check if optional services like network file sharing, DNC communication, or remote desktop are consuming excessive resources. Temporarily disable non-essential services via MOD > System Configuration if resource issues persist.

Heidenhain's StateMonitor or RemoTools connections consume system resources even when not actively transmitting data.

Boot into Service Manager

Power cycle the control. During boot, when the Heidenhain logo appears, hold down the Service Manager access key (typically defined in machine parameters or by machine builder). This accesses the control's maintenance environment.

Service Manager credentials may be required. Contact your machine tool builder or Heidenhain service if access is password-protected.

Execute file system check

In Service Manager, navigate to Maintenance > File System Check. Select the system partition and execute a read-write check with automatic repair enabled. This runs fsck utility on the Linux file system to repair corrupted structures.

This operation may take 10-30 minutes depending on partition size. Do not interrupt or power off during the check.

Review system log for errors

After file system check completes, access System > View Logs in Service Manager. Look for kernel errors, I/O errors, or disk-related warnings that occurred prior to the alarm. Document any repeated error patterns.

Repeated I/O errors on the same disk sectors indicate potential hardware failure of the storage device (SSD/CF card).

Perform normal boot test

Exit Service Manager and allow normal control boot. Verify the alarm does not recur. If alarm persists, file system damage may be beyond automatic repair, requiring software reinstallation.

If reinstallation is needed, back up all machine parameters, tool tables, presets, and NC programs before proceeding.