Anyone expeirence abnormally high Stryd Lap power data after upgrading to 6.0 fw? I see the lap power shows in the 1000 to 2000 range while power should be around 230s.
I just returned from my first run with FW6.0 and the power-values that I get from my Stryd have not changed and show no spikes. Or another way: it works as expected :-) The issue with the power-meters in that mentioned thread is a bit different because Stryd is using a ConnectIQ Datafield and it's own implementation vs. Stryd's ANT+ channel.
Anyway: what's causing the high values that jtsang reported is still not answered.
I actually use a Connect IQ data app called DataRun Premium Copy 2 Version to view Stryd 3s Power and Lap Power and the vale on the Lap power was showing some very high numbers in the 1000 to 2000 range. I did a further test yesterday evening and use the DataRun Premium version instead of the copy version and I did not see any spikes. But that was only a 5 minute test jogging around the house. I'll need to test this further when I do my run this evening. I've reported this to the developer.
Ok, this seems to be different then. I use Stryd's Connect-datafield which is directly talking to the footpod. From the documentation of the DataRun Premium it looks it uses the Stryd via it's powermeter-connection. E.g. it will go through Garmin's eco-system. So in that case I could imagine that you could be hit by the FW6.0 issue with powermeters, as well (the thread that OnlyTwo mentioned).
So if the problems persists, maybe you could give the original Stryd-datafield a try and check if you see correct values there.
If you use the Stryd as a native Ant+ (bicycle) power sensor, you will get the spikes. If you use the Stryd Power data field which creates its own connection to the Stryd, you will not get the spikes.
If you use Datarun Premium, you can download the Copy 1 with 7 data fields. On my request, a spike filter was added to two of the available power fields in that version. The first one is the field which shows average power for a configurable number of seconds. The other one is a newly added field which shows instant power, but spike filtered.
If you use the Stryd as a native Ant+ (bicycle) power sensor, you will get the spikes. If you use the Stryd Power data field which creates its own connection to the Stryd, you will not get the spikes.
If you use Datarun Premium, you can download the Copy 1 with 7 data fields. On my request, a spike filter was added to two of the available power fields in that version. The first one is the field which shows average power for a configurable number of seconds. The other one is a newly added field which shows instant power, but spike filtered.
I was using the DataRun Premium Copy 1 version. That makes sense that I didn't see the spikes on the power field and only the Lap power since that field didn't have a filter applied to it. Interestingly, I didn't notice the spikes on the Data Premium (Non Copy version) last night testing it. But I'll do a run tonight with it and see.
So the average power and power for each lap after the workout when I look at it from GC or TP looks normal. But it’s when the workout is in session, the power on the datafield is abnormall. I emailed Joop who is the developer of the datarun connect in field and he said that it’s not a easy fix to adjust the lap power issue. This seems more to be a Issue Garmin need to fix in their fw. I attached a screen shot of my watch showing the high lap power. ciq.forums.garmin.com/.../1431286.jpg
OnlyTwo, in case you were not being sarcastic towards Garmin: As far as I know, the lap power functionality works correctly in Datarun Premium. It is the data which Garmin feeds to Datarun Premium which are wrong in some watches. If he removes the datafield, it will also be removed from those watches which do not have the error, which would be rather sad.
So the average power and power for each lap after the workout when I look at it from GC or TP looks normal. But it’s when the workout is in session, the power on the datafield is abnormall. I emailed Joop who is the developer of the datarun connect in field and he said that it’s not a easy fix to adjust the lap power issue. This seems more to be a Issue Garmin need to fix in their fw. I attached a screen shot of my watch showing the high lap power.
I noticed exactly the same yesterday with the 5-field copy 1 display...
