Search

6 result(s) for ConditionBranches

• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  3.1.8 ConditionBranch
  ConditionBranch specific state of a Condition Note 1 to entry: The Server can maintain ConditionBranches for the current state as well as for previous states
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  4.2 Conditions
  components. In certain cases, however, previous states that still need attention are also maintained. ConditionBranches are introduced to deal with this requirement and distinguish current state and previous states. Each ... independent of its state. However, Servers may provide access to Condition instances only while ConditionBranches exist. The base Condition state model is illustrated in Figure 1 . It is extended
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  4.4 Previous states of Conditions
  occur in short succession there can be multiple unacknowledged states and the Server maintains ConditionBranches for all previous unacknowledged states. These branches will be deleted after they have been acknowledged ... they reached their final state. Multiple ConditionBranches can also be used for other use cases where snapshots of previous states of a Condition require additional actions
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  4.5 Condition state synchronization
  This is True even if the only interesting item regarding the Condition is that ConditionBranches exist. This allows a Client to accurately represent the current Condition state. A Client that ... Some Servers - in particular if they require acknowledgement of previous states - will maintain separate ConditionBranches for prior states that still need attention. ConditionRefresh shall issue Event Notifications for all interesting
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.2 ConditionType
  False. The retain bit on the current Event is True, as long as any ConditionBranches require Operator input. See 4.2 for more information about the need for creating and maintaining ... previous ConditionBranches and Clause B.1 for an example using branches. The BranchId DataType is NodeId although the Server is not required to have ConditionBranches in the AddressSpace
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.7.2 AcknowledgeableConditionType
  Condition instance as specified in 4.2 . Clients are expected to keep track of all ConditionBranches where AckedState /Id is False to allow acknowledgement of those. See also 5.5.2 for more ... information about ConditionBranches and the examples in Clause B.1 . The handling of the AckedState and branches also applies to the ConfirmedState . In the event of a restart of an AlarmManager