@GMiller
Glad to hear that Garmin USA provided excellent customer support - that’s been my experience too as an owner of several Garmin products.
Ride On!
Hi G, what email address did you use to get in contact with Garmin? I was about to return the unit but was afraid all they would do was replace it with another Flux 2. I would be tempted to take advantage of upgrading to the Neo.
Would you be able to send me the email you sent them?
I think the unit works fine…
in sim mode, try to find an uphill section, get in the big chainring and middle of the cassete and its impossible to not go above the 60w mark !
i have also tacx flux 2 and got no problem at all, and I useit with a MTB 1x12, 36t chainring…
Hi Jeffro
I went to the Garmin website and then selected support. There was a number I called toward the bottom for product support. Followed the prompts to get to the cycling trainers. The person I spoke to created a ticket for me and sent me an email that started the process. The number I called was a US number. Not sure if it’s different depending on what country your in.
Cheers
I think it’s the unit.
I’m also having the same issue with the Flux 2. I almost can’t get above ~300W… except those 2000W peaks when stopping paddling. Looking at the chart of the old Flux (Garmin Tacx Indoor Bike Trainers) there shouldn’t be a problem going 500W with the 39x19 at 100rpm cadence. When I’m using ERG and doing a 400W interval the resistance goes up to 280-300W and that’s it. The same problem exists in the TACX Training App. Below 300W the resistance is controlled just fine. I filed a support ticket on the 2000W issue and now also requested support on this issue. I hope this gets resolved…
I’m having the same issue unfortunately on my only 2 months old tacx flux 2.
Even on my hardest gear i can’t seam to go above 400/450watt. Even when i’m spinning around 110rpm… I also have some major power spikes of 2000watts for 5secs. This happens around 4 times a hour. I detected this problem with bot ant+ and bluetooth, so the connection doesn’t seem to be the problem.
I filed a ticket at Garmin and hopefully they can resolve the problem.