The current version of the PI Interface for OPC XML-DA seems to only support SOAP 1.1. All recent OPC XML-DA servers are developed following SOAP 1.2 standards, meaning the PI interface will not connect. Please enhance the interface to also support servers using the newer SOAP 1.2 standards.

This also relates to tech support case 00857284

Rockwell FactoryTalk Batch v12.01 allows to output batch data to a SQL database as well as EVT files. Just like with EMDVB, the PI Interface for FTBatch should be able to use both data sources.

The PI XMLTool that is bundled with the PI Interface for OPC XML-DA does not function with Windows Server 2019 even though the PI Interface for OPC XML-DA itself is documented to function. Can the client tool please be worked on so that it will function with the same operating systems that the interface does. This is a key component to aide in the troubleshooting of the interface as well as determining the correct instrumenttag field by the browsing the XML-DA tags on the server.

On PI Interface for Foxboro I/A 70 series version 2.4.2.12, the supported operational System are Windows 2008 R2, Windows 7, Windows 8 and 8.1, Windows 2012 Server.
Can we also test the interface against Windows 10, to included it as a supported OS?

China Network Isolator interface does not support float64 point type, which is required by many customers in China. Right now, they have to change the point type to string first and then to float64 by analytics, this will consume two times of license number.

Add PI Interface for OPC XML-DA documents to the Live Library

The interface instancesnames contain the plantsnames and I want to put the interfaces with the same plant name together in the list.

The PI Interface for OPC DA is packaged with the PI OPCtoCSV tool which extracts all OPC Items. When the tool is run into error with certain branches, the tool will stop and disconnected from the OPC server/tunneller. For example: “GetItemProperties(“xxx”) error 0x800706be. The remote procedure call failed. pEnumleaves  Next() returned 0x800706ba”
If we could specify an option for the tool to skip those branches in error and also attempt to reconnect to the OPC server/tunneller, for automation purpose for the tool to continue running instead of exiting.

CA ISO is planning to upgrade its ADS (automated dispatch system) to version 8. This upgrade introduces breaking changes from the current system, API version 7.

The CA ISO interface should be updated to account for these changes.

When primary server is down, secondary server is accessed instead of primary server, which is good. However, in the case of output point with source tag, it stops working, then restarting the interface instance of interest is needed. Of course, if we set up UniInt Failover that backup instance keeps its session with secondary server, this issue can be prevented. But, it will be better if source tag is also switched to secondary server.

As a PI System Administrator, I would like to monitor the point count and other parameters for scan class 0 via Performance Counters. Currently, this is only exposed via the UniInt Health Tags.

As an interfaces user, I would like to know which versions of iFIX and Windows Server OS are compatible with the PI Interface for GE iFix so that I can determine whether this interface is suitable for my use case.

The last update for this interface was in 2014, so there has been no testing on compatibility since iFIX 5.5, but I am looking to use versions 5.8, 5.9, and 6.0 and Windows Server 2016.

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

PI AMI Itron Interface currently supports TLS1.1. Microsoft ended support for TLS1.1 in March 2020. To keep the PI AMI Itron Interface usable with latest browsers, please update to support TLS1.3.

Batch interfaces should follow a similar approach to UniInt based interfaces to retrieve the diagnostic tags. That is to say they should pull the diagnostic tags based on the PointSource, Location1, and ExDesc, not a hardcoded name based purely on EXE name and Location1. This would allow the PI admin to name tags to their organization's naming convention and also avoid naming conflicts between interface instances of the same type running on another interface node.