Wrong Cadence while not moving

[moppedurmel]

Good morning!

I've replaced my Oregon 600 by the 700. I like the wireless features, mainly the automatic transfer of tracks to Garmin Connect without using a cable.

But I've seen seen an annoying thing with the cadence sensor. It won't go to zero when I'm standing. You can see it in the attached graph:

Bildschirmfoto von 2020-05-31 07-04-44.png

Is this a bug?

Kind regards
Stefan

[GPSrChive]

Please send gpx file to webmaster@gpsrchive.com and include a link to this discussion and the GarminDevice.xml file from the GPSr.

[moppedurmel]

Information is on the way.

[GPSrChive]

Where is the included graph taken from?

[GPSrChive]

GPSrChive > Oregon 7x0 > Common Issues > Bug 46 posted and reported to Garmin.

[moppedurmel]

Where is the included graph taken from?

The graph was taken from the Garmin website Connect. It's a screenshot with the details of a bicycle tour I've made. It was the same tour the gpx file I provided.

[moppedurmel]

Just tested this issue with the fresh 5.00: Still the same bug.

[moppedurmel]

After some mails Garmin decided to send me a cadence sensor 2, the current model.

Now the behaviour is better. Cadence went to zero. But not in every case:

Fenix:

fenix_cadence.png

Oregon:

oregon_cadence.png

In the meantime firmware version 5.20 is available, so i've to do a test with this version.

[GPSrChive]

Thank you for the update!

Are you still connecting to the Cadence Sensor 2 via ANT+, or are you now using Bluetooth?

Please let us know how it works once you test more with firmware 5.20.

[moppedurmel]

Yesterday I could do a parallel test using Version 5.20 on the oregon.

As you can see the behaviour with the Garmin Cadence 2 is better than with the old one. So there must be a dependency with the sensor hardware.

The sensor is connected to the Fenix and the Oregon using ANT+. As far as I can see the Oregon supports bluetooth, but primary only for the communication with a smartphone.

But there are still segments where the cadence isn't zero where it should be.

Fenix:

fenix.png

Oregon:

oregon.png

Maybe one can make a comparison between the Fenix and an Edge? It could be that the measurement