Wonderware In. Touch 2. Patch 0. 1 Readme. Wonderware. It updates the previous Read. Me files included with Wonderware. In. Touch HMI 2. 01. Important! Installation - You need to install In. Touch 2. 01. 2 (v. If you have not installed In. Touch 2. 01. 2 (v. Readme section below. Wonderware In. Touch HMI 2. Patch 0. 1 Information Applying. Patch 0. 1 to In. Touch HMI 2. 01. 2 (v. Resolved. Issues - Wonderware In. Touch HMI (v. 10. Patch 0. 1In. Touch. Documentation Issues. Applying Patch 0. In. Touch HMI 2. 01. This section explains how to apply In. Touch HMI 2. 01. 2 (v. Patch 0. 1 to. existing instances of In. Touch 2. 01. 2 (v. Important. In. Touch HMI 2. Patch 0. 1 must be applied only to In. Touch HMI 2. 01. 2. No other version of In. Touch can be upgraded with this patch. Intouch Scada Software. Free Windows software for Data Acquisition. This device is usually used as an HMI/SCADA Interface and possibly a data storage unit. Wonderware InTouch HMI 2014 (v11.1). InTouch Machine Edition 2014 Patch 7.The In. Touch HMI 2. Patch 0. 1 Setup.
Wonderware Technical Support web site. You can copy the Setup. In. Touch is installed, or burn it to a CD. If you. decide to copy the patch file to a CD, you must use the following conventions to. In. Touch HMI 2. 01. Patch 0. 1 CD: For standard In. Touch, the CD volume name must be Patch. The Setup. msp file must be placed at the root of the CD. You must install the Setup. UAC is turned off or. The Updating System dialog box shows the progress. L0. 01. 00. 43. 9: HF CR L0. SR. 1. 56. 16. 84. Using Dynamic Resolution (DRC) replace- type windows behavee. L0. 01. 10. 32. 3: HF CR L0. SR. 4. 16. 10. 07. HF 2. 35. 5: Zooming in and printing the application output wrong. L0. 01. 10. 61. 1: HF CR L0. SR. 1. 98. 16. 99. On importing an In. Touch window in a Managed Application, the. System tags displayed as placeholders. L0. 01. 10. 69. 5: HF CR L0. SR. 4. 16. 10. 08. In. Touch keypad remains open even after the parent window. L0. 01. 10. 79. 1: HF CR L0. SR. 3. 34. 10. 81. HF 2. 29. 4: Importing DBLoad from the IDE failed. Add a new. Registry DWORD value Disable. Write. To. New. Tag to the following Registry. On 3. 2- bit operating systems. HKEY. Otherwise, set the value to 0. L0. 01. 15. 20. 1: HF CRs L0. L0. 01. 16. 12. 1 SRs 3. L0. 01. 15. 66. 7: HF CR L0. SR. 4. 16. 10. 13. Window location information was unexpectedly changed and. Window. Maker. L0. HF CR L0. 01. 15. SRs. 3. 34. 10. 95. When an attribute in alarmed state had its value. L0. 01. 16. 35. 9: HF CR L0. SR. 3. 82. 31. 31. After switching languages, then printing a window without. L0. 01. 16. 36. 7: HF CR L0. SR. 3. 34. 10. 86. HF 2. 46. 7: With the Alarm. DBLogger running as a service, a local. Galaxy flooded the Alarm database. GB in two days. If the same alarm is. In. Touch alarm providers, then the alarm is. L0. 01. 16. 41. 9: HF CR L0. SR. 1. 03. 12. 14. The windows still loaded properly. L0. 01. 16. 55. 1: HF CR L0. SR. 1. 03. 12. 22. When a condition script was configured to execute every. SQL through SQL Access, Window. Viewer ceased to. L0. 01. 16. 69. 0: HF CR L0. SR. 1. 03. 12. 24. The Alarm DB Logger hangs with the error message, . L0. 01. 16. 86. 5: HF CR L0. SR. 1. 53. 16. 21. A Smart Symbol replace operation modified many Tagnames in. Instance References column. The window was saved and closed, but when. Tagnames appeared in the. Instance References column. L0. 01. 16. 86. 7: HF CR L0. SR. 4. 20. 10. 03. Language Switching for Application Server Alarm Comments did. ACK Alarms. L0. 01. HF CR L0. 01. 16. SR. 4. 16. 10. 15. Key scripts linked to the CTRL key did not import. L0. 01. 17. 30. 5: HF CR L0. SR. 1. 03. 11. 81. Action scripts were deleted during conversion from In. Touch. 9. 5 to In. Touch 1. 0. 1 if Active. X was not installed. L0. 01. 17. 43. 6: HF CR L0. SR. 1. 03. 12. 24. Opening an Archestr. A Symbol from another Archestr. A Symbol. showed with Show. Symbol function, then opening a keypad on a textbox. In. Touch window caused the In. Touch. application to freeze. L0. 01. 17. 53. 9. L0. 01. 17. 54. 0: The Show. Graphic. function forced displays into the viewable window instead of the. L0. 01. 17. 55. 1: HF CR L0. SR. 4. 16. 10. 18. Window. Maker crashed with a Heap error message when zooming. SR. 3. 39. 32. 68. Attempting to change the size of very large symbols are. L0. 01. 17. 60. 0: HF CR L0. SR. 4. 16. 10. 13. Linked tag information was lost when importing windows. Active. X controls. L0. 01. 17. 64. 6: HF CR L0. In. Touch application logon using Single Sign- On failed when a domain was. L0. 01. 17. 70. 1: HF CR L0. SR. 3. 38. 11. 89. Using a resizeable keyboard in In. Touch does not allow entry. L0. 01. 17. 80. 2: HF CR L0. SR. 1. 26. 11. 88. A Super. Tag with exactly 6. DBLoad to fail on. CSV file. L0. 01. HF CR L0. 01. 17. SR. 4. 16. 10. 19. Zooming in and printing an application prints incorrect. L0. 01. 17. 87. 3: HF CR L0. SR. 1. 03. 12. 31. With an Archestra symbol with an embedded Alarm Client. Control and alarms selected at run time, the selected alarms can become. L0. 01. 17. 91. 1: HF CR L0. SR. 2. 45. 15. 36. When running Recipe Manager on a dual monitor system, the. Recipe Select dialog box split between screens instead of remaining on one. L0. 01. 18. 08. 2: HF CRs L0. L0. 01. 15. 74. 5: Initial values in a DBdump for some tags are different when. Group By option is selected or de- selected. L0. 01. 18. 08. 3: HF CR L0. SR. 4. 16. 10. 18. When multiple pens were added in run time, one or more pens. Trend Client. Error messages were written to the. Logger: . Key in dictionary: 'ffc. Key. being added: 'ffc. L0. 01. 18. 27. 2: HF CR L0. SR. 3. 38. 11. 91. The Alarm DBLogger didn't connect to WWALMDB on a remote. Errors messages appeared in the Logger. Please use 'Create' button. Configuration page! L0. 01. 18. 39. 7: HF CR L0. SR. 4. 16. 10. 23. When Tag names were changed in the Tagname Dictionary, the. Data Change scripts still showed the old names. L0. 01. 18. 59. 4: HF CR L0. SR. 2. 53. 15. 22. An Intouch application implemented with custom Active. X and. Active. X event scripts crashed when the Active. X event scripts were. L0. 01. 18. 69. 6: HF CR L0. SR. 4. 31. 10. 12. The Alarm DBLogger did not allow configuration of a query. L0. 01. 18. 91. 1: HF CR L0. SR. 1. 26. 12. 03. Attempt. Invisible. Logon did not work correctly if the logged. L0. 01. 18. 91. 4: HF CR L0. Alarm Restore failed using the archived files and the In. Touch Alarm Db. Restore application when the folder used is 2. GB in total size. L0. 01. 19. 00. 4: HF CR L0. SR. 1. 03. 12. 37. With Windows Input Service for Touchscreens active and a. Real tag configured, changing the tag value with the touchscreen caused. Window. Viewer to crash. The hardware was a B & R Panel PC. L0. 01. 19. 13. 1: HF CR L0. SR. 4. 16. 10. 25. CPU went to 1. 00% and the system froze when a rotated text. L0. 01. 19. 14. 5: HF CR L0. SR. 1. 03. 12. 40. On a Windows 7 SP1 3. In. Touch. 1. 0. 1 SP3 Patch. Simplified Chinese, the Select. Query method of the. Alarm. DBView Control in Chinese In. Touch didn't work and displayed a warning. L0. 01. 19. 33. 7: HF CR L0. SR. 2. 06. 11. 18. While running In. Fusion View, a While True script stopped. True. A While True script should. True, and should work evn. WYSE clients). L0. HF CR L0. 01. 18. SR. 1. 03. 12. 40. An Action Script On Left Key Up did not work correctly with. Archestr. A Symbol opened by using the Show. Symbol command. L0. HF CR L0. 01. 19. SR. 3. 17. 11. 97. When running an In. Touch Managed application in In. Touch. version 1. SP3 P0. 1, with DASABCIP 4. SP2 installed on the same node. OS Group- based security, attempting a Secured Writes failed with the. Item. Location of Change. Existing Documentation. Change. 1In. Touch. This type of query. In. Touch as an alarm provider running in a Terminal Services. In. Touch running in a console session. HF CR. L0. 01. 19. SR 1. 03. 12. 44. The source alarms will not. Alarm. Viewer control's alarm query is configured. This. type of query only works when querying In. Touch running in a Terminal. Services session. It explains the new features and any known. About This Release Version 1. Wonderware In. Touch HMI includes enhancements and new. Features. System. Requirements. Product. Compatibility. Wonderware. In. Touch HMI Installation. Resolved. Documentation. Important! Installation - Installing the In. Touch HMI on a computer used as a. This is applicable for. Windows Vista and newer operating systems. In a. 3. 2- bit operating system, the default maximum memory of WWHeap is increased to. GB from 2. 56 MB. Special configuration can increase the maximum limit to. GB. In a 3. 2- bit environment, the In. Touch memory management can be. GB by adding the /3. GB switch in the boot. An entry in. the boot. GB switch looks like the following. For other. operating systems, the Windows name is different. If the /3. GB switch is. Windows, the paging file size should be set to a system managed. In. Touch can access up to 3 GB of memory. In a 6. 4- bit. operating system, it is not necessary to edit the boot. In. Touch. can use up to 4 GB of memory. For additional information, refer to. Microsoft Knowledge Base articles, such as KB 3. To. enable this functionality, you must configure the memory health check interval. Do the following to set the memory properties. On the Special menu, point to Configure and then click. Window. Viewer or in the Application Explorer under. Configure, double- click Window. Viewer. The Window. Viewer. Properties dialog box appears with the General tab active. The. system will remove the oldest closed in- memory window from the cache. The default value is 0 hours. You can enter a value. If you enter 0, there will be no time limit. These windows will always be. The system will remove the oldest. The Alarm DB Logger now runs as a Service in Windows Vista. Galaxy Alarms and In. Touch. Alarms from Terminal sessions. However, there is a limitation in that the. Alarm DB Logger configured as a service and In. Touch running. locally as a console application is still not supported. If In. Touch needs to. Console session, the Alarm DB Logger must be configured in the. Alarm DB Logger Manager as a “Normal Application” instead of a “Windows. Service”. Refer to the updated Tech Note 7. Attempts to modify these. In. Touch. language version, may cause unexpected functional or operational issues that. TN IT1. 48 Installing In. Touch 2. 01. 4R2. Description. This article from In. Source shows how to install Wonderware In. Touch 2. 01. 4R2 on a new PC using the System Platform 2. R2 installation media. Author: Dillon Perera. Published: 0. 7/2. Applies to: In. Touch 2. R2. Details. The System Platform 2. R2 installer is used to install In. Touch. In. Touch and Wonderware System Platform applications can be developed and tested. System Platform Development Server: Install the components required to host the development server, and develop and test In. Touch and Wonderware System Platform applications. Historian Server Node: Install the necessary components to store historical data in an Archestr. A environment. Historian Client Node: Install the components required to connect to an existing Historian Server and analyze the data. Information Portal: Install the necessary components for aggregating and presenting plant production and performance data on the internet or company intranet with the capability to access live plant process data, integrated data trending and analysis, production and performance reporting, and integration to existing IT infrastructure and web portals. All- in- One Node: All products are installed on a single node. Custom: Allows you to customize the components that are installed. In. Touch Access Anywhere Secure Gateway Node: Install the components to access Wonderware In. Touch applications hosted on Terminal Servers by using HTML5 compatible web browsers. You must install this component on a computer with no other System Platform components installed. Read through and agree to the End User License Agreement. IF this is the first Wonderware product you are installing, it will prompt you to enter in a username and password for an administrative Windows account. This account gets used by the Wonderware software for two reasons: 1) When communicating between computers, this account allows access to other pc’s for sharing files and data. Without this access, the software would not be able to use all of the PC’s resources, such as accessing the file system. Note: If you are unsure of what account to use, enter one temporarily.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2017
Categories |