Great. I will also think about whether we can be more "forgiving" on our side (the current behavior is by design - we strive to provide consistent & valid data out of methods). Let me know if you need anything in this respect.

Best regards

Hello, thank you for the captures. I had some difficulties analyzing them, because neither in your UaExpert nor in your QuickOPC capture you had browsed into the "CM100 Data" node which we had used before and for which I knew which nodes get returned to you.

But anyway, I think I found the reason. The server is not conformant with OPC UA specification in that it returns invalid Namespace indices in some of its browse names. QuickOPC resolves the namespace indices to namespace URIs, and this fails when the index is invalid.

Example. Data returned in packet #87 in your UaExpert capture:



The namespace index in the BrowseName (which is UA QualifiedName) is 14. There must be a namespace with index 14 in the server's namespace table. But there isn't - the server only has 4 namespaces, as can be seen from the response in packet #60 from the same capture:



The server vendor needs to fix this.

Best regards

Thank you.

Please have a look here: kb.opclabs.com/Collecting_information_for_troubleshooting . The page has links to articles which detail how to use Wireshark for OPC UA.

From "Assets to collect", I just need #1 (the Wireshark captures). But please *also* make one with UaExpert, so that I can compare them.

Best regards

Hello.

If I understand your reply correctly, the issue can be seen in the "Address Space Browser" window as well. In that case, we do not need to look further into your code at this point.

The cause, however, remains a mystery to me. I will need to analyze the communication between the client and the server (ideally in both cases - with QuickOPC, and also with UaExpert). Here are the options:

1. If the server is PC-based and a demo version of it can be obtained, let me know which server/how, and I will test it here.
2. If your server's endpoint (one port...) can be made publicly available on the Internet, you can expose it to me and I would test from here (can be firewalled so that only allows access to specified source IP).
3. I can send you instructions on how to use Wireshark to capture the communication, and you would then send me the capture files for analysis.
4. If you can disclose the server vendor/model: Next week I will spend on so-called OPC Interoperability Workshop, where many OPC vendors come together and test their clients/servers together. There is a chance that the server will be represented/available there, and I can make the necessary test&analysis there.

Let me know what works for you.

Best regards

Hello.

This is not what I have asked for. Please re-read the instructions. The missing part is that you need to invoke the "To Address Space Browser" command.

Regards