Search
9 result(s) for SubStateMachine
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.6 FiniteStateMachineTypeunique across all States defined in the StateMachine . Be aware that States in a SubStateMachine may have the same StateNumber or BrowseName as States in the parent machine. A concrete ... have a HasSubStateMachine Reference to the StateMachineType Object which represents the child States . The SubStateMachine is not active if the parent State is not active. In this case the CurrentState
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.10 InitialStateTypeFiniteStateMachine does not have to have a State of this type. A SubStateMachine goes into its initial state whenever the parent state is entered. However, a state machine may define ... transition that goes directly to a state of the SubStateMachine . In this case the SubStateMachine goes into that State instead of the initial State . The two scenarios are illustrated
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.16 HasSubStateMachinemost one HasSubStateMachine Reference . The SourceNode (the state) and the TargetNode (the SubStateMachine ) shall belong to the same StateMachine . Therefore, the SourceNode shall be referenced from the ObjectType FiniteStateMachineType
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.17 TransitionEventTypeStateMachine instance where the Transition occurs. If the Transition occurs in a SubStateMachine , then the NodeId of the SubStateMachine has to be used. If the Transition occurs between a StateMachine ... SubStateMachine , then the NodeId of the StateMachine has to be used, independent of the direction of the Transition . Transition identifies the Transition that triggered the Event . FromState identifies the State
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.18 AuditUpdateStateEventTypeStateMachine instance where the State changed. If the State changed in a SubStateMachine , then the NodeId of the SubStateMachine has to be used. The SourceName for Events of this type
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State MachinesSubStateMachines , it may add Transitions from the States to the States of the SubStateMachine , and it may add Causes and Effects to a Transition . In addition, a subtype
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State MachinesStateMachineType with a SubStateMachine using inheritance Figure 8 - Example of a StateMachineType with a SubStateMachine using inheritance Figure 8 gives an example of a StateMachineType having a SubStateMachine ... contains an Object "MySubMachine" of type "AnotherStateMachineType" representing a SubStateMachine . The "State1" references this Object with a HasSubStateMachine Reference , thus it is a SubStateMachine
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State MachinesExample of a StateMachine having Transition to SubStateMachine The StateMachines shown so far only had Transitions between States on the same level, that is, on the same StateMachine . Of cause ... often required to have Transitions between States of the StateMachine and States of its SubStateMachine . Because a SubStateMachine can be defined by another StateMachineType and this type can be used
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State MachinesExample of a StateMachine adding a SubStateMachine on a Subtype When a subtype of FiniteStateMachineType having States extends the StateMachine , it is not allowed to add additional States , but instead ... MySubStateMachineType" is a subtype and extends the StateMachine with a SubStateMachine as defined in Figure 13 . The "MySubSubStateMachineType" is another subtype as defined in Figure