[glamprecht]

I think you're quite smart in figuring out from the data that you are missing packets.

If you send me your code I'll have a look at how you communicate with the CAN driver of your USB/CAN dongle. At the office we just did the same, because we are running 500k fully packed with data. I had quite a fight with the developer today that wrote code without putting traps in to detect buffer overflow, CAN error state, driver state and interrupt failure.

I can probably help you a bit with the code. I have done Freescale and Fujitsu CAN implementations in the past. On the PC side using P-CAN, Vector and RM-bluetooth CAN At some stage even stream video over CAN.

What I'm trying to say is that making sure from first principles that your driver/interface to the CAN box/DLL should be solid or robust from a coding perspective, otherwise you will always have some kind of problem you can't explain down the line.