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.

Smart Connector foo DeltaV should let user configure some default attributes for tags created:
- User should be able to define what the default point security should be
- User should be able to decide if tags should be created as Poll or Advise

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.

The newest version of UCOS now supports string tags.  Currently the CSIUCOS interface (1.0.0.22 as of writing) does not support these types of tags.

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.

allow instruction level data to use batch level start time. Add an option to allow this. use case: the instruction level start time is the time when the DOT should be ramped up or down.  The batch start time is a few minutes before that timestamp.  To get the turbines adjusted in time, they need to use the batch start time.  This gives the operator enough time to adjust the set point and have the new target met by the instruction start time.

The new CSI UCOS API now supports a "bumpless download".

"CSI has recently added what they call a “bumpless download” feature to their UBrowser application that the interface uses to communicate with the database. What this does is allows the database to be updated without stopping the service. "

Please implement this feature.

Note: This was previously Enhancement 121741.

Add support for Conversion Factor PI Point attribute to PI Interface for BACNet.

Note: This was previously Enhancement 118928.

Upon initial configuration, the XML config file does not include the default interface settings.  This can cause confusion for the user.  Explicitly add the elements for the default values to the XML config file.

Note: This was previously Enhancement 123207.

OPC HDA Interface would be enhanced to use  switch '/outputsnaptime'.  For output tags, the interface would use the timestamp from the original event that triggered the output to timestamp the data.

Note: This was previously Enhancement 124754.

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.

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.

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.

Currently DNP3 outputs are done one event at a time. We could improve performance by either supporting multiple DNP messages per TCP packet or multiple analog output commands per DNP message.

The PI Interface for Quindar SCADA should have an option to log all values and timestamps from the data source (Prior to any processing by UniInt) for a specified PI point.

For the SNMP Interface, the suggestion would be to have the interface output a .txt file that includes the SNMP devices that have lost connection with the interface. This could be useful when there is a high volume of SNMP devices that connect to the interface.

The health point names for the Read_Only 1.6.8.1 SNMP Interface have a different naming convention than the health points for Read-Write SNMP Interface 1.5.1.306. In order to keep monitoring consistent across version upgrades, the suggestion is to keep naming convention of the health points the same across versions.

Can you remove the restriction to use only an IP address in the BACnet Network Discovery Tool?  The interface will correctly load and poll tags to a network device referenced by name instead of IP, however the Discovery Tool has the limitation of being IP only.