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.8 votes
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.4 votes
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.
The ItemID of PI tags retrieved using the PI OPC DA Server has a backslash. In order to maintain consistency with browsing for OPC tags on their client, is there a way to remove or replace the backslash in the ItemID? For example, <servername>.sinusoid instead of <servername>/sinusoid2 votes
- Don't see your idea?