Once done correctly! there is no need to do it
again until the next configuration change on the Regarding temperature Power (chain!
chainring! pedals). Rotor told me that the gauges were not
sensitive on this point and therefore there was no need to do an offset
before each ride! nor during a ride. I am surprised by this
statement…But indeed and unlike a powertap or SRM Regarding temperature which calibrates itself
each time you are freewheeling! there is no manipulation to
do on the ROTOR.
My test conditions took place in good weather
without wind and with a temperature of 11/13 degrees which did not change. The
various sensors were all taken out 20 minutes fax lists before the tests to avoid any
temperature/calibration problems! the 0 offsets were carried out before each test.
I started with the Powertap/Rotor Power pair. 2 Garmin 500s with the latest update were
used with recording every second enabled. The power display
was set to 1 second! so without smoothing! to see the
responsiveness of each sensor. From the first few turns of the wheel! we notice a
big difference in responsiveness. The powertap starts at the quarter turn but
it is also a well-known criticism. The power keeps fluctuating and
it is very difficult to follow a setpoint. This is why 99% of
users use the ‘average power 3s’ function to smooth the display.
Conversely! the rotor is very stable. It is even quite disconcerting how
stable it is. It feels like a home trainer! Better than an SRM! Changing the display to 3s does not
change anything. On the other hand! you have to quickly go back to 1s because
unlike the powertap! you realize that the Rotor is not very fast at detecting
changes in power.
So with a display averaged over 3s it’s even worse
Indeed! as soon as you change power! the powertap reacts
much faster than the rotor! so a power peak from a very short 3s sprint! the rotor has little chance of seeing it at the right intensity. You 6 most common marketing automation pains: part two have to press for 5s
to get a semblance of value! I say semblance of value because on this side
! the information does not seem to be well
managed. On sprints around 1200 watts detected on the powertap! the rotor detects 900 watts! A customer also using the rotor
regularly sends me peaks at 1600w (he has the latest update) while he
does not exceed 1100w on a powertap. The power tap! when used against the SRM!
delivers the same values as the latter! at 20 watts. So we can really
think that the Rotor handles sprints and very short accelerations be numbers poorly
in general.