# Help on TCP Driver Device

**URL:** <https://forum.inductiveautomation.com/t/help-on-tcp-driver-device/22139>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [January 26, 2019, 9:16am UTC](https://forum.inductiveautomation.com/t/help-on-tcp-driver-device/22139 "2019-01-26T09:16:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![c.bertulli](https://avatars.discourse-cdn.com/v4/letter/c/f19dbf/32.png) [@c.bertulli](https://forum.inductiveautomation.com/u/c.bertulli)\
**Post date:** [January 26, 2019, 9:16am UTC](https://forum.inductiveautomation.com/t/help-on-tcp-driver-device/22139/1 "2019-01-26T09:16:51Z")

</div>

Hi All,

I have a QRCode maker device that “prints” out the QRCode via the serial port (F.E the code is GA0729830G 90101-18 ). Then I have another device that takes the “message” from the serial port and share it over the internet ( Wi-FI ). Everything is working perfectly.  
Now I want to use the “message” inside Ignition, so I’ve created a “TCP Driver Device” to get the message. The device is connected. My issue consists that I don’t receive the message correctly:

**Packet Based:** I don’t receive the message at all or only some characters  
**Character Based:** There is no “Final character” to check, I’ve tried anyway with “ **-** ” and it’s working correctly, the message I receive is “GA0729830G 90101” so, without the **-18** finale, but I need the full message.  
**Fixed Size:** The code can have 19 characters ( like this one ) or 18 or 20 etc… so this option will not work for me ( I’ve tried anyway and even this one is working correctly but, as I mentioned, the characters can change)

I don’t understand much the other parameters, **Field Count** and **Field Delimiter**.

Any help on this?

---

<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:** [January 26, 2019, 1:17pm UTC](https://forum.inductiveautomation.com/t/help-on-tcp-driver-device/22139/2 "2019-01-26T13:17:51Z")

</div>

Can you modify what the 2nd device sends so either:

1. it pads shorter messages to the same length
2. it sends UDP packets instead, which would allow you to use the UDP driver + packet based

---

<div class="post-metadata">

**Author:** ![c.bertulli](https://avatars.discourse-cdn.com/v4/letter/c/f19dbf/32.png) [@c.bertulli](https://forum.inductiveautomation.com/u/c.bertulli)\
**Post date:** [January 26, 2019, 1:21pm UTC](https://forum.inductiveautomation.com/t/help-on-tcp-driver-device/22139/3 "2019-01-26T13:21:42Z")

</div>

Well, I just found out the solution thanks to you 👍 ( in an older post [TCP Driver](http://forum.inductiveautomation.com/t/tcp-driver/2555/2?u=c.bertulli))  
I’ve set up the configuration like the following:

\*\* **Character Based** with a `\r Carriage-return` as a **Message Delimiter**

---

<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:** [January 26, 2019, 1:23pm UTC](https://forum.inductiveautomation.com/t/help-on-tcp-driver-device/22139/4 "2019-01-26T13:23:48Z")

</div>

Ah, that’s even better than my other 2 suggestions.