CRR variation: unidirectional or bidirectional?
Posted: Wed Sep 05, 2018 7:16 pm
As regards the firmware update with the variable CRR: does it just go up from baseline or can it go both ways?
My use case is that I cycle often on the towpath by a canal and many of the roads are rubbish, so when I was writing up the bike I put the lower setting. From memory it was ‘bad asphalt’ or similar (the 28mm tires are mildly treded too), but rarely I actually get some nice road (or more commonly road I now know how to avoid all the potholes)
Should I be putting the Crr for the most common road surface or the best surface?
Currently I have 0.0058, which is for cheap commuter 28mm lightly treded tires on a rubbish surface. The distance in the GPS VeloTrack app is consistently roughly 2% higher, so very closely correct.
My use case is that I cycle often on the towpath by a canal and many of the roads are rubbish, so when I was writing up the bike I put the lower setting. From memory it was ‘bad asphalt’ or similar (the 28mm tires are mildly treded too), but rarely I actually get some nice road (or more commonly road I now know how to avoid all the potholes)
Should I be putting the Crr for the most common road surface or the best surface?
Currently I have 0.0058, which is for cheap commuter 28mm lightly treded tires on a rubbish surface. The distance in the GPS VeloTrack app is consistently roughly 2% higher, so very closely correct.