Diez B. Roggisch wrote:
if you have the chance, try attach a machine with legacy rs232
port, and see if the errors still remain.
Additionally, what kind of buffers does your device have? I'm using
pyserial to control a very sensitive device with nuttily
implemented buffering strategy. It has
Diez B. Roggisch wrote:
RS232 is unfortunately as bad as a protocol as it can get. I've used
it for communication with a microcontroller for just a few bytes every
second. And it failed miserably, so I needed to implement a protocol on
top of it.
We normally do this anyway, except for stuff
On Sunday 30 March 2008 12:19:58 Bjoern Schliessmann wrote:
Diez B. Roggisch wrote:
if you have the chance, try attach a machine with legacy rs232
port, and see if the errors still remain.
Additionally, what kind of buffers does your device have? I'm using
pyserial to control a very
On Sat, 29 Mar 2008 13:14:46 +0200, Hendrik van Rooyen wrote:
Hi,
I have been doing some tests on a device that we are thinking of
incorporating into a product, and I have seen that reception on a serial
port at 115200 baud over about six metres of RS-232 cable makes
mistakes, to the order
Hi,
I have been doing some tests on a device that
we are thinking of incorporating into a product,
and I have seen that reception on a serial port
at 115200 baud over about six metres of RS-232
cable makes mistakes, to the order of 125 lines
with errors in them out of approximately 18.4
million
Hendrik van Rooyen schrieb:
Hi,
I have been doing some tests on a device that
we are thinking of incorporating into a product,
and I have seen that reception on a serial port
at 115200 baud over about six metres of RS-232
cable makes mistakes, to the order of 125 lines
with errors in
On Mar 29, 4:26 pm, Diez B. Roggisch [EMAIL PROTECTED] wrote:
Hendrik van Rooyen schrieb:
Hi,
I have been doing some tests on a device that
we are thinking of incorporating into a product,
and I have seen that reception on a serial port
at 115200 baud over about six metres of
