Many alarm properties are bind-able, which means they can be bound to other Tags in the system, or expressions. Normally an alarm would be generated each time the alarm condition was met, but the Active Delay attribute will prevent any alarms from being generated until the value on the Tag has stayed in an alarm state for a set period of time.ĭescriptions of each attribute can be found on the Tag Properties page.
Similar in concept to properties on Vision components, alarm settings, also known as alarm properties, allow you to modify the behavior of each alarm.įor example, in some situations a Tag may frequently enter and leave an alarm state, but only for a brief moment. This means that at least one alarm is configured on this Tag.
This means that when the value on the Tag is equal to 1 (or True in the case of a boolean) then the alarm will become active. In the image below the Name was changed to "High Value" and the Setpoint was changed to 1.
In practice, acknowledgment allows users to 'claim' alarms, or otherwise let colleagues know that the alarm is being handled. Until an alarm has been acknowledged, it is said to be unacknowledged, or ' unacked'. This flags the alarm as such in Ignition, and the acknowledgment state of each alarm can be made visible throughout Ignition. When it becomes false, the alarm is said to be clear.Īlarms may also be acknowledged. When the condition becomes true, the alarm is said to be active. Each alarm is a condition that will be evaluated when the value of the Tag changes. Alarms are defined on Tags or OPC items in SQL Bridge (Transaction Groups).