GPSMAP 66 Firmware 6.00

[GPSrChive]

Yes, I have multiple eTrex Legend GPSr!

[AndyJ]

I'll have to keep an eye on this... on my first longer bike ride after updating to 6.00, the date in the FIT recording suddenly jumped forward nearly 2 years for 2 points, and then went back to the correct date. It was only the date that was wrong; the time was actually correct. For example, here's the timestamps:

Fri, 04 Dec 2020 15:30:41 GMT
Fri, 04 Dec 2020 15:30:49 GMT
Fri, 21 Oct 2022 15:30:58 GMT
Fri, 21 Oct 2022 15:31:09 GMT
Fri, 04 Dec 2020 15:31:17 GMT

[GPSrChive]

Can you please email the FIT file to Webmaster@GPSrChive.com?

[masaki]

I'll have to keep an eye on this... on my first longer bike ride after updating to 6.00, the date in the FIT recording suddenly jumped forward nearly 2 years for 2 points, and then went back to the correct date. It was only the date that was wrong; the time was actually correct. For example, here's the timestamps:

Fri, 04 Dec 2020 15:30:41 GMT
Fri, 04 Dec 2020 15:30:49 GMT
Fri, 21 Oct 2022 15:30:58 GMT
Fri, 21 Oct 2022 15:31:09 GMT
Fri, 04 Dec 2020 15:31:17 GMT

I've been having this issue since 2019-10-04 and regularly submitted new samples to Garmin Technical Support. I believe the software was 3.80 at the time. Last email with support was 2020-01-31. Time is always correct. Just the date is incorrect. Garmin has not acknowledged this issue though.

I set my 66s to log per second, I always just let it fill up the memory and auto archive the track. I've been doing this since 62s, 64s, 64st and never any issue until 66s.

Workaround so far that is still working-ish for me.

I save the track often. e.g. Drive to hiking spot. Save track. Start hike. Finish hike. Save track. Or connect 66s to laptop every night so it archives the track. So far the issue with some track points logged with futuristic date stamp has only happened a few times.

*This* post reply, is actually the ONLY one I have come across with the futuristic date stamp issue.

[GPSrChive]

Masaki, what were your time stamps doing?

[SFP]

Firmware 6.00 didn't fix the calorie calculations issue and it's still not working. Neither did the 5.00.

[GPSrChive]

Firmware 6.00 didn't fix the calorie calculations issue and it's still not working. Neither did the 5.00.

Which calorie issue are you referring to?

[g66]

>>Added support for starting navigation from the Explore App.

Is there any video-tutorial, how the new connection with the old explore app should/could work.

I am tired of installing a new buggy version and destroy my 66 therefore
It now works with JNX-Maps - never touch a running system

[GPSrChive]

Is there any video-tutorial, how the new connection with the old explore app should/could work.

I do not think Garmin have produced any recent Explore app tutorials. If you have specific Explore app questions, please post them here.

I am tired of installing a new buggy version and destroy my 66 therefore
It now works with JNX-Maps - never touch a running system

I do not believe GPSMAP 66 firmware version 6.00 will create any new issues not already present in firmware version 5.00.

[DDM]

Changing the main version number without resolving any bugs or demands for adapting by the users..... Imagine Microsoft or Apple doing this.... New Windows 11 .... we added a new series of icons....
Bravo Garmin