Active Community: Message List

Re: Rectal bleeding after running

guest — Thu, 15 Sep 2005 00:30:28 GMT

RunnerDiva,

I know runners are prone to diarrhea due to the friction that is caused in our intestines from the running motion. However, you may have caused a flare-up in a condition called ulcerative colitis. I have had this for the last 4 years. If the condition doesn't clear up in a week or so, you may want to visit a GI Dr. They will probably do a colonoscopy. You will more than likely be put on a medication called Asacol. For me, I'm okay if I keep my workouts short and fairly easy. However, I'm currently training for a marathon and have been plague with your same symptoms since June. You're lucky right now that you can control your bowel movement until you're finished with your run. This may not be the case if you continue to increase your mileage and/or increase your effort level. Hopefully things will clear up.

Re: Garmin Forerunner 301 VS Polar 625X

guest — Mon, 05 Sep 2005 13:04:08 GMT

As mentioned before on this post, I use the Garmin FR301. To answer a previous question about average pace, yes, you can view your average pace for the run as you proceed. You have to setup a "custom page". I have my custom page showing my average pace, time of day, and total distance. I'm still very happy with my purchase.

Re: Garmin Forerunner 301 VS Polar 625X

guest — Sat, 13 Aug 2005 10:35:56 GMT

On the FR301 you can remove the strap in the same way you would remove a watch band. Use a small flat head screw driver to compress the spring that goes through the loops of the strap and remove the spring and strap. Repeat this on the other side. I would think this is how the strap attaches to the FR201 also. I haven't had to look into this, but Garmin probably sells replacement straps.

Re: GPS v. Foot pods for Distance/HRM devices

guest — Fri, 05 Aug 2005 12:41:31 GMT

I have not used my Forerunner in a city so I can't speak to its accuracy in the city. I love my Forerunner right now, but I have to admit, I do most of my running in a subdivision terrain.

Here's a COOL link that I just picked up from a message board to map my runs. If you zoom in on the roads you're running, it is very accurate on calculating your distance. If you're not interested in your pace while you're running, you could use this map and an old fashion stopwatch to calculate your workout pace.

http://www.sueandpaul.com/gmapPedometer/

Re: GPS v. Foot pods for Distance/HRM devices

guest — Wed, 27 Jul 2005 02:21:35 GMT

I have posted several times about my experience with the Gramin Forerunner 301 GPS monitor. From experience, if you're running under heavy tree cover for extended periods of time, the GPS monitor will loose it's signal. It regains the signal in the clear and then predicts your distance based on a straight line, but you will more than likely be disappointed. For me, I found that I wasn't running under tree cover as much as I thought I would be. So the GPS format works well for me. Since I don't use the pedometer type distance monitor, I can't speak to it's accuracy when you change stride length going up and down hills under the trees. I suggest find a store that will let you return the monitor within 30days if doesn't meet your expectation. That's what I did before I purchased the Garmin Forerunner 301. Good luck. I don't think either system is going to be perfect. I like not having to attach the foot pod to my shoe every run though.

Re: Garmin Forerunner 301 VS Polar 625X

guest — Sat, 23 Jul 2005 15:11:39 GMT

UPDATE:

I purchased the 301 back in early June. I have used it on almost every run since buying it. Overall, I'm very satisfied with my purchase. Here are a few of my comments/observations.

1)I like knowing my training pace/heart rate and total distance as my workout proceeds. I hate running without it now. I need to return my unit because the backlight doesn't work and I told the customer service rep from Garmin I was really going to miss it for the few weeks that it was going to be gone.

2) I really think the distance calculation is accurate. I never question my run distances now.

3) The heart rate monitor is just okay. It does spike a lot so I can't use the "max" heart rate number that the 301 shows me. I do believe the average heart rate number for my run. After using the heart rate monitor for a month, I can pretty much tell what my heart is without using the monitor based on my physical condition and pace at the time. If you're wanting to save money, consider the Garmin 201. It's probably $100 less expensive than the 301 which incorporates the heart rate monitor. You can borrow a friends heart rate monitor for a month and get to know your heart rate based on physical excursion and pace. After you know that, you really don't need the heart rate monitor anymore. HOWEVER, I'm glad I bought the 301 with heart rate monitor.

4) I had to replace the heart rate monitor's battery that came with the unit after one month of use. I thought this was a little short lived. I'll see how long a brand new battery will last now. On the plus side, it was really easy to replace the battery, the battery was only a couple of dollars and I found the battery at the local grocery store.

5) Concerning GPS signal loss - 95% of the time I don't have a problem. Most of my runs are in subdivision type terrain. I have run in the rain with my 301 and had no problems. I did run a 1/2 marathon in the hills of KY and had some problems with signal strength and loss. Because of the hills and heavy tree cover, my GPS was giving me lap alerts inconsistent with the mileage markers on the course. However, when I crossed the finish line, which was also the starting line, my total miles was 13.1. Can't complain about that. On future races, I might not use the auto lap feature unless I know the course is fairly open and flat.

6) Training Software: I don't use the training software for anything more than just personal interest. The software was easy to install and start using. I do love showing my friends the elevation/pace trend of my 1/2 marathon I ran in the hills of KY. I lasted about 7 miles before the hills, temperature, humidity and lack of training took it's toll. I had to start walking up the hills which the GPS monitor picked up. It was actually a pretty funny trend graph.

7) 301 Size: It's big. However, it doesn't bother me while training. On the plus side, at races its easy to find other Garmin users and start up a conversation. Everyone I have talked to loves their unit, but then they are all "gear geek's" like me.

Well that's about it. Overall, I'm very satisfied with my purchase. I would much rather use the Garmin Forerunner over the Polar 625X. I like the fact that the forerunner is a two component system (watch and heart rate monitor) versus the three component Polar system (watch, foot pod and heart rate monitor).

Re: Garmin Forerunner 301 VS Polar 625X

guest — Sat, 04 Jun 2005 19:04:54 GMT

Thanks for the good review. Sounds like you haven't had any problems with the FR301 that are big nuisances for the money you paid. For instances the HR monitor spiking or the distance measurement not being very accurate. I'm getting real close to pulling the trigger and buying one myself. I got a small bonus last quarter that I'm thinking of siphoning off $250 for myself before the household checkbook sucks it away.

Re: Garmin Forerunner 301 VS Polar 625X

guest — Fri, 03 Jun 2005 18:39:27 GMT

How's its tracking ability on cloudy and/or cloudy rainy days?

Re: Garmin Forerunner 301 VS Polar 625X

guest — Thu, 02 Jun 2005 23:12:37 GMT

Thanks Rick for the thumbs up vote on GPS monitors. Do your clients find them very accurate or only good enough for what they want to do? Any of them complain about signal loss when going under heavy tree areas (trail running)?

Re: 2nd week training for marathon help

guest — Thu, 02 Jun 2005 01:34:19 GMT

Sounds like you're a beginning runner with no mileage base under your belt. I wouldn't start with a marathon as my first goal race. I would consider finding a 15K or half-marathon race to start training for. You're going to end up getting injured or having a terrible time on your first marathon.