Use Garmin Auto Pause or Not?
-
No new posts
Moderators: k9car363, alicefoeller | Reply |
![]() |
Expert ![]() ![]() ![]() ![]() | ![]() I just recently had my Garmin 310XT repaired (replaced really) and I have been fiddling with all the settings to get them back they way I like them.... I came back from my first solo ride with the new Garmin yesterday with lower than expected averages based on my perceived effort. After looking at the data, I figured out that the auto pause setting is off - when before, I had it on. On my settings before I had auto pause off for run and on for bike. My thoughts were that on runs (mostly trail running) my stops are normally a result of trail traffic and are usually pretty short in duration. I always try to make up the stop with a little extra effort when I get going again. On the bike, my stops can be much longer (traffic lights, etc) and making up that time would, for the most part, be unrealistic - so, I had them factored out of my data with the auto pause. Just curious..... what auto pause settings to you use for run and bike and why? |
|
![]() ![]() |
Master ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() | ![]() I use autopause when stopped setting mostly because I forget to manually turn off and on my garmin unit if I at a stop light or stop to use the restroom. This is especially so if I'm biking. Edited by betyoursilver 2011-08-11 8:28 AM |
![]() ![]() |
Pro ![]() ![]() ![]() ![]() ![]() ![]() ![]() | ![]() I use auto pause for running and cycling training. Set to speed = 0 and (when I remember) turn it OFF for any races. |
![]() ![]() |
Veteran ![]() ![]() ![]() ![]() ![]() ![]() | ![]() I use it for both as I'm already slow. I don't need artificial roadblocks to make me feel any slower like traffic lights etc. Even over the course of a long ride, the slow downs leading up to a light are clear on the GTC graphs and are still impacting my times. Just not as drastically. |
![]() ![]() |
Master ![]() ![]() ![]() ![]() ![]() ![]() ![]() | ![]() I don't use the Garmin, but I do use my auto pause feature for both the run and the bike. As others have said, stop lights and such can really impact your data. I've done 60 mile rides where I've come back and seen 6 or 7 minutes of "stop time"
Just remember to turn it off for races, I've forgotten a few times! |
![]() ![]() |
Elite ![]() ![]() ![]() ![]() ![]() | ![]() I use the auto pause 1. It more accurately portrays my overall speed when I look back at data to judge race pace. Without it, it's just waaaay too low of avg speeds. 2. works well in races. I turn it on and press start when I set up transition. I don't have to mess with it in T1 then. it turns on when I move and shuts off when I re-rack the bike in T2. |
|
![]() ![]() |
Pro ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() | ![]() I use auto pause for running and cycling with speed set to 0.3 for the run and 1.5 for the bike (to eliminate the annoying start stop when you are indeed standing still due to the movement of the connecting satellites). For swimming I have auto pause off as the satellite signal in the water is a bit spotty to say the least (and I have no problem with that!) |
![]() ![]() |
Expert ![]() ![]() ![]() ![]() | ![]() Thanks everyone! I never even thought about the setting while racing.... I have always used the auto-multisport while racing (with auto-pause off for run and on for bike). I usually end up with splits on my Garmin that are very close to race timing results. I wonder what settings the Garmin uses for transitions in multisport mode? |
![]() ![]() |
Master ![]() ![]() ![]() ![]() ![]() ![]() ![]() | ![]() My biggest thing on races is that, obviously, the time clock never stops so I want to make sure my device is as accurate (to the time clock) as possible. I've lost signal going under bridges and such which has altered the data, usually not a big deal on the bike since when your racing you don't have to worry too much about stop signs and overpasses and tunnels go by pretty quick, but on the run that tunnel may take 15, 20, 30 seconds... who knows? Also FWIW, my run auto pause is .5 MPH and my bike is 1.5 MPH. Works pretty good for me, my watch, and my usual training grounds. |
![]() ![]() |
Champion ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() | ![]() I never autopause. Clock doesn't stop in a race. That being said, if I will be at a light for an extended period of time or I stop to refill water I do go ahead and stop the Garmin then restart when I continue on. That's mostly because if I'm supposed to be doing 3 hours of Z2 then I really don't need to count the 5' that I'm in the gas station getting water. But I don't see the need to stop it for every slowdown just to inflate my ego about training speeds. |
![]() ![]() |
Veteran ![]() ![]() ![]() ![]() ![]() ![]() | ![]() jldicarlo - 2011-08-11 3:09 PM I never autopause. Clock doesn't stop in a race. That being said, if I will be at a light for an extended period of time or I stop to refill water I do go ahead and stop the Garmin then restart when I continue on. That's mostly because if I'm supposed to be doing 3 hours of Z2 then I really don't need to count the 5' that I'm in the gas station getting water. But I don't see the need to stop it for every slowdown just to inflate my ego about training speeds. just to clarify, it's not about ego, it's about accuracy. If I'm comparing one ride to another 2 months later, I'd like to compare my actual performance instead of the variables of how long I stop for 26 traffic lights on ride 1 for 12 minutes vs 21 for 4 minutes on ride 2. |
|
![]() ![]() |
Champion ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() | ![]() Out2BeALoser - 2011-08-12 8:17 AM jldicarlo - 2011-08-11 3:09 PM I never autopause. Clock doesn't stop in a race. That being said, if I will be at a light for an extended period of time or I stop to refill water I do go ahead and stop the Garmin then restart when I continue on. That's mostly because if I'm supposed to be doing 3 hours of Z2 then I really don't need to count the 5' that I'm in the gas station getting water. But I don't see the need to stop it for every slowdown just to inflate my ego about training speeds. just to clarify, it's not about ego, it's about accuracy. If I'm comparing one ride to another 2 months later, I'd like to compare my actual performance instead of the variables of how long I stop for 26 traffic lights on ride 1 for 12 minutes vs 21 for 4 minutes on ride 2. If you are stopping you are getting rest. So the REAL comparison is the total time. I could ride 25 mph for 5 miles if I rode a mile at a time then stopped for 5 minutes in between each mile. But I couldn't ride 25mph for 5 miles without stopping. |
![]() ![]() |
Veteran ![]() ![]() ![]() ![]() ![]() ![]() | ![]() Ok I'll try once more. Comparing my moving time to my moving time gives a far more accurate picture than the vagaries of including how long each light cycle happened to add. I'm not trying to put up my number, I'm trying to remove variables. And, since I've done that comparison over and over, you can see the trends. And yes, even that there are stops you will Always have to make. So I'm not comparing that wow, I did that ride in 4 minutes less. I'm comparing that on x hill my moving time has been consistent, or between street x and y. |
![]() ![]() |
Master![]() ![]() ![]() ![]() ![]() ![]() | ![]() Stopping for a couple minutes at a light shouldn't make a difference in the effort being sustained for the lighter efforts, so cutting out that time is ok. When running a tempo or intervals, yes, because it's a size-able break for one of them and can have a very noticeable effect. |
![]() ![]() |
Master![]() ![]() ![]() ![]() ![]() ![]() | ![]() Realized that last sentence may be confusing (too much computer time at work). Stopping for a couple min or more (or at all) during the "on" parts of a tempo or interval session does impact the run. And can do so quite noticeably. As for using autopause then or not, I don't know. That particular session is kind of messed up already, so do what you like. Best to avoid it altogether for them. |
![]() ![]() |
Champion ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() | ![]() Out2BeALoser - 2011-08-12 2:02 PM Ok I'll try once more. Comparing my moving time to my moving time gives a far more accurate picture than the vagaries of including how long each light cycle happened to add. I'm not trying to put up my number, I'm trying to remove variables. And, since I've done that comparison over and over, you can see the trends. And yes, even that there are stops you will Always have to make. So I'm not comparing that wow, I did that ride in 4 minutes less. I'm comparing that on x hill my moving time has been consistent, or between street x and y. Extra rest is a variable that is important and really should not be removed if you are truly trying to compare. It's like when people don't count their rest intervals in the pool in their swim time...makes the total number meaningless! You can't remove wind or temperature fluctuations and those probably have just as much time impact as resting does. There were no less than 12 stop signs on my 6 mile loop I rode in Iraq last year. If I had left autopause on during my 50 mile ride on those short loops I would have lost a LOT of data because the Garmin would have been constantly starting and stopping. |
|
![]() ![]() |
![]() | ![]() I leave auto-pause off on all sports. I can see why people would want to use it either way. I use SportTracks to import my data and it can include/exclude stopped time with the click of a button, but I find that I rarely take out the stopped time. |
![]() ![]() |
Veteran ![]() ![]() ![]() ![]() ![]() ![]() | ![]() jldicarlo - 2011-08-12 3:00 PM Out2BeALoser - 2011-08-12 2:02 PM Ok I'll try once more. Comparing my moving time to my moving time gives a far more accurate picture than the vagaries of including how long each light cycle happened to add. I'm not trying to put up my number, I'm trying to remove variables. And, since I've done that comparison over and over, you can see the trends. And yes, even that there are stops you will Always have to make. So I'm not comparing that wow, I did that ride in 4 minutes less. I'm comparing that on x hill my moving time has been consistent, or between street x and y. Extra rest is a variable that is important and really should not be removed if you are truly trying to compare. It's like when people don't count their rest intervals in the pool in their swim time...makes the total number meaningless! You can't remove wind or temperature fluctuations and those probably have just as much time impact as resting does. There were no less than 12 stop signs on my 6 mile loop I rode in Iraq last year. If I had left autopause on during my 50 mile ride on those short loops I would have lost a LOT of data because the Garmin would have been constantly starting and stopping. Let's just agree to disagree, ok? It works for you, great. Just don't dismiss everyone else who uses it as doing so to inflate their egos. |
![]() ![]() |
![]() | ![]() I use it for the bike but not for the run. and I try to remember to turn it off for races. |
![]() ![]() |
Extreme Veteran ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() | ![]() Not wishing to Hi-Jack, but I also have just recieved my "refurbished" replacement 310xt, had the auto pause on my a recent bike ride and it constantly cycled on and off even though I was constantly moving (albeit slowly - I was climbing) I presumed that it had not properly acquired the satelites, anyine else have this issue. Also, on 3 different 310xt I have had the same problem, plug in to charge and it turns on instead of going into charge mode, then I go to use it and it is discharged - tell me I am not the only one, Garmin is starting to think I have Munchausens'! |
![]() ![]() |
Member ![]() ![]() ![]() ![]() ![]() | ![]() I don't use autopause, but instead choose to simply press stop in the rare occasions when I stop - which are generally limited to stoplights. While I understand the arguement about not stopping, etc... - the reality is that I can't run a red light during training - such acts usually involve getting flattened by semi trucks. And yes, it does affect rest and your numbers, I'm also reaslitic about how much it affects it. If I'm running a 20 mile long run and manage to hit 3 lights along the way, each for 45 seconds - I'm not too concerned about the supposed rest there. But by the same token, if I choose a cycling route through the city and I've got 10-15 minutes of stoppage time, that's significant. The good news here is that auto pause and manual pause are all recorded as timestamps, and most modern programs like TrainingPeaks shows the total stoppage time in there, so nobody's fooling anyone. Of course, you can solve this problem by simply avoiding routes with stops, or in the case of cycling - selecting a trainer for some of your rides (I do all my non-long rides indoors on a trainer). |
|