Heidenhain codes
HeidenhainParameterIntermediate30-120 minutes

140-0029

HEIDENHAIN 140-0029 - Incorrect insertion value in data object Attribute

Incorrect insertion value in data object Attribute

The loaded configuration data comes from an older control version. An attribute was inserted by update rules, but the insertion value specified in the rule is incorrect.

Root Cause Summary

The root cause is an insertion of data that violates the defined constraints for a specific attribute within a TNC data object structure. This occurs when user input, imported data, or system configuration contains values that do not match the expected data type, format, or permissible range. The control's validation mechanism rejects the improper value to maintain data integrity within the system tables and configuration files.

Safety

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

Causes and Fixes

  1. 1

    Identify affected tool table attribute

    Press MOD key, select 'Tool Table' and locate the tool number or name referenced in '%2'. Check the attribute '%3' mentioned in alarm (common: L=length, R=radius, R2=radius2, LCUTS=cutting edge length, ATP=auto tool changer position).

    The alarm displays immediately after pressing ENT on an invalid entry—the cursor remains on the problematic field.

  2. 2

    Verify data type and range

    Ensure numeric fields contain only numbers and decimal points. Check that values are within permissible ranges: tool lengths typically ±9999.9999mm, radii 0-999.9999mm, pocket numbers 0-254. Remove any alphabetic characters except in NAME or DOC fields.

    Do not use comma as decimal separator; TNC controls require period (.) for decimal point.

  3. 3

    Correct and validate entry

    Enter correct value, press ENT to confirm. If alarm persists, delete the entire tool entry and re-create it. Verify tool.t file integrity by checking file size and date in PGM MGT.

DIY Feasiblemedium confidence

Call a technician if:

  • ·Multiple data objects affected simultaneously
  • ·Kinematic configuration errors persist
  • ·Machine parameters cannot be properly updated

Prevention

  • Always backup configuration before software updates
  • Verify backup file compatibility before restoration
  • Maintain updated machine parameter documentation
  • Test configuration changes in simulation mode first

Common Mistakes

  • Restoring complete backups from incompatible TNC versions
  • Ignoring software version compatibility warnings
  • Not documenting parameter changes during updates
  • Skipping system validation after configuration changes

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.