Hi, 235 is my first running watch - bought it to help with training towards a marathon. So I don't have huge experience in running generally or with running watches either.
I've found the pace alerts really useful (alert when too fast or too slow) but I find that they're behaving strangely in a couple of ways. (I had a quick look for other threads about this but couldn't see any obvious ones.)
1. abrupt spikes when an autolap is triggered
My pace alert for a long run is: too fast if faster than 5:20/km; too slow if slower than 5:50/km.
Normally I'll trundle along at about 5:25/km - 5:30/km, though sometimes I'll end up running a bit quicker than that without realising it.
When I hit an autolap (set to 1km), it'll record my time for the lap as expected.
However the alerts then usually go a bit nuts - after auto-lap has given me lap-time, I'll then often immediately get an alert saying I'm too fast (say 4:55/km), and immediately then get another one saying I'm too slow (say 6:10/km). This sometimes happens a few times before it settles down.
2. slow alert suddenly triggered when I haven't significantly changed pace
This happened to me twice when I was out yesterday. Again I'd be running along at about 5:30/km or so. Then the watch started to tell me I was running much more slowly, e.g. 6:40/km, 7:10/km.
I paused and then resumed the workout (kept running), and it seemed to settle down and track my pace properly again. As mentioned, this happened twice.
I imagine it's got something to do with how the lap pace is averaged/updated, but I do find it strange/disruptive.
Has anyone else had experience of this? Anything I can do to reduce/minimise this?
Cheers,
Michael