We are currently facing an issue with multiple HMIs running a Cimplicity project that handles data input/output for three units. The problem is that Alarm messages from the T controllers of the second unit appear in the WorkstationST Alarm Viewer but are not displayed in the Cimplicity project's AlarmList.

Here's what has been checked so far:

• UDH and PDH configuration has been verified.
• LHMI and RHMI have been rebooted.
• The project on each HMI has been restarted in Workbench.
• All services in WorkstationST Status Monitor are showing as "OK."
• Additionally, Cimplicity Log Viewer shows entries stating "Alarm definition not configured T40U2" every time alarm messages from the Cimplicity project are acknowledged in the AlarmList.

The controllers of the second unit have also been rebooted. During the reboot, diagnostic I/O messages present on the controller do appear in the Cimplicity AlarmList. In the AlarmList settings, all message types and classes have been specified, and all sources are included. There are no message filters applied.

The main issue is that alarm messages from the second unit are not appearing in the Cimplicity AlarmList. Any suggestions or insights on resolving this would be greatly appreciated.

 

The error of outputting alarm signals from Unit to HMI has been fixed. To fix this, Build and Load were performed in the ToolboxST project for the RHMI configuration. Afterwards, the Alarm Server and Cimplicity Workbench services were restarted on RHMI. As a result, the Cimplicity and Alarm List projects began to display Unit alarm messages correctly. To check the correct output of messages, the mineral oil tank heater was switched to manual control, the message was displayed, The turbine casing door was opened, a message about unauthorized door opening was received

 

The log message "Alarm definition not configured T40U2" indicates that there may be a missing or incorrect alarm definition for that specific controller. Go into the Cimplicity Workbench and double-check the alarm definitions for the second unit.

 

The log message "Alarm definition not configured T40U2" indicates that there may be a missing or incorrect alarm definition for that specific controller. Go into the Cimplicity Workbench and double-check the alarm definitions for the second unit.

The error of outputting alarm signals from Unit to HMI has been fixed. To fix this, Build and Load were performed in the ToolboxST project for the RHMI configuration. Afterwards, the Alarm Server and Cimplicity Workbench services were restarted on RHMI. As a result, the Cimplicity and Alarm List projects began to display Unit alarm messages correctly. To check the correct output of messages, the mineral oil tank heater was switched to manual control, the message was displayed, The turbine casing door was opened, a message about unauthorized door opening was received