Total Ascent and Descent No Longer Match

So odd.

It's not odd, it's a Garmin Edge we are talking about, I cannot recall if the 305 was bugged, but every Edge since then has been bugged, the firmware has never been fully sorted to remove the bugs before a new model is released and true to form, it too will be bugged and the old model support discontinued.

And take for example, the Garmin 20 which I use for the likes of riding Paris Breat Paris, it had 28 firmware updates and is far more reliable than using an Edge.

It's time Garmin sorted it's issues out and started producing reliable Edges. They are training devices for cycling, there is no need to connect them to a mobile phone etc as going through issues with them, it seems to be connecting to a phone that is the root cause of most issues. The Edge does not need to receive weather information, rider tracking, electronic gearing info, text message info etc. You can use your phone for doing that and your eyes to see what the weather is as you ride. 

Would the maritime and aviation industry put up with issues like Garmin Edge users have to put up with. There would be aircraft crashing on a daily basis thanks to incorrect elevation data.

Which is probably why the Dakota 20 was updated so much, it had a far greater amount of various users using them from walkers to cyclists and from sailing to hang gliding.. The uproar from such a variety of different users would be far greater than those only using an Edge and they would have to listen to the complaints and rectify all the faults.

Basically, Garmin is clueless how to sort out all the Edge faults as they have made them to complex nowwith how they work with mobile phone interconnectivity and to hard to find the faults to rectify and when they do, they introduce other faults.

I was referring only to "Elevation Point Found" (which you've never seen) vs "location calibrating......" (which I've never seen).

A discussion regarding Garmin's lack of interest and/or ability to correct years' old firmware and hardware issues would rival War and Peace in length, and would resolve nothing.

I actually mis wrote what I meant to say which I worded correctly earlier, it's "Calibrating Elevation to location". There is no such thing as " Elevation point Found"

I was mistaken - my Edge 500 displays "elevation point found."

My 530 displays "Elevation calibrated to location."

That certainly sounds like a programming issue, as the unit is ignoring the elevation you entered for your GPS coordinates.

What if you delete the locations.fit file, in case yours is corrupted?

Tried it and made a new location for my start location and no change. Unless I am doing an event, it is the only location stored in the folder and after an event I delete all the locations for the event.

I was going to reinstall the firmware again past two days, but I have forgot how to do it and cannot find the file to upload on the 530 to do it. I've done it a few times in the past but thanks to Covid brain fog, I've cannot remember how to do it.

In fact, I might have remembered how to do it but it will have to wait till I get home from my ride.

The 9.75 firmware and backdating instructions are in this download.

https://forums.garmin.com/beta-program/edge-530-830-1030-series/f/announcements/334458/xx30-series-new-betas---special-notes-in-post

If you choose backdating, you can backup your settings so you don't have to start over from factory defaults.

But before you do this, have you tried browsing the 530 as a USB device and deleting the locations.fit file, rather than deleting your locations on the 530?

BTW, I've been running 9.81 beta firmware since it came out without issue.

I heve tried deleting the locations.fit file and it made no difference. But before that, I had opened it with a fit file reader and also another program and it confirmed that I only had one location stored in the file and it had the correct elevation.

Trying to reinstall the firmware, does not work, probably because I am not updating or backdating and just detects that I have 9.75 installed already and just deletes the backdating file so its obvious the 530 detects the file when it boots up.