So close, but alas, so far away ...

After a month of 'missing right sensor' and 'low battery' warnings (the pedals are only a month old) I replaced all the batteries, straightened the tape that had gone awry, applied some oil and otherwise tried to ensure my Vector 3's were in tip-top shape.

I went on a ride today and voila, everything was working. It was a wonderful thing. PCO, power phase, standing/seated time ... and of course accurate power! No beeps or other weirdness.

Just when I thought I might be out of the woods, Cycling Dynamics (and everything that goes with it) disappeared! Like gone. See attached fit file. Anyone got any thoughts on what is going on now?! What a mess. :(

0 CSYVE over 7 years ago

Could someone from Garmin please take a look at the fit file I attached above and let me know what might have caused the loss of Cycling Dynamics about halfway through my ride?

It would be really great if someone produced a fit file analyzer that allowed riders to take a look at the diagnostic and other info in the fit file themselves ...

0 t_smit over 7 years ago

I looked at it. Unfortunately your head unit (510?) does not store all the diagnostics info that Vector generates.

The situation is that there are several identifiable problems with cycling dynamics:
1. CD getting lost only on the right pedal. This might be due to a very short power interruption.
2. CD stopping on both pedals. This can have two causes:
First, it's actually been turned off somehow.
Second, with head units that support both BLE and ANT, if the user has both link types in the head unit's sensor list, then the head unit could possibly experience a short interuption in the ANT reception, and switch to the BLE link. The external result of that would be that the recording of the CD information disappears, but Vector would be completely unaware (and there is nothing that the Vector team can do about that).

We are investigating the possible ways that the cycling dynamics configuration (and possibly other settings) could get corrupted to cause the behaviour you and others are seeing.

There are numerous Fit file decoders out there, but they will only decode the publicly released message types.

0 CSYVE over 7 years ago

Thanks for checking it out, t_smit. Yes, it's a 510. I usually ride with a Elemnt Bolt. I've been riding with both in the hope of being able to provide some insight that would solve the issue.

Both the Bolt and the 510 were connected using ANT. The 510 doesn't support BLE (?) and I have never used BLE to connect a sensor to my Bolt (I'm not sure it can do that?)

It looks like CD was lost on both pedals. Before, when I was getting the 'missing right sensor' warnings, I would see PCO drop off for that one pedal, but the other would still report PCO. In this case, both were gone.

To eliminate all possible BLE interference I'm going to turn of Bluetooth on my iPhone before my next ride and I'll report back ...