Over 31.000 km in 1 day. I knew i'm the bad ass in MTB, but i didn't know how much - Fenix 6x PRO

Hi,

Yesterday I went mtb biking. After about 50 km, my watch went completly crazy for a while. There were no trees, it was an open space. For a moment I "felt down" over 500 m under the ground and... my distance increased to over 31.000 km (there is a graph: GRAPH). Yeah, great job. I think, the yellow TDF t-shirt will be mine.

Dear Garmin, in this case, I see 3 options:
1. you can sponsor me, as the greatest cyclist in the world ;).
2. you can tell me the truth, I'm a looser, and my fenix 6x pro is... :(.
3. You can explain me, what's the problem.

My watch: Fenix 6x pro
FW: 16.7
GPS+Gallileo

Top Replies

Garmin - Chris over 3 years ago in reply to mountain bear +2 verified

Looking at your activity, your choice of using the word crazy, covers whatever happened to your watch during the activity. The .FIT file saved for that activity, I am surprised it even successfully synced…

All Replies

0 eivinnh over 3 years ago

3D distance could make issues like this if there is bad GPS reception. GPS altitude might fluctuate and add to the distance.

0 Dr Phil over 3 years ago

Post a link to the activity.

0 mountain bear over 3 years ago in reply to eivinnh

Eivinnh, there were a few slight unnatural peaks in height, and that's one, short and very large. In this "jump", fenix showed me that I am at -500m (total about 700). The total ascent was about 7700 m, but it would not increase the distance to over 31,000 km anyway.

0 mountain bear over 3 years ago in reply to Dr Phil

connect.garmin.com/.../7109964405

0 Ɛpsilon over 3 years ago

Looking at the elevation graph, I bet the fit file got corrupted at the beginning. Note the difference plotting it over distance then to time. A huge amount of data got added at superluminal speed it seems! There's a huge amount of data WAY before you started the activity. What happens if you trim the first ~10-30 sec's off?

0 Dr Phil over 3 years ago in reply to mountain bear

Hmm. Without parsing the .fit file it's hard to see what happened. On occasion a GPS point has been saved at long/lat 0/0 which is somewhere off the African coast. Hopefully this is a one off (and these things do happen occasionally with most things technical). Do another activity and see what happens.

Did you ensure you had a good GPS signal before starting?

0 mountain bear over 3 years ago in reply to Ɛpsilon

It doesn't work. Everything was ok, up to 50 km. So, as I expected, cutting the beginning did not help :(. I spoke to garmin support. They offered to replace the watch.

0 mountain bear over 3 years ago in reply to Dr Phil

I had a good gps signal (gps + gal) throughout the activity and when the watch went crazy the signal was very good for sure (it was flat, no trees, perfect weather.

+1 Garmin - Chris over 3 years ago in reply to mountain bear

Looking at your activity, your choice of using the word crazy, covers whatever happened to your watch during the activity. The .FIT file saved for that activity, I am surprised it even successfully synced to Garmin Connect given the information on it. Hopefully, this will be a one-off scenario for your watch. If a pattern should develop, please do not hesitate to reach out to your region's Product Support.

0 subra over 3 years ago

mountain bear said:
There were no trees, it was an open space.

mountain bear said:
I had a good gps signal (gps + gal) throughout the activity and when the watch went crazy the signal was very good for sure (it was flat, no trees, perfect weather.

But your trace is near a lake. May be it's a reflexion of the GPS signal from the water surface, e.g. multipath.