-
Completed one warm up run, an interval session, added another 2km run at a steady pace and all produced HR data. However, my short cool down run (just over 400 Metres) back home, produced no HR data.
The log on the watch is void of a HR reading, so the watch didn’t record. I think I did, but I can’t be sure that I had a green HR symbol before starting to run because sometimes with the sunglasses on, it’s difficult to see in certain light/shade. However, for over 2 minutes of running, I would expect the OHRM to pick up my HR at some point!
I’ve checked it since and I still have a functioning OHRM. I’ll be making sure that I have that green HR symbol before I start a run in the future, rather than expecting it to pick up at some point after starting, because clearly it may not!
-
Is the sport profile the same you selected before ?
Maybe you can check if HR is enabled via MC web -
@sartoric said in SSWHRB - Short run produced no HR data!:
Is the sport profile the same you selected before ?
Maybe you can check if HR is enabled via MC webYes, exactly the same sport profile as the previous run which I’d broken out of seconds earlier stopping and saving it out. The only reason I split the two runs was because of a busy road that was going to stop me in my tracks.
-
After raising this here, I’ve been scrutinizing the HR data when running. In short, I don’t believe it. It was totally believable prior to the last firmware update, but now it takes longer to lock, and won’t actually lock unless the arm is dangling i.e. if the forearm is point upwards it refuses to lock the HR.
As far as I’m concerned it’s as though the OHRM is not as sensitive/responsive, and struggles to register meaningful data when the forearm isn’t pointing downwards. I get data, but it’s not correct. If I look at my HR data prior to the fw update it’s solid and looks logical, but there’s no logic, or sometimes a lack of consistency to it now on many of my running activities.
Boooo said the crowd, basically! Booo!
