Heart Rate “spikes” when pairing Coros HR armband with Run

[sky-runner]

@zagazoo I use Coros HR armband a lot with Race and Race S. I have never seen spikes like this. This may be a Run specific issue.

[ADidier]

Tested today with the Coros HR armband, everything seems fine - firmware du Coros : V1.22.0

[ruNSuunto]

Today I ran with the Suunto Run and Coros HRM together and with my Garmin paired with a Coospo chest strap.

The graphs look very similar with some very slight differences as to be expected comparing optical with a chest strap but again the Suunto Run with the Coros HRM produced a spike not present on the other combination.

It showed a brief spike elevating my heart rate by around 20 BPM.

Tomorrow I’m going to replicate the run but with the heart rate monitors switched to see what is going on. I’ll provide some pictures after to show the issues I’ve had.

I have also noticed that even when using a chest strap with the Suunto Run that the heart rate graph on the app and the summary values provided for Max Heart Rate are not always the same. The graph might show a max heart rate around 174 for example but the information provided in the Heart rate section along with the Physiology and Power may provide a max HR of 190.

[ADidier]

@ruNSuunto I cannot find the peaks with the same type of equipment as you.
Can you check the firmware numbers of your equipment: Suunto Run and Coros Heart Rate Monitor?

[Matteiva]

@zagazoo for spikes problem with external HR sensor ( chest or optical band ), solved twice by re installing the app.

I got that problem one year ago, suunto race, and once again a month ago, vertical 2

Suunto support explained to me there are different heart rate algorithm which took place, once before start activity ( when external device is detected and read before the start), one during activity, showed on the screen, one to create the summary graph on the watch when activity ends, and also one when sync with the suunto app )

In my case the final on watch report was good, but spikes were noticable during activity ( data on screen ) and also on the app report.

Re installing the app solved the problem each time.

Strange isn’t it ?

Hope it will help

[Mff73]

@Matteiva said in Heart Rate “spikes” when pairing Coros HR armband with Run:

installing the app solved the problem each time.

The smartphone app?

[Matteiva]

@Mff73 yes strange isn’t it ? at first it seems a watch / bluetooth whatever problem with the external device, but in fact the app algo or watch / app link / algo are both implied in this bug

[ruNSuunto]

Steady run today with the Coros HRM paired with the Suunto Run. Again almost spot on but like every run it seems with this combination i get this rogue spike or spikes. I used a Garmin Forerunner and a Polar H9 on the other wrist with that graph not showing this spike.

The Run/Coros combo produced a max HR of 180 compared with the chest strap at 153.

Another example of this issue and i have a few more.
It is incredibly frustrating and unacceptable given the importance of heart rate data and the fact it is a basic function of running GPS watches going back many years and something which shouldn’t be an issue for modern watches at all.

I bought a Coros HRM because it has a reputation for good accuracy and improved comfort. As is i cannot continue to use it with the Suunto Run. Also when using the Run with a chest strap i often get differing max heart rate information that doesn’t match the graph or summary figures in the app. I shouldn’t be needing to wear two GPS watches and two external heart rate monitors during a run to validate the data produced on a new model watch. My Garmin is over 5 years old and more basic but has never had any issues at all like these experienced with the Run.

[Mff73]

@ruNSuunto
Did you read above and could try uninstall and reinstall Suuntoapp and check again HR display?

[ruNSuunto]

My run today was spot on. Used the Run with the Coros HRM and it was exactly the same as the Polar chest strap.

Before I had followed the suggestions and uninstalled and reinstalled the app. So it does seem that at least for this run it has eliminated the spiking.

However it has been mentioned in previous posts that uninstalling and reinstalling the app solved the problem each time in occured suggesting it is a temporary fix and not a permanent solution. It also doesn’t alter the data that is already present and incorrect from previous runs so I do believe it’s an issue Suunto need to look into.