Using Forerunner 255 (former user of Forerunner 235 for 7 years), noticied that after about 50 minutes running and reaching 160bpm, it suddenly went to around 100 bpm.
Is it related to sensor? Outside temperature was about 18-20 degrees.
Using Forerunner 255 (former user of Forerunner 235 for 7 years), noticied that after about 50 minutes running and reaching 160bpm, it suddenly went to around 100 bpm.
Is it related to sensor? Outside temperature was about 18-20 degrees.
It is not so strange that it acts like that. The sensor picks up a noisy signal. The algorithms in the watch will continuously try to determine which of the many frequencies that is your heart rate. Some…
I have no connections to Garmin, but I am a robotics engineer, so I have an understanding about how the technology works. I have had watches from other brands, like Polar and Fitbit, and they had the same…
I have the same feeling. They keep introducing new functions, but they can't handle basic readings. Therefore, new functions based on these readings are also wrong. Heart rate spikes, I reset the watch…
I have the same feeling. They keep introducing new functions, but they can't handle basic readings. Therefore, new functions based on these readings are also wrong. Heart rate spikes, I reset the watch during the run to get it back to normal. Interruptions in training recording or altitude spikes are standard. I wonder if it's only the watches from the Forreuner group that are so weak or if the entire Garmin has fallen so low.
Also, you only have to google for "Apple watch HR problems" or "Huawei watch HR problems" to get loads of similar complaints. It's not only Garmin.
I've the same issue with a HRM connect via ANT during strength training. After around 40 minutes the the recording stops or it stuck at a HF number today it was 106 and then after a while 90.
When I move the HRM a little the numbers came back but then it stops again.
P.s. Can't run at the moment because of a muscle issue in my calf
Some HRM straps turn off after a few minutes if they do not detect vertical movements. My HRM Run does this while my HRM Pro seems to stay on for the full activity.
Oh, didn't know that.
I've a HRV Dual from Garmin. I use that one since begin of the year during strength training, cause the optical sencor isn't made for this moves. But IMHO in the past the HRM worked as it should.
Maybe it's the firmware version 22.24 which trigger this error. Maybe @garmin sierra is reading this here also
It also happens to me a few times per year and every time i remember me fixing the strap of my 255 either from being too loose, being to tight, or having caught part of a sleeve.
The strange thing is that it does not recover by itself even if i remove and wear again the watch or pause it. Most of the times if i stop and start a new activity it also keeps reading wrong HR.
At least once after starting a new activity unsuccessfully, i rebooted it and still read wrong. Other times this is has fixed the issue.
My advise: Just fix the watch strap properly and try not to mess with it while running.
this happens to me at least a few times every run using a brand new 255. my running cadence is around 160 spm and when operating in high aerobic my HR is often around there as well.
i typically see several "events" in my run where the heart rate will drop from 150 or 160 to 120 with no warning, and then either jump back up if i adjust the strap, or slowly creep back up over several minutes. this problem existed with the forerunner 55, but is now completely out of control with the forerunner 255, ruining the HR data on most workouts. at this point my 55 is the superior device for hr monitoring despite having what is usually described as a "simpler" optical HRS.