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

AndreasH are you using any additional sensors or CIQ data fields? Would you mind posting one of your activities?

We're still working with Garmin to diagnose our issues, and I'd love to see someone else's data. Thanks!

I'm having the exact same problem. Fenix 5x plus sapphire with HRM Run and
Footpod
https://connect.garmin.com/modern/activity/2812287888
P.S. same problem Hrm-Tri https://connect.garmin.com/modern/activity/2814493075

I'm have the exact same issue with my 5+ titanium. 2:08 all running dynamics are lost, but the heart rate date seems correct. I washed my HRM Run second generation and changed the battery. I also ran with the same HRM Run using my Fenix 5 and I had all my running dynamics.

So I just went out on another run this morning and I connected my HRM Run along with my RD pod. The RD Pod records running dynamics just fine, my HRM Run records heart rate just fine, but not running dynamics. So this make me think the issue is only connected to HR straps recording running dynamics.

We are currently looking into this and I will update this thread once we have more information.

We are currently looking into this and I will update this thread once we have more information.

Dear Garmin Team this issue is repeated I already complained for that on my previous watch garmin fenix 5 with hrm+tri

Jan502 I do not believe this is the same issue that others reported on the non Plus Fenix 5 series, as that seemed exclusively to be general drop outs of RD data, HR data or both from HRM Run/Tri and was seemingly due to the low signal sensitivity on some devices. This issue does not question that the 5+ series has no problems receiving the signal, but that the RD data (not HR) is lost completely at exactly 2 min 8 sec after starting a Run activity; that is specifically something I never saw anyone report when following the Fenix 5 series (non Plus) since their launch in 2017.

Hi, here are the activities:

https://connect.garmin.com/modern/activity/2811629630
https://connect.garmin.com/modern/activity/2809339902

Not using any other sensors.

As noted a couple times, starting with the original post, this is not happening exclusively at 2:08.

It’s a common number that turns up, especially prevalent on 2gr8pyrs runs, but there are numerous variations. She’s also had runs with NO RD data at all, though the HRM was connected and registering heart rate throughout - verified by disabling the wrist heart-rate monitoring.

Others data reflects this also - doctormich example drops at 0:16 , and andreasH’s drop at 2:06 and 2:08.

And others are having no such problems at all.


Mine have dropped ( as in last data point present) at:

2:08 (first run and noticed afterwards that smart recording was on - all subsequent runs at 1 second recording)


The next run for me was a 5 minute warmup, and it recorded all the way thru ok! (2gr8pyrs dropped out)


2:14 for the race we were warming up for.

Garmin support asked that we perform tests to rule in/out the Stryd footpods*.


2:14 Stryd Disabled (per garmin support)

2:08 Stryd Disabled (repeat test)


2:10 Stryd FP disabled (per garmin support)

2:10 Stryd FP disabled (repeat test)

( I then ran with both watches to make sure the HRM was still ok with my 5X)

2 runs:
2:13-16, 46-49 gaps (Styrd enabled - running with BOTH my 5X+ and 5X on)

2:05-13 gap* (Styrd enabled - running with BOTH my 5X+ and 5X on)


With both watches running, both watches recorded the entire runs but both had brief gaps.

2:09 - again running with just the 5X+ after the runs with both watches. The 5X+ reverted to dropping out.

New Red/black HRM-Runs drops at:

2:10

2:09

Garmin suggested “For the time being, please start the activity right away (less than two minutes) when sitting on the timer loop” as a workaround.

We usually let the watch stage for a while to let the pace settle to zero, and give the gps a bit of a soak before starting the activities.

So last night started the activities as soon as all gps and sensors were acquired - 2gr8pyrs recorded the entire run (the first time she’s had that happen), but mine cut out at 2:09

Today’s a rest day, so we’ll repeat that test again tomorrow.

2gr8pyrs and I have been communicating with Garmin over the issue, and trying to provide controlled test data to help diagnose / fix the issue - only changing one thing at a time, and repeating the tests to confirm results. At their request, we’ve sent our Garmin folders as well as the FIT files. Clearly this isn’t an simple problem to solve, especially given the exceptions and variants.


* No difference for our tests with/without Stryd and others are having the problem and don’t use any sensors other than the HRM’s

I am not sure if this useful , but on my f5x+ I don't have this issue (yet) but I have in the watch configuration/system/save every second.
please check if you have the same and do test