Search

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

28 result(s) for Transition

OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

7.2 HasEffectDisable

subtype of HasEffect . The semantic of this ReferenceType is to point from a Transition to an Alarm that will be disabled. If the Reference is to an Object then
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

7.3 HasEffectEnable

subtype of HasEffect . The semantic of this ReferenceType is to point from a Transition to an Alarm that will be enabled. If the Reference is to an Object then
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

7.4 HasEffectSuppressed

subtype of HasEffect . The semantic of this ReferenceType is to point from a Transition to an Alarm that will be suppressed. If the reference is to an Object then
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

7.5 HasEffectUnsuppressed

subtype of HasEffect . The semantic of this ReferenceType is to point from a Transition to an Alarm that will no longer be suppressed. If the Reference is to an Object
OPC-10000-10 – OPC Unified Architecture - Part 10: Programs

5.2.3.2 ProgramStateMachineType states

used to distinguish the nature of the termination. The Halted state references four Transition Objects , which identify the allowed state transitions to the Ready state and from the Ready, Running ... prepared to begin execution. Programs that are ready to begin upon their creation may transition immediately to the Ready state. The Ready state references four Transition Objects, which identify
OPC-10000-10 – OPC Unified Architecture - Part 10: Programs

5.2.5.1 Overview

Effects of each of the Program's state transitions. These Effects are Events. Each Transition shall have a HasEffect Reference to a ProgramTransitionEventType and can have an AuditProgramTransitionEventType. When ... transition occurs, Event notifications of the referenced type are generated for subscribed Clients. The Program Invocation may serve as the EventNotifier for these Events or an owning Object
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.3 Definition of state machine

have one or more SubStateMachines . Each FiniteStateMachineType may have one or more Transitions . A Transition is directed and points from one State to another State . Each Transition can have ... Cause leads a FiniteStateMachine to change its current State from the source of the Transition to its target. In this specification we only specify Method calls to be Causes
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.5 TransitionVariableType

TransitionVariableType The TransitionVariableType is the base VariableType for Variables that store a Transition that occurred within a StateMachine as a human readable name. The SourceTimestamp for the value specifies when ... Transition occurred. This value may also be exposed with the TransitionTime Property . The TransitionVariableType is formally defined in Table 5 . Table 5 - TransitionVariableType definition Attribute Value BrowseName TransitionVariableType DataType LocalizedText
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 ... unique across all Transitions defined in the StateMachine . The initial State for a Transition is a StateType Object which is the target of a FromState Reference . The final State
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.8 FiniteTransitionVariableType

FiniteTransitionVariableType The FiniteTransitionVariableType is a subtype of TransitionVariableType and is used to store a Transition that occurred within a FiniteStateMachine as a human readable name. The FiniteTransitionVariableType is formally defined ... reflect the required DataType . This value shall be the NodeId of one of the Transition Objects of the FiniteStateMachineType . If the FiniteStateMachine is subtyped, it shall be the NodeId
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.11 TransitionType

have a ModellingRule as they are not applied on the instances. Each valid Transition shall have exactly one FromState Reference and exactly one ToState Reference , each pointing to an Object ... ObjectType StateType . Each Transition can have one or more HasCause References pointing to the cause that triggers the Transition . Each Transition can have one or more HasEffect References pointing
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.12 FromState

subtype of NonHierarchicalReferences . The semantic of this ReferenceType is to point from a Transition to the starting State the Transition connects. The SourceNode of this ReferenceType shall be an Object
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.13 ToState

subtype of NonHierarchicalReferences . The semantic of this ReferenceType is to point from a Transition to the ending State the Transition connects. The SourceNode of this ReferenceType shall be an Object ... only exposed uni-directional. Sometimes this is required, for example, if a Transition points to a State of a sub-machine. The representation of the ToState ReferenceType in the AddressSpace
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.14 HasCause

subtype of NonHierarchicalReferences . The semantic of this ReferenceType is to point from a Transition to something that causes the Transition . In this specification we only define Methods as Causes . However
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.15 HasEffect

subtype of NonHierarchicalReferences . The semantic of this ReferenceType is to point from a Transition to something that will be effected when the Transition is triggered. In this specification we only ... NodeClass . If the TargetNode is an EventType , each time the Transition is triggered (either by a Client or internally in the Server ) an Event of that EventType or a subtype
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.17 TransitionEventType

BaseEventType . It can be used to generate an Event identifying that a Transition of a StateMachine was triggered. It is formally defined in Table 17 . Table 17 - TransitionEventType Attribute Value ... TypeDefinition ModellingRule Subtype of the base BaseEventType defined in OPC 10000-5 HasComponent Variable Transition LocalizedText TransitionVariableType Mandatory HasComponent Variable FromState LocalizedText StateVariableType Mandatory HasComponent Variable ToState LocalizedText StateVariableType Mandatory
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.18 AuditUpdateStateEventType

AuditUpdateMethodEventType . It can be used to generate an Event identifying that a Transition of a StateMachine was triggered. It is formally defined in Table 18 . Table 18 - AuditUpdateStateEventType Attribute Value
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.4.19 Special Restrictions on subtyping StateMachines

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. That is, for each State ... same BrowseName and the same StateNumber shall be defined on the subtype. For each Transition defined on the supertype another Node of the same ObjectType having the same BrowseName
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.5.1 StateMachineType using inheritance

FiniteStateMachineType . It contains two States , "State1" and "State2" and a Transition "Transition1" between them. The Transition points to a Method "MyMethod ... Cause of the Transition and an EventType "EventType1" as the Effect of the Transition . Instances of "MyStateMachineType" can be created, for example "MyStateMachine
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.5.4 Example of a StateMachine having Transition to SubStateMachine

Example 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 ... expose the FromState or ToState References uni-directional, that is, only pointing from the Transition to the State and not being able to browse to the other direction
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.6.2 ChoiceStateType

entered. The Guards defined on the Transitions from the ChoiceState determine which Transition is used. The Guards shall be defined in a way that at least one Guard is true ... Transition can be determined. If this is not the case, the StateMachine is non-well formed. To avoid this, the specific ElseGuardVariableType can be used, which is only "true
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.6.3 HasGuard

subtype of HasComponent . The semantic of this ReferenceType is to point from a Transition to a Guard . The Guard indicates if the Transition can be used or not (see GuardVariableType ... Transition can only be used, if the Guard is "True". A Transition can point to several Guards . In that case, all Guards need to be "True
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.6.4 GuardVariableType

GuardVariableType The GuardVariableType provides the information of a Guard of a Transition in a StateMachine . A Guard indicates, if the Transition can be used or not. The Guard defines ... False". Only if the semantic is "True", the Transition connected via a HasGuard Reference can be used. The value of the GuardVariableType provides the semantic
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.6.6 ElseGuardVariableType

once for each State. That means, that each State shall at most have one Transition (referenced as SourceNode ) referencing an ElseGuardVariableType . The ElseGuardVariableType shall be the only Guard ... Transition . That means, if a Transition references an instance of an ElseGuardVariableType , it shall not reference any other Guards . The semantic of the ElseGuardVariableType is, that if a pseudo state
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.7 Example of a StateMachine using a ChoiceState and Guards

representation in the OPC UA AddressSpace is shown in Figure 17 as RobotStateMachineType. The Transition T2 between the ChoiceState and S2_Loaded has the Guard "Else" of ElseGuardVariableType ... Transition T3 between the ChoiceState and S3_Ready has the Guard "OnPathTrue" having an "Expression" Property (not shown in the figure). The ContentFilter of the Expression
OPC-30050 – OPC UA for PackML - Common Object Model: PackML

6.3.5 StateMachines Overview

given instance of the StateMachine . A StateMachine may restrict the States and Transition that are currently available. The following figure provides an overview of the PackML States. The Stopped State
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

8.4.10 ProductionProgramStateMachineType

address space is given in Table 54 . The name of each transition consists of the names of the states it connects: [ FromState ]To[ ToState ]. The ProductionProgramStateMachineType is formally defined ... Units MachineTool Production ProductionProgramStateMachineType The ProductionProgramStateMachineType allows to send Events of ProductionProgramTransitionEventType with every transition, as indicated in Table 54 . This makes it possible to send all relevant information
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

8.4.11 ProductionPartStateMachineType

address space is given in Table 57 . The name of each transition consists of the names of the states it connects: [ FromState ]To[ ToState ]. The ProductionPartStateMachineType is formally defined ... Units MachineTool Production ProductionPartStateMachineType The ProductionPartStateMachineType allows to send Events of ProductionPartTransitionEventType with every transition, as indicated in Table 57 . This makes it possible to send all relevant information