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

Cadence Lock Issues

Hi,

I figured I would make a separate post for this - mainly because the forum search function makes it really hard to find information relating to the Cadence lock issues in other posts.

So I've now done 3 runs with my Forerunner 235 - once with firmware 3.10, once with firmware 3.13b and once with firmware 3.13b but with a Wahoo TICKR Run chest strap HRM attached.
Run 1 https://connect.garmin.com/modern/activity/975234830 (3.10 firmware and 235 optical HRM)
Run 2 https://connect.garmin.com/modern/activity/977945044 (3.13b firmware and 235 optical HRM)
Run 3 https://connect.garmin.com/modern/activity/978756577 (3.13b firmware and Wahoo TICKR Run chest HRM)
If you expand out the Heart Rate graph and then add an overlay for Cadence you'll better see the cadence lock issue.
For all intents and purposes it has been the same run - though you'll see that I had to stop on the last two runs and re-route due to exhaustion - I'm not a runner and I'm pushing the limits of my current ability trying to improve my cadence and pace, which may or may not be working lol

The second run (the first with 3.13b) clearly demonstrates the cadence lock problem - my BPM and SPM are the same almost the whole way through.
The run I did today with the HR strap shows a clear difference between BPM and SPM.
The HR is a lot less spiky too - but that is to be expected with a chest strap vs. a wrist based HRM, and is still less spiky than the first run with 3.10 shows.

Anyway - does anyone know if there is a way to fix this? Has anyone tried the latest firmware release (3.20) to see if that helps? Or does anyone know if Garmin are aware of the issue and if they're working on it?
  • Former Member
    0 Former Member over 9 years ago
    The last sensor update was January 14th that stated "Addressed issue which can cause wrist heart rate to remain on a fixed value." It really doesn't explain what exactly was to be "fixed" but it's speculated that this was to correct cadence lock. Needless to say, it's one of many problems that still exist with the oHRM sensor. On the positive side, supports says a fix will be released "very soon". LOL.
  • Has there been any firmware updates to deal with this issue. This watch is a bit of a joke with the cadence lock issue. I get it on pretty much every second run...


    Nope, but don't worry... An update will come "soon". Then again, time is relative and their soon is more likely relative to the ramining life of earth itself instead of the life of their customer...

    The last sensor update was January 14th that stated "Addressed issue which can cause wrist heart rate to remain on a fixed value." It really doesn't explain what exactly was to be "fixed" but it's speculated that this was to correct cadence lock. Needless to say, it's one of many problems that still exist with the oHRM sensor. On the positive side, supports says a fix will be released "very soon". LOL.


    Believe that update was addressing the '66bpm' HR lock, not cadence lock...