Category

Title

Description

Server

Vision System – Basic Vision System

The VisionSystemType with all mandatory sub nodes is implemented by the server.

Server

Vision System – Basic Result Management

The Result Management node with all mandatory sub nodes is implemented by the server.

Server

Vision System – Basic Configuration Management

The ConfigurationManagement node with all mandatory sub nodes is implemented by the server.

Server

Vision System – Basic Recipe Management

The RecipeManagement node with all mandatory sub nodes is implemented by the server.

Server

Vision System – Safety State Management

The SafetyStateManagement node is implemented and VisionSafetyEvents are generated by the server.

Server

Vision System – System State Information

The SystemState node is implemented and used by the server to publish its current state.

Server

Vision System – Diagnostic Events

The DiagnosticLevel node is implemented, used by the server to publish the current diagnostic level, and can be written by the Client to set the current diagnostic level. VisionDiagnosticInfoEvents are generated by the server.

Server

Vision System – Information Events

VisionInformationEvents are generated by the server.

Server

Vision System – Error Conditions

VisionWarningConditions, VisionErrorConditions and VisionPersistentErrorConditions are generated by the server.

Server

Vision State Machine – Automatic Mode

The AutomaticModeStateMachine node with all mandatory sub nodes and the SelectModeAutomatic method are implemented by the server.

Server

Vision State Machine – Easy Confirmation

The ConfirmAll method is implemented by the server.

Server

Vision State Machine – Error Events

ErrorEvents and ErrorResolvedEvents are generated by the server.

Server

Vision State Machine – StepModel Preoperational

The PreoperationalStepModel state machine is implemented by the server.

Server

Vision State Machine – StepModel Halted

The HaltedStepModel state machine is implemented by the server.

Server

Vision State Machine – StepModel Error

The ErrorStepModel state machine is implemented by the server.

Server

Automatic Mode – Simulation

The SimulationMode method is implemented by the server. The isSimulated sub nodes of ResultReadyEvents, ResultDataType and ResultType are implemented and reflect the state of the simulation mode during creation of the job generaring this result; likewise, the isSimulated output arguments of methods GetResultComponentsById and GetResultById reflect this state.

Server

Automatic Mode – StepModel Initialized

The InitializedStepModel state machine is implemented by the server.

Server

Automatic Mode – StepModel Ready

The ReadyStepModel state machine is implemented by the server.

Server

Automatic Mode – StepModel SingleExecution

The SingleExecutionStepModel state machine is implemented by the server.

Server

Automatic Mode – StepModel ContinuousExecution

The ContinuousExecutionStepModel state machine is implemented by the server.

Server

Meta Data Handling – Measurement ID

The measId argument of methods StartSingleJob and StartContinuous is associated to the jobs started by calling these methods. Results arising from these jobs include the given MeasId. Therefore the server implements the MeasId sub node of all occurrences of ResultDataType and ResultType as well as within ResultReadyEvents, and returns it in the output argument of methods GetResultComponentsById and GetResultById as well as observing it in the input argument of method GetResultListFiltered. The server may additionally implement the MeasId sub node of VisionDiagnosticInfoEvents , VisionInformationEvents , VisionWarningConditions, VisionErrorConditions and VisionPersistentErrorConditions.

Server

Meta Data Handling – Part ID

The partId argument of methods StartSingleJob and StartContinuous is associated to the jobs started by calling these methods. Results arising from these jobs include the PartId. Therefore the server implements the PartId sub node of all occurrences of the ResultDataType and ResultType as well as within ResultReadyEvents, and returns it in the output argument of methods GetResultComponentsById and GetResultById as well as observing it in the input argument of method GetResultListFiltered method. The server may additionally implement the PartId sub node of VisionDiagnosticInfoEvents , VisionInformationEvents , VisionWarningConditions, VisionErrorConditions and VisionPersistentErrorConditions

Server

Meta Data Handling – Recipe ID External

The externalRecipeId argument of methods StartSingleJob and StartContinuous is associated to the jobs started by calling these methods. All results arising from these jobs include the ExternalRecipeId. Therefore the server implements the ExternalRecipeId sub node of all occurrences of the ResultDataType and ResultType as well as within ResultReadyEvents, and returns it in the output argument of methods GetResultComponentsById and GetResultById as well as observing it in the input argument of method GetResultListFiltered. The server may additionally implement the ExternalRecipeId sub node of VisionDiagnosticInfoEvents , VisionInformationEvents , VisionWarningConditions, VisionErrorConditions and VisionPersistentErrorConditions

Server

Meta Data Handling – Recipe Versioning

To enforce the uniqueness of recipe IDs, the server implements the calculation and comparison of hash values of the binary object representing a recipe. All occurrences of the RecipeIdExternalDataType and RecipeIdInternalDataType implement the sub nodes version, hash and hashAlgorithm.

Server

Meta Data Handling – Product ID

The productId argument of methods StartSingleJob and StartContinuous is associated to the jobs started by calling these methods. All results arising from these jobs include the ProductId. Therefore the server implements the ProductId sub node of all occurrences of the ResultDataType, ResultType and RecipeType as well as within ResultReadyEvents, and returns it in the output argument of methods GetResultComponentsById and GetResultById as well as observing it in the intput argument of method GetResultListFiltered. The server may additionally implement the ProductId sub node of VisionDiagnosticInfoEvents , VisionInformationEvents , VisionWarningConditions, VisionErrorConditions and VisionPersistentErrorConditions

Server

Meta Data Handling – Configuration ID External

The externalConfigurationId argument of methods StartSingleJob and StartContinuous is associated to the jobs started by calling these methods. All results arising from these jobs include the ExternalConfigurationId. Therefore the server implements the ExternalConfigurationId sub node of all occurrences of the ResultDataType and ResultType as well as within ResultReadyEvents, and returns it in the output argument of methods GetResultComponentsById and GetResultById as well as observing it in the intput argument of method GetResultListFiltered. The server may additionally implement the ExternalConfigurationId sub node of VisionDiagnosticInfoEvents , VisionInformationEvents , VisionWarningConditions, VisionErrorConditions and VisionPersistentErrorConditions

Server

Meta Data Handling – Configuration Versioning

To enforce the uniqueness of configuration IDs, the server implements the calculation and comparison of hash values of the binary object representing a configuration. All occurrences of the ConfigurationIdDataType implement the sub nodes version, hash and hashAlgorithm.

Server

Meta Data Handling – Processing Times

The server implements the logging of the start and end times of a job and associates these with the results of this job. Therefore the server implements the processingTimes sub node of all occurrences of the ResultDataType and ResultType as well as within ResultReadyEvents, and returns it in the output argument of methods GetResultComponentsById and GetResultById().

Server

Meta Data Handling – Processing Times Extended

The server implements the logging of the start and end times of a job as well as the determination of the duration of acquisition and processing and associates these with the results of this job. Therefore the server implements the processingTimes sub node of all occurrences of the ResultDataType and ResultType as well as within ResultReadyEvents, and returns it in the output argument of methods GetResultComponentsById and GetResultById.

Server

Result Handling – Event Based Content

The server provides full or partial result content as sub node of ResultReadyEvents and provides a means for the client to interpret the application-specific structure of this node.

Server

Result Handling – Method Based Content

The server provides full or partial result content in the output argument of methods GetResultComponentsById GetResultById and provides a means for the client to interpret the application-specific structure of this argument.

Server

Result Handling – Result File

The server implements the ResultTransfer node to offer additional result content as a downloadable file. It implements the HasTransferableDataOnFile node within all occurrences of ResultDataType and ResultType and provides information about the existence of such content in these nodes and in the output argument of methods GetResultComponentsById and GetResultById.

Server

Result Handling – Result Folder

The server provides meta data and full or partial result content by implementing the Results folder node.

Server

Configuration Handling – Configuration File

The server allows upload and download of configuration objects. Therefore it implements the ConfigurationTransfer node as well as the AddConfiguration and RemoveConfiguration methods. Additionally it signals the availability of a local configuration object by using the hasTransferableDataOnFile node within all occurrences of the ConfigurationDataType.

Server

Configuration Handling – Configuration Folder

The server provides meta data on local configuration objects by implementing the Configurations folder node.

Server

Recipe Handling – Recipe File

The server allows upload and download of recipe objects. Therefore it implements the RecipeTransfer node as well as the AddRecipe and RemoveRecipe methods. Additionally it signals the availability of a local recipe object by using the Handle node within all occurrences of the RecipeType.

Server

Recipe Handling – Recipe Folder

The server provides meta data on local recipe objects by implementing the Recipes folder node. Additionally it returns the node id of the recipe object created in the folder by an AddRecipe method call.

Server

Recipe Handling – Product Folder

The server provides meta data on local product objects by implementing the Products folder node. Additionally it returns the node id of the product object created in the folder by an AddRecipe method call.