Use the charts in this section if you have a scanner on your system that should be, but is not, healthy (online). The charts guide you through a series of checks to assess why the scanner might be in the failed state.
In each case, start with CHART 1: Basic Checks for Scanners that are in a Failed State. This chart will guide you through some basic checks. If these checks do not solve the abnormal condition that ClearSCADA has detected, you will be directed to carry out further checks on other charts.
If ClearSCADA has detected an abnormal condition associated with a scanner on a simple driver, we recommend turning on the log file options for that driver (see Driver Log File Options that are Common to Many Simple Drivers).
After the abnormal condition has re-occurred, send the log files to Schneider Electric. You may be asked to turn on different logging options and reproduce the abnormal condition, if the condition cannot be diagnosed from the initial logs.
For further information on analyzing a ClearSCADA system, see System Analysis in the ClearSCADA Guide to the Server Status Tool, and the driver-specific documentation.
When troubleshooting on a ClearSCADA system, always check the Events List for diagnostic messages. These may help to identify the cause of any abnormal conditions that ClearSCADA has detected.
To display channel or server details in List format from the Queries Bar, filter the constraints on the Channels List.
To display scanner details in List format from the Queries Bar, filter the constraints on the Point Sources List.