GPSrChive Discussion Forum

sammyB wrote: Wed Aug 21, 2019 10:38 am Hej, here in sweden it is still not possible to download software 2.70
Do you now wy?

I could download it with the "Garmin Webupdater" before "Garmin Express" provided the update

Have done this before, bud no results, now it works fine.
Thanks

feraltek wrote: Fri Jun 07, 2019 5:07 am Ditto - Vs.2.60 and Garmin Express says I'm up to date.

HI Try with Garmin WebUpdater.

Updated via webupdater
Garmin express could not find any update

tomocernec wrote: Thu Aug 22, 2019 2:35 pm

feraltek wrote: Fri Jun 07, 2019 5:07 am Ditto - Vs.2.60 and Garmin Express says I'm up to date.

HI Try with Garmin WebUpdater.

Thanks, but I already updated it back in July. There's a message from me earlier on this same thread.

Did someone test 2.70 with expedition mode extensively - just read the info that someone had the problem that logging stopped in e-mode and could not find satellites after stopping e-mode - just reboot was solving the problem.
https://www.naviboard.de/showpost.php?p ... stcount=39

Maybe that might be the reason, why 2.70 was not published for s long time

I have updated to chip Firmware 2.70 and after testing several times, it has not fixed the problem with EM turning off the satellite reception as soon as EM is resumed. I sent Garmin UK a video showing exactly what happens and they agree it is a software problem, but unfortunately 2.70 doesn’t fix it for my 66st.

Who else has this same problem? (Bug #56 in Common Issues)

So 2.60 seems to be the better joice.

How to downgrade from 2.70 to 2.60?

Is there a manual option to downgrade the gps-fw?

@Spiney
Do you have 3.10/2.70 ?
When did you send the video to Garmin?

E-mode was working on mine with 3.10/2.70 - but i testet only 2 times with 1 minute in e-mode today (manual e-mode)

How long has the unit to be in e-mode?
Do you use manual e-mode or automatic e-mode (which settings)

Yes I am running with 3.10 / 2.70 and am happy with everything else using this firmware combination. I sent the video to Garmin UK on 17th July. I also had the problem with 3.10/2.60 so I would suggest you stay with 2.70. If EM is working okay for you, it will probably keep working okay. Let us know when you have been out for a hike or two.

EM was fine in this respect before I updated to 3.00. With 3.00/2.60, I made various changes to the settings etc to see if they had an effect and the problem did disappear but I could not identify exactly which setting made the 66st behave normally . Unfortunately, when I upgraded to 3.10/2.60, the problem returned and I have not been able to get rid of it with 2.70 either.

On my device this problem occurs the first time the device is resumed from EM. I have been using EM in Auto mode but I have tried Manual mode, all the GNSS/SBAS combinations, power save ON/OFF but cannot get rid of this bug.

I have asked Forum users a couple of times if they have had this problem, but not had much of a response, so I don't know if my problem affects many devices.