Search

Scope: Core (OPC-10000-*) All specs

13 result(s) for TransitionType

OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.11 TransitionType

TransitionType Transitions of a FiniteStateMachine are represented as Objects of the ObjectType TransitionType formally defined in Table 11 . Each Object of the TransitionType or one of its subtypes shall ... References pointing to the effects that occur when the Transition was triggered. Table 11 - TransitionType definition Attribute Value BrowseName TransitionType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

7.2 HasEffectDisable

disabled. The SourceNode of this ReferenceType shall be an Object of the ObjectType TransitionType or one of its subtypes. The TargetNode can be of an Object or AlarmType . The representation
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

7.3 HasEffectEnable

enabled. The SourceNode of this ReferenceType shall be an Object of the ObjectType TransitionType or one of its subtypes. The TargetNode can be of any NodeClass . The representation
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

7.4 HasEffectSuppressed

suppressed. The SourceNode of this ReferenceType shall be an Object of the ObjectType TransitionType or one of its subtypes. The TargetNode can be of any NodeClass . The representation
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

7.5 HasEffectUnsuppressed

suppressed. The SourceNode of this ReferenceType shall be an Object of the ObjectType TransitionType or one of its subtypes. The TargetNode can be of any NodeClass . The representation
OPC-10000-10 – OPC Unified Architecture - Part 10: Programs

5.2.3.3 ProgramStateMachineType transitions

ProgramStateMachineType transitions ProgramStateMachineType Transitions are instances of the TransitionType defined in OPC 10000-16 which also includes the definitions of the ToState, FromState, HasCause, and HasEffect references used. Table
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.6 FiniteStateMachineType

activated. The Transitions that may occur are represented with instances of the TransitionType . Each Transition shall have a BrowseName which is unique within the StateMachine and may have a TransitionNumber
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.12 FromState

Transition connects. The SourceNode of this ReferenceType shall be an Object of the ObjectType TransitionType or one of its subtypes. The TargetNode of this ReferenceType shall be an Object
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.13 ToState

Transition connects. The SourceNode of this ReferenceType shall be an Object of the ObjectType TransitionType or one of its subtypes. The TargetNode of this ReferenceType shall be an Object
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.14 HasCause

initial state. The SourceNode of this ReferenceType shall be an Object of the ObjectType TransitionType or one of its subtypes. The TargetNode can be of any NodeClass . The representation
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.15 HasEffect

EventTypes . The SourceNode of this ReferenceType shall be an Object of the ObjectType TransitionType or one of its subtypes. The TargetNode can be of any NodeClass . If the TargetNode
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.6.3 HasGuard

True"). The SourceNode of this ReferenceType shall be an Object of the ObjectType TransitionType or one of its subtypes. The TargetNode shall be a Variable of the VariableType GuardVariableType
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.9.2 ConnectionConfigurationSetStateMachineType definition

defined in subsequent clauses. The ConnectionConfigurationSetStateMachineType is formally defined in Table 91 . StateType and TransitionType only exist in the type system; thus, they do not have a modelling rule. Table ... StateType 0:HasComponent Object 4:Error 0:StateType 0:HasComponent Object 4:ReadyToProcessing 0:TransitionType 0:HasComponent Object 4:ProcessingToReady 0:TransitionType 0:HasComponent Object 4:ProcessingToError 0:TransitionType