Usage Logging

This section briefly describes Typhoon HIL software logging feature.

Typhoon HIL software can log various usage statistics that is then available to you for further analysis.

Currently there are three types of events that are being log:
  • Application usage events - this type of logging provides you with information about how long a particular application was used. It is available for the following parts of the Typhoon HIL software tool-chain:
    • Typhoon Test Suite
    • Typhoon Test IDE
    • HIL SCADA
    • Schematic Editor
  • Simulation events - this type of logging provides you with information about each simulation that you started, such as its duration, the simulation flags status and the information on the used HIL device(s) . It is available for the following parts of the Typhoon HIL software tool-chain:
    • HIL SCADA
    • HIL API
  • Compilation events - this type of logging provides you with information about each compilation that you started, such as its duration, the number of warnings and errors. It is available for the following parts of the Typhoon HIL software tool-chain:
    • Schematic Editor
    • Schematic Editor API
  • Detailed Compilation events – this type of logging refers to a special type of Compilation events that are being logged: Instead of the number of warnings and errors, these log events contain the actual warnings and errors messages. These events are logged in a separate file. This type of logging is available for the following parts of the Typhoon HIL software tool-chain:
    • Schematic Editor
    • Schematic Editor API

Usage logs files are stored in the %APPDATA%\Roaming\typhoon\logs\ folder. This folder is used for storing all supported types of log files.

Note: The usage log folder is shared with all software versions of Typhoon HIL Control Center that you currently have installed on your PC.

All events are logged in the events.log file, except for Detailed Compilation events which are logged in a separate compilation.log file.

The logging folder always contains up to 11 events.log and 11 compilation.log files (the events.log file together with up to 10 files named events.log.1 through events.log.10, and the compilation.log file alongside with up to 10 files named compilation.log.1 through compilation.log.10).

Note: Each log file has the maximum size of 100MB.

The file which is being written to, is always the events.log (or compilation.log): when the file reaches the maximum size limit of 100 MB, it is closed and renamed to events.log.1, and if files events.log.1, events.log.2 etc. exist, then they are renamed to events.log.2, events.log.3 etc. respectively. If you already have 10 log files of any of the two types in the logging folder, the *.log.10 file will be overwritten when the current *.log file reaches the maximum size limit of 100 MB so, if you use log files extensively, make sure that you backup your log files at a schedule that matches your pace of testing.