AVEVA™ PI System™ Feedback Portal

Welcome to our 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

Clear

Ideas

    Showing 9 of 5194

    Allow AVEVA Adapter for Modbus TCP to collect data on INT64 and UINT64 registers

    Certain equipment is providing energy data under INT64 or UNIT64 register types. However, the Adapter currently only supports FLOAT64, which is not compatible. We want to be able to configure the Adapter for Modbus TCP to collect data on INT64 and...
    Alexa Derago 3 months ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 0 Future consideration

    Support System States for the Adapter for Azure Event Hubs

    The data passed through the Adapter for Azure Event Hubs can be very dynamic in its configuration. It would be useful to be able to send system states to indicate bad data, and possibly the nature of that bad data. In the same way that interfaces ...
    Mike Horrocks almost 2 years ago in AVEVA™ Adapters / AVEVA Adapter for Azure Event Hubs 2 No status

    Defining "Scan Class" and "Poll" Capabilities in Aveva Adapter for Azure Event Hubs

    Define the "Scan Class" and "Poll" capabilities in the Aveva Adapter for Azure Event Hubs, similar to the functionality available in the Interface. Ensure the ability to manually select a "Scan Class" for PI Points and define it as "Poll".
    Guest about 1 year ago in AVEVA™ Adapters / AVEVA Adapter for Azure Event Hubs 0 No status

    Expand Healthpoint (Device Status) Information of the PI Adapter for Modbus TCP from Component to "Device" Level

    When configuring PI Modbus TCP adapter you first define a component level and under this type you define your different devices/machines/sensors. In case of a broken connection to one of the devices the healthpoints currently only deliver the stat...
    Mario Amrhein about 2 years ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 0 No status

    Support for "RTU over TCP" for Modbus Adapter using MBAP header

    Challenge: Today, the PI Adapter for Modbus TCP does not natively support " RTU over TCP". It does support Modbus TCP, so as long as the "bridge" properly converts Modbus RTU to Modbus TCP (including the MBAP header), it should work fine. If the b...
    Hans-Otto Weinhold about 2 years ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 0 No status

    Allow multiple references to holding register for bit extraction

    Given a 16bit integer holding register, in certain instances we only care for specific bits rather the integer value. Using the bitmap allows the selection of those specific bits but you can only reference the register once. i.e. In data selection...
    Matthew Kishe almost 3 years ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 8 Future consideration

    Addition of substitution parameters in DefaultStreamIdPattern -> specify a ValueField for it to read from

    People wanting to use a single EventHub and Container holding events from many sources with common attribute naming. Want to be able to differentiate the naming of the pi tags based on source. Being able to substitute a unique source identifier (s...
    Guest almost 2 years ago in AVEVA™ Adapters / AVEVA Adapter for Azure Event Hubs 0 No status

    Error message should be generated for the Modbus request time out

    After request time out, Modbus adapter should generate an error as time out after specified duration set by user.
    Guest almost 2 years ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 0 No status

    Accept HEX numbers for Register offsets in data selection

    Most modbus equipment providers provide information using registers in Hex format i.e. 0x0000 ~ 0xFFFF. It would be nice if the offset could accept this to avoid error in conversions HEX to DEC. Would make things alot more seamless/easier.
    Matthew Kishe almost 3 years ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 0 Future consideration