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…
Garmin-Matthew Gradient lag is 1min 30sec !!!
https://youtu.be/L2uY2Y9rdqE
How do you know that the MTB course is actually 750m and not 610m?
The barometric altimeter has an accuracy of 15m, so 135m instead of 125m is fine and within the specs.
Why is the elevation profile showing that much incline and decline when the road is actually flat? If I remember correctly when following a course the gradient is just taken from the course and not calculated live, but I might be wrong. If I remember correctly, then you would need to fix your course to get a better gradient showing or not follow a course while riding.
The value shown in the Grade data field is computed from the barometric data and distance data.
There is around a 15 second delay due to data smoothing. A delay of this length i shown above (90 seconds) s not due to data smoothing. It is either a faulty unit or a unit with a blocked a barometric sensor port.
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 edge 520 it was 750m
I do not use course following feature
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 at battery charging port, it looks clean and fine
I had similar gradient lag yesterday while on the road bike by far the worst I’ve seen. I was on a short climb I had been climbing for well over a minute climb pro was showing climb starting in…. I had previously deleted all existing maps and re added them. Current Gradient lag pretty much makes using climb pro and power guide a total waste of time and yes these are 100% related to gradient lag.
did yesterday my regular course, Epix2 gave me 833m of total ascent.
Epix elevation reading are perfect! Very quick. It detects the smallest height difference and do it instantly
here is the video. When me and epix were climbing, edge continued the descent. At the end edge was -5% and epix gave +7% grade
the grade is upper left
https://drive.google.com/file/d/1phbhDLMb7N_wK2Om8MYFBNHhIbH-yA8T/view?usp=drivesdk
https://drive.google.com/file/d/1C_QRgL10rzq7S7nJy6-yMJOeIyFjtNic/view?usp=drivesdk
I did an “elevator test”)) as i said, Epix is perfect. Edge demonstrates unacceptable lag for punchy XC MTB tracks.