Eclipse Plugin 2.1.3 - no info.elapsedDistance

Hi Travis,

I actually meant for Joao to upload their FIT file, but I'm grabbing yours now to see if those work for me also, so thanks for that. Not surprised about you using multiple devices; I see people doing that all the time around Calgary, where we have a high percentage of runners in the city.

Cheers,
Dougas

The FIT file doesn't seem to be an issue - I can replicate my problem with simulated data...

I tried Travis' file, and the problem persists...

Regards,
JF

Hi Travis,

I actually meant for Joao to upload their FIT file, but I'm grabbing yours now to see if those work for me also, so thanks for that. Not surprised about you using multiple devices; I see people doing that all the time around Calgary, where we have a high percentage of runners in the city.

Cheers,
Douglas

Okay, so I'm not sure which file is which but those both work just fine for me in the simulator, giving me everything I am expecting (position, speed and altitude) except heading, which is probably because neither device has a magnetic compass. Thanks again.

I am convinced that this is an issue with something in the D2 Bravo generated FIT file that the simulator is not happy with.

Cheers,
Douglas

Both have a magnetic compass.

According to Brian's response in this post, there seems to be an issue with both the data recorded by the d2bravo and the simulator.

Travis

the problem remains on my laptop. Did you try on a Mac, or are you using Windows?

Windows. I don't have access to a Mac for testing. I know that there are others who do. Perhaps one of them would be willing to pull down the project and and try it out.

Windows. I don't have access to a Mac for testing. I know that there are others who do. Perhaps one of them would be willing to pull down the project and and try it out.

I tried using the same System.println() statement on my data field -- using Mac OS 10.11.6, SDK 2.1.3 and Eclipse plugin 2.1.4 -- and, like Travis, Joao's code works for any FIT file that isn't a FIT file generated by my D2 Bravo. I am convinced, as Travis noted, that this is related to my issue in the other thread. Furthermore, because the Tactix Bravo (with it's builtin Jumpmaster app) will also likely be recording speeds higher than the original FIT spec allows, I suspect that the Fenix 3 also records FIT files using the same enhanced fields.

We can confirm this if Joao can send me a Fenix 3 FIT file.

Cheers,
Douglas

We can confirm this if Joao can send me a Fenix 3 FIT file.

Cheers,
Douglas

See the attached file.

I just went out for a run, and my data field was working correctly - this seems to be just a simulator issue, the watch firmware is feeding the correct information.

Hope this helps,
JF

I'm playing back the .fit file from your zip, and I'm getting elapsedDistance just fine in the sim (windows), with both a watch-app and a data field. (after 20 mins, I show an elapsedDistance of 3.56 miles)

What version of the SDK are you using? IIRC, the 2.1.0 preview has a problem with elapsed distance, and it wasn't that it didn't change, but changed at something like 1/10 of what it should, so it changed very slowly. Your file appears to run at a normal speed with 2.1.3

I'm playing back the .fit file from your zip, and I'm getting elapsedDistance just fine in the sim (windows), with both a watch-app and a data field. (after 20 mins, I show an elapsedDistance of 3.56 miles)

What version of the SDK are you using? IIRC, the 2.1.0 preview has a problem with elapsed distance, and it wasn't that it didn't change, but changed at something like 1/10 of what it should, so it changed very slowly. Your file appears to run at a normal speed with 2.1.3

Thanks for trying. I think it's now proved that everything works fine in Windows, but I'm using a Mac, perhaps there's some problem in the build for this platform... Can anyone with a Mac reproduce this problem?

I'm using 2.1.3, I downloaded and installed a couple of days ago.

Regards,
JF