My new 1030 plus is a replacement for 810.
the gradient is so slow the climb is half over before it is correct. Speed display jumps all over the place. Strava routes are nearly impossible to load.
I had them last week, but they have now disappeared. Is this really the best that Garmin can do?
what a rubbish device.
I can confirm this is an open ticket and we are looking into potential causes. I unfortunately do not have a timeline for a resolution, but I am working to get more information on my end to keep everyone…
Honestly what I have more of a problem with rather than the real time gradient on the display is with the delay in the altitude graph on the .fit file, which I'm assuming is the reason why the gradient…
I also remember a time when I would be paralyzed by such an imperfection of an expensive device. Today I am glad to find time to cover my 8000km per year. However, as an independent software developer…
What can I say... I am of two minds:
1) Garmin claims it doesn't occur on all devices and they can't reproduce it on their devices. This of course speaks for a hardware problem.
2) I have a hard time believing that.The Edge PLUS has the BMP280 chipset from Bosch built into it. This is the successor of the BMP180, which is installed in the Edge 1030. According to the data sheet, the new 280 is more sensitive than its predecessor. Personally, I think it's more of a software problem, for example, too much smoothing.
3) And there it is initially only about the response time of the elevation output.
In addition, there is the delay in the gradient output. And here I have proven that 2 IQ data fields for gradient react much faster than the original Garmin data field. You have to assume that the IQ calculation is based on the same values of delta elevation to delta distance as the Garmin data field.So again, a software faster response time of the Garmin gradient field must be possible!
I will send both the data from a test drive and all my other tests to Garmin Blake.
Somehow, though, I get the feeling they don't want to deal with my tests or they don't care....
But as I said, I will provide Garmin Blake with all the data he requests.
Let's see...
And as a side note: Me personally, I don't care much about this delay things. I do not mind much. 
But I'm interested to solve technical issues - and it can be made better!
I'll get back to you today on the subject of gradient lag. I end my collaboration in this regard, after I have passed all available and desired data to garmin-blake.
I would like to write down here still my personal conclusions of my tests:
It is a fact that the delay of the gradient display consists of 2 different components: the delay of the elevation evaluation and the delay of the gradient calculation itself.
1) Delay of the elevation evaluation:
I have proven that at least on my device there is a delay of the elevation display of almost 20 seconds. (See my postings before.)
I cannot determine if this delay results from a hardware error (faulty barometric chipset) or from the software treatment. This could be determined by reading the raw data of the chipset in real time and comparing it with the output of the elevation display. But this is not possible for me.
2) Delay of the gradient display from gradient calculation and smoothing:
In addition to the delay from 1) a delay from the gradient calculation is added. This delay cannot result from a hardware problem! As proof, I have compared the gradient display of the garmin original data field simultaneously with the display from IQ gradient displays.(See my postings before and the PDF image attached here.) It shows that IQ gradient calculations are much more accurate and correct than Garmin's data field - especially after changes of gradient like start of climb or end of climb.
Since the calculation of the gradient in both cases is based on the same basic values - delta altitude to delta distance - here simply the Garmin calculation is not good enough!
(I know, that for gradient calculation a certain delay is a must, because calculation can be done only, if you have ridden a „delta distance“.)
And with this I end my tests and postings, and I hope they may be helpful for Garmin.
ComparisonGradient.pdf (please change zoom level of PDF to see all data!)
