Hi, please check values provided by Connect IQ device simulator, seems that cadence data are too high, both simulated data ( cadence of the order of 180) and n fit playback ( cadence data are not the ones stored on .fit ). Thank you !
Former Member
Hey Fabrizio67,
I checked this out in the sim. It looks like the simulated data does come up around 180 or so. I think that's correct, it's just pretty high for most folks. To ensure that the sim is actually giving the correct info based on what is being fed to it, I took a fit file from one of my own runs where I know the cadence. What I got was pretty accurate (about 156 or so most of the way through). What kind of discrepancy are you seeing on the known cadence on the fit file?
Hi Coleman.ConnectIQ , it seems that the cadence is twice that of the fit file, but i am not sure 100%, 156 for cadence ? are you sure is it normal ? My average cadence is 80, max 110 ! However, i think that the simulated data could be not more than 110
Coleman.ConnectIQ , i refer to bike cadence, not run cadence, i use currentCadence of Activity.Info object as reported by documentation, it seems refers to bike cadence, not run cadence var currentCadence; // Current cadence in revolutions per minute simulated device is edge 1000
Looking a little deeper with one of the engineers, it looks like that's a bug in our docs. The Activity.Info object is going to give you the cadence in whatever format is native to the device. For cycling that should be RPM, for running that should be SPM (steps per minute), etc. I'm getting a ticket to fix that so it doesn't cause confusion in the future. As far as what you are seeing in the simulated data, It looks like it's defaulting to running cadence numbers so I don't think that's a bug thought that might be a limitation of that tool that we want to discuss as a team. In regards to the what the sim is doing with your playback fit data, I would like to figure out what is causing the discrepancy there. Would you be willing to give us some more detail here, PM me, or email us at [email][email protected][/email] with the fit files and expected values included?
Thanks for the files. I was able to confirm with one of our engineers that the simulator is adjusting some of the fit data. I think that the original design assumed the most regular use case of a running profile. The data for cadence appears to be single leg cadence when recorded via a running profile. On a device, the CIQ virtual machine will simply display the info requested from the device which is edited natively on the device based on the fitness profile. Long story short, the device multiplies the cadence number by two to give steps per minute in a running profile so that's what our simulator does. I've created a ticket to improve this feature for both cases. A workaround for the time being is to divide the data by 2 so you have accurate info, then remove the division workaround when you compile for a device. It's not elegant, but it should work. This is one of those cases where it's clear that we provide a simulator and not a full fledged emulator for development. There are simply too many device and profile specific nuance to catch all of them. However, we do try to give you the closest idea we can to device behavior. Thank you for helping us find some things we missed!
