I have 17.0.5 and having problems with trigger detection.
I went to the expert settings to adjust the corridor and sector values.
However, setting the sector for *either* "normal" or "wide" changes *both* values.
Also, choosing either normal or wide doesn't seem to help resolve triggers that aren't being found in the lap data.
Trigger detection problems
Re: Trigger detection problems
Also, reading the manual (http://www.gps-laptimer.com/LapTimerDoc ... iggers.pdf) there is a diagram on page 3 that shows the detection corridor as being directly ahead of the car.
However, the problems I'm having are with triggers that are in sharp (90 deg) turns, so perhaps the detection corridor is too narrow to pick up the trigger on the inside of the turn.
What about having "recalculate" search for the GPS fix line segment that intersects the trigger line closest to the trigger point and going in the correct direction?
However, the problems I'm having are with triggers that are in sharp (90 deg) turns, so perhaps the detection corridor is too narrow to pick up the trigger on the inside of the turn.
What about having "recalculate" search for the GPS fix line segment that intersects the trigger line closest to the trigger point and going in the correct direction?
Re: Trigger detection problems
In Expert Settings, you can change the corridor for narrow, normal, wide settings. As triggers with directions defined always use Wide, that is the area you want to change. In Expert Settings both the width and the angle to left and right can be adjusted.
Please keep in mind the trigger directions are defined to not mis-detect triggers. Following your proposal using the driving direction would void this functionality (which is necessary for tight tracks).
Harry
Please keep in mind the trigger directions are defined to not mis-detect triggers. Following your proposal using the driving direction would void this functionality (which is necessary for tight tracks).
Harry