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

Gps instant pace completely wrong sometimes even if the gps track is good

Mirko_Italy
over 5 years ago

In my run today for three minutes gps instant pace was completely wrong (about 1 minute/km slower) than real instant pace. I tought that maybe it was a difficult place for gps (near the mountain and under trees), but at the end of the run I looked at the track and it was correct in that point of the run. Anybody else had similar experience?

In the rest of the run gps instant pace was quite good, even if much more smoothed than instant pace of my Runscribe footpod paired with another watch.

Firmware 3.08 beta (I reported the issue to [email protected]. I had another watch FR610 paired with a footpod, and I sent both the two activities of the same run recorded with two different watches)

  • 0 over 5 years ago

    Also in good conditions, instant pace of 935 was better for me... Too slow and than in the lap/km ok.. Bo!?!.. Track no problem, good.

  • 0 over 5 years ago

    i usually use average pace field on my runs, but i had a same experience looking at the momentary pace graph - interestingly strava showed a different momentary pace later on. i opened a discussion here: https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-945/194341/pace-not-matching-watch-gc-strava

    i you have strava, would you be willing to check, if the momentary/instant pace is shown any different at some points on your run? 

  • 0 over 5 years ago in reply to DanielM

    In Strava the gps instant pace of FR945 is correct and matches the instant pace of the FR610 that was paired with a footpod. I attach screenshot in the moment that I run beside a little house. Time in Strava (1:06:36) is a bit different than time in the FR945 and in the FR610 (1:06:45), but this doesn't matter, because we have as reference the point beside the house:

    1- gps pace of FR945 that I read  in the watch during the run and reported after in Garminconnect  -> 4:55/km (this is wrong, I was faster)

    2- gps pace of FR945 in Strava -> 4:19/km (this is about correct)

    3- Runscribe footpod pace recorded by the FR610 - > 4:19/km (this is abouot correct)

    Lap pace of gps  was about the same and  correct for all FR610 (4:40/km), FR945 garminconnect (4:43/km), and FR945 strava (4:38/km).

    It seems that in some moments instant pace from gps of the FR945 gets out of whack and reports completely wrong values. This time it was not a matter of seconds, but the watch reported a completely wrong value for 3 minutes, even if the track is perfect and if Strava reports the correct value. Probably there is something in the algorithm that causes some errors. The watch FR945 was connected with a ANT+ Garmin chest strap heart rate monitor and with the CIQ app Gaitcoach (that was receiving data from the Runscribe foot pods).  The ANT+ footpod was set to off in the menu of the watch and was not connected to the FR945. The FR945 was with GPS+Galileo

    I attach screenshots

  • 0 over 5 years ago in reply to Mirko_Italy

    Giusto Mirko, hai spegato perfettamente le cosa!!! Explaned perfectly, the same for me ....

  • 0 over 5 years ago in reply to Mirko_Italy

    Thanks for checking. It is the same with me. I had the watch set to 1sec recording and GPS+GLONASS. Former Member was discussing active in the other thread - was i find most curious is that starve gets it right from the same watch data!

  • 0 over 5 years ago

    Again and again.. today i had time adn payed attention to this fr945 instant pace. I know that is totally bad as i said in other posts. Today i was doing a good effort and it showed 5.30 ( the real was about 4.10 4.20 per kilometer). As ALWAYS i trained in an excelennt sky view, no buildings, no trees. The part that was very annoying was when i lap.. it shows the average and showed the real one 4.18 for example. So showing 5.10.... 4.55....5....5.15.....4.50 and suddemdly in the lap moment it resumes as 4.18?..  i was veryyyy angry as is an evident bug from garmin. Totally useless.

  • 0 over 5 years ago

    I have the same problem since a view races firmware 4.10

    Showing pace is the most important of an watch for runner for me :(
    is there no fix for this?

  • 0 over 5 years ago in reply to dersascha

    I also do have the same issue since 4.10 - Perfect GPS lock and correct path on garmin connect afterwards, but completely wrong instant pace. This also affects to some extent the average lap pace.