🚀 go-pugleaf

Good Morning!
I've read Mr. Moeller's and Mr. Mulroy's advise, and wish to add some
diagnostic advise.
1) you are having a problem with code locking up after calling it a few
time.
2) you are sending data to the serial port.
3) programs are using Writefile to send data to the COMM port all the time
without messing up.

alright, now lets try to figure out what's going wrong.
Try running the program several times, but keep tract of how many bytes
you've written to the port.
using just a rough guess,
40times/sec * 20bytes = 800bytes/sec
19200bit/sec / 11bits/byte xmitted = 1745 bytes / sec.
okay, so you shouldn't be overrunning the buffer.
are the 40/times a second evenly spaced? what's driving this?

You didn't say, but are you running any of this in multiple threads?
you might be having a thread problem and not a COMM problem.

when the writefile doesn't return, what does your LCD do?

while you are doing things in your program with the comm port, what else are
you doing?
did you try creating a disk log of the info that you are sending to the comm
port?
maybe the data is buggering up
do you test the result of bytes written?

I know it's frustrating debugging code when it stops at a place you can't
examine,
but hang in there, there are techniques to get around that!

have Fun
Stephan


"MWP" <mwp@overclockers.com.au> wrote in message
news:3ec25f43$1@newsgroups.borland.com...

Hi all...

Im am doing the following simple line that is running about 40 times a
second:
WriteFile(ComHandle, Block, Length, &BytesWritten, NULL);

ComHandle is pointing to a COM port opened at 19200.
Length is never more than 20 (verified).

It will work for a random amount of time then, WriteFile gets called but
doesnt return... ever.

Anyone know what the problem could be?