This might not be easy, but any ideas how to take out a load of ridiculous spikes and drops to get, at least a semblance of a reflective TSS from my ride today. 790 TSS for 100 miles, Nah!!
Ok, I have tried the Fitfile tools to take out the power spikes and it cut out anything above 1300 watts. The graph looks more like it now, however, the data is still reading maximum of 6662 and TSS 790?!
I'm guessing, even though the Fitfile editor steips out the big readings, the data is written into the text. Is there anyway to sort this??
Ps - Vector 3 Dual. Latest firmware


Nah, I'm not feeling the 790. On all accounts the ride was a low intensity ride. It was reading an IF 0.997! I wish!! HR was AVG of 119. Even training effect registered it as a base ride.
There are distinct periods within the activity where the power meter disconnected. Well it looks like it. There were 3 distinct spikes biggest 6652w. I was able to to to take out any high power readings above 1300, being generous. All that did was take the graph markings out but still left the Data there.
Bear in mind, the Vector 3 duals have new batteries on the latest firmware. I've had zero probs with them. So, I'm guessing it's not the pedals.
I don't connect them via BT, I'm guessing that's more flaky than ant+, well, until the new firmware is updated for 530.
Does GCM have to be running on the phone for all things to be running correctly? Or should the 530 just work independently? I noticed a difficulty in connecting speed sensor and Vector 3, until the app was open on the phone. But perhaps that was my imagination?!
Lastly, on 2 cafe stops, I paused the device (pressed pause) and then turned off the 530. Had a brew, turned it back on, gave it a couple of minutes to locate itself, then started the activity again. Every time I calibrated the pedals. Maybe, unecessary, but still did it
Also, connected via Ant+ was scoshe HR and Garmin Speed sensor (magnetless)
Here's the activity -
https://connect.garmin.com/modern/activity/3777095323
Thanks for the help
Garmin Connect does not compute any of the power stats. They are computed on the Edge and written into the FIT file as part of the session record. Stripping out the power spikes will not fix the power stats unless you also modify the session record.
I recomputed the data and got the values shown below, which are contained in the new FIT file. If you wish to use them then delete your activity from GC and upload this file.

I used the http://fitfilerepairtool.info/ tool to do this. There is an option when you go to save the file to recompute the power stats.
You might want to try the 3.41 beta release. I ride with a V3 paired over ANT and I'm not seeing any spikes.