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

Running alert delay

Hi there,

I’ve just got a 255 Music and am loving it. However one thing I was wondering if just how the alerts work for running. I’ve got pace range alerts set up for running, as well as a heart rate zone alert. I find that the watch takes about 30 seconds of being in the slower pace before it tells me my pace is slow. Is this normal/is there any way to change this?

Furthermore it seems as though once I’m ‘stuck’ in whatever range I’m not meant to be in (pace/heart rate) it won’t keep buzzing me until the next lap. Is this how it’s meant to work? Just wondering if there’s a way to change the threshold for the alert, particularly for pace. Thanks

0 Bitti over 1 year ago

I've haven't really studied it in depth, but at least on my Forerunner 965 there seems to be quite a lot of "intelligence" in the alerts. When you get an alert seems to depend on not only if you are out of zone, but also how much out and how fast you are moving towards / away from the zone. If you just briefly get out of zone, there is no alert (which is good for uphills, gps errors etc.). And if you stay out of zone, further alerts seem to depend on how you pace/hr changes. Which can also be good if you decide to run a recovery step faster/slower than suggested, then you get one or two initial alerts, but then none as long as your pace/hr stays constant.

0 Pratik over 1 year ago

I have Forerunner 255s Music and upgraded to Epix Pro gen 2 a month ago. It's same with the Epix too! So, I think they do take time around 5 seconds sometimes more. It's really frustrating when you try to run in very narrow target pace range for a training and almost 70-80% of the training duration it's off because of these delays on display and delayed audible alerts