# TCP UDP module

**URL:** <https://forum.inductiveautomation.com/t/tcp-udp-module/4112>\
**Category:** General Discussion\
**Created:** [March 7, 2012, 2:14pm UTC](https://forum.inductiveautomation.com/t/tcp-udp-module/4112 "2012-03-07T14:14:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![SamJaimes](https://avatars.discourse-cdn.com/v4/letter/s/a6a055/32.png) [@SamJaimes](https://forum.inductiveautomation.com/u/SamJaimes)\
**Post date:** [March 7, 2012, 2:14pm UTC](https://forum.inductiveautomation.com/t/tcp-udp-module/4112/1 "2012-03-07T14:14:49Z")

</div>

Hello!

I have been asked about the UDP and TCP Drivers-module. What difference there is over the Modbus module? ![:scratch:](https://us1.discourse-cdn.com/inductiveautomation/original/1X/76d1620bec252bfac07050c889ff5a91dc8a9c25.gif ":scratch:")

---

<div class="post-metadata">

**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:** [March 7, 2012, 3:25pm UTC](https://forum.inductiveautomation.com/t/tcp-udp-module/4112/2 "2012-03-07T15:25:05Z")

</div>

There’s a huge difference. The only thing they have in common is that they happen to use TCP, just like any other ethernet driver.

The TCP/UDP module does not implement any protocol. They are meant to connect to devices like barcode scanners, which upon receiving a connection, simply stream data back over the connection as it becomes available. You setup some simple options on what size or character constitutes a message barrier and a field, and that’s it.