Emerson Exchange 365

• Not Answered

ALARMS.MACK value remains 1

Hi,

In phase SFC logic I have pulse action to acknowledge any unit alarms using alias with a confirm expression that ALARMS.MACK = 0. Pulse action is remaining active and when investigating I see that ALARMS.MACK value is set to 1 but remains at that value causing confirm expression to not be true. Any ideas on why this field value would not reset to 0 at next scan? This issue only appears to occur occasionally and there has been no correlation made with the state of any of the unit module alarms at time of executing action. The unit has been downloaded and as well as controller setup data and still occasionally see issue. Also worth noting this issue only started showing up after upgrading from V12 to V14.

Phase Pulse Action Expression:

#THISUNIT#/ALARMS.MACK := 1

Confirm Expression:

#THISUNIT#/ALARMS.MACK = 0

Thanks,

Colton Feller

Colton Feller

• 5 May 2021 7:05 PM
• Cancel

2 Replies

• Andre Dicaire

  

  • 5 May 2021 10:08 PM

  According to BOL, MACK should return to 0, as it did in v12. I would suggest you open a CTS call with the GSC. On that note, have you installed the latest Hotfixes to the system?

  Andre Dicaire

  • Cancel
• Colton Feller

  

  • 6 May 2021 3:48 PM

  In reply to Andre Dicaire:

  Initial GSC support didn't even know about the .MACK field...
  
  We will check on any pending Hotfixes and continue to escalate with GSC and local EIP.
  
  Thanks,
  
  Colton Feller

  • Cancel