Changes

From Fellrnr.com, Running tips
Jump to: navigation, search

Garmin 225

3,606 bytes removed, 09:57, 11 August 2017
m
no edit summary
{{DISPLAYTITLE:Garmin 225 Review}}
I've tested several optical heart rate monitors and found them rather ineffective, so I came to the [[File:Garmin 225-top.JPG|thumb|right|300px|The {{Garmin 225}} with low expectations, showing the display of Heart Rate from its Optical Heart Rate Sensor. To my surprise, ]]The big difference between the 225 worked much better than and the competition, though there are still compromises in [[Garmin 620]] is the 225addition of [[Optical Heart Rate Monitoring]] (OHRM). I's optical HRMve found that OHRM is not ready for real world usage. I'm also a little disappointed in the way Garmin has crippled the 225 's software compared with the 620, and I'm looking forward to trying out the replacement 235. The older 225 doesn't have Garmin''I would recommend not buying the 225 until the 235 is released and tested. I think the 235 will be a big improvement over the 225, with things like s [[Connect IQ]], but even if you decide the 225 which is for youanother significant shortcoming, the release of the 235 and I'd argue it should drop the price be a major factor in your choice of the 225watches.''' A simple rating of the Garmin 225 can be based on how well they can answer some For a more fundamental look, there are four basic questions:* '''How far did I run?''' This is the most basic question, and the 225 has somewhat reasonable, but not great rather poor GPS accuracy, so its estimate of how far you've run needs to be treated with a little quite a bit of caution. * '''How fast am I running?''' Knowing how fast you're running can be a nice to know, or it can be vital for your training or race performance. Because of the nature of GPS, watches that rely on GPS signal alone tend to have serious problems with current pace. Without the ability to display current [[Pace From A Footpod]] while getting all other data from GPS, the 225 can't answer this question. The mediocre poor GPS accuracy exacerbates this issue, and I've seen the pace estimate wildly wrong on the 225. The 225 would be my top pick for marathon runners, but I firmly believe that this is a killer feature, as accurate pacing is essential for a good marathon performance. (I've some slight hope that Garmin will add this feature in with a firmware update, as they have to a number of their newer watches.)
* '''Where am I? '''The 225 has no navigation features. If you're lost, the 225 won't be much help.
* '''What's my cadence? '''[[Cadence]]''' '''is one of the most critical and often overlooked aspects of running. If you get your Cadence right, many other things naturally fall into place. There is support for Cadence from the internal accelerometer, though I find that's not as accurate as the [[Footpod]] which it supports.
The 225 is not a good choice for ultrarunners, as its battery life is too short. See [[ShoesBest Running Watch#Watches for Ultrarunning| Watches for Ultrarunning]] for more details. (Turning off the optical heart rate monitor only increases the battery life a couple of hours.)[[File:Garmin 225-top.JPG|thumb|none|200px|The {{Garmin 225}}, showing the display of Heart Rate from its Optical Heart Rate Sensor.]]=Optical Heart Rate Monitoring=No one likes to wear a chest strap, and it can be particularly annoying for ladies as it can interfere with support clothing. This makes the idea of an optical heart rate monitor that uses the changes in capillary fill under the watch quite attractive, so I focused on this functionality. * Optical HRM is never going to be as accurate as a chest strap. The chest strap measures the electrical impulses from the heart and can measure the time between each beat. This allows for analysis of [[Heart Rate Variability]], which can provide some interesting insight, such as [[FirstbeatBuyAmazon| Training Effect]]. If you need that level of accuracy, optical HRM is not there and I doubt if it will ever get there. On the other hand, if you're after a good approximation of your heart rate, then optical holds more promise. * One of the challenges for optical HRM is that movement can move the blood in the capillaries and make measurement tricky. I've found that the 225 works best with the strap tight; I have to tighten the strap two notches past where I'd normally consider the watch to be 'comfortably tight'. This tightness is enough that I can clearly see the imprint of the watch in my wrist when I take it off after a run. However, I have low body fat and skinny wrists (~9 inches/15cm), so those with a little more soft tissue might find it easier. * Because blood flow to the skin is reduced when you're cold, I found it helped to keep my arms warm. In cold weather I used an arm warmer with the thumb hole placed so I could peak at the display. In really cold weather I'd normally wear my watch over the first layers of insulation, which obviously won't work with an optical HRM. This means the 225 will have to be covered most of the time in cold weather, which is annoying at best. * The Garmin 225 will give a HR reading even if it can't get a reasonable signal. I'd much rather it gave a clear indication that it was having problems so I could adjust things. I generally know roughly what my HR should be for a given situation, so I can rapidly work out when it's confused, but you might find it harder. * If you're still reading this, and you're okay with the compromises I've mentioned, then I found the 225 to do much better than the other optical HRM systems I've tried. I had remarkably few instances of the 225 reading wildly too high or too low. The graph below compares the 225 with two chest strap based systems. {| classAZID="wikitable" B00XKRWTUE|- valignAZN="top"|[[File:Garmin 225 Warmth.jpg|none|thumb|x200px|I found it helped to keep the 225 warm for improved heart rate accuracy, but in colder conditions this becomes essential to prevent frostbite.]]|[[File:Garmin 225 Imprint.jpg|none|thumb|x200px|I had to have the Garmin 225 tight enough that it left a clear imprint when I took it off.]]|[[File:Garmin 225 Confused.jpg|none|thumb|x200px|I'd rather the Garmin 225 said it couldn't find a Heart Rate rather than guessing. Here you can see it getting a Heart Rate from black cloth.]] |}==Heart Rate Comparison with Chest Straps==[[File:Garmin225 Comparison.jpg|none|thumb|500px|Comparison of the Garmin 225 with the [[Garmin Epix]] and the [[Suunto Ambit 2]].]]The diagram above is a comparison of the Garmin 225 in red with the [[Garmin Epix]] in blue and the [[Suunto Ambit 2]] with the Polar H7 strap in green. * The workout is a [[High Intensity Interval Training]] session, something that tends to highlight problems in [[Heart Rate]] monitoring due to the rapid changes in intensity. This is a WinTab workout, using 20 seconds all out, 10 seconds recovery, repeated eight times. (This is often confused with a [[Tabata]] workout, but a Tabata uses a specific intensity of 170% of the workload at [[VO2max|V̇O<sub>2</sub>max]], not 'all out'.) The chart does not show the prior [[Warmup]] and short recovery time to rest the various monitors. * The Wintab is from 1:00 to 5:00 on the chart, followed by a [[Cooldown]] from 5:00 to 14:00. There is then a gentle increase in intensity (going up a hill) from 14:00 to 16:00. After running as gently as possible from 16:00 to 19:00 there is a ~1 minute higher intensity period followed by a short walk to the end. * The red arrow shows the rapid rise in heart rate from rest to maximum intensity. You can see that the 225 lags slightly behind the other two systems, but this is not excessive. * The blue arrow highlights a slight drop in the HR reading from the 225. I've noticed this periodically, where the 225 becomes just slightly confused. One of the reasons I wore both a Garmin and Polar HRM is to verify that the fault lies with the 225, not the chest strap. These periods of confusion are generally fairly short and the different is not huge. In other optical systems, and with the 225 if it's not clamped down hard, they will often get wildly confused, reading wildly low (~90 instead of ~130), or wildly high (~170 instead of ~130). * The green arrow shows another lag in response, and because the period of high intensity is so short, the 225 never reads the highest reading of that segment. If you relied on the 225, you'd see a heart rate of 10 beats lower than actually occurred. Overall, I'm impressed with the Garmin 225's optical system, and I think it's well worth considering. You need to be prepared to live with the compromises, but for many, the chest strap has its own issues, including chaffing and the strange looks you sometimes get. }
=Garmin 225 Pros=
* The Optical Heart Rate monitoring is more effective than other implementations I've tried. (See above for details.)
* The GPS accuracy of the 225 is reasonable. It's not as good as the [[Polar V800]] or some of the other watches, but it's okay for most usage. Not surprisingly, the accuracy is about the same as the similar [[Garmin 620]].
* The 225 is small and light, but the display is quite legible for its size. The display is color, but really this isn't much use on the 225. There is a display of HR with a color indicator of zone, but that's more of a novelty than a useful feature.
* The 225 has some basic activity monitoring built in, which is not as good as the [[Basis Activity Tracker]] but it's nice to have.
=Garmin 225 Cons=
* The Optical HRM is not suitable for real world usage, but it's on a par with other systems. See [[Optical Heart Rate Monitoring]] for more details.
* A lot of the missing features from the [[Garmin 620]] are from Garmin crippling the software rather than hardware limitations. I always like to see a company make the best product they can for a given price point, rather than using software crippling. Things like only displaying 3 data fields, or limiting the number of screens of data on the 225 is needlessly annoying. It's particularly bad when you want the optical heart rate monitoring, and can't get the advanced features on the 620.
* There is no way of displaying your current pace from the [[Footpod]] while using GPS for overall distance and course. While the 225 now has good GPS accuracy, it is not sufficient to give useful current pace information. For situations where pacing is critical, such as running a marathon, a Footpod works better. (Earlier versions of the firmware would always display the pace and distance from the Footpod when it's connected, but this was fixed in a recent update.)
* The 225 includes an internal accelerometer to give you an idea of pace and distance while running on a treadmill without a footpod, but I found it was too far out to be of any use. A lot will depend on your running style and how you use a treadmill.
* The battery life is short for ultramarathons, but it is fine for the most runners.
=GPS Accuracy =
The Garmin 225 does rather poorly for GPS accuracy, and rather worse than the similar [[Garmin 620]]. I was expecting it to be using the same chipset and antenna as the 620, which I would expect to give similar GPS performance. It's hard to be sure of the underlying chipset without disassembly, but the problem could also be due to a change in the antenna due to the extra optical HRM.
{| class="wikitable"
|- valign="top"
|[[File:BridgeGarmin 225.jpg|none|thumb|x300px| You can see the 225 has rather mediocre accuracy, and is rather worse than the similar [[Garmin 620]]. It does badly around the twisty section, cutting the corners too much due to smoothing. It does a little better with the sharp turn seen on the right side of the diagram. It gets a little lost going under the bridge on occasion, but that's not too much of an issue. The lap markers in blue are more widely dispersed than they would be with a better device. (This diagram has tracks color coded with green indicating good accuracy through to red indicating poor accuracy, and the lap markers as blue dots.)]]
|- valign="top"
|[[File:AccuracyGarmin 225.jpg|none|thumb|x300px| This close up section of a zigzag shows the 225 tracking okay most of the time, but a disturbing number of the tracks are poor. (This diagram has tracks color coded with green indicating good accuracy through to red indicating poor accuracy, and the lap markers as blue dots.)]]
|- valign="top"
|[[File:ZigZagGarmin 225.jpg|none|thumb|x300px| Here you can see the 225 displaying the typical GPS behavior with the tracks that have the green lines shifted slightly down and to the left, blue up and to the right. This is less marked that other devices, but you can see the pattern. You can also see the lap markers shifted based on direction. (This image has the tracks color-coded for direction, with green coming from the right, blue from the left.)]]
|}
=What's Missing=
While I don't consider these missing features as 'cons', it's worth understanding the features that are missing compared with other watches.
* '''Alerts'''. Some watches will alert you when a metric is out of range. The alert for [[Cadence]] is really useful and one of my favorite features.
* '''Web Configuration'''. Some watches allow you to setup the configuration via a web site, and then download your changes. This is vastly easier than fiddling with the watch.
{{BuyAmazon|AZID=B00XKRWTUE|AZN=Garmin 225}}
=Visual Comparison=
{| class="wikitable"
|[[File:Polar V800-side.JPG|none|thumb|150px|Polar V800 side]]
|}
=Teardown=
There's a nice teardown of the Garmin 220 (the 225 without the OHRM) on [http://www.microcontrollertips.com/teardown-garmin-forerunner-220-sport-watch-heart-monitor/ microcontrollertips.com].
=Comparison Table=
{{:Best Running Watch-table}}

Navigation menu