Weird cadence behaviour when using the simulator

Hi,

I'm new to this, and I'm trying to make a small datafield which displays 4 values (one in each corner of the datafield), similar to MapDashboardMS, but within a single small datafield, not a double one).
I have the basics down, and the datafield works. Only when using the CIQ simulator the cadence values are weird.
When using the Data Simulation data source the values are normal, however when I switch to replay a fit file from my bike (exported from Garmin Connect) the cadence numbers seem to be double the value they should be.

This is the code that gets the current cadence:

if(info has :currentCadence){

if(info.currentCadence != null){

mValue3 = info.currentCadence as Number;

} else {

mValue3 = 0.0f;

}

Just plain simple.
I don't understand how the displayed value from the FIT file is double the value it actually is.

Top Replies

FlowState over 1 year ago +1 verified

I think what's happening here is:

- FIT files internally represent cadence in units of 1 RPM (revolution per minute). For cycling, this number is displayed to the end user without modification. For…

All Replies

+1 FlowState over 1 year ago

I think what's happening here is:

- FIT files internally represent cadence in units of 1 RPM (revolution per minute). For cycling, this number is displayed to the end user without modification. For running, this number has to be doubled (because Garmin uses the common definition of running cadence which is "steps per minute", and 1 "revolution" equals 2 steps.)

- For whatever reason, the simulator is applying the running algorithm when you replay a FIT file

In the simulator, did you set the sport to cycling using Menu > Simulation > Activity Select? The fact that data simulation works for you sugggests the answer might be yes, in which case this seems to be a simulator bug.

If you search for "garmin half cadence" you'll find a ton of bugs related to this inconsistency, both in Connect IQ and general Garmin functionality. My favorite one is this old bug: Bug: range of average cadence is half of the range of cadence. That was from over 7 years ago. But more recently, there's this: The classic bug half cadence/incorrect arose on fr965 again.

0 Marco over 1 year ago in reply to FlowState

Thx. I had the activity select indeed set to Cycling in the Simulator settings. Might be a weird bug then. I'll just test it on my bike computer and see what it reports.