Use the Log Viewer

Error messages are created by the Communication Driver and logged by the Logger. You can view these messages with the Log Viewer. The Log Viewer help files explain how to view messages and how to filter which messages are shown.

Log Flags are categories of messages. The Log Flag Editor User Guide contains an explanation of the categories. Using the Log Flag Editor, you can specify which log flags the Communication Driver creates.

Note: Generating large numbers of diagnostic messages can impact Communication Driver performance. You should not run in production with any more flags than those set when the Communication Driver is installed. To troubleshoot you can turn on more flags, but there is a performance impact. For more information, see the Log Flag Editor User Guide.

Open the Log Flag editor

1. In the Operations Control Management Console, expand Log Viewer and then expand the log viewer group.

2. Select Local.

3. On the Action menu, click Log Flags.

In general, look at error and warning messages to determine if a problem exists. To determine whether the Communication Driver is communicating with a device, you can enable the DASSend and DASReceive log flags. From these you can determine whether or not the device is responding.

Basic log flags

The basic log flags for all AVEVA components are:

• Error: A fatal error, the program cannot continue. By default set on by logger.

• Warning: The error is recoverable. A client called with a bad parameter, or the result of some operation was incorrect, but the program can continue. By default set on by logger.

• Start-Stop: Each main component logs a message to this category as it starts and stops.

• Info: General diagnostic messages.

• Ctor-Dtor: C++ classes of interest log messages to this category as they are constructed and destructed.

• Entry-Exit: Functions of interest log messages to this category as they are called and return.

• Thread Start-Stop: All threads should log messages to this category as they start and stop.