Hello.
Note: Both of your posts contained forward slash, no backward slash.

But anyway, I do not think there is anything to be solved on our side. Each HTTP request contains the URL used. We are sending the URL to the server precisely as it is entered into the system (e.g. what you type in Connectivity Explorer, or what you pass in the code through the QuickOPC API). You have verified that "the hard way" by finding the difference between having and not having the slash at the end, and I have verified it today by testing various URLs and observing the communication in the network analyzer.

It is the responsibility of the server to provide URLs that work, and your responsibility to use the right ones when connecting to the server. If the right ones are those with slash at the end, then you need to use them.

I do not know whether you have used the trailing slash with your dOPC Explorer tests. if you did, then it's clear. if you have not, and it still worked, then it is possible that the dOPC Explorer has added the slash by itself, but in such case it is not doing it quite right.

Best regards

Can you please send us the Wireshark capture file of the "failed" communication between Connectivity Explorer and your server (showing the original reported issues), and optionally, a Wireshark capture of a successful communication between dOPC Explorer and your server.

Thank you

Hello.
TCP Connection Test does not send any request *inside* the TCP stream. It simply attempts to opens the socket, and the closes it if opening has succeeded.

I spoke with the developer. The current plan is that we will allow the GetStatus call be disabled also for XML-DA. We will also try to analyze what dOPC Explorer does - the hypothesis being that it does *not* call GetStatus. I will post here when I have more (allow some days).

Best regards

Hello.

If you are referring to "TCP Connection Test" in Connectivity Explorer, then all it does is it tries to establish a TCP connection to the given host/port, and then it closes it. It does not attempt to issue any kind of request to the server. It meant to test for common error cases like "computer not running", "Server not running", "Incorrect port used", or "firewall blocks the port". I assume that the TCP Connection Test actually succeeded, is that correct? If so, any response from the server is irrelevant.

And, I apologize, it looks like that the advise I gave you (for disabling the periodic GetStatus check) was wrong. It only applies to OPC COM. The XML-DA has a different implementation which ignores this parameter. I will need to discuss with the developer what we can do to disable the GetStatus call in XML-DA. There isn't currently a setting for that. And we are not quite sure that, after doing it, things will start working.

Regarding the port choice in URL: This has been tested and should work, I do not think it is the cause.

I will post another reply here after we decide what the next step should be.

Best regards

Please try disabling the periodic GetStatus check in Connectivity Explorer like this:

1. In Connectivity Explorer, perform Tools -> Configure Connectivity.
2. Select "OPC DA Configuration ...". under Members. Select Selector -> Shared Parameters -> Client Parameters -> Server Status Check period in the right pane.
3. Enter -1 in the property grid next to "Server Status Check".
4. Press OK to close the the "Configuration Part Collection Editor" dialog.
5. Restart Connectivity Explorer (you might be asked to do so).
6. Retest.

From the code: Set EasyDAClient.SharedParameters.ClientParameters.ServerStatusCheckPeriod to Timeout.Infinite (-1), it should disable the periodic calls to GetStatus.

Note that this is a static property on EasyDAClient class, it influences connections to all servers, and it needs to be set once, before any actual instances of EasyDAClient are created.

Best regards