The OPC landscape is shifting away from DA/HDA and towards UA servers. A significant number of OPC client tools are being created that connect to OPC UA servers, and none of these are compatible with PI without the use of a third party UA wrapper since we only provide DA and HDA servers.103 votes
We have been gathering use cases and information about OPC UA Server functionality as it pertains to OSIsoft products.
There are a number of different requirements to consider, and as such we’re changing the status back to “UNDER REVIEW / RESEARCHING” to more accurately reflect the current status of the work.
At this time, we are not committing to bringing this capability to market.
We will update this thread if the status changes.
The ProgID of the 2015 PI OPC DA Server is OSISoft.OPCDA2.DA.1, while the ProgID of the 2010 PI OPC DA Server is OPC.DA.1.
Existing client tools that pointed to the 2010 PI OPC DA server will need to be reconfigured to point to the new ProgID after the PI OPC DA server is upgraded to 2015.
While this is done because of an architecture change between the 2010 and 2015 servers, potentially necessitating changes to be made to the client application, it is still desirable in some cases to point it to the new server without changing the ProgID.7 votes
In the PI OPC DA/HDA Server 2010 product, there was a “Create Timestamps” functionality (found in the OPCServerConfig Tool). This option had the PI OPC Server create timestamps for OPC clients. I rely on this functionality heavily for an OPC client I use every day. Thus, currently I have to stay on PI OPC DA/HDA Server 2010 since this functionality was removed from the newer version. I would like to have this functionality back.3 votes
We understand this feature is important and we are planning to restore it. We will give you an update on the release schedule when this is finalized.
As a PI user, I want the OPC DA and HDA Servers to honor the Windows identity of any connected OPC client.3 votes
We understand the requirement. It makes sense. We have been looking into it but it turns out to be difficult to do. We used a third-party framework to build the PI OPC DA Server which separates interactions with the OPC client from interactions with the PI Data Archive. It solved a number of problems but unfortunately there is no easy way to have OPC client user credentials flow to the PI Data Archive. We are evaluating our options.
Today PI OPC DA can only expose tags from DA.
To have the option to expose information from AF.
Both the AF structure and attributes.
We are using AF for everything so why not in PI OPC DA.1 vote
- Don't see your idea?