# PLC / Network Redundancy in Ignition **URL:** \ **Category:** Ignition\ **Tags:** scripting\ **Created:** [January 2, 2024, 2:06pm UTC](https://forum.inductiveautomation.com/t/plc-network-redundancy-in-ignition/83683 "2024-01-02T14:06:24Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![Khurram\_sarfraz](https://avatars.discourse-cdn.com/v4/letter/k/67e7ee/32.png) [@Khurram\_sarfraz](https://forum.inductiveautomation.com/u/Khurram_sarfraz)\ **Post date:** [February 10, 2024, 12:41pm UTC](https://forum.inductiveautomation.com/t/plc-network-redundancy-in-ignition/83683/7 "2024-02-10T12:41:12Z")
> [@Redundancy configuration for Siemens 400 PLC](https://forum.inductiveautomation.com/t/redundancy-configuration-for-siemens-400-plc/80119/11): > > I am using the same method as you have described where the UDT parameter name is set by using system.tag.writeBlocking script I want to changeover from PLC1 to PLC2 when PLC1 is no longer connected. I have Connected status from PLC1 (S7-400H) as integer and im using it in IF ELSE script to changeover to PLC2 (S7-400H) when PLC1 is no longer connected. This script doesn't work for me, I have also tested creating Memory integer tag instead of connected status tag and simulated 0 and 1 but that … The application i have in my project is to only read the values from the PLC and not control. And if the PLC we are connected to is lost (shutdown) our tags should shift over to the Redundant one. This post was very helpful and I think im missing a small trick here, Applying the the udt method where parameter name can be shifted to the other PLC when one PLC which we are connected to is lost ... will solve my problem.. If someone can help .. Thanks --- _[View the full topic](https://forum.inductiveautomation.com/t/plc-network-redundancy-in-ignition/83683)._