Hi Jan,

It should be easy to duplicate my results:

1. Set the receive display mode to HEX.
2. Set the baud rate to 1200 baud or higher.
3. Turn on the logging feature.
4. Send continuous data from some other computer.
5. Let it run for a little while.
6. Stop sending data from the other computer.
7. Wait for the display to stop updating.
8. Close the log.

When I do this, there are two indications that something is wrong:

1. There is data missing from the log.
2. When you stop sending the data from the other computer, the Terminal display continues to update for a long time. From this, I am guessing that it is buffering the input data somehow, and has gotten quite far behind in processing it.

If you set the receive display mode to ASCII, the problem does only happen with the higher baud rates. I haven't experimented with this very much, although I was using it that way when I first discovered the problem. The other thing I noticed was that if you set the Rx Clear to, say, 27 (1Bh, or ESC) while in ASCII mode, the log will often be missing characters immediately after an ESC arrives in the input stream. This seems like the program gets so busy clearing the screen that it misses some of the input data. As far as I can tell, the RxClear doesn't have any effect when you are in HEX mode, but I may be wrong about that.

I have made email contact with the author of the program, and he is aware of the problem. I couldn't tell if he has plans to fix it or not.

-- Russ