In case of csv files in subfolders within Main Path for UFl, PI UFL Interface should be able to search the csv files with placeholder and extract data from csv files from multiple sub-folders within the main folder.

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/

CNI interface should support message 25. Currently, we do not support any message beyond 22.

hen the primary Interface becomes available and healthy again, it becomes "back up". I need the primary Interface to become the "primary" whenever it is healthy.

https://pisquare.osisoft.com/thread/42591-revert-back-to-primary-data-collector

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.

Allow for monthly scan intervals for scan classes. i.e. "scan monthly on the first hour of the first day of every month".

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).

(Posted on behalf of our customer)

It can reduce the chance of startup failure because of the connection to PI Data Archive time-out. It's also helpful if interface can reduce time to get PI point information from PI Data Archive.

Currently only POINT/ANALOG fields support COUNT. This request would be to enhance the interface to additionally support the COUNT field.

1. Having the capability of acknowledging the message in the PI Buffer GUI and removing the "red flag" when messages acknoledged.
2. Having the Buffer updated automatically when a tag is renamed, without having to restart the buffer.

We use the Phoenix Contact Firewall with the OPC Inspector. When the OPC server restarts or breaks the connection for a few seconds, the firewall blocks all ports except port 135. After initial connection through this port, new firewall rules are dynamically established for DCOM connections. If connection break to OPC Server we have to restart interface manually.

I would like the PI UFL Interface to be able to directly read from input files that are in non-UNC paths such as Azure File share, so I do not need to periodically copy the input files into another path.

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.

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.

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.

Create an option to allow the PI Interface for UFL to delete files with the read-only attribute.

As of version 3.8.1 COLD failover is no longer supported by the PI to PI Interface (https://techsupport.osisoft.com/Troubleshooting/Enhancements/19255OSI8). However, the PI Interface configuration utility still allows COLD failover to be selected. This leads to an invalid configuration and the interface refuses to start.

PI ICU should not allow the selection of COLD failover as it does not allow HOT failover, both of which are not supported by the interface.

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.