Ticket Created
over 5 years ago

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
  • Former Member
    Former Member over 5 years ago

    3.0.12.     The Simulator reports its version as 99.99.99.

    I don't know what Garmin connect thinks of the ride.   I've uploaded thousands of rides to Strava, and its analysis correlates with the published distance for the course,  the distance reported by the unit, and my wristwatch.    I'd remember riding an extra 60km in the dark.

  • Which SDK?  And how does the data compare to what you see in Garmin Connect instead of Strava?