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

Absurd training stats afte training with Zwift and Tacx Neo

After 6.0 FW upgrade I get absurd stats after training with Fenix 5 Plus, Zwift and Tacx Neo, e.g. 60000 W max power or w/kg FTP of 1125 W. The W numbers during training look OK, though.

Seems to be FW bug! never had this behaviour before...
  • I see the exact same thing- several 60000W power spikes on my watch that don't show up in either Zwift or on my Garmin 1030.
  • I have the same thing. V6.0 forward on Fenix 5 plus records 60000+ watt spikes in power readings from Tacx Neo. Figure are fine on edge 1000 and recorded in Zwift. Anyone know If this has been logged with Garmin?
  • Anyone know If this has been logged with Garmin?

    Never hurts to log it yourself, irrespective of whether someone else has logged it. The more the merrier.
  • Former Member
    0 Former Member
    I'm getting the same issue since FW update with sporadic peaks of 57,000W+ when using Garmin Fenix 5 with TACX Neo but no issues with Edge 800 or Edge 520.
  • The recent FW betas seemed to fix this for me and others.
  • Former Member
    0 Former Member
    Just spoke to Garmin support. Was advised this is a known issue and is set to be rectified with the new public update. Currently not available - no date offered but the beta is available at https://www8.garmin.com/support/download_details.jsp?id=14335 and from the comment above, this appears to have fixed the issue for some.
  • Same problem. I wish I could output this average power (especially on a recovery session as this was!)ciq.forums.garmin.com/.../1467951.png
  • This issue with solved for me with the 6.58 beta.
  • Former Member
    0 Former Member
    Just spoke to Garmin support. Was advised this is a known issue and is set to be rectified with the new public update. Currently not available - no date offered but the beta is available at https://www8.garmin.com/support/download_details.jsp?id=14335 and from the comment above, this appears to have fixed the issue for some.


    Funny that. I've been going back and forth with Garmin Support about this for 3 months.

    They have led me along for 3 months now. I have an APAC device, and first they lied and claimed they were getting an engineer to provide the bug fix for APAC devices for me. When pushed, they provided no such link and just went silent. I kept asking them where the link was for a fix for APAC devices, and nothing -- just silence. They are now failing to address the problem and not responding to me over what is a significant defect for such an expensive watch.

    I've now had to escalate to Fair Trading. Appalling behaviour from Garmin, who treat their customers with complete and utter contempt.
  • Funny that. I've been going back and forth with Garmin Support about this for 3 months.

    I've now had to escalate to Fair Trading. Appalling behaviour from Garmin, who treat their customers with complete and utter contempt.


    I have to completely agree with you. It's absolutely unacceptable that Garmin has left his major bug (which affected more power meters than just the Neo) out for over FOUR MONTHS now! FOUR MONTHS! It blows my mind. I haven't been able to use my Neo 2 with my Garmin for an entire season. After just getting a warranty replacement for my Fenix 5X Plus last week, I'm looking hard at Suunto or an Apple Watch for the future. This is total garbage Garmin.

    And yes, I know there are beta firmware releases. This is an unacceptable excuse. I don't want to be a beta tester. The betas have their own issues. I could see trying a beta if you are a bleeding-edge kinda person, and didn't want to wait a week or two for a public release.. but four months (and counting, mind you)? No.