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

Running pace way off with fw 4.20

Geri
over 5 years ago

Yesterday I ran 10km with constant 4:40 pace. It was a workout from TrainingPeaks. My trainer set a pace target between 4:30 and 5:00. During the run I let the watch show the workout screen with pace zones and alerts. I know that this screen shows a cumulated pace value, but it seemed to be ok. At the beginning it was a bit high as I started with a bit higher pace but after some minutes it started to converge to the 4:40 value. I am used to check my default first screen for running metrics like HR, total time and instant pace. Yesterday, the instant pace value was way higher than my real instant pace during the whole running. It showed values like 5:40-5:50 even though I was running with more or less constant 4:40 pace, and never slow down to 5:40! The workout screen was OK with about 4:42 and the 1km alerts showed also values around 4:40. I am pretty sure that my real instant pace was around 4:40. I have never noticed this anomaly before. I own the 945 for a couple of months now and the instant pace values were OK. I am on the latest firmware 4.20. I have also bluetooth connection problems with my iPhone SE since the last update to 4.20. Have you experienced similar behavior?

  • 0 over 5 years ago

    I wanted to attach the FIT file. You can check the related running here.
    connect.garmin.com/.../4676691133

  • 0 over 5 years ago

    I also started experiencing this behavior (around the 4.20 upgrade as well)

  • 0 over 5 years ago

    +1 here too, same 4.2 fw. i've noticed that instant pace pretty jumpy although i was running pretty even those 900m at 5min/km (and 100m strides at 4:15min/km). i've marked the jumps in the printscreen below:

     

    https://connect.garmin.com/modern/activity/4676541455 - this is the activity...

    have a nice weekend,

    tudor

  • 0 over 5 years ago in reply to tsofron

    Thank you for your answer! However, my problem is not reflected in the FIT file. The recorded pace seems to be correct. My problem is that the watch shows the wrong pace during the activity, even if it writes the right pace values into the FIT file.

  • 0 over 5 years ago in reply to Geri

    Exactly the same behavior here, fit is normal, only watch UI is showing strange behavior

  • 0 over 5 years ago in reply to Bram2473

    Thank you! Then it seems to be a firmware bug. :/ I hope it will be fixed in the next release.

  • 0 over 5 years ago

    I don't think it has anything to do with FW 4.20.

    My watch has always exhibited this behaviour and from what I have read and my own experience it is because "current pace" is not taken from the GPS but form the accelerometer / gyro. It's easy to see: when you start an activity and start moving immediately, you get a pace reading before getting a GPS lock.

    So I'm not surpised that when you try to push yourself or train at an unusual pace, if your stride length is unusual, your current pace will be way off. Can you compare your stride lengths on this workout with previous ones?

  • 0 over 5 years ago in reply to KubrickFr

    Maybe you are right, but I checked and didn't notice any unusual in my stride length. It is more or less the same as during my previous activities. So I am not totally convinced.

  • Former Member
    0 Former Member over 5 years ago

    I have a similiar experience but at a a different level. I run my 10k usually at around 50 minutes. My pace varies between 4:30 to 5:30, but my garmin Forerunner 245 shows pace between 6:00 and up to 8:40. Usually this happens when I run faster than 4:30 and when there is a slight decline. This started with update 4.20 as well. I also have a Stryd footpod so before I read this I though that the Stryd may need updating, but it seems not.