Elapsed time

I'm fairly certain that this is how it has always worked. At the very least, that is how it worked when I recorded commutes. It is also consistent with how Garmin describes the various times and averages.

https://support.garmin.com/support/searchSupport/simpleCase.faces?caseId=%7Bb6dded60-28a4-11e0-d39a-000000000000%7D

To avoid this, just end the workout when you arrive at your destination.

Travis

I'm fairly certain that this is how it has always worked. At the very least, that is how it worked when I recorded commutes. It is also consistent with how Garmin describes the various times and averages.

https://support.garmin.com/support/searchSupport/simpleCase.faces?caseId=%7Bb6dded60-28a4-11e0-d39a-000000000000%7D

To avoid this, just end the workout when you arrive at your destination.

Travis

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 also note that my Connect records also show last weeks activities as being recorded using a 705 when in fact I use a 605. Somethings not right

looks like the elapsed time is correct, it's the Time that's wrong, now shows the same hours & minutes as the Elapsed Time

moving time and elapsed time

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 noticed that Garmin did something to change the data-analysis as of Feb 4, 2013. Their software now miscalculates running pace -- the system fails to account for time the device is "ON" but I have pushed the "STOP" button. Basically, if I pause the stopwatch for a couple of minutes mid-run, Garmin now fails to subtract the paused interval from the work-out. They calculate from beginning of run to end of run without considering any stops in between -- totally messed-up.

uploaded this weeks rides after updating my Connect software but the two problems still exist which are the Time reading same figure as Elapsed Time and stating my device is a 705 when it's actually a 605. Can this please be recognised as a problem?

Sometimes "time" and "elapsed time" are the same number. As for how your device is recognized.... does it matter?

At any rate, if you want Garmin to acknowledge the issue, you need to file a support ticket on their support site. Despite Garmin name on this website, it is virtually a user forum. All the mods I see active here are volunteers and don't work for Garmin. I'm not even sure the admin is a Garmin employee.

No I think this is a new software problem as I have been having the same problem the last 2 weeks or so. The time on my 305 display and on the first upload page is what I think is right, but then the time on the activities page is different. I think it is the elapsed time that includes when I stop the time en route - to wait for traffic at a road say. Was there an update recently that has caused this? I was trying to send an email from the website but it kept crashing on me...

No I think this is a new software problem as I have been having the same problem the last 2 weeks or so. The time on my 305 display and on the first upload page is what I think is right, but then the time on the activities page is different. I think it is the elapsed time that includes when I stop the time en route - to wait for traffic at a road say. Was there an update recently that has caused this? I was trying to send an email from the website but it kept crashing on me...

This is definitely a new problem that was introduced around 4th Feb 2014.

I've raised a helpdesk request with Garmin, so will see what response I get back.