Software 6.0 power meter issues

I wrote to te support, they answered just the usual bla-bla-bla nothing... I was not so brave to downgrade firmware, so I will wait until they do something :(

I too contacted support and of course they're asking me whether I am using third-party power meters. I mailed them that I didn't observe the issues when simultaneously recording things with a FR735XT and that the issues disappeared after a downgrade to 5.1. Let's see whether this convinces them, but I am afraid that first level support is just to far away from the developers.

If anybody has an F5+ with the latest (buggy) firmware and an Edge or another power meter compatible watch, I suggest you use both devices to record an activity and mail the two resulting FIT files to the beta team. Maybe that'll get their attention.

i have srm pc8 and fenix 5 plus, the fenix gives me the error, if sending archive of the two will serve them?

I have the same issue. Fenix 5 Plus Sapphire and TACX Neo Smart. Powerspikes up to 60 000W.

Okay, at least Garmin Germany has acknowledged the problem and confirmed that they are working on it:

"Uns liegen Meldungen vor, die das Problem, das Sie beschreiben, zum Inhalt haben.
Die entsprechenden Entwicklungsabteilungen in den USA wurden bereits über den Sachverhalt informiert. Die Kollegen dort überprüfen das Problem und arbeiten an einer Lösungsmöglichkeit.
Bis es soweit ist, möchten wir Sie um etwas Geduld bitten."

It basically means that the development team is aware of the issue and is working on a fix.

What I had to do to get around first level support ("are you using third party power meters" - much like some people here in the forum) was:

1. Make clear, that the issue is not present with firmware 5.1 and that downgrading fixes the issue.
2. If possible, record the same activity with a different device - in my case a F735XT.

I suggest that everybody opens up cases - usually the people assigned to allocate resources to bug fixing are so far removed, that they tend to look at the number of cases associated to a specific bug, so complaining seems to be the only thing we can do to push priority up.

Seeing spikes when using a Stryd running power meter too (I pair the Stryd as a power meter and footpod, then use a custom data field to show power while in run mode).

Fortunately Stryd has a datafield I can use that writes the power (and a few other running-power metrics) to the FIT file as extended channels - the Stryd data shows NO spikes, confirming that it's the watch itself rather than the third party power meter.

I already logged a support call and was asked to send my watch content (minus maps) to the support team. I got this by reply:

Thank you for your email.
I have added your details to our investigation case on the issue.
Rest assured as soon as we have an update or solution we will let you know.
Kind regards,
Jeremy
Garmin Europe

new BETA 6.51 which should contain a powermeter fix is available

I installed beta 6.51 and went for a run with my Stryd powermeter last night. The beta seems to have fixed the power spikes.

Can someone tell me if the estimated calculation of VO2max is affected by these peaks? it gives me the sensation that no. Thank you