Hi TI,
We still have problem with bit unreliable USB connection. Sometimes, sync pattern is not where it should be (No SYNC pattern error). How reliable the COM through the USB is?
Even more often, the checksum of the packet header is wrong. Pasting one case of:
* Example of correct header captured (CS=0):
rxHeader_UINT8 (2, 1, 4, 3, 6, 5, 8, 7, 2, 1, 1, 3, 66, 22, 10, 0, 182, 173, 145, 104, 52, 0, 0, 0, 12, 112, 13, 0, 0, 0, 0, 0, 78, 0, 0, 0, 130, 78, 0, 0, 2, 0, 0, 0, 86, 2, 0, 0, 0, 0, 222, 253)
rxHeader_parsed (506660481457717506, 50397442, 661058, 1754377654, 52, 880652, 0, 78, 20098, 2, 598, 0, 64990)
* Incorrect checksum header (CS=47727):
rxHeader_UINT8 (2, 1, 4, 3, 6, 5, 8, 7, 2, 1, 1, 3, 66, 22, 10, 0, 168, 74, 251, 162, 52, 0, 0, 0, 110, 112, 13, 0, 0, 0, 0, 0, 78, 0, 0, 0, 132, 78, 0, 0, 2, 0, 0, 0, 86, 2, 0, 0, 0, 0, 31, 2)
rxHeader_parsed (506660481457717506, 50397442, 661058, 2734377640, 52, 880750, 0, 78, 20100, 2, 598, 0, 543)
As you can see both looks similar and seems OK to me. Can just some bits be flipped? Isn't there any automatic mechanism used for correction of data sent over serial line?
Thank you, Lukas
