Android Grand Prix Edition App useless for Auto-X
Android Grand Prix Edition App useless for Auto-X
The group I Auto-X with uses a fairly big go-kart course as the setting for their Auto-Xs. A couple of years ago Harry's lap timer worked perfectly there. I'm not sure what edition I was on back then but I always upgrade to the latest/best edition as soon as the latest edition is available. It used to start recording when I reached the Starting point that I set and end at the Finish point that I set, no problem. Now it MIGHT start when I cross the starting line and when it does it'll record for 12-13 seconds if i'm lucky, then it acts like i crossed the finish line and stops recording. The Start and Finish lines are always 100-200 feet if not more apart as they always were when it worked just fine. Other Auto-Xers who use other Harry's laptimer competitors have no problem with their app working fine and recording the whole run. What happened to make it quit working as great as it once did??? Is there something I can check/fix in the settings to resolve this???
Re: Android Grand Prix Edition App useless for Auto-X
[Deleted double posts, as a first time poster you need to wait until the post is approved]
This is most probably some issue with your track configuration / track set or your GPS reception. There are no known issues with trigger detection except the named prerequisites to successfully map reality to the app. Starting with the track set, is it predefined or have you set it up your self? Which one is it? For kart sized tracks, you need to define a driving direction for triggers, otherwise chances are good LapTimer will catch trigger on a counter straight. A frequent issues are additional triggers set accidentally. So please verify you have no other triggers sitting in your database. You can find your triggers in the row below the track section header in Lap List. Check "Unspecified" track in particular. Finally, make sure you do not have conflicting track definitions (you get a warning and a red exclamation sign for conflicting tracks in Lap List).
On GPS: low accuracy means LapTimer is "blind" or nearly blind and will not be able to detect triggers. Make sure you have the device mounted like shown in illustration #3 of LapTimer's Quick Reference.
- Harry
This is most probably some issue with your track configuration / track set or your GPS reception. There are no known issues with trigger detection except the named prerequisites to successfully map reality to the app. Starting with the track set, is it predefined or have you set it up your self? Which one is it? For kart sized tracks, you need to define a driving direction for triggers, otherwise chances are good LapTimer will catch trigger on a counter straight. A frequent issues are additional triggers set accidentally. So please verify you have no other triggers sitting in your database. You can find your triggers in the row below the track section header in Lap List. Check "Unspecified" track in particular. Finally, make sure you do not have conflicting track definitions (you get a warning and a red exclamation sign for conflicting tracks in Lap List).
On GPS: low accuracy means LapTimer is "blind" or nearly blind and will not be able to detect triggers. Make sure you have the device mounted like shown in illustration #3 of LapTimer's Quick Reference.
- Harry
