Track Attack

Help on issues you run into with LapTimer; in case you have a question on how to use LapTimer, use the forum "Using LapTimer" instead
User avatar
rbpeirce
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 73
Joined: Fri Jul 08, 2016 8:21 pm

Track Attack

Post by rbpeirce » Tue May 07, 2019 1:48 pm

I don't know if this is a HLT issue, a TA issue or a transfer issue but TA doesn't seem to have any method to contact them.

I only found out about TA over the weekend and that I could load HLT data into it, which I tried yesterday. What I found was the lap trace over the track map and the speed traces themselves weren't right. The lap traces fell way outside the track lines with sharp changes and different laps were wildly different from one a another. Also, the speed traces didn't correspond to what the HLT video showed and different laps were wildly different. I know from past experience that the HLT speed information in the rendered video is pretty accurate.

TA requires a .vbo output from HLT and I have no idea if that is any different from, for example, a .csv output.

TA looks like a great way to examine data compared to looking at is on an iPhone 5, but not if it isn't accurate!
2012 Porsche Cayman R
2016 Audi A7
User avatar
Harry
Site Admin
Site Admin
Posts: 9547
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: Track Attack

Post by Harry » Tue May 07, 2019 1:55 pm

Hello,

No support on Track Attack here. Data recorded by LapTimer is data delivered by the sensors used. In case you use internal sensors - take care to mount the smartphone as shown in illustration #3 of Quick Reference. The internal GPS sensor is good enough to derive precise lap times, for analysis of data recordings (like line driven etc), you need to add an external sensor. See www.gps-laptimer.de/compatibility/ios or www.gps-laptimer.de/compatibility/android.

- Harry
Image Image Image Image
gremlin
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 69
Joined: Sun Aug 20, 2017 10:23 pm

Re: Track Attack

Post by gremlin » Mon May 20, 2019 6:35 pm

I use Track Attack extensively with Harry's and it's been quite good, that sounds however like oyu have a data error with the GPS. They have a facebook page for support at the moment but I'm not sure they're responding there it's worth a shot.

The latest versions of Track Attack aren't loading VBO files from the latest versions of HLT (23) I don't know what changed here, the format that got exported or something in their importer, but something stopped working and it's sad because they've got some great tools for analysis.
User avatar
Harry
Site Admin
Site Admin
Posts: 9547
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: Track Attack

Post by Harry » Mon May 20, 2019 7:05 pm

I’m not aware of any change for the VBO Export.

- Harry
Image Image Image Image
gremlin
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 69
Joined: Sun Aug 20, 2017 10:23 pm

Re: Track Attack

Post by gremlin » Mon May 20, 2019 9:31 pm

Good to know, thanks Harry. I'll keep on the Track Attack folks and see if I can't get a response.

One question as I've been looking through the files and trying understand them, the time field seems to be UTC but just seems to be time of day, how does it know on what day the recording too place? I can't see that data in the file.
User avatar
Harry
Site Admin
Site Admin
Posts: 9547
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: Track Attack

Post by Harry » Mon May 20, 2019 9:54 pm

Individual fixes come with the time of day (UTC) only. The day is part of the introducing comments / tags.

Harry
Image Image Image Image
gremlin
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 69
Joined: Sun Aug 20, 2017 10:23 pm

Re: Track Attack

Post by gremlin » Mon May 20, 2019 11:22 pm

Where would it be? Here's the top several lines of one of my files

The File created is when I exported the data, not when it was recorded

Code: Select all

File created on 18/05/2019 at 17:51:43

[header]
satellites
time
latitude
longitude
velocity kmh
heading
height
long accel g
lat accel g
GasPedalPosition
EngineSpeed

[comments]
Generated by LapTimer v23.0
(c) 2006-2019 Harald Schlangmann

[session data]
laps 32
name PacificRaceways
driver RAM
vehicle '14 Porsche Cayman

[laptiming]
Start   +7328.8487 +2839.2551 +7328.8210 +2839.2535 ¬ Start / Finish
Split   +7328.1943 +2839.1912 +7328.2217 +2839.1880 ¬ Split 2
Split   +7328.7141 +2839.1483 +7328.7418 +2839.1466 ¬ Split 1

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

[data]

018 001835.18 +2839.25043681 +07328.81006481 177.500 275.30 +00084.10 -0.17 +0.14 013 04284
018 001835.28 +2839.25068243 +07328.81397048 177.500 275.30 +00084.10 -0.17 +0.14 013 04284
User avatar
Harry
Site Admin
Site Admin
Posts: 9547
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: Track Attack

Post by Harry » Tue May 21, 2019 8:50 am

You are certainly right. The VBO format indeed misses the date of recording. Not sure, but maybe Racelogic devices always create this file while recording, so the date in "File created on ..." can be used... Added to my list. For now, you need to memorize the data yourself.

- Harry
Image Image Image Image
gremlin
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 69
Joined: Sun Aug 20, 2017 10:23 pm

Re: Track Attack

Post by gremlin » Tue May 21, 2019 7:35 pm

Thanks it'd be awesome if that created date was the time the recording was creating in local time I'd guess?
User avatar
Harry
Site Admin
Site Admin
Posts: 9547
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: Track Attack

Post by Harry » Tue May 21, 2019 7:55 pm

Hmm, the time stamp is UTC = GMT like for all GOS sources. Mixing this up with local time dates doesn’t sound good to me...

Harry
Image Image Image Image
Post Reply