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

Edge 1040 auto-pausing even when doing 25kph!

steventonm
over 2 years ago

Happily riding along at 25kph, and suddenly my device goes to "pause", then quickly goes to green "start' arrow, then quickly returns to the desired status quo. It is unsettling to say the least. I cannot believe it is shadow causing GPS to disconnect. Good clear terrain on the ride. I am using Multi GNSS, Auto-pause when stopped, Timer start mode manual. The fault occurs quite often, maybe 7 or 8 or so times in a ride of 30 minutes. Any ideas, is it a firmware bug, does anyone else have the same issue?

  • 0 over 2 years ago

    and you don't have a speed sensor on the bike?

  • 0 over 2 years ago in reply to aweatherall

    Yes, I did think that might give a solution, but, frankly, when I spent £520 for the thing, why should I have to buy a speed sensor, when there is supposed to be the most sophisticated GPS choices in it of any Garmin! I had a Garmin Edge 305 for over 13 years and it gave me no trouble at all!!!

  • 0 over 2 years ago in reply to steventonm
    steventonm said:
    frankly, when I spent £520 for the thing, why should I have to buy a speed sensor, when there is supposed to be the most sophisticated GPS choices in it

    GPS isn't as accurate as a properly calibrated speed sensor.  

    It will give you a relatively close approximation of speed.

  • 0 over 2 years ago in reply to fallingrock

    Thank you both for the quick response. Maybe I will just have to swallow my stubborn-ness and get the garmin wheel-hub speed sensor for the sake of another £30, to see if that will resolve the issue. Cheers!

  • 0 over 2 years ago in reply to steventonm

    neither me nor my wife experience an autopause with 1040, even very slow uphill, almost still.

    Contact support, it may be software, but at least in 14.50, this problem does not exist on our 2 units !

  • 0 over 2 years ago in reply to Klick

    My Garmin Express only show version 14.2 available. I believe though that Garmin are rolling out 14.50 and have about 50% coverage so far. I am keeping a close eye out for 14.50. Thank you for your comment.

  • 0 over 2 years ago

    I had the same issue today for the first time, in multi-GNSS mode. Did not see it before in 14.50 and 14.20. Changed to multi-GNSS-multi-band for the last hour of the ride and did not have the issue again. 

  • 0 over 2 years ago in reply to benpete

    I still have some more experimenting to do, but I think I have found my answer. Firstly, on Garmin Connect ride report, you can see the drop to "Zero Speed" occurring many times on the speed graph, when I am actually doing 20+kph, which is the evidence of the auto-pause.

    I am using the 1040 with an e-Bike, and the 1040 has been using the speed, cadence, and distance sensors that the e-Bike already has to offer. What I have discovered is that the e-Bike Speed sensor was defaulted to Wheel Size Automatic on the Edge, which was 2224mm. (27.87mm Diameter Wheel). My bike is a 29'er, which yields near-enough 2310mm circumference!!! This is very nearly 4% error in measurement. SO, I have disabled the speed sensor coming from the e-Bike, and have been using just Balanced Multi-GNSS. I have found no more drop-outs occurring since doing so. Yes I am now using the GPS for speed and distance, and I know I can change the circumference manually, but I am quite happy with the precision offered. So I think that what was happening was the device was being corrupted with false date from the e-Bike, and the GPS was telling the computer to hold off for a few seconds to catch up with the erroneous data coming from the e-Bike, and doing this many times during my rides. I intend to get the MTB back on the trails soon, so I will confirm to myself that all is good now with no more drop-outs as the MTB will rely entirely on the 1040 for speed calculation. The more I think about it, the more I am sure that this is what was happening. I imagine that if the ACTUAL circumference were to be used on the Edge (manual input) then the device will not drop to pause, but that will be another experiment when I get time.