InTouch HMI 2017

Материал из archestra.info
Перейти к: навигация, поиск

Wonderware InTouch HMI 2017 (v17.0) Readme

Wonderware InTouch HMI 2017 (v17.0) Readme

Last revision: Thursday, April 27, 2017

In This Document

About This Readme

New Features in InTouch HMI 2017

System Requirements

Wonderware InTouch HMI Installation

Resolved Issues

Known Issues

InTouch Documentation Issues

InTouch Documentation

About This Readme

This Readme provides information about InTouch HMI 2017 (v17.0). Readme files from previous releases of Wonderware InTouch HMI are posted on the Schneider Electric Software Global Customer Support (GCS) website.

Important!

When installing System Platform Version 2017, Operations Integration (OI) Gateway is installed as a hidden feature of InTouch HMI 2017.

  • If you previously installed FS Gateway, the WSP 2017 installation will remove FS Gateway, preserve your existing FS Gateway configuration, and port your configuration to a new instance of OI Gateway, retaining the FS Gateway name. Existing FS Gateway configurations that use OPC access will not be impacted.
  • OI Gateway will be installed as part of Wonderware System Platform 2017.
  • If your system has an older version of OI Gateway installed, the WSP 2017 installation will upgrade OI Gateway as a first action. You will need to re-run the WSP 2017 installation to install other components.

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.

Related Topics

Wonderware InTouch HMI 2017 (v17.0) Readme

New Features in InTouch HMI 2017

System Requirements

Wonderware InTouch HMI Installation

Resolved Issues

Known Issues

InTouch Documentation Issues

InTouch Documentation

Important Information for Microsoft Windows 2016

When Wonderware System Platform is installed on a Windows Server 2016 system with Remote Desktop Services enabled, WindowViewer will fail to launch. WindowMaker cannot be closed unless shut down via the Task Manager.

Workaround:

  1. Download and install the latest Microsoft Windows update KB3194798 on the Windows 2016 system. This Windows update is located at the following URL:

    http://www.catalog.update.microsoft.com/Search.aspx?q=KB3194798

  2. After installation of the update is complete, restart the system and install Wonderware System Platform 2017.

    Important: The Microsoft update can be installed before or after Wonderware System Platform is installed. However, it is recommended that you install the update prior to installing System Platform.

How to Find the Latest Product Requirements and Compatibility Information

For important information about this product release, go to the Schneider Electric Software Global Customer Support (GCS) web site. Information on the GCS web site includes product requirements, compatibility, as well as downloads from previous releases. Once you log in, you can filter search results by product name and the release/version.

  • The GCS Product Hub contains Readme files, videos, and product downloads from previous product releases.
  • The GCS Technology Matrix is a searchable database that contains the latest product information. Enter the product name in the search bar, then select the current release to view:
    • Product Information: version name, number, release date, etc.
    • Product Notes: key release information, new features, and updates
    • OS Compatibility: list of compatible Windows and Windows Server versions
    • Database Compatibility: list of compatible SQL Server and other database product versions
    • Virtualization Compatibility: list of compatible virtualization software products and versions
    • Product Coexistence: list of products that can be installed on the same computer
    • Product Interoperability: list of products that can communicate with each other through a common message protocol

New Features in InTouch HMI 2017

InTouch 2017 provides support for the latest versions of Microsoft products and includes new run-time and development-environment features. Run-time features are designed to improve usability, IT compliance, and connectivity. Development features are designed to improve engineering efficiency and usability.

Run-Time Features and Enhancements

  • Pan and Zoom
  • Enhanced Events and Alarms Client Control
  • Improved performance!
  • More extensive filtering and sorting capabilities
  • Improved default settings
  • Ability to run WindowViewer as a service
  • OI Gateway – OPC UA connectivity
  • Can be used with new visualization technology (InTouch HMI and InTouch OMI in the same Galaxy)

Development-Environment Features and Enhancements

  • New InTouch Script Editor (for Classic, Modern, and Managed InTouch)
  • Application Target Resolution (for Classic, Modern, and Managed InTouch)
  • Application Templates (for Modern and Managed InTouch)
  • Window Templates (for Modern and Managed InTouch)
  • "Frame-type" Windows (for Modern and Managed InTouch)
  • Thumbnail refresh (for Modern and Managed InTouch)
  • Script DLL Import (new for Modern InTouch)
  • Control DLL Import (new for Modern InTouch)

New Licensing Technology

  • Activation-based – no more dongles!
  • Centralized license management
  • Incremental capabilities
  • Reservation capabilities

System Requirements

Introduction

This section describes the hardware and software requirements to support Wonderware System Platform 2017 products, including InTouch HMI 2017.

Related Topics

Wonderware InTouch HMI 2017 (v17.0) Readme

About This Readme

New Features in InTouch HMI 2017

Wonderware InTouch HMI Installation

Resolved Issues

Known Issues

InTouch Documentation Issues

InTouch Documentation

Hardware Requirements

Hardware Requirements

System Sizing Guidelines

The following table provides guidelines for hardware configurations suitable for Wonderware System Platform 2017 software based on the size of the installation. These guidelines are subject to the limitations of your Windows operating system.

  • The Intel Itanium 2 processor is not supported.
  • We recommend 1280 x 1024 as the minimum display resolution for engineering tools such as the Integrated Development Environment (IDE).
  • A Windows Server operating system is required for large installations with more than 50,000 I/O per node.
  • SQL Server Express is not supported for installations with more than 25,000 I/O per node (small installations only).

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 30

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 2017. 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

  • Smart Card: Raak Technologies C2-40 Mini Driver Smart Card
  • Smart Card Reader: OK 3021 USB Smart Card Readers

Operating System, .NET Framework, and Virtualization Requirements

  • Software Requirement Notes
  • Notes Common to All Components
  • Wonderware InTouch HMI
  • .NET Framework
  • Virtualization
  • SQL Server
  • InTouch Access Anywhere

Software Requirement Notes

Windows Operating System Notes

  • Windows versions 8.1, and 10 support touch screen gestures. If the user swipes in from the right edge of a touch screen with a finger gesture, a set of Windows charms appears, which includes Search, Share, Start, Devices, and Settings. Moving the mouse cursor to the upper-right corner of a screen also shows the Windows charms for non-touch screens.

    Showing the set of charms is a standard feature of Windows versions 8.1, and 10 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.

  • Newer operating system Service Packs (SPs) than those listed do not block the installation of Wonderware products. A warning message may appear during the installation process.
  • The Galaxy Repository (GR Node) can run on a client Windows operating system in a configuration in which Wonderware System Platform products are installed on up to five nodes. For a system with more than five nodes, the Galaxy Repository must installed on a computer running a Windows Server operating system.
  • Development and application nodes are considered to be clients of the server GR node.
  • When an operating system is upgraded on a computer, existing Wonderware System Platform products must be uninstalled prior to the upgrade and then reinstalled after the upgrade. There are three exceptions. Wonderware System Platform products do not need to be uninstalled when upgrading from: ◦Windows 8 to 8.1
    • Windows 8.1 to 10
    • Windows 2012 to Windows 2012 R2

.Net Notes

  • Versions of .NET (other than 4.x versions) can coexist, but all .NET code, including QuickScript.net scripts, run under .NET 4.5.1.

    For more information about .NET Framework requirements and compatibility, see .NET Framework Requirements and Compatibility .

  • .NET 3.5 is installed only because the supported SQL Server versions require it. No other dependencies must exist.

Operating System Notes Common to Wonderware 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 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 Wonderware 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

  1. After starting InTouch WindowViewer (alarm provider), open the SMC Logger and look for the most recent string generated by AlarmMgr. For example: "Registering AlarmMgr with SLSSVC as AlarmMgr 253.127.148.120". The indicated IP address will be unique to your alarm-providing node. Note the IP address for Step 2.
  2. In the Alarm Query tab of the AlarmViewer control on the remote computer, configure the alarm query as follows, substituting your nodename of the alarm providing InTouch HMI for "nodename" below and substituting your IP address noted in the previous step:

    \\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.

  3. Test to validate that the alarms generated from the alarm-providing node are shown accurately in the AlarmViewer control.

Using Alarm Manager on a Single Node Running Both Wonderware 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, Wonderware Application Server and InTouch 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 Schneider Electric Software 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 the "Remote Desktop Host" role in order for TSEGetClientId() and other related functions to work properly.

The impact to Wonderware Application Server is minimal as most Wonderware Application Server processes run as services. One impact to Wonderware Application Server is to carry forward the restriction introduced with the Windows Vista operating system which permits only one alarm provider. While both Wonderware Application Server and InTouch HMI can be configured as alarm providers, only one alarm provider can be configured at any one time.

Wonderware 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 Fast User Switching.

Wonderware 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

  1. Click Start and then Run. The Run dialog box appears.
  2. Enter gpedit.msc and click OK. The Group Policy dialog box appears.
  3. Go to the following location: Local Computer Policy > Administrative Templates > System > Logon.
  4. Set Hide Entry Points for Fast User Switching to Enabled. Enabling this policy hides the Switch User option in the Logon interface, the Start menu, and the Task Manager.
  5. On the File menu, click Exit to close the Group Policy dialog box.

By enabling the policy, Administrators hide the Switch User button in Windows logon, in the Start menu, and in the Task Manager.

Wonderware InTouch HMI 2017 Operating System Notes

  • Windows client (starting with Windows 7) do not support a dedicated single-node server configuration that runs one or more databases for an InTouch HMI system.
  • The EnableDisableKeys() function writes to the Windows registry to enable or disable some keys on the host computer running an application in WindowViewer. For security purposes, Windows 7 and later versions of Windows prevent Standard or Power users from writing to the registry. Windows Administrators can write to the registry if not disabled by local domain security policies.

    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.

  • As of Wonderware System Platform 2014, a computer running Windows 7 or later operating systems can be configured as both an InTouch and an Application Server alarm provider. For more information, see Using Alarm Manager on a Single Node Running Both Wonderware InTouch HMI and Application Server Alarm Providers on Windows Vista and Later Operating Systems.

    The following InTouch legacy script functions do not operate on 64-bit versions of Windows: WWPoke(), WWExecute(), WWRequest(), ActivateApp() and SendKeys().

  • If Recipe Manager is started using the path Start\Program\Wonderware\InTouch\Recipe, then select Run as Administrator on Windows 7 or later operating systems.
  • The InTouch Extensibility Toolkit might need to be started by right-clicking and selecting Run As Administrator on Windows 7 or later operating systems to function properly.
  • The onscreen keyboard options have changed, beginning with Windows 7 and Windows Server 2008 R2 operating systems.
  • Hovering to select from the Windows keyboard does not work in supported versions of Windows operating systems.

Wonderware InTouch HMI 2017 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. ArchestrA Symbols 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, ArchestrA Symbols cannot communicate with InTouch tags when used with an InTouchView license.

In ArchestrA Symbols, InTouch:‹tagname› is still a valid method of referring to an InTouch tag on a local node.

Wonderware InTouch HMI 2017 Support for Windows User Account Control

Wonderware System Platform 2017 with InTouch HMI supports User Account Control-enabled operations on run-time nodes.

.NET Framework Requirements and Compatibility

IMPORTANT: Wonderware System Platform 2017 installs .NET 4.5.2 if the currently installed version of .NET is 4.5 or lower. If .NET 4.5.1 or later is installed, no change is made to the .NET Framework. Prior to upgrading your existing applications to Wonderware System Platform 2017, we strongly recommended that you:

  • Back up your applications
  • Familiarize yourself with the changes introduced by Microsoft in the .NET Framework
  • Review your .NET scripts and .NET controls for any required changes

After upgrading to Wonderware System Platform 2017, 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.5.2. We also recommend you test the upgrade in a staging system prior to upgrading your production system.

Wonderware System Platform 2017 leverages Microsoft .NET Framework 4. The Wonderware System Platform installation program will install .NET 4.5.2 if your system uses version 4.5 or lower. No change is made if your system uses .NET 4.5.1 or higher. Multiple versions of the .NET Framework can coexist. On nodes where SQL Server is installed, .NET 3.5 is also installed by Wonderware 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. Wonderware System Platform 2017 will use .NET 4.5.1, 4.5.2, or later.

All user-supplied .NET code that runs in the context of InTouch HMI and Application Server requires .NET Framework 4.5.1 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 Wonderware System Platform 2014. These changes may also affect .NET controls developed with .NET 3.5.

In ArchestrA 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 ArchestrA 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 Schneider Electric Global Customer Support (GCS) Technology Matrix for supported virtualization environments.

Related Topics

System Requirements

Hardware Requirements

SQL Server Requirements

InTouch Access Anywhere Requirements

SQL Server Requirements

SQL Server Requirements for All Wonderware Components

See the GCS Technology Matrix for SQL Server requirements for Wonderware System Platform 2017 components, including InTouch HMI 2017.

Note: Match SQL Server version (32- or 64-bit) to operating system version.

We recommend that you install and configure the supported SQL Server version before you begin the Wonderware System Platform installation program, especially if you expect Wonderware Information Server to coexist, either on initial or subsequent installations, with the InTouch HMI, Application Server, or the Historian Server.

The Wonderware 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, then resume the installation.

Considerations for SQL Server

  • Alarm DB Logger To use the Alarm DB Logger, you must set the default SQL Server authentication mode from Windows-based to Mixed Mode.
  • SQL Server Configuration Rights: While installing Wonderware System Platform, configuration changes to SQL Server are required. If the installer does not have SQL Server administrative rights, the proper configuration of SQL Server may not be applied. A post-install aaConfig SQL utility enables you to verify if the SQL configuration has been performed.
  • Maximum Server Memory: After installing SQL Server, Use SQL Server Management Studio to confirm that the Maximum Server Memory is configured to approximately 65% of the computer's total available RAM. By default SQL Server does not clamp this setting. The Wonderware System Platform installation process will attempt to adjust it if it has the appropriate rights to configure SQL Server.
  • Restoring a CAB: You cannot restore a Galaxy .cab file backed up in SQL Server 2012 or SQL Server 2008 to a node with an earlier version of SQL Server. For example, you cannot restore a Galaxy .cab file backed up in SQL Server 2012 to a node with SQL Server 2008. For example, you cannot restore a Galaxy .cab file backed up on SQL Server 2008 to a node with SQL Server 2005. SQL Server database backups from SQL Server 2005 forward are not backward-compatible. Attempting such a restore initializes, and the progress dialog box quickly displays 100% completion of restoring the database, but the Galaxy .cab restore operation does not actually complete, and no Galaxy Repository is created. When you start the IDE, the Galaxy is blank.
  • Migrating SQL Server Versions: You can migrate a SQL Server database to a later version from any of two prior versions. For example, you can migrate to SQL Server 2012 from SQL Server versions 2008 or 2005. You can migrate to SQL Server 2008 from SQL Server versions 2005 or 2000. You cannot migrate directly from SQL Server 2000 to SQL Server 2012. Such a migration requires an intermediate version installation. For more information and helpful procedures, see the following Microsoft references:
  • SQL Server Rights Requirements: SQL Server 2008 and later versions do not automatically create the BUILTIN\Administrators role delivered in SQL Server 2005. Because of this change to SQL Server, the Wonderware Application Server 2014 installation process will create the necessary operating system user group (aaAdministrators) as well as the necessary SQL Server role. This automated process will provide the rights required to allow operations within the Galaxy Repository without the need for blanket BUILTIN\Administrator rights. The aaAdministrators group must be present and enabled. If you accidentally delete the aaAdministrators group from the Windows operating system, you can run either of two options to restore it:
    • Run the Change Network Utility from the Windows Start menu.
    • Run the aaConfig SQL Utility from the Windows Start menu.

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 Wonderware Application Server User's Guide, About ArchestrA User Accounts, for further information and procedures to restore the aaAdministrators group.

Considerations for SQL Server Express

  • SQL Server Express is supported for use on a Galaxy Repository node and recommended for use only with small systems.
  • If you plan to modify an InTouch HMI installation which has SQL Server Express installed, then add Wonderware Application Server with full SQL Server, you must install the full SQL Server prior to modifying the InTouch HMI installation or installing Wonderware Application Server.
  • If you plan to use SQL Server Express with Wonderware Information Server and Wonderware on the same node, the following limitations apply:
    • Install Wonderware Information Server first with the SQL Server Express default instance name set to "SQLEXPRESS". Then, install Wonderware InTouch HMI. This scenario will work without issues because each component uses a dedicated instance of SQL Server Express.
    • If you install InTouch HMI first, the Wonderware System Platform installer silently installs and configures SQL Server Express. Installing Wonderware Information Server will fail during configuration with an error message stating: "SQL Server client components not found."

      To work around this issue, configure Wonderware Information Server to use an instance of SQL Server Express (or a non-Express edition) on a remote node.

    • The computing capacity of SQL Server Express is limited to the lesser of one CPU socket or four processor cores.
  • For InTouch HMI installations, the Wonderware System Platform installer installs SQL Server Express, if these conditions are met:
    • No other SQL Server elements are installed on the computer at the time of installation.
    • You select only the InTouch Development and Runtime Wonderware System Platform installation option. When you select InTouch Development and Runtime, a Galaxy Repository will be installed.
    • The installation program includes an option to not install SQL Server on an InTouch development computer. When the option is selected, it prevents SQL Server from being installed. Clear this option to automatically install SQL Server on a development computer.

Related Topics

System Requirements

Hardware Requirements

Operating System, .NET Framework, and Virtualization Requirements

InTouch Access Anywhere Requirements

InTouch Access Anywhere Requirements

The following sections describe the requirements to run Wonderware InTouch Access Anywhere Server and supported browsers. For detailed information, see the Wonderware 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 Wonderware 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.

  • Wonderware InTouch Access Anywhere server must be installed on a 64-bit version of Windows that is supported by InTouch HMI 2012 R2 (version 10.6) or later.
  • Wonderware InTouch Access Anywhere must be installed on the same RDP Server computer as Wonderware InTouch HMI 2012 R2 (version 10.6) or later.
  • Remote Desktop (RDP) must be enabled and properly configured on the host computer. For information and guidance, see Tech Note 782, "Installing Remote Desktop Services on Windows 2008 Server R2 for Wonderware Products". You also can refer to http://technet.microsoft.com/en-us/library/dd883253.aspx.
  • You must have an InTouch 2012 R2 TSE (RDS) or newer license activated. When InTouch is launched by InTouch Access Anywhere, this RDS license will be consumed per browser session. It will be released when InTouch is closed by InTouch Access Anywhere.
  • Per-Device licenses are not supported.

Supported InTouch Access Anywhere Browsers

Wonderware 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 Wonderware InTouch Access Anywhere include the following:

Browsers Tested with InTouch WindowViewer

  • Apple Safari
  • Google Chrome
  • Microsoft Edge
  • Microsoft Internet Explorer
  • Mozilla Firefox
  • Opera

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.

  • Apple Safari versions 5 and 6
  • Google Chrome versions 11-27
  • Microsoft Internet Explorer versions 7 and 8
  • Mozilla Firefox versions 4-21
  • Opera versions 11-14

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.

Related Topics

System Requirements

Hardware Requirements

Operating System, .NET Framework, and Virtualization Requirements

SQL Server Requirements

Wonderware InTouch HMI Installation

For detailed English installation instructions, see the Wonderware System Platform Installation Guide (WSP_Install_Guide.pdf) or Wonderware System Platform Installation Help (WSP_Install_Guide.chm). Condensed English installation instructions are also provided in the printed Wonderware 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.

Installing the Wonderware InTouch HMI

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 ArchestrA 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:

  • Installation DVD.
  • Computer that meets the hardware and software requirements listed in this Readme.

    Important: Use the hardware and software requirements listed in the Wonderware Application Server Readme if you are going to install the ArchestrA 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 Wonderware System Platform installation program:

  • Windows Installer 4.5
  • Microsoft .NET Framework 4.5.2
  • SQL Server 2014 Express SP1

    SQL Server 2014 Express SP1 is installed automatically if either of the following conditions are met:

    • No version of SQL Server is installed on the host computer.
    • You select only InTouch Development and Runtime during the Wonderware System Platform installation. You must not select any Application Server components. When you select InTouch Development and Runtime, a Galaxy Repository will be installed for you.

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 Wonderware System Platform installation prerequisites, see the Wonderware 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 ArchestrA environment. You must specify the same user account on every node when you install the Wonderware 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:

  • User account with a permanent password that does not expire.
  • User account in which the password cannot be changed.
  • User account that is a member of the local Administrators group.

After you install the InTouch HMI, you can use the ArchestrA Change Network Account utility to change or recreate the ArchestrA user account. This utility is accessible from the Start menu in the Wonderware 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

  1. Insert the installation DVD into the computer's DVD drive.
  2. Using Windows Explorer, manually start the installation by double-clicking setup.exe on the DVD.
  3. Follow the prompts to start the installation and install system prerequisites, as necessary.
  4. 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.
  5. Choose the components you want to install.
    1. If you choose InTouch Run Time Only, the following will be installed:
      • InTouch Run Time
      • InTouch documentation
      • Alarm DB Logger
      • OI Gateway (as a silent installation)
      • Application Server Bootstrap
      • ArchestrA Data Store
      • InTouch Supplemental Components: InTouch Recipe Manager, InTouch SQL Access, and Symbol Factory

      Note: The 16 Pen Trend supplementary component is not installed by default. You must select the Customize Installation option and select 16 Pen Trend from the product list to install it as part of the InTouch HMI installation procedure.

      • License Manager
      • Client Components
      • Server Components
    2. If you choose InTouch Development and Run Time, the following will be installed:
      • All items listed under step a in these instructions.
      • InTouch Development
      • Application Server (Bootstrap, IDE, and Galaxy Repository)
      • InTouch demo applications
      • Schneider Electric License Server
  6. When the installation prompts you to verify your selection, select Customize Installation if you want to add or remove components of your InTouch installation.
  7. After you verify and customize your selection, you are prompted to select the language you want to install. English is selected by default, but you can choose another language.
  8. Follow the subsequent installation steps to:
    1. Accept the End User License Agreement.
    2. Create a new ArchestrA user account, or specify an existing account.
    3. Install any prerequisite software components not yet installed on the computer.
    4. The installation proceeds to completion. You must restart the computer after completing the installation.

Activating Your InTouch License

Wonderware enforces the use of its products with a software license. InTouch uses the Schneider Electric License Server to make licenses available. The Schneider Electric License Manager manages one or more License Servers.

You use the Schneider Electric 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. Once activated it 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 Schneider Electric licensing, see the Schneider Electric Licensing Guide.

Antivirus Software Exclusions

After installing Wonderware InTouch HMI, configure your antivirus software to avoid scanning archive files.

Notes:

  • The folders listed in this section may be different based on your installation choices.
  • Exclude the files in the lowest level subfolder of the listed directories in this section. Antivirus exclusions should not be recursive and should only apply to the lowest listed subfolder in the specified folder path.
  • If you are using a 64-bit operating system, folder names must be specified accordingly. For example, the program files root folder in a 64-bit operating system is C:\Program Files (x86)\... and the application data root folder in a 64-bit operating system is C:\ProgramData\.

Add the following folders of 32-bit operating systems to your antivirus scan exclusion list:

  • C:\ProgramData\ArchestrA\
  • C:\Program Files\ArchestrA\
  • C:\Program Files\Common Files\ArchestrA\
  • C:\Program Files\FactorySuite\ (The FactorySuite folder may not exist in newer installations)
  • C:\Program Files\Wonderware\
  • C:\InSQL\Data\
  • C:\Users\All Users\Applications
  • C:\Historian\Data

Add the following folders of 64-bit operating systems to your antivirus scan exclusion list:

  • C:\ProgramData\ArchestrA\
  • C:\Program Files (x86)\ArchestrA\
  • C:\Program Files (x86)\Common Files\ArchestrA\
  • C:\Program Files (x86)\FactorySuite\ (The FactorySuite directory may not exist in newer installations)
  • C:\Program Files (x86)\Wonderware\
  • C:\Users\Public\Wonderware\
  • C:\Historian\Data

Add the following folders to your antivirus scan exclusion list:

  • History Store Forward folder default location: ◦C:\Documents and Settings\All Users\Application Data\ArchestrA\
    • C:\Users\All Users\ArchestrA\
  • Checkpoint folder location default location:
    • C:\Program Files\ArchestrA\Framework\bin (32-bit Windows)
    • C:\Program Files (x86)\ArchestrA\Framework\bin (64-bit Windows)
  • InTouch HMI application folders:
    • C:\Users\Public\Wonderware\IntouchApplications (default folder path)
    • You can select an application folder path when an InTouch HMI application is created.
  • ArchestrA System Management Console (SMC) Logger storage file path:
    • C:\ProgramData\ArchestrA\LogFiles (default folder path)

Add the following file types to your antivirus exclusion list:

  • SQL Server database files of type:
    • .mdf
    • .ldf
  • Exclude *.aFDX files from the C:\Windows\Temp folder

Modifying, Repairing, or Removing the InTouch HMI

To modify, repair, or remove a product

  1. Insert the installation DVD into the computer's DVD drive.
  2. Access the Windows Control Panel and select the Programs and Features option. The list of software installed on your computer appears.
  3. Select the InTouch component, and then click the Uninstall/Change button. The Modify, Repair or Remove Installation dialog box appears.
  4. Follow the prompts to modify, repair, or remove InTouch. The name of the Uninstall/Change button varies depending on the version of Windows installed on your computer.

    Note: Modern applications can no longer be created, edited, or run after Wonderware 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 Wonderware Application Server is uninstalled.

Upgrading to Version 2017 from an Earlier Version of the InTouch HMI

Upgrading refers to installation on a computer that already has a previous version. An upgrade removes the previous version of InTouch HMI and installs Version 17.0.

After the hardware and software requirements are met, you can upgrade to Wonderware InTouch HMI Version 17 from the following versions of the InTouch HMI:

  • Version 10.1 SP3
  • Version 10.1 SP3 P01
  • Version 10.2
  • Version 10.5
  • Version 10.6
  • Version 10.6 P01
  • Version 10.6 P02
  • Version 10.6 P03
  • Version 11.0
  • Version 11.0 P01
  • Version 11.1
  • Version 11.1 P01
  • Version 11.1 SP1

You can only upgrade Wonderware System Platform products that are already installed. You cannot install any new Wonderware System Platform products by an upgrade process.

To upgrade from a previous version of the InTouch HMI

  1. Insert the DVD into your DVD-ROM drive. Run setup.exe to start the set-up program. The upgrade feature dialog box appears.
  2. Follow the prompts to complete the upgrade.

Upgrade Notes

  • Important Note: If you plan to upgrade Wonderware System Platform on a computer that has InTouch Access Anywhere Server installed, you must first uninstall the InTouch Access Anywhere Server. Then, upgrade Wonderware System Platform and finally reinstall InTouch Access Anywhere Server.
    Back up any custom configuration of the installed instance of InTouch Access Anywhere before you uninstall it.
  • InTouch Development (WindowMaker) is now installed with support for ArchestrA graphics. This includes the ArchestrA Integrated Development Environment (IDE), Bootstrap, Galaxy Repository (GR), and FS Gateway.
  • If Wonderware Application Server is installed on the same node as Wonderware InTouch HMI, both must be upgraded to System Platform Version 17. You must upgrade Wonderware Application Server before upgrading InTouch HMI.
  • If you are using managed InTouch applications with ArchestrA Symbols from Application Server 3.1 SP3 or earlier, run the ArchestrA Symbol Analysis and Repair Utility before installing Wonderware Application Server to ensure that all issues reported by the utility are addressed.

Migrating Applications to Wonderware InTouch HMI 2017 (v17.0)

Migration converts applications created with earlier versions of InTouch HMI to the current version. You can migrate applications to InTouch HMI 2017 that were developed with the following earlier versions of InTouch HMI:

Product

From

Upgrade

Node-by-Node Upgrade

Migrate

Wonderware InTouch

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

Y

N/A

Y

10.1 SP3 P01

Y

N/A

Y

10.2

Y

N/A

Y

10.5

Y

N/A

Y

10.6

Y

N/A

Y

10.6 P01

Y

N/A

Y

10.6 P02

Y

N/A

Y

10.6 P03

Y

N/A

Y

11.0

Y

N/A

Y

11.0 P01

Y

N/A

Y

11.1

Y

N/A

Y

11.1 P01

Y

N/A

Y

11.1 SP1

 

 

 

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 Wonderware 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 17 with InTouch HMI. InTouch no longer includes SPCPro and will not open or migrate applications containing SPCPro components.

Resolved Issues

InTouch HMI 2017 resolves the issues listed in the following table. These issues are listed by their Change Request (CR) number and any assigned Service Request (SR) number. The left column of the table shows the original Change Request in which the issue was identified. The Related Change Requests column shows other subsequent change requests that are related to the original change request.

Original Change Request

Related Change Requests

Description

L00138456

L00139114

SR 42010123: WindowViewer was not maximizing to full screen mode upon double click of the taskbar, but was switching to the size that was configured as the Restored mode.

L00138909

L00139137

SR 103137401: I/O tags were not updating in a published Managed Application running on a local NAD directory.

L00139003

L00139302:

CS: case#1293620: When InTouch was running on a multi-monitor system, WindowViewer error messages would always appear in the primary window, regardless of the window the message corresponded to.

L00139025

L00139308, L00139669, L00140078

SR 45511002: The quality dotfield for a loop-back tag was always 32, even when the tag value changed. This prevented loop-back tags from being historized.

L00139217

L00139797

SR 52311223: The ArchestrA Embedded Alarm Client was locking up and discontinuing alarm state updates if the Ack.Visible button was pressed more than once per second to acknowledge visible alarms.

L00135162

L00130870, L00139659, L00139360

SR 20114850: A large amount of AlarmDBLogger deadlock error messages (messages without a specific log flag) were being logged. The amount of deadlock error messages was preventing other useful error messages from being analyzed.

L00139194

L00139486, L00139525, L00139562

SR 103137794: When migrating an InTouch application from a Wonderware 2012 system to 2014R2 with or without Patch 01, all Tab Control Object indexes would clear.

L00139552

L00139674

SR 54410187: When a Smart Symbol was resized in a Standalone application, language translation was not working for text displays embedded in the same InTouch window as instances of that Smart Symbol.

L00139785

 

SR 103137826: The configuration version of some objects would automatically increment upon import to a new galaxy.

L00140009

L00141964

L00140094

SR 103138479: The Percent of Vertical Fill calculations were more precise for InTouch symbol animations than for ArchestrA symbol animations. As a result, ArchestrA symbol animations displaying completely accurate fill levels.

L00140023

L00140168

SR 48911092: The DividedByZero exception error logged in the System Management Console was not capturing the symbol and element names of the ArchestrA Graphic causing the error.

L00139694

L00140027

L00140079

SR 54410233: The WindowViewer window could not be permanently resized. Any WinHeight adjustment greater than 1212 pixels would revert back to 1212 after launching and closing WindowViewer.

L00139598

L00139823, L00140037

L00139845

SR 103138239: Numeric values entered in Textboxes contained in ArchestrA Graphics were not displaying properly when the Tab key was used to focus instead of a mouse click.

L00140142

L00140253

: The slider animation was not working during Runtime on symbols launched by the ShowGraphic script function or ShowSymbol animation link.

L00140013

L00140208, L00140300, L00140760, L00140815

L00140300

: When restoring archived alarms, the AlarmDB Restore utility was duplicating data in the ProviderSession table.

L00140113

L00140283

L00140354

SR 103137969: When the WindowViewer memory cache was enabled, the text in an ArchestrA graphic with translated text would not be translated if the graphic was called by the ShowSymbol animation link.

L00133204

L00137580, L00140211, L00140301

L00140606

SR 19713806: ArchestrA graphics in deployed InTouchView applications were shifting from the locations they were placed in during design time.

L00137469

L00138102, L00140309, L00140591, L00141609

L00140489

SR 103135801: After installing HotFix L00138102 for InTouch 11.0 P01, using the function SetCustomPropertyValue for a symbol, WindowViewer would become unresponsive.

L00122821

L00140316

L00140440

SR 50310537: After upgrading from InTouch 10.5 to 11.1 SP1, if the Alarm Client was configured with Historical Alarms and Events, the script function AlarmClient.TimeSelector.SetStartAndEndTime() would fail to set custom start and end times.

L00140008

L00140347, L00140364, L00140516

SR 51311198: When migrating a Standalone 10.1SP3 P01 InTouch application to 11.1 P01, WindowViewer was consuming large amount of CPUs. This was causing I/O updates to the application to slow down.

L00140353

L00140451, L00140470

SR 103139190: When exporting ArchestrA Graphics from InTouch 2012R2 and importing them into 2014R2, the Embedded Alarm Client symbol was displaying an error when the Reset button was selected.

L00140433

L00140575

SR 56510146: Language identifiers were being prefixed to the Alarm and Tag comment fields when WindowViewer was running.

L00140353

L00140451

SR 103139190: When exporting ArchestrA Graphics from InTouch 2012R2 and importing them into 2014R2, the Alarm Client symbol was displaying an error when the Reset button was selected.

L00140490

L00141242

L00141041

SR 51710052: Exporting and restoring a galaxy would cause the configuration version to increase by one. The same behavior would occur when importing and restoring individual objects and symbols.

L00140507

L00140924

SR 45511054: After upgrade from InTouch 2014R2 P01 to 2014 R2 SP1, the script function EAC.Ack was not acknowledging all visible alarms. This caused unacknowledged alarms to appear in the Alarm grid.

L00140508

L00140704

SR 24516789: When the Alarm Manager and Alarm Printer were on different processor cores, the Alarm Printer would slow down and cause background functions to behave erratically.

L00140592

L00140814

SR 50610221: When the "Register using Galaxy_ instead of Galaxy" option was checked in the WinPlatform Object for "InTouch Alarm Provider," an invalid reference warning was being logged in the SMC.

L00140067

L00140429, L00140617, L00140642

L00140581

SR 49910354: The ACK All button in the Embedded Alarm Client was failing to acknowledge alarms.

L00140656

L00140887

SR 12613699: On standard multi-monitor systems, WindowViewer would not display across multiple monitors unless the Menu Bar was enabled in the WindowViewer Properties dialog box.

L00140676

L00140888

SR 103139584: The Import/Export function for ArchestrA graphics was not importing overridden text for a symbol if any of its elements had the locked property set to True.

L00140013

L00140208, L00140760

L00140300

: When restoring archived alarms, the AlarmDB Restore utility was duplicating data in the ProviderSession table.

L00140648

L00140775

L00140818

SR 103139591: The Alarm DB Restore utility was not restoring archived alarms.

L00140786

L00140954

SR 20115015: OnShow scripts used in InTouch windows were failing to execute, and could not write to attributes configured in Application Server. This write failure would cause an error to be logged in the Wonderware Logger.

L00140790

L00140909

SR 24516833: The graphic elements of a rectangular symbol were changing pixels when placed in an InTouch window. This change was causing stacked rectangular symbols to overlap or misalign.

L00140438

L00140820

L00140853

SR 10418074: When migrating InTouch 2014R2 to 2014R2P01 or 2014R2SP1, the anchor points of ArchestrA symbols containing embedded symbols would shift, and some of the embedded symbols were getting resized.

L00140881

L00140988

SR 50110050: After opening and closing a Managed InTouch application in WindowMaker, the GR node was requesting the application to be checked in even when no changes were made.

L00140816

L00141001, L00141109, L00141201

L00141105

SR 52312996: On a localized Windows 2012 R2 terminal server machine, the StringFromTimeLocale() and StringFromTime() functions used to get current alarm stamps were causing English time formats to display instead of German.

L00141115

L00141246

SR 41810449: The action script While Down applied in an ArchestrA graphic would not release if a DialogValueEntry script was called first in InTouch.

L00140911

L00141247

L00141357

SR 31310145: When windows caching mode was disabled in InTouch windows containing embedded .Net controls, large amounts of memory were being consumed by system by subsequent opening and closing of those windows.

L00141150

L00141316

L00141487

SR 103140230: The boundaries around symbols embedded from the Graphic Library were not inheriting their original dimensions, and would shift to the right upon embedding.

L00141324

L00141753

SR 41810446: When the combo box in an ArchestrA symbol was resized, the dropdown list in the combo box was not properly resizing along with it.

L00141325

L00141420

SR 103140325: Not all prefixes used in Alarm and Tag comment fields were appearing in alarm history and DB Dump displays during runtime, specifically text enclosed in the characters "<>".

L00140669

L00141339

SR 56510296: Embedding the SA_PlantModelPicker symbol in a Managed InTouch application failed to populate the tree view and resulted in an error in the Logger.

L00141177

L00141399

L00141501

SR 56510296: On a Windows 7 operating system, when a combo box was added to an ArchestrA symbol, it would display as a flat box rather than a three-dimensional design.

L00140991

L00141485

L00141692

SR 56510199: ArchestrA graphics were not appearing immediately in run time windows. There was a significant lag between the time the window was opened and the appearance of the graphic.

L00141488

L00142010, L00142011

L00141805

SR 41810082: When WindowViewer was running on a dual-monitor system, inconsistent window frame behavior would occur between the primary and secondary monitor screens.

L00141412

L00141598

L00141718

SR 103140678: When the font or font size of the Numeric Resizable Keyboard were changed, the new font settings were being applied to all of the keyboard fields except for the "New Value" field.

L00141937

L00141628

SR 103140762: After importing an Application Style Library, the styles were changing for graphics based on elements styles in WindowMaker but now consistently in WindowViewer.

L00141664

 

SR 19819161: When migrating to 11.1 from an older version, Tag Viewer was not showing all of the alarm groups.

L00141383

L00141687

L00141806

SR 103140572: Loading a PDF Client Control was causing InTouch to crash on execution.

L00141176

L00141700, L00141916

L00141810

SR 103140007: When the TimeSelector.TimeSelector.SetStartAndEndTimes action script was used to set the Trend Start Time for a button, the start time would not set until the button was clicked twice.

L00141115

L00141759, L00141760

L00141246

SR 41810449: The action script While Down applied in an ArchestrA graphic would not release if a DialogValueEntry script was called first in InTouch.

L00141768

L00141889, L00142054, L00142055

SR 41810456: When an action script contained a shortcut key and the DialogValueEntry method, the script would run twice, causing dialog boxes to appear more than once.

L00141419

L00141792

L00141939

SR 103140679: French and Italian keyboards were not displaying any combination of keys pressed in combination with "Ctrl".

L00141871

L00141886

SR 51010939: Each time the numeric keypad was opened, three Global Device Integration objects would be consumed and would not be released until the keypad was closed. This would result in Window Viewer crashing in environments where the keypad was in constant use.

L00141464

L00142048

L00142547

SR 51311659: When an ArchestrA Embedded Alarm Client was embedded in an InTouch ViewApp object and configured to filter the defined areas, it would fail to filter any added subareas alphabetically.

L00124331

L00141858, L00142107

L00142279

SR 45210046: Text changed from bold font to regular font would still appear in bold when the language was switched at run time.

L00141781

L00142125

L00142414

SR 49810069: When a Managed Application was running in WindowViewer, exceptions were frequently being logged in the System Management Console reading Exception in UpdateLGHData: Data Collection was Modified.

L00141865

L00142399

L00142438

SR 52313558: When an ArchestrA Graphic was opened, the selection properties were disabled for all other objects in the application.

L00142237

L00142413

L00142451

SR 103141321: When changes were made to a deployed InTouchView Application and the View Application was redeployed, WindowViewer would not prompt the user to restart the application to view changes.

L00142432

L00142512

SR 19714269: When the Show Symbol animation was used to invoke a pop up symbol, shortcut keys were not functioning properly when used to enter User Input animation values into the pop up symbol.

L00141631

L00141818

L00142471

L00142517

SR 103140847: The ArchestrA Watchdog Service was consuming large amounts of CPU. This was preventing WindowMaker from launching.

L00142160

L00142475

L00142531

When a window was resized at runtime using the WWMoveWindow() function, a halo would remain around a graphic when the mouse was hovered over it.

L00138976

L00142527

L00142955

L00143142

L00143420

L00143421

L00143165

SR 103137546: WindowMaker was crashing when a window containing "% S" text was printed to a text file. This issue occurred in InTouch for Japanese and Simplified Chinese languages as well.

L00142601

L00142974

SR 48410388: ArchestrA Graphics in WindowViewer were taking longer than one minute to close.

L00141664

L00141938

L00142641

SR 19819161: When migrating to 11.1 from an older version, Tag Viewer was not showing all of the alarm groups.

L00142679

L00142707

L00142976

SR 103142465: When WindowViewer was configured with the Inactivity Timeout property enabled, the user was logged out when the timeout value was reached.

L00142662

L00142829

In InTouch for Japanese, image files could not be selected in the Alarms and Events dialog box.

L00142861

L00142829

L00143167

L00142884

SR 51311955: When new instances of a window were created using the "Save As" function, new Phrase IDs were not being created for each new instance. When instances of the original window were translated and then exported, the duplicated Phrase IDs were causing each window instance to be overwritten with the translations of the original.

L00142708

L00143417

SR 55110592: When a DataStatus symbol was used to monitor the status of a combo box containing the SetCustomPropertyValue script, no data would be displayed in the symbol at run time when the combo box caption was changed if the user was not logged on. An error icon would appear instead.

L00143108

L00143166

L00144006

The eDNA Tag Browser would return tags that used characters not allowed in InTouch with a reference to the Attribute () function. "Galaxy" would then be added as a prefix to the tag upon return to the Galaxy Tag Browser, preventing correct assignment to an object.

L00142946

L00143147

L00143255

SR 54610137: When the ArchestrA Alarm Control was configured in historical alarms and events mode and OS security was enabled, a wwUser Login Failed messaged would appear when the application was deployed.

L00143259

L00143619

SR 103143013: When an ArchestrA symbol containing two horizontal or vertical lines that were placed on top of each other or grouped, the symbol would disappear.

L00142805

L00143261

L00142558

When the TimeOAT and TimeLCOAT criteria were configured in a query at run time, alarms were not being filtered in the Embedded Alarm Client.

L00143268

L00143443

When a modal graphic was shown using the ShowGraphic script function and the TopMost property set to True, the change notification dialog was not appearing, and the graphic could not be closed. InTouch had to be restarted to close the graphic.

L00142863

L00143282

L00143367

SR 51312009: The InTouch Trend Client was not consistently plotting data. The yellow trend line would disappear after certain timestamps.

L00143272

L00143456

L00143618

SR 52314988: The $NewAlarm system tag was not resetting to zero after the first time the alarm limit was reached and the alarm acknowledged.

L00143128

L00143519

L00143667

SR 52314664: When point animations were used in embedded ArchestrA Graphics, the graphics would disappear if the InTouch tags controlling the point values kept the initial default values at zero. The graphics could not be redrawn after the tags were changed to alter the point values.

L00143276

L00143568

L00143666

SR 2314883: When InTouch regional settings were switched to Turkish and memory tags were used in the custom properties of an embedded ArchestrA symbol, Galaxy:InTouch would be added as a prefix to the tag name.

L00142452

L00143628

L00143678

SR 103141911: When a discrete tag was set to True and its AlarmEnabled field set to zero, the alarm dotfield would not automatically reset to False.

L00140347

L00140008

L00140364

L00140516

SR 51311198: When migrating a Standalone 10.1 SP3 P01 InTouch application to 2014 R2 P01, WindowViewer was consuming large amount of CPUs. This was causing I/O updates to the application to slow down.

L00130673

L00133920

L00135032

L00135479

SR 45710843: The Alarm Toolkit was not fetching summary alarms.

L00139908

L00140052

SR 103138592 When the Embedded Alarm Client was configured to retrieve unacknowledged alarms and used the methods SetXmlAlarmQuery and GetXmlCurrentAlarms2, all alarms would be returned by default.

L00142640

L00143249

SR 19819225 In a multi-Galaxy environment, when an owning object assignment was used to switch to a different object, incorrect values would display for the new object.

L00140299

 

SR 103139047: The ArchestrA Trend Client User Guide (aaTrendClient.pdf) was updated to include more detailed description on the differences between the ArchestrA Trend Control and the Historian Client Trend Control.

Known Issues

This section describes known issues that remain in the release of InTouch HMI 2017. The issues are listed by their Change Request number.

Change Request

Description

799750

When the Embedded Alarm Client is changed from Current Alarms mode to Historical Alarms mode with a customized default query, a blank query cannot be created and saved. Upon saving a blank query, an error will appear that the action is not allowed.

Workaround: Create a new instance of the Embedded Alarm Client and switch to Historical Alarms mode without first customizing the default query.

799156

In the Embedded Alarm Client, when executing a filter in WindowViewer that contains three or more grouping operations, an error will display stating that the filter is not valid.

Workaround: Use a query for the same grouping logic and add "Provider" and "Group" to satisfy the query definition for a current alarm.

792924

When Wonderware System Platform is installed on a Windows Server 2016 system with Remote Desktop Services enabled, WindowViewer will fail to launch. WindowMaker cannot be closed unless shut down via the Task Manager.

Workaround:

  1. Download and install the latest Microsoft Windows update KB3194798 on the Windows 2016 system. This Windows update is located at the following URL:

    http://www.catalog.update.microsoft.com/Search.aspx?q=KB3194798

  2. After installation of the update is complete, restart the system and install Wonderware System Platform 2017.

    Important: The Microsoft update can be installed before or after Wonderware System Platform is installed. However, it is recommended that you install the update prior to installing System Platform.

     

793477

In a Windows 8.1 32-bit Operating System, an attempt to connect to a Galaxy from the IDE or open an InTouch Modern application in WindowMaker will not succeed while creation of another Galaxy or Modern application is in progress.

Workaround: Wait for the Galaxy or Modern application to finish being created before launching the IDE or WindowMaker.

792205

The Cross Reference Utility search results for references made by ArchestrA Graphics do not give the expected result for a nested embedded symbol where the embedded symbol was either renamed, edited or deleted but the base symbol was not saved or validated after the changes were made.

Workaround: Open and save the base symbol, perform a validate operation, or update the thumbnail of the base symbol after renaming or deleting the embedded symbol, then invoke the Cross Reference Utility.

786699

When InTouch WindowViewer and a Wondeware System Platform 2017 ViewApp run concurrently in separate RDP sessions on the same client device, one license will be acquired per RDP session. However, when both WindowViewer and the Wonderware System Platform 2017 ViewApp are closed in one of the sessions and relaunched, each instance of View.exe in the session will acquire a separate license.

Workaround: Close all instances of View.exe in every RDP session that is running from the same client device.

789103

In an InTouch Modern application, when a client control embedded in a symbol is overridden by a client control of a different version, the updated client control will not be reflected upon the initial close and restart of WindowViewer.

Workaround: Restart WindowMaker after importing the newer version of the client control.

When a script function library is imported into an InTouch Modern application and an action script from the library is used on a symbol and the imported script library is then overridden by a library of the same version but different method logic, the action script used in the symbol will fail to execute at runtime.

Workaround: Update the symbol thumbnail of the symbol containing the script before switching to runtime.

787020

A Tag used in overriding a custom property of a symbol that is embedded in a Frame window is not added to the list of Tags in Use in WindowMaker. Hence the Delete unused tags action will falsely list the tag as not in use. Please note that this limitation applies to Frame window only.

786775

When a symbol is embedded in a Frame window, a small white rectangle temporarily appears in the upper left corner of the frame. The rectangle disappears as soon as the symbol has been loaded.  The white rectangle is noticeable when the Frame background color is non-white.

783666

The ZoomPercent property in Named Script expression box does not get evaluated at runtime when it is used without an element.

For example, ZoomPercent >= 200 does not get evaluated at runtime.

Workaround: Use the ZoomPercent property of an element instead. For example, Button01.ZoomPercent >= 200.

768592

InTouch applications have the capability to run on the same computer as Wonderware System Platform 2017 ViewApps. However, to run both applications on the same computer, the InTouch application must be launched before a Wonderware System Platform 2017 ViewApp .

L00142816:

In a system with a large number of alarms that are rapidly changing state, applying an ArchestrA Alarm Control filter by name, value or state does not reduce the Alarm Manager or WindowViewer CPU consumption. Alarm Manager and WindowViewer will consume the same amount of CPU as before the filter was applied. The "CurrentValue" and "Quality" sorting columns do not work.

Workaround: To reduce CPU consumption, apply a provider, group or priority filter.

L00142564:

The InfoAppTitle method returns an empty string for Internet Explorer.

Workaround: Use Google Chrome.

L00137472:

Angled connector lines do not maintain horizontal and vertical orientation with 90 degree angles to each other when placed in a symbol whose dimensions exceed 1280 by 1280 pixels. Instead, a connector will revert to a straight line between connection points beyond the 1280 by 1280 pixel boundary.

L00139557:

When using a non-default SQL port: In Runtime with multiple EACs configured, database connections may fail with a "Timeout expired" warning (see full text below) appearing in the SMC.

Error Message: Open() in DCMConnection failed: 'Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.'

Workaround: Perform a manual refresh on the ArchestrA Alarm Control (EAC) to re-establish the connection.

L00139560:

When using a non-default SQL port: If the primary Historian server is down during a restart of WindowViewer, trend updates are delayed by approximately 25 seconds. This is a one-time delay after WindowViewer restarts.

L00139681:

After changing the SQL port of the Historian node and restarting Historian, the ArchestrA Trend Client (RT Trend) does not reconnect to Historian.

Workaround: Restart the instance of WindowViewer hosting the Trend client.

L00139786:

After switching between default and custom SQL ports for Dual Historian, on a machine where the ArchestrA Trend Client (RT Trend) is used and is configured by scripting, only the real time trend displays, not the Historian trend.

Workaround: Delete the servers.xml file typically found at the following location: C:\Users\<user-name>\AppData\Local\Wonderware\ActiveFactory\servers.xml.

L00139789:

Connecting to a SQL database in Microsoft Windows 8 or Windows 10 operating systems, when a non-default port is configured for SQL, results in an error message that a connection to the server is not available.

Workaround: Disable (shut down) the firewall on Windows 8 and Windows 10 operating system machines.

L00139833:

Migrating a Galaxy which has an InTouchViewApp with embedded Historian Client controls from Wonderware System Platform versions 2012R2 or 2014R2 to version 2014R2 Service Pack 1, results in errors logged in the Logger.

Workaround: Before migrating the InTouch application, delete the previous version Historian Client controls that exist in the Galaxy. Import the newer version controls.

InTouch Documentation Issues

The following table lists corrections to InTouch 2017 documentation.

Item

Location of Change

Existing Documentation

Change

1

InTouch HMI Application Management and Extension Guide (ITAppManagement.pdf), "Viewing Applications at Run Time in a Different Target Resolution Size", pg. 155

WindowMaker Help (WM.chm), "Viewing Applications at Run Time in a Different Target Resolution Size" topic

(Existing topic)

Add the following sentence to the end of the first paragraph:

The target resolution size is automatically adjusted at run time to account for WindowViewer’s menu and title bar controls.

2

InTouch HMI Application Management and Extension Guide (ITAppManagement.pdf), "Zooming at Run Time", pg. 169

WindowMaker Help (WM.chm), "Zooming at Run Time" topic

Note: You cannot write to this property at run time.

Replace the existing note with the following and add the accompanying content:

Note: You can write to this property at run time.

When ZoomPercent is set for a symbol, the symbol will be zoomed to the set percent at the center of the viewable area.

When ZoomPercent is set for a symbol’s element, the symbol will be zoomed to the set percent but will center on the element.

The following script is an example of ZoomPercent set for an element:

TextBox1.ZoomPercent = 500

3

InTouch HMI Application Management and Extension Guide (ITAppManagement.pdf), "Zooming at Run Time", pg. 169

WindowMaker Help (WM.chm), "Zooming at Run Time" topic

(Existing bulleted list)

Add the following bullet item to the end of the To zoom with mouse gestures bulleted list:

Select the Rubber Band Zoom icon from the Pan and Zoom Control Toolbar to select a specific area to zoom in on.

4

InTouch HMI Application Management and Extension Guide (ITAppManagement.pdf), pg. 172-173

WindowMaker Help (WM.chm)

(New topic)

Add the following topic heading and accompanying text directly after "Animation Support for Touch Gestures" topic:

"Using the ShowGraphic() Function with Frame Windows"

You can run the ShowGraphic() script function to change the symbol associated with a frame window at run time. Specify the frame window name and associated symbol as in the following example:

Dim graphicInfo as aaGraphic.GraphicInfo;
graphicInfo.Identity = "InTouch:FrameWindow01";
graphicInfo.GraphicName = "Symbol_002";
ShowGraphic( graphicInfo );

"Symbol_002" will display in "FrameWindow01" at run time regardless of the frame window’s design time configuration. You can use a ShowGraphic script to host different symbols in the same window.

Limitation:

Graphic caching occurs only for the symbol currently shown in the frame window at the time the window is closed and cached. Replaced symbols will not be cached.

5

InTouch HMI Concepts and Capabilities Guide (ITConcepts.pdf), "Reserving Licenses", pg. 33

WindowMaker Help (WM.chm), "Reserving Licenses" topic

You can also reserve a license for a specific RDS client node that connects to a given RDS Server. To do this, enter the client node name as the device name when reserving license. Any other RDS client nodes without a license reservation will consume a floating license.

Remove paragraph.

6

InTouch HMI Concepts and Capabilities Guide (ITConcepts.pdf), "Using the Cross Reference Search Criteria", pg. 67

WindowMaker Help (WM.chm), "Using the Cross Reference Search Criteria" topic

(Existing bulleted list)

Add the following note under the third item in the bulleted list:

Note: A symbol embedded in a frame window that has a reference to an InTouch tag will not be processed in the Cross Reference report.

InTouch Documentation

The InTouch product library consists of a set of Portable Document Files (PDF) available in the following location of the Wonderware System Platform DVD:

\Wonderware 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.

Avantis  |   Industry Software Suites   |  OASyS  |   SimSci  |   SimSuite  |   Skelta  |   Wonderware

Copyright © 2017 Schneider Electric Software, LLC.  |  Contact Us