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

Pace During Workout is Incorrect

The calculation of the instant pace in version 7.11 deviates from the actual speed in about 0.5 min/km to 1 min/km.

  • Nice! I’ll try calibrating mine with a long run before using it for intervals.

  • Yeah, with v7.11 its VERY slow to update paces during intervals. Pre-v7.11 the pace at the beginning of an interval would be pretty close then level off a bit. With v7.11 it takes anywhere from 0.25 to 0.30 mile for it to dial in the pace. Nearly impossible to run 800m intervals at a specific pace and annoying for any other distance. I really hope they fix this one soon.

    Here is an example from todays run.  Each purple arrow is where the issue resides.  Im not taking 1/4 mi to ramp up to the target pace. Each middle interval is 0.5 mi.  Beginning/end intervals are 2 miles.

    For comparison, here is a similar workout on v6.04.  You can see the difference is quite drastic. Middle three intervals are same distance at 0.5 mi.  Beginning/End intervals are 1.5 miles.

    Both of these were ran on essentially the same route.

  • This morning when I did a 2420m warmup run (track run), the pace was wrong all the way. Pace chart shows 0:41/km all the way but the avg pace is 5:09/km, the pace chart showed up correctly on Strava, so I'm not sure what went wrong here.

    Also the Power chart is completely off, it is impossible to run at this power level

    Was running with HRM Pro connected.
    The metrics for the actual workout and the cooldown run were okay (still with the instant pace issue at the beginning of the run).

  • Same here. I did 12 x 20 seconds sprints under 2:15/km and got 0.1 aneorobic training effect. In Connect it says I ran at 3:50/km but I know for sure it was under 2:15/km. In Strava it says 2:37/km for some but others 2:50/km which is still not correct as that's my 300m pace not 20 second pace. 

    I also did a threshold workout and it was all over the place 3:20/km one second then 4:10/km then 3:45/km all within 100m on a straight path 

  • hope you don’t mind my asking if there’s been any progress on this, or at least suggestions for how to deal with this in the meantime? Do footpod/HRM pro-based paces work better? Any guidance would be appreciated - this bug has been a big issue for me. 

  • Hello .  I don't mind you asking at all.  I'm happy to help.  Unfortunately, I do not have any updates on the investigation.  I did just verify my answer to move it to the top replies section.  This will hopefully draw attention to my comment and get more users to submit the necessary info to be added to the investigation, which should give us more data to analyze.

    As for tips, I don't have much, unfortunately.  For non-workouts, I like to use the Lap Pace data field instead of the Pace to display on my main data screen.  For structured workouts, this is not possible as you are unable to change the data fields on the workout data screen.

    I'll be sure to update here when I hear any news.

  • Thank you Kevin! I haven't received a request for information on this particular issue - should I expect to hear from someone?

  • I haven't received a request for information on this particular issue

    Please see and respond to my questions at the top of the "Top Replies" section of this thread.

  • 1. Yes

    2. Yes

    3. Norway/Switzerland

  • Hi ,
    Since many of us have given the consent to view/access our Garmin account why don't you have enough data to analyse this issue? Is it not clear that this is an actual issue, it isn't something that is hard to recreate either.

    Here is another activity that clearly indicates the issue. The lap avg pace don't match up with the pace chart at all.
    It took nearly 3 minutes for the watch to catch on to my pace.
    connect.garmin.com/.../10057588063