Posts Tagged ‘garmin’

Winter Training – The Climb by Garmin

Forwarded to me by Christian, here’s the first LFNP post of 2011.

It’s a beautifully-shot film, and it reminded me of a few things:

  • riding up cols in Europe
  • Rapha’s short season of exquisite movies about riding
  • how I don’t have a Garmin Edge 800
  • how I don’t have a heart-rate monitor at all, ever since my Garmin Forerunner 50 gave up the ghost

(more…)

Stock Hill

Ooh check out Garmin Connect’s new embedding feature! Disappointing isn’t it. Naturally, what I want to do is display my heart rate graph – if my Forerunner 50 had the functionality, I’d want to embed a map. Not just the stats, basically. At any rate you’ll just have to click through for now.

Stock Hill – a suburban street in Biggin Hill – is a tough session. It’s tougher than Swain’s Lane, because it’s longer – 2 min repeats on shorter recovery – even though it’s possibly not quite as steep as the steepest ramp of Swain’s Lane. The best thing is, the gradient is constant, and the road is smooth. You start out at around 130bpm, move over 80% at 30 secs, then spend the final 30 secs in the red at around 170bpm (my max today was 177). I hit the first couple of reps pretty hard, and descended straight away, allowing myself only about 30 secs recovery. I was really suffering on rep 3 though, so I backed it off a half and extended the recovery period.

I did 8 reps, alternating 4 seated and 4 standing, pushing about a 34-20 gear (3,4 & 5 down on the cassette).

iPad cyclo-computer rumour

Clearly ridiculous - or is it?

Clearly ridiculous - or is it?

Apparently Steve Jobs was annoyed when his Garmin malfunctioned on a lunchtime hike; on returning to the office, he got his boys onto some R&D for a new Apple bike computer, nickname: Colossus.

Via Velodramatic.

Final pre-Marmotte Regent’s Park & Swain’s Lane

Just back from a 2-hour Regent’s Park / Swain’s Lane session in the warm sunshine. Nice to have it back after quite a few cloud-covered outings.

My technique in the park today was, rather than ride at threshold for 5 minutes, start from the same corner but go all-out to the traffic lights, then recover. On my first one of these I hit 193 bpm, which I think must be close to my maximum. Needless to say the 2 boys attempting to follow me were toasted, burned, then binned.

Ignore (again) the ridiculous 240bpm peak in the first 5 minutes.

Ignore (again) the ridiculous 240bpm peak in the first 5 minutes.

I’ve identified a definite bug in my Garmin heart-rate monitor, reviewed earlier on this blog. Occasionally, in the first few minutes of a workout, the monitor will display a massively erratic reading, e.g. 240 bpm, while I’m coasting downhill. This is kind of annoying, because it throws my nice heart-rate graph out of whack.

On the subject of Garmin, it’s great to see continual enhancements to the user interface on the Connect website. The whole Garmin project feels fresh and innovative – I will certainly be investing further.

Here’s one example: the ‘Player’ workout playback function, with variable speeds and micro-controls to view exactly when and how hard you were training. However, I guess it’s supposed to show a graph in the middle – my version didn’t.

Garmin's workout 'player'. Cool.

Garmin's workout 'player'. Cool. Fresh. etc.