Yesterday, I did my first ride after installing my new €5 cadence sensor and connecting it to my bike computer. I wanted to go for a short trip and when I left home, I assumed that I’d be alone. I was wrong. After about one kilometre, I met one of the triathletes from TriTeam Chaos who told me that he’d meet two other guys for a training trip. I went with them until Greifenstein, but then I returned because joining people whose stamina is about 100% higher than your own is rather exhausting :-)
In general, the trip was pleasant because I returned before it started to rain. The only negative thing was that this trip was meant to show that the cadence sensor and the bike computer work together. They did so for the first four kilometres, but then all of a sudden, the bike computer failed to display the speed (the cadence was still shown). Today, I disassembled everything and found the reason: The cable connecting the bike computer to the speed sensor was torn. Since I couldn’t find a replacement part, I tried to fix it myself. Those who know me a bit better know I’m not a very handy person, but nonetheless, I managed to connect the cable again! The funny thing is that I explicitly bought a wired bike computer because I feared that the sensor’s battery could fail at any time without warning. Now I know that something similar can also happen with a wired sensor :-(
Because of this hardware problem, the data below comes from my Forerunner 405 (which I’m about to replace with a Forerunner 910XT with a wireless cadence sensor!).

The usual numbers:

Note: The climb was measured using a non-calibrated barometric altimeter; the amount of energy consumed was calculated from the measured heart rate and physiological parameters.

The GPX file recorded with my eTrex can be found here.

Read more about the “Tracking for Freedom” project here. All blog posts about the project are tagged Tracking for Freedom.

Today, I finally managed to go for another trip for the “Tracking for Freedom” trip. I was once again with the guys from TriTeam Chaos, but this time we were even eight people. The beginning of the trip was very nice, I even had the engery to chat with some of the other participants. Later, we went up to the hills of the Wienerwald and I painfully realized that I am not (or at least not yet) a climber. I was definitely the slowest member of the group and others even had time to go up the hills twice while I was still fighting myself. I’m proud that I never had to stop and push my bike. I have attached the evelation profile of the trip to this post.

The trip's elevation profile

The usual numbers:

Note: The climb was measured using a non-calibrated barometric altimeter; the amount of energy consumed was calculated from the measured heart rate and physiological parameters.

The GPX file recorded with my eTrex can be found here.

Today, I did another trip for the “Tracking for Freedom” project and for the first time, I was not alone. Three triathletes from TriTeam Chaos allowed me to join them on their bicycle tour. They taught me slipstreaming and I owe them a big thank you for taking me with them. I think I have never had a higher average speed on one of my tours. The track was already familiar with me, but I have never followed it so far in the past. Of course I’m not in the shape to go for a whole tour with professional triathletes, so I had to return earlier than the others.

The usual numbers:

Note: The climb was measured using a non-calibrated barometric altimeter; the amount of energy consumed was calculated from the measured heart rate and physiological parameters.

The GPX file recorded with my eTrex can be found here.