Re: Serial Port CE_OVERRUN errors
- From: Hans-Peter Diettrich <DrDiettrich@xxxxxxxxxxx>
- Date: Mon, 06 Feb 2006 21:46:07 +0100
Paul E. Schoen schrieb:
Since I am sending the data at exactly 4800 characters per second (in
pairs), speeding up the baud rate just puts more space between the pairs,
hopefully to allow the USART to do its buffering before the next start bit
occurs.
The UART has enough time to do the internal buffering, for any supported baudrate. Problems can arise only from a slow response of the next stage, the system that retrieves the data from the receiver.
I plan to recommend that my customers use only WinXP and a 1 GHz or better
processor, which will not impose any hardship.
I wonder how we could perform data acquisition in 1988, with 9600 Baud, with the first portable 8088 PC, running at 0.004 GHz, with online graphics of the received data, and writing to diskettes. We only had to use a RAM disk later, because diskette operation was unreliable in a moving car (Porsche ;-).
IMO there's something wrong with your data acquisition machinery or software. Imagine what amount of information comes in from an Internet connection, and can be handled even by older systems.
DoDi
.
- Follow-Ups:
- Re: Serial Port CE_OVERRUN errors
- From: Maarten Wiltink
- Re: Serial Port CE_OVERRUN errors
- From: Paul E. Schoen
- Re: Serial Port CE_OVERRUN errors
- References:
- Serial Port CE_OVERRUN errors
- From: Paul E. Schoen
- Re: Serial Port CE_OVERRUN errors
- From: Jamie
- Re: Serial Port CE_OVERRUN errors
- From: Paul E. Schoen
- Serial Port CE_OVERRUN errors
- Prev by Date: Re: DCU file ownership
- Next by Date: Re: Question about showing hints in status bar
- Previous by thread: Re: Serial Port CE_OVERRUN errors
- Next by thread: Re: Serial Port CE_OVERRUN errors
- Index(es):