ConnectIQ simulator on Mac - still no elapsedDistance

Hi,

A few months ago, I reported that the simulator was not providing any info.elapsedDistance when reading through my .FIT files.

I upgraded everything to:

-Eclipse Neon 4.6.1
-Connect IQ IDE 2.2.1
-Connect IQ SDK 2.1.5
-Running on Mac OS X 10.9.5

I simplified my program (a data field) to:

function compute(info) {

    System.println(info.elapsedDistance );

    return;

}

When I run the program on the simulator, I get "null" until I load a .FIT file (recorded on my Fenix 3 watch), and press the start button. After that, I always get "0.000000" as the elapsed distance. This was not the behaviour in the past (SDK 1.x.x), which correctly set the original recorded elapsed distance.

The program works in my watch, but not on the simulator.

Can anyone try the same in a Mac environment? I think there's something wrong with the SDK build for this OS...

Thanks in advance,
João Fonseca

Former Member over 9 years ago

I remember your post from before and doing some work on it. Unfortunately, I can't find the ticket where we did the work which is perhaps why you are still having this issue. I apologize. I have created a new ticket with the information in this thread and linked the old thread as well to get a full picture of the issue. Thank you.

-Coleman

joao_g_fonseca over 9 years ago

I remember your post from before and doing some work on it. Unfortunately, I can't find the ticket where we did the work which is perhaps why you are still having this issue. I apologize. I have created a new ticket with the information in this thread and linked the old thread as well to get a full picture of the issue. Thank you.

-Coleman

Thank you. When you work on the issue, let me know if you need me to test anything on my side, I'll be glad to help.

As a side note, perhaps you should consider making your bug tracking system public. This would keep the community informed about known issues, and would allow you to get more feedback from everyone.

Regards,
JF

Former Member over 9 years ago

Unfortunately we won't have a public facing bug tracking system. However, We have recently added a Known Issues thread to the forum (though sparse at the moment) that will continue to be beefed up and updated as we go along. As of right now it only contains the biggest fires, but will hopefully be fleshed out in a more satisfactory way as time allows.

Thanks again!

Former Member over 9 years ago

I'm still unable to reproduce this issue. I've used simulated data and played back fit files from multiple devices. The only difference I'm seeing at this point is that I'm on Sierra now. When you updated the SDK did you try importing the project again? I'm wondering if there is an issue with the project file. You could always send us the project file at [email][email protected][/email] and we would be happy to test it out.

Thanks,
Coleman

joao_g_fonseca over 9 years ago

You could always send us the project file at [email][email protected][/email] and we would be happy to test it out.

Hi, I just sent you an email with a project that reproduces the problem on my mac, and a .FIT file. Hope this helps.

Thank you,
JF

Former Member over 9 years ago

JF,

Thank you for the email with the information and your fit file. We have found that there is a limitation specific to the Mac Sim that is feeding the sim a [0,0] value at before the timer is started. If you Simulate the data, then start the timer, the distance values will work correctly. If you do the steps in the reverse order it will display the 0.00 value that you have experienced. We do have a ticket open to address this.

Thank you for your help and patience!
Coleman

MOMOTM over 9 years ago

I have the same problem

Hi!

Is this resolved? I m still having this problem. I m trying to simulate a .FIT file where speed was recorded via Garmin Footpod. I can see only 0.00000 as a distance reading in println(info.elapsedDistance). And I did press Start button on simulation screen.

jim_m_58 over 9 years ago

It's also on Windows. I did this bug report about that about a month back with 2.2.4

https://forums.garmin.com/showthread.php?371390-elapsedDistance-incorrect-when-playing-back-a-fit-in-the-sim

For me, it did show a distance, but it was changing very slowly. For a 2 mile recording, it showed .65 miles for example. I'm playing back that same .fit right now with 2.2.5. (I see Coleman posted it's still in backlog, but my test with 2.2.5 also verifies that it's not fixed :) )

Former Member over 9 years ago

Jim is correct. This bug is being tracked, but we are currently backlogged on some of our bug tickets. My home is that this will be prioritized up soon.

Thanks,
-Coleman

Travis.ConnectIQ over 8 years ago

I'm currently working in the code that deals with simulated and parsed fit file data, this had a chance to debug into this.

The problem in this case is that the FIT file doesn't have any GPS data in it. The current simulator code reads the GPS position data from the file and uses that to determine distance, and that breaks down in this particular case. I've re-opened the original bug report and will *try* to make a fix as part of another bug I'm fixing in the same area.