130-0097

Access System Error Log

Press MOD key, navigate to System Test > Error Messages or Diagnostic Log. Review all entries immediately preceding alarm 130-0097 for related internal errors (especially 100-series or other 130-series codes).

Look for repeating error patterns or specific task IDs mentioned in log entries—these indicate which subsystem is failing.

Perform Complete Cold Restart

Switch control OFF at main disconnect. Wait minimum 30 seconds for all capacitors to discharge. Power ON and observe boot sequence. If alarm occurs during boot, this confirms software corruption.

Ensure machine axes are in safe position before power cycling as references will be lost.

Check Software Version Consistency

MOD > System Information > Software Versions. Verify NC Software version matches PLC Software version and all firmware components. Mismatched versions after partial update can cause system errors.

Note the exact version numbers and build dates—provide these to service as they indicate which software generation is installed.

Attempt System Restore from Backup

If control boots to MOD mode, navigate to System Restore or Recovery functions. Attempt to restore from most recent known-good backup or factory default configuration if available.

System restore will overwrite current configuration—only proceed if machine data backup exists.

Prepare for Software Reload

If alarm persists, prepare for complete TNC software reload. Export all error logs via TNCremoNT or USB (MOD > File Management > Export Diagnostics). Contact Heidenhain with logs and software version for reload media.

Keep machine documentation ready including control serial number, software licensing information, and any custom PLC code backups.

Review PLC Program Status

Access MOD > PLC Programming > Program Status. Check if PLC runtime shows errors, stopped state, or cycle time violations. PLC task failures can cascade into system errors.

Note the PLC cycle time display—values consistently above 10ms on iTNC/TNC 640 or 20ms on TNC 530 may indicate processing overload.

Isolate PLC Influence

If possible in MOD mode, temporarily disable custom PLC program execution (rename or move PLC program file). Restart control to test if alarm clears, indicating PLC code triggered system fault.

Disabling PLC will remove all machine logic—only perform with machine in safe state and E-stop enabled.

Check Real-Time Performance

MOD > System Test > Real-Time Monitor or Performance Display. Observe CPU load, task jitter, and cycle time consistency. Excessive load or timing violations indicate resource exhaustion causing communication failures.

Look for sudden spikes in CPU load percentage—values sustained above 85% can cause inter-process communication timeouts.

Test with Minimal Configuration

Boot control with minimal axis configuration and no NC program loaded. If system stabilizes, gradually re-enable components to identify which subsystem triggers the communication fault.

This isolates whether the fault is hardware-based (occurs even minimally configured) or software-based (triggered by specific processes).

Perform Hardware Self-Test

Boot into Service Mode (hold specific key combination during startup per control model). Execute MOD > System Test > Hardware Test or Memory Test functions to identify failing components.

Service Mode access: typically hold CE + MOD or other key combination during power-on. Consult service documentation for exact procedure for your TNC model.

Check Environmental Conditions

Verify control cabinet temperature is within specification (typically below 45°C). Inspect cooling fans for operation. Check for dust accumulation on processor heatsinks. Overheating can cause intermittent processor faults.

Allow control to cool completely before opening cabinet—verify line power is disconnected.