CIQ Simulator data not from real world

Did you change the activity sport to Cycling in the simulator? (menu > Simulation > Activity Select)

Yes, nothing happened.

It is worked so-so (not perfect) till I am not stop and the activity paused IRL. After that, cadence went crazy.

But actually the whole simulator working far from the well, like I load my fit workout and see a complet different data on the simulator than I did IRL or that the fitview show me in the datas. Like the cadence start 90 but I never went over 75 till many minutes, I know how I biking and also I see in the fitviewer. The speed also too high just like everything. Something definately wrong with that when I replay a FIT or as I said using random data. 

The funny thing is, I remember when I devs last time months ago before SDK 8.x.x coming I did not remember speed, cadence etc problem. It is maybe a new, I try to found the last working SDK, but before v8 like 7.4.3 said it is too old and crashing my app.

And I do not want to put on the list that simple thing, if I emulating a bike computer why the running is the sport activity. Or why the fonts and the font positioning is different from any device. And so on, the list can be looooooong.

Someone need to take care of the CIQ simulator and rethink a bit about how it need to be working, and bugfix it.

It seems OK while my bike is paused. After that the cadence launch to the sky, like 142RPM sometime up to 180, I never ever made this quick, usually between 70-85RPM. It was ok till the pause.

I test the fit file with www.fitfileviewer.com, and the cadence is OK, 70-75RPM.

Did you change the activity sport to Cycling in the simulator? (menu > Simulation > Activity Select)

The default is Running, and for running activities, cadence data is presented differently.

Biking cadence = revolutions per minute (this is the same as the raw value in the FIT file)

Running cadence = steps per minute (this is double the raw value in the FIT file)

In running, since 1 "revolution" (or "stride") is actually 2 steps, running cadence is presented as double the underlying value. For example, if my average cadence for a run was reported as 190 spm, then the FIT file will have recorded 95 rpm.

The problem is that ActivityInfo.cadence doesn't necessarily reflect what's in the FIT file, it reflects what's displayed on the screen in the native Cadence field. And for running, this is double the FIT file value.

If you are testing your data field in a running activity, this could explain the discrepancy you are seeing. Your cycling cadence is being reported in terms of running cadence "units". Then again, you'd expect the simulator to automatically read the activity sport from the FIT file. But maybe it's not doing that.

Because the same field - ActivityInfo.cadence - is used for either cycling cadence or running cadence, it has also led to the infamous "half cadence" bug which is the opposite of what you are seeing: some CIQ apps would display half the expected cadence for running activities, because the ActivityInfo.cadence field was incorrectly reporting cadence in "cycling units" (revolutions/strides) 

To me it's kind of a strange decision for the cadence field to have different units/meaning based on the activity type. The fact that running cadence is conventionally reported as steps per minute (or 2X strides/revolutions per minute) shouldn't change the number that is in the cadence field. I understand why it was done, but it has led to recurring half cadence bugs over the years.

What makes things even more confusing is the terminology around running cadence.

In running, 1 "stride" is typically defined as a complete "revolution" meaning 2 steps. Even Garmin uses "strides" to describe the units of the FIT file cadence field, which again, is half the displayed running cadence (half the average steps per minute). And the FIT file also contains the "total strides" field, which is half the total steps. So here, Garmin agrees that 1 stride = 2 steps.

But Garmin also uses "stride length" to mean the length of 1 step.

What should've happened is everything internal, including ActivityInfo.cadence, should've been in consistent units, regardless of sport type.

If Garmin wanted an easy way for data fields to display running cadence (in steps per minute), there could've been a separate field for that.

As another example of the "running cadence is 2 times cycling cadence" rule, it's often said:

- cyclists should aim for 90 RPM (as a middle ground)

- runners should aim for 180 steps per minute

It's exactly the same target, just expressed 2 different ways (in two different units).

1) I know, but maybe not a big deal to make a bit more usable. 

2) I have explore2, there is no this kind of setting. Google said: "The Edge Explore 2 automatically uses Every Second Recording and this setting cannot be changed."
So the bug is in the simulator, not in the FIT file.

1) random data isn't the way to go as it's generating data that can be used for any sport.

2) Recoded a few of your rides on a real edge, and then copy those fit files to your machine and play them back when you want to see real data.  You probably want to set your edge for every second recording instead of "smart recording" which is the default and data is isn't recorded as often