Autosport Labs

I've sent my log file to the email address as it's almost 20 MB even zipped. When in the racecapture app the device is listed as running 2.8.7 firmware, which is listed as the most recent on the web page. The event is here: https://podium.live/events/thompson-champcar-2019/device/teamz2 Distance def...

Brent, I'm showing 31 laps in podium, but the first 7 laps are --:--. The others have times. I think you should be able to see it under "Palmer SCDA - 2019" on August 15th. The predictive lap timer and lap times were working great the whole time, so it seems like the distance calculation m...

I'm not certain if this goes under the RCP/Pro page or the app page, but I seem to have lost the ability to plot by distance in the Podium interface. I'm uploading using a Mk1 RCP/Pro through a tablet. Both a running the lastest versions of firmware/software. I haven't used my RCP for over a year (c...

This is a dedicated racecar (chump). Our GPS had between 9-11 satellites, a quality of 2, and DOP oscillating between 0.1 and 0.9. We were running our radio around 462 MHz, and the antennas were set up exactly as in the picture. The weird part is that telemetry knew I was at Watkins Glen and showed ...

No, I meant in the current release (1.09). I hadn't realized that there was a new release out until now and was still running 1.08 (or sort of running it, the cursor problem meant it didn't really work for me). Haven't tried 1.10.1 yet.

I seem to be having intermittent trouble with the auto track detection not triggering my laps. I previously had intermittent troubles with automatic track detection where it simply didn't work but about a year ago it seemed to get a lot better and be fixed. My recent issue was at Watkins Glen where ...

I just noticed that the cursor problem is fixed in 1.09! Thanks a lot for fixing it!

The 6 minute lap isn't actually what I'm worried about, it's the fact that the 1:43.9 lap (lap 15) isn't showing in analysis but does show in in the data file (and in my transponder lap times). The fact that it didn't recognize a lap while going through the pits between the following two laps doesn'...

It also may help, my transponder times are:
1:44.806
1:43.959
4:23.623
2:14.503
1:47.519

In the analysis program my laps are listed as:
14 - 1:44.802
16 - 6:38.100
17 - 1:47.502

In the data file the lap times are listed as:
14 - 1.7467
15 - 1.7333
16 - 6.635
17 - 1.7917

Changing the resolution to the lowest available didn't fix the cursor problem. As far as the lap time, I see what you see in terms of the going through the pits on the graph, but that doesn't match what I see in the log file (when opening in excel). If I look at the minimum lap time (1.733) it is li...

I've used high end data analysis software (like Pi) that allows you to upload video and sync it to distance. You can then do a split screen with another lap (and synced video) and have them be completely synced. This is a very effective driver training tool when comparing two drivers. Does anyone kn...

I'm running 10.12.2, I have a 15 inch macbook pro from late 2015 (top of the line). My display is 2880x1800. The dropdown does not stay open even if my mouse is hovering over it. It will only stay open if I'm actively scrolling up or down. I have about 1 second to click on a lap after stopping scrol...

Following up with this, I can open the log file and see that there is a 1:43.99 listed as a lap time. However, in the analysis software the fastest lap is listed as a 1:44.9 and the lap which my co-driver was fastest on is missing! The sessions tab jumps from lap 14 to lap 16.

I've got two bugs which are fairly annoying with the analysis section of the RCP app. 1. The cursor on the graph moves a 1/2x the pace of my mouse. This means that I can't ever actually look at the values on the second half of any lap because my mouse runs out of screen when the cursor is at 50% of ...

After some research, I may have solved this one as well. I think the time is actually Unix time. It starts at 1/1/1970 GMT and is the # of milliseconds since then. If you are using excel, you need to convert it in to days since 1/1/1970 and then add "1/1/1970" (use the quotes) to it. Seems...