Because both terms are very similar, this area is covered together by the PmAlarmEvent object in the PROMOTIC system. Such objects can be in an application more than once - so you can create more groups of alarms/events (e.g. if you want to separate communication and technological alarms or events from a boiler-room and a drying-room, etc.) There must be specified already before its creating whether such object serves for controlling alarms or events. Thus one single object cannot be assigned for alarms and events at the same time.
Specific alarm/event can be created (i.e. define it for later activation/deactivation/acknowledgement, etc.) by various ways:
If you want to have only one group of alarms/events (so that you could, for example, view all these alarms together) but you want to create it by more PmAlarmEvent objects (e.g. you want to have one PmAlarmEvent object for each boiler-room), then it can be done by the following process: You create one PmAlarmEvent object which will serve as the base (root) for all further objects. You parametrize it accordingly but you don't need to create even single alarm/event in it. Then you create next PmAlarmEvent objects on other relevat suitable places where you check the Parent enabled configurator and you set the path to the base object. Then you create required alarms/events in these objects.
Thus you'll maintain these alarms/events with these objects but internaly they are "pointed" to the base object. All alarms/events can be viewed together, they can be stored in one file, etc.
It is possible to view the current state and the history.
By means of the PmAlarmEvent.WndState method it is possible to view the current state. This is handy especially for alarms. Here you can see always the last state of the alarm, its activation time, acknowledgement time, etc. Here you can also acknowledge alarms.
By means of the PmAlarmEvent.WndHistory method it is possible to view the history. This is handy for alarms and events. The items are ordered by the activation time and you can see how alarms/events arose one after the other in the time.
By the PmAlarmEventItem.Active property we can find out if the alarm is active.
|active unacknowledged (red)||An alarm that has been activated and no inactivation occurred nor the user acknowledged it.|
|active acknowledged (yellow)||An alarm that has been activated, no inactivation occurred and the user acknowledged it. It doesn't happens at alarms that have the Acknowledge type configurator set to "2 = acknowledgement and automatic inactivation".|
|inactive unacknowledged (blue)||An alarm that has been inactivated but the user hasn't acknowledged it. It doesn't happens at alarms that have the Inactivate type configurator set to "2 = inactivation and automatic acknowledgement".|
|inactive acknowledged (green)||An alarm that has been inactivated and if needed, the user has even acknowledged it.|
It is set in the Activate delay [sec] and Inactivate delay [sec] configurators that allows not to activate/deactivate the alarm right immediately but instead of this to set it into the suspicious state for activation or deactivation. The suspicion changes into the real activation/deactivation of the alarm or the suspicion expires after the specified time.
By this method it is possible to prevent unnecessary activation/inactivation of alarms caused by some swings of values of the watched variable, for example, by the the interference or failure of the communication. By this method it is also possible to implement alarms for the actions with the 'timeout', when the alarm is activated with delayed activation before such action and after detection of the successful termination of the action, the alarm is inactivated. If the action is not successfully terminated in the set time, then the alarm in the suspicion is activated automatically in the set time.
If the value in Number of inactive, unacknowledged alarms (blue) to keep configurator of the PmAlarmEvent objekt is greater than 1, then alarms that wait for the acknowledgement, remain in the list even after activation of new alarm with the same name. In this only case a situation when there are more the same alarms in state browser, can occur.
In the window with the alarm groups list there is an outline of all alarm groups. There is stated the number of
By double-clicking the name of any alarm group (or in the script by calling the PmAlarmEvent.WndState method) an outline of alarm states in the group is opened. There is possible to view and acknowledge alarms in this window. If it is enabled, then there is also possible to set and save ("Settings" and "Save") columns width, color of alarm states, format of displayed time, etc.
But each line of the viewer informs only about the time of the last activation/inactivation/acknowledgement of the alarm. The whole history of all alarms can be displayed by clicking the "History" button or in the script by calling the PmAlarmEvent.WndHistory method. By this the window for all history overview of all alarms from the group is opened. In this window it is possible to view the history of all alarms in the specified group.
There is an overview of all event groups in the window with the list of event groups. By double-clicking the name of any event group (or in the script by calling the PmAlarmEvent.WndHistory method) a window with the history overview of the group is opened. In this window it is possible to view the history of all events in the group.