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?

  • Ahh, ok perfect.

    Many thanks @1track!

  • I did reset on your advice. Nothing changed.
    The elevation lag is kind of "within expectations", but a bit later than Epix and further readings much slower which cause total ascent shortage
    https://youtu.be/ltctVcPakkI?si=vgUIpcdxohRW0RR9

  • As you see on graph there is bigger lag than Epix has and because of slow readings Edge graph is smooth

  • The unit is faulty in some way. Additional postings are not going help as there is nothing anyone can do for you remotely. The problem is not a generic problem across the 1040. 

  • I used to have the exactly the same with edge 830. Dealer diagnostics for both said they are totally fine(((
    And my mates also have the same issues

  • Lets not confuse this thread with talk about older models. Let's keep it on the 1040.

    I would suggest moving any discussion of elevation lag to its own thread away from this gradient lag discussion and see if anyone else reports it on the 1040. In your specific case the unit needs to be exchanged.

  • I agree that should replace the unit.

    But I kind of disagree about having big elevation lag in another thread. It's related, and it's very difficult to show statistics from gradient lag. If you compare e.g. Fenix7 with 1040 they should have almost the same elevation graph, and lag, now when it's fixed. As I showed in my second diagram on page 52. Before when there was that big gradient lag the elevation lag was bigger for 1040 than Fenix7 (which is kind of funny, why did the tiny watch perform better than 1040).

    My point is that if elevation lag is acceptable, also gradient lag will be that, and if elevation lag is to big, also gradient lag will be that.

    About Michael_kalina's latest graph, that is about the same which I had when I compared 1040 with Fenix7 last autumn when there was that big problem with 1040. It's a little mystery I think, a HW problem that cause 1040 to act as it was doing with the SW last autumn...

  • If elevation lag is ok, that doesn’t mean gradient lag is necessarily ok.

  • I want to unsubscribe from this thread, but the e-mail unsubscribe link is broken.

    This horse has been flogged to death!

  • Another data point supporting Michael_Kalina's findings.

    Here is my ride data from a short one last night. My Epix Pro from last night is the more detailed red line, the dark blue line is my 1040 on the same route last month, and my Edge 1040 from last night is the smoother blue one.

    Last month's ride matched almost identically to my Epix Pro from last night. The odd man out is the 1040 last night.

    https://1drv.ms/i/s!AjfmC9r0iGv6maJDcEZF5lUH74LMIQ?e=ub0wUH

    The elevation is lagging and the Grade field doesn't change as fast as it did before I came home from the PBP at the end of August. 

    My 4 baro ports look clear.

    EDIT. 1 Baro port. Looked behind the usb cover to find it. 


    I've ridden the route represented in the graph many times and it used to update much more quickly. Before September.

    Something has obviously changed.