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

Time in Zones Does Not Add Up To 100%

Glenn_M_Eades

I just got back from a run, and sync'd my Forerunner 225 using Garmin Express 7.28.

When reviewing my run in Garmin Connect, I noticed my "Time In Zones" did not appear to be complete or accurate. 

Normally, the time for all zones should add up to 100%. 

Here are the actual numbers from todays run - 

Heart Rate Zones 

Zone 5        > 156 bpm • Maximum     0:00      0%
Zone 4  131 - 155 bpm • Threshold  18:22    38%
Zone 3  112 - 130 bpm • Aerobic        4:18      9%
Zone 2    95 - 111 bpm • Easy             3:11      6%
Zone 1    78 -  94 bpm • Warm Up      0:00      0%

That only adds up to 53%
 
That leaves 47% of my run unaccounted for, and no way to know what % in which zone(s) it was run in.

This was a 47:35 run, but only 25:50 shows up in the HR Zones Chart.

HR Chart - https://imgur.com/a/dQg4QYh (Download for a larger view)

As you can see my heart rate at the start of my run was around 126bpm and at no time did it ever go lower than 110bpm. 

Does anyone have any idea why this may have happened, or how to fix it?

It's not going to be very good as far as tracking my progress this season if this keeps occurring. 

Top Replies

All Replies

  • 0

    Do you have any time with HR below 78 bpm?

    Is the time adding up to the total of your workout? 25 minutes 51 seconds

  • 0
    Glenn_M_Eades said:
    That leaves 47% of my run unaccounted for, and no way to know what zone(s) it was run in.

    I wouldn't say "no way", you can easily lookup the heart rate graph.

  • 0 in reply to e7andy
    e7andy said:

    Do you have any time with HR below 78 bpm?

    Is the time adding up to the total of your workout? 25 minutes 51 seconds

    OP's HR being in zone 0 (i.e. the zone below zone 1) for a significant amount of time does seem like the most plausible explanation at first glance, except they also have 0% time in zone 1. Hard to imagine they could go directly from zone 2 to zone 0 (or vice versa), skipping zone 1 completely, even if they paused their activity while their HR was changing significantly - they would have to be very lucky (or unlucky) to happen to exclude all the HR readings between zone 0 and zone 2.

    It's also kind of implausible that anyone could run in zone 0 for half of a 50 minute run, unless their zones are set wrong. And in this specific case, it's hard to believe that anyone (regardless of age) could run at less than 78 bpm for 25 minutes.

      could you make your activity and share a link here so we can look at it?

  • 0 in reply to e7andy

    It was a 47:35 run. That's why I stated it only recorded 53% of the run. 

  • 0 in reply to Jan_Mantau

    Really? and you can see the shifts from one zone to another and what percentage of the time one is in those zones by looking at a graph? That's an amazing skill you have there, but unfortunately one that very few others possess.  

  • 0 in reply to flowstate

    I'm assuming you were asking for a screenshot of my HR chart. Here ya go - 

    HR Chart - https://imgur.com/a/dQg4QYh (Download for a larger view)

  • 0 in reply to Glenn_M_Eades
    Glenn_M_Eades said:
    I'm assuming you were asking for a screenshot of my HR chart.

    What would be more interesting, is the link to the activity (open it in Garmin Connect Web  and post the URL address of the page), or even better, the FIT file (use the default export option on the activity page). It looks like the file may be corrupted for some reason.

  • 0 in reply to trux

    Yes, it's clearly corruption.

    When I got back from my run last night the 225 wasn't able to be recognized by Garmin Express at all. When I looked at it in Disk Manager it had lost its formatting and had converted to RAW format.

    It's old enough, it's seen better days, and now that it's proven itself to have become unreliable I've just ordered up a Forerunner 255 Music. That should certainly solve the problem.