ALMD Properties dialog box - Configuration tab

Condition to trigger the alarm.

Select Input = 1 for an active alarm when In = 1. Select Input = 0 for an active alarm when In = 0.

Select a severity ranging from 1...1000 to rank the importance of an alarm condition. The severity does not affect processing of alarms by the controller, but is used for sorting and filtering functions at the alarm subscriber.

By default, in the

FactoryTalk Alarms and Events

system, severity ranges are mapped to priorities:

1...250 are Low priority.

251...500 are Medium priority.

501...750 are High priority.

751...1000 are Urgent priority.

Configure the severity to priority mapping in the

FactoryTalk Alarms and Events

system. For details, see the

FactoryTalk

Help:

Start > Programs >

Rockwell Software

>

FactoryTalk

Tools >

FactoryTalk

Help

.

Enter the amount of time in milliseconds an alarm condition must be active before reporting the alarm.

Enter the length of time in minutes to shelve an alarm. Minimum is 1 minute. This sets the value of the ShelveDuration tag.

Shelving an alarm postpones alarm processing. Similar to suppressing an alarm, except that shelving is time limited. If an alarm is acknowledged while it is shelved, it remains acknowledged even if the alarm becomes active again. The alarm becomes unacknowledged when the shelve duration ends, provided the alarm is still active.

Enter the maximum time duration in minutes to shelve an alarm. This sets the value of the MaxShelveDuration tag.

Tip: Setting the value of the ShelveDuration tag to exceed the time specified in the MaxShelveDuration tag is possible, either programmatically or through HMI. However, the Maximum Duration setting takes precedence, and the alarm remains shelved for the duration specified in the MaxShelveDuration tag.

Select this box to latch the alarm. A latched alarm remains active after the alarm condition becomes false, until a reset command is received. The reset command is ignored until the alarm condition is false.

Select to require acknowledgment of the alarm.

The message string (maximum of 255 characters, including characters that specify embedded variables) contains the information to display to the operator regarding the alarm. Enter text and/or embed variable information. Click to open the alarm message editor. Select the variable and add it anywhere in the message string.

Cannot programmatically access the alarm message string from the alarm tag. To change the alarm message based on specific events, configure one of the associated tags as a string data type and embed that associated tag in the message.

Create a new tag associated with the alarm. To create a tag:

Specify up to four tags that contain pertinent data when alarm conditions occur. A snapshot of the values in these tags is stored whenever the .In condition changes to the In Alarm state, or other alarm state changes occur. The stored values are transmitted to the alarm subscribers. The stored values can be embedded in the alarm Message.

Associated tags may be any atomic data type (BOOL, DINT, INT, SINT, LINT or REAL) or a STRING. They may be elements in a UDT or an Array. Variable array references are not allowed.

If the alarm is controller-scoped, the associated tags must also be controller-scoped.

Associated tags may be specified by typing the tag name directly, choosing an existing tag from the list, or using New Tag... .

Group related alarms. Specify the alarm class exactly the same for each alarm to group in the same class. The alarm class is case sensitive.

For example, specify class Tank Farm A to group all the tank alarms for a specific area. Or, specify class Control Loop to group all alarms for PID loops.

Display and filter alarms at the HMI based on the class. For example, an operator can display all tank alarms or all PID loop alarms.

Alarm Class does not limit the alarms that an Alarm Summary object subscribes to; it can only be used to filter the alarms that are displayed to the operator once they have been received by the Summary.

Enter a command to execute on the operator station when requested by an operator for a specific alarm. This lets an operator execute any standard

FactoryTalk View

command, such as call specific faceplates and displays, execute macros, access help files, and launch external applications. When the alarm condition occurs and displays to the operator, a button on the summary and banner displays lets the operator run an associated view command. Be careful to enter the correct command syntax and test the command at runtime because no error checking performed when the command is entered.

Enter a command to execute on the operator station when requested by an operator for a specific alarm. This lets an operator execute any View 5000 command, such as call specific faceplates and displays, execute macros, access help files, and launch external applications. When the alarm condition occurs and displays to the operator, a button on the summary and banner displays lets the operator run an associated view command. Be careful to enter the correct command syntax and test the command at runtime as no error checking is performed when the command is entered.

The Status pane shows the alarm state. Reset, acknowledge, disable or enable, and shelve or unshelve the alarm.

Click to accept the edits and close the dialog box.

Click to close the dialog box without accepting the edits.

Click this button to apply your edits and continue editing in this dialog box.

Click for help on this tab.