Tech Notes

Tech Note 86: How to Distribute WindowViewer Processes Across Multiple CPUs in Wonderware InTouch for Terminal Service Environments

When working in Wonderware InTouch for Terminal Service Environments it is the default behavior to lock all WindowViewer processes to the first CPU; however, it is fairly common for server class systems to have multiple core CPUs or even multiple CPUs. Wonderware has released the "InTouch Affinity Control" which allows system administrators to take advantage of the processing power, and distribute all of the client InTouch sessions across all available CPUs. This document will list the procedures necessary to install and utilize the "InTouch Affinity Control".


Tech Note 85: Configuring Automatic I/O Referencing Scripts in Wonderware Application Server 3.0

Wonderware Application Server 3.0 provides the ability to automatically assign object attribute I/O references via its scripting engine. The main benefit of using this feature is that a large quantity of PLC I/O references can be automatically configured during Runtime based upon the object instance name that has been assigned when creating instances. Effectively, by entering one name to represent the object in the process (e.g. name of pump, valve, transmitter, etc.), multiple I/O references can be automatically set to support communication to the object. This tech note provides the steps how to configure automatic I/O referencing script in Wonderware...

Tech Note 82: Resolving slow WindowMaker load times for Wonderware InTouch managed applications

Default Wonderware InTouch application settings can result in long waits opening ArchestrA IDE managed applications containing a large number of windows with embedded ArchestrA Graphics. Each window is programmatically opened to complete the initial load of all ArchestrA graphics in the development environment. Adding a setting to the application's INTOUCH.INI file can vastly improve the initial load times in Wonderware InTouch WindowMaker for instances when this delay adversely affects the speed of development. This document lists the steps necessary to locate and add the LoadAllActiveXOnStartup flag set to zero in the managed application's INTOUCH.INI file.


Tech Note 81: How to change Wonderware Historian’s server name for Wonderware QI Analyst 4.2 workspaces and data tables

Wonderware QI Analyst can be configured to retrieve historical data from Wonderware Historian Server (formerly known as IndustrialSQL Server or InSQL). If Wonderware Historian is moved to a different computer after QI Analyst has been configured, QI Analyst may not be able to retrieve data from the Historian as an incorrect computer name or server alias is used by QI Analyst to access data. In such case Wonderware QI Analyst workspace may fail to open. This tech note describes the procedure to rectify the problem.


Tech Note 80: How to use the $PingNode Object Template in Wonderware Application Server

This tech note describes how to use a custom $PingNode object template created for Wonderware Application Server. Object based on that template provides ping status for a given machine (node).

The $PingNode object template includes the Ping script that can be customized to provide additional features. By default the enabled object will ping the configured node every 10 seconds and report general status and reply time. It also can be configured to alarm if a ping timeout is incurred.

This type of information should be useful for monitoring system health of network hardware and other machines that are not part...

Tech Note 79: How to install Microsoft Loopback Adapter on different operating systems

Wonderware Industrial Application Server uses the Suitelink protocol (a proprietary TCP/IP wrapper) and the NMX protocol (Network Message Exchange) to communicate with I/O devices and platforms/objects in the application galaxy. The Archestra Integrated Development Environment (IDE) uses the NMX protocol to communicate with and deploy objects to platforms in the galaxy (this requires a valid network connection for development and testing operations). In the absence of a network adapter or valid network connection, Microsoft's Loopback Adapter may be installed to satisfy the Archestra IDE's requirement for a valid network connection.

The Microsoft Loopback Adapter will prevent the Archestra IDE from closing...

Tech Note 77: How to resolve Language Switching Dictionary XML Import errors

The release of Wonderware InTouch 9.5 Service Pack 1 added a comprehensive Runtime Language Switching feature. This Runtime Language Switching feature gives developers the ability to create applications where the displayed language can be changed at runtime based upon the requirements of the user.

In addition, Wonderware released the Language Switching Translation tool: a Microsoft Excel file that can be used to export or import an application's text fields to and from an XML file for easier translation.

Developers may not have access to Microsoft Excel during application development or may use a text editor to add the text translations to...

Tech Note 76: Configuring the DDESuitelink Client Object in the ArchestrA IDE

This tech note details the procedure used to configure DDE (Data Dynamic Exchange) and Wonderware Suitelink client connections using Wonderware Application Server and the ArchestrA IDE (Integrated Development Environment). The DDESuiteLinkClient object available in Archestra IDE provides a client connection to DDE or Suitelink servers so that data can be read and written to external data sources such as a PLC (Programmable Logic Controller).

This tech note consists of three parts:

  • Part 1 - details the process of configuring and deploying a new instance of the $DDESuiteLinkClient template for communication with a data source
  • Part 2 - details testing of the...

Tech Note 75: How to Automate the Update Function Feature in Wonderware ActiveFactory IndustrialWorkbook

This Tech Note provides the procedures necessary to automate the Refresh Function on every function in the Wonderware ActiveFactory IndustrialWorkbook.

This procedure is beneficial when working with Excel spreadsheets that contain many ActiveFactory functions. By default the Refresh Sheet function of Wonderware ActiveFactory IndustrialWorkbook does not refresh new cell population. Because of this users would need to select and refresh every individual function in the workbook.