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

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:
  • As my problem isnt fixed yet, can we post our device and firmware so we can get some clue what is causing the problem?

    I have a fenix3 on 7.0 firmware
    (GC says i have 7.7.0 firmware, this is causing a problem with elevation corrections already, maybe it has to do woth this too)
  • Garmin connect still displaying wrong pace in graph

    Garmin - are you stil busy working on the bug in the display? I notice my lactate threshold speed is indicated on Garmin Connect as 1min34sec per km - wish I could run that fast!
  • Former Member
    0 Former Member
    - Elevation correction always enabled / Fenix not correctly recognized since April 18.
    - Lactate treshold graph defective since May 11.

    Meanwhile, I highly doubt anyone is busy fixing this GC bugs. :( It's hard to understand why such stupid mistakes remain for weeks and months.
  • Former Member
    0 Former Member
    Garmin - are you stil busy working on the bug in the display? I notice my lactate threshold speed is indicated on Garmin Connect as 1min34sec per km - wish I could run that fast!


    mine is 12 sec/mile which is equivalent to 300 miles/hour!
  • Former Member
    0 Former Member
    My and my husband are having the same issue. Now I can't see my gradual (but steady) improvement in threshold pace :(
  • Man this is getting really annoying!

    This is one of those "high end" features that the 630 and 735 are supposed to add to the mix to justify the premium pricing and now we can't even see our progression.

    My 735 just posted a new auto-calculated LT of 161 bpm and 2:03 min/mi!
  • Former Member
    0 Former Member
    mine is 12 sec/mile which is equivalent to 300 miles/hour!


    If you just run a little bit faster, you could hear a sonic boom :D
  • A whole month spent, and still nothing... :mad:
  • Former Member
    0 Former Member
    Same problem with my Garmin Connect. My FR630 shows correctly.
  • same here

    Fenix 3, software v.7.0