Reading OPCUA Data from a Niagara Supervisor - Bad Quality Issues

So I am working with support on this issue but wanted to see if the forum Gurus had any input on this as well.

We are working on an intergration with a client connecting to their BMS/EPMS data via an OPCUA connection (Ignition as the client) to their Niagara Supervisor OPCUA Server.

I have noticed the data quality since day one of successfully connecting to the Niagara Supervisor, has not been stable.

It will fluctuate from being Good to going to Bad("Bad_OutOfService: The source of the data is not operational.") at times.

I can see the timestamps and data updating on the Good points in designer. But to add to the pecularity of the situation when i use the OPC Quick client in the gateway even on the points that are reading good in designer I will get the Bad("Bad_OutOfService: The source of the data is not operational.") returned back with a value of null.

Here are my connection settings

Here is a snap of designer with good and bad quality data

Here is an example of the OPC Quick client returning a message when trying to read data that is showing good in designer

Also if it helps the data when i originally import into designer is configured as arrays such as a double array or a boolean array and i have to change it to double or boolean.

If anyone has run into similar issues or can provide any guidance that would be appreciated.

Thanks

Steve

This StatusCode comes from the Server. It's not likely to be an Ignition setting you're looking to change. You should probably be working with support from that vendor if you aren't already.

Thanks Kevin, yeah I am working with the clients team who did the config as well on there side. Just wanted to rule out possible config issues on my end.

So to update on this working with the client, they rebooted the supervisor VM and all the data came in good on my end. However alot of the data quit updating after a while and the same issue then presented itself, the data went stale and when we restarted the tags in our ignition instance to force a refresh some of them went back to bad.

They are running a test instance of ignition locally and provided screenshots. From both the OPC Expert interface on the server as well as from their ignitions quick client

This sounds similar to some other support tickets I've seen involving this Niagra Supervisor server. Unfortunately it seems like their OPC UA server implementation is poorly done. I don't know if you'll be able to configuration change your way around that.

Yeah that's what I am afraid of.

Here is the niagara settings if it reveals anything