Quote Originally Posted by swingtan View Post
Lennart and lakingslayer, the "weird frames or "logs full of notes" sounds like the problem I'm having as well. I've found that repeated tries at opening the file eventually seems to get a clean read and displays "sane" data. I have no idea if the data is actually correct though.

The way the logs look when they open in "corrupted" form reminds me of the first BBL logs I tried on the E38 when the V2 would cause I/O problems between the ECM and other modules, bringing up dash alerts and dropping corrupted data into the log file. This was back around the start of this year. When opening these files in ScanTool, I'd get the same weir looking data displayed as I get now. It's almost like the BBL files don't have an <EOF> character and ScanTool ends up with random data at the end of the log.

Simon.
There appears to be a bug in the frame count value. The frame count value is written into the file as a 16 bit value ("%d") but should be written as a 32 bit value ("%ld"). That will cause problems if the log file is longer than 65535 frames. A fix is being made now.

If any of you have log files of less than 65535 frames that are showing corrupt frames, please send them to me at [email protected].


Regards
Paul