Search

36 result(s) for Ready

• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.9.1 Overview
  ConnectionConfigurationSet . If the transient error has cleared, the state machine will transition to Ready ; otherwise, it will return to Error . The error may be a permanent error that needs correction
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.9.2 ConnectionConfigurationSetStateMachineType definition
  HasComponent Variable 0:LastTransition 0:LocalizedText 0:FiniteTransitionVariableType M 0:HasComponent Object 4:Ready 0:StateType 0:HasComponent Object 4:Processing 0:StateType 0:HasComponent Object 4:Error 0:StateType ... Type IsForward TargetBrowsePath 4:ReadyToProcessing 0:ToState True 4:Processing 0:FromState True 4:Ready 0:HasCause True 4:ConnectionManager 4:ProcessConnectionConfigurationSets 0:HasEffect True 4:ConnectionConfigurationSetProcessingStartedEventType 4:ProcessingToReady
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  8.6 ConnectionConfigurationSetProcessingStartedEventType
  ConnectionConfigurationSetProcessingStartedEventType This EventType is generated by a ConnectionConfigurationSetStateMachine upon transition from the Ready State to the Processing State as a result of a ConnectionManager starting to process the ConnectionConfigurationSet
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  8.7 ConnectionConfigurationSetProcessingSucceededEventType
  EventType is generated by a ConnectionConfigurationSetStateMachineType upon transition from the Processing State to the Ready State after successful completion of the Connection establishment. Its representation in the AddressSpace is formally
• OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  7.12.3 GetReady Method
  authorized Client to request the system to transition from the Idle state to the Ready state . Internally the system prepares to get started in the next step (e.g. switching ... internal preparations for this transition are successful, the system will transition from Idle to Ready . If the internal preparations are unsuccessful then the IdleToIdle transition occurs. In conjunction with
• OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  7.12.4 StandDown Method
  StandDown method allows an authorized Client to request the system to: transition from the Ready state to the Idle state or cancel an ongoing preparation of the system and causes
• OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  7.13.1 Overview
  started because a preparation is needed GettingReady The system was commanded to get ready (internally or via GoToReady () and the needed preparation to get ready is done in this state ... system prepares what is to be done (e.g. switching on intermediate circuit) to be ready to start execution in a next step. Typically, all task controls which participate in system
• OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  7.16 TaskControlStateMachineType
  loaded inside a task control and the possibility to reset the loaded program the Ready State can be extended by the ReadySubstateMachineType. The Task Control Monitor ConformanceUnit supports monitoring ... transitions is shown in When the state machine changes from Executing State to Ready State caused by internal behaviour of the task control (e.g. because program is ended
• OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  7.16.5 UnloadByNodeId Method
  Table 82 . This method might not always result in a state change from Ready to Idle . Table 82 - UnloadByNodeId Method AddressSpace definition Attribute Value BrowseName UnloadByNodeId References NodeClass BrowseName DataType
• OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  7.16.6 UnloadByName Method
  Name input argument. This method might not always result in a state change from Ready to Idle . The possible Method result codes are formally defined in the table below. Table
• OPC-40082-4 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 4: Dosing Systems
  11.15 AbortCleaning
  device MachineryItemState is NotAvailable , the component State shall switch to Off , otherwise to Ready . Signature: AbortCleaning(); Table 24 - AbortCleaning Method AddressSpace Definition Attribute Value BrowseName AbortCleaning References Node Class BrowseName
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  7.5.2.2 PrepareRecipe
  vision system is in state Initialized, it is expected to change into state Ready after successful preparation of the recipe and be able to execute jobs called by a Start ... method with the given ExternalId. If the vision system is already in state Ready when PrepareRecipe is called, it is expected to be in state Ready again after successful preparation
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  7.5.2.3 UnprepareRecipe
  PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory If the vision system is in Ready state when UnprepareRecipe is called, and the recipe to be unprepared is the only recipe ... additional recipes in prepared state, the vision system is expected to remain in state Ready and be able to be called by a Start method with one of the remaining
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  8.2.2.2 Resetting the system
  model of this specification. Either the vision system is idle - reflected by, e.g. the Ready or Initialized state - and the intent of calling the Reset method is to return
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  8.2.2.4 Error handling
  decide that it can immediately take on the next job and return to the Ready state; it may decide that it needs a re-initialization of a recipe and return
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  8.3.1 Introduction
  resume and finish this operation. Failing that, it will try to return to Ready state for the next Start method; failing that, it will return to state Initialized ... made Ready again. Note however, that the method of resolving an error and resuming operation after the Error state is defined by the vision system, not this specification
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  8.3.2.1 Introduction
  automatically transition into Initialized . It is expected that within the states Initialized and Ready , the system can carry out management operations, with recipes and configurations. In order to carry ... RecipeManagementType in chapter 7.5 . At some point, the system will be in Ready state. The simplest way will typically be a single call to AddRecipe and to PrepareRecipe to load
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  8.3.2.2 Single job operation
  event. Note that there is no temporal relationship between the system returning to the Ready state and the completion of image acquisition or processing for the job triggered ... Start method. The system can already have left state SingleExecution to Ready , it can even accept another Start method call and carry out the next job, before the AcquisitionDone event
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  8.3.2.3 Continuous operation
  pieces but constantly acquire and process data. The system may go back to the Ready state, automatically due to internal conditions, or by calling the Abort or Stop methods
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  8.3.2.4 General remarks on Stop and Abort methods
  Executing" states, with the intention that the system transitions to the Ready state. Both can be considered intended interruptions of a running system, in contrast to an error ... method call, the system is expected to end running operation and transition to the Ready state as fast as possible, without regard to acquired or computed data. In response
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  8.3.5.1 Introduction
  ToTransition InitializedToReadyRecipe TransitionType -- ToTransition InitializedToReadyProduct TransitionType -- ToTransition InitializedToReadyAuto TransitionType -- HasSubstate Machine InitializedStepModel VisionStepModel StateMachineType -- Ready HasProperty StateNumber 6 PropertyType -- FromTransition InitializedToReadyRecipe TransitionType -- FromTransition InitializedToReadyProduct TransitionType -- FromTransition InitlializedToReadyAuto TransitionType -- FromTransition SingleExecutionToReadyStop ... management can be carried out through the server, if the optional management objects exist. Ready This state indicates that the vision system is capable of being started to carry
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  8.3.5.2 Initialized State
  more recipes can be prepared by the PrepareRecipe method such that these are ready to be used in processing operations. Results can be pulled from the internal result-store ... state in the VisionStateMachine . This state can be left in the following ways: Into Ready state by a PrepareRecipe method call. Into Preoperational state of the VisionStateMachine by a Reset
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  8.3.5.4 SingleExecution State
  least so far that the internal resources are available to transition into state Ready to accept the next start command. Results can be pulled from the internal result-store ... state. It can do completely different things or nothing at all before returning to Ready state. The point is rather that the difference between SingleExecution state and Ready state lies
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  8.3.5.5 ContinuousExecution State
  state. It can do completely different things or nothing at all before returning to Ready state. The point is rather that the difference between ContinuousExecution state and Ready state lies ... VisionStateMachine . This state can be left in the following ways: Into the Ready state by Stop and Abort method calls, see Section 8.3.2.4 for details. Into the Preoperational state
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  8.3.7.1 StartSingleJob method
  type job in the vision system which will be reflected by transition from the Ready state to the SingleExecution state. Signature StartSingleJob ([in] MeasIdDataType measId,[in] PartIdDataType partId,[in] RecipeIdExternalDataType ... have to instantiate this method with an application-specific parameter structure before entering the Ready state. The server may re-instantiate this method with a different parameter structure after preparing
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  8.3.7.2 StartContinuous method
  type job in the vision system which will be reflected by transition from the Ready state to the ContinuousExecution state. It has the same signature and semantics as method StartSingleJob
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  8.3.7.3 Abort method
  server, the vision system is expected to end running operation and transition to the Ready state as fast as possible, without regard to acquired or computed data. See the general
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  8.3.7.4 Stop method
  server, the vision system is expected to end running operation and transition to state Ready as soon as possible while retaining as much result data as possible. See the general
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  8.3.8.2 JobStartedEventType
  triggered by the server when the state machine transitions from the Ready state to the SingleExecution or ContinuousExecution state. Figure 28 defines the structure. It is formally defined in Table ... fieldbus start signal. The event transports the jobId created upon the transition from state Ready to state SingleExecution or ContinuousExecution . This enables clients to maintain a time-sequential
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  8.3.8.3 ReadyEventType
  triggered by the server when the state machine transitions to the Ready state from one of the "Execution" states, i.e. SingleExecution or ContinuousExecution . Figure 29 defines the structure ... client still has to make sure that the state machine is actually in the Ready state before calling the StartSingleJob or StartContinuous method as the vision system may fall
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  8.3.8.5 AcquisitionDoneEventType
  mandatory. The event provides the JobId created upon the transition from the Ready state to the SingleExecution or ContinuousExecution state. This enables the client to maintain a time-sequential ... which the event was triggered. The JobId is created by the transition from state Ready to state Acquiring
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  11.5 Interaction between Messages, State Machine, and Vision System
  failing method call Let's assume the vision system is in the Ready state with an activated recipe in its memory. A client can call the PrepareRecipe method to load
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  B.1.4 Example for a recipe life cycle
  system carries out its task, going through the Executing state to return to state Ready waiting for further instructions. There are many other possibilities of errors, e.g. trying to prepare
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  B.1.5.1 Types of recipe management
  outside the scope of this specification, starts automatically through states Preoperational and Initialized into Ready . It will immediately react to Start method, ignoring a possible recipe or product argument. Single ... call to the AddRecipe method and immediately prepare this recipe and transition into Ready . It can immediately react to a Start method call, ignoring a possible recipe or product argument
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  B.1.5.2 State handling for recipe management
  preparation of the recipe is not yet finished. A system may stay in state Ready and react correctly to the previously prepared recipe or a different prepared recipe. The server ... vision system. That means that calling the AddRecipe or PrepareRecipe methods in Ready state may result in the system falling back into state Initialized , then returning automatically to state Ready
• OPC-40550-1 – OPC UA for Woodworking Machines - Part 1: Vertical Interface
  7.10 IWwUnitValuesType InterfaceType Definition
  STANDBY state in msec. The AbsoluteReadyTime Variable provides the absolute time of the READY state in msec. The RelativeReadyTime Variable provides the relative time since startup of the READY state