The 625 has major flaws:
First, the mileage meter uses the same circuitry to measure both run and bike mileage, so when you download your workouts, you get total mileage without separating running from cycling. It’s more important to know your running mileage in order to keep it within a proper range, whereas bike mileage can fluctuate more without leading to overuse injuries.
Second, the software doesn’t allow any sort of journal to be kept where you could break out weekly run mileage or make any other notations that would be useful to pull out on a weekly or monthly basis.
Third, you can’t use it in a tri, because you have to actually switch the recording mode off and back on again to change from bike to run. As if this weren’t bad enough, the foot pod shuts itself off after a short time with no communication with the watch, so even if you set it up on your run shoes, you have to shut off the watch, change to run mode (shifting through three modes to get there) and then switch on the foot pod. How much does that suck?
Fourth, the altitude function is never correct. You have to reset it almost daily, and then it still isn’t right. I’m standing next to the sign that says “elevation 72 feet,” so I set the watch to 72 feet. Then I switch it on and start to run and rotate through the functions to “alt” and it says 465 feet!! Wassup wif dat?
Finally, the damned things just aren’t all that reliable. I started my run yesterday, and here are the errors:
1- System showed a HR of 166 - which is 7 beats above my absolute max HR - for the first ten minutes. I was running LSD, so it was reading about 40-50 beats above my actual HR. It eventually settled down, but I need to watch my HR at the beginning of long runs, because I have a tendency to go out too fast, and the stupid thing is virtually NEVER correct early in a session.
2- After I got going and the number dropped into a realistic range, I could tell the HR displayed was now too low, but it didn’t get to the right number for nearly fifteen minutes. It is not uncommon for the HR number to “stick,” i.e., show the same number for a while until you move it up to the chest strap and then it changes (and you usually have to do this several times). If I’m seeing a number that’s lower than I want, I speed up and feel myself working harder and breathing harder, but the Polar is still showing the low number that I don’t want. Then suddenly it will wake up and show me that I’m now way above my desired HR… and pissed off to boot.
3- At the end of yesterday’s run, the watch indicated 16.25 miles. When I downloaded, it said the run was 15.9!! I’ve measured this course, and it IS 16.25.
4- It can’t even do it’s internal math correctly. If I run 1 mile in 8:00, it tells me (on the fly) that my pace is between 7:00 and 7:45, then after download, it would show the carefully measured 1 mile split as taking 8:00 at a 7:49 (or some such wrong number) pace. How hard is it to calculate 8÷1=8???
5- On download, if you click splits at .25 miles, it shows the first as .2 and the second as .3, iow it can’t handle the second decimal place.
I could go on, but you get the idea…