[MidlifeCrisis]

I could not find any previous discussion of this issue. I have noticed two problematic issues with the time stamps in ST logs when logging as fast as possible.

The first is that the initial time stamp in any second is missing a '0' character after the decimal portion of the second value. So, for example, where the order of records in the log is correct, the time stamp itself is wrong for the first field at the beginning of each second, like so:

Time Stamp A/F Ratio
19:18:40.993 14.70
19:18:41.93 14.70
19:18:41.193 14.70

and so on.

The '0' character that should precede the '93' in the middle record is missing. This is not a problem until you open the log in Excell and do some operation that sorts on the Time Stamp - it makes a mess of the data. Look at the log in this post to see a perfect example - examine the timestamps closely Stock boost sensor high limit?

The second problem is that the time stamp format does not import gracefully into Excell natively. So, when you double click on a .csv log file and Excell opens it, the time stamps all get converted in a way that drops the hour value and rounds the decimal seconds value to a tenth second resolution. This creates duplicate time stamps in many cases. Again, this is not a problem initially, because the rows are in the right order UNTIL the first time you sort based on time stamp after some other data manipulation - something I do all the time for intake calibration analysis where I sort on MAF Voltage first and Time Stamp second to see what the latest A/F Learned is for each MAF Voltage.

Anyone else seen this? Is there a fix or work around?

- Bruce

[wdb]

I can't help you with the missing zero but I can give you a time format in Excel that should fix any problems with losing precision. Select the entire column containing the timestamps, then click Format, Cells. Select "Custom" and enter the following exactly as shown: h:mm:ss.000

[MidlifeCrisis]

Excellent, it worked to cure the Excel problem. Thanks!

I did some logs this morning at the rate of 5 per second instead of 10 per second and observed that the problem still exists for any value that would be properly formatted as hh:mm:ss.0xx. That initial zero after the decimal point is still missing.

Temporary cure: Create a new column that is purely an increasing number sequence right after the log is opened and sort on that instead of the time stamp.