# Slow data reception

**URL:** <https://forums.digi.com/t/slow-data-reception/3946>\
**Category:** NET+OS\
**Tags:** tcp\
**Created:** [May 23, 2006, 3:21pm UTC](https://forums.digi.com/t/slow-data-reception/3946 "2006-05-23T15:21:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jorge\_schuler](https://avatars.discourse-cdn.com/v4/letter/j/e0b2c6/32.png) [@jorge\_schuler](https://forums.digi.com/u/jorge_schuler)\
**Post date:** [May 23, 2006, 3:21pm UTC](https://forums.digi.com/t/slow-data-reception/3946/1 "2006-05-23T15:21:22Z")

</div>

Hi all  
We use digi to connect a serial device through TCP/IP, using a Borland C++ DLL. When we send commands to this device it answers serially, one byte at a time. Obviously this is very slow if we also receive the data one byte at a time over tcp/ip. So i’m changing this by raising the recv buffer size.  
In my test i have no problems with the “short” answers. But when the ammount of data is larger (~60 bytes) the communication acts very strange. First of all i receive gargabe. Secondly, after sniffing with ethereal i realize that digi sends the data, complete at first. Then keeps sending fractions of the same data. So when i send another command to the serial device, althought it answers i keep receiving fragments of the 60 bytes.  
Any ideas? should i force my app to keep receiving data after i receive the needed data, to make digi stop sending those chunks?

Thanks in advance