Elapsed distance on simulator

Hi,

My development environment is:
- Mac OS X 10.11.6
- Eclipse Neon 4.6.2
- Connect IQ IDE 2.2.3
- Connect IQ SDK 2.2.3

I get incorrect value as elapsed distance when I run the program on simulator and playing back from the .FIT file.

I tried two .FIT files.
The one was recorded by my Edge520.
In this case, the elapsed distance is not zero, but it is different from the activity when I recorded it.

The other downloaded from this URL.(https://developer.garmin.com/downloads/connect-api/sample_file.fit)
In this case, the elapsed distance is always zero.

I referred to this thread.(https://forums.garmin.com/showthread.php?364836-ConnectIQ-simulator-on-Mac-still-no-elapsedDistance&highlight=elapsed+distance+simulator)
And, as written in it, I tried to start the timer after playing the data, but it did not work properly.

Is there anyone who has any information?

Sorry about my poor English.
Thank you.

Former Member over 7 years ago

A while back the simulator was updated to behave more like devices. You must start a recording via the menu or by pressing the start button on the device before distance will accumulate.

jim_m_58 over 7 years ago

Brian - I'm been using simulated data most of the time, but just did a test with a couple of .fit files I have (one is right about 2 miles, the other is a 5k - about 3 miles, both recorded with smart recording), and for example, the 2 mile one shows 0.64 miles. I put together a slightly modified version of the RecordingSample (basically just to display the distance) and I'll do a bug report and email in the .fit files I'm using.

fuu_yass over 7 years ago

Thank you for checking operation and posting the bug report.
I'll keep watching the trends of that report.

Regard.

Former Member over 7 years ago

Sorry, I misread the original post. I missed the "not" in "the distance is not zero"

There is an issue in the simulator that we could not resolve with distance calculation that (IIRC) causes it to calculate all distance in the E/W direction to be calculated as if it were at the equator. However, this should cause it to over estimate distances, so it does not seem like this report can be attributed to that. We will investigate long at this using Jim's report.

fuu_yass over 7 years ago

Thank you very much for investigating.
By the way, even in my case it became shorter than the actual distance just like a Jim.
I hope this bug to be fixed.

camillo.vezzoli over 7 years ago

I am also having the issue, I recorded a short fit file for development purposes. The ride is 350 meters long. When used in the simulator, the total elapsed distance is 150 meters.

It's basically impossible to develop features that rely on distance, the only way to develop is write code, upload on the device, go out for a ride, take note of data, get back to the office and *hopefully* amend the code... not efficient!!

djhawley over 7 years ago

Sorry if somebody has already pointed this out, but I believe I'm having the same issue.

I've established it seems to be doing the distance in feet rather than metres. (i'm using the simple data field sample)

at 6:46 my activity is at 1600m (0.99 miles)

The displayed distance is 0.31 miles

0.31 * (3.28084 feet in a meter) = 1.0 miles.

Is this a simulator bug or something that needs to be taken into account on a device too as to whether they're using imperial or metric?