Configure alarms and events for application objects
- Last UpdatedJan 16, 2025
- 3 minute read
The following table shows the different types of alarms that can be specified for application objects. The table shows the application objects containing native alarm attributes.
You can also set alarms for an object’s attributes. The types of alarms available depend on the attribute type. For more information about setting alarms for attributes, see Set alarms on the attributes page.
|
Application Object |
Alarm Types |
||||
|---|---|---|---|---|---|
|
State |
Limit |
Target Deviation |
Rate of Change |
Statistics |
|
|
AnalogDevice |
X |
X |
X |
X |
|
|
DiscreteDevice |
X |
X |
|||
|
FieldReference |
|||||
|
Sequencer |
X |
||||
|
SQLData |
|||||
|
UserDefined |
X |
X |
X |
X |
|
The following list shows the types of alarms for each application object in more detail.
-
AnalogDevice
-
Level alarms (HiHi, Hi, Lo, LoLo) [limit alarms]
-
Rate of Change alarms (Up, Down)
-
Target Deviation alarms (Minor, Major)
-
PV Bad Value alarm [state alarm]
-
-
DiscreteDevice
-
Uncommanded change alarm [state alarm]
-
Command time-out alarm [state alarm]
-
Active1 state alarm [state alarm]
-
Active2 state alarm [state alarm]
-
Fault state alarm [state alarm]
-
Active1 state duration alarm [statistical alarm]
-
Active2 state duration alarm [statistical alarm]
-
-
Sequencer
-
Execution halted [state alarm]
-
Condition trigger failure [state alarm]
-
OnEntry output failure [state alarm]
-
OnExit output failure [state alarm]
-
-
UserDefined (Attributes can be alarmed)
-
PV State alarm [state alarm]
-
PV Bad Value alarm (that is, bad quality) [state alarm]
-
Attribute alarm features
State alarms
Limit alarms (HiHi, Hi, Lo, LoLo)
Rate of Change alarms (Up, Down)
Deviation alarms (Minor, Major)
Bad Value alarm (that is, bad quality)
-
There are no built-in alarms for these application objects:
-
FieldReference
-
SQLData
You can also configure your application objects to generate an event each time the object’s PV value changes.As mentioned above, you can also configure an alarm on any object for any attribute. See Set alarms on the attributes page for more information.
To configure alarming and events for application objects
-
Open the application object with the Object Editor.
-
For a DiscreteDevice, select the General tab, enable inputs, and then enable Generate event upon PV.

For objects that do not include this check box, use the Attributes page.
Note: If you are using field attributes instead of Attributes, use the Field Attributes page.
-
Enable the Log change feature.
-
Enable Generate event upon change.

-
-
Select or clear the check box based on whether you want to generate an event each time the object’s PV value changes.
-
Select the tab that lists alarm attributes.
-
For the AnalogDevice object, select Alarms.
-
For the DiscreteDevice object, select Alarms.
-
For the Sequencer object, select Settings.
-
For the UserDefined object, select Attributes (or Field Attributes, if you are using field attributes). See Set alarms on the attributes page for further directions.
-
-
Select the check box that enables alarming for the object.
-
Assign values to the attributes for the type of alarm you selected by completing the following steps:
-
Assign values to the alarm limits based on the type of alarm.
-
Assign an alarm priority (1-999) for each limit you set.
-
Accept the default alarm message or include another message for each alarm limit.
-
Assign values to the remaining attributes based on the type of alarm you selected. For more information about other alarm attributes, see Types of alarms.
-
-
Save your object changes and close the Object Editor.