58 tooth chainring?

[Wankelschrauben]

Good point !!!!!

What gear was he wearing as a matter of interest?

I was wearing a tight fitting black T-Shirt, brightly coloured patterened shorts and clipless shoes.

 

[Angelfishsolo]

You won't. Voltage is too low, and you'd be adhereing an LCD screen to a set of sunglasses. Just requires a little skill, a magnifying glass and some finesse.

I lack the latter

 

[JonnyBlade]

I was wearing a tight fitting black T-Shirt, brightly coloured patterened shorts and clipless shoes.

So you probably just looked like a cyclist giving it stink!!!! Great speed Buddy, would you have gone faster if you hadn't been stopped?

​

 

[gaz]

I'm not sure I understand what you are saying.

My experience suggests that speed is calculated from the rear wheel speed, sit on a turbo and spin with gps turned on, speed will be displayed but no distance information. Unles you turn gps off, then you get speed and distance.

Ok done a little bit of reading and I confirmed what I thought. Although I didn't write it very well

The max speeds on garmin connect are not quite right. Where it gets the data from I don't know. If you find that you have a ride which says you did a max speed of 100mph and then put that tcx file into another price of software (e.g. Ascent) it shows you a different max speed.
So looking at the data and checking it with another piece of software should verify if it was a glitch.

I don't think I have had an issue with max speed whilst using the gsc10. I suspect the issue is down to the errors you sometimes get with gps readings and it jumping out of place.

 

[JonnyBlade]

Ok done a little bit of reading and I confirmed what I thought. Although I didn't write it very well

The max speeds on garmin connect are not quite right. Where it gets the data from I don't know. If you find that you have a ride which says you did a max speed of 100mph and then put that tcx file into another price of software (e.g. Ascent) it shows you a different max speed.
So looking at the data and checking it with another piece of software should verify if it was a glitch.

I liked travelling at 9800 mph so I'm leaving it as it is

 

[Angelfishsolo]

Ok done a little bit of reading and I confirmed what I thought. Although I didn't write it very well

The max speeds on garmin connect are not quite right. Where it gets the data from I don't know. If you find that you have a ride which says you did a max speed of 100mph and then put that tcx file into another price of software (e.g. Ascent) it shows you a different max speed.
So looking at the data and checking it with another piece of software should verify if it was a glitch.

Does it say by how much the garmin will be out (on average?). Also isn't the implication there is an inherent problem with the Garmin?

 

[Rob3rt]

Ok done a little bit of reading and I confirmed what I thought. Although I didn't write it very well

The max speeds on garmin connect are not quite right. Where it gets the data from I don't know. If you find that you have a ride which says you did a max speed of 100mph and then put that tcx file into another price of software (e.g. Ascent) it shows you a different max speed.
So looking at the data and checking it with another piece of software should verify if it was a glitch.

I don't think I have had an issue with max speed whilst using the gsc10. I suspect the issue is down to the errors you sometimes get with gps readings and it jumping out of place.

Yes you can use Excel to review the data, it would appear that Garmin software doesnt appear to filter out gps glitches well. You could process your own data using Octave (basically GNU MATLAB) and a custom (albeit very simple) search and destroy algorithm and then review using Garmins software if you wanted.

I'm pretty convinced that the garmin uses the gsc-10 for speed if it is detected, if its not present then it will proceed with gps. If this wasnt the case, what is the point in logging rear wheel speeds? Unless they have some algorithm to test cross correlation.

 

[iAmiAdam]

Ah yes, I'll have to double check. Garmin don't make this easy eh.



A very fast cadence. But the way that people have dismissed that +40mph is not possible because they can't do it and pro's can. Must mean I can't spin that fast.

Gearing you were in please, 170 RPM is something that sprinters do in the closing metres.

 

[Rob3rt]

Does it say by how much the garmin will be out (on average?). Also isn't the implication there is an inherent problem with the Garmin?

Not neccessarily, just their post-processing software. Its been long established there are better 3rd party software suites out there for reviewing the data they log.

 

[gaz]

Does it say by how much the garmin will be out (on average?). Also isn't the implication there is an inherent problem with the Garmin?

As far as im aware it's only a problem with garmin connect and the max speed. And it's only an issue if you had a gps blimp whilst cycling and you are not using the gsc10 unit.

 

[gaz]

Gearing you were in please, 170 RPM is something that sprinters do in the closing metres.

34-11. And I did do this in a bit of racing

 

[Angelfishsolo]

As far as im aware it's only a problem with garmin connect and the max speed. And it's only an issue if you had a gps blimp whilst cycling and you are not using the gsc10 unit.

OK so this seems to suggest that unless GB155 has been very unlucky his reported figures are in the main correct.

 

[JonnyBlade]

Spinning at 40 mph. Is that the pedals whilst on the lower gears are spinning at 40 mph or the bike is being propelled forward at 40mph because that is wicked fast and way out of my league

 

[Angelfishsolo]

Not neccessarily, just their post-processing software. Its been long established there are better 3rd party software suites out there for reviewing the data they log.

OK thanks for that

 

[iAmiAdam]

34-11. And I did do this in a bit of racing

Around 150 cadence then, why were you sprinting in the little ring?