Release notes

22133

Attribute values referencing other event frames are captured regardless of the order event frames are created.

22140

Unirecord data sources are now included in unirecord imports and exports.

22172

When removing an interface from PI Event Frames Interface Manager it will also remove any associated services.

22181

When adding an interface to PI Event Frames Interface Manager, the instance id will be initialized as the same value of interface id.

22211

MONITORTAGWINDOW now defaults to 0. Monitor tag counts do not get trimmed to the most recent <MONITORTAGWINDOW> days of activity and but instead roll over at INT_MAX unless MONITORTAGWINDOW is deliberately set.

22218

All generated unirecords will have the placeholder [TIMESTAMP] have the format "YYYY-MM-DD" for a SQL source and "YYYY/MM/DD" for non SQL source like EVT files.

22221

Monitor tags now accurately reflect the number of batches and their child events.

22224

PI Event Frames Interface Manager properly creates new default virtual user service without errors.

22235

Interface configuration for RST and RET reads UnitedStates format standard.

22245

The unit procedure batch id attribute is controlled by the unit procedure recipe template batchid.

22246

PI Event Frames Interface Manager does not allow older interfaces to edit health tags.

22249

All batch interfaces remove passwords from INI file regardless of parameter capitalization.

22268

All RST and RET within the configuration will be parsed as US format.

22275

A check that verifies that a Procedure Event Frame and a Unit Procedure Event Frame are both generated by the same interface instance before linking them together.

22283

The Event log source will be created during the interface install step.

22464

The 'Watch Interface Log' button in PI Event Frames Interface Manager opens Windows Event Viewer.

23177

PI Event Frames Interface Manager now stores RST and RET as UTC Note. This can be edited in a local friendly time string and read into the interface correctly.

When written by the configuration program, they will write the times out as UTC and a local time string as a comment.

24781

The interface setup kit may use the same GUID for all the interface installs, which can cause trouble when installing multiple batch interfaces on the same machine. PI Event Frames Interface Manager now uses different GUID for each interface.

25811

PI data server collectives and PI buffering to multiple PI data servers is now supported.

26756

Writing batches to a PI Batch database is no longer supported. This version of the interface only creates Event Frames in PI AF.

50935

Addressed advanced parsing issue when using LBE ("Left Bound Exclusive").

52120

Whenever an Interface becomes the primary, it will use the /RST command line switch as the start date and process the batches.

67289

UniRecord exports now include all UniRecord fields.

67298

Event sorting is faster and memory consumption is better managed during event queuing.

68207

PI Event Frames Interface Manager now stores SCAN values as low as one second without complaint.

68907

The interface creates a virtual service account to run the service in new installations The Virtual Service Accounts are named inline with the interface: NT Service/<Interface Instance Name>.

69287

Updated the PI Event Frames Interface Manager utility to only allow TagPath properties to be set on Asset Templates and Property Templates Fixed issue where the TAGPATH value was not being saved properly.

69854

Fixes minor failover issues and includes a health tag that can be used to monitor failover status

70398

Float tag values are now evaluated correctly.

70403

Message logging includes exception data.

72522

Interface stability improvements

73489

Interface no longer hangs due to locale thread lock issue

73498

Setup kit creates the event source name under application logs to match with Interface application name which is used by logging framework.

50290

If a child active point receives events when the parent active point is inactive, those events will accumulate in memory. If this happens for many events, the build-up of memory can result in an interface crash due to its 32-bit limitation.

Windows Server 2022 (64-bit)

Yes

Windows Server 2019 (64-bit)

Yes

Windows Server 2016 (64-bit)

Yes

Windows 11 (64-bit)

Yes

Windows 10 (64-bit)

Yes