Occurs when a new alarm is detected after the initial receipt of alarms by the Alarm Summary object. By default, this event does not fire. To trigger the event when information in the Alarm Summary object changes, set the CheckForNewAlarms property to TRUE. The event occurs even if the change in content happens off screen.
For example, in run mode, if a tag goes into a HI alarm and then changes to HIHI, the NewAlarm event fires once, unless the previous HI alarm is acknowledged. The NewAlarm event detects if an alarm is new, not a new severity. If you want to detect a change in severity, use the CheckForSeverityIncrease property and SeverityIncreased event.
Syntax
object_NewAlarm(strNode As String, strTag As String)
Properties
The NewAlarm event syntax has these parts:
|
Part |
Description |
|
object |
An object expression that evaluates to an object in the Applies To list. |
|
strNode |
String. A list of nodes with new alarms. Example of parsing the list |
|
StrTag |
String. A list of tags with new alarms. Example of parsing the list |
Remarks
Whenever you change the filter or sort configuration, the Alarm Summary object updates its list of alarm. However, this change does not cause the NewAlarm event to occur.
If a tag is in alarm and another alarm occurs for this tag, the NewAlarm event does not trigger again. For example, if a tag is in HI alarm and it goes to HIHI alarm the NewAlarm event fires only once. In order for the event to trigger twice, the HI alarm would have to be acknowledged and return to an OK alarm state prior to the tag going into a HIHI alarm.
