GeoBobC

Indeed. It is under Additional Software for my 60c. Thanks for the tip. Seems like Garmin could have made it easier to find, but it is there.

I seached the Garmin website for an Ximage download. It was nowhere to be found on the menus (that I could see). I could only find it with the "Search" function. Is Garmin phasing out Ximage?

I'm on my third in less than two months. The first attempt to put one on my Garmin 60c was a disaster: bubble galore. They promptly sent me a second one with better installation instructions: put it in some water that has a few drops of shampoo or liquid soap. It worked like a charm: perfect fit, crystal clear. Alas, soon thereafter I took a good spill while running with the 60c and I got a nice scratch in the protector. They promptly sent me a third since the protectors have a lifetime warranty. When I removed the scratched protector, the 60c screen was unblemished so the protector did its job. All in all, I endorse the company: they (he?) have excellent and prompt service.

fyi the unit holds 1000 waypoints, not 500. According to Garmin the GPSMAP 60C holds: 50 reversible routes, 10,000 track points with tracBack® technology (navigate to any track point on the displayed map), and 1000 waypoints with additional graphical icons for location identification

Good point; scratch that one from the list of possibilities.

If the GPS has only a 2D lock it will display horizontal location correctly but could be off thousands of feet in altitude.

Unfortunately, no. The 12XL was designed in the pre "Selective Availability" days of 100 meter accuracy and did not anticipate this degree of precision. It's a great unit but is limited.

http://www.vehicle-tracking.com/products/3100.html

I just put two screen protectors on a Garmin 60c. The first result was a disaster. The second time I put some water in a bowl with a couple drops of shampoo added (liquid soap would work). I dunked the protector screen in the bowl, sprinkled some of the water on the 60c screen, and carefully placed the protector on the 60c screen. The protector "floated" on the 60c so I could precisely align it. After I pushed the water out with my fingers the screen was perfectly placed and flawless: not a single air bubble remained.

Very good topic. I've often wondered why different units perform differently. I've had two different Garmin units (of the same exact make: two 60c's, for example) side by side, and the specific satellites that each acquires are different. GPS A may pick up satellite 8 while GPS B does not, yet GPS B will acquire satellite 10, and GPS A will not. You would think that two units from the same manufacturer would acquire the same satellites. Garmin swears there is little or no difference, unit to unit. If that's true (I don't believe it is), then other factors contribute to the difference. Satellite configuration can. Even moving a unit a few inches (when there are obstacles to clear view) can change the reception significantly. I've not experienced a change due to battery power; others may have. It may be that the almanac data each unit has is different enough to contribute to the differences as well. I've heard that units "learn" where satellites were (when last powered on) and look for them in that location first. If two units look in different locations that could be a factor. It almost seems random at times but it cannot be.

For what it's worth: my experience with 3.90 is that it's as good or better than previous firmwares with respect to satellite performance. There are many variables that can influence accuracy/satellite performance. The most important one I've found is that the satellites are constantly moving. Checking accuracy at a benchmark spot by returning at a later time may not provide completely meaningful results unless conditions are identical, including satellite configuration. I've found the Trimble planning software to be quite helpful in determining this.

My experience with pre 3.90 versions was that the problem was more than not stopping/starting the active tracklog when satellite lock was lost. I experienced many cases where I had a satellite lock and could navigate, place waypoints, etc. However, the track log would not "drop" tracklog points consistently. For example, I could navigate to a corner, record a waypoint at the corner, turn 90 degrees to the right and see the map page accurately update. However, when the tracklog was downloaded to Mapsource there would be no track points at the corner. In some instances I had gaps of four minutes where no tracklog point was recorded even though I satellite lock throughout, and had track setup to record every 10 seconds. It seems like the tracklog points would not be recorded if the satellite signal was strong even though it was strong enough to navigate with. The good news is that 3.90 appears to have solved this, as expected and hoped. My hat is off to Garmin. Once again, they listened to their customers, acknowledged they erred, and corrected the problem.

I started this post (to which no one replied so maybe I'm one of the few that noticed it): http://forums.Groundspeak.com/GC/index.php...99012&hl=corner I contacted Garmin and they confirmed there was a problem. I was notified by Garmin this morning to expect an update; I assume this is it.

Has anyone experienced this? I have noticed in the last 30 to 60 days that many of the tracks recorded in my 60c have missing points at corners where a turn is made. The track log will record points before and after the corner but not at the corner. The GPS has (at least) three or four satellites and never loses satellite lock. Furthermore the map page correctly displays my location and the turn. I have track log detail turned to "more often". I recorded hundreds of logs previously but have just noticed this behavior recently. I am using firmware version 3.61. I contacted Garmin this morning and they claim to know about this, although it appears to be rare or infrequent. Here's the response I received: "I will reply again once I have a more solid answer than "there are plans to fix this in the next software update." Thanks again for your assistance and patience with this matter."

I am editing GPX files manually to create a track file that can be read into Mapsource (see sample line below). It appears the default datum for GPX files is WGS84 and the coordinate format is "hddd.dddd" Question: is there a way to use NAD27 coordinates within a GPX file, or must coordinates always be in WGS84? <trkpt lat="47.513217" lon="-122.078100"><time>2001-01-01T08:00:00Z</time></trkpt>

Yes; I purchased a 60c when they were first available. I returned it to Garmin within the first three months because the USB connector worked loose. Garmin replaced the USB connector on the GPS and I have not had trouble with it since.

"The fine print": COUPON EXCLUSIONS: • Valid for 20% off one full-price item. • Offer good for purchases made at REI stores, REI.com and by mail or phone. • Existing members must provide membership number and coupon code MEM25 at checkout to receive this discount. • If you’re not yet a member, you must have a membership in your shopping cart and enter coupon code MEM25 at checkout to receive this discount. • Offer not good on REI-OUTLET.com items; sale/clearance items (prices ending in $._9 or $._3); special orders; package discounts; REI gift cards or gift certificates; gift boxes; memberships or shop services. • Offer not good on REI Adventures trips; boats; emergency location transmitters; GPS receivers; 2-way radios; MP3 players; digital cameras or Oakley items. • Merchandise purchased with this discount is not eligible for the REI member refund. • Offer is nontransferable and not redeemable for cash. Discount may not be combined with any other offer. • Limit one coupon per member. • Offer good 5/6/05- 5/15/05.

It's tracks only I'm concerned about, so the waypoint limitation of 10 characters is not an issue. I also am not concerned about the loss of existing tracks. My primary usage is creating track log files externally, and then importing them into Mapsource. If I could easily find another way to manually create track log points in Mapsource, and convert them into an actual track, I would do it. What are the free 3rd party programs I can use to do this?

Removing the ability to handle PCX5 files is indeed a bad step in my opinion. I create tracklog files externally and import them via this capability. I really don't understand Garmin's rationale. Either (a) there are very few users of this functionality, so why bother removing it, or ( there are lots of users of this functionality, so why remove it? I'm sure there are other solutions, but why make us go search for it? I sent Garmin an email; perhaps some others with an interest in retaining this will also.

Is there a good source of information for predicting GPS satellite configurations at a certain location, at a specified date and time? I've noticed that from day-to-day the reception (and therefore accuracy) I get varies, and have assumed this is due to the satellites' positions relative to the earth constantly changing. If, for example, I knew that satellite reception would be better at 3:00 p.m than at 5:00 pm, then I could plan my outing accordingly to take advantage of the best reception times.

I have a 60c and a Map76. I vote for the 60 over the 76, although each has advantages and disadvantages. In spite of what you might read, there are some distinct and significant differences between the two operationally. In general, I believe the 76 has superior ease of use and much greater customization available. At just one example, on the 76 you can turn off the accuracy circle and the "bearing" (Goto) line, while on the 60 you cannot. Another example: you can set the distance units to "yards" on the 60, while on the 76 that option is not available. If you look at the "map setup" options on each, you will find the 76 has more options: you can customize what appears, and how it appears quite extensively on the 76. However, my 60 has superior satellite reception to my 76. I live in the NW and frequently use them in heavy tree cover. Just this past weekend, I took the 76 out for a run. It dropped satellite coverage 7 times; on this same trail I've never lost coverage with the 60. The 60c is a bit lighter and smaller, but seems "chunkier". Of course they're apples and oranges, but my 60 holds 56m of maps while my 76 only holds 8. Battery life on the 60 is superior. I like them both, but given a choice I'd take a 60 over a 76.

The satellite search algorithm was changed in version 3.70. It was intended to improve search capabilities for EGNOS (Europe) satellites, but does so at the expense of locating and locking onto WAAS satellites (US). http://forums.Groundspeak.com/GC/index.php?showtopic=94147

RE: "nothing about fixing the problem with the WAAS search for satellites" - step 1 is admitting there is a problem, which Garmin does not. They have stated this WAAS search behavior is by intent. Therefore we cannot expect a "fix" from Garmin unless enough individuals contact them to complain. I'm sticking to 3.61.

Best I've ever seen is 6. Worst is 283. Average between 20 and 30. I live in the NW with lots of trees.

If you have a Garmin 60c/60cs check out this post: http://forums.Groundspeak.com/GC/index.php...0entry1411520 Garmin made some changes in the 3.70 firmwares that are design to help with EGNOS signals, but can be at the expense of U.S. WAAS signals.