Search
10 result(s) for States
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsSystemStateStateMachineType The SystemStateStateMachineType includes a hierarchy of sub-states. It supports multiple transitions between Operating, StartingUp, ShuttingDown, Shutdown, OutOfService and Maintenance. The state machine is illustrated in Figure ... Optional HasComponent Method OutOfServiceShutdown Defined in Clause XXX Optional The actual selection of States and Transitions would depend on the deployment of the StateMachine . If the StateMachine were being applied
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machinesassume that state machines are typed and instances of a type have their states and semantics specified by the type. For some types, this means that the states and transitions ... fixed. For other types the states and transitions may be dynamic or unknown. A state machine where all the states are specified explicitly by the type is called a finite
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.6 FiniteStateMachineTypeFiniteStateMachineType The FiniteStateMachineType is the base ObjectType for StateMachines that explicitly define the possible States and Transitions . Once the States and Transitions are defined subtypes shall not add new States ... Transitions (see 4.4.19 ). Subtypes may add causes or effects. The States of the machine are represented with instances of the StateType ObjectType. Each State shall have a BrowseName which
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.9 StateTypeStateType States of a FiniteStateMachine are represented as Objects of the StateType. Each Object of the StateType or one of its subtypes shall be referenced from the ObjectType FiniteStateMachineType
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machinessubtyping apply for StateMachine types as well. Some additional rules apply for StateMachine types. States and Transitions are not instantiated, this information is only provided on the ObjectType . They have ... ModellingRule , and thus, also the inheritance of States and Transitions is not defined. Therefore, the following rules apply for subtyping StateMachines . Each State and Transition defined on the supertype shall
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machinesdefined, called "MyStateMachineType", inheriting from the base FiniteStateMachineType . It contains two States , "State1" and "State2" and a Transition "Transition1" between them
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machinessimplicity no effects and causes are shown, as well as type information for the States or ModellingRules . The "MyStateMachineType" contains an Object "MySubMachine" of type
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State MachinesStateMachine 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, it is possible ... 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 MachinesStateMachine 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 SubStateMachines ... added to existing States . The example in Figure 12 shows a very simple StateMachine with two States . Figure 12 - Example of a StateMachine with two States In Figure
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.9.1 Overviewexecuted internally (a ConnectionManager establishing Connections ) that involve the processing of a ConnectionConfigurationSet . The States and Transitions that comprise the state machine are illustrated in Figure 38 . Numbers in circles