1030+ gradient issue II

i saw this same problem when i added grade into my windfield app a few months back.   the internal garmin grade definitely lags and can be calculated much quicker.   it's a bit tricky though since you do have to travel some distance before you try and calculate, and even that won't match up between two people on the same hill.  imagine a climb sliced into an infinite amount of 10 meter sections, each one starting a meter apart.  not all are the same grade and even with someone riding more or less next to you, there grade may not perfectly match yours.  i believe garmin implemented the delay on purpose to try and smooth some of that out.  the calculation i use in my app simply looks at the last x meters and gives you a grade based on that.  so it's faster and appears to me in my testing at least to be at least if not more accurate.

link to my app if you're interested.  grade isn't the main focus but it is an optional field which is nice since it doesn't take up an entire field on the screen

https://apps.garmin.com/en-US/apps/a924715a-2d53-42a1-a8f9-e365bc849840 

Says it requires a firmware update on my 830. I'm staying on 7.10 until they fix the bluetooth sensor dropout issues that started with 8.0

Waar kan ik dat regelen hoe moet ik hem omruilen ? Mvg piet de bruin 0653108607

What is the cost of the Windfield app?

https://windfield.app/versions

the PRO for 12 usd/yr is really the one to get though. Especially since I added the Strava integration into it

The elevation reading is just as slow to update as the gradient indication. I was out on a hilly ride today, came down a descent with a climb immediately following, and looked at the elevation field at the bottom so I could measure the height of the following climb. About 10-15 seconds later, while I had already been going uphill for that 10-15 seconds, I looked down at the elevation field again, and noticed that it had decreased by a further ten metres from the reading at the bottom, and I was already probably half a dozen metres higher by that time.

I've worked in software development for over 30 years, and never have I worked on a project where we released on the world the sort of bug-ridden crap that Garmin routinely foist on their customers.

Got fed up waiting for Garmin to fix this issue, 10-15 secs is completely unacceptable, so took advantage of Hammerheads trade in offer over Xmas and exchanged the Garmin for Karoo2. Gradient changes recorded in around 2-3 secs, and the climber function is just as good, if not better as the criteria for classification of climbs is lees strict, so more climbs included. No regrets and Garmin just lost another customer!

Please garmin fix this problem in the last update, please

It is certainly a bad approach to the issue, the problem could be eliminated by modifying the SW. Garmin seems to consider the current situation to be fully satisfactory.