140-0026

Identify Updated Data Object

Read the alarm parameters '%1' (object type), '%2' (object name), and '%3' (attribute name) from the error log. Press MOD > Service > Error Messages to view complete alarm details with all parameters.

Common objects affected include tool.t, preset.pr, kinematics.h, and tncopt.sys files during major version updates.

Verify Software Version Change

Check MOD > System Settings > Software Info to confirm current NC software version. Compare with previous version documented in machine records to identify if upgrade occurred.

Updates from iTNC 530.xxx to TNC 640.xxx or within major build numbers (e.g., 340.xxx to 640.xxx) frequently trigger data structure updates.

Review Inserted Attribute

Open the affected data object (e.g., tool table via MOD > Tool Table or preset table via MOD > Datum Table) and verify the new attribute appears with appropriate default values.

New attributes typically receive safe default values (0, empty string, or OFF) - verify these defaults are appropriate for your machining operations.

Clear Alarm and Document

Acknowledge the alarm using the CE (Clear Error) key. Document the software version change and affected data objects in machine maintenance log for future reference.

This alarm is informational - the control has already corrected the data structure. No further action is typically required unless default values need adjustment.

Identify Imported File Source

Determine which file was recently imported via USB, network, or TNCbackup restore. Check MOD > File Management history or TNCbackup.sys log to identify the source file and timestamp.

Tool.t and preset.pr files from iTNC 530 controls frequently lack attributes required by TNC 640 software versions.

Compare File Structures

Create a new reference data object on the current control and compare its structure with the imported file. Use MOD > Programming > File Edit to view text-based data objects and compare attribute lists.

Use external text editor on backup USB to compare .t or .pr files side-by-side - newer versions show additional attribute columns.

Verify Default Attribute Values

Open the imported data object and check that automatically inserted attributes contain appropriate values. For tool tables, verify attributes like R2, DR, LCUTS using MOD > Tool Table form view.

Default values may not match your application requirements - verify tool data is correct before machining.

Update Import Procedures

If regularly importing from legacy controls, establish export/import procedure that includes format conversion or manual attribute addition before import to prevent recurring alarms.

Use TNCtest or DNC software to convert legacy data formats before importing to current control software version.

Access Kinematic Configuration

Navigate to MOD > System Settings > Kinematics to view active kinematic configuration. Note the '%1' parameter identifies which kinematic file was modified (machine.h, toolchng.h, etc.).

Do not modify kinematic files without proper authorization and backup - incorrect settings can cause collision or positioning errors.

Review Inserted Kinematic Attribute

Open the specific kinematic file using MOD > File Management and examine the newly added attribute '%3'. Compare with Heidenhain kinematic documentation for your machine configuration.

Common added attributes include new compensation parameters, extended axis definitions, or enhanced rotary axis configurations introduced in newer software.

Validate Kinematic Function

Perform kinematic test movements in manual mode using handwheel and MPG. Verify all axes respond correctly and no unexpected behavior occurs with the updated kinematic configuration.

Test with reduced feedrates (10-25%) and increased safety distance from fixtures and workpiece.

Contact Machine Builder if Necessary

If kinematic attributes were auto-inserted after software update, contact machine tool builder to verify default values are correct for your specific machine configuration and axis arrangement.

Keep machine-specific kinematic documentation and OEM contact information readily accessible for post-update verification.