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

GPS lag: wrong slow pace reported during Interval training transitions

I set up an interval training and uploaded to the watch.

So I have a slow pace interval, then a fast pace interval. Cool.

Just a few seconds before the fast pace interval kick in I switch my running speed and reach the faster speed but the FR955 GPS is lagging and 10 (something) seconds into the fast pace interval warns me that I'm running at a slow pace, but ... it's just wrong.

After a few seconds warn me again: "you're going the right speed".

GPS antenna is set to: automatic.

I think there are multiple possible approach to the issue.

FR955 could push on GPS precision during interval training transitions or... just wait a few seconds more before warning.

  • I believe Garmin changed the way of reporting speed a while ago. It looks like the watch shows an average pace of the last 15 secs or so. That is why you always run too slow at the beginning of a speed interval. It used to be better, but now it is annoying. Personally I start speeding up 10 secs before the actual change from slow to fast. That manages the wrong notifications a bit. But also in long runs a a certain pace, it takes about 10-15 seconds before the watch shows an increase in speed. Result of that is that I frequently overshoot the pace, so I have to slow down again. And after 10 sec I find out I am going to slow again. The delay between actual speed and speed shown is too big to be reliable.

  • Second this ( changed rounding).

    Actually they change from time to time (I remember a battle at 225-230/630 era).

    It is always a trade-off between "jumping" pace and rounded pace. 

    Personally I am totally happy. I use single run screen and set 5 sec rounding. 

    If you want fast and reliable pace changes, get foot pod and set speed to be taken from it (but you need to calibrate it to your pace it know a correction for this pace)

  • I can understand what's behind this behavior which you can call "bug", but ... again this is something easy to fix on the software side.

    Giving false warning to the user is not what you should want.