Enhanced VBO export

Request and discussion on new / to change features
ereynold60
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 79
Joined: Fri Mar 13, 2015 9:31 pm

Enhanced VBO export

Post by ereynold60 » Mon May 23, 2016 10:26 pm

The current VBO export works fine with Circuit Tools, but OBD wheel speed is missing in the exported data columns. RPM and Throttle are exported and with columns labeled as EngineSpeed and GasPedalPosition, respectively. It would seem fairly easy to also export WheelSpeed using OBD data. GPS data is not that accurate for slow speed hairpins or in the last stages of a high-G braking zone, even with 10Hz GPS... (yes I'm talking about a 2-3MPH difference, but it does matter) OBD data is more reliable.

These links below also show how to manually link an external video to be viewed in Circuit Tools. It would be great to have LapTimer provide a VBO+video export option... (actually just the VBO file, but with the file configured with the right fields):

http://www.racechrono.com/vanilla/discu ... -vbo-files
VBO File Reverse Engineering for External Video.doc: https://drive.google.com/file/d/0Bw0_gq ... sp=sharing

It would be great if LapTimer created a VBO file with an adjustable "sync" setting, as some my videos required a 2.3 second delay. I found that 100 milliseconds for each line in the GPS trace worked pretty well, although Laptimer could easily compute the sync point for each GPS point from timestamps.

As for video file names, the user would need to rename his video file to the same name as the VBO file and add "0001.MP4"

In my view, this option would mainly (only) apply to full session exports.
Last edited by ereynold60 on Mon May 23, 2016 10:31 pm, edited 1 time in total.
User avatar
Harry
Site Admin
Site Admin
Posts: 9444
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: Enhanced VBO export

Post by Harry » Mon May 23, 2016 10:31 pm

Hi,

I have official information on how to export videos with VBO, it is just about time available and other requests. It will be added sometime. ;-) For additional OBD information: other than GPS and acceleration data derived from it, Racelogic has no common scheme for engine channels. That's the reason I have added only those available from all Racelogic loggers I got my hands on. So EngineSpeed and GasPedalPosition are kind of an ad hoc standard while everything else is named different by installation. I could add my own conventions, but again, there is so much else to do. :-)

- Harry
Image Image Image Image
gplracerx
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 836
Joined: Thu May 03, 2012 5:26 am
Location: Kingsport, TN USA

Re: Enhanced VBO export

Post by gplracerx » Tue May 24, 2016 1:49 pm

My experience is the opposite. Wheel speed is much noisier and less reliable than GPS speed and, because it doesn't update as fast as the GPS, it suffers from artefacts caused by the extrapolation and interpolation routines in HLT. You could probably get better accuracy and precision if you combined the GPS data with the accelerometer data by integrating the linear acceleration to get speed. You can calibrate the position of the device by using integrated yaw rate data to get course and comparing that data with the GPS course data and the integrated accelerometer speed with the GPS speed. You can use Solver in Excel to calculate lateral and lineal accelerometer offsets and a yaw angle between the device and the vehicle frames. There's still going to be drift in the integrated accelerometer data because you're integrating the signal noise and creating a random walk. But it's not all that bad.

And Circuit Tools doesn't use the speed data in the .vbo file. It calculates speed and acceleration from the GPS position data only.
ereynold60
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 79
Joined: Fri Mar 13, 2015 9:31 pm

Re: Enhanced VBO export

Post by ereynold60 » Wed May 25, 2016 3:52 pm

gplracerx wrote:My experience is the opposite. Wheel speed is much noisier and less reliable than GPS speed and, because it doesn't update as fast as the GPS, it suffers from artefacts caused by the extrapolation and interpolation routines in HLT. (SNIP)

And Circuit Tools doesn't use the speed data in the .vbo file. It calculates speed and acceleration from the GPS position data only.
I agree that OBD can be very noisy, unless you calibrate the OBD delay, per my post here: viewtopic.php?f=8&t=3731#p19333. Once this is done you get quite accurate speed in slow hairpins and at the end of hard braking zones; in these areas I find GPS to be an approximation.

Agree that CT calculates its own speeds using GPS position and timing only.
ereynold60
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 79
Joined: Fri Mar 13, 2015 9:31 pm

Re: Enhanced VBO export

Post by ereynold60 » Thu May 26, 2016 2:03 am

After bending several spreadsheets around... I successfully created a VBO file to integrate video and OBD wheel speed in MPH.. This required extract OBD wheel speed from a CSV export, matching up timestamps in the VBO file and then inserting and reformatting the VBO file as 'text' with spaces as separators... anyway below is a code extract from the VBO file.

I understand the desire to do VBO files in a standard way, but it doesn't appear to matter. The VBO data is a stream of GPD locations along with relevant data at the point. It doesn't matter what you label the columns; all that does is give that data channel a name. It graphs very nicely as other channels.

Image

https://drive.google.com/open?id=0ByvT9 ... HUzUEdBNGM

Code: Select all

File created on 17/05/2016 at 12:32:22
[header]
satellites
time
latitude
longitude
velocity kmh
heading
height
long accel g
lat accel g
GasPedalPosition
EngineSpeed
WheelSpeed mph
avifileindex
avisynctime

[comments]
Generated by LapTimer v20.0.10
(c) 2006-2015 Harald Schlangmann

[session data]
laps 10
name COTA
driver ESR
vehicle Porsche Cayman S (981)

[laptiming]
Start   +5858.3919 +1807.9124 +5858.4091 +1807.9240 Start / Finish
Split   +5858.1561 +1808.1908 +5858.1683 +1808.2065 Split 2
Split   +5857.9758 +1808.1661 +5857.9960 +1808.1590 Split 1

[avi]
20160508_COTA_S2_
MP4

[column names]
sats time lat long velocity heading height longacc latacc GasPedalPosition EngineSpeed WheelSpeed avifileindex avisynctime

[data]

013 160028.66 +1807.91406000 +05858.37724000 047.000 128.00 +00149.30 +0.13 +0.00 074 03077 29.204446 0001 000000000
013 160028.76 +1807.91366000 +05858.37658000 047.400 128.00 +00149.30 +0.13 +0.00 074 03077 29.204446 0001 000000100
013 160028.86 +1807.91320000 +05858.37594000 047.900 128.00 +00149.30 +0.13 +0.00 075 03101 29.825817 0001 000000200
013 160028.96 +1807.91276000 +05858.37528000 048.100 127.70 +00149.30 +0.14 +0.01 077 03119 29.825817 0001 000000300
013 160029.06 +1807.91230000 +05858.37458000 048.100 128.50 +00149.30 +0.14 +0.02 077 03119 29.825817 0001 000000400
013 160029.16 +1807.91186000 +05858.37394000 048.300 128.20 +00149.30 +0.14 +0.02 077 03119 29.825817 0001 000000500
013 160029.26 +1807.91140000 +05858.37328000 048.500 128.00 +00149.30 +0.13 +0.02 053 03150 29.825817 0001 000000600
013 160029.36 +1807.91096000 +05858.37258000 049.200 128.20 +00149.30 +0.12 +0.00 043 03171 30.447188 0001 000000700
013 160029.46 +1807.91050000 +05858.37188000 049.600 128.00 +00149.30 +0.11 -0.01 048 03170 30.447188 0001 000000800
013 160029.56 +1807.91000000 +05858.37124000 049.600 128.10 +00149.30 +0.10 -0.02 048 03170 30.447188 0001 000000900
013 160029.66 +1807.90956000 +05858.37058000 049.600 128.10 +00149.20 +0.10 -0.02 068 03224 30.447188 0001 000001000
013 160029.76 +1807.90910000 +05858.36988000 049.700 128.10 +00149.20 +0.10 -0.01 082 03261 31.068559 0001 000001100
012 160029.86 +1807.90866000 +05858.36918000 050.100 128.20 +00149.20 +0.11 -0.01 082 03261 31.068559 0001 000001200
013 160029.96 +1807.90820000 +05858.36848000 050.700 128.10 +00149.20 +0.12 +0.00 092 03342 31.068559 0001 000001300
013 160030.06 +1807.90770000 +05858.36778000 051.300 128.10 +00149.20 +0.14 +0.01 100 03397 32.311302 0001 000001400
013 160030.16 +1807.90720000 +05858.36708000 051.600 128.00 +00149.20 +0.16 +0.03 100 03399 32.311302 0001 000001500
013 160030.26 +1807.90676000 +05858.36638000 051.800 127.90 +00149.20 +0.18 +0.05 097 03443 32.932673 0001 000001600
013 160030.36 +1807.90630000 +05858.36562000 053.200 128.10 +00149.20 +0.20 +0.06 094 03501 33.554044 0001 000001700
013 160030.46 +1807.90580000 +05858.36488000 054.500 128.20 +00149.10 +0.21 +0.07 093 03521 34.175415 0001 000001800
013 160030.56 +1807.90530000 +05858.36412000 055.300 128.30 +00149.10 +0.21 +0.08 097 03617 34.175415 0001 000001900
013 160030.66 +1807.90474000 +05858.36338000 056.000 128.30 +00149.10 +0.22 +0.09 100 03681 35.418158 0001 000002000
013 160030.76 +1807.90420000 +05858.36262000 056.800 128.40 +00149.10 +0.22 +0.10 100 03745 35.418158 0001 000002100
ereynold60
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 79
Joined: Fri Mar 13, 2015 9:31 pm

Re: Enhanced VBO export

Post by ereynold60 » Thu May 26, 2016 10:31 pm

Harry - I think it would be great to have an option to export all available data similar to that which comes in the CSV export. Below is a test where I have created a VBO file for Circuit Tools that includes, video, as well as OBD data for WheelSpeed, RPM, Throttle, Gear, CoolantTemp, IntakeAirTemp... Circuit Tools processes these fine; each field or "channel" is a stream of data that CT processes without any errors. Naming conventions aren't necessary other than too make the data understandable.

Perhaps a selectable or configurable VBO export dialog to select individual channels to export... or just export any data that Laptimer has available.

See screenshot and sample code from my modified VBO file below:

Image

https://drive.google.com/file/d/0ByvT9J ... sp=sharing

Code: Select all

File created on 17/05/2016 at 12:32:22
[header]
satellites
time
latitude
longitude
velocity kmh
heading
height
long accel g
lat accel g
GasPedalPosition
EngineSpeed
WheelSpeed mph
RPM
Throttle
Gear
CoolantTempF
IntakeAirTempF
avifileindex
avisynctime

[comments]
Generated by LapTimer v20.0.10
(c) 2006-2015 Harald Schlangmann
Updated by E.Reynolds with video and OBD data channels 25/5/2016

[session data]
laps 10
name COTA
driver ESR
vehicle Porsche Cayman S (981)

[laptiming]
Start   +5858.3919 +1807.9124 +5858.4091 +1807.9240 Start / Finish
Split   +5858.1561 +1808.1908 +5858.1683 +1808.2065 Split 2
Split   +5857.9758 +1808.1661 +5857.9960 +1808.1590 Split 1

[avi]
20160508_COTA_S2_
MP4

[column names]
sats time lat long velocity heading height longacc latacc GasPedalPosition EngineSpeed WheelSpeed RPM Throttle Gear CoolantTempF IntakeAirTempF avifileindex avisynctime

[data]
013 160028.66 +1807.91406000 +05858.37724000 047.000 128.00 +00149.30 +0.13 +0.00 074 03077 29.204446 3077 74 2 188.6 104 0001 000000000
013 160028.76 +1807.91366000 +05858.37658000 047.400 128.00 +00149.30 +0.13 +0.00 074 03077 29.204446 3077 74 2 188.6 104 0001 000000100
013 160028.86 +1807.91320000 +05858.37594000 047.900 128.00 +00149.30 +0.13 +0.00 075 03101 29.825817 3076 74 2 188.6 104 0001 000000200
013 160028.96 +1807.91276000 +05858.37528000 048.100 127.70 +00149.30 +0.14 +0.01 077 03119 29.825817 3119 77 2 188.6 104 0001 000000300
013 160029.06 +1807.91230000 +05858.37458000 048.100 128.50 +00149.30 +0.14 +0.02 077 03119 29.825817 3119 77 2 188.6 104 0001 000000400
013 160029.16 +1807.91186000 +05858.37394000 048.300 128.20 +00149.30 +0.14 +0.02 077 03119 29.825817 3119 77 2 188.6 104 0001 000000500
013 160029.26 +1807.91140000 +05858.37328000 048.500 128.00 +00149.30 +0.13 +0.02 053 03150 29.825817 3119 77 2 188.6 104 0001 000000600
013 160029.36 +1807.91096000 +05858.37258000 049.200 128.20 +00149.30 +0.12 +0.00 043 03171 30.447188 3172 37 2 188.6 102.2 0001 000000700
013 160029.46 +1807.91050000 +05858.37188000 049.600 128.00 +00149.30 +0.11 -0.01 048 03170 30.447188 3170 48 2 188.6 102.2 0001 000000800
013 160029.56 +1807.91000000 +05858.37124000 049.600 128.10 +00149.30 +0.10 -0.02 048 03170 30.447188 3170 48 2 188.6 102.2 0001 000000900
013 160029.66 +1807.90956000 +05858.37058000 049.600 128.10 +00149.20 +0.10 -0.02 068 03224 30.447188 3170 48 2 188.6 102.2 0001 000001000
013 160029.76 +1807.90910000 +05858.36988000 049.700 128.10 +00149.20 +0.10 -0.01 082 03261 31.068559 3261 82 2 188.6 102.2 0001 000001100
012 160029.86 +1807.90866000 +05858.36918000 050.100 128.20 +00149.20 +0.11 -0.01 082 03261 31.068559 3261 82 2 188.6 102.2 0001 000001200
013 160029.96 +1807.90820000 +05858.36848000 050.700 128.10 +00149.20 +0.12 +0.00 092 03342 31.068559 3261 82 2 188.6 102.2 0001 000001300
013 160030.06 +1807.90770000 +05858.36778000 051.300 128.10 +00149.20 +0.14 +0.01 100 03397 32.311302 3397 100 2 188.6 102.2 0001 000001400
013 160030.16 +1807.90720000 +05858.36708000 051.600 128.00 +00149.20 +0.16 +0.03 100 03399 32.311302 3397 100 2 188.6 102.2 0001 000001500
013 160030.26 +1807.90676000 +05858.36638000 051.800 127.90 +00149.20 +0.18 +0.05 097 03443 32.932673 3401 100 2 188.6 102.2 0001 000001600
013 160030.36 +1807.90630000 +05858.36562000 053.200 128.10 +00149.20 +0.20 +0.06 094 03501 33.554044 3471 95 2 188.6 102.2 0001 000001700
013 160030.46 +1807.90580000 +05858.36488000 054.500 128.20 +00149.10 +0.21 +0.07 093 03521 34.175415 3521 93 2 188.6 102.2 0001 000001800
013 160030.56 +1807.90530000 +05858.36412000 055.300 128.30 +00149.10 +0.21 +0.08 097 03617 34.175415 3521 93 2 188.6 102.2 0001 000001900
013 160030.66 +1807.90474000 +05858.36338000 056.000 128.30 +00149.10 +0.22 +0.09 100 03681 35.418158 3681 100 2 188.6 102.2 0001 000002000
013 160030.76 +1807.90420000 +05858.36262000 056.800 128.40 +00149.10 +0.22 +0.10 100 03745 35.418158 3681 100 2 188.6 102.2 0001 000002100
013 160030.86 +1807.90370000 +05858.36182000 057.600 128.30 +00149.10 +0.22 +0.11 100 03813 36.6609 3789 100 2 188.6 102.2 0001 000002200
013 160030.96 +1807.90314000 +05858.36102000 058.500 128.70 +00149.10 +0.22 +0.12 100 03829 37.282271 3829 100 2 188.6 102.2 0001 000002300
013 160031.06 +1807.90260000 +05858.36022000 059.400 128.90 +00149.10 +0.23 +0.13 100 03880 37.282271 3829 100 2 188.6 102.2 0001 000002400
013 160031.16 +1807.90204000 +05858.35942000 060.000 129.10 +00149.10 +0.22 +0.14 100 03981 37.903643 3914 100 2 188.6 102.2 0001 000002500
013 160031.26 +1807.90144000 +05858.35862000 060.900 129.30 +00149.10 +0.23 +0.15 100 04027 38.525014 4027 100 2 188.6 102.2 0001 000002600
013 160031.36 +1807.90084000 +05858.35776000 062.100 129.60 +00149.10 +0.23 +0.16 100 04027 38.525014 4027 100 2 188.6 102.2 0001 000002700
013 160031.46 +1807.90024000 +05858.35692000 062.900 129.80 +00149.10 +0.24 +0.17 100 04027 38.525014 4027 100 2 188.6 102.2 0001 000002800
013 160031.56 +1807.89964000 +05858.35606000 063.700 130.00 +00149.10 +0.24 +0.18 100 04027 38.525014 4027 100 2 188.6 102.2 0001 000002900
013 160031.66 +1807.89904000 +05858.35516000 064.800 130.20 +00149.10 +0.25 +0.18 096 04227 38.525014 4027 100 2 188.6 102.2 0001 000003000
Last edited by ereynold60 on Thu May 26, 2016 10:49 pm, edited 1 time in total.
User avatar
Harry
Site Admin
Site Admin
Posts: 9444
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: Enhanced VBO export

Post by Harry » Thu May 26, 2016 10:38 pm

Thanks for sharing. It is on the list. ;-)

- Harry
Image Image Image Image
ereynold60
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 79
Joined: Fri Mar 13, 2015 9:31 pm

Re: Enhanced VBO export

Post by ereynold60 » Thu May 26, 2016 10:53 pm

Harry wrote:Thanks for sharing. It is on the list. ;-)

- Harry
Super...Thanks Harry... I'm looking forward to it.
mastaflow
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 1
Joined: Wed Aug 17, 2016 7:46 am

Re: Enhanced VBO export

Post by mastaflow » Wed Aug 17, 2016 8:19 am

I'm using HLT with internal GPS (1Hz) and GPS speed has nothing to do with real speed. OBD speed seems to be much more accurate.
001.PNG
001.PNG (59.81 KiB) Viewed 1818 times
So it would be great to have all data in vbo-files.
Also I think that column names do not matter at all. VBO-format is pretty simple and I see no problem to change them with text editor if needed. It is much more easier than combining CSV and VBO :)
User avatar
Harry
Site Admin
Site Admin
Posts: 9444
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: Enhanced VBO export

Post by Harry » Fri Aug 19, 2016 4:07 pm

Hi,

GPS and wheel speed are actually better than expected for an internal GPS. GPS will have min/max values clipped in case it is a short peak. The only issue is the sensor delays are not quite in sync (OBD is ahead). You can compensate this (for new recordings) by reducing the OBD delay by e.g. 0.5 seconds. Search for "sensor delay" here on the forum to find more information. Both GPS speed (see column velocity km/h) and wheel speed are included in LapTimer's VBO export already.

- Harry
Image Image Image Image
Post Reply