HLT vbo vs csv export

[blkcaymans]

I've been doing some HLT data analysis in Circuit Tools using the export .vbo functionality. I want to add a couple more data columns to the .vbo file from the HLT raw data such as RPM and Throttle but when I compare the .csv export and the .vbo export the rows of data for the same lap are substantially different... One example lap has 421 rows of data in the .csv but the .vbo has 1128. Anyone know why?

Thanks

[Harry]

The CSV export includes all data while VBO comes with a selection only. The reason the number of rows is bigger for VBO is it did not work using lower GPS update rates (neither does it work with no satellite information available). So LapTimer adds interpolated data to make CT2 work...

Harry

[blkcaymans]

Thanks Harry, that makes sense! Is there are formula you are using for the interpolation or a set number of interpolated values between each actual value? With 421 rows in my .csv I would have thought the .vbo would have 842 or 1263... The 1128 number doesn't make sense.

Thanks

[Harry]

LapTimer interpolates VBO to 10 Hz independent of the input (1 Hz, 5 Hz, 10Hz, 20 Hz). So for this exports, nearly no fix will match the original fixes. As CT expects logger output, LapTimer mimics something like that by not only joining lap data but adding some extrapolation to the beginning and the end in addition. Otherwise, CT will not detect the first and the last lap. This export is probably the most complex LapTimer features... Interpolation is done like all LapTimer interpolations work - using a linear approach taking the speed development between two fixes into account.

- Harry

[blkcaymans]

Thanks Harry! I'll add a feature request to export the OBD data to .vbo when it's available.