OPC Data Access specification is based on COM, and uses Windows VARIANT type (from COM Automation) for representing data values.

Note: Some OPC servers even use certain VARIANT types that are not officially supported by Microsoft.

Microsoft .NET has a different concept, and all data is represented using an Object type. Conversions between the two are available, but not always fully possible.

In addition, not everything that can be stored in an Object can later be processed by all .NET tools and languages. Microsoft has created so-called Common Language Specification (CLS), which has certain rules and restrictions that, if followed, guarantee cross-language compatibility.  Public QuickOPC.NET components (assemblies) are fully CLS compliant, and that includes the way the data types are converted to and from OPC types.

QuickOPC.NET converts data from COM to .NET according to following table:

Types that are highlighted do not convert from COM to their “natural” .NET counterparts, because the corresponding .NET type is not CLS compliant. Instead, a “wider” type that is CLS compliant is chosen.

Types not listed in the above table at all are not supported.

Strings are internally represented in Unicode wherever possible.

QuickOPC-COM is meant to be used from applications based on COM Automation, and in general, any valid VARIANT can be processed by such application. Some automation tools and programming languages, however, have restrictions on types of data they can process. If your tool does not support the data type that the OPC server is using, without QuickOPC, you would be out of luck.

In order to provide the ability to work with widest range of OPC servers and the data types they use, QuickOPC-COM converts some data types available in OPC. We have made a research into the data types supported by various tools, and QuickOPC-COM uses a subset of VarType types that is guaranteed to work in most tools that are in use today (one of the most restrictive languages appears to be VBScript).

Note that the QuickOPC-COM only converts the data that it passes to your application – either in output arguments of property accessors or methods, or input arguments in event notifications. In the opposite direction, i.e. for data that your application passes to QuickOPC-COM, we use very “relaxed” approach, and accept the widest range of possible data types.

QuickOPC-COM converts data from OPC Data Access according to following table:

Types that are highlighted are converted to a different data type. If a precise match does not exist, a “wider” type is chosen.

Types not listed in the above table at all are not supported.

Strings are internally represented in Unicode wherever possible.