This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

What about Gradient Lag?

Can anyone report if Garmin have fixed the issue that the 1030+ has with ridiculously long responses to changes in gradient?

  • I've been running my 1040 (non-solar) on my handlebars vs. my Karoo 2, my Edge 1030 (not plus) and my Explore 1000 (2 at a time). I've also tried a bunch of IQ apps re gradient on the same screen as Garmin's Grade field: AppBuilder (search for the formula to use); Sensible Grade; BRM Grade; Grade % Extended; and Elevation Grade.

    Some surprising (to me) results: BRM Grade was the best -- but it didn't improve on Garmin's default grade field by much. The latter clips off peaks and lows, so a climb that is mostly 6%, but includes a 10% segment, might show, at most, as 8% on the Garmin Field, but you'll see the full range, and a bit quicker, with BRM. Next best, I thought, was Grade% Extended, although I don't like its display options. Unlike others, I didn't think Sensible Grade was particular useful. But I ended up feeling like if Garmin could improve the responsiveness of its gradient field by 2 to 3 seconds -- and maybe give us back a single decimal option to minimize the clipping at the extremes -- I would be satisfied.

    Total Ascent, however, was another story. Rode the same course 2 times. My 1040 gave the total ascent around 2000 ft both times. Every other device was in the 1400 to 1600 ft range and, when uploaded to Strava and MyConnect with elevation correction applied, ended up around 1500. My friend rode with me the second time, with his own Edge 1040, and got 1650 ft for the course.

    So, do I have a bum barometer? I reset the Altimeter using DEM one time and GPS the other, but no appreciable difference (nor did I necessarily expect a difference for Total Ascent, as opposed to Elevation). Or is this a Garmin software problem again? Any thoughts/help appreciated.

  • Many Thanks for the extensive testing/comparison and reporting the (disappointing) results. 

    All the best, NZ

  • @Garmin-Matthew It’s been over 4 months since you “assured us” Garmin engineers were looking into the Gradient Lag problem and had a plan for improving it.

    Still no resolution? WoW… I hope you aren’t paying the engineers overtime - over the past 4 months of hard work, only to still find the 1040 ‘back at square-one’ with laggy, 15+ seconds of imprecise gradient displays.

    Q/ Was it simply a canned response - in order to help appease your unsatisfied, disappointed customers and owners of the laggy Edge series computers, including this 1040?

    Summer is coming to an end in 3 weeks in the Northern hemisphere. 

  •   I'm with you bro.  But what I have seen watching this thread the last year is that not only does Garmin not care about their customers, they actually hate us.  They are all talk, no action.  

  • I was thinking about this thread during my ride today and was going to ask for an update as well. I'm tired of my Garmin's random number generator version of gradient. That said, for a reason I can't explain, I still have it on my main data screen...maybe for some sort of comedic value.

  • Thanks for the recent posts about no update from Garmin.  I am in the market for a new bike computer, and have been watching this thread for over a year.  It is now time to actually make my purchase.  While all bike computers have their problems, the lack of improvement on this bug (and garmin's past bug history), has led me to decide against getting a new Garmin.  I'll vote with my $$$.  

  • You are lucky one)) if i knew, I would never buy 1040 either

  • Same, I waited 6 months until I read here that it was fixed before I upgraded from a 1030+ (it wasn't). At this point I doubt it will ever work acceptably on this hardware.

  • Exactly. And when the new 1050+ or whatever comes out, Garmin will have no compunction, shame or decency telling us how great everything is and to upgrade for $600. "the new 1050+..now with minimal gradient lag!"