Related
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

Forerunner 745 pace issue

L Peters
over 3 years ago

Is anyone else having issues with the 'live' pace (minutes per mile), shown by the watch while running? Mine was spot-on when I first got it, but now it's all over the place when under just the lightest of tree cover. The recorded result seems accurate, but that's not much help when I'm trying to keep a certain pace while running. I tried a Fenix prior and returned it as the pace shown while running was so far off. Am guessing this might be a GPS issue, anyone else seeing this? I'm finding it quite frustrating.

Thank you in advance for any thoughts!

  • 0 over 3 years ago in reply to Donal

    Sorry to hear this, not sure how that effects the pace shown when the person next to you isn't having the same issue. On one of the runs over the weekend (rained for the first part of the run), I felt the pace was just slow overall. Ran with the dog, so know there were slow portions, but it didn't seem to reflect the times when we were moving along.

    However, after updating the watch yesterday, it did seem a bit better on my run this morning. There was some variance, but it appeared to be much less. Not sure if I just happened to have a better signal, or if the issue is being addressed.

  • 0 over 3 years ago

    My new 745 has the same problem. I guess that the every second update of the pace doesn'r help the stability of the readings

  • 0 over 3 years ago in reply to Prosperot

    Bummer, sorry to hear. Seems ridiculous for a device at this price point. Hope they solve it soon.

  • 0 over 3 years ago

    Did anyone yet gave 6.02 a try to see if it solves this problem?

  • 0 over 3 years ago

    Today's run, including the river path. As on previous runs the first pass shows no real drop in pace, where as the second pass shows a very big drop in pace and then the subsequent increase afterwards to average it all out. The only difference was with my watch been on my left wrist, it was river side on the first pass and not on the second, but surely my body can't have been blocking GPS signals that much. 

  • 0 over 3 years ago

    Chexking out runningdf4 data field, which offers this option:

    * Allow user to configure the average period for instant PACE calculation for more stable results

  • 0 over 3 years ago

    It seems like this is the same with every GPS dependent watches. The best of you want to get rid of anything like that is a pod, like STRYD. After struggling iwht the Fenix 6s, and now on the 745 (which is better), it was too much so i bought the pod for stable and accurate pace and distance. Bonus it can give you power.

  • 0 over 3 years ago

    For me, the issue seems to be resolved with 6.20 and gps 5.11

  • 0 over 2 years ago

    The real pace was 5:40 the first 10 km and about 4:45 last 5 km. The track line looks correct and average pace too, but the momentary values of pace are always wrong