235-0091

Access System Information

Boot control and press MOD key, navigate to 'System Information' > 'Module Overview' to view installed hardware module versions and firmware

Document all module part numbers and firmware versions before proceeding - this is critical for matching driver compatibility

Check Software Version Compatibility

In MOD function, go to 'System Files' > 'Version Info' and compare NC software build number with driver package version listed in system log during boot

Do not attempt manual driver updates without verified compatible versions from Heidenhain technical documentation

Review Recent Software Changes

Check 'System Log' under MOD for entries related to software updates or system restorations. Look for entries with 'Driver' or 'Module Init' keywords immediately before alarm occurrence

System log entries with timestamp just before alarm will show specific module names that failed initialization

Restore Known-Good Configuration

If alarm followed a software update, boot to previous system partition using MOD > 'Boot Options' > 'Select System Partition' and choose previous dated partition

TNC controls maintain multiple system partitions - always test new software on alternate partition before making it default boot partition

Access System File Directory

Press MOD key, navigate to 'System Files' > 'TNC:\system\' directory and locate machine.cfg or sysconfig.sys (depending on control generation)

Never edit system files directly on the control without backup - use TNCremo from external PC for safety

Verify Configuration File Integrity

Open machine.cfg in the TNC editor (read-only mode) and check for obvious syntax errors, incomplete lines, or unusual characters. Compare file size and date against backup or commissioning documentation

Configuration files should have consistent formatting - random characters or truncated sections indicate corruption

Restore Configuration from Backup

If corruption suspected, navigate to MOD > 'System Restore' and restore machine configuration from most recent backup archive. Alternatively, copy known-good configuration file from TNCremo backup location

Machine builders typically provide original commissioning files - contact them for baseline configuration if available

Perform System Consistency Check

After restoration, use MOD > 'System Functions' > 'Check System Consistency' to verify all configuration files match installed hardware and no orphaned references exist

This function cross-references all system files and will flag mismatches between configuration and actual hardware detection

Check Module LED Status

Visually inspect all control cabinet modules during startup. Green LEDs should be solid on CC/MC/UM modules. Flashing red or orange indicates module-level faults preventing driver initialization

Do not reseat modules with power applied - always disconnect main power and wait for capacitor discharge (minimum 2 minutes)

Access Module Diagnostic Display

In MOD function, go to 'System Information' > 'Module Health' and check status of each detected module. Note any modules showing 'Not Ready', 'Fault', or 'Initialization Error' status

Modules detected but showing initialization errors indicate communication is working but internal module firmware has issues

Review Module Communication Log

Navigate to MOD > 'System Log' > filter for 'Hardware' category. Look for backplane communication errors, timeout messages, or module not responding errors during boot sequence

Backplane communication errors typically show hex addresses - cross-reference these with module slot positions documented in machine electrical drawings

Reseat Suspect Modules

Power down completely, disconnect main power, wait 2+ minutes, then carefully remove and reseat identified module(s). Check backplane connector pins for damage or contamination before reinsertion

Use proper ESD precautions - grounding strap required when handling control modules