The ExclusiveLimitAlarmTypeis used to specify the common behaviour for Alarm Typeswith multiple mutually exclusive limits. The ExclusiveLimitAlarmTypeis illustrated in Figure 20.
Figure 20– ExclusiveLimitAlarmType
The ExclusiveLimitAlarmTypeis formally defined in Table 96.
Table 96– ExclusiveLimitAlarmType definition
|
Attribute |
Value |
||||
|
BrowseName |
ExclusiveLimitAlarmType |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Subtype of the LimitAlarmType defined in clause 5.8.18. |
|||||
|
HasSubtype |
ObjectType |
ExclusiveLevelAlarmType |
Defined in Clause 5.8.21.3 |
||
|
HasSubtype |
ObjectType |
ExclusiveDeviationAlarmType |
Defined in Clause 5.8.22.3 |
||
|
HasSubtype |
ObjectType |
ExclusiveRateOfChangeAlarmType |
Defined in Clause 5.8.23.3 |
||
|
HasComponent |
Object |
LimitState |
|
Mandatory |
|
|
ConformanceUnits |
|||||
|
A & C Exclusive Limit |
|||||
The LimitStateis a sub state of the ActiveState and has an IsTrueSubStateOfreference to the ActiveState. The LimitStaterepresents the actual limit that is violated in an instance of ExclusiveLimitAlarmType. When the ActiveStateof the AlarmConditionTypeis inactive the LimitStateshall not be available and shall return NULL on read. Any Eventsthat subscribe for fields from the LimitStatewhen the ActiveStateis inactive shall return a NULL for these unavailable fields.