Sensor HUD 2.70, anyone brave enough?

Got the 2.70 update to the OHR + 4.60 firmware. Performed a hard reset and started from scratch with my personal settings. One different thing I did now was to record the data every second instead of "smart" (I donit care if battery lasts only 2 days instead of the normal 4/5)...
About 2 hours ago I did a Les Mills RPM class and the OHR was perfect! (compared to the watch+chest strap provided in the gym)
https://connect.garmin.com/modern/activity/1174876565

This is a remarkable improvement for my case! In the next couple of days I'll make some intervals workout and then a longer run, but things look really good right now.

If it is was "perfect" are you sure that your 235 had not paired to the strap you mention?

Pretty sure because it was a Geonaut watch which does not pair via BT with it's strap.

Got the 2.70 update to the OHR + 4.60 firmware. Performed a hard reset and started from scratch with my personal settings. One different thing I did now was to record the data every second instead of "smart" (I donit care if battery lasts only 2 days instead of the normal 4/5)...
About 2 hours ago I did a Les Mills RPM class and the OHR was perfect! (compared to the watch+chest strap provided in the gym)
https://connect.garmin.com/modern/activity/1174876565

This is a remarkable improvement for my case! In the next couple of days I'll make some intervals workout and then a longer run, but things look really good right now.

I've done 2 workouts so far with 2.70 and noticed my heart rate at the start of the activities is abnormally low. I noticed your activity starts low as well for the first 7 or so minutes, until it jumps up. Is this expected in your case given your effort?

5317

I've done 2 workouts so far with 2.70 and noticed my heart rate at the start of the activities is abnormally low. I noticed your activity starts low as well for the first 7 or so minutes, until it jumps up. Is this expected in your case given your effort?

It was expected and on track with the Geonaut watch because I started pedaling very lightly a few (maybe 5 minutes) prior to the start of the class (which then starts with a couple of minutes of "ramp-up").
The HR took only a few seconds to pick up to the same level as the on the chest strap was reporting to the Geonaut watch.

Like I said, this was just one activity following a hard reset and I do have the data recording set to every second. This was a great improvement but it was in a room with even lightning, so no cadence lock due to light fluctuations derived from the arms movement was expected. Until the end of Sunday I'll have a intervals workout on a track and a longer (~13kms ) on a road, so it should give me a better perspective about this update.

Still, after the last 4.3 firmware and 2.6 OHR update , my first run was a 10kms run at 4:50/km and my heartbeat was stuck at 90 the entire time... so yeah, this is much better now and I'm quite happy about it... ahah!



Edit:
And here's my HR widget since the update+hard reset+RPM class (forgive me for my fur jacket :P )

Pretty good looking, no spikes!

How long were your intervals? Here it was 400m @5k pace / 200m rest...
Can imagine those are too short as the watch doesn't adjust too smoothly (understatement of the year).
...

*Edit* Thinking about it I would at least expect to see SOME changes. But after my first 2 intervals it doesn't even go above like 120bpm. I WISH I was that fit. Bah, always like a russian roulette game with this watch and also with garmins updates.

Have you had substantially different results doing the same workout with a chest strap HRM? Just curious if what you're seeing is more a matter of simple cardiac lag, though perhaps exacerbated a bit by smoothing algorithms.

See http://running.competitor.com/2013/12/training/3-common-heart-rate-training-mistakes_29427/3

Have you had substantially different results doing the same workout with a chest strap HRM? Just curious if what you're seeing is more a matter of simple cardiac lag, though perhaps exacerbated a bit by smoothing algorithms.

See http://running.competitor.com/2013/12/training/3-common-heart-rate-training-mistakes_29427/3

Yeah, at worst the HR lagged with the intervals... So you saw the tempo increases and the HR increases were then behind. But in this case, the HR just doesn't go up at all. But as mentioned, partially blaming it to the short intervals myself and not writing it off just yet. But I would expect it to at least respond somehow (and a max HR at that pace of ~155 or so is certainly not realistic).

I know the cardiac lag phenomenon, but it represents in a different way then my log shows... But that of course also depends on how the Garmin algorithms.

I feel bad for Garmin engineers

Some people say its good
some say its ok
some say it sucks

Clearly, everyone has a different opinion. They should stick to the data they collect and ignore feedback here.

(FWIW 2.7 works fine for me, as does 4.6. It stands to be tweaked and improved, that remains to be seen.)

Did the update, got the 4.70 also, forced a hard reset and started my personal configs from scratch.

How did you do hard reset?