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. PI Connector for OPC UA Relay Support

    As a PI Admin relays allow for improved security of process-network-to-DMZ communication.  This will greatly aide in the PI Connector for OPC UA's deployment in production systems.

    47 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 →
  2. PI Connector for MQTT

    Create a PI Connector that supports the MQTT messaging protocol

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

    We’ll send you updates on this idea

    27 comments  ·  New PI Connector request  ·  Flag idea as inappropriate…  ·  Admin →

    We are pleased to announce the release of PI Connector for MQTT Sparkplug 1.0.0.6.

    The PI Connector for MQTT Sparkplug connects to a MQTT server and subscribes Sparkplug-defined topics. The data collected by the connector provides real-time updates based on the data received based on the subscribed topics. The connector models the topic data and metrics by creating a PI AF hierarchy/structure in PI Asset Framework, and by creating PI points in the PI Data Archive.

    Release notes and user guide for the PI Connector for MQTT Sparkplug 1.0.0.6 are available on the OSIsoft Customer Portal and OSIsoft Live Library.

  3. Ability to change which PI tag the PI Connector for OPC UA writes to without having recreate new PI tags

    Currently, once PI tags are created by the PI Connector for OPC UA the connector uses the point ID for its mapping from the OPC UA server to the PI tags. Thus, if a configuration change occurs on your OPC UA server (i.e. NodeIDs change) the only way to map the newly named (with no change in the data stream) NodeID to a PI tag is to create a new PI tag instead of simply changing the configuration on a PI tag. As a PI system administrator, I want the ability to change a PI tag attribute (i.e. Extended Descriptor)…

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

    We’ll send you updates on this idea

    1 comment  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  4. Support Server Level Failover

    To ensure that data continues to flow from the OPC UA server to PI Connector for OPC UA, the connector could be configured to switch to another OPC UA server under the same conditions as the OPC DA Interface

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

    We’ll send you updates on this idea

    5 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  5. Get EngUnits from OPC UA connections

    Get EngUnits from OPC UA connections and use with Element Attributes and/or templates

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

    We’ll send you updates on this idea

    2 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support passing dynamic timestamps to REST API URI

    In order to retrieve Forecast data from a REST API, I would like to be able to pass timestamps from the Connector dynamically into the URI. For example:
    ...rest/forecast.wsgi?type=hourly&start=2017-02-15T13%3A44%3A44Z&end=2017-02-30T13%3A44%3A44Z&SID=PDX

    19 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 →
  7. Allow the UFL Connector to performa a scan Immediately after startup

    On startup, the Connector currently waits for the configured scan frequency time to pass before doing its first scan. There are cases where a low scan frequency (e.g. once per day) is required. This results in an unnecessary delay before the Connector starts collecting data. Please all ow the option to perform a scan immediately after the Connector finishes its internal startup routine.

    18 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 →
  8. Provide the option to have flow control loops (for/foreach/while/case..)

    We have been dealing with large files with many columns (over 100).
    In this cases, it is a pain to design the ini file - especially when extracting every column's data into variables. It was annoying to the point that we wrote a perl script to help out with that ! 

    Why does not PI UFL support FOR loops ? ( and while loops, case statements, etc)

    Large matrix data extraction like:

    [Data]
    Data.FILTER=C1==""?",,,,,,,,,,,,,,,,,,,,,,,,,,…

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

    We’ll send you updates on this idea

    0 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  9. Selecting a subset of items from the same OPC UA template

    When multiple OPC objects share the same template, you can only either select the entire template or not since only the template would be populating the filter file. In the example above, if one were to want to bring CC1001 in PI but not CC2001, then, they would need to be moved to a specific folder in the UA Server or change the template on the UA Server side. There should be a user-friendly way to perform more granular selection

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

    We’ll send you updates on this idea

    1 comment  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  10. Multiple AF Databases Support

    Support for replicating data from multiple AF Databases.

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

    We’ll send you updates on this idea

    3 comments  ·  PI System Connector  ·  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.

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

    We’ll send you updates on this idea

    COMPLETED  ·  3 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add scan time offset option to UFL Connector

    Use case: The UFL Connector needs to read a huge data set from a REST Server which is updated once a day. The only way to control when the data fetch occurs is by starting the connector at the desired time. The Connector however currently waits for the configured scan frequency time to pass before doing its first scan after starting. Furthermore, the Connector/hosting server may be restarted throughout the day for various reasons (e.g. application of Windows patches) throwing the timing off and further adding another 24 hour delay.

    Scanning, processing and sending to PI the same data more…

    9 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 →
  13. 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.

    9 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 →

    The latest versions of PI Connector for Wonderware Historian and PI Connector for UFL include the capability to configure the substitution off illegal characters for PI point names and AF element names. Please let us know in a new idea other connectors where you have identified a need for a change in this functionality.

  14. PI Connector for OPC UA Ignore First Value

    Some OPC UA servers send an initial subscription value of BAD or Bad_WaitingForInitialData when a subscription is first made. This data does not reflect integrity or the health of the data stream, and as such is not desirable to archive this value in some situations.

    This request is for the connector to have a configurable flag to no longer store the initial value sent by the UA Server data source.

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

    We’ll send you updates on this idea

    4 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  15. PI Point name Illegal character handling in PI Connectors

    Currently source points for PI Connectors that contain illegal characters are handled differently depending on the PI Connector. Some will replace the character while others will map an illegal character replacement when creating the PI Point. These illegal characters should be dealt with the same across all PI Connectors. Examples of illegal data source Characters: * ' ? ; { } [ ] | \ ` "

    6 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 →

    The latest versions of PI Connector for Wonderware Historian and PI Connector for UFL include the capability to configure the substitution off illegal characters for PI point names and AF element names.

  16. Create the ability to configure an update frequency of a connector subscribing to changes on an OPC UA Server

    In some cases an OPC UA Server can have tags that update several times per second.  Currently the OPC UA Connector would receive an update on every one of those changes.  This can create a heavy load on the network and OPC Server.  For this scenario it would be good to configure a minimum time that the connector waits before receiving a new update for a tag.

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

    We’ll send you updates on this idea

    5 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  17. Enable the UFL Connector to read data from REST Endpoints

    Many devices and services (including the PI Web API) offer data via REST endpoints. It would be very useful if the UFL Connector could connect to such REST Endpoints and consume the data without the need of a 3rd party tool. Built-in support for JSON would also be nice.

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

    We’ll send you updates on this idea

    0 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
    COMPLETED  ·  Chris Coen responded

    This feature was released in version 1.1 of the PI Connector for UFL.

  18. Read files from .zip folders

    Would like UFL connector to take a .zip folder and read the files within that folder

    5 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 →
  19. Add back the functionality of sending PI System Digital States with UFL Connector

    In PI UFL Interface we can use the StoreInPI functionality to store System Digital States but in UFL Connector we can't.

    In our usage, we have tags related to Limits and we want to show the limit value when a limit is set or "No Limit" when no limit is set. So, we changed the System Digital State to contain "No Limit" as one of the options.

    When we use PI Web API or AF SDK we can set that correctly, but as the data is flowing we receive the text "No Limit" and right now we need to ignore…

    4 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 →
  20. UFL Connector does not use User Agent header in GET requests

    I have a customer that would like to pull data from NOAA NWS website using NOAA's API. The API requires User Agent info in the header of the request. Currently the UFL Connector does not provide the User Agent info and there is no option to include it. Customer would like the Connector to provide User Agent information in the header of GET requests.

    PI Square Thread: https://pisquare.osisoft.com/thread/35672-does-ufl-connector-send-user-agent-info-in-get-requests

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

    We’ll send you updates on this idea

    0 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • 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