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

    10 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. Transformations and scaling

    Add the ability to configure PI points so that the PI Connector for OPC UA performs transformations and scaling on the values before being archived.

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

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  3. Rollback Option for System Connector

    We had an issue with the System Connector and had to reinstall every part of it, but then all tags in the destination system have been created again. The old tags have not been updated anymore. We think about an option to reverse every change the connector did on the destination system (delete AF Elements, Attributes, Event Frames, PI Tags) that have been created by the connector.

    We thought of a workflow like this:

    Delete the routing of the "not-correct-working" Connector via DCM
    Delete the Connector via DCM UI (and de-registering it from DCM and Relay in that step)
    Deleting…

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

    We’ll send you updates on this idea

    1 comment  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  4. Merge Two Tags or Copy Tag Data to a New Point

    Sometimes, when dealing with APS, a new TAG is generated for an existing point. Data stops going to the old point. It would be nice if there was an easy way, within the gui (not manually dumping and importing) that we could take the values from one tag, and place it into the new tag.

    There are other times when we may want to copy all historical values from a tag, and place it into a new tag.

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

    We’ll send you updates on this idea

    3 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  5. Enable or Disable single DataSource

    When a datasource is actually offline and we don't want the UFL connector to keep trying uploading or connecting to it and pollute the message log .

    The best option would be having the stop/start enable/disable and restart options for each datasource.

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

    We’ll send you updates on this idea

    1 comment  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  6. OPC UA Connector Trend Advise Option

    OPC UA Connector Trend Advise Option, such as in the UniInt interfaces

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

    We’ll send you updates on this idea

    3 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  7. Support Assigning Point Sources for Connectors

    Connectors currently assign point sources; this is not user configurable.  In addition, all connector of like kind get the same point source.  This makes it difficult to determine which tags "belong" to which connector node.  Users would like to be able to monitor\count\filter searches based on connector node.

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

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  8. Synchronize behavior between PI Connector for Cygnet and Cygnet enumeration value representation

    The values stored in the “Table Entry” column in Cygnet TRS should match the “State” column in the PI Server Digital states table. This way end users are not confused why the trends in PI do not match the trends in Cygnet.

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

    We’ll send you updates on this idea

    0 comments  ·  CygNet  ·  Flag idea as inappropriate…  ·  Admin →
  9. Windows Authentication to the Rest Endpoint should be supported with PI UFL Connector. Currently only Basic is supported

    I tried connecting to a REST endpoint using PI UFL Connector. However, it seems the Connector only supports Basic Authentication. The REST point only supports Windows Integrated Security. We can use Web Browser to read data from the REST endpoint. We get the following error in the connector log: HTTP status code: Unauthorized

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

    We’ll send you updates on this idea

    2 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for reaching out. We can extend the connector to support the NTLM authentication, which falls under Windows Authentication. Would it meet your needs?

  10. 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 →
  11. Have PI System Connector support null system digital states

    Would like to have the connector support Null System digital states. Null system digital states can work locally on a PI Server. Would like the connector to support all the options found locally so that we could accurately sync systems.

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

    We’ll send you updates on this idea

    STARTED / IN DEVELOPMENT  ·  3 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  12. Have option to enable exception on Connectors.

    There are use cases where data is sent over networks with latency (satellite link, for example) so being able to filter out noise at the connector is important.  This is also important when a connector sends data to a local PI Server in the field (low latency), but then PItoPI is used to send snapshot updates to a central PI Server over a high latency link.

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

    We’ll send you updates on this idea

    3 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  13. PI Connector Relay support write modes

    While writing data to PI through the connector relay there seems to be no option to control the write mode . E.g."[-109] Value at This Time Already Exists" is shown in the logs if the archive already contains an event with the same timestamp. The default update option can be "Replace" instead of NoReplace. Other write options can be made configurable.

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

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  14. Illegal character handling in PI Connectors - AF element

    Update to the Wonderware and UFL connector to handle illegal char only changes the PI tag. The AF still updated with the original char change. (i.e. \ to %19i). The AF element need to match the PI tag name and need done for all connectors.

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

    We’ll send you updates on this idea

    0 comments  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  15. Collect units of measure and description from Siemens Simatic PCS 7

    Support collecting units and description from the Siemens Simatic PCS 7 system and writing them to the AF attribute and the PI Point attributes.

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

    We’ll send you updates on this idea

  16. Add the ability to write to a point using an attribute other than tag name

    Provide the capabilities of mapping a UFL data point to a PI tag using a PI Point attribute other than the tag name.  For example, we’ll have a data file from another database that uses a different ID than our PI point name. Could we write to PI using that ID as the point instrumenttag or exdesc?

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

    We’ll send you updates on this idea

    1 comment  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  17. Put a REST endpoint on all connectors

    It would be very useful to see the data flowing through a connector at the edge, or even the data buffered in a connector. Every connector could have a rest endpoint with the same methods as PI Web API. Possible uses:

    -Diagnose connection/configuration issues
    -Attach a dashboard directly to the connector on the node (for example a display on a monitor in a mining truck)
    -Attach third party software for local analysis or alarming of equipment status (for example, alerting the driver of a truck of important events)

    I'm sure there are many others...

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

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  18. Control which PI/AF servers each data source sends data to.

    Right now, for one instance of the connector, all configured data sources will send data to all configured PI Data Archives and PI AF Servers. It is all or nothing. Due to the fact that you cannot have multiple instances of the same connector on any given node at a time, if you want this kind of granular control you would need an entirely new node and another connector. In the past, it was trivial to have multiple interfaces instances on the same node to send different data to different PI Data Archives; connectors should allow this capability.

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

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  19. PI Connector for Modbus TCP - include option to configure response data byte size by register type.

    Certain RTUs limit the number of Boolean/Discrete values they return independently of the number of floats they return. The PI Connector for Modbus has a configuration option for “Maximum Response Data Bytes” but it applies to all register types. Enhance the maximum response data byte size configuration to provide an option to configure the max byte size by register type.

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

    We’ll send you updates on this idea

    0 comments  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  20. PI Connector for Modbus TCP

    Develop a PI Connector for Modbus TCP. 

    Connectivity to Modbus slave devices; used for general purpose connectivity to many legacy industrial devices.

    Interoperable with Edge Data Store (EDS) and OSIsoft Cloud Services (OCS).

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

    We’ll send you updates on this idea

    0 comments  ·  New PI Connector request  ·  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