Inaccurate values using polar h10
-
I realized that when I use my polar h10 with my race s (FW 2.44.46) and I have heart rate fluctuations (e.g. intervals, hilly course) that sometimes my heart rate seems not to respond fast enough (no reduction for up to 10s).
This especially happens from high to low heart rate.
I then connected the h10 to also a Garmin (ant+) and polar (BT) watch at the same time. I saw that when this happens, both watches show the exact same value while my race s shows different values for up to approx. 10s.(Sometimes 20 BPM higher)
After that, the race manages to show the same value as the other two watches again. Overall, the Garmin and the polar watch ALWAYS show the exact same value the race not.Seems as if Suunto has some kind of algorithm applied that modifies the values coming from polar h10 whereas the other watches just show the measured and broadcasted value which should be the more accurate way as the polar h10 is said to have ECG accuracy.
For some reason this doesn’t always happen.Can someone please test and verify this behavior?
-
Sounds strange. Maybe your Race S uses wrist-based heart rate instead of the H10? With the latest firmware update, it shows the ID of the connected heart rate strap, so you can check it
-
@Rayfox thanks for the idea but verified that already. HR sensor LEDs were off the whole time!
I also think it is really strange because I do not know where the values come from. Always thought that with a HR belt it just outputs raw transmitted data.
-
@brave_dave the strap transmits R-R data, the time in between beats, and the BPM is computed from that. But you need to apply some small filter because R-R can be noisy.
-
@isazi thanks for the explanation! But apparently then polar itself and Garmin use the exact same filter/algorithm (100% overlap of data, maybe already filter applied by the h10. Is that possible?). Only Suunto uses another one. Which one though is more correct… At least, the values from Garmin and polar seem more realistic to me!
