Heidenhain codes
HeidenhainParameterIntermediate30-120 minutes

140-0034

HEIDENHAIN 140-0034 - Data object moved to file

Data object moved to file

The loaded configuration data is from an older NC software version. A data object was saved in the wrong file and has been moved according to update rules.

Root Cause Summary

This message indicates the TNC control has automatically preserved a data object by moving it to an archive or backup file. This is a protective measure performed during system maintenance, updates, or when the control detects potential data integrity issues. The original data is safeguarded and can be restored if needed.

Safety

  • Refer to Heidenhain service manual
  • Ensure qualified technician performs repairs

Causes and Fixes

  1. 1

    Confirm Update Activity

    Press MOD key → Software Version Info to check if a recent software update occurred. Compare displayed version with previous known version.

    TNC controls always create timestamped backups during updates. The filename in '%3' typically includes a date/time stamp.

  2. 2

    Verify Data Object Integrity

    Access the data object type indicated in '%1' (e.g., if 'Tool Table', press TOOL TABLE key; if 'Preset Table', press POS key). Verify all entries are present and correct.

    After updates, the control may migrate data formats. The moved file represents the pre-migration version.

  3. 3

    Locate and Document Backup

    Press MOD → File Management, navigate to the path shown in '%3'. Note the backup file location and size for future reference.

    Standard backup location is typically TNC:\system\backup\ or TNC:\backup\ depending on control generation.

  4. 4

    Test Machine Operation

    Perform a dry run test of a known program to verify tool data, offsets, and presets function correctly with the current active data objects.

    Use dry run mode with feed override at 0% initially to verify correct tool selection and offset application.

DIY Feasiblehigh confidence

Call a technician if:

  • ·Configuration files are corrupted beyond recovery
  • ·Machine parameters are lost after migration
  • ·Servo axes fail to function after data migration

Prevention

  • Always backup machine parameters before software updates
  • Use compatible TNCremo versions for data transfer
  • Regularly check file system integrity
  • Document software version history

Common Mistakes

  • Ignoring the alarm as purely informational without verification
  • Manually moving configuration files
  • Not backing up parameters before software updates
  • Using incompatible TNCremo versions

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 free

Was this guide helpful?

Always verify with your machine manual or a certified technician before performing service procedures.