I was just creating a new track (for those who are interested, it is a autocross-track in Austria/Europe named "Nordring" in Fuglau) where we recently did a 24h race.
1. How do I share this track with others?
2. I set a `Cancel-trigger´to stop the actual lap when leaving the track for the paddock - is it somehow possible to measure the time we spend in the box, as I like to find out afterwards, how much time in total, we were not driving?
3. as I didn´t try the software in the field yet - is it possible after the race to see a total of the driven distance?
Idle-time during 24h race
Re: Idle-time during 24h race
[Moved to Using LapTimer]
To share a track, select the row showing "Trigger+POIs xxx" in Lap List - the one just below the AX section header. In the POI List you will land in, scroll to the bottom and press "Certify". This will generate a mail you can send to your friends for sharing.
To get a full view on how much time you spent in the pits, I'd suggest to not use a Cancel trigger but let LapTimer simply continue recording. Please take care you have a power supply connected. You will get one (long) lap including the pit break you can use later for analysis. In case you lots of fun in experimenting, you may add a stop / go trigger in the pit entry and exit. The exit one should be associated with a separate track set named "Nordring Pits". Not sure this will work, but please try. You need to take care however, both triggers are far enough from the track so they do not fire when doing a regular lap.
No session aggregation so far.
- Harry
To share a track, select the row showing "Trigger+POIs xxx" in Lap List - the one just below the AX section header. In the POI List you will land in, scroll to the bottom and press "Certify". This will generate a mail you can send to your friends for sharing.
To get a full view on how much time you spent in the pits, I'd suggest to not use a Cancel trigger but let LapTimer simply continue recording. Please take care you have a power supply connected. You will get one (long) lap including the pit break you can use later for analysis. In case you lots of fun in experimenting, you may add a stop / go trigger in the pit entry and exit. The exit one should be associated with a separate track set named "Nordring Pits". Not sure this will work, but please try. You need to take care however, both triggers are far enough from the track so they do not fire when doing a regular lap.
No session aggregation so far.
- Harry
Re: Idle-time during 24h race
How far should trigger be away from each other, not to interfear with one another?
If I do, as You suggest - setting a stop/go-trigger at the entry and the exit of the pit lane, i could give them a direction, so that they won´t affect the trigers on the track. This of course works only, if the pit lane is accessed against the drivig direction on the track (on this special course it is like this)
Will aggregation be a topic in the future?
And average speed which can be monitored in the display while driving?
The question is may be interesting for those, who do regularity challenges as the mille miglia etc.
If I do, as You suggest - setting a stop/go-trigger at the entry and the exit of the pit lane, i could give them a direction, so that they won´t affect the trigers on the track. This of course works only, if the pit lane is accessed against the drivig direction on the track (on this special course it is like this)
Will aggregation be a topic in the future?
And average speed which can be monitored in the display while driving?
The question is may be interesting for those, who do regularity challenges as the mille miglia etc.
Re: Idle-time during 24h race
Please have a look into this sketch:
The distance shown is the critical component. It needs to be bigger than any corridor LapTimer uses to detect triggers. As long as the stop/go trigger on the start / finish line has a direction, LapTimer will always use a wide corridor. This corridor's width is 25m by default. As LapTimer adds the current accuracy, we need to have a minimal distance of 35m (25m plus 10m for an o.k. accuracy) between the right end of the track and the triggers positioned in the pits. Actually it is irrelevant if the additional triggers are on the pit lane or if they are moved further to the right. They need to be at least that 35 meters away.
As an optimization, you can remove the direction from the stop/go triggers in the pit lane. In this case, LapTimer will use the normal corridor if set like this in Settings. The normal corridor is 15m by default, so the min overall distance needs to be more than 25m (15+10) in this configuration. To not get a new lap triggered when passing the pit lane, you need to remove direction from the track trigger too.
Hope that is not too complicated. In case you have a chance to test this, please let us know how it worked.
- Harry
- Scan-130530-0002.jpg (67.66 KiB) Viewed 1523 times
As an optimization, you can remove the direction from the stop/go triggers in the pit lane. In this case, LapTimer will use the normal corridor if set like this in Settings. The normal corridor is 15m by default, so the min overall distance needs to be more than 25m (15+10) in this configuration. To not get a new lap triggered when passing the pit lane, you need to remove direction from the track trigger too.
Hope that is not too complicated. In case you have a chance to test this, please let us know how it worked.
- Harry