Garmin Fenix 5S Warning
If you are thinking about purchasing the Garmin Fenix 5S, I would highly recommend you reconsider (or at least hold off until some dust settles). I have been using the 5S for a month now and have found the GPS accuracy is sub par compared to my 920XT. Specifically, the 5S records roughly 1 tenth of a mile extra on every mile, and that adds up rather quickly. My rides/runs are all at the beach (flat, strait, no trees, and no buildings higher than 4 stories). So getting a good GPS signal isn't (or shouldn't) be an issue. I have been using the 920XT on the bike simultaneously and that's how I noticed the issue. My bike route happens to have mile markers on the road, so on my last ride I hit the split button on each watch to record the difference. Sure- I might hit the button a little early or late each time, but it shouldn't be a whole tenth of a mile off. You can see the results in the Connect files available at the below links (FYI- I'm using GPS Only on both watches). Searching through various forums and blogs it looks to me like I'm not alone with this problem. Sadly, I probably would have been better off with the 735XT.
https://connect.garmin.com/modern/activity/1813943648
https://connect.garmin.com/modern/activity/1813944937
https://connect.garmin.com/modern/activity/1813943648
https://connect.garmin.com/modern/activity/1813944937
1
Comments
Seriously, since I use my Fenix 3 for EVERYTHING, I checked its accuracy. I routinely ride with a PowerTap Joule GPS as well as my watch. Less than a 1% difference. I run on a trail with 1/2 mile markers... much less than 1%. So the 3 remains a reasonable choice despite the 5's travails.
"Looking over the information, the track information seems nearly identical, My theory is that your Fenix 5s may have every second recording enabled. When this setting is enabled the device lays several more track points in an effort to help you collect more specific data. However, as a trade off if the device records this often, it is much more prone to be affected by what we refer to as GPS drift.
GPS Drift is something that can affect every device, but tends to show more on modern devices with high sensitivity receivers and fast recording settings (such as every second recording). Connect does its best to cut the extra unneeded data points, but it may be that the distance held the inaccuracy.
The two GPS tracks seem nearly identical, so we will need to take a deeper look at the original files, but the unit itself does not seem to be malfunctioning. "
Ill try GLONASS on my next ride out of curiosity if nothing else. But seriously, I've got practically 180 degrees of unobstructed sky to work with so there shouldn't really need to be a whole lot of extra software help needed to find or accommodate for the lack of satellites.
I've done a significant amount of riding with various different settings and on various different bikes. I've finally discovered the issue and wanted to report it back so that others might be able to troubleshoot this problem if they run into it.
I removed the PT sensor from the Fenix, then re-added it and was prompted to enter the wheel size. Voila, everything is groovy.
now that your device is working with a 650 you could use my groovy old ride