Previously Primary Controller goes in failure on restart after switchover?

Hi,

I am using an 800xA System 5.1 FP4, and my range of controllers include PM861, PM864A and PM865A (Sil3) and everything seems to be correctly configured. All the controllers work in redundancy on start up with Prim and Dual LEDs lit as they should be.

The issue arises when I cause a fault in the primary controler (A). The seconday controller (B) takes over as required instantly. However the Controller A on startup goes in fault and does not startup. If I then give a power cycle to the Controller A, it then starts up correctly and assumes the secondary role as required.

I am facing this problem in all my controllers so it must be some issue with the configuration. I have set the secondary controller IP address from the IP Config Tool and since on intial startup the controllers do go in redundancy I do not believe the issue would arise from there.

Each controller has different modules on its CEX Bus;

PM861: No module, connected by TK850.

PM864A: BC810, CI854A.

PM865A: BC810, SM811.

Please also see the attached Controller Logs.

I have also confirmed all the firmwares so I do not believe the issue lies over there. I also increased the task intervals but to no use.

One point that I would like to clarify is in the IP Config Tool, I unchecked the Enable Autorestart; does this have any bearing on this issue?

Thanks and Regards,

Haidar

Comments (0) New comment

haidar.hussein Rank: 250

Asked 4 years ago

Answer this question Follow

Answers

The option in IPConfig 'Enable Autorstart' if checked, then controller restarts automatically after a software crash. Then you can download to the project. If disabled, then manual restart of the controller is required before download.

So it is to decide whether the controller should restart automatically after a crash.

This action will only remove the manual restart option if checked. We also keep this option un-checked to make sure user should restart after each crash with his consent. So when there is a crash, you have to manually restart the failed controller in order to fetch the log and bring it back to the network.

Comments (4) New comment