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

AVEVA™ Plant SCADA

TABLE OF CONTENTS

Logging Parameters

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedJul 08, 2025
  • 1 minute read

warning2

UNINTENDED EQUIPMENT OPERATION

  • Do not under any circumstances change or remove any of the undocumented citect.ini parameters.

  • Before deleting sections of the citect.ini file, confirm that no undocumented parameters will be deleted.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

Note: Always seek the advice of Technical Support personnel for this product regarding undocumented features.

[S7TCP] Parameter

Description

Allowable Values

DebugLevel

The trace level used for the log file.

ALL or any combination of the following, separated by a pipe character (|) :

ERROR

WARN

TRACE

DEBUG

See note below.

See Logging for examples.

DebugCategory

The categories used for the log file.

ALL or any combination of the following, separated by a pipe character (|):

PROT = protocol level debug

DCB = front end debug (i.e. I/O server)

MISC = any other debugging

ALL = all of the above

See Logging for examples.

Note: Setting DebugLevel to DEBUG or ALL will cause the driver to log a large amount of debugging information (for example, sent and received protocol messages in binary format). This information is typically unnecessary for driver diagnostics. This may impact performance and result in multiple wraparounds that write over data.

It is recommended that you use the following DebugLevel and DebugCategory settings:

  • [S7TCP]DebugLevel=ERROR|WARN|TRACE

  • [S7TCP]DebugCategory=ALL

TitleResults for “How to create a CRG?”Also Available in