• State Not Answered
  • Replies 8 replies
  • Subscribers 2 subscribers
  • Views 2069 views
  • Users 0 members are here
Options
Related

Distance incorrect, but track OK

Data
over 4 years ago

(Updated this post) During an activity, distance stops updating, while the map page on the watch still correctly updates the position (blue arrow), but does no longer draw the track.

Afterwards the data in the FIT file contains correct data (GPS positions are all logged, none missing, speed, cadence, heart rate, temperature, running power etc also OK) except for the part of the activity where the distance stops updating; the same value repeats in the Distance field until the end of the activity.

Hoping to hear from others if they ever saw the same thing, just to rule out a hardware issue.

  • 0 over 4 years ago

    Sounds weird! I didn't install the beta version and I did several hikes (also tracked with Locus Maps on my phone), lots of runs (also standard courses) and cycling (with a simple bike computer in parallel) and there was no issue with the track quality and distance. So I will stay with 13.0 so far.

  • 0 over 4 years ago in reply to RunR

    Back on 13.00 now, also because of the LiveTrack not working with 13.71. Downgrade took real long, had me worried. And lost all settings and VO2Max etc. of course. Not syncing data has a price :)

    I realized later that this isn't the first time that there is a problem during a second activity that is started quite soon after stopping the first. Although those problems manifested immediately after starting activity #2, not after ~10 minutes. Spontaneous reboots, loss of GPS, loss of Bluetooth phone connection or sensors. It's been that way since I own the watch. Somehow I suspect the watch itself, it was bought used, who knows what it has been through or why the first owner sold it.

    A workaround would be to use Change Sport instead of stopping and starting the individual activities. Guess I'll do that and hope the Fenix 5Plus lasts a good few more years!

  • 0 over 4 years ago

    This happens with FW 13.72 as well. A few GPS data points are missing (Lon 0, Lat 0) and after that distance is not updated anymore.

  • 0 over 4 years ago in reply to Data

    I regulary run from work to the subway, take the train (30min) and then start a second run home. So far I never had issues with a Fenix 1, Fenix 3 and Fenix 5 Plus, the distances are consistent and ant+ sensors (tempe, footpod, HRM) work fine. My last competition with warm-up and race in seperate activities (with ~10min in between) is a year ago (also without issues).

  • 0 over 4 years ago in reply to RunR

    I have never seen this before with the 5 Plus, or with other devices. It happens only with the last two betas, that's why I guess it might be related to SW 13.71 and 13.72. My Fenix 1 does just fine on the same activities. What software level is on your 5 Plus?

  • 0 over 4 years ago in reply to Data

    As mentioned earlier in this thread, I have still 13.0. And I will keep that as long as you describe such weird issues!

  • 0 over 4 years ago

    FWIW - it's probably not due to the beta's, but what I do.

    Steps to reproduce: End a run and save it (probably both optional). Start a Walk activity. Go (hotkey) to the widget loop. Do some things like: reviewing a run, recalibrating the altimeter, reading notifications. Return to the Walk activity.

    After returning to the Walk activity the watch will show alerts:  'GPS found', 'RD Pod / Foot Pod / Tempe connected'. Often, distance is no longer updated from there on.

    The FIT file will have some Record messages without GPS positions from the point where the widget loop was entered until it's back in the Walk activity.

    It's certainly a weird use case, and I'm not sure this kind of usage is even supported, but I've done this the same way with a Forerunner 935 and that just always kept tracking distance without issues.

  • 0 over 4 years ago

    Is there anyone else who has seen this issue?

    Activity starts normally, GPS reception OK (according to GPS datafield). At some point the track is no longer drawn on the map screen. The position on the map is still accurately displayed, just no track.

    The FIT file contains accurate GPS data (no missing data) so the track is displayed just fine. Only the Distance data is missing for a part of the activity, so the overall distance (and average speed) is incorrect. Altitude is stuck on the same value for the same part as the missing distance.

    Today was the first time I've experienced this during a Bike activity. Settings were: GPS+Galileo, 1-second recording, ANT+ speed and cadence sensors, Tempe, using built-in OHR, no third-party datafields, apps or watchface, FW 14.00 (but have seen this issue since 13.71).

    Nothing special at the point where distance stopped updating, no buttons pressed, no pauses, no auto-lap, I was just pedaling along at a steady speed.

    Please let me know if you have seen the same (i.e. correct track, no missing GPS data, incorrect distance) because I want to rule out it is a hardware issue with my watch.