== Distance numbers for my Umbria 100 (well, now all my bikes) This is probably going to be completely boring for anyone who isn't me. But I want to write it down somewhere, so it might as well be here. * bought the bike in late April of 2006 (I have the exact date somewhere) * put the bike computer on about May 28th 2006 (ditto for the date) * as of May 28th 2007, I believe the odometer was about 5550 km (it was at least 5500 km, and I believe it was a bit more). * at the end of my bike ride home from gaming on April 13th 2008, the odometer hit its 9999.9 km max distance. Some amount of distance was lost. * Monday April 14th: +4.2 km on the commute to work, +some unknown distance commuting to dentist's and back (I think 4-6 km). Computer totally reset in the afternoon, before my commute home. * May 28th 2008: during the day at work, the odometer read 723.46 km. * Jan 4th 2009: before riding the bike in 2009, I reset the odometer. Pre-reset it read 4794.2 km. I carried over the April 14 2008 wheel size of 2170 mm. * May 29th 2009: just at the departure from work, the odometer read 1867.5 km and I had biked 5.229 km that day. (I was just at the start of St George, so that's about right.) * August 2nd 2009: the odometer read 4046.9 km, with some amount lost because the bike computer had been increasingly flaky. I carried over the 2170 mm wheel size when I transfered the odometer to a new bike computer, a dZ4L (versus the old dB4L). * September 12th 2009: the odometer read 4528.6 km, with some amount lost on last Sunday's TBN ride because the old dB4L odometer was significantly flaky (~20km lost, I think). This time I really did switch bike computers (delayed due it turning out to require a new wiring harness). * October 18th 2009: after possibly my last 'official' TBN ride of the year, the odometer read 5289.6 km. It had also showed signs of internal frost/moisture condensation on the display; hopefully this won't cause problems during winter. * October 23rd 2009: problems. During my commute home in relatively strong rain, my dZ4L totally reset itself. Before the commute home I believe it read just over 5350 km (~40 km on the 19th, plus commuting on Wednesday, Thursday, and half of Friday). On inspection, it appears that the dZ4L cannot possibly be very water-resistant; the transparent plastic cover over the LCD is not sealed or anything, just sort of pressed down over the unit, and I can even see moisture wicking its way up and accumulating between the transparent plastic and the main body. Damnit. I reset the dZ4L to the last officially recorded distance number (5289.6 km) and a 2170 mm wheel size. * November 2nd 2009: the dZ4L's LCD segments have faded, and it reset itself this morning just out of the blue (when being put back on the bike). Distance numbers at the time of the reset: 5413.5 km, then plus 4.745 km of commute. (Re-set to 5418.2 km, but it doesn't really matter because it's going back to MEC tonight for a swap.) * November 3rd 2009: finally get a replacement dZ4L from MEC. Set to 2170 mm wheel size and 5418.2 km distance. Distance for Monday night and Tuesday was not recorded, as the old computer wasn't remounted. * December 31st 2009: the end of year distance number is 5856.8 km. I carried over the 2170 mm wheel size when resetting it for 2010. * April 8th 2010: the bike had its annual tuneup; the chain plus drivetrain was replaced. Current distance: 736.91 km, and I should check the chain every 1000km or so from now onwards so that next time I don't have to replace the entire drivetrain. * April 28th 2010: while carrying the bike computer to record the current distance, it got reset (nngh). I know it was at least 1250 km, and I think it was 126x, for a relatively low x. Reset the distance to 1250 km in great aggravation. 2170 mm wheel size again. * December 31st 2010: the end of the year distance number is 6769.0 km. I carried over the 2170 mm wheel size when resetting it for 2011. * December 31st 2011: the end of year distance number is 8005.7 km. I carried over the 2170 mm wheel size when resetting it for 2012. * December 31st 2012: the end of year distance number is 9660.9 km. I carried over the 2170 mm wheel size when resetting it for 2013. * December 31st 2013: the end of the year distance number is 7449.7 km. I carried over the 2170 mm wheel size when resetting it for 2014. * December 31st 2014: the end of the year distance number on my commuter bike is 3184.2 km and on the Brodie is 2579.0 km (in 127 hrs 42 minutes); total distance 5763.2 km, or embarrassingly low. I carried over the 2170mm wheel size on the commuter and the 2205mm wheel size on the Brodie. * December 31st 2015: the end of the year distance number on my commuter bike is 3679.7 km and on the Brodie is 2444.3 km (in 119 hrs 43 minutes); total distance 6124.0 km, better than last year. I carried over the 2170mm wheel size on the commuter and the 2205mm wheel size on the Brodie. * April 18 2016: During servicing, Urbane Cyclist discovered that my Miele Umbria 100 had two frame cracks (one clearly serious). My first commuter bike is officially dead. Final distance for that bike this year is 909.65 km. * April 26th 2016: New dZ4L3 on the new Urbanite Market commuter bike with 700x35C tires. Measured tire circumference comes out to about 2170 mm, which is what the old commuter bike was set to, so I'm carrying forward having the bike computer set at 2170 mm wheel size. * July 24th 2016: Cross-checking against GPS numbers strongly suggests that the Brodie's 2205 mm wheel size is wrong (even if the Topeak Panoram V10x manual really does believe otherwise), so I changed it to 2170 mm. This year's distance before the shift is 1274.2 km. This shift is subject to change. (For future reference: a couple of manuals call 700x35c tires 2168 mm.) NOTE: I have run 700x35 tires on the bike for some time, probably since at least 2010 (I know for sure 2013 and I'm sure for several years before then). Two balacing factors: * this includes some amount of distance from walking the bike, especially on daily commutes (where I walk it a few hundred meters inside the building). * the tire size is set slightly low. I believe I set 2170 mm (700x30 in the manual) versus 2180 mm (theoretically correct for 700x38 according to [[here http://www.chainreaction.com/radarcomp.htm]]), but I may have set lower. (Did I set it to 2070, the listed 700x18 size? I may have.) Update, June 9th 2008: I found my [[gear calculator Umbria100Gearing]] program, dating from May 20th 2007, and it uses a wheel size of 2155 mm. At the April 14 2008 reset, I put the wheel size at 2170 mm. This appears to be roughly correct within a cm or less, based on rolling tests at work (where there is a set of 1-foot floor tiles nicely lined up). == Distance numbers on my 2013 Brodie Elan The Brodie has a Topeak Panoram v10x wired bike computer, because MEC was out of stock on the latest dZ4L3 at the time. The Brodie has 700x35 Vittoria Randonneur Pro 35c tires, and the Panoram's manual lists these as 2205 mm so that's what I set. Since I like to keep track of this, I got the bike May 31st 2014. === bike computer functions This is for my old(er) dB4L; the dZ4L is similar but slightly better documented and some bits actually are documented, eg the time reset. * press left and right for 4 seconds on either display and you get to total reset. Doesn't seem to flip to anything else. * press left for long enough on the clock/odometer (second screen) and you can reset the odometer. * somehow I managed to get to set the time without totally resetting the unit, but I am not sure how any more. I've now reproduced this. Once the odometer is high enough, press and hold the left button on the second screen to change the clock; it may matter that this was shortly after a trip reset. \\ (At least I assume it requires the odometer to be high enough.) The Filzer product page is [[here http://www.filzer.com/products.php?id=6]]. Also [[here http://www.filzer.com/computer_faq.php]].