Heidenhain codes
HeidenhainParameterIntermediate30-120 minutes

140-0035

HEIDENHAIN 140-0035 - Data object divided into

Data object divided into

The loaded configuration data is from an older NC software version. A data object has been split into multiple objects according to update rules.

Root Cause Summary

The TNC control automatically divides data objects when they exceed internal structural limits defined by the control's database architecture. This is a protective measure to maintain system stability and ensure data integrity, particularly common with preset tables and tool management files that grow continuously during normal operation. The alarm serves as notification rather than a fault condition.

Safety

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

Causes and Fixes

  1. 1

    Access Preset Table Manager

    Press POS key (or PRESET TABLE softkey), then press 'Display all presets' to view the complete preset table and check the total number of entries. Note the REF system being used.

    The control typically names split tables with numeric suffixes like PRESET.PNT, PRESET_1.PNT, PRESET_2.PNT in the TNC:\table directory.

  2. 2

    Export and Archive Old Presets

    Navigate to PGM MGT, select the preset table (PRESET.PNT), press BACKUP softkey, and save to external storage. Then delete obsolete or redundant preset entries using the DELETE PRESET function.

    Always backup preset data before deletion - datum references cannot be recovered once deleted.

  3. 3

    Consolidate Preset Tables

    If multiple split tables exist, manually merge essential presets into a single table using the EDIT function in preset table mode. Keep total entries below 1800 to maintain operational margin.

    Use systematic numbering (e.g., presets 1-999 for machine 1, 1000-1999 for machine 2) to avoid future consolidation issues.

  4. 4

    Verify Table Accessibility

    Return to operating mode (Manual or Program Run) and test access to specific presets using G54-G57 or extended presets. Confirm all required datums are accessible without errors.

DIY Feasiblehigh confidence

Call a technician if:

  • ·Parameter values appear corrupted after migration
  • ·Machine kinematics behave unexpectedly
  • ·Safety systems not functioning properly

Prevention

  • Always backup machine configuration before software updates
  • Document current parameter settings before upgrading TNC software
  • Test all machine functions after software migration

Common Mistakes

  • Ignoring the alarm without verifying data integrity
  • Not updating documentation after parameter restructuring
  • Failing to test affected machine functions after data 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.