Top positive review
1,173 people found this helpful
This 405 user loves his new 110
on August 16, 2010
I have used a Garmin 405 to track my weekend long runs for about 1.5 years. Previously I owned the Garmin 305. I'm using the 110 with with my 405 chest strap (saved me $50).
The 110 does everything I do with my 405 in a significantly smaller, lighter form factor with a superior GPS chip (in theory, to be proven).
REASONS WHY I LIKE MY NEW 110 BETTER THAN MY OLD 405:
* It's smaller and less bulky than the 405, looks and feels like a regular watch, and wraps snugly around my smallish wrist.
* I don't have to fiddle around with the temperamental 405 touch-(in)sensitive bezel.
* The displayed numbers for distance/hr/time/pace are bigger on the 110 than the 405, so easier for me to read on the run.
* There are fewer menus to navigate.
* Like the 405, GPS locking and accuracy works just fine, even under trees (more below).
* Like the 405, I can set the auto-lap to increment every 1 mile (other distances available).
* The 110 displays everything I want to track during and after my run.
- Elapsed distance (for run), Elapsed time (for run), Current HR, Average pace (for current lap), Last lap pace (displayed automatically for a few seconds after each lap), Average HR (for run), Average pace (for run). Average HR and pace for the entire run are show under "History" at the end of my run.
* To make this tangible, I can glance at the watch to see that so far I've run 2.1 miles in 21 minutes, my current HR is 160, my pace for the current mile (mile 3) is 9:56 and my pace for the last lap (mile 2) was 10:01. At the end of my run, I click through to "History" and see that my average HR for the entire run was 162bpm and my average pace was 9:54 minute miles. For me, currently, all I care about is keeping my HR in the 160-170bpm range (your range will probably be different) while trying to keep my pace under 10:00. In general, I suspect most runners will have the same requirements: Track your current HR to keep it within a target range while attempting to meet or beat a per-mile pace goal.
* The 110 has a longer battery life
* I never used the other 405 features like courses, virtual partner, etc. Ironically, I "customized" the 405 screens to pretty much do what the 110 displays by default (but cannot be changes).
WHAT'S ALL THE FUSS ABOUT "CURRENT PACE"?
I guess some runners want to know the pace they are running RIGHT NOW. Think of it as their instantaneous pace - kinda like what a car speedometer gives you. Some folks call it "current pace" but that can be confusing when you also have average pace for the current mile, so let's call current pace the "right-now" pace. Unlike the 405, the 110 does not give you your right-now pace. Instead you get your average pace for the current lap. If your auto-lap is set to 1 mile (the default setting) then you'll see your average pace for the current mile. I for one don't need right-now pace. Since I'm trying to hit per-mile pace goals I want to see my average pace for the current mile. If I'm trying to hit a 10:00 pace for the current mile, and I start out too slow, the 110 will tell me my average pace for the current mile is slower, let's say 11:00, and I know I need to run the rest of the mile faster to bring my average pace for the current mile down from 11:00 to my target pace of 10:00. As I speed up, my average pace for the current mile will slowly drop from 11:00 to 10:00. Bottom line: Right-now pace doesn't help me hit per-mile pace goals so I could care less if it's "missing" from the 110. If all you are doing is trying to hit per-mile pace goals (eg run a 10:00 miles) then you'll be just fine with the 110.
ANY GPS ISSUES?
Not for me. Check out connect dot garmin dot com slash activity slash 44862992 and you'll see my test walk/run. Click to view the map in "Satellite" mode and notice that most of my test walk was under thick tree cover.