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

    26 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.

  2. 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 →
  3. 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 →
  4. 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 →
  5. 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=="\"?*\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"
    Tag=["\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Quality=["\"*\",\"*\",\"*\",\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value1=["\"*\",\"*\",\"*\",\"*\",\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value2=["\"*\",\"*\",\"*\",\"*\",*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value3=["\"*\",\"*\",\"*\",\"*\",*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value4=["\"*\",\"*\",\"*\",\"*\",*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value5=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value6=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value7=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value8=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value9=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value10=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value11=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value12=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,*,*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value13=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,*,*,*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value14=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,*,*,*,*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value15=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value16=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value17=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value18=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value19=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value20=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value21=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value22=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value23=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"]
    Value24=["\"*\",\"*\",\"*\",\"*\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,\"(*)\",*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*"] …

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

    2 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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 →
  8. 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 →
  9. 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.

  10. 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 →
  11. 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 →
  12. 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 →
  13. Replication of Event Frames between PI Systems

    Ability to replicate Event Frames (EF) between PI Systems.

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

    We’ll send you updates on this idea

    0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  14. Replicate PI Tag Configuration Changes

    Ability to replicate PI tag configuration changes to the destination system.

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

    We’ll send you updates on this idea

    0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow REST parameters to be passed from tag configuration for UFL connector

    Allow parameters to be passed from the tag configuration or from the ini file to the URL specified as the REST endpoint for the REST client. For example, to query the following URLs:

    https://restcountries.eu/rest/v1/alpha/uk
    https://restcountries.eu/rest/v1/alpha/fr
    https://restcountries.eu/rest/v1/alpha/es

    we would have something like:
    https://restcountries.eu/rest/v1/alpha/ + %Exdesc%

    for the address, where the Exdesc of the tags are Exdesc=gb, Exdesc=fr, Exdesc=es.

    This would allow one data source to be configured for multiple REST endpoints without needed a third party tool in between.

    3 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 →
  16. Auto creation of ini based on json schema

    It will be great if we could generate a pseudo ini file with property key as seed for the for variable and field names. We can then pick and choose what to use for store in PI and creating AF structure

    3 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 →
  17. Support choosing which collective member is the data source

    When configuring the PI System Connector, there is currently no option to constrain the communications for the data source of PI Tag data to a secondary or tertiary PI Collective member. 

    The ability to force the PI System Connector to use the secondary or tertiary PDA as the data source will allow customers worried about impacting their primary archive's performance to manually balance the load on their collective and eliminate impacting the performance of their existing solutions.

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

    We’ll send you updates on this idea

    0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  18. IED Security for PI Connector for IEC61850

    Enable the connector such that it can use the IEC61850 security parameters of username and password,

    2 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 →
  19. User guide FIELD mistakes

    Many examples in the user guide use "[FIELDS]". Also, on page 40, it says "FIELD]". These should all be "[FIELD]".

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

    We’ll send you updates on this idea

    4 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  20. Missing prefix removal paragraph in the user guide

    At one point, the user guide mentions "This section has a paragraph describing how to remove the prefix". There is no such paragraph. Please add this paragraph to the user guide.

    1 vote
    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
COMPLETED