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

Moving time way off!

I really really liked the way moving time used to work and missed it when GARMIN took it out. Apparently it has been put back in, but it does not give accurate data. I've made two passes of one of my favorite MTB single track loops. Both times I rode the entire course without stopping at all. Not once. However, my elapsed time and moving time vary by 2 to 3 minutes! Before they messed with it, my elapsed and moving times would either match up or vary by 2 or 3 seconds. Two or 3 seconds is fine, 2 or 3 minutes is ridiculous! Has anyone else been getting such incredibly erroneous data? I have a Garmin 800.
  • moving time

    Yes, just started using my edge200 on my MTB. Time and Elapsed Time seem to be correct but moving time is less by the difference between the first two.

    I'm using auto-pause and I'm guessing the garmin connect subtracts the stopped time (which it still has as data) from a time that has already had the stop time removed. a double subtraction? Just a guess. Will investigate further.

    Chris
  • Former Member
    0 Former Member over 12 years ago
    Inaccurate moving time (or super human speed!)

    Yes, just started using my edge200 on my MTB. Time and Elapsed Time seem to be correct but moving time is less by the difference between the first two.

    I'm using auto-pause and I'm guessing the garmin connect subtracts the stopped time (which it still has as data) from a time that has already had the stop time removed. a double subtraction? Just a guess. Will investigate further.

    Chris


    I've experienced strange goings on wiht time/moving time and elapsed time -
    I ran 10K (10.02Km) using my Garmin 305 Forerunner in a time of 44:32, an elapsed time of 44:32 and a moving time of 10:12. Average speed was 13.5 km/h; average moving speed was 58.9 km/h and I attained a top speed of 107.1 km/h (Usain Bolt's top speed is 43.93 km/h)!! I think Garmin must be having a laugh.

    I suspect this has arisen due to poor satellite reception/locking and the device not locking on correctly to the satellite reception (though the route I took is under open skies).
    I performed a factory reset (Power and Mode buttons) and will try for a new land speed record tonight.
    Any thoughts?