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.
-
SNMP: Throttle scan specific informational messages as the interface may fill up logs every scan frequency
This is for SNMP version 1.6.3.0, the following message is printed every scan frequency:
"Scan class <scan class number> for device <IP address> will be skipped due to previous pending requests"
And this needs to be throttled as the logs may be get filled up quickly with this type of messages.
Note: This was previously Enhancement 124938.
5 votes -
Add subscribeCOV support to BACnet Interface
My device only supports SubscribeCOV, but the PI Interface for BACnet only supports SubscribeCOVProperty. I would like the PI Interface for BACnet to support SubscribeCOV like the PI Connector for BACnet already does.
4 votes -
4 votes
-
Interface TCP\IP para Data-Logger Davis (WeatherlinkIP)
Se recomienda agregar funcionalidad para adquiquirir datos de un DataLogger WeatherlinkIP, ya que actualmente solo se soporta conexiones seriales con este data Logger:
Davis Vantage Pro / Pro Plus Weather Station (NTI)
Davis Weather Station (NTI)Tener en cuenta que actualmente todas tecnología se basa en conexiones TCP\IP.
https://www.davisinstruments.com/product/weatherlinkip-for-vantage-stations/
3 votes -
PI Interface for ABB Web Imaging System via ABB CNI
CNI interface should support message 25. Currently, we do not support any message beyond 22.
3 votes -
Buffering Manager - add metrics for each buffered interface
When validating/troubleshooting data flow issues, it would be helpful to see metrics on which interfaces are actively sending data to the buffering subsystem via Buffering Manager. If an interface is in a bad state or stopped, it would be obvious which interface is having issues since the count would be zero. Currently the counts in the buffer queue are for all interfaces, so this only gives the user an idea on whether the buffer subsystem is forwarding data to the data archive, without knowing which interfaces this data is coming from.
3 votes -
64-bit version of CatGH5 interface
There needs to be a 64-bit version of the CatGH5 interface that is capable of parallel processing in order to efficiently process an quantity of data/files (that the 32-bit version is not up to the task of handling well).
3 votes -
PI Interface for GE HABConnect FLDTIME Support for COUNT Objects
Currently only POINT/ANALOG fields support COUNT. This request would be to enhance the interface to additionally support the COUNT field.
3 votes -
PI-SNMPTrap interface request support for SNMPv3 trap
PI-SNMPTrap interface currently only has support for SNMPv1 and SNMPv2C trap. Feature request for PI-SNMPTrap interface to include support for SNMPv3 trap.
Monitoring of snmp traps originating from CISCO switch devices require support for SNMPv3 trap.
3 votes -
PI PerfMon tags to support Timestamp DataType
There are some performance counters that are Date and Time based.
PI PerfMon tags have to be configured as Float32 or Int32 and at PI AF it has to be converted by using PI Analysis or Formulas. Would be easier to configure, maintenance and to build reports if there is a direct way.
3 votes -
BACNet: Add support for Conversion Factor PI Point attribute to PI Interface for BACNet
Add support for Conversion Factor PI Point attribute to PI Interface for BACNet.
Note: This was previously Enhancement 118928.
3 votes -
DNP3: handle invalid timestamps from the RTU
If the RTU provides a timestamp of 0 when using RTU provided timestamps, which does not conform to the DNP3 spec, allow the option to timestamp the event with PI time or drop the event altogether.
Note: This was previously Enhancement 123208.
3 votes -
Create a migration path for AMI Interfaces when PI Server is moved to a new machine/hostname
Currently, AMI Interfaces require a rebuild of the AMI cache files when the PI Server is migrated to a new machine/hostname (Although to clarify if the hostname does not change during the PI Server migration the cache does not need to be rebuilt). This is undesirable for large AMI implementations as rebuilding the cache files can be a time consuming process.
It is requested that AMI Interfaces should be able to handle PI Server migrations with new hostnames without rebuilding the AMI cache files
2 votes -
Streamlined management of PI Interface for SNMP .pwd file
When using the interface to gather data for hundreds of SNMP devices, managing the .pwd file becomes very burdensome due to an inability to format the file. Comments are helpful in sorting devices, but they are removed upon encryption. It would be nice to see a tool that helps with the management of passwords.
2 votes -
PI Buffer Subsystem doesn't use the user who is logged in
PI Buffer Subsystem must have a option to set up the user account is logged instead of using Windows Domain or Local account that is running the windows service. This is a huge security issue when using Buffer on client computer to send manual data because you will need to create a Mapping or Trust and give permission in so many pi points when the user logged on computer should have access to write in few pi points.
Please prioritize this one!
2 votes -
Davis to Pi Interface - Additional sensor functionality
Add functionality for the Davis to Pi Interface to read additional sensor data points. The Davis to Pi Interface does not support the use of additional sensors, such as a second or third temperature sensor. The Davis console supports additional sensors, but the Pi Interface cannot read them.
2 votes -
Expand failover functionality in Schneider-Electric Foxboro fxbais interface
Failover mechanism in fxbais (Schneider-Electric PI interface for Windows) doesn't lead to a failover when the primary interface node loses connection to the network (f.i. when its NIC fails). It just starts buffering and sends its data after the connection is back again.
It keeps on updating its watchdog CALC block on IA, so no take over is initiated.
Some applications require "near real time" data, so if it comes in a day later, it's not very useful.
In such a case, the secondary interface node could perfectly take over the data collection.2 votes -
Determine the packet loss of the ping (Ping Interface tag) out to another tag
Scenario: I have a tag that pings site A. I have the response times, which quantifies the response times of the network, but this line is also a bit slow and we suspect packet loss, but I want that in a tag.
2 votes -
Add -f (Ping Switch) to OSIsoft Ping Interface
Enhancement for Ping Interface to add -f switch 'Set Don't Fragment flag in packet. When sending large packets we do not want to Fragment.
Case: When monitoring a site ping worked for small packets, however with large packets sent, the site showed packet loss which in turn was an actual hub issue missed when using Ping Interface.
2 votes -
PI PerfMon interface to support ArcReplace
Right now PerfMon only supports ArcNoReplace. PerfMon has a history of failing over if a server is unreachable. And since PerfMon only supports Hot failover, every time it fails over the new interface tries to write values that the old one already wrote. I would like to be able to specify ArcNoReplace so I don't get an error flood every time the interface fails over.
2 votes
- Don't see your idea?