Changes

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

Garmin 620

7,320 bytes added, 18:57, 10 May 2017
m
comment: batch update
{{DISPLAYTITLE:Garmin 620 Review}}
[[File:Garmin620.jpg|thumb|right|200px|The {{Garmin 620}} , showing the display of Cadence, Vertical Oscillation and Ground Contact Time. Note that the display is wonderful running watchcolor, but I found the colors muted and not always easy to distinguish. It]]There's a lot to like in the {{Garmin 620}}; it's much smaller than many [[Best Running Watch| comparable watches]] and its interface is nice to use. How well the 620 will suit you will depend a long on your needs, so for a simple evaluation of a GPS watch, I look at how well it can answer some basic questions:* '''How far did I run?''' This is the most basic question, and the 620 has somewhat reasonable, but it packs in more features while retaining not great usabilityGPS accuracy, so its estimate of how far you've run needs to be treated with a little caution. It* '''How fast am I running?''s my top pick for most runners, though if ' Knowing how fast you're on running can be a tight budgetnice to know, there are other contender's such as 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 [[Garmin 310XTPace From A Footpod]] or while getting all other data from GPS, the 620 can't answer this question. The mediocre GPS accuracy exacerbates this issue, and I've seen the pace estimate wildly wrong on the [[Suunto Ambit2 R]] that offer better value for money620. The 620 would be my top pick for marathon runners, but it lacks the ability to show your current pace from a Footpod while using GPS for everything else. Having run many marathons, I firmly believe that this is a killer feature, as accurate pacing is essential for a good marathon performance. * '''Where am I? '''The 620 has no navigation features. If you're lost, the 620 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. Not only does the 620 get [[Cadence]] from a [[Footpod]], it will also get it from the Garmin Run Heart Rate monitor. There is also support for Cadence from the internal accelerometer, though I find that's not as accurate. The Cadence alerts are especially useful for keeping you on track. The 620 is not a good choice for ultrarunners, as its battery life is too short.See [[File:Garmin620Best Running Watch#Watches for Ultrarunning| Watches for Ultrarunning]] for more details.jpg|thumb|none{{BuyAmazon|200pxAZID=B00FBYYC90|The {{AZN=Garmin 620}}, showing the display of Cadence, Vertical Oscillation and Ground Contact Time. Note that the display is color, but I found the colors muted and not always easy to distinguish. ]]
=Garmin 620 Pros=
* With the updated firmware, the GPS accuracy is reasonable. It's not as good as the [[Polar V800]] or some of the other watches, but it's okay for most usage.
* The 620 is small and light, but the display is quite legible for its size. I find it much easier to read than either the [[Garmin 610]], [[Suunto Ambit2 R]] or the [[Garmin 10]]. (It's a lot better than the [[Garmin Fenix 2]].
* Like the Fenix 2, the 620 will show and record [[Cadence]], Vertical Oscillation (VO) and Ground Contact Time (GCT). The 620 has a nice display of Cadence, VO, and GCT that gives a color coded indication of how well you're doing.
* The 620 will provide alerts when a metric is out of range. The alert for [[Cadence]] is really useful and one of my favorite features of the 620. Before the firmware fix for GPS accuracy I'd wear the 620 just for the Cadence alert and use another watch for tracking distance.
* Like several other devices, the 620 displays [[Firstbeat| Training Effect]], an indicator of how hard or effective a training session is.
* The 620 includes an estimation of the [[Firstbeat| Recovery Time]] before the next workout, just like the Fenix 2.
* The 620 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.
* The touchscreen works better than any other I've tried while running.
* There is a prediction of your [[VO2max|V̇O<sub>2</sub>max]], which worked well for me, but I would not rely on its accuracy.
* The battery life is short for ultramarathons, but it is fine for the most runners.
* You need to have the new HRM for the new features. It will display Heart Rate and calculate [[Firstbeat| Training Effect]] with the older Garmin HRM, but not Ground Contact Time or Vertical Oscillation.
=GPS Accuracy Issues=The Garmin 620 had some well-known [[GPS Accuracy]] issues, but this has been resolved with a firmware update. * The 620 does surprisingly well going under the bridge, an indication that it is not having excessive problems with reacquisition. * On the out-and-back turnaround the 620 does a little better than I'd expect for its overall rating. * Running in a straight line is a fairly easy task for most GPS watches, and the 620 does well, beating many watches that have higher overall accuracy. * I not had any issues with the 620 acquiring or maintaining the GPS signal, unlike some other devices. {| class="wikitable" |- valign="top"|[[File:BridgeGarmin 620 (3.30).jpg|none|thumb|x300px| You can see the 620 does a reasonable job most of the time. There are a number of tracks where it gets a little lost, and there are some very minor issues with the 620 reacquiring the signal after the bridge. It does poorly around the twisty section, cutting the corners too much due to smoothing. Interestingly, it does a better with the sharp turn seen on the right side of the diagram. 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 read indicating poor accuracy, and the lap markers as blue dots.)]]|[[File:BridgeGarmin 620 (pre-v3.30).jpg|none|thumb|x300px| The earlier version of the firmware does rather horribly. The tracks are widely spaced and the 620 often gets rather lost. (This diagram has tracks color coded with green indicating good accuracy through to read indicating poor accuracy, and the lap markers as blue dots.)]]|- valign="top"|[[File:AccuracyGarmin 620 (3.30).jpg|none|thumb|x300px| This close up section of a zigzag shows the 620 tracking okay, though here again we see the wide spacing of the tracks. There are more green lines than red, and the 620 is coping reasonably well. (This diagram has tracks color coded with green indicating good accuracy through to read indicating poor accuracy, and the lap markers as blue dots.)]]|[[File:AccuracyGarmin 620 (pre-v3.30).jpg|none|thumb|x300px| The earlier firmware shows how badly the 620 was doing. The lines are almost noise and the lap markers are widely scattered. (This diagram has tracks color coded with green indicating good accuracy through to read indicating poor accuracy, and the lap markers as blue dots.)]]|- valign="top"|[[File:ZigZagGarmin 620 (3.30).jpg|none|thumb|x300px| Here you can see the 620 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. (This image has the tracks color-coded for direction, with green coming from the right, blue from the left.)]]|[[File:ZigZagGarmin 620 (pre-v3.30).jpg|none|thumb|x300px| With the earlier version of the firmware the behavior is pretty much lost in the noise. It does seem like the green tracks are closer to the trail, but it's hard to be sure. (This image has the tracks color-coded for direction, with green coming from the right, blue from the left.)]]|}=Resolving GPS Accuracy =If you are having GPS accuracy issues, then the following suggestions may help.
# Make sure your firmware is up to date. The 620 actually has two firmware installations, one for the watch functionality, and one for the GPS. The GPS firmware needs to be at 3.30 or above.
# Synchronize the 620 with the Garmin software to update the EPO data which is used to improve GPS startup time.
# Leave the 620 in "ready to go" mode with a good view of the sky for at least 20 minutes. There is information (the almanac) that can take 12.5 minutes under ideal conditions to download from the satellites. In theory the 620 should get all of the satellite data from the EPO file, but the almanac might help.
# If none of these steps work, do a factory reset.
=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.
* '''Altimeter. '''GPS is far less accurate vertically than horizontally, so a barometric altimeter can provide a much better idea of your ascent and descent. It can also be useful for navigation if you're ascending or descending a mountain. In some races I've been far more interested in how much ascent is left rather than the distance to the top.
* '''Navigation.''' The navigation capabilities are useful if there is a risk of getting lost. I've made good use of this feature when running in an unfamiliar city, or when running remote trails.
* '''Downloadable Apps'''. Smart watches have got is used to the idea of a device that can be extended with new functionality, and this concept is being introduced to running watches.
* '''Extended battery life'''. Some porches can extend the battery life by turning the GPS reception off for short periods. This can dramatically reduce GPS accuracy, but it's a useful trade-off for some ultramarathons.
* '''Graphs'''. Instead of simply displaying a numeric value for things like heart rate, some watches will display a graph of the value over time, giving you a sense of how things are progressing.
* '''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.
=Visual Comparison=
{| class="wikitable"
|- valign="top"
|[[File:Garmin 620-top.JPG|none|thumb|150px|Garmin 620 top]]
|[[File:Garmin 620-side.JPG|none|thumb|150px|Garmin 620 side]]
|[[File:Suunto Ambit2-top.JPG|none|thumb|150px|Suunto Ambit2 top]]
|[[File:Suunto Ambit2-side.JPG|none|thumb|150px|Suunto Ambit2 side]]
|- valign="top"
|[[File:Suunto Ambit3-top.JPG|none|thumb|150px|Suunto Ambit3 top]]
|[[File:Suunto Ambit3-side.JPG|none|thumb|150px|Suunto Ambit3 side]]
|[[File:Polar V800-top.JPG|none|thumb|150px|Polar V800 top]]
|[[File:Polar V800-side.JPG|none|thumb|150px|Polar V800 side]]
|- valign="top"
|[[File:TomTom Cardio Runner-top.JPG|none|thumb|150px|TomTom Cardio Runner top]]
|[[File:TomTom Cardio Runner-side.JPG|none|thumb|150px|TomTom Cardio Runner side]]
|[[File:Garmin Epix-top.JPG|none|thumb|150px|Garmin Epix top]]
|[[File:Garmin Epix-side.JPG|none|thumb|150px|Garmin Epix side]]
|- valign="top"
|[[File:Garmin 920XT-top.JPG|none|thumb|150px|Garmin 920XT top]]
|[[File:Garmin 920XT-side.JPG|none|thumb|150px|Garmin 920XT side]]
|[[File:Leikr 1-top.JPG|none|thumb|150px|Leikr 1 top]]
|[[File:Leikr 1-side.JPG|none|thumb|150px|Leikr 1 side]]
|}
=Comparison Table=
{{:Best Running Watch-table}}
=Teardown=
There's a nice teardown of the Garmin 220 (the lower end 620) on [http://www.microcontrollertips.com/teardown-garmin-forerunner-220-sport-watch-heart-monitor/ microcontrollertips.com].

Navigation menu