Applies To:
  • CitectSCADA 3.40 4.20

I have alarms associated with a device and when that device returns from a state of communications break all the alarms get logged to the alarm device I have configured, regardless of their state. This did not happen is previous versions. What is wrong? 

A problem was introduced in Versions 3.40, 4.20 where all alarms, regardless of their state, are logged to the configured alarm device. This happens when communication to the device the alarms are associated with is regained after a time of failure (often known as 'coming out of #COM'). CIT has confirmed this to be a problem in Citect for Windows versions 3.40 and 4.20. This problem has been fixed in version 3.40 Patch C and 4.20 Patch C respectively. These patches are available on our BBS or FTP site.