Search
12 result(s) for StateMachines
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions7.1 Overviewthat a specific Effect on Alarm s caused by the transition of a StateMachine . StateMachines that describe the state of a process, system or equipment can vary, but an example
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsF.1 Overviewlimits or other items related to the Alarms in the hierarchy. Optionally, multiple SystemState StateMachines can be deployed. Figure F.1 - SystemState transitions
-
OPC-10000-10 – OPC Unified Architecture - Part 10: ProgramsA.2.2 DomainDownload statesstandard states of a ProgramStateMachineType . Additionally, the DomainDownloadType extends the ProgramStateMachineType by defining subordinate State Machines for the Program's Running and Halted states. The subordinate states describe the download ... performed. The instance exists until explicitly removed by the Client . The initial state of the Program is Ready and the terminal state is Halted. The DomainDownload can be temporarily suspended
-
OPC-10000-10 – OPC Unified Architecture - Part 10: ProgramsA.2.6.2 DomainDownloadTypeoptional ProgramStateMachineType components, valid extensions such as subordinate State Machines , and constrained attribute values applied to instances of DomainDownload Programs . Table A.2 specifies the optional and extended components defined ... model that illustrates the association between the states and the DomainDownload, Transfer, and Finish State Machines. Note that the current state number for the sub State Machines is only valid
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State MachinesSubStateMachines , the StateMachine also contains information about the current state of the SubStateMachines . StateMachines which have their states completely defined by the type are instances of a FiniteStateMachineType . Each FiniteStateMachineType
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.1 OverviewStateMachine . See OPC 10000-9 and OPC 10000-10 for additional examples of StateMachines . Figure 3 - The StateMachine Information Model
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.3 StateVariableTypeprovide vendor-specific information about the current state or the available continuation options. StateMachines produce Events which may include the current state of a StateMachine . In that case Servers shall
-
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
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State MachinesSpecial Restrictions on subtyping StateMachines In general, all rules on subtyping apply for StateMachine types as well. Some additional rules apply for StateMachine types. States and Transitions are not instantiated ... States and Transitions is not defined. Therefore, the following rules apply for subtyping StateMachines . Each State and Transition defined on the supertype shall be available on the subtype as well
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State MachinesSpecific StatusCodes for StateMachines In Table 19 specific StatusCodes used for StateMachines are defined. Table 19 - Specific StatusCodes for StateMachines Symbolic Id Description Bad _ StateNotActive The accessed state
-
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
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.6.1 OverviewOverview This section describes extensions to the StateMachine model allowing choices and guards on StateMachines