I will pass that information on to the customer. Thank you for the clarification.

I do not see anything wrong - this behavior is by design. Here is one of the "OnReadComplete" notifications:




The value returned by the server is a one-dimensional array of VT_UI4. A corresponding .NET type would be an array of UInt32, but not all .NET languages can process it. Our component conforms to CLS (Common Language Specification), which allows the broadest interoperability. For this reason, the array of VT_UI4 is converted to array of Int64 before passing onto the application.

This behavior is documented in the Concepts, see Advanced Topics -> Data Types -> Data Types in OPC "Classic".

Also:
msdn.microsoft.com/en-us/library/12a7a7h3(v=vs.110).aspx#Types

Thought I had- looks like I forgot to hit the Insert button.

Should be attached now.

I do not see the OPC Analyzer trace - are you sure you have attached it?

I am testing the latest version of the client with an Omron OPC Server. There is a tag in the server defined as an Unsigned Double Binary Word.

However the value that i received from your library e.Vtq.Value is an Int64[] of 2 Arrays. Example the OPC set the value as FF FF FF FF, What I received will be
Int64[0] = FF FF FF FF
Int64[1] = 00

This is the same case when I need to write a U4 value back to the OPC. I have to define Int64[].

I have attached an OPC Anlyzer trace showing the problem behavior.

Please let me know if you need any additional information.