OPC UA Connector stops reading data if status is BAD

Hi.

I have an OPC UA Connector running. The local OPC UA server is synchronized with a remote OPC UA server. Sometimes the remote server is blocking read access to the local server, because they do not want us to read the data during specific time periods. However, when the connection between the two OPC UA servers are restored, the PI connector does not resume reading the data.

 

During the outage, when using an OPC UA client to read the object, the value says "Bad_NoData". But in PI the last good value is just frozen. And when the data comes back into the local OPC UA server, the PI data is still frozen. There are no error messages in the PI system, and I have to reboot the whole system to get the PI system to store new data.

 

Any suggestions? PI connector version 2.0.

Parents
  • To answer my own question, we found a workaround. Whenever the signal quality goes to bad, it seems like the PI connector stops subscribing to the tag. And it does not recover without rebooting. What we did is configure the OPC UA server to override quality to "good" at all times, since PI doesn't use this for anything useful anyway. This seems to have solved the issue.

Reply
  • To answer my own question, we found a workaround. Whenever the signal quality goes to bad, it seems like the PI connector stops subscribing to the tag. And it does not recover without rebooting. What we did is configure the OPC UA server to override quality to "good" at all times, since PI doesn't use this for anything useful anyway. This seems to have solved the issue.

Children
No Data