Could be, but I don't think it was just me being a little too eager and stepping to hard on the gas at the beginning of the second interval. I actually felt the Kickr resistance spike and it took 20-30 seconds before it slowly came down to the normal 250w. I felt surprised...
As far as the graph goes, I'm ok with showing the pm actual power instead of the smoothed Kickr output. While a smooth graph appeals to my inner OCDness I think I'll survive :)
Thanks for fixing this!
One thing that you'll see differently between our solution vs the Kickr solution is that we're displaying your actual power meter data and graphing that. With the Kickr solution, it's still displaying the Wahoo Kickr power data.
Because of the big flywheel on the Kickr, the Wahoo Kickr data will be smoothed.
I believe that power meter users always want the power meter on their bike recorded; that way you have a single source of power data across all of your rides.
So if you do a jump from rest to FTP like at the beginning of the second power interval in the graph above, you'll see that your power meter actually jumps up much higher than it's supposed to at first, and then the Kickr locks in.
That's just the nature of the beast with any ERG trainer. You're going to get a bit of a spike unless you're extremely smooth and the firmware on the ERG trainer is magical :). We don't actually adjust the offset at all when you make a big jump like that. We give the Kickr a cooling off period to let it kinda set in before we start taking data to apply a new offset.
One thing I could do is make it so that we report the Kickr data instead of the power meter data in TrainerRoad. You'd get extremely smooth graphs, but you'd be hiding some of your power meter data.
Another example of this would be 15 second on/off sprints. The kickr does a pretty good job with these, but you'll be losing some of the top end power that your PM puts out if we just recorded the Kickr data. I think you want to show the power meter data from your Quarq/Vector/SRM/P2M/ect. Although it's a little more jumpy, I think it gives a better representation of what you're actually doing.
As far as the graph goes, I'm ok with showing the pm actual power instead of the smoothed Kickr output. While a smooth graph appeals to my inner OCDness I think I'll survive :)
Thanks for fixing this!
Nate Pearson wrote:
Hey Everyone. One thing that you'll see differently between our solution vs the Kickr solution is that we're displaying your actual power meter data and graphing that. With the Kickr solution, it's still displaying the Wahoo Kickr power data.
Because of the big flywheel on the Kickr, the Wahoo Kickr data will be smoothed.
I believe that power meter users always want the power meter on their bike recorded; that way you have a single source of power data across all of your rides.
So if you do a jump from rest to FTP like at the beginning of the second power interval in the graph above, you'll see that your power meter actually jumps up much higher than it's supposed to at first, and then the Kickr locks in.
That's just the nature of the beast with any ERG trainer. You're going to get a bit of a spike unless you're extremely smooth and the firmware on the ERG trainer is magical :). We don't actually adjust the offset at all when you make a big jump like that. We give the Kickr a cooling off period to let it kinda set in before we start taking data to apply a new offset.
One thing I could do is make it so that we report the Kickr data instead of the power meter data in TrainerRoad. You'd get extremely smooth graphs, but you'd be hiding some of your power meter data.
Another example of this would be 15 second on/off sprints. The kickr does a pretty good job with these, but you'll be losing some of the top end power that your PM puts out if we just recorded the Kickr data. I think you want to show the power meter data from your Quarq/Vector/SRM/P2M/ect. Although it's a little more jumpy, I think it gives a better representation of what you're actually doing.