Release Notes
- Last UpdatedJan 23, 2025
- 6 minute read
PI Interface for ABB800xA Batch Release
Version 5.1.2.7
Overview
The PI Interface for ABB 800xA Batch collects ABB system data from an Oracle-based 800xA backend to create event frames in PI Asset Framework.
We offer two ABB 800xA Batch interfaces: one for the Production Data Log (an Oracle-based 800xA backend) and one for Production Response (SQL-based 800xA backend). PI Interface for ABB 800xA Batch 5.1.2.7 supports version 6.0.3.2 and 6.0.3.3 of the ABB 800xA Batch system that use Oracle 9.2.0.7.0 and above as the batch historian.
This interface allows users to specify which events trigger event frame creation, configure how the property and tags are named, and define the process data that is stored in PI.
The 5.1.2.7 release of PI Interface for ABB 8000xA Batch internally replaces PI SDK with AF SDK - this improves the security, robustness, and communication capabilities of the interface. As a result, this interface only writes Event Frames to a PI AF Server, and disallows creating PI Batches in the PI Batch Database. Users creating PI Batches in the PI Batch Database will need to migrate to Event Frames in order to utilize this version of the interface.
Enhancements
There are no enhancements for this release.
Fixes
This section lists items that were resolved or added in this release.
|
Work Item |
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. |
|
22151 |
Duplicate event frames are not created when BatchID or Name contains not allowed characters. |
|
22153 |
Restore DESCRIPT handling in phase step logic. |
|
22156 |
Cache start and end times can no longer be permanently altered by arbitration events. |
|
22196 |
Event frames separated by more than cache time no longer merge. |
|
22200 |
A delay has been added to allow attribute "__BatchStartTime" time to be available. |
|
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 don't get trimmed to the most recent 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. |
|
22219 |
Unit procedure level event frames using different units will no longer be merged. |
|
22221 |
Monitor tags now accurately reflect the number of batches and their child events. |
|
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. |
|
22250 |
Merging issue causes unit procedure and operation not to close. |
|
22251 |
Empty UniRecord dump files are no longer generated. |
|
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. Fix in current development branch and in 4.3.x.x Branch. |
|
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. |
|
22281 |
Procedures created by Operation recipes are properly updated extended properties for determining end time and merge. |
|
22283 |
The Event log source is created during the interface install step. |
|
22289 |
When network interruptions cause AFSDK to becomes out of sync and throw duplicate uniqueid exceptions, the interface attempts to complete the rest of the checkin, set the offending event frame(s) to a checked in state, and exits. |
|
23832 |
A delay (/DELAYBUFFER) was added so the source data is available at the time of query. This helps event start times such as __BATCHSTART. |
|
24117 |
Interface now supports the INCLUDEINCOMPLETEDATA configuration option. If set to true, the interface creates unit procedures and all its children without a unit. |
|
25811 |
PI data server collectives and PI buffering to multiple PI data servers is now supported. |
|
25995 |
There is a new AFERR (-500) value that gets set on the Batch Status tag during an EFGEN AF check in error. Customers can monitor the value of the tag and notifications and analyses can be performed in the event that an error occurs. |
|
26466 |
Batch Interfaces now support an AF Interface Statistics element that stores the values of the PI tags recorded during interface execution. The location of the newly created element can be configured using the Batch Interface Configuration Manager and passed through the INI file. |
|
26756 |
With the release of version 5, if you have a batch interface supported batch database, it will no longer be able to write to PIBatch Database. Version 5 only supports Event Frames Customers who need to write to PIBatch. The database needs to stay with Version 4.x.x.x Batch Interfaces. |
|
27053 |
Added new logging level 3 (DB) to include Unirecord diagnostics messages into message log. |
|
27091 |
Extra emphasis on ensuring AF checkin is performed before disconnecting, as well as the addition of the AFAutoCheckin feature. |
|
67289 |
UniRecord exports now include all UniRecord fields. |
|
67298 |
Event sorting is faster and memory consumption is better managed during event queuing. |
|
67927 |
A UID in the UIDLIST with zero or empty start times will be ignored. |
|
68377 |
Changed the Batch list management algorithm to improve event processing accuracy (prevent missed batches). |
|
68907 |
Default account to setup interface service is now Default Virtual User (NT Service/). |
|
69287 |
Updated the BIFConfig 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 |
Interface supports failover and includes a health tag that can be monitored. |
|
70398 |
Float tag values are now evaluated correctly. |
|
70403 |
Message logging includes exception data. |
|
70471 |
Very long log messages are successfully logged. |
|
72522 |
Interface stability improvements. |
|
73489 |
Interface no longer stops 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). |
|
75880 |
Procedure level recipe events are processed correctly and have no missing end times. |
Known Issues
There are no known issues for this release.
System Requirements
Operating Systems
This interface is a 64-bit application.
|
Platform |
64-bit Application |
|---|---|
|
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 |
Distribution Kit Files
|
Product |
Software Version |
|---|---|
|
Microsoft Visual C++ 2015-2019 Redistributable (x86) |
14.21.27702 |
|
Microsoft Visual C++ 2015-2019 Redistributable (x64) |
14.21.27702 |
|
PI AF Client 2018 SP3 Patch 4 |
2.10.10.2539 |
|
PI Interface for ABB 800xA Batch (ABB800xA) |
5.1.2.7 |
|
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.
Installation and Upgrade
The PI Interface for ABB 800xA Batch can be installed or upgraded using the PI Interface for ABB 800xA Batch installation kit, ABB800xA_5.1.2.7_.exe. This installation kit can be obtained by using the How to Download Products link listed in the AVEVA Customer Portal How To's list. This list is located on the AVEVA Customer Portal.
For additional information regarding the PI Interface for ABB 800xA Batch installation, please see the Installation instructions portion of the PI Interface for ABB 800xA Batch (PIBatchGuide) User Guide. This user guide is available for download from the AVEVA Customer Portal.
Uninstalling PI Web API
The PI Interface for ABB 800xA Batch Interface can be uninstalled using the Programs and Features list accessible from the Windows Control Panel. After accessing the Programs and Features list, select the entry named PI Interface for ABB 800xA Batch Interface (ABB800xA) and then select Uninstall from the menu.
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.
There are no security vulnerabilities in this release.