PI Interface for Werum PAS-X 5.1.8
- Last UpdatedNov 09, 2026
- 5 minute read
PI Interface for Werum PAS-X Batch creates Event Frames in the PI AF database based on Primary Batch Records from the PAS-X MES. The interface automatically creates PI AF Elements that correspond to equipment managed by PAS-X and boasts several configurable options to get the most context from your PAS-X data.
PI Interface for Werum PAS-X Batch 5.1.8.4, released February 2024, internally replaces PI SDK with AF SDK - this improves the security, robustness, and communication capabilities of the interface.
For more information on product features and functions, including system requirements and installation/uninstallation instructions, refer to PI Interface for Werum PAS-X Batch guide.
The latest information about the 5.1.8.4 release is available online on the AVEVA Documentation Portal.
New features and enhancements
There are no new features or enhancements in this release.
Resolved issues
This section lists items resolved in this release:
|
Work Items |
Description |
|---|---|
|
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. |
|
22156 |
Cache start and end times can no longer be permanently altered by arbitration events. |
|
22163 |
SQL Native client print message was disabled for Oracle based interfaces. |
|
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. |
|
22209 |
Interface will no longer have a delay in processing a batch when the local time is greater than GMT. |
|
22211 |
MONITORTAGWINDOW now defaults to 0, meaning monitor tag counts do not get trimmed to the most recent <MONITORTAGWINDOW> days of activity and roll over at INT_MAX unless MONITORTAGWINDOW is deliberately set. |
|
22216 |
Interface ID has been added to the message logs in order to uniquely identify log message. |
|
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 United States 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. |
|
22250 |
Merging issue causing unit procedure and operation not to close has been fixed. |
|
22260 |
Batch event frames no longer merge event frames when merging is disabled and unique ids do not match. |
|
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 that they 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. |
|
23299 |
EMDVB fetches SQL data with greater efficiency EMDVB gathers SQL data for lists of batches rather than querying each batch's data individually, and reuses the same SQL connection for all queries. |
|
24445 |
Tests have been modified to allow for Daylight Savings on Test machines. |
|
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. |
|
24847 |
SQL Native Client is no longer supported, and is now replaced with OLEDB for all supported batch interfaces. |
|
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. |
|
27091 |
Extra emphasis on ensuring AF checkin is performed before disconnecting, as well as the addition of the AFAutoCheckin feature. |
|
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. |
|
67926 |
Interface will not allow Batch events with a zero start time. |
|
68207 |
PI Event Frames Interface Manager will now store 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. |
|
69486 |
All attributes are now created on the correct event frame. |
|
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 locks 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. |
Known Issues
There are no known issues for this release.
Security information and guidance
We are committed to releasing secure products. This section is intended to provide relevant security-related information to guide your installation or upgrade decision.
We proactively disclose aggregate information about the number and severity of security vulnerabilities addressed in each release. The tables below provide an overview of security issues addressed and their relative severity based on standard scoring.
Overview of new vulnerabilities - Fixed or Mitigated
This section is intended to provide relevant security-related information to guide your installation or upgrade decision. AVEVA is proactively disclosing aggregate information about the number and severity of PI Interface for Werum PAS-X Batch security vulnerabilities that are fixed in this release.
For this release of PI Interface for Werum PAS-X Batch, no vulnerabilities have been fixed or mitigated.
Security vulnerabilities fixed in PI Interface for Werum PAS-X Batch 5.1.8.4 release
|
Severity Category |
CVSS Base Score Range |
Number of Fixed Vulnerabilities |
|---|---|---|
|
Critical |
9 - 10 |
0 |
|
High |
7.0 - 8.9 |
0 |
|
Medium |
4.0 - 6.9 |
0 |
|
Low |
0 - 3.9 |
0 |
Distribution Kit Files
|
Product |
Software Version |
|---|---|
|
Microsoft Visual C++ 2019 Redistributable (x86) |
14.21.27702 |
|
Microsoft Visual C++ 2019 Redistributable (x64) |
14.21.27702 |
|
PI AF Client 2018 SP3 Patch 4 |
2.10.10.2539 |
|
PI Interface for Werum PAS-X Batch (WPASxBatch) |
5.1.8.4 |
|
PI Network Subsystem Support (PINS)* |
3.4.435.538 |
* - The PI Network Subsystem Support (PINS) component is not displayed on the installation welcome screen if the PI Data Archive is installed already.