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 PI Connectors
Categories PI Connector for OPC UA
Created by Clint Ramsey
Created on Aug 20, 2022

RELATED IDEAS

OPC UA: allow a host name override

Allow a hostname override when connecting to the OPC UA endpoint.   We have some use cases where the URL returned by two independent OPC UA servers has the same name.  This prevents the Connector from connecting to the correct endpoint. Allow an IP address to be specified in the config, which would be used to connect instead of the URL hostname.
  • Attach files
  • Admin
    Alan Izar
    Reply
    |     Jul 12, 2023

    Declined - At the time we will not be implementing this idea since it does not align with our current data collection strategy. This feature is now available for Adapters.

  • Guest
    Reply
    |     Aug 20, 2022
    Allow the discovery from the OPC UA endpoints located in segregated network with unkown host/DNS. Now, the name resolution needs to be done manually through the “hosts” file of the OS that hosts the connector...
  • Guest
    Reply
    |     Aug 20, 2022
    In order to let Clients having endpoints located in segregated network with unkown host/DNS to use the discovery functionality from the OPC UA instead of manually force the connection adding the hostname and the IP of the source in a dedicated file of the OS that hosts the connector. Osisoft will as consequence obtain adavantages expanding their Cients sector (more and wider Client sector with different architecture will use their products).
  • Gabriel Verreault
    Reply
    |     Aug 20, 2022
    Example of the implementation in UAExpert attached. Article describing this more in depth https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=OPC-UA-Cannot-connect-when-using-IP-Address
  • Gabriel Verreault
    Reply
    |     Aug 20, 2022
    This can be achieved by setting UseDnsNameAndPortFromDiscoveryUrl = False in App.OpcUa.Config and restarting the connector for the changes to take effect.
  • Gabriel Verreault
    Reply
    |     Aug 20, 2022
    In version 2.0.x, it is also available in the Data Source configuration. See UseDnsNameAndPortFromDiscoveryUrl in the UserGuide for details