140-0037

Identify Software Version Change

Access MOD > System Info and document current NC software version. Compare with previous version from machine documentation or backup files to confirm if an update occurred.

Check the file SYS:\VERSION.TXT or use MOD 99 to view detailed software version history and installation dates.

Access PLC Compiler Messages

Enter MOD function, navigate to PLC Programming section, and review the compile log (typically SYS:\PLC\COMPILE.LOG) for detailed messages about attribute '%3' of object '%1'.

The compile log will show old versus new attribute locations - document these for reference when updating PLC code.

Recompile PLC Program

In PLC Programming mode, select 'Compile PLC Program' to rebuild with current data object definitions. This automatically updates attribute references to new memory locations.

Ensure you have a backup of the current PLC program before recompiling, stored on external media or TNCbackup.

Verify Attribute Mapping

After recompilation, test PLC functionality related to the affected data object '%1'. Monitor for proper operation of functions using attribute '%3'.

Use PLC trace function (MOD > PLC > Trace) to monitor the specific data object in real-time and verify correct attribute access.

Verify Backup File Origin

Check the properties of the restored backup file (typically TNC:\backup\*.tar or *.zip). Compare the backup date and source NC software version against your current version using MOD > System Info.

Backup archives contain metadata files showing the source NC software version - extract and review SYS.INFO or VERSION files from the archive.

Identify Conflicting PLC Elements

Access MOD > PLC Programming and open the PLC source file. Search for references to data object '%1' and attribute '%3' noted in the alarm text.

Use the find function (Ctrl+F in PLC editor) to locate all instances of the affected object and attribute for comprehensive review.

Update or Recompile PLC Code

Attempt to recompile the PLC program with current NC software definitions. If compilation fails, contact Heidenhain service for updated PLC source compatible with your NC software version.

Do not manually edit PLC attribute addresses without Heidenhain documentation - this can cause system instability or safety function failures.

Incremental Restore Alternative

If full backup restoration causes persistent conflicts, restore only NC programs and tool tables, then manually reconfigure machine parameters rather than restoring entire PLC configuration.

Use TNCbackup selective restore feature to exclude PLC programs and system files when software versions don't match.

Review PLC Modification History

Access MOD > PLC Programming and check file timestamps on PLC source files (typically SYS:\PLC\*.PLC). Identify any custom modifications made to standard Heidenhain PLC programs.

Compare against original Heidenhain PLC templates from NC software installation to identify custom code sections.

Locate Attribute References

Open the PLC source file and search for direct references to attribute '%3' of data object '%1'. Check for hard-coded memory addresses or outdated symbolic names.

Document all custom PLC logic before making changes - PLC programs may contain undocumented machine-specific interlocks or safety functions.

Consult Data Object Documentation

Access TNCguide (Help > TNCguide) and navigate to PLC Programming > Data Objects section. Search for object '%1' to find current attribute definitions and proper access methods.

For iTNC 530/TNC620/640 controls, Heidenhain's KCX (Cycle and Function Documentation) includes comprehensive data object structure details.

Update PLC Code Syntax

Modify PLC code to use current symbolic attribute names and access methods as documented in TNCguide. Replace any hard-coded addresses with symbolic references.

Use structured data object access (e.g., OBJECT.ATTRIBUTE notation) rather than direct memory addressing for future-proof PLC code.