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
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
    Incorrect time on file

    Hi all,

    This file would not upload to strava, so used the online tool to fix the time data, and it uploaded but it said that one of my stops was for approx 24 hours - not the 15 minutes it was. Would have put me into the future or something. Ride was on Jan 15th.

    thanks kindly

    Richard
  • Former Member
    0 Former Member over 8 years ago
    Hello Richard,

    At 115kms the 520 lost satellite lock for 7 minutes and corrupted the timestamps. Also there are 310 Stop/Start events and many of them are only 1-5 seconds apart. That is an indication that the speed/cadence sensor needs adjustment or battery or something. Fixed with the Fit File Repair Tool.

    https://www.dropbox.com/s/cnajg9p6ik8p6m2/2017-01-15-06-16-25-fixed.fit?dl=0
  • Former Member
    0 Former Member over 8 years ago
    Thanks mate - will look into the cadence stuff.

    Hello Richard,

    At 115kms the 520 lost satellite lock for 7 minutes and corrupted the timestamps. Also there are 310 Stop/Start events and many of them are only 1-5 seconds apart. That is an indication that the speed/cadence sensor needs adjustment or battery or something. Fixed with the Fit File Repair Tool.

    https://www.dropbox.com/s/cnajg9p6ik8p6m2/2017-01-15-06-16-25-fixed.fit?dl=0
  • Former Member
    0 Former Member over 8 years ago
    Corrupt FIT repair

    Hello There,

    I did a long ride today and, as seems to be usual for my 520, it choked on it when I switched it off. I stopped the activity and saved it as usual, but it still ended up with a corrupt file. Interestingly, Strava warned me about it when I uploaded it, but it ended up uploading just fine. So I suppose that they have a sort of built-in repair tool. I tried uploading to Garmin Connect, WKO+, and VeloPro with no luck.

    Is there a fix for this file? I tried to attach it, but got the message "exceeds your quota by 414mb." Only Garmin would refuse their own files. :mad:

    Thanks,

    Ak
  • Former Member
    0 Former Member over 8 years ago
    Error Log file attached

    Hello There,

    I did a long ride today and, as seems to be usual for my 520, it choked on it when I switched it off. I stopped the activity and saved it as usual, but it still ended up with a corrupt file. Interestingly, Strava warned me about it when I uploaded it, but it ended up uploading just fine. So I suppose that they have a sort of built-in repair tool. I tried uploading to Garmin Connect, WKO+, and VeloPro with no luck.

    Is there a fix for this file? I tried to attach it, but got the message "exceeds your quota by 414mb." Only Garmin would refuse their own files. :mad:

    Thanks,

    Ak


  • Former Member
    0 Former Member over 8 years ago
    Here is the error log

    Error log attached.
  • Former Member
    0 Former Member over 8 years ago
    Time problem?

    Hi,

    Can anybody help me? This is the first time I've had any problems with my edge 520 and it not downloading an activity properly.

    The attached file gets uploaded to Garmin Connect and the mapped route, time, distance, average speed, elevation gain, calories and average temp are all logged correctly. But then underneath where all the in depth information is, the information is all over the place. The time bar along the bottom seems to increase by 130 Hrs every time? Can anybody help me and explain why it would do this and how to prevent it happening in the future and maybe even help repair the file?

    It doesn't sync with Strava either probably because of the reason above. I tried to repair it using a tool online and it does this but deletes the second half of my ride.

    Any help would be appreciated.
  • Former Member
    0 Former Member over 8 years ago
    Hi Johno,

    It looks like your 520 lost GPS lock 20min48sec into your ride for not quite a minute. This caused your timestamps to jump forward to April 2019. Luckily an easy fix with FFRT.

    Give this file a try.

    cheers
    Mike
  • Former Member
    0 Former Member over 8 years ago
    Thanks Mike that's worked a treat. Seemed to have lost the signal from when I stopped to chat to other riders. Could this have had something to do with it?
  • Former Member
    0 Former Member over 8 years ago
    Hi Johno,

    Would hazard a guess it would depend on what was around you when you stopped? Anything like power lines or an airport navigational device? A tall building that might have 'screened' the horizon?