Hello.

I can basically confirm the first part ("QuickOPC sets up a test OPC UA server, connects to it and provides the data to VEE pro using the COM interface."). The only slight correction there is that our sample OPC UA server runs on the Internet and the QuickOPC calls made from VEE Pro connect to it (we do not set the OPC UA server locally, although it would be perfectly possible). You can see this from the endpoint URL in the program. In a production scenario, the OPC UA server will most likely be somewhere on the local network.

I do not quite understand the question in the second part, maybe you need to reword it or elaborate a little. I would expect that for what you want to do, the architecture would be the same as in my "proof of concept".

Best regards

Hello.

I have successfully created a "proof of concept", reading a value from an OPC UA server into Keysight VEE Pro. In the end, I failed to do so using the QuickOPC .NET interface, which I think would be generally better, but I could make it work over the QuickOPC COM interface. The distinction is mainly in how the code looks internally, but the end result is the same.

Here are the steps:
1. I used Windows 10 21H1.
2. Install Keysight VEE Pro 9.33.
3. Install QuickOPC 2023.1; make sure "COM development" is included when the Setup wizard runs.
4. In VEE Pro, create a new project.
5. From the VEE Pro menu, select Device -> ActiveX Automation References, and add a reference to "OPC Labs EasyOPC-UA Library".
6. Create your program like this:



(the block that does the reading can be created using Device -> Function & Object Browser; then select ActiveX Objects -> OpcLabs_EasyOpcUA -> EasyUAClient -> ReadValue)
7. Run it and enjoy.


This, of course, is the simplest possible program. We have, however, many examples in several COM-based tools/languages available. VEE Pro isn't really doing different things, it's just expressing them graphically instead in textual code, so I believe that in principle the whole QuickOPC feature set existing in COM interface is available to VEE Pro in this way.

I can help with specific tasks you are after.


Best regards

Hello.
no, we do not have new information on this subject. I kind of hoped that the original poster (@veecan) would show here some of his results, but that did not happen.

I briefly checked Vee Pro capabilities/user's manual, and in principle it appears to support the usage of .NET libraries (such as QuickOPC) quite well. However, Vee Pro officially runs .NEt Framework 3.5; and we need .NET Framework 4.7.2 for current QuickOPC. There are some unofficial tricks to make it work on the Web.

Please let me know some summary of what you want to achieve. For example, do you intend to use OPC "Classic" (COM/DCOM based), or the newer OPC UA (Unified Architecture)? Do you need reads, writes, subscriptions, - which of those? Etc.

I may then spend some time trying to make it work with the trial version of Vee Pro.

And, please confirm that you have an OPC Server - and that the Vee Pro part would be an OPC Client - and not vice versa. Because, currently, QuickOPC is for OPC Client development, not for OPC Server development.

Best regards

OPC specifications do not give any meaning to the order of the branches/leaves. They do not tell the servers in which order to provide the nodes, and they do not tell the clients to keep the order in which the nodes are coming.

It is assumed that when some order is needed, the client will sort the nodes (e.g. alphabetically). That can easily be done in most programming languages.

See also: stackoverflow.com/questions/26341994/sorting-items-in-opc-server

Best regards