Has the currentCadence handling changed?

Hi,

I have several running fields in the store. For ages I had to double (multiplied by 2) the averageCadence field to show the correct value on the watch and passed the currentCadence value 1 by 1 (without multiplying). This worked as I said for ages and I never touched it for years.

Now I got a firmware update on my f6x pro and since then the currentCadence value is way to small. Indeed it seems that the value has to be doubled as well to show up correctly. Is this an intended behaviour? How can I support now older watches and newer watches at the same time?

Top Replies

All Replies

jim_m_58 over 4 years ago in reply to F3b Software (Brian)

SPORT_HIKING has has a discrepancy in cadence for 7 years. It always needs to be *2, and with SPORT_WALKING, max and avg needed to be *2, but current was fine.

The *2 is from cadence being revolutions vs steps (which makes sense on a bike)

The latest FW/VM seems to break the way it worked before, even though the way it worked before was broken.

flowstate over 4 years ago in reply to jim_m_58

F3b Software (Brian) said:
From what is written in the API below it is RPM not RPM/2.

jim_m_58 said:
The *2 is from cadence being revolutions vs steps (which makes sense on a bike)

To elaborate on all of this:

Cadence (biking) = RPM (revolutions per minute) which is equivalent to one-foot cadence
Cadence (running) = SPM (steps per minute). This is two-foot cadence. SPM = RPM * 2

Interestingly, a "good" cadence for biking is said to be 90 RPM, while a "good" cadence for running is said to be 180 SPM; these numbers are equivalent to each other.

(I'm not a cyclist so don't beat me up over the 90 RPM number. Also, I realize that the 180 SPM thing is debatable for runners.)

Personally I would expect any non-cycling cadence to be expressed as two-foot cadence, for consistency. This would mean that Garmin would be internally doubling its raw cadence readings before storing/displaying them.

jim_m_58 over 4 years ago in reply to jim_m_58

There was beta FW released for the va4 and venu today that looks to address this issue on those devices (version 6.33)