UPDATE: Seems switching the Garmin to miles and back to km sorted the issue - at least for my short test run
Hello lovely running friends, I really hope you've all had a great festive period, although I know sometimes things don't work out as planned. If that's you, have a virtual hug! I hadn't managed to get out for a few days when I last went out, which was boxing day, and I know I can start to feel the all-too-familiar black dog hovering around when I don't run for a bit.
Anyway, I got two running-related gifts this Christmas: The first was a pair of On Cloudventure Waterproof Trail Shoes, a pressie from me to me. How sad am I?! The second was a Garmin Forerunner 30 watch, from the parents. Very kind of them, I wonder how they knew what to buy?
By boxing day, I was sick of stuffing food down my throat, and itching to try out my new gear. I know "stuff" won't make anyone happy ultimately, but it is always nice to have something new once in a while, lifts the spirits and enthusiasm levels! I decided as these were new shoes, and heavier than my Cloudflows, I should only do a short run initially, so ended up doing about 2.5k just to see how these puppies performed. The answer is: very well! I didn't need to use them for either of the routes I've run with them, though on the slightly dodgy bits of canal towpath which aren't well maintained, I do think they helped.
In fact, I was really quite speedy, managing 2.6k in 6:06/km, although the Garmin hadn't recorded the minute or two of the run. That was a rookie mistake, definitely due to me not realising that when everyone says you should wait for a GPS lock, they mean it. The other reason for the speedyness was down to the fact that the Garmin was apparently set to miles not km, even though I was pretty sure I had done it correctly, so I was thinking at 10 minutes per km I was being very slow, so when I sped up I actually ended up managing at least the downhill sections of the run faster than I intended.
It was, therefore, with confidence that I set off on a slightly longer run today, just shy of 7.5k. Shoes happy, tech sorted, so I thought... I had made sure the Garmin was set to km, waited for the GPS Lock thing to happen, and off I went. Happily it was recording position from the outset unlike last time, but I realised pretty quickly it was still in miles not km. I stopped under a bridge as it was raining slightly, and checked the setting. Nope. km. What gives???!
To cut a long story short, I kept going, and after doing a quick bit of mental arithmetic realised that I needed to be going a little faster than 10mins/mile, but I was still quite confused, so I just continued. I was using one of those fixed bpm running tracks again, but the one I use for fast 5ks, as I wanted to see how I could sustain it. The answer: I struggled a bit towards the end, but kind-of managed. It wasn't as fun as a slower run. I think my next run will be a nice long one at a lower pace.
So yes - help needed. I have a lovely Garmin that tells me Distance in km, Time, and the pace in minutes/mile. That makes no sense!!! Mr Google seems to show other people with the same issue, but no clear solution. Anyone know how to fix it??
Thanks all, run safe!!