Академический Документы
Профессиональный Документы
Культура Документы
278589
Tagable (AlmTag) ........................................................................................................................................................7-2 Analog Tagger (ATAG) ...............................................................................................................................................7-3 Overview.................................................................................................................................................................... 7-3 TagName Reporting ........................................................................................................................................... 7-3 Configuring Filtering ......................................................................................................................................... 7-4 Configuring Alarm Behavior ............................................................................................................................. 7-4 Logging Behavior .............................................................................................................................................. 7-6 Event Behavior .................................................................................................................................................. 7-6 Delta Alarming................................................................................................................................................... 7-6 Alternate Return to Normal Alarm Severity ...................................................................................................... 7-6 Creating a Snooze Alarm ................................................................................................................................... 7-6 Reducing Nuisance Alarms ................................................................................................................................ 7-7 Using Mode to Force an Output Value .............................................................................................................. 7-7 Creating Custom Alarm Text ............................................................................................................................. 7-7 Attributes ................................................................................................................................................................... 7-8 Digital Tagger (DTAG) .............................................................................................................................................7-11 Overview.................................................................................................................................................................. 7-11 TagName Reporting ......................................................................................................................................... 7-12 Configuring Alarm Behavior ........................................................................................................................... 7-13 Logging Behavior ............................................................................................................................................ 7-13 Event Behavior ................................................................................................................................................ 7-13 Alternate Return to Normal Alarm Severity .................................................................................................... 7-13 Creating a Snooze Alarm ................................................................................................................................. 7-14 Reducing Nuisance Alarms .............................................................................................................................. 7-14 Using Mode to Force an Output Value ............................................................................................................ 7-14 Creating Custom Alarm Text ........................................................................................................................... 7-14 Attributes ................................................................................................................................................................. 7-14
Metso Automation
7- 1
278589
Tagable (AlmTag)
Tagable atomic blocks consist of Analog Tagger (ATAG) Digital Tagger (DTAG) Use the Analog Tagger (ATAG) atomic block to assign a tagname, scaling, alarming, and value forcing capability to any analog point, and use the Digital Tagger atomic block to apply similar capabilities to digital points. These atomic blocks are typically used to assign tagnames and alarming capabilities to individual signals entering buffers and to points related to PID-related atomic blocks. See Chapter 3, "Atomic block Category: Buffers," and Chapter 4, "Atomic block Category: Modulating Control Logic." The following two sections discuss key features of each atomic block, such as value forcing using the Mode and ForcedVal parameters, configuring a snooze alarm, creating custom alarm text, and other features. Parameters included with this atomic block allow you to assign a tagname to a point, set alarm and range high and low limits, range clamping, and various alarm behaviors.
Metso Automation
7- 2
278589
Overview
Use the Analog Tagger (ATAG) atomic block to assign a tagname, scaling, alarming, and value forcing capability to any analog point. Parameters included with this atomic block allow you to assign a tagname to a point, set alarm and range high and low limits, range clamping, and various alarm behaviors. This atomic block is typically used to assign tagnames and alarming capabilities to individual signals entering buffers and to points associated with PID-related atomic blocks. See Chapter 3, "Atomic block Category: Buffers," and Chapter 4, "Atomic block Category: Modulating Control Logic." Changes simple input to complex output(OutCtl)
TagName Reporting
The tagname reported with an alarm has always been the tagname or service name of the alarming block (DPU 2.0 or earlier). With DPU 2.1 this is still true except for the following case. The tagname reported with an ATAG or DTAG alarm will be the tagname of the block that the defeat attribute is wired to. For example, multiple taggers in a macro could share a common defeat that is defined in the macro shell.
Metso Automation
7- 3
278589
ATAG Defeat
If either or both of the taggers above went into alarm (and defeat is false), 2 alarms could be shown on the alarm summary or alarm list with a tagname X. Acknowledging one of the alarms would acknowledge them both since it would use the macro tagname and acknowledge all alarms in its group. Each alarm acknowledge is stored as an event. Only a wire from the defeat attribute of a tagger causes this behavior. NOTE: It is illegal to put atoms with tagnames in a macro. If the atoms in the above example had tagnames, those tagnames would be shown on the alarm list regardless of a defeat reference. This could result in alarms being listed that could not be acknowledged.
Configuring Filtering
Use the FilterTC to configure value filtering. Filtering is performed as a rolling average using the following formula: TC = FilterTC / ElapsedTime FilteredValue = ((LastFilteredValue * (TC-1)) + InputValue) / TC For example a FilterTC of 1 and an elapsed time of .5 seconds yields a 50% contribution from the current input value into the rolling average. A FilterTC of 2 yields a 25% contribution.
Metso Automation
7- 4
278589
Set this parameter to 1 to generate a normal alarm when an acknowledged alarm clears. The default setting (0) is a no Return to Normal alarm. Normally, cleared but unacknowledged alarms stay on the alarm list until acknowledged. Select the second option to cause the alarms (except NORMAL alarms) to be removed from the list automatically when cleared, even if unacknowledged. Select option 3 to do both. ATAG Rate Alarm maxDPU version 2.1 supports ATAG rate alarms. configured to enable a rate alarm: Attributes to be
LimRate Value that when exceeded will cause a rate alarm to be generated. Disables rate alarms and CondRate when set to 0. LimRate value should be positive. RateTime Time period for the rate calculation. Should be entered in seconds. If set to 0, time period is the same as the time class. RateClamp is not used at this time since there is no visible rate value (Status or Output attribute) to clamp. Future attributes: Rate, EnRate. ATAG always checks for rising rate and falling rate (if LimRate is nonzero). Rate is the lowest priority ATAG alarm. If a limit alarm is active and the rate limit is exceeded, a rate alarm is not generated. If a rate alarm is active and a limit alarm occurs, the limit alarm will be shown on the alarm summary. Rate Calculation: If RateTime is not zero Rate = DeltaValue * (RateTime / DeltaTime) Else Rate = DeltaValue Hysteresis is applied to the rate value. Calculated rate value is not visible at this time. A Rising rate alarm is generated if the rate value >= rate limit. A Falling rate alarm is generated if the rate value <= -rate limit.
Metso Automation
7- 5
278589
Rising rate alarm is cutout by HiCutout. Falling rate alarm is cutout by LoCutout. CondRate attribute is set if the rate value exceeds the LimRate even if a limit alarm is active.
Logging Behavior
By default, all alarms (Severity 1 to 5) are also logged. If Log Only is selected in the AlmBehave attribute, all alarms are logged including severity 0. Additionally, no alarms are generated for the atomic block (treated as if it is severity 0).
Event Behavior
When an alarm occurs, an alarm event (Alm) is generated. A clear event (Clr) is generated when the alarm condition clears. These events are generated each time there is a transition into or out of alarm regardless of whether the alarm has been acknowledged. An acknowledge event occurs when the alarm is acknowledged and is displayed as an Edit Action (EA). The behavior of the events is slightly different than the maxPAC buffers and MIO buffers. For more details on event behavior of maxPAC buffers, refer to Event Behavior in Chapter 3. For details of event behavior in MIO buffers, refer to Event Behavior in manual MIO Buffers Programmers Reference and Users Guide (278732).
Delta Alarming
A delta alarm is displayed on the alarm screen as a HiHi or LoLo alarm. The value and limit exceeded is displayed in the alarm line. There is currently no indication of whether the value is getting better or worse.
Metso Automation
7- 6
278589
Use the AlmDelay parameter to reduce the occurrence of nuisance alarms. This attribute can delay alarm generation from 1 second up to 1 hour. Use this feature for points that characteristically reach an alarm state only momentarily and then revert back to a normal state.
Metso Automation
7- 7
278589
Attributes
Output Description/Application TRUE if an alarm is in the alarm list. FALSE if no alarm in the list. True if output exceeds high limit. Calculated regardless of enable state, cutout state or defeat state. Not latched True if output exceeds high high limit. Calculated regardless of enable state, cutout state or defeat state. Not latched True if output exceeds low limit. Calculated regardless of enable state, cutout state or defeat state. Not latched True if output exceeds low low limit. Calculated regardless of enable state, cutout state or defeat state. Not latched True if output exceeds range high limit. Calculated regardless of enable state, cutout state or defeat state. Not latched. True if output exceeds range low limit. Calculated regardless of enable state, cutout state or defeat state. Not latched True if output exceeds rate limit. Calculated regardless of enable state, cutout state or defeat state. Not latched Output value Complex Output Output percent Inputs Description/Application Disables all high limit alarms when true Disables all low limit alarms when true Input value
Name AnyAlarm CondHi CondHiHi CondLo CondLoLo CondRangeHi CondRangeLo CondRate Out OutCtl OutPct
Type Float/ Bool Float Float Float Float Float Float Float Float Complex Float
Name Type Float HiCutout Float LoCutout Complex InCtl ** Normally Referenced
Name AlmBehave
Type Float
Configuration Parameters Description/Application Alarm behavior. 0 = No return to normal alarm (default), 1 = Create a normal alarm if acknowledged alarm clears, 2 = Auto acknowledged alarm when cleared, 3 = Create a normal alarm and auto acknowledge (1 and 2), 4 = Log Only. Number of seconds to delay alarm Another group hierarchy that can be used for alarm filtering. Tagname of a group. Alarm Severity (0-5). No alarms for severity 0. Alternate Description of point Alternate Short Description of point Alternate units of measure
Metso Automation
7- 8
278589
Desc EnHHLL
String Float
EnHiLo EnRange FilterTC ForcedVal Gname Hysteresis LimDeltaHi LimDeltaLo LimHi LimHiHi LimLo LimLoLo LimRangeHi LimRangeLo LimRate
Float Float RelTime Float String Float Float Float Float Float Float Float Float Float Float
Mode
Long
RangeClamp RateClamp RateTime ReAlarmTime ScaleEn ShDesc TagName TUOM UserRef RetAlmSev
Float Float Time Time Float/ Bool String String String Long/ String Float
** Normally Constants
Metso Automation
7- 9
278589
Status Description/Application Current acknowledged state. Readable only. 1 = acknowledged, 0 = unacknowledged. Calculated Rate of Change Value Alarm description Set to the current alarm type as follows: 0 = Clear alarm No alarm is active or alarms are Defeated 1 = Clear Digital alarm. Not used by ATAG. 2 = Digital alarm Digital alarm is active. Not used by ATAG 3 = Normal alarm Denotes a return to normal alarm. AlmType set to this if AlmBehave = 1 and the previous type was not normal, alarm is acknowledged and the severity is not 0. 4 = Rising alarm Denotes rate limit is exceeded upwards. Only set if other alarm types are not active. 5 = Falling alarm Denotes rate limit is exceeded downwards. Only set if other alarm types are not active. 6 = Low alarm Denotes low alarm limit exceeded. 7 = High alarm Denotes high alarm limit exceeded 8 = Low Low alarm Denotes LoLo alarm limit exceeded 9 = High High alarm Denotes HiHi alarm limit exceeded 10 = Range Low alarm Denotes low range limit exceeded 11 = Range High alarm Denotes high range limit exceeded Set to the latched (unacknowledged) alarm type. Types are defined above. Handle of tagname specified in the AlmParent attribute. Current alarm state: 0 = no alarm, 1 = unacknowledged alarm 3 = acknowledged alarm, 4 = cutout (no alarm), 8 = defeated (no alarm), 9 = defeated (unacked alarm), 11 = defeated (acked alarm) Alternate Alarm Description Alarm occurrence time. Updated whenever the alarm changes to a worse state regardless of acknowledge state. Input auctioneering reference Input high range Input low range Input incremental reset Input forceback status Input Type Input value Output auctioneering reference Output high range Output low range Output incremental reset Output forceback status Output type Output value Text for mode Command
AltAlarmText AlmTime InCtlAREF InCtlRHI InCtlRLO InCtlRST InCtlSTAT InCtlTyp InCtlVAL OutCtlAREF OutCtlRHI OutCtlRLO OutCtlRST OutCtlSTAT OutCtlTYP OutCtlVAL Tmode
String Time Float Float Float Float Long Float Float Float Float Float Float Long Long Float String
Metso Automation
7- 10
278589
Alarm behavior 0 = No 'return to normal' alarm 1 = Create a normal alarm if acknowledged alarm clears 2 = Auto acknowledged alarm when cleared 3= create a normal alarm and auto acknowledged (1 and 2) 4 = log only EnHHLL 0 = None 1 = Low 2 = High 3 = Both 4 = Delta 5 = Repetitive Delta HiCut out 0 = False 1 = True LoCutout 0 = False 1 = True RangeClamp 0 = False 1 = True RateClamp 0 = False 1 = True ReAlarm Time 0 = False 1 = True
Overview
Use the Digital Tagger (DTAG) to assign a tagname, simple alarming, and value forcing capability to any digital point.
Metso Automation
7- 11
278589
This atomic block is typically used to assign tagnames and alarming capabilities to individual signals entering buffers and to points related to PID-related atomic blocks. See Chapter 3, "Atomic block Category: Buffers," and Chapter 4, "Atomic block Category: Modulating Control Logic."
TagName Reporting
The tagname reported with an alarm has always been the tagname or service name of the alarming block (DPU 2.0 or earlier). With DPU 2.1 this is still true except for the following case. The tagname reported with an ATAG or DTAG alarm will be the tagname of the block that the defeat attribute is wired to. For example, multiple taggers in a macro could share a common defeat that is defined in the macro shell.
ATAG Defeat
If either or both of the taggers above went into alarm (and defeat is false), 2 alarms could be shown on the alarm summary or alarm list with a tagname X. Acknowledging one of the alarms would acknowledge them both since it would use the macro tagname and acknowledge all alarms in its group. Each alarm acknowledge is stored as an event. Only a wire from the defeat attribute of a tagger causes this behavior. NOTE: It is illegal to put atoms with tagnames in a macro. If the atoms in the above example had tagnames, those tagnames would be shown on the alarm
Metso Automation
7- 12
278589
list regardless of a defeat reference. This could result in alarms being listed that could not be acknowledged.
Logging Behavior
By default, all alarms (Severity 1 to 5) are also logged. If Log Only is selected in the AlmBehave attribute, all alarms are logged including severity 0. Additionally, no alarms are generated for the atomic block (treated as if it is severity 0).
Event Behavior
When an alarm occurs, an alarm event (Alm) is generated. A clear event (Clr) is generated when the alarm condition clears. These events are generated each time there is a transition into or out of alarm regardless of whether the alarm has been acknowledged. An acknowledge event occurs when the alarm is acknowledged and is displayed as an Edit Action (EA). The behavior of the events is slightly different than the maxPAC buffers and MIO buffers. For more details on event behavior of maxPAC buffers, refer to Event Behavior in Chapter 3. For details of event behavior in MIO buffers, refer to Event Behavior in manual MIO Buffers Programmers Reference and Users Guide (278732).
Metso Automation
7- 13
278589
Use the ReAlarmTime parameter to create a snooze alarm. The snooze alarm option causes acknowledged alarms to be promoted to unacknowledged after the passage of a set unit of time. The value and units are configurable
Attributes
Name AnyAlarm Out Type Float/ Bool Float Outputs Description/Application TRUE if an alarm is in the alarm list. FALSE if no alarm in the list. Output value Inputs
Metso Automation
7- 14
278589
Name AlmBehave
Type Float
Mode
Long
Configuration Parameters Description/Application Alarm behavior. 0 = No return to normal alarm, 1 = Create a normal alarm if acknowledged alarm clears, 2 = Auto acknowledged alarm when cleared, 3 = Create a normal alarm and auto acknowledge (1 and 2), 4 = Log Only. Number of seconds to delay alarm Another group hierarchy that can be used for alarm filtering. Tagname of a group Alarm severity (0 to 5) Alternate Description of point Alternate text for false state Alternate Short Description of point Alternate text based on state of output (AltTrText or AltFlsText) Alternate text for true state Disables all alarms when non-zero. A defeated alarm will not log even if set to Log Only. The non zero defeat values are the security level of the defeat, except at nine where the alarm can be defeated at any level and is designated as such by 11 19. Description of point Enables alarming: 0 = No alarm, 1 = Alarm if Hi, 2 = Alarm if low, 3 = Any transition. Text for false state Value that Out will be if Tagger is in Forced Mode Generic name Invert the input Invert the output 1-Latch to True if input true anytime since last execution 2-Latch to False if input false any time since last execution. 3-Filter transients use value if input has been stable since last execution. The Mode of the tagger as one of Normal, Forced, or Track. Track mode behavior is identical to Normal mode, except that if the ForcedVal attribute has no reference assignment, the value of ForcedVal will be kept equal to the currect In value, i.e., Track the input. This will provide a bumpless transfer of the output, should the mode be changed to Forced Acknowledged promoted to unacknowledged after time period specified here. (0 to disable) Short description of point Enable SOE 1-T 2-F 3-Both Name of point Text for true state Tagname of User Object supplying Alarm Text Return to normal Alarm Severity. 0 is same as AlmSev. 1-5 is on return to normal the new Alarm Severity if one is to be generated. Status Description/Application
Metso Automation
7- 15
278589
Metso Automation
7- 16