Last revision: 8/25/2021
This Readme provides information about InTouch HMI 2020 R2 SP1 (Version 20.1.100). Readme files from previous releases of InTouch HMI are posted on the Support website.
This release includes all the issues shipped in the InTouch HMI 2020 R2 Patch 01 released and can be installed directly.
Important!
When installing System Platform 2020 R2 SP1, Operations Integration (OI) Gateway is installed as a hidden feature of InTouch HMI 2020 R2 SP1.
For more information about OI Gateway installation, upgrade, and uninstall, see the System Platform Installation Guide, "InTouch HMI Requirements and Prerequisites" section, "Installing OI Gateway and Modifying FS Gateway Installations" topic.
Remote Desktop Services and InTouch HMI
When InTouch HMI 2020 R2 SP1 is installed on an older Windows 10 or Windows Server 2016 computer that has not been updated and has Remote Desktop Services enabled, WindowViewer may fail to launch. WindowMaker cannot be closed unless shut down using Task Manager.
Workaround:
Important: You can install the Microsoft update before or after System Platform. However, we recommend installing the Microsoft update before you install System Platform.
For important information about this product release, go to the AVEVA Global Customer Support (GCS) website. Information on the GCS website includes product requirements, compatibility, as well as downloads from previous releases. After you log in, you can filter search results by product name and the release/version.
InTouch HMI 2020 R2 SP1 (Version 20.1.100) includes a number of hot fixes, and provides support for the latest versions of Microsoft products. Refer to the GCS Technology Matrix for the list of supported Microsoft products.
Cybersecurity Enhancement
This version of InTouch HMI incorporates the following cybersecurity enhancements:
This section describes the hardware and software requirements to support System Platform products, including InTouch HMI.
System Sizing Guidelines
The following table provides guidelines for hardware configurations suitable for System Platform 2020 R2 SP1 software based on the size of the installation. These guidelines are subject to the limitations of your Windows operating system.
Hardware Requirement |
Small Installation (1 - 25K I/O per Node) |
Medium Installation (25k - 50k I/O per Node) |
Large Installation (More than 50k I/O per Node) |
|---|---|---|---|
CPU Cores (Minimum)1 |
Greater than or equal to 2 |
Greater than or equal to 4 |
Greater than or equal to 8 |
RAM1 (GB) |
Greater than or equal to 4 |
Greater than or equal to 8 |
Greater than or equal to 16 |
Storage (GB) 2 |
Greater than or equal to 100 |
Greater than or equal to 500 |
Greater than or equal to 1000 |
Network (Mbps) |
Greater than or equal to 100 |
Greater than or equal to 1000 |
Greater than or equal to 1000 |
Notes:
1 In redundant environments, increase CPU and RAM to maintain a maximum of 40% typical resource utilization.
2 Minimum amount of storage needed to provide sufficient capacity for 1 week @ max frequency.
Hardware Requirements Notes
Windows operating systems and SQL Server versions may impose hardware requirements that exceed the minimum requirements for InTouch HMI 2020 R2 SP1. Refer to the following Microsoft Web pages for Windows and SQL Server hardware requirements:
Auxiliary Hardware Requirements
This section describes any optional hardware requirements beyond the specific hardware requirements discussed earlier in this Readme.
Alternative Authentication Using Smart Cards
This section describes additional details about the supporting software for an InTouch HMI system.
Software Requirement Notes
Windows Operating System Notes
Showing the set of charms is a standard feature of Windows versions 8.1 that cannot be disabled by software for a touch screen. As a result, operators can access these Windows charms and possibly unlock a dedicated touch screen view node.
.Net Notes
For more information about .NET Framework requirements and compatibility, see .NET Framework Requirements and Compatibility .
Operating System Notes Common to AVEVA Products
ActiveX Controls Behavior on Supported Windows Operating Systems
Due to the Data Execution Prevention (DEP) feature of Windows 7 and later operating systems, any ActiveX control built with ATL version 7.1 or earlier will fail to host or will have unpredictable behavior in InTouch 2017 UPDATE 1 either in WindowMaker or WindowViewer. For more information, refer to Tech Note 922: "Some ActiveX Controls NOT Supported in InTouch 2012 R2 (Version 10.6)" available from the Technical Support web site.
Configuring Remote Alarm Retrieval Queries
The process to configure remote alarm retrieval queries has changed for interactive applications such as InTouch HMI when running on currently-supported Windows and Windows Server operating systems.
When InTouch WindowViewer is started and generates alarms from an interactive Windows desktop session, an AlarmViewer control (running within InTouch HMI) on a remote node must be specially configured to query the alarms. The source alarms will not appear unless the AlarmViewer control's alarm query is configured.
This type of query only works for InTouch HMI as an alarm provider running in a Terminal Services session, not for InTouch HMI running in a console session.
To configure the AlarmViewer's alarm query
\\nodename:ip_address\intouch!$system
where nodename is the name of the node that is providing the InTouch alarm and ip_address is the IP address that you determined in step 1.
Using Alarm Manager on a Single Node Running Both InTouch HMI and Application Server Alarm Providers
Starting with Microsoft Windows Vista, the operating system imposes "Session 0 Isolation" as a security enhancement. All Windows services and associated programs are required to run in Session 0, and no GUI applications are allowed to run in Session 0.
Prior to Windows Vista, Application Server and InTouch HMI WindowViewer ran in the same Windows session. Session 0 Isolation requires that Application Server and WindowViewer run in separate Windows sessions. Alarms that are reported by the Galaxy are handled by the Session 0 instance of Alarm Manager (AlarmMgr), which is now different from the Console Session instance of AlarmMgr that handles InTouch alarms. A simple alarm query in an InTouch alarm display such as
\InTouch!$System \Galaxy!Area_001
is now serviced by two separate instances of AlarmMgr -- one running in the Console Session for InTouch, another running in Session 0 for the Galaxy.
This behavior, and related behaviors and error messages resulting from the Windows operating system Session 0 changes, along with procedures to configure the Distributed Alarm System to support alarms from both InTouch and Application Server on the same computer node running with Windows Vista and later operating systems, are described in detail in TechNote 988, "AlarmMgr Support for InTouch and AppServer on Windows Vista and Later". You can download this TechNote from the Global Customer Support (GCS) website.
Remote Desktop Services (Terminal Services) Behavior in Windows Server Operating Systems
Windows Server 2008 R2 and later Windows versions no longer support the /console switch as a means of starting the remote desktop (RDP) client, also known as Session 0 or Terminal Server Console session. In Windows Server 2008 or later, Session 0 is no longer an interactive session, and is reserved only for Windows services. From Windows Server 2008 and later, all remote connections are treated as remote RDP sessions regardless of /console, /admin, or any other switches used to make the connection.
This impacts InTouch HMI functionality such as Alarm Manager that depends on the Remote Desktop (Terminal Server Console) session.
In another aspect of Remote Desktop Services behavior, InTouch HMI functions such as TSEGetClientID() can return a null value with InTouch running in a remote desktop (RDP) client session. The cause of this behavior is that the relevant roles are not installed on the RDP client. You must install the "Remote Desktop Host" role in order for TSEGetClientId() and other related functions to work properly.
The impact to Application Server is minimal as most Application Server processes run as services. One impact to Application Server is to carry forward the restriction introduced with the Windows Vista operating system which permits only one alarm provider. While both Application Server and InTouch HMI can be configured as alarm providers, only one alarm provider can be configured at any one time.
Application Server and InTouch HMI detect when the application is running in the console. In Windows Server, it implies that the application was started by a user physically at the machine. However, this behavior may require you to disable the group policy that enables Fast User Switching.
The software detects when an application is running in the console. All remote connections are treated as a remote RDP session by Windows Server, regardless of /console or /admin switches in the mstsc connection.
To disable fast user switching through the Group Policy interface
By enabling the policy, Administrators hide the Switch User button in Windows logon, in the Start menu, and in the Task Manager.
InTouch HMI Operating System Notes
You can configure local Windows security policies that work in conjunction with the EnableDisablekeys() script function to regulate the user's access to keys in a running InTouch application.
The following InTouch legacy script functions do not operate on 64-bit versions of Windows: WWPoke(), WWExecute(), WWRequest(), ActivateApp() and SendKeys().
InTouch HMI View Applications and DDE Support
NetDDE is not supported for InTouchView applications.
By design, an InTouchView application does not serve data to any other source, including InTouch HMI itself. When WindowViewer starts, it verifies if the application is an InTouchView application. When WindowViewer detects an InTouchView application, it does not register to become a DDE server. Industrial Graphics make use of the client layer when accessing InTouch tags, and appear as a third-party client trying to access WindowViewer as a data server. As a result, Industrial Graphics cannot communicate with InTouch tags when used with an InTouchView license.
In Industrial Graphics, InTouch:‹tagname› is still a valid method of referring to an InTouch tag on a local node.
InTouch HMI Support for Windows User Account Control
System Platform 2020 R2 SP1 with InTouch HMI supports User Account Control-enabled operations on run-time nodes.
.NET Framework Requirements and Compatibility
IMPORTANT: System Platform 2020 R2 SP1 installs .NET 4.8 if the currently installed version of .NET is 4.7.2 or lower. If .NET 4.8 or later is installed, no change is made to the .NET Framework. Prior to upgrading your existing applications to System Platform 2020 R2 SP1, we strongly recommended that you:
After upgrading to System Platform 2020 R2 SP1, you should perform application testing on application scripts and on script libraries used by the application to ensure they continue to function properly under .NET 4.8. We also recommend you test the upgrade in a staging system prior to upgrading your production system.
System Platform 2020 R2 SP1 leverages Microsoft .NET Framework 4. The System Platform installation program will install .NET 4.8 if your system uses version 4.7.2 or lower. No change is made if your system uses .NET 4.8 or higher. Multiple versions of the .NET Framework can coexist. On nodes where SQL Server is installed, .NET 3.5 is also installed by System Platform to support SQL Server. In this scenario, other applications you have on the same machine with dependencies on .NET 3.5 will access .NET 3.5. System Platform 2020 R2 SP1 will use .NET 4.7.1, 4.7.2, or later.
All user-supplied .NET code that runs in the context of InTouch HMI and Application Server requires .NET Framework 4.8 or higher. Although .NET Framework 4.5.1 (and later) is highly compatible with applications that are built with earlier .NET Framework versions, you may have to update your scripts, if your .NET scripts were created prior to System Platform 2014. These changes may also affect .NET controls developed with .NET 3.5.
In application scripting, some .Net codes could fail if not using proper text encoding, and could cause a script to exit without completion. The UTF8Encoder is the default BinaryStream decoder in .Net 4.5. To enable an application script to decode ASCII XML data, for example, insert the following snippet:
BinaryReader streamReader = new BinaryReader(ms, new ASCIIEncoding());
To learn more about changes introduced in different versions of the .NET Framework, refer to the following Microsoft resources:
What's New in the .NET Framework: http://msdn.microsoft.com/en-us/library/ms171868%28v=vs.110%29.aspx
What's obsolete in the .NET Framework Class Library: https://msdn.microsoft.com/en-us/library/ee461502%28v=vs.110%29.aspx
Migration Guide to the .NET Framework 4.6 and 4.5: https://msdn.microsoft.com/en-us/library/ff657133%28v=vs.110%29
.NET Framework 4 Migration Issues: http://msdn.microsoft.com/en-us/library/ee941656%28v=vs.100%29
Virtualization Host Support
See the Global Customer Support (GCS) Technology Matrix for supported virtualization environments.
SQL Server Requirements for All Components
See the GCS Technology Matrix for SQL Server requirements for System Platform 2020 R2 SP1 components, including InTouch HMI 2020 R2 SP1.
Note: Match SQL Server version to operating system version.
We recommend that you install and configure the supported SQL Server version before you begin the System Platform installation program, especially if you expect Information Server to coexist, either on initial or subsequent installations, with the InTouch HMI, Application Server, or the Historian Server.
The System Platform installer will install all prerequisites except the SQL Server requirement for installing the Historian Server. If you select the Historian Server for installation, and if the supported version of SQL Server is not already installed, you must exit the installation program, install the supported SQL Server version, and then resume the installation.
Considerations for SQL Server
If you accidentally delete the aaAdministrators group from the SQL Server security logins, you must run the aaConfig SQL Utility to restore it. Refer to the Application Server User's Guide, About ArchestrA User Accounts, for further information and procedures to restore the aaAdministrators group.
Considerations for SQL Server Express
To work around this issue, configure Information Server to use an instance of SQL Server Express (or a non-Express edition) on a remote node.
The following sections describe the requirements to run InTouch Access Anywhere Server and supported browsers. For detailed information, see the InTouch Access Anywhere documentation.
You can determine the version of InTouch Access Anywhere Server installed on a computer using Programs and Features from the Windows Control Panel.
Requirements
The InTouch Access Anywhere Server can be installed as a System Platform installation option. The InTouch Access Anywhere Secure Gateway is an optional component installed on a separate computer within a network DMZ.
The following requirements must be met before you install the InTouch Access Anywhere Server or a Secure Gateway.
Supported InTouch Access Anywhere Browsers
InTouch Access Anywhere can run on smart phones, tablets, laptop computers, or any other device that supports an HTML5-compliant web browser. Browsers validated to support InTouch Access Anywhere include the following:
Functionally Compatible Browsers
Older versions of the listed browsers are functionally compatible with InTouch Access Anywhere. You may be able to use the following older versions of these browsers, but specific behaviors are unknown because no formal testing has been done with InTouch Access Anywhere.
You are strongly encouraged to upgrade to one of the supported browser versions listed in Browsers Tested with WindowViewer. For a complete list of considerations to run an InTouch application with InTouch Access Anywhere on a portable device, see the InTouch Access Anywhere User Guide.
Product Compatibility refers to the ability of a product to work with various versions of other products running on different network nodes. Product Compatibility also refers to the ability of a product to work with various versions of the same product running on different nodes.
Coexistence refers to same-node installation of a product with other products that support the same hardware, operating system, and SQL Server versions. Other products not listed will be covered by System Compatibility Testing unless specifically noted.
In a single-node environment, if you want to install multiple components on a single computer, all components must be at the same versions.
In a node-to-node environment, components are compatible between the current licensed version and one licensed version back. Refer to the GCS Technology Matrix for more information.
The following table lists products and their compatibility and coexistence with InTouch HMI 2020 R2 SP1.
Product |
Version |
Compatibility |
Co-existence |
System Platform
|
4.5 |
N |
N |
2012 |
Y |
N |
|
2012 R2 |
Y |
N |
|
2012 R2 P01 |
Y |
N |
|
2012 R2 P02 |
Y |
N |
|
2012 R2 P03 |
Y |
N |
|
2014 |
Y |
N |
|
2014 P01 |
Y |
N |
|
2014 R2 |
Y |
N |
|
2014 R2 P01 |
Y |
N |
|
2014 R2 SP1 |
Y |
N |
|
2017 |
Y |
N |
|
2017 Update 1 |
Y |
N |
|
2017 Update 2 |
Y |
N |
|
2017 Update 3 |
Y |
N |
|
2017 Update 3 SP1 |
Y |
N |
|
2017 Update 3 SP1 P01 |
Y |
N |
|
2020 |
Y |
N/A |
|
2020 R2 |
Y |
N/A |
|
2020 R2 P01 |
Y |
N/A |
|
Manufacturing Execution System
|
MES 2017 R2 |
Y |
Y |
MES 200 |
Y |
Y |
|
InTouch CE |
10.1 |
N |
N |
InControl |
7.11 SP2 P01 |
N |
N |
Batch Management |
2020 |
Y |
Y |
QI Analyst |
8.0 SP4 |
Y |
Y |
SCADAlarm |
6.0 SP2 P01 |
N |
N |
Intelligence |
2014 R3 |
Y |
N |
2017 U1 |
Y |
Y |
|
Workflow Management |
2020 |
Y |
Y |
Mobile Operator Rounds |
5.01 |
Y |
Y |
2014 R2 |
Y |
Y |
|
Insight (see components below) |
1.0 |
|
|
Insight Client (On-Prem) |
17.x (via Historian) |
Y |
N |
Historian Client |
10.x/17.x |
Y |
N |
InTouch |
11.x |
Y |
N |
Recipe Management |
2020 |
Y |
Y |
PlantSCADA |
2016 |
Y |
Y |
2018 |
Y |
Y |
|
2018 R2 |
Y |
Y |
|
ClearSCADA |
CS 2017 R1 |
Y |
Y |
CS 2017 R2 |
Y |
Y |
|
CS 2017 R3 |
Y |
Y |
|
GS 2019 |
Y |
Y |
|
AVEVA System Monitor
|
1.1 |
Y |
Y |
1.2 |
Y |
Y |
|
Sentinel Agent |
1.0 |
N/A |
Y |
Sentinel Server |
1.0 |
N/A |
N |
ASB (now PCS)
|
SP 2012 R2 SP1 |
N |
N |
SP 2014 R2 SP1 P01 |
Y |
Y |
|
SP 2017 |
Y |
Y |
|
SP 2017 U1 |
Y |
Y |
|
SP 2017 U2 |
Y |
Y |
|
PCS and SMS
|
SP 2017 U3 |
Y |
Y |
SP 2017 U3 SP1 |
Y |
Y |
|
SP 2020 |
Y |
Y |
Supported |
Y |
Not Supported |
N |
Not Applicable |
N/A |
In some cases, InTouch HMI is supported in newer environments than a compatible product. InTouch HMI has been tested for compatibility with a listed product only in the environments that are supported by that particular product.
For detailed English installation instructions, see the System Platform Installation Guide (SP_Install_Guide.pdf) or System Platform Installation Help (SP_Install_Guide.chm). Condensed English installation instructions are also provided in the printed InTouch HMI Getting Started Guide booklet that is included in the installation package. This booklet is provided for all supported languages.
The information provided in this Readme file supersedes the InTouch Installation Help (Install-InTouch.chm) for the French, German, Japanese, and Simplified Chinese languages.
The major decision you must make when you install InTouch HMI is whether to install the InTouch development and run-time components, or the run-time components alone. The installation program guides you in selecting the features you want, verifying or modifying your selections, installing prerequisite software, and then installing InTouch HMI and the IDE if you chose to install development components.
What You Need to Install InTouch HMI
You must have the following materials ready to install InTouch HMI:
Important: Use the hardware and software requirements listed in the Application Server Readme if you are going to install the IDE.
Prerequisites
The installation program analyzes the software installed on your computer and lists any required software that is not installed.
Note: At the start of the installation, the prerequisites check is system-specific rather than product-specific.
The following prerequisites, if not already present on your system, will be installed by the System Platform installation program:
SQL 2017 Express Core is installed automatically if either of the following conditions are met:
The installation program installs both system-specific and product-specific prerequisites. You do not have to exit from the installation program to install the prerequisite software. For more information about System Platform installation prerequisites, see the System Platform Installation Guide.
About the ArchestrA User Account
The ArchestrA user account is a user name and password combination that enables inter-node communication between all computers in an Application environment. You must specify the same user account on every node when you install the System Platform components for the first time on computers that communicate with each other.
WARNING! The ArchestrA user account is a Windows operating system account located on the local computer or on a domain. Do not delete this account with operating system account management tools. If you do, ArchestrA-enabled software may stop functioning properly.
If the ArchestrA user account has not previously been configured, you will be prompted to configure it during the InTouch HMI installation. You must specify a user name, password, and domain.
If you choose to use an existing user account, it should meet the following requirements:
After you install the InTouch HMI, you can use the Change Network Account utility to change or recreate the ArchestrA user account. This utility is accessible from the Start menu in the AVEVA Common folder after you install InTouch. You must have Administrator privileges on the computer to make changes with the Change Network Account utility. For more information, see the Change Network Account utility help.
Note: If you recreate the user account using the Change Network Account utility, the Microsoft Windows security component on the computer can take several minutes to update this information on the ArchestrA Galaxy node. Until that occurs, the ArchestrA component may not function properly. Restarting the Galaxy node updates this information immediately.
Performing the InTouch HMI Installation
Before you start installing InTouch HMI, you should have a clear idea whether you want to develop, deploy, and publish your own applications, or require only the InTouch run time, to run applications already created and deployed.
The following procedure will guide you through the installation, with information specific to the InTouch HMI.
To install the InTouch HMI
The installation program prompts you to select an installation type: either product-based selection or installation by computer roles. As you are only installing InTouch HMI, click the product-based selection as your installation type.
Note: The 16 PenTrend supplementary component is not installed by default. You must select the Customize Installation option and select InTouch 16 PenTrend from the product list to install it as part of the InTouch HMI installation procedure.
Activating Your InTouch License
InTouch uses the AVEVA Enterprise License Server to make licenses available. The AVEVA Enterprise License Manager manages one or more License Servers.
You use the AVEVA Enterprise License Manager interface to make licenses available to InTouch. First, import the entitlement XML file received upon purchase of the license. Then, select which licenses on the entitlement to activate on the License Server. After activation, the license becomes available to WindowMaker or WindowViewer upon start up. The license is released when InTouch is shut down.
InTouch will run in Demo Mode if it cannot consume a valid license at start up time.
To install AVEVA Enterprise licensing, see the AVEVA Enterprise Licensing Guide.
Antivirus Software Exclusions
Antivirus software should be implemented as part of a defense-in-depth strategy to secure your industrial control systems.
Visit https://softwaresupport.aveva.com/ to get the latest information on antivirus software recommendations.
To modify, repair, or remove a product
Note: Modern applications can no longer be created, edited, or run after Application Server is uninstalled from the same computer that also hosts InTouch run time and development components. Modern applications no longer work because the Galaxy Repository required for Modern applications is removed when Application Server is uninstalled.
Upgrading refers to installation on a computer that already has a previous version. An upgrade removes the previous version of InTouch HMI and installs the latest version.
After the hardware and software requirements are met, you can upgrade to the latest version of InTouch HMI from the following versions:
You can only upgrade System Platform products that are already installed. You cannot install any new System Platform products by an upgrade process.
To upgrade from a previous version of the InTouch HMI
Upgrade Notes
Migration converts applications created with earlier versions of InTouch HMI to the current version. You can migrate applications to InTouch HMI 2020 R2 SP1 that were developed with earlier versions of InTouch HMI as shown in the following table:
From |
Upgrade |
Node-by-Node Upgrade |
Migrate |
7.0 |
N |
N/A |
N |
7.1 |
N |
N/A |
N |
7.11 P07 |
N |
N/A |
Y |
8.0 SP2 P04 |
N |
N/A |
Y |
9.0 P03 |
N |
N/A |
Y |
9.5 SP1 |
N |
N/A |
Y |
10.0 SP2 |
N |
N/A |
Y |
10.1 (no SP) |
N |
N/A |
Y |
10.1 SP2 |
N |
N/A |
Y |
10.1 SP2 P01 |
N |
N/A |
Y |
10.1 SP3 |
N |
N/A |
Y |
10.1 SP3 P01 |
N |
N/A |
Y |
11.1 SP1 |
Y |
Y |
Y |
11.1 SP1 P02 |
Y |
Y |
Y |
17.0 |
Y |
Y |
Y |
17.1 |
Y |
Y |
Y |
17.2 |
Y |
Y |
Y |
17.3 |
Y |
Y |
Y |
17.3.1 |
Y |
Y |
Y |
17.3.101 |
Y |
Y |
Y |
20.0.000 |
Y |
Y |
Y |
20.1.000 |
Y |
Y |
Y |
20.1.001 |
Y |
Y |
Y |
Note: For InTouch Version 10.2 and newer, refer to the System Platform migration table. InTouch cannot be installed or upgraded as a single product since Version 10.2. Therefore all installed products on a node must be upgraded at the same time.
SPCPro was a Statistical Process Control (SPC) utility available with InTouch HMI prior to Version 11.0. SPCPro is no longer supported by InTouch HMI. We recommend that that you migrate your SPCPro databases to the latest version of QI Analyst if you still use SPCPro with InTouch. QI Analyst provides support for the latest versions of operating systems and databases.
QI Analyst also includes a utility to migrate your SPCPro database to a QI Analyst database, leaving the existing SPCPro database intact. Please contact your local sales representative for further information.
Important Note: We strongly recommend that you migrate your current SPCPro databases to QI Analyst before installing System Platform Version 20.0.000 with InTouch HMI. InTouch no longer includes SPCPro and will not open or migrate applications containing SPCPro components.
InTouch HMI 2020 R2 SP1 includes corrections for the issues listed in the following table. These issues are listed by their Defect ID (IMS number), any assigned Service Request (SR) or Case Number with a brief description of the defect.
Defect ID |
SR/Case Number |
Description |
IMS-823477 |
960030435 |
The Read-Only InTouch application on a non-RDS machine did not acquire the read-write supervisory license. |
IMS-838424 |
960028998 |
When the Cross Reference Utility was run, WindowMaker shut down with an exception error even before the tag usage count was updated. |
IMS-845573 |
960005409 |
Opening frame windows multiple times over a period of time, caused the WindowViewer to slow down and exceed memory usage. |
IMS-846459 IMS-1030936 IMS-1030960 |
960038785 |
The key script configured for Industrial Graphics functioned differently for a mouse-click and a key press. |
IMS-848041 IMS-926460 IMS-926462 |
960033707 |
The Cross Reference Utility failed to display the script name when a key script was created with more than 15 tags. |
IMS-858456 |
960036305 |
When InTouch logging was configured to use a remote historian, all the logged tags were not added to the Historian. However, when the historian was local all the tags were added and the values were logged. |
IMS-861525 |
960042641 |
The Alarm Viewer crashed when the Ack All method was called for multiple objects at the same time. |
IMS-922312 |
960044552 |
The WindowViewer did not acquire a license automatically at startup. |
IMS-925014 |
960042055 |
The users who upgraded only System Platform and not MES noticed that closing an InTouch session, which was created by scripting and contained the MES .NET Control, removed the current session from the Session table. |
IMS-976316 IMS-1057574 |
960049846 960055547 |
The Historical Logging Properties dialog box of the French and Japanese InTouch HMI 2020 R2 applications did not display the Log Alarms and Events checkbox which allows configuration to store Alarms and Events to the Historian. |
IMS-976972 |
960048278 |
During the upgrade to InTouch HMI 2020 R2, when an Industrial Graphic containing third-party fonts was imported, the font got automatically changed. |
IMS-977907 |
1507496 |
In the Alarm Client Control, the query to determine the Column filters did not display the expected results if the operator strings were in lower case. |
IMS-979008 |
960044045 |
Performance issues were noticed in the Cross Reference Utility, with the application taking a long time to process and display the data. |
IMS-980014 |
960045836 |
In the Alarm Client Control, the Reason entered in the UnShelve Comment dialog box while unshelving alarms were not displayed when All Alarms were viewed. Instead, the Alarm Unshelve reason was over-written by the Alarm Shelve reason. |
IMS-985151 |
960050552 |
When an Alarm Client Control was used within an Industrial Graphic, moving the graphic or making configuration changes to any column cleared the Historical Alarms and Events list. |
IMS-1045435 |
960054550 |
The Cross Reference Utility did not display the key scripts configured in the WindowMaker. |
IMS-1058087 |
960041831 |
Users running the AlarmDB on different versions of the SQL server reported that the Shrink Command on the Transaction log file failed. |
IMS-1086236 |
960047452 |
The InTouch Application Manager in the NAD client stopped responding and did not display any applications when the NAD Master was disconnected. |
IMS-1094094 |
960054070 |
When the tag value of the Industrial Graphics in the frame window of the WindowMaker was updated, the tag value display toggled between the old and the new values. |
IMS-1095879 |
960058675 |
Some touch screen users observed an intermittent issue with the checkboxes not getting selected or cleared on a Frame window of the WindowMaker. |
IMS-1099234 |
960057458 |
In a French InTouch HMI application, when users attempted to login with the correct User Name and an incorrect password, the error message was displayed in English. |
IMS-1135057 |
960061462 |
The Cross Reference Utility displayed incorrect tag usage information. |
IMS-1138294 |
960058203 |
Historical data was not received for a Trend Client Control graphic configured with relative references. |
IMS-1145997 |
960061476 |
Some users noticed performance issues with the InTouch HMI application upon launching the Trend Client Control. |
IMS-1180592 |
NA |
Users could not create or update symbols or toolsets in the AVEVA Connect cloud drive. |
IMS-1184683 |
960064017 |
When querying a large number of alarms in history blocks, the Alarm Client Control failed to return results and the InTouch HMI application did not release the memory. |
IMS-1188032 |
960063030 |
The WindowViewer froze when the PostLogonDialog() function was run from the Action scripts. |
IMS-1209652 |
960067666 |
In some cases, memory was not released by WindowViewer causing performance issues. |
IMS-1214039 |
960068244 |
Post-upgrade to InTouch HMI 2020 R2, some users noticed performance issues while publishing or exporting an InTouch HMI application. |
IMS-1214981 |
960069917 |
When an InTouch application was published using the Application Publisher within a restored WindowMaker, several libraries of the Graphic Editor were missing. |
IMS-1216192 |
960053773 |
The Galaxy Browser InTouch Tag Browser did not allow the selection of $System and Alarm Group tags. |
IMS-1216414 |
960070301 |
Post-migration to InTouch HMI 2020R2, the dialog windows opened using the ShowGraphic() method did not display properly. |
IMS-1218862 |
960066184 |
When the Alarm Client Control was set to Historic or History Blocks, running a query with multiple conditions generated a query with incorrect parenthesis. |
IMS-1227909 |
960070605 |
In the pen configuration of the Trend Client Control, the configured tag values for Units, Min, and Max did not display correctly in the runtime. |
IMS-1229405 |
960073123 |
When switching languages at runtime, the translation did not happen successfully for each alternative alarm entry in the list. For these non-translated alarm entries, the LogViewer displayed an error on failure to get the translation text for the Alarm. |
IMS-1245033 |
960073164 |
When an Industrial Graphic opened using the ShowGraphics() method was closed using the Hideself () method, errors were logged in the Logger. |
IMS-1246601 |
960058583 |
In an InTouch HMI application with embedded aaHistClientTrend Control ActiveX control, closing the WindowMaker did not release the Historian client license in License Manager. |
IMS-1270480 |
960073673 |
The InTouch OPC UA Clients could connect to the InTouch OPC UA Server in Anonymous mode even when Anonymous mode was not enabled in the InTouch HMI Application Manager. |
IMS-1294915 |
960073654 |
Post-upgrade to InTouch HMI 2020, a published application was open by default in WindowMaker. Once WindowMaker was closed, it could not be reopened. |
IMS-1294954 |
960031648 |
After installing the InTouch 2017 U3 SP1 application, the first Update Use Count was very slow, and WindowMaker could not be opened. |
IMS-1296889 IMS-1392254 |
960077056 |
On importing an InTouch HMI application, WindowViewer crashed when the unused tags were deleted. |
IMS-1307665 |
960080400 |
When an XML file containing the grouped embedded graphics with configured text was imported using the Graphic Access API, the Substitute text was reverted to the default text. |
IMS-1369647 |
960081895 |
Post-upgrade to InTouch HMI 2020, when a window configured with tag references was printed to a text file from WindowMaker, the text file displayed a long chain of zeros instead of the tags used in the windows. |
IMS-1389107 |
960084305 |
Newly created users in the aaUsers, aaInTouchUsers, and Users user groups could not launch the InTouch Managed Application from a remote desktop session. |
IMS-1396780 |
960086276 |
The Alarm DB could not be restored during the processing of the AlarmMaster file. |
IMS-1401656 |
NA |
While migrating to InTouch HMI 2020R2, the imported ActiveX event script could not be deleted. |
IMS-1400206 IMS-1430742 |
960093332 |
The InTouch HMI application displayed an error while renaming the Industrial Graphics. InTouchViewApp was not synchronized to the Runtime node after adding new symbols to the template. |
IMS-1415533 |
960094208 |
In the Alarm Viewer ActiveX control, the NewAlarm event is triggered even when the alarms are acknowledged and returned to normal. |
IMS-1419505 |
960095152 |
When the alarms were acknowledged with no comment in the Ack Comment dialog box, the users could not sort the alarms list in the Alarm Manager based on the Alarm Comment. |
IMS-1420060 |
960095262 |
Post-migration to InTouch HMI 2020 R2, some users received errors when converting Smart Symbols to Industrial Graphics. |
IMS-1420339 |
960095566 |
When a script contained placeholder tags, running the InTouch application in WindowViewer logged only the first line of the script and not the script name. |
IMS-1422322 |
960098075 |
Opening the Tagname Dictionary for a tag containing a dot field (for example, firstentry.secondentry) displayed the Tagname Dictionary only for the first entry, and not the second entry. |
InTouch HMI 2020 R2 Patch 01 Issues Included in this Release
InTouch HMI 2020 R2 Patch 01 includes corrections for the issues listed in the following table.
These issues are listed by their Defect ID (CR, TFS or IMS) number, any assigned Service Request (SR) or Case Number with a brief description of the defect.
Defect ID |
SR/ Case Number |
Description |
IMS-569447 |
960012340 |
Users were not able to substitute the tag reference of an Industrial Graphic using the shortcut command ‘Ctrl+E’. |
IMS-570302 |
960013179 |
In a Key Script using the 'On Key Up' condition type for a tag, did not reflect correctly in the Cross Reference Utility report under the 'Where' column. |
IMS-586010 |
960009354 |
In some cases, memory was not released after a window was printed causing performance issues. |
IMS-587358 |
001750964 |
When the Freeze Property was used on a Trend Client Control, the TimeDuration property did not change the Start Time but updated to the Current Time. |
IMS-612770 |
960020556 |
After upgrading to System Platform 2020, some users encountered a delay in retrieving and processing historical alarms in the Alarm Client Control. |
IMS-615679 |
960021443 |
After upgrading from InTouch HMI 2014 R2 SP1 to InTouch 2017 Update 3 SP1, the AnnotateLayout function did not work as expected. |
IMS-618832 |
960018137 |
For a German Operating System, importing or exporting a graphic using the GraphicAccess library failed when the decimal separator was a comma. |
IMS-628969 |
960007445 |
When a published application pointing to a locally hosted historian is run on an InTouch node, the 8-pen trend assignment changed randomly after a few weeks. |
IMS-629954 |
960023094 |
On migrating from System Platform 2014 R2 to System Platform 2020, the vertical alignment of text boxes with dynamic text did not display correctly in the InTouch Web Client. |
IMS-632766 |
960019233 |
Inserting rows in a SQL database using InTouch SQL commands via scripts caused memory issues over a period of time. |
IMS-635200 |
960024622 |
When an embedded symbol object or a group object containing a textbox was resized, the text box was also getting automatically resized when viewed in the InTouch Web Client. |
IMS-639586 |
960026719 |
When a graphic element initially configured X=0 coordinate or Y=0 coordinate, was reconfigured in the runtime to a different position, the graphic would move to its original location when the window was reopened. |
IMS-640711 |
960011506 |
Pressing the Enter key, while using the ShowGraphic function caused the application to lock under certain conditions. |
IMS-651248 |
960021064 |
On using the Like filter in the Alarm Client Control, the AlarmDuration column displayed the duration in milliseconds rather then the full time format. |
IMS-691692 IMS-702837 IMS-702887 |
960027983 |
Maximum Value and Minimum Value of the Input analog animation link were not recorded via the print function. |
IMS-692114 |
960027837 |
Users could not import Batch Management 2000 .Net GUI and Stateless API into an InTouch HMI 2020 application. |
IMS-726886 IMS-841016 IMS-841017 |
960029914 |
Using the command prompt to run an application in WindowViewer, did not display the embedded graphic in the window. |
IMS-777093 |
960031354 |
When a Managed Application was open in WindowMaker, and the user attempted to launch Application Manager, the user was asked to launch WindowViewer instead. After WindowViewer was launched, Industrial Graphics were not displayed and there was an error in obtaining a license. |
IMS-788066 |
960031117 |
The Replace override option did not work as expected when the LoadQueryFilterFIle API was used for a Alarm Client Control filter. |
IMS-803250 |
960027477 |
Importing InTouch windows took longer than expected and sometimes caused the WindowMaker to stop responding. |
IMS-842092 |
960038700 |
Industrial Graphics were not displayed in the WindowViewer, when the NAD client was enabled and the NAD server was disconnected from the network. |
IMS-834029 |
960021032 |
In cases when the Application Server AppEngine Object was configured with scripts using the Alarm Toolkit APIs, when the primary engine failed over to the backup server, performance and memory issues were observed in the backup server. |
IMS-837661 |
960037547 |
The TimeOAT column in the Alarm Client Control displayed the UTC time, however the timestamp was recorded in the local time zone. |
IMS-926668 |
960046619 |
The WindowViewer user session was logged-off earlier than the configured Inactivity Timeout. |
104036 |
- |
The WindowMaker Substitute Tags Replace feature for embedded symbols did not work as expected. |
This section describes known issues that remain in the release of InTouch HMI 2020 R2 SP1.
Issue ID |
Description |
TFS-1351507 |
Language switching is not supported for the Carousel Widget in runtime. |
TFS-1369183 |
A Carousel Widget containing the Web Browser Widget, QR Code Scanner Widget, Trend Client Control, Alarm Client Control or SQL Data Grid Control will not display correctly in WindowViewer, as default browser security options prevent cross-origin requests. |
TFS-1372178 |
Carousel widgets in a managed application migrated from InTouch 2020 to InTouch 2020 R2, do not contain the latest properties. Workaround: On migrating a Galaxy from InTouch 2020 to InTouch 2020 R2, run the IDE as an Administrator atleast once, to allow loading the latest InTouch 2020 R2 carousel widget properties. |
TFS-1371799 |
When an InTouch 2020 application (.aapkg) is exported and imported to InTouch 2020 R2, then the default namespace for a tag reference within a Carousel widget is not resolved in runtime. Workaround: Open the graphic containing the Carousel widget. Edit any property and save the graphic. The tag reference is resolved, and the graphic is displayed in runtime. |
TFS-1374896 |
After a graphic/toolset is created, the letter case of the graphic name cannot be changed in WindowMaker. For example: INTOUCH cannot be changed to InTouch. Workaround: Rename the graphic to a temporary name. Rename the graphic again with the correct letter case. For example: Rename INTOUCH to ChangeName and then rename to InTouch. |
TFS-1377672 |
Connecting many clients to a busy OPC UA server may cause various warnings and errors to be logged from the InTouch OPCUA Host process. Warning messages are for information purposes only and do not indicate any loss in functionality. Error message indicate that the operation was aborted. Workaround: It is recommended that client connections to the server be planned and monitored, so not to burden the server and cause connection failures. |
The InTouch product library consists of a set of Portable Document Files (PDF) available in the following location of the System Platform installation media:
\AVEVA System Platform\InstallFiles\CD-Intouch\UserDocs\English
You need Adobe Reader installed on your computer to view InTouch documentation. You can download the latest version of Adobe Reader from the Adobe Corporation web site:
http://www.adobe.com/products/acrobat/readstep2.html
After installing Adobe Reader, double-click a PDF file with your pointing device to view the book with Adobe Reader. You can also open a book with the Adobe Reader Open command from the File menu. Context-sensitive documentation is also available with InTouch online help. Select Help for information about the current InTouch window that you have open on your computer.
|
© 2021 AVEVA Group plc and its subsidiaries. All rights reserved. | Contact Us |