Release notes
- Last UpdatedMay 04, 2023
- 5 minute read
PI Interface for OPC DA
Version 2.7.2.20
Unilnt Version 4.7.2.1
Overview
PI Interface for OPC DA is an OSIsoft client application that reads and archives data from OPC data sources.
Fixes and enhancements
Fixes
This section lists items that were resolved in the 2.7.2.20 release:
|
Work Items |
Description |
|---|---|
|
40582 |
ICU Control now correctly adds /UWQ parameter to the .bat file even if is set to the default value of 0. |
|
40584 |
Interface now sends "good quality" when /SG is parameter is set. |
|
40593 |
Resolved duplicate data in PI DA resulting from duplicate connections to the OPC Server when interface gets disconnected from the OPC Server. |
|
40602 |
Exceptions occurring in the On data changed are now caught and logged. |
|
40608 |
Resolved incorrect file permissions on .cred file creation. The service user now has access to the credential file. |
|
40619 |
Backup interface will only collect data from the OPC Server during hot failover. When the interface is assigned to "primary," it will begin sending data to PI. |
|
40623 |
Interface now continues to update existing Advise tags according to their ExcMax parameter when a new Advise tag is added to a separate empty scan class. |
|
40633 |
Timestamp plug-in now works with event (triggered) PI points. |
|
40636 |
Startup Delay (/SD) can now be greater than 2 seconds when connecting to a DeltaV OPC Server. |
|
40641 |
Resolved interface not sending correct values for VT_DATE types when using a certain time format (/TF) parameter. Both 'ccyy' and 'yy' are now properly parsed when sending outputs. |
|
40651 |
Resolved interface incorrectly reporting opc quality 0xFF as a "Bad" quality when quality should be reported as "Good." Interface now accepts quality range 0xC0 - 0xFF as a "Good" range. |
|
40652 |
Resolved the interface stopping unexpectedly when adding data to queue. |
|
40668 |
Resolved interface stopping unexpectedly from misconfigured location codes. Interface now reports an error message with invalid scan classes and then exits. |
|
40670 |
Interface now starts, collects data, and utilizes specified digital states when Generic Plug-in DLL is used. |
|
40672 |
When the /CredFilePath is left empty, the warning message now displays the correct parameter name. |
|
40675 |
Resolved the PI OPC DA Interface falsely reporting the device status "One or more groups not getting data" under certain configurations |
|
40676 |
Resolved PI String tag output event not being correct if day part of date is not specified in time format (/TF). |
|
40705 |
OPC DA Server VT_DATE tags with millisecond timestamp values are now written to PI string tags (location2=7) with the correct millisecond values as per the time format specified on the interface, and as decimal second values written to PI Float tags. |
|
43675 |
Resolved explicit logging for output tags assigned to an output group that does not exist. |
|
72454 |
Generic and Metso plugins now read digital states properly. |
Enhancements
This section lists the enhancements in the 2.7.2.20 release:
|
Work Items |
Description |
|---|---|
|
41277 |
Updated default authentication level to 'Packet Integrity' in order to be compatible with the requirements of Windows DCOM Server Security. Notes: Interface: The DCOM security authentication level is defined by the /da parameter. OPC servers: The PI OPC Servers will continue to work using that setting. It is recommended to use that setting in the DCOM hardening guidelines. By default, the PI OPC Servers will use an authentication level of 'Default', which will use the machine-wide setting defined at the Computer level. If the machine-wide authentication level is set to Packet Integrity or greater, no change is required. Third-Party Applications: Some OPC applications will fail to establish communication even though the system-wide authentication level is set to Packet Integrity because they hard-code the authentication level to None, Connect, Call, or Packet. Contact the specific vendor of the application for details on how to enable an authentication level of Packet Integrity or greater. Performance: Application performance could be impacted. It is recommended to test with Packet Integrity to ensure performance remains adequate in your environment. To mitigate performance issues, the following should be considered:
|
|
43132 |
Updated dependencies included in install kit provided by OPC Foundation to latest version. |
|
72453 |
Removed bundled executable tools for security purposes including:
|
Known Issues
This section lists problems and/or enhancements that have been deferred until a future release
-
There are no known issues with this release or its ICU control.
System Requirements
Operating Systems
This release is supported on the following operating systems:
-
Windows 11
-
Windows 10
-
Windows Server 2022
-
Windows Server 2019
-
Windows Server 2016
-
Windows Server 2012
Distribution Kit Files
|
Product |
Software Version |
|---|---|
|
PI Interface for OPC DA (OPCInt) |
2.7.2.20 |
|
PI Interface for OPC DA – Plug-Ins |
2.7.2.20 |
|
PI Interface for OPC DA (OPCInt) – ICU Control |
2.7.2.20 |
|
OSIsoft MS VB Runtime Redistributables |
1.0.1 |
|
Microsoft Visual C++ 2015-2019 Redistributable (x86 and x64) |
14.21.27702.2 |
|
PI Software Development Kit (PI SDK) 2018 SP1 Patch 3 (x86 and x64) |
1.4.7.620 |
|
PI GenericNames DLL (PIGenericNames) |
1.3.5.25 |
|
PI Spt DLL (PISpt) |
1.2.4.0 |
|
PI Interface Configuration Utility |
1.5.1.10 |
|
PI Buffer Subsystem 2018 SP2 Patch 2 |
4.9.0.37 |
Installation and Upgrade
The PI Interface for OPC DA can be installed or upgraded using the desired option of the PI Interface for OPC DA installation kit.
-
For the read-only option: OPCInt_ReadOnly_2.7.2.20_.exe
-
For the read-write option: OPCInt_ReadWrite_2.7.2.20_.exe
This installation kit can be obtained via the OSIsoft Customer Portal. For detailed instructions on downloading the installation kit, please see the How to Download Products link located on the OSIsoft Customer Portal site.
For additional information regarding the PI Interface for OPC DA installation, please see the Installation instructions portion of the User Guide. This user guide is located in the PI Interfaces section of the AVEVA Documentation Library.
Uninstalling PI Interface for OPC DA
The OPC DA interface can be uninstalled using the Programs and Features list accessible from the Windows Control Panel. After accessing the Programs and Features list, perform the following steps to uninstall the interface and its ICU control:
-
For the read-only option:
-
Select PI Interface for OPC DA (OPCInt) - Read-Only and then select Uninstall.
-
Select PI Interface for OPC DA (OPCInt) - ICU Control and then select Uninstall to uninstall the interface's ICU control.
-
-
For the read-write option:
-
Select PI Interface for OPC DA (OPCInt) and then select Uninstall.
-
Select PI Interface for OPC DA (OPCInt) - ICU Control and then select Uninstall button to uninstall the ICU control.
-
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.