Garmin Enduro "Resume Later" feature breaks the FIT synch?

I've been having trouble with My Garmin Enduro sometimes not synching activities and I have narrowed it down to my use of the "Resume later" feature.

I often go on long rides, and use the Resume later feature when I'm stopped for coffee / lunch etc. When I synch it later, it does not appear in my Garmin activities list and is greyed out on my watch in the previous activities list. If i try to import manually into Garmin Connect i get the error "One of your files was not accepted by the system. Please contact Support for assistance."  If I use an external fit repair website it works and i can successfully import into connect.

Using the website http://www.rainorshine.bike i've been able to load in the FIT and view it and sure enough, at the time when I used "Resume later" i find

latitude, longitude, heartRate, distance, grade, temperature, timestamp, 

-27.46849120594561, 153.08883662335575, 105, 51.20226906539, NaN, 84.2, 21345,
-27.468480141833425, 153.08882765471935, 104, 51.20319490818, NaN, 84.2, 21348,
-27.468470418825746, 153.0888219550252, 106, 51.20391569854, NaN, 84.2, 21356,
179.99999991618097, 179.99999991618097, 109, 51.20391569854, NaN, 84.2, 21385,
179.99999991618097, 179.99999991618097, 112, 51.20391569854, NaN, 84.2, 21388,
-27.468709386885166, 153.08950667269528, 88, 51.20454949696, NaN, 89.6, 25831,
-27.468699663877487, 153.08950927108526, 88, 51.20522679135001, NaN, 89.6, 25832,
-27.46867150068283, 153.08951346203685, 87, 51.20684235595, NaN, 89.6, 25836,
-27.46864853426814, 153.08948596939445, 90, 51.209184924620004, NaN, 89.6, 25841,

(see the 2 rows with lat long both 179.999) - you can also see that the time stamp jumps around this time.

also when I view the FIT in this website I get

which kind of confirms that something is going wrong with lat /long

I've noticed this happens a few times during my activity - which might just be the default when I am out of GPS range because under cover etc. But, is this causing connect to fail to import the activity? is it the 180,180 lat/long or is it the jump in time stamp that is causing the synch error.

I'm attaching the .FIT file in case any smart person can help debug why I'm getting these errors.  https://www.dropbox.com/s/2oqnlasqdkfmmf5/2022-02-06-07-27-01.fit?dl=0

Steve

  • telling people that you MUST get a GPS fix before starting an activity is simply incorrect.

    So me, and I'm guessing most other users of Garmin GPS watches are wrong to wait before getting a good GPS signal then? 

    It's a very handy feature when you're at the start line of a city marathon and can't get good GPS fix.... you just start the race. Otherwise, there would be many people crowding at the start line waiting for a GPS fix

    That doesn't happen because I expect that virtually all competitors will have started their watch in plenty of time to get a good fix before pressing start when the race begins. That, after all is largely the reason behind the Power Save Timeout setting in the Settings for each activity - to allow the watch a longer period of time before timing out and reverting back to the watch face, allowing users plenty of time to get a good GPS signal before starting.

    Perhaps you would humour me and try ensuring you have a GPS fix before you start an activity and again before restarting an activity after Resume Later and see what that does to your .fit file. 

  • To humour you, I did indeed go for a run this morning, waited for a GPS fix and ran for an hour or so, and when I finished the activity (forgot to use resume feature), the watch crashed at save, displayed the Garmin triangle of death and reset. As expected, the activity would not synch and displayed in grey on the watch history. I downloaded the FIT to my laptop, and imported it into garmin connect webpage to get the usual "One of your files was not accepted by the system. Please contact Support for assistance." I then ran it through www.fitfiletools.com section remover and tried again and as expected it uploaded perfectly (except it saves it as event type "other" rather than "running". 

    So, I learnt 2 things: 1) It's not related to resume later function after all. My enduro just created 'bad' FIT files sometimes.

    2) It really doesn't matter if you have a good gps fix at the start or not.

    Interestingly, I have now downloaded software called "FitFileExplorer" where I can view the FIT. The absolute ONLY thing I can see different between the original FIT that won't load into Garmin Connect and the FitFileTools version is fit file tools has added 2 sections to the repaired FIT.

    "session" - which includes start time, start location, total distance, etc.

    and "activity" - which is a timestamp and "num_sessions = 1". 

    Neither of these exist in the previous "repaired" FIT that I did, so probably not relevant.

    There doesn't seem to be anything else different between the 2 files.

    I'm guessing that whatever is invalid in the FIT does not display in the app FitFileExplorer.

    So, I'm none the wiser. Except, I am going to contact my local garmin customer support and request a replacement.

    For those following, here is the original ("BAD") FIT: https://www.dropbox.com/s/5odo5yqvd00bsq8/2022-02-10-08-07-32.fit?dl=0

    An the "good" repaired FIT: https://www.dropbox.com/s/bqqc9f8q9ev474i/2022_02_10_08_07_32%20fitfiletools-5.fit?dl=0