Each alarm has a Category that indicates the type of alarm. You can filter Alarms Lists or the Alarm Banner so that they only display alarms of a specific category. For example, so that they only display ‘Channel Status’ alarms.
The alarm categories include:
- Archive Volume—Alarms that have been raised in relation to the archive volume (the media to which data is being archived). For example, the archive volume being full.
- Archiving—Alarms that have been raised to indicate problems that have been detected with data archiving.
- Callback—Alarms that have been raised due to an outstation or similar device not reporting back within the callback time.
When you perform a Callback action on an outstation, the outstation should report to the ClearSCADA server within a pre-defined time, referred to as the callback time. If the outstation does not report within this time, an alarm is raised.
- Channel Status—Alarms that have been raised to indicate problems that have been detected with the availability of a communications channel. For example, channels on which communications has been interrupted unexpectedly.
- Control Checks—Alarms raised because a Control Feedback point or an Uncommanded Change point did not have a required value (see Control Feedback Settings and see Uncommanded Change Settings in the ClearSCADA Guide to Core Point Configuration).
- Control Status—Alarms that have been raised due to controls being unsuccessful. For example, controls that were unsuccessful due to communications being interrupted between the ClearSCADA server and the outstation to which the server was attempting to send the control requests.
- Dial In Overactive—Alarms that have been raised due to PSTN outstations dialing in more often than expected.
- File Upload Status—Alarms that have been raised to indicate errors detected with file upload activity, such as outstation data not uploading successfully into ClearSCADA.
- Forecast—Alarms that have been raised to indicate that a Forecast database item has a value that exceeds one of its alarm limits.
- Historic Corrupt—Alarms that have been raised to indicate errors detected in historic data that is being retrieved.
-
Historic Export—Alarms that have been raised due to anomalies associated with the export of historic data from ClearSCADA.
- Historic Overactive—Alarms that have been raised to indicate that the value of the maximum number of records per data file (granule) exceeds one of the historic limits set, see Define the Acceptable Limits for Historic Data Files.
- Historic Write Error—Alarms that have been raised to indicate write errors detected when historic data is being recorded.
- Interface Alarm—Alarms that have been raised by an external application, using the SetInterfaceAlarm method. The SetInterfaceAlarm method is purely for use with the Automation Interface.
- Outstation Comms—Alarms that have been raised due to an outstation or similar device being unable to communicate with the ClearSCADA server.
- Outstation Error—Alarms that have been raised due to general errors being detected on an outstation or similar device. This category is for outstation alarms that are not included in any of the other outstation categories.
- Outstation Hardware—Alarms that have been raised to indicate that component errors, such as the battery being low, have been detected in an outstation. This category is limited to those outstations that can provide data about their hardware, such as Kingfisher outstations.
- Point Error—Alarms that have been raised due to miscellaneous errors being detected on points.
- Point No Change—Alarms that have been raised due to a point’s value not having changed by a specified amount for a defined period of time. Such alarms only apply to points that are configured to use the No Change feature.
- Point State—Alarms that have been raised due to a point’s value changing and causing the point to change state. For example, a point state alarm is raised when an analog point’s value rises above one of its alarm limit thresholds (defined in its configuration).
- PSTN Test— Alarms that have been raised indicating problems with fallback PSTN connections between outstation hardware and the ClearSCADA server.
- Scanner Status—Alarms that have been raised to indicate problems that have been detected with a scanner or point source (simple drivers). For example, a scanner being offline.
- Scheduled Dial In—Alarms that have been raised to indicate unexpected scheduled dial ins, or scheduled dial ins that did not occur when expected.
- Server Status—Alarms that have been raised to indicate problems detected with a server or channel (simple drivers).
- System Alarm—Generic alarms that relate to system-wide problems that have been detected. For example, licenses expiring.
- Unknown Dial In—Alarms that have been raised due to an unknown PSTN outstation dialing-in to ClearSCADA.
There may also be further categories relating to specific drivers—for information on any alarm categories not listed above, see the Driver Reference Suite.