Re: Serial (rs232 etc.) to IP
- From: Paul Keinanen <keinanen@xxxxxx>
- Date: Wed, 26 Oct 2005 22:25:05 +0300
On 26 Oct 2005 10:57:55 -0700, cs_posting@xxxxxxxxxxx wrote:
>> ..and by doing this also ruin the serial line throughput when a half
>> duplex protocol is used with short message frames. Some converters
>> wait 10-100 ms after the last serial character received, before the
>> (TCP or UDP) IP-frame is sent. For instance at 115200 bit/s, this
>> corresponds to 100-1000 character times.
>
>This is a valid concern, however there's a bit of a problem with single
>character packets when many common embedded TCP devices try to talk to
>common desktop operating systems.
>
>TCP requires that you hang onto all outgoing data until it has been
>acknowledged, because if it's not acknowledged you will have to resend
>it. Most embedded implementations handle this by sending a packet, and
>then being unable to send another until the first has been
>acknowledged. The Windows TCP stack often takes as much as 200 ms to
>acknowledge a packet when only one is outstanding, so single character
>packets can be slowed down to the rate of only five per second!
If you are using a protocol that was initially written for serial line
communication with normal CRC checks and timeout controls, why bother
with TCP, just use simple UDP. If the UDP frame is lost, let the
original serial line protocol timeout mechanism handle any missing
data.
Paul
.
- Follow-Ups:
- Re: Serial (rs232 etc.) to IP
- From: Ignacio G.T.
- Re: Serial (rs232 etc.) to IP
- From: cs_posting
- Re: Serial (rs232 etc.) to IP
- References:
- Re: Serial (rs232 etc.) to IP
- From: Frieder Ferlemann
- Re: Serial (rs232 etc.) to IP
- From: packer44
- Re: Serial (rs232 etc.) to IP
- From: Paul Keinanen
- Re: Serial (rs232 etc.) to IP
- Prev by Date: Re: IDEA: ARM stamp SBC ?
- Next by Date: Re: IP addresses for embedded device with ethernet
- Previous by thread: Re: Serial (rs232 etc.) to IP
- Next by thread: Re: Serial (rs232 etc.) to IP
- Index(es):
Relevant Pages
|