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

Why do all my workouts show up as "Low Aerobic"?

Do I have a setting wrong? I'm not the strongest rider, but I wondering if I can even use Garmin Connect as a training guide.

In the last month, including today, it shows that all workouts are "Low Aerobic". (All Green bars, no purple (Anaerobic) or orange (High Aerobic). Average heartrate was 150 today.

I did 23 or so intervals well above my FTP (208). How does that count as Low Aerobic? And the "Load Focus" page has: Anaerobic: 14, High Aerobic: 0, Low Aerobic: 895.

I'm hoping that I just have some zones set wrong or something? All the documentation I could find said that the Anaerobic as high power (for me) for short (< 2 min) intervals. All intervals today were between 60 and 90 seconds.

Thanks,

Karl

  • Former Member
    0 Former Member over 4 years ago

    hi Karl,

    I'm hoping that I just have some zones set wrong or something?

    and your zones are ? and the device used is ?

    upload one of your fit files from the activity here fit2tcx runalyze (you can save the link and page for later use)

    and search at the end for "NUMBER=216"

    you see your zones at line xxx6

    = TYPE=5 NUMBER=216
    --- xxx253=963163363=963163363
    --- xxx2=527546=527546,2084311,483005,463990,77999,54001,0 (time in zones)
    --- xxx0=18=18
    --- xxx1=0=0
    --- xxx6=106=106,130,145,155,163,185 (zones)
    --- xxx10=3=3
    --- xxx11=185=185
    --- xxx12=55=55
    --- xxx13=163=163

    happy & safe sporting

  • I have a Garmin 830.

    Heart Zones (and my max heart rate is about 181):

    • Zone 5: > 185 (never getting there)
    • Zone 4: 166-185 bpm 
    • Zone 3: 145-165 bpm
    • Zone 2: 124-144 bpm
    • Zone 1: 104-123 bpm

    And for Power: (Shows my FTP setting is 210 w)

    • Zone 7: > 314 w
    • Zone 6: 252-314 w
    • Zone 5: 221-251 w
    • Zone 4: 189-220 w
    • Zone 3: 158-188 w
    • Zone 2: 116-157 w
    • Zone 1: 53-115 w

    From Fit file:

    = TYPE=7 NUMBER=216
    --- xxx253=963274681=963274681
    --- xxx2=71012=71012,353735,803998,2310998,511000,0,0
    --- xxx5=698791=698791,1200936,602002,128995,731984,559027,124007,5001,0,0
    --- xxx9=53=53,116,158,189,221,252,315,4000,65535,65535
    --- xxx0=18=18
    --- xxx1=0=0
    --- xxx15=210=210
    --- xxx6=104=104,124,145,166,186,207
    --- xxx10=1=1
    --- xxx11=207=207
    --- xxx12=0=0
    --- xxx13=0=0
    --- xxx14=1=1

    It seemed to work fine last season. Did a software update wipe something out?
  • Former Member
    0 Former Member over 4 years ago in reply to KSZachry

    hi, thank you for the feedback Thumbsup

    xxx11=207 is your max hr in the fit file

    you can upload one of your previous correct fit files so you can see if the settings were different before

    check and sync your hr zones on all Garmin platforms, starting with Garmin Connect Web

    = TYPE=7 NUMBER=216
    --- xxx253=963274681=963274681
    --- xxx2=71012=71012,353735,803998,2310998,511000,0,0
    --- xxx5=698791=698791,1200936,602002,128995,731984,559027,124007,5001,0,0
    --- xxx9=53=53,116,158,189,221,252,315,4000,65535,65535
    --- xxx0=18=18
    --- xxx1=0=0
    --- xxx15=210=210
    --- xxx6=104=104,124,145,166,186,207
    --- xxx10=1=1
    --- xxx11=207=207 (your max hr setting) is it on auto ?
    --- xxx12=0=0
    --- xxx13=0=0
    --- xxx14=1=1

    happy & safe sporting

  • Thanks so much. I think I have that it set now... But for my understanding:

    • Auto detect was on. Occasionally when I pass powerlines it has strange readings. I've turned that off. So that was probably what lead to all these issues.
    • It will only apply going forward. It will not change past workouts (no big deal).
    • In some of the reading I did a while back I thought that Power played the bigger role when you were cycling. But it sounds like Anaerobic, High Aerobic, and Low Aerobic are based solely on heart rate?

    Thanks so much for helping me get this fixed.