Someone have an explanation?

I have an MSComm control on my dialog. It has the following settings.

RTSThreshold=1
InputLength=1
115200,n,8,1
Buffer=(Large enough, like 1024)


Anyway, I have something sending HEX data to the port.
Comm event fires, everything is good. The data being sent looks like
10 02 02 00 00 01 05 89 8B 86 10 03

I put a breakpoint in the loop retrieving the bytes, from the first 10 through the 05 is fine.......89 becomes 2030, 8B =2039, and 86 = 2020....

Then the trailing chars come in normally. Why are those higher bytes coming through wrong???

Have you checked the parity?

Parity is off,

115200,n,8,1 <-- n=no parity
sender is also using no parity

I had the problems you mention when the parity, data bit and stop bit where different. Have you tried receiving the data with some other application?

Yes, data comes through normally everywhere except that MSComm control.