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

WHR (Wrist Heart Rate) / Sensor Hub firmware module 2.60

Seeing as the discussion threads on Sensor Hub (WHR – Wrist Heart Rate) firmware module v2.41 and v2.50 have been closed, and nobody has yet created a new thread for the just-released v2.60, I guess I'll do the honours. Here we go!

  • Announcement by Garmin (on 12 April 2016 at 18:34 GMT)

Changes made from version 2.50 to 2.60:
  • Increase fidelity of the all-day heart rate plot
  • Improve cadence rejection
  • Improve performance during interval activities


N.B. Firmware v4.20 for the Forerunner 230/235 was also announced separately at around the same time.

_
  • While I don't any problems, I saw one person say that they wore a tennis style wrist sweat band below the watch to keep it from slipping down.
  • Former Member
    0 Former Member over 9 years ago
    I have the same issue. My resting heart rate used to be around 48 witch I think is accurate and now I have a resting heart rate of 38...Testing...


    I think this is due to the poor sampling previous to this update. That's about what mine would be overnight. I would turn on HR broadcasting which had a much better sample rate and my RHR would be like you are seeing now, about 10 lower. So if this update increased sampling, most people should see a lower RHR. Can't wait to download and give it a try.
  • Former Member
    0 Former Member over 9 years ago
    Just updated an hour ago. 72 default HR fixed. Mine seems to lock on my actually HR a little faster than others, only taking about 5-8 seconds. Great improvement. I fully understand the limits of a wrist-based oHRM, but I'm looking forward to an interval session later today without my chest strap to see how it stands up. I'll wait a couple of days to see how my RHR readings come back. Never really had a problem there with v2.50. It may be a little soon, but does anyone have any feedback on how the sensor is working as far as reporting calories burned outside of doing a workout? From reading the post so far, it sounds like the updates will make me a happy camper. :D

    Update: Well, I can't speak for a steady paced workout, but I found the oHRM is still terrible for HIIT. Here are my HR readings one minute into my workout. Manual check was 119, Timex Ironman w/ chest strap 121, FR235 oHRM 157. I expected a difference, but not this extreme. Back to the old chest strap for me.
  • Well it's given me a resting HR of 37 today - around 14 lower than my previous average, and 11 lower than my previous minimum.

    This seems unlikely to me (as far as I know, I am still alive.)


    What other devices have you used to measure RHR?

    I've only just now applied the update, but previously my 235 has given a RHR that's been way high compared to what it usually has been when I've measured with chest strap and 920xt or prior watches. Sufficiently so that I literally haven't paid attention to it. I'll be looking to see what I get for RHR the next few nights.
  • Did a second 8 mile run this morning and was careful to make sure that my watch stayed in place and tight. I wore it right where it is recommended in the manual (about 2 inches above wrist bone, not on my forearm and not upside down) Over the entire run my heart rate was perfect with not a single cadence lock!

    Also, the quality of the all-day HR over the last 24 hours is greatly improved. No more 30 minute "135 BPM" hills while sitting at my desk. I still have a few spikes, but since the sample rate is so much improved, those spikes are spikes and not mesas.

    Battery life seems to be the same as well. I charge thrice a week and it is usually at about 65% when I do. My next charge is tonight and right now the battery is at about 70%.

    So good job Garmin I.T. people.
  • Former Member
    0 Former Member over 9 years ago
    First cadence lock after upgrade to 4.2


    I've never had this problem before. But after installing 4.2 and 2.6 :

    https://connect.garmin.com/modern/activity/1124747815
  • Former Member
    0 Former Member over 9 years ago
    What other devices have you used to measure RHR?

    I've only just now applied the update, but previously my 235 has given a RHR that's been way high compared to what it usually has been when I've measured with chest strap and 920xt or prior watches. Sufficiently so that I literally haven't paid attention to it. I'll be looking to see what I get for RHR the next few nights.



    Only the 235 - so of course it is possible that my new low RHR is the correct one. Seems very low that though.
  • Former Member
    0 Former Member over 9 years ago
    What the hell? People are posting on how whr 2.60 has eliminated the occasional spikes on the 4 hour HR chart. I'm having the complete opposite effect. Prior to 2.60, I'd occasionally get spikes in the 120's. I'd maybe see 2 or 3 of these in a day. I downloaded 2.60 this morning and things are terrible. I did a HIIT workout with a chest strap earlier reaching 152 bpm. Since then I have been relaxing in the backyard in a lawn chair. My 4 hour chart shows spikes of 161, 141, 134, 152 and 137. I can't possibly be the only having this problem. Anyone else seeing this kind of behavior? Less than 16 hrs into the day and my 235 says I've burned 2881 calories including a 400 calorie workout. Something's off.
  • No, I wouldn't say it has eliminated the occasional and obviously erroneous HR spikes

    What the hell? People are posting on how whr 2.60 has eliminated the occasional spikes on the 4 hour HR chart.
    Not exactly the case for me. Looking at it just now, it shows I was averaging in the high forties while I slept, low fifties while I checked my messages and news sitting in bed, and then jumped to 138 around the time I physically got out of bed.
  • Anyone else seeing this kind of behavior?


    Nope, mine has been substantially better today. The HR chart has got to have at least 10x the detail/polling rate. I still get the random spikes out of nowhere, but I wear it fairly loose when I'm not running, so I kind of expect it to miss occasionally during the day. But before it'd have 4 hour long sections of HR in the 130s, now that it's polling more it only has occasional short blips. Way better.

    I ran 10mi worth of 1/2mi intervals this evening and did not have a single cadence lock that I could discern. The HR recovery delay between intervals also seemed a lot better.

    My guess though is that some people who weren't having problems before will now have issues with the new algorithms causing cadence lock that they didn't have happening before. Hence why the update took forever... it's going to be hard to find the sweet middle spot where it messes up the least.