PI Connectors

Welcome to the PI Connectors feature suggestion box. We created this forum to hear your ideas, suggestions and feedback.

Please suggest your most important features and design change ideas on this site! Also vote for your favorite features now! We welcome your feedback.

  • NOTE: for documentation feedback and bugs, please report to Documentation@osisoft.com rather than entering them on this site.

How can we improve PI Connectors?

(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. Migration from interface to connector

    Would like a way to migrate from interface to connector as easily as possible.

    7 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  BACnet  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add failover capability for the BACnet Connector.

    Failover similar to the UFO available for UNIint interfaces.  Warm failover would be sufficient, although I'm sure there are some who would like cold and hot as well.

    6 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  BACnet  ·  Flag idea as inappropriate…  ·  Admin →
  3. Log device information when the Connector receives errors from a device

    Currently the Connector logs when it receives errors, but does not print information that can be used to determine which device is reporting the errors.

    We currently need to perform a wireshark trace to look at the individual packets to determine which devices are sending errors.

    4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  BACnet  ·  Flag idea as inappropriate…  ·  Admin →
  4. Suppress the creation of "Status Flag" PI Points

    The end-user would like to suppress the creation of the "Status Flag" PI Points, as they wish to keep their point count to a minimum due to the license-enforced point limit.

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  BACnet  ·  Flag idea as inappropriate…  ·  Admin →
  5. Make the connector a BACnet Device (get a BTL listing)

    Some devices can only send COV notifications to other BACnet devices. Since the Connector is not a device and does not respond to who-is messages (and does not listen on port 47808), the connector is unable to utilize COV subscriptions for these devices.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

Feedback and Knowledge Base

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
COMPLETED