Ascent Totally Inaccurate
-
Hey Mark and Carsten,
Thanks for posting!To begin, I’d like to mention that the Karoo 2 uses a barometer to measure elevation, grade, and temperature, which are recorded in real-time during a ride. This is accomplished through a barometer, by measuring pressure and temperature; thus, time and weather become key elements here.
Every platform has its own means of measuring and interpreting elevation data. Strava compiles the readings from the FIT file using base map data and GPS data. As a result, the data would show a difference.
We’ve seen this happen for a few users in specific countries, and we discovered that if you have a SIM card placed on the device, the elevation reading can be affected. Our team is actively reviewing the instances and working on a solution to remedy this. The next software update will have some more changes around the reliability improvements on Barometer sensors.
I will be happy to work with both of you and thus have written to both of you separately to ensure that we have the ride data looked into from our end -
Funnily my K2's been constantly recording way more ascent than Strava or other computer suggest.
Elevation data from my last 5 rides
K2 Strava Garmin Wahoo
1876m 1535m
1079m 501m 507m/496m 425m
742m 407m
1174m 670m
248m 159mElevation appears accurate but the grade% is too sensitive. It keeps showing some -1% to 5% when riding on a seemingly flat stretch of road.
I can't believe this issue has been reported since launch and is still not fixed. I have to manually correct elevation every time a ride is uploaded to Strava it's embarrassing.
-
I hadn't paid much attention to elevation graphs until this past summer. The K2 seemed pretty good for the most part then I started noticing not just climb totals being different between the K2 and other sites (RWGPS, Strava etc. as noted by others here) but also that whether I let the unit automatically determine my start elevation or did it manually that the end elevation right back in front of my garage door where I began the ride was as much as 100m off, always higher if I remember correctly, than the starting elevation (210m is what it should be). I bring this up because I'm wondering how much of an effect this is having on the elevation gain totals the K2 is coming up with.
Has anyone else checked their start/end elevations when riding a closed loop to see if your unit does the same thing? My rides are virtually always under 1000m total climbing, usually 500-800m over 60-100km loops so no huge changes to deal with in the calculations, and being closed loops virtually identical descent figures.
-
Wallace.
I also noticed this problem with the slope that jumps 1-6 +/- in the driveway. As you write, it just adds meters to the sum of elevation gains, because what else is this measurement measured by a mechanical sensor? The worst is on uneven surfaces when the Karoo2 vibrates. I reported this with the FTP file to HH. In the next few updates I noticed an improvement, but the slope still jumps at 1-3 +/-. I think it's a sensor problem, it's too sensitive.
Bob.
My routes are mostly loops and have similar elevation gains as yours. It seems to me that the start/finish difference on the route has two reasons.
1 change in atmospheric pressure while driving that affects the measurement.
2 start driving on automatic height measurement. It doesn't work well at the start. I always check the altitude and if it does not match with google maps, I set the altitude manually.
-
Thanks Grzegorz. I'll start manually checking the detected elevation pre-ride as you suggest. What took me by surprise was that when I looked at the elevation data on RWGS for example, sometimes the start elevation looked correct but the end of ride elevation was way off, or other times BOTH the start and stop were wrong despite it being ok at the end of the previous ride which is usually the day prior. Maybe that was the difference between it being set to manual vs. automatic but I wasn't thinking to check it each day. On your advice I will going forward though.
-
I check the device altitude every time before starting a ride, the number seems consistent and accurate. I also checked the start and stop altitude today, the difference was within 5 metres. However for today's ride, K2 recorded 1199m of ascent, 30% more than Strava 894m. On one 8km stretch of flat road where I think K2 picked up near 100m of ascent, the data from dashboard shows a consistent elevation but varying gradients. I think it's all software related problem.
-
In my opinion, it's a mechanical sensor error. This is especially true on rough roads when the Karoo2 vibrates. In my opinion, this can only be controlled by changing the sensitivity of the sensor in the software.
Now you have examples of me crossing a railroad crossing.
3 photos of the GPX track line from the Sigma Rox10 computer and 3 photos from the Karoo2 of the same place.-the road is flat 0% slope, each of the 3 sigma measurements has 0% slope (Nachylenie)
- now the same distance measured by Karoo2. Before crossing 0% gradient, after rail potholes -2.3% and beyond -0.2% gradient
And it happens all the time, sometimes it adds the slope (most often), sometimes it takes away the slope. Finally, the difference with other measurements such as Strava
This needs to be fixed HH. -
I have the same problem with my HH K2. On every known route I always get more ascent.
A small examples:
HH 697m - Strava 331m
HH 1240m - Strava 610m
HH 1070m - Strava 410m
HH 1200m - Strava 385mEvery second that passes the HH shows a different % gradient, very erratic and no consistency.
I sent my *.fit from HH and Strava several times to HH support and I have only received a response that it is a problem with the barometer and they and the manufacturer are trying to resolve it.
400€ for a premium gps that shows chaotic info during/post route is a joke. In the meantime, I tell HH support to replace the unit with a new one because I have the warranty and they tell me that they can't do it because is possible that the one they send me will give me the same problem. Is this a joke? What is the warranty for?
-
I have been bragging to my riding buddies how great K2 is compared to the Garmin I used to have. For the most part this is no idle brag, but fact. I typically don't pay too much attention to my cumulative ascent. Where I ride is fairly flat. However one of my buddies, probably tired of hearing how great the K2 is, pointed out my K2 consistently reads 2-2.5 times the actual elevation cumulative ascent. Please help me remove the egg from my face and fix this issue.
-
Hi, I've got big differences in ascent with my K2. With my K1 ascent were equivalent with Strava and my buddies Garmin.
For exemple I've got a ride in moutain totally fool : 2100 ù for a 7km ride in small mountain. By the way altitude of the spot is not good neither.
Regards
Jerome PEREZ
Please sign in to leave a comment.
Comments
12 comments