My Move still isn’t showing any symptoms, but it’s a Kickr v6 on rails, so yes, it can suffer from this problem. Still not sure yet why mine hasn’t been affected, I don’t think anyone has identified the trigger.
As far as I understand it, the global trigger is having virtual shifting enabled (Zwift ride… only option if you want “gears”, or on Zwift play controllers).
After that, it looks like it’s debatable with some combination of specific gears or not and coasting down hill.
Symptoms are power staying on if you start coasting, together with a jump in cadence - the only amusing thing about this is seeing your avatar spinning away at 120rpm as you sit doing nothing. Other symptom is elevated power during normal riding/racing. Mine is +5-8%
My workaround to avoid doing a factory spin down (which does work but as others mentioned… if you can avoid… avoid) is to boot up with no blue tooth. Go into Zwift, Kickr is WiFi connected so no issues - but do loose shifting, peripherals. Then beech island loop as suggested… perform multiple up hill then downhill coasts (after powering up to at least 40kph). Keep fingers crossed. Hopefully the “spinny man” goes away after 4-10 goes.
After that, save ride, exit Zwift , power off (unplug) trainer. Wait a minute. Plug back in. Turn Bluetooth on…. Then Zwift… and hope it doesn’t reoccur mid ride /race…
To say this is a faff is an understatement!
Fingers crossed for a fix in the lifetime of this trainer.
1 Like
Having virtual gears is a prerequisite, but not a trigger. I’ve done race-ending sprints in high virtual gears before coasting, hill climbs, coasted down hills, ERG workouts, all the normal things you’d do while riding/racing, and (fortunately) so far never triggered any symptoms. Some have said it may be related to the physical gear ratio used (e.g. little ring vs big ring) - I’m on a triple chainset and leave it in the middle chainring, and a middle gear. I run a 10-year-old Win 10 PC over ethernet for Zwift, with Bluetooth and ANT+ device pairing. I use Wi-fi for the v6/Move trainer connection with Play controllers. I’ve seen several suggestions for the trigger, but none have been confirmed that I’m aware of.
Certainly hope a fix comes soon as it sounds like a hassle to keep resetting the calibration without using a factory spindown - I did one of these to make sure everything was okay even though showing no symptoms. Came back with a brake factor of 1.00 and continues to work fine. I’ll bookmark your detailed workaround in case it becomes a problem though!
I spoke to wahoo as well
No ETA on fix, but they are working on it
Known issue (triggered by virtual gears 22-24)
For my clarity- this is occurring with zwift play, zwift click and zwift ride?
Hardware does not matter as this is a firmware issue, right?
I starting looking at the JetBlack Victory or the Elite Direto as alternatives (I have a Kickr V6 on backorder and may cancel).
Reports are its affecting KickR v6, KickR Core, and KickR Move. (The KickR bike has its own on board virtual shifting)
I’ve seen it triggered while climbing and also in gears 19 to 20 at high flywheel speed with the larger (46T) chainring in use.
I’ve not seen it triggered on my small chainring (30T), but using a small chainring causes a muddy pulsating feeling through the pedal stroke and is not pleasant.
We have had no reports of other hardware such as Zwift Hub being affected.
I’ve been racing with mechanical shifting for the past few weeks and I have had no issues - except for a couple of harsh/missed gear changes under heavy load.
3 Likes
I recently ran into this issue the other day in a 5v5 ladder race. I couldn’t super tuck as it would spin up to like 5-10W right after I went into the position. Quite annoying.
I use a Kickr V6 together with a newly bought Zwift Ride with Zwift Cog V2. I’ve used my Kickr V6 for a long time with my outdoor bike with manual gears without any issues. I hope a fix will land soon as it is essentially impossible for me to be competitive as I can’t properly do downhills.
1 Like
Concerning to me that they still seem focused on the 22-24 gearing as it is definitely a more widespread issue
3 Likes
Agree - definitely isn’t remotely gears 22-24. In fact, I haven’t used those gears the last dozen times the issue has come back.
For consideration - you might want to try out loading into Figure 8. Figure 8 has a nice downhill that starts sooner than Beach Island Loop - I stumbled into this because of the 30xp per km that could be attained last week, during Stage 1 of the Tour of Watopia. I believe it fits the bill, in terms of a significant enough decline. Make sure you don’t accidentally turn like I did - you’ll encounter the downhill when entering the tunnel. Admittedly, I was unable to remedy the issue, once it started - but just wanted to throw that out there, as it sounds like you’re having a little more success with that workaround.
1 Like
I had a V6 on backorder, expected in Nov- and was going to go in a different direction- but turns out it shipped yesterday.
So- there are no issues if I use mechanical shifting, right?
Thanks.
Correct, it works fine without the virtual shifting.
How can you know for sure if you are affected? I have a V6 and use Virtual shifting frequently. I dual recorded not long ago with stages PM and did not see any issues. But sometimes when downhill in zwift, supertuck not always go smooth and stays at 10w or so…But never high rpm or 30-40w extra.
I just did Mountain Mash route and go direct in downhill of epic KOM and watts drop to zero and I did go to supertuck and no issues visible?
So how can I now if I am affected with the bug? ;-). Or is it not always noticable?
If you’re staying at 0 watts and super tucking ok, chances are that you are ok. The most comprehensive way is dual recording, but I know that can be extra work. It sounds like your dual record was ok, so you have a couple of solid data points that you aren’t being impacted.
Mine starts a bit gradual, then it gets worse, if I don’t do the factory spin down. It is creeping back today. I do have a guaranteed method of triggering it - basically a full blown sprint, shift up into the gears pretty far. It brought the issue back right after.
As Chad says. If you see coasting watts then the issue is present.
The KickR auto calibrates every time it detects coasting above 37kph and is allowed to spin down.
So it’s possible that it can sort itself out during the same ride/race and visa versa. There have been some DQs in the Zwift World Series for that reason as they are dual recording and race control can see the drift.
I think Chad’s on to something with the trigger, it seems to happen to me if I go full gas and shift up a few gears under load then coast. This normally happens at the end of a race, but can also be when cresting a long climb and getting into supertuck.
1 Like
Did virtual shifting ever work without issue with the version 6?
How many Zwift World Series races are going to be annulled before this is fixed?
Hey everyone - Wahoo has released a firmware update on KICKR v6, KICKR CORE, and KICKR MOVE that should address this issue.
Please update using the Wahoo app at your earliest convenience.
UPDATE October 29 - Wahoo has updated their firmware release note pages linked above with this information. Please note the difference between auto-calibration and factory spindown in the context of immediate resolution.
- Fixed: Auto-spindown errors when using virtual shifting in specific scenarios.
- In the previous firmware versions, there was an issue with the trainer calculating the correct spindown values during the auto calibration process in certain scenarios when also using Zwift Virtual Shifting. The conditions could result in the trainer reporting “ghost” watts (watts while coasting), and could result in a power offset throughout the ride. If you are currently experiencing “ghost” watts, this firmware update will not immediately fix the issue on its own, but having updated to the current firmware, the auto calibration process will fix the power offset over time without manual intervention. If you would like to resolve the power offset immediately , you can complete a factory spindown.
6 Likes
Is there some way to prompt users to do that?
I expect a large percentage of users have never updated their firmware since getting a trainer unless they have had an issue.
On that it would be kind of cool if zwift could prompt that for all trainers…maybe a feature request.
4 Likes