Related
Options

Elapsed Time Incorrect

emw
over 3 years ago

Hi All.

I don't have an exact timeline as I don't always look at "Elapsed Time" however I've noticed this happen lately (when I pay attention to that stat)… the Elapsed Time didn't add up as I knew the time of day when I started our outing and when I finished and then hit save (note: I always press Start/Stop when I stop to regroup or when having a break). A most recent example (when I made sure to pay attention and take note) in summary is:

  • I started my trail run at 12:05 PM (confirmed in Garmin Connect and Strava).
  • I stopped several times for photos and at the summit (to put a jacket on and some more photos) - all times that I stopped moving I hit Stop (and Start when I began moving again).
  • I completed my loop at 12:15 PM and then hit Save.
  • When I upload to Garmin (and then Strava) the times were:
    • Time = 1:53:25 (correct)
    • Moving Time = 1:52:30 (probably correct as it was steep terrain and heavily treed in areas)
    • Elapsed Time = 1:58:46 (incorrect as it should have been 2:10 based upon the Time of Day for start at 12:05 PM and finish at 2:15 PM). Strava Flyby interestingly shows my icon disappear at the 1:58:46 mark, even though there is about 1.6 km (or about 12 minutes) of remaining track (the track is visible but my icon is not for the remaining 12 minutes).

Of note I did hit my lap button a few times but I did not let my screen timeout nor did I hit "Resume Later" and I am using the fenix 6X Pro (19.20 software). 

Thoughts?

  • 0 over 3 years ago in reply to emw
    emw said:
    PS, how do you view the FIT data in Excel?

    There is a SDK (Software Development Kit) available for FIT: https://developer.garmin.com/fit/download/
    The SDK contains documentation, C/C++ library and headers, Java classes and a couple of Java applications for exporting the complete FIT file, or part of it, to CSV. 

    This is what you need to do:

    1. Download the SDK from link above and extract it to an appropriate folder.
    2. Download the original activity data from Garmin Connect and extract the file.
    3. Using two separate Explorer windows, one with the folder containing the fit file and one with the SDK\java folder: Drag the .fit file onto FitToCSV.bat which will create a csv-file in the same folder as the fit file.
    4. Open Excel and import the csv file using the import wizard, use comma as separator.

    What you get is raw data and it requires knowledge to interpret everything. Parts of it can be found in the SDK and documentation and parts of it is only known to the device developer (like Stryd).

    There are other tools available that will help you and do some translation of raw data, problem is that I haven't found any tool that do everything correctly. They either interpret things wrong or ignore parts unknown for the developer.

  • 0 over 3 years ago in reply to TobiasLj

    thank you, it worked... now i just need to figure out what a lot of the column headers are ;)

  • 0 over 3 years ago in reply to emw
    emw said:
    now i just need to figure out what a lot of the column headers are ;)

    Yep, and that is easier said than done :-)

    FIT is a very low level format designed for the ANT/ANT+ protocol. The data from sensors are stored every second without any additional info to keep the size of data as small as possible. For sensors that has a higher sampling frequency than 1s (such as HRV data from the HR monitor and accelerometers) the data is aggregated and stored as a chunk of data every second.

    The Java application that converts from FIT to CSV do some translation of the information types but still a lot that requires knowledge to understand.

  • 0 over 3 years ago

    Yes, something is fishy with the different timers. I did not stop anywhere on todays run. And there is a difference of 13 seconds between Time/Elapsed Time vs Moving Time. 

  • 0 over 3 years ago in reply to AndersB
    AndersB said:

    And there is a difference of 13 seconds between Time/Elapsed Time vs Moving Time. 

    This kind of things usually can be attributed to limited GPS accuracy. The watch thinks you were stopped while actually you weren't. Take a close look at the pace graph. Perhaps you'll be able to identify the moment when the SNAFU happened.

    But in your case at least the math checks out, contrary to OPs case.

  • 0 over 3 years ago in reply to tmk2

    No, I cant find 13 "stopped" seconds in the Pace diagram, not in the .FIT file either. There is 6 seconds with 0 m/s in the beginning of the activity, but not 13 seconds. The 6 seconds is due to delays in the watch. I was moving from the first second.

  • 0 over 3 years ago in reply to AndersB

    Agree that the moving time algorithm may cause questions for activities where you did move all the time but for activities where you did stop for some time it seems more accurate. I don't pay much attention to the numbers since the important time for me is Time which in almost all of my activities is the same as elapsed time since I never pause.

    For what it's worth the moving time has nothing to do with the watch, it is post processing done after the activity is transferred to Garmin Connect.

    Other platforms, like Strava, do this as well. From a MTB activity lately:

    Which one is correct? Don't know and I don't care :-)

  • 0 over 3 years ago in reply to TobiasLj
    TobiasLj said:
    For what it's worth the moving time has nothing to do with the watch, it is post processing done after the activity is transferred to Garmin Connect.

    And the reason why even the ‘always correct and accurate’ Strava is no better than anything else. My 56 minute swim (stopped for only a couple of minutes) in GC was reported as 22 minutes moving time in Strava because I swim crap. There are always differences in distance and time between Strava and GC.  However, some folk would have us believe that only Strava is correct.