ShakeNBake

We're experimenting with a data coaching class at the next Schnellfest at COTA. I WAS hoping that I could get data out of track precision into circuit tools, but I can't seem to get a clean data file out. Anyone have luck doing this? I have not had track precision on the track yet, I tried using the sample data file (Jorg's lap at silverstone) and the VBO is fubar. Position data comes in, but somehow all the other channels, including velocity (I presume it's a time domain thing) are corrupt. Any help would be much appreciated, I was hoping to open up the coaching to anyone with a GT car, but unless I can get this onto a laptop, it's pretty useless as a tool. Thanks!

ShakeNBake

Well, I talk that back. With some monkeying, I was able to get data I recorded around my house into it. So crossing fingers data captured in anger at COTA will import for folks. Man, you'd think someone would try to make this work better. What a joke,

mthreat

In another thread here, I think someone said something about circuit tools expecting the data in 0.10 second increments (0.10, 0.20, 0.30, ...) but the Track Precision App exports it with times like below, that aren't multiples of 0.10. I'll remove the rest of the line and just post the first 2 fields (sats and time):

5 104459.06
5 104459.16
5 104459.26
5 104459.36
5 104459.46
5 104459.56
5 104459.67
5 104459.76
5 104459.86
5 104459.97

If the comment about the 0.10 increments is true, I see 2 potential problems with the data from the Porsche app. One is that the timestamps aren't multiples of 0.10. If they were all e.g. 0.16, it would be easy to just write a program (in Python or something) to read the file and write out a new file, changing all the 0.x6 values to 0.x0, for example 0.16 -> 0.10, 0.26 -> 0.20, etc. However, in the above data, you see two that end in .x7 instead of .x6. I guess you could change these to 0.x0 as well, but what the hell Porsche, just fix it.

I'll be at the next Schnellfest also. It'd be great to get this data into circuit tools.

HalV

I don't think that times listed in hundredth of a second should be an issue. For example, here is a line from an output from Harrry's Laptimer in VBO format.
[data]

009 211331.85 +2785.33031455 +05656.88925036 130.300 109.20 +00369.90 -0.01 -0.52 100 05946 0061 -00000001
...
Things get a little trickier when you want to merge video.