8,101
edits
Changes
From Fellrnr.com, Running tips
no edit summary
{{DISPLAYTITLE:Garmin Fenix 2 Review}}
The {{Fenix 2}} combines the best features of the [[Garmin 910XT ]] and [[Garmin 620]], plus some extras and it could be [[Best Running Watch| a great running watch ]] if it were not for the [[GPS Accuracy]] problems. This is a remarkable watch, While Garmin have improved the accuracy of the Fenix 2 with a vast array of featuresfirmware upgrades, but its accuracy remains reasonably easy to usemediocre at best.
{| class="wikitable"
|- valign="top"
|[[File:Fenix2 Nav.jpg|none|thumb|200px|It is possible to load maps to the Fenix 2.]]
|}
* When combined with the new heart rate monitor strap, the Fenix 2 will show and record [[Cadence]], Vertical Oscillation (VO) and Ground Contact Time (GCT). This is fascinating data, but it's not clear how to interpret and use VO or GCT. This confusion is compounded by the way that a higher Cadence will result in a lower VO and lower GCT simply because of the faster turnover. The Fenix 2 has a display of Cadence, VO, and GCT that gives an indication of how good your current values are, but without the color display of the Garmin 620 this indicator is not as clear. The Fenix 2 can also display Cadence using the internal accelerometer.
* Like several other devices, the Fenix 2 displays [[Firstbeat| Training Effect]], an indicator of how hard or effective a training session is. In my unscientific trails, the [[Firstbeat| Training Effect]] on the Fenix 2 seems similar to the [[Garmin 620]], which is a change from the [[Garmin 610]]/[[Garmin 910XT]].
* The Fenix 2 builds on the [[Firstbeat| Training Effect]] to give an estimation of the [[Firstbeat| Recovery Time]] before the next workout. While this is only an estimation and there are no studies that evaluate it, there is the possibility that it might help prevent [[Overtraining]]. There is also a display of your recovery after the first mile or so of each run, which is again a nice idea. Sadly, if you miss the message, there does not appear to be a way of recalling it, nor does the Fenix 2 record this value.
* The Fenix 2 will cache the locations of the GPS satellites for the next few days, which will reduce the satellite acquisition time when travelling to a new location. In my usage the satellite acquisition was very rapid when cached, but if I'd not connected it for a while, it could be painfully slow to acquire a lock.
* You can add as many pages of displays as you want, which given how much the Fenix 2 can tell you, is great.
* The Fenix 2 can display alerts and text messages from a smartphone. I suspect this is of more use if you're wearing the Fenix 2 as an ordinary watch, rather than when running.
* The Fenix 2 includes an internal accelerometer to give you an idea of pace and distance while running on a treadmill without a footpod. I found it was too far out to be of any use, giving a display that was off by 1-3 minutes/mile. A lot will depend on your running style and how you use a treadmill.
* You need to have the new "HRM Run" for the running dynamics features. It will display Heart Rate and calculate [[Firstbeat| Training Effect]] with the older Garmin HRM, but not Ground Contact Time or Vertical Oscillation.
* The display on the Fenix 2 is a little harder to read than most other watches. The backlight compounds the problem as it is a dull red glow.
=GPS Accuracy Issues=
The Fenix 2 has some well-known [[GPS Accuracy]] issues that are mostly shared with the [[Garmin 620]], which both use the MediaTek GPS chipset. I've seen three types of problem with the Fenix 2:
# Generally mediocre performance, though this obviously varies. Occasionally the Fenix 2 will be quite good, as you'd expect from a random level of error.
# The Fenix 2 records the right shape track, but offset by some distance. This does not look like a typical accuracy problem that would manifest itself randomly.
# Occasionally the Fenix 2 will report "lost satellite reception", which may well be a problem with the clock on the Fenix 2.
==Is It Just Some Watches?==
Some people are quite happy with the accuracy of their Fenix 2 or [[Garmin 620]], prompting speculation that this is a quality control issue and the problems only effect some devices. I don't believe this is the case for a number of reasons.
# I've tested 5 devices (2x Fenix 2,3x 620) that exhibit the problem. It seems remarkably unlikely that 5 out of 5 devices would have the problem. The problems with these devices seem remarkably similar, though only the Fenix 2 has the catastrophic 'lost satellite reception' problem.
# The severity of the problem depends on the situation. Running a fairly straight course with a wide open view of the sky is likely to give pretty good results.
# Awareness of the problem will depend on testing methodology. Few users gather enough data to be statistically significant, or run on a course that's certified. Even running on a certified course, it's tough to hit the tangents perfectly unless you're a front runner.
=What's Missing=
While I don't consider missing features as 'cons', it's worth understanding the features that are missing compared with other watches. However, the only feature that's missing from the Fenix 2 is the ability to download apps, rather like a smartphone.
{{BuyAmazon|AZID=B00IKNDDNK|AZN=Garmin Fenix 2}}
=Comparison Table=
{{:Best Running Watch-table}}
