First Gen HRM-Run drops out after 2-ish mins

+1 same issue with my HRM TRI

Not sure what’s going on for you guys, but my Gen 1 HRM Run worked flawlessly today with my Fenix 5 Plus (along with connection to both of my RunScribe pods) https://connect.garmin.com/modern/activity/2800322090 Just wondering if the usual tech fixall “turn off then on” thing helps. It used to fix my Fenix 5 not finding my Scosche Rhythm+ in BLE mode, on the odd occasion things went funky. Failing that, perhaps tap up Garmin Customer Support in your respective country.

We've done 3 runs each - a 3 miler, a 5.5 minute warmup, and a 5 mile. My warmup is the only one that made it thru. My other runs it drops out at 2:08 & 2:14. My wife's dropped at 2:08, 2:09, and 2:08. Each time they connect fine. We only noticed the issue when we looked it garmin connect. I wasn't looking at those screens during the runs, so it's possible they were registering and some wrong with persisting the data, but that would seem unlikely. My wife's on with Garmin support now, so we'll see what they say...

EoSNJ Look at the following article and let us know which step works for you.

https://support.garmin.com/en-US/?fa...region_sensors

tried factory reset, new hrm battery, new sync....nothing...

Just a thought, but have you tried an alternate strap (you say you are using first gen HRM Run, the one with the removeable pod). My experience is that the HRM Run pod stops transmitting after a couple of minutes if it fails to detect a heart rate. So just wondering if your strap is shot (they do eventually go) and failing to give data to the pod once you start moving about.

EoSNJ Look at the following article and let us know which step works for you.

https://support.garmin.com/en-US/?fa...region_sensors

Garmin-Heath None. As described previously, the HRM Run connects ok. It drops out after approx 2:08 during a run, consistently. Battery changed a month ago - status is 'ok'. The replaced the strap itself about a month ago too, and yes it's been washed properly. I've had this HRM-Run for several years now, and it's worked fine with a 920xt, Fenix 3, FR620, and Fenix 5X.

The new 5X Plus is the first I've seen this behavior. My wife's 5 (non-X) Plus is doing the same thing at the same time point - as if there's a time-out/keep-alive communication not taking place.


We're both using Stryd footpods, and those work properly for the full duration of the activity. My wife opened a ticket with tech support, and the tech asked that we try turning off the Stryd sensors to rule out conflicts. I ran multiple 1/2 mile tests today with the Stryd disabled and enabled.

Tests 1 and 2 were half mile each (5 minutes) - per the tech, the first was with both foot pod and power sensor disabled. the second was with power enabled. Both tests drop out at the same point, +/- a second or 2.

Being as we've been running with our 5X's (original recipe) with no such drop outs, I ran 2 more tests - this time wearing BOTH watches connected to the HRM-run at the same time.

In these tests, the data is present for the duration of the runs on both watches - However, it has gaps at ...drum roll please... ~2:08 for several seconds.

Subsequent test with just the 5X Plus again drops out completely at 2:08/9.

My wife will be doing tests tonight, and will send the data off to the garmin tech for investigation.

Here are the links to Saturday's a trail race we ran on Saturday.

https://connect.garmin.com/modern/activity/2799320854

https://connect.garmin.com/modern/activity/2799306124

and a sample from today:

https://connect.garmin.com/modern/activity/2804091684

jeremy96121 is yours dropping at a consistent time?

@Crispen_Ellisdon I'm going to try a reset of the HRM itself and see if that helps. The strap is only a month old. It does seem to be time-out related though - and the old 5X able to keep it alive, but the new Plus isn't.

The thing with ANT+ is that the watches don’t transmit to the sensor, they simply receive. So if the sensor is timing out, it’s not the watch that’s the problem. If there’s any way you could get your hands on another HRM Run to test, that would rule in/out the coincidence that your current pod just happened to develop a fault at the same time as changing to the new watch.

The thing with ANT+ is that the watches don’t transmit to the sensor, they simply receive. So if the sensor is timing out, it’s not the watch that’s the problem. If there’s any way you could get your hands on another HRM Run to test, that would rule in/out the coincidence that your current pod just happened to develop a fault at the same time as changing to the new watch.

Yep, trying to rule things out. I need to do test with just my old watch to see if it's clean. When wearing them both, they both recorded the entire run though with a 1-2 second drop at 2:08.

My wife has a second strap and HRM Run and she'll test with that tonight. I don't have a second one, but I have a new version on order that should be here tomorrow.

(btw, I did try 3 times to edit that post to correct the tag to you, but it kept timing out! LOL )