brianwchan wrote:
Hi Nick,
Hoping you can help with a problem I have running TR on my Kickr Snap.
Currently running the TR trial, as I received the trainer as a Christmas present. I've tried performing the 20 min FTP test twice: first time running on my 2014 Macbook Pro, with constant ANT+ dropouts and the TR app eventually freezing and crashing; the second time on my Surface Pro 4 which correctly picked up all sensors (no dropouts), but experienced extremely inconsistent spikes in resistance throughout the ride, but most noticeably during the 20min test. I can't really overemphasize how erratic the resistance spikes were; totally unrideable such that eventually I had to stop because the constant pausing as the trainer ground to a stop rendered the data/test useless, as well as causing me to blow out my legs.
Here's my setup:
- Garmin USB ANT+ Dongle on Surface Pro 4
- Garmin Vector 1 dual pedals
- Garmin Fenix 3 HR for heartrate in ANT broadcast mode
- Garmin Speed sensor (rear hub, accelerometer)
- Wahoo Kickr Snap firmware 2.1.5
Notes:
- I performed an advanced spindown when I received the unit 2 weeks ago
- I perform a normal spindown every ride
- I've turned off Bluetooth on the Trainerroad devices screen in order to reduce interference since all my sensors are ANT compatible anyways
Questions:
1. On the devices screen, the Kickr Snap appears to be listed twice: as a generic "ANT+ Trainer" and also as a "Kickr Snap" - which device should I pair with?
2. During the 20min FTP segment, from the documentation online it appears that the it looks like the mode of resistance should be "Standard" during the test. However during my segment in the lower part of the screen it looked as if I was set in "Resistance 20%". This occurred when paired to the trainer as an "ANT+ Trainer" as opposed to the "Kickr Snap". I assume being in the incorrect mode (resistance) contributed to the poor experience during FTP testing, but still doesn't make sense given the suddenness and magnitude of the resistance increase. For example, I'd be pedaling along ~200 watts, big ring, middle of cogs - perhaps watts would drop by 5-10, but cadence stayed the same - I'd then experience a crushing increase in resistance to where I could barely move the cranks fully standing up on the bike. It would also then be impossible to downshift to the small ring and larger cogs because of low chain speed. Lastly, this same scenario has also happened when in the small ring and largest cog; leaving me with no lower gears to bailout on - very frustrating!
Thanks in advance for your help - I was hoping to replace much of my outdoor training with the Kickr but it's been nothing but issues so far.
Sorry to hear about the rough experience here Brian. :(
Before we move forward with any troubleshooting, we wanted to confirm something about the advanced calibration you performed on the Snap: did you perform this within the 'Wahoo Fitness App' or the 'Wahoo Utility App'? You'll need to make sure it's completed within the Fitness App which can currently only be done using an iOS device. As far as we're aware, Wahoo doesn't support this advanced calibration on any other devices. When you get a chance, let us know that you've done it within the Fitness App on an iOS device.
1. You're seeing the Snap being advertised over two different connection protocols: one being the ANT+ package and the other being the Bluetooth package. In your next go at things, try pairing the trainer as a "Kickr Snap" only, which is over BT. To avoid any additional frustration, test things out in the workout titled "Power Training Ridethrough" as it is a 5 minute workout that can be used to make sure your power is being locked into target. Make sure you're only paired to the following devices: Kickr Snap, Vector pedals, HRM, and Speed sensor. I mention this list of devices because sometimes the power measuring device within the Snap can pair as well which will throw a wrench in things. So keep an eye out for any additional "power meter" being paired other than the vector.
2. You're seeing "Resistance" mode instead of "Slope/Standard" because of the way the standardized ANT+ trainer profile (ANT+ FE-C) was implemented. Resistance/ERG are the only modes the ANT+ FE-C profile supports. If you connect the trainer as "Kickr Snap" you'll see the Standard (Level 3) setting once you enter a testing interval. Despite that limitation with the ANT+ FE-C profile, you'll still get a reliable estimation of your FTP using either mode change. This isn't what is causing the problems you're experiencing, but if you prefer Slope to Resistance (non-linear resistance curves to linear resistance curve), connecting via Bluetooth will make that option available.
Lastly (sorry for the novel), when you try things out again put yourself in a relatively easy gear (small cog up front, middle in the back) and set your FTP back around 200. There is a possibility your FTP was underestimated because of the weird activity you were getting.
Our support agent whom you have an open conversation with is going to follow-up with you where we can keep things more organized. We'll look forward to hearing back from you there and getting you back on the bike without issue. Thanks again for bearing with us through this.
Get Faster with TrainerRoad