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 Other specific PI Connector
Created by Ee Sheing Lee
Created on Aug 20, 2022

RELATED IDEAS

Enable the option to not sync/overwrite pi point attributes for PI Connector GE e-terrahabitat after connector is started

As of version 1.1.1.42, by specifing tag under a given field node, this allows you to set any PI point attribute you want with an associated value. Furthermore, you can specify an associated key filter for that attribute. However, if we manually change the PI Point attributes, for example compression setting using PI Builder, once the connector is restarted, this setting will not be preserved and will be reverted back to the setting. This is expected behavior as documented in the manual (sync option: manual and auto) To prevent this override, we could remove the DefaultPointAttributes from the config.xml file or define key filter for certain subset of PI Tags. Unfortunately, we have a “typical” setting loaded in DefaultPointAttributes by default, so that any new automatically-created tag has at least “sane” defaults in those fields. Using PI Asset Connector for Emerson DeltaV as an example, we can define [UC] switch to disable the synching, it will be great if the Connector for GE e-terrahabitat can have this similar setting or provide additional option in the config.xml for this feature to prevent the override of pi point attributes upon restart of the connector
  • Attach files
  • KPRoth
    Reply
    |     Jan 30, 2023

    @Janelle: thanks for the response. Unfortunately, we have tens of thousands of points, and within any given set of points of a similar type we have many 1-offs where we need to set a different parameter than the typical default for those points. We strongly prefer to manage the 1-offs by simply editing the specific tags that need the adjustment (and then let the pi collective's tag sync push the update to the other collective members), rather than having to go in and change our configuration files on both members of the pi-collective, with the risk that we break the config due to typos.


    In other words, the choice to decline this enhancement means this connector is effectively incompatible with my company's needs, and we can no longer upgrade to newer versions. Please reconsider.

  • Admin
    Janelle Minich
    Reply
    |     Jan 30, 2023

    The PI Connector GE e-terrahabitat connector applies default point attribute settings upon connector restart, and that is by design. This is so we can ensure the default point attributes defined in the configuration file are in sync with the point attributes in the Data Archive. If the user wishes to update the PI Point attributes, the configuration file should be updated to reflect those changes, and then the connector can be restarted.

  • KPRoth
    Reply
    |     Aug 20, 2022
    The prior version (1.1.0.5) only applied the DefaultPointAttributes once, when an auto-sync'd Pi tag was first created, and never forcibly re-applied the default attribute when the connector was restarted. That behavior allowed us to set a reasonable default compression-deviation setting for all new tags, but then come back later and further tune the compdev value on specific tags. Unfortunately with the new behavior as of 1.1.1.42, the ability to come back and tune the compdev settings is lost. This needs to become an option again for us.