ANT+ FE-C control of KICKR v6
AnsweredI'm attempting to use my Karoo 2 to control my KICKR v6, both updated to the latest available firmware. I've read through https://support.hammerhead.io/hc/en-us/community/posts/360049908333-Newbie-workout-trainer-issue .
My Karoo 2 is connecting to my KICKRv6 with the ANT+ 'Trainer 24785' sensor. I do NOT have the Power sensor or Bluetooth 'Wahoo KICKR 60D1' sensors connected. I'm using a workout synced from TrainingPeaks that has power target data in it. When I start a ride with the default 'Indoor' profile, I then attach a workout to it. The upper field does show power data, but it just gives me up/down background arrows depending on my power compared to what the workout calls for. Starting a simple workout that calls for 150 watts as a warm up, I can easily spike it to 300+ watts in the space of a second or two. The power does not normalize down to 150 watts, but instead remains as high as I care to make it for extended periods of time (20 seconds, 60 second, infinity)
Using other trainer controller software like Wahoo SYSTM, TrainerDay, etc seems to "just work" for a given workout.
What am I doing wrong? Is this behavior normal and expected? It certainly makes the Karoo2 effectively useless at controlling a smart trainer if so.
-
Hi Zach: Sorry for not getting back to you sooner. We appreciate you sharing your experience with us.
We were testing this from our end to understand the behaviour. While testing this, we were able to see a few seconds delay for the current Power to normalise once you cross well ahead the target power and stops pedalling. A delay more than 3 seconds is not expected.
Since you are seeing a delay of more then 10 seconds for the current Power to come down, could you please share a short video showcasing the issue? You can share a link to a video uploaded on photos.google.com or any other cloud services that you'd like to use at support@hammerhead.io
This helps us to investigate the issue further.
-
I’d guess the trainer probably just somehow failed to connect as controllable/in ERG mode the first time around. If you happen to get this again, disconnecting and reconnecting the trainer (or turning the Bluetooth and ANT+ interfaces off and back on might be quicker) would probably be enough.
Please sign in to leave a comment.
Comments
3 comments