axismd.ai
Heidenhain Controller
Parameter · Intermediate · 30-120 minutes
HEIDENHAIN 120-0006 - Configuration of soft key not readable
The control's user interface initialization process cannot parse the soft key configuration file due to file corruption, syntax errors, or version incompatibility. This prevents the proper display and assignment of programmable soft keys on the TNC screen. The issue typically stems from manual editing errors, interrupted file transfers, or mismatched configuration files after software updates.
120-0006
HEIDENHAIN 120-0006 - Configuration of soft key not readable
Configuration of soft key not readable
The control cannot read the soft key configuration because the requested key is missing from the setup data. Verify the configuration dataset to resolve this issue.
Root Cause Summary
The control's user interface initialization process cannot parse the soft key configuration file due to file corruption, syntax errors, or version incompatibility. This prevents the proper display and assignment of programmable soft keys on the TNC screen. The issue typically stems from manual editing errors, interrupted file transfers, or mismatched configuration files after software updates.
Safety
- Refer to Heidenhain service manual
- Ensure qualified technician performs repairs
Causes and Fixes
- 1
Access file manager and locate configuration files
Press PGM MGT key, navigate to TNC:\ drive, open system folder, then config folder. Look for files with .SOF or .SKY extensions (names may be machine-specific like MACHINE.SOF or SOFTKEY.SKY).
Use SHOW ALL FILES option in MOD settings if configuration files are not visible in standard file manager view.
- 2
Rename problematic soft key file
Select the soft key configuration file, press RENAME softkey, and add .BAK extension (e.g., MACHINE.SOF becomes MACHINE.SOF.BAK). This prevents the control from loading the corrupted file.
Document the original filename and location before renaming. Some machine functions may be unavailable until proper configuration is restored.
- 3
Restart control to load default configuration
Perform complete control restart (power cycle or controlled shutdown/restart through MOD menu). Control should boot without the alarm using internal default soft key layout.
If alarm clears with renamed file, the original configuration was definitely the problem. Request correct file from machine builder.
- 4
Restore or obtain correct configuration file
If you have backup, copy known-good .SOF/.SKY file to TNC:\system\config. Otherwise, contact machine tool builder for the correct soft key configuration specific to your machine model and control software version.
Always keep backup copies of working configuration files on external USB drive after any successful customization.
Call a technician if:
- ·If configuration data cannot be restored after multiple attempts or backups are unavailable.
- ·If hardware diagnostics indicate a failing memory module or persistent communication errors.
Prevention
- Regularly back up configuration data to an external drive or cloud storage after any changes.
- Ensure software and firmware updates are performed during scheduled maintenance with stable power.
- Train operators to avoid manual edits to soft key configurations without proper authorization.
- Schedule periodic hardware inspections to check for loose connections or wear.
Common Mistakes
- Attempting to update software or firmware without backing up current configuration data, leading to permanent loss.
- Ignoring diagnostic logs or error messages during troubleshooting, missing critical clues to the root cause.
Seeing Multiple Alarms?
Seeing another alarm with this one? Enter the code.
Get machine-aware diagnosis
AxisMD logs alarms against your actual machines, tracks patterns, and gives AI context your manual doesn't have.
Start freeWas this guide helpful?
Always verify with your machine manual or a certified technician before performing service procedures.