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.
-
Support PI tag renaming
Tags created by a PI Connector can be renamed, but these renamed points can be "forgotten" if the Connector's point cache is lost. Updating the Tag Mapping configuration file can avoid this cache loss, but I would like to be able to rename Connector tags without updating this configuration file.
137 votesWe are working on this request. We plan to provide users the ability to pick their tag naming convention and not worry about managing a cache file.
-
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)…
28 votesWe are currently working on incorporating functionality that will allow users to write data to existing tags without having to recreate a new set of tags.
-
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=PDX19 votesNext release of the connector will include this functionality.
-
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.
14 votesThis functionality will be included with the upcoming release (1.3.×.x)
-
Multiple AF Databases Support
Support for replicating data from multiple AF Databases.
10 votesThis functionality will be included with the upcoming release (version 2.1.x)
-
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 votesThis functionality will be included with upcoming release (1.3.×.x)
-
Read files from .zip folders
Would like UFL connector to take a .zip folder and read the files within that folder
5 votesThis functionality will be included in upcoming release (1.3.×.x)
- Don't see your idea?