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

1030+ gradient issue II

says:

"After reviewing internally, we have found that the devices showing a delay in Grade by up to 10-15 seconds are operating within our expectations.

For users seeing the delays in Grade of 20-30+ seconds, please reach out to your local support team as this may be hardware-related and may require an exchange."

A delay of 1-3 seconds is acceptable in practice. For longer delays, remove this information from the display. It's useless.

Top Replies

MGMATE over 2 years ago in reply to Wongataa +5
What that reflects is that something is wrong.
- In Edge 1030 (non plus) they are using Bosch 280 pressure sensor with relative accuracy +-1meter. and It works relatively well (I had it during 2 years)…
8958970 over 2 years ago in reply to bbrannon +5

The sensor is fast enough. It can give up to 200 samples per second. The problem is that none of the garmin programmers ride a bike uphill.
AuldNik over 2 years ago in reply to Wongataa +5

Wongataa said:
How fast do you think it is actually possible to detect a gradient change?

Considerably faster than the 1030+ manages. I mounted both the 1030+ and my old Edge 1000 on my handlebars, and…

All Replies

0 NZourik over 1 year ago in reply to scanducci

1000% AGREED!

0 scanducci over 1 year ago

and now with garmin 1040? Edge 1040 have the same problem or not? Will we be forgotten?

0 5698970 over 1 year ago in reply to scanducci

We have long been forgotten, a hardware failure. For me, the Edge 1030+ was replaced, but no change was made

0 YanGreg over 1 year ago in reply to scanducci

Forget it .They are never going to fix this .Probably a bad sensor choice for the 1030+ they did and wont admit it. And do the right thing !!!!

0 ralfborn over 1 year ago in reply to YanGreg

Even more worse the new 1040 obviously shows same dysfunctional behavior. I live in an area with lots little climbs, sometimes, my 1030+ does not even notice so a huge amount of elevation gain is neglected over the cycling season. On top of that, measured acceleration on my unit shows the same, dysfunctional behavior. When accelerating from 30 to lets say 35 Km/h it's more a jump to 35 km/h while my mobile or other gps units in my reach correctly display the accelerating speed so the average speed measured is affected as well as the summed up height count.

0 Garry over 1 year ago in reply to ralfborn

https://you.38degrees.org.uk/petitions/refunds-for-edge-1030?source=rawlink&utm_medium=socialshare&utm_source=rawlink&share=a9f8fa46-36db-4ef9-bf38-17b7ca907472

Sign the petition to Garmin UK asking for a refund

0 YanGreg over 1 year ago in reply to Garry

can't sign it I am from canada

0 NZourik over 1 year ago in reply to GarminNut

GarminNut

Exactly!!
Wongataa is just being silly…

0 onEDGE over 1 year ago

I’ve noticed that the Elevation and Grade data fields are significantly slower to update on the 1030 Plus when compared to the 820 and my older 510.
Comparing the 510 to the 1030P the 510 is near real time, the 1030P is a bit after the event. This seems bizarre to me considering the processing power of the 1030P.

The temp on the 1030P did seem artificially high but turning off WiFi reduced it to near ambient.

0 NZourik over 1 year ago in reply to onEDGE

@onEdge

Correct, seems all Edge versions ending in x30, or xx30 or the 1040 are afflicted with the unbearable gradient lags, despite (or more likely - because of) their “upgraded elevation/gps/barometric processors” over their predecessors’.

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

Curiously - not the regular 1030.