New 60cs Software V 3.20

[+Team BlackZ]

Might want to update. Looks like they fixed a few bugs. Also the 60C has an update too.

Edited April 12, 2004 by Team BlackZ

[+Team DEMP]

Not that I have one, but to make it easy on folks, here's a link to the update as well as what's listed for this version.

 

http://www.garmin.com/support/download_details.jsp?id=475

 

Changes made from version 3.10 to 3.20:

 

Added Fuel Services option to the Find menu.

Find-by-name searches now only return a list of items that begin with the input string.

Added the ability to automatically close the keyboard when six or less items are in a find-map-points-by-name list.

Improved map colors for contour lines and night mode.

Corrected memory problem related to Follow Road route calculations.

Corrected problem with certain alarms working only during active navigation.

Corrected problem with saved track profile zooming.

Corrected problem with find-address searches across multiple map sets.

Corrected problem when finding waypoints and canceling from the Select Symbol filter option.

Corrected problem with auto daylight savings so that it works for years other than the current year.

Corrected problem causing an error beep after filling out a text or number field.

Corrected problem with the Altimeter page when going to the Reset page and clearing the track log.

Corrected problem with the Calibrate Compass option on the Geocaching Compass page.

[dchengmd]

Man, Garmin is just awesome. 3.10 was just out a few weeks ago.

[+RocketMan]

It looks like they fixed most (if not all) of the bugs/problems that I have encountered. I will have to give it a try when I get home. It sounds like they are listening to their customers. Way to go Garmin. RM

[+TFTC]

I wish they'd increased the notes size

[jbclimber]

I disagree with:

 

Improved map colors for contour lines.

 

When I use Topo (100K, not 24K), I can barely see some of the contour lines now.

Hmm.

[+Andy and Robin]

The find problem that this supposedly corrected is not fixed. When you do a search by name the waypoint you search for does not end up on the top of the list still. You need to scroll up to find it. I'm disappointed as this was my worst gripe.

[+nonnipoppy]

Duh! Where to check to see if version loaded is 3.20. I can't find it. Thanks.

[+Stem]

Duh! Where to check to see if version loaded is 3.20. I can't find it. Thanks.

menu, menu, setup, system, menu, software version

[+Team Four Paw]

You still can't project waypoints to the hundreth decimal place like you can with the legend..

[4x5shooter]

I disagree with:

 

Improved map colors for contour lines.

 

When I use Topo (100K, not 24K), I can barely see some of the contour lines now.

Hmm.

Ditto. I use 24K Topo East, and the lines are so thin now that they're almost invisible. Was someone actually complaining about the topo lines before? I can't imagine why. I liked the thicker lines.

 

They are still pretty easy to see (and look nice) in "night" mode, because the background is black so they stand out more. But I rarely hike at night.

[+nonnipoppy]

Thanks. All is well

[jbclimber]

4X5shooter:

 

Please contact Garmin and let them know that the contour lines are not improved in this new version. As a matter of fact, I would say that they are mostly un-readable. I don't want to be the only one complaining about this because it may not get fixed. Thanks

[TooCold]

Same thing here. The lines in my topo-Norway maps seem to be almost gone. This sucks, so I hope they fix it. Maybe it is possible to flash my 60cs back to 3.10?

 

Will contact Garmin and let them know.

[Mythos]

Same thing here. The lines in my topo-Norway maps seem to be almost gone. This sucks, so I hope they fix it. Maybe it is possible to flash my 60cs back to 3.10?

 

Will contact Garmin and let them know.

I reinstalled 3.10 from 3.20. It works, but I lost all settings, tracks and waypoint when downgrading. Be sure to have a backup.

 

Here are some screendumps showing the difference:

 

3.10:

3.20:

[+Shadow n Seqoui]

I disagree with:

 

Improved map colors for contour lines.

 

When I use Topo (100K, not 24K), I can barely see some of the contour lines now.

Hmm.

same.. same...

 

I thought the lines where gone myself... guess they are still there... if you can call them lines.

[4x5shooter]

I sent an e-mail to Garmin and referenced this thread. I'd suggest others do the same. Bring back the topo lines!

[Moun10Bike]

I sent in my request through Garmin's online technical support. I hope to see this "improvement" gone in a new firmware update soon. Yuck!

[+EtrexRose]

I like how it looks with 3.20. Less lines sticking out at you blocking other stuff. But I can see why many would be unhappy, i'll go either way.

[+TFTC]

I like how it looks with 3.20. Less lines sticking out at you blocking other stuff. But I can see why many would be unhappy, i'll go either way.

Sounds like a good candidate for a setting.

[jbclimber]

I like how it looks with 3.20. Less lines sticking out at you blocking other stuff. But I can see why many would be unhappy, i'll go either way.

For city driving I could care less about contour lines, generally.

 

For hiking, you need the contour lines. Otherwise the GPS can not be used like a map. Topo maps are useless if you can't see the contours.

 

My opinion.

[Loren Smith]

I noticed if you hold the GPS 60CS at a 45 degree angle and look down at it the screen the contour lines look fine. If you look strait on or from the bottom up you can barely see them. Also in night mode they look fine. However I have reported this to garmin and they say a fix is coming.

 

 

Loren

Edited April 14, 2004 by Loren Smith

[4x4cache]

 

I reinstalled 3.10 from 3.20. It works, but I lost all settings, tracks and waypoint when downgrading. Be sure to have a backup.

 

I'm new to all this stuff. I just got my Garmin 60CS. And already I need to upgrade my software? If I do what is the procedure to reinstall the old version if I don't like the new one? By the way I LOVE my new 60CS. I was like a kid getting a new bike for Christmas when it arrived from Fedex.

Edited April 14, 2004 by 4x4cache

[Moun10Bike]

I got this reply from Garmin today to my comments about the problems with contour lines:

 

Thank you for contacting GARMIN International.

 

I would be happy to assist you with this. You are correct. This is a known problem with this version of the software and our engineers are working on it for the next update. Unfortunately, I can not give you a date on when the next update will be posted.

 

If you would prefer to revert to the older version until a newer one is posted, I am including a link to a website that offers archived versions of GARMIN software options. GARMIN is not allowed to archive these ourselves due to ISO contract restrictions.

 

http://www.gpsinformation.org/perry/gpsmap60/

 

With Best Regards,

Kristi Jamison

GARMIN International

Senior Product Support Specialist

techsupp@garmin.com

800-800-1020

913-397-8200

913-397-0836 fax

http://www.garmin.com/

 

So, things look good for this getting corrected in the near future!

Edited April 14, 2004 by Moun10Bike

[+pecka]

I know we should stop moaning about the bugs in the fw. but I just can't help myself as I found yet another one that didn't appear in the previous version. When I do find by name in the cities and look for Ostrava, which is one of the big cities here in CZ, I alway press O, S and T and then the 60C automaticly closes the virtual keyboard and presents me w/ 5 cities - 2 from Poland, 1 from Russia, Germany and Sweden.

I'm using the Atlantic basemap model. Can anyone try it on their units?

[4x5shooter]

When I do find by name in the cities and look for Ostrava, which is one of the big cities here in CZ, I alway press O, S and T and then the 60C automaticly closes the virtual keyboard and presents me w/ 5 cities - 2 from Poland, 1 from Russia, Germany and Sweden.

I'm using the Atlantic basemap model. Can anyone try it on their units?

It may be in there with an alternate spelling, if there is one. That's one of the problems with using "find by name"-type searches on any computer program.

 

Here's something I wish was in the firmware: whenever I do routing, I manually turn on the "data fields" so I know how close I am to the next turn and my ETA. When I'm not routing, these fields are just blank, so I have to manually turn them back off. It would be nice if they automatically came up when routing, then went away once you reached the destination. The 2610 does something almost like that -- allowing different tabs when routing versus when just driving. I wish the 60CS could do that.

[+pecka]

It may be in there with an alternate spelling, if there is one. That's one of the problems with using "find by name"-type searches on any computer program.

 

Here's something I wish was in the firmware: whenever I do routing, I manually turn on the "data fields" so I know how close I am to the next turn and my ETA. When I'm not routing, these fields are just blank, so I have to manually turn them back off. It would be nice if they automatically came up when routing, then went away once you reached the destination. The 2610 does something almost like that -- allowing different tabs when routing versus when just driving. I wish the 60CS could do that.

No, there is no problem with find by name in the previous version, so I guess they messed with it.

[+pecka]

Here comes another one, and I'm not making this up. I have connected my 60c to the USB port and the display got corrupt - the display was diagonnally smeared. I switched off and everthing was ok. weird

[+Kiefer3D]

A problem I've noticed that no one else seems to be aware of, is the tracklog record. When set on “Auto” recording method the unit takes tracklog points every one or two seconds regardless of whether the interval is set to “most often,” “least often” or in between. In only 3 hours it filled up a quarter of the memory’s unit (set at 10000 trackpoints.) This was a point every one or two seconds. It also takes trackpoints at this rate when it has no signal, filling up the memory with useless data. This is clearly an error, rather than just a feature I don’t like.

[Moun10Bike]

A problem I've noticed that no one else seems to be aware of, is the tracklog record. When set on “Auto” recording method the unit takes tracklog points every one or two seconds regardless of whether the interval is set to “most often,” “least often” or in between. In only 3 hours it filled up a quarter of the memory’s unit (set at 10000 trackpoints.) This was a point every one or two seconds. It also takes trackpoints at this rate when it has no signal, filling up the memory with useless data. This is clearly an error, rather than just a feature I don’t like.

I hadn't noticed this yet because the RAM mount for the 60 is not out yet, so I am still using my V on bike rides. So, I decided to record a track today on my way into work. I can confirm what you are seeing. I am set to "Auto" and "Most Often". In previous units (including my V), this setting would record track points "when needed", with more points getting laid down on curvy sections of road/trail and fewer on straight sections. Also, for a typical mountain bike ride, the time between point recording varied widely, from 2-3 seconds to 20-30 seconds or more.

 

In comparison, the track that I recorded with my 60CS this morning while driving shows points being laid down at its previous location (i.e. it was laying down points before it had gained signal), and then shows tracks getting laid down every 1-2 seconds during the drive, even when stopped at a light. I'll be reporting this bug to Garmin, too.

[capt caper]

A problem I've noticed that no one else seems to be aware of, is the tracklog record.  When set on “Auto” recording method the unit takes tracklog points every one or two seconds regardless of whether the interval is set to “most often,” “least often” or in between.  In only 3 hours it filled up a quarter of the memory’s unit (set at 10000 trackpoints.)  This was a point every one or two seconds.  It also takes trackpoints at this rate when it has no signal, filling up the memory with useless data.  This is clearly an error, rather than just a feature I don’t like.

 

I noticed it also and I saw a post on another fourm that a guy did a spread sheet on it and proved it also.

Anyway I sent them a email awhile back and the guy said that he had one and didn't notice any thing wrong with it but would forward it to Tech.

I guess when sending emails like this maybe one should request it get forwarded anyway. Alot of the tech answer guys don't really or can't duplicate the problems.

 

What I do now when transfering tracks to the gps I shut the gps tracking off in the setup. It still will allow recieveing and sending tracks fine.

 

And just before a hike I reset the tracklog so I don't get the loose tracks when loaded back into my programs.

 

I fine this way does a clean install.

 

I just took all of my mountain active tracks I've saved over the years and sent them into the 60cs this way and then loaded them back into Topo 5. and NGTopo.

 

Also I'm getting freezeups while I've been loading these maps,info to and from programs. But when using it hiking I've never had a problem.

 

Hope this helps

Edited April 15, 2004 by capt caper

[cbcain]

After upgrading to 3.20 I get this odd problem. When driving, the next turn pop up works...however if I am walking it doesn't. All other settings are the same(follow road, shortest distance, etc.)

 

Also, didn't the 60Cs switch to geo-cache navigation when you got close to the cache? Mine doesn't anymore, I have to switch to the compass page or recalculate and choose off road.

 

I have been up for 32 hours and that may be part of the problem. Any advice is appreciated.

 

Chris

[+Firehouse16]

A few things I'd like to see them change. First is why is the cache ttitle when searching limited to 10 characters? It looks like it could hold at least 12. Secondly the "notes" window, it looks like it's at least three lines yet only 2 lines can be displayed. I would like to see this expanded to at least 3 lines or a scrolling window so we can hold more info there!

 

Thank you!

[+Firehouse16]

I just upgraded to V3.20 and I noticed that when I try and do a name search for a geocache that if I put in letter "D" it actually started about "H", if I put "S" in it starts at "W", serious glitch!

[+jotne]

Same thing here. The lines in my topo-Norway maps seem to be almost gone. This sucks, so I hope they fix it. Maybe it is possible to flash my 60cs back to 3.10?

 

Will contact Garmin and let them know.

I reinstalled 3.10 from 3.20. It works, but I lost all settings, tracks and waypoint when downgrading. Be sure to have a backup.

 

Here are some screendumps showing the difference:

 

3.10:

3.20:

 

Topo line is fixed in 3.30.

 

Corrected problems finding items when results contain characters with diacritic marks.

Corrected a problem on the Geocache Find page where a Find By Name search could potentially highlight a point past the first correct match.

Corrected an orientation problem on the Turn Preview Page if the route is calculated close to the first turn.

Corrected problems with the automatic closing feature of the Turn Preview Page when using German or Italian languages.

Corrected potential problems resulting from automatic closing of the keyboard.

Corrected potential problem where invalid characters could be entered into a waypoint comment.

Corrected potential display problems on the Altimeter Page barometer plot view.

Corrected contour line colors to increase visibility.

[+4x4 Trail Busters]

I have just downloaded the FW 3.30 and they have indeed upgraded the problems, especially with the topo lines. They are much more visible now. I just love Garmin, they respond soooo... quickly when there is a problem.

[+Firehouse16]

Time to yell.

 

WHAT ABOUT FIXING THE TRACK LOG PROBLEMS???????

 

I did a 13hr caching and hiding tour and when I got home over 1/2 of the track log for the trip was gone! With my legend it wouldn't even have come close to filling the track log completely, Frustrating! I don't why we can't have 50,000 track points or automatic rollover into a new track log.

 

I also don't like the compaction of data if you save the track log. We got 54mb's of room, let us use it better.

 

GARMIN READ THIS PLEASE!!!! it's my only complaint since you fixed my other one, thanks!

[+RocketMan]

I also don't like the compaction of data if you save the track log. We got 54mb's of room, let us use it better.

 

GARMIN READ THIS PLEASE!!!! it's my only complaint since you fixed my other one, thanks!

Does the data get compacted when you save the track or just truncated? In my experience, it seems like it gets truncated, losing part of the track. RM

[stevesisti]

I also don't like the compaction of data if you save the track log. We got 54mb's of room, let us use it better.

 

GARMIN READ THIS PLEASE!!!! it's my only complaint since you fixed my other one, thanks!

Does the data get compacted when you save the track or just truncated? In my experience, it seems like it gets truncated, losing part of the track. RM

I'm also interested in seeing revisions to the active track log vs the saved one. My understanding is that when you "save a track", it's a max of 500 points done by some internal algorithm or "logic" reduction from the 10,000 max of the active track...omitting points at straight sections while "protecting" the ones in "turns". If you hike 10 miles...using the "active" track you can theoretically lay a point every 5 ft or so. If you were to save the track and reuse it in the future as a "saved" track.....you will only see a point every 105ft or so. And then you are at the mercy of Garmins logic for "dropping" points during the saving process.

 

Seems a compromise in having 2 "active" track lengths of 10,000 points and 20 svaed of 500 would allow some people to get the maore "detailed" tracks they require. Personally I like recording and saving tracks for my favorite hiking areas...500 points on a long hike just isn't enough detail for me.

 

Truncating or "shortening" a track occurs in the "active" track when you fill the 10,000 max points and have "allow wrap" selected. Saving doesn't "truncate" per say, it just drops a hell of a lot of the points to fit it into the 500 max saved track allocation.

Edited May 8, 2004 by stevesisti

[+Firehouse16]

Oooh, also forgot. I wish Garmin would let us make full use of the notes window. It appears to be about 4 lines big, yet we can only use about 1-1/2 lines. Man if I had four lines I'd never need printouts again for the most part!

 

Garmin can you hear me!

[capt caper]

Time to yell.

 

WHAT ABOUT FIXING THE TRACK LOG PROBLEMS???????

 

I did a 13hr caching and hiding tour and when I got home over 1/2 of the track log for the trip was gone! With my legend it wouldn't even have come close to filling the track log completely, Frustrating! I don't why we can't have 50,000 track points or automatic rollover into a new track log.

 

I also don't like the compaction of data if you save the track log. We got 54mb's of room, let us use it better.

 

GARMIN READ THIS PLEASE!!!! it's my only complaint since you fixed my other one, thanks!

I feel the same way and asked in an tech email to Garmin to change it. The 76S I have would lay down a good detail of track points on the Most setting but still had points left from a long day hike of 10 hours or so. Auto mode is the best compared to every 10 feet or so.

 

Also I miss the 750 track log with 10 saved tracks. I would rather have a larger saved with fewer available. I have a laptop so changeing the 10 out would be easy.

[+Sergeant D]

I just got my 60CS today in the mail. It has version 3.00. Should I attempt the upgrade? I am upgrading from a GPS-III and I am not an advanced user. I just don't want the thing to do a white screen on me during the update and then have to be sent back. I would be pretty gutted if that happened.

 

Thoughts? Opinions? Advice?

 

Thanks, this board is great!

 

Sgt D

[+pecka]

You should definitely upgrade, ver 3.00 has some serious issues that were "polished" in the latest upgrade. It's also really easy, just make sure you have fresh pair of batteries in the unit and everything should be alright.

[4x5shooter]

Don't worry, updating the s/w is not difficult at all. After downloading the update file, you double click on it and it extracts everything into the "Garmin" folder on your computer.

 

Then plug in your GPSr to your computer, go to the "Garmin" folder and double click on the file named "updater," and the s/w is updated. No techie-type knowledge needed.

[jonavin]

Just make sure you close all the other applications before you begin, as instructed. I didn't do that and it failed to update. I had to take out the battery for it to "reboot". Restarted my computer and shutdown everythign that's runnign it updated with no problems.

 

As long as you follow the simple instructions you'll be fine.

[pitchblende]

I disagree with:

 

Improved map colors for contour lines.

 

When I use Topo (100K, not 24K), I can barely see some of the contour lines now.

Hmm.

Ditto. I use 24K Topo East, and the lines are so thin now that they're almost invisible. Was someone actually complaining about the topo lines before? I can't imagine why. I liked the thicker lines.

 

They are still pretty easy to see (and look nice) in "night" mode, because the background is black so they stand out more. But I rarely hike at night.

? - contour lines look OK with 3.20.

 

It was in 3.10 that you could barely see them.

[+TeeEff]

Corrected potential problem where invalid characters could be entered into a waypoint comment.

 

If this is the problem that I've been having, it still doesn't seem to work correctly. When I create a new street address waypoint, I put the address in the comments field. When I put in the street address and then hit the CR symbol, it goes to the next line and I put in the city. When I'm done editing however, a "J" is inserted where I put the CR and the last part of the street name runs together with the city.

 

For example, I entered:

 

4620 ALVARADO[CR]

SAN DIEGO

 

When I was done editing, it looked like this:

 

4620 ALVARADO

RDJSAN DIEGO

 

Anybody else with this problem?

[Moun10Bike]

? - contour lines look OK with 3.20.

 

It was in 3.10 that you could barely see them.

That was not the case with me. Contour lines were fine in 3.10, but almost invisible in 3.20. 3.30 has corrected the problem.

[Erskine]

The contour lines issue in 3.20 seemed to be apparent in "daytime" viewing mode. In nighttime view mode, it was fine, but impossible to see in daytime mode. Yes, they have fixed the problem, but still, the contour lines are easier to see in the nighttime mode or color choice.