Search

23 result(s) for StateMachines

• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  7.1 Overview
  that 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 & Conditions
  F.1 Overview
  limits 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: Programs
  A.2.2 DomainDownload states
  standard 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: Programs
  A.2.6.2 DomainDownloadType
  optional 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 Machines
  4.3 Definition of state machine
  SubStateMachines , 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 Machines
  4.4.1 Overview
  StateMachine . 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 Machines
  4.4.3 StateVariableType
  provide 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 Machines
  4.4.6 FiniteStateMachineType
  FiniteStateMachineType 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 Machines
  4.4.19 Special Restrictions on subtyping StateMachines
  Special 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 Machines
  4.4.20 Specific StatusCodes for StateMachines
  Specific 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 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
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.6.1 Overview
  Overview This section describes extensions to the StateMachine model allowing choices and guards on StateMachines
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  5 Modelling Approach of PackML
  When possible OPC UA constructs will be used to represent parallel PackML concepts including: StateMachines to reflect the state of the system Methods to issue commands to the Server DataTypes
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  6.1 General
  with "PackML" A key point is a standard ObjectType representation of the StateMachines defined in PackML. The model also defines some standard instances that are expected ... DataType naming: All ObjectTypes include " ObjectType " as part of the name All StateMachines will end in "StateMachine", all States will end in "State
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  6.3.1 Overview
  Overview The PackML model when adapted to OPC UA results in a number of StateMachines (see section 6.3.5 for a definition). Instances of these StateMachines may not expose all states
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  6.3.3 PackMLStatusObjectType
  BaseDataVariableType Optional R HasComponent Variable Product PackMLProductDataType[] BaseDataVariableType Optional R In OPC UA defined StateMachines , a mandatory Variable CurrentState provides the current state of the StateMachine , which is the current
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  6.3.5 StateMachines Overview
  StateMachines Overview The Figure 14 provides an overview of the StateMachines that are part of the model. Figure 14 - PackML StateMachines Overview A key point in PackML StateMachines is that ... StateMachines defined in PackML shall require that the optional AvailableTransitions and AvailableStates component of the FiniteStateMachineType be provided on all instance of the StateMachine . This allows Clients to understand
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  7.1.2 Server
  states and transitions supported by the StateMachine . This include the mandatory Sub- statemachines Server PackML State Abort The server supports the Abort Method Server PackML State Clear The server supports
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  B.1.1 LocaleId "en"
  display names for the LocaleId "en" and the State values for all StateMachines defined in this specification are listed in Table B.1 Table B.1 - Recommended display names
• OPC-40001-3 – OPC UA for Machinery - Part 3: Job Management
  6.3 Integration into a MachineryItem
  MachineryItem may also add several job management instances in order to support different specialized StateMachines for the job orders. In this case, the 2: DefaultInstanceBrowseName should only be used once
• OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management
  C.2.2 Time-based KPI's (Actual times)
  time elements. General: Determination with the use of status variables This specification provides two StateMachines in the MachineOperationMonitoringType : MachineryItemState ( MachineryItemState_StateMachineType ) to represent the machine status in terms of production
• OPC-40718 – OPC UA for Surface Technology - Shot Blasting Machinery
  6 Shot Blasting Technology Information Model overview
  MachineryLifetimeCounter are used to map any counting series. The MachineryOperationMode and MachineryItemState represent the StateMachines provided by the OPC UA for Machinery. Additionally, the Building Block JobManagement can be used
• OPC-40719 – OPC UA for Plasma Surface Technology
  6 Plasma Surface Technology Information Model overview
  MachineryLifetimeCounter are used to map any counting series. The MachineryOperationMode represents a StateMachines provided by the OPC UA for Machinery. The MonitoringType contains all measured values. And the Building Block