Hello.
thank you.

Please rebuild your application with QuickOPC 5.80.293, which is now on our Web site and on www.nuget.org . It has the same fix that has been made to the OpcCmd utility you tested with.

Note that there is no guarantee that this will fully resolve your original problem with writing the Boolean value, but the expectation is that at least the ArgumentNullException should go away, and we will make a step forward.

I cannot fully stress out how helpful it was that you have provided the assistance needed to pinpoint the bug. I really appreciate it. Thank you once again.

Best regards

Hello,
thank you for the trace file (received by email). It was really helpful.

I think I have found a bug in QuickOPC that causes the problem. I am not 100% sure, but the likeliness is very high. And I have prepared a new build of OpcCmd with the bug fix.

Can you please download the new version (same location), and repeat the test? For verification, the OpcCmd version should now be 5.81.0.31 or later.

The idea is that if we can make the browsing and writing work with the OpcCmd test, we will then publish a new build of the QuickOPC, with the final verified fix.

Best regards

Thank you, the browse operation failing should do. Please send the file.

Hello,
here are the instructions for troubleshooting with OpcCmd:

1. Determine what your endpoint URL is. In my example below, I will use "opc.tcp://opcua.demo-this.com:51210/UA/SampleServer", but you need to replace it with your own.
2. Determine what the node Id we want to test is. In my example below, I will use "nsu=http://test.org/UA/Data/;i=10216", but you need to replace it with your own.
3. Download OpcCmd utility from www.opclabs.com/files/downloads/OpcCmd/OpcCmd-Windows.zip .
4. Unpack it into directory of your choice.
5. From command line, go to the directory where OpcCmd is installed, and enter (for interactive mode)6. Verify that the OpcCmd version displayed on the screen is 5.81.0.29 or later.
7. Go through initial setup. Select "Interoperability" when asked for standard initial configuration.
8. Enter command9. Verify that in the command output, 21 or more source switches has been set to Verbose.
10. Enter command:11. Enter command below (replacing the endpoint URL and node ID with your own):12. Verify that the commands reports the error you were getting (ArgumentNullException).
13. Enter command:14. Verify that the command reports a success.
15. Enter command:16. In the directory where OpcCmd.exe is, locate the file TraceOutput-DelimitedList.csv .
17. Post the file here on the forums, or, if you want to keep it confidential (contains things like computer names, endpoint URLs, node Ids etc.), email it to support09 (at) opclabs.com.

Note: There may be additional steps needed if the server enforces a secure connection.

Hello,

while I was working on adding the instrumentation for troubleshooting this issue, i have realized that there might be an easier way. We have an OpcCmd utility which allows you to perform various OPC-related operations from command line, and it is of course built on top of QuickOPC. The nice thing about it in this case is that it already has built-in capabilities for configuring the tracing and capturing the output into a file.

So, the idea is that I will give you an up-to-date build of OpcCmd, with the added instrumentation (tracing) for your issue. And step-by-step instructions on what to do: basically, to invoke the failing Write , for which you just need to server's URL, and the node Id of the "problematic" node. And you will run it, and the tool will generate a file with the diagnostics information. The advantage is that you do not have to re-build your application, and modify it to enable the tracing etc.

Let me know if I can proceed in this way.

Regards

Thank you. Will do that. Please allow some time. I will post here when it is ready.