🚀 go-pugleaf

"MWP" <mwp@overclockers.com.au> ha scritto nel messaggio
news:3ec26741$1@newsgroups.borland.com...
>
> The device at the other end is a LCD module which doesnt have any kind of
software/hardware flow control.
>

Confirm Ed's first guess: check rather the LCD and your software than the
pc. You do nothing special with the com port, so if that wouldn't work,
Windows would have to write off the serial interface as such.

What kind of LCD are you using? I have never heard about one with an asynch
serial interface. You probably have a third-party add-on controler board,
and these are all but reliable. And probably you are not just reading but
have to write a bytes to request reading. Are you sure you are syncronized
between writes & reads? The 250ms read cycles, is at a request by LCD specs
or is that just what you have seen as result?

Anyhow you should open the port in async mode, set its (internal) buffers
and both write & read having set the timeout structure.
Then every supposed write/read sesions should:
- clear Tx buffer and Rx buffer
- write request in one go (with timeout), not char by char as the LCD could
timeout.
- check tx-buffer empty flag,
- read n characters with timeouts.

Sorry I do not remember out of mind the exact structures and api calls for
that.

Rgds, Martin