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

Live Pace Accuracy

Running software 17.26

I'm having issues with interval training on a 255m during running activities. I'm running intervals with both the "Pace" and "Lap Pace" fields on my data screen. The live pace disagrees with the lap pace. For example my lap pace will decrease even though my pace is still higher than the lap pace. Or I can be running a lap pace that is 10-20s quicker than any value that's shown in the pace field.

Pace seems to be different to what I was used to with my 245m. On the 255 it feels less accurate and is rounded to 5s intervals. I felt the 245m pace was more accurate and didn't round.

Has anyone experienced similar?

Top Replies

global_local over 1 year ago +1

8601751 said:
Running software 17.26

Here is the problem. I noticed too that "instant pace" is not really instant but rounded average with about 20-30 sec base. Sad but the truth - Garmin does…
RDW over 1 year ago +1

The 17.xx updates broke instant pace for me.

Previously it used to work on what i guess was a 5 second or so average (and rounded to 5 sec bands on display) so worked nicely for intervals and adaptation…
RDW over 1 year ago in reply to global_local +1

The issue for me is instead of maybe 5 seconds average which allowed instant adjustment its now 20-30 seconds so so delayed its impossible to use it as a reference. That isnt the GNSS/Chipset as it all…

All Replies

0 8601751 over 1 year ago in reply to ovekvam

Using pace for intervals is what is really driving this for me. I had a FR245m that seemed to give good enough data to understand if you were close to your target. My biggest frustration is a data screen I like to have showing pace and lap pace during intervals. I will look at pace to try to hit my target but lap pace is lower and falling indicating an inaccuracy. At the end my actual interval pace shows up lower than the target pace I was running to by watching the instant Pace field.

0 global_local over 1 year ago in reply to ovekvam

Correct. It is fully up to you, what you prefer - which pace, but you need the data flow every second. Position and time. Every second. Then you can choose - instant, lap, or full activity pace.

I use the datafield RunningDF4 were i can define the base from 5 till 30 sec. Normally i use 10 sec base - good compromise between precision and dynamic.

Now, if i start the run, saying 5.00-6.00 min/km, first 10-15 sec i see only "-.--" on the watch. No data coming in. Then comes 15 min, 12min, and after another 10-15 seconds i see a pace value that i _really_ have a 20-30 sec before.

Another one sample. I do a steady run 6.30. Then i accelerate myself to 3.00 for a next 15 sec and go slowly with walking speed 10.00. The watch shows at acceleration - 6.30. Last 5 sec are 6.30, 6.20, 5.50 and so on. If i walk after sprint i get first my 3.xx pace.

It is really useless in that form.