Changes made to a master template automatically propagate to all deployed InTouch windows across the facility. Key Features and Capabilities
It built upon the ArchestrA architecture, allowing for tighter integration with Wonderware Application Server 3.5. Graphic Evolution:
: 2 GB minimum (4 GB or more recommended for System Platform nodes)
For those maintaining legacy systems or planning a migration, the recommended specifications for 10.5 include:
A core strength of InTouch 10.5 is its ability to communicate with almost any industrial hardware vendor, including Rockwell Automation (Allen-Bradley), Siemens, Modicon, and GE. DA Servers and OI Servers wonderware+intouch+105
This is often caused by an oversized or corrupted alarm log database, or an unresolved network path in the application directory. Deleting temporary .wvw files in the application folder or re-indexing the local runtime database usually resolves the startup hang. The Path Forward: Migrating from InTouch 10.5
| Operating System | Default WWHeap Memory | Maximum Accessible Memory | Configuration | | :--- | :--- | :--- | :--- | | 32-bit | 1.5 GB | Nearly 2 GB | Special configuration | | 32-bit (with /3GB) | 1.5 GB | Up to 3 GB | Add the /3GB switch to boot.ini file | | 64-bit | N/A | Up to 4 GB | No special configuration needed |
To ensure stability, InTouch 10.5 (2012) requires specific hardware and software configurations. According to the official installation guides , the recommended setups are: Recommended Specification
Installing InTouch 10.5 required careful planning and adherence to specific prerequisites due to its integration with Application Server and Windows security features. Changes made to a master template automatically propagate
Run when a specific graphical window opens, stays open, or closes.
Includes InTouch QuickScripts for logic implementation (Condition, Data Change, Key, and Application scripts).
InTouch 10.5 operates primarily under two distinct application architectures. Choosing the right architecture depends on your facility's scale and engineering workflows. Standalone Applications : A traditional, self-contained HMI application.
InTouch 10.5 introduced several refinements that enhanced engineering efficiency and operational awareness. DA Servers and OI Servers This is often
It was optimized for then-modern environments like Windows Vista and Windows 7, requiring the disabling of User Account Control (UAC) for seamless installation. Enhanced Interconnectivity:
The migration process also included converting the alarm system. When moving from a Standard Alarm system to the Distributed Alarm System introduced in 10.5, all standard alarm displays were automatically migrated to the new Distributed Alarm Display objects.
: Supports tag-based applications ranging from 64 to unlimited tags.
If runtime objects display text tags like ??? or reveal "Bad Quality" status, the communication link is broken. Open the Wonderware System Management Console (SMC), check the log viewer for connection timeouts, and verify that your Access Name settings in WindowMaker match the exact Topic Name configured in your DA Server. 3. WindowViewer Freezes on Startup
Used to connect InTouch to third-party OPC (OLE for Process Control) DA servers.