[edit to add CAT4] and one more suggestion at the bottom]
Garmin OWS Potential Issues and potential improvements.
Using the Epix (with similar results on F6) during OWS and using FIT Decoders I can see why I am (and others) are still having issues with…
I cycled 78.8 or so km the day before yesterday. I'd plotted the route along points of interesting in Google Maps earlier and got roughly 85km. Of course GM is not infallible, but so far it's been fairly spot on. Also the weekend before I did a ride which…
I just tested 7-iron-A and 7-iron-B under the same conditions. Which one did I hit straighter? which has more consistent distance?
I have download the session data and come up with these.
Average-Off-Center
Remove any "-" signs from Total-Deviation…
Update: I've tested this again this morning, with a short course around my local park. It is now working as expected again: no audio annoucements, displaying Distance To End. I'll put it down as a glitch for now...fingers crossed it doesn't turn up again…
I did a workout today with my 955 (with software version 14.20), and configured a Structured Repeats workout for 4x1500m (with 3:00 rest), and warmup turned on.
The warmup had no issue, and once I pressed the lap button, I was able to complete the first…
So, to clarify the GPS situation; the watch had all 3 satellite systems "ON" plus the multiple frequencies... The Edge 830 had both the GPS and Galileo systems "ON" but does not offer the multiple frequency option... Now after several more testing runs…
I'm just onwdering if anyone has a fix for inaccurate distance (and therefore pace) on run in Garmin forerunner 945. It was pretty accurate I think for the last year until about a week ago and is missing around 1km (I know because I do the same run often…
It uses a combination of GPS and 'dead reckoning' distance estimation based on the accelerometer in the watch, because the GPS does not have continuous signal reception.
Distance could even be recorded in OWS with GPS set to off, before 22.73…
