PI Interfaces

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.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. DNP3 Interface specify Class for scans

    Create some way to configure PI Points belonging to a DNP3 interface instance such that the interface only requests data for a single class (Class 1/Class 2/Class 3) and not all three? Essentially, an event scan that will request one specified Class 1, 2, or 3 data from the RTU.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DNP3  ·  Flag idea as inappropriate…  ·  Admin →
  2. PI Interface DNP3 - unsolicited data listen only mode of operation requested

    Is there an option in DNP3 driver (In fact at TCP level) to make it listen on a certain (usually 20000 for DNP3)? In era of IoT devices, most devices are sleeping devices, they wake up usually once a day and push data to DNP3 Master (PI), however DNP3 PI collector doesn't support this model. As an enduser I would like to utilize this mode of operation at our plant. FYI, there are other products e.g. Citect SCADA and ClearSCADA use two separate ports for Inbound and outbound DNP3 traffic to use the both modes simultaneously.

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  DNP3  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow the same RTU Address to be used across different IP nodes

    The current implementation of the PI Interface for DNP3 does not allow the same RTU address to be used across different IP nodes. The PI Point Location3 attribute is used to specify the RTU address only. If a customer has multiple RTUs with the same address but on different IP nodes, they either have to reconfigure all of the RTUs to have different addresses, or create a new DNP3 interface instance for every IP node.

    Case example:

    Customer has 800 SEL-735 meters, each with a different IP address, and each with a DNP Address (RTU address) of 1. He has…

    9 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  DNP3  ·  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/PREVIEW
COMPLETED