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... with a strap?

Former Member over 9 years ago

Has anyone ever seen the "cadence lock" issue when using an external HR strap? I'm waiting til after Manchester Marathon to return my watch as faulty (I have an RMA but don't want to go without it til after the race) but in the meantime I've stopped using the optical sensor and using the strap. When this happened.

https://connect.garmin.com/modern/activity/1103856131

After my warm up you can see a section with an elevated heart rate, roughly in line ith my Cadence... after a couple of miles it reduces down to the normal level in line with my effort. You can see there is no dramatic drop in pace or elevation that accounts for it - if anything its faster and going more uphill.

I've turned off my optical sensor (In Menu > Settings > Heart Rate Monitor, turned it from Auto to OFF) and the strap was paired OK.

Is it possible there is still some crossover?

0 R_Tellis over 9 years ago

Could be as simple as not enough moisture between skin and contacts on the strap, or static from your shirt. Once you start to seat a bit those problems are mitigated.

0 Former Member over 9 years ago

That's possible, but I always lick (Yeah I know) the sensors and it was absolutely PISSING with rain when I went out yesterday.

I've had erratic symptoms like that with a strap before but never has it so closely matched my cadence. Often its actually reporting much much lower than I am working in those instances.

It just seems awfully coincidental...

0 robkalinsky over 9 years ago

Yes, I used to see something like this all the time with my chest strap. Like you, I always wetted it, but it always showed an elevated heart rate the beginning of runs for a bit. Looking back, it was likely cadence lock, although I did not know it at the time. I actually thought my heart was elevated at the beginning of runs, but that is almost certainly not the case. I'm not sure how to avoid this issue.