# Question about tcp driver

**URL:** <https://forum.inductiveautomation.com/t/question-about-tcp-driver/10865>\
**Category:** Ignition\
**Created:** [December 2, 2015, 11:20pm UTC](https://forum.inductiveautomation.com/t/question-about-tcp-driver/10865 "2015-12-02T23:20:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![TLaroche](https://avatars.discourse-cdn.com/v4/letter/t/85f322/32.png) [@TLaroche](https://forum.inductiveautomation.com/u/TLaroche)\
**Post date:** [December 2, 2015, 11:20pm UTC](https://forum.inductiveautomation.com/t/question-about-tcp-driver/10865/1 "2015-12-02T23:20:08Z")

</div>

Hello,  
We set up a connection with a TCP scale using character based messages.  
The message delimiter is 'LGM ’ (minus the single quotes.) The problem starts when setting up the delimiter as there is a space after the M. This works fine until an operator clicks to manually enter a weight. (normally this is because they forgot to weigh a coil at the current station.) After the manual entry the delimiter loses the ‘space’ character and the tcp read stops working.  
Is there a way to hard code a space into the delimiter field. Something that would look like this in python,maybe?  
str1 = “LGM”  
str2 =" "  
str3 = str1+str2

Thanks,  
Todd

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [December 3, 2015, 12:44pm UTC](https://forum.inductiveautomation.com/t/question-about-tcp-driver/10865/2 "2015-12-03T12:44:12Z")

</div>

At first blush I’d say no, but could you pad a space at the front of the manually entered weight?
