PI Interfaces
Welcome to the
PI Interfaces feedback page!
We created this forum to hear your ideas, feature suggestions and feedback on PI Interfaces. 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.
-
UNIINT Interfaces and Connectors should be able to retry an output event if output write fails
When an interface fails writing to a DCS system, the interface writes a failure status to the output tag and goes on. User has requested an option to have an output tag retry after write failure. It would be good to have this functionality in all uniint interfaces as they are recompiled, starting with the OPC DA interface, also to have this added to PI Connectors. Retries could stop after x retries of 1 minute retries, or when a new output value comes in. Or some other policy could be worked out.
3 votes -
Migrate the PI Universal Interface (UniInt) Framework to use PI AF SDK
Most PI Interfaces are based on the PI Universal Interface (UniInt) Framework and rely on PI API and its successor, PI SDK. PI SDK has, in turn, been superseded by PI AF SDK. PI SDK also relies on the deprecated and insecure ActiveX technology, which PI AF SDK does not use. I don't know or want to think about how insecure PI API is, even when the Windows Integrated Security version is used.
For many data sources, the only OSIsoft-supported option to get data from the data source to PI is a PI Interface, partly because an equivalent PI Connector…
2 votes -
Meter Type support for REXU-EA
PI Interface for EnergyAxis to support REXU-EA meter types.
2 votes -
Allow scan class 0 to be monitored via Performance Counters
As a PI System Administrator, I would like to monitor the point count and other parameters for scan class 0 via Performance Counters. Currently, this is only exposed via the UniInt Health Tags.
2 votes -
Improved handling of PI Write failures
Provide a configuration option in UniInt interfaces, to enable shutdown of the interface if it consistently receives error messages when attempting to write to PI. Recently had an interface successfully connect to PI but not achieve write access to its tags; would've been nice to have this interface gracefully shut down or restart, and allow its UFO failover partner to serve the data flow
2 votes -
Remotely view logs
I understand that you can remotely view logs using pigetmsg. However this solution does not work for me as the interface is on a controlled network that only allows outbound traffic. I would like a way for the interface node to be able to push out interface logs somewhere such as to my DA, that way I could use SMT to view my interface logs.
2 votes -
Managing loss of connectivity - local data
For a PI tag with a specific scan class, if no new value is collected by the PI Interface after a period of time (for example 2x the scan class) , the interface will add automaticaly the value "No Data". It will avoid the usage of a dedicated analyze for this, in the PI Server. And like that, the PI user will be aware of the issue, by using any PI Visualization tool.
1 vote -
Replace pipc.log and PI Message logs with the Event Viewer
PI Connectors already use the Event Viewer to log messages. It is time for PI Interfaces to do the same.
0 votes
- Don't see your idea?