I have ran into a bit of trouble today with my Garmin 520 not working correctly. One the way to work it was auto stopping while moving and only recorded 1.6m of the 2.5 mile route.
I went for a ride after work and was getting the same issue. So i stopped and turned off Auto Pause. Carried on down the road a little further and looked down to see 0mph when i was doing around 15+. Stopped again to try to figure out the issue, decided that the battery in the speed/cadence sensor was low and was causing some sort of issue. Went to Asda (other supermarkets are available) bought new battery and replaced it. Had to re add sensor to garmin then set off again.
Intermittent signals from normal to nothing were still coming through so i stopped again and switched off sensor in the garmin 520 and after that i had no more trouble. Just rode on without any cadence info.
Soooo. Why is the speed sensor taking priority over the GPS data for speed, surely the gps data should be first with the speed sensor as backup for tree cover, tunnels etc.
Has anyone one else had this issue, and is my Speed cadence sensor dead?
Not sure if theres a better place to post this than the bike thread
When you are stopped, the GPS is still "moving". The garmin GPS doesn't get instant feedback so cadence takes priority.
I think the candence sensor was not connected, it wouldn't be an issue.
You can see this when I stop at a red light below at 01:53 - 01:59 - this was a test video with my first commute with an action camera. It's sped up and you might want to turn your volume down before hitting play
No its not that it was still showing speed when i stopped, it was auto pausing while i was moving at speed, so i switched auto pause off. Then i noticed it was showing inaccurate speed data including zero mph when i was riding steadily at around 15mph..... But it all worked correctly once i switched off the speed cadence sensor in the head unit.
Which Garmin sensor are you using, just for interest?
Different manufacturers use different priorities, but I believe Garmin is speed sensor over GPS (I can't recall for combined and separate speed/cadence sensors).
It sort of makes sense, as there should be less noise on a wheel based speed sensor than GPS, so higher accuracy, but there are times when it doesn't work, such as signal drop out, or if you're off road and having lots of wheel slip. I don't believe any let you change priority though.
Its a Garmin gcs10. that seem to be no longer available. I have one on each bike, but this one is the oldest one. Might have to fork out some cash for the newer type that attach to the pedal and the wheelhub and don't require magnets
Wolfdancer, I ah see. I posted late and forgot about coasting while moving.
For cadence, I use the "wahoo rpm" which attaches to the pedal. It's cheaper than the garmin and ant+ and bluetooth compatible so you can use it with with non-gamin apps / devices. It uses a gyro rather than a magnet for cadence so just attach to the pedal. The downside is that very bumpy bits of road with throw it off. strava seems to do decent job of smoothing out those peaks / troughs caused by pot holes.
I should have thought of this sooner, but i still have my old garmin 500 unit, i should test if the sensor is sending info to that unit correctly, which i can try on the way to work tomorrow.
I will try changing the data recording on the New head unit too
Test ride commute Old garmin recorded 1.2 miles of the commute with sensor info switched on New unit recorded the whole 2.5 miles with sensors switched off
Free training & racing tools for runners, cyclists, swimmers & walkers.
Fetcheveryone lets you analyse your training, find races, plot routes, chat in our forum, get advice, play games - and more!
Nothing is behind a paywall, and it'll stay that way thanks to our awesome community!
TriSport Fetch: The smell of 220
Nov 2024
