New in InTouch HMI 2023 R2

InTouch HMI 2023 R2 (Version 23.1.000) includes a number of new features, hot fixes, and provides support for the latest versions of Microsoft products. Refer to the GCS Technology Matrix for the list of supported Microsoft products.

Alarm Latching and Alarm Dismiss

If the Alarm latching feature is enabled, an acknowledged alarm that has returned to a normal value will continue to be displayed in the LATCHED alarm state. LATCHED alarms can be displayed in the current alarms mode to show that the alarms did occur. Alarms go to the LATCHED state when:

• ACK an alarm from UNACK_RTN state.

  Or

  Return an alarm from ACK state.

To view the LATCHED state, enable the LATCHED state in the Alarms and events configuration screen of the IDE. You can dismiss the LATCHED alarms to remove the LATCHED alarms from the current mode of the Alarm Client Control grid. The dismissed LATCHED alarms will be visible in the recent mode of the Alarm Client Control.

Credential Manager

Use the Credential Manager utility to securely store and manage login credentials. You can retrieve the stored credentials (from AVEVA Application Manager for standalone applications, and from the Application Server for managed applications) for authenticating access to other components in WindowMaker, WindowViewer, and Alarm utilities.

By default, all named credentials are added to the Administrators group. In addition, we recommend that you add groups to which the users running the application belong. This will allow users to access their credentials even when running the application in a non-administrator mode, such as WindowViewer.

Changes to the default TCP port for communication with Historian Server

The default TCP port for communication with Historian server has been changed to 32565. This is configurable and is used for data replication and communication with remote IDAS version 2023 R2 and later. The Classic Historian TCP port - 32568 was used for data replication and remote IDAS communication with Historian versions 2023 and earlier, and is retained for compatibility with previous versions.

OPC UA enhancements

A new option, External providers, has now been added under the Tag dictionary. It lists all the OPC UA server connections configured in the Gateway Communication Driver present on the same machine. Using this option, you can avoid several manual steps and easily create access names and InTouch tags for OPC UA item references. Create the tags by dragging and dropping from the External providers pane to the new Model – Tagname pane, which displays all the alarm groups and tags of the InTouch application.

Create graphic elements and Industrial Graphics using InTouch tags

A Model – Tagname tab has been added in the Properties configuration pane of the Industrial Graphic Editor, which displays all the tags available in the InTouch application. You can drag and drop the tags to the canvas to create graphic elements or Industrial Graphics. When creating multiple symbols at a time, the dot field property will be bounded automatically. This method simplifies the graphic development workflow and significantly reduces the application development time.

Embed an Industrial Graphic from the Toolbox tab of Industrial Graphic Editor

You can embed an existing Industrial Graphic into your current graphic using the Toolbox tab located in the Properties configuration pane of the Industrial Graphic Editor. The Toolbox tab displays all the Industrial Graphics available in the InTouch library. After you have embedded the graphic, you can then edit it like any other component of the graphic.

Support for Import of SVG as an Industrial Graphic

The Industrial Graphic Editor supports the import of Scalable Vector Graphics (SVG) as Industrial Graphics. You can perform the following:

• Import an SVG into the Industrial Graphic Editor. The graphic elements are automatically converted to an Industrial Graphic, which can include many primitives.

• Insert the SVG while using the Image icon from the Tools panel of the Industrial Graphic Editor

• Use SVG for the UpImage and DownImage on a button

• Use SVG for the Quality & Status display icons under Styles configuration

Support for user defined types (UDTs) in InTouch

This feature supports the following:

Manually create one or more UDTs, with nesting up to six levels

Manually create one or more UDT instances from a UDT

Bind individual UDT instance members to I/O

Reference individual UDT instance members in Industrial Graphics symbols

Import and export UDT to a JSON file

Edit UDT in bulk using external JSON editor

Edit and override UDT Properties except Name and Type

Changes in a data type are reflected immediately in the User Defined Type view

Configure the owning object of an embedded graphic and point to an UDT instance. During runtime, the me. relative reference is replaced by the UDT instance. You can also update the owning object to a different UDT instance during runtime.

Intellisense for UDT instances lists all members and member data structures for the immediate level only. The Industrial Graphic Editor supports intellisense in scripting, animation, and custom properties. Native InTouch supports intellisense in scripting only.

You can configure UDTs in Industrial Graphic animations and native InTouch animations.

You can configure UDTs in an Industrial Graphic script and a native InTouch script.

Update the alarm properties in the Properties grid. In the WindowViewer, you can view the members of an instance that are generating alarms and display them in an Alarm Client Control.

The UDT members of an instance can log data to LGH files or the Historian, as with other InTouch tags.

The UDT member of an instance behaves the same as other InTouch tags in the MapApp.

The UDT member of an instance works the same as other InTouch tags in the web client.

Introducing the new Unified Identity

AVEVA Unified Identity enables Single Sign-On (SSO) for all Operations Control products on a given node with AVEVA Connect cloud capabilities. It supports common user authentication, authorization, and access entitlements across AVEVA Operations Control products. It includes the following:

User Authentication via a single common user ID, configured and managed within AVEVA Connect.

User Authorization via roles, groups, and rules (allow/deny).

Single Sign-On: After you sign on to a supported product, subsequent sign-ons to that product or other supported products on the node are automatic.

The connected experience requires access to the AVEVA Connect cloud repository from each node where you want to use it.

Option to secure InTouch application folder

To restrict access to the applications folder for Standalone applications, a new check box has been introduced in Application Manager under Tools > Security. When the security feature is enabled on a node, strict read and write permissions are applied to the InTouch View Application.

Update default local working directory for NAD and Managed InTouch application

An option Enable local working directory integrity check for Managed and NAD InTouch Applications has been added in the Application Manager, under Tools > Node properties > Security. If this option is enabled, when launching WindowViewer for a Managed InTouch application and NAD (Network Application Development) application, a file time stamp and file content hash comparison is performed between the deployed application and the application in the local working directory. If the files do not match, WindowViewer will copy the deployed application to the local working directory and run the application.