The OPC DA Server service uses %PIPC%\PI_OPCDA2\Data\SavedNamespace.xml to load the tags and does not update the cache until the service is stopped and started again. If any new tag is added to the PI Server, it is not picked by the OPC DA Server. The service should periodically update its cache from the PI Server after the initial start.13 votes
Title says it all!
It would be awesome to have an AF OPC Server exposing real-time data from AF element hierarchy using any type of attributes data reference.5 votes
We have started work on an OPC UA server for the PI System which will expose asset and time series data in the PI System through the OPC UA specification. We consider this experimental work. We will certainly release it if we are sure we can meet your requirements of features, performance, and scalability. The OPC UA spec is large so I need to know what parts are the most important. Names of OPC UA client applications would be helpful.
This is an identical request: https://feedback.osisoft.com/admin/v3/suggestions/18844639/activity
With PI OPC DA Server 2017, SDK aliasing is no longer supported. It would be nice to be able to not reconfigure the client's ItemIDs and use an alias after migrating a Data Archive.2 votes
As a PI OPC DA Server User, I would like to be able to create groups of tags (items) on the OPC Server, so that when I look for a specific tag in an OPC Client tool I don't have to search through the thousands of other tags that exist on my PI Server. This will make using the PI OPC DA Server more efficient and enjoyable.1 vote
- Don't see your idea?