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

Old OHR problem is not fixed?

G141592653589793238
9 months ago

Hello, I can't find the thread in which all these types of problems with the OHR were grouped, where the HR suddenly shot up at a certain moment of the activity. The truth is that it doesn't happen to me often, but today I checked it and it happened twice in one day. Two different activities, a correct warm-up beforehand, a strength session in the middle and again another short run. Both with the same problem (20.29), the graphics are not logics.
I'll try to test it again tomorrow with 20.31 but it's not a sign of anything because it hasn't happened to me all the time, it's more random but frequent...
Thanks,

  • 0 9 months ago

    Hi, this is not fixed, no.

    See my thread

    https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-955-series/384760/heart-rate-values-from-optical-hrm-still-totally-wrong-with-20-26

    and the original thread, which is linked there.

    Garmin-Sierra confirmed that it is an issue and they are trying to find a solution, but that doesn't exist yet.

  • 0 9 months ago

    This is probably the most annoying bug for me and unfortunately, the fix has not been implemented which is very frustrating as I can't really trust the OHR data.

  • 0 9 months ago

    I do not have issues with optical, but with strap. Mostly the beginning of a run up to  170-175 at easy pace (tempo of zone 2, but not it's heart rate). And after 3-4 minute a drop to the correct HR like 145. Puzzles me, but I know it will drop down again, so I just keep running until it does.

  • 0 9 months ago

    Thank you all very much! Now I understand and I read the last post of this thread. Since the threads were closed I hadn't found them because I suspected that if the problem continued it should remain open, but no...

    Yes, I agree, it's a bit frustrating. Luckily it hasn't happened to me many times, but it does happen and it shouldn't, as I've commented in some of those threads.

    Today I did a test again and it worked fine (20.31), but I don't know, I'll have to let this month go by checking after each activity to see if 20.31 has solved something or if it's just luck of the draw. I say this because from yesterday to today the only thing I changed was the firmware version, but it shouldn't have any influence since there is no such change detailed in the Change Log, I didn't change anything about the activity either, same distance, same intensity, same warm-up, almost the same temperature and even the same hour, but without any error, why it happens, it's a mystery...

  • 0 9 months ago in reply to G141592653589793238

    Here's another example. Around the 18km mark my heart jumps up significantly for one of the 1 mile reps - you can see it's no faster than the other reps. It was 8C and cloudy, but not raining. Running v20.31.

  • 0 9 months ago

    Since months no solution - really bad... I am very pissed off.

  • 0 9 months ago in reply to 9869093

    Yeah, it's getting a bit silly. Honestly I think this is the root cause of the new overly ambitious race predictor times that some people are seeing. Garmin upgraded me from the 945LTE (for an unrelated issue) and at first the new predictions were actually way better for me, but I think that's because it was using the HR / paces data from all the activities recorded on the 945LTE. Now that I have done a few weeks of training with the 955, my VO2 has shot through the roof and my race predictions are too fast.