What you mean stable ? When GPS is ok how long should wait ? When I know is "stable"
I create the activity while changing into my running gear and put my shoes on. Even though it's been 10 minutes or so, I notice often that my HR goes crazy (130-150) after I've finished tying my shoes. So I sit still for about a minute on my step watching my HR and suddenly it will begin to decline rapidly and quickly 'snaps' down to 90 - 100 or so ... that tells me it has finally found a stable HR and I usually have a decent reading. If I'm impatient and run right away, the first 10 minutes of my run will almost always have stupid high and volatile HR before it finds my actual HR.
Max556 Not sure why this should be a surprise if you are using your hand/fingers to tie shoelaces that will involve significant activity in the wrist as the tendons and muscles work to tie the lace - very much dependent on your own wrist morphology - how tight and where you place the watch
JSrunner This is not surprising to me ... what you described is pretty much what I figured is going on. I was just trying to explain to JAN502 the process I go through to get a stable HR before I run, who asked "What do you mean by stable?"
JSrunner This is not surprising to me ... what you described is pretty much what I figured is going on. I was just trying to explain to JAN502 the process I go through to get a stable HR before I run, who asked "What do you mean by stable?"
Max
But solution "stable" in my case not helps ;-( I see always the same issue when hr go up more than 161 bmp ;-(
new test carried out: https://connect.garmin.com/modern/activity/2503491026 I updated to 7.61 version. As you can see I was increasing pace progressively an so did HR. Except a not real surge-peak in minute 23-25. HR reading was quite good, I also wore FR220 with HR chest band, both HR readings were quite the same. I reached near 180 in min 50, km 11. So watch was measuring quite good HR except the sudden raise.
My 225's HR was working so badly that I ended up exchanging it for 235. it worked better, but not perfect...
I had good results with 7.30 firmware and one day, I updated to 7.50, and it could never get my HR stable, so I downgraded to 7.30 and never tried to update since.
but even now, sometimes when I get the GPS right, the HR won't sync and I can go for a full run without it even showing on the watch..and when its freezing you don't want to wait for 10 min (sometimes, it won't even sync after several minutes waiting...) and the results is total sh*** like this : https://connect.garmin.com/modern/activity/2526109606
but I kind of accepted that wrist HR is not a reliable technology.
I'm having the same issue and even sent the watch to garmin twice, but the third watch shows the same problem, so I don't think it's a problem that can be solved by exchanging the hardware... My workaround at the moment: Before starting to run I make sure that the heart-symbol isn't flashing but it shows without interruption. If the heart-symbol continues to flash I turn off the heart rate detection, go back to the screen that shows the actual time, then I turn auto heart rate detection on again. In my experience the heart rate will now be measured correctly - at least during the actual training.
