140-002C

Identify the unknown object name

Read the alarm message completely - the '%1' will be replaced with the actual object name (e.g., 'Q125', 'MyDatum', 'TOOL_OFFSET'). Write down this exact name.

Press the HELP key while the alarm is displayed to see additional context about where the error occurred.

Locate reference in NC program

Open the NC program in Edit or Test Run mode. Use the GOTO function (search) to find all instances of the unknown object name. Check for correct spelling and syntax.

Enable block scan (PGM MGT → Test Run → Single Block) to step through the program and identify the exact block where the alarm triggers.

Verify parameter declaration

If the object is a Q-parameter, ensure it is assigned a value before being used (e.g., 'FN0: Q125 = 10'). For string parameters (QS), verify proper declaration syntax for your TNC version.

Parameters used in cycles must be defined before the cycle call - move declarations to the beginning of the program if necessary.

Correct or define the parameter

Either correct the spelling to match an existing parameter, or properly define/initialize the parameter in the NC program before its first use.

Use the calculator function (MOD → Calculator) to test parameter expressions interactively before adding them to the program.

Check preset table entries

Press the Preset Table key and verify that any named datums referenced in the program actually exist. Check both preset number and any symbolic names.

Heidenhain allows both numbered (e.g., '#1') and named presets - verify which format your program uses and ensure consistency.

Verify tool table configuration

Press the Tool Table key and search for the tool name or number shown in the alarm. Check if tool names are spelled exactly as referenced in the program (case-sensitive on some TNC versions).

Use MOD → Machine Configuration → Tool Table Format to verify which columns are active if the alarm references a tool parameter column.

Review table column names

If the alarm references a table column (e.g., custom tool data), verify the column exists and is enabled in the table configuration. Access via MOD → System Tables.

After software updates, custom table columns may need to be reconfigured - check backup documentation for original table structure.

Create missing entry or update program

Either add the missing preset/tool entry to the appropriate table, or modify the program to reference an existing valid entry.

When transferring programs between machines, use the 'Export with Tables' function to include preset and tool data.

Access touch probe configuration

Press MOD key → Touch Probe Configuration (or Probe Settings depending on TNC version). Check if the probe name referenced in the alarm exists in the configuration list.

Different probe types (3D probes, tool probes, laser probes) have separate configuration sections - ensure you're checking the correct probe type.

Verify probe cycle syntax

Review the measuring cycle in the NC program (typically TCH PROBE cycles). Ensure the probe name parameter matches exactly with a configured probe name, including case sensitivity.

Use the Cycle Editor (cycle key during program edit) to insert probe cycles - this ensures proper syntax and available probe names.

Configure missing probe or update reference

Either configure the missing probe in MOD → Touch Probe Configuration with proper calibration data, or modify the program to use an existing configured probe name.

Always calibrate a newly configured probe before use. Uncalibrated probes can cause collision damage.