Since V10_SP14, the app TS-TCLog enables the export of tool change data for customized evaluations in your company. Furthermore, TCLog enables a powerful engine for piece counting and collecting tool usage times.

Details around configuring the piece counter or collecting tool usage times are described in the articles, which describe the overview panel.

You are able to configure

  • counting the use of a tool
  • collecting tool usage times
  • monitoring against given use counts of a tool (piece counter)
  • monitoring against a given tool usage time

The logged data enables e.g. evaluations

  • at which average, minimum or maximum piece count or tool life times tools were changed.
  • about tool costs per part and which tools have the biggest share in the CPP calculation

Generation of log files

  • The ToolScope has its own piece counter for tools. Whenever in this piece counter a tool change is registered (when you are resetting the piece counter), a tool change log entry is generated. The change log files are are generated and saved in the User log directory of the ToolScope. The file name additionally contains the date and time of the start of each log.


  • You can access these log files from a SoftScope from the location shown below:



Description of the raw file information

The raw files are written as CSV-files. They can easily be imported in Excel, databases, or business intelligence software.

Raw data of a typical exported file:


If imported in Excel- the actual file structure gets visible:



This file is generated whenever a Tool Change is triggered in the Toolscope.

Detailed explanation of the entries are as follows:

  • Time: This entry shows the date and time at which the tool change has occured
  • Control Channel: The control channel number on which the process was running when tool change was triggered
  • Tool:  Name of the tool that was changed
  • Counter reading: The number of piece counter at the time of tool change.
  • Alarm Time, Source, Number, Message:
    • These are only set if there was an alarm in the process of this tool some time before the tool change.
    • If that is the case, the time of this alarm, the ToolScope-Monitoring-Window (Source), the alarm number and corresponding alarm message are written down.
  • Reason:This entry shows the reason for the tool change that was given by the user via the right button list.



Downloading tool change logs manually by USB

To download the needed files from a ToolScope, you can download them via USB. For this plug a USB-device into the ToolScope and navigate to Service -> USB within the ToolScope. Check the timeframe you are interested in on the left and "User Log" on the right to receive the correct files. At the end hit "Start":


Downloading tool change logs manually by network

To download the tool change logs from a ToolScope, you can also download them over the network. For this, connect to the ToolScope-IP with a FTP-Client or over the Windows-Network and go to ftp/logs/Service/User Log . See the article about the directory structure.



Tool Life Analysis Excel

KOMET BRINKHAUS offers you easy to use examples for making evaluations. The examples target on giving you a fast start.

Once the summary files are imported available from your workstation, the Excel file can access it. we can give file location as an input parameter. You do not have to download them for this. A connection to the KOMET Cloud is sufficient.



Tool Life Analysis Excel file can be stored anywhere and you can import all Tool change csv files by entering the location where these files are stored through this Excel and can generate reports according to your inputs. These reports will help to know the Maximum lifetime, Minimum Lifetime, Mean Lifetime, Number of Tool Changes of each tool.

Detailed steps to generate a report

           Step 1 :: Choose the language of the view



              Input –

                  1 for German

                  2 for English

                  3 for Chinese



           Step 2 :: Enter the location where you have saved all the tool change log files




            Step 3 :: Enter your time frame starting and ending date and time. Format should be  YYYY-   MM-DD HH:MM.







           Step 4:: Enter one keyword present in the name of  file that is being analyzed.

           E.g.  In this case, file name starts with "Tool change" followed by DATE and TIME. So we can use “Tool change” as  the keyword.





          Step 5 :: If the logs of each machine is in a separate sub folder enter 1.By default it will be 1.





        Step 6:: If more than one ToolScope is present, we can separate each machine’s Tool  Change logs in a separate Sub- Folder or Sub-Sub-Folder by giving machine names to that Sub-Folders.

        If logs are present in the Main Folder or Search Folder, input will be 0.

        If logs are present in Sub-Folder or Sub-Sub-Folder, input will be 1.





        Step 7:: This value depends on the number of spindles of the machine. If it is a double spindle machine, there will be two spindles so two identical tools can work in parallel.  So the value to enter is 2.Similarly, if it is an Eight Spindle Machine value to enter will be 8.





         Step 8:: This value indicates the time slots at which the changed times of Tool Changes are analyzed. It calculates the number of tool changed at a certain time in a day.





         Step 9 :: Now, you can click “Start” to generate reports.





Once the start button is clicked,Tool change Excel will  process the tool change log files and generate different reports.

These reports will show the maximum lifetime, minimum lifetime, mean lifetime, and amount of tool changes of each tool


Mean tool lifetime per station per machine are shown below:





 Below report show the tool lifetime analysis of a single tool: