You can no longer post new replies to this discussion. If you have a question you can start a new discussion
Elapsed time
Former Member
my uploads this week show the time elapsed from the start of my commute to work and end when I commute home i.e. it shows a 10 hour ride rather than 1 hours actual riding time. This also effects the averages. Is this a problem with my device or with Garmin connect?:confused:
I was thinking about moving time and elapsed time when I answered this, but another thread reminded me of my error. Here is what Garmin says about them from the FAQ for Garmin Connect...........
Garmin Connect provides three Time measurements on the Details page:
Time
Time is the recording time reported by the device. For Fitness devices, this should equal the Time value reported on the device. For other devices, this should equal the amount of time elapsed from the actual Start and Finish time of an activity.
Avg Speed/Pace is based off the Time value.
Moving Time
Garmin Connect calculates Moving Time by removing the amount of time when the user is stopped. This is helpful for customers who upload activities with a Garmin device that either don't have AutoPause or have AutoPause turned off. For those who have AutoPause turned on or hit the Stop and Start button in the middle of an activity, the Moving Time should be very close or equal to Time.
Avg Moving Speed/Pace is based off the Moving Time value.
Elapsed Time
Garmin Connect calculates the Elapsed Time by the amount of time elapsed from the actual Start and Finish time of an activity. This is helpful for customers with a Garmin device that have AutoPause turned on or hit the Stop and Start button in the middle of an activity. For those who don't have AutoPause or have that feature turned off on their device, Elapsed time should be very close or equal to Time.
Despite any of the above, in the grand scheme of things, these numbers are not off enough to significantly affect your stats.
I don't disagree that it the GC site might be screwed up. But posting here doesn't notify garmin of the problem. You have to open a support case at their support site, as did the person of the previous post
AFAICT, given the definitions on the support page and the behavior people are seeing, Garmin Connect is behaving as designed. If it behaved differently ob Garmin Connect before February 4th, or behaves differently on device X with firmware Y, it does not matter. Elapsed time is the time measured from when you first start an activity until you complete the activity by holding reset. It doesn't matter if you pause, auto-pause or power the device down... Until you complete the activity, the elapsed time is still ticking.
And that makes sense for elapsed time. As for most competitions, it's the time from when the start sounds until you cross the finish, even if you stop to get some water/fuel or whatever. Which is why you minimize the time you spend in "pit-stops"
I've uploaded 1500 activities since 2006 and this is the first instance of a change in how the Elapsed Time is recorded. My Edge device has the correct cycling times but the Connect account is now showing totally different data just for this week. Has anyone else seen the same change?
I'm having the same issue. Have you found out if there is a fix for this? It's been happening for about 2 weeks or so on all of my activities.
I'm having the same issue. Have you found out if there is a fix for this? It's been happening for about 2 weeks or so on all of my activities.
I've got the same problem, started after maint. on the 4th Feb. What I am doing is to do a full edit and input the correct time, using the lap time split or summary, replacing the elapsed time which at least gives me the correct avg speed etc.
I've got the same problem, started after maint. on the 4th Feb. What I am doing is to do a full edit and input the correct time, using the lap time split or summary, replacing the elapsed time which at least gives me the correct avg speed etc.
Thank you for that tip. I guess that's what I will do until they get this fixed. It's definitely something in the "upgrade" or whatever they did a couple of weeks ago.
