K2 and Strava distance and elevation different?
Answered
1. Went on ride with friends. Start and stop the same place, same route, we ride together. They are on Garmins.
2. Uploaded my ride to Strava afterwards. The 2 people I went riding with have 29.12 and 29.3 mi for distance and both are about 1450 feet total elevation for the ride. Me? 30.5 miles and 1350 feet. Huh? More than a mile off?
3. Log on to Hammerhead dashboard. Click on ride. Although the header shows the same data as Strava (30.5, 1350), when I click on the ride and look at it, it shows 29.3 mi and 1531 feet of climbing? Huh? Why the difference?
4. Go back to Strava and look at ride. Click on "?" next to distance and click on revert distance button. Do the same for elevation. Now shows 29.3 mi and 1475 feet of climbing, which is closer to what my friends' Strava shows...
Is this what I have to do every time I upload to Strava? Is there a setting I need to change? I have it on auto pause at 0 mph.
-
I figured out that the distance error is likely from the auto wheel circumference is wrong. Auto calculate overestimated my circumference. Strava prioritizes the distance based on the Garmin speed sensor over the GPS data, so Strava overestimates the total distance traveled. The Dashboard uses the GPS data. I suspect that manually entering the wheel circumference will fix this problem.
Not sure if this is a K2 auto wheel circumference problem or my speed sensor doesn't transmit to the K2 well and therefore the calculated circumference is off and over estimated. Will try changing the battery on the speed sensor and see.
-
@Gordon: Thank you for sharing your experience and we have received similar reports from other users as well.
This could happen because of two reasons.
> The one as you mentioned if there is any inaccuracy in recordings or while automatically calibrating the wheels using the speed sensor. Let us know your findings after changing the battery of the sensor.
> The other reason for the discrepancy could be due to the fact that different platforms use different algorithms to calculate the values out of the FIT files.
-
It did improve slightly after changing the battery, but auto wheel circumference still way off and therefore the total distance on the ride was thrown off when imported to Strava. Is it a sensor cutting out issue? I also got honked at by several cars with my radar connected, because the radar does not beep or show cars when they are behind me. The only warning I get is that there is a white, yellow, red or green icon in the top left of the screen. That is a really subtle difference to have to note. There is no car icon with the distance away. I love the K2 and it is beautiful, but there are some serious problems with it, to be honest. The wheel circumference thing is annoying for sure, but the radar not working is pretty much a deal breaker. I need that for safety. That radar is charged prior to every ride, so it is not a battery issue. My Garmin ALWAYS picks up and beeps when cars are behind me, I also get false positives when bikers are behind me. I get silence from the K2. I need help to fix this. I want to love the K2, but if these issues can't be resolved, I will have to return it.
-
OK. Newbie radar problem. Easily fixed. Radar works. Too easily muted. Now unmuted.
Updated software this am. Still auto wheel circumference is not correct. Also, how frequently is the hammerhead seeing or looking for speed sensor data? I have auto pause on at 0 mph, but after stopping at a light, it takes like 2-3 seconds for the hammerhead to display 0 mph and then pause the ride. I don't know how my Garmin auto pauses (no change in GPS or 0 mph), but I feel like the head unit should be communicating with the speed sensor way more frequently than it appears to be, especially if you are going to use it for auto pause.
Will moving the sensor further up the list make it check speed more frequently? And/or make the auto wheel circumference more accurate?
Please sign in to leave a comment.
Comments
4 comments