Trip Log - Total Ascent [Bug 72]
-
- Posts: 112
- Joined: Tue Oct 01, 2019 1:19 pm
- Location: United Kingdom
Trip Log - Total Ascent [Bug 72]
I have Total Ascent selected as one of the data fields to display in my trip log. However no matter what I do I cannot get it to reset to zero.
1) No Active Route
2) Tried Reset, Reset Trip Data
3) Trip Recording is stopped
What am I doing wrong?
What I am after is a display of the amount of Ascent that has been undertaken so far on today's trip.
1) No Active Route
2) Tried Reset, Reset Trip Data
3) Trip Recording is stopped
What am I doing wrong?
What I am after is a display of the amount of Ascent that has been undertaken so far on today's trip.
- GPSrChive
- Site Admin
- Posts: 3921
- Joined: Fri Jan 20, 2017 11:29 pm
Re: Trip Log - Total Ascent [Bug 72]
My apologies, this is a known issue with firmware 3.40, but had not been posted to the Common Issues page yet! It is now listed as Bug 72.
Thank You for the reminder!
Thank You for the reminder!
-
- Posts: 112
- Joined: Tue Oct 01, 2019 1:19 pm
- Location: United Kingdom
Re: Trip Log - Total Ascent [Bug 72]
No problem.
I don't know how close you are to Garmin. But it has got to be worthwhile to them to invest in some automated testing for their software. Looking at the user interfaces I assume they have one code base for a lot of their products. So having automated test tools could be applied across their whole range. This aligned to continuous integrations and daily build/tests would really help them deliver bug free products.
https://martinfowler.com/articles/conti ... ation.html
Bugs like this (core functionality) still there a year after launch really isn't very good quality control.
I don't know how close you are to Garmin. But it has got to be worthwhile to them to invest in some automated testing for their software. Looking at the user interfaces I assume they have one code base for a lot of their products. So having automated test tools could be applied across their whole range. This aligned to continuous integrations and daily build/tests would really help them deliver bug free products.
https://martinfowler.com/articles/conti ... ation.html
Bugs like this (core functionality) still there a year after launch really isn't very good quality control.
- GPSrChive
- Site Admin
- Posts: 3921
- Joined: Fri Jan 20, 2017 11:29 pm
Re: Trip Log - Total Ascent [Bug 72]
Actually, this bug is NEW to firmware 3.40, and did not exist previously.
-
- Posts: 135
- Joined: Wed Jul 03, 2019 1:48 pm
Re: Trip Log - Total Ascent [Bug 72]
Lets hope to get some new additional bugs with 3.50
I am joking !!!!!
I am joking !!!!!
-
- Posts: 112
- Joined: Tue Oct 01, 2019 1:19 pm
- Location: United Kingdom
- GPSrChive
- Site Admin
- Posts: 3921
- Joined: Fri Jan 20, 2017 11:29 pm
Re: Trip Log - Total Ascent [Bug 72]
Preaching to the choir here!
-
- Posts: 22
- Joined: Sun Feb 16, 2020 4:59 pm
- Location: Germany
Re: Trip Log - Total Ascent [Bug 72]
Do you think, we get new firmware updates ? I hope they continue developing...
-- Greetings from Germany --
- GPSrChive
- Site Admin
- Posts: 3921
- Joined: Fri Jan 20, 2017 11:29 pm
Re: Trip Log - Total Ascent [Bug 72]
Eventually, yes - but they have been releasing many updates for the fitness products recently... Certainly the GPSMAP 66 is not forgotten.
-
- Posts: 30
- Joined: Tue Aug 20, 2019 3:28 pm
Re: Trip Log - Total Ascent [Bug 72]
Hello
I would like to remind, that apart from the user interface the numerics of the ascent figures should be trustworthy. This would imply the barometric altitude, which the ascent figures are based on, to be independent of the weather situation. In consequence the “Auto Calibration” of the altimeter should work in continuous mode. Fw 2.10 through to 3.40 fail in this respect. The feature simply is non-functional. I meanwhile had three replacements of my 66. All show the same behaviour. I’m tempted to regard this as a newly discovered physical constant. However, the bug has evolved from FW 3.10 to 3.40 (credits to Charles Darwin). Upon release of FW 3.40 it was claimed in the release notes that “Improved altitude accuracy with auto calibration” had been achieved, which I would not dare to confirm.
When contacting Garmin, they are ever so courteous and committed to tackle the bug. However, I have described the bug painstakingly both on phone and through mail more than once. This spoils the otherwise good impression of the GPSMAP 66.
I would like to remind, that apart from the user interface the numerics of the ascent figures should be trustworthy. This would imply the barometric altitude, which the ascent figures are based on, to be independent of the weather situation. In consequence the “Auto Calibration” of the altimeter should work in continuous mode. Fw 2.10 through to 3.40 fail in this respect. The feature simply is non-functional. I meanwhile had three replacements of my 66. All show the same behaviour. I’m tempted to regard this as a newly discovered physical constant. However, the bug has evolved from FW 3.10 to 3.40 (credits to Charles Darwin). Upon release of FW 3.40 it was claimed in the release notes that “Improved altitude accuracy with auto calibration” had been achieved, which I would not dare to confirm.
When contacting Garmin, they are ever so courteous and committed to tackle the bug. However, I have described the bug painstakingly both on phone and through mail more than once. This spoils the otherwise good impression of the GPSMAP 66.