Current elevation and gradient lag not fixed. The lag is 30-40 secons
As a result total ascent is ridiculous. On a 750m MTB XC course gives only 610m
Garmin-Matthew this month is THREE year anniversary of this bug and you haven’t fixed it yet!
Current elevation and gradient lag not fixed. The lag is 30-40 secons
As a result total ascent is ridiculous. On a 750m MTB XC course gives only 610m
Garmin-Matthew this month is THREE year anniversary of this bug and you haven’t fixed it yet!
https://forums.garmin.com/beta-program/edge-1040-series/public-beta-bug-reports/i/edge-1040-series---18-xx-bug-reports/18-23-elevation-problems-got-even-worse
Vote up please who has elevation problems
How do I know it is 750?
Answer
1) I run that course. Used to have all fenixes since Fenix 3. Now it is Epix 2. All watches give 750m
2) when it is a group ride, everyone has 750
3) when I used to have…
I used to have have Edge 830. And all this mess started 3 years ago. I gave it to official dealer, they said it is totally fine. I bought Edge 1040 and the same problem.
Barometric sensor port, if it is…
A very illustrative proof of the slow speed of the altitude change output on the Edge 1040. This is the main reason for the delayed grade display.
Garmin-Matthew please reach out the videos to the developer team!
Edge elevation graph is very smooth and slow
The case is closed
All the bugs and lags are within an expected level of operation
Very disappointing answer Garmin. What you call "limitations" is a bug of course, because other Garmin wearables proofing better results. This lack is very annoying for biking with a lot of ascents. And this gap should also influence other metrics, shoudn't is? And just because it is written anywhere, it doesn't have to stay poorly. So Garmin, please address to these "limitations".
Good news are coming, I hope
Yay, that's great news!
Finally we heard some good news. Thanks, mate.
Hi Michael, has it already been worked out as announced?
Unfortunately not. They are insisting on exchanging the device. But my Ukrainian dealer (well known in Ukraine for its greed and stupidity) refused
Anyway I strongly believe it is a SW bug rather than a HW one
As I said in the heading it all started three years ago with *30 series.
https://forums.garmin.com/sports-fitness/cycling/f/edge-830/235410/massive-elevation-inaccuracy/1641096#1641096
Either brand exchange or SW fix. Device exchange will not work out