This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Auto Pause/Start Working HORRIBLY

TheFitnessGuru
over 2 years ago

Okay, did my first ride with the Edge 1040, standard model, not solar. And I have to say that the Auto Pause and Auto Resume are abysmal! I am used to my Edge 1000, where it takes almost exactly 2.5 seconds both to auto pause and auto resume again, once I get over the auto pause speed. I am not expecting miracles here! I get that these devices aren't perfect, and I never complained about the Edge 1000's 2.5 second start/stop times, because GPS requires cell data, or at least communication with satellites, and it seems reasonable to expect delays in things like auto starting and stopping.

I was on with Tech Support (lol did almost as much phone troubleshooting while stopped on my first 1040 ride) and they couldn't figure out what was wrong. I tried setting the pause speed a little lower. It was 5 MPH, but I dialed it back to 3 MPH, hoping that would help. It didn't. Well, it helped starting, but only by a second or two. They couldn't figure out what was going on.

Basically it takes TEN SECONDS from when I get pedaling more than the pause speed for the 1040 to restart, and almost the same thing, 8 seconds from when I come to a complete stop, to pause.

Now after I hung up with tech support, and continued my ride, I also tried setting the GPS to most accurate, which if I remember right is regular GPS + Glonass? but I could be wrong. Either way, once I did that, the projected battery life immediately plummeted, which is perfectly fine by me. I don't need anywhere near 100 hours of battery, so I like to max out all the settings.

After hanging up with Garmin, I also noticed something interesting, and this I believe is what's causing the problem, but I have no idea what's causing the cause of the problem. I noticed that whenever I come to a complete stop, it takes the 1040 at least 8 full seconds to count down from whatever speed it was just registering to the auto-pause speed. This does NOT happen with my Edge 1000. The two+ seconds pause on that unit is just I assume the device catching up with the data, which I expect and am okay with. But taking upwards of ten seconds just to acknowledge that I have come to a stop is very weird to me.

  • 0 over 2 years ago in reply to TheFitnessGuru

    I guess that's a nice work around for the 1040 being unable to auto pause and restart quickly enough.  I don't have the speed sensors and it's too bad that one has to buy them in order for auto pause and restart to work properly.  

    In contrast, we have Strava on our phones and auto pause and restart seems to work very quickly.  In fact someone I ride with has the voice notifications turned on and I can here his phone say pausing ride and resuming ride almost instantly when he stops and starts riding again.  I guess I took I took it for granted how well that worked on our phones.  I wonder if it is because there are motion sensors in the phone.  Maybe it uses the motion sensors to indicate motion and no motion quicker.  It's too bad that the Edge 1040 doesn't recognize starts and stops as quickly as our phones do out of the box without any extra hardware!

  • 0 over 2 years ago in reply to CNY MTBer
    CNY MTBer said:
    guess that's a nice work around for the 1040 being unable to auto pause and restart quickly enough.  I don't have the speed sensors and it's too bad that one has to buy them in order for auto pause and restart to work properly.  

    I was concerned that the speed sensor, on the hub of my read wheel whose battery was dead was going to have the guts ruined by a battery that leaked/exploded inside, but that didn't happen. I bring this up because when I spoke to the lady in Garmin tech support, I told her in no uncertain terms that Garmin's engineers and developers had just under 30 days to get this sorted out and working properly, or I was going to send this back in the box and go back to using my Edge 1000. Now, had my fears about the speed sensor ended up being true, after reading this thread, I would have called Garmin again and asked for a gratis speed sensor so I could make sure and get this sorted out within my return window. I say this because I honestly think that if you call Garmin's tech support and link them to this thread, then ask for a courtesy speed sensor, I am pretty sure they will give you one. If not, you can always decide to tell the tech you will send the 1040 back as not working properly.

    The reason I am suggesting you point the tech to this thread is because when I spoke to her the other day, she said this was NOT an issue she had ever seen or heard of before on the 1040. Obviously, this thread is tacit proof that this is an actual issue, and one quite easily resolved.

    So if giving anyone unhappy with the auto start/stop auto time a free speed sensor stops people from mass-returning these devices, then it really is a win for everyone involved.

  • 0 over 2 years ago

    I read a lot of remarks regarding the speed sensor. I never ever used a speed sensor on my road bikes, and never had complaints until 1040 on auto-pause. I have experience with GPS biking with forerunner 610, 910xt, edge 500, 800, 830, and now this. This needs to be fixed.

    Don't get me wrong. The speed sensor is a great solution if you want to have more reliable data riding in densely covered places and or technical terrain with tons of cornering like mountain bike tracks often do.

  • 0 over 2 years ago

    Yes this delay is terrible, using GPS.  was instantioiouse as far as i could tell on the 1030.  unfortulanty you can't put a speed sensor on a DTSwiss 1100 hub it too thin. 

  • 0 over 2 years ago in reply to Julian Young

    Yes … you can. A piece of expanded foam from laptop packaging cut down to suit under the sensor. 

  • 0 over 2 years ago

    For me the delay using GPS is 2-3 seconds.  I have no idea why it is faster than some others are seeing but it is.  It's the same as my Epix2 watch which i used side-by-side for a while.

  • 0 over 2 years ago in reply to djwalker1260

    Yep.  At the relatively low speeds of cycling, and particularly the low speed when you want auto-pause to work, GPS is not the best due to its inherent position/speed noise. That's why using a speed sensor has always been an option, even with GPS bike computers.   The current strap-on speed sensors can be used on either the front or rear hub.  I prefer the front.

  • 0 over 2 years ago in reply to looigi

    So why do "cheapies" like the 130+ work so much better?  I run the 130+ gps only with autopause and it is significantly, by 5-10 seconds, more responsive and accurate on GPS only.

  • 0 over 2 years ago

    hhhhmmmm ... Trialled it this morning .... 1040 (std) set to "when stopped", no speed sensor ... and on a tree lined road at a set of traffic lights about 7 "mississippis" but about 1/2 mile further on another set of lights but clear sky view and it's about 3 "mississippis".

    "resume" from both was about the same time frame - 2 to 3 "mississippis"

    You'll have to excuse the less than scientific timings as it was a busy road - trying to time it accurately seemed a little less than sensible :)

  • 0 over 2 years ago

    If you’re training and especially if you care about your power data, auto pause should never be on.