# 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:** 12
**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 3, 2024, 9:11pm UTC](https://forum.inductiveautomation.com/t/modbus-server-driver/95481/12 "2024-09-03T21:11:14Z")
A complete implementation of your use case with my alternate driver is shown over here: > [@Modbus Slave/Server to Generate Read Only Tags](https://forum.inductiveautomation.com/t/modbus-slave-server-to-generate-read-only-tags/87583/21): > > I've create a generic "Modbus Publish" script that eliminates the need for a second set of tags. I've publicly posted it here: [https://www.automation-pros.com/ignition/modbusPublish.py](https://www.automation-pros.com/ignition/modbusPublish.py) It requires the "Queue Utility" script posted here: [https://www.automation-pros.com/ignition/queueUtil.py](https://www.automation-pros.com/ignition/queueUtil.py) and described over here: Both scripts rely on my Integration Toolkit's globalVarMap() script function, but you can rework that (not quite 1:1) to use system.util.getGlobals() if you must. (Not recomme… Does not require double tags. Optionally takes advantage of the common address patterns between the IA driver and my server driver to minimize the configuration required. One of its users has precisely the same motivation as you: expose a device that accepts only one connection to multiple consumers. --- _[View the full topic](https://forum.inductiveautomation.com/t/modbus-server-driver/95481)._