Karoo2 - MTB Ride Ascent seems wrong / too much
Hi Hammerhead,
On my last MTB ride K2 recorded 3474m ascent...which seems way too much. Dashboard shows the same number from this upload. Uploaded to Komoot the tour shows 1010m/ Strava 1055m. When I download the ride as a .fit-file from Hammerhead-dashboard and upload it back as route, dashboard will show me the route with 1114m (still a tolerance to Komoot and Strava but at least in the same range as the other platforms).
Some facts about my ride:
- MTB Ride with a lot of single trail, mini-climbs and partly very bumpy
- SIM card installed and enabled, tracking running (I read in the forum that there were some errors years ago which should be fixes by now)
- weather cold, sunny and stable
- ride location was in Germany
I would like to ask for support for this problem.
Thanks Andreas
** PS some thoughts:
Riding my Road-Bike on roads I have the impression that there are no dramatic deviations from the K2 to the measurement data of other devices (like my Suunto-Watch) or to calculated data of different platforms.
I guess platforms like Strava/Komoot/HH-Dashboard just calculate the ascent by the GPS-Data of an certain tour based on data of their own maps? Is it possible that these "theoretical" platform-calculations don't get the mini up's & down's on a longer MTB-Trail ride? And in this case the real-life-measurement of the K2 is more accurate that these calculation? I can imagine that this could be part of an explanation...but anyway, the deviation of about 2200m seems not realistic...?
-
Take a look at the elevation profile of your ride on the Hammerhead dashboard, I bet yours looks something like this as well
This was from my ride today, 3755 m according to Karoo, 183 m according to Strava (as an upside, Strava at least did the Correct elevation thing by default without asking). There are several other threads about this, try turning mobile data off to see if it helps. And yeah, this was in Germany as well.
-
Hi Anna, yes I have also a lot of razorblade peaks....similar to yours.
I always ride with mobile data on...because of the tracking feature. But I will test it next ride!
--> but i would really be interested what Hammerhead does about this? The other posts brought no solution and were months or years ago.... -
Yeah, there was something about altitude in the last update or the one before that, but I think it only concerned the beginning-of-ride calibration. This really needs to be addressed, and since my Karoo does not do this in comparable conditions in Finland, I can’t see it as anything other than (primarily) a software issue.
-
Right, must be software...I have absolutely no clue what they programmed that active mobile data destroys your climb-metres.
The question is how to adress problems if HH does not answers. And even if they do, it is usually "we forward it to the product team" and thats it....fire & forget :-(
-
Same Problem for me (still),also asked for support months ago. Answers is always "I share it with the product team"
Hammerhead should focus on first of all professionally cleaning up all their SW-Bugs and ensuring well-engineered stable basic functions instead of coming up with new-half baked feature-updates that won't work either.
-
Today I recorded 4703 m which Strava corrected to 280 m, new record?
As far as I have understood, the mobile data thing has something to do with the Karoo using the GSM base stations for some kind of recalibration when it momentarily loses GPS signal, and turning mobile data off stops this (or at least makes it much less frequent). My pet theory is that base stations in Germany (and other places where this occurs) are configured differently from what the Karoo expects, maybe the coordinates they broadcast are confusing something like altitude at antenna vs ground level or something...
Please sign in to leave a comment.
Comments
7 comments