13 Profiles and Namespaces ToC Previous Next

13.2 Conformance Units ToC Previous Next

13.2.3 Client ToC Previous Next

Table x defines the Client based Conformance Units.

Table 159 – Definition of Client Conformance Units

Category Title Description
Client Vision System – System State Information Client The Client is capable of monitoring the SystemState node if existing in the server including optional items.
Client Vision System – Diagnostic Events Client The Client is capable of reading and writing the DiagnosticLevel node if existing in the server and to monitor VisionDiagnosticInfoEvents generated by the server, including all possibly existing data elements of the events.
Client Vision System – Information Events Client The Client is capable of monitoring VisionInformationEvents generated by the server, including all possibly existing data elements of the events.
Client Vision System – Error Conditions Client The Client is capable of monitoring, acknowledging and confirming VisionWarningConditions, VisionErrorConditions and VisionPersistentErrorConditions generated by the server, including all possibly existing data elements of the conditions.
Client Vision State Machine – State Machine Monitoring The Client is capable of monitoring state and transitions of the mandatory VisionStateMachine.
Client Vision State Machine – State Machine Events Monitoring The Client is capable of monitoring the events generated by the mandatory VisionStateMachine.
Client Vision State Machine – State Machine Control The Client is capable of controlling the mandatory VisionStateMachine by calling its methods.
Client Vision State Machine – StepModel Monitoring The Client is capable of detecting the existence of StepModel state machines inside any state of any state machine in the server and monitor their states and transitions.
Client Vision State Machine – StepModel Events Monitoring The Client is capable of monitoring events generated by an active StepModel state machine in the server.
Client Vision State Machine – StepModel Control The Client is capable of controlling any StepModel state machine existing in the server by calling its Sync method.
Client Vision Automatic Mode – Automatic Mode Selection The Client is capable of calling the SelectAutomaticMode method and monitor the success of entering the VisionAutomaticModeStateMachine.
Client Vision Automatic Mode – Safety Information Client The Client is capable of monitoring VisionSafetyEvents and the SafetyStateManagement node and is capable of reporting safety information by using the ReportSafetyState method.
Client Vision Automatic Mode – Easy Confirmation Client The Client can call the ConfirmAll method if implemented by the server.
Client Vision Automatic Mode – Simulation Mode Control The Client is capable of calling the SimulationMode method. If the client processes vision system results, it takes appropriate action based on the value of the isSimulated flag included with the results.
Client Vision Automatic Mode– Automatic Mode Monitoring The Client is capable of monitoring state and transitions of the AutomaticModeStateMachine
Client Vision Automatic Mode – Automatic Mode Events Monitoring The Client is capable of monitoring the events generated by the AutomaticModeStateMachine.
Client Vision Automatic Mode – Automatic Mode Control The Client is capable of controlling the AutomaticModeStateMachine by calling its methods.
Client Meta Data Handling – Client Job ID The Client is capable of reading a jobId from methods providing one and to pass it to methods accepting one, provided the client implements the call of this method at all (as stated by other Conformance Units). The client is also capable of processing jobId information contained in vision system results.
Client Meta Data Handling – Client Measurement ID The Client is capable of providing a measId to all methods accepting one, provided the client implements the call of this method at all (as stated by other Conformance Units). The client is also capable of processing measId information contained in vision system results and events and returned by methods.
Client Meta Data Handling – Client Part ID The Client is capable of providing a partId to all methods accepting one, provided the client implements the call of this method at all (as stated by other Conformance Units). The client is also capable of processing partId information contained in vision system results and events and returned by methods.
Client Meta Data Handling – Result IsSimulated The client is capable of monitoring if the isSimulated flag included within ResultReadyEvents.
Client Meta Data Handling – Client Recipe ID The Client is capable of providing externalRecipeId or internalRecipeId arguments to methods requiring one (provided the client implements the call to that method at all, as stated by other Conformance Units) and of processing externalRecipeId and internalRecipeId information contained in vision system results and events and returned by methods.
Client Meta Data Handling – Basic Client Recipe Versioning The Client is capable of comparing version and hash information contained in externalRecipeId and internalRecipeId structures.
Client Meta Data Handling – Full Client Recipe Versioning The Client is capable of computing hash information on recipes based on the hashAlgorithm information optionally contained in externalRecipeId and internalRecipeId structures, provide the server with such information and process such information when returned from the server.
Client Meta Data Handling – Client Product ID The Client is capable of providing a productId to all methods accepting one, provided the client implements the call of this method at all (as stated by other Conformance Units). The client is also capable of processing productId information contained in vision system results and events and returned by methods.
Client Meta Data Handling – Basic Client Configuration Versioning The Client is capable of providing externalConfigurationId or internalConfigurationId arguments to methods requiring one (provided the client implements the call to that method at all, as stated by other Conformance Units) and of processing externalConfigurationId and internalConfigurationId information contained in vision system results and events and returned by methods.
Client Meta Data Handling –Full Client Configuration Versioning The Client is capable of comparing version information contained in externalConfigurationId and internalConfigurationId structures.
Client Meta Data Handling – Client Processing Times The Client is capable of processing basic ProcessingTimes information contained in vision systems results and events and returned by methods (provided the client implements calls to these methods at all, as stated by other Conformance Units).
Client Meta Data Handling – Client Processing Times Extended The Client is capable of processing extended ProcessingTimes information contained in vision systems results and events and returned by methods (provided the client implements calls to these methods at all, as stated by other Conformance Units).
Client Result Handling – Client Event Based Content Basic The Client is capable of monitoring ResultReady events generated by the server and extracting all provided meta data from the event.
Client Result Handling – Client Event Based Content Extended The Client is capable of monitoring ResultReady events generated by the server and extracting all provided meta data from the event, as well as extracting application-specific result content.
Client Result Handling – Client Method Based Content Basic The Client is capable of calling method GetResultListFiltered, GetResultById, GetResultComponentsById, ReleaseResultHandle. The client is further capable of processing the meta data for the returned results.
Client Result Handling – Client Method Based Content Extended The Client is capable of calling method GetResultListFiltered, GetResultById, GetResultComponentsById, ReleaseResultHandle. The client is further capable of processing the meta data for the returned results as well as extracting application-specific result content.
Client Result Handling – Client Result File The client is capable of using the ResultTransfer methods to obtain opaque result content based on resultId and hasTransferableDataOnFile information obtained from ResultReady events or method calls.
Client Result Handling – Client Result Folder The client is capable of obtaining result meta data from the Results folder node, if implemented by the server.
Client Configuration Handling – Client Configuration Methods The client is capable of calling the methods of the ConfigurationManagementType node to manage configuration information on the server.
Client Configuration Handling – Client Configuration File The client is capable of using the ConfigurationTransfer methods to upload and download opaque configuration content based on configurationId and hasTransferableDataOnFile information obtained from events or method calls.
Client Configuration Handling – Client Configuration Folder The client is capable of obtaining configuration meta data from the Configurations folder node if implemented by the server.
Client Recipe Handling – Client Recipe Methods The client is capable of calling the methods of the RecipeManagementType node to manage recipe and product information on the server.
Client Recipe Handling – Client Recipe File The client is capable of using the RecipeTransfer methods to upload and download opaque recipe content based on recipeId and hasTransferableDataOnFile information obtained from events or method calls.
Client Recipe Handling – Client Recipe Folder The client is capable of obtaining recipe meta data from the Recipes folder node if implemented by the server.
Client Recipe Handling – Client Product Folder The client is capable of obtaining product meta data from the Products folder node if implemented by the server.

Previous Next