This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Workout pace alerts not working correctly

Non solar 12.23.

Doing 1 mile intervals and had the pace set to a range but alerts seems to be picking up my current pace to alert if slow or fast instead of the overall step pace.

End up spending time looking at my watch to see how I'm going instead of listening for a beep.

Anyone else have this issue?

I'm using workouts created before I got 955 and just edited to suit the interval

  • Has anyone managed to get an average pace alert to work on a workout?

  • Also interested in a solution to this.  First run with 955 today and getting same experience.  All previous Garmins 910/735 have used average lap pace for the alerts.

  • This would be really useful especially given that the FR955's instant pace is both very coarse (only to 5 seconds) and very lagging. Not sure why it's so coarse given that multiband GPS is dead-on accurate. Strangely enough I find that GAP (grade adjusted pace) which is also an instant pace field is pretty indicative of my effort level going up and down hills.

  • I've always set my alert to 1 min for current pace and HR. I don't notice any lag.

    The average and lap pace are the ones that are supposed to be lagging.

  • I think I might be confused Sweat smile

    What I think OP is asking about is a pace range alert for average pace instead of instantaneous pace for a workout step. In GC it looks like you can only set a pace range alert for instantaneous pace. My comment about instant pace lagging is with regards to the instant pace data field seeming to take some time to update in response to large changes in speed (e.g. if I'm running downhill after just completing an uphill the pace seems to take 20-30 seconds to "catch up"). It's not as noticeable if you're just getting periodic updates to instant pace and not watching that value otherwise.

    It could be also that on the alert the instant pace is recalculated at that moment so it always seems accurate.

    The average/lap pace fields have a resolution of 1 second so they can actually update more rapidly than instant pace at the beginning of a lap.