1030 + gradient issue

Please check your DMs here in the forums momentarily. gigas10

gigas10 said:

I will be willing to participate in the test.

I will DM you as well GarminNut

GarminNut said:

I have a 10 to 15 second delay before the gradient percentage matches the terrain.  What log files do we need to send to whom? 

The only answer I ever got was to swap the device for a reconditioned one. The money is impossible to return it to me. In other words, the proposed solution is another fixed second-hand device that works just as badly. SCAMMERS

Did you call them or was this response from email? Either way, if that's not acceptable, call them back.

For the respect you show, I think you are a GARMIN paid worker, so nothing to add to that. That would explain your ridiculous Garmin brand defense

I had to send them a lot of emails, because they answered me automatically. I was finally able to get a personalized response. Official answer to the problems described in this thread and bad temperature displayed   was, "since it is not possible that the instantaneous gradient has a delay of 15 seconds and if that the temperature that shows  it is 4 degrees higher than the real one, then the reason would be that my unit It was defective, that I send it to the technical service and that they would send me another reconditioned second-hand device.

Or the cleaning lady who did not give a crap about functionalities for one product

Former Member adressed me personally:

I responsed in this thread - I‘m willing to do.
I sent him a PM - I‘m willing to do.

I’ve never got a response.

However, it is strange that Garmin cannot reproduce this issue. It's not rocket science. It's a simple calculation: delta altitude divided by delta distance.
The delayed display of the slope results from 2 facts:
1) the change of barometric pressure is displayed with a delay of 10 sec. An iPhone can do this much more accurately.
2) the calculation of the slope is done with a further delay. This is of course unavoidable, but the calculation of the slope via IQ data fields is much faster. So damping of the Garmin slope data field is unnecessarily high.

I do not know with which activity or log files can be helped here.
Garmin programmers should simply look at the code of the relevant 2 outputs critically and improve.

I think Garmin just don't care.  They have agreed to replace my 1030Plus, though they have made a pigs ear of that and require that I send my device back with no clarity on how long it will take to replace, perhaps a month or more.  They are a joke.

If your analysis is correct, I suspect it is, then their failure to act beggars belief.  I have been using my Wahoo these last few days, I don't think it is as good as my Garmin for most things but I don't think any of us should carry on supporting a company that is so unwilling to engage with us.

As a matter of course each of us on this forum should DM Blake a copy of every new post, with the tag line How Long!!!

The thing is we all want a resolution not a war but we can only get that if Garmin shows us basic respect.