# Ignition as Modbus Slave OR Write **URL:** \ **Category:** Ignition\ **Created:** [December 18, 2017, 10:18pm UTC](https://forum.inductiveautomation.com/t/ignition-as-modbus-slave-or-write/16356 "2017-12-18T22:18:29Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![afarzin](https://avatars.discourse-cdn.com/v4/letter/a/c5a1d2/32.png) [@afarzin](https://forum.inductiveautomation.com/u/afarzin)\ **Post date:** [December 18, 2017, 10:18pm UTC](https://forum.inductiveautomation.com/t/ignition-as-modbus-slave-or-write/16356/1 "2017-12-18T22:18:29Z")
My end goal is to have data that Ignition is currently reading made available to another device (PLC). Is it possible to have the modbus drive act as a TCP slave, or to have all the tags be written out to specific registers on the other device in bulk (at the device config level, not writing a script for each tag inside Vision). ---
**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:** [December 18, 2017, 10:39pm UTC](https://forum.inductiveautomation.com/t/ignition-as-modbus-slave-or-write/16356/2 "2017-12-18T22:39:50Z")
The driver only acts as a master. You could add the other slave device as a device in Ignition and periodically read from the first and write the results into the 2nd with a gateway timer script or something. ---
**Author:** ![dcamp](https://avatars.discourse-cdn.com/v4/letter/d/a88e4f/32.png) [@dcamp](https://forum.inductiveautomation.com/u/dcamp)\ **Post date:** [December 19, 2017, 8:21pm UTC](https://forum.inductiveautomation.com/t/ignition-as-modbus-slave-or-write/16356/3 "2017-12-19T20:21:13Z")
Can the data that Ignition is reading, be published as “MQTT” data? If so “Open Automation Software” probably would have a driver for your PLC that could subscribe to an MQTT Broker. Just a thought.