How can we get GoodXXX status codes from the method on a client

[natali.oliinyk]

Hi :)

I'm using Softing library to create opc ua server and client and noticed one peculiarity, whatever GoodXXX code the server returns as status code of the method, client will always get just Good.

For example method returns StatusCodes.GoodCompletesAsynchronously (0x002E0000), but client receives just StatusCodes.Good (0x00000000)

Maybe someone can explain it to me and if possible how can we workaround this behavior?

[Support Team]

Hi,

the best way to analyze this behavior is the Wireshark. Unfortunaltely with most UA applications only possible on insecure, non-encrypted connections. However, this may give you an insight, if and which status code was really send "over the wire" to the client. If you can see the correct status code in the Wireshark capture, most probably the client side SDK is mapping it to a more "general" status code for simplification. Just an educated guess, the Softing Toolkit may have decided to map the very detailed and precise status codes as of OPC UA, to the very simple (good, uncertain, bad) codes known from old classic OPC DA.

When doing same test with latest Unified Automation SDK, please note that you can also analyze "encrypted" traffic with the Wireshark.