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?

  • Hello @Garmin-Matthew, 

    Anybody home?

  • Incorrect position on an elevation profile when following a course or using power guide has nothing to do with the gradient lap. 

    Gradient is computed from barometric data and distance. The Edge applies a smoothing algorithm, which results in the reported 10 to 15 second delay. 

    The position on the elevation profile is a function of the elevation accuracy in the course files used to build the power guide.

    The Edge uses the elevation and position data supplied in the course file so the gradient calculation does not affect the position along the elevation profile. 

  • Agreed said gradient lag is a pain, at release if was abysmally slow, with later release it has is less laggy, but still slow. I do understand, with gradient calc there will be lag from averaging over the past 2 or 3 secs

    FWIW I use the gradient field in the IQ app Windfield. Gradient updates quicker than native Garmin gradien. WF Grade + | Garmin Connect IQ

    Bonus with touch screen 1040 is that WF gradient field will, with appropriate screen taps will cycle through gradient, elevation, total elevation of ride and time of day
  • If I understand correctly the use of a dedicated speed sensor like the Garmin Speed 2 I have is recommended/beneficial for best accuracy.

    In regard to your last sentence: So it's advisable to have multi-GNSS enabled for best position accuracy.

  • here is elevation itself, not gradient. The lag is massive

    www.youtube.com/.../ANUqOyR4wGk

  • Thanks, but I don't understand why the Elevation is taken from the course file when out on the road, surely it should use the built in Altimeter and display that? I presume it does that on a free ride and records the Altimeter data. I think that was what Michael Kalina was complaining about, the displayed elevation is lagging behind reality out on the road. If you have poor data in the course file (elevation out of sync with GPS coordinates) it's going to display rubbish, GP Lama found this when loading a course file from Strava and using that with climbpro a while back not sure if that is still as issue.  I presume over the length of the ride the elevation data recorded is accurate as everything eventually catches up?

  • Yes, I was free riding and elevation was very much lagging.
    P.S. I do have the speed sensor, just in case

  • Thanks for the suggestion.

    However, with this IQ app, will it require a full screen devoted to solely Gradient?  

    Meaning, having to constantly flick/swipe through screens to go between displaying this app’s Gradient value and back to the other data such as HR, Power, Speed, Cadence etc…?

  • I've just finished uploading a video on  my Youtube-channel. The video shows me riding uphill and to me gradient looks spot on and felt like what was shown during the ride, too. The ride was some weeks ago, but it shouldve been the 18.xx beta already.

    The climb starts about 30 seconds into the video (links directly to the position): https://youtu.be/naC_iEZhaEc?t=30

    Here comes the really steep part in the next bend (links directly to the position): https://youtu.be/naC_iEZhaEc?t=100

    I didn't have a look at elevation but when gradient is in order elevation necessarily is, too.

  • re IQ app no need for a different screen, you just replace the Garmin grade field with the IQ app WF grade+  - much as you select any field to display what you require. No swipe/flick to another screen. Give it a go. I experimented and ran WF grade+ field alongside the normal garmin grade field and now just use the WF grade+ field