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.
-
Migration from interface to connector
Would like a way to migrate from interface to connector as easily as possible.
7 votes -
Add failover capability for the BACnet Connector.
Failover similar to the UFO available for UNIint interfaces. Warm failover would be sufficient, although I'm sure there are some who would like cold and hot as well.
6 votes -
Log device information when the Connector receives errors from a device
Currently the Connector logs when it receives errors, but does not print information that can be used to determine which device is reporting the errors.
We currently need to perform a wireshark trace to look at the individual packets to determine which devices are sending errors.
4 votes -
Suppress the creation of "Status Flag" PI Points
The end-user would like to suppress the creation of the "Status Flag" PI Points, as they wish to keep their point count to a minimum due to the license-enforced point limit.
3 votes -
Make the connector a BACnet Device (get a BTL listing)
Some devices can only send COV notifications to other BACnet devices. Since the Connector is not a device and does not respond to who-is messages (and does not listen on port 47808), the connector is unable to utilize COV subscriptions for these devices.
2 votes
- Don't see your idea?