Issues with power meter
-
I have an issue with power reading using the Race and Inpeak V2 left arm power meter. It works but when I ride and raise my wrist to check the power value it shows zero. Then the power starts to increase gradually while reaches the actual value. It seems to me the watch does not show/calculate the 3s avg power and shows it on the display. Instead it starts averaging it after the display turns on. Of course I am pedalling when it happens.
Does anyone have the same issue? It is not a huge one but it is time consuming to wait 3+ seconds to see the actual value. My Epix never did it with this Inpeak power meter. Checking the power graph it seems ok. -
@szleslie it is known issue after the last firmware update. We can just wait for the fix…
-
@nseslija Thx for the info.
-
I’ve had consistent issues with power when indoor cycling. I use Assioma single-side pedals, and although they’re several years old, they’re very reliable.
What I experience is frequent power resets when maintaining a consistent cadence. I’ll be spinning around 90 rpm, power will be reading as normal, then drops off to 0, and then takes 3 seconds (as that’s what i’m using to display power) to get back to the correct power value. It happens approximately every minute.
I haven’t the pedals connected to anything other than my watch - I don’t use a headunit or anything like Zwift. I’ve never seen this with any other Suunto watch, or with previous head unit (Wahoo Bolt)
-
@Steven-Limmer Hi, it is a known issue discussed in other threads.
-
A new firmware release should be imminent, let’s see if the issue is fixed (I have no power meters to test).
-
@isazi I’ll test that on first day when update arrives
-
@Likarnik well, real soon as far as I know
-
@isazi It also happens with the inbuild power meter, at least on Race S. Just try a Run with Power Sports Mode and you should see the Value dropping every few minutes
-
@isazi Good to know, then I will wait for it instead of ordering the new Coros Nomad just based on frustration about this issue…