FR 955 Series: Training effect calculation is wrong AFTER 12.23 software (may include 12.27 and 13.15 sw)

I totally agree with you!  I didn't have the TE problem; my problems were: VO2 at almost the same level for the past 3 months, lactate threshold auto detection not working, I had to run a manual FTP test to get it, HR auto detection not working properly either give me max HR rate when running in zone 2 and not updating after a race where my HR was at least 5bpm over the Mar HR and o whole bunch of other issues such glances, maps just like most of the other people.

So I decided to sacrifice my data to give them a hand, and I have reset all my HR zones to default. Garmin - Kevin want to see the data after 2 weeks. So far as you can imagine I run on zones 4 and 5 even on easy runs and my recovery counts in days and all my runs are VO2 Max but I still see no increase in VO2 as of yet.. We will see how this goes.

Here's the thread for the VO2:

https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-955-series/304806/vo2max-isn-t-increasing#pifragment-1279=5

Regards,

Thank you for the update!

I’ve seen the same issue with my max HR updating to a figure over 180 when I didn’t go above 160bpm.

I turned off my max auto update, but I did notice something similarly odd yesterday in my Connect daily summary on the computer ... according to the HR section, my high was 185.  I did two workouts yesterday, one bike one run, at an avg/max of 140/158 and 142/160 respectively according to the Garmin summaries. I didn't remotely approach 185. Not sure if it's related to the issue here but seems like at least an odd coincidence. I might have seen this happen once before but dismissed it.

On a semi-related note, I have found errantly high HR readings can occur if I don't have my watch strap cinched down enough. As in, running along at a steady pace, 140's, and suddenly it surges to 150's 160's -- I tighten one notch (without breaking stride) and it goes right back to 140's where it should be. This happened during my steady state run yesterday and was responsible for the 160 max, but still doesn't explain where the hell 185 came from ...

This is exactly what happened to me. HR updated to 185 or 186 when I was absolutely nowhere near that. I wear an external sensor so not using my OHR though.

All,

After updating your watch to the recently released software containing a fix for this report, you will also want to ensure that you have your heart rate zones set correctly.  This will ensure that the data displayed in your "Time in Zones" section of your Activity Summary accurately reflects what is being used to actually calculate the Training Effect for the activity.

Thank you, i did need to correct my zones slightly after this update.

I've been having same issues as everyone just had the watch couple of weeks so though it was settling down and cos of not having hrv.  Updated all of the HR zones and my max HR and it was calculating too low and changed auto detect off - ran at zone 2 pace and gain was saying threshold.

Checked setting again and noticed in user > heart rate > zones > Heart rate there is a Sport section went into running this hadnt updated my main profile and zone percentages so was still on 175 max hr instead of 193.  Have3 updated this and think is going to resolve the issue so worth going through the sports section - guess might want different zones etc for cycling put it must be trumping the main setting (as would expect), didnt have that on previous watches.

Hi I’ve got the latest beta software but I’m not sure this is fixed?  I did a circuit this morning whereby my I spent a lot of time in all zones. A lot at threshold yet it gets logged as base low aerobic??

surely that’s not right? I appreciate I spent time in my low aerobic zones too but surely if I’m hitting threshold for many minutes it shouldn’t be logged as base/low aerobic? My max HR is 180 and my zones set as % of max HR  

Thanks