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

AVEVA™ Plant SCADA

Debug Runtime

  • Last UpdatedFeb 06, 2024
  • 1 minute read

Debugging Plant SCADA's runtime system involves two processes:

  • Gathering information about Runtime

  • Analyzing logged data to identify problems.

The information gathered from your system will include:

  • Hardware alarms

  • Log files.

Hardware alarms are typically displayed on a dedicated alarm page to alert operators to current problems.

Log Files are a record of time-stamped system data that can be analyzed to determine the cause of a problem.

This information can be analyzed directly to identify problems, or you can use the Plant SCADA Kernel to perform advanced debugging.

The Kernel can perform low-level diagnostic and debugging operations, and runtime analysis of your Plant SCADA system. Use it to display low-level data structures, runtime databases, statistics, debug traces, network traffic, I/O device traffic and so on.

You can also call built-in Cicode function or user-written Cicode functions, and use the Cicode Profiler to view how your Cicode is performing.

Note: The process involved in debugging device communications is described in the Communicating With I/O Devices section of the help. See Troubleshooting Device Communications.

See Also

System Tuning

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