We would like to have some sort of digital state such as "Intf Shut" written to all OPC tags when both interfaces in a failover pair are shut down.

Currently, the /opcstopstat and /stopstat parameters (which write a specified state to all tags when the interface is shut down) are ignored if the interface is in failover. We'd like for some sort of status to be written to tags when no data is being collected by either interface.

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.

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!

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

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.

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.

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.

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.

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.

Allow Print() function to evaluate runtime variables before outputting text to the log.

For example: I have created a Counter variable that increments for each event that is successfully sent to PI. I would like to output the final tally to the logs but printing the raw number [Print(Counter)] is not valuable without context. Instead, I would like to combine literal string text with the dynamic value of this Counter variable:

Print("Events sent to PI: {Counter}")

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.

Provide support for Modbus function code 20

As a PI System Admin, I would like to see a confirmation window (acceptation pop-up message), when deleting Interface instances in PI Event Frames Interface Manager. This would minimize the deletion of the instances by error.

POINDexter application be modified such that addresses beyond 64000 are able to be ‘tested’ / polled, rather than having to configure a tag to read those registers

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.

Customer would like the ability to have PItoPI create a list of tags that includes the FULL name of the source tags, as well as the destination tags they are mapped to.  This will greatly assist in managing tags that are being sent to a remote customer.