Applies To:
  • CitectSCADA 5.xx

If you are using Alarm, Report, or Trend clusters in your project, it may cause redundancy issues.

This affects those that use servers as a display client and switch to different clusters on the Citect SCADA network. When alarm, report and trend redundancy is configured, SCADA starts with a client connection to its redundant pair for each type of server configured. What can happen is that if you switch clusters and subsequently a redundant server goes down, the redundant client connection will attempt to connect to the standby server specified at the last cluster change. This is incorrect. It should constantly recall the original redundant server from startup. 

Citect has confirmed this to be a problem in CitectHMI/SCADA versions 5.xx. This problem has been fixed in version 6.10.