The "Long Track" at BIR worked last year, but not this year.

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
Post Reply
User avatar
swbca3691
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 64
Joined: Wed Sep 02, 2015 10:57 pm
Location: Edina, MN
Contact:

The "Long Track" at BIR worked last year, but not this year.

Post by swbca3691 »

There are 2 tracks at BIR (Brainerd International Raceway) Many of the HPDE events drive the "Short Track" in the morning and the "Long Track" in the afternoon. The long track overlays most of the short track.

Last year I had no problems with Lap timer loading the second track for the afternoon. This year, the two events I have attended at BIR have not responded to the Start Finish line for the Long Track in the afternoon. I get a 25 minute lap for each "Long Track" session instead of 12 two minute laps.

When I load the long track for the afternoon, it says there are points already loaded for the short track, do you want to purge them (I don't remember the exact phrase). I say "yes" and load the Long-Track.

Because it didn't work a few weeks ago, today I loaded the Long-Track in the afternoon, and then I immediately loaded the Long-Track a second time. It said there are common points with the Long-Track already loaded, do you want to purge them. I said YES and it load the long-track again.

But, again it still never sees the start-finish line and records a single 25 minute lap.

Thank You for your support.
User avatar
Harry
Site Admin
Site Admin
Posts: 10642
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: The "Long Track" at BIR worked last year, but not this year.

Post by Harry »

I assume you are driving the Long configuration clock wise? The start / finish line is actually in bad position - directly behind the sharp turn. Especially with a weak GPS reception, GPS may "overshoot" and pass the trigger. Please try two things: 1) select the multi lap from Lap List, scroll down to Data Recordings and press Recalculate. Select Verify Lap to reevaluate lap splits. Select Wide when asked. 2) Next time you run into this issue, try dragging the trigger to the outer tracks limit or even beyond. As an alternative, raise the Wide Corridor from 40 to 80 meters in LapTimer's Expert Settings.

- Harry
Image Image Image Image
User avatar
swbca3691
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 64
Joined: Wed Sep 02, 2015 10:57 pm
Location: Edina, MN
Contact:

Re: The "Long Track" at BIR worked last year, but not this year.

Post by swbca3691 »

Three questions . .

you said 2) Next time you run into this issue, try dragging the trigger to the outer tracks limit or even beyond.

1. is that done before or after the track event ? and where in the interface is this done ?

2. I just bought a Dual XGPS160n external GPS sensor. Will that help ?

3. Is it possible to edit the GPS coordinates on one of your tracks ?


Thank You,
User avatar
Harry
Site Admin
Site Admin
Posts: 10642
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: The "Long Track" at BIR worked last year, but not this year.

Post by Harry »

E.g. in LapTimer - Analysis - Realtime - Map. You will see the triggers and can drag them around. This will make the track set loaded a User Track Set (instead of Certified). You can submit this User Track Set using Certify (Lap List - track - User Track Set - Certify.

Please add a common why and which triggers have been moved.

Harry
Image Image Image Image
Post Reply