Bad Multisport File?

Weird fit file recording with my 945 LTE today on a Sprint Tri.

Strava Received a file and showed:

  • Swim
  • T1
  • Bike
  • Other (maybe T2 + Run)

Looking at Garmin Connect it seems like I may have not pressed the lap button properly when starting the run, which may make the above correct / clear.

However... somehow the last "Other" on Strava showed the full race distance (16 miles) but had a GPS plot and time for T2+Run distance.  The distance error caused it to think I covered 16 miles in only 20 or so minutes which instantly flagged it if I classified it as a Run.

I ended up playing with FitFileTools.com to eventually get my Swim/Bike/Run activities loaded to Strava, but it was a battle given that Strava wanted to consider them as duplicates each time I tried to crop  file and load it - a bit of a mess.

I want to claim fully user error missing the lap button, but the weird distance/time makes me wonder if there's some additional other fit file problem here?

I also notice the bike it synced to strava shows 1.28 miles in nearly 38 minutes, but the GPS track looks correct.  I think Strava can fix the distance per GPS coordinates, but... huh?

At least the watch not auto-lapping on the run now makes sense (I was likely in T2 :) )  Clearly I don't look at the watch much while racing.

  • it seems like I may have not pressed the lap button properly when starting the run

    Wrong button presses during a multisport activity are common, but can be fixed using software such as Fit File Repair ToolAttach it to this thread. We can take a look to see if the adjustments can be made to fit with reality.

    • Zip the file, then in a reply post Insert >> Image/video/file >> click Upload >> browse for file >> OK.
    • Or upload the fit file to a file sharing service, such as OneDriveGoogle DriveDropbox, etc., then share a link to the file in your post.
  • Thanks for reaching out.  Let me see if I can attach it here.

    I'm most curious if the 945 LTE is doing something weird beyond my button press mishap as I think I have somewhat recovered my activities (I had an Edge 530 for the bike portion and tried to strip out pieces from the full file from fitfiletools.com tools).

    B6K60825.zip

  • Looking at Garmin Connect

    How did you get this on Garmin Connect? The file you attached won't upload. Is the file straight from your 945, unchanged?

    Looking at your file with Fit File Repair Tool there was one timestamp with distance values not in ascending order, which would prevent Garmin Connect from accepting the upload. This I fixed with FFRT's "Recalculate Distance Values based on GPS Distance Values."

    Beyond that, the speed and distance values are all on "Sessions 5"

    Could you let me know what the elapsed time should be for each session?

    This is the fixed file without adjusting the wrong button presses - B6K60825-fixed.fit

  • Interesting.  Sorry for the possible error here - the file I uploaded to the post was pulled from the watch this morning after I had re-downloaded HR from my HRM Tri as the HR data that shows on GC (from the auto-sync over BLE) had wrist HR for the swim which was clearly way off.  The initial HRM Tri download seemed to struggle before I saved the activity so I decided I'd sync it later.

    Here is a file from GC exported as "original file" in case you want to see if it has errors too. Orig_ACTIVITY.zip

    Total times according to race results...

    • Swim: 13:53
    • T1: 1:39
    • Bike: 36:58
    • T2: 0:58
    • Run: 20:04

    Really if the last split just needs to be merged out you could probably guess ~20 seconds after pace went from near 0 to running.

    In between all of this Support had asked to swap out my watch due to a handful of other minor SW bugs I had reported.  The race was on my original watch and I cloned the file over to the new one so maybe did something weird here too.  Unrelated, but I think the new watch shows or likely shows all the same "issue" (but as I said, very minor issues I just wanted them to be aware of to clean up when they get a chance).