PI Interfaces

← User Feedback for OSIsoft Products and Services

Welcome to the PI Interfaces feedback page!

We created this forum to hear your ideas, feature suggestions and feedback on PI Interfaces. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.

Please note that your ideas and comments posted here are visible to all other users.

  • For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal  (https://my.osisoft.com) instead of sharing them on this site.
  • For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.

How can we improve PI Interfaces?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

  1. PI BACnet interface doesn't say which PI point caused the device to return Error 31

    For the PI BACnet interface, the following error can be returned from the device for a particular request and then written into the message logs:

    " >> BACnet error packet received. Error Code: 31; Error Desc: Unknown Object; InvokeID: 0"

    However, this log message does not include which request caused the error. This error message should include which PI point resulted in this error so that the customer can easily find the relevant point and either correct the configuration or investigate why the device cannot find the object.

    16 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    STARTED / IN DEVELOPMENT  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →

  2. Allow bulk editing for EFGen

    Allow a way to bulk edit EFGen configuration, preferably in a spreadsheet format.

    12 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    STARTED / IN DEVELOPMENT  ·  0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

  3. PI Event Frames Generator - Fix 'merge consecutive' in PIBAGEN mode.

    To enable us to move from PIBAGEN to EF Gen interface, we need 'merge consecutive' to work when running  in PIBAGEN mode. Currently none of this functionality is working, and the following known issues is already found.

    119695 - Merge consecutive at unit procedure level does not merge all consecutive unit procedures.
    124407 - Unit Procedures may be improperly merged in PIBaGenCompatibility mode.
    119363 - Consecutive subbatches can get merged incorrectly

    Please make an updated version of the 'PI Event Frames Generator' where this important functionality is working.

    5 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

PI Interfaces

Categories

Feedback and Knowledge Base

(thinking…)
Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA/PREVIEW
COMPLETED