Rotareneg

On my 60Cx the top item on the Addresses find page is the region selection field, which defaults to the state you're in. Just move the cursor up from the city field and change the region to the one you need. And yes, past version 4 Metroguide won't autoroute on the GPS, but it still has addresses and everything else (I'm using MG v6 until CN 8 comes out.)

I think you deserve an award for most obfuscated post.

It's a bug that I've already reported to Garmin (and they've verified it.) If you're not using the default color scheme the GPS can crash when looking at tide stations.

This post has a link to a program that'll do that: http://forums.Groundspeak.com/GC/index.php...dpost&p=2036010

Mapsource puts a folder in My Documents called My Garmin. If I remember correctly you can just put the .bmp's you uploaded onto your 60C into that folder.

I used dlgv32 Pro. The aerial photo is from the Kansas GIS site. As far as the track deviating from the road... I'm using Metroguide v6 (waiting for CN v8 to come out before upgrading) and it didn't have a detailed map of the parking lot. Thus I had a hard time finding my way out and hit a couple curbs.

Blob on the right is electronics, was looking at DVDs. The mess on the left is groceries.

Here's a picture showing two visits to a Wal-Mart while carrying my 60Cx. The tracks were both recorded while set to auto with a "most often" interval. I've carried both my Legend and a Legend C in the same building (which has a metal roof with skylights) and the best they ever did was occasionally pick up a single SV when one was directly lined up with one skylights, they couldn't come close to having an actual fix. The 60Cx on the other hand kept a lock the entire time although clearly the accuracy suffered since most of the signals were reflected and/or defracted off/around the interior of the building. The picture resolution is 1 foot/pixel.

Nope, WAAS is fully functional. EGNOS, the European equivalent, is still in testing.

You'll have to reset the GPS to do that. First, read this: http://www.gpsinformation.org/dale/dgps.htm#waas In Europe you'll be using EGNOS, not WAAS, so you don't want 35. (both work the same, but broadcast information specific to the intended areas of reception.) Next, save any waypoints, routes, or tracks to your computer with whatever software you're comforatable with and make note of any settings you want to preserve as they'll all be wiped when you reset the GPS. When you're ready to reset turn the Legend off, and then hold down the page button, the up button, the "enter" button (the click stick) AND the power button. Hold them until the GPS turns on, in roughly 5 seconds. Now you'll need to let the GPS download the GPS and EGNOS almanacs. Make sure you turn WAAS/EGNOS back on the settings, then sit the GPS somewhere with a clear view of the sky, partiularly to the south, and let it sit for 15 minutes. If you watch the display the last two channels should begin scanning for SVs with numbers 32 and up after a little while. Assuming the EGNOS SVs are not in some test mode that the GPS is set to ignore, it should pick up 33 and continue scanning until it finds 37 or 44.

Since AOR-W (PRN 122, Garmin #35) began moving to the west the only time it's shown up for more than a few seconds on my 60Cx was the other day when it apparently went into a test or error mode for a while. At that time my Legend was also unable to get corrections, but has otherwise worked just fine with 35 in the same locations where the 60Cx acts like it can't see 35 at all. I think the problem is that the SiRFstarIII firmware doesn't support WAAS all that terribly well. Since 35 has stopped transmitting ranging data while it's being moved the receiver for some reason just ignores it when it should work like most other receivers and just download the corrections, which is what Garmin's other GPSs do, indicated by the signal bar never turning solid but still getting the differential corrections. Couldn't get my 60Cx to crash the way you said, but try this one if you're really bored (already reported to and verified by Garmin): Change the color scheme away from default, to emerald for example if it's daytime. Next, try to view a tide prediction station (use find, they're at the bottom.)

"The ranging codes broadcast by the satellites enable a GPS receiver to measure the transit time of the signals and thereby determine the range between each satellite and the receiver." The WAAS satellites send both the WAAS corrections and function as a "regular" GPS SV most of the time. Drat, can't delete my post that became superfluous after fizzy beat me by a minute...

The SV orbit and clock corrections will work, but since you're so far out of the intended area of use the ionosphere corrections will be useless at best.

Sounds like the infamous "jet lag" bug: http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=27491 I've noticed it do the same thing after shopping for a while in a building that blocked reception.

Anyone else managed to get custom icons to work with the POIs? I've got a nice little benchmark icon that works fine for waypoints, but not when uploaded with the POI loader. Also, in case anyone was wondering, there's no limit to the number of characters in the text fields: It's just limited to 2 lines of text for the title and 4 for the description. The font is proportional so you can fit in a whole heck of a lot more "l"s than "W"s. Also also, the forums new quick edit function's nifty.

My Legend has a similar configuration with one coil spring and three flat ones, while my 60Cx has the "leaf spring" contacts on all four ends.

The cut-off voltage is somewhere between 3.4 and 3.5. I'm tempted to open the thing up and see what DC to DC converters it's using on the various power inputs, but I'm not that brave/crazy/rich.

I left those lithium AA's sitting overnight and their voltage bounced back up to 1.744, too high to work in the 60Cx. I suspect both Garmin and Energizer are to blame: The discharge curves on Energizer's spec sheets for the E2 lithiums never show their voltage going over 1.6v, and Garmin apparently didn't do any more research than to look at that spec-sheet.

Been talking to Garmin about it, they had me try running the batteries for a little while in another device (I used my Legend) first and it worked fine. The Energizer E2 Lithium spec sheet discharge curves all start at 1.6v which should be fine in the 60Cx, but in reality they start at near 1.78v and need to be discharged slightly to get them down to their rated voltage. That was just something they had me check as an experiment, they're working on the problem now. Hopefully it's something that can be fixed with a firmware update.

Well, my 60Cx does not charge the batteries, I verified that with a multimeter.

Yep, same problem with my 60Cx, same batteries too.

You don't need to go to the waypoint find menu, just hit mark at any time and it'll open the new waypoint page which you can then change to the location you want.

Budbrew, not sure if you saw my post in the other thread, but I can verify the problem you're having with the lithium batteries: my 60Cx does the same thing with them.

Woah... has anyone else tried lithium batteries in their 60 "x" model? I just stuck a pair in my 60Cx and can confirm Budbrew's results: the unit beeps, the "GPSmap 60Cx" screen comes up for a moment, and then the screen fades out. The batteries are at 1.77v each, and they work perfect in my Legend. Energizer 2500 mAh NiMH batteries have been working fine in the 60Cx.

I just posted that 'cause some people seemed to be concerned about the accuracy (EPE) reported by the 60Cx being higher than they were used to with their older GPSr's. The trees didn't have leaves on either trip, and Trimble Planning shows that the PDOP was better when I was using the Legend C than the 60Cx.