Table 157 defines the namespace metadata for this specification. The Object is used to provide version information for the namespace and an indication about static Nodes. Static Nodes are identical for all Attributes in all Servers, including the Value Attribute. See OPC 10000-5 for more details.
The information is provided as Object of type NamespaceMetadataType. This Object is a component of the NamespacesObject that is part of the Server Object. The NamespaceMetadataType ObjectType and its Properties are defined in OPC 10000-5.
The version information is also provided as part of the ModelTableEntry in the UANodeSet XML file. The UANodeSet XML schema is defined in OPC 10000-6.
Table 157 – NamespaceMetadata Object for this Specification
|
Attribute |
Value |
|||
|
BrowseName |
||||
|
References |
BrowseName |
DataType |
Value |
|
|
HasProperty |
NamespaceUri |
String |
||
|
HasProperty |
NamespaceVersion |
String |
1.0 |
|
|
HasProperty |
NamespacePublicationDate |
DateTime |
2018-06-18 |
|
|
HasProperty |
IsNamespaceSubset |
Boolean |
False |
|
|
HasProperty |
StaticNodeIdTypes |
IdType[] |
|
|
|
HasProperty |
StaticNumericNodeIdRange |
NumericRange[] |
|
|
|
HasProperty |
StaticStringNodeIdPattern |
String |
|
|
This section defines Conformance Units that are specific to the OPC UA Machine Vision Information model. These Conformance Units are separated into Conformance Units that are Server specific and those that are Client specific.
Table 158 defines the server based Conformance Units.
Table 158 – Definition of Server Conformance Units
|
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. |
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. |
Profiles and facets are named groupings of Conformance Units as defined in OPC 10000-7. This section describes the various facets and profiles on the server and the client side that are provided as part of the OPC UA Machine Vision companion specification information model.
|
Profile |
Related Category |
URI |
|
Basic Vision System Server Facet |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/BasicVisionSystemServerFacet |
|
Inline Vision System Server Facet |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/InlineVisionSystemServerFacet |
|
Automatic Mode Server Facet |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/AutomaticModeServerFacet |
|
Processing Times Server Facet |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/ProcessingTimesMetaDataHandlingServerFacet |
|
File Transfer Server Facet |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/FileTransferServerFacet |
|
Basic Result Handling Server Facet |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/BasicResultHandlingServerFacet |
|
Inline Result Handling Server Facet |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/InlineResultHandlingServerFacet |
|
Full Result Handling Server Facet |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/FullResultHandlingServerFacet |
|
Standard Configuration Handling Server Facet |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/StandardConfigurationHandlingServerFacet |
|
Full Configuration Handling Server Facet |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/FullConfigurationHandlingServerFacet |
|
Standard Recipe Handling Server Facet |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/StandardRecipeHandlingServerFacet |
|
Full Recipe Handling Server Facet |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/FullRecipeHandlingServerFacet |
|
Basic Vision System Server Profile |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/BasicVisionSystemServerProfile |
|
Basic Vision System Server Profile without OPC UA Security |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/BasicVisionSystemServerProfileWithoutOPCUASecurity |
|
Simple Inline Vision System Server Profile |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/SimpleInlineVisionSystemServerProfile |
|
Simple Inline Vision System with File Transfer Server Profile |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/SimpleInlineVisionSystemWithFileTransferServerProfile |
|
Simple Inline Vision System with File Revisioning Server Profile |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/SimpleInlineVisionSystemWithFileRevisioningServerProfile |
|
Inline Vision System with File Transfer Server Profile |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/InlineVisionSystemWithFileTransferServerProfile |
|
Inline Vision System with File Revisioning Server Profile |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/InlineVisionSystemWithFileRevisioningServerProfile |
|
Full Vision System Server Profile |
Machine Vision CS Server |
http://opcfoundation.org/UA-Profile/External/Server/ MachineVision/FullVisionSystemServerProfile |
This facet defines the elements for a very basic machine vision system. It shall implement the mandatory nodes and also some fundamental types and functionality concerning results, configurations and recipes
Table 161 – Definition of Basic Vision System Server Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Vision System |
Basic Vision System |
Mandatory |
|
Vision System |
Basic Result Management |
Mandatory |
|
Vision System |
Basic Configuration Management |
Mandatory |
|
Vision System |
Basic Recipe Management |
Mandatory |
An “inline” machine vision system, as defined in Section 3.1, is used in the manner of a 100% inspection system within a production line (which does not necessarily mean that it is a quality inspection system at all).
This type of use typically takes place under the guidance and supervision of a control system which requires information about the current operating state of the vision system, error conditions and other diagnostic information, and may want to inform the vision system about safety-related events.
Table 162 – Definition of Inline Vision System Server Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Vision System |
Safety State Management |
Optional |
|
Vision System |
System State Information |
Mandatory |
|
Vision System |
Diagnostic Events |
Mandatory |
|
Vision System |
Information Events |
Mandatory |
|
Vision System |
Error Conditions |
Mandatory |
This facet gives a superior control system more detailed control over the behavior of the vision system. This is related to the notion of an inline machine vision system which will typically operate in automatic mode.
Table 163 – Definition of Automatic Mode Server Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Vision State Machine |
Automatic Mode |
Mandatory |
|
Vision State Machine |
Easy Confirmation |
Optional |
|
Vision State Machine |
Error Events |
Mandatory |
|
Vision State Machine |
StepModel Preoperational |
Optional |
|
Vision State Machine |
StepModel Halted |
Optional |
|
Vision State Machine |
StepModel Error |
Optional |
|
Automatic Mode |
Simulation |
Mandatory |
|
Automatic Mode |
StepModel Initialized |
Optional |
|
Automatic Mode |
StepModel Ready |
Optional |
|
Automatic Mode |
StepModel SingleExecution |
Optional |
|
Automatic Mode |
StepModel ContinuousExecution |
Optional |
This facet contains information about the basic start and end time of jobs as well as information about internal timing of jobs.
Table 164 – Definition of Processing Times Server Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Meta Data Handling |
Processing Times |
Mandatory |
|
Meta Data Handling |
Processing Times Extended |
Mandatory |
This facet combines the various TemporaryFileTransfer definitions for the transfer of black-box data to and from the vision system.
Table 165 – Definition of File Transfer Server Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Result Handling |
Result File |
Mandatory |
|
Configuration Handling |
Configuration File |
Mandatory |
|
Recipe Handling |
Recipe File |
Mandatory |
This facet contains the basic definitions for the handling of result content within the ResultDataType (the basic definitions for the identification of results are already contained in the Basic Vision System Facet in Section 13.3.2.2.1).
Table 166 – Definition of Basic Result Handling Server Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Result Handling |
Event Based Content |
Mandatory |
|
Result Handling |
Method Based Content |
Optional |
This facet contains result handling functionality which will typically be expected from an inline vision system (see Section 13.3.2.2.2). Since such a system running within an automated production line will usually handle series of individual, often identifiable parts, and may need to buffer results for later collection, the conformance units Part ID and Result File are part of this facet.
Table 167 – Definition of Inline Result Handling Server Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Machine Vision CS Server Facet |
Basic Result Handling Facet |
Mandatory |
|
Meta Data Handling |
Measurement ID |
Mandatory |
|
Meta Data Handling |
Part ID |
Mandatory |
|
Result Handling |
Method Based Content |
Mandatory |
|
Result Handling |
Result File |
Mandatory |
This facet adds the capability of exposing individual results in the address space inside the Results folder to the Inline Result Handling Facet (see Section 13.3.2.2.7).
Table 168 – Definition of Full Result Handling Server Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Machine Vision CS Server Facet |
Inline Result Handling Facet |
Mandatory |
|
Result Handling |
Result Folder |
Mandatory |
This facet combines the handling of configuration identification with the transfer of black-box configuration content by TemporaryFileTransfer objects.
Table 169 – Definition of Standard Configuration Handling Server Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Meta Data Handling |
Configuration ID External |
Mandatory |
|
Configuration Handling |
Configuration File |
Mandatory |
This facet adds the capability of exposing individual configurations in the address space inside the Configurations folder to the Standard Configuration Handling Facet (see Section 13.3.2.2.9).
Table 170 – Definition of Full Configuration Handling Server Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Machine Vision CS Server Facet |
Standard Configuration Handling Facet |
Mandatory |
|
Meta Data Handling |
Configuration Versioning |
Mandatory |
|
Configuration Handling |
Configuration Folder |
Mandatory |
This facet combines the handling of recipe and product identification with the transfer of black-box recipe content by TemporaryFileTransfer objects.
Table 171 – Definition of Standard Recipe Handling Server Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Meta Data Handling |
Recipe ID External |
Mandatory |
|
Meta Data Handling |
Product ID |
Mandatory |
|
Recipe Handling |
Recipe File |
Mandatory |
This facet adds the capability of exposing individual recipes and products in the address space inside the Recipes and Products folders to the Standard Recipe Handling Facet (see Section13.3.2.2.1113.3.2.2.11).
Table 172 – Definition of Full Recipe Handling Server Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Machine Vision CS Server Facet |
Standard Recipe Handling Facet |
|
|
Meta Data Handling |
Recipe Versioning |
Mandatory |
|
Recipe Handling |
Recipe Folder |
Mandatory |
|
Recipe Handling |
Product Folder |
Mandatory |
This Profile is a FullFeatured Profile intended for basic machine vision systems capable of limited handling of recipe and configuration information, provision of result information and content and executing the standard automatic mode as defined in Section 8.3.
It is built upon the Embedded 2017 UA Server Profile which provides Security conformance units.
Table 173 – Definition of Basic Vision System Server Profile
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Machine Vision CS Server |
Basic Vision System Server Facet |
Mandatory |
|
Machine Vision CS Server |
Basic Result Handling Server Facet |
Mandatory |
|
Vision System |
Diagnostic Events |
Optional |
|
Vision System |
Information Events |
Optional |
|
Vision State Machine |
Automatic Mode |
Mandatory |
|
OPC UA |
Embedded 2017 UA Server Profile |
Mandatory |
This profile is intended as fallback for very limited systems not capable of implementing OPC UA security functionality as required by the Embedded 2017 UA Server Profile used in all other profiles in this specification. We strongly recommend implementing OPC UA security whenever possible.
Table 174 – Definition of Basic Vision System Server Profile without OPC UA Security
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Machine Vision CS Server |
Basic Vision System Server Facet |
Mandatory |
|
Machine Vision CS Server |
Basic Result Handling Server Facet |
Mandatory |
|
Vision System |
Diagnostic Events |
Optional |
|
Vision System |
Information Events |
Optional |
|
Vision State Machine |
Automatic Mode |
Mandatory |
|
OPC UA |
Micro Embedded Device 2017 Server Profile |
Mandatory |
In accordance with the notion of an “inline” machine vision system, used, as defined in Section 3.1 and Section 13.3.2.2.2, in the manner of a 100% inspection system within a production line, this is a FullFeatured Profile, providing the typical functionality required for a simple version of such a system: full automatic mode, diagnostic info required by a control system, basic result handling. It lacks the handling of client-supplied IDs included in the (not-simple) Inline Result Handling Facet in Section 13.3.2.2.7, leaving the part tracing to the superior control system.
Table 175 – Definition of Simple Inline Vision System Server Profile
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Machine Vision CS Server |
Basic Vision System Server Facet |
Mandatory |
|
Machine Vision CS Server |
Inline Vision System Server Facet |
Mandatory |
|
Machine Vision CS Server |
Automatic Mode Server Facet |
Mandatory |
|
Machine Vision CS Server |
Basic Result Handling Server Facet |
Mandatory |
|
Meta Data Handling |
Processing Times |
Mandatory |
|
OPC UA |
Embedded 2017 UA Server Profile |
Mandatory |
This FullFeatured Profile complements the Simple Inline Vision System with the handling of recipe and configuration identification and the black-box transfer of contents by TemporaryFileTransfer objects.
Table 176 – Definition of Simple Inline Vision System with File Transfer Server Profile
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Machine Vision CS Server |
Simple Inline Vision System Server Profile |
Mandatory |
|
Machine Vision CS Server |
Standard Recipe Handling Server Facet |
Mandatory |
|
Machine Vision CS Server |
Standard Configuration Handling Server Facet |
Mandatory |
|
Machine Vision CS Server |
File Transfer Facet |
Mandatory |
|
Meta Data Handling |
Processing Times |
Mandatory |
This FullFeatured Profile complements the Simple Inline Vision System with File Transfer by the capability of managing recipe and configuration versions.
Table 177 – Definition of Simple Inline Vision System with File Revisioning Server Profile
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Machine Vision CS Server |
Simple Inline Vision System with File Transfer Server Profile |
Mandatory |
|
Meta Data Handling |
Recipe Versioning |
Mandatory |
|
Meta Data Handling |
Configuration Versioning |
Mandatory |
This FullFeatured Profile complements the Simple Inline Vision System with File Transfer by the complete ProcessingTimes information and the additional capability of handling result content and client-supplied IDs defined in the Inline Result Handling Facet in Section 13.3.2.2.7, and is thus suitable for sophisticated vision systems in automated production handling part traceability information.
Table 178 – Definition of Inline Vision System with File Transfer Server Profile
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Machine Vision CS Server |
Simple Inline Vision System with File Transfer Server Profile |
Mandatory |
|
Machine Vision CS Server |
Processing Times Server Facet |
Mandatory |
|
Machine Vision CS Server |
Inline Result Handling Server Facet |
Mandatory |
This FullFeatured Profile complements complements the Inline Vision System with File Transfer by the capability of managing recipe and configuration versions and is thus suitable for sophisticated vision systems in automated production handling a multitude of recipes and configurations changing over time.
Table 179 – Definition of Inline Vision System with File Revisioning Server Profile
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Machine Vision CS Server |
Inline Vision System with File Transfer Server Profile |
Mandatory |
|
Meta Data Handling |
Recipe Versioning |
Mandatory |
|
Meta Data Handling |
Recipe Versioning |
|
This FullFeatured Profile comprises the complete functionality of this specification and is thus suitable for the most complex vision systems.
Table 180 – Definition of Full Vision System Server Profile
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Machine Vision CS Server |
Inline Vision System with File Revisioning Server Profile |
Mandatory |
|
Machine Vision CS Server |
Full Result Handling Server Facet |
Mandatory |
|
Machine Vision CS Server |
Full Configuration Handling Server Facet |
Mandatory |
|
Machine Vision CS Server |
Full Recipe Handling Server Facet |
Mandatory |
Table 181 – Definition of Client Facets
This facet contains the basic functionality required for a client to monitor and control a vision system server using DataChange subscriptions and basic methods.
Table 182 – Definition of Basic Control Client Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Vision System |
System State Information Client |
Mandatory |
|
Vision System |
Error Conditions Client |
Optional |
|
Vision State Machine |
State Machine Monitoring |
Mandatory |
|
Vision State Machine |
State Machine Control |
Mandatory |
|
Vision Automatic Mode |
Automatic Mode Selection |
Mandatory |
|
Vision Automatic Mode |
Automatic Mode Monitoring |
Mandatory |
|
Vision Automatic Mode |
Automatic Mode Control |
Mandatory |
This facet contains functionality required for in-depth control of a vision system including StateChanged and Error events and the StepModel methods and events.
Table 183 – Definition of Full Control Client Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Vision System |
System State Information Client |
Mandatory |
|
Vision System |
Error Conditions Client |
Mandatory |
|
Vision State Machine |
State Machine Monitoring |
Mandatory |
|
Vision State Machine |
State Machine Events Monitoring |
Mandatory |
|
Vision State Machine |
State Machine Control |
Mandatory |
|
Vision State Machine |
StepModel Monitoring |
Mandatory |
|
Vision State Machine |
StepModel Events Monitoring |
Mandatory |
|
Vision State Machine |
StepModel Control |
Mandatory |
|
Vision Automatic Mode |
Automatic Mode Selection |
Mandatory |
|
Vision Automatic Mode |
Simulation Mode Control |
Mandatory |
|
Vision Automatic Mode |
Automatic Mode Monitoring |
Mandatory |
|
Vision Automatic Mode |
Automatic Mode Events Monitoring |
Mandatory |
|
Vision Automatic Mode |
Automatic Mode Control |
Mandatory |
This facet contains basic functionality required to monitor and access result information, including the distinction between real and simulated results.
Table 184 – Definition of Basic Result Content Client Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Meta Data Handling |
Client Result IsSimulated |
Mandatory |
|
Result Handling |
Client Event Based Content Basic |
Mandatory |
|
Result Handling |
Client Method Based Content Basic |
Mandatory |
This facet contains the same functionality as the Basic Result Content Client Facet in Section 13.3.3.2.3 and in addition the capability to process the – potentially dynamic – application-specific result content and to access black-box result content using TemporaryFileTransfer objects.
Table 185 – Definition of Simple Result Content Client Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Meta Data Handling |
Client Result IsSimulated |
Mandatory |
|
Result Handling |
Client Event Based Content Basic |
Mandatory |
|
Result Handling |
Client Event Based Content Extended |
Optional |
|
Result Handling |
Client Method Based Content Basic |
Mandatory |
|
Result Handling |
Client Method Based Content Extended |
Optional |
|
Result Handling |
Client Result File |
Mandatory |
This facet contains the same functionality as the Simple Result Content Client Facet in Section 13.3.3.2.4 and in addition the capability to access result nodes exposed by a server in the Results folder.
Table 186 – Definition of Full Result Content Client Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Meta Data Handling |
Client Result IsSimulated |
Mandatory |
|
Result Handling |
Client Event Based Content Basic |
Mandatory |
|
Result Handling |
Client Event Based Content Extended |
Mandatory |
|
Result Handling |
Client Method Based Content Basic |
Mandatory |
|
Result Handling |
Client Method Based Content Extended |
Mandatory |
|
Result Handling |
Client Result File |
Mandatory |
|
Result Handling |
Client Result Folder |
Optional |
This facet contains functionality to process the entire range of meta data a vision system server can provide for a result.
Table 187 – Definition of Result Meta Data Client Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Meta Data Handling |
Client Job ID |
Mandatory |
|
Meta Data Handling |
Client Measurement ID |
Mandatory |
|
Meta Data Handling |
Client Part ID |
Mandatory |
|
Meta Data Handling |
Client Result IsSimulated |
Mandatory |
|
Meta Data Handling |
Client Recipe ID |
Mandatory |
|
Meta Data Handling |
Basic Client Recipe Versioning |
Optional |
|
Meta Data Handling |
Client Product ID |
Mandatory |
|
Meta Data Handling |
Basic Client Configuration Versioning |
Optional |
|
Meta Data Handling |
Client Processing Times |
Mandatory |
|
Meta Data Handling |
Client Processing Times Extended |
Mandatory |
This facet contains the capabilities required to access the full potential range of configuration handling functionality potentially provided by a vision system server.
Table 188 – Definition of Configuration Handling Client Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Meta Data Handling |
Basic Client Configuration Versioning |
Mandatory |
|
Meta Data Handling |
Full Client Configuration Versioning |
Mandatory |
|
Configuration Handling |
Client Configuration Methods |
Mandatory |
|
Configuration Handling |
Client Configuration File |
Mandatory |
|
Configuration Handling |
Client Configuration Folder |
Optional |
This facet contains the capabilities required to access the full potential range of recipe handling functionality potentially provided by a vision system server.
Table 189 – Definition of Recipe Handling Client Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Vision Automatic Mode |
Automatic Mode Events Monitoring |
Mandatory |
|
Meta Data Handling |
Client Recipe ID |
Mandatory |
|
Meta Data Handling |
Basic Client Recipe Versioning |
Mandatory |
|
Meta Data Handling |
Full Client Recipe Versioning |
Mandatory |
|
Meta Data Handling |
Client Product ID |
Mandatory |
|
Recipe Handling |
Client Recipe Methods |
Mandatory |
|
Recipe Handling |
Client Recipe File |
Mandatory |
|
Recipe Handling |
Client Recipe Folder |
Optional |
|
Recipe Handling |
Client Product Folder |
Optional |
This facet contains the capabilities required to access the full potential range of state and condition information functionality potentially provided by a vision system server.
Table 190 – Definition of Vision State Monitoring Client Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Vision System |
System State Information Client |
Mandatory |
|
Vision System |
Diagnostic Events Client |
Mandatory |
|
Vision System |
Information Events Client |
Mandatory |
|
Vision System |
Error Conditions Client |
Mandatory |
|
Vision State Machine |
State Machine Monitoring |
Mandatory |
|
Vision State Machine |
State Machine Events Monitoring |
Mandatory |
|
Vision State Machine |
StepModel Monitoring |
Mandatory |
|
Vision State Machine |
StepModel Events Monitoring |
Mandatory |
|
Vision Automatic Mode |
Safety Information Client |
Mandatory |
|
Vision Automatic Mode |
Easy Confirmation Client |
Optional |
|
Vision Automatic Mode |
Automatic Mode Monitoring |
Mandatory |
|
Vision Automatic Mode |
Automatic Mode Events Monitoring |
Mandatory |
This facet contains the capabilities required to access production-quality relevant information potentially provided by a vision system server, including the distinction between real and simulated results, result contents and the processing times which can be an important indicator for problems in either production or vision system.
Table 191 – Definition of Production Quality Monitoring Client Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Meta Data Handling |
Client Result IsSimulated |
Mandatory |
|
Meta Data Handling |
Client Processing Times |
Mandatory |
|
Meta Data Handling |
Client Processing Times Extended |
Mandatory |
|
Result Handling |
Client Event Based Content Basic |
Mandatory |
|
Result Handling |
Client Event Based Content Extended |
Mandatory |
This facet contains the capabilities required to manage the retrieval and organized backup of all types of data from a vision system server.
Table 192 – Definition of Data Backup Client Facet
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Meta Data Handling |
Client Job ID |
Mandatory |
|
Meta Data Handling |
Client Measurement ID |
Mandatory |
|
Meta Data Handling |
Client Part ID |
Mandatory |
|
Meta Data Handling |
Client Result IsSimulated |
Mandatory |
|
Meta Data Handling |
Client Recipe ID |
Mandatory |
|
Meta Data Handling |
Basic Client Recipe Versioning |
Mandatory |
|
Meta Data Handling |
Full Client Recipe Versioning |
Mandatory |
|
Meta Data Handling |
Client Product ID |
Mandatory |
|
Meta Data Handling |
Basic Client Configuration Versioning |
Mandatory |
|
Meta Data Handling |
Full Client Configuration Versioning |
Mandatory |
|
Meta Data Handling |
Client Processing Times |
Mandatory |
|
Meta Data Handling |
Client Processing Times Extended |
Mandatory |
|
Result Handling |
Client Method Based Content Basic |
Mandatory |
|
Result Handling |
Client Method Based Content Extended |
Mandatory |
|
Result Handling |
Client Result File |
Mandatory |
|
Result Handling |
Client Result Folder |
Mandatory |
|
Configuration Handling |
Client Configuration Methods |
Mandatory |
|
Configuration Handling |
Client Configuration File |
Mandatory |
|
Configuration Handling |
Client Configuration Folder |
Mandatory |
|
Recipe Handling |
Client Recipe Methods |
Mandatory |
|
Recipe Handling |
Client Recipe File |
Mandatory |
|
Recipe Handling |
Client Recipe Folder |
Mandatory |
|
Recipe Handling |
Client Product Folder |
Mandatory |
This FullFeatured Profile defines a client capable of basic monitoring and control of a vision system server and its results.
Table 193 – Definition of Basic Control Client Profile
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Machine Vision CS Client |
Basic Control Client Facet |
Mandatory |
|
Machine Vision CS Client |
Basic Result Content Client Facet |
Mandatory |
|
OPC UA |
Standard UA Client 2017 Profile |
Mandatory |
This FullFeatured Profile defines a client capable of in-depth monitoring and control of a vision system server and full utilization of its results.
Table 194 – Definition of Simple Control Client Profile
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Machine Vision CS Client |
Full Control Client Facet |
Mandatory |
|
Machine Vision CS Client |
Simple Result Content Client Facet |
Mandatory |
|
Machine Vision CS Client |
Vision State Monitoring Client Facet |
Mandatory |
|
OPC UA |
Standard UA Client 2017 Profile |
Mandatory |
This FullFeatured Profile defines a client capable of in-depth monitoring and control of a vision system server and full utilization of its results including all potentially provided result meta data.
Table 195 – Definition of Full Control Client Profile
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Machine Vision CS Client |
Full Control Client Facet |
Mandatory |
|
Machine Vision CS Client |
Full Result Content Client Facet |
Mandatory |
|
Machine Vision CS Client |
Result Meta Data Client Facet |
Mandatory |
|
Machine Vision CS Client |
Vision State Monitoring Client Facet |
Mandatory |
|
OPC UA |
Standard UA Client 2017 Profile |
Mandatory |
This FullFeatured Profile defines a client capable of full utilization of the results of a vision system server including all potentially provided meta data. The intention of such a client is not control of the vision system server but observation and retrieval of its results.
Table 196 – Definition of Result Content Client Profile
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Machine Vision CS Client |
Full Result Content Client Facet |
Mandatory |
|
Machine Vision CS Client |
Result Meta Data Client Facet |
Mandatory |
|
OPC UA |
Standard UA Client 2017 Profile |
Mandatory |
This FullFeatured Profile defines a client capable of monitoring all aspects of the state of a vision system server as well as production-quality relevant data and events. The intention of such a client is not control of the vision system but observation and condition monitoring.
Table 197 – Definition of Monitoring Client Profile
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Machine Vision CS Client |
Vision State Monitoring Client Facet |
Mandatory |
|
Machine Vision CS Client |
Production Quality Monitoring Client Facet |
Mandatory |
|
OPC UA |
Standard UA Client 2017 Profile |
Mandatory |
This FullFeatured Profile defines a client capable of retrieving and providing all meta data and black-box data for vision system server configurations, recipes and results. The intention of such a client is not control of the vision system server, but management of all relevant data in connection with the server.
Table 198 – Definition of Configuration Management Client Profile
|
Group |
Conformance Unit / Profile Title |
M / O |
|
Machine Vision CS Client |
Configuration Handling Client Facet |
Mandatory |
|
Machine Vision CS Client |
Recipe Handling Client Facet |
Mandatory |
|
Machine Vision CS Client |
Data Backup Client Facet |
Mandatory |
|
OPC UA |
Standard UA Client 2017 Profile |
Mandatory |
Namespaces are used by OPC UA to create unique identifiers across different naming authorities. The AttributesNodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId. Unlike NodeIds, the BrowseName cannot be used to unambiguously identify a Node. Different Nodes may have the same BrowseName. They are used to build a browse path between two Nodes or to define a standard Property.
Servers may often choose to use the same namespace for the NodeId and the BrowseName. However, if they want to provide a standard Property, its BrowseName shall have the namespace of the standards body although the namespace of the NodeId reflects something else, for example the EngineeringUnitsProperty. All NodeIds of Nodes not defined in this specification shall not use the standard namespaces.
Table 199 provides a list of mandatory and optional namespaces used in an MachineVision OPC UA Server.
Table 199 – Namespaces used in a MachineVision Server
|
NamespaceURI |
Description |
Use |
|
Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. |
Mandatory |
|
|
Local Server URI |
Namespace for nodes defined in the local server. This may include types and instances used in an AutoID Device represented by the server. This namespace shall have namespace index 1. |
Mandatory |
|
Namespace for NodeIds and BrowseNames defined in this specification. The namespace index is server specific. |
Mandatory |
|
|
Vendor specific types and instances |
A server may provide vendor-specific types like types derived from ObjectTypes defined in this specification or vendor-specific instances of those types in a vendor-specific namespace. |
Optional |
Table 200 provides a list of namespaces and their index used for BrowseNames in this specification. The default namespace of this specification is not listed since all BrowseNames without prefix use this default namespace.
Table 200 – Namespaces used in this specification
|
NamespaceURI |
Namespace Index |
Example |
|
0 |
0:EngineeringUnits |
|
|
2 |
2:VisionSystem |