Related
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

New Issue: HR detection inaccurate for first part of run

3682096
over 5 years ago

I've been running with my FR245 for a while now, but have just run into a new issue this week that's happened three times now (out of four runs). The detected heart rate is too high for the first 5–15 minutes.

The heart rate should be around 130, but it gets up to 170! It hovers around there for 5–15 minutes and then is fine for the rest of the run. I double checked (finger on neck), and it does appear to be a watch problem.

This happened today after the 3.90 update, but it also happened earlier this week before the update. It has never happened before this week. Anyone else experiencing this?

  • 0 over 5 years ago

    This might be related to temperatures getting lower in some parts of the world at this time of year, although I don't know where you work out. Often optical sensor performance is worse in low temperatures, until you warm up.

  • 0 over 5 years ago in reply to tmk2

    Thanks for the reply. I don't think that's it in this case. This has never happened before, despite much colder runs, and one of the incidents happened while treadmill-running in a gym (moderate temperature).

  • 0 over 5 years ago

    Yes I have intermittently experienced this. It seemed better after 3.7 but maybe coincidence. Not sure about 3.9, I've only just updated to it. One hypothesis is that it keys to my cadence when wrist Smirkpulse is weaker at start of run. I do intend to cross check with a strap hrm at some time, but for now I don't worry about it (kind've like I Ignore the firstbeat dubious ratings of training effect and recovery time Smirk)

  • 0 over 5 years ago

    I have a brand new 245 (two weeks old) and this happens on roughly 1/2 of my workouts. The first couple of times, it seemed to correct after about 15 minutes, but then it measured me at about 95% of my max heart rate for about an hour and a half run. The only way I've reliably gotten it to reliably reset is to pause the run, select "resume later", power cycle the watch and continue. Very frustrating to say the least.

  • 0 over 5 years ago in reply to kevinhankens

    Yeah, that's very frustrating indeed. It's happened for me both on a treadmill (i.e., room temperature) and outside in a variety of temperatures. This never happened with my previous 245. Have you contacted support, out of interest?

  • 0 over 5 years ago in reply to swad

    Thanks for the reply. Yeah, the cadence could interfere, but one would expect a running watch to handle, well, running. :) Interestingly, it actually happened at the end of my run the other day too. Also odd that this never happened on my previous 245.

  • 0 over 5 years ago in reply to 3682096

    No, I haven't, but I likely will.

  • 0 over 5 years ago in reply to kevinhankens

    Any update on this?  I am having the same issue.  

  • 0 over 5 years ago in reply to 7830166

    What I’ve been doing is turning the watch to “treadmill run” and select the heart rate screen while I’m stretching and getting ready to run. The HR is wacky for about 10-15 minutes, but when I get outside in my driveway, I hit the back button and select “run” and wait for GPS. By the time I’m running, it seems like it’s getting correct data. Not ideal, but I can live with it.

  • 0 over 5 years ago

    I have this issue since I bought it. My solution is selection my exercise and just staying still for like 2-3min for gps and heart rate monitor to stabilize. Usually I'll see my heartrate about 80-100 and then at some point after 2-3 min it will rapidly go down to my real heart rate at about 40-50 and after that I just start my activity and it is pretty good after that. I'm not quite sure why it can't track precisely straight away.