file:///media/rhandsome/toshiba/wonderware/do... Wonderware InTouch HMI Version 10.1 Readme

Transcription

1 Wonderware InTouch HMI Version 10.1 Readme Last revision: 01/30/2009 This document contains important information about Wonderware InTouch HMI Version Review this document for known issues and changes to InTouch 10 documentation included on this CD. Important! If you are using managed InTouch applications with ArchestrA symbols, before installing Wonderware Application Server 3.1, run the ArchestrA Symbol Analysis and Repair Utility and ensure all issues reported by the utility are addressed. If InTouch 10.0x and Application Server 3.0x are installed on the same node, they both must be upgraded to Application Server 3.1 and InTouch If your version of Wonderware Application Server is older than version 3.0, you must upgrade it before upgrading to InTouch Galaxies with ArchestrA Symbols or InTouchViewApp Objects containing ArchestrA Symbols that leverage the Runtime Language Switching functionality, must always be modified on the same language operating system and InTouch language version with which it was initially developed. Attempts to modify these components in a different language operating system, or a different InTouch language version may result in unexpected behavior and is not presently supported. Published applications running in an operating system langauage different from the originally developed language are supported. Refer to Known Issues CRs L , L , and L The antivirus software exclusions list has been updated. Click this Antivirus Software Exclusions link for details. About This Release Antivirus Software Exclusions System Requirements Resolved Issues InTouch 10.1 Known Issues InTouch 10.1 InTouch Documentation Issues InTouch Documentation About This Release Version 10.1 of Wonderware InTouch HMI includes the following enhancements and new features: Language Switching for ArchestrA Symbols You can switch to localized strings for ArchestrA Symbols. This includes any configuration-time changes to support 1 of 10 04/28/ :57 PM

2 the extracting and importing of text strings. You can localize the following strings: Text constant custom properties Text graphics Text overrides of custom properties in WindowMaker You can also add, edit, and remove the locale data from the Symbol Editor. Licensing InTouch licensing now accounts for Terminal Service sessions. The licensing system now enforces per session licensing to prevent running unlicensed copies of InTouch within Terminal Server Sessions. Non-Administrator Interactive User At a high level, this feature allows InTouch run-time functionality to be run by users who do not have administrative rights on the computer. It does not provide this support for configuration operations. Functionality is available for the following operating systems: Windows XP SP3 (Power user) Windows 2003 SP2, R2 + SP2 (Power user) Windows Vista SP1 (Standard user with the UAC enabled) Well-known Client Control Support The Symbol Editor has been extended to allow new Graphic Objects to appear in the Symbol Editor tool palette. Printing Enhancements Several printing features are added to the InTouch HMI: Saving and Printing a Tag Cross-Reference List Printing Scripts Printing Information about WindowMaker Objects Printing Information about InTouch Windows Printing Window Information from a Command Prompt Deployed File Management You can add additional files in a managed InTouch application so they are deployed and available at run time. Antivirus Software Exclusions Configure your antivirus software to prevent archive files from being scanned. Also, antivirus software should not scan files in the following ArchestrA folders (ensure subfolders of the listed directories are also excluded): C:\Program Files\ArchestrA\ 2 of 10 04/28/ :57 PM

3 C:\Program Files\Common files\archestra\ C:\Program Files\FactorySuite\ (may not exist in newer installations) C:\Program Files\Wonderware\ C:\InSQL\Data\ C:\Documents and Settings\All Users\Application Data\ArchestrA 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 files of type:.mdf.ldf System Requirements This section describes the hardware and software requirements to install Wonderware InTouch HMI Version Hardware Requirements Software Requirements Other Software Requirements Hardware Requirements The following lists show the recommended specifications to install Wonderware InTouch HMI Version These recommendations are for development systems. Run-time requirements may be different, depending on the InTouch application and other factors. Computer with 1.2 gigahertz (GHz) or faster processor 512 MB of memory minimum, 1 gigabyte (GB) or greater recommended At least 4 GB of available disk space Super VGA ( ) or higher-resolution video adapter and monitor CD-ROM or DVD drive for installation Keyboard Mouse or compatible pointing device 3 of 10 04/28/ :57 PM

4 Software Requirements The following table lists the supported operating systems that can be installed on computers that run InTouch server and client components. Product Name Components Operating Systems WindowMaker WindowViewer ArchestrA IDE ArchestrA Run Time Galaxy Repository Windows Vista Business Windows Vista Business SP1 Windows Vista Enterprise Windows Vista Enterprise SP1 Windows Vista Ultimate Windows Vista Ultimate SP1 Windows 2003 Standard Server R2 Windows 2003 Standard Server SP2 Windows 2003 Enterprise Server R2 Windows 2003 Enterprise Server SP2 Windows XP Professional SP3 Windows XP Tablet Note: InTouch HMI version 10.1 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 2003 Standard Server R2 is the recommended operating system to run InTouch server components. Microsoft Windows XP Professional SP3 is the recommended operating system to run InTouch client components. Vista Restrictions InTouch HMI version 10 or later 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. You can run InTouch only on computers running a 32-bit operating system. You cannot run InTouch on a computer running a 64-bit operating system. 4 of 10 04/28/ :57 PM

5 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. Other Software Requirements The following list describes other third-party software required for Application Server version 3.1. Microsoft.NET Framework 3.5 Microsoft.NET Framework 3.5 must be installed on every computer that hosts an InTouch version 10.1 component. The InTouch installation program stops if.net Framework 3.5 is not installed on the target computer. A dialog box appears requesting that you install.net Framework 3.5. If you click Install Prerequisites, the installation program automatically installs.net Framework 3.5. Microsoft SQL Server 2005 Microsoft SQL Server 2005 SP1 or SP2 database must be installed on the same computer as the ArchestrA Galaxy Repository. Resolved Issues in Wonderware InTouch HMI Version 10.1 Wonderware InTouch HMI Version 10.1 resolves the following issues. The issues are listed by their Change Request number: L : For an action script, double-clicking text within the double quotes selects additional text beyond the double-quotes, when a colon (:) follows the text. (See SR ) 5 of 10 04/28/ :57 PM

6 L : You can instantiate a SmartSymbol that references a tag that does not exist. (See SR# ) L : The InfoAppTitle function does work with non-administrator user rights. (See SR ) L : Printscreen and Printwindow functions do not work if WindowViewer is running as service. L Placing an apostrophe (single quote) in the comment text box of a discrete alarm tag (OnMsg) causes the Alarm DB Logger to fail to log an alarm. L : Control label text is scrambled when created using the Wizard Graphics and saved as a SmartSymbol. (See SR ) L : The OnShow script in an ArchestrA Symbol appears to run, but the script does not set an attribute. (See SR ) L : When a client control is deleted and a new version of the client control is imported from a remote IDE, an ArchestrA Symbol referencing the client control will show Version 1 on the remote IDE and Version 2 on the Galaxy Repository IDE. This is a mismatch of versions. (See SR ) L : The graphic element reference list is incomplete, or it is corrupted. The error message "Failed to get Graphic element reference list" appears in the SMC logger. (See SR ) L : Customized graphic text is lost after group change. (See SR ) L : The RegisterEngine number decreases when a new connection is made using remote desktop (TSE) to the Application Server. (See SR ) L : Custom property links for ArchestrA symbols do not accept the following special characters that can be used in InTouch tag names: _(underscore), -(hyphen), $(dollar), %(percent), and &(ampersand). L : MX References do not start in scripting;.inputsource in ArchestrA Symbols does not start in scripting. The MX References do work on display the link and in a custom property. (See SR ) L : Graphic symbol custom property overrides are lost after group change. (See SR ) L : Warning "Could not find embedded graphics" appears after a template and its instances of a Galaxy are exported as an aapkg file, and are then re-imported into a new Galaxy. (See SR ) L : License enforcement of Terminal Service Edition does not work. Too many WindowViewer sessions are permitted to open. L : The Graphic toolbox pop-up window and the Graphics tab preview window thumbnails show "not found" when an application object instance containing symbols with date time picker is imported in a new Galaxy. L : SPC Pro does not work when WindowViewer is started up directly on a computer with a standard user login. L : If you are using the SPC Control Chart on the Windows Vista operating system, you need to specify a System Data Source Name (DSN) and make sure that all application users can write to the folder in which the database file resides. 1) The ODBC data source needs to be created as a System DSN and not as a User DSN. As application creator must be admin/power-user and application user can be standard user, it is likely these will be different users. A User DSN won't work for standard user and gives errors in the SMC. 2) If you are using a database file (such as a Microsoft Access MDB file), then application creator must ensure that the application user can write to the folder in which the database file resides. Writing is required for database access (for example, adding sample points in the database). By 6 of 10 04/28/ :57 PM

7 default, most folders are not write-enabled. Known Issues in Wonderware InTouch HMI Version 10.1 This section describes all known issues in Wonderware InTouch HMI Version The issues are listed by their Change Request number: L : Touch push button animations do not work on client controls. L : The Symbol Editor stops responding when you edit the "format string" property of the checked list box client control. L : Windows do not print if the window name contains special characters. Rename the directory path and the filename to remove all special characters. L : WindowViewer does not start when configured to start as a service. An error message appears Access denied. The user win.ini and the MS Windows system win.ini are not in sync. See to pick up the correct system win.ini file. L : Spaces are not imported as part of the translation for the selected language. L : Terminal Server sessions crash when a ViewApp is changed and then redeployed while WindowViewer is running in a 100-terminal session configuration across 10 Terminal Servers. For certain applications and systems, you need to adjust the restart delay time by adding "ViewManagedRestartWaitPeriod" to the "Intouch" section in the Win.ini file. The default delay time is 5-seconds. L : There are inconsistencies between the selected language and the strings that are shown. L : After you click "NO" in the Network Application Development properties dialog box, WindowViewer does not ask you to "restart" and "load" changes. L : InTouch applications receive quality status and locale information from the deployed Galaxy. InTouch applications cannot receive data from an undeployed Galaxy. L : Translations are not loading after embedding a primitive from a different Galaxy employing a different language. Only the default English strings are shown. L : The Annotation window stops responding if you use standard Windows cut, copy, and paste shortcuts. Microsoft provides a Microsoft.Ink.dll CLR2.0 Update. See the following link to download the update e3bdbf9d805f&DisplayLang=en L : Running the AlarmDBLogger Manager as a Windows service is not working. Disable this option for Vista. 7 of 10 04/28/ :57 PM

8 L : If you are a Terminal Server user and you do not have "Administrator" privileges, you must be either a "Power User," or a "Remote Desktop User" to access the license. Otherwise, you receive a licensing error message. It is not obvious that you are missing rights and privileges necessary to successfully login. L : Non-English locale animation static "text" strings are not propagated to default (English) locale static "text" strings. L : Exporting the language dictionary using Microsoft Vista may result in not being able to retrieve the dictionary file as a standard user. When running WindowMaker as a standard user elevated to administrator rights as a different user than logged onto the Desktop, exporting the Language dictionary opens a default path that is not accessible by the standard user. It is recommend that you change the path to a public folder location. L : When an ArchestrA Symbol is exported from an application developed with an English version of InTouch and imported into an application developed in a different InTouch Language, like French, the strings of the ArchestrA Symbol cannot be substituted in WindowMaker. L : An ArchestrA Symbol with string substitutions is not showing the string substitutions in WindowMaker when the Galaxy Primary language is not English. L : InTouch Applications, which are configured to support runtime language switching and contain ArchestrA Symbols and native InTouch animations, initially show mixed language strings, if executed in an operating system language different from the one in which it was originally developed. L : The EnableDisableKeys function does not work in a Vista operating system, if the user is configured as a Standard User. Use the runtime environment configuration options in WindowMaker in addition to the operating system security policies to lock the application from access to the desktop. InTouch Documentation Issues The following table lists all documentation corrections to InTouch 10.1 documentation. Item Location of Change Existing Documentation Change 1 Creating and Managing ArchestrA Graphics User s Guide (aagraphics.pdf), "String Substitutions and Language Switching" section, page 426 Application Server Help (IDE.chm), "String Substitutions and Language Switching" topic n/a Add the following text after the first paragraph: If you perform a first-time string substitution on an embedded symbol in the primary language, that substitution is shown in the secondary languages. You can then perform a substitution in the secondary language to create a string substitution specific to the secondary language. If you perform a first-time string substitution on an embedded symbol in a secondary language, the substitution is also applied to the primary language, because the translated string that previously existed for the primary language is no longer valid. Because the primary language value is changed in the symbol, this 8 of 10 04/28/ :57 PM

9 string applies to all secondary languages configured. You can then perform a second substitution in the primary language, which will apply to all secondary languages except the ones that have had a specific substitution set. 2 InTouch HMI Documentation Addendum (ITAddendum.pdf), ".CVS Format for Printing Windows" topic, page 25 The current screen capture shows "Conveyor, Main, Reactor display, Menu" If you perform a string substitution in a secondary language with an existing string substitution in the primary language, the new substitution is applied to the secondary language only. The screen capture should show "Conveyor,Main,Reactor display,menu" InTouch Documentation The InTouch product library consists of a set of Portable Document Files ( PDF) located in the UserDocs folder of the InTouch installation CD. You need Adobe Reader installed on your computer to view InTouch documentation. You can download the latest version of Adobe Reader from the Adobe Corporation web site: 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. InTouch 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. Context-sensitive documentation is also available with InTouch online help. Select Help for information about the current InTouch window that you have open on your computer. Searching InTouch Books with Adobe Reader The InTouch 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 product library. To search for information across all InTouch books simultaneously 1. Open Adobe Reader. 2. Press CTRL+SHIFT+F or select Search from the Edit menu. The Search dialog box appears. 3. Type the word or phrase that you want to search for in the InTouch books. 4. In the Where would you like to search area, select the option to search all PDF books. 5. If necessary, locate the InTouch version 10 PDF package located on your Wonderware CD or on a 9 of 10 04/28/ :57 PM

10 network folder containing copies of the InTouch PDF book files. 6. Click Search. Adobe Reader lists the InTouch books containing information that matches your search criteria. 7. Click on the links to open the InTouch book to the topic containing the information that meets your search criteria Invensys Systems, Inc. All Rights Reserved. 10 of 10 04/28/ :57 PM