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.204 votes
We plan to provide users the ability to pick their tag naming convention and not worry about managing a cache file. We are working on implementing this functionality with PI Connector for OPC UA.
Support for health tags (similar to UniInt health tags), Windows performance counters, or any other way to bring Connector status and health information into PI tags to put them side-by-side with Interface health monitoring.189 votes
We understand and acknowledge the importance of this request. We are evaluating how to provide a homogeneous and unified experience for health information across all our connectors.
PI System Connector: Need real time snapshot data support for the PI System connector.125 votes
I know a lot of you are really excited about snapshot support for PI System Connector, so I wanted to offer you an update on our release plans.
Q4 2020 – You can expect to see a PI System Connector release introducing snapshot support for PI Points with the compression attribute set to zero (on the source system).
Early 2021 – You can expect to see a PI System Connector release that will expand on the Q4 release by adding snapshot configuration options and snapshot support for PI Points with the compression attribute not set to zero (on the source system).
The editor should allow you to see in real time how it interacts with the data. Being able to test the INI file prior to loading some file would make it much more manageable to read a variety of data format and insure that it has the expected behavior before starting the connector and having to use a trial and error approach. A good example of this is what Microsoft does with PowerQuery in PowerBI. This would allow troubleshooting UFL issues much more easily and allow more people to use the connector without having to spend a serious amount of time testing all the various scenarios.
The editor should allow you to see in real time how it interacts with the data. Being able to test the INI file prior to loading some file would make it much more manageable to read a variety of data format and insure that it has the expected behavior before starting the connector and having to use a trial and error approach. A good example of this is what Microsoft does with PowerQuery in PowerBI. This would allow troubleshooting UFL issues much more easily and allow more people to use the connector without having to spend a serious amount of…85 votes
Support connector-level failover in PI Connector for OPC UA 2.x (relay-enabled version). Similar to UniInt failover (interfaces), failover should be data source specific and always favor the data source in the better state.72 votes
Support for Alarms & Conditions. This data type would be good candiate for storing into Event Frames. Tell us more about your use case in the comments, which source system you have that support A&C, and how you would select which A&C to collect/not collect. How would you like Event Frames built and named?67 votes
We are currently evaluating how to appropriately and effectively bring this functionality forward. We are working through details pertaining to implementation of this functionality.
The PI Interface for RDBMS is one of the most used PI Interfaces. Unfortunately, the fact that it is a PI Interface makes it unnecessarily difficult to use, and turning it into a PI Connector can help alleviate this. No more Location codes, squishy PI ICU, distributor tags, SQL file in the InstrumentTag, strange notations in the ExDesc, etc.63 votes
From this item description it looks like the major pain point with existing RDBMS interface is providing configuration information (to the tags and interface). I would like to understand more if the request behind the connector is to solely minimize providing configuration information to the existing interface and tags?
allow historical data access with custom time ranges, like OPC HDA59 votes
We have a feature in the upcoming 1.2 release of the connector that will allow you to collect data from OPC UA tags that do not have current values but do have history. We would poll these every 60 seconds (default) to find new data.
Was that part of this request in any way? Can you describe in more detail what you would like as a feature that prompted you to vote for this time?
Currently Connector configured to rertieve event on change and not based on a scan class like interfaces.The Connector suscribes to the changes, and when a change comes in to the server, the data will be sent to PI connector. We need option to retrieve the data every certain minutes even data is the same and is not changed on OPC server.
We understand that for slow changing points, values might not change often and thus there is a need to collect values at certain time intervals as opposed to on change. However, scanning at frequent intervals leads to increased load on the server and thus can lead to performance degradation. We are discussing how best to solve this problem with PI Connector for OPC UA.
Add failover capability so I can run a pair of connectors that will failover to the backup if the active is unavailable42 votes
Add reading capability for OPC UA Arrays. Currently items with “ValueRank“ = 1 are ignored.39 votes
Example 1 - OPC
If a new connection needs to be made to one OPC Server, restarting the connector forces all data sources (and potentially connections to multiple OPC Servers) to be restarted.
Example 2 - UFL
If my web service is down and I do not want to connector to keep trying to access to REST Server, I cannot stop/disable only one data source36 votes
Allow a hostname override when connecting to the OPC UA endpoint. We have some use cases where the URL returned by two independent OPC UA servers has the same name. This prevents the Connector from connecting to the correct endpoint. Allow an IP address to be specified in the config, which would be used to connect instead of the URL hostname.32 votes
As an equipment specialist working centrally, I wish to deploy my AF Element Templates including Analysis and Notifications Templates to my remote sites so I have them managed from a central location. This also insures that remote sites are using the same calculations and KPIs.32 votes
We are aware of the interest in this functionality, but at this time it is not in our short-term plans to implement.
We would like to learn more about the different scenarios in which you would be syncing your Analyses and Notifications.
Please continue to share your use cases here.
The REST endpoint from which I want to pull data requires token authentication. I would like the UFL Connector to be able to obtain the token given the username and password I enter on the Admin page.30 votes
Ability to turn off auto creation of PI tags - When data is sent via REST to a PI Connector for UFL service ,currently it looks for a PI Tag in the PI Server and if the PI Tag does not exist it creates a new PI Tag. It would be good if we could turn off the feature if not required as in our case we have a naming convention for PI Tags and we create the tag names in advance so would not like to allow for the auto creation of PI Tags.29 votes
I’m not sure why this would be needed. In the UFL connector you need to specify the name of the tag that you write to. And if that tag already exists, it will write to it. If that tag does not exist, then the connector would create that tag with your desired tag name. Why would you want the connector not to create that tag?
Support acquiring data by polling the OPC UA server rather than subscription.27 votes
This request is partially similar to the following request – https://feedback.osisoft.com/forums/555139-pi-connectors/suggestions/19611235-retrieve-data-even-it-s-not-changed-on-opc-server
PI Connector for IEC 60870-5-104 writes 'No Data' or another SYSTEM digital state when connection to the Data Source is lost.
This connector is specially used to monitor the connection of the machines, but if there is a general network crash, and the connector losses the connection to the Datasource, it will stop sending data instead of sending something to alert of the situation.
Not being aware of that situation can cause big impact in the companies.
Receiving a Sytem digital state when the connection to the data source is lost would help to create an alarm and let the people in charge know.26 votes
I would like to have the option to replicate AF Analyses using PI System Connector with the option to mark the desired analyses for replication.26 votes
There are several edge cases when it comes to replicating analyses. This item needs more deliberation.
For OPC UA Analog Items, the OPC UA standard mandates an EURange property and an optional InstrumentRange property. These Range properties contain a Low and High field.The PI Connector for OPC UA should have an option to use either of these Ranges to set the Zero and Span of the PI tags it creates and the Maximum and Minimum AF Attribute Traits.24 votes
- Don't see your idea?