FB501BKL - FITBIT SURGE - BLACK LARGE My maximum heart rate is 157....however when I workout and my heart rate reaches 140 - 143 my heart rate reading shuts down.... I even had a friend wear my fit bit surge to see if the same thing happened to her and it did. Is there a reason why this happens?

Question

GolfGirlRN · Accepted Answer

Chris,

I have not had this happen; I actually reached 162 for a short period of time and did not have an issue. When you say "shuts down" do you mean the screen goes blank, the monitor won't show anything over 143, or the HR doesn't register at all? This may be worth checking with customer service to see if this is common.

~GolfGirlRN

Krysse · Answer

I wish I was as healthy :) My heart rate reaches in the 170's and is tracked just fine. Contact Fitbit Customer service. You may have a defective tracker.

TrueVol22 · Answer

Sounds faulty. I've been wearing my Surge for 2 months. I've maintained maximum heart rate that rate for a duration and never had a shutdown issue.

1575 · Answer

Try wearing it a few inches farther than you would a normal watch

Rocketangel · Answer

Never seen this happen. May be your unit. Try a full re set and/or Get in touch w/Fitbit tech support. Use Twitter they monitor it and get back to you soonest. Very very good support. They believe in and back their product line !!

Answered by Rocketangel 10 years ago

ForeverStudent · Answer

The measurement frequency and sensitivity of the fitbit surge can't handle heartrates above roughly 140. I experience the same problem. My hypothesis is this: The HR measurement of the surge is not "constant" but has some frequency (think the way the light on the wrist-side blinks). When your HR gets above 140 or so, the measurement frequency can't accurate detect and measure your HR.

Think of video recording the wheel of an accelerating car. The wheels appear to move forward at first, then become a blur, at some point the wheels may appear to be rotating backward, or maybe not at all.

Haley88 · Answer

Haven't has that problem...have you tried to reboot it?

1-7 of 7 Answers