Last revision: 08/14/2007
This document contains the latest information about Wonderware® InTouch® HMI version 10. Review this document for descriptions of new features, installation requirements, and any known issues.
Upgrading from a Previous Version
Known Issues – InTouch HMI version 10
InTouch HMI Documentation Issues
Version 10 of the InTouch HMI provides a set of new features and enhancements to existing features.
InTouch HMI version 10 is more tightly integrated with the Wonderware ArchestrA environment. You can install the Wonderware Integrated Development Environment (IDE) with InTouch HMI to centrally manage your InTouch applications in a Galaxy Repository (database). The Wonderware IDE includes the Symbol Editor, the Graphics ToolBox, a set of sample databases, and the InTouchViewApp object template.
The Wonderware IDE provides an extensive set of graphic and scripting tools to create complex symbols that can be embedded into InTouch applications.
This section describes the hardware and software requirements to install InTouch HMI version 10. For updates to this information, see the Wonderware Technical Support website at www.wonderware.com/support.
The following lists show the recommended hardware specifications to install InTouch HMI version 10 by itself or the InTouch HMI with the ArchestrA IDE. These recommendations are for development systems. Run-time requirements may be different, depending on the InTouch application and other factors.
Note:
The Microsoft Windows Vista operating system imposes hardware requirements that exceed the minimum requirements for InTouch HMI version 10. If you intend to run InTouch HMI version 10 with Windows Vista, see the following Microsoft web site for hardware requirements:
www.microsoft.com/windows/products/windowsvista/editions/systemrequirements.mspx
This section describes the operating system and other software requirements to install InTouch HMI version 10.
The following table lists the supported operating systems that can be installed on computers running InTouch server and client components.
| Operating Systems | InTouch HMI Components | ||||
| WindowMaker | WindowViewer | ArchestrA IDE | ArchestrA Run Time | Galaxy Repository | |
| Windows Vista Enterprise (See Windows Vista Restrictions) | ● | ● | ● | ● | |
| Windows Vista Business (See Windows Vista Restrictions) | ● | ● | ● | ● | |
| Windows Vista Ultimate (See Windows Vista Restrictions) | ● | ● | ● | ● | |
| Windows Server 2003 Standard SP2 | ● | ● | ● | ● | ● |
| Windows Server 2003 Enterprise SP2 | ● | ● | ● | ● | ● |
| Windows Server 2003 Standard R2 SP2 | ● | ● | ● | ● | ● |
| Windows Server 2003 Enterprise R2 SP2 | ● | ● | ● | ● | ● |
| Windows XP Professional SP2 | ● | ● | ● | ● | |
| Windows XP Tablet 2005 | ● | ● | ● | ||
Notes:
The following list describes other third-party software requirements to support InTouch HMI version 10.
SQL Server 2005 SP2 (Standard or Enterprise only) or SQL Server 2000 SP4 can be used for InTouch database components. A SQL Server 2000 SP4 database cannot be used as the Galaxy Repository database. Also, other versions of SQL Server 2005, including Compact, Express, Workgroup, and Developer are not supported as a Galaxy Repository.
SQL Server 2005 SP2 is the recommended database to use with InTouch HMI version 10.
ArchestrA 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, ArchestrA symbols cannot communicate with InTouch tags when used with an InTouchView license. Windows Server 2003 and Windows XP Pro still support NetDDE.
You can upgrade to InTouch HMI version 10 from InTouch version 8 and later. When upgrading from InTouch HMI version 8 or later, the installation procedure detects which InTouch components are currently installed and updates them accordingly. Adding or removing components during the upgrade is not recommended.
Upgrading to InTouch HMI version 10 may require a reboot if the Microsoft MDAC version currently installed on the computer is not at the prerequisite version level. The InTouch HMI requires, at a minimum, MDAC 2.7 SP1 for Windows XP Professional and MDAC 2.8 for Windows Server 2003. The version of MDAC installed on the computer is verified during the installation of version 10.
If you are upgrading from InTouch version 7.11 to InTouch HMI version 10, uninstall InTouch 7.11 before you install the new version.
If InTouch 7.11 is installed and you have Alarm DB Logger set to run as a service, change the service mode to manual before you uninstall InTouch and reboot your computer. You must also ensure that this service is not running before you install InTouch HMI version 10. Otherwise, the installation cannot update the files properly. If you uninstall InTouch 7.11 with Alarm DB Logger in automatic mode, the InTouch installation does not complete properly.
Install InTouch Terminal Services on a stand-alone server. We strongly recommend that you not install InTouch Terminal Services on any computer that also acts as a database server such as Wonderware Historian, RAS server, or PPTP server.
InTouch and InTouch Terminal Services are not supported and should not be installed on a computer configured as a domain controller. InTouch Terminal Services is designed to perform like Windows 2000 Professional at the end-user level and it will not assign top priority to critical domain-level processes. Installing InTouch Terminal Services on domain controllers can significantly degrade the performance of your InTouch applications.
Important Note:
If you copy the contents of the InTouch HMI installation CD to a folder on your hard drive and then run the installation from this folder, the full path name of the folder must not contain a blank space.
This section describes all known issues identified in InTouch HMI version 10. The known issues are grouped by function.
L00056999: The Rainbow Sentinel driver does not install correctly if an ArchestrA product is installed on a computer running the Windows Vista operating system and a second ArchestrA product is currently installed.
An error can occur by running setup.msi to install a second ArchestrA product on a computer that already has an ArchestrA product installed on it. Do not use setup.msi to install the second ArchestrA product. Install the second ArchestrA product by running the setup.exe file instead.
L00057160: Need to modify InTouch for Tablet PC installation for Microsoft.Ink.dll issue.
Compatibility issues with CLR2.0 have been found in Windows XP SP1/SP2 versions of the Microsoft.Ink.dll file running on Tablet PCs. Because Microsoft.Ink.dll is a system file, you must manually install an updated copy of the file to enable the InTouch for Tablet PC annotate functions (cut, copy and paste). Refer to Microsoft Knowledge Base issue KB900722 for details and a link to download the replacement file.
L00062633: When the ArchestrA License Manager installs a new license file from a CD, the file remains read-only. Any subsequent attempt to add licensing information to the file fails indicating "Read/write access denied to file."
After the license file is installed, edit the file's properties and clear the read-only attribute.
L00064271: Installing legacy components (version 7.x or earlier) after ArchestrA components (version 8 or greater) creates duplicate common components that causes installation errors.
If you wish to continue using legacy Wonderware products, install the FactorySuite 2000 common components from the Device Integration product CD prior to installing the ArchestrA components.
L00065667: The ArchestrA License Manager appends new feature lines to the end of the license file.
Open the license file with a text editor and move the new feature line from the bottom to the top of the file. Save your changes to the license file.
L00066339: The License Utility becomes unusable when ActiveFactory 9.2 and the ArchestrA IDE co-exist on a machine and ActiveFactory 9.2 is uninstalled later.
In order to make the License Utility usable, perform the following steps:
Depending on the order of products installed, or uninstalled, the license utility menu option may, or may not appear under start/programs/Wonderware/Common. If the shortcut is not available, the License Utility can be launched by locating licview.exe file in c:\program files\common files\ArchestrA folder.
L00067871: InTouch TSE does not detect previous installs of older standard InTouch.
If a standard version of InTouch is installed on a computer, InTouch TSE installs without detecting the version of standard InTouch already installed on the same computer. Your InTouch TSE instance becomes corrupted if you attempt to uninstall the first standard Version of InTouch after the TSE version was installed.
L00039530: Action scripts with remote references are lost when SmartSymbols are exported and imported.
Animation links are lost if there is a reference to a Quick Function and the function is not defined in the target application. If you export and import a window with a reference to a Quick Function not in the application, the script is retained but you receive an error message that "Quick Function not defined". The solution is to import the Quick Function too.
L00040200: Using a blink animation in a SmartSymbol does not reference the first parameter of an instance reference with a logical AND operation to #Vstring.
The expected results should be: Galaxy:instance.test1.#VString == "1" AND Galaxy:instance.test2.#VString == "0" after referencing an instance. Instead, the first reference to the instance does not accept the first parameter. The actual results are: Galaxy:me.test1.#VString == "1" AND Galaxy:instance.test2.#VString == "0".
There is a solution to the problem.
L00061995: The input field of a user input animation link should be resizable to fit higher resolution screens.
The input link for the Analog and/or String user input links can be resized with a mouse pointer. You must add the Resizable InputLink parameter to the InTouch.ini file under the [InTouch] section. The value assigned to the Resizable InputLink parameter must be a non-zero value.
After the input link is sized the first time, you can manually adjust the size of the input field by setting values to the Width and Height parameters within the intouch.ini file. See the following example.
Example:
[InTouch]
Resizable InputLink = 1
Resizable InputLink Width=300
Resizable InputLink Height=50
L00062330: Some InTouch tag types (GroupVar, HistTrend, and TagID) do not display in the ArchestrA IDE Attribute browser.
When using a Galaxy repository as the remote tag source for an InTouchView application, the GroupVar, HistTrend, and TagID tag types do not appear in the ArchestrA IDE Attribute Browser dialog box. Normally, these tag types do not appear in InTouch scripts.
L00065809: Failure to import the translated dictionary for an imported SmartSymbol with language switching. No error message appears in the Logger.
There is a solution to set translated SmartSymbol strings working with run-time language switching.
Any time the SmartSymbol is embedded in a new window, steps 4 and 5 must be completed to enable language switching for the new instance of the SmartSymbol.
L00067416: Some embedded controls do not appear when a window is panned or zoomed from WindowMaker. Instead, a rectangle placeholder appears with the name of the control.
Pan and Zoom Limitations:
WindowMaker panning and zooming does not apply to the following InTouch controls:
ActiveX controls
Distributed Alarm Object
Trends (16-Pen Trend, Historical trend, Real-time trend)
Hist Trend with Left/Right scooters (showing time) and EU scale
SPCPro objects
Text boxes
Check boxes
List boxes
Combo boxes
Radio Group objects
ArchestrA graphics (InTouch panning and zooming has no effect on ArchestrA graphics)
L00067550: WindowMaker experiences a disk write error after attempting to substitute references for a symbol that has a large number of references.
The disk write error occurs because the symbol data that is being updated exceeds the temporary storage buffer size.
If you want to change the references for the same symbol using ArchestrA graphics, you can use an input control and the OwningObject property to show data for other object instances on the same WinPlatform. This allows you to configure a single symbol, but show data for different object instances.
The following procedure explains how to configure an EngineGroup display symbol, which has many data references and use a combo box to select between three different AppEngines. The AppEngines are named AppEngineA, AppEngineB, and AppEngineC. All of these AppEngines are deployed.
L00068996: Substitute String function does not work for double-byte characters inside an ArchestrA symbol.
A WindowMaker error occurs when attempting to substitute strings of an ArchestrA symbol formatted with unicode characters with multi-byte characters. Incorrect characters are substituted when translating from multi-byte characters to unicode.
The solution to the problem is to perform the symbol's string substitution on the symbol within a new symbol using the ArchestrA IDE Graphic Editor rather than WindowMaker.
L00069271: Migration of older aaPKG files to a Galaxy created with the Base_InTouch.cab file fails.
A Galaxy created from the Base_InTouch.cab file provides only the InTouchViewApp base template to run the sample applications included with InTouch HMI version 10. This unique Galaxy does not provide the other standard system objects needed to support ArchestrA applications.
If you attempt to import or migrate the contents of aaPKG files created with earlier versions of Wonderware Application Server (2.0, 2.1, or 2.5) to a Galaxy created with the Base_InTouch.cab file, the older ArchestrA objects are assigned because no version 3.0 templates are part of the Galaxy. When you attempt to deploy an instance of an application, a failure occurs because the Galaxy's required version 3.0 automation objects are missing.
Important:
Take these steps to restore the correct version 3.0 system objects to your Galaxy:
L00037868: Communication with an I/O server stops if an I/O tag is included in an Asynchronous Quick Function and it is linked to an Access Name by DDE type communication.
A tag's value updates correctly if it is ran from a Synchronous Quick Function. Also, a tag's value updates correctly in Synchronous or Asynchronous Quick Functions if the topic is configured to communicate with SuiteLink rather than DDE.
L00057767: A condition script goes into an endless loop if an I/O discrete tag is reset while the script is running.
The conditions that cause a condition script to go into an infinite loop are shown in the following list:
To work around this issue, the value display link should be changed to the name of the I/O discrete tag.
L00059086: After a failover, not all topics transfer to the secondary tag source of an Access Name.
When a secondary tag source is configured for an InTouch Access Name, the secondary configuration information is stored as another Access Name with the suffix _SEC appended to the original Access Name. For example, if AB_HFPP is the Access Name for which a secondary tag source is defined, then the internal name of the secondary Access Name is AB_HFPP_SEC.
Problems can occur if you define a new Access Name that is a duplicate of an assigned internal secondary Access Name. The work around for this problem is to create unique primary and secondary Access Names that differ by more than the _SEC suffix.
L00061804: Query Filter for an alarm comment does not retrieve any records during language switching.
If the InTouch alarm database contains old data without a unique two-character prefix and new records configured for language switching (prefixed with two unique characters), then alarm comment queries do not work with these operators: <, <=, >, and >=. This is because the old database contains existing alarm comments without unique characters and new alarm comments with concatenated unique characters.
L00061933: ArchestrA graphic symbol with an InTouch:Tag reference does not connect to InTouch tags within an InTouchView application.
By design, an InTouchView application does not serve data to any other source, including the InTouch HMI itself. WindowViewer verifies if the started application is intended for the InTouch HMI or InTouchView. If the started application is an InTouchView application, WindowViewer does not register to become a DDE server.
ArchestrA graphics make use of the client layer to access InTouch tags. The graphics appear as a third-party client attempting to access WindowViewer as a data server, which is prohibited for InTouchView applications.
L00064546: InTouch application on a non-upgraded remote node cannot see an alarm generated on a upgraded remote node.
When a Galaxy Repository (GR) node is upgraded while hosting alarms, the updated AreaHierarchy.xml file is not distributed because the GR platform engine is stopped. A remote node relies on the GR platform attribute to trigger a global data cache sync operation.
Before the GR node is upgraded, the last version of AreaHierarchy.xml remote node should have all objects hosted by the GR node marked as deployed. Based on the timing of the deployment, there is a good chance that the next version of the AreaHierarchy.xml file after the GR is upgraded and redeployed will still have all objects marked as deployed. The ITAlarmProvider cannot determine if the areas have been undeployed and redeployed.
L00065377: OS style keyboard always appears on the first monitor of a multi-monitor configuration, regardless of where it is invoked from.
The Windows keypad always appears in the lower corner of the first monitor of a multi-monitor configuration. There is no alternative solution. Using the InTouch keypad and resizable keypad works better in a multi-monitor configuration.
L00068346: Embedded ArchestrA button symbols lose focus and fail to reset values when calling a pop-up window.
When users click an ArchestrA graphic button with a mouse, the graphic button symbol does not recognize when the user releases the mouse button after a pop-up window is called. When the graphic button is clicked and a pop-up window appears, the graphic button is still regarded as pressed because the pop-up window has focus.
The first time this occurs, the user must click on the graphic button to reset it and any discrete values it controls. After the first occurrence, the user can click anywhere within the window to reset the graphic button.
L00068579: If a window contains only an ArchestrA symbol, switching to run time does not work as expected.
If an InTouch application window contains only ArchestrA graphics and makes a reference to remote data with an Access Name, incomplete or invalid status data is returned after failover occurs to the Access Name's secondary tag source. The SMC logger does not contain any messages to indicate that a failover occurred because the InTouch application is unaware of the data connection established by the ArchestrA graphic.
The IOGetNode and IOGETActiveSourceName functions are included in scripts to report the current status of tag sources for an Access Name. These functions return the active tag source (primary or secondary) and the node name of the active tag source obtained from the InTouch data channel. ArchestrA graphics do not support the IOGetNode and IOGetActiveSourceName script functions. As a result, both functions return either incomplete or incorrect data from scripts that query the status of an ArchestrA data channel.
The following table lists corrections to the InTouch HMI version 10 documentation.
| Item | Location of Change | Existing Documentation | Change |
| 1 |
ITDataManagement.pdf: "Understanding InTouch Remote Reference Limits" section, page 259 WM.chm: "Understanding InTouch Remote Reference Limits" topic |
You can set up InTouch Access Names with primary and secondary target addresses. The secondary address usually serves as a backup or failover tag source while an application is running. When your application switches between the primary and secondary tag source of an Access Name, its sticky remote reference tag count does not increment despite the change in the addressing of the Access Name. |
Replace this paragraph with the following: When fail-over to the secondary tag source occurs, the application can access the same items from the secondary source without increasing the licensed tag count. After failover, accessing new items from the secondary tag source increases the tag count. These items are accessible after fail-back to the primary tag source. After the tag count reaches the licensed maximum, no further items can be activated regardless of whether they are accessed from the primary or secondary tag source. |
| 2 |
ITDataManagement.pdf: "Understanding InTouch Remote Reference Limits" section, page 258 WM.chm: "Understanding InTouch Remote Reference Limits" topic |
The InTouch 60K license does not use sticky tag counts that impose limits on the number of dynamic remote tag references. This allows an application to dynamically access more than 60K tags during the period the application is running. The tag use count for dynamic remote references fluctuates up and down as windows with remote references are opened and closed. |
Add this paragraph immediately after the fourth paragraph on page 258. Dynamic reference tag counts only fluctuate up and down when WindowViewer uses disk storage to save the contents of a running application. If the WindowViewer Always load from disk configuration option is not selected, then the count assigned to the No. of remote tags that can be activated without running out of remote tag handles does not necessarily decrease after closing a window containing remote tag references. |
| 3 |
ITAlarmsAndEvents.pdf: "Example Alarm Queries" section, page 55 WM.chm: "Example Alarm Queries" topic |
For example: \\ProdSvr\InTouch!System Use the following syntax for querying alarms from a Galaxy. This syntax gets alarms from a specific attribute of an object in a specific area on a specific computer. \\NodeName\Galaxy!Area.Object.Attribute Use following query syntax for all alarms from a specific area: \\Galaxy!Area The following query syntax retrieves alarms from two areas: \\Galaxy!Area1 \\Galaxy!Area2 The following query syntax retrieves all alarms from the Platform on computer node (by default): \\NodeName\Galaxy You can also use a wildcard character in an alarm query. The following query retrieves all alarms from Area1, Area2, Area3, and so on: \\Galaxy!Area* The following query retrieves all alarms from all objects starting with the characters Tank in the area named Area: \\Galaxy!Area.Tank* |
For example, on a node called MyNode1: \\MyNode1\InTouch!System Use the following syntax for querying alarms from a Galaxy. This syntax gets alarms from a specific alarm name of an object in a specific area on a specific computer. The alarm name may be an attribute name or an alarm primitive name. \\NodeName\Galaxy!AreaName!ObjectName.AlarmName The following syntax gets all alarms from a specific area: \Galaxy!AreaName The following syntax gets alarms from two areas: \Galaxy!Area1 \Galaxy!Area2 The following syntax gets all alarms in the specified Area from the Platform on the specified computer node (by default): \\NodeName\Galaxy!AreaName You can also use single wildcard to match alarm names within a specified area. The following syntax gets all alarms from all objects starting with the characters "Tank" in the "AreaName" area: \Galaxy!AreaName!Tank* The following syntax gets all alarms named "Hi" from all objects in the "AreaName" area: \Galaxy!AreaName!*.Hi |
| 4 |
ITAppManagement.pdf: "Publishing a Stand-alone InTouch Application" section, page 27 WM.chm: "Publishing a Stand-alone InTouch Application" topic |
To publish an InTouch application | To publish a stand-alone InTouch application |
| 5 |
ITConcepts.pdf: "InTouch Basic Objects" section, page 39 WM.chm: "InTouch Basic Objects" topic |
Graphic label reads "ArchestrA Tools Panel Graphic Primitives" | Label should read "ArchestrA Tools Panel Graphic Elements" |
| 6 |
ITConcepts.pdf: "Exporting and Importing InTouch Tags" section, page 66 WM.chm: "Exporting and Importing InTouch Tags" topic |
You can use any application that supports the .csv file format to add, modify, or delete tags. | You can use any application that supports the .csv file format, to add, modify, or delete tags in the import file. |
| 7 |
ITVisualization.pdf: "Selecting Tags or Attributes" section, pages 97-99 WM.chm: "Selecting Tags or Attributes" topic |
Locate all instances of the phrase "Attribute Browser." | Change all instances of "Attribute Browser" to "Galaxy Browser." |
| 8 |
ITAAIntegration.pdf: "Published InTouch Applications" section, page 13 WM.chm: "Published InTouch Applications" topic |
A managed application appears in InTouch Application Manager as Published. | A published application appears in InTouch Application Manager as Published. |
| 9 |
ITDataManagement.pdf: "Memory Tag Properties" section, page 22 WM.chm: "Memory Tag Properties" topic |
-- | In the Priority row of the table, add a bullet in the Message column. |
| 10 |
ITDataManagement.pdf: "I/O Tag Properties" section, pages 23-24 WM.chm: "I/O Tag Properties" topic |
-- |
In the Min Value row, add bullets in the Integer and Real columns. In the Priority row, add a bullet in the Message column. In the Square Root Conversion row, add bullets in the Integer and Real columns. |
The InTouch HMI product books consist of a set of Portable Document Files (PDF) located on the installation CD. Each book is a separate PDF file. You need Adobe Reader installed on your computer to view the InTouch books. You can download the latest version of Adobe Reader from the Adobe Corporation web site:
www.adobe.com/products/acrobat/readstep2.htm
After installing Adobe Reader, double-click on 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.
The InTouch HMI library includes a navigational book titled the InTouch HMI Guide to Documentation. This book provides an overview of all the books in the library and summarizes their contents. Use this book as a navigational aid to quickly find the information you need. Also, use the procedure described in Searching InTouch Books with Adobe Reader to search for information within all books of the InTouch HMI library simultaneously.
InTouch HMI installation instructions are located in the root folder of the InTouch installation CD as an online help file. You can view these instructions by clicking Help as you complete the InTouch installation procedure.
Product documentation is also available as online help. Click Help from an InTouch window to view the online help that describes the function you are currently using.
The InTouch HMI version 10 books are delivered as an Adobe PDF package, which provides a master index of all books. Using Adobe Reader, you can simultaneously search for a specific topic across all books that belong to the InTouch HMI product library.
To search for information across all books
© 2007 Invensys Systems, Inc. All Rights Reserved.