axismd.ai
Heidenhain Controller
Parameter · Intermediate · 30-120 minutes
HEIDENHAIN 140-0038 - Data object: Key was changed from to
This alarm occurs when the TNC control detects that an internal data object's key identifier has been modified from its previous value. This typically happens during configuration changes, software updates, or parameter restorations where the control's internal data structure mappings are updated. In most cases, this is an informational notification rather than a fault condition.
140-0038
HEIDENHAIN 140-0038 - Data object: Key was changed from to
Data object: Key was changed from to
The loaded configuration data is from an older NC software version. A data object key was changed by update rules during migration.
Root Cause Summary
This alarm occurs when the TNC control detects that an internal data object's key identifier has been modified from its previous value. This typically happens during configuration changes, software updates, or parameter restorations where the control's internal data structure mappings are updated. In most cases, this is an informational notification rather than a fault condition.
Safety
- Refer to Heidenhain service manual
- Ensure qualified technician performs repairs
Causes and Fixes
- 1
Review Recent Configuration Changes
Press MOD key, navigate to System Files → Configuration Files. Check the timestamp of machine.CFG and other relevant configuration files to identify recent modifications or restorations.
Use the file comparison feature in MOD to compare current CFG with backup versions to pinpoint exact changes.
- 2
Verify Data Object Integrity
Note the data object name from alarm parameter %1. Access MOD → Machine Parameters and search for parameters related to this object name to verify values are appropriate for your machine configuration.
Data objects typically relate to kinematic configurations, tool management, or axis assignments—verify these functional areas work correctly.
- 3
Acknowledge and Test Functionality
Clear the alarm using CE key. Perform functional test of the machine area related to the data object (e.g., test axis movement if axis-related, test tool changer if tool data object).
Test in manual mode at reduced feedrate first to ensure no unexpected machine behavior.
- 4
Create New Baseline Backup
If functionality is correct, create a new configuration backup via MOD → Backup/Restore to establish current configuration as the new baseline with updated key values.
Label backup with date and note 'Post key update' for future reference.
Call a technician if:
- ·Database rebuild fails repeatedly
- ·Critical servo parameters show incorrect values after translation
- ·Machine exhibits unexpected motion behavior after key translation
Prevention
- Always document TNC software version before creating backups
- Verify parameter compatibility before transferring configurations between different TNC versions
- Regularly backup configuration after software updates
- Use TNC-specific backup tools rather than manual parameter copying
Common Mistakes
- Ignoring the alarm assuming it's informational only
- Not verifying critical machine parameters after key translation
- Transferring complete configurations between incompatible TNC versions
- Failing to create new baseline backup after successful translation
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.