🚀 go-pugleaf

First, I like to thank both of you, for helping me out.

Second, I believe that both of you are right in your asumptions to a degree.
The reason
I say to a degree, is because I have not shown how I am setting the port and
ReadTimeIntervals.

I am sorry for that? Is like showing people bits of a puzzle and not the
whole picture!!

I am very hesitant in getting rid of ClearCommError(), I think it is a nice
function, because
it prevents having to do reads if there is nothing to read?
> Then that suggests your code really is not set up properly, if it is
taking
> up to 10 seconds to get that response.  I am still of the opinion that you
> need to get rid of ClearCommError() altogether, for the purpose of polling
> thequeue status anyway.  If the code still runs slowly after removing it,
> then something else is still messed up in your remaining code.  My guess
> would be that either 1) you did not actually configure the baud rate
> correctly in your code, or 2) you did not set up the timeouts properly
when
> you opened the serial port.  But I cannot say for sure, because you never
> showed any of that code yet.


> You are not using overlaped I/O properly to begin with, because you are
> relying on your queue status and not the overlapped status.  For that
> matter, since your code is processing in a serialized manner anyway, your
> Read() method can't return until the reading actually finsihes, so why are
> you using overlapped I/O at all?  It is not gaining you anythig in this
> situation, so you could just remove it altogether and let ReadFile()
operate
> synchronously instead.

I believe your absolutely correct on this, I have overlaped I/O, but why
should I use it
if I have another mean of coming out and prevent that my application from
hanging.


In addition, and please correct me if I am wrong, but in my timeout

// Set a safety timeout
dwRead_Time_Out = GetTickCount() + (iExpected*2);

(iExpected*2) is a millisecond count I am adding to GetTickCount(), because
if not
this means what I am thinking is happening, it is not really happening.

Thank you,
Neil P.