140-0018

Identify conflicting tool numbers

Press MOD key, select TOOL TABLE, and review the alarm message parameters '%1' and '%2' to identify which specific tool number(s) are causing the conflict. Note these numbers for comparison with the source file.

The '%1' parameter typically shows the object type (e.g., 'TOOL') and '%2' shows the specific identifier (e.g., tool number '5').

Review source and target tool data

Compare the tool data in both the source file being imported and the current active tool table. Determine if you need to preserve existing data or replace it with imported values.

Use split-screen view in file management to display both tool.t files simultaneously for easy comparison.

Use merge function with overwrite option

In MOD > TOOL TABLE, select the import function and enable the 'Overwrite existing tools' option. Alternatively, use FILE MANAGEMENT > select tool.t file > COPY with overwrite confirmation enabled.

Overwriting will permanently replace existing tool data. Document critical tool settings before proceeding if needed.

Alternative: Renumber tools in source file

If preservation of both tool sets is required, edit the source tool.t file using a text editor or table editing function to change conflicting tool numbers to unused numbers in your tool table range.

Maintain a tool numbering strategy: use ranges like 1-100 for milling, 101-200 for turning to avoid future conflicts.

Access preset table management

Press POS key (or MOD > PRESET TABLE depending on TNC model) to view the active preset table. Identify which preset number shown in '%2' parameter already exists.

On iTNC 530 and TNC 620/640, use the 'Preset table overview' soft key for quick visibility of all active presets.

Determine preset data priority

Verify if the existing preset contains critical datum positions for current production parts. Check the last modification date and coordinate values to determine which data should be retained.

Overwriting active presets may affect running production programs. Verify no jobs are referencing the preset before modification.

Delete or overwrite conflicting preset

Either delete the existing preset entry (select line, press DELETE soft key), or proceed with import using overwrite confirmation when prompted during the file operation.

Use the 'Backup preset table' function before overwriting to maintain a recovery point.

Check for programmatic preset writes

If alarm occurs during NC program execution, search programs for PRESET or PRESET TABLE WRITE commands and verify logic includes checks for existing entries or explicit overwrite parameters.

Cycle 247 (DATUM SETTING) can programmatically write presets - review its implementation in your programs.

Check pallet table contents

Navigate to MOD > PALLET TABLE (or pallet management function specific to your TNC model). Review existing pallet names/numbers and compare against the data being imported.

Pallet tables are stored as pal.p files - use file management to examine the source file structure before importing.

Review TNCbackup restoration settings

If alarm occurred during backup restoration, re-enter MOD > TNCbackup and select 'Selective restore' instead of full restore. Choose only non-conflicting data objects or enable overwrite options.

Full backup restoration with overwrite will replace all current machine settings and data tables. Ensure machine is not in production.

Examine PLC program data writes

If your machine uses PLC functions for pallet management, check the PLC program for data object write commands. Verify PLC logic includes existence checks before creating new pallet entries.

Contact your machine tool builder for PLC documentation if pallet management is integrated into the machine's automation system.