Heidenhain codes
HeidenhainParameterIntermediate30-120 minutes

140-0028

HEIDENHAIN 140-0028 - Data object inserted

Data object inserted

The loaded configuration data comes from an older control version. A missing data object was inserted by update rules during the migration.

Root Cause Summary

This message confirms successful completion of a data import or insertion operation. It typically occurs during intentional file transfers, system restores, network synchronization, or when the PLC/machine manufacturer's software automatically updates control tables. No fault condition exists - this is purely confirmatory feedback from the TNC system.

Safety

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

Causes and Fixes

  1. 1

    Verify Tool Table Contents

    Press the TOOL TABLE soft key (or access via Programming and Editing > Tool Table). Review all tool entries to confirm the imported data matches expectations, checking tool numbers, geometries, and compensation values.

    Use the search function (F5 key) in the tool table to quickly locate specific tool numbers if many entries were imported.

  2. 2

    Check Import Source File

    Press PGM MGT key, navigate to TNC:\ or the external storage location, and verify the timestamp and size of the .T file that was imported to ensure it was the correct version.

    The control automatically creates backup files with .Tbak extension - compare these if data appears incorrect.

  3. 3

    Acknowledge and Clear

    Press the CE key to acknowledge the message. The control will return to normal operation with the newly inserted tool data active.

    Do not continue machining until tool data has been verified - incorrect tool length or radius values can cause collisions.

DIY Feasiblehigh confidence

Call a technician if:

  • ·Configuration corruption persists after multiple restore attempts
  • ·Machine behavior changes unexpectedly after parameter insertion
  • ·Unable to identify which parameters were inserted

Prevention

  • Always backup configuration before software updates
  • Document all parameter changes with version information
  • Regularly validate configuration integrity
  • Maintain version-specific backup sets

Common Mistakes

  • Ignoring the alarm assuming it's harmless
  • Not verifying inserted parameter values match machine requirements
  • Restoring old backups without checking version compatibility
  • Failing to test machine functions after parameter insertion

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.