OPC UA Connection configuration

Unfortunately, your screenshots are not visible for me, and may be corrupt.

What kind of UINT are you trying to read? 16, 32, or 64 bit?

A drawback of Citect is that it does not support 64-bit variables. Please submit a post on the Ideas Forum if you think this should be added to Citect (or upvote this similar subject: https://citectscada.ideas.aha.io/ideas/SCADA-I-17).

If you are trying to read a 16-bit value, make sure to use UINT as data type in Citect.
If you are trying to read a 32-bit value, make sure to use ULONG as data type in Citect.

Hi Patrick,

Sorry I forgot to specify it, this is a uint16. 

Here is the declaration of the variables in the Citect project (hoping you can see the attached pictures) :

The result :

Another OPC UA client on the same station:

Hi Pascal,

That's strange. Configuration looks to be all-right.
Have you installed the newest driver already? v3.04.06.000 is currently the latest version available from the Support site.

Do you get any errors in the kernel and/or syslog file of the I/O server? Or any errors on the OPC server side that may hint at an issue?

Also, do you see bad quality or any errors if you try to read the tag using TagDebugForm() instead of TagDebug() ?

If nothing is showing out of place, then perhaps Support may be able to assist you.

Regards,
Patrick

Hi Patrick,

Here is the result of reading the tag with TagDebugForm ()

Looks like there's no error, just a value of 0 (zero).

Interestingly, the tagdebug says it's an INT... I'd hazard a guess you are looking at a data type mismatch. Something I've seen on other OPC servers is that depending on optional tag suffixes, it can manually retrieve it as another data type. It could be that your OPC client software is just smarter than Citect so can interpret it correctly. When you browse with the client, are there any other hidden tags? Look for something like "*.UInt16".
Have you also tried just polling it as an INT and seeing if you get the right value?

Hi Patrick,

I tried reading the variable with declarations of different Citect data types:

Reading is ok for Long, Ulong and String type, strange then that the type declared on the DeltaV system side is 16 bit Integer

So I will change the Citect data types to ULong or Long instead of Uint and Int

Nice find, and looks like a good solution to me.
Perhaps you can report the issue to Support as it might be a bug in the OPCUA driver.

I will report this problem to support. Thank you for your support !