# Is there a good functional reason to add two PLC connections to separate Leased and Driven tags?

**URL:** <https://forum.inductiveautomation.com/t/is-there-a-good-functional-reason-to-add-two-plc-connections-to-separate-leased-and-driven-tags/113457>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [January 21, 2026, 5:42pm UTC](https://forum.inductiveautomation.com/t/is-there-a-good-functional-reason-to-add-two-plc-connections-to-separate-leased-and-driven-tags/113457 "2026-01-21T17:42:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![bmeyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmeyers/32/37453_2.png) [@bmeyers](https://forum.inductiveautomation.com/u/bmeyers)\
**Post date:** [January 21, 2026, 5:42pm UTC](https://forum.inductiveautomation.com/t/is-there-a-good-functional-reason-to-add-two-plc-connections-to-separate-leased-and-driven-tags/113457/1 "2026-01-21T17:42:03Z")

</div>

I am looking at a customer's setup and they separated PLC connections based off the type of tag they are pulling from it. I am scratching my head as to why they would do this setup when they could just make two tag providers to accomplish the same thing.

Am I crazy or is this unnecessary? Wouldn't this add unnecessary overhead to the gateway?

The connections list looks like the following:

```python
PLC_A_Leased
PLC_A_Driven
PLC_B_Leased
PLC_B_Driven
PLC_C_Leased
PLC_C_Driven
```

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [January 21, 2026, 5:43pm UTC](https://forum.inductiveautomation.com/t/is-there-a-good-functional-reason-to-add-two-plc-connections-to-separate-leased-and-driven-tags/113457/2 "2026-01-21T17:43:55Z")

</div>

This is done so that re-optimization due to lease changes doesn't effect the non-leased tags.

---

<div class="post-metadata">

**Author:** ![bmeyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmeyers/32/37453_2.png) [@bmeyers](https://forum.inductiveautomation.com/u/bmeyers)\
**Post date:** [January 21, 2026, 6:22pm UTC](https://forum.inductiveautomation.com/t/is-there-a-good-functional-reason-to-add-two-plc-connections-to-separate-leased-and-driven-tags/113457/3 "2026-01-21T18:22:08Z")

</div>

Thanks, your answer helped me find more information about it.

> [@How fast does "leased" tag time take effect](https://forum.inductiveautomation.com/t/how-fast-does-leased-tag-time-take-effect/34936/6):
>
> Normally it takes effect a lot faster than that, but for heavily loaded devices switching between rates can be expensive. To “clean room” test it, try the following: Set up a new device connection to the device (along-side your existing device connection) Set up a single tag on a leased scan class / tag group Put that individual tag in a window. Open that window and observe how long it takes to switch. If those steps show the leased tags come through quickly, you’re probably running into sl…

---

<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:** [January 21, 2026, 8:38pm UTC](https://forum.inductiveautomation.com/t/is-there-a-good-functional-reason-to-add-two-plc-connections-to-separate-leased-and-driven-tags/113457/4 "2026-01-21T20:38:49Z")

</div>

> [@Kevin.Herron](#):
>
> re-optimization due to lease changes

This is not an issue with my drivers, FWIW.

The lease killer is **this** :

> [@How fast does "leased" tag time take effect](https://forum.inductiveautomation.com/t/how-fast-does-leased-tag-time-take-effect/34936/13):
>
> No, known pathological OPC client behavior. If there is any enabled OPC tag that yields unknown node, subscription changes are batched every 8 seconds.

I know Kevin plans a fix, but there no timeline that I know of.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [January 21, 2026, 8:41pm UTC](https://forum.inductiveautomation.com/t/is-there-a-good-functional-reason-to-add-two-plc-connections-to-separate-leased-and-driven-tags/113457/5 "2026-01-21T20:41:22Z")

</div>

This behavior changed in 8.3 for the better.

There’s still an issue with the Logix driver’s heavy-handed approach to re-optimizing every time subscriptions change.

I’m testing a new approach to managing sampling that should be more friendly to lease changes with the Beckhoff ADS driver. If it works out, future drivers, including some future Logix driver rewrite, will probably use a similar approach.