I would like the ability for the PI Interface for OPC DA to retry writing data when it receives a CONNECTEADVISELIMIT error. Certain OPC servers return a CONNECTEADVISELIMIT error when write requests are received in quick succession, and having a setting to retry writing the data would be better than the current method of performing a restart of the service. The issue is exacerbated when the network is unstable.1 vote
We have reviewed this idea, and it’s not something we plan to implement. Even though we are declining this idea for now, it is still open to comments. We do want to hear your opinion. Thank you for the feedback, and please, keep sharing!
It is currently possible to debug one tag, or all tags. Logging timestamp and data for all tags is expensive and make logs harder to read, so one one would like to select an arbitrary number of tags.1 vote
We have reviewed this idea, and it’s not something we plan to implement. We do want to hear your opinion. Thank you for the feedback, and please, keep sharing!
Currently, with OPC event tags, if the connection between the interface and PI Data Archive is broken and signups lost, the event tags will stop polling the OPC server for data. I would like to see a level of redundancy added whereby if the OPC-PI Server connection is broken, the event tags will default over to a predefined scan class, or alternatively be advise tags.0 votes
- Don't see your idea?