🚀 go-pugleaf

In article <3603@naucse.cse.nau.edu> rrw@naucse.cse.nau.edu (Robert Wier) writes:
> Now, working on the same project I've run into a snag using the 
> COM port.  We have a situation where we don't know when the 
> data will appear - it can be anywhere from 100 ms to 11 seconds
> after the previous carriage return.
>
> The problem we are having (my students are currently using 
> Quick-C) is that when you go out to read a character and there
> isn't one there yet, the port seems to "time out" in 1.5 seconds
> or so.  I can't find any way to defeat this, although I certainly
> see why in most circumstances it would be useful.
>
> I know it CAN be done, because Kermit does it.  The big K just
> sits waiting patiently for something to arrive and display it on
> the screen.
>
> Does anyone know how to do this?  Does it require going directly
> to the UART and bypassing the built in routines?  Or is there 
> something actualy in the hardware in the nature of a switch
> which has to be reset?
>

You can do this by first checking if there is a character to fetch and after
that fetch the character!

And how to check if there is somthing to fetch is simple, just check the com
ports status register!

// Gunnar


===============================================================================
				Gunnar Dahlstrom
			Chalmers University of Technology
			    Div. Building Technology
			   412 96 Gothenburg,  Sweden
			E-Mail:  dahlstr@hus.chalmers.se
===============================================================================