Applies To:
  • CitectSCADA 1.00, 1.01, 1.10, 1.11, 1.20, 2.00, 2.01

Question: The alarms are not acked on the alarm server on startup. I have set the [alarm]ack=1 option but the alarms are still not acked at startup. 

The alarms are only acked at startup if you have a single alarm server and no save file configured. If you have a Primary and Standby alarm server, then when an alarm server starts up, it will get all the current alarm states from the other alarm server. As the alarms are in their current valid states, there is no reason to ack them at startup. If you don't have a Standby alarm server, and have a save file configured, the alarm states will be recovered from the save file. If the alarms are recovered from the save file, then they also will not be acked at startup.

If you need to ack the alarms at startup - even if there is a Standby server or valid save file - call the AlarmAck function from the startup Cicode.