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

530 auto pause when freewheeling?!!

Crispee
over 3 years ago

Hi, new to Garmin 530 and although all rides record etc and I seem to be coping getting used to the features I have an annoying issue with cadence. Setup is 530 plus speed 2 and cadence 2.

When on a ride and freewheeling at any point, e.g. downhill, and so have stopped pedalling the auto pause will kick in! It then restarts once I start pedalling again. I’ve googled for an answer and found absolutely zero hits for this issue and I’ve no idea what setting would cause this.

Why would the cadence cause auto pause to kick in?

Anyone any ideas?

Chris

  • 0 over 3 years ago

    Check that wheel size look OK under the sensor details for the speed sensor. The Edge will need to bin communication with the sensor for this setting to show.

    Also check what the auto-pause setting is configured to. Is it set to a speed or to when stopped?

  • 0 over 3 years ago in reply to aweatherall

    Hi, thanks for the advice. I’ve checked all my settings are correct. I contacted a friend this afternoon who has a 530 and we double checked my settings against his just in case I missed something but we found nothing. Problem though is the cadence sensor on the crank arm behaving like a speed sensor! Stop pedalling and the timer auto pauses! 

    In the end I switched off the auto pause and left it at that. I put the bike on the maintenance stand and switched everything off and went to do a few jobs. Came back an hour later and switched the 530 on, spun the pedals and all worked without auto pause. Thought I’d give it another go so switched on auto pause again. This time all started up as expected when I spun the pedals, indicated 20mph ish and stopped pedalling…nothing. Started spinning pedals again and timer was still running perfectly. 

    Tried it a few times, switching 530 on and off each time, and works as it should now. Weird! The simple act of disabling auto pause and then re-enabling it seems to have fixed the issue I’ve been living with for the last month. Time will tell if it’s a permanent fix…

    Thanks again for posting!

  • 0 over 3 years ago in reply to Crispee

    Let us know how it goes.

  • 0 over 3 years ago

    Cadence should not be causing autopause to function. My guess is the sensors are misaligned. (The sensors are identical - the sensor guesses what it is supposed to be doing by the accelerometers detecting which way it is spinning.

    1st step would be to delete the pairing of the CADENCE sensor, and see if the problem re-occurs when freewheeling.

    2nd step would be to delete pairing of the SPEED sensor and just use GPS speed, and see if the problem re-occurs.

    By process of elimination, you should then know which is causing the problem.

    When re-pairing the sensors, make sure they are installed on the bike, and give the wheels/cranks a spin BEFORE trying to pair, so the sensors know which way they are aligned. If you want to be ultra-cautious about this, do this one at a time (back-pedal the cranks to wake up the cadence sensor WITHOUT turning the wheel, then freewheel the wheel WITHOUT turning the cranks).

  • 0 over 3 years ago in reply to mcalista

    Hi mcalista and thanks for your detailed response. You’re absolutely correct, cadence sensor should not be causing any auto pause issues. I played around a little yesterday afternoon and performed some of the things you mention above in an attempt to understand what may have been the issue. What is very strange is that the auto pause didn’t kick in as soon as the cranks were stopped, auto pause kicked in once I started spinning the cranks again, then after a couple of seconds would restart the timer. V strange as that isn’t even how it should theoretically operate. 

    At the moment it’s now behaving correctly so I’ll wait and see. Should it show signs of reverting to the issue then I’ll give your process above a go. My friend with the 530 suggested I just reset to factory and start again but that seemed a little extreme to start with lol.