Ticket Created
over 5 years ago

WERETECH-7759

Simulator doesn't report correct elapsed distance or run in real time when playing back a .fit file.

I'm testing a data field that calculates a metric based upon elapsed distance versus elapsed Time.    I've tested this data field on the road, and I'm reasonably certain its working correctly.

For validation purposes, I've got it printing elapsed time and distance to the console.

My testing isn't working because the simulator is mis-reporting the elapsed distance, and not running in real time.

I'm using a .fit file from one of my own rides: 307.83km, 12:21 moving time, 13:34 elapsed time ( as reported by Strava)

When run in the simulator, the console log reports 370km, in an elapsed time of 22 hours.   The console log contains 44k log lines, or 12.1h of entries at 1 per second.

I'm running the simulator on a dedicated machine (a mac) that doesn't sleep.  It consumes about 30% of a CPU.

Former Member
Former Member
  • over 5 years ago in reply to Apollo_18

    btw: If I let the simulator run for 1 km. stop, and then upload the FIT output file from the simulator to my Garmin account. Then that output FIT file shows up wrong. I.e. the 1 km track is clearly visually much shorter than the first 1 km lap in my actual run. So, something is not working right.

  • over 5 years ago in reply to jim_m_58

    I have tried with both smart and 1 sec recording, both are wrong

  • over 5 years ago in reply to Apollo_18

    When you recorded the .fit, did you use 1 second or smart recording?  Smart is the default, but 1 sec would be better for this.  The reason being is the app on the watch always sees 1 sec data even when using smart recording, while in the fit with "smart" the times aren't consistent.

  • over 5 years ago

    I am working on a Pacer app, and also use elapsed time and distance in the simulator using own FIT files from my fr645. And the distance is clearly not correct in the simulator. But when I use my app on the road, it wotks just fine. But not in simulator!

  • Former Member
    Former Member over 5 years ago in reply to jim_m_58

    Maybe it hasn't been updated on the mac.   The machine where I found the issue also reports 3.0.0, and I did the install about two weeks ago.