# PLC redundancy TCP IP and COM (radio)

**URL:** <https://forum.inductiveautomation.com/t/plc-redundancy-tcp-ip-and-com-radio/113897>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [February 11, 2026, 9:19am UTC](https://forum.inductiveautomation.com/t/plc-redundancy-tcp-ip-and-com-radio/113897 "2026-02-11T09:19:49Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 11, 2026, 1:23pm UTC](https://forum.inductiveautomation.com/t/plc-redundancy-tcp-ip-and-com-radio/113897/5 "2026-02-11T13:23:57Z")

</div>

If you make both connections Modbus RTU over TCP, my alternate Modbus module may suit your needs. It can maintain dual connections (alternating paths), then fall back to one path when the other fails.

> [@Automation Professionals' Advanced Modbus Driver](https://forum.inductiveautomation.com/t/automation-professionals-advanced-modbus-driver/41312/68):
>
> Automation Professionals is pleased to announce a new production release of the Advanced Modbus Module. For Ignition v8.1.x: v1.1.7.242701819 This includes a bugfix for the driver status problem mentioned in [comment #63](https://forum.inductiveautomation.com/t/automation-professionals-advanced-modbus-driver/41312/63) above. This includes the constrained Transaction ID feature requested in this topic:

---

_[View the full topic](https://forum.inductiveautomation.com/t/plc-redundancy-tcp-ip-and-com-radio/113897)._