If you update with a Setup. You can also use the full InTouch To update to InTouch Version You can upgrade to InTouch version The following list shows earlier versions of InTouch that can be upgraded to version Important: You must use the full InTouch Adding or removing InTouch components during an upgrade is not recommended. You do not need to migrate your existing InTouch applications created with either InTouch version The existing application version is maintained after Patch 02 has been applied.
Applications created with versions of InTouch earlier than version This section explains how to apply Patch 01 to existing instances of InTouch version 10 installed at your site. The Patch 01 Setup. You can copy the Setup. This section lists known issues that remain in the InTouch version 10 Patch The issues are identified by their Change Request number.
An interim solution for this problem is to embed the symbol into another ArchestrA symbol and do the overrides there because it permits Unicode characters.
You can substitute public custom properties used as references in an embedded ArchestrA Symbol with alternate references. Only references from public custom properties can be substituted in an embedded ArchestrA symbol. The ArchestrA IDE provides an extensive set of graphic and scripting tools to create complex symbols that can be embedded into InTouch applications. For updates to this information, see the Wonderware Technical Support website at www. These recommendations are for development systems.
Run-time requirements may be different, depending on the InTouch application and other factors. This section describes the operating system and other software requirements to install InTouch HMI version The following table lists the supported operating systems that can be installed on computers running InTouch server and client components. The following list describes other third-party software requirements to support InTouch HMI version 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.
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. The version of MDAC installed on the computer is verified during the installation of version If you are upgrading from InTouch version 7.
If InTouch 7. Otherwise, the installation cannot update the files properly. If you uninstall InTouch 7. Install InTouch Terminal Services on a stand-alone 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 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. 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.
The known issues are grouped by function. L 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.
Do not use setup. Install the second ArchestrA product by running the setup. Compatibility issues with CLR2. Because Microsoft. Refer to Microsoft Knowledge Base issue KB for details and a link to download the replacement file. After the license file is installed, edit the file's properties and clear the read-only attribute. L Installing legacy components version 7. If you wish to continue using legacy Wonderware products, install the FactorySuite common components from the Device Integration product CD prior to installing the ArchestrA components.
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. If the shortcut is not available, the License Utility can be launched by locating licview. 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.
L Action scripts with remote references are lost when SmartSymbols are exported and imported. Animation links are lost if a reference to a Quick 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. L 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. Instead, the first reference to the instance does not accept the first parameter. The actual results are: Galaxy:me. L The input field of a user input animation link should be resizable to fit higher resolution screens.
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. See the following example. Normally, these tag types do not appear in InTouch scripts. L 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.
L 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. L 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. All of these AppEngines are deployed. L 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.
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. When you attempt to deploy an instance of an application, a failure occurs because the Galaxy's required version 3.
A tag's value updates correctly if it is ran from a Synchronous Quick Function. The conditions that cause a condition script to go into an infinite loop are shown in the following list:. L After a failover, not all topics transfer to the secondary tag source of an Access Name. Problems can occur if you define a new Access Name that is a duplicate of an assigned internal secondary Access Name.
L Query Filter for an alarm comment does not retrieve any records during language switching. This is because the old database contains existing alarm comments without unique characters and new alarm comments with concatenated unique characters. 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. L InTouch application on a non-upgraded remote node cannot see an alarm generated on a upgraded remote node.
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. Based on the timing of the deployment, there is a good chance that the next version of the AreaHierarchy.
The ITAlarmProvider cannot determine if the areas have been undeployed and redeployed. L 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. L 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.
L 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.
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. As a result, both functions return either incomplete or incorrect data from scripts that query the status of an ArchestrA data channel. 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. 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.
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:. You can also open a book with the Adobe Reader Open command from the File menu. 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. 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.
Using Adobe Reader, you can simultaneously search for a specific topic across all books that belong to the InTouch HMI product library. Before installing the Service Pack: Ensure that you create good known backups of all applications and galaxies.
This service pack requires InTouch applications be converted recompiled prior to running. You can convert stand-alone or published applications directly from WindowMaker. A development license must be present in the node to allow access to WindowMaker. After conversion, applications cannot be opened or run using InTouch 10 versions older than InTouch 10 service pack 2.
Ensure that application dependencies, such as ActiveX controls and add-on functions are installed to WindowMaker before you convert the application using the IDE.
Applications that have existing corruptions may affect the conversion process. Installing Wonderware Application Server 3. Managed applications that are deployed to the platform are also removed. The workflow for importing windows from other applications has been modified.
To prevent manipulation of windows outside the supported environment, windows that are to be imported into an InTouch application must be exported first from the existing application. ONLY windows that are in an "exported" state are allowed to be imported into an application. The Antivirus Software Issues list has been updated. Click this Antivirus Software Issues link for details. Use the following links to the various sections of this Readme.
InTouch Version Hardware Recommendations : Hardware requirements remain unchanged since the initial release of InTouch version Software Requirements : Several Windows operating systems have had service pack updates since the initial release of InTouch version Important: InTouch If you attempt to update to SP2 with a different language than your installed instance of InTouch, you may have to completely uninstall and then reinstall InTouch.
You cannot re-install an earlier version of InTouch For example, the update fails if you attempt to re-install InTouch To update InTouch Version Using Windows Explorer, double-click on the Setup. Click Next in the Welcome dialog box. Accept the Wonderware license agreement and click Next. In the Select Features and Destination Folder dialog box, select the optional components, if any, to install with InTouch, and then click Next. Click Next to continue installing InTouch on your computer. The Updating System dialog box shows the progress of the SP2 update.
Click Finish. Restart your computer. Verify that your instance of InTouch is at version Click Help from the Application Manager menu bar. Click About Application Manager. You should see Version: The issues are listed by their Change Request number: L : Memory consumption increases rapidly when you import new windows into a large InTouch application.
See SR and SR L : An InTouch tag assigned to a custom property can be written to and from multiple Terminal Service sessions on the same physical client, running separate applications with the same tagname defined.
See SR L : In a Terminal Services environment, an InTouch:Tagname ArchestrA symbol assigned to a custom property can be written to and from multiple sessions or from different physical clients when the InTouch application is running and a client session is restarted from a different client.
L : When copying a group of graphic elements and pasting them on a different graphic, all the elements are not copied and pasted.
L : Visual Element Reference List VERL corruption can occur when you import windows from another managed InTouch application that has symbol references that have not been updated due to renames or deletions. L : The wrong symbols are shown at run time upon deploy changes.
L : Custom properties for ArchestrA symbols do not work if the graphic symbol is placed beyond the by pixel region. The process always prompts you to restart WindowViewer rather than automatically loading the changes. L : MX references should read and write values, when the application is running on a Terminal Services client session and the application is restarted on the Console.
L : WindowMaker crashes while converting a managed application that has an ActiveX reference, if the corresponding ActiveX control is not installed to WindowMaker.
Install ActiveX controls and add-on functions before accessing WindowMaker. You add these functions to the InTouch installation folder to make them available in the application. When you open or migrate an application on a computer that does not have the add-on functions installed, then the system may treat them as tag names and attempt to define them as tag names, which will corrupt the application.
L : A WindowViewer client application containing graphic symbols fails to restart the first time if a master application directory is unavailable on the Network Application Development node. Red errors are logged in the System Management Console. Restarting the WindowViewer application works, even if the master application directory is unavailable.
Software Requirements : Several Windows operating systems have distributed service pack updates since the initial release of InTouch version If you attempt to update to SP1 with a different language than your installed instance of InTouch, you may be forced to completely uninstall and then reinstall InTouch.
Click Next from the Welcome dialog box. In the Select Features and Destination Folder dialog box, do any of the following, and then click Next. Select the optional components, if any, to install with InTouch. Click Browse if you want to change the folder location where InTouch is installed. The Updating System dialog box shows the progress of the SP1 update. If requested, click Yes to restart your computer. L : An unhandled exception occurs in WindowViewer after pressing an application button that is associated with a script containing the hideself function.
L : Scripts associated with the click event of an Alarm Viewer control do not appear if the script refers to an undefined tag. L : A. NET control that is docked to the right is drawn on the left-hand side of the symbol. If the symbol is saved and used in an InTouch application, the control appears correctly on the right-side of the screen when the InTouch application is run.
L : The values shown from a secondary published process InTouch window do not refresh correctly if viewed from a Windows Information Server website. System Requirements. Installation Information. Internet Explorer 6. It is recommended that you read the DAServer Installation Guide prior to beginning the installation process. In addition to the procedures described in the DAServer Installation Guide , the following installation requirements and other requirements pertaining to the installation and uninstall orders have to be followed.
A DAServer must always be installed last. This installation order will ensure that any differences, which may exist in the common components included with individual product releases, will install and run without version conflicts. In case of any future patch on the installed Wonderware FactorySuite products, follow the particular installation instructions from the patch.
At the time of this release, InTouch, Version 7. Please check the FactorySuite Product version-compatibility matrix at www. Although Wonderware DAServers can communicate with multiple client protocols at the same time, you should be aware of the advantages and disadvantages of the technologies used for any particular protocol. As a result, there may be a chance that when the DAServer is connected remotely with an OPC client and the network is interrupted, a delay of six 6 minutes may be experienced in the OPC client program before declaring the connection to the DAServer a failure.
Please note that this is expected; the DAServer remains active and continues to provide data connectivity to other clients that have good network connections. When installed on a Windows operating system, the first time the DAServer is activated, a "server busy" message may appear.
Subsequent activation of the DAServer will not produce this message. Windows NT 4. Internet Explorer 6. The following defects were fixed for this patch release. Click on the defect number for a more detailed description of the problem. L 3Dtext and text object in Japanese version of InTouch 7.
L In the French version of InTouch 7. L AlarmDBView Control takes a long time to get populated with data if database contains a large number of records. L The "Invalid floating pt value" error message box is not modal is hidden. L SuperTags are not shown in alphabetical order, but are in the order in which they were created. L Logger shows Mutex errors after a few days of running InControl. L Wizard is not retaining animation links.
L "Not enough space for string - new name too long? L There is a difference in the text display block between single and double byte characters.
Double byte character fields are much wider that the text included. L Unexpected results occur when setting width of pen in pen trend during design time. L Fonts display is 'blotchy' in WindowMaker when using 'Smooth edges of screen fonts' setting. Fonts in WindowViewer are displayed OK. L Tag assignment in pen window results in "Tagname. L The Edit Custom Color dialog box, when opened from the pen trend control dialog box, causes WindowMaker to crash.
L X or Y location of window changes when reducing the width or height of the window manually and without saving and closing. L When a new application and a new window are created, printing the window disables WindowMaker after the printout. L In the 16 Pen Trend environment, switching between WindowMaker and WindowViewer and then clicking on the scooter or F2 will increase its size. L In the 16 Pen Trend environment, Pen Trend goes blank in the run-time if trend is stopped Stop button while the Configuration dialog box is opened.
L In the Japanese version of InTouch, creating an application path with certain Japanese characters and deleting the application from the list causes the InTouch Application Manager to not find the application. L Alarm DB Logger will not function if there are more than 16 lines of queries in its Alarm Query configuration. L The sharing of the Wonderware license folder when InTouch is started is a security concern. Provide the ability to halt the sharing of this folder. L After installation of InTouch 7.
L Enhancement to the pen trend functionality to eliminate occasional double thick line. L WindowViewer crashes on initialization of a HistData wizard. L In the Japanese version of InTouch, the color fill animation link is the opposite of what is true. L In Historical trending mode, pen trend, the start time of the trend is the current time. This problem results in an empty future trend.
L In the Japanese version of InTouch, the error "can not open tagname. L Changing the font properties does not always provide the same results. ACK was used, or when the almAck comment was blank empty string. L Unreadable characters displayed in the keypad a dash "-" looks the same as period ". L WWRequest does not function after a failed connection.
InSQL shows Null until the tag changes value. L Alarm DB Restore stops restoring when it encounters comments in the comment file that contain a comma. L Windows Textbox only displays characters of a character-long tag. L A gap is displayed on the right side of a historical trend during the fall back time change in October for Greenwich time zone when it is set to auto adjust for time change.
L Enhancement request: New feature to be able to bypass the creation of placeholders based on the existence of tags in the tagname dictionary when windows and scripts are imported from one application to another. L Screen display flickers when halo is bigger than screen resolution and the mouse is moved over push buttons. L When browsing tags during historical trend pen assignment, the entire remote tagname dictionary is displayed instead of only the history tags.
L If an application is developed with a later version of InTouch, the Application Manager states the version as 'Old'. L The alarm system registers Rate of Change alarm based on a previous setpoint at startup when Retentive Parameters is selected for a tag. L Not enough disk space error is displayed when trying to install InTouch Patch 5a.
L Alarm entries are corrupted when acknowledged if the AlarmUserDefStr is set in the application on a start script. UpdateView on method call execute. Exception 0xAB: Object variable or With block variable not set". L 60k license is not allowing over 61, RTR and local tags, total. L Text Object's Font size does not save correctly when modifications are done with the mouse.
L The InTouch Keyboard is shown even when the check box is cleared. L When you open an application created in an English version of InTouch in a Japanese WindowMaker, some characters' font size changes. L Attempting to display historical data in a trend when the selected range spans a Daylight Savings Time transition loses data. L Terminal Services client connects to a server and runs WindowViewer in a different screen resolution than that of the server application, and the font size is not adjusted to the client environment when set to Japanese as its default language or when using a Japanese OS.
Back to Top. Back to Resolved Issues. Problem: Times New Roman font is rotated 90 degrees, and Terminal font is incorrect. French, German InTouch The user would receive the error message "You must first select an InTouch object" when trying to add an object, even though the object was, in fact, selected. This has been fixed. Also, if a new library was created and then an item added, it succeeds but the object is blank in the library.
All INI file operations were modified to use the Registry instead. This allows the Symbol Factory to operate properly under Windows XP if a restricted-access user is logged on. Three new Registry entries and a help file for Symbol Factory were introduced in this patch. Running the same query from Query Analyzer also has the same delay. Delay is greatest when SQL Server is on another node.
0コメント