7 am Yesterday I pried apart the garmin. The battery looked fine, but there were corroded contacts. I removed all the powder, cleaned things up and soldered a jumper between the posts. I added a couple rubber bands to hold the two halves of the garmin together, and charged it. It seemed to charge normally. This morning I took it on the run/ride with Ash. Everything worked fine. I guess some water or sweat got in and caused some trouble. The mode button still doesn't work, but I can at least see pace, distance, time and elevation. I need to glue the halves back together with some bathroom silicone, just in case I need to get in there again. That, and stay out of the water. I like the sprinklers and hoses and whatnot, but with that garmin, it's a no-no any more. So anyway, it was good for a run-time up to an hour. I wouldn't trust it for a marathon just yet. The bad news about having it is now I know for certain how slow I'm going. I spent an hour looking at stuff on the blog last night, and at this point I a flabbergasted I ran a 3:00 marathon at huntsville last fall. I have an idea what I need to do to run a 2:52-2:58 marathon, but I'm not sure if I'm willing to pay the price. I think it's as simple as miles per week. If I was consistently in the 55-65 mpw range during July and August, that would be a good portent for a sub 3 marathon in September. Currently, 7 mile runs are no problem. I would need to do 9-10 mile runs 6 days a week. It doesn't seem like that big of a deal, but it stacks up. With family, church, work and a broad lack of discipline, it's easy to miss a day or two a week. We've got a few major things on the horizon, and I don't know if it will be worth the sacrifice during those months. I read so many motivating entries from runners of all stripes on here, and I know there are dozens and dozens of people who are equivalently busy that work harder. Still sussing this out. |