I want to share an issue I’m experiencing with my Tacx Neo 2T smart trainer since the latest firmware update (the one that enabled the Zwift Cog and virtual shifting). In recent weeks, the cadence reading has not been stable:
Experience: I’ve been using smart trainers since February 2017 (Wahoo Kickr Core until March 2020 and Tacx Neo 2T since April 2020). I weigh 88 kg, my current FTP is 260 W, I typically pedal at 90 rpm and find it difficult to go above 95 rpm, so I’m not a rookie.
Unexpected behaviour: During workouts, the cadence displayed jumps from my usual 90 rpm to 110, 120, 140 or even 150 rpm for a moment and then returns to 90. This is very noticeable during warm‑ups and cool‑downs below 150 W with ERG enabled, but I’ve also seen it—although less often—at power levels above 160 W. It occurs in both Zwift and the Tacx Training app and doesn’t depend on the length of the session.
Why it matters: I chose the Tacx Neo 2T for its technology and accuracy, but since that update the cadence reading is no longer precise. I have several videos showing the issue.
Not a sensor failure: It’s not that the cadence isn’t being measured or that the crank arm can’t reach a sensor; it seems to be a matter of the quality of the data sent by the trainer to my computer, iPad or iPhone after the update.
Has anyone else noticed this problem or know of a setting or solution? Any suggestions would be greatly appreciated.
I have a Neo 2 (not 2T) that has been updated to the latest firmware, and have not experienced any issues with cadence. Something 2T specific, perhaps?
I’ve got a 2T with the latest firmware. I’ve used it with and without virtual shifting & I’ve not had the problem you are having, sorry. Hope you can get it sorted.
I had the same thing happen yesterday! The cadence jumped around quite a bit, and I also had the power output go low, on an ERG workout, and it only rose when I shifted up a couple gears. Note, I was NOT using the Cog, this is a standard 11-speed road bike on the 2T.
I wondered if it was the high communication rate (race mode?) somehow freaking out. SO I had the cadence jump to over 120, and the power lag at least 30 watts until I shifted, both of which made absolutely less than zero sense. ERG is ‘you ride what the set-point is’, the power demand doesn’t depend on cadence or ‘gear’. (EDIT: Or was it the Zwift app telling me I needed to work harder to get the power up? )
I’ve done around a dozen rides since I switched to the 2T so that was a real weird experience. (The workout had the cadence demand at 65rpm, and output at 175, so is that a sweet spot for it to trip out?)
I’ll likely ride that workout again today and see what happens. (I did take some screen shots)
Also that ride I also had a problem that the Companion app would not ‘connect’. Both the Zwift computer used and the Companion app iPad are on a dedicated wifi ssid, so they should have seen each other and latched on and happy days, but I even logged out of Companion, logged back on, and, crickets…
Same here, not that it likely matters. (Mine is also Di2, but Ultegra is very popular) It seemed to me to be a Zwift issue, as I didn’t get dinged for the hysterically low output. Almost like it somehow knew I did put out the right power, but the Zwift display didn’t show it. Was surprised that I got the star.
@Juanfer I see you shared this in Garmin’s forums already, and would recommend you also reach out to their support team like @Rich mentioned, since this is also happening in the Tacx app where Zwift is not part of the testing setup. Garmin Support should be able to give you a better sense of what is happening with your trainer regarding the cadence readings being off, and advise you on next steps.
I’ve also recently switched back to my Tacx NEO 2T (with Zwift Ride & Cog) after a few years of using the Zwift Hub and KICKR Core, and have not experienced the issue you are seeing, or any issues for that matter. Hopefully Garmin can help get this resolved for you quickly as the NEO 2T has provided the best in-game experience for me compared to all other trainers I’ve used to date
I did get a couple instances on that last ride where was possibly skating around a bit. Also had the instance where Zwift reported I was not putting out enough power in ERG mode, with output only going into range after up-shifting. Maybe I’ll just turn off race mode. Set it to see what it’s like - FAST. Too fast?
You haven’t said how you’re certain this is the case. You sound like you’re aware that the Tacx Neo 2 and 2T have a capacitive cadence sensor that detects when your (steel) pedal axle passes it? See Garmin’s support site for details about this.
In some cases, the pedal may not pass close enough to trigger the sensor reliably. You might try attaching a steel item to the crank (a spoon, a spanner, some household item like that) with a zip tie or tape to test this out and see if it improves reliability in your case(s).
I’m familiar with how the cadence sensor works on the Tacx Neo 2T, and that’s precisely why I believe the problem is not in the hardware but in how the signal is processed or transmitted after the latest update.
I’ve run several tests, both in Zwift and in the Tacx Training app, using two different Neo 2T units and various devices (PC, iPad, iPhone). In all cases, the same behavior can be observed, and I have videos clearly showing it: the cadence reading momentarily jumps to values like 110–150 rpm and then returns to the actual ~90 rpm, without any change in my pedaling. This occurs even in long sessions and in different environments, so I rule out that it’s random or tied to a specific setup.
As for the hypothesis that the pedal might not pass close enough to trigger the sensor: I find this unlikely, since the phenomenon happens intermittently during a session in which, for the rest of the time, the reading is stable and accurate. That’s why I don’t see the need to attach metallic items to “bring the sensor closer”; the correct reading is present and only fails in brief bursts.
If you can replicate the problem in the Tacx app, you are in a good position to talk to Garmin support about it since that would indicate it’s unrelated to Zwift.
The following steps are used to restore the software of a Tacx Trainer.
Open TTA on a mobile device.
Connect the trainer.
With TTA open in the background open the firmware restore link.
Select ‘‘Set Up Trainer’’ or just click the trainer.
Select Firmware Update.
Select ‘‘Update Now’’ to update the trainer.
Please use this link here →
tacx[dot]page[dot]link/?link=https%3A%2F%2Fapi[dot]tacxtraining[dot]com%2Fdevice-api%2Fv3%2Ffirmware%2F70ZR8LGNV3AljwIt9Ab4YC&apn=tacx.android&isi=1575884075&ibi=com.garmin.tacxtraining
I am also having the same problem in that I’m trying to restore the 2T Firmware to 0.0.38 but the link provided in the various forums does not seem to work anymore. If anyone has a new link to try to follow the steps to restored firmware I would be very grateful.
Hello Nick, I suggest you to contact Garmin support, they’ll give you a personalized link for you, but it’s not sure the link will work… I had to send my 2T back to Garmin and after a quick internal check they decided to replace it. I hope that was just a case, but it seems that recent firmware updates aren’t that stable…
)
