140-0024

Identify the renamed attribute details

Press MOD key, navigate to System Error Messages, and record the complete alarm text including data object '%1', object type '%2', and attribute '%3' values displayed in the alarm message.

Screenshot or write down all three parameter values as they are essential for locating the affected configuration element.

Check NC software version and release notes

Press MOD key, select System Information, note the current NC Software number. Access the Heidenhain Service Pack Notes or Software Update Documentation for your specific control model (TNC 320/530/620/640) to find the attribute rename reference table.

Heidenhain typically provides attribute conversion tables in the 'Configuration Changes' section of service pack documentation.

Update machine parameter references

Press MOD key, enter password if required, select Machine Parameters. Search for the old attribute name identified in step 1 and verify the system has automatically remapped it to the new name. Document any parameters that require manual adjustment.

Do not modify machine parameters without OEM authorization or complete backup of current settings.

Verify PLC program compatibility

Access the PLC programming environment (MOD > PLC > Edit) and search for any references to the old attribute name in markers, data objects, or function calls. Update to the new attribute naming convention as documented in the release notes.

Use the PLC search function (Find Text) to locate all instances of the old attribute name throughout the PLC program.

Clear alarm and verify system stability

Acknowledge the alarm using the CE (Clear Error) key. Perform a complete control restart (power cycle or CTRL+ALT+DEL reboot). Verify the alarm does not reappear and check the error log for any additional related messages.

After reboot, run through a complete machine initialization sequence to ensure all data objects load correctly with the new attribute names.

Identify the imported configuration source

Determine which configuration file was recently imported (machine parameters, PLC configuration, or system backup). Check the file date and source control version by examining the file header information in the Configuration Editor (MOD > Configuration Data Management).

Configuration files contain version stamps in their headers - use a text editor on the TNC to view .CFG or .H files to identify source version.

Access data object in Configuration Editor

Press MOD, navigate to the specific data object type mentioned in the alarm ('%2' parameter). Use the Configuration Editor's search function to locate object '%1' and examine the attribute structure for the renamed attribute '%3'.

The Configuration Editor provides a tree view structure - expand all nodes under the affected object to see both old and new attribute names if both exist.

Compare with control's expected structure

In the Configuration Editor, access the template or default structure for the data object type by selecting 'Show Default' or 'Template View'. Compare the imported attribute names with the control's current expected attribute names and note differences.

Create a reference document listing old vs. new attribute names for future imports from the same source.

Manually remap or update attribute references

Either manually edit the imported configuration file to use new attribute names before re-importing, or allow the control to complete its automatic remapping and verify the values transferred correctly by comparing key parameter values between source and destination.

Always create a backup of the current working configuration before accepting imported configurations with renamed attributes.

Validate functionality after remapping

After clearing the alarm, test all machine functions that depend on the affected data object, including axis movement, spindle operation, tool management, or custom PLC functions. Verify no data was lost during the attribute renaming process.

Use the TNC's built-in data comparison tools (MOD > Compare Files) to verify parameter values match between backup and active configurations.