Freelance AC800F FI830F Profibus communication error
Freelance AC800F FI830F Profibus communication is dropping to S900 IO Profibus slave.and all the S900 cards on that slave are not communicating. In redundant controller mode controller is toggle between before failure.
Communication is resuming after restart of RLM module. But problem repeating again after some time.
Attached are the logs of the AC800F controller kindly help me identify the where is the issue.
59523 PBM0 : Event 0x1001012F in PMDEVFC. Line 2685 10.01.18 10:26:43.357
59522 PBM0 : Event 0x1001012F in PMDEVFC. Line 2434 10.01.18 10:26:43.355
59521 PBM0 : Event 0x10010130 in PMDEVSO. Line 1203 10.01.18 10:26:42.877
59520 PBM0 : Event 0x10010112 in PMDEVFC. Line 4205 10.01.18 10:26:42.875
59519 PBM0 : Event 0x10010190 in PMDEVSO. Line 1007 10.01.18 10:26:32.428
Redundancy Toggle ->Prim (Fieldbus) 10.01.18 10:24:48.887
59517 RRCV : Event 0xFFFF03A7 in REDBTR.d Line 3766 10.01.18 10:24:47.030
59516 RRCV : Event 0xFFFF03A7 in REDBTR.d Line 3766 10.01.18 10:18:18.376
Redundancy Toggle ->Sec (Fieldbus) 10.01.18 10:18:18.305
59514 PBM0 : Event 0x1001012F in PMDEVFC. Line 2685 10.01.18 10:18:18.297
59513 PBM0 : Event 0x1001012F in PMDEVFC. Line 2434 10.01.18 10:18:18.295
59512 PBM0 : Event 0x10010130 in PMDEVSO. Line 1203 10.01.18 10:18:17.813
59511 PBM0 : Event 0x10010112 in PMDEVFC. Line 4205 10.01.18 10:18:17.810
59510 PBM0 : Event 0x10010190 in PMDEVSO. Line 1007 10.01.18 10:17:32.312
Redundancy Toggle ->Prim (Fieldbus) 10.01.18
I propose you open a case with the ABB support line.
The Profibus master gets quite some Diagnostic messages which have a zero lenght (0x10010210) before the controller finally fails over to the secondary. The secondary has problems to establish communication with the slave, stating a protocoll error and that the slave does not behave correctly (0x10010190). Subsequently the master tries to get the slave into cyclic communication but fails and toggles back to the old primary.
Reasons could be a bad slave communication module, a bad RLM or a bad FI830. You can try to replace them subsequently, one at a time, to see if the error disappears.
Also timing issues on the Profibus line could be the reason if you did not take into account the data telegram delay of an RLM of 11 Bit times [us] + 0.6 us.
Also wrong bus termination comes to my mind, especially with RLM you have to consinder each of the lines A,B,M to be a seperate Profibus line and to be terminated correctly.
You see, the situation is very complex and opening a support case will serve you best.