InTouch HMI known issues

Issue ID

Description

4022193

Trend Pen is not connecting to Historian when SMS is turned off and InTouch application was running on a computer other than the Historian.

Workaround

It will work only for the following SMS configuration:

First and second options under Configurator->System Management Server

IMS-3566480

IMS-4878412

Alarm Client Control failed to retrieve alarms from a history block when the number of alarms is huge.

Workaround

To prevent out-of-memory issues while fetching a large number of alarms in the Alarm Client Control, follow the procedure below:

When displaying 100,000 alarms, the process memory of the View process increases by approximately 600 MB. To keep the memory usage within acceptable limits, it is necessary to configure a maximum limit for historical alarms.

Configuration Steps:

• InTouch Or OMI applications

  1. Set the MaxTotalRetrievalCount property of alarm client.

  2. In the OnShow script of the symbol that contains the Alarm Client Control, set the MaxTotalRetrievalCount property. Using AlarmClient.MaxTotalRetrievalCount = XXXXXX

• InTouch applications only

  For InTouch applications, you can also set the maximum limit using the MaxHistAlarmsCount property in the intouch section of the intouch.ini file.

Example:

MaxHistAlarmsCount=XXXXXX;

Location of intouch.ini

• Managed application:

  C:\Program Files (x86)\ArchestrA\Framework\FileRepository\<galaxy_name>\ObjectFileStorage\

  lt;intouchtemplatename>\CheckedOut

  C:\Program Files (x86)\ArchestrA\Framework\FileRepository\<galaxy_name>\ObjectFileStorage\

  lt;intouchtemplatename>\CheckedIn

• Deployed application: C:\Program Files (x86)\ArchestrA\Framework\Bin\<YourProjectName>

2612382

MxDataProvider Service is not deploying on Runtime node as PCS-Services Repository is installed on Runtime node.

2897808

Attempting to sign an alarm acknowledgement fails in a Managed InTouch application with an error message warning of incorrect user credentials. The SignedAlarmAck feature is not currently supported for a Managed InTouch application configured for AVEVA Operations Control connected experience.

1928318

When the Supertag instances are created by importing from a .CSV file, the imported Supertags are not displayed in the Supertags pane of the WindowMaker.

Workaround: The Supertag instances created by importing from a .CSV file can be viewed in the tag dictionary.

1765301

When an existing Custom Client Control or Web Widget is overwritten to the Cloud, the latest version is not available for other users.

Workaround: To overwrite an existing Custom Client Control or Web Widget to the Cloud, restart the WindowMaker and delete the existing client control or Web Widget in the source repository. This allows successful upload/download of the the client control.

Similarly, restart the WindowMaker to retrieve the latest Custom Client Control or Web Widget.

TFS-1351507

Language switching is not supported for the Carousel Widget in runtime.

TFS-1369183

A Carousel Widget containing the Web Browser Widget, QR Code Scanner Widget, Trend Client Control, Alarm Client Control or SQL Data Grid Control will not display correctly in WindowViewer, as default browser security options prevent cross-origin requests.

TFS-1371799

When an InTouch 2020 application (.aapkg) is exported and imported to InTouch 2020 R2, then the default namespace for a tag reference within a Carousel widget is not resolved in runtime.

Workaround: Open the graphic containing the Carousel widget. Edit any property and save the graphic. The tag reference is resolved, and the graphic is displayed in runtime.

TFS-1374896

After a graphic/toolset is created, the letter case of the graphic name cannot be changed in WindowMaker. For example: INTOUCH cannot be changed to InTouch.

Workaround: Rename the graphic to a temporary name. Rename the graphic again with the correct letter case. For example: Rename INTOUCH to ChangeName and then rename to InTouch.

TFS-1377672

Connecting many clients to a busy OPC UA server may cause various warnings and errors to be logged from the InTouch OPCUA Host process. Warning messages are for information purposes only and do not indicate any loss in functionality. Error message indicate that the operation was aborted.

Workaround: It is recommended that client connections to the server be planned and monitored, so not to burden the server and cause connection failures.