It seems my actual cadence on our Wahoo Kickr Core is often much faster then in-game cadence of my avatar!?!
Below 30rpm real cadence my avatar its virtual legs sometimes even completely stop turning while my speed on a steep climb like Alp du Zwift stays constant 10kmh, since my real legs are still producing 200+W.
Funny enough on the flats @0% my actual and virtual cadence ~85rpm often is the same.
I couldn’t find this specific issue as a known bug here via Search
Bluetooth connections between Kickr and iPad Air seems fine.
Is their any way to fix this so my virtual in-game cadence always stays 1:1 in sync with my real cadence?
Zwift doesn’t so anything with the cadence reported by your trainer other than displaying and recording it. So if your in-game cadence is wrong it’s because your trainer is reporting it wrong.
Almost every trainer on the market (including your Kickr Core) estimates your cadence from fluctuations in power as you pedal. So what’s likely happening is the estimate is simple wrong sometimes.
The only way around that would be to pair an actual cadence sensor.
thank you Steve. appreciate.
I’ll try my Garmin cadence sensor attached to the left crank-arm of my bike instead as alternative. Then report back if this improves/ resolves real rpm cadence at crank vs. virtual/measured cadence by Zwift differences
Indeed that works as it should with a real cadence sensor connected!
I wasn’t aware e-trainers only estimate cadence (rpm) based on power data (W), not actually measuring it combined with rpm data of flywheel-sensor.
The same flywheel speed can be achieved with various different cadences down to which gear you’re in.
Some trainers do have cadence sensors (neo 2t does j think) but most just use the spikes in power to estimate when the pedals are pushed down. If you have a less smooth pedal stroke (I do!) It can make this estimate erratic or just incorrect.
interesting. clear tx. same here regarding (lack of) smooth pedaling.
I like strong ‘thrusty’ pedaling against higher resistance better (70-80rpm), then too light ‘airy’ high cadence (>110rpm).
Obviously when cadence drops below 40rpm my Kickr Core has a hard time calculating actual rpm!
Anyway, fixed now with a spare Garmin cadence sensor laying around unused👍
@Chris_Holton @Steve_Hammatt thanks for helping me out understanding this issue!