Last year I used the certified Mettet track - and had problems where it would not register the complete lap. I tried setting the detection to narrow but I did not get better results. I have not been to the track since then - but I hope to do further testing. The only option i see is moving the trigger to a spot where another part of the track is not too close to interfere.
Which leads me to the simple question - laptimer could use a better algorithm to detect the trigger based on:
-feasable laptimes
-direction of travel
-speed
attached is a lap that the start was triggered on the short straight
-wrong direction
-too slow
-overall laptime not possible (at least not for me)
This is an example of how a lap looks:
I hope my comments help in improving the app
- Board index Harry's GPS Suite LapTimer Tracks
- Search
-
- It is currently Fri Apr 26, 2024 3:00 pm
- All times are UTC+01:00
Mettet
All discussions on existing and 'to be done' Track Sets
Jump to
- Harry's GPS Suite
- ↳ LapTimer
- ↳ Announcements
- ↳ Outdated
- ↳ Trouble Shooting
- ↳ Outdated
- ↳ Using LapTimer
- ↳ Outdated
- ↳ Accessories
- ↳ Global Navigation Satellite System (GNSS) Sensors
- ↳ Tire Management Sensors
- ↳ Engine Sensors
- ↳ Mounts
- ↳ Action Cams
- ↳ Audio
- ↳ Feature Requests
- ↳ Tracks
- ↳ Community
- ↳ Support LapTimer Development
- ↳ Camper
- ↳ Announcements
- ↳ Beta v19
- ↳ Dyno
- ↳ Announcements
- ↳ Using Performance Testing
- ↳ GPS Buddy
- ↳ Branded Apps (Go-Kart Racing Club, OMP Racing Suite, ROUSH Lap Timer etc)
- ↳ AppStore and Playstore
- ↳ FAQs and HOW-TOs
- ↳ Outdated
- ↳ About this Forum
- ↳ VideoPro
- ↳ Sailor