Kenjobi

The problem whereby the x series Garmins do not always regain a fix after losing GPS signals may have been solved in the latest GPS firmware patch (version 2.5) on the 60CSx. It does not seem possible to download this patch directly from the Gamin website, however, if you use their WebUpdater software, it will install the new patch although you may have to run it twice. You can download WebUpdater here: WebUpdater To find out what version of GPS firmware you are running select Menu, Menu, Setup, Enter, System, Enter, Menu, Software Version, Enter. Both the unit software and the GPS firmware are listed. If you have don't have GPS version 2.5, then it is worth updating (The versions may be different on the 76 series and I've not been able to test this). Once the WebUpdater has done it's thing, you should see GPS software version 2.5. Upon restart, it appears that the unit has no idea where it is or what time it is so it takes a little while with a good clear view of the sky before it gets itself in order. I've run many tests to try and get the unit to not regain a fix after losing all GPS signals and it has never failed. One time it did appear that it was not going to work but it seems now that the unit recognises the condition and resets the GPS hardware itself rather than you having to do this. Note that this so called 'tunnel' problem only ever occurred if you had WAAS/EGNOS enabled. Added Edit I notice there's more info about the GPS firmware version with similar instructions on this thread: http://forums.Groundspeak.com/GC/index.php?showtopic=132173

I think you might have the answer here 8mmag. I never saw the reported problems with elevation until a fortnight or so ago. I figured it might be a problem with the 2.62 beta firmware so I rolled back to 2.60 but the errors returned after a short time. On reflection, I was letting the track log fill and it was set to autowrap. I have not let the track log fill since that time and the problem has not returned. This sounds like a purely software related issue and should be an easy fix for Garmin. Fingers crossed eh?

The above picture confirms that the 60CSx does show D's on the signal strength bars when a WAAS/EGNOS fix is available. I get them with EGNOS where I live and I have also seen them with WAAS when I was last in the States. However, I have never seen the estimated accuracy figure reduce once the WAAS/EGNOS fix is established and I have never seen the signal bar for the WAAS/EGNOS satellites go solid. This thread confirms for me that until Garmin fix the WAAS/EGNOS problems, it is better to disable WAAS/EGNOS on the x units. Note also that the problem whereby the unit fails to regain a fix after losing a signal such as when going through a tunnel never occurs if you disable WAAS/EGNOS.

Unfortunately, the "not regaining fix after tunnels" problem still persists with this beta release. However, turning off WAAS/EGNOS stops the problem occurring. More info in the post below: http://forums.Groundspeak.com/GC/index.php?showtopic=125398

Thanks for the feedback on this one. This morning, I found a solution for this problem which I've just posted in a new topic at: http://forums.Groundspeak.com/GC/index.php?showtopic=125398

I recently posted a topic regarding the fact that my GPSMAP60CSx does not always regain fixes after completely losing sight of the GPS satellites. For example, after travelling through tunnels. From other posts it appears that all the SirfStar III based Garmins are affected by this bug. The post can be read at: http://forums.Groundspeak.com/GC/index.php?showtopic=125226 I'm pleased to say that I've found a 'solution' for this and it simply involves disabling WAAS/EGNOS on the system setup screen. After doing this, I cannot get the problem to occur. If you want to test this for yourselves, you could do the same thing that I did which was to enable WAAS/EGNOS, select the satellite screen and get a fix. The fix does not need to include a WAAS/EGNOS satellite (in fact, I was unable to get a WAAS/EGNOS fix during my tests). Next, cover the unit completely with aluminium foil, thereby totally blocking the GPS signals. After about 30 seconds, remove the aluminium foil. The unit should be displaying the Lost Satellite Signal message. 4 out of 5 times on my unit, the fix does not return. Instead, the satellites that were included in the previous fix briefly appear then disappear. Sometimes this behaviour repeats itself every 5 seconds or so, other times, they just disappear from the screen and never return. The only solution at this point is to reboot or disable/enable the GPS receiver with menu options. Repeating the test with WAAS/EGNOS disabled I could never get the problem to occur. I tried about 20 times. My conclusion is that the problem lies somewhere within the Sirfstar III chipset/firmware which may explain why Garmin have not been very forthcoming with information regarding this problem. I imagine that discussions are taking place between the two companies to find a resolution. It would be interesting to know if anyone trying the above can not get the problem to occur. This could indicate that there are different hardware versions out there. I hope the above is helpful to other owners of the x model Garmins that have experienced this problem. It was really causing me some difficulties and the device is so sensitive and accurate without WAAS/EGNOS that I don't really need it for the most part.

I've owned a 60CSx for over a month now and generally I'm very happy with it. The ability to find and lock onto satellites in difficult conditions is exceptional and way ahead of any other Garmin units that I've owned (45XL, 12XL, eMap). However, where I live is very mountainous and there are many fully enclosed tunnels. More often than not, the unit fails to regain a fix after travelling through these. The same issue has been mentioned in other posts in this forum and appears to relate to all of the new 76 and 60 models with the Sirfstar III chipset. It's some consolation to know that I am not alone and this gives me hope that a fix will be forthcoming. The only solutions available at the moment are to switch the unit off and on again or to disable the GPS receiver circuits and re-enable them via menu options on the main satellite screen. The latter being rather dangerous to do while driving. More importantly, it simply shouldn't happen in the first place! Yesterday, I upgraded to the latest firmware version (2.6) and, even though it was not mentioned in the release notes, I hoped that the problem would have been quietly resolved. Alas no! The problem persists. I emailed Garmin asking when they would do something about it over a week ago but have had no answer. I'm wondering if anyone else had a definite response from Garmin stating when they will resolve this most fundamental flaw in an otherwise great product? Also, it would be interesting to know if anybody with the units mentioned has never experienced this problem after driving through long (more than 30 seconds) tunnels. Note that it does not happen every time but typically 3 out of 5 times. I imagine that the same effect could be achieved by letting the unit get a fix then putting it into an enclosed tin box for a minute or so but I've not tried this.