Main - page of object PmAlarmEvent

Basic parameters of an alarm/event group.
Configuration items:
Group preset toSpecifies which item type will managed by this object:
Events - The group contains only event items (without states), no inactivation, nor acknowledgement, nor state viewer, etc. is used.
Alarms - The group contains alarm items (with states), but it can contain even event items (without states), inactivation, acknowledgement, state viewer, etc. is used.
Group identifierThe unambiguous identifier of an alarm/event group in the application.

This configurator sets the initial value of the property PmAlarmEvent.GroupId.

Macro expression can be used for input (it is evaluated while the application is launching).

This is a system name and must not contain diacritics, empty string, spaces and the first character must not be a number.
Displayed group titleThe displayed name of an alarm/event group. It is used in viewers, print-outs, etc.

This configurator sets the initial value of the property PmAlarmEvent.GroupTitle.

The name doesn't need to be entered (can be empty string) - then the group name is not displayed anywhere. It has sense only when there is only one alarm/event group in the application.

Macro expression can be used for input ($.text ..) (it is evaluated while the application is launching).

AreaMarking the area where the alarm/event group belongs (group or subgroup). All alarm/event items of one PmAlarmEvent object belong to the same area. It goes about an arbitrary string that enables to users easier filtering the set values when watching the group. It is useful first of all when more objects PmAlarmEvent store the data to the common disk file (see the configurator "Parent enabled"). Each group then has its own different area, that can be used in the alarm viewer (status and history) for distinguishing and filtering them. When opening the viewer (status or history) over the PmAlarmEvent object of the subgroup type, the viewer automatically uses the filtration string, filtering the content of the group for specified area. Then only the alarms and events of the specific subgroup are displayed.

Macro expression can be used for input (it is evaluated while the application is launching).

Parent enabledIf checked, then the parent group can be set in the Parent configurator.
ParentAlarm/event items (PmAlarmEventItem objects) arise and are stored to the disk in the parent group. Alarm/event groups are displayed in the state viewer or in the history viewer also in this parent group. Filtering in the viewer according to the Area configurator enables to display items only of the certain alarm/event group in the frame of the parent group. Pages Storage, State viewer and History viewer then have no sense.
Remote group (client)If checked, then the group is not meant for generating alarm/event items but it serves only for the remote viewing another alarm/event group. All operations that would have resulted in writing to disk, will fail over such group.

Macro expression can be used for input (it is evaluated while the application is launching).

Number of inactive, unacknowledged alarms (blue) to keepIf it's not zero, then when activating the inactive, unacknowledged item (blue) the item is activated (red) but at the same time the original inactive, unacknowledged item (blue) is kept so that both items are seen concurrently (red and blue). After the acknowledgement of the inactive, unacknowledged item (blue), this item is automatically removed. The configurator allows to set the maximum number of inactive, unacknowledged items (blue) (copies of the active item) for each alarm/event item. The zero means that no older occurrence of the inactive, unacknowledged alarm/event items (blue) doesn't arise, each alarm/event item occurs only once (no copy).
Invoke viewer on activationThe configurator specifies if the state viewer or the history viewer has to be automatically displayed after the state change of one of the items from the alarm/event group.
no viewer - No viewer is displayed.
state viewer - The state viewer of an alarm/event group is displayed.
history viewer - The History viewer of an alarm/event group is displayed.
Priority needed for invoking the viewerThe configurator specifies the necessary minimum priority that the alarm/event item must have when changing the state so that the state viewer or the history viewer is automatically invoked. It means that only the alarm/event item with the same or higher priority than the set priority can cause automatic invoking the viewer.
0 = low - Necessary minimum priority of the alarm/event item is set to 0 (i.e. the priorities 0, 5 and 10 for all alarm/event items).
5 = medium - Necessary minimum priority of the alarm/event item is set to 5 (i.e. the priorities 5 and 10 for all alarm/event items).
10 = high - Necessary minimum priority of the alarm/event item is set to 10 (i.e. the priority 10 for all alarm/event items).
Delete inactive acknowledged (green) (valid only for dynamically created items)If checked, then the alarm/event item is removed from the list if it becomes inactive and acknowledged at the same time (see the state inactive acknowledged (green)). It has sense only for the dynamically created alarm/event items. The same value can be set even for alarm/event item templates, see Delete inactive acknowledged (green). To suppress (but not to remove) displaying inactive and acknowledged (green) alarm/event items can be done by the Hide inactive acknowledged (green) configurator.
Change inactive confirmed (green) CEASED to NEW non-initialized alarms in [s] (-1=never)The configurator sets/disables the time delay in seconds, before the inactive confirmed (green) CEASED alarms are automatically switched to inactive confirmed (green) NEW non-confirmed alarms. The value -1 disables the automatic switching.

When used together with configurator PmAlarmEvent > State viewer > Hide inactive acknowledged (green), it is possible to view only active alarms or recently ceased. This way the never-activated alarms or long ceased alarms are not displayed.

Sound notificationThe way of sound indication of an alarm items state.

This configurator sets the initial value of the property PmAlarmEventItem.SoundMode.

0 = no sound
1 = sound stops after Acknowledge or Inactivate
2 = sound stops after Acknowledge and Inactivate
3 = sound stops after Acknowledge
Sound playerThe configurator specifies the sound playback method.
0 = beeper (obsolete, only for OS Windows XP) - The sound is generated on an internal beeper in a form of simple tone. The higher number of sound active alarms the higher pitch.

Caution!The internal beeper works correctly only in OS Windows XP (if present). In OS Windows Vista it does not work at all and in OS Windows 7 its functionality is transferred to soundcard, but not exactly (the tone pitch is constant).

1 = sound server - The sound is played by a sound server on a sound card of a computer. The sound itself is in a form of WAV sound file. The additional parameters can define the number of sound repeating (if the alarm is still sound active) and eventually the delay between sound repeating. The sounds are queued both by rise time of a request and by priority of an alarm. The sound which starts playing is always played to its end. There is always maximally one played sound at the moment. Sounds are played one by one.
Sound parametersSound playback method parameters (valid only for sound server). It is a text in format KeyVal. For example "file:#pmres:Sound/alarm01.wav;repeat:5;delay:2.5;".

System dialog "Sound parameters" can be used for sound selection and playback parameter setting (allowing also sound sample playback).

Parameters entered here can be modified by any PmAlarmEventItem object - see the configurator Sound parameters.
file:xx; - Sound file. It is recommended to use the PROMOTIC path syntax - see PROMOTIC path to files and folders.

There are some *.wav files located in the Promotic folder ("/Pm/Resource/Sound") that can be used. The link to these files is for example #pmres:Sound/alarm01.wav. The designer can create personal files and place them into the application source folder (see the configurator "Paths to system folders"). For example of the filelink: #appres:MySound1.wav.

repeat:xx; - The number of sound repeat (-1 = unlimited, default).
delay:xx; - Delay while repeating in seconds (e.g. delay:0.5;). The delay is a minimal time between an end of previous and a start of next replaying of the same sound. The delay can be greater if another sound is being replayed at the moment (need to wait for its end) or some others sound of higher priority are in a queue. Default option is delay:0;.
PROMOTIC 8.3.30 SCADA system documentation - MICROSYS, spol. s r.o.

Send page remarkContact responsible person
© MICROSYS, spol. s r. o.Tavičská 845/21 703 00 Ostrava-Vítkovice