ya, I was going to mention the sometimes dual bike thing on some bike computers. I have or had one that could do it but never used the dual function, something like a "A" and "B" setup in teh menu.

Well, you guys got me to thinking so I looked up some units online. I like the VDO line so I see the 4.1 has a 2 bike function. And, no dealer in Canada as MEC has stopped carrying the product line. I've put an email into the maker so if they will ship, I will buy :)

An elegant solution.

Also, interesting about the bearing. I cut that stem pretty even and it rotates smoothly so I think it will work out but another thing to think about when doing this.

A question for the math crowd, of which I am admittedly not a member in good standing...

What would the difference in distance measurement be between a 2155mm and 2100mm wheel? Is it enough to worry about or would the measure for one be ballpark accurate enough for the other?

Turns out O have a second Cat Eye Strada cadence computer in my parts bin.

Hmmmm, first you take one number and key it into a calculator, ... ...

The difference is about 2.6 percent. Is that enough to worry about or not, your call. If one wheel is always right the other wheel would be 2.6 percent off.

I personally would want better accuracy than that for distance.

But, for speed that is close enough for me. A lot of my computers that I have used over the years rounded off to the nearest half MPH, I suspect for you they would round off to nearest half km/hr. At 19 km/hr, if it is off by 2.6 percent it would read almost exactly a half km/hr off, either 19.5 or 18.5. I would not notice that kind of error for speed.

When touring, I use both a computer (one that is over a decade old) and a GPS. I mostly use my computer for cadence or speed measurements. I almost always have my GPS screen on the map with no other data. But I toggle to my GPS data screen for distance measurements, both distance traveled that day and distance to destination. And sometimes estimated time to destination. My GPS does not have a pressure sensor in it, so I usually disregard any elevation related data in my GPS as inaccurate, but I have it configured to show elevation.

Sometimes my wireless VDO computers have added extra distance for no reason that I can figure out. So, I am less likely to look at their distance data, that is part of the reason I am more likely to look at my GPS for distance data. My older Sports Instruments (defunct company) wired computers were always spot on for distance but they lack cadence data.

When in a country that uses km instead of miles, I re-configure my GPS and computer to use the local units, I want my electronics to match the units on the road signs.

Or maybe plan B. If you configured your computer to the mid-point between the two wheel sizes, then both wheels would have a 1.3 percent error, one reads high the other reads low. At a 1.3 percent error, that becomes almost insignificant, I could live with that much error for both distance and speed.

Funny, that's the plan I've decided on. I posted this same question in the road cycling sub forum and someone suggested it. That idea gives a variance of 1.3 which seems acceptable. As I said there, the way I use a computer for touring around here is pretty basic and I only need to know distances for navigation within km's not meters.

FWIW, this is the maths I came up with
One revolution is 2100mm = 210cm's.
1km = 100000cm's.
100000/210 = 476 revolutions.
27.5mm = 2.7cm's deviation per revolution.
476 revolutions x 2.75cm's = 1285cm's
1285cm's = 12.85m

So... if my thinking is correct, I would have a discrepancy of 12.85 metres for every 1 km travelled.
or.. 12.85 meters x 100km's = 1.285 km's per 100 km's traveled.

If that is correct, would it also stand to reason that if I were travelling at 25km's per hour I would have a speed discrepancy of .32 km's per hour?
1.285 meters per 100km's / 4 = .32.

My math was simpler, I divided 2155 by 2100 and subtracted 1:

2155 / 2100 - 1 = 0.026 or 2.6%

and then if you pick the mid point and allocate half that 2.6 percent error to each option, that is 1.3 percent error for each wheel choice. So, use 2127 or 2128 for your computer setting, mid point between 2100 and 2155.

Or you could use logarithms, ....

close enough for jazz I reckon, and what I would do, being the lazy son of a gun that I am.

I gave my brain a break and took the bike out for another trip instead.
This time I drove an hour west to a place called Finns Slough by the ocean. From there I rode to Terra Nova Park and back again on mixed pavement and gravel, stopping at the Historic fishing town of Steveston for fries and a coffee. I added the saddle bag this time because it's quite cold out and I wanted to take a down jacket just in case.
Much better than math ;)

Finns Slough

http://i.imgur.com/hsY1oIll.jpg

http://i.imgur.com/HubzLNsl.jpg

http://i.imgur.com/JzavuOWl.jpg



Waterside trails

http://i.imgur.com/7dglWSbl.jpg



http://i.imgur.com/jEURGTel.jpg

http://i.imgur.com/gUSbEXql.jpg


Steveston

http://i.imgur.com/p2H8Dkgl.jpg

http://i.imgur.com/0dZSdZgl.jpg

http://i.imgur.com/rej1xi7l.jpg