HEIDENHAIN ITNC 530 - 6-2010 DIN-ISO PROGRAMMING, Руководство пользователя

Страница: 176 / 618

176 Programming: Tools
5.2 T
ool D
a
ta
Applying the tool usage test
With the TOOL USAGE and TOOL USAGE TEST soft keys, you can
check before starting a program in a Program Run operating mode
whether the tools being used in the selected program have enough
service life remaining. Here the TNC compares the actual values for
service life in the tool table with the nominal values from the tool
requirement file.
After you have clicked the TOOL USAGE TEST soft key, the TNC
displays the results of the tool usage test in a pop-up window. Use the
CE key to close the pop-up window.
The TNC saves the usage times in a separate file with the extension
pgmname.H.T.DEP
(see “Changing the MOD setting for dependent
files” on page 554). The generated tool usage file has the following
information:
Column Meaning
TOKEN
„
TOOL: Tool usage time per TOOL CALL. The
entries are listed in chronological order.
„
TTOTAL
: Total usage time of a tool
„
STOTAL
: Call of a subprogram (including
cycles). The entries are listed in
chronological order.
„
TIMETOTAL:
The total machining time of the
NC program is entered in the WTIME column.
In the
PATH
column the TNC saves the path
name of the corresponding NC programs.
The
TIME column shows the sum of all TIME
entries (only when the spindle is on, and
without rapid traverse). The TNC sets all
other columns to 0.
„
TOOLFILE: In the PATH column, the TNC
saves the path name of the tool table with
which you conducted the Test Run. This
enables the TNC during the actual tool
usage test to detect whether you
performed the test run with the TOOL.T.
TNR
Tool number (
–1
: No tool inserted yet)
IDX Tool index
NAME Tool name from the tool table
TIME
Tool-usage time in seconds (feed time)
WTIME Tool-usage time in seconds (total usage time
between tool changes)
RAD Tool radius R + Oversize of tool radius DR
from the tool table. The unit is 0.1 µm.