Hi. Did u solve this issue? I've experience the same. Happened after a few months using them. So frustrating. I've reset the watch but still the same. It happens to my 245 and 945. Natural arm swing. No phone or bottle at hand during running. Even i stop glancing at the watch for the sake of testing the cadence data. My avg cad is 180-190. But the graph will shows half of the cad around 90 at most of the points during the run session. Just like your picture.
Can garmin representative reply on this?
Exact same issue here. Are you still experiencing this issue, 1 month on?
My cadence switches between 180 and 90 during the run, skewing the average cadence values to 110–130 SPM typically.
I've been in contact with Garmin Support, had several back-and-forth emails, but the only suggestion has been to restart the Garmin. Since then, radio silence. It's quite annoying, as I did used to use the cadence reading to keep my form in check. Historically, it worked fine, then suddenly this issue arose.
same here. Suddenly having this issue in the past few weeks. In contact with support lots of hassle and no solution yet.
I have replied in another thread. Try to record a video of you running and check your arm swing. Also u can try give your watch to friend for a try. I have solved mine. Even i thought my arm swing is the same but it is not in the video. Another thing to try is go into strength mode, and try do pushup, if the watch record the rep accordingly, then your watch hv no problem. Good luck.
I appreciate your reply here and trying to help but unfortunately all the points you raised failed to make any sense to me:
1 does the video thing mean forerunner series watches measure cadence for selected arm swings?
2 does the friend thing mean forerunner series watches measure cadence for selected people?
3 i bought the watch for running and I expect it to measure my cadence during running as advertised. Just because it works for push-ups doesn’t mean it’s fine because it sure doesn’t work for running and I honestly couldn’t care less about whether or how it works with push ups.
Sorry for the confusion. I thought you are already understand how garmin watch works.
Accelerometer is the sensor in the garmin watch which measure your movement i.e. cadence. So the sensor detect hand movement of running forward and backward swing.
Possible reason u have the problem is because your hand movement wasnt like normal running i.e. your hand goes sideways/ upward-downward instead of forward-backward. also happen when u run for a long time and hand start feeling tired, and your hand movement is not that obvious. Also happen if u run holding phone and water bottle.
The reason I suggest for the video is because im too confident with my arm swing is not the problem initially. So i gave my friend (avid runner) to try and the cadence data has no problem (which means the watch accelerometer is ok). So i asked him to record my video of running and from there I knew my arm swing needs to be improved.
The reason I suggest for push-up is just to test the accelerometer function. Because by doing push up (which is very minimal wrist movement), the watch can detects how many repetition precisely. If you cannot push-up, you can try other easy movement i.e. biceps curl etc.
Hope the explanation now make sense to you
I have this exact problem. I've had the watch for three years, and I've never had a cadence recording issue when running outside, even though my arm swing isn't always super consistent. In the last month of outdoor runs, my watch has stopped tracking my cadence with any consistency. It will get stuck at a cadence of 123 when my feet are hitting the ground at 180-190 spm, easily. What's worse, because my watch is tracking a lower cadence, it also assumes I'm running more slowly--blips in cadence correspond with unrealistic drops in pace (I run 8:00-8:30 usually, but my watch records a pace of 11:00-10:00 minutes whenever the cadence locks at 123).My GPS is turned on--I checked. It's almost like my GPS connection cuts out and that makes my watch lock my cadence at 123-ish and slows my pace, then compensates once I regain the signal by recording a higher pace and cadence than I'm actually doing (200 spm and 6:20 pace, for example).
I've tried a reset once. Planning on doing it again.