160-0123

Access Configuration Files

Enter MOD mode (key switch to position 2), select 'System Files', navigate to TNC:\system\ and open SIK.SYS for review. Look for ALIAS_STROBE sections and note configured types.

Always create a backup copy of SIK.SYS before making any modifications - store it on external USB media with date stamp.

Identify Missing Strobe Type

Cross-reference the %1 parameter from the alarm message with existing ALIAS_STROBE entries in SIK.SYS. Check machine manufacturer documentation for required strobe type definitions for your specific hardware configuration.

The %1 parameter typically indicates the strobe number or type - common values are 0-3 for different synchronization channels.

Add Missing Configuration Entry

If the strobe type is missing, add the appropriate ALIAS_STROBE definition to SIK.SYS using the exact syntax from machine documentation. Ensure proper formatting with correct module addresses and timing parameters.

Incorrect strobe configuration can cause communication failures with drives or I/O modules. Only use parameters provided by machine manufacturer or Heidenhain technical support.

Reload Configuration

Save the modified SIK.SYS file, exit MOD mode, and perform a complete control reboot (power cycle) to ensure all configuration changes are loaded into active memory.

Monitor the boot sequence on screen - configuration errors will typically display during initialization phase.

Verify Hardware Detection

Navigate to Test Mode -> System Test -> Hardware Status and verify all interface modules are listed with green status. Check specifically for CC (Component Communication) or CMA (Communication Module Analog) modules.

Ensure control power is stable and all module connections are secure before checking hardware status.

Check Module Seating and Connections

Power down the control completely, open the control cabinet, and verify all interface cards are fully seated in their backplane connectors. Check ribbon cables and connector pins for damage or corrosion.

Follow proper ESD precautions and lockout/tagout procedures before opening control cabinet. Ensure mains power is disconnected.

Review PLC Diagnostics

In PLC Mode (Operating Mode -> PLC), check the PLC error log and module diagnostics for any communication errors related to the hardware modules. Look for timeout or initialization failure messages.

The PLC diagnostics often show more detailed hardware communication errors than the main alarm display.

Perform Module Reset

If module is detected but showing errors, attempt a module reset through Test Mode -> System Test -> select specific module -> Execute Reset. Then perform full control reboot.

Some interface modules require specific power-up sequences - consult module documentation for proper initialization procedure.

Check Software Version Compatibility

Navigate to MOD -> System Information and note the current TNC software version. Compare against machine manufacturer's configuration documentation to verify configuration file format compatibility.

Heidenhain periodically changes configuration syntax between major version releases - always review release notes for configuration file changes.

Review Software Update Documentation

Access the TNC software release notes (typically in TNC:\system\doc\ or from Heidenhain website) and search for any changes related to alias strobe configuration or CMA/CC module handling.

Pay special attention to sections marked 'Configuration Changes' or 'Compatibility Notes' in release documentation.

Update Configuration File Syntax

If syntax changes are documented, modify SIK.SYS or CMA.SYS files according to new format requirements. Common changes include additional timing parameters or module addressing format modifications.

Keep original configuration file backup accessible in case updated syntax causes additional errors.

Contact Machine Builder for Updated Configuration

If unable to resolve through documentation, contact the machine tool builder for updated configuration files compatible with current TNC software version. Provide exact control software version number and machine serial number.

Many machine builders maintain version-specific configuration files on their support portals - check online resources before calling.