Search

17 result(s) for States

• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  F.2 SystemStateStateMachineType
  SystemStateStateMachineType 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 Machines
  4.3 Definition of state machine
  assume 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 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 ... 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 Machines
  4.4.9 StateType
  StateType 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 Machines
  4.4.19 Special Restrictions on subtyping StateMachines
  subtyping 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 Machines
  4.5.1 StateMachineType using inheritance
  defined, 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 Machines
  4.5.2 StateMachineType with a SubStateMachine using inheritance
  simplicity 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 Machines
  4.5.4 Example of a StateMachine having Transition to SubStateMachine
  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, 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 Machines
  4.5.5 Example of a StateMachine adding a SubStateMachine on a Subtype
  StateMachine 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 Model
  6.9.1 Overview
  executed 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
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  6.3.5 StateMachines Overview
  provided on all instance of the StateMachine . This allows Clients to understand the available States and Transitions for the given instance of the StateMachine . A StateMachine may restrict the States ... Transition that are currently available. The following figure provides an overview of the PackML States. The Stopped State is commonly the initial sub-state that will be the starting point
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  12.1 Overview
  provides information about the state of a MachineryItem . It defines some common top-level states. Companion specifications or vendors might extend those states with substates, but cannot add additional ... level states. In order to have a modelling mechanism that allows the creation of substate, but also to define causes and effects on specific transitions, the concept of a FiniteStateMachine
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  12.2 MachineryItemState_StateMachineType
  TransitionType - 0:HasComponent Object FromExecutingToExecuting - 0:TransitionType - Conformance Units Machinery MachineryItem State The States and Transitions define a StateMachine as shown in Figure 14 . It does not define an initial ... State , i.e., the initial State is vendor-specific. Note: None of the States or Transitions have a ModellingRule , i.e., they are only provided in the TypeDefinition , not on the instance
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  13.1 Overview
  intention of this base specification is not to restrict the Transitions between the States , the StateMachine defines Transitions between all States . Instances might restrict the usage of the defined States ... StateMachine . An overview of the StateMachine is given in Figure 17 . The States are further described in 13.2 . Note that the MachineryOperationMode may not be known by the MachineryItem itself
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  13.2 MachineryOperationModeStateMachineType
  TransitionType - 0:HasComponent Object FromProcessingToProcessing - 0:TransitionType - Conformance Units Machinery Operation Mode The States and Transitions define a StateMachine as shown in Figure 17 . It does not define an initial ... State , i.e., the initial State is vendor-specific. Note: None of the States or Transitions have a ModellingRule , i.e., they are only provided in the TypeDefinition , not on the instance
• OPC-40530 – OPC UA for Laser Systems
  7.2.4 LaserSystemState_StateMachine ObjectType Definition
  This is done using a FiniteStateMachine as defined in OPC 10000-16. The chosen states (see Figure 7 ) are generalized and not manufacturer specific, to allow a wide variety ... Since the intention of this specification is not to restrict the transitions between the states, the state machine defines transitions between all states. Instances might restrict the usage
• OPC-40740 – OPC UA for Process Air Extraction and Filtration Systems (PAEFS)
  7.5.4 MachineryItemState StateMachine
  This building block provides information about the state of a MachineryItem . It defines the states NotAvailable , OutOfService , NotExecuting and Executing . The exact semantics of the states are defined ... StateMachine defines Transitions between all States . Instances might restrict the usage of the defined States and Transitions . An overview of the StateMachine is provided in Figure 15 . Figure 15 - MachineryItemState