140-0023

Identify Changed Data Object

Access MOD mode > PLC > Error Log and note the exact data object '%1' '%2' and attribute '%3' displayed in the alarm. Record these identifiers for reference.

The alarm parameters are displayed in sequence: %1=object type (e.g., M, T, Q), %2=object identifier, %3=specific attribute name

Review PLC Source Code

In Programming mode, open the PLC program file (typically plc.src or machine-specific .PLC file) and search for the identified data object declaration using the TNC's text search function (GOTO > Search).

Look for VAR, VAR_GLOBAL, or TYPE declarations that define the flagged object

Compare with OEM Reference

Obtain the correct PLC program version from the machine tool builder or from your documented backup library and compare the data type definition of the affected object.

Do not modify OEM-protected PLC code without authorization from the machine tool builder

Correct Data Type Definition

Modify the data object declaration to match the required data type (e.g., change from INT to DINT, BOOL to BYTE, etc.) ensuring compatibility with all references throughout the PLC program.

Common data type corrections: marker bits should be BOOL, counters typically DINT, analog values often REAL

Recompile PLC Program

Navigate to MOD > PLC > Compile and execute a complete PLC recompilation. Monitor the compilation output for additional errors or warnings related to the modified object.

Successful compilation will show 'PLC compiled without errors' - any remaining errors must be resolved before proceeding

Access Table Management

In MOD mode, navigate to System > Table Configuration or the specific table editor (Tool table, Preset table, etc.) and identify if recent changes were made to table structure or custom columns.

Check the modification date/time stamps in table properties to identify recently changed definitions

Review Table Column Definitions

Examine the data type assignments for custom table columns, particularly those matching the '%3' attribute identifier from the alarm. Common issues include numeric types (INT, REAL) mixed with string types (STRING).

Modifying standard table columns can cause system instability - only modify OEM-approved custom columns

Restore Correct Data Type

Use the table editor to modify the column definition back to the correct data type. For custom columns, refer to the machine documentation for required data type specifications.

If uncertain of correct type, export table to USB, delete custom column, then recreate with verified data type from machine documentation

Validate Table Structure

After correction, perform a control restart (MOD > System > Restart Control) to force complete table validation and ensure the alarm clears during system initialization.

Check TouchProbe Cycle Configuration

Navigate to MOD > TouchProbe > Configuration and review the installed cycle versions and parameter definitions. Note any recent cycle updates or manual parameter file modifications.

TouchProbe cycles are typically located in TNC:\system\tpa or similar directories - check file modification dates

Verify Cycle Compatibility

Cross-reference the installed TouchProbe cycle version with the TNC software version using the compatibility matrix in the TNC Service Manual or online Heidenhain Technical Documentation portal.

Incompatible cycle versions can cause probe crashes or incorrect measurements - verify before use

Reinstall TouchProbe Cycles

If version mismatch is identified, obtain the correct TouchProbe cycle package from Heidenhain for your specific TNC software version and install via MOD > Software Update > Import Software Component.

Always backup current configuration to USB before updating TouchProbe cycles

Reset TouchProbe Parameters

After cycle reinstallation, navigate to MOD > TouchProbe > Reset to Default to restore standard parameter definitions, then reconfigure only necessary custom parameters according to machine requirements.