Difference between revisions of "uaCap:AlarmsConditions NonExclusive"

From UaCapabilities
Jump to: navigation, search
 
Line 1: Line 1:
 
{{CapabilityUri|/Alarms/NonExclusive}}
 
{{CapabilityUri|/Alarms/NonExclusive}}
 
'''Description'''
 
'''Description'''
<br>The alarm model can function in one of two manners. In this manner, more than one sub-state can be active at a time. For example, if a temperature exceeds the HighHigh limit the associated non-exclusive LevelAlarm will be in both the High and the HighHigh sub-state.
+
<br>The sub-states in the alarm model can function in two different modes: exclusive or non-exclusive. Non-exclusive means that more than one sub-state can be active at a time. For example, if a temperature exceeds the HighHigh limit the associated non-exclusive LevelAlarm will be in both the High and the HighHigh sub-state.
  
 
'''Usage Considerations'''
 
'''Usage Considerations'''

Latest revision as of 13:26, 16 February 2015

URN:          https://opcfoundation.org/wiki/index.php/Alarms/NonExclusive

Description
The sub-states in the alarm model can function in two different modes: exclusive or non-exclusive. Non-exclusive means that more than one sub-state can be active at a time. For example, if a temperature exceeds the HighHigh limit the associated non-exclusive LevelAlarm will be in both the High and the HighHigh sub-state.

Usage Considerations
All Alarm system include at least one of the alarm models (exclusive or non-exclusive).


Conformance Testing

Client Server

Ability to use non-exclusive Alarms

Support of non-exclusive Alarms