...
A common issue is disconnected / offline devices constantly throwing communication faults.
in the SCU under Task Configuration you can add C to the command line to to supress communication faults.
See this Tech note. The command line is at the end of the note.
https://automatech.app.box.com/s/0rg97ysf39lpi08dfifkrmb3dzrukex7
...
At the SCADA, if you run Netdiag and select the NNT tab, you will see the connection order that the Clients connected to the SCADA.
Each time an alarm occurs, it sends the Alarm to clients in the order they connected.
The message is sent , then the client answers that it received the message an it goes down the list.
...
If they you have configured "Fake" iFix Reduncy and do not actually have actual Failover SCADAs configured ,
Then you are also Duplicating the alarms. Each SCADA is acting as an independant SCADA and is sending out its own Alarm to each Client.
If they have interconnected the SCADAs, ( List the other SCADAs as Remote nodes in the SCADA SCUs ) , then all alarms from the other SCADAs are sent to the "Client" SCADA.At the SCADA, if you run Netdiag and select the NNT tab, you will see the connection order that the Clients connected to the SCADA.Each time an alarm occurs, it sends the Alarm to clients in the order they connected.
The message is sent , then the client answers that it received the message an it goes down the list.
...
The graphics can have their Animation rates slowed to 0.5 or 1 second updates rates.
This helps cut the network loading on the SCADAs. See the refresh rate tool in the Picture Toolbox.
See documentation about Network Loading.
...
You can configure the SCADA to only send Specific Alarms to Specific Client nodes.
If the Clients have specific duties , then you can have the SCADA only send alarms that matter to that Node / Operator.
...
...
...
Understanding Alarm Transfer https://www.ge.com/digital/documentation/ifix/version2022/index.html#environment-setup/env_understanding_alarm_transfer.htm