Hi Steve,

>I determined that I had a timer running which was actually checking the inbuffercount and placing a message on the screen if not zero. However, this appears to reset the buffers. Setting a trace on the outbuffercount appears to reset the buffer as well. Unfortunately, I have found no way to see if the data is staying in the output buffer or is being reset because checking the buffer size appears to clear it.
>

Interesting observation. You might try increasing your .SThreshold value so you aren't hitting that event so heavily. Also, how much processing are you doing there? A DOEVENTS might be in order...

>In addition, the oncomm event appears to be firing after some interval with the status of "1" when there is no connection to the scale and handshaking is on. My impression (or misguided wish) is that the oncomm should fire either after a send or change in status is detected. Otherwise, it should wait, buffer ready, until something is ready at the other end.
>

Are you reading muliple scales, manually disconnecting or switching cables?