8,101
edits
Changes
From Fellrnr.com, Running tips
no edit summary
* Adding a Footpod to the {{Garmin 310XT}} improves its GPS accuracy.
* For the {{Garmin 610}} there was no difference with and without the Footpod. (Trueness was 3.33%/3.32%, Precision was 3.54%/3.68%, with/without).
* It takes time for the GPS watches to acquire the satellites. Some watches tended to say they are ready to go before they have an optimal lock. Therefore, to improve accuracy try to give them a little more time. Note that some newer GPS watches such as the {{Garmin 620}} have the ability to be preloaded with the satellite positions, reducing this startup time and start up in accuracy inaccuracy dramatically.
=Footpod Accuracy=
The accuracy of a Footpod is far higher than GPS, as well as more consistent and quicker to react to changes in pace. For any given run, the average pace error from the Footpod is only 7 seconds/mile (at a 9:00 min/mile pace) or 5 seconds/Km (at a 5:30 min/Km pace). In practical terms, I've found that I always have to use a Footpod to pace a marathon or for critical speedwork. For details of how the Footpod calibration was done, see [[GPS Testing Methodology]].
|}
=Garmin Fenix 2 Issues=
Like the Garmin 620, I've had similar GPS accuracy issues with the Fenix 2. In fact, the Fenix 2 is the only device I've ever had that has given the "lost satellite reception" message on my usual running route. Because of these issues Garmin replaced my Fenix 2 under warranty, and below are the results for the original and new watches. The replacement watch also gave "lost satellite reception" repeatedly and the error values for the Fenix 2 do not reflect these problems as the data from those runs was useless for analysis. I suspect there are three (possibly related) problems with the Fenix 2:# The MediaTek GPS chipset is not as accurate as the SiRF chipset. The best results from the Fenix 2 are generally mediocre. # The Fenix 2 records the right shape track, but offset by some distance. This does not look like a typical accuracy problem that would manifest itself randomly. # Occasionally the Fenix 2 will report "lost satellite reception", and I have several instances of this where the date and time were wrong after reception was lost. If a GPS device has the wrong time, then it will expect the satellites to be in different positions and will be unable to acquire a position fix. I have four instances where the workout file was stored with a date in April 2019, indicating that was the date when I terminated the workout and attempted to reacquire satellite lock. In one case I noticed the date and time was set incorrectly on the watch display after the satellite lost message. This problem might also explain the offset track above, but only if the clock was out by a very small amount.
{{:GPS Accuracy-Fenix2}}
{| class="wikitable"
