Can someone help me with this

Four of a kind · 02-03-2012 03:59AM #1

http://connect.garmin.com/activity/153931687

from this recording it shows that my spin distance was 4.90km - but this isn't true because it showed as 7.89km when I completed the cycle. And I know for a fact it was this distance as I drove it in the car earlier just to confirm.

I don't know what it could be, maybe some setting I've enabled on the edge 500 that records laps or something?

Would appreciate any help to get this to just show the total distance of the trip.

Thanks.

kumate_champ07 · 02-03-2012 06:13AM

Did you hold the bottom right bottom for 3 seconds when you powered it on? If you dont it will still have the distance covered during last session and it will be included with your new total

Idleater · 02-03-2012 06:45AM

Also check that the cadence sensor has calibrated the wheel circumference correctly. I think it's buried in the bike settings and takes a couple of k to set. I think only once but until it's set, the unit will be gps alone and distance will be a bit off while it gets a fix.

TheBlaaMan · 02-03-2012 08:42AM

Four of a kind wrote: »

http://connect.garmin.com/activity/153931687

from this recording it shows that my spin distance was 4.90km - but this isn't true because it showed as 7.89km when I completed the cycle. .

Units issue?

5miles = 8km etc

??

coastwatch · 02-03-2012 10:01AM

+1 on a units issue, maybe you've discovered a bug?

Four of a kind wrote: »

http://connect.garmin.com/activity/153931687

I don't know what it could be, maybe some setting I've enabled on the edge 500 that records laps or something?

Would appreciate any help to get this to just show the total distance of the trip.

Thanks.

There's a Auto Lap setting which can be set to trigger a lap by Position or Distance. It looks like it's set to Position on your unit and got triggered when you passed your start location (coming back from Boyle?). Try turning off Auto Lap ( see page 11 of the manual)

http://static.garmincdn.com/pumac/Edge500_OwnersManual.pdf

Eamonnator · 02-03-2012 10:04AM

4.90 miles= 7.89 kilomtres

looks like you cracked it BlaaMan

Four of a kind · 02-03-2012 01:34PM

Eamonnator wrote: »

4.90 miles= 7.89 kilomtres

looks like you cracked it BlaaMan

3.04 miles is what that distance summary shows though? That's not = 7.89km?

The auto lap was set to distance and clocked at 5km, so I turned this off. Hopefully this will fix that problem.

coastwatch · 02-03-2012 02:20PM

It looks like its uses average speed x time to calculate distance.
The average speed in the summary is showing 12.4 (km/h) which is incorrect
I calculate the average speed to be 19.96km/h.
But 19.96/1.6 = 12.4 miles/hour.
If you use 19.96km/h instead, you get
19.96km/h x 0.395hrs (23:43mins) = 7.89km.

So I still think it's a bug (units issue in the summary section)

Four of a kind · 02-03-2012 02:38PM

coastwatch wrote: »

It looks like its uses average speed x time to calculate distance.
The average speed in the summary is showing 12.4 (km/h) which is incorrect
I calculate the average speed to be 19.96km/h.
But 19.96/1.6 = 12.4 miles/hour.
If you use 19.96km/h instead, you get
19.96km/h x 0.395hrs (23:43mins) = 7.89km.

So I still thinks it's a bug (units issue in the summary section)

Ok, so what can I do to fix it?

Four of a kind · 02-03-2012 02:41PM

coastwatch wrote: »

It looks like its uses average speed x time to calculate distance.
The average speed in the summary is showing 12.4 (km/h) which is incorrect
I calculate the average speed to be 19.96km/h.
But 19.96/1.6 = 12.4 miles/hour.
If you use 19.96km/h instead, you get
19.96km/h x 0.395hrs (23:43mins) = 7.89km.

So I still thinks it's a bug (units issue in the summary section)

This is the cycle on Strava: http://app.strava.com/rides/4669170

It shows up as the correct distance there.

seamus · 02-03-2012 02:47PM

For ****s 'n' giggles, enabled elevation corrections and see if that fixes the distance.

Four of a kind · 02-03-2012 03:02PM

seamus wrote: »

For ****s 'n' giggles, enabled elevation corrections and see if that fixes the distance.

Clicked enable, but still the same.

http://connect.garmin.com/activity/153931687

coastwatch · 02-03-2012 03:17PM

Four of a kind wrote: »

Ok, so what can I do to fix it?

Good question, more testing & cycling I think

It must be a rare bug, otherwise there'd be a lot more postings / complaints.

I use Garmin Training Center. The program is installed on your pc (available to download and free) but it has all the same functions / info. I have it installed on a PC & Mac and the interface is much nicer on the Mac

Duraface · 02-03-2012 03:52PM

Idleater wrote: »

Also check that the cadence sensor has calibrated the wheel circumference correctly. I think it's buried in the bike settings and takes a couple of k to set. I think only once but until it's set, the unit will be gps alone and distance will be a bit off while it gets a fix.

I also had this problem with my garmin on one of my bikes. It should automatically calculate and set the circumference of the wheel but if for any reason the sensor doesnt pick up the magnet correctly on every rotation of the wheel it can set it wrong. Go into bike settings and check the wheel circumference it should be approx 2096 for a 700 x 23 (courtesy of google). You can manually change this if it is incorrect.

Four of a kind · 02-03-2012 05:18PM

Duraface wrote: »

I also had this problem with my garmin on one of my bikes. It should automatically calculate and set the circumference of the wheel but if for any reason the sensor doesnt pick up the magnet correctly on every rotation of the wheel it can set it wrong. Go into bike settings and check the wheel circumference it should be approx 2096 for a 700 x 23 (courtesy of google). You can manually change this if it is incorrect.

mine is set at 2071 and is on auto.

Should I change it? On my tyre it says 700x23C

Idleater · 02-03-2012 06:52PM

Sounds about right. Mine are 2076 and 2094... Must recalibrate...
Cycle that route again and see what it measures to. Was the askew one the first cycle on the garmin?
What I alluded to in my post above is that before the circumference is calculated it may have been inaccurate. It does seem odd all right but I have occasionally had the magnet slip or the memory filling up with the net results being a reasonably accurate map but incorrect speed and distance.

Four of a kind · 02-03-2012 06:56PM

Did a 20km cycle earlier and this time it was spot on:

http://connect.garmin.com/activity/154187882

The only thing I did was turn the auto lap function off, so maybe that's where the problem was in the first place.

Idleater · 02-03-2012 07:06PM

Four of a kind wrote: »

Did a 20km cycle earlier and this time it was spot on:

http://connect.garmin.com/activity/154187882

The only thing I did was turn the auto lap function off, so maybe that's where the problem was in the first place.

It's not auto lap, turn it back on and retest :-)
I auto lap at 5km with no issues. Also just see if switching off auto pause helps. I turned that off after a commute in the fog last year constantly paused due to no signal. Garmin connect and strava both give total and moving time so auto pause is redundant.

Four of a kind · 02-03-2012 08:09PM

Idleater wrote: »

It's not auto lap, turn it back on and retest :-)
I auto lap at 5km with no issues. Also just see if switching off auto pause helps. I turned that off after a commute in the fog last year constantly paused due to no signal. Garmin connect and strava both give total and moving time so auto pause is redundant.

So if turn auto pause off and I stop for a break, then garmin will still keep counting time wise? So for the above route I just did today, it took me 1h 14mins of actual cycling to complete, but without the auto pause it took 1h 38mins.

So I don't really have to bother with the auto then your saying? Will this skewer any stats?

Idleater · 02-03-2012 08:42PM

Four of a kind wrote: »

Idleater wrote: »

It's not auto lap, turn it back on and retest :-)
I auto lap at 5km with no issues. Also just see if switching off auto pause helps. I turned that off after a commute in the fog last year constantly paused due to no signal. Garmin connect and strava both give total and moving time so auto pause is redundant.

So if turn auto pause off and I stop for a break, then garmin will still keep counting time wise? So for the above route I just did today, it took me 1h 14mins of actual cycling to complete, but without the auto pause it took 1h 38mins.

So I don't really have to bother with the auto then your saying? Will this skewer any stats?

Yeah, while you're stopped at traffic lights the trip time will stop I think but the total elapsed time continues. With auto pause off both times continue until you press stop when you finish. You can press lap with no problems. I mean to press lap when going in for coffee but normally end up with one 45 minute 5km segment. I think technically the total elapsed time continues until you reset the trip allowing you to press stop and start during a journey. However I don't know what the resulting garmin upload is like - possibly multiple journeys.
Anyway, When you upload the file to garmin you see 2 times total and moving regardless of auto pause state.
Basically if you want to know during a cycle what your moving as opposed to elapsed time is use auto pause, otherwise it doesn't matter.

Duraface · 02-03-2012 08:46PM

Four of a kind wrote: »

mine is set at 2071 and is on auto.

Should I change it? On my tyre it says 700x23C

As idleeater was saying thats Ok it would be reading half that figure to get the differential you were talking about. Its always going to vary a little from wheel to wheel.

Four of a kind · 02-03-2012 08:50PM

Idleater wrote: »

Yeah, while you're stopped at traffic lights the trip time will stop I think but the total elapsed time continues. With auto pause off both times continue until you press stop when you finish. You can press lap with no problems. I mean to press lap when going in for coffee but normally end up with one 45 minute 5km segment. I think technically the total elapsed time continues until you reset the trip allowing you to press stop and start during a journey. However I don't know what the resulting garmin upload is like - possibly multiple journeys.
Anyway, When you upload the file to garmin you see 2 times total and moving regardless of auto pause state.
Basically if you want to know during a cycle what your moving as opposed to elapsed time is use auto pause, otherwise it doesn't matter.

I havn't looked into lap function, but why would I want to press this if I just say stopped for a few mins break along a route?

box_fresh · 02-03-2012 09:19PM

looks like there is a bug when the programme totals lap distance making a conversion to miles but showing up as Km

In the laps section lap 1 is 5k and lap 2 2.89k but the total has fed in as 4.9

If you look at the graphs they all show distance as 7.9km

Four of a kind · 02-03-2012 10:43PM

box_fresh wrote: »

looks like there is a bug when the programme totals lap distance making a conversion to miles but showing up as Km

In the laps section lap 1 is 5k and lap 2 2.89k but the total has fed in as 4.9

If you look at the graphs they all show distance as 7.9km

I noticed that initially. But didn't know what it meant. So can the bug be fixed?

Am I better off leaving lap data turned off?

Can someone help me with this

Comments