Other log files

MacroTrace.log file

The MacroTrace.log file contains a record of PcVue main events. New events are appended to the file providing a complete summary of operations. The following events are recorded.

  • Start and stop of PcVue 
  • Load, start, stop and unload of each manager
  • Connection and disconnection of a networked stations
  • Start and stop of communication for data acquisition
  • Manager watchdog messages

The maximum file size is configured by the Max size for MacroTrace log file setting in the Audit diagnostics settings. In the event that the max size is reached, a backup MacroTrace.bak.log is created and a new empty file started.

HDS.log file

The HDS.log file contains a record of events produced by the Historical Data Server. Each time the HDS is started the previous HDS.log is renamed to HDS1.log. If HDS1.log already exists, it is renamed to HDS2.log etc. The number of rotating file is nine.

Writing to the file takes place on each new event and there is no limit on the size of the file.

OPCsrv.log file

The OPCsrv.log file contains a record of events, produced by the PcVue main program, dedicated to OPC server activities. Each time PcVue is started, the previous OPCsvr.log is renamed to OPCsvr1.log. If OPCsvr1.log already exists, it is renamed to OPCsvr2.log etc. The number of rotating file is nine.

Writing to the file takes place on each new event and there is no limit on the size of the file.

SV32.Exceptions.log file

The SV32.Exceptions.log file is generated in the unlikely event of a fatal error of the PcVue main program. It contains important diagnostic information when an exception occurs or a manager watchdog is triggered. The information it contains can only be interpreted by your technical support contact and you may be asked to provide such files when reporting a problem.

This file is not renamed on the start of PcVue unlike Trace.log. It will contain information about all exceptions with the most recent at the end of the file. The maximum size is 10 Mb. If this maximum size is reached, the file is saved as SV32.Exception.bak.log and a new SV32.Exception.log is created.