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

Still some issues with .tcx file processing?

Former Member over 9 years ago

I run with a Forerunner 410. About two weeks ago I encountered the problems outlined in the following forum thread -

https://forums.garmin.com/showthread.php?357331-Time-data-from-gpx-files-not-seen-by-GC

Following the notification to the thread that the site had been updated with a fix, I followed the instructions to export, delete and re-import the affected activities. As expected, that resolved the problem, and I've had many runs since where the uploaded activities displayed as expected.

However, I ran on Sunday, and the activity does not display as expected. I ran for 15.0km. I ran without pausing for the first 14.5km, then paused the watch for several minutes, and resumed for another 0.5km of running, before ending the session. The pausing activity may be relevant - I don't normally pause mid-activity, and this is the only time I've done it since the fix for that other issue went in, and the only time I've had a problem.

Here's the link - https://connect.garmin.com/modern/activity/1307131773

The pre-pause splits all show a moving-time of 0, while the split that spanned the pause shows a moving time of 2:22 (which was the post-pause duration).
The activity displays as follows - when graphing 'over distance' the elevation and heart-rate profiles are as expected, but the pace is a flatline of 1:00:00/km for the first 14.5km, and then shows the actual pace I was running for the last 0.5km (between 00:04:30/km and 00:05:00/km). The x-axis on all of those graphs correctly runs from 0-15km. When graphing over time, the x-axis only runs from 0-2:22 (rather than the 0-1:21:41 you would expect), the elevation and pace graphs are flatlines (apart from an initial brief ramp), and the heart-rate is a slowly rising straight-line.

This definitely seems like a Connect issue rather than a watch malfunction - I ran again today (without pausing) and the uploaded activity was as expected. I also uploaded the problem activity to another fitness site (not sure if I'm allowed to mention it by name, so I won't), and it displayed correctly there also. It may be related to the issue that occurred earlier this month and that seemed fixed, but I'm not sure, so I've opened a new thread in case it's different.

0 Former Member over 9 years ago

I'd also like to raise this as an issue as the same thing is happening to my runs. I also run with a Forerunner 410 and my runs aren't capturing the beginning sections of my runs when uploading to Garmin Connect. I did create my own thread before seeing this one which can be seen here:

https://forums.garmin.com/showthread.php?359120-Data-Missing-from-Garmin-Connect-(Moving-Time)

I exported, deleted, and imported to see if it resolved the issue and although I can now see the elevation data over the whole run the 'Moving Time' still has the first 3 miles as a flat line. My logged run can be viewed here:

https://connect.garmin.com/modern/activity/1309293673

0 Former Member over 9 years ago

BeOneOptica came up with a partial workaround for this issue which involved handmodifying the tcx file (see the thread he links to above for details).

In order to test out his approach, I deleted the activity I've linked to above, hand modified it, and re-imported it. You can find details of the results in my reply on his thread (EDIT: my reply on his post is at the moment awaiting moderation), but in short while it improved matters it'd didn't fully resolve them, and hand-modifying files is not a sustainable approach long-term.

The reason I'm replying on this thread also is to explain why the activity I linked to in my original posting is no longer there, since it was deleted during the above activity. For details of files that show up this problem, along with an analysis of the file elements that trigger the issue see BeOneOptica's thread.

0 RUCKERX5 over 9 years ago

My husband and I both have 410's and are experiencing the same issue described in this thread. As indicated, it appears to occur specifically when the activity has been paused mid-stream. Has Garmin acknowledged it as an issue yet? Also, I'm wondering if it's impacting devices other than 410's.

0 Former Member over 9 years ago

We appreciate the discussion on this issue and want to escalate it to the Garmin Connect team for further investigation. If possible we would like to be able to provide the team with examples of this issue. As indicated above, users have found a work around, but if there are TCX files that can be posted that would be helpful to further investigate this issue.

0 RUCKERX5 over 9 years ago

One additional trend I have noticed: The issue appears to only occur with the first occurrence of a pause during a given activity. Yesterday I rode a 20-mile bike ride with 2 breaks along the way. I paused my 410 with the upper right button at approximately mile 6, then again at approximately mile 12. The graphs and splits after mile 6 appear to be correct; however, "moving time" appears to be missing from prior to the mile 6 break. I have attached a tcx export, as well as screen prints of the Garmin Connect views that go with the export.

0 RUCKERX5 over 9 years ago

Updated with files for debugging

0 Former Member over 9 years ago

Thank you for providing the file and the screenshots. This information is being escalated to the Garmin Connect team for further investigation and resolution.

0 PAULVDMEE over 9 years ago

I think i also suffer from the same issue (if i understand the problem correctly)
I also have a garmin Forerunner 410, and I use the pause during some of my runs.
This is causing issues with Garmin Connect (suddenly) where my pace is only shown from the moment i used the pause:
https://connect.garmin.com/modern/activity/1313984300
Also the pace graph looks really weird if i select "Per distance" instead of "Per time". With the "Per Time" it only shows the time since the pause:

while when I select "per distance" i get the full distance (but a wrong graph)

If needed I can provide another run where i have the same issue.
I know the Forerunner is and old watch, but it serves me well, and still works.
Hopefully you can and will fix this issue in Garmin Connect.

0 RUCKERX5 over 9 years ago

I have briefly reviewed the GC charts and data from a friend's 8/15 run where I know she paused midway through. She has a 620 and her GC views do not appear to have this issue. This makes me think it may be specific to the 410. I am also still happy with my 410 (besides this issue) and hope it is resolved quickly.

0 Former Member over 9 years ago

I have briefly reviewed the GC charts and data from a friend's 8/15 run where I know she paused midway through. She has a 620 and her GC views do not appear to have this issue. This makes me think it may be specific to the 420. I am also still happy with my 420 (besides this issue) and hope it is resolved quickly.

I'm pretty sure the 620 exports in .fit file format. The original issue here (which seems to have been only partially fixed) was an issue with .tcx (which is what the 410 exports) and .gpx files. I'm not sure if the remaining issue applies to both .tcx and .gpx, or just to the former, but I'm not surprised the 620 is OK since .fit files were never impacted.