PI Connectors

Welcome to the PI Connectors feedback page!  

We created this forum to hear your ideas, feature suggestions and feedback on PI Connectors. 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. New function for Ethernet/IP (“scanner”)

    Add the function to able to act as (“scanner”).
    At this moment the connect can only act as an adapter, that means that It can't collect data from other device that also are connector is an adapter.
    https://www.odva.org/Technology-Standards/EtherNet-IP/Overview

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

    We’ll send you updates on this idea

    0 comments  ·  Ethernet/IP  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support user-defined data types in the PI Connector for EtherNet/IP

    As an advanced user, I would like to be able to specify a user-defined data type for the array sent to the PI Connector for EtherNet/IP.  For example, if I have a 32-bit array composed of one INT and two SINTs, I would like to be able to configure the connector to parse this array correctly. Currently the data type specification of the array is limited to one data type (DINT, INT, FLOAT, or SINT).

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

    We’ll send you updates on this idea

    0 comments  ·  Ethernet/IP  ·  Flag idea as inappropriate…  ·  Admin →
  3. Mass create data source list for PI Connector

    For the PI Connector for EtherNet IP you can have up to 100 data sources. Typing in all of them is tedious. It would be nice if we could copy/paste information from Excel OR have a structured import/export file to the data source list.

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

    We’ll send you updates on this idea

    1 comment  ·  Ethernet/IP  ·  Flag idea as inappropriate…  ·  Admin →
  4. The connector creates too many tags

    Currently, the connector will create 124 or 248 tags per data source, regardless of how many meaningful data points are actually in the data set.
    This greatly limits the use of the connector to any customer that is not an EA.

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

    We’ll send you updates on this idea

    0 comments  ·  Ethernet/IP  ·  Flag idea as inappropriate…  ·  Admin →
  5. Connector provides Timestamps

    The EtherNet/IP protocol does not specify timestamps when data is transmitted, the connector currently assigns the timestamps base on when the data is being processed.

    This leads to the following issue, if the network/computer/etc gets busy, we will have several values be processed at the same time. Thus, many values with the same timestamps.

    A possible work around is that the connector specifies time frequency, for example values come 10ms apart.
    If the connector read this frequency, the connector could possibly assign better timestamps for values that are processed at the same time.

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

    We’ll send you updates on this idea

    0 comments  ·  Ethernet/IP  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support string data types for PI Connector for EtherNet/IP

    String data, such as serial numbers, are supported by the EtherNet/IP protocol and are often collected to help understand what was being made by a piece of equipment at any given time.

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

    We’ll send you updates on this idea

    0 comments  ·  Ethernet/IP  ·  Flag idea as inappropriate…  ·  Admin →
  7. PI Connector for Ethernet IP should retrieve tagnames from the PLC array

    The AF Hierarchy that is created by the connector does not take into consideration any of the tagnames within the PLC array, it just creates attributes for them as slot.n where “n” is a number corresponding to the array position. Not only is this is not human friendly, but it will require renaming all assets and PI tags in order to understand what the data is.

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

    We’ll send you updates on this idea

    0 comments  ·  Ethernet/IP  ·  Flag idea as inappropriate…  ·  Admin →
  8. Need EtherNet/IP connector to be able to read and write.

    Need EtherNet/IP connector to be able to read and write.
    Currently EtherNet/IP connector is read only.

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

    We’ll send you updates on this idea

    0 comments  ·  Ethernet/IP  ·  Flag idea as inappropriate…  ·  Admin →
  9. Have Option to Enable Exception Testing

    Related enhancement request: https://feedback.osisoft.com/forums/555139/suggestions/37362121.

    There are use cases where the need for exception go beyond simply reducing network traffic achieved by the current wire-level compression. The Ethernet IP connector has the potential to send very high frequency data which often exists in the real-world as noise. Other PI System components that operate off of snapshot data such as the PItoPI interface and various visualization products can be negatively impacted by this lack of a data filter.

    See also https://feedback.osisoft.com/forums/320517-pi-vision/suggestions/39650839-option-to-disable-snapshot-values-on-trends.

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

    We’ll send you updates on this idea

    0 comments  ·  Ethernet/IP  ·  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
TELL US MORE
EVALUATING
PLANNED
IN DEVELOPMENT
COMPLETED
DECLINED