# CODESYS Redundancy with PFC200 controllers

**URL:** <https://www.wago.community/t/codesys-redundancy-with-pfc200-controllers/1153>\
**Category:** CODESYS\
**Tags:** pfc200, codesys\
**Created:** [August 21, 2024, 10:57am UTC](https://www.wago.community/t/codesys-redundancy-with-pfc200-controllers/1153 "2024-08-21T10:57:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Petrus](https://avatars.discourse-cdn.com/v4/letter/p/ecd19e/32.png) [@Petrus](https://www.wago.community/u/Petrus)\
**Post date:** [August 21, 2024, 10:57am UTC](https://www.wago.community/t/codesys-redundancy-with-pfc200-controllers/1153/1 "2024-08-21T10:57:27Z")

</div>

I made CODESYS Redundancy tests with two 750-8212 controllers (firmware 27). When a network cable between active and passive controller is removed, it seems that recovery takes sometimes over 5 minutes. Both controllers remain in Standalone state and synchronization doesn’t happen. By clicking manually “synchronization” button in Redundancy Configuration, controller state changes to Active-Passive. Usually, recovery to Active-Passive state is fast and happens automatically. By rebooting a controller, recovery is also fast and most of the time there is no Standalone issue. However, sometimes both controllers stay in Standalone mode also after a reboot.

Have you met similar behavior with CODESYS Redundancy? I have timeout setting 1000 ms and Synchronization timeout setting 100 ms for redundancy. I didn’t see difference when these values were increased. I also got information that similar long Standalone state issue is visible with other hardware than WAGO controllers.

In Runtime log, I can see the following messages. “DEBUG RedundancySynchronize called” is repeating for several minutes until message “DEBUG Try to synchronize”.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/1X/58211ff7ec5d3ba693d050856d3ed9b67dd3875e.png)