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

AVEVA™ Plant SCADA

Tracelog Trace Messages

  • Last UpdatedJul 18, 2023
  • 2 minute read

The Scheduler outputs diagnostics information to the platform trace log.

For more information regarding log files and the rules belonging to platform logging systems refer to the section Monitoring and Debugging Runtime in the Plant SCADA main help.

The tracelog.Report.<Report server name>.dat file contains report server related trace information and is similar to the syslog.dat file.

Refer to the Debug Parameters help for information pertaining to logging. If you require additional information refer to the help for the Computer Setup Editor.

Note: By default the logging levels are set to every category, but only Critical and Error level traces will be logged. As the traces from the Scheduler are currently Informational only, change this level to include information. (If that is the only change made, then informational traces from every component will be directed to the tracelog) With manipulation of the debug ini parameters, you can fine tune a fairly granular trace set.
Example for Scheduler critical, error, information ONLY:
[Debug]SeverityFilter= Critical,Error,Information
CategoryFilterMode=0
CategoryFilter=Scheduler

Runtime Transition Manager

These messages are prefixed with "Runtime Transition Manager:"

  • Start delayed - Start operation was requested but delayed due to the start delay period not having elapsed. The message indicates that the start will occur later and specifies in how many milliseconds. A timestamp is supplied indicating the local time that the start was called.

  • Started - Runtime transitions manager has been started, and a local timestamp supplied indicating when.

  • Delayed Start Cancelled - Prior start call which was queued due to startdelay has been dequeued and not started.

  • Stopped - Runtime transition manager has halted its operation and a local timestamp indicating when.

Equipment

These messages are prefixed with "Equipment"

  • Mode changed - Gives an equipment name, the previous mode (Automatic or Manual) and the new mode, along with the standard timestamp information of when the transition occurred.

  • Demand Response Mode changed - Gives an equipment name, the previous demand response mode (numeric) and the new mode, along with the standard timestamp information when the transition occurred.

  • Manual state changed - Gives an equipment name, the previous state (string) and the new state, along with the standard timestamp information when the transition occurred. This message is only triggered on manual override state changes.

  • State changed - Gives an equipment name, the previous state (string) and the new state, along with the standard timestamp information when the transition occurred. This message will be triggered for both automatic equipment state changes and manual ones.

    Note: Currently traces for equipment property changes are logged on the server that they occurred on. No updates done via synchronization are logged.

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