1030+ gradient issue II

NZourik said:

This includes the Edge 530, 830, 1030 Plus, 1040… 

Curiously - not the regular 1030.

The 1030 has an older model of barometric sensor than the other units, which appears to perform much better than the later model in the 530, 830, etc. Either that or Garmin's programmers are completely incompetent when it comes to writing the code for the newer sensor.

My wife has a 1030 and I have a 1030+. When we arrive at the top of a climb together, the altitude indication on her 1030 stops incrementing at that point. The altitude indication on my 1030+ will keep gaining altitude for the next 10 seconds or so, while the unit itself is not. Same with the gradient indication. The 1030 is much quicker to show a valid gradient - if I go up a short steep climb (say 100m @10-12%), the 1030+ has still not indicated the true gradient by the time I reach the top, and the gradient indication continues to increase for about ten seconds after I have got to the top of the climb and am no longer ascending.

@AuldNik,  Some Garmin diehard fanboy will inevitably jump in anytime soon, trying to explain - the older Edge 1030 regular, the 1000, the 810 etc. were “not precise” and the newer Edge x30 series, 1030 Plus, 1040 behave with 10-15 second lags, in order to be “more precise”.

The biggest problemis that Garmin is saying that , and for them this lag “is normal” behavior 

No need to test. Go read the 1040 forum. Same grade issue as here and 530 / 830. 

I've been experiencing this lag since I received the 1030+ early last year, but it seems to have gotten worse in the past 6 months. I too have now noticed the correlation between altitude lag and all of the other incorrect readings - honestly I never noticed how bad elevation data was behaving before, so I can only assume it wasn't as bad before.

It's particularly bad with rapid changes in gradient and elevation, particularly which short/sharp climbs and descents, to the point where I'll be going up/down a slope of say %15, but the reading with be +/-%15 almost like I'm on a counter-sine wave. Elevation data is beyond-ridiculous and never gives an accurate reading unless you haven't moved from a flat area for a while. Also it throws figures of 30-80% gradient at me all the time, like it's just started guessing because it's so useless. This is far from ideal as a serial Everester.

You could argue that it doesn't really matter, but when you do lots of climbing on short climbs it completely screws up your overall data as the unit has no idea what's going on and records it as such. It also makes it hard for me to manage efforts when I don't know exactly what the correct slope I'm ascending is. It shouldn't bother me so much, but it does my bloody head in! My old Edge 510 never had this problem and how old is that thing now?!

The irony is that I complained about my 1030 lag originally, but it was nowhere as bad as this, and wish I'd never got a warranty replacement because of the screen playing up as it actually worked better despite that. Also I never had a problem with the 1030 refusing to start an activity until the device was hard-reset occasionally.

There are things I like about the 1030+ (mapping is far better, screen is good) but this inaccuracy is completely unacceptable for a "flagship" device, and it's worse when Garmin sweeps it under the carpet like spending $1000 doesn't matter to them. 10-15 seconds lag should never be within an 'acceptable' level

Dear Garmin

got the same issue with a new 1030 plus. It’s roughly 600m off on climbs despite calibrating gps and compass. Renders the climb pro feature pretty useless. What can one do?

that's perfect :), according to Garmin