Using the Lap Timer for "Pro Solo".
Posted: Tue Jun 10, 2014 4:22 am
Over here the SCCA has an alternate form of autocross called "Pro Solo". This puts cars side by side on mirror image courses with a drag race start.
Normally i'll mark a start and finish line for an autocross course. Usually you cross the start line at some speed, so a normal trigger works well. I've never had any luck with the standing start trigger.
I tried to mark the start and finish lines for both courses. Usually the lap timer will complain when I add more than one trigger to a course. This time it just refused to set the second start line trigger. The two start lines are only about 6m apart.
To work around that I put in one trigger between the two start lines, a few metres in front of the line. This did work reliably to trigger the timer. I also marked the two finish lines. This worked relatively well to do data acquisition.
Next I wanted to compare runs, but I find that the lap timer will not compare runs from one course to the other. When I try that, the data shows up for comparison, but the time deficit shows up steadily rising. The time deficit is the most massively useful feature of the lap timer for working out where you gain or lose time, this makes it less useful. I was interested in comparing how I was doing on the different course. Comparing a 36.5s run with a 35.3s run on the other side, the time deficit just climes to about 33s.
I thought the lap timer did the comparison on a time vs distance traveled basis, so I can't work out why its behaving like this.
Normally i'll mark a start and finish line for an autocross course. Usually you cross the start line at some speed, so a normal trigger works well. I've never had any luck with the standing start trigger.
I tried to mark the start and finish lines for both courses. Usually the lap timer will complain when I add more than one trigger to a course. This time it just refused to set the second start line trigger. The two start lines are only about 6m apart.
To work around that I put in one trigger between the two start lines, a few metres in front of the line. This did work reliably to trigger the timer. I also marked the two finish lines. This worked relatively well to do data acquisition.
Next I wanted to compare runs, but I find that the lap timer will not compare runs from one course to the other. When I try that, the data shows up for comparison, but the time deficit shows up steadily rising. The time deficit is the most massively useful feature of the lap timer for working out where you gain or lose time, this makes it less useful. I was interested in comparing how I was doing on the different course. Comparing a 36.5s run with a 35.3s run on the other side, the time deficit just climes to about 33s.
I thought the lap timer did the comparison on a time vs distance traveled basis, so I can't work out why its behaving like this.