Wonderware+intouch+105 [ CONFIRMED ]

Since AVEVA has declared versions prior to 2017 as "legacy," official support is limited. However, you can find help via:

IF Tag("PumpCmd") = 0 THEN
  Tag("PumpCmd") = 1
ELSE
  Tag("PumpCmd") = 0
END IF

AlarmAcknowledge(Tag("AlarmID"))

(Note: adapt to actual VBScript/JScript syntax used in WindowMaker/InTouch.)

If you are installing v10.5 today, you may encounter these specific issues: wonderware+intouch+105

To understand why version 10.5 was so important, one must look at the architecture behind it. Wonderware had long been the king of standalone HMI applications. However, as plants grew larger and data became more distributed, the need for a unified "System Platform" emerged.

InTouch 10.5 was built on the ArchestrA technology framework. This was a paradigm shift. Before this, an HMI was often a standalone island of data. With 10.5, the InTouch application became a window into a broader Galaxy (the application object database). This allowed for object-based development, where a pump object created once could be replicated across a plant with its scripting, alarms, and history already embedded. Since AVEVA has declared versions prior to 2017

This is the most common strategy for v10.5.

InTouch 105 suffers from memory leaks. Set up a scheduled task (via a script) to restart WindowViewer nightly at 2:00 AM during downtime. Use a master/slave redundancy model to swap between two PCs. IF Tag("PumpCmd") = 0 THEN Tag("PumpCmd") = 1

Critical Warning: Do not install InTouch 10.5 on Windows 10 or Windows 11. It is unsupported and will cause DCOM errors, graphics flickering, and communication dropouts.

Version 10.5 has specific prerequisites that differ from modern versions.