Orny's Cycling Journal

Been a long time, I know. But thus far, my 2024 cycling has been uneventful but steady, as evinced by my Fitness chart, which has hovered almost unchanged since November… albeit at a level I consider reasonably active. Group rides have included ten PMC Zwift rides during the first two months of the year, which then transitioned to a dozen outdoor Friday Truancy rides as the weather improved.

Aside from just riding around, I’ve had to replace a lot of equipment due to wear and tear, including a saddle bag, gloves, three punctured inner tubes, and my heart rate monitor. My most noteworthy new purchase was a HoverAir X1 automated selfie drone, but I’ll discuss that in a separate, future blogpo.

I’d planned to undertake 2024’s first organized cycling event back in February. But as I packed the car the evening before my 2-hour drive to Hempstead, I left the interior cabin light on, and climbed into the car at 5am to discover a dead battery. Needless to say, I wound up aborting my Pedaling the Prairie ride.

With few events that early in the year, it wasn’t until this past weekend that I lined up for my first century of 2024: the Red Poppy Ride in Georgetown, 30 minutes north of Austin.

I approached it with a bit of trepidation. I’ve done no long rides this year, and an imperial century (at 161 KM) would be twice the distance of my longest indoor (82 KM) and outdoor (72 KM) rides thus far. I’ve also only done one century in the past 18 months; that was last September’s Livestrong Challenge, which pushed me beyond my limit and resulted in ignominiously puking my guts out into a trash bin at the finish line. That left me wondering if I am still physically suited to riding 100 miles now that I’m 60 years old.

Ride start: not a small ride!

After the half-hour drive to the start, I picked up my bib number (a grossly inappropriate #357) and joined a large field of several hundred riders, although most were doing shorter routes. Typical of Hill Country mornings, the sky was about 70 percent obscured by thin clouds, and the temperature hovered around 20°. You couldn’t ask for a better forecast for a long ride.

Having suffered three flats in recent months, I imagined that my rear tire wasn’t holding air pressure well and chose ask the mechanical support tent to replace my inner tube at the last minute. That work left me with just enough time to line up at the start with my buddy Jordan and his friends John, John, and Bob.

While swapping my tube, I heard snippets of the organizer’s pre-ride announcements, which mentioned some rough gravel sections of the route, a detour, and route markings. He said something about the 100-mile route coming back the to the start and then going out again on a second route to complete the full distance. I was already confused about the route because the organizer hadn’t provided a downloadable GPS course, while the cue sheet and two maps on the event website all disagreed with one another. And none of them had shown a mid-ride return to the start.

So as we rolled out at 8am, I wasn’t just worried about aging and my fitness, but also my tire, the route and any detours, the gravel sections, and the route arrows.

The first 22 km of the ride included a couple small hills before the course flattened out. More taxing was the 20 km/h headwind, which would persist through the north- and east-ward first third of the ride. We were quickly onto empty country roads through endless farmland and cornfields already showing ears with silks… in mid-May!

Fields and fields and fields and fields and...

I was taking it easy, but keeping up with the pack. My friend Jordan disappeared down the road, but his outgoing buddy Bob and I chatted off and on as the miles ticked away. I zipped past the first two water stops before finally pulling off at rest stop #3 for a 5-minute break. It was 9:20am, and I’d covered 37 km.

Having finished the northeast-bound part of the course, we turned south. The change put the wind behind us, which was a delightful benefit on the endless false flats we covered. At 10:30am I pulled into water stop #4 for another quick refill. With 65 km down, I was on pace to complete my century in 6:10!

This was where things got frustrating. First my GoPro battery died after just 17 still photos. And 30 minutes on I felt the tell-tale squishiness of my rear tire going flat: the very misfortune that I’d hoped to avoid by installing a new inner tube. Ironically, it wasn’t due to a puncture; the leak was at the valve stem, indicating a manufacturing defect in the brand-new tube I’d gotten at the support tent.

Somehow, one of the few support vehicles pulled up almost immediately, followed – equally improbably – by the aforementioned Bob, John, and John trio. After installing my remaining spare tube, it took two of us to manhandle the tire back onto the rim, and we’d lost 20 minutes by the time we set out again. With 85 km still to go, no spare tubes, and gun-shy after my recent spate of flats, I decided it would be safest to continue riding with these guys, who were doing a more relaxed pace than I had been.

Having just had a long break, we skipped nearby stop #5 and rode on to stop #6, where we arrived just after noontime with 99 km on the odo. There was still some high overcast, but much of the fog had burned off, and temperatures had climbed moderately toward 26°.

Along the way, one of the Johns and I discussed the route, because none of the riders or support staff had any idea which of the several conflicting routes was the “real” one. Fortunately, John’s plan and my route gleaned from the cue sheet were in agreement, so we committed to that option, and to hell with the official route, whatever it was.

Texas: not unlike Ohio, Penna, or Mass

On the following segment, we endured about a mile of gravel road (where I fretted about my tire), followed by a gulley where Opossum Creek was just high enough to spill over the roadway, forcing a ginger water crossing. Along the way, Bob and the other John peeled off to complete shorter routes; but the remaining John and I were joined by another century rider named Dodge.

We rolled into rest stop #8 at 1:26pm, having completed 125 km. I was starting to feel the effort in my legs and traps. The whole day my Garmin bike computer had steadily predicted – based on my previous training – that I’d run out of stamina after 115 to 120 km, and it was eerily accurate.

This was actually the same location as stop #1, so we were pretty close to the start. But in order to complete the full century route, we needed another 35 km. This was the dubious part of the route, but the three of us agreed to follow the cue sheet, which did a 28 km loop by doubling back and rejoining the roads we’d already ridden. That included a second passage of the short gravel section and the Opossum Creek crossing, where I dunked my cycling sandal-clad feet in the stream to cool off.

And in no time (about 70 minutes, akshually) we rolled right back into the same rest stop, arriving at 2:50pm, now with just 9 km left to go.

After a minimal rest we knocked out the final segment back to the start/finish, hitting 100 miles (161 km) just before the end, celebrating Dodge’s first-ever 100-mile ride – and my 109th!

Reflections

While I can’t say this ride was spectacularly special, it did provide some memorable elements.

Most importantly, it gave me back my mojo, after such a difficult experience on my last century, eight months ago. It proved that – despite my age – I still have the strength to complete a 100-mile ride, even early in the year and in the absence of adequate training rides.

One of the reasons why it wasn’t a more painful experience is that riding with Bob and John forced me to pace myself. Although I thought I was being conservative at the start, my average power riding solo before I flatted was 152W, while after I flatted and joined them it was 112W.

My only physical complaints were growing pain in my traps toward the end of the ride, and saddle irritation in the days following.

One mistake was that I forgot to take the electrolyte caplets I’d brought along. That wasn’t an issue thanks to the temperate weather, but I don’t want to overlook that in future, more challenging (i.e. hotter) events.

In terms of equipment, the obvious issue was riding on an untested inner tube and worn tire. The entire second half of the ride was tinged with fear that I might have a second flat, but my backup tube performed flawlessly. But I do need to practice re-seating my tire on the rim, and am considering trying out a set of Pirelli P-Zeros over the tight-fitting Conti GP5000s.

And I can’t let it pass that I finished the 7½-hour ride with 56% battery charge left on my Garmin cycling computer, thanks in part to the 45 minutes of charge gained from its built-in solar panel. It’s nice no longer needing to carry a USB power bank and plug it in halfway through a long ride. And the unit’s stamina estimates again proved surprisingly accurate.

But the biggest worry and inconvenience was the organizer’s poor communication of the ride route. The overview map depicting all half-dozen courses was unclear. The 100-mile route map was incorrect, only showing an 86-mile route with no inner loop. The cue sheet included that inner loop, but that contradicted the other two maps. And the verbal announcement at the start said something about returning to the start, which wasn’t on the cue sheet or any map!

Out on the road, the half dozen routes were marked by colored arrows, but no one had labeled which color arrows went with which distance, so when they diverged, riders had to guess which arrow to follow. At every rest stop, riders were asking which route was correct, and the volunteers couldn’t do anything but point at the map. And after all that, the arrows painted on the road veered off and went in yet another direction altogether!

Of course, all this would have been avoided if the organizer did what every other event does: provide GPS route files that can be downloaded to one’s bike computer. I have no idea why the organizer neglected to offer this basic service, especially when their vague maps and cue sheets and arrows all contradicted each another. But setting that frustration aside, in the same way as I did during the ride…

I did enjoy the event. It had been nearly two years since I had a satisfying century ride, and I really needed the confidence boost that this one provided. I’m glad I did it, and glad to have my first century of 2024 under my belt. And I expect to return to the Red Poppy Ride, albeit after taking extra precautions to clarify the intended route.

Back on September 10th, I completed the 100-mile Livestrong Challenge Austin ride and raised $875 for the Livestrong Foundation.

Rather than give you the usual chronological ride report, I’m gonna organize this mostly by themes, in hopes that it will be both more effective and readable. Are you with me here? Let’s start with the elephant in the peloton…

The Decision

My decision to participate will surprise those of you who know my feelings about Lance Armstrong, the Livestrong Foundation’s disgraced founder. I don’t ever want to contribute in any way to the fame or fortune he has amassed from lying to the public and terrorizing the people around him.

So what convinced me to do the Livestrong ride? Here are the factors that went into my choice:

• Lance has left the organization and is no longer involved in any official way. After suffering due to their association, Livestrong have wisely distanced themselves from him, although he remains their largest financial backer.
• There are surprisingly few century rides here in Austin, and it’s been a long eleven months since my last one (back in Pittsburgh).
• I hate cancer even more than I hate Lance, and Livestrong does admirable work for cancer survivors.
• I have two friends who are Livestrong bigwigs, and their vocal support of the foundation earns it a degree of approval. My childhood friend Scott is on their Board of Directors and is a survivor of testicular cancer; and Steven, the leader of the Pan-Mass Challenge’s popular Team Kermit, is a Livestrong Ambassador (i.e. a distinguished volunteer).
• Along with Steven, several other PMC friends from Boston come down to Austin for the Livestrong ride.

So while I hate the idea of being associated with Lance Armstrong, I don’t think it’s unreasonable for me to take part in this ride. But I took perverse pride in wearing my 2011 PMC jersey during the event.

Poor Training and Lead-Up

Ornoth with Scott & MJ

Scott, Ornoth, & Steven before the start

Ornoth lined up in the VIP starting area

MJ & Scott, Steven & Ornoth ready for the start

Ornoth rolling out with Team Kermit

Rolling through the ranchland in Driftwood

Scenic level crossing on the Blanco River

ClimbPro showing Fulton Ranch hill

Team Kermit's Ornoth, Christophe, and Steve after conquering Fulton Ranch hill

Real-Time Stamina, estimating 21% or 17km remaining before bonking

Ornoth dragging himself toward the finish

Ornoth crossing the finish line

And having finished, collapsing

Not looking good post vomiting after the finish

Solar power gain, showing 71 minutes gained over a 9-hour ride

May, June, and July were filled with short rides focused on becoming Local Legend on the Ladera Norte hill. So I didn’t begin training for distance until August. And August’s training was cut short after badly throwing my back out. Right when my training should have been peaking, I was off the bike for ten days, while the small training effect I’d gained atrophied away.

Four days before the event, I was just getting back onto the bike when Team Kermit members started assembling in Austin. They were looking to meet up and ride every day, right when I would normally be tapering my training in order to be well-rested for the event.

Instead, on Thursday before the (Sunday) event, local Austin Kermit member Scott led a group of five of us up the Walnut Creek Trail, then back to 51th Street for lunch at Jewboy Burgers. Then on Friday I led a sightseeing ride up the Shoal Creek bikeway and back down Scenic Drive. We finished at event packet pickup, where I received a Livestrong Challenge cycling jersey and VIP rider bib tag #28.

I took Saturday off while the Kermiteers spent the day doing another long ride down to the Veloway park. I’d ridden 150 km in two days and was suffering for it. My back was still iffy, my ass was abraded, and my legs were too tired to tackle a hundred-mile ride without rest. At the same time, I hadn’t eaten or slept well, was already dehydrated, and down 1.8 kilos of body weight in a week. For the first time, my final ride prep included zip-tying a stuffed Kermit doll to my helmet, complete with white cowboy hat and rodeo bull-riding pose.

Quick Ride Summary

My Strava activity’s description summed my Livestrong Challenge up best: it was very good until it wasn’t.

After about five hours of sleep, I got up at 4:30am and set out in darkness at 5:45 on the 15 km ride downtown. I rode with Team Kermit from their hotel to the start, where we lined up in the VIP section before being set loose on the streets of Austin at 7:30am.

At the tail end of a brutally hot summer, the ride began under pleasant temperatures that warmed considerably, but not to the extremes that we’ve lived under for the past three months. South from Austin to Buda, then west and south through Driftwood.

Enjoying the freedom of having two water bottles rather than one, I skipped the first three rest stops out of a desire to stay ahead of the pack and beat the time limits for the 100-mile route, which the organizers had shortened by 30 minutes. So my first break came two hours in, after 57 km, (or 72 km if you include my 15 km commute to the start). As you might guess by such a long stretch without a break, I had been feeling good thus far.

I refilled my bottles and marshaled some strength for the long, steep hill at the end of the next segment. I enjoyed the pleasant tree-lined streets near Wimberley, and a stunning level crossing of the Blanco River. Then came the 15% grade climb up Fulton Ranch hill, which is essentially the halfway point of the course. It was quite manageable for a cyclist used to the much lumpier terrain back in Pittsburgh. At the top, a water stop beckoned; I pulled in at 10:30am, having taken three hours to knock out 77 km (or 92 km).

While resting here, Team Kermit members Christophe and Steve rolled in, and we would leapfrog each other for the rest of the 110 km trek back to Austin. But this would be the point when things slowly started going to hell. The temps climbed through the 30s, and I was feeling the effort in my feet, legs, lower back, traps, and hands.

As my reserves dwindled, my speed and power dropped, and my horizon shrank to simply reaching the next rest stop. I hadn’t eaten any solid food during the whole ride, and was pounding fluid in an attempt to address both heat and thirst. Extended 15-minute rest stops and hand towels soaked in ice water were just enough to keep me from blowing up.

I stopped twice to battle fatigue and nausea during the last segment to the finish, but completed the final loop around Auditorium Shores. The event photographers captured my grim visage as I crossed the finish line at 3:07pm. I’d completed the official 158 km official course in 7h 37m, but had fulfilled my 108th imperial century by riding 15 extra km to the start.

I collapsed in exhaustion underneath the Team Kermit tent and waved off others’ attempts at congratulations, accepting only a folding chair and an ice-water towel. And then came that feeling we’re all familiar with: a particular certainty that it’s time to find a convenient but discreet place to deposit some biological material. So I staggered nonchalantly over to a nearby trash can and retched about three gallons of undigested fluid that I’d carried with me over the preceding few dozen kilometers.

So my Livestrong Challenge ended successfully but ignobly. I managed to recuperate enough to stand for a team picture before I said goodbye, then met up with my partner Inna, who mercifully drove me those extra 15 km back home.

My First Century in Eleven Months

This was my first 100-mile ride since October 2022. Eleven months is a long layoff; I haven’t gone that long between centuries in fifteen years (since 2007-2008)! You ask me how it went? Go back and read the summary: it was very good until it wasn’t.

Mistakes were made. Looking back on it, nearly all of them were about my personal physical fitness and decisionmaking, not my equipment or the location or the event. So I guess that would be the logical place to start…

My Fitness and Decisionmaking

A century always demands a lot of stamina and will power from me, but this was an exceptional case. Despite being one of the first dozen riders out of the gate, then skipping three rest stops, I only marginally beat the last finishers on the course.

I could blame the Texas heat, but even at 37°C (98°C) it was mercifully moderate in comparison to the seventy days above 38°C (100°F) that Austin experienced over the summer.

Or I could blame my age. After all, I’m only weeks away from my sixtieth birthday, and that’s the kind of thing that can slow a guy down.

While those are valid considerations, there was a whole panoply of other factors that impaired my performance, leaving me with weak legs and zero stamina toward the end of the ride.

Despite not doing any long rides in nearly a year, I barely did any lengthy training rides prior to the event. I went into it fatigued and dehydrated from too little sleep and too much riding just before the event. I was insufficiently fueled due to an irregular eating schedule and not eating any solid food during the ride. And I still had lingering injuries to my lower back and my backside (the latter attributable to insufficient time in the saddle).

But the biggest wildcard was hydration. Consuming two bottles over the first five segments of my ride – especially since the first segment was a casual commute – doesn’t seem like an especially egregious error. But it set me up poorly for the second half of the ride, where my perceptions of thirst and heat were clearly malfunctioning, causing me to take in more fluid than I could digest. This is the biggest thing I’ll have to monitor on future long rides.

There were lots of physical niggles along the road, of course. Early on, I had to make a quick roadside stop to flush some stinging sunblock out of my eyes. In my cycling sandals, some pain developed in my big toes, but I got away without a repeat of the abrasions I’d gotten on top of my feet a couple weeks earlier.

And I’d expected pain in my hands due to a slight change in my position on the new bike. I did have some discomfort, but not the severe palsy that I’d feared. It would be prudent to address this soon by buying new cycling gloves and plush handlebar tape.

The New Bike

Like its owner’s ride, my new Specialized Æthos was very good until it wasn’t.

It looked like Pæthos came through its first century in flying colors, to the extent that I had very little to say about it, other than that it suited me well and earned my full confidence.

Two weeks before the event, I’d gotten a flat on a pair of brand new tires. That got me so worried about the rough chipseal of Texas back roads that I’d carried two spare inner tubes, in addition to a pump, a CO2 dispenser, and a Shrader-to-Presta adapter in case I needed an automotive air compressor. That was all overkill; Pæthos appeared to handle everything that was thrown at it.

Just before the ride, I’d also converted from one water bottle cage to two, which was a big win. That gives me the flexibility to ride farther unsupported or without stopping (e.g. skipping three water stops). But it also gave me the option of carrying both sport drink for hydration and clear water to pour over my head and body when the heat was at its worst. And I did lots of that on the Livestrong ride!

But those Texas roads did get me in the end. After I got home, I noticed a break in the carbon rim of my rear wheel, which most likely happened due to a rock strike somewhere along the Livestrong route. I took it in to Specialized to see if it was rideable or a case for a warranty replacement, and they chose to replace the rim. Pretty ridiculous that my first set of carbon wheels lasted a mere 4,000 km.

The New GPS Bike Computer

This was also the first century-length test for the Garmin Edge 840 Solar that I picked up last month, which delighted me in nearly every way. On top of flawlessly handling mapping and turn-by-turn navigation, it now sports graphical data fields (e.g. power and heart rate charts), and the new ClimbPro feature, which tracks your location on an elevation profile of the current climb.

While cool, I had already tested that stuff; I was more eager to try out some other features that could only be done on a century-length ride. After all, I couldn’t finish my full review until I’ve put it through all my typical use cases.

Top of the list was battery life. The battery on my old Edge 820 had deteriorated to the point where I had to plug it into a portable USB battery for any rides longer than 90 minutes. The new unit claimed 26 to 32 hours, and I finished my 10-hour day with a whopping 72% charge remaining. I think I can finally leave my USB charger at home for good!

Of course, that includes the benefit I derived from the unit’s solar charging feature, which in Texas is a painless way to give the battery slight boost. Over 9h 15m the unit gained about 72 minutes worth of solar power, or about 8 minutes per hour. Not revolutionary, but not trivial either!

The other major feature I wanted to test was Garmin’s new “real-time stamina” estimate, which supposedly learns your physiology and provides a real-time guess about how long you can go until exhaustion. At my first rest stop, it estimated that I had 55% stamina remaining, and – ominously – that my reserves would run out 40 km before the end. I monitored that number all afternoon as it fluctuated, but it consistently told me that I’d have nothing left in the tank for the last 25-35 km of the ride, which is exactly how things played out. It was surprisingly accurate, given the variables that it didn’t know about, like fueling and hydration.

One feature came as a complete surprise to me. When Kermit team leader Steven texted us to ask where we were on the course, I deliriously scrolled down through the usual canned, stock responses for something appropriate as I continued pedaling. At the bottom of the list was something my old unit had lacked: the ability to actually type a freehand text response right there on the head unit! So I was able to pound out a response that truly captured my feelings in the moment. In response to his “How far out are you??”, I answered “Lifetimes”.

The only glitch I had was a minor one. I’ve always had an alert set to pop up when I reached the 100 mile threshold, but it never showed up on the new computer. I’ll have to re-test that, the next time I get the opportunity to pound out a hundred-mile ride.

My Friend Scott

As I mentioned above, my childhood friend Scott is on the Livestrong Board of Directors and is a survivor of testicular cancer.

Our friendship goes back fifty years to 1972: 3rd grade back in Maine, Cub Scouts, then French and several other classes through middle and high school. After going separate ways for college, 25 years later we rediscovered each other and our common commitment to cycling to combat cancer. In 2008 he rode the Pan-Mass Challenge, so it seemed appropriate for me to take part in his preferred event, especially since I’m now based in Austin.

I ran into him and his partner MJ outside the hotel as we were both heading to the start, and got to chat with them a little more just before we lined up for the depart. It was the first time I’d seen him in ten years, and it was wonderful to touch base, although it was much briefer than it deserved… Hopefully another time.

Steven and Team Kermit

My friend Steven is both a Livestrong Ambassador and the captain of the Pan-Mass Challenge’s very popular Team Kermit, founded in honor of – and continuing in memory of – his son Jared. I have several connections in the group and have ridden alongside numerous Team Kermit riders in the PMC all the way back to their founding in 2005. Most recently, I’ve nurtured friendships with several Kermiteers by riding with them virtually on the weekly PMC Zwift indoor trainer rides.

While I’ve never ridden the PMC as part of a team, I thought it would be fun to bolster Team Kermit’s numbers on the Livestrong ride, so I registered as an official team member. The days preceding the ride were spent tagging along – and even leading – some fun local sightseeing rides for our traveling visitors. Taking charge was local Austinite and Team Kermit member Scott.

Riders Christophe and Steve I only knew from the Zwift group rides, so it was nice to put names with their faces. They rode with me for the second half of the century route, and their companionship was absolutely invaluable.

I’m very much a lone wolf, so there were several times when I felt awkward as a member of a team, especially a team who decorates our helmets with large, stuffed Kermit toy dolls, which gets a ton of attention and comments! But they’re truly good people, and I was happy to be allowed to represent them.

Riding in Texas

This was my first century-length ride in the Lone Star State, which I view as a milestone, since it’s such a vastly different environment from my familiar riding in the Northeast.

My top concern was the Texas heat, especially after months of temperatures hovering at or above 40°C. Riding in that kind of heat is seriously dangerous, and I wanted to be sure my first long ride offered the kind of generous support you get on large charity rides. Wisely, most centuries down here take place in the spring and fall, and we were lucky that event day hovered just below 40°C. But temperature concerns will always be present for every ride I do down here.

My second concern was the roads, not knowing quite what to expect in terms of traffic, surface quality, and space to ride. In the end, those things all vary. There were trafficky bits and quiet bits; there was smooth tarmac and ample rough chipseal; broad roads with dedicated bike lanes and narrow, single-lane roads without even a shoulder. Finding quiet, comfortable roads for long, solo rides is just going to require some investigation.

Once outside of the city and its immediate suburbs, the terrain was mostly what I’ll call scrubland. Plots of large ranches with low, hardy, weatherbeaten vegetation like juniper (which Texans call “cedar”) and live oak. There aren’t a ton of rivers and creeks – and those are nearly all dry after the summer’s heatwave – where you often see dramatic exposed limestone. It has a lot of character, without being entirely desert or prairie. The Blanco River crossing was really interesting, and I even shared the road with a roadrunner while climbing out of it.

At a macro level, riding in Texas is going to take some adjustment, but it should be amply doable, with careful scouting and route selection, and more experience managing my hydration.

Livestrong: the Event

This was also my first Livestrong ride. How was that?

The route was mostly fine. My only complaint was is that because the start/finish is downtown, a large percentage of the ride was urban and suburban strip mall hell, leaving less than a third of the route for scenic rural country roads. The entire second half of the ride paralleled ugly Interstate 35 on the run back to Austin. But the scenic bits we did get were thoroughly pleasant.

Ride support was generally great, with no less than nine water stops spaced about 16 km apart, well-stocked with ample ice and wet towels, although no cola was available until the end.

As a rider, the cutoff times for the century route were not especially generous, particularly after they were shortened an extra 30 minutes. Fortunately they weren’t an issue for me, though.

The fundraising minimum (ZERO!) was surprisingly welcoming, with premiums offered at varying – and entirely voluntary – fundraising thresholds. By raising $875, I earned an on-course tribute sign, a tote bag, a tee shirt, a cheap mini Bluetooth speaker, the ubiquitous water bottle, an event cycling jersey, and a finisher’s medal, plus the right to line up in the VIP section at the head of the ride. That’s a much friendlier model when compared to the PMC’s $2,000 to $6,000 fundraising requirement just to participate!

Unlike the PMC, where thousands of spectators — often former patients and their families – line the entire route and thank you for riding, community support was mostly non-existent on the Livestrong ride. Other than the crowd at the start/finish, a few bystanders waving from nearby bus stops, and water stop volunteers, during the entire ride I only encountered one couple sitting at the side of the road in the middle of nowhere, cheering their hearts out. The two events couldn’t be more different in that respect.

It all adds up to a mixed picture: a well-run and rider-friendly event for an organization that has wisely distanced itself from its shameful founder, and which Scott and Steven have convinced me does admirable work helping cancer patients and their families. And even if it’s no Pan-Mass Challenge or Dana-Farber Cancer Institute, I’m very likely to participate again in the future, for the same reasons I outlined above.

Epilogue

So there you have it; it was a landmark ride. To encapsulate, it was:

• My first Livestrong ride
• My first imperial century in 11 months
• My first century of 2023
• My first century in Texas
• My first century on Pæthos, my new bike
• My first century with my new Garmin bike GPS
• My first event as an official member of Team Kermit (or any team, for that matter)

While this century included a grim struggle and an ignoble footnote, I hold to my words that it was very good until it wasn’t. Troubles aside, I completed the course safely and enjoyed the overwhelming majority of it, and gained lots of lessons to bring forward for future rides. I enjoyed it immensely and am glad to have done it.

You’d think a ride visiting every recognized neighborhood in the city would be fairly straightforward… but it’s not.

No, actually it’s one of the hardest rides I’ve done. First, there are no less than 90 neighborhoods, separated by Pittsburgh’s canonical three rivers. That means it’s going to be a long ride: about 120 km, in fact. Also remember that this is the hilliest city in America, so the route has to pack in over 2,000 meters of climbing (over 1¼ miles of vertical elevation, for the primitives in the audience). Combine the two, and you’re talking a minimum 8+ hours in the saddle. Plus it used to be held in the worst of August’s heat.

Although I debated whether I really wanted to, in the end there was no choice but to do this year’s Every Neighborhood Ride (ENR).

The handful of finishers at Arsenal Park

Riders gathering at Doughboy Square

Riding along the Allegheny on Pittsburgh's North Side

Why? First, it would be something entertaining to do while my partner Inna was out of town for a week. Second, the date got moved from the heat of summer to early October, which would make it a lot easier. Plus, although I loyally rode in 2016, 2017, and 2018, I missed the 2019 ride while up in Michigan doing LHT, and it wasn’t held in the Covid years of 2020 and 2021. And if missing the ride for three years wasn’t reason enough, riding a few miles farther would also allow me to complete my sixth century of 2022.

So Saturday I found myself on the road at 7:20am, pedaling the short 6 km down to Doughboy Square in a very chilly 5°C. I’d donned most of my cold-weather riding gear, including full-fingered gloves and my priceless thermal cycling jacket and bib tights.

About two dozen riders gathered there and chatted before perfunctory instructions and our roll-out. Within a block the group had split, with about ten riders speeding ahead in Jake’s fast group. I maintained the self-discipline to stick to my plan of staying with Jen’s slow group, having paid the price in previous years for over-exerting myself chasing Jake.

The first leg saw us cross the Allegheny to touch Pittsburgh’s North Side neighborhoods, then make a very quick trip across the Ohio and back to set foot in the West End. A dozen kilometers in, we faced our first long climb – East Street – where I got ahead of the group and waited at the top. After a screaming descent down Marshall Ave., we finished up the North Side and crossed the Ohio to hit McKees Rocks and the climb up to the first rest stop at Chartiers Playground.

It was 10am and we were 30 km in. The sky was heavy overcast, but the sun had broken through the clouds for a few seconds. It wasn’t warming up much, but my gear kept me warm everywhere except my face. My biggest concern was for my 5½ year old bike GPS, whose feeble battery could barely hold a charge in the cold. Fortunately, I’d brought along two portable chargers to see me through.

The second leg caught almost all the neighborhoods in the South Hills, which was the lumpiest portion of the route, causing the group to start rubber-banding a bit. That meant the pace was very gentle, with lots of brief rests while the slower riders caught up. People usually begin dropping off near the second rest stop, so a few riders said goodbye at that opportunity.

We reached that halfway stop in Allentown at 12:25pm with 60 km done. At 10°C, I felt it was warm enough to strip the arm warmers underneath my jacket, as well as my skull cap. At this point, the ride had been so relaxed that I began to entertain the idea of riding the extra 40km to finish my sixth imperial century of the year.

In the third leg, we finished off the South Hills by illegally crossing some active rail lines, taking the GAP bike path through Hays and down to Lincoln Place, then crossing the Monongahela River. But as soon as we did, one rider flatted, which provided an unplanned 20-minute delay. That was followed by the familiar but long climb up Hazelwood, the screaming descent down Forward, and the short gravel hike-a-bike through Frick Park along Nine Mile Run to our final rest stop, which had been relocated due to January’s Fern Hollow bridge collapse.

It was 2:40pm, and we’d covered 89 km. The clouds were starting to way, and the temps had reached a still-chill 12°C, and would only go down from here. We lost a couple more people, but gained the three that were left in Jake’s fast group. My bike GPS had finally exhausted my first portable charger after five full charge cycles, so I swapped to the second.

The final segment is always something of a cluster. It amounts to a hilly circle and a half of the inner city, and many exhausted riders simply peel off toward home whenever it’s convenient, rather than completing the full ride. And the few who remain require frequent regrouping and ad hoc rest stops. Along the way I finally took off and stowed my heavy gloves.

The chaos was compounded by construction and a route change occasioned by the absence of the Fern Hollow bridge, which was formerly part of the route. On top of that, my bike GPS wouldn’t navigate any farther, because it had exhausted its route storage of 200 waypoints; so instead of helping navigate, I was glued to the ride leaders for the rest of the ride.

Finally nine weary riders pulled into the finish at Arsenal Park at 5:16pm, having covered 123 km and climbed 1,788 meters in 9¼ hours. Post-ride chat was amicable but brief, as people looked homeward. With the clouds mostly gone and sunlight fading, I made my own farewells, hoping to squeeze out another flat 40 km to complete my imperial century. I was going to be cutting it close…

Actually no, I wasn’t. I still had 15 km to go when the sun set at 6:51pm, and I didn’t pull into our driveway until 7:35, after more than 12 hours of riding. But before then I covered the bike paths out to the Penitentiary, then the jail trail, Panther Hollow, and the always-frustrating final climb back up to Squirrel Hill, the latter in complete darkness with no headlight. But I was happy to complete my sixth century of the year.

Despite riding 100 miles and climbing over 2,000 meters, the casual pace had conserved my strength, and most of my aches weren’t from over-exertion but simply accumulated time in the saddle.

The Every Neighborhood Ride is one of Pittsburgh’s best and most unique cycling events. You’re usually in a small group of companions, all working to overcome this city’s profoundly ill-conceived topography. And it’s unique among group rides in that you’re with that same set of companions for seven, nine, maybe twelve hours, chatting, encouraging, and getting to know one another. That, plus congenial ride leaders, makes ENR one Pittsburgh ride that I’ll miss when I move on from here. It was nice to come back to it after three years away, and it was a nice and easy – if very long – day out.

My second year riding in Pittsburgh somehow felt both pleasantly normal as well as superlative and memorable in so many ways. Overall, I rode a ton, befriended some good folks, grew more familiar with my new hometown, set some new records, met all my goals, vanquished Pittsburgh’s hardest challenge, and had a blast doing so. Here’s my year in review…

Team Decaf group ride at the Point, with Ornoth back center

Ornoth crushing a hill on the Escape to the Lake MS ride

Ornoth & Monica finishing the Pittsburgh Randonneurs' 100k populaire

Ornoth leading a pack through the city during PedalPGH

Ornoth descending Dirty Dozen Hill 6 (Rialto) from the neighborhood of Troy Hill.

Video of Ornoth (in black) amongst a group of Dirty Dozen riders (around 3:02) to the top of Suffolk St.

Great closeup action shot of Ornoth ascending Dirty Dozen Hill 9 (Canton Ave).

Video of Ornoth conquering the upper half of Canton Ave (10:50 to 11:00).

The tired-but-happy look of an official Dirty Dozen finisher!

Ornoth's 2017 Cycling Calendar

My Original 2017 Goals

This time last year, I set four explicit goals for 2017.

Purchase and learn how to use a new Garmin Edge 820 GPS cyclo-computer. This was the first thing I did upon getting back to Pittsburgh in February. The 820 has a lot of new features, some of which actually work. The D-Fly integration with my electronic shifters has mostly worked, despite the added drain on the Di2’s battery, and I’ve enjoyed perusing my shifting data on di2stats.com. I created my own custom data field (feet of ascent per mile) for display on the 820, and got Shimano’s E-TUBE app working such that I can update my shifters’ firmware from my phone. While the 820 didn’t live up to what it should have been, it’s been a steady performer and a worthwhile purchase. Read my full Garmin Edge 820 review.

Ride both days of the 2017 Escape to the Lake MS Ride. My partner Inna’s support made this weekend expedition possible, and it was a lovely experience. Not only did I get to complete the event and finish on the very shore of Lake Erie, but Inna and I stayed and spent an extra day lounging on the lakeside beaches of Presque Isle State Park. It was very reminiscent of my Cape Cod trips with Sheeri back when she supported my Pan-Mass Challenge rides. Read my Escape to the Lake ride report.

Complete the 2017 Woiner Cancer Foundation 3-2-1 Ride. This became a primary goal after I missed the 2016 ride during my mother’s hospitalization. In 2017, they offered a special 80-mile route to VIP fundraisers from 2016 (which I qualified for), so on October 1st I saddled up for a long, chilly, flat ride along the Great Allegheny Passage from Ohiopyle back to Pittsburgh, most of it on crushed limestone rail trail. I enjoyed exploring some new territory while further increasing the amount of money I’ve raised for cancer research. Read my 3-2-1 Ride report.

Attempt my first Dirty Dozen race. Climbing the city’s 13 steepest hills, including the steepest public street in the world, this is an immense challenge, and the city’s most infamous ride. I missed last year’s edition while caretaking my mother, but this year I participated in all the training rides, then enjoyed an immensely fulfilling and memorable ride on race day, earning hard-won lifetime bragging rights. Unquestionably the highlight of the year. See my training rides blogpost, my full Dirty Dozen ride report, and my time-lapse videos of the most difficult hills.

Additional Highlights

Achieving all my explicit goals guaranteed that I had a good year. But there was an awful lot more to 2017 on top of that…

• Further deferring my job hunt gave me the entire year off to devote to cycling, and I made good use of the opportunity. I topped 4,000 miles for the first time since 2010. And I shattered my record for number of rides per year; this year’s 154 rides is about double number of rides I used to do in Boston.
• I continued meeting and befriending lots of local cyclists, which has been rewarding, and one of the biggest overall themes for 2017. It’s nice when someone recognizes you, which is happening regularly now, so I’m starting to feel more like a known community member than an unfamiliar outsider.
• I attended both the Spring Rally and Fall Rally organized by the Western Pennsylvania Wheelmen, and got a snazzy new WPW jersey.
• I claimed 13 more tags in the BikePGH forums’ Tag-o-Rama cycling and photography game, placing me within the Top 20 players. It’s been an interesting way to learn more about the city. See all my Tag-o-Rama photos.
• I was quoted (anonymously) in BikePGH’s summary of their survey of cyclists’ attitudes toward self-driving vehicles, and re-quoted in the Pittsburgh Post-Gazette’s article covering the survey. I was righteously amused. Read my self-driving vehicle blogpost.
• I participated in the National Bike Challenge, confirming that I’m around the Top 10% most active cyclists locally, state-wide, and nationally. Read my National Bike Challenge blogpost.
• I joined a half dozen other BikePGH forum readers in playing Velogames’ annual Tour de France fantasy league. It was interesting, but my team selections placed me near the middle of the pack. Oh well!
• I picked up an attractive graphic poster of the “Hell of the North: Paris-Roubaix”, which is hung above my desk at home.
• I continued to maintain BikingPGH’s Annual Ride Calendar, as I described here, and also iterated on my paper-based cycling wall calendar. Both have been useful planning tools that I’ll continue working on for 2018. Here’s a link to the full size 2017 version.
• I picked up two absolutely pivotal pieces of kit: a thermal cycling jacket and a pair of thermal full-leg bibs, both from my favorite manufacturer: Craft. Those have utterly transformed my relationship to cold-weather riding, and made even the 17° Dirty Dozen practice ride a pleasant experience.
• My Strava trophy case added badges for completing climbing challenges and gran fondos for April, May, June, July, and August, plus a gran fondo for October. Ironically, despite training for and completing the Dirty Dozen, as well as my 250,000-foot climbing goal, I failed to earn Strava’s climbing challenge badges for October, November, or December!
• That 250,000-foot goal, as well as the six centuries I rode in 2017, are highlights that I’ll discuss in more detail in the next section.

The Charthouse

Last year’s annual summary included a chart showing that my first year riding in Pittsburgh utterly shattered all the previous climbing records set during my years in Boston.

In 2017, I eclipsed last year’s record, surpassing a quarter million feet of climbing (47 vertical miles), more than double the climbing I’d ever done back in Boston. My 62 feet of ascent per mile ridden is also a new record. You can see an updated version of that climbing chart by reading my 250,000 foot blogpost.

Also in last year’s summary, I used the Strava Premium and Stravistix TRIMP “fitness and freshness” charts to tell the story of my year and put it into context with previous years, so I’ll do that again here. In 2017 I used the detailed TRIMP charts exhaustively in planning my pre-event training and recovery, which proved remarkably effective.

The above chart shows my fitness level over the past twelve months, with major rides highlighted. Obviously, I started the year with zero fitness after spending five months off the bike while caretaking my mother. You see a big jump when I got home in February, followed by a period of consolidation; another jump in mid-April, which kicked off a lengthy and consistent improvement leading up to my first century of the year: the two-day Escape to the Lake MS Ride in mid-June.

After finally notching that first 100-mile ride, my fitness stayed at a high level through my four summer centuries: the Akron Bicycle Club’s ABC Ride in July (a new event to me), followed a week later by the PMTCC 3-State Ride (when my fitness peaked), then August’s Every Neighborhood Ride, and PedalPGH (which were both long group rides that I extended into full centuries).

My fitness dipped noticeably during a two-week vacation in September before a quick spike for my first 3-2-1 Ride on October 1 (a long charity ride that I extended for my sixth and final century of the year).

The next two months were spent preparing for the Dirty Dozen ride, but hill climbs don’t accrue as much fitness benefit as endurance rides, so although I was gaining power, you see a jagged slight downward trend in fitness there. After the Dirty Dozen, my fitness remained high to the end the year, while I polished off my goal of climbing a quarter million feet in 2017.

Tacking my 2017 fitness onto the end of the chart to depict my past seven seasons tells the same story in brief: beginning from ground zero, an initial kick, consolidation, and a second kick up to peak fitness. I stayed at a high level of fitness for a much longer time this year, thanks to training for November’s Dirty Dozen and my climbing goal-driven riding in December.

All that late-season riding drives the major difference between 2017’s curve and that of previous years: I’m ending the calendar year at a much higher level of fitness than ever before. Now, whether that will translate to better form next spring is an open question, and will depend on how much riding I do in January, February, and March.

I’m sure there’ll be days that call me outside for a ride, but right now I’ll happily take a couple months to rest and recover.

Goals for 2018

It feels kind of strange, but I’m going into 2018 without any major cycling goals.

Having two seasons under my belt, I’ve done all the new rides that I wanted to experience when I moved here, so I don’t feel like I have any unfinished business that needs particular attention.

I’m happy with my fitness, my equipment, my knowledge of the area, and the relationships I’ve been growing in the local cycling community.

So my overall attitude going into 2018 is: “Nothing specific, but more of the same, please.”

That said, there are a couple things I anticipate for 2018.

With a trip to Italy planned for May, I do hope to do some riding around the Tuscan hills, and hopefully spectate a stage of the Giro d’Italia, as well. That trip would probably be the highlight of my year, and it’s the only new experience I’m specifically targeting.

And there’s a rumor that GCN might be sending a crew to Pittsburgh next year, presumably for November’s Dirty Dozen, or at least a peek at the route. It would be fun to be involved with that somehow, although I’m not relishing the idea of doing that ride again!

And along the way, I’ll pass two milestones on my R2-Di2 bike seen here; I’ll eclipse 15,000 miles on it, which is just a round number, but at 16,800 miles I’ll surpass all the riding I did on my first bike—the Devinci hybrid seen here—reminding me that after five years “the new bike” ain’t quite so new as she used to was.

But other than those things, I’m happy to take 2018 as it comes. If it’s anything like how enjoyable and eventful 2017 was, I’ll have absolutely no cause to complain!

Three months ago, I replaced my aging Garmin Edge 800 GPS cycling computer with the new Garmin Edge 820. After 52 rides and 1,400 miles, it’s time for an in-depth review.

I’m a data weenie. I was logging my weekly miles all the way back in 2000, and saving GPS tracks of significant rides using a handheld GPS long before GPS tracking was integrated into bike computers. So I’m sensitive to the features, usability, and reliability of my bike computer.

I was really happy with the Edge 800, which I bought when they first came out in 2011. Over the years, Garmin introduced the newer Edge 810 and the larger Edge 1000, plus the smaller Edge 500 and 510, but the 800 was so good that I never felt the need to upgrade.

However, after six years, my Edge 800’s battery had begun to flag, and I was tempted by all the improved features and functions of the new units. Last July, when Garmin released a new unit in the 800 series, I read the reviews like a hawk, and finally picked up my unit in February, after I returned from my five-month stay up in Maine.

I’ll divide this review up into four sections: basic features and things I’m neutral about; features I don’t know much about because I didn’t test them; features I like and am excited about; and the things that disappoint me about the unit. Then the executive summary is at the end.

The Neutral

My biggest problem with my aging Edge 800 was battery life. I need a device that will record GPS data and provide navigational cues through at least a 9-hour 200k ride. I recently completed a 7-hour century ride, and had over 40 percent charge left, which means the Edge 820 can be expected to live up to its spec of 12-hour battery life.

I was a little concerned that the 820 has a smaller screen than the 800. On the other hand, it has better resolution. So far, reading the screen has not been a problem at all.

At a minimum, I need to be able to import GPX-formatted route data from the computer to the unit. No problem with the 820.

I also download all my raw GPS data (Garmin .FIT files) to my computer for archival. Thankfully, the 820 still supports this type of access.

Rather than coming with an SD card slot, this device has a fixed memory capacity of 8 GB. So far that hasn’t been an issue, and I can only see it becoming so if you were to load multiple continents’ worth of map data. Activity .FIT files don’t take up very much space at all.

Sometimes, if you were following a course and deviated from the path, my 800 would simply give up trying to navigate for you. The 820 hasn’t been bad, in that it tries to get you back onto the course.

Some folks have complained about the altimeter being off, or drifting during rides. I haven’t noticed a problem, given the understanding that barometric altimeters have limited accuracy by definition.

One new feature on the 820 is real-time weather alerts. This would be a cool feature, except it only receives major alerts like flash floods. Useful, but only rarely. Given that the device has a live Internet connection through a Bluetooth link to your cellphone, I’d rather see live local radar and notices of impending rain. There’s an app for that in Garmin’s ConnectIQ Store, but I haven’t tried it out yet.

Another new feature is the display of “recovery time” at the end of each ride. Basically, it’s a gratuitous, dumb feature. Recovery varies from person to person, and even a novice rider can sense how long they’ll take to recover from any given effort. I’ve turned that feature off.

One undocumented feature on the Edge 800 was the ability to set the boot screen text that displays when the unit powers up. I had set that to an inspirational message—“Always lead, never follow”—plus my phone number in case the unit was lost. I was happy to learn that the feature still works on the 820.

One evening, I learned that the Edge 820 automatically switches to an inverted-color display at night for better visibility. I’d love to say that’s an improvement, but it’s a feature that was also available on the 800; I had merely turned it off at some point!

The Unknowns

The Edge 820 comes with a power saving mode that comes on when the battery reserves start getting low. I haven’t tested it yet.

It also introduces an “incident detection” feature, where it’ll alert a contact if it thinks you’ve crashed. So many other users reported false positives that I have never turned the feature on.

Presumably you can load your own maps onto the unit. That’s a feature that existed on the Edge 800, but I’ve never felt any desire to mess with the maps that it came with. Though it might be a handy thing if you traveled or moved to a different continent…

Although Garmin did away with the idea of bike profiles, you can still set odometer values based on the sensors that are on each bike. Seems like a lot of work, and I don’t need total odometer readings while riding. I can just get that from the laptop.

The most exciting and useful feature that I haven’t had the opportunity to test is the Edge 820’s FE-C indoor trainer integration, which should allow the computer to set the trainer’s resistance level. In addition to using the Zwift social training app, theoretically you can follow a real-world course that you rode, and the unit will alter resistance to simulate the terrain. I’m looking forward to that, but that’ll require a very expensive trainer purchase, which I’ve been delaying.

The Positives

Let’s start with the obvious. Coming from a seven year old model, the Edge 820 has updated maps, and lots of software updates, both built-in as well as regular firmware updates going forward. It’s nice to be back on a supported platform!

In addition to GPS satellites, the new unit also has the ability to receive signal from the Russian GLONASS constellation, making GPS locks faster, more accurate, and stable. I suspect this is also the reason why the regular signal stops/dropouts/starts I used to have near heavy infrastructure (e.g. bridges, railways) on the Edge 800 are almost completely gone.

With a Bluetooth connection to my phone, the Edge 820 will display incoming SMS messages, and notifications for incoming calls. It works well, and has been a nice convenience, given how many hours I’m on the bike.

For ultra distance rides, you can plug the Edge 820 into a portable battery pack and it’ll charge itself, while continuing to record ride data. To be honest, I think my Edge 800 could do this, but I never bothered to test it. However, I tested the 820 for this review, and it worked well.

With my Edge 800, after a ride I had to connect the device to my laptop and manually kick off a synchronization job to upload my data to Garmin Connect, then manually upload to Strava, as well. The 820 will use Bluetooth or Wifi to automatically upload ride data to both sites without a wired connection. Very convenient, especially when you’re away from home at a multi-day event.

Garmin has created an open API called ConnectIQ for developers to add their own apps and custom data fields to the unit. A favorite is the Strava Live Suffer Score data field, which displays how hard your ride is. I’ve got a great idea for my own custom data field, but setting up the required Windows dev environment is a huge bother.

The Edge 820 also will store your favorite Strava road segments and display a countdown and timer when you are on them, allowing you to measure your effort against your PR or the KoM holder in real time. It’s a cool feature, except for the discouraging Sad Trombone sound it makes when the record-holding time finishes before you do…

With an extra bit of hardware, the Edge 820 will communicate with your Shimano Di2 electronic shifting groupset. That allows me to display which chainring and cog I’m in (both numerically and graphically), as well as the system’s current battery level. It’ll beep when you’re at your absolute highest and lowest gears, and give you a text alert if the Di2 battery goes below 25 percent charge. On top of all that, all your shifting data gets added to your ride logs, which you can analyze later through sites like di2stats.com.

The Negatives

The touch screen is really poor… nearly unusable. Every interaction with the unit must be very deliberate, and often repeated. My unit is barely tolerable, but many people have simply given up and returned theirs for a refund. It’s terrible.

Scrolling and zooming the map are incredibly slow. Like, almost unusably slow. If there’s one thing a mapping GPS should get right…

Loading and calculating routes is even worse! If I have a stored GPS breadcrumb track, it shouldn’t take upwards of five minutes for the unit to begin offering navigation cues. Why would it take even longer than the Edge 800?

When I first started using the unit, it spontaneously turned itself off several times. Fortunately, after a little while, that stopped happening.

Along with SMS and incoming call notifications, it would be nice if the unit offered incoming email notifications, as well. Missed opportunity.

I had a lot of trouble setting my Max Heart Rate. By default, the unit will override any number you specify with whatever it gets from a heart rate sensor. But since HRM straps are notorious for occasionally giving ludicrously high readings (e.g. above 220 BPM), it kept resetting itself until I shut off the auto setting and entered a fixed HR max.

Presumably, the Edge 820 supports Live Track, where you can send a URL to a friend, and they can visit a site that shows where you are in real time. In my experience, the data connection to the phone is too fragile, and I’ve never gotten Live Track to work… not even once. Both Google Maps’ Location Sharing feature and the Glympse app work far better.

Then there’s Group Track, where you and your riding buddies can presumably “Live Track” each other, with the head unit displaying the locations of your other riding buddies in real time. Even if I had other riding buddies with compatible head units (not very likely), the fact that it depends entirely on the utterly non-functional Live Track feature means I can’t use it anyways.

That cool Shimano Di2 integration I talked about above took *way* more time, effort, and money than it should have. First, to get the Di2 to talk to the Garmin, I knew I had to order and add a tiny wireless transmitter and a cable to my Di2 system, plus the special tool to connect the cable. When that didn’t work, I learned that I also had to order and replace my old battery mount. Tiring of the runaround when that didn’t work, I brought it in to the bike shop, where they individually updated the firmware on every piece of my Di2 setup. That didn’t work, either, so I ordered a new front junction box, plus two more new cables. When those came in, we installed them and did two more whole rounds of firmware updates during several phone calls with Shimano support. Then we finally had to pair the Di2 transmitter with the Garmin, and iron out a few minor bugs in the system (not reading battery level, thinking it had 11 sprockets rather than 10). In the end, it took a couple months, three trips to the LBS, a few calls to Shimano support, seven new parts from four separate orders, and an extra $450 in parts and labor to set up, just for my head unit to display what gear I’m in. Had I known that at the beginning, I never would have bothered.

The Bottom Line

Ultimately, the unit mostly works, and is generally okay. It’s a good step up from my aging Edge 800. I like the auto-upload, custom data fields, Di2 integration, phone and text message notifications, and Strava Live Segments. And I’m hoping that the FE-C trainer integration works well. But none of those are must-haves, so I wouldn’t say I’m blown away by the new features.

On the other hand, a lot of people really hate the unit, and I can understand why. The touch interface is terrible, basic functions such as loading routes and map data are ridiculously slow, and key features like Live Track, Group Track, and incident detection simply don’t work.

While Garmin enjoyed a market-leadership position in GPS cycling computers for several years, riders who are frustrated with Garmin’s lack of responsiveness are turning to other vendors, now that quality alternatives are available like the Wahoo Element Bolt.

By all measures, the Edge 820 should have continued Garmin’s domination of the GPS cyclocomputer market. I really hope they have learned the drawbacks of releasing such a flawed product and do a better job next time. In the meantime, hopefully they’ll keep issuing firmware updates that fix the Edge 820’s broken features and provide more compelling functionality.

It’s still a good unit, but it’s definitely not the category-redefining product that I had hoped it would be.

This post covers a very busy month of July, which included a solo century, the Tour de Cure, the 3-State Century, and more.

As usual, July began with Fourth of July weekend, which is always a perfect time to lay down some hefty miles, whether three or four rides in a row or a single century.

Looking for my first long ride since June’s endo, I chose to do my first Pittsburgh solo century, and my third hundred-plus mile ride of the year. For a course, I cobbled together a flattish out-and-back route to Brush Creek Park. Just shy of Ellwood City, it covered some of the same ground as the final third of the 200k brevet that I did back in March.

Thanks to my early start (6:20am), the day began with a lot of mist and fog, and a surprising amount of wildlife: 6 rabbits, 4 deer, 2 groundhogs, and a horse being ridden down the road.

At the park that was my halfway turnaround point, I took a photo of my bike in front of a covered bridge before pushing on. I hadn’t ridden too hard, and continued to feel good until the last 15-20 miles. I struggled through the last 5-10 miles, stopping at a neighborhood convenience store to down a cola and a candy bar before finishing the job. I really need to do better with eating and drinking on long rides.

In the end, it was a nice ride, but pretty challenging toward the end.

Two weeks later came my first Tour de Cure charity ride for the American Diabetes Association, for which I again footed my own fundraising. That was my fourth century of the year. More importantly, it was also my first ever gran fondo, an endurance ride where riders are timed on certain segments of the course.

The weather was awesome, and I wore my Kraftwerk Tour de France jersey, a tricolor that looks a lot like the French champion’s jersey, in honor of both the ongoing tour as well as those affected by a terrorist attack in Nice. Around 80 riders took off with me at 7am for the century route.

There were three timed fondo segments, and I estimated my times using nearby Strava segments, to give myself a number to shoot for. Although I am reasonably pleased with my performance, it was nothing as compared to riders 30 years younger, who also had the support of an entire semi-pro team.

The first segment was 1.4 miles, featuring a half-mile climb. My estimate had been 6 minutes, and I actually traversed the Strava segment in 6:02. The second segment was a long, 6.7-mile time trial with some descending but minimal climbing. After estimating 22 minutes, I brought it home in 19:31. The final segment was a 1.7-mile brutal rolling climb. After a 10-minute prediction, I finished in 9:11. Out of a total of 36 gran fondo riders, I placed 25th, 20th, and 26th on those segments, placing 23rd overall, or 36th percentile. What do you expect from an old man?

I rode a fair amount of the day with a young guy named Eric, whom I’ve talked to at the Tuesday night Team Decaf rides, who was doing his first-ever century. I should also note that I beat him on two of the three timed segments, pipping him by a combined 19 seconds overall. Later in the day, at mile 66, he somehow managed to get his chain jammed underneath his bike’s chain catcher, which took us about 10 minutes to un-wedge.

I had mechanical issues of my own, too. Around mile 60, my right-side pedal, which I’d just had serviced by my local bike shop, started making sounds like it was about to fall apart. Fortunately, it hung together till the end, albeit making crunchy-poppy noises with every turn of the crank.

As for the ride planners, one obstacle they provided was a lack of ice at any of the rest stops, on a day which grew increasingly scalding. On the other hand, there was an impromptu rest stop with (warm) drinks left at the side of the road at mile 98; the last ten miles were all mostly downhill; and I was pleased to receive another finisher’s medallion.

The summary for this ride was pretty positive, but again the last 20 miles were quite a slog.

My next century—my fifth of the year and third of the month!—came a week later, at the Pittsburgh Major Taylor Cycling Club’s annual 3-State Century. I’ve only ever done one other three-state ride (MA/RI/CT), and that was years ago. After leaving home in Pittsburgh, we’d go straight west, spend all of three miles in West Virginia before crossing the Ohio River, travel in the state of Ohio for another three miles to the Pennsylvania line, then mostly follow the river upstream back to Pittsburgh.

Although much of the route was flattish, there were three major climbs, all them coming in the first half of the ride; the ascents were actually much easier for me than the long, high-speed descents that followed each climb!

Although the route was only 93 miles (not even close to a century), my ride to the start and back home rounded me up to 112 miles, which allowed me to surpass 10,000 total miles on the “new” bike. It also fulfilled my goal of doing more centuries in 2016 than the mere four I did last year, which had been a record low.

By far the most salient feature of this ride was the heat. The day began at 70 degrees and climbed well into the upper 90s, and the NWS issued a region-wide heat advisory. New high temperature records were set in five out of six area weather stations, and in Pittsburgh it was the hottest day in four years. Normally I like it warm, but that was a little much. I coped by drinking lots of fluid, then finished the day pouring bottle after bottle of water over myself and stuffing ice into my jersey pockets.

On the other hand, I finished stronger than any of my other long rides this year. I even pulled two guys home over the final 17 miles of the route. For the first time this year, the heat was a bigger challenge than fatigue.

While I’d planned to take a personal rest stop on the way home at the foot of the 300-foot climb up to Squirrel Hill, I opted to press on due to gathering clouds, which developed into a very strong thunderstorm that hit about 40 minutes after I finished.

Although the heat made it difficult, I enjoyed the 3-State Century a lot, and probably finished stronger than any other century this year. It was a good, interesting day in the saddle, and I saw a lot of area roads that I hadn’t tried thus far.

Those constitute my major rides over the past month, but there were also a couple Team Decaf and Performance Bike group rides, plus several recovery rides. And a couple short trips to the LBS to fix the problems I was having with my pedals.

In equipment news, I picked up a cool new jersey and cap that are vaguely ska-oriented, which I’m sure you’ll see later, plus a couple Mondrian-themed cycling caps (dark and light replicas of the old La Vie Claire team kit).

But the thing that has me really excited is the announcement of the new Garmin Edge 820 cycling GPS unit. My first Edge 800 has served me very well since 2011, but it recently started suffering spontaneous power-offs, and several generations of GPS bike computers have come out since then. Among the features I’d gain with the 820 are: live weather, live cyclist tracking, live group tracking, WiFi downloads, ANT+ FE-C control of indoor trainers, Strava live segments, email and text notifications from my phone, Di2 electronic shifting integration, and third party data fields & apps written for ConnectIQ. The only reason I haven’t bought one already is because I want to wait for other users’ experiences and Ray Maker’s in-depth review to come ou. But you can rest assured that it’s item number one on my wish list.

It was a great month, and I’m looking forward to more new adventures in the waning days of summer.

It’s been a while, but I thought I’d do a quick writeup of the ride I did the day after Thanksgiving, since it was kind of memorable in its own way.

One of the things I wanted to do was test my Garmin Edge 800 GPS cyclocomputer, since it had been acting up since my last big ride, six weeks earlier. I’d given it a complete hard reset, but frustratingly, it wasn’t any better. It’s great when it works, but that’s only about 80 percent of the time. And for $700, I think it’s reasonable to expect better reliability.

Still, with the temperature in the mid-50s, I moseyed out Mass Ave. all the way to Lexington, because I wanted to pick up a Lexington Minuteman newspaper. Johnny H, one of my longtime riding buddies, had posted that he’d seen my photo in it, so I had to check that out firsthand.

After wandering around town a bit, I spotted a handful of cyclists pulling up to a coffee shop, and discovered that one of them was another old friend, Joy. I spoke to her briefly, then stepped inside a CVS and picked up a paper.

I came back out and parked myself on a bench with Joy and her friends while I leafed through the paper until I found the photo of me; the same picture that had graced the Pan-Mass Challenge home page for three months filled a quarter of the second page of the sports section. It was the focus of a thank-you message to PMC riders, although I’m still not sure whether it was from the paper, from the Dana-Farber Cancer Institute, the Jimmy Fund, or the PMC itself!

And if that ad appeared in a local paper in Lexington, it might well have also been placed in other town papers, although I haven’t gotten any information from the inquiries I’ve sent.

I said goodbye to Joy and rode down Waltham Street to Waltham (my first time down that road), and pulled into my riding buddy Jay’s driveway. I called him on my cell to ask whether he was home, and to open his back door for me. Since I hadn’t seen Jay in months, I figured this would be a good time to deliver something I’d been saving for him: a pair of size 12 PMC-branded flip-flops that I’d grabbed for him at PMC headquarters when I was there to pick up this year’s Heavy Hitter premium (a backpack). He was properly surprised and pleased, which was gratifying, and we chatted briefly.

From Waltham I took Linden Street and Waverly Oaks (another road I traveled for the first time) into Belmont, where I stopped at Belmont Wheelworks, arguably the best-stocked bike shop in eastern Mass. I was surprised to find it very quiet on the infamous “Black Friday” after Thanksgiving. I hadn’t brought a shopping list, but I did wind up walking out with two new tires, since my old ones were wearing out, and my preferred tires (Michelin Lithion IIs with blue sidewalls) are hard to find. So that was good, too.

As I approached Mt. Auburn Street in Cambridge, I had a brainstorm. I was only a couple blocks from Fastachi, a local nut roastery. Normally I wouldn’t stop, but since I was running errands I’d brought my bike locks, and it was Thanksgiving, so why not? I walked away with a mess of freshly-roasted cashews, hazelnuts, roasted corn, and some New Zealish licorice. Oh yeah, and some chocolate-covered caramels, too!

I hopped back on the bike, but hadn’t gone a quarter mile when I felt the tell-tale squidginess of a flat rear tire. Perfect! I popped the wheel off and removed the inner tube. Out of habit, I did what you’re supposed to do, which is run your hands around the inner surface of the tire to see if you can feel what might have caused the puncture, although usually there’s nothing to find, since I typically get pinch-flats. But this time I discovered an inch-long nail that had gone straight through the tire and into the tube. Glad I bothered to inspect the tire!

I installed my backup tube with the speed that comes from practice, and used my wonderful frame pump to fill it up to 100 PSI before mounting up and lumbering home, my bag filled to bursting with two bike locks, two new tires, a newspaper, a huge bag of roasted nut goodies, and a punctured inner tube.

It hadn’t been a particularly long or fast ride, but even despite the flat it was just a nice day on the bike, which was doubly good after a very discouraging Quad ride the week before.

Right now my life consists of work, cycling, fundraising, and occasional sleep, so my periodic updates this time of year tend to cover a lot of ground… like this one, which covers the past month.

July was a memorable month, but not for good reasons. Although I usually spend most of the Fourth of July holiday on the bike, with one of those days comprising a century ride, this year a terrible cold hit me Friday afternoon and kept me housebound the entire holiday weekend. Pure suckage!

The next weekend I had to go up to Maine, and convinced myself that I could get some training in by riding the 70 miles from Portland to Augusta. That ride wound up being really difficult, thanks to my lingering illness, a 25-35 mph headwind that hadn’t been forecast, and a mile-long section of muddy dirt road up and over a big hill in Sabbatus. But at least I managed to get some time in the saddle…

Which I needed, because the weekend after that was the CRW’s Climb to the Clouds, a very hilly century that goes up Mt. Wachusett, and is a traditional warmup for the Pan-Mass Challenge.

So CttC was just brutal. Combine my reduced training this year with oppressively humid 96-degree blazing sun and the CRW’s extremely limited idea of what constitutes a supported ride, and you can begin to imagine how difficult it was. Thankfully, I can say that my age wasn’t a factor, as my three buddies (all 17+ years younger) also concluded that they never wanted to do that ride again.

The ironic thing is that I spent half the day hammering, thinking I was chasing them, when actually I was ahead of them. Although I let them go ahead after the first 10 miles, they stopped at a water stop I skipped. I was surprised to see them ride past me in Princeton, where I stopped but they did not. So I got back on the bike and chased, unknowingly passing them *again* when they stopped at a convenience store. So I beat them over the mountain, and they only caught up with me after I’d spent 20 minutes at the next water stop, 53 miles in.

And as I predicted last year, the summit road was closed to us for the third year in a row, which was disappointing.

Toward the end of the ride, I was nauseous and unsafely overheated, and kept pouring water over my head to cool off. I stopped at the little Chinese grocery in West Concord and picked up their last two bottles of water, only to discover on gulping it down that it was seltzer! I sipped what my stomach could tolerate and poured the rest over my head and limped to the finish, where I pretty much just collapsed. But not before getting shit from the ride organizers for asking if I could have some ice. I was too destroyed to muster any argument when the guys decided to go home early rather than take the traditional postride dip in Walden Pond.

Definitely one of my worst days on the bike. There damned well better be some training benefit, after all that suffering!

And to make matters worse, my brand new $700 bike computer / GPS failed to record the quarter of the ride that included Mt. Wachusett and the following descent (GPS data). I had already left its heart rate monitor at home, because it had been malfunctioning. At least Garmin is replacing the HRM strap; hopefully the new one will last longer than the first one.

And then yesterday Boston tied the second hottest temperature ever recorded in the city’s 140 years of keeping records. Thinking I couldn’t get into much trouble in just one hour, I biked home from work in 103°F / 40°C heat. Against a convection oven-like 25 mph headwind, over three sections of stripped/grooved pavement along one of Boston’s biggest and fastest 6-lane arterials, and then stupidly up and over Dorchester Heights, just for fun.

That kind of heat will raise your heart rate 10 bpm no matter what you’re doing, and by the time I was done my heart was pounding and I was feeling very lightheaded. Kinda scary! Hopefully this stretch of intense heat will break and the weather will be more forgiving for the upcoming PMC ride!

And that brings me around to the tiny list of positive things that happened this month. First, Garmin did replace my problem HRM strap, and the new one seems to be functioning well; tho I probably will use it sparingly until PMC weekend.

Second, a question I’d sent in to the RoadBikeRider online magazine was published this week. The question was about how to fit a cooldown, stretching, shower, and recovery meal all into the half hour after stopping that is the optimal window for those activities. You can see the full question and RBR’s response here.

And, finally, the news that really matters: PMC fundraising. Once I finally started getting fundraising letters out, the money came in quite readily. I’ve surpassed the minimum and made the Heavy Hitter level for the sixth year in a row, and have settled at $7,200 for the moment, which is quite satisfactory, although there’ll be additional donations coming in over the next month or two.

Naturally, if you haven’t made your donation yet, please do so here.

And PMC weekend is only two weeks away. I’d normally be excited, but after the difficulties of the Maine ride and CttC and this brutal heat, I’m a little gun-shy about looking forward to riding. It hasn’t been a great year for any of my cycling buddies; just ask Lynda, who canceled her plans to do the epic 745-mile PBP ride; or Paul, who bought a pricey new bike only to have Jay destroy it by driving his truck over it on the way to the 150-mile Harpoon B2B ride that was supposed to be the highlight of his season.

The bad juju is in full force this year.

So we’ll see. There’s two more weekends before the PMC, and I don’t have anything special planned for them. Hopefully there’ll be a couple Quad rides and some hill repeats in there, and then a relaxing, rewarding PMC ride once the calendar turns to August.

Hopefully…

A new GPS has been on my wish list for at least five years. My old GPS was a Garmin eTrex that I picked up no less than eight years ago, back before GPS’ could even display maps!

I’ve been holding out for a while, waiting for the next generation of GPS’ to come out. I’ve had my eyes on a couple specific units:

Garmin has had a GPS designed specifically for cycling, but it doesn’t have maps, making it little more than a glorified cyclo-computer. They’re planning on coming out with a mapping unit, the Edge 705, but they just postponed its release into 2008, which is frustrating.

DeLorme, a company based in Maine, has a unit called the PN-20 that maps against aerial photography. That’s cool, but it’s also dog slow, which eliminated it from consideration.

Magellan is coming out with a line of handhelds called Triton, which look really interesting. But I heard rumors that they, too, were going to delay the Triton’s release into 2008. Sigh.

There’s also the Garmin eTrex Vista HCx. The Vista’s been out for a while, but they’ve made incremental improvements in it, including color maps and a much higher-sensitivity antenna. It’s also pretty familiar to me, since it’s the most advanced version of my old eTrex base model. And it has the advantage of already being commercially released.

Well, about the time I heard that the Edge 705 and Triton were being delayed, REI announced a sale on the eTrex Vista where they cut the price by $80. That was enough to get me to jump, so I picked one up on my way back from Maine last weekend.

I used the Vista the next day on a road trip to Connecticut, and again on a 40-mile Thanksgiving day bike ride. Here’s my first impressions…

The unit’s still acceptably small. In fact, it’s a tiny bit smaller than the original eTrex.

The display is quite a bit smaller than the old eTrex, but it has better resolution, and is color, so it’s a net improvement.

The old unit often took quite a long time to locate satellite signals. The new unit is noticeably faster, although it still can take several seconds.

Another annoyance is that the old unit only allowed six characters for waypoint names. The new unit allows about fifteen. Yay.

Naturally, the lack of maps was the biggest shortcoming of my old eTrex. This unit displays color maps, which is a huge improvement.

Still, the unit isn’t very useful without buying a memory card and Garmin’s supplemental map set, which will run you another $150.

My other major complaint about my old unit was that the batteries and electronics weren’t securely seated, so the smallest bump would cause the unit to power off. Not only was that inconvenient and annoying, it also put gaps in my tracklog. In 40 miles of biking Boston’s notoriously rough roads yesterday, the new unit didn’t shut off on me once. The battery compartment is very noticeably a tighter fit than before.

Battery life still seems great. I’ve been running two AAs, and have not had any issues with juice, even when running WAAS and the backlight all the time.

So far I’m pretty pleased with the unit, although I’ve only barely begun to put it to use.