Bad Garmin, bad judgment

On September 24, 2016 By Emerging RunnerLeave a comment

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.

Running Watchpocalypse on the Bethpage trail

On September 18, 2016 By Emerging Runner6 Comments

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.

Running blind to time and distance

On August 14, 2016 By Emerging Runner5 Comments

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.

Garmin design failure no excuse for a new watch

On September 25, 2015 By Emerging RunnerLeave a comment

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.

Today’s fifty step run

On March 15, 2013 By Emerging Runner2 Comments

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.

Garmin FR210 behaving badly

On January 8, 2013 By Emerging Runner6 Comments

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.

Hurricane damage assessment run

On November 1, 2012 By Emerging RunnerLeave a comment

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.

Rethinking GPS versus foot pod

On September 26, 2012 By Emerging RunnerLeave a comment

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.

The key to capturing cadence

On May 11, 2012 By Emerging RunnerLeave a comment

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.

In treadmill I trust. Or do I?

On January 27, 2012 By Emerging Runner2 Comments

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.