Errata exists for this version of the document.
The NonExclusiveLimitAlarmType is used to specify the common behaviour for Alarm Types with multiple non-exclusive limits. The NonExclusiveLimitAlarmType is illustrated in Figure 19.
Figure 19 – NonExclusiveLimitAlarmType
The NonExclusiveLimitAlarmType is formally defined in Table 64.
Table 64 – NonExclusiveLimitAlarmType definition
|
Attribute |
Value |
||||
|
BrowseName |
NonExclusiveLimitAlarmType |
||||
|
IsAbstract |
False |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
Subtype of the LimitAlarmType defined in clause 5.8.11. |
|||||
|
HasSubtype |
ObjectType |
NonExclusiveLevelAlarmType |
Defined in Clause 5.8.14.2 |
||
|
HasSubtype |
ObjectType |
NonExclusiveDeviationAlarmType |
Defined in Clause 5.8.15.2 |
||
|
HasSubtype |
ObjectType |
NonExclusiveRateOfChangeAlarmType |
Defined in Clause 5.8.16.2 |
||
|
HasComponent |
Variable |
HighHighState |
LocalizedText |
TwoStateVariableType |
Optional |
|
HasComponent |
Variable |
HighState |
LocalizedText |
TwoStateVariableType |
Optional |
|
HasComponent |
Variable |
LowState |
LocalizedText |
TwoStateVariableType |
Optional |
|
HasComponent |
Variable |
LowLowState |
LocalizedText |
TwoStateVariableType |
Optional |
HighHighState, HighState, LowState, and LowLowState represent the non-exclusive states. As an example, it is possible that both HighState and HighHighState are in their True state. Vendors may choose to support any subset of these states. Recommended state names are described in Annex A.
Four optional limits are defined that configure these states. At least the HighState or the LowState shall be provided even though all states are optional. It is implied by the definition of a HighState and a LowState, that these groupings are mutually exclusive. A value cannot exceed both a HighState value and a LowState value simultaneously.