66st - unfortunately unreliable

Discussion related to the Garmin GPSMAP 66s/st GPSr
Solaris
Posts: 9
Joined: Tue Mar 23, 2021 8:11 pm

66st - unfortunately unreliable

Unread post by Solaris »

Hello,

Here I am, a new member, with a few observations about my new 66st.

I knew about its problems before buying, so I shouldn't be surprised, but... it's just not a good, reliable instrument at this point. Over two years of development and it still behaves like a pre-production test unit. I have to admit that I try to use it a lot to get familiar with its functions, maybe that's why I encounter the issues.

It came with firmware 4.20, I updated it to 7.20 and did a hard reset.

Every day I encounter a freeze or crash or both. One, two or more. What's bad, is that there's no pattern to it, I can't reproduce it. It happens while changing settings or taking a screenshot or deleting an activity (damn, I hate those - give me my simple tracks back!) etc. After all that time they still can't make it work. I never had such issues during years of using my 62stc.

At this point it's a piece of equipment I have to worry about, instead of trusting it. Maybe it's good enough for "Activities" like park running or weekend geocaching, but nothing more.

Here is a log of the latest crash. Yes, I have more of those. Not all though, I stopped paying attention to them at some point.

Crash Info
"product_name":"GPSMAP 66s",
"software_part_number":"006-B3028-00",
"ms_since_epoch":1616523479000,
"system_version":"7.20",
"build_type":"RELEASE",
"backtrace":"Function Address: 0x00305ACA Call Address at Function: 0x00305AE4 Function Address: 0x00309B66 Call Address at Function: 0030A388
Function Address: 0x003E79B6 Call Address at Function: 0x003E7A24 Function Address: 0x003E857E Call Address at Function: 0x003E8650 Function Address: 0x003E8672 Call Address at Function: 0x003E8736 Function Address: 0x003B82B2 Call Address at Function: 0x003B834C Function Address: 0x003B85B0 Call Address at Function: 0x003B8686 Function Address: 0x00331FC6 Call Address at Function: 0x00332006 Function Address: 00332214
Call Address at Function: 0x00332292 Function Address: 0x003B64E8 Call Address at Function: 0x003B655C Function Address: 0x003059C2 Call Address at Function: 0x003059D2 Function Address: 0x0031553A Call Address at Function: 0x00315664 Function Address: 0x0042B4A8 Call Address at Function: 0x0042B4BA",
"error_cause":"RTL Trap",
"proprietary_info":{
"Commit ID":"990a25a980ca5923821297868aca3c70f33021d9",
"Time":"2021-3-23 19:17:59",
"RTL Error Number":"6E5D8025",
"Error Message":"Prefetch abort, system r0-15 + cpsr",
"Task Name":"BTF main",
"Saved SP":"02DE1ED8",
"Saved LR":"003770E3",
"Saved PC":"09620008",
"R
[0]":"6E5D8025",
"R[1]":"480008C0",
"R[2]":"00305AE5",
"R[3]":"09620008",
"R[4]":"00000001",
"R
[5]":"00000000",
"R[6]":"02D6A228",
"R[7]":"00305AE5",
"R[8]":"00000002",
"R[9]":"00000000",
"R
[10]":"00000000",
"R[11]":"00000000",
"R[12]":"00000000",
"R[13]":"00000000",
"R[14]":"02DE1ED8",
"R
[15]":"003770E3",
"cpsr":"09620008"
}}]
User avatar
GPSrChive
Site Admin
Posts: 3881
Joined: Fri Jan 20, 2017 11:29 pm

Re: 66st - unfortunately unreliable

Unread post by GPSrChive »

Remove all of your custom GPX files and retest. Does it still crash? User created GPX files are a very common contributor to device crashes.

Also, you do not have to use activities, thee devices still do traditional tracks also, but only after you enable them:

Setup > Recording > Advanced Setup > Output Format > GPX & FIT

See GPSrChive for more detailed information.
Solaris
Posts: 9
Joined: Tue Mar 23, 2021 8:11 pm

Re: 66st - unfortunately unreliable

Unread post by Solaris »

Thank you for replying,

Yes, I tried removing waypoints, tracks etc.
I also set the output format as GPX + FIT right away, of course, but all I want from my device is to have option "Save Track" which just saves track. Now when I save, it saves file to Recorded Activities, but adds the track to Archived Tracks. To have it in Saved Tracks, I have to go to Recorded Activities, click Save As Track, and then it shows in Saved Tracks. It's just ridiculous.

I wanted to write that the problem with crashes and freezes is that they are unpredictable, but when writing this post, I wanted to be sure I'm not mistaken about the procedure I'm describing and saved the Activity I had on screen and... it crashed.

Damn this piece of junk, seriously :)


crash log
"product_name":"GPSMAP 66s",
"software_part_number":"006-B3028-00",
"ms_since_epoch":1616543404000,
"system_version":"7.20",
"build_type":"RELEASE",
"backtrace":"
Function Address: 0x003A7F22
Call Address at Function: 0x003A8260 Function Address: 0x003A844E Call Address at Function: 0x003A8492 Function Address: 0x0012F6F6 Call Address at Function: 0x0012F732 Function Address: 0x001311C6 Call Address at Function: 0x0013129A Function Address: 0x0043C5BE Call Address at Function: 0x0043C632 Function Address: 0x0011CDA0 Call Address at Function: 0x0011CDF0 Function Address: 0x0011D2AA Call Address at Function: 0x0011D48E Function Address: 0x00342DFC Call Address at Function: 0x00342ED2 Function Address: 0x00343004 Call Address at Function: 0x00343036 Function Address: 0x0034317E Call Address at Function: 0x00343238 ",
"error_cause":"RTL Trap",
"proprietary_info":{
"Commit ID":"990a25a980ca5923821297868aca3c70f33021d9",
"Time":"2021-3-24 0:50:4",
"RTL Error Number":"6E5D8024",
"Error Message":"Data abort, system r0-15 + cpsr",
"Task Name":"CDP main",
"Saved SP":"02DFB8B8",
"Saved LR":"003A8137",
"Saved PC":"003A8260",
"R[0]":"6E5D8024",
"R[1]":"00000000",
"R[2]":"C13F4000",
"R[3]":"00000000",
"R[4]":"00000080",
"R[5]":"038B31B0",
"R[6]":"000012A8",
"R[7]":"038B0C60",
"R[8]":"02DF716C",
"R[9]":"00000000",
"R[10]":"00000000",
"R[11]":"00000000",
"R[12]":"00000000",
"R[13]":"00000001",
"R[14]":"02DFB8B8",
"R[15]":"003A8137",
"cpsr":"003A8260"
}}]
User avatar
GPSrChive
Site Admin
Posts: 3881
Joined: Fri Jan 20, 2017 11:29 pm

Re: 66st - unfortunately unreliable

Unread post by GPSrChive »

Solaris wrote: Wed Mar 24, 2021 12:02 am Thank you for replying,

Yes, I tried removing waypoints, tracks etc.
I also set the output format as GPX + FIT right away, of course, but all I want from my device is to have option "Save Track" which just saves track. Now when I save, it saves file to Recorded Activities, but adds the track to Archived Tracks. To have it in Saved Tracks, I have to go to Recorded Activities, click Save As Track, and then it shows in Saved Tracks. It's just ridiculous.
This is not hot how the device operates. If you have GPX & FIT selected in setup, saving an activity will also save a tracklog simultaneously. You do not have to open the Activity and save as a track to have the track.

Your saved tracks will immediately be available in 'Saved Tracks > Archived Tracks' on the GPSMAP 66. You can also find them on the GPSMAP 66 while connected to a computer in USB Mass Storage Mode in the /Garmin/GPX/Archive Tracks/ directory.
Solaris
Posts: 9
Joined: Tue Mar 23, 2021 8:11 pm

Re: 66st - unfortunately unreliable

Unread post by Solaris »

gpsrchive wrote: Wed Mar 24, 2021 3:12 am
Solaris wrote: Wed Mar 24, 2021 12:02 am (...) when I save, it saves file to Recorded Activities, but adds the track to Archived Tracks. To have it in Saved Tracks, I have to go to Recorded Activities, click Save As Track, and then it shows in Saved Tracks. It's just ridiculous.
This is not hot how the device operates. (...)
This is exactly how the device operates.
The only way to show the track in the "Saved Tracks" folder - not in "Archived" subfolder - is to save it again from "Saved Activities".

I thought maybe I missed some option in the menu, so I checked in the online manual. Ironically, the search result for "saving a track" is... "Creating a Track from a Saved Activity": https://www8.garmin.com/manuals/webhelp ... D030C.html

gpsrchive wrote: Wed Mar 24, 2021 3:12 am Your saved tracks will immediately be available in 'Saved Tracks > Archived Tracks'
As I wrote, I want to save the track and access it directly from designated folder, not to archive it. Archiving and putting it in a separate folder is a different function.
User avatar
GPSrChive
Site Admin
Posts: 3881
Joined: Fri Jan 20, 2017 11:29 pm

Re: 66st - unfortunately unreliable

Unread post by GPSrChive »

Ah Ha!

Now that you have provided additional detail, I can better help you.

All Garmin Outdoor Recreation GPSr have three types of tracks.

1. Current Track - The currently active tracklog recording (not yet saved)
2. Favorite Tracks - Can be set to 'Show On Map' (limited storage - varies by model)
3. Archived Tracks - Can not be set to 'Show On Map' (less limited storage - usually about 10x the number of favorite tracks)

Every time a track is saved on a Garmin GPSr, it is saved into the 'Archived Tracks' folder.

If you want to move the track to the 'Favorite Tracks' folder, you can open it in 'Archived Tracks', press Menu, and select 'Make Favorite'.

The same can be done to move a track from 'Favorites' to 'Archived' (press Menu and select 'Archive').

The reason for this is older Garmin GPSr could only store a small number of tracks before older track data was overwritten. Newer devices offered virtually unlimited storage, but the operating system can only index and display a limited number of tracks on the map screen at any given time, so the user had to be given a way to choose 'Favorite' tracks that can be displayed on the map page, and 'Archive' tracks that are kept in storage for future reference.

Additional information is available at GPSrChive > How To... > Tracks.
Solaris
Posts: 9
Joined: Tue Mar 23, 2021 8:11 pm

Re: 66st - unfortunately unreliable

Unread post by Solaris »

Thank you very much for detailed information!

I just miss the simplicity of my 62stc, where Save Track means Save Track :D
It has 200 tracks limit, but all I usually needed was a quick access to save and load three to four tracks, reachable as fast and within as few clicks as possible.

Additional steps are not a big deal when sitting at home, but in the field, when trekking or paddling, one not always has the luxury of performing additional tasks without sacrificing safety.


Anyway, thank you again for your help, time to exercise a new muscle memory ;)
User avatar
GPSrChive
Site Admin
Posts: 3881
Joined: Fri Jan 20, 2017 11:29 pm

Re: 66st - unfortunately unreliable

Unread post by GPSrChive »

Solaris wrote: Wed Mar 24, 2021 2:33 pm I just miss the simplicity of my 62stc, where Save Track means Save Track :D
According to this Garmin Trail Tech Blog post, Track Archiving was introduced in March of 2010, predating the GPSMAP 62 by several months.

I just checked a GPSMAP 62s v7.20, and it also provides 'Archived' and 'Favorite' track capabilities.

Solaris wrote: Wed Mar 24, 2021 2:33 pm It has 200 tracks limit, but all I usually needed was a quick access to save and load three to four tracks, reachable as fast and within as few clicks as possible.

Additional steps are not a big deal when sitting at home, but in the field, when trekking or paddling, one not always has the luxury of performing additional tasks without sacrificing safety.
I do not expect the addition of a single keystroke to your workflow will cause you much grief or place you in additional danger. If at any time you are in a position where a single keystroke would make that difference, might I suggest not fumbling with the GPSr until safer to do so?

:D
User avatar
GPSrChive
Site Admin
Posts: 3881
Joined: Fri Jan 20, 2017 11:29 pm

Re: 66st - unfortunately unreliable

Unread post by GPSrChive »

Solaris wrote: Wed Mar 24, 2021 12:02 am I wanted to write that the problem with crashes and freezes is that they are unpredictable, but when writing this post, I wanted to be sure I'm not mistaken about the procedure I'm describing and saved the Activity I had on screen and... it crashed.

Damn this piece of junk, seriously :)
Please take the time to remove all personal data files you have added to the GPSr, including the microSD card, if present.

Then test for repeated crashes and lock-ups.

When none occur, begin adding your data back to the device, slowly, and methodically, retesting for crashes frequently.

When the constant crashes begin again, the most recently added files will be the cause.
Solaris
Posts: 9
Joined: Tue Mar 23, 2021 8:11 pm

Re: 66st - unfortunately unreliable

Unread post by Solaris »

gpsrchive wrote: Thu Mar 25, 2021 12:32 am According to this Garmin Trail Tech Blog post, Track Archiving was introduced in March of 2010, predating the GPSMAP 62 by several months.

I just checked a GPSMAP 62s v7.20, and it also provides 'Archived' and 'Favorite' track capabilities.
I never claimed that GPSMAP 62 doesn't have Archiving.

So again: as I explained before and I thought that it is clear already, when I choose to Save a Track in GPSMAP 62, it is logically stored in "Saved Tracks" folder. And that's what I expect.

To archive it, when I don't need direct access to it, I manually choose "Archive" from the menu and then it's being moved to "Archived Tracks" folder. That's all, can't be simpler.

As you suggest, I'll remove all my files and maybe reset it again, will see what happens.
Locked

Return to “GPSMAP 66s/st”