# Automation Professionals' Advanced Modbus Driver

**URL:** <https://forum.inductiveautomation.com/t/automation-professionals-advanced-modbus-driver/41312>\
**Category:** 3rd Party Modules\
**Created:** [December 8, 2020, 8:45pm UTC](https://forum.inductiveautomation.com/t/automation-professionals-advanced-modbus-driver/41312 "2020-12-08T20:45:46Z")\
**Posts on this page:** 1\
**Showing post:** 68

<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:** [September 26, 2024, 6:26pm UTC](https://forum.inductiveautomation.com/t/automation-professionals-advanced-modbus-driver/41312/68 "2024-09-26T18:26:24Z")

</div>

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:

> [@Modbus TCP - Moore / Siemens 353](https://forum.inductiveautomation.com/t/modbus-tcp-moore-siemens-353/95970):
>
> I have a new installation with a Moore / Siemens 353 controller using Modbus TCP. It all works great for the first 15 or so minutes - then, it just times-out and cycles from connecting/disconnecting/etc. If I disable/enable, it starts to work again - for 15 minutes. Is there some obvious setting that I can change to correct this behavior?

---

_[View the full topic](https://forum.inductiveautomation.com/t/automation-professionals-advanced-modbus-driver/41312)._