# New DNP3 Driver Beta

**URL:** <https://forum.inductiveautomation.com/t/new-dnp3-driver-beta/80774>\
**Category:** Ignition Early Access\
**Created:** [October 20, 2023, 4:18pm UTC](https://forum.inductiveautomation.com/t/new-dnp3-driver-beta/80774 "2023-10-20T16:18:10Z")\
**Posts on this page:** 1\
**Showing post:** 101

<div class="post-metadata">

**Author:** ![msteele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/msteele/32/77889_2.png) [@msteele](https://forum.inductiveautomation.com/u/msteele)\
**Post date:** [December 6, 2024, 7:41pm UTC](https://forum.inductiveautomation.com/t/new-dnp3-driver-beta/80774/101 "2024-12-06T19:41:56Z")

</div>

Is there any consideration for adding connection redundancy for this and other drivers? (I ask about this one since we rely heavily on it and it's one of the newest).

It would be great to have a way to target two DNP3 outstations representing a primary/backup or an A/B in a failover scheme.

Otherwise [it looks like](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957/4) the best approach is to build some scripting that tests conditions on multiple DNP3 outstations and swaps all UDT instance `opc_dnp3DeviceName` string parameters based on certain conditions which would then remap all OPC Item Paths from one device to another.

---

_[View the full topic](https://forum.inductiveautomation.com/t/new-dnp3-driver-beta/80774)._