# Modbus TCP uncontrolled polling

**URL:** <https://forum.inductiveautomation.com/t/modbus-tcp-uncontrolled-polling/32176>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [February 12, 2020, 5:03pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-uncontrolled-polling/32176 "2020-02-12T17:03:07Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![jgardner](https://avatars.discourse-cdn.com/v4/letter/j/a587f6/32.png) [@jgardner](https://forum.inductiveautomation.com/u/jgardner)\
**Post date:** [February 14, 2020, 2:07pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-uncontrolled-polling/32176/6 "2020-02-14T14:07:06Z")

</div>

I confirmed yesterday that the 8.0.9 nightly build has (so far) resolved the Direct / Leased polling rate issue. I was able to create stable UDT instance Modbus Tags (with parameterized paths). It is also allowing one address range (readings) to have a faster rate than another range (serial numbers). All is right in the world at the moment. 👍

---

_[View the full topic](https://forum.inductiveautomation.com/t/modbus-tcp-uncontrolled-polling/32176)._