Freelance 2013 diagnosis alarms
with regards to Rafidyja alarms:
It is a redundant AC 800F’s Ethernet modules in slot E1 (Control network) that have failed during self-test. Those self-test happens when the controller is booting. You need to look at the controller’s diagnostic data (via Web interface) to get the last error code.
A module counts how many times it failed a self-test. After 3 times failing, it is assumed to be broken and the Controller stops when booting as a safety measure to prevent a broken module to go into execution. One can force the controller via the terminal interface to go on, ignoring the errors, but it requires a manual intervention. As this is a redundant controller, it could happen that after a failover, if the controller with the 3-fault Ethernet module becomes secondary and reboots, redundancy is broken, until that manual intervention.
I strongly recommend to at least replace the 3-fault module, better both faulty modules.
Those alarms can be acknowledged, but as the fault doesn’t go away they will not disappear when acknowledged.
With regards to Zubair Mishrif:
There are several diagnostic messages for slaves 1, 2, 3 and 4 at the PROFIBUS line 1. “C1_S3” indicates PROFIBUS Line 1, Slave 4. “Diag. fault for module 2 12” indicates that modules number 2 and 12 on that slave have a diagnostic message.
“Diagn. Fault on unit” means the slave itself has diagnostic messages.
Reason for the diagnostics can be evaluated going into the System Display (or Freelance Engineering in commissioning mode)and browse to the mentioned slaves and modules and investigate the details shown there. It can be simple things, like you have not disabled an unconnected input (which produces cable break diagnostics) or real faults.