<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>VeloDramatic &#187; garmin</title>
	<atom:link href="http://www.velodramatic.com/archives/tag/garmin/feed" rel="self" type="application/rss+xml" />
	<link>http://www.velodramatic.com</link>
	<description></description>
	<lastBuildDate>Thu, 09 Feb 2012 21:37:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Garmin 500 Mount Fails</title>
		<link>http://www.velodramatic.com/archives/4963</link>
		<comments>http://www.velodramatic.com/archives/4963#comments</comments>
		<pubDate>Mon, 22 Feb 2010 17:00:08 +0000</pubDate>
		<dc:creator>Velodramatic</dc:creator>
				<category><![CDATA[Product Reviews]]></category>
		<category><![CDATA[garmin]]></category>

		<guid isPermaLink="false">http://www.velodramatic.com/?p=4963</guid>
		<description><![CDATA[


UPDATE: Garmin contacted me today and wants to see the unit and mount. I'm happy to see them react proactively to the issue, and hope this is an isolated problem with an explanation. More information as and when I get it.

A few weeks back I wrote that the Garmin 500 had a new twist and [...]]]></description>
			<content:encoded><![CDATA[<!--start _raw-->
<img src="http://images.velodramatic.com/garmin500/garmin500-5.jpg" width="500" height="367" alt="Piece of the Garmin 500 broken off in the mount" style="display:block; border:none; margin-bottom:10px !important;" />

<p><strong>UPDATE: Garmin contacted me today and wants to see the unit and mount. I'm happy to see them react proactively to the issue, and hope this is an isolated problem with an explanation. More information as and when I get it.</strong></p>

<p>A few weeks back I wrote that the Garmin 500 had a new twist and lock mount, perhaps as a reaction to the problems that some users experienced with the slide-and-latch mechanics of its predecessors. Out riding yesterday, my Garmin 500 broke free from the mount and skittered behind me as I crossed a six lane road. I stopped quickly,  laid the bike down and ran back to retrieve the unit (<em>advantage mtb shoes</em>) before cross traffic ran it over. Expecting it had just released, I was dismayed to find that pieces of the unit itself had cracked off in the mount (<em>see photo showing one of the pieces</em>). Examining the 500 closely revealed the plastic molded pins on the back of the Garmin unit itself had broken away. Nothing struck the Garmin during the ride, and the road I was riding on was perfectly smooth. <em>I'm baffled.</em></p>

<img src="http://images.velodramatic.com/garmin500/garmin500-6.jpg" width="500" height="367" alt="The pins molded into the back of the Garmin 500 have broken away" style="display:block; border:none; margin-bottom:10px !important;" />

<p>I suppose I'll have to send the unit back to Garmin, which I'll do this week. This is the first time Garmin hardware has failed me, ironically with the new mounting mechanism. Perhaps the old one, wasn't so bad after all.</p>

<!--end _raw-->]]></content:encoded>
			<wfw:commentRss>http://www.velodramatic.com/archives/4963/feed</wfw:commentRss>
		<slash:comments>31</slash:comments>
		</item>
		<item>
		<title>Going by the Numbers &#8211; Garmin Edge 500</title>
		<link>http://www.velodramatic.com/archives/4772</link>
		<comments>http://www.velodramatic.com/archives/4772#comments</comments>
		<pubDate>Mon, 25 Jan 2010 06:17:34 +0000</pubDate>
		<dc:creator>Velodramatic</dc:creator>
				<category><![CDATA[Product Reviews]]></category>
		<category><![CDATA[Road Bike Gear]]></category>
		<category><![CDATA[connect]]></category>
		<category><![CDATA[edge 500]]></category>
		<category><![CDATA[garmin]]></category>

		<guid isPermaLink="false">http://www.velodramatic.com/?p=4772</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[

<img src="http://images.velodramatic.com/garmin500/garmin500-2.jpg" width="550" height="367" alt="The new Garmin 500 fronts the improved Garmin Connect; but it still has problems" style="display:block; border:none; margin-bottom:10px !important;" />

<p>Seems like our whole lives go by the numbers. We start off measuring ourselves against the kitchen door and it never stops. </p>

<p>Grades, scoreboards, girls' telephone numbers, salary, mortgage, it all adds up. Cyclists may be among the most chronic counters. Logging mileage is just the tip of the iceberg... calories, feet of climbing, power, heart rate, cadence all are fodder for increasingly sophisticated computers. Garmin's latest, the Edge 500, takes a fresh look at the data we love to collect.</p>

<p>No doubt getting input from the men in Argyle, Garmin engineers slimmed the unit down. It weighs just 57g compared to my comparatively portly Edge 305 at 79g. There's a new spin-and-lock mount, secured to bar or stem with o-rings. It feels very secure and that's going to be well received by those who experienced problems with the slide-and-latch mechanism of its predecessors (<em>I never ejected my unit while on the road, but I did snap the tabbed latch off one mount</em>). </p>

<p>Cosmetically, the white and silver unit is prominently trimmed in Garmin blue... that's great... IF YOU HAVE A BLUE BIKE. I'd rather they'd stuck with a neutral scheme: black, white, silver or better yet, provide optional colored bezels. Did no one tell them; we obsess about the total look of our rides?</p>

<p><em>Even when we're not riding, we're still counting. Last week a combination of weather and work had me go five days between rides, the longest I've gone on foot in three years. Around day four paranoia kicked in and I started thinking this is how you stop riding for good... so it didn't matter that Thursday was horrible out, I was riding no matter what. Some records are NOT meant to be broken.</em></p>

<p>The Edge 305 survived a trip through our washing machine so I had no doubts about the 500's ability to survive the elements and an accidental drop (<em>or two</em>). Garmin hardware is tough.</p>

<p>Two years ago I complained bitterly about the sorry state of Garmin's Connect software. After acquiring the once nimble MotionBased startup, Garmin seemed intent on hobbling backwards with a slow, buggy and functionally inferior service. I'm happy to report that Connect has improved (<em>at least this afternoon</em>).</p>

<h4>Connect Rates a B</h4>
<p>Software is the great differentiator. Get it right, the iPhone comes to mind, and success follows. Get it wrong, and a line of dissatisfied customers will soon stretch around the internet block actively sharing their bad experiences with everyone who'll listen. Connect looks cleaner. The dashboard tab displays the last 5 uploaded activities, and the most recent one in detail. The Activities tab shows a 20-record table with quick edit functionality that's passable but hardly efficient. Curiously it provides edit capability for "event type" which is not displayed in the table itself. During the upload process two of my activities never completed processing (with a checkmark indicator) but nevertheless appeared in the table. That kind of disconnect doesn't foster confidence, and there's more.</p>

<h4>Firmware Web Updater Rates a D</h4>
<p>Logging back in while putting this post together I noticed that there was a firmware update for the Edge 500 (v2.1). After downloading and installing a 20+MB web updater tool, the update was downloaded and applied. Unfortunately, here's where things didn't work so well. The updater carrier finished its role by indicating the device would restart. It never did by itself. Twenty minutes later, I restarted the device and the update was validated but in the process all my screen settings, bike info and history were erased. <strong>So much for that great comeback, some of the old inconsistencies remain.</strong> Solution: Connect should store all of these customized settings and refresh them on the device in situations like this. <em>There will have to be a pretty compelling reason to update the firmware for me to risk having that happen again.</em></p>
 
<p>It's tough to count on software but without it we'd be back to scribbling in notebooks. That might be an option I'd consider, if I could read my own handwriting.</p> 

]]></content:encoded>
			<wfw:commentRss>http://www.velodramatic.com/archives/4772/feed</wfw:commentRss>
		<slash:comments>15</slash:comments>
		</item>
	</channel>
</rss>

