Monitoring and Debugging the Runtime System

Debugging CitectSCADA runtime systemThe system that controls and monitors your application, process, or plant. The runtime system is sometimes called the Man-Machine Interface (MMI), and is compiled from a project. involves two processes:

• gathering information about Runtime
• analyzing logged data to identify problems

The information gathered from your system will include:

• hardware alarmA hardware alarm indicates that an error has been detected in your system. Typically displayed on a dedicated hardware alarms page, this type of alarm may indicate that a loss of communication has occurred, that Cicode can not execute, that a graphics page is not updating correctly, or that a server has become inoperative. A description and error code are provided to help decipher the cause of the problem.
• log filesLog files are a record of time-stamped system data that can be analyzed to determine the cause of a problem. The available log files include syslog.dat, tracelog.dat, debug.log, kernel.dat, and dedicated driver logs.

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

The Kernel can perform low-level diagnostic and debugging operations, and runtime analysis of your CitectSCADA 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.

Note: The process involved in debugging device communications is described in the 'Communicating With I/O Devices' section of the help. See Debugging I/O Devices and Protocols.

See Also