TheWiz

That's good news...thanks for your reply. Steve

I've had it installed since April with no problems. Seems to fix several problems from previous revs. Well thank you for a fast reply. Though I've not found any problems before v4.10... Before I do an update, I'm just hoping they haven't removed any of the fine features I've enjoyed so much. Thanks agin Steve

Hi all...I'm looking for your thoughts on version 4.10 for the Garmin 60sc both Pros and Cons if any. Thanks Steve

roger that....and thank you all for the quick replies. Steve

Good feedback folks. Thank you. Along time ago though when I first bought the 60cs unit and was observing everyones' learning curve here, I seem to recall reading where you could enter the unit menu and select "Map Setup" while understanding you could only use **one onboard map resource at a time**...you could while out in the field select from a Topo, or City Select or whatever you purchased and felt inclined to fill up your 56mb of memory with. Is this not right and does this understanding of mine not include field selection of the marine POI? Thanks again, Steve

I'd like to reload the Marine POI that are now gone after a 60cs version 4.0 load and a 53mb load of maps from version 7.0 City Select N.A. I tried once to reload the marine POI and lost my City Select load of map regions. Did I not leave enough room for the POI when I loaded the 53mb of City Select Maps? I've seen this discussed before by folks who really know and just need a refresh from you if you feel inclined to respond. Thanks for your help Steve

This thread addresses the now resolved issue of "lockups during trackback navigation of a saved tracked" Found at fault was the failing function of any trip computer display field when "waypoint at destination" was being used in one of the fields. Please see http://forums.Groundspeak.com/GC/index.php...ic=72160&st=700 this thread for your general lockup questions. Steve

To my liaison at Garmin who helped get it done: Good job Joey...you got it done and before April 1st.... So, I'll be keeping my 60cs. Many thanks, Steve

Good news everyone...It appears that our lockup of the 60cs that required battery removal if you were using "Waypoint at destination" within any of the Trip Computer display fields during continuous display of the trip computer in active trackback navigation...has been fixed. It only took nine months of my persistant testing and reporting to Garmin to get it done but I'm glad to report that today you have a better working GPS than the one you bought with any version prior to 3.70 for the 60cs and I suppose the 60c or any related model you may own. You're welcome, Steve

Funny thing is, all my previous updates on this unit went off without a hitch. But I promptly killed mine with v4.00. Thankfully, Magellan is the kind of company that will make things right....they just sent me a brand spanking new unit for free after having had it for four years... Pretty awesome in my oppinion.

With exaustive testing on my part...I've found that NOT using "Waypoint at Destination" in any of the trip computer fields has stopped my lockup in trackback during active navigation with continuous display of the trip computer. So, my point...just for a goof, in case in your unit this might have anything to do with your type of lock up and until Garmin fixes this problem...drop "Waypoint at Destination" from what ever fields you might be using it and see if that stops your particular lockup. It would be worth a try cause it stopped my lockup type.

No

Well, here's Garmin's latest response: After talking with the one of the guys working with the 60 issues, and about this problem, he notified me that he has fixed the problem but was not able to release this fix in time for the beta version. Since this is just a beta version, complete versions are always release after the beta version, which will include this fix. I apologize about the previous response which said this fix was included in this beta versions when it wasn't. Am confident in the next complete version the fix will be there.

Could be that Trimble is.. the only real act in towm. Anyway, here's the response from Garmin: After talking with the one of the guys working with the 60 issues, and about this problem, he notified me that he has fixed the problem but was not able to release this fix in time for the beta version. Since this is just a beta version, complete versions are always release after the beta version, which will include this fix. I apologize about the previous response which said this fix was included in this beta versions when it wasn't. Am confident in the next complete version the fix will be there.

I would send it back ASAP.....Having purchased it LAST April (over 8 months ago) and NO geocache finds logged to date in your profile, that is a bum unit! I'm not a Geocacher...I need the unit for navigation but it seems the market wants Geocache toys and not real and reliable navigation gear anymore.

Yes, I too would like to know whats so hot about Garmin after all the %$#% I've been through with them. Garmin's response: Yes, this is the part within the update which fixed your " lock-up. Thanks Reply to Garmin: I hate to say it....but if that was the fix, it didn't work. I don't know what they think!.. they fixed. For what it's worth, here again in short is the problem we have in the 60cs: With v3.61Beta installed: Whole unit lockups still happen with "waypoint at destination" in a (trip computer) display field during active navigation in trackback with the trip computer display continuously on screen with no button pushing until lockup occurs. With that said, my next request is for an engineering contact that I can consult with directly on this matter. This is pretty much the last straw for me now having put up with this problem for a year in this unit and other copies of the 60cs I've used trying to get one that works. Considering your product involves the safety of the general public, (both the GPS user) and the (Non-User)... no Garmin system should ever be released for purchase until that design can be offered in a reliable form. My intent was to buy a navigation system, not a Fischer Price geocache toy. You will never know how many hours I have put into helping Product Support troubleshoot these issues and many others I have found in the unit that still go unfixed. This system is so far from ready to be released to the public and yet Garmin continues adding features to the 60cs while the basics don't work right. I can't even begin to tell you just how disgusted I am with Garmin products and the lack of effective support on the several occasions that I've needed it. Which...so happens to be why I've made no further moves to purchase any other overpriced products or accessories that Garmin offers. For this reason I will most likely be returning the unit for a full refund if this highly essential function is not fixed by April, the one year anniversary of my dealing with these buggy 60cs units. So that we can get to the bottom of this and a bunch of other 60cs problems, ASAP.... please pass along the necessary contact information for your engineering department where I can give them the straight poop on this and other issues with this system that remains unreliable.

Garmin's response: Yes, this is the part within the update which fixed your " lock-up. Thanks Reply to Garmin: I hate to say it....but if that was the fix, it didn't work. I don't know what they think!.. they fixed. For what it's worth, here again in short is the problem we have in the 60cs: With v3.61Beta installed: Whole unit lockups still happen with "waypoint at destination" in a (trip computer) display field during active navigation in trackback with the trip computer display continuously on screen with no button pushing until lockup occurs. With that said, my next request is for an engineering contact that I can consult with directly on this matter. This is pretty much the last straw for me now having put up with this problem for a year in this unit and other copies of the 60cs I've used trying to get one that works. Considering your product involves the safety of the general public, (both the GPS user) and the (Non-User)... no Garmin system should ever be released for purchase until that design can be offered in a reliable form. My intent was to buy a navigation system, not a Fischer Price geocache toy. You will never know how many hours I have put into helping Product Support troubleshoot these issues and many others I have found in the unit that still go unfixed. This system is so far from ready to be released to the public and yet Garmin continues adding features to the 60cs while the basics don't work right. I can't even begin to tell you just how disgusted I am with Garmin products and the lack of effective support on the several occasions that I've needed it. Which...so happens to be why I've made no further moves to purchase any other overpriced products or accessories that Garmin offers. For this reason I will most likely be returning the unit for a full refund if this highly essential function is not fixed by April, the one year anniversary of my dealing with these buggy 60cs units. So that we can get to the bottom of this and a bunch of other 60cs problems, ASAP.... please pass along the necessary contact information for your engineering department where I can give them the straight poop on this and other issues with this system that remains unreliable.

Garmin's response: Yes, this is the part within the update which fixed your " lock-up. Thanks Reply to Garmin: I hate to say it....but if that was the fix, it didn't work. I don't know what they think!.. they fixed. For what it's worth, here again in short is the problem we have in the 60cs: With v3.61Beta installed: Whole unit lockups still happen with "waypoint at destination" in a (trip computer) display field during active navigation in trackback with the trip computer display continuously on screen with no button pushing until lockup occurs. With that said, my next request is for an engineering contact that I can consult with directly on this matter. This is pretty much the last straw for me now having put up with this problem for a year in this unit and other copies of the 60cs I've used trying to get one that works. Considering your product involves the safety of the general public, (both the GPS user) and the (Non-User)... no Garmin system should ever be released for purchase until that design can be offered in a reliable form. My intent was to buy a navigation system, not a Fischer Price geocache toy. You will never know how many hours I have put into helping Product Support troubleshoot these issues and many others I have found in the unit that still go unfixed. This system is so far from ready to be released to the public and yet Garmin continues adding features to the 60cs while the basics don't work right. I can't even begin to tell you just how disgusted I am with Garmin products and the lack of effective support on the several occasions that I've needed it. Which...so happens to be why I've made no further moves to purchase any other overpriced products or accessories that Garmin offers. For this reason I will most likely be returning the unit for a full refund if this highly essential function is not fixed by April, the one year anniversary of my dealing with these buggy 60cs units. So that we can get to the bottom of this and a bunch of other 60cs problems, ASAP.... please pass along the necessary contact information for your engineering department where I can give them the straight poop on this and other issues with this system that remains unreliable.

Just sent to Garmin: See highlighted below: Was this a fix for our previously discussed unit lockup with "waypoint at destination" in a trip computer display field during active navigation in trackback with trip computer diplay continuously on screen undisterbed? Steve Changes made from version 3.60 to 3.61: Now report DEM map support to PC software. Fixed lockup that could happen when selecting a Tracback point. Fixed shutdown caused by viewing some Marine Light points. Fixed problem with Indonesian Southern Grid using wrong longitude

The v3.61 release does not appear to have addressed our problem, my unit is still doing it.

This is the "Lock Ups in TrackBack of saved tracks" thread. This thread is pertaining to the lock ups experienced when the trip computer display is on screen with a field on that display filled with a "waypoint at destination" setting during active trackback navigation. Please check other threads for discussion on your lockup type.....tnx

Well, I guess I'll load this Beta v3.61 and see if it fixed our original issue here. I should know if it is fixed and post my observation within a day or so....so stay tuned. Steve

You are right...very different problem, see my first and earlier entries here for understanding of the original thread. It appears we are getting off topic. TheWiz

WxGuesser Sounds like a different issue than we're discussing here. Please read my earlier notes on the questionable function of the our configuration being being troubleshot there and please let us know what you observe.

I've had three 60cs units and they all would lockup while in Trackback with "Waypoint at Destination" in any of the Trip Computer fields with the Trip Computer displayed uninterupted while navigating in excess of 15 minutes touching no buttons until no digits are actively updateing in that display.