iamasmith

And BaseCamp lets you Geotag photos from a track that has timing that you can correlate to to your photo timing (you can adjust the offset). But you will need a Garmin unit and a topo product to be able to use it.

Of course it's quite a different process but I assumed that updates would be like the Oregon updates (which I have done a LOT of ), Those updates carry both GPS Firmware and Unit Software updates and downgrading also downgrades both. You say this isn't the case with the 60CSx typically? (this is the first upgrade I have seen for it since I bought it). Anyway, I think even if they fix this update I think I'll wait for people to confirm that there aren't any losses of precision in the new versions. I think, since 3.70 is SO good that we should probably keep a close eye on comparing newer versions.

Argh... site threw an error and I had multiple posts. Sorry.

...

...

Did you run the updater twice. The second time updates the chipset FW? If so, did you back off the chipset software too. Both updates may be needed so the two programs are compatible with each other. Hmmm... good point. When I installed 3.70 I thought it would back off the GPS firmware too. That's showing version 3.00 though. Can't remember if that was at an earlier rev with 3.70. You believe running the 3.70 upgrade again will back that down too?

I also had to revert my 60CSx to 3.70. After upgrading to 3.90 I had immediate problems with the uniting hanging during the power down beep when I pressed the power button. Resulting in a neverending beeeeeeeeeeeeeeeeee.... sound - had to remove the batteries to get round that. Also the unit started just freezing up randomly whilst I was using it. Did the update twice from webupdater from the mac, once from web updater on a pc, once as a manual update on a pc and did a couple of factory resets to make sure there wasn't some stuffed config information. Reverted to 3.70 and the unit works perfectly again.

Oh my, it lets you Geotag photos from the Track Playback... I have to try that out tomorrow!

Awesome, I couldn't get any 3D under Fusion because it needs 1.3 OpenGL and Fusion only provides 1.2

"BaseCamp is compatible on both PC and Mac computers. Beginning in the first quarter of 2009, the utility will ship with all new TOPO U.S. 24K DVD and TOPO U.S. 100K DVD products. For those who currently own TOPO U.S. 2008, BaseCamp will be available for a free download at www.garmin.com at the end of the first quarter 2009. For unit compatibility and more information, visit www.garmin.com" Here's hoping too! (using .NET isn't encouraging though.. I would certainly not have put .NET development at the top of my list of technologies if I wanted to share code between platforms) I DID notice that if you go for download ID 4436 rather than 4435 it goes for the same file. Perhaps that's in as a placeholder for the Mac version... But again all pure speculation.

Umm, I'm hoping they aren't going to call that a feature without putting in an option to disable it

On the battery thing... I'm sure being avid cachers that you won't have noticed this I, however, have had a couple of fallow weeks and I have noticed that on a couple of occasions I power on the unit that was near to full charge and it is in the red. I'm wondering if something isn't being turned off properly when you power down on 2.93. Anyone else notice this?

Sounds like you answered the question that I was going to ask you about your trip in the last bit. If you were going to a cold climate then you aren't going to get spectacular performance out of NiMH. Lithium (NOT rechargeable Lithium Ions) will give the best performance in cold climates. Regards, -Andy

Sure, I had the same thought. That's why I went for a 300 because I wanted the Altimeter and Compass as well. Each product is going to be a sweet spot for somebody. Regards, -Andy

These can all also go on the card. Actually I don't think Wherigo cartridges do run from a card. They certainly wouldn't on my 300 with 2.80 which was the last time I played one, they had to go into the units internal flash. Regards, -Andy

Be aware that if you go into Highway view on a 60CSx it just shows the road that you are navigating on, no text etc. I never found it to be particularly useful to try to actually drive in this mode. If you are going to use the standard map view or the route directions screen then it is fine. The Oregon (and almost certainly the Colorado) has an Automotive mode for the map that shows you a 3D Satnav style map which is just the same as the Automotive units, albeit you can't turn it landscape. Regards, -Andy

I have had crashes on Wherigo using older firmware (no surprises there but still an incident) and on 2.85 I had some crashes when I first loaded City Nav onto it and started plotting routes to POIs in Monaco etc to try it out. My view is crashes will be sorted out. Garmin DOES tend to get their units stable at least. There are issues around screen brightness though but the touch screen for Geocaching and general convenience? That's the killer bit, it is sooo convenient, if I want extra ruggedness like on a dive boat and stuffed in the bag with my gear I take my 60CSx. The only downsides that I can see to the Oregon in a final state when all the wrinkles are sorted out are.. * Screen readability (I use mine a lot at night and it isn't an issue, in daylight it is workable... new generation OLED displays or at least reflective would have been nice). * Screen fragility (not really an issue in most cases.. I didn't buy it for extreme use). * Lack of Antenna Jack (this BUGS me, I may not have needed it yet but I really wish that it had the option). I knew about all of these things before I bought it, I had just about convinced myself to buy a Colorado but hinting by Garmin support along the lines of.... 'oh, I would get an Oregon, they seem much more popular' when I asked about accuracy and the fact that I thought the text input looked so clunky on the Oregon swung my at the last minute. It was one of those 51% committed one way when I hit Submit Order but I'm glad I went that way. Regards, -Andy

You mean you aren't clipping the carabiner to the chest strap of your rucksack ala the promotional video? Seriously though, it isn't great is it. The only thing they could do is change the sound though. Actually the first time I tried it I thought I had a duff unit - there was road noise and I had the unit pressed up to my ear and still couldn't hear it when I walked in range of the waypoint. Regards, -Andy

I'm just stating the obvious of course but when you said you had it set to follow roads, you did mean that you had configured the 60CSx to do Road Navigation as well as MapSource didn't you? Otherwise it will just plot a straight line between your waypoints. Regards, -Andy

Put in 2.86 today. Went to a place with good reception. Got 2m on accurancy at best. But no WAAS/EGNOS. It was listening for #33, #37 and #39 but no EGNOS info seemed to be processed. My good ole MAP60CS on the other hand locked in on #33 and displayed the D on most of the birds fairly quick. I am testing right now and I see a good signal on #33, but no D's. Now going for #37, no signal. And #38 and #39 and #40. No good. Back to #33, good signal. Accurancy improved but still no D's. If this improves I will report back Oslo, Norway Yeah, one thing I have noted is that you still have to have a solid green bar from the EGNOS bird before any corrections start showing up. This seems to take about 5 mins sometimes. I don't think the unit has the ability to fast lock onto these birds like the regular constellation (stores ~3 days of ephemeris apparently to do this - that's augmented by the Cartesio chipset AFAIK). If the signal from the WAAS bird drops to zero and you lose the white bar whilst it is loading then you can start counting 5 mins again. The 60CSx didn't have this issue at all. It may just be the way it has to be of course with the Cartesio models. I'm wondering if the Nuvis with this chipset are the same.

This is related to the Oregon. I have TOPO GB v2 and City Nav Europe on that product and I have a 60CSx with just TOPO GB. The accuracy circle issue isn't related to the right product being missing from the Oregon it is that the Oregon doesn't support it.

As an owner of an Oregon 300 and a 60CSx, I tell you that the single thing that I miss most about the 60CSx when out caching is the accuracy confidence circle. I actually think I saw it when I got the unit with 2.20 software but it has been removed and people have said that Garmin's official line was that it was confusing people...? Actually I think there are still plenty of options that could 'confuse people' on the Oregon such as map spheroid, datum (don't tell me what they are I do know ). I really miss this feature, it was a really nice indicator when you were getting close to GZ. Having the option to put the data field showing accuracy on the screen just isn't as nice as showing a circle around you... Even my iPhone does that!, Joe Public MUST be getting used to seeing this feature and understanding what it is. Surely Garmin should be offering at least an option to enable it? What do you think folks? -Andy

Getting vastly improved accuracy and getting EGNOS outside my house which I never got on my Oregon before (my 60CSx always locked really quick there). I only ever had 2 EGNOS locks on bird #33, never on #37 until now. It seems the GPS rev update has made quite a difference for me at least. Regards, -Andy

And if you don't have Stuffit then you can use the unzip command under terminal to extract the files from this self extract ZIP package. Regards, -Andy

I found this comment in another website interesting, and have tried without success to alter it!! Can you suggest a method of achieving it? Here are the screenshots of the options and grid lines. . Were the four options available in v2.8? That menu option set looks like the 'Setup Heading' screen. That is just for the compass heading though.