Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Plant SCADA

Logging

  • Last UpdatedJul 09, 2024
  • 2 minute read

The OPCLX driver can log combinations of trace levels across different categories. This is achieved by setting the following INI parameters.

[OPCLX]DebugLevel

This parameter allows you to define the trace level. The options include:

WARN

Output warning messages.

ERROR

Output error messages.

TRACE

Output trace messages.

DEBUG

Output debug messages.

ALL

All of the above.

[OPCLX]DebugCategory

This parameter allows you to enable logging for a particular category of trace. The options include:

TAG

Tag configuration trace

PROT

Operations related to the OPC protocol interface

CACHE

Operations related to the driver cache

DCB

Front end driver trace

MISC

Miscellaneous operations

THRD

Thread trace

BEND

Operations related to the back-end thread of the driver

FEND

Operations related to the front-end thread of the driver

ALL

All of the above

In both cases, you can use ALL or any combination of the available options separated by a pipe character ( | ).

Example

[OPCLX]
DebugLevel=WARN|ERROR|TRACE
DebugCategory=ALL

In most cases, you can set the DebugLevel and DebugCategory parameters to ALL. If this results in a large, cumbersome log file that causes older data to be overwritten, you can consider refining the debug options.

Note: These parameters do not have a value specified by default. To enable logging for this driver, you need to manually configure these parameters in your INI file.

The events generated by the OPCLX driver are logged in the following Plant SCADA syslog file:

syslog.IOServer.<Cluster name>.<IO Server name>.dat

This file is located in the directory specified by the Citect.ini parameter [CtEdit]Logs. By default, this location will be:

%PROGRAMDATA%\AVEVA Plant SCADA <VersionNumber>\Logs

If you are running the driver on a version of Plant SCADA prior to v7.20, a file called OPCLX.log will be delivered to the "Logs\Drivers" directory instead.

The size of the syslog file and its rollover process is configured via the [Debug]SysLogSize and [Debug]SysLogArchive INI parameters. For more information, see the topic Debug Parameters in the Plant SCADA documentation.

Note: If the number of messages being processed for a driver exceeds the value specified by the Plant SCADA parameter [Kernel]ErrorBuffers, the pending messages will not be logged. If this occurs, you can increase the value of this parameter so that all the messages generated by the driver are reported. The number of messages that are not logged can be monitored via the Kernel's General window under the item "Lost Errors". If you adjust [Kernel]ErrorBuffers and Lost Errors are still occurring, you may need to adjust the level of system logging.

See Also

Logging Parameters

In This Topic
Related Links
TitleResults for “How to create a CRG?”Also Available in