Incorrect Elevation Gain
Answered
Hi guys,
Let me share with you a couple of bugs I have found:
1. When sync routes from Komoot
Planned route in Komoot:
Dashboard after sync Komoot account:
Can't understand the difference !! And why does it change from 370 m (which is the real gain) to 728 m!
2. When riding
Planned route in Komoot:
Recorded route in Karoo:
I truly believe that Komoot has calculated the gain correctly, but these 500m difference it is simply not possible....But there's more... When you click on the route, the gain is different...
Can't send now the K2 screen but at the end of the ride the field ASCENT showed: 1772 m. I'm gonna try switching the Elevation Calibration to Manual to see if this second problem is solved, but the planned routes one (where apparently the dashboard just has to sync with Komoot) I can't figure it out.
Thank you !!
-
Today I drove a flat lap with 190 HM.
Karoo 2 says 1220 Hm. That is absolutely unbelievable and incomprehensible. Strava says correct 191 Hm.
Hammerhead has been ignoring this incorrect elevation issue for months. But I've only had the problems since the end of last year after the big map update. Previously, the deviations were all within the acceptable range. The problem is much more extreme for me in Germany than last week on vacation in Spain. There were deviations between 50 and 150 m. You can live with that. So the problem must be related to the map data. It's funny, too, because the barometer measures altitude. The device is really useless. But Hammerhead only releases pointless stuff in the updates when finally solving this height problem. It's a shame, otherwise a great device. -
I ride mostly in Germany (Berlin area). I noticed that since removing the SIM card (which didn't work with the Karoo anyway :-/), recorded elevation data is slightly better again (though still very much off in general - I always use correction on Strava). When I was riding in Luxembourg/France and the Netherlands recently, the Karoo's recorded elevation data seemed almost accurate though! I have no explanation for the behaviour, it's really weird.
-
i don't use a SIM though. But if the altitude meters driven are 7 times the actual altitude meters, this can no longer be tolerated. I've probably already had 20 trips with such extreme deviations. On a completely flat ride, meters of altitude of a mountain stage. Something like that with a bike computer is a cheekiness after all. Garmin and Wahoo get you that too.
-
Also note the slope and inclination, ridiculous. The worst thing is that Hammerhead completely ignores it and does not react to it during any update. Only new features but no fix bugs. I will probably switch to Garmin again and will have to do without the ingenious navigation and operation. But the basic functions are flawless with Garmin. Then Hammerhead should rather build navigation devices than the best bike computer in the world.
-
Pay attention to this: Today I have done a ride (133km 1900m elevation gain) WITH SIM card installed. Just at the moment I was starting my ride, K2 has notified me about loosing connection with my speed sensor (no battery at all). Well, elevation gain showed by K2 has been 1932m, real Strava data 1884m. Soooo goooood!!
Maybe my speed sensor was the problem? Don't think so, but I have to do more tests about this...
-
Been having this issue for some time now where my elevation gains are higher than those that ride in my group. Every time. Today on a ride my unit showed 3009 feet of elevation and my friend left this message for me on Strava: Your elevation is 1,000 ft more than the rest of us… you do hill repeats somewhere? What if anything can be done about this?
-
Hi all
Just received my karoo 2 three days ago, first ride that i do twice every week, very flat, strava elevation 147meters, almost same as my garmin 530 and garmin 1040, .... karoo giving 501m !!!!
Should i just get my money back or request for a new one?
Attaching screenshots:
Karoo summary:
Karoo:
Strava after adjusting:
-
timewriter opened a new request here: https://support.hammerhead.io/hc/en-us/community/posts/15247028058907-elevation
By the way, second attempt today but more prepared with a screen with ascent, descent and elevation data fields to try to understand what's going on. Overall same result as yesterday real ascent around 420m, karoo 3 ascent -> 1190m (ooooopsss).
the elevation i think was pretty much ok but moving +1m -1m too much, and every time that happens, ascent and descent is updated, i believe this might be easy to solve to just update ascent and descent when there is a +3/-3 meters net ascent or descent. The barometer might not have the accuracy to do these updates every meter or even less than that. In my garmin it is only updated when 5-6 net meters elevation gain/loss happens. I'm going to open a bug ticket by sending an email to support too to see if they are in to answer and solve it.
maybe you can comment on that one and we get it fixed soon.
cheers
-
Looks like most of the units have the same problem, even if you get a replacement. Support told me they are working on it and requires a firmware update for the barometer chip, so looks like it’s a hardware issue with one of the components.
I decided to do not return mine and wait for the update, but yes, it is very frustrating.
-
Hi all and Hammerhead support...
This issues goes back (more then) two year already. I wanted to open a new post on the same topic, but it's still not fixed, as far as I can see. So it doesn't makes sense to open a new post on the same topic.I live in The Netherlands (flat as a pancake) and I constantly show higher elevation then my fellow riders. I feel embarrassed. And Hammerhead should too, as this goes on for 2 years now!
I still love the Karoo, but please, fix this and share a good answer on status and timelines when it get's fixed.
Thanks
-
Here my educated tip based on my own experience ... stop waiting for a fix.
Elevation gain measurement/recording is a core function of such a GPS device. If it fails to do so, this is a massive product error giving you the right to return and request full refund.This is how I did already 1,5 year ago after using the device for almost a year waiting for month to get this issue resolve. After waiting month for a fix I wasn't willing to wait and asked by a formal support request to have this fixed in a timely manner or return/refund claiming that this a massive product defect. Guess what ... they just said I should return my K2 and once done they refunded my full payment.
I continue to view this topic and fast forward 1,5 years we are still in the same situation. Neither from you should expect that they fix this as the European community seams to be to small to focus their development resources on this bug.
Again, don't stick with a product which will not do what it is supposed to do ... report this formally as a massive product error ... if they don't fix it this is giving you the right to return and refund.
May receiving a higher number of product returns will help them to focus their work schedule to fix it.BTW... my Garmin 1030 I bought with the refunded money works perfect ... yes, K2 is a bit more fancy but by function Garmin is fully the same... so use our power as customer.
Please sign in to leave a comment.
Comments
84 comments