🚀 go-pugleaf

> As next step i tried using WaitCommEvent and its relatives 
> (using EV_TXEMPTY)
> causing the result, that the process returns in the middle of 
> the transmittion
> process and not at its end as described:"EV_TXEMPTY The last 
> character in the
> output buffer was sent."

The behaviour is correct. The output buffer IS NOT the output 
register. You can have, for example, a 16-byte output buffer. 
Furthermore, a byte requires time to be "serialized" once it is 
read from the register. So you can't base the control on that 
event, unless you set the output buffer length to 1 and as soon 
as you receive the event, wait for the last byte to be shifted 
out and then drop RTS. But not always this trick works properly.

> So I not able to control the RTS line in a suitable way.

Have you evaluated the possibility of using an automatic 232/485 
converter?

> Does anybody has a solution for this problem.

It's one of the most difficult issues in serial communications I 
ever faced and I'm still looking for a good software solutions 
as well.

Steve.