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

When stopped 1040 keeps moving drifting? How to stop this from happening?

I use my 1040 for bikepacking racing. When I start off on a 300 or whatever miles route. I don't stop the unit ever, always running. Been using the 1030, 1030 plus and now 1040. It didn’t happen before but know the 1040 never stops moving. When I stop it things I’m still moving and just drifts around. On my file it looks like a bowl of spaghetti. How can I stop this from happening? I don’t want my time to stop and this is messing my avg moving speed.

Top Replies

  • Or does the gps and speed sensor work together?

    In my experience yes and speed sensor nails drift completely, I too run the activity recording without any pause, Audax rides up to 40+ hours…

All Replies

  • While this might be more of a workaround than a solution, why not enable auto-pause? This will pause the recording when it detects that you stopped and resume when you resume. Do you need continuous heart rate recording during the pause, or something like that?

  • I need overall time, average moving speed, avg overall speed for say 40hour ride. I bikepacking race I’m usually don’t stop maybe a 15min nape or to grab resupplies. It I auto pause and sometimes bushwhacking (very slow) this would screw up most of the stats.

  • That sucks I was thinking about just adding a speed sensor but doesn’t look like it would help? If it’s going to sleep after 6mins

  • I was thinking about just adding a speed sensor but doesn’t look like it would help?

    I was curious and looked at my 2 most recent rides, one ride on a bike with a speed sensor and one on a bike without but both using the same 1040 with an "Auto Select" GPS setting. Both rides have the same brief (10 minute) water/coffee stop mid-way. I zoomed in on the GPS trace to see what was recorded at the stop. The ride with Speed Sensor trace has a tiny wiggle of a few metres on the trace but does not record any distance covered while "stopped". The without speed sensor ride trace shows an even smaller "wiggle" actually just a single dot and also records 0m distance while stopped.

    While these are a very limited test case it may be that the GPS is good enough to prevent distance being recorded while stopped, maybe related to the minimum speed for recognising / notifying  "movement" at the start of a ride? The GPS "Auto Select" does not (in these & my experience generally) appear to greatly increase battery usage*. Perhaps try the auto select to see what is recorded while you stop. In any case a speed sensor might still be a good addition regardless of the time out on newer (better?) versions.

    *sometimes you have to doubt the battery estimates, with 100% battery the estimate on my home screen says 95h with GPS on "Auto Select" but changing the GPS to just "GPS" changes the estimate to 78h ?? (you would think they should be the other way round?) I use some agressive battery saving settings so 85-95h is what I would expect and have got in the past.(PS Non-solar)

  • Thank you. Will try all of that. I do usually use battery save mode so it would have just been “GPS” not auto select. My next big event is early Feb 370 miles HuRaCan in Florida 

  • I find I can get much better battery life than the "battery save" settings by minimising the main battery intensive functions manually especially backlight where the battery save or auto settings are too high (for my needs), careful with the alligators especially at night.

  • O there definitely gatorsJoy thank you will try that alsoThumbsup