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

AVEVA Enterprise SCADA

TABLE OF CONTENTS

Enable logging

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedApr 24, 2025
  • 2 minute read

While executing the Application Calculation Engine (ACE) code (acecode), most errors are logged in the ACEEngine.log file. However, common messages, such as failure to write a record in manual-override, are not commonly logged. To enable these messages, the debug level must be elevated from the default.

The following example uses the toggledebug executable to elevate the ACEEngine debug messages to allow the writing of warning, informational, and verbose messages to the ACEEngine.log file. In this example, the Process ID (PID) for the ACEEngine is 1234. In practice, you will have to use the task manager or the process list in the Network Management Console (NMC) to determine the PID.

Example

toggleDebug -p 1234

Note: As indicated in the table below, the first toggle enables warning messages, then informational messages, and finally verbose messages. To turn off extra debugging, toggle back to the default from verbose using the same command. The default is DebugLog and the other three (Fatal, Exit, and Always [Error]) are always logged.

Logging debug levels

Debug Level

Application Calculation Engine (ACE) Actions

Fatal

Writes the given message to the AVEVA Enterprise SCADA log file (oasErrLog.log), and then exits the program immediately and writes a stack trace into the AVEVA Enterprise SCADA log file.

Exit

Writes the given message to the AVEVA Enterprise SCADA log file (oasErrLog.log), and then exits the program without a stack trace being written into the AVEVA Enterprise SCADA log file.

Always (Error)

Writes the given message to the AVEVA Enterprise SCADA log file (oasErrLog.log). If any messages are written into the program-specific debug log file (programName.log), then this message is also written there, and will have a heading of 'Error'.

DebugLog

Writes the given message to the program-specific debug log file.

Warning

If the dynamic debug level is set high enough through the 'toggleDebug' utility, then messages marked with this level are written out to the program-specific debug log file (programName.log).

Info

If the dynamic debug level is set high enough through the 'toggleDebug' utility, then messages marked with this level are written out to the program-specific debug log file(programName.log).

Verbose

If the dynamic debug level is set high enough through the 'toggleDebug' utility, then messages marked with this level are written out to the program-specific debug log file (programName.log).

 

Related Links