What about Gradient Lag?

I bought Bolt V2 just to see gradient behavior, unfortunately I can go next week in the mountains, but in the sort climb I had very good behavior ,like 3-5 sec lag lets say or even less , climb was very short, like 40-50 seconds

also temperature was spot on, or at least I think it was, 1 C below one of my friends Edge and usually 1040 is higher than 830 with 2-3 degrease

I know that is not relevant but still ,if that crapy device can perform instant percentage , I don't care about battery 

First, "heavy calculating" was just some words I came up with (English is not my native language, doh), the unit must do something in these 20-25 secs of lag, which it is most often on my 1040. And gradient is following altitude, which is lagging some second(s) less.

As I wrote, Garmin's explanation to the lag is "This lag is a result of the amount of data inputs being processed", since altitude have almost the same lag as gradient my question is: what can take up to 20 seconds to calculate to show the altitude on the display? Especially when "One would hope the 1040 chip could do this in nanoseconds." as you wrote.

I have also in earlier posts asked why "This lag is a result of the amount of data inputs being processed" can be an explanation when a modern unit should be very quick.
If you look back through the current 27 pages of this post, you will see that I have questioned Garmin's explanation.

And I repeat, it's NOT some kind of average. Again, as I wrote, in my test route I have a dale(?) that is appr. 100m, it's something like desc 3m in 30m, flat 30m, asc 3m in 40m. The display is showing exactly that but with a delay of 20 seconds. So it's showing the same altitude and 0% gradient all through the dale which take appr. 20 secs. And after the dale when it's flat again it starts to show -1%..-3%..-4%..-2%..0%.....1%..3%..4%..1% (not exactly, but so you get a picture of what is happening). The altitude is behaving the same way, but some second earlier, as it should be. So, it's not  some average or smoothing. It's the same every time I go there, and I have seen the same in other places too.

Have anyone complained about shown gradient on e.g. Edge 800? Or why did they do this? What's the point of showing altitude and gradient 20 secs later (as it is for me).

No, once again, I don't buy "This lag is a result of the amount of data inputs being processed", for altitude? Come on.

I think if Garmin were to close the post someone is just going to open another one so they can keep complaining.  At this point I think they should just remove the gradient as a possible display option and be done with it.

Why don't they just add an option like "Gradient and altitude as Edge 800"?

Or the delay can be entered, some people like the 15 secs delay of altitude and gradient, some perhaps want 30 secs, or 1 minute? And some people that want the gradient to be shown want the delay to be 2 secs.

Hi K-O,

Yes I bought the Karoo 2 as I find the 1040 an extreme disappointment. The K-2 Gradient is as near real-time as you can get with sensors and elev. gain change calculations and has decimal point.

(For me the 1040 temp. is 3-6C too high, again the Karoo 2 is much closer to reality.)

Garmin have developed a dud device at a very high price. Unless you are into all the fitness features, 8 years on from the 1000 there are no noticeable improvements, apart from excellent battery life and a bigger screen.

@MikeF-Swiss.

Am absolutely NOT saying the 1040 (or 1030+) are better than the 1000 ever was, with respect to gradient lag reporting or giving a ‘good enough’, reliable gradient reading.

I miss the 1000’s gradient display. However my 1030 (non+) is a decent replacement for gradient weenies such as myself. OTOH, I hate my other Edge, a 1030+ for gradient. Just as laggy as the 1040.

Usually, when one hears (new/faster/improved) “design feature”, one naturally figures it’s way better than its’ predecessor - at least I do. YMMV

I have now looked in FIT files for both Edge 800 and 1040 about the delay for altitude, for the same route.
Edge 800: 1-5 secs delay (and NOT flipping(English?) up and down)
Edge 1040: 10-15 secs delay

Hello

I sold my Edge 1030+ to replace it worh a 1040, counting that the gradient lag problem was to be solved on the newer unit.

I have been taking some time off but will resume training next week, so I will buy a unit before restarting.

I will have to buy a Wahoo or any other unit that reads gradient with a reasonable delay if the 1040 problem cannot be solved on this unit.

Do you think it will be possible for Garmin to solve the gradient lag problem via firmware in the near future or it is a problem that the 1040 will have for ever ?

Thanks

I was actually chatting with Garmin last week about this issue via Instagram and I got this replay. "This is something we are currently investigating, and have no public announcement on.

hmm....