# Modbus Server Driver **URL:** \ **Category:** 3rd Party Modules\ **Created:** [September 3, 2024, 1:46pm UTC](https://forum.inductiveautomation.com/t/modbus-server-driver/95481 "2024-09-03T13:46:18Z")\ **Posts on this page:** 1\ **Showing post:** 48
**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:** [June 1, 2026, 6:23pm UTC](https://forum.inductiveautomation.com/t/modbus-server-driver/95481/48 "2026-06-01T18:23:38Z")
It already supports that, either via a gateway serial port, or via a remote ethernet-to-serial converter. I have clients using it specifically because it has sane multi-drop behaviors and very predictable slave interleaving. Perhaps you should try it? See this comment and the question above it: > [@Automation Professionals' Advanced Modbus Driver](https://forum.inductiveautomation.com/t/automation-professionals-advanced-modbus-driver/41312/164): > > There is no 1:1 equivalent. But the driver does round-robin scheduling of requests to units, and has per-unit rate limits. If, in a single poll rate, you have multiple requests to each of four units, they'll be executed like so: Unit 1 Req 1 Unit 2 Req 1 Unit 3 Req 1 Unit 4 Req 1 Unit 1 Req 2 Unit 2 Req 2 .... If the each set of requests takes longer than the per-unit rate limit, then the poll will smoothly run through all of the requests from start to finish, then wait for the next poll s… --- _[View the full topic](https://forum.inductiveautomation.com/t/modbus-server-driver/95481)._