Reset Trip Odometer broken on 62s with new firmware

[+LucaPCP]

I updated the firmware of my 62s, and in the last firmware I have, 5.60, the reset of the trip odometer does not work properly any more.

I typically reset the odometer soon after power on at the beginning of a hike.

What happens is that once reset it shows 0m (or 0ft), but as soon as you move a bit, it jumps to some long distance (10.7 Km, the last time I did it).

What I think it happens is that also the last point of the previous track (before switching the unit off in the previous location) is included in the calculation.

 

This is a major deal, as trip odometer is one of the very basic functions I rely on. It's absolutely no fun to check the GPS, looking for the fork that should be say 1.5 miles from the trailhead, and get some absolutely bogus distance.

 

Is there any way for me to install an older software? Can anyone email me a copy (lda@dealfaro.org) if not?

 

Many thanks!

[+LucaPCP]

Your mistake is resetting it 'soon after power on'. You need to wait until it has a satellite lock and shows your current position.

 

That's what I meant: I reset it after the satellite lock. I normally switch the unit on and mount it to the bike / backpack. Then I get the rest of the stuff ready. When I am about to start the hike / trip, I check that it has a satellite lock and I reset the trip computer.

 

It failed to reset the trip odometer properly repeatably, several times.

 

I solved this by downgrading the firmware to 4.80, which I remember behaving fine. No more playing with firmware updates for the 62s for me! ;-)

Edited September 1, 2014 by LucaPCP

[+Lil Devil]

Did you report the problem to Garmin? They can't fix it if they don't know about it.

[+LucaPCP]

Did you report the problem to Garmin? They can't fix it if they don't know about it.

 

Yes.

But actually many people were complaining already on the Garmin Forums, so not sure I am the first. It appears to affect other models as well.

I made a very precise bug report, so let's see if they manage to fix it.

[+gpsblake]

LucaPUP, what was the last version you used where the odometer worked correctly?? I would like to roll back my firmware to see if it takes care of this problem. Here is a video of me being victimized by this bug.

 

http://youtu.be/fWmFn54V0T8

[+LucaPCP]

GpsBlake, I don't remember 100% correctly. But I have this very strong impression that I was on 4.80 last year, and I did not notice anything wrong then.

I reverted mine to 4.80. I will report back in a couple of days if this fixes it.

 

Yes, it's a very annoying bug. On the last hike, I was looking out for a fork some 3km from the trailhead, and when I glanced at the GPS, it reported some completely nonsense trip odometer - not pleased.

 

(I prefer metric for gps distances... I can understand 3.4 miles, but for short distances, 2000 ft says nothing to me).

[+LucaPCP]

I tested it more carefully. Version 4.8 also has the bug. I had to go all the way back to firmware 3.6, but I confirm that 3.6 works.

Tomorrow I will experiment more.

Edited September 2, 2014 by LucaPCP

[+LucaPCP]

I confirm: as for firmware versions,

• 3.6 works
  
• 4.3 has the bug
  
• 4.8 has the bug
  
• 5.6 has the bug
  

I have reverted to 3.6 and I am happy again.

I have not tested version 3.9.

Edited September 2, 2014 by LucaPCP

[+gpsblake]

Thanks LucaPCP, I will do the same and see if I get the same results.