List of predefined alarms

Introduction

The alarm numbers between 1 and 100 have been reserved for special purposes in the IGSS software package. These so-called system alarms are typically used for generating warnings from the running SCADASupervisory Control & Data Acquisition system to assist in controlling and troubleshooting. When activated, these alarms will appear in the active Alarm list.

These alarm numbers should neither be deleted nor used for alarm indication purposes on user created objects in the system.

1: Alarm in referenced diagram

The very first alarm number is automatically attached to every graphical descriptor, typically buttons,which references another diagram in the mimic. Its function is to show alarm situations present on a referenced diagram by blinking an alarm color. In other words, the sole purpose of this alarm is to allow alarm display on a diagram not currently visible in the mimic.

Two conditions must, however, be met for the so-called alarm permeation to be functional in the mimic.

No pixels in the referenced diagram may be visible from the diagram upon which the referencing button is placed.
In the right click menu for the button descriptor, the alarm boder must be set to at least 1. Click on the button descriptor and go Attributes of Button > Bindings to Object > Geometry > Size of Alarm border, double clik on the latter and in the Line Width dialog box choose a width of at least 1.

If alarm display is not desired whatsoever on the button, then right click the betton and on the Display tab under the Alarm indication group make sure there are no check marks present in any of the settings boxes here.

To view a complete list of both system alarms and alarms created for objects in the current system, you must be in the Definition module and go Edit > Alarm Texts…

Communication errors

The alarm numbers between 10 and 51 are reserved for various communication errors (the communication ports, the PLC, the data collection engine, etc.). Click here for details on driver error codes.

Alarm number(s) …	are used when …
1	a button descriptor is created which references an underlying diagram.
10 and 11	the setup of drivers is erroneous.
20 and 21	the communications ports are faulty.
30 to 39	the extended event-driven communication drivers fail; please refer to driver documentation.
40	a general PLC error occurs; please refer to PLC documentation.
41 to 45	there are driver communication errors; please refer to driver documentation.
46	the connection to the PLC program is missing; the physical connection may be in order, but for some reason the PC has not received the expected "I'm alive" message.
47	the extended event-driven communication drivers fail; please refer to driver documentation.
50	incomprehensible data from the PLC is received by the data collection engine (DC).
51	too much data output is generated, for example, if a DDE link generates too much data.

Errors and messages related to other system parameters

The IGSS system reserves the numbers between 80 and 100 for alarms related to system conditions and errors

Alarm numbers …	are used when …
80	a network connection to the station type AB-server is lost.
90	an alarm has been generated by an Event.
91	an operator has attached an alarm inhibit flag to all the alarms defined for the given object.
92	an operator has attached an alarm inhibit flag for specific alarms defined for a given object
94	the current disk usage exceeds the High Limit value of the predefined System object. The default value is 80 %.
95	the current disk usage exceeds the High Alarm value of the predefined System object. The default value is 90 %. All writing to the harddisk is suspended when this alarm occurs, that is, no log files (.log) or base class files (.bcl files) are saved.
96	an operator writes a comment on the Object note tab of an object.
97	an alarm normally sent out to the WinPager module has been temporarily disabled.
98	an Event has been generated in the Event list.
99	an undetermined alarm has been received on the IGSS server. This alarm is used when IGSS receives an error message that it is unable to find a matching alarm text for. This situation could arise if an alarm text was modified after the installation of the configuration.
100	(reserved for future use by the system)