Total Ascent Values Exaggerated by 50% [Bug 29]

[JungleJim]

Then the last person I spoke to seemed interested and took all the details and opened a support ticket with Garmin Tech to sort the issue. I'm not holding my breath though. It just seems it depends what person you get on the support chat, some just seem keen to fob you off as fast as they can others are keen to help.

This is my experience as well. Some support reps are very helpful and willing to investigate while others almost immediately put it off to user error or "that's just the way it works".

[RickN55]

Is there a way to delete these incorrect values? without removing the tracklogs, it seems as if there is an additional file and somehow altitude changes were entered twice. The incorrect measured values ​​will probably be corrected again as soon as a new update fixes this error.

I doubt that a software update will fix the already recorded values. If you want to correct them now you have some options: have Garmin Connect correct the elevation based on map data (needs synchronizing your activities with Connect) or manually edit the recorded activity files in Basecamp to recalculate the summary data by removing one of the recorded track points.

It almost looks like the issue seems to be that the Total Ascent as calculated by the GPSMAP and stored in the activity summary data does not match the ascent that can be calculated from the elevation in each recorded track point.

Can you explain more on how you can change the in the Connect app? I'm not sure how to do this but would like to try..

[RickN55]

Then the last person I spoke to seemed interested and took all the details and opened a support ticket with Garmin Tech to sort the issue. I'm not holding my breath though. It just seems it depends what person you get on the support chat, some just seem keen to fob you off as fast as they can others are keen to help.

This is my experience as well. Some support reps are very helpful and willing to investigate while others almost immediately put it off to user error or "that's just the way it works".

Yup, just a matter of luck getting through to the right person. If I get one of the ones that just seem like they're fobbing you off, I just keep closing the chat and trying again until I get someone decent.

[JungleJim]

Can you explain more on how you can change the in the Connect app? I'm not sure how to do this but would like to try..

I don't think you can do this from the app, but if you go to Connect web and view an activity, you have the option called "Elev Corrections" that defaults to disabled. When you enable it Connect will use mapping elevation data instead of the data recorded by the GPSMAP. See the screenshot.

Elevation correction Connect

Screenshot 2024-01-12 at 13.43.25.png

[RickN55]

Thanks will try later on the laptop.

Just done a 5.7 mile walk with both the 67 and Epix Pro Gen 2 Sapphire. My brand new 67 is still well out on the Ascent and descent.
Same walk same time both start/stopped at the same time
GPSMAP 67 Ascent 902ft/Descent909ft
Epix Ascent 400ft/Descent 401ft

Still well out

[Domi93CH]

I have the feeling that the air pressure sensor somehow has very strong fluctuations and therefore causes these high values. It always goes up and down a bit, sometimes by 0.5 mBar, which can always make up a meter or two.

[RickN55]

I have the feeling that the air pressure sensor somehow has very strong fluctuations and therefore causes these high values. It always goes up and down a bit, sometimes by 0.5 mBar, which can always make up a meter or two.

I'm hoping it's more of a software fault rather than hardware. As the values are crazy out, I did the same route with my 65s and epix and both which read just under 400ft ascent / descent, the 67 was reading over 900 for both! Really poor for the flagship GPS device to be this inaccurate, especially given the price £469 in the UK!

[Domi93CH]

It's unlikely to be a hardware error since it worked normally in 4.70. I think that a smoothing of the pressure sensor signal was accidentally deleted

[RickN55]

It's unlikely to be a hardware error since it worked normally in 4.70. I think that a smoothing of the pressure sensor signal was accidentally deleted

It's a shame we can't revert to older firmware on these models like the 65s and older. When i got my new device last week I tried to avoid the 6.60 update but it did it automatically was gutted!

[Domi93CH]

This must be possible somehow, since the Garmin employees are unlikely to delete everything every time they try something. Maybe there is a secret key combination in the test menu to allow older firmware to be installed.
Garmin will probably release defective firmware to force people to buy the successor product.
Otherwise, I see no reason why downgrades should be banned.
So I'll do the next update for sure and after that my 67 will never see WiFi or Garmin Express again.