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 Pace Way off

During summer I mainly use my Forerunner for Cycling and Inline-Skating. I had no major problems here.

Having started winter training I did my first run yesterday and the running pace was way off what it should be.
I ran at a constant pace of 5:15 but as you can see in the graph attached Pace dropped every lap near some trees in the park. (just some trees, sky is not fully covered)

I know that some GPS inaccuracy can be expected but this is even worse than my Forerunner 305 did back in the days. Should I consider this normal? ciq.forums.garmin.com/.../1273072.png

  • Good point. I ran with HRM-TRI, so cadence should be there right? I checked today's run (notice the 5:15 pace ;-) ) and no cadence there too... Strange...

    https://connect.garmin.com/modern/activity/2327817281
  • Is the HRM-Tri connected before you start your run? The data looks like it's coming from the WHR.

    Little to do with the GPS though! However, if the running metrics are coming from the strap, then either something's wrong or your stride length and cadence really are all over the place which would suggest pacing is not as consistent as you believe.

    What type of surface are you running on?
  • The surface on the problem part of the lap is gravel. Data is better on the other part of the lap which has a mix of sand, wood and mud where you'd expect more fluctuations.
    I'll try a run without HRM-TRI on the same lap later this week and check if things are better...
  • Good point. I ran with HRM-TRI, so cadence should be there right? I checked today's run (notice the 5:15 pace ;-) ) and no cadence there too... Strange...

    https://connect.garmin.com/modern/activity/2327817281


    I can see Run Cadence in that one OK.
  • I can see Run Cadence in that one OK.

    That's the type of graph I see when cadence comes from the device, not the strap.
  • I assume when you are comparing distance, you are looking at the distance in the watch or Garmin Connect and not at a site like Strava. Strava usually recalculates distance from the GPS track, ignoring the recorded distance. The recorded distance is calculated from way more data than just just the recorded GPS points. So, 1 second vs smart recording should have no impact on distance recorded. Lastly, there can be anomalies purely based on where the GPS satellites happen to be during that particular activity. So you'd really want more data ponits than just a single run.

    That said, I have noticed discrepancies between the recorded pace and the recorded distance vs time. If you calculate the pace for each data point based on time & distance, the 935 is often on the low side, even when averaged over 30 seconds periods.
  • Cadence is back in both runs. Don't know why it wasn't there yesterday.

    Re: distance: the lap is an officially measured 2k lap. I did 3 of them and I know it's 500m to get to the lap from my starting point.

    Another thing to try is to let the watch outside with GPS fix for a few minutes before starting the run. (like we had to do back in the days....)
  • That's the type of graph I see when cadence comes from the device, not the strap.


    Don't think so. I got "Run Cadence" yesterday when wearing an HRM-Tri.