8 ObjectTypes for Vision System State Handling ToC Previous Next

8.3 VisionAutomaticModeStateMachineType ToC Previous Next

8.3.5 VisionAutomaticModeStateMachineType States ToC Previous Next

8.3.5.1 Introduction ToC

Table 97 specifies the VisionAutomaticStateMachine’s state Objects. These state Objects are instances of the StateType defined in OPC 10000-5 – Annex B. Each state is assigned a unique StateNumber value.

See Table 98 for a brief description of the states. The states will be detailed in the following subsections.

Table 97 – VisionAutomaticModeStateMachineType States

Browse
Name
References Target BrowseName Value Target Type
Definition
Notes
Initialized HasProperty StateNumber 5 PropertyType --
  FromTransition ReadyToInitializedRecipe   TransitionType --
  FromTransition ReadyToInitializedProduct   TransitionType --
  FromTransition ReadyToInitialzedAuto   TransitionType --
  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   TransitionType --
  FromTransition SingleExecutionToReadyAbort   TransitionType --
  FromTransition SingleExecutionToReadyAuto   TransitionType --
  FromTransition ContinuousExecutionToReadyStop   TransitionType --
  FromTransition ContinousExecutionToReadyAbort   TransitionType --
  FromTransition ContinousExecutionToReadyAuto   TransitionType --
  ToTransition ReadyToInitializedRecipe   TransitionType --
  ToTransition ReadyToInitializedProduct   TransitionType --
  ToTransition ReadyToInitializedAuto   TransitionType --
  ToTransition ReadyToSingleExecution   TransitionType --
  ToTransition ReadyToSingleExecutionAuto   TransitionType --
  ToTransition ReadyToContinuousExecution   TransitionType --
  ToTransition ReadyToContinuousExecutionAuto   TransitionType --
  HasSubstate Machine ReadyStepModel   VisionStepModel StateMachineType --
Single Execution HasProperty StateNumber 7 PropertyType --
  FromTransition ReadyToSingleExecution   TransitionType --
  FromTransition ReadyToSingleExecutionAuto   TransitionType --
  ToTransition SingleExecutionToReadyStop   TransitionType --
  ToTransition SingleExecutionToReadyAbort   TransitionType --
  ToTransition SingleExecutionToReadyAuto   TransitionType --
  HasSubstate Machine SingleExecutionStepModel   VisionStepModel StateMachineType --
Continuous Execution HasProperty StateNumber 8 PropertyType --
  FromTransition ReadyToContinuousExecution   TransitionType --
  FromTransition ReadyToContinuousExecutionAuto   TransitionType --
  ToTransition ContinuousExecutionToReadyStop   TransitionType --
  ToTransition ContinousExecutionToReadyAbort   TransitionType --
  ToTransition ContinousExecutionToReadyAuto   TransitionType --
  HasSubstate Machine ContinuousExecutionStepModel   VisionStepModel StateMachineType --

Table 98 – VisionAutomaticModeStateMachineType State Descriptions

StateName Description
Initialized This state indicated that the vision system is sufficiently initialized so that management operations like configuration and recipe 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 out jobs, e.g. through Start methods called on the server.
SingleExecution This state indicates that the vision system will acquire the data required for carrying out a single inspection or measuring job and will finish whatever operations are necessary to return to the Ready state to accept the next job.
ContinuousExecution This state indicates that the vision system continually acquires and processes data, until it is stopped by internal or external reasons, e.g. calling the Stop or Abort methods on the server.

8.3.5.2 Initialized State ToC

In this state, the system is characterized by the following properties:

  • The system is able to perform management and operations.
  • Configurations can be managed by methods detailed in Section 7.2.
  • Recipes can be managed by methods detailed in Sections 7.5, 7.6, 7.7.
  • One or 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 by the methods detailed in Section 7.10.
  • The system can be put into simulation mode (see Section 8.3.7.5). This state will be the first state entered in the VisionAutomaticModeStateMachine when the superior VisionStateMachine enters the Operational state either by an automatic transition from Preoperational or by a SelectModeAutomatic method call.

If an error is dectected which suspends normal operation, the system will change to the Error 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 method call.
  • Into Halted state of the VisionStateMachine by a Halt method call.
  • Into Error state of the VisionStateMachine by an internal error. All method-triggered transitions can also occur automatically upon an internal decision of the system.

This state can be a composite state with an optional VisionStepModelStateMachineType SubStateMachine.

8.3.5.3 Ready State ToC

In this state, the system is characterized by the following properties:

  • The vision system has prepared one or more recipes such that they can be used for processing immediately upon a StartSingleJob or StartContinuous method call (unless it is a system without any recipe management).
  • The vision system is ready to accept either a StartSingleJob or a StartContinuous method to begin image processing operation.
  • Recipes can be added and retrieved by methods detailed in Sections 7.5, 7.6, 7.7.
  • Which recipes are ready for use can be changed by calling the PrepareRecipe method depending on the recipe handling capabilities of the system.
  • Results can be pulled from the internal result-store by the methods detailed in Section 7.5.
  • The vision system can be put into simulation mode (see Section 8.3.7.5). Depending on the recipe handling capabilities of the vision system, calling an AddRecipe or PrepareRecipe method in this state may cause the system to fall back into Initialized state, temporarily preventing it from accepting Start methods.

If an error is dectected which suspends normal operation, the system will transition to Error state in the VisionStateMachine.

This state can be left in the following ways:

  • Into the SingleExecution state by a StartSingleJob method call.
  • Into the ContinuousExecution state by a StartContinuous method call.
  • Into the Initialized state by an UnprepareRecipe method call.
  • Into the Preoperational state of the VisionStateMachine by a Reset method call.
  • Into the Halted state of the VisionStateMachine by a Halt method call.
  • Into the Error state of the VisionStateMachine by an internal error. All method-triggered transitions can also occur automatically upon an internal decision of the system.

This state can be a composite state with an optional VisionStepModelStateMachineType SubStateMachine.

8.3.5.4 SingleExecution State ToC

In this state, the system is characterized by the following properties:

  • The vision system has received a command to begin the execution of an individual job (measuring, inspection, identifying, …), e.g. by a call to the StartSingleJob method on the server.
  • The vision system collects sensor data (i.e. acquiring single or multiple images, possibly awaiting triggers, often in hardware).
  • If data acquisition is a “multi-stage-process” (interaction with other devices) this may be modelled with a VisionStepModelType SubStateMachine (all states allow for this, but this is the most typical application, therefore we emphasize it here).
  • The vision system may indicate to the client by an AcquisitionDone event that acquisition has been finished, e.g. as a signal that the part can be removed from the camera’s field of view, either by moving the part or he camera.
  • The vision system carries out the processing of the acquired data at 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 by the methods detailed in Section 7.5 (depending on the capabilities of the system). Note that the above description illustrates a typical behavior. The vision system is, however, in no way obliged to perform any particular operation – like image acquisition or processing – in this 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 in the availability of the required resources for starting a job.

If an error is detected which suspends normal operation, the system will change to state Error in the VisionStateMachine.

This state can be left in the following ways:

  • into the Ready state by an automatic transition when the required resources are available. The system shall trigger a Ready event in this case. Note that this is in no way related to the vision system completing an image acquisition or evaluation and/or producing a result.
  • Into the Ready state by the methods Stop and Abort, see Section 8.3.2.4 for details.
  • Into the Preoperational state of the VisionStateMachine by a Reset method call.
  • Into the Halted state of the VisionStateMachine by a Halt method call.
  • Into the Error state of the VisionStateMachine by an internal error. All method-triggered transitions can also occur automatically upon an internal decision of the system.

This state can be a composite state with an optional VisionStepModelStateMachineType SubStateMachine.

8.3.5.5 ContinuousExecution State ToC

In this state, the system is characterized by the following properties:

  • The vision system has received a StartContinuous command to begin the execution of a continuous job
  • The vision system collects sensor data (i.e. acquiring single or multiple images, possibly awaiting triggers, often in hardware) and processes this in a continuously ongoing fashion.
  • Results can be pulled from the internal result-store by the methods detailed in Section 7.5 (depending on the capabilities of the system). Note that the above description illustrates a typical behavior. The vision system is, however, in no way obliged to perform any particular operation – like image acquisition or processing – in this 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 in the availability of the required resources for starting a job.

If an error is detected which suspends normal operation, the system will change to the Error state in the 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 of the VisionStateMachineType by a Reset method call.
  • Into the Halted state of the VisionStateMachineType by a Halt method call.
  • Into the Error state of the VisionStateMachineType by an internal error. All method-triggered transitions can also occur automatically upon an internal decision of the system.

This state can be a composite state with an optional VisionStepModelStateMachineType SubStateMachine.

Previous Next