Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Help with corrupt fit file

Former Member
Former Member over 9 years ago
Might as well start a thread for this like they have over in the 500 forum.

I've only had my 520 for a week, and I really like it. The only issues I've had so far are that sometimes the bluetooth requires me to restart on the device to work properly, and then tonights FIT file is really corrupt so I can't load it over to strava.

The online FIT tool doesn't fix it, and then I opened it in golden cheetah. It seems the timestamps are all whacky, where it should be increasing every second, but it looks like the stamps are becoming integer overflows. The data is there, I just don't know of a way to edit all of the timestamps by just setting them as monotonically increasing seconds after they start getting corrupt in the file.

Any ideas?

  • Former Member
    0 Former Member over 8 years ago
    14h problem

    Hello,
    I think my garmin has taken a jump in the time of about 14 hours and I do not have the data of all the route of today and I would need to recover them to verify the training, is it possible to correct it? Thank you

  • Former Member
    0 Former Member over 8 years ago
    14h problem

    Hello,
    I think my garmin has taken a jump in the time of about 14 hours and I do not have the data of all the route of today and I would need to recover them to verify the training, is it possible to correct it? Thank you

  • Former Member
    0 Former Member over 8 years ago
    hi SarucaVF,

    Give this file a try.

    cheers
    Mike
  • 0 over 8 years ago
    Opal 3100

    This file will not load in Strava, and the graphs in GC are flat lines. Appreciate if someone can fix it, Strava reported bad time data.
  • Former Member
    0 Former Member over 8 years ago
    hi 2nfinite,

    Give this file a try.

    cheers
    Mike
  • 0 over 8 years ago
    Mike,

    Thanks! How did you fix it? I tried by following the Strava instructions:
    https://support.strava.com/hc/en-us/articles/216918067-Uploading-Garmin-files-with-bad-time-data

    And using Corrupt Time Fixer:
    https://www.fitfiletools.com/#/ctf#view

    The output of Corrupt Time Fixer still had a large time jump when importing into TrainingPeaks and Strava. Looking back now, it appears I did not try selecting the Normalize Time option.

    Appreciate the help!

    Brian
  • Former Member
    0 Former Member over 8 years ago
    hi Brian,

    I use the paid version of the Fit File Repair Tool - supremely capable and Mathias pumps out a lot of updates.

    cheers
    Mike
  • 0 over 8 years ago
    Hi Mike,

    I've been in the software industry for a long time, and like to support developers like Mathias, but its Windows only and I don't have a current license to run in a virtual machine on my MacBook Pro. I downloaded the Garmin FIT SDK, compiled the examples, and played around enough to know how much time it would take me to fix the file. So I'm happy to buy a Fit File Repair Tool license but not until I have another reason to buy a Win 10 license and deal with the hassle of installing/maintaining Win10.

    Curious, did you just run a single command to fix it?

    I haven't looked at the time stamps in the .fit or .tcx, however looking at the bad file in TrainingPeaks it appears at ~70% into the ride the timestamps were advanced by more than 12 hours. Seems like a simple fix, thats one reason I was surprised the fitfiletools.com site only partially fixed the file - enough to load into Strava, but with a large time jump still in the file. This is the first time I've had a bad .fit file, and first time trying to fix using fitfiletools.com. Probably user error on my part - yesterday was first hot (95 degree) ride of the year, and I was exhausted after being on my bike for 2+ hours in the heat.

    Thanks,
    Brian
  • Former Member
    0 Former Member over 8 years ago
    hi Brian,

    Imported the file - noted what errors FFRT found - selected 'Repair Timestamps' from the 'Advanced Repair Feature' tab and let FFRT resolve the issue - exported the file.

    About 5 or so mins work.

    cheers
    Mike
  • 0 over 8 years ago
    Mike,

    Thanks again, appreciate your help and explanation!

    Brian