AVEVA™ PI System™ Feedback Portal

Welcome to our new feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Add a new idea Subscribe
Status Declined
Product AVEVA™ PI System Access (PSA)
Categories PI OPC DA & HDA Servers
Created by davidrosinski
Created on Aug 23, 2022

RELATED IDEAS

Add OPCclient to all PI OPC DA server install kit

In verifying the OPC DA server DCOM setting you need to use the OPCclient to check PI tags values. In the OPC DA server 2017 you need the latest version of OPCclient (was not in OCP client tools) to allow to connect correctly to the OPC DA server 2017. If the OPCclient was in the OPC DA server 2017 I would not had needed to go down load OPC Tools kit.
  • ADMIN RESPONSE
    Aug 23, 2022
    Thank you for your input. While we realize that requiring two downloads can be bothersome, we have made the decision to keep these downloads separate as it allows for faster release times. Also, for this use case, it is important to install the Client on a separate node in order to fully test DCOM.
  • Attach files
  • Kenneth Reiss
    Reply
    |     Aug 23, 2022
    I will have to be the devil's advocate and disagree with this one. The OSIsoft setup kits are already extremely bloated and downloading multiple installation packs on a slow connection is painful. The the good old days, each component was downloaded separately (prereqs, SDK, etc.).
  • davidrosinski
    Reply
    |     Aug 23, 2022
    In response to Kenneth Reiss, "I will have to be the devil's advocate a..." Kenneth I did the old way and followed the OPC DA server 2017, which was to download OPC Tool. When I did that the OPC Tool could not work with the new OPC DA 2017 version. So I had to call OSI to find out that I needed to use OPCclient from OPCint installation kit. That is why I believe that the OPCClient that work with OPC DA 2017 should been in the OPC DA server 2017 installation kit.
  • Guest
    Reply
    |     Aug 23, 2022
    How can the version of the OPC Client affect whether you can get data out of the OPC Server? If the Server is 2.05 compliant any Client should be able to test it. Never used the OSI OPC Client for testing, but is it not 2.05 compatible?
  • davidrosinski
    Reply
    |     Aug 23, 2022
    In response to Anonymous Guest, "How can the version of the OPC Client af..." I like to test the OSI DA OPC server with OPC client due to it OSI application. This way OSI cannot said it the OPC client issues when it is their product. By using OSI OPC Tool kit (include an OPCClient) I found out that it was not compatible 2.05. DA OPC Server document from OSI said to use OSI OPC Tool kit to test the DA OPC Server connection, but if you use the OPCint kit the OPCClient does work. Way OSI has to separate version of the OPCclient is the question. I thought if the DA OPC server documents said to use OPCclient to test  DA OPC server then the DA OPC Server kit should include it.