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.53 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 HDA37 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?
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.25 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.
Adding the Relay and the DCM framework to the "legacy"IEC 104 Connector in order to improve the architecture management and security22 votes
Collecting more data to understand the need and use case behind this request.
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.22 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?
RWE Power AG
“But one really important feature we need, is the ability to write back from PI into the SCADA system
Until now, we couldn’t find anything about this (important) functionality.
So our question is if we can use this connector bi-directional?
And if not, is this already in the roadmap for this connector?”20 votes
Can you share with us any info about your use case for sending data back to the SCADA system? For example, what is the purpose of that data? How many tags and how often will you send?
The PI System Connector allows to include PI Point replication directly from the PI Data Archive even if they are not reference in the PI AF hierarchy with the "Include all PI points from this PI Data Archive" option.
I would like to replicate only some PI Points that are not referenced, not all. This would remove the need to maintain both a PI to PI and a PI System Connector.
I could create a bogus AF Database referencing those points but I would prefer not to.16 votes
As suggested in the description of this item, PI System Connector uses AF database as the primary source and thus any filtering that is desired at the PI Tag level can be accomplished by referencing only those tags in the source AF database. If users would only like to replicate PI tags without an AF model, then PI-to-PI interface can serve as an alternate option.
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: Unauthorized9 votes
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?
- Don't see your idea?