Related
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

Lactate Threshold bug in GC

kalamarios
Hi there. Today my FR630 detected a new Lactate Threshold (7:03/mi 162bpm) but once it got uploaded to GC it shows up as (1:58/mi 162bpm) which screws up the whole plot. Is there a way to remove the measurement without removing the run which is otherwise fine? I am attaching the LT plot as shown at GC to see what I mean:
  • 0
    I bought my fenix3 three weeks ago and seen this problem since my first activity upload on Garmin Connect: reasonable T-pace on the Fenix (4:23/km), much faster pace shown on the plot in the web application (1:13/km), even faster value shown beside the plot as most recent (0:08/km).
    I noticed that the values in the plot always seem off by a multiplicative factor 3.6, like somewhere a speed is given in km/h but then interpreted in m/s...
    It's just a "curiosity", but I hope this can help someone at Garmin to find and fix the bug, since the same factor 3.6 seems to apply also to the other people who reported their wrong values in this thread. No clue instead for the ~30 times faster pace given in the summary!

    Fenix 3, version v7.0
  • 0
    In fact, my (most recent) value shown by connect is Exactly 36 times Fenix 3 recorded value... (Trail running, 0:09 / 5:14)
  • 0
    Same issue - Fenix 3 Ver 7.0

    I've got a pace of 0:13/Mile - screws the graphs and invalidates the tool from a trend and current measurement perspective.

    Could you fix this please?

    Thanks

    Matt
  • Former Member
    0 Former Member
    The Connect team is still working on correcting this issue. We apologize for the delay and any inconvenience.
  • 0
    The Connect team is still working on correcting this issue. We apologize for the delay and any inconvenience.


    Thanks for the update GFM1011.

    Do you happen to know what sort of resolution are they seeking? Meaning are we going to lose the erroneous entries (deleted) or will they be restored to the values we saw on the device itself (735xt in my case)?
  • Former Member
    0 Former Member
    Note: the issue persists with activities created on a Fenix 3 running the new public release 7.20 (as expected, sounds like it is a pure connect website problem, Lactate Threshold data on watch is fine).
  • 0
    A whole month spent, and still nothing... :mad:


    Not sure how Garmin prioritize things, but I guess having individual tickets opened instead of just relying on this forum might help push things forward...? :cool:
  • 0
    Wrong display of data in pace/lactate thereshold

    I have the same problem.
    Does Garmin have already a solution for this bug?
  • 0
    Maybe later... One day, perhaps... :rolleyes:
  • Former Member
    0 Former Member
    =(

    I have the same problem.