Hello,
when I stop pedaling it happens sometimes that the cadence value remains blocked at the last measured value.
It happens when very low cadence values are detected, although I stop pedaling the last cadence values are displayed (and recorded).
The Garmin is purchase by me about 2 months ago, firmware 10.00.
I have tested two different cadence sensors, with the seperated cadence sensor and the integrated speed / cadence sensor, but the problem is the same.
These sensors do not show the problem with my previous Garmin Edge 510, so I think it's a software problem with the Garmin Edge 820.
Anyone have this issue?
If it is the cadence sensors that uses a magnet then make sure you put your left forward when coasting. With the left foot back (horizontal) the crank arm magnet used by the cadence sensor is next to the sensor so will trigger a reading if the crank arm moves a little near the sensor.
I see this with my 820, and it seems the issue is in the 820 not the sensors.
The "stuck" cadence values occur on the 820 with both Garmin's Magnet-free sensors (original, not BT v2) and a Wahoo BlueSC combined sensor.
Recording the same ride simultaneously on my old Edge 800 and the newer Edge 820, the 820 shows these stuck values while the 800 does not, both onscreen and in the .fit files.
I have a PowerPod indirect power meter which captures the ANT+ sensor data and uses it for it's own calculations. The data saved by this device prove that the "stuck" values are not being transmitted.
I see similar phenomenon with the Edge Explore. Sometimes (but not always) when I stop pedaling, the cadence value is stuck on the last non-zero value. It's definitely an issue with the head unit and not the sensor itself, because I have this sensor paired concurrently to a FR735XT, and the FR735XT does not show this issue.