InTouch 10.0 SP2
InTouch Version 10 Service Pack 2 Readme
Last revision: 12/22/2008
About This Readme
This Readme combines information from InTouch 10.0 Service Pack 2 (SP2) with previous Readme files included with Wonderware® InTouch® version 10.0 and its prior service pack and patches:
- InTouch version 10.0.100 (SP1)
- InTouch version 10.0.003 (Patch 03)
- InTouch version 10.0.002 (Patch 02)
- InTouch version 10.0.001 (Patch 01)
- InTouch version 10.0 (No Patch)
The information from these Readme files is in order based on when the InTouch versions were released.
Important!
- Before installing the Service Pack:
- Ensure that you create good known backups of all applications and galaxies.
- If you use the InTouch application with ArchestrA Symbols, run the ArchestrA Symbol Analysis and Repair Utility and ensure all issues reported by the utility are addressed.
- This service pack requires InTouch applications be converted (recompiled) prior to running. You can convert stand-alone or published applications directly from WindowMaker. You must convert managed InTouch applications by accessing WindowMaker through the IDE. 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.
- If InTouch 10.0x and Application Server 3.0x are installed on the same node, they both must be upgraded to Application Server 3.0 SP2 and InTouch 10.0 SP2.
- Installing Wonderware Application Server 3.0 Service Pack 2 automatically undeploys a platform that is currently deployed in the node that is being updated. Managed applications that are deployed to the platform are also removed. See the section "Applying SP2 to Wonderware Application Server 3.0" in the Readme for Application Server 3.0 SP2 for full details on installing the service pack.
- 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.
This Readme explains how to apply SP2 to InTouch version 10.0 and its previous service pack and patches. This Readme lists all resolved issues in InTouch version 10.0 and the service pack and patches. It also includes descriptions of any known product issues that remain unresolved and possible interim solutions.
Use the following links to the various sections of this Readme.
InTouch Version 10.0 SP2 Information
Requirements to Apply InTouch 10.0 SP2
Compatibility Requirements for InTouch 10.0 SP2
Applying SP2 to InTouch Version 10.0
Migrating Applications to InTouch 10.0 SP2
Resolved Issues - InTouch Version 10.0 SP2
Known Issues - InTouch Version 10.0 SP2
InTouch Version 10.0 SP1 Information
Requirements to Apply InTouch 10.0 SP1
Compatibility Requirements for InTouch 10.0 SP1
Applying SP1 to InTouch Version 10.0
Migrating Applications to InTouch 10.0 SP1
Resolved Issues - InTouch Version 10.0 SP1
Known Issues - InTouch Version 10.0 SP1
InTouch Version 10.0 Patch 03 Information
Requirements to Apply InTouch 10.0 Patch 03
Applying Patch 03 to InTouch Version 10.0
Resolved Issues - InTouch Version 10.0 Patch 03
Known Issues - InTouch Version 10.0 Patch 03
InTouch Version 10.0 Patch 02 Information
Requirements to Apply InTouch 10.0 Patch 02
Applying Patch 02 to InTouch Version 10.0
Upgrading Earlier Versions of InTouch to InTouch Version 10.0 Patch 02
Migrating Applications from Earlier InTouch Versions to InTouch 10.0 Patch 02
Resolved Issues - InTouch Version 10.0 Patch 02
InTouch Version 10 Patch 01 Information
Applying Patch01 to InTouch Version 10
Resolved Issues - InTouch Version 10 Patch 01
Known Issues - InTouch Version 10 Patch 01
InTouch Version 10 Information
Upgrading from a Previous Version
Known Issues – InTouch HMI Version 10
InTouch HMI Documentation Issues
Requirements to Apply InTouch 10.0 SP2
This section describes the hardware and software requirements to install InTouch 10.0 SP2. Use the following links for information about the original hardware and software requirements when InTouch version 10.0 was released in August 2007.
-
Hardware Recommendations:
Hardware requirements remain unchanged since the initial release of InTouch version 10.0. - Software Requirements:
Several Windows operating systems have had service pack updates since the initial release of InTouch version 10.0. InTouch 10.0 SP2 also supports Windows XP Pro Service Pack 3 and Windows Vista Service Pack 1.Important:
InTouch 10.0 SP2 does not support .NET Framework 2.0 SP1 nor .NET Framework 3.5. InTouch 10.0 SP2 only supports the versions of .NET Framework described in the original InTouch 10.0 Readme. InTouch 10.0 SP2 requires Microsoft .NET Framework 2.0 at version CLR 2.0.50727.42, or .NET Framework 3.0.
Antivirus Software Issues
Configure the antivirus software such that the antivirus software does not process files in the following ArchestrA folders:
C:\Program Files\ArchestrA\
C:\Program Files\Common files\ArchestrA\
C:\Program Files\FactorySuite\ (may not exist in
newer installations)
C:\Program Files\Wonderware
C:\InSQL\Data\
From Application Server Platform objects:
- History Store Forward directory: (if not default)
From Application Server Engine objects:
- Checkpoint directory location (if not default)
<InTouch Application folder path> including:
C:\Documents and Settings\All Users\Application Data\ArchestrA\
<SMC Logger Storage file path>. The
default is:
C:\Documents and Settings\All Users\Application Data\ArchestrA\LogFiles\
SQL server database type files
- .mdf
- .Ldf
Compatibility Requirements for InTouch 10.0 SP2
If InTouch 10.0x and Application Server 3.0x are installed on the same node, they both must be upgraded to Application Server 3.0 SP2 and InTouch 10.0 SP2.
Applying SP2 to InTouch Version 10.0
This section explains how to apply SP2 to existing instances of InTouch version 10.0 installed at your site. SP2 is distributed on a re-mastered InTouch version 10 product CD. Localized versions of the SP2 CD are also available in different languages.
InTouch Version Requirements to Apply SP2
The following table shows how to apply SP2 to InTouch 10.0 and earlier versions of InTouch.
| Current Installed Version of InTouch | Description | Direct Update with SP2 | Special Update Requirements |
| InTouch version 8.0 SP2 Patch 04 | InTouch version 8.0 Service Pack 2 with Patch 04 applied | Yes | Requires an InTouch version 10.0 license |
| InTouch version 8.0 TSE SP2 Patch 04 | InTouch version TSE 8.0 Service Pack 2 with Patch 04 applied | Yes | Requires an InTouch version 10.0 license |
| InTouch version 9.0 Patch 03 | Base install of InTouch version 9.0 with Patch 03 applied | Yes | Requires an InTouch version 10.0 license |
| InTouch version 9.0 TSE Patch 03 | Base install of InTouch version 9.0 TSE with Patch 03 applied | Yes | Requires an InTouch version 10.0 license |
| InTouch version 9.5 Patch 03 or SP2 | Base install of InTouch version 9.5 with Patch 03 or SP2 applied | Yes | Requires an InTouch version 10.0 license |
| InTouch version 9.5 TSE Patch 03 or SP2 | Base install of InTouch version 9.5 TSE with Patch 03 or SP2 applied | Yes | Requires an InTouch version 10.0 license |
| InTouch version 10.0.000 | Base install of InTouch version 10.0 | Yes | None |
| InTouch version 10.0.000 TSE | Base install of InTouch version 10.0 TSE | Yes | None |
| InTouch version 10.0.01 | Base install updated with Patch 01 | Yes | None |
| InTouch version 10.0.01 TSE | Base install of InTouch 10.0 TSE updated with Patch 01 | Yes | None |
| InTouch version 10.0.002 | Base install of InTouch 10.0 or InTouch 10.0.01 updated with Patch 02 | Yes | None |
| InTouch version 10.0.002 TSE | Base install of InTouch 10.0 TSE or InTouch 10.0.01 TSE updated with Patch 02 | Yes | None |
| InTouch version 10.0.003 | InTouch version 10.0 or InTouch 10.0.002 updated with Patch 03 | Yes | None |
| InTouch version 10.0.003 TSE | InTouch version 10.0 TSE or InTouch 10.0.002 TSE updated with Patch 03 | Yes | None |
| InTouch version 10.0 SP1 | InTouch version 10.0 updated with SP1 | Yes | None |
| InTouch version 10.0 SP1 TSE | InTouch version 10.0 updated with SP1 TSE | Yes | None |
Important SP2 Update Notes:
- You must apply an InTouch version 10.0 Wonderware product license to upgrade a version of InTouch prior to version 10.0 with the SP2 re-mastered CD.
- You must update InTouch version 10 to SP2 in the same language as your installed instance of 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 10.0 after SP2 is applied. For example, the update fails if you attempt to re-install InTouch 10.0 Patch 03 on an installed instance of InTouch version 10.0 SP2.
To update InTouch Version 10.0 with SP2
- Log on to the computer as an administrator.
- Close Application Manager, WindowMaker, or WindowViewer if they are running.
- Place the InTouch version 10 SP2 CD in the computer's CD-ROM drive or browse the folder where an image of the SP2 CD has been copied.
- Using Windows Explorer, double-click on the Setup.exe file to start the update.
- 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.
- In the Ready to Install Wonderware InTouch dialog box, scroll the list to verify your InTouch installation choices.
-
Click Next
to continue installing InTouch on your computer.
The Updating System dialog box shows the progress of the SP2 update. - If the OS Configuration Utility dialog box appears, click OK to continue installing SP2.
- Click Finish.
- Restart your computer.
- Verify that your instance of InTouch is at version 10.0.200 by completing the following procedure.
To verify InTouch Version 10.0 has been updated to Service Pack 2
- Start Application Manager.
- Click Help from the Application Manager menu bar.
-
Click About Application
Manager. The About
InTouch Application Manager dialog box shows the InTouch
version installed on the computer.
You should see Version: 10.0 SP2 listed in the dialog box after SP2 is installed.
Migrating Applications to InTouch 10.0 SP2
All applications created from InTouch version 7.0 through InTouch 10.0 SP1 can be migrated directly to InTouch 10.0 SP2. Applications created with InTouch prior to version 7.0 must be first converted to a version 7.0 application and then migrated to InTouch 10.0 SP2.
You are required to migrate your existing InTouch applications created with InTouch version 10.0 or its service pack or patches. The existing InTouch applications will be migrated to the new version of InTouch 10.0 SP2 when you open WindowMaker for the first time after installing the SP2.
Resolved Issues - InTouch Version 10.0 SP2
InTouch version 10.0 SP2 resolves the following issues. The issues are listed by their Change Request number:
| L00080689: | Memory consumption increases rapidly when you import new windows into a large InTouch application. (See SR23930042) |
| L00080774: | The error message “Compatible version of WindowMaker is not installed” appears when you try to open an InTouch TSE application using the IDE. (See SR24513243) |
| L00080775: | If two windows are open in WindowViewer that have ActiveX AlarmTreeViewer controls on each window, one window does not show any information. (See SR 103113133) |
| L00081535: | When a "While Showing" script runs every 500 milliseconds and writes data to the Galaxy, memory consumption for the View.exe process increases 4k every 2/3-seconds. (See SR33410298) |
| L00082673: | In a Terminal Server environment, the “Anonymous Engine ID” value is not being released, or decremented when WindowViewer itself terminates (shuts down) the terminal session. (See SR15314499) |
| L00083320: | A GDI Object handle leak exists in WindowViewer when a window that contains a text object and a combo box is opened and closed. (See SR 103113472) |
| L00083685: | Fast switching of ArchestrA pop-up Symbols and normal user interaction with ArchestrA symbols causes the WindowViewer to crash. (See SR24513590) |
| L00083733: | InTouch:<Tagname> remote references and custom properties in ArchestrA symbols are not updating when the InTouch WindowViewer is running on a Terminal Server client session. (See SR23516653 and SR19416452) |
| L00083951: | 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 SR10415014) |
| L00084011: | The AlarmViewer control display lines show gaps if you scroll up and down. (See SR33810560) |
| L00084049: | You cannot close a modeless ArchestrA pop-up Symbol after installing Wonderware Application Server 3.0 SP1. (See SR37510020) |
| L00084878: | 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. |
| L00084935: | When copying a group of graphic elements and pasting them on a different graphic, all the elements are not copied and pasted. |
| L00084955: | The
Visual Element Reference List (VERL) of a managed InTouch application
can become corrupted if WindowMaker is not gracefully shut down
preventing synchronization of the application information with the
Galaxy Repository. |
| L00084956: | 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. |
| L00085031: | The wrong symbols are shown at run time upon deploy changes. |
| L00085119: | If an ArchestrA IDE is closed before saving a window with an embedded ArchestrA Symbol in an InTouchApp, a crash of the IDE occurs, when you click on an ArchestrA Symbol after restarting the ArchestrA IDE. |
| L00085368: | Custom properties for ArchestrA symbols do not work if the graphic symbol is placed beyond the 2000 by 2000 pixel region. (See SR103113360) |
Known Issues - InTouch Version 10.0 SP2
This section describes known issues identified in InTouch version 10.0 SP2.
| L00081320: | "Load changes to WindowViewer" does not work for managed InTouch applications. The process always prompts you to restart WindowViewer rather than automatically loading the changes. |
| L00086172: | 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. |
| L00086256: | In a Terminal Services client session, direct remote references in ArchestrA symbols (e.g. InTouch:AccessName1:IO100) linked to DDE Access Names do not work; however, references placed in InTouch windows work. |
| L00087126: | 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. Add-on functions are a set of script functions not included with the InTouch HMI. You can get them from the Wonderware Knowledge Base CD and Technical Support sites. 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. |
| L00087647: | 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. |
InTouch Version 10 Service Pack 1 Readme
Last revision: 08/08/2008
About This Readme
This Readme combines information from InTouch 10.0 Service Pack 1 (SP1) with previous Readme files included with Wonderware® InTouch version 10.0 and its prior patches:
- InTouch version 10.0.003 (Patch 03)
- InTouch version 10.0.002 (Patch 02)
- InTouch version 10.0.01 (Patch 01)
- InTouch version 10.0
The information from these Readme files is in order based on when the InTouch versions were released.
This Readme explains how to apply SP1 to InTouch version 10.0 and its patches. This Readme lists all resolved issues in InTouch version 10.0 and the patches. It also includes descriptions of any known product issues that remain unresolved and possible interim solutions.
Use the following links to the various sections of this Readme.
InTouch Version 10.0 SP1 Information
Requirements to Apply InTouch 10.0 SP1
Compatibility Requirements for InTouch 10.0 SP1
Applying SP1 to InTouch Version 10.0
Migrating Applications from Earlier Versions of InTouch to InTouch 10.0 SP1
Resolved Issues - InTouch Version 10.0 SP1
Known Issues - InTouch Version 10.0 SP1
InTouch Version 10.0 Patch 03 Information
Requirements to Apply InTouch 10.0 Patch 03
Applying Patch 03 to InTouch Version 10.0
Resolved Issues - InTouch Version 10.0 Patch 03
InTouch Version 10.0 Patch 02 Information
Requirements to Apply InTouch 10.0 Patch 02
Applying Patch 02 to InTouch Version 10.0
Upgrading Earlier Versions of InTouch to InTouch Version 10.0 Patch 02
Migrating Applications from Earlier Versions of InTouch to Patch 02
Resolved Issues - InTouch Version 10.0 Patch 02
InTouch Version 10 Patch 01 Information
Applying Patch01 to InTouch Version 10
Resolved Issues - InTouch Version 10 Patch 01
Known Issues - InTouch Version 10 Patch 01
InTouch Version 10 Information
New Features of InTouch Version 10
Upgrading from a Previous Version
Known Issues – InTouch HMI Version 10
InTouch HMI Documentation Issues
Requirements to Apply InTouch 10.0 SP1
This section describes the hardware and software requirements to install InTouch 10.0 SP1. Use the following links for information about the original hardware and software requirements when InTouch version 10.0 was released in August 2007.
-
Hardware Recommendations:
Hardware requirements remain unchanged since the initial release of InTouch version 10.0. - Software Requirements:
Several Windows operating systems have distributed service pack updates since the initial release of InTouch version 10.0. InTouch 10.0 SP1 also supports Windows XP Pro Service Pack 3 and Windows Vista Service Pack 1.Important:
InTouch 10.0 SP1 does not support .NET Framework 2.0 SP1 nor .NET Framework 3.5. InTouch 10.0 SP1 only supports the versions of .NET Framework described in the original InTouch 10.0 Readme. InTouch 10.0 SP1 requires Microsoft .NET Framework 2.0 or .NET Framework 3.0, which are both at version CLR 2.0.50727.
Compatibility Requirements for InTouch 10.0 SP1
If InTouch 10.0 SP1 will be installed on a computer that belongs to an ArchestrA Galaxy, Application Server must be updated with SP1 too. All InTouch or Application Server components that belong to the same Galaxy must be updated to SP1. InTouch must be at version 10.0 SP1 and Application Server at version 3.0 SP1.
Applying SP1 to InTouch Version 10.0
This section explains how to apply SP1 to existing instances of InTouch version 10.0 installed at your site. SP1 is distributed on a re-mastered InTouch version 10 product CD. Localized versions of the SP1 CD are also available in different languages.
InTouch Version Requirements to Apply SP1
The following table shows the pathways to apply SP1 to InTouch 10.0 and earlier versions of InTouch.
| Current Installed Version of InTouch | Description | Direct Update with SP1 | Special Update Requirements |
| InTouch version 8.0 SP2 Patch 04 | InTouch version 8.0 Service Pack 2 with Patch 04 applied | Yes | Requires an InTouch version 10.0 license |
| InTouch version 8.0 TSE SP2 Patch 04 | InTouch version TSE 8.0 Service Pack 2 with Patch 04 applied | Yes | Requires an InTouch version 10.0 license |
| InTouch version 9.0 Patch 03 | Base install of InTouch version 9.0 with Patch 03 applied | Yes | Requires an InTouch version 10.0 license |
| InTouch version 9.0 TSE Patch 03 | Base install of InTouch version 9.0 TSE with Patch 03 applied | Yes | Requires an InTouch version 10.0 license |
| InTouch version 9.5 Patch 03 or SP1 | Base install of InTouch version 9.5 with Patch 03 or SP1 applied | Yes | Requires an InTouch version 10.0 license |
| InTouch version 9.5 TSE Patch 03 or SP1 | Base install of InTouch version 9.5 TSE with Patch 03 or SP1 applied | Yes | Requires an InTouch version 10.0 license |
| InTouch version 10.0.000 | Base install of InTouch version 10.0 | Yes | None |
| InTouch version 10.0.000 TSE | Base install of InTouch version 10.0 TSE | Yes | None |
| InTouch version 10.0.01 | Base install updated with Patch 01 | Yes | None |
| InTouch version 10.0.01 TSE | Base install of InTouch 10.0 TSE updated with Patch 01 | Yes | None |
| InTouch version 10.0.002 | Base install of InTouch 10.0 or InTouch 10.0.01 updated with Patch 02 | Yes | None |
| InTouch version 10.0.002 TSE | Base install of InTouch 10.0 TSE or InTouch 10.0.01 TSE updated with Patch 02 | Yes | None |
| InTouch version 10.0.003 | InTouch version 10.0 or InTouch 10.0.002 updated with Patch 03 | Yes | None |
| InTouch version 10.0.003 TSE | InTouch version 10.0 TSE or InTouch 10.0.002 TSE updated with Patch 03 | Yes | None |
Important SP1 Update Notes:
- You must apply an InTouch version 10.0 Wonderware product license to upgrade a version of InTouch prior to version 10.0 with the SP1 re-mastered CD.
- You must update InTouch version 10 to SP1 in the same language as your installed instance of InTouch. 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.
- You cannot re-install an earlier version of InTouch 10.0 after SP1 is applied. For example, the update fails if you attempt to re-install InTouch 10.0 Patch 03 on an installed instance of InTouch version 10.0 SP1.
To update InTouch Version 10.0 with SP1
- Log on to the computer as an administrator.
- Close Application Manager, WindowMaker, or WindowViewer if they are running.
- Place the InTouch version 10 SP1 CD in the computer's CD-ROM drive or browse the folder where an image of the SP1 CD has been copied.
- Using Windows Explorer, double-click on the Setup.exe file to start the update procedure.
- Click Next from the Welcome dialog box.
- Accept the Wonderware license agreement and click Next.
- 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.
- In the Ready to Install Wonderware InTouch dialog box, scroll the list to verify your InTouch installation choices.
-
Click Next
to continue installing InTouch on your computer.
The Updating System dialog box shows the progress of the SP1 update. - If the OS Configuration Utility dialog box appears, click OK to continue installing SP1.
- Click Finish.
- If requested, click Yes to restart your computer.
- Verify that your instance of InTouch is at version 10.0.100 by completing the following procedure.
To verify InTouch Version 10.0 has been updated to Version 10.0.100
- Start Application Manager.
- Click Help from the Application Manager menu bar.
-
Click About Application
Manager. The About
InTouch Application Manager dialog box shows the InTouch
version installed on the computer.
You should see Version: 10.0.100 listed in the dialog box after SP1 is installed.
Migrating Applications to InTouch 10.0 SP1
All applications created from InTouch version 7.0 through InTouch 10.0 Patch 03 can be migrated directly to InTouch 10.0 SP1. Applications created with InTouch prior to version 7.0 must be first converted to a version 7.0 application and then migrated to InTouch 10.0 SP1.
You do not need to migrate your existing InTouch applications created with InTouch version 10.0 or its sequence of patches. The existing application version is maintained after updating InTouch with SP1.
Resolved Issues - InTouch Version 10.0 SP1
InTouch version 10.0 SP1 resolves the following issues. The issues are listed by their Change Request number:
| L00050706: | Starting and stopping WindowViewer changes the user's local security settings (Disable TaskMgr, DisableLockWorkstation, DisableChangePassword, NoCLose, NoLogOff) in the Windows Active Directory Group Policies. | ||
| L00057466: | WindowViewer freezes for several moments when the Alarm Printer Utility queries the InTouch alarm provider. | ||
| L00066442: | An InTouch application using a QIAnalyst DB connection ActiveX control no longer functions after it is converted to a managed application and deployed to a node other than the GR node. | ||
| L00067458: | WindowMaker fails after the Properties dialog box of the AlarmViewer control is opened, a new window is created, and the ENTER key is pressed. | ||
| L00070408: | An InTouchViewOEM license message indicates that the wwsuite.lic file was located, but the InTouchViewOEM feature line could not be found inside of it. The message appears every five minutes when running an application with an InTouch View Client HWKey license. | ||
| L00072216: | An unhandled exception occurs in WindowViewer after pressing an application button that is associated with a script containing the hideself() function. | ||
| L00073012: | Scripts associated with the click event of an Alarm Viewer control do not appear if the script refers to an undefined tag. | ||
| L00074111: | 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. | ||
| L00074135: | The Minimum Value and Maximum Value labels for the Resizable keyboard are swapped in the Japanese version of InTouch. | ||
| L00074282: | The values shown from a secondary published process InTouch window do not refresh correctly if viewed from a Windows Information Server website. | ||
| L00075202: | WindowViewer fails if the user minimizes, closes, or quick switches an InTouchView application containing an indirect reference in a graphic. | ||
| L00075600: | The InTouch Application Publisher / Expander does not correctly detect a failure to create or access the temporary file (DataFile.cmp) that it should create. | ||
| L00075601: | A text function does not return a negative number indicated by a minus sign ( - ) when formatted output is used. | ||
| L00075661: | The contained elements within a symbol can have duplicate element IDs if the element also belongs to a duplicated group. The duplicate element IDs result in the string substitutions being lost. | ||
| L00075732: | The symbol reference in the ShowSymbol animation changes when a group with child element configured with the animation is copied and pasted across symbols. | ||
| L00075734: | Double clicking the name of a tag in a script opens the correct tag from the Tagname Browser, but returns an incorrect tag after clicking Cancel, Close, or ESC. | ||
| L00075920: | Modifications to embedded ArchestrA graphics are not seen in a managed InTouch client application running on another node. | ||
| L00075921: | After modifying a running InTouch application, the dialog box that indicates that WindowViewer must be restarted, appears in the background. | ||
| L00075954: | The InTouch 16 Pen Trend utility cannot connect to the ArchestrA Attribute browser to select Galaxy tags while a managed application is running. | ||
| L00075955: | The InTouch PrintWindow() function does not print embedded ArchestrA graphics correctly. | ||
| L00075980: | An embedded ArchestrA symbol cannot be moved beyond the 2000 X 2000 pixel region of an InTouch window. | ||
| L00076010: | The InTouch Language Switching Export Dictionary function does not export all strings to the XML output file. | ||
| L00076027: | When two windows that each contain a checkbox window control are placed next to each other, the elements of the two windows start to flicker, making it difficult to operate WindowMaker. | ||
| L00076355: | The shape of a text object changes after resizing it in WindowMaker. | ||
| L00076516: | WindowMaker takes over five minutes to open a managed application. | ||
| L00076971: | The XML Import function fails on Tag Replacement when creating a window with many SmartSymbols. | ||
| L00077047: | WindowMaker crashes after opening and closing multiple windows containing trend controls when running InTouch on a Japanese language version of the Windows operating system. | ||
| L00077061: | The Alarm Printer Utility throws an error when attempting to open an existing configuration file created in InTouch 10.0 or its patches. | ||
| L00077204: | An InTouch application fails after running a script that contains the IsAnyAsyncFunctionBusy() function. | ||
| L00077262: | The wrong ArchestrA symbols can be replaced in a window while editing a managed application in WindowMaker if the SQL Server process in the GR Node is not available. | ||
| L00077661: | The Old Password field of the Change Password dialog box is limited to six characters when running localized versions of InTouch in Japanese or Chinese on computers running Windows Vista. | ||
| L00077712: | The Visual Element Reference List does not update correctly if an embedded ArchestrA symbol is renamed several times while the $InTouchViewApp template remains Checked In from the IDE. | ||
| L00077729: | The Visual Element Reference List shows incorrect values if an ArchestrA symbol is embedded in several InTouch managed application windows simultaneously and is renamed several times. | ||
| L00077755: | The status of an ArchestrA symbol is not updated to unbound in the Visual Element Reference List after the symbol is deleted. | ||
| L00077799: | The Visual Element Reference List is not updated after renaming a symbol to the same name as of a previously deleted symbol while InTouch WindowMaker is open. | ||
| L00077822: | ArchestrA symbols embedded in a managed InTouch application window do not appear correctly if they are renamed from the IDE. | ||
| L00077898: | The Visual Element Reference List is not updated after renaming and deleting an embedded ArchestrA symbol from a managed InTouch application whose InTouchViewApp template is not checked out or open. | ||
| L00077975: | An instance of an ArchestrA symbol cannot be embedded in a window from WindowMaker if the symbol name contains double-byte characters. | ||
| L00077999: | A copy of an embedded ArchestrA symbol appears as "NotFound" in WindowMaker if the name of the original embedded symbol contains double-byte characters. | ||
| L00078345: | Display Symbol animation with the position specified as Right of Symbol does not work with grouped objects. | ||
| L00078382: | WindowViewer crashes when trying to acknowledge all alarms with the Freeze option enabled. | ||
| L00078665: | Indirect tags are assigned to the same value by the Last BindTo statement if multiple indirect tags are declared in an ArchestrA graphic script. | ||
| L00078740: | The size, shape, and dimensions of ArchestrA symbols change after several consecutive move, flip, or rotation operations. | ||
| L00078905: | Some elements are missing after copying and pasting a group of elements between graphics. | ||
| L00079249: | Clicking on a WindowViewer window containing an ArchestrA symbol using animation does not reset the time out period specified by the $InactivityTimeout function within a script. | ||
| L00080044: | String values associated with an embedded ArchestrA symbol do not appear correctly from WindowViewer after the user clicks Yes to a message indicating the graphic was developed in a different language locale. The problem results from importing a symbol into an ArchestrA IDE that has a different language locale than the original IDE used to create the symbol. | ||
| L00080479: | An ArchestrA Symbol cannot be embedded in a managed application window beyond a 2000 X 2000 pixel area of the window. | ||
| L00080480: | The XML Import function fails on Tag Replacement when creating a window with many SmartSymbols. | ||
| L00081876: | On computers running Japanese or Chinese language versions of the Vista operating system, the password entry field of the User Configuration dialog box is limited to six characters. |
Known Issues - InTouch Version 10.0 SP1
This section describes known issues identified in InTouch version 10.0 SP1.
| L00077886: |
The ArchestrA Visual Element Reference List (VERL) shows incorrect
values after swapping the names of symbols from the ArchestrA IDE and
embedding them again into a managed InTouch application window from
WindowMaker.
You can prevent VERL errors from occurring by saving immediately after each symbol rename operation rather than saving only once after all symbols have been renamed. |
||
| L00082397: |
An assertion error occurs when migrating a version 7.11 application to
InTouch 10.0 SP1. This error results from attempting to migrate an
application containing more than 61,401 tags, which exceeds the maximum
limit of the Tagname Dictionary.
Before attempting to migrate a version 7.11 application to InTouch 10.0 SP1, ensure the tag count of the application is 61,401 or less. If necessary, remove tags from the application to be less than tag maximum before migrating the application to InTouch 10.0 SP1. |
InTouch Version 10.0 Patch 03 Readme
Last revision: 05/20/2008
About This Readme
This Readme combines information from previous Readme files distributed with Wonderware® InTouch version 10.0 and InTouch version 10.0 Patch 01 and Patch 02. The information from these Readme files is in order based on when the InTouch versions were released.
This Readme explains how to apply Patch 03 to InTouch version 10.0 and lists all resolved issues in InTouch version 10.0, Patch 01, Patch 02, and Patch 03. It also includes any known product issues that remain unresolved.
Patch 03 includes two files (Setup.msp and this ReadMe.html) to update an existing instance of InTouch version 10.0 to InTouch 10.0 Patch 03. Also, Patch 03 includes two files (SetupTS.msp and this ReadMe.html) to update an existing instance of InTouch 10.0 TSE.
Localized versions of Patch 03 are available to download from the Wonderware Technical Support web site. Patch 03 is also distributed on a CD containing localized versions of the Patch 03 files in separate folders.
Click on the following links to go to the various sections of this Readme.
InTouch Version 10.0 Patch 03 Information
Requirements to Apply InTouch 10.0 Patch 03
Applying Patch 03 to InTouch Version 10.0
Resolved Issues - InTouch Version 10.0 Patch 03
Known Issues - InTouch Version 10.0 Patch 03
InTouch Version 10.0 Patch 02 Information
Requirements to Apply InTouch 10.0 Patch 02
Applying Patch 02 to InTouch Version 10.0
Upgrading Earlier Versions of InTouch to InTouch Version 10.0 Patch 02
Migrating Applications from Earlier Versions of InTouch to Patch 02
Resolved Issues - InTouch Version 10.0 Patch 02
InTouch Version 10 Patch 01 Information
Applying Patch01 to InTouch Version 10
Resolved Issues - InTouch Version 10 Patch 01
Known Issues - InTouch Version 10 Patch 01
InTouch Version 10 Information
New Features of InTouch Version 10
Upgrading from a Previous Version
Known Issues – InTouch HMI Version 10
InTouch HMI Documentation Issues
Requirements to Apply InTouch 10.0 Patch 03
This section describes the hardware and software requirements to install InTouch 10.0 Patch 03, which are the same as InTouch version 10.0. Use the following links for information about the hardware and software requirements applicable to Patch 03.
Applying Patch 03 to InTouch Version 10.0
This section explains how to apply Patch 03 to existing instances of InTouch version 10.0 installed at your site. You can apply Patch 03 to the following versions of InTouch:
- InTouch version 10.0.000
- InTouch version 10.0.002 (Patch 02)
Important:
A direct update from InTouch 10.0 Patch 01 (version 10.0.001) to InTouch 10.0 Patch 03 (version 10.0.003) is not supported. If your instance of InTouch is at Patch 01, update to Patch 02 before applying Patch 03.
If you attempt to install Patch 03 on an InTouch 10.0 Patch 01 instance, you will receive an error indicating the patch cannot be installed by the Windows Installer service.
To update InTouch Version 10.0 with Patch 03
- Close Application Manager, WindowMaker, or WindowViewer if they are running.
- Open Windows Explorer, and then move to the location where the InTouch patch Setup.msp file is located.
- Double-click on the Setup.msp file to start the patch installation procedure.
- Click Next at the Welcome dialog box.
- Accept the Wonderware product license and click Next.
- Click Next to start installing files. The Updating System dialog box shows the progress of the patch update.
- If the OS Configuration Utility dialog box appears, click OK to continue installing the patch.
- Click Finish.
- Click Yes to restart your computer.
- Verify that your instance of InTouch is at version 10.0.003.
Verify InTouch Has Been Updated to Version 10.0.003
After you complete the update procedure, verify that your instance of InTouch version 10.0 is at version 10.0.003.
To verify InTouch Version 10.0 has been updated to Version 10.0.003
- Start Application Manager.
- Click Help from the Application Manager menu bar.
-
Click About Application
Manager. The About
InTouch Application Manager dialog box shows the InTouch
version installed on the computer.
You should see Version: 10.0.003 listed in the dialog box after Patch 03 is installed.
Resolved Issues - InTouch Version 10.0 Patch 03
InTouch version 10.0 Patch 03 resolves the following issues listed by their Change Request number:
| L00077355: | Incorrect ArchestrA graphics
appear in managed InTouch application windows after an embedded
ArchestrA graphic is duplicated with a Save As operation in
WindowMaker.
After the ArchestrA symbol is duplicated with a Save As operation, the visual element references contained within the WIN files become unsynchronized with the visual element reference list of the managed InTouch application. The possible result is that symbols show the wrong graphic, appear as NOT FOUND, and may have references to another graphic. |
||
| L00077356: | Incorrect ArchestrA graphics
appear in the windows of a managed InTouch application after the
embedded ArchestrA graphics are renamed in WindowMaker.
After the ArchestrA symbol is renamed, the visual element references contained within the WIN files become unsynchronized with the visual element reference list of the managed InTouch application. The result is that symbols show the wrong graphic, appear as NOT FOUND, and may have references to another graphic. |
Known Issues - InTouch Version 10.0 Patch 03
This section describes a known issue identified in InTouch version 10.0 Patch 03.
| L00077729: | The VERLs of multiple managed
InTouch applications do not match after a common, shared ArchestrA
symbol is renamed multiple times.
The issue results from the client-side template cache not being updated. This cache is based on the gobject ID and package ID, which do not change during the rename of a referenced ArchestrA symbol. To update the VERL property of an InTouch managed application, close and restart the ArchestrA IDE, which refreshes the cache. |
InTouch Version 10 Patch 02 Readme
Last revision: 02/11/2008
About This Readme
This Readme combines information from previous Readme files distributed with Wonderware® InTouch version 10.0 and InTouch version 10.0 Patch 01. The information from these Readme files are in chronological order based on when the InTouch versions were released.
This Readme explains how to apply Patch 02 to InTouch version 10.0 and upgrade an earlier version of InTouch to version 10.0 Patch 02. It also explains how to migrate applications from earlier versions of InTouch to the current version.
This Readme lists all resolved issues in InTouch version 10.0, Patch 01, and Patch 02. It also includes any known product issues that remain unresolved.
InTouch 10.0 Patch 02 is distributed by two separate product packages:
- Patch 02 includes two files (Setup.msp and Readme.html) to update an existing instance of InTouch version 10.0 to InTouch 10.0 Patch 02. Localized versions of Patch 02 are available to download from the Wonderware Technical Support web site. Patch 02 is also distributed as a mini-CD containing localized versions of the Patch 02 files in separate folders.
- InTouch 10.0 with Patch 02 Product CD includes a complete set of files to install or upgrade InTouch to version 10.0 Patch 02. This is the current product distribution CD and is available in localized versions for all languages supported by InTouch.
The following table shows the installation, update, and upgrade pathways to InTouch version 10.0 Patch 02:
| Current Installed Version of InTouch | Full InTouch 10.0 with Patch 02 Product CD | InTouch Patch 02 |
| None (New Install) | ● | |
| InTouch version 10.0.001 (Patch 01) | ● | ● |
| InTouch version 10.0.000 | ● | ● |
| InTouch version 9.5 Patches 01, 02, 03, and SP1 | ● | |
| InTouch version 9.0 Patch 03 | ● | |
| InTouch version 8.0 SP2 Patch 04 | ● |
Use the following links to the various sections of this Readme.
InTouch Version 10.0 Patch 02 Information
Requirements to Apply InTouch 10.0 Patch 02
Applying Patch 02 to InTouch Version 10.0
Upgrading Earlier Versions of InTouch to InTouch Version 10.0 Patch 02
Migrating Applications from Earlier Versions of InTouch to Patch 02
Resolved Issues - InTouch 10.0 Patch 02
InTouch Version 10 Patch 01 Information
Applying Patch01 to InTouch Version 10
Resolved Issues - InTouch Version 10 Patch 01
Known Issues - InTouch Version 10 Patch 01
InTouch Version 10 Information
New Features of InTouch Version 10
Upgrading from a Previous Version
Known Issues – InTouch HMI Version 10
InTouch HMI Documentation Issues
Requirements to Apply InTouch 10.0 Patch 02
This section describes the hardware and software requirements to install InTouch 10.0 Patch 02, which are the same as InTouch version 10.0. Use the following links for information about the hardware and software requirements applicable to Patch 02.
Other Software Requirements for InTouch 10.0 Patch 02
The following software requirements are in addition to the original requirements listed for InTouch version 10.0:
- You must apply Patch 01 to Wonderware Application Server version 3.0 if you intend to use it with InTouch 10.0 Patch 02. Wonderware Application Server 3.0 Patch 01 is available on the InTouch Patch 02 mini-CD in a folder named Application Server Patch 01 and is downloadable from the Wonderware Technical Support web site. Refer to the Readme file within the Application Server Patch 01 folder for more information about applying Patch 01 to Wonderware Application Server version 3.0.
- You must apply Patch 01 or greater to Wonderware Application Server 2.1 if you intend to use it with InTouch Patch 02. InTouch 10.0 Patch 02 supports Microsoft .NET Framework 2.0 or 3.0. Without Patch 01, Wonderware Application Server version 2.1 does not support .NET Framework 2.0.
Applying Patch 02 to InTouch Version 10.0
This section explains how to apply Patch 02 to existing instances of InTouch version 10.0 installed at your site. After Patch 02 is applied, InTouch is at version 10.0.002.
You can use either Patch 02 or the InTouch 10.0 with Patch 02 product CD to update an existing instance of InTouch version 10.0 to Patch 02.
- For instructions to update InTouch version 10.0 with Patch 02, see Updating to InTouch Version 10.0.002 with Patch 02.
- For instructions to update InTouch version 10.0 with the InTouch 10.0 with Patch 02 product CD, see Updating to InTouch Version 10.0.002 with the InTouch Version 10.0 with Patch 02 Product CD.
Updating to InTouch Version 10.0.002 with Patch 02
You can apply Patch 02 to the following versions of InTouch:
- InTouch version 10.0.000
- InTouch version 10.0.001
Important:
InTouch Patch 02 must be applied only to InTouch version 10.0. No other version of InTouch can be upgraded with this patch. For instructions to upgrade earlier versions of InTouch to version 10.0 Patch 02, see Upgrading Earlier Versions of InTouch to InTouch 10.0 Patch 02.
Patch 02 consists of two files; this Readme and a Setup.msp file. The Patch 02 Setup.msp patch file can be downloaded from the Wonderware Technical Support web site or from the Patch 02 mini-CD. The mini-CD contains folders of localized versions of the Setup.msp file for the various languages supported by InTouch version 10.0.
If you download the Patch 02 Setup file from Wonderware's Technical Support web site, you can copy the Setup.msp patch file directly to the computer where InTouch is installed, or burn it to a CD.
To update InTouch Version 10.0 with Patch 02
- Close Application Manager, WindowMaker, or WindowViewer if they are running.
- Place the Setup.msp patch file in a folder on the computer where InTouch is installed, or place the Patch 02 mini-CD into the computer's CD-ROM drive.
- Open Windows Explorer, and then move to the location where the InTouch patch Setup.msp file is located. If you are using the Patch 02 mini-CD, open the folder on the CD for the language applicable to your installed instance of InTouch version 10.
- Double-click on the Setup.msp file to start the patch installation procedure.
- Click Next.
- Accept the Wonderware product license.
- Click Next. The Updating System dialog box shows the progress of the patch update.
- If the OS Configuration Utility dialog box appears, click OK to continue installing the patch.
- Click Finish.
- Click Yes to restart your computer.
- Verify that your instance of InTouch version 10.0 is at version 10.0.002.
Caution
You must update with the
Setup.msp file in the same language as your installed instance of
InTouch. If you update with a Setup.msp file in a different language
than your installed instance of InTouch, you may be forced to
completely uninstall and then reinstall InTouch.
Updating to InTouch Version 10.0.002 with the InTouch 10.0 with Patch 02 Product CD
You can also use the full InTouch 10.0 with Patch 02 product CD to update an existing instance of InTouch version 10 to version 10.0.002.
To update to InTouch Version 10.0.002 with the InTouch 10.0 with Patch 02 CD
- Close Application Manager, WindowMaker, or WindowViewer if they are running.
- Place the InTouch product CD into the computer's CD-ROM drive.
- Follow the steps of the update procedure. You can get information during the installation procedure by clicking Help.
- Verify that your instance of InTouch version 10.0 is at version 10.0.002.
Verify InTouch Has Been Updated to Version 10.0.002
After you complete the update procedure, verify that your instance of InTouch version 10.0 is at version 10.0.002.
To verify InTouch Version 10.0 has been updated to Version 10.0.002
- Start Application Manager.
- Click Help from the Application Manager menu bar.
-
Click About Application
Manager. The About
InTouch Application Manager dialog box shows the InTouch
version installed on the computer.
You should see Version: 10.0.002 listed in the dialog box after Patch 02 is installed.
Upgrading Earlier Versions of InTouch to InTouch 10.0 Patch 02
You can upgrade to InTouch version 10.0 Patch 02 from InTouch version 8.0 and later. The following list shows earlier versions of InTouch that can be upgraded to version 10.0 Patch 02:
- InTouch version 9.5 Patches 01, 02, 03, and SP1
- InTouch version 9.0 Patch 03
- InTouch version 8.0 SP2 Patch 04
Important:
You must use the full InTouch 10.0 with patch 02 product CD to upgrade
an earlier version of InTouch to version 10.0 Patch 02.
When upgrading from InTouch HMI version 8.0 or later, the installation procedure detects which InTouch components are currently installed and updates them accordingly. Adding or removing InTouch components during an upgrade is not recommended.
Migrating Applications from Earlier InTouch Versions to InTouch 10.0 Patch 02
You do not need to migrate your existing InTouch applications created with either InTouch version 10.0 or InTouch version 10.0 Patch 01. The existing application version is maintained after Patch 02 has been applied.
Applications created with versions of InTouch earlier than version 10.0 are migrated to the current version (version 10.0.002) the first time you open them with WindowMaker.
Resolved Issues - InTouch Version 10.0 Patch 02
InTouch version 10.0 Patch 02 resolves the following issues listed by their Change Request number:
| L00074343: | The WEI Work Order list and Parameter list ActiveX controls generate an Assertion error followed by a User defined break point error after switching to WindowMaker two or more times in succession. | ||
| L00074715: | ArchestrA Symbols that are overlayed in WindowViewer do not pass mouse events to any object beneath the top most symbol. |
InTouch Version 10 Patch 01 Readme
Applying Patch 01 to InTouch Version 10
This section explains how to apply Patch 01 to existing instances of InTouch version 10 installed at your site.
Important: InTouch Patch 01 must be applied only to InTouch version 10. No other version of InTouch can be upgraded with this patch.
The Patch 01 Setup.msp patch file is available from the Wonderware Technical Support web site. You can copy the Setup.msp patch file directly to the computer where InTouch is installed, or burn it to a CD.
Apply the Patch
- Close Application Manager, WindowMaker, or WindowViewer if they are running.
- Place the Setup.msp patch file in a folder on the computer where InTouch is installed, or place the Patch CD into the computer's CD-ROM drive.
- Open Windows Explorer, and then move to the location where you placed the InTouch patch Setup.msp file.
- Double-click on the Setup.msp file to start the patch installation procedure.
- Click Next.
- Accept the license.
- Click Next. The Updating System dialog box shows the progress of the patch update.
- If the OS Configuration Utility dialog box appears, click OK to continue installing the patch.
- Click Finish.
- Click Yes to restart your computer.
Verify InTouch Has Been Updated
- Start Application Manager.
- Click Help from the Application Manager menu bar.
-
Select About Application
Manager. The About
InTouch Application Manager dialog box shows the InTouch
version installed on the computer.
You should see Version: 10.0.001 listed in the dialog box after Patch 01 is installed.
Resolved Issues - InTouch Version 10 Patch 01
InTouch version 10.0 Patch 01 resolves the following issues listed by their Change Request number:
| L00061933: | A symbol does not connect to InTouch tags if it is included in an InTouchView application. | ||
| L00063009: | Users are unable to change a password from the InTouch Login dialog box when using ArchestrA operating system group-based security. | ||
| L00063320: | The Alarm Tree View ActiveX control cannot display alarms from an Alarm Group whose name contains an ampersand character (&). | ||
| L00064395: | In the application object instance, the Custom Properties of an embedded symbol do not resolve using the modified reference value. | ||
| L00064824: | In a Terminal Services Environment, multiple users cannot work on different managed InTouch application templates. | ||
| L00066097: | Users cannot move to different window locations by pressing keyboard arrow keys within WindowMaker. | ||
| L00066153: | Language switching does not work with an imported window. | ||
| L00066180: | The default font size for numbers and formatted run-time data becomes smaller after switching to WindowViewer. | ||
| L00066394: | There is a 100 percent CPU performance issue when closing the script editor dialog box for applications containing several hundred scripts. Closing a script dialog box can take up to a minute in InTouch version 10. | ||
| L00066987: | An assertion error (dbsrch.c line 67) occurs when picking a tag. | ||
| L00066988: | The AlarmChange() function must be added to InTouch to support the DomainName and OperatorFullName arguments. | ||
| L00067616: | Symbol tool tips do not work if the symbol is placed over another symbol. | ||
| L00067899: | The New AlarmChange() function does not work after an alarm is acknowledged by a script containing the AlarmAck() function. | ||
| L00067940: | InTouch shows a negative zero (-0.0000000) value in a scale I/O real type value if the value from the PLC is 0. Tests from InTouch to Excel show the same result. In exponential form, InTouch displays -2.220446e-16. | ||
| L00068094: | The Alarm Viewer Control in WindowViewer cannot connect to a remote alarm provider. | ||
| L00068112: | WindowViewer becomes non-responsive and eventually crashes when you have a Galaxy with 18000 User Defined objects and AppEngRedundancyDisplay symbol is embedded in InTouch. | ||
| L00068233: | When the Always load windows from disc option is selected, ActiveX control properties are not synchronized with bound InTouch tag values when the application window is visible. | ||
| L00068320: | The title of a pop-up show symbol window does not appear if a custom property or UDA is assigned to the title. | ||
| L00068338: | The AlarmViewer ActiveX control freezes an InTouch application for an extended period of time and forces CPU usage to 100 percent even after the control returns the results of the query. | ||
| L00068369: | The AlarmTree control freezes and the status bar shows a status of 0 percent after refreshing a window. | ||
| L00068440: | The ArchestrA Graphic menu option appears in all localized versions of WindowMaker when editing a stand-alone InTouch application. | ||
| L00068462: | The AlarmChange() function does not change the AlarmPriority field. | ||
| L00068516: | An alarm comment for a tag with ACK model as "Expanded Summary" is missing if the Retain ACK comment as Alarm Comment option is selected. | ||
| L00068580: | Tool tips do not appear in unfocused windows containing a symbol animation. | ||
| L00068593: | When running a change window color script, the new color fails to apply to areas containing check boxes or radio button lists. | ||
| L00068703: | An error occurs when importing a dictionary file containing 36 Smart Symbols. | ||
| L00068726: | Blink animation fails if a ShowSymbol animation is nested more than one level deep. | ||
| L00068749: | A Custom Property does not retain its overridden show symbol attribute value when the graphic is nested in a group within another symbol. | ||
| L00068752: | One of two ShowSymbol windows does not show the configuration error for an undefined InTouch tag. | ||
| L00068996: | The SubstituteString() function does not work for double-byte characters inside of an ArchestrA symbol. | ||
| L00069631: | The Quality and Status settings for FillColor, LineColor, and TextColor overrides are not shown at run time if an animation other than Blink / PercentFill is configured on the group. | ||
| L00069805: | The Use Existing Tags (Conserve Placeholders) option should work with SmartSymbols. | ||
| L00069857: | WindowViewer crashes after switching to another application window. | ||
| L00069884: | The storage time of alg files can be configured to a maximum of only 96 days. | ||
| L00069934: | The substituted strings of an ArchestrA Symbol embedded in an InTouch application in one language OS do not display correctly when run in another language OS. | ||
| L00070252: | The Purge utility cannot purge databases over over 1 GB in size. | ||
| L00070401: | AlarmPrinter does not format trailing spaces correctly within alg files. This means there are no trailing spaces used for the "column" of the alarmstate. | ||
| L00070817: | Scaling an I/O tag for a Square Root Conversion does not work in InTouch version 10. | ||
| L00070830: | If Network Application Development (NAD) is enabled, changes to retentive tag values are not retained after restarting the application. | ||
| L00070907: | Double-clicking on a tag within a QuickScript to access the Tagname Dictionary shows only a partial tag name if the tag appears after 460 characters in the script. | ||
| L00071089: | An embedded symbol containing horizontal or vertical lines disappears when Flip Horizontal / Vertical or Rotate Clockwise / Counter clockwise functions are applied to it. | ||
| L00071232: | Importing windows from an exported window with the Selecting the Existing Tags (Conserve Placeholders) option creates placeholders for the tags configured in SmartSymbols even though these tags exists in the new application. | ||
| L00071281: | WindowViewer crashes when a pop-up window with value entry for secured write is closed before the Wonderware Application Server secured write dialog is closed. | ||
| L00071343: | Substitute tags do not work with SmartSymbols that include Alarm Group tags. | ||
| L00072280: | The QuickScript Save button is disabled if the script is modified several times. | ||
| L00072368: | In a migrated stand-alone application, opening and closing the Tag Browser from the Script editor causes the application to become unresponsive for more than 40 seconds. | ||
| L00072414: | When a .Net control belongs to a window being compiled, the DesignMode property is set to False in the Load event and True in the HandledDestroyed event. | ||
| L00072451: | If a comment field appears in an application window, WindowViewer crashes if the user enters a blank space as the comment. |
Known Issues - InTouch Version 10 Patch 01
This section lists known issues that remain in the InTouch version 10 Patch 01. The issues are identified by their Change Request number.
| L00072216: | An unhandled exception occurs in WindowViewer after pressing a button that incorporates a script containing the HideSelf() function. | ||
| L00072430: | If you have an application with ArchestrA Graphics running on multiple Terminal Server sessions on the same node and connected to the same Terminal Server, the data associated with the graphics is not consistent for all Terminal Server sessions. | ||
| L00072656: | The changed reference for a
custom property is not saved if it contains localized double-byte
characters when you substitute tags for an embedded symbol(Object name
or attribute name contains localized characters).
Interim Solution 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. |
||
| L00072666: | WindowViewer stop responding after a pop-up window with a value entry for secured write is closed before the Application Server secured write dialog box is closed. |
InTouch Documentation Issues
The following table lists corrections to known issues in the InTouch HMI version 10 documentation.
| Item | Location of Change | Existing Documentation | Change |
| 1 |
ITAAIntegration.pdf: "Substituting References in ArchestrA Symbols", page 60 |
You can substitute all references in an embedded ArchestrA Symbol with alternate references. | Replace this paragraph with the following: 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. |
Wonderware InTouch HMI Version 10 Readme
Last revision: 08/14/2007
InTouch Version 10 Features
Version 10 of the InTouch HMI provides a set of new features and enhancements to existing features.
ArchestrA Integration
InTouch HMI version 10 is more tightly integrated with the Wonderware ArchestrA environment. You can install the ArchestrA Integrated Development Environment (IDE) with InTouch HMI to centrally manage your InTouch applications in a Galaxy Repository (database). The ArchestrA IDE includes the Symbol Editor, the Graphics ToolBox, a set of sample databases, and the InTouchViewApp object template.
ArchestrA Graphics
The ArchestrA IDE provides an extensive set of graphic and scripting tools to create complex symbols that can be embedded into InTouch applications.
Enhancements to Traditional InTouch
- The appearance of the Application Manager window has been updated to current Microsoft standards. It also includes a button to launch the ArchestrA IDE from the Application Manager.
- WindowMaker includes a new hierarchical project view that lists the windows and scripts that are part of an InTouch application.
-
Alarm Viewer control enhancements
- NewAlarm event occurs when a new alarm is detected.
- NewAlarmEventMode property (Integer) to control when NewAlarm events occur.
- NewAlarm property available from AlarmViewer control.
-
Run-time language switching enhancements
- Alarm comments can be switched to another language while an application is running.
- WindowViewer includes the new Language menu command to switch languages.
-
Multi monitor enhancements
- Support for operating system-managed multiple monitor configurations.
- Enhancements to existing run-time functionality to ensure accurate screen sizing and placement of application elements (keypads, pop-up menus, input fields) on the correct screen.
- Improvements to ShowAt() and DialogStringEntry() functions for multi monitor scripting.
- Terminal Server capacity is increased up to a maximum of 75 simultaneous InTouch client sessions. The actual upper limit to the number of simultaneous client sessions is based on the design of the InTouch application and the server's hardware capability.
- The Tahoma font is now the default InTouch font.
- InTouch HMI version 10 can run under the Microsoft Windows Vista operating system. For more information about supported editions of Vista, see Operating Systems.
System Requirements
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.
Hardware Recommendations
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.
InTouch HMI Stand-alone Hardware
- Computer with 1.2 GHz or faster processor clock speed
- 512 MB of memory minimum, 1 GB or greater recommended
- At least 4 GB of available hard disk space
- Super VGA (1024 × 768) or higher resolution video adapter and monitor
- CD-ROM or DVD drive to read Wonderware installation media
- Keyboard and mouse or compatible pointing device
InTouch HMI and the ArchestrA IDE Hardware
- Computer with 2 GHz or faster processor clock speed (dual core processor recommended for optimal performance)
- 2 GB of memory
- At least 4 GB of available hard disk space
- Super VGA (1024 × 768) or higher resolution video adapter and monitor
- CD-ROM or DVD drive to read Wonderware installation media
- Keyboard and mouse or compatible pointing device
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
Software Requirements
This section describes the operating system and other software requirements to install InTouch HMI version 10.
Operating Systems
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:
- InTouch HMI version 10 does not support any version of the Microsoft Windows 2000 operating system. If you attempt to install or upgrade the InTouch HMI on a computer running Microsoft Windows 2000, an error dialog box appears during the installation procedure.
- Microsoft Windows Server 2003 SP2 is the recommended operating system to run InTouch server components.
- Microsoft Windows XP Professional SP2 is the recommended operating system to run InTouch client components.
Other Software Requirements
The following list describes other third-party software requirements to support InTouch HMI version 10.
- The InTouch HMI requires Microsoft .NET Framework 2.0 or .NET Framework 3.0, which are both at version CLR 2.0.50727. If neither version of .NET Framework is installed on the computer, the installation procedure halts and shows a message to install .NET Framework. You can select to install .NET Framework from the InTouch HMI installation CD or manually using your own version of .NET Framework.
-
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.
- The SQL Server 2005 SP2 database must be installed on the same computer as the ArchestrA Galaxy Repository.
Windows Vista Restrictions
- InTouch HMI version 10 can run under Windows Vista Enterprise, Windows Vista Business, or Windows Vista Ultimate. The Windows Vista Home Basic and Home Premium editions are not supported.
- Users must log on as a Windows Vista administrator to run the InTouch HMI. You cannot run the InTouch HMI as a Windows Vista standard user or power user.
- You can run Wonderware 32-bit software only with a 32-bit version of Windows Vista. Running a Wonderware 32-bit application with a 64-bit version of Windows Vista on 64-bit hardware is not supported
- The Windows Vista User Account Control (UAC) must be disabled when running the InTouch HMI. Refer to the following Microsoft web site for instructions to disable the UAC.
- When you disable Windows Vista UAC, you must restart the computer before attempting to install the ArchestrA IDE or Wonderware Application Server. A Galaxy connection error occurs if you attempt to install the ArchestrA IDE or Wonderware Application Server and you did not restart the computer after you disabled the UAC.
- Windows Vista does not support a dedicated single-node server configuration that runs one or more databases for an InTouch HMI system.
- If a computer runs Windows Vista as part of an InTouch system, it cannot be configured to be both an InTouch and ArchestrA alarm provider. The computer running Windows Vista can be either an InTouch or ArchestrA alarm provider, but not both simultaneously.
-
Windows Vista does not support NetDDE for InTouchView applications. By
design, an InTouchView application does not serve data to any other
source, including InTouch 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 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.
- InTouch HMI cannot be configured to run as a Windows Vista service. Windows Vista security prevents started Windows services from interacting with desktop objects. When the InTouch HMI is installed on a computer running Windows Vista, scripts do not run correctly if they include the InTouch ActivateApp() and SendKeys() functions. These functions interact with desktop objects by starting Windows programs and sending keystrokes to these programs.
Upgrading from a Previous Version
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.
Upgrading from InTouch Version 7.11
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.
Upgrading InTouch Terminal Services
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.
Known Issues–InTouch HMI Version 10
This section describes all known issues identified in InTouch HMI version 10. The known issues are grouped by function.
Installation Issues
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:
- Locate and remove the "LicView.exe" file (dated Thursday, August 03, 2006, 9:20:20 PM, size 68.0 KB) from C:\Program Files\Common Files\ArchestrA folder.
- Run the product installer repair (this may require the original product CD).
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.
WindowMaker Issues
L00039530: 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.
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.
- Create an application with InTouch.
- Import the SmartSymbol from blink.www.
- Create and open an InTouch application window.
- Start a SmartSymbol Edit, placing the blink animation on the window. Do not make any changes. Do not break the cell. Simply End the SmartSymbol Edit and commit the edit. You have replaced a broken XML file of the SmartSymbol with one that works.
- Delete the remnant editing copy from the application window.
- Place an instance of the "blink" SmartSymbol on an application window and substitute "instance" for "me". You may want to re-export the corrected InTouch SmartSymbol for use in other applications.
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.
- Import the SmartSymbol into the new application.
- Configure the new language with the same ID.
- Embed the SmartSymbol into all the windows where it is needed.
- Export the translated dictionary from Special->Language->Export Dictionary.
- Import the same dictionary created in Step 4 back into the application.
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.
- Open the object editor for one of the AppEngine objects. For example, AppEngineA.
- In the editor, click the Graphics tab and then add a new local graphic to the list. For example, EngineGroup1
- Select the new local graphic, and then click Open to open the Symbol Editor.
- On the Edit menu, click Embed Graphic.
- Show the Graphic Toolbox and then browse to and select the EngineGroup display symbol. The display symbol is now shown in the Symbol Editor as an embedded symbol.
-
To be able to point the symbol at a different object instance at run
time, add a combo box that references the OwningObject property of the
embedded symbol.
- Place a combo box on the embedded display symbol and then open its animation editor.
- In the Reference box, make a reference to the OwningObject property for the Display symbol. For example, EngineGroup1.OwningObject. You can either type the reference or use the Galaxy Browser to select the OwningObject property in the Element Browser tab.
- Configure the values and captions for the combo box. For example, use AppEngineA, AppEngineB, and AppEngineC as the values and captions.
- Click OK.
- Save and close the Symbol Editor.
- Save and close the AutomationObject Editor.
-
To use the EngineGroup display symbol in a window of a managed InTouch
application, do the following:
- Open the window in WindowMaker.
- On the Edit menu, click Embed ArchestrA Graphic. The Galaxy Browser appears.
- Show the Instances view and then select the EngineGroup display symbol attached to the AppEngineA instance.
- Click OK.
- Place the symbol in the window.
- Start WindowViewer. The symbol shows information for AppEngineA (it is the default owning object).
- To have the symbol show information for another AppEngine instance, select the instance from the combo box. The EngineGroup display symbol now shows data for the selected AppEngine.
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.
- Create a new ArchestrA symbol and embed the symbol that you would like to perform the substitution on within the new symbol.
- Substitute the symbol's strings within the new symbol in the ArchestrA IDE Graphic Editor.
- Embed the new ArchestrA symbol containing the substituted strings in an InTouch window from 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:
- Do not attempt to import/migrate older version aaPKGs files to a Galaxy created using the Base_InTouch.cab file.
- If you accidentally delete ArchestrA templates, then reimport the version 3.0 aaPKG file from the Wonderware Application Server \bin folder to your Galaxy.
Take these steps to restore the correct version 3.0 system objects to your Galaxy:
- Delete all the objects in the Galaxy.
- Import the version 3.0 templates in the aaPKG file located in the Wonderware Application Server \bin folder.
- Import the earlier version aaPKG file with the migration option.
WindowViewer Issues
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:
- An I/O discrete tag refers to itself as an item name in an Access Name.
- An I/O discrete tag is included in a condition script with code to reset the discrete tag value to FALSE.
- A user input link sets the discrete tag value to TRUE.
- A value display link displays the discrete tag as a remote reference.
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.
InTouch HMI Documentation Issues
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. |
InTouch HMI Documentation
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.
Searching InTouch Books with Adobe Reader
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
- Open Adobe Reader.
- Press CTRL+SHIFT+F or select Search from the Edit menu. The Search dialog box appears.
- Type the word or phrase that you want to search for in the InTouch books.
- In the Where would you like to search area, select the option to search all PDF books.
- If necessary, locate the PDF files located on your InTouch installation CD or on a network folder containing copies of the book files.
- Click Search. Adobe Reader lists the InTouch books that contain a match for your search criteria.
- Click on the links to open the InTouch book to the topic containing the information that meets your search criteria.
© 2008 Invensys Systems, Inc. All Rights Reserved.
