This problem should now be fixed in QuickOPC 5.23 build 1371.1, download from: www.opclabs.com/products/quickopc/downloads/download-2/form/6-quickopc-5-2x-download-form .

Best regards

We will fix it in version 5.23. I will inform you through the forum when it is ready. Estimated: Tomorrow.

No need for further steps on your side. I have prepared a setup close to yours (the OPC server on local and remote machine, but with different items in them). And, I was able to reproduce the problem, with QuickOPC version 5.23.

Further investigation shows that this issue is fixed in the current version (5.31); it exists in 5.30 still.

Easiest way to resolve it would be to switch 5.31. Do you have a reason to stay with 5.23? (such as that you cannot use .NET Framework 4.5+ ?).

I am not sure if I understand your reply correctly. I will try to formulate it myself and ask you for confirmation.

Are you now saying that the problem is not

"... when I try to find the OPCServer located in a remote machine, it shows the OPCServer's that are installed in my own computer, as they were in the remote machine, and cannot see the Server in the remote machine."

as you originally wrote, but instead:

When I select a server from a remote machine that happens to have the same name (identification) as the server on my local machine, I receive nodes coming from the local server, and not from the remote server.


Because these two problems are different, and the document you provided does not show the nodes inside the servers.

Dear Sir,

thank you for the details. I think I can understand now what is happening. It is not, however, precisely what you think. The servers are not from the local machine; they are from the remote machine, but are filtered each time in a different way. Let me explain.

You are comparing the behavior of OpcBrowseDialog component in your project with the behavior of OpcServerDialog component in our demo app. Both these components have a ServerFamilies setting in their inputs. This property allows the developer to specify whether he/she is interested in OPC Data Access servers, OPC Alarms&Events servers, or both. Note that our "Kit Server", which is installed with the product, is both an OPC-DA and an OPC-A&E Server, and thus appears properly as one "server" in each family.

Both these components have the default value of ServerFamilies set to "All".

The EasyOPC.NET Demo Application currently only shows how to work with OPC Data Access servers, and therefore it would be more logical if were only showing the OPC-DA servers. You can call it a bug: the demo application uses the default ("All") for ServerFamilies with its OpcServerDialog, and that's why it shows all servers on every machine, including the "OPC Labs Kit Event Server", which is an OPC-A&E Server that ideally should not be displayed.

In your application, you have probably kept the ServerFamilies of the OpcBrowseDialog at its default ("All"), and therefore you would expect to see the same set of servers (both OPC-DA and OPC-A&E). At first I was surprised as well and though that it was a bug in the OpcBrowseDialog. After some more investigation, however, I have found that this is by design. And, although it is not truly documented, it is quite a logical behavior. Here is what happens:

In the OpcBrowseDialog, there is one more thing that comes to play, and it the type of node you actually want to select. This is given by Mode.SelectElementType, and defaults to DANode, meaning that you want to select a node (item) that resides in an OPC-DA Server. For this reason, the code in the dialog intelligently decides not to show any OPC-A&E Servers, because it would make no sense to browse for OPC-DA items in an OPC-A&E server. The ServerFamilies can get "restricted" by the SelectElementType. In some cases (such as when SelectElementType == Server), the ServerFamilies are left untouched, but in most other cases they get restricted by the final type of node you are selecting. Therefore, in your case, you do not see the "OPC Labs Kit Event Server" locally or on the remote machine, because it is an OPC-A&E Server - but is installed on both, that's practically for sure.

I hope it is clear now.