| |
Main
Date: 21 Aug 2006 23:56:59
From: lyle
Subject: garmin 305
|
I upgraded through prosportwatches.com from Garmin 101 to the 305.
While the distances appear to be extremely accurate, the current Pace
is horrible. I run 8:30/ml consistently and pace shows 10:30, 11:00,
etc. I have to do the calculations in my head from each mile from the
time. Anyone else have this problem? Solution
Thanks
Lyle Goldstein
|
|
| |
Date: 23 Aug 2006 01:40:50
From: Phil M.
Subject: Re: garmin 305
|
lgoldstein27@nyc.rr.com wrote:
> I upgraded through prosportwatches.com from Garmin 101 to the 305.
> While the distances appear to be extremely accurate, the current Pace
> is horrible. I run 8:30/ml consistently and pace shows 10:30, 11:00,
> etc. I have to do the calculations in my head from each mile from the
> time. Anyone else have this problem? Solution
I wouldn't mess with current pace. If you set your autolap to 1 mile or
less and just look at the current average for that lap, then you'll get
much more accurate readings. Also, you might want to post this to
http://forums.motionbased.com for a more complete answer to this and any
other Forerenner questions.
--
Phil M.
|
| |
Date: 22 Aug 2006 07:46:35
From: Newsdude
Subject: Re: garmin 305
|
I use the 205 and get fairly accurate current pace readings (and if
anything, mine occasionally seem a little fast). Did you turn on the pace-
smoothing function? That might help.
"lyle" <lgoldstein27@nyc.rr.com > wrote in news:1156229819.318837.300980
@i3g2000cwc.googlegroups.com:
> I upgraded through prosportwatches.com from Garmin 101 to the 305.
> While the distances appear to be extremely accurate, the current Pace
> is horrible. I run 8:30/ml consistently and pace shows 10:30, 11:00,
> etc. I have to do the calculations in my head from each mile from the
> time. Anyone else have this problem? Solution
>
> Thanks
>
> Lyle Goldstein
>
>
|
| |
Date: 04 Sep 2006 10:14:51
From: Mark
Subject: Re: garmin 305
|
lyle wrote:
> I upgraded through prosportwatches.com from Garmin 101 to the 305.
> While the distances appear to be extremely accurate, the current Pace
> is horrible. I run 8:30/ml consistently and pace shows 10:30, 11:00,
> etc. I have to do the calculations in my head from each mile from the
> time. Anyone else have this problem? Solution
I have plenty of trouble with the pace readings on my Garmin 301, and I
find pace smoothing just makes it worse. I usually give myself a 30
seconds/mi range to move in, from my target pace to 30 seconds/mi faster
than my target pace. My Garmin is beeping at me constantly. Sharp
corners especially send it wailing because, to the Garmin, it looks like
you are suddenly moving much slower.
Pace smoothing, for me at least, makes the problem worse. I liken it to
the slinky effect you see in bumper to bumper traffic, or for the
military types, the slinky effect you get in marching formations: The
Garmin screams at you that you are moving too slow, so you up the pace a
bit. But pace smoothing averages results which effectively dampens
changes. The pace you see on the Garmin is not necessarily your real
pace. The next thing you know, the bloody thing is screeching at you for
going too fast.
Maybe it's just me!! But I leave pace smoothing off. Well, I don't think
you can turn it off. But I leave it on "least" or whatever the minimal
setting it.
Mark
|
| |
Date: 04 Sep 2006 20:04:41
From: steve common
Subject: Re: garmin 305
|
"lyle" <lgoldstein27@nyc.rr.com > wrote:
>While the distances appear to be extremely accurate, the current Pace
>is horrible. I run 8:30/ml consistently and pace shows 10:30, 11:00,
>etc. I have to do the calculations in my head from each mile from the
>time. Anyone else have this problem? Solution
Solution = do not use the functions/displays which use instantaneous pace.
The "average pace on current/previous lap" fields are much more useful.
I configured the beast to display that value instead of "current pace".
Thanks for reminding me I have one :-) (it's in for repairs).
|
|
