Configuring Alarms Wonderawre Intouch
Alarms and Events Window Popup Wonderware Intouch:-https://youtu.be/fHKgPYI8agA
Configuring Discrete Alarms
A discrete alarm corresponds to a discrete tag. You can configure whether the alarmed state corresponds to the discrete tag’s true (On, Yes, 1) state or false (Off, No, 0) state.
To define alarm conditions for a discrete tag
Open the Tagname Dictionary.
Select an existing discrete tag or create a new discrete tag.
Click either Alarms or Details & Alarms at the top of the Tagname Dictionary dialog box to show the discrete alarm details dialog box.
In the ACK Model area, select the alarm acknowledgement model for the tag.
Click Condition for acknowledgment to count against all transitions into the alarmed state or a sub-state up to the time of the acknowledgement. This is the default acknowledgement model.
Click Event Oriented for an acknowledgment to only be for a particular transition to the alarmed state or a sub-state; an acknowledgment is accepted only if it refers to the most recent transaction.
Click Expanded Summary for an acknowledgment to only be for a particular transition, whether to an alarmed state, to a sub-state, or a return to normal. Each transition from the normal state marks the beginning of a new “return to normal” (RTN) group. All transitions in an RTN group must be acknowledged individually before the overall RTN group is considered acknowledged.
In the Alarm Comment box, type an alarm comment up to 131 characters.
In the Alarm State area, select the active alarm state to be the discrete tag’s On or Off value.
In the Priority box, assign an alarm priority number between 1 to 999. The default priority number is 1, which is the highest alarm priority.
Optionally assign an alarm inhibitor tag for the discrete alarm.
In the Alarm Inhibitor box, click the button to show the Select Tag dialog box containing a list of defined tags.
Select a tag from the list and click OK. The name of the tag you selected as the inhibitor tag appears in the Alarm Inhibitor box.
For more information on inhibiting alarms, see Inhibiting Alarms.
Click Save.
Click Close to close the Tagname Dictionary dialog box.
Configuring Value Alarms
A value alarm is associated with integer or real tags. You can set alarms when the tag value transitions from a set of predetermined thresholds that range from LoLo to HiHi. You can configure whether the alarmed state corresponds to any value of the tag and the associated priority of that alarm.
To configure a value alarm
Open the Tagname Dictionary.
Select an existing real or integer tag or create a new tag.
Click either Alarms or Details & Alarms at the top of the Tagname Dictionary dialog box to show the alarm details dialog box.
In the ACK Model area, select the alarm acknowledgement model for the tag.
Click Condition for acknowledgment to count against all transitions into the alarmed state or a sub-state up to the time of the acknowledgement. This is the default acknowledgement model.
Click Event Oriented for an acknowledgment to only be for a particular transition to the alarmed state or a sub-state. An acknowledgment is accepted only if it refers to the most recent transaction.
Click Expanded Summary for acknowledgment to only be for a particular transition, whether to an alarmed state, to a sub-state, or a return to normal. Each transition from the normal state marks the beginning of a new “return to normal” (RTN) group. All transitions in an RTN group must be acknowledged individually before the overall RTN group is considered acknowledged.
In the Alarm Comment box, type a default comment up to 131 characters. The comment is assigned to the tag’s .AlarmComment dotfield.
Select the alarm types (LoLo, Low, High, HiHi) to detect when the value of the tag is beyond an absolute limit.
In the Alarm Value boxes, type the limit values for the alarm types.
For example, in the case of LoLo and Low alarms, an alarm condition exists whenever the value of the tag is less than the Alarm Value. In the case of High and HiHi alarms, an alarm occurs whenever the value of the tag exceeds the Alarm Value. You can use real numbers for the limits.
In the Value Deadband box, type the number of engineering units the tag value must drop below or above the alarm value before it transitions out of an alarm state.
For example, to return-to-normal from an alarm condition, a tag value must not only return inside its alarm limit, but also return through your specified Value Deadband. The Value Deadband prevents nuisance alarms caused by repetitive re-annunciation of an alarm where the tag value hovers around the limit, continually fluctuating in and out of an alarm state.
Optionally assign an alarm inhibitor tag for the tag’s alarm types (LoLo, Low, High, HiHi).
In the Alarm Inhibitor area, click the button to show the Select Tag dialog box containing a list of defined tags.
Select a tag from the list and click OK. The name of the tag you selected as the inhibitor tag appears in the Alarm Inhibitor box.
Click Save.
Click Close to exit the Tagname Dictionary dialog box.
Configuring Deviation Alarms
A deviation alarm is associated with integer or real tags. You can set an alarm by comparing the current tag value to a target value, and then the absolute value of the difference is compared to one or more limits, expressed as a percentage of the range of the tag value.
For example, the following values set the conditions for a tag’s minor and major deviation alarms:
Minimum Value = -1000
Maximum Value = 1000
Minor Deviation % = 10
Major Deviation % = 15
Target Value = 500
Using these values as an example, the minor and major deviation alarms points are calculated by the following steps:
Calculate the total value range of the tag.
1000 – (-1000) = 2000
Multiply the total value range of the tag by minor and major deviation percentages.
2000 x 0.10 = 200 = minor deviation limit
2000 x 0.15 = 300 = major deviation limit
Add and subtract the minor and major deviation limits from the target value.
500 – 200 = 300 = minor deviation lower limit
500 + 200 = 700 = minor deviation upper limit
500 – 300 = 200 = Major deviation lower limit
500 + 300 = 800 = Major deviation upper limit
To configure a deviation alarm
Open the Tagname Dictionary.
Select an existing real or integer tag or create a new tag.
Click either Alarms or Details & Alarms at the top of the Tagname Dictionary dialog box to show the alarm details dialog box.
Select the deviation (Minor and Major Deviation) alarm types you want to use to detect when the value of an analog type tag is in a major or minor deviation from the specified target value.
In the %Deviation box, type the percentage that the analog tag can deviate from the target value to trigger a minor or major deviation alarm condition. It is expressed as a percentage of the range of the tag. For an I/O tag, the Min EU and Max EU values entered in the tag’s details dialog box define the range. For memory tags, the range is defined by the minimum value and maximum value.
In the Target box, type the tag reference value that minor and major deviation percentages are based.
In the Deviation Deadband % box, type the deviation percentage the tag value must drop below the limit before the tag is taken out of its alarm condition.
Click Save.
Configuring Alarms Configuring Alarms Configuring Alarms Configuring Alarms Configuring Alarms Configuring AlarmsConfiguring AlarmsConfiguring AlarmsConfiguring AlarmsConfiguring AlarmsConfiguring AlarmsConfiguring AlarmsConfiguring AlarmsConfiguring AlarmsConfiguring AlarmsConfiguring AlarmsConfiguring AlarmsConfiguring Alarms
Click Close to close the Tagname Dictionary dialog box.
Configuring Rate of Change Alarms
A rate of change alarm detects when the value of an alarm changes beyond an specified range over a specified interval. The tag is tested for a rate-of-change alarm whenever its value changes. The change rate is calculated using the previous value, the time of the last update, the current value, and the current time.
The calculated value is compared to the rate-of-change percentage allowance specified for the tag. If the rate-of-change is greater than the percentage allowance, the alarm condition is set for the tag. A rate-of-change alarm remains in effect until the rate at which the tag is changing drops below the alarm limit.
To configure a rate of change alarm
Open the Tagname Dictionary.
Select an existing real or integer tag or create a new tag.
Click either Alarms or Details & Alarms at the top of the Tagname Dictionary dialog box to show the alarm details dialog box. The following figure shows only those options that apply to rate-of-change alarms.
Select the Rate of Change box.
In the % per box, enter the maximum allowable percentage change limit.
Select Sec, Min, or Hr as the time interval unit.
In the Priority box, type a number between 1 and 999 to set the alarm priority.
Optionally assign an alarm inhibitor tag for the rate of change alarm.
In the Alarm Inhibitor area, click the button to show the Select Tag dialog box containing a list of defined tags.
Select a tag from the list and click OK. The name of the tag you selected as the inhibitor tag appears in the Alarm Inhibitor box.
For more information on inhibiting alarms, see Inhibiting Alarms.
Click Save.
Click Close to close the Tagname Dictionary dialog box.
Disabling Alarms
You can disable or enable all alarms of a tag at once using the .AlarmEnabled or AlarmDisabled dotfields. For an alarm that has sub-states, each sub-state can be individually disabled. For example, an analog value alarm can have Hi enabled and HiHi disabled.
During run time, the Alarm Provider does not generate alarms for an alarm or sub-state that is disabled. Changes to whether an alarm is disabled or enabled can be made at run time.
Whenever an alarm transitions from disabled to enabled, the checking logic determines whether the item should be put in the alarmed state by the Alarm Provider.
If an alarm becomes disabled or actively inhibited while the item is in an alarmed state, the item will be forced to a different (valid) state. What that state should be depends upon which states are available and whether they have also been disabled. This activity is handled by the Alarm Provider according to the type of alarm and limit values.
Also Read:-