# Modbus tcp comunication - ignition

**URL:** <https://forum.inductiveautomation.com/t/modbus-tcp-comunication-ignition/39149>\
**Category:** Ignition\
**Created:** [September 28, 2020, 9:56pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-comunication-ignition/39149 "2020-09-28T21:56:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rcepeda](https://avatars.discourse-cdn.com/v4/letter/r/6a8cbe/32.png) [@rcepeda](https://forum.inductiveautomation.com/u/rcepeda)\
**Post date:** [September 28, 2020, 9:56pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-comunication-ignition/39149/1 "2020-09-28T21:56:52Z")

</div>

Hi,  
I’m trying to connect a Modbus TCP device to Ignition V8.012 using Modbus TCP Device Connection, when I create the connection in the gateway its status is Connected but when I create a Tag in my project and setting the communication configuration the comunication´s status in the gateway change to Disconnected and Connected every second, so my Tag´s value is Bad.

I attached a screen shot showing the error.

 ![ignitionError](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/e/fea9be8838b95ca88504536d98a144dc3288dac4.png)

---

<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 29, 2020, 12:43am UTC](https://forum.inductiveautomation.com/t/modbus-tcp-comunication-ignition/39149/2 "2020-09-29T00:43:47Z")

</div>

“End of stream reached”. That means the device is hanging up on you. This can happen if you are using the wrong protocol (should this have been Modbus RTU over TCP?) or an unsupported command is being sent by Ignition. What brand and model device is this?