Heidenhain codes
HeidenhainParameterIntermediate30-120 minutes

140-0027

HEIDENHAIN 140-0027 - Data object removed

Data object removed

The loaded configuration data comes from an older control version. A data object was removed by update rules even though it is still supported.

Root Cause Summary

This alarm is generated by the TNC's file management system when a data object is intentionally or automatically removed from the control. It serves as a notification and audit trail entry rather than indicating a fault condition. The alarm typically requires acknowledgment but does not prevent operation unless the removed object was critical to machine function.

Safety

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

Causes and Fixes

  1. 1

    Verify alarm details

    Press ERROR key to display the alarm log. Note the exact data object type '%1' (e.g., 'Program', 'Tool Table', 'Preset Table') and name '%2' that was removed.

    The alarm text provides complete path information - document this for recovery if needed

  2. 2

    Check deletion timestamp

    Navigate to MOD > System > Log Files > Event Log. Filter for recent deletion events to identify who performed the deletion and exact time.

    Event log entries include user login information if password protection is enabled

  3. 3

    Restore from backup if necessary

    If the deleted object is required, press PGM MGT key, navigate to TNC:/ directory structure, and copy the file from backup location (USB drive or network path configured under MOD > Network Settings).

  4. 4

    Clear alarm and verify

    Press CE (Clear Error) key to acknowledge the alarm. Verify machine operation is unaffected. If the deleted file was critical, the control will generate additional alarms indicating missing dependencies.

DIY Feasiblehigh confidence

Call a technician if:

  • ·Multiple critical machine parameters affected
  • ·PLC program compilation failures persist
  • ·Machine kinematic behavior changes after parameter migration

Prevention

  • Maintain detailed parameter documentation before TNC software updates
  • Create complete system backups including all configuration data
  • Review TNC migration guides before upgrading control software

Common Mistakes

  • Ignoring the alarm assuming it's harmless
  • Not documenting which parameters were removed
  • Failing to verify machine functionality after parameter migration

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.