Showing posts with label Garmin FR60. Show all posts
Showing posts with label Garmin FR60. Show all posts

Saturday, September 24, 2016

Bad Garmin, bad judgment

How far & how fast? Garmin's not talking
Today's run (street): 4.4 miles
Yesterday's run (street): 3.2 miles

My stopwatch would have been a better choice than my FR 60 on today's run, but I didn't realize that until I was about three miles in. That's when I experienced another Garmin meltdown. I naively thought that the Garmin was back to its old self because the timer seemed to be working again. I wasn't able to pair it with my foot pod, but I didn't really care. In fact, even if I could, the data would have been flawed because I hadn't calibrated the foot pod in six years.

It's finally fall and that means the weather is much more run friendly in the morning. Yesterday I ran my usual Friday circuit a little faster than usual and I was happy about that. I don't know if I've turned a corner in terms of pacing, but I'm generally running 45 seconds to a minute per mile faster than just a few weeks ago. I suspect cooler conditions contributed, but some of it must be due to improved fitness.

This morning I completely ignored what was happening outside and only noted the 59° temperature posted by the local news station. When I stepped outside, I felt a light but steady rain falling. I went back inside to change my running shoes because I didn't want the Zantes to get soaked. I went into the guest room to get new shoes from my gear cabinet and my wife was running on the treadmill. I told her it was raining and she said, "I told you that twice this morning." Actually she had mentioned it, but I'd decided the rain would stop before I went out.

A few minutes later I was out the door with different shoes and my ASICS rain jacket. Despite the extra layer, I stayed comfortable because of a steady breeze coming from the north. I wore the hood for the first mile. Although the conditions were cool, the humidity fogged my glasses. Things got better when I removed the hood when the rain lightened to a mist.

At least Gmaps still works
I enjoyed the cool breeze and the cloud-covered sky and I started to wonder how much time had passed since I'd started. I glanced at the Garmin which showed I'd been running about 30 minutes. I calculated in my head that, based on the rest of my planned route, I'd end up running about four and a quarter miles. About a minute after I'd checked the time, I heard the same sound that I heard at the end of last Sunday's run on the Bethpage trail. Once again, the Garmin's display said "Scanning" and I knew that I'd lost both the timer and my elapsed time.

I finished the rest of my run without knowing how long or far I'd gone. I hadn't taken note of the time when I left, so I couldn't calculate my pace based on post-run mapping and duration. I can estimate it roughly, but the margin of error is wide. I located my stopwatch when I got home and will take that along tomorrow. I'll get a GPS watch eventually, but for now I'll track my metrics like they did in the olden days. By that I mean in 2005 when Google launched Gmaps.

Sunday, September 18, 2016

Running Watchpocalypse on the Bethpage trail

Somewhere on that path sits half a Garmin.
Today's run (Bethpage bike trail): 5 miles (estimate)
Yesterday's run (track): 3.5 miles

On November 18, 2008, I published my first post on Emerging Runner. Today, almost eight years later, I'm publishing post number 2,100. I've covered many subjects over that time, and my tag cloud on the left lists well over a thousand of them. This blog has definitely accomplished my initial objective, serving as my training journal and an outlet for communicating with the running community. Writing 2,100 posts took a lot of time and effort, but it's been worth every minute. If it wasn't for this blog I wouldn't have met my Runsketeer buddies who I both adore and admire. Don't tell them though. It would only go to their heads.

Running is a simple thing, but it has its nuance. One aspect that fascinates and frustrates me in equal measure is the technology we use to gather running data. I've been through three Garmins over the past eight years and most of that experience has been good. My original Garmin, an FR 50, served me well until I accidentally destroyed it while replacing its battery. I replaced it with an FR 60 that improved on the 50 and has a far better battery replacement system.

About a year after buying the FR 60, I broke down and bought my first GPS watch, a Forerunner 210. It was big step up from the 60. I liked it a lot, despite occasional issues capturing a signal and the need to replace the data cradle after a while. Recently, the loop that secures the strap broke so I took the intact loop off my retired FR 60 to replace it. Soon after that, the FR 210's strap broke off making the watch unwearable. I returned the loop to the FR 60 and resumed wearing that watch on my wrist as a stopwatch while I secured the FR 210 to my SPIbelt using a keyring loop. That worked fine until today.

Yesterday's run - the FR 210's last map
Yesterday, I went to the local track to get in 14 laps before the sun came up. I had to be somewhere at 8:00 AM, so that was the best way to get in my miles. I ran well and have really taken to the NB Zante 2's that did great on the track. It was a typical track experience with the usual personas walking, running, sprinting and one guy who was throwing a medicine ball around.

This morning I headed to the Bethpage bike trail. My plan was to run about five miles, which I think I did. I'm not sure, because the god of watches decided to mess with both my Garmins today. My run started fine and I was in a great mood. The clouds hid the sun, but not the humidity. I made my way south from Haypath Rd and ran through Bethpage Park almost to the Parkview Court crossing. There were lots of walkers and it looked like a large group had come out together because many were wearing tees that said, "Move It." Early in my run, when I was halfway up a short steep section of the path, a runner coming north shouted, "I hear that hill is pretty steep today." I laughed because it was true.

I ran well despite the humidity and was about a half a mile to endpoint when I reached down to my side to look at the FR 210 and see how much distance I'd covered. There was nothing to grab and I discovered that my Garmin had fallen off the SPIbelt. It was probably sitting on the side of the path somewhere. I doubled back about a quarter mile, but was unable to find it. I was upset, but I've been planning to replace it since using it that way was fairly awkward.

Without a GPS map of my run, I figured I'd look at Gmaps when I got home and use the time from my FR 60 to calculate my pace. Annoyed, I ran the final half mile and about a hundred feet from the finish, my FR60 started to beep and the display blinked, "Scale Not Found" and then "Scanning." I couldn't turn off the message or get back to the timer (or turn that off for that matter). The watch would not respond to the buttons when I pressed them.

So in the space of five minutes, I went from having two functional running watches to none. When I got home I removed and replaced the FR 60's battery. That got it working, but I lost all the data from today's run. Before I could declare even partial victory, the watch started flashing "Scale Not Found" again.

It's time for a new watch, so my search begins in earnest. I doubt I'll have a replacement in time for next weekend. Until then, I'll rely on Gmaps and my $15 stop watch to capture my distance and pace. That should give me something to write for my 2,101st post.

Sunday, August 14, 2016

Running blind to time and distance

One lacks GPS, the other lacks a strap
Today's run (street): 3.75 miles
Yesterday's run (street): 4.5 miles

They ran the Dirty Sock this morning and I cannot imagine how those poor runners managed through 6.2 miles of hot and steamy air. Make that wet air. Air that you can feel without a breeze. The humidity today and yesterday could only be described as brutal. Despite that, I did get out Saturday and today, although there was nothing about my running that could be mistaken for a racing level effort.

Yesterday was the first time I ran without my FR210 on my wrist since I bought it, and it was disconcerting not to be able to monitor time or distance. I put the watch in my SPIbelt and tried to listen for the chirp that indicated mile splits, but I was unable hear them. Without that information, I had to guess my mileage based on the route I was running. I was surprised at the end to see that I'd covered 4.5 miles in sweltering conditions. I got home and jumped in the pool wearing my running clothes. Learning from past errors, I carefully removed my phone, Garmin and Fitbit before diving in.

This morning I'd planned to get out before the direct sun added to the already hot day. Unfortunately, I didn't actually start until 7:40 AM. By then, the air felt like a steam bath. After yesterday's experience  running without either distance or time indicators, I decided to put a new battery in my old FR60. At least I'd have a stopwatch to reference.

Equipped with phone, Fitbit and two Garmins, I set off into the heat and humidity. I still couldn't monitor my distance progress unless I pulled my GPS watch from my SPIbelt, not an easy thing to do while running. I felt like I ran more than 3.75 miles, but in this weather, that was more than enough.

Running with 1 1/2 watches is going to get old real fast. My FR210 wristband has further disassembled past the point where I could repair it with this cool hack. I should probably buy another GPS watch, but that seems wasteful because both the watch and GPS part of my FR210 still works. I'm open to suggestions.

In term of this weekend's running, my paces today and yesterday were glacial. Still, I enjoyed the fact that I'm getting through every run without worrying when fatigue will kick in. Even though conditions were suboptimal, I never once wished these runs would end. If I had run the Dirty Sock today in this weather I would have gotten through it. But not very quickly.

Friday, September 25, 2015

Garmin design failure no excuse for a new watch

Mis-connection
Today's run (street): 3.25 miles

Having a day off on Wednesday certainly made my work week go by quickly. Before I knew it, Friday had arrived. Yesterday was an interesting day. Some organizational changes meant that I had a new team to manage. I was fine with that, although I only found out about it that morning. I was thrilled not to have to drive to my office today, and that allowed me to do my usual Friday morning, pre-weekend run.

I work from home most Fridays, and the lack of a commute gives me plenty of time for a run. I had an early meeting happening via Google Hangout that put pressure on me to run and get back in time to look presentable on camera. That meant getting my procrastinating butt out the door early. On the positive side, the recycling trucks had not yet made the scene. On the negative side, our quiet neighborhood was already being overrun by cars and buses speeding their way to the middle school.

It was 64° with a little more humidity than on Wednesday, but it felt cooler. This was likely due to wearing short sleeves this time. The middle school traffic eventually disappeared and I thought I'd caught a break. But right on cue, I saw a stream of cars and buses heading to the elementary school. I avoided those roads and finished up my run.

Later in the day, I took a break to download my Garmin data and discovered the charging-data connector had broken since its last use. The design of the FR210 is a step backward from my old (non-GPS) FR60 that connected to my PC wirelessly and downloaded data automatically. The FR210's connector has a set of copper pins that match up with contacts on the watch. The connector is held in place by a spring driven clasp. It's a terrible design and, now that it's damaged, I'll need to figure out a way to keep it connected for charging.

Although this would be a great excuse to upgrade to a more contemporary model, I really have no need for a newer GPS watch. A quick search on the web showed that I can replace the connector for $15 through Amazon - so that's on order. I have my issues with the FR210, but after almost five years, it continues to be a very reliable unit.

Friday, March 15, 2013

Today's fifty step run

No power, no problem, today
I originally thought the theme of today's post would be about my discovery that my Garmin was out of battery and that would force me to run outside without capturing any data. But that wasn't the way it played out. Instead, I ended up stopping my run almost as soon as it started. Nothing to do with technology this time.

I was actually looking forward to running free of big brother NAVSTAR as I geared up for the cold morning temperatures (29°). I'll admit that I wimped out and put on my Garmin 60 to use as a stopwatch, but I didn't connect the foot pod or the HRM. So technically I was running free. However, between elapsed time and Gmaps, I could still calculate pace and distance. And you know I would have.

After running fifty steps from my house on my way around the neighborhood, I realized that my hip soreness had not gone away. In fact it was fairly painful and I worried that continuing my run might only exacerbate the problem. I decided that getting in a routine run was not worth the possibility of further injury so I stopped, turned around, and headed home.

I iced the spot for about 30 minutes and then continued my day that included lunch with a good friend. I considered doing an afternoon run if my hip felt better (it does) but decided instead to give it additional rest until tomorrow. I may go for a trail run at Stillwell on Saturday. In the past, the dirt surface has provided a good, softer alternative to pavement. It's a good surface to run on when dealing with an injury. Of course, if the temperatures are still below freezing tomorrow, the dirt may be just as hard as pavement.

Tuesday, January 8, 2013

Garmin FR210 behaving badly

Get back to work!
Today's run (treadmill): 25 minutes

After two years of stellar service, my Garmin FR210 has started to exhibit some bad behavior. I bought this watch because it provided basic GPS metrics, elevation data and wireless syncing with my heart rate monitor. Like all GPS systems, the distance accuracy wasn't 100%, but after a while I understood the margin of error and mentally corrected for it. There are things I still don't like about the watch, such as the weird way it connects to a PC for data uploads, but overall it has been a great resource and a good value.

The bad behavior started on January 1st, with my first run of the year. I was a couple of miles into the Hangover Fun Run at Eisenhower Park, when I looked at the watch only to see that it wasn't recording time or distance. I decided to let it go and just use the event clock to record my time. I figured that I must have neglected to fully push the start button and was paying the price for that inattention.

Since then, I've run five more times. On three of those runs I've noticed that the timer stopped recording after I'd initially started it. It doesn't happen every time, but it forces me to pay careful attention to the watch on every run. I don't know why this would suddenly happen. I checked the FR210 forum on Garmin Connect but haven't seen anyone else with the same complaint.

It would be a shame to have to replace this watch because I've come to rely on it to capture all my metrics, including a map of where I'd run. I still have my FR60 that works fine, but it lacks GPS so I'd need to return to using the foot pad. If I did that, I'd lose the mapping but would gain cadence, something I miss since switching from the 60 to the 210. I could always use an app on my smartphone to do the mapping since I carry the phone on every run. It's worth thinking about. But I'd rather have the FR210 working as it should.

Thursday, November 1, 2012

Hurricane damage assessment run

Yesterday's run (street): 3.5 miles

Hurricane Sandy has left most of Long Island a mess. Our neighborhood sustained a lot of damage.Yesterday, I went out for a run for the first time since Sunday and saw the damage up close. A number of roads are blocked by safety tape due to fallen trees or power lines. We, like hundreds of other families in the neighborhood, still have no power and it's not likely that we'll get it back until next week.

My run was interesting because of what I saw, but the run itself, in terms of performance, was not very good.  Without the ability to charge my Garmin, I used my old FR60 as a stopwatch and timed my run which I was able to Gmap at 3.5 miles. I'm hoping to get out for a run today but I'm working remotely and today is (unsurprisingly) busy.

We're planning to stay with my in-laws tomorrow so we'll get to enjoy hot showers, access the Internet and not worry about draining cellphone batteries. This is very much like what we experienced last year with Irene. That took far longer to resolve than we ever expected. Hopefully, LIPA will surprise us and restore our power before we overstay our welcome.

Wednesday, September 26, 2012

Rethinking GPS versus foot pod

Today's run (treadmill): 2.5 miles

My first method of capturing running data was with the Nike+ chip that fit into a concave spot located under my shoe's sock liner. The accuracy of the this system was surprisingly high, but the software was buggy and the wristband that displayed metrics like pace, time and distance had serious corrosion issues. After going through three of these wristbands in less than a year, I got my money back and bought a Garmin FR50.

FR60

The Garmin 50 (and after that the FR60) uses a foot pod that works in a similar way to that Nike+ chip and I got used to tracking my distance and pace that way. The foot pod needed to be calibrated each time I switched running shoes (in my case, frequently) but the accuracy was very high. I started running with the Saucony Hattoris that have no laces to hold a foot pod, and made the switch to the Garmin FR210 GPS watch thinking I'd be upgrading my experience.

As it turned out, after almost two years, I've discovered I've given up more than I've gained by switching to GPS. The accuracy of GPS (~ 3%) is far worse than with the foot pod (~ 1%). The foot pod also captures cadence, an important metric, but the FR210 does not.


FR210


I had an amusing experience on the treadmill with the FR210 this morning. I wore the watch to capture my heart rate but, even indoors, it had locked in on satellite. When I finished my run I saw that the watch had recorded my distance at .14 miles. I've been considering using the FR60 again with the foot pod for treadmill runs. But for outdoor runs, I have to say the one big advantage of using the GPS watch is that there's no fussing with calibration or switching foot pods. Nothing's perfect, but at least I have a choice.

Friday, May 11, 2012

The key to capturing cadence

Cadence catcher
Today's run (street): 2.5 miles

I finally got outside this morning, for the first time since Sunday's race. The treadmill runs I did yesterday and Wednesday were fine, but I think I run differently on the machine, compared to the road. I wonder if it has something to do with stride length. Outdoors, I never think of how far I extend my legs when I come down, although I do focus on landing on my mid-foot. On the treadmill, a too-long stride is usually announced by the sound of the kick plate at the front of the tread. That feedback surely influences the way I run.

The shorter stride on the treadmill is not necessarily a bad thing, because it probably forces me to increase my cadence to keep up with the tread belt. Mid-foot running supposedly optimizes stride length, and cadence is used like a gas pedal to regulate speed.

This morning I pushed a little harder than I had during the past two workouts because I've recovered from my 13.1 mile run last weekend. I tried to use arm movement to maintain a brisk cadence, but in the end, my overall pace turned out to be just about average. I do wish my Garmin FR210 captured cadence so I could compare it to my speed over a run. Unfortunately, the GPS watch lacks that capability. I suppose I could always count steps. That, or go back to my FR60 that uses a foot pod to capture that metric.

Friday, January 27, 2012

In treadmill I trust. Or do I?

Today's run (treadmill): 25 minutes

This is the key
A rainy morning kept me inside today so I did yet another treadmill run. I'm curious to know how close the readout on the treadmill's display matches my actual progress and performance. I replaced the treadmill's console a few months ago but wasn't able to run the calibration sequence when I installed it. Every time I run on the machine I question the accuracy of its recorded distance and speed.

I've often felt that running on this treadmill (a Sole F63) and our prior Pro-Form unit felt harder at a given speed than when running on the road. A 9:00 pace on the Sole feels like about 8:50 on pavement. It may be that the treadmill forces a shorter stride and higher cadence that feels more challenging. I would think that the treadmill would feel easier and street running because there's no wind resistance. Plus, you don't experience hills unless you select an incline.

I still have my foot pod that links to my Garmin and I could probably answer my accuracy questions by comparing the Garmin performance with the Sole's on the same run. Before I do that, I need to replace the foot pod battery and do some calibration runs outside in order to establish an accurate baseline. The other issue is that the foot pod won't attach easily to my Hattori's so I'll need to run in a different shoe. I guess I can make excuses why it will be hard to test or I can just go ahead and try it.

Wednesday, May 18, 2011

Is cadence the key?

Not quite stepping lively
Today's run (treadmill): 2.51 miles

I had lunch yesterday with a friend, TC, who's just been granted entry to the NY Marathon after being accepted as a charity runner by the Boomer Esiason Foundation (Cystic Fibrosis). TC is about to start serious training and he asked me to help him set up his Garmin FR60 on Garmin Connect. Although TC has been using this watch for months, he's never uploaded his runs. I had no idea that the FR60 could hold 90 workouts but that's what was uploaded. It was interesting to see his runs displayed on Connect. I couldn't help but compare his typical pacing and cadence to mine. It wasn't much comparison though. He seems to average 90 SPM while I'm happy when I exceed 84.

I thought about cadence this morning as I ran on the treadmill. I'm past thinking that any one thing (core exercise, LSD, tempos, Chia) will produce measurable improvement. However, it seems logical that an increase in cadence would align with an increase in running speed. As I worked my way up from my easy start, I was curious to know if my cadence would increase as I moved my pace from 9:50 to 8:50 over my run. After the run I realized that the FR 210 doesn't capture cadence data off the foot pod so I'll never know how I did for SPM today. I guess I'll need to revert to the FR60 for treadmill runs in the future.

Tuesday, May 17, 2011

The FR 210 and foot pod: challenges and results

Today's run (treadmill): 2.5 miles

Foot pod, meet FR 210
I planned for rain this morning and set up my gear for an indoor run. It would be my first time back on the treadmill in almost a month and a return to using the Garmin FR60 watch for tracking performance. I attached the foot pod to my Mirages (I'm already spoiled by the pod-free FR 210) and reached into the drawer for my FR60. It then occurred to me that the 210 also syncs with the foot pod so I chose that watch instead. After a couple of cycles through the menu, the 210 was paired with the sensor.

I started my run at a moderate pace, which is my method of choice for tolerating the treadmill. Start it easy and end it hard. I had a scare at the beginning that my knee would act up but after a moment of pain it was fine and three hours later it's still fine.

I hit start on the 210 and glanced down after a minute to verify that it was capturing my pace. It wasn't until I'd reached the six minute mark that I looked again at the watch to see that, while it was displaying pace, it wasn't recording time. I don't know why that happened but I hit start again and this time noted that the stopwatch was running.

I used the time display on treadmill and the average pace captured by the Garmin to calculate my actual distance (the treadmill does not do that accurately). It was a pretty good workout and I didn't find the treadmill as tedious as I usually do. Perhaps all that biking this weekend helped my running. If that's the case I'm thrilled to find a cross-training workout that's both fun and beneficial.

Saturday, March 12, 2011

Return to the Muttontown trails

Circuitous run on the Mystery Trail
Today's run (Muttontown Preserve): 3 miles

I took advantage of the weather today and headed over to Muttontown Preserve at noon for a run. Our morning was very busy so I didn't get out as early as I would have liked. Even with that late start the parking lot was less than a quarter full and I was glad to know that the trails probably wouldn't be crowded. The snow is all gone but some of the effects of all that water remain. The dirt roads around the entrance were rutted and the trails have a lot of muddy sections. With the noon day sun, I started my run wondering if I should have picked shorts instead of running pants. As it turned out I made the right choice.

Rough road leading to some rough trails
I followed the same path I originally tracked on my previous run and held my breath as I passed by the place where I fell head first into frozen mud. No such issue today but the condition of the trails was marginal and several times I encountered fallen trees along my path. Some places were completely blocked and that forced me to bushwhack through thorny brush to reconnect with trail on the other side. It was then that I really appreciated having long pants and long sleeves. I'd hoped to make my way south, then west and come back north to the trail-head but my poor navigation kept me contained in the northwest part of the preserve. I actually ended up running part of one loop three times. By the third time, I finally recognized the terrain!

I had MotionX running on my iPhone and even with the real-time mapping and compass I managed to get lost. I could see where I went wrong but I couldn't find an alternative path to correct my vector. Instead of mountain bikers, like I often see at Stillwell, I encountered people riding horses on the trail. Between the mud and horses I needed to do a lot of careful stepping. My Garmin, with its auto-pause set too low, kept stopping and restarting and occasionally not restarting. Of my approximately 35 minutes running, the Garmin recorded only about 25 minutes. MotionX did a better job although I'm not confident in the iPhone's GPS accuracy. At least, by the map,  I have a good idea where I ran.

Altogether it wasn't a very far run but the elevation changes were frequent with a total gain of 220 feet. I came away from the Muttontown Preserve feeling a little ambivalent about the place. I know that MP provides potential for a good fulfilling run but I'm zero for 2 so far. I really wish the trails were better marked so I could spend more time appreciating the experience and less time worrying about direction. Still, it was great to be back on dirt and though my distance was only about three miles they were three hard miles. I'm hoping to cover more distance on the road tomorrow and I'm glad to know that I probably won't get lost when I do it.

Sunday, February 13, 2011

A pace I can live with

Today's run (street): 4.12 miles

Yesterday afternoon I updated the firmware on my Garmin FR60 which reset the watch to its factory settings. I was happy that I had the foresight to upload this week's runs to Garmin Connect before I did the upgrade or they would have been lost to the ages. I restored all the settings and preferences but I neglected to re-pair the watch to the foot pod. When I went out for my run this morning I hit the start button and didn't think much about it. A few minutes into the run I looked at the display and saw it was tracking time but not distance and I realized that I hadn't paired the unit. I figured I'd just Gmap the route I ran and calculate pace later, based on the recorded time.

I recently had a similar experience when I saw that I hadn't started the Garmin after I'd begun to run. I ran most of  my route knowing that my speed and distance weren't being captured and that was both annoying and liberating. Today I felt better when I discovered the problem because at least I had captured the run time. I decided to forget about pace, speed, etc., and just ran free for 30-40 minutes. I took it easy because that was what I'd originally intended for this run -- a short version of LSD. About 30 minutes into the run I was feeling like I could run all day and it occurred to me that I should think about a pace that I could maintain comfortably for a half marathon.

Today's pace was 9:53. Not fast but manageable over long distances. It would be good (psychologically) to average below 10 min/mile for the half marathon. The challenge of running a half under two hours is much greater -- I'd need to average 9:09 or better to do that. I'll work on my distance as much as I can from here on. With the temperatures moving toward the 50's I might get the first chance in a while to do a long run at Bethpage next weekend.

Saturday, January 22, 2011

Garmin foot pod calibration - one of life's mysteries

Today's run (street): 5 miles

The action of calibrating my Garmin's foot pod is hit or miss. The best way to do it is when you run an exact distance and it calibrates automatically. Another method is to adjust the foot pod based upon a known factor, such as the percentage between what was recorded and what you actually ran. The third way is the worst way and of course it's the one I usually follow because it's also the the easiest. In this case, when I'm consistently over or under recording my distance (compared with Gmaps) I manually compensate by arbitrarily increasing the the index until I get close. Sometimes this works great and the foot pod will report accurately for many runs. Since I often switch the foot pod between pairs of shoes it's usually off by some factor anyway and that's why I Gmap my runs.

Easier said than done
This morning I adjusted the foot pod thinking that a .05% decrease would compensate for over recording would get me to the 1/100ths of a mile accuracy that I often observe. When I went out this morning on the freshly plowed streets I was moving well. Except for on the spots that were still covered with packed snow my pace was fast and my stride was good. I often follow the same exact route for the first mile to gauge whether the Garmin is ahead or behind my real distance. I must have been confused today because I came through the first mile thinking that the foot pod was under recording, when in fact it was probably off by 3% the other way. I'm still fuzzy about when it chirped and where I was when that happened but when I finished my run the recorded distance was .23 miles greater than what I mapped using Gmaps.

I find it hard to believe my calibration was that far off and I have a different theory. Much of the roads were covered with a combination of slush and snow and my form differed greatly when I ran on those sections versus the open pavement.  It's possible that this difference in stride, cadence and lift may have thrown off the foot pod. I won't ever really know but I'm planning to reset the foot pod to 100% index value and start again. If I thought that a GPS watch would be more accurate I'd probably buy the Garmin 210. Most of the time I'd be better off just running with a stop watch and calculating pace later, after I'd Gmapped the route. The only problem with that is when I run the trails or on the treadmill and the foot pod also provides excellent data that I value, including split times and cadence. I guess I'll just keep calibrating and hoping for the best.

Monday, January 10, 2011

Running off the grid

Yesterday's run (street): 4.6 miles

It was a surprisingly busy weekend, especially on Sunday. I didn't have time to post but I was able to work in a morning run. After Saturday's unusually tough four miles I'd hoped Sunday's would be better. It's been cold since the turn of the year and yesterday morning the temperatures were in the mid 20's with wind chills making it feel like the teens. I've learned that until the temperature approaches 10 degrees that smart layering will hold off the cold long enough to to keep things tolerable until my body warms up from the run.

I thought yesterday's run would be a repeat of Saturday's. My legs felt a bit stiff over the first mile and I anticipated that things would go from bad to worse. With nothing to lose, I decided to pick up the pace to see if it would make a difference. That actually helped a lot and my stride began to feel more natural. I took a different route than normal so after running a while without hearing the chirp of my Garmin I looked at the watch to see that I'd never turned on the foot pod. I fortunately remembered my start time and paid attention to my finish time and after Gmapping the route I figured out my approximate pace. In the past I would have been upset to have run without capturing the metrics on the Garmin but once I realized I was untethered I actually felt very free during the run.

Neither run this weekend was very long but at least yesterday's turned out satisfying. With more snow on the way I'm thinking that I'll probably be constrained to the treadmill and elliptical this week.

Wednesday, June 16, 2010

Not sure what to make of my FR60 calibration

Yesterday's run (street): 2.8 miles @ 9:29/mile
Today's workout (elliptical): 25 minutes

I've been focused on business needs this week and that has disrupted my blogging schedule. I'm at an industry event today where I presented in the morning. That was the last big thing I needed to get through for the week (so far). I'm thinking again about my running.

Yesterday I returned to the street and ran (according to Garmin) 2.95 miles. Knowing that my distance number on the FR60 was overstated by 6.5% against the distance of my 8K, I suspected that I didn't actually cover what the display showed. I "Gmapped" my route as soon as I could and discovered my true distance was 4.4% less than what was indicated. This didn't surprise me but it also makes me wonder if the 8K course was actually 8.2K. I have not moved the sensor on my foot pod the last three times yet my margin of error seems to have swung from calibrated to over counting by different amounts on subsequent runs. I'm transferring it to the Kinvaras tonight for tomorrow morning's run. I'll see what happens after that. My run on Tuesday morning went well although I didn't go particularly fast. Once again I surprised myself by not really caring about my pace. I've decided that I can either dedicate time to speed drills and tempos and improve my average pace or I can go out almost every day and just run for fun. I'm definitely focused on the fun option right now.

I chose to do an elliptical session this morning which was a perfect workout to prepare me for today's events. Tomorrow I'm planning to go out again and run. I'm thinking of pursuing a new distance goal this weekend. I think breaking 10 miles is the next frontier for me. Perhaps not this weekend, but soon.

Tuesday, April 27, 2010

Pacing discovery on the treadmill


Today's run (treadmill): 2.4 miles at 9:08/mile

Although I was fully prepared to run on the treadmill when I set up my gear last night I felt a little differently this morning. The alarm woke me up from a sound sleep and made me question whether a workout or thirty extra minutes of sleep would do me the most good. I would have liked the extra sleep but I knew if I didn't run I'd feel guilty for the rest of the day. Despite its negative connotations, I truly believe that guilt has its good side. I had a little coffee and got on the machine, resigned to running a couple of miles.

As I started my run I compared the pace on the display to the pace on my Garmin that I knew was accurately calibrated. The two readings were closer than I'd expected them to be. I increased the tread speed and saw that the paces changed in sync with each other but once I got to target speed I found that I could achieve a faster pace on the Garmin, compared to the treadmill's, just by quickening my cadence. When I resumed my default running rhythm the Garmin's readout resumed duplicating the treadmill's. It was an interesting discovery because now I know I can naturally speed up or slow down a little without needing to mess with the treadmill's controls. That makes a big difference to me because much of my frustration with the treadmill is from the tedium that comes with being forced to maintain a hardwired pace.

Although I started off tired I did rebound and got through 2.4 miles at a decent pace. I don't know why I find treadmill running so much harder than road or trail running but I do. Still, I rather it be that way than the other way around.

Monday, April 26, 2010

Sunday run with the Emerging Runner Girl

Yesterday's runs (street): 4.4 miles at 9:02 + .75 mile fun run

Counting Friday's run in the city, I managed to cover a little more than 12 miles this weekend. Out of those twelve my favorite experience was on a distance less than a mile (more below). With last Tuesday's 4.8 miles in Central Park and another 2+ miles on Wednesday, I still fell short of my informal weekly goal of reaching 20 miles. Of course if I include the 2 miles covered on the elliptical last Thursday I'll be able to claim that goal. Okay, done. 21 miles for the week!

As hoped, the rain slowed down by early Sunday afternoon and I took the opportunity to hit the neighborhood streets. I don't generally do my best speed running at 1:30 in the afternoon but I tried to keep the pace as brisk as possible. Due to the wet roads I wore my Adidas Response 15 trail runners. That was less for protection on the slippery road service and more to keep my Brooks GTS 10's from getting wet and dirty. I ran about 1.5 miles on local neighborhood streets and then cut over the neighborhood #2 for the bulk of the run. Since I was running in trail shoes I took advantage of a few areas alongside the road that had packed dirt and grass. It was pleasing to hear the chirp of the Garmin as I passed the two mile point. The third followed surprisingly soon after the second. At one point I looked at the watch and noticed that it was giving me readouts that said "00:15 ahead" which confused me. I then realized that when I updated the FR60's firmware yesterday it switched to a default setup that included a virtual running partner. I would have had fun with the virtual partner if I better understood the interface. I again relied on my heart rate monitor to guide me in terms of effort. My pace seemed fast for those conditions but, after verifying on Gmaps, I confirmed that the Garmin was accurate.

When I got home from my run I was met by my 11 year old daughter who had been riding her scooter and waiting for me to return. We decided to run a loop around some of the local roads and covered .75 miles between 10-10:30 mins per mile. Though it had been months since we ran together she kept up very well. My daughter has near perfect running form and she lands on her front foot naturally. I think she was happy when I told her that I learn things by watching her run. Next weekend I hope we will be able to cover more distance.

It's still very soggy in NYC and on Long Island so I'm not sure what outdoor running I'll be able to do during the week. I'm planning to get at least one Central Park run in before next weekend, assuming we see clear skies this week.

Saturday, April 17, 2010

Time to calibrate the FR60

Today's workout (street): 4.17 miles at 8:57/mile

Yesterday's run felt so effortless that I wasn't ready to stop when we reached the end. Business took priority over pleasure but I did feel great for the remainder of the work day. The run itself was work and I felt the effect of all those hills this morning when I woke up. Still, I was anxious to get out for another run. My wife and kids were volunteering at my son's elementary school all morning. I had nothing on the calendar until after lunch so I headed out for my run around 9:00 AM with temperatures in the the high 30's under overcast skies. My Garmin was fairly quiet so I knew I was within pace range although a check of the display showed my pace to be a little slower than it seemed. I stepped it up after the first mile and would periodically surge for 30 seconds to a minute before falling back to my default pace. I was running faster than yesterday's city excursion and I felt the difference. All the same I didn't feel that I was working that hard and the data from my heart rate monitor confirmed it. I felt like I had covered a lot of ground but I ended up only going a little more than four miles. It was just far enough to count as a good workout.

When I finished the run I checked my Garmin and saw it displayed 4.07 miles, averaging 9:10. 9:10 isn't a bad pace and I figured that yesterday's run had wore me out more than I'd thought. I then mapped the exact route using Gmaps and saw that the Garmin under-counted the distance by 2.3%. Adjusting my pace for that variance, my overall average was under 9:00 (8:57) and my splits were 8:54, 8:57, 9:03 and 8:59. Love the FR60! I'm going to try to calibrate it a little closer so I don't have to do so much math. I haven't messed with the calibration adjustment on the FR60 yet. The default accuracy is +/- 3%. It wasn't all that easy to adjust the 50 so I'm hoping the 60's controls are better. My problem with calibration is that I switch my foot pod often between my pairs of street and trail running shoes and every change affects the calibration accuracy. Overall, I'm happy with my recent runs and glad that I've made my way down to the low 9:00's that I was running prior to my pneumonia disruption. I don't know what I'll run tomorrow. The skies are looking ominous but I'm hoping that this passes and that the trails are in good shape by Sunday.
 

blogger templates | Webtalks