How to subscribe to an ExtensionObject or nested value array about libua HOT 10 CLOSED

Hello, you can see the implementation in the TestClient project, and the implementation of the subscription for the server in the TestServer project.

from libua.

Hello,

Can you capture subscribing via uaexpert in Wireshark with no security and share that here? I would guess it subscribed to something besides (nodeid, value).

from libua.

Hi Nauful,

sure, I've capture the traffic from UAExpert and the LibUA client for the mentioned node, which is now ns=4;i=2801; after an structure update on the OPC server. The according dump is named after that at the end (..._libua / ..._uaexpert).

What I've seen so far, the requests are nearly the same for the specific node, but in the LibUA client, the "NotifyDataChangeNotifications" method is not fired on an publish response for that node. Maybe there is some filter or switch case missing in LibUA?

opc_nodeid_subscribe_libua.zip
opc_nodeid_subscribe_uaexpert.zip

from libua.

Hmm, it looks like that should have worked. Please check this line and step through to see if it reaches the call to NotifyDataChangeNotifications:

If decoding succeeds, it should call NotifyDataChangeNotifications. You override that in your client, for example:

from libua.

Thanks for the hint. I've stepped through the code and found the failing part in the Client.cs on line 4299, where the call succeeded &= recvHandler.RecvBuf.Decode(out notifications[j]); returns 'false'.
Digging deeper in the stack, it tries to decode the notification as variant in MemoryBufferExtensions.cs on line 1194. Finally in the VariantDecode function in MemoryBuffer.cs line 635, it fails on line 644, where if ((mask & 0x80) != 0) is always 0.

Maybe the ExtensionObject has a different mask and need to be handle separately in the MemoryBufferExtensions.cs?

from libua.

Thanks, that gives me a hint. Let me investigate. I don't think I've seen an extension object in a variant before so this is a new case.

from libua.

Fixed, let me know if the latest version works.

from libua.

Looks good, great work 👍 . The only thing that seems to be missing is the source timestamp, the server timestamp is correct in the notification. Maybe another bug?

from libua.

There's no source timestamp in the data:

uaexpert requested both timestamps:

In your CreateMonitoredItemsRequest, request both source and server timestamps:

from libua.

Okay that was my fault, sorry for that 👍 .

Thanks again for the fast response and quick fix, everything is working now like expected :-)

from libua.