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

Cycling training using FR645M with a bike speed/cadence sensor

I did a Cycling training with my FR645 Music (firmware 2.5) and used a Garmin bike speed/cadence sensor GSC 10.

During this cycling training, the watch keep displaying an annoying message "Calculated wheel dimensions" all the way.

This message was displayed almost every 20-30 seconds with a beep. Sometimes every 1-2 minutes. The watch displayed a message "Error 02" or "Error 20" (I don't remember exactly) once too.

How can this be fixed please ? (I would like to keep the auto calculated wheel dimensions)

Except this annoying message, the sensor seems to work well.

0 rclar over 7 years ago

I just posted about the same problem over in the speed/cadence sensor group. I didn't get the error message you did, but I was inundated with calculated wheel dimension alerts all hour long during my first ride with the watch.

I'd rather not set the wheel size to manual, but something certainly seems to be wrong with the 645. My 920xt never had this problem.

Thanks

0 Former Member over 7 years ago

Are you using different bikes while doing your cycling workouts? I don't understand why you wouldn't manually set the wheel size unless you were constantly changing bikes with different wheel sizes?

0 Fab86 over 7 years ago

Yes, I am using different bikes at different moment. So, I don't want to calculate wheel size by myself if my watch can do it. It's a feature provide by the watch. So, I would like to use it.

rclar, Yes, it's probably the 645 which has a problem. My old FR410 never had this problem with the GSC 10.

0 rclar over 7 years ago

The price on the new style speed/cadence sensor had dropped considerably, so rather than just trying a new battery, I switched to the new style. I still have a gsc-10 on my other bike however, just haven't been out on that bike yet this year.

I had noticed what I thought was a problem with trainer road this winter, where the cadence wasn't generally recording, but I chalked that up to a trainer road issue.

0 Fab86 over 7 years ago

It seems to be fixed with the last firmware.