Garmin Connect

[R600]

just uploaded my ride for today and i notice that connect isn,t showing calories or time when moving. has anyone else had this problem or have i changed any settings by mistake.

 

[HLaB]

They stopped moving time last week for some reason, which was a pity it made me 0.1mph faster its still giving me Calorie data though, perhaps you dont pedal hard enough

 

[RaRa]

I spotted this yesterday and also accoring to the uploaded data during yesterday's ride I appear to have started with a HR of 3 and reached the giddly hights of a max HR of 32. So either I've suddenly turned into an elite athlete or I was technically dead before I started the ride!

 

[BSRU]

Their reason/excuse for removing the moving time was it confused users having three different times displayed, although I think the confusion is caused by their description of the three times.

 

[Andrew_P]

Don't really know why but this has really pished me off, if anything moving time should have been the driver for the stats, total time when commutting is nice to know but useless as a comparasion tool..

Garmins suggestion is to use Autostop, but then you lose total time? Also not sure what the Edge 705 is like but my phone was crap at autostop, even moving time on the Garmin would sometimes miss stops.

 

[HLaB]

I could have been wrong but I thought moving time didn't count the few seconds you were shuffling along in junction queue, etc and I quite liked it too. I use Autostop but its a tends to be non immediate, its reasonably quick but there is often a pause between actual stopping and application. I currently use it where it only stops the clock at 0mph; maybe I should change it to 2or3mph.

 

[Andrew_P]

I could have been wrong but I thought moving time didn't count the few seconds you were shuffling along in junction queue, etc and I quite liked it too. I use Autostop but its a tends to be non immediate, its reasonably quick but there is often a pause between actual stopping and application. I currently use it where it only stops the clock at 0mph; maybe I should change it to 2or3mph.

I would guess Auto @ 0mph would be the same as the connect moving time in that it would miss really short stops. Although I use a GC10 speed I reckon moving time was down to the GPS signal and there would be a bit of lag in that. Just frustrating that comparing past and present is now useless, like starting over.

I always felt that the Avg moving Speed, Avg Moving Pace, avg moving HR would have been better tools anyway and should have been the items shown in historical reports.

 

[HLaB]

I would guess Auto @ 0mph would be the same as the connect moving time in that it would miss really short stops. Although I use a GC10 speed I reckon moving time was down to the GPS signal and there would be a bit of lag in that. Just frustrating that comparing past and present is now useless, like starting over.

I always felt that the Avg moving Speed, Avg Moving Pace, avg moving HR would have been better tools anyway and should have been the items shown in historical reports.

There was a very small difference on a ride with a lot of junctions, say 17.2mph (ave moving speed) compared to say 17 or 17.1mph (average speed), I'm guessing that was just adjusting for that lag. On a ride with very few stops the speeds were the exact same. For me it was a good comparison, Actual time, time and moving time. Al my MCL data (apart from the last week) is average moving time, I'm certainly not going to go back and readjust that.

 

[Edwards80]

I'm not sure if the Garmin compensates for it but if you watch the speed whilst you are stationary it will show 0.1/0.2 occasionally depending on how good the satellite links are, which may be delaying the autostop from kicking in. I set mine at 3mph, I'm not doing that speed for anything other than stopping at lights etc.

It still shows total moving time / total time elapsed etc.

 

[Andrew_P]

Just in case you have not noticed but Garmin are back tracking sometime in April so expect another ball up!

Although I have now learned to love Autostop much more relaxed waiting at lights now :-)

Inside Garmin Connect: An update on Moving Time



March 19, 2012 - posted in Ask Garmin, Garmin Connect, Into Sports,

​

Thank you for all of the feedback regarding the recent removal of Moving Time from Garmin Connect. While the switch was done with the best intentions of clearing up confusion that we’d heard about from some customers, it’s very clear that the information provided by this data was very valuable to many of you. We appreciate all of the responses we’ve received, and we’ll be reinstating Moving Time in the next update that will roll out the first week of April. Moving Time data will again be viewable in your previous activities as well as those you’ve done since the recent change. We apologize for any additional confusion or frustration that these changes may have caused, as our goal was just the opposite. Thank you again for the valuable feedback!

 

[HLaB]

I'm not sure if the Garmin compensates for it but if you watch the speed whilst you are stationary it will show 0.1/0.2 occasionally depending on how good the satellite links are, which may be delaying the autostop from kicking in. I set mine at 3mph, I'm not doing that speed for anything other than stopping at lights etc.

It still shows total moving time / total time elapsed etc.

I was thinking of doing similar (maybe below 2mph) but after reading LOCO's post I think I'll wait

 

[R600]

just noticed its back

 

[Garz]

Their reason/excuse for removing the moving time was it confused users having three different times displayed, although I think the confusion is caused by their description of the three times.

This is what I thought when I first noticed the change. If only they could fix the 500 course bug now...

 

[Garz]

I'm not sure if the Garmin compensates for it but if you watch the speed whilst you are stationary it will show 0.1/0.2 occasionally depending on how good the satellite links are, which may be delaying the autostop from kicking in. I set mine at 3mph, I'm not doing that speed for anything other than stopping at lights etc.

It still shows total moving time / total time elapsed etc.

Don't set it too low, if you live where there is some beastly hills and your creaking up the 25% the last thing you want is the bleep and timer stops only cos your creeping up the hardcore gradient.