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.133 votes
We have decided at this time that we will not create a PI OPC UA Server. We will continue to evaluate the OPC UA data egress use case in the future, but this capability is not on our current roadmap.
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.8 votes
While we appreciate the interest the community has for this suggestion, we have decided to decline this item in favor of other high priority work. Thank you for your feedback, and please continue sharing suggestions for how we can improve the PI Developer Technologies for you!
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.5 votes
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.
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
This feature is not a priority at this time. We will update this thread if we decide to add this capability in the future.
As a PI user, I want the OPC DA and HDA Servers to honor the Windows identity of any connected OPC client.3 votes
Apologies as I meant to set this item to declined with my previous update.
Thank you for your valuable feedback. We have no plans to work on this feature in the near future, so I am setting the status to declined. I will update the status if we eventually schedule this work.
- Don't see your idea?