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

Difference between elapsed and moving times

I have a new forerunner 245. I've run a couple of 5ks in the last week and, on both occasions, my moving time (& total time) has been circa 8 seconds less than the recorded race time. The race time accords with the elapsed time (not a chipped race). Although I have auto stop "on" I definitely do not stop or come anywhere close to stopping so am unsure why there is a difference? The only explanation I can think of is that the 'moving' time relies on GPS and, given the route is heavily wooded, the GPS signal is lost momentarily during the race. I've run this same park run race before on my old garmin (75?) and it was always accurate so don't think it is connected with the race timing. Any thoughts?

0 tmk2 over 4 years ago

Take a close look at the pace graph in Garmin Connect. You should be able to identify the spot where the watch though you were stationary. Alternatively, you can post a link to the activity, so someone else can have a look at it.

0 richarddonaldson444 over 4 years ago in reply to tmk2

Hi, many thanks for your suggestion. Interestingly there were no gaps on the pace graph during the race and so my theory is probably incorrect. On closer inspection however it did seem there was a gap at the very beginning. They were both busy races and so the start was slow but not stationary. I can only imagine the garmin considered the slow pace at the very start of the race to be stationary - although I'm still surprised it would be as long as 8 seconds!

Many thanks.

0 tmk2 over 4 years ago in reply to richarddonaldson444

richarddonaldson444 said:
On closer inspection however it did seem there was a gap at the very beginning. They were both busy races and so the start was slow but not stationary.

That explains it, I think. The thing with GPS is that it's relatively inaccurate and noisy, and so most devices do some kind of filtering, and that can cause delays when reacting to change of pace. Meaning that the watch may need several seconds to pick up your pace when you start running from a stationary (or very slow) position.

If it's any consolation, I also notice this phenomenon when starting a run.

0 6960018 over 2 years ago

I have Garmin Forerunner 245 and each time when I start my run Garmin lose some small part of race (on the start 1th lap), GPS line is green 100%.

It is on stadium GPS signal 100% clear sky...

There https://www.strava.com/activities/6309643782/laps or https://connect.garmin.com/modern/activity/7885771191 I lose 30 meters and time on 1 lap

There https://www.strava.com/activities/6309643782/laps or https://connect.garmin.com/modern/activity/7876634519 I lose 100 meters and time on 1 lap

How to fix this issue?

0 richarddonaldson444 over 2 years ago in reply to 6960018

I found that switching off the 'auto-stop' function seemed to resolve the issue?

0 flocsy over 2 years ago in reply to richarddonaldson444

auto stop or auto pause? I don't use auto pause any more, because it't needs a few seconds to detect that I started to run, so I just press the button on start and stop.

0 6960018 over 2 years ago in reply to richarddonaldson444

Issue was fixed, thank you!