140-0025

Identify Affected Tool Table

Navigate to Programming and Editing mode, press 'Tool Table' softkey. Check which tool table file is active (typically TOOL.T). Note the '%1' parameter from alarm message which identifies the exact data object.

The alarm message variables %1 (object name), %2 (object type), and %3 (attribute name) provide exact identification—write these down before clearing the alarm.

Review Tool Table Attributes

Open the affected tool table file. Check for uncommon or legacy column headers. Compare against current TNC documentation for supported tool attributes (L, R, R2, DL, DR, DR2, TL, RS, LS, LCUTS, ANGLE, TT, RT, etc.).

Older TNC controls used different attribute names for tool offset types—these get automatically converted or removed during import.

Export Reference Tool Table

Create a new tool table using current TNC version: Programming mode → Tool Table → press 'New Tool Table' softkey. Define a test tool to generate current attribute structure. Compare this reference against imported table.

Use the reference tool table as a template for restructuring imported tool data if multiple attributes were removed.

Verify Tool Functionality

Test that all tool data is still accessible and functional after attribute removal. Run tool call (TOOL CALL) in MDI mode for affected tools. Verify radius, length, and all compensations are correct.

Always verify tool geometry after data migration—removed attributes may have contained critical offset data that needs manual re-entry.

Locate Affected Data Object

Press MOD key → Select 'File Management' → Navigate to TNC:\table directory. Identify the file matching '%1' from alarm message (preset.pr, pallet tables, or .tab files).

Preset and pallet table structures changed significantly between TNC 4xx/TNC 320 and iTNC 530/TNC 620 generations.

Check Preset Table Structure

In Manual Operation mode, press 'Preset Table' softkey. Review active preset table for missing or unusual entries. Standard attributes should include: DOC, X, Y, Z, A, B, C, and comment fields.

If multiple presets show zero values after import, the removed attribute likely contained critical coordinate data requiring manual re-establishment.

Re-establish Critical Data

Use the 'Touch Probe' functions or manual entry to re-establish any preset data that may have been lost. Document original values if available from source control for verification.

Never assume preset values migrated correctly—always verify with physical measurements or proven part program before production machining.

Update Data Object to Current Version

Save the modified table using current TNC format: Preset Table → press 'Save' softkey → confirm overwrite. This ensures future compatibility without attribute conflicts.

Create dated backup copies before overwriting: use format 'preset_YYYYMMDD.pr' in TNC:\backup directory.

Verify Software Version Change

Press MOD key → Select 'System Information' → note current NC Software version. Compare against previous version documentation or backup records to confirm recent update.

Check MOD → Information → 'Logbook' for software update history with timestamps.

Review Update Documentation

Consult the Heidenhain Technical Manual for your specific software version. Look for 'Migration Notes' or 'Compatibility Information' sections that list deprecated attributes and their replacements.

Heidenhain typically provides attribute migration tables in software release notes—these show old vs. new attribute names for data objects.

Check All System Data Objects

Navigate to Programming and Editing → press MOD → 'File Management' → systematically check tool.t, preset.pr, and any custom .tab files. Open each to verify no critical data loss occurred beyond removed attributes.

After major version updates (e.g., TNC 530 to TNC 640), multiple data objects may be affected—check all system tables before resuming production.