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

Huge bug - Wrong current pace/speed and graph vs Strava/Runkeeper

In 3 out of 4 runs I've noticed something really obvious - current pace is off by cca 1 min/km and final graph on CG is not showing pace/speed accurately.

Maybe the best example would be of my recent run. During 1km lap I ran 4:46 mins but both during the run and on GC graph pace range was from 5:55 to 5:00. Strava and Runkeeper are showing pace graph just fine (5:01 to 4:23 min/km).

Change to "speed" and look at split 3 (from 2.00 to 3.00 km) to see what I'm talking about.
https://connect.garmin.com/modern/activity/996157194

So this is not the case when unit GPS is off or something similar - it's just the Garmin's algorithm that's wrong. And the fact that data in CG contradicts left me wondering how a company that core business is GPS manages to get such a simple thing that wrong, even though it happens now and then.

0 timgrose over 9 years ago

Try the 3.25 beta. There are further current pace improvements in that.

0 Former Member over 9 years ago

I'm seeing the same issue with current pace off by up to 40s/mile. Major differencesearch when I upload to Strava too. Worst case so far was doing pickups at the end of a long run. Watch showed 9:05 pace - which I couldn't understand as it didn't match the effort. Garmin Connect agreed. Strava said I was doing about 7:40 pace, which would match the effort. Heart rate monitor is abysmal during intervals too. But the pace issue is awful. Also today was running at about 7:30 pace according to after uploading I saw it was at 7:06. I'll be sending it back I think

0 timgrose over 9 years ago

Again you might want to try the 3.25 beta for improved current pace performance.

0 Former Member over 9 years ago

Again you might want to try the 3.25 beta for improved current pace performance.

I dont think that the issue is relative to the instant pace, this is a GC bug but i can be wrong. Please have a look to the maximal pace w.r.t to the mean pace for some intervals, you can see that the max is lower than the mean... odd thing

i've posted to a thread in GC forum, but no answer so far

0 Former Member over 9 years ago

I installed 3.25 and went out for a run this morning. I did notice an improvement. It took a bit of time (around 3 or 4 mins) to settle down, but when it did
it was an improvement. I would still say it lags behind - as in it doesn't update the pace for around 10 to 15 seconds after changing pace, but it more accurately reflects the pace than before. I'm happier than before. I will be testing it out in conjunction with my old 310xt during the week and will report the results here. If the two are in close agreement I'll be happy enough. HR was all over the place at the start of the run though
Now - Garmin connect shows a gradual change in pace at the start of the run, but Strava has the pace changing up and down which matches the changes in HR.

Garmin Connect:

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

Strava:

https://www.strava.com/activities/459278878/overview

So I'll persevere as it seems the issues can be overcome with software updates.

0 R_Tellis over 9 years ago

Even if you were hooked up to a medical grade EKG machine there would be a small lag between when you increase your pace and where your HR will increase. It's a physiological response called 'cardiac lag'.

0 Former Member over 9 years ago

Even if you were hooked up to a medical grade EKG machine there would be a small lag between when you increase your pace and where your HR will increase. It's a physiological response called 'cardiac lag'.

I'm not referring to the cardiac lag. I'm referring to the apparent lag in the pace readout on the watch from when I increase my pace to when the watch displays the new pace. It was always bang on with the 310xt, there just seems to be delay with the 235. As for the cardiac lag issue, i'm aware it exists, however this watch doesn't accurately track heart rate during intervals - a different issue to the heart lagging behind.