Check out my first activity.
HR drops to 63. The strap is the Garmin HRM-RUN. Less than a year old. Works fine on other garmin devices.
What's going on?
Hrm run sensor causing drops to 63 in hr data on Edge 520 unit
Thanks Alan and others for sharing feedback and problem solving. So glad to see i was not alone here. I have tested my new edge 520 with existing hrm run sensor and strap for 1 week now. Without fail i was getting drops to exactly 63 bpm throughout each activity. When running forerunner 620 with the hrm run sensor, no issues. However, when running forerunner and edge 520 together, forerunner also showed dips to 63 bpm at same time! I resolved by buying standard garmin sensor and strap. Unpaired hrm run sensor and edge and connected normal sensor to edge. No dramas, all good. It was definitely the hrm run sensor causing tbe issue, as can use the new standard sensor with new and old straps and it still works well with the edge 520 regardless. Frustrating not to be able to use the hrm run sensor with edge 520 reliably. Can this be fixed? Software update perhaps?
I was told by support weeks ago that an update was coming soon. I guess I understated just how "soon" that would actually be.
I contacted support right after I received my 520 and they were nice enough to send me a standard HRM strap as I had a century ride that weekend (or following, cant remember when I called). I now have a tri this Sunday but it looks like I will have to use the standard strap and not HRM Run for the race.
curious, could the problem be hardware of the 520? ie, it broadcast or interferes with the signals, and cant be fixed by software. Would this actually cause problems if a 520 is near other devices, like at a race? Is that part of the holdup on new firmware? It seems like the vivoactive was getting 2 updates a month easy near the beginning.
Incpmpatibility of hrm run with edge 520 needs to be better highlighted
I spoke with Garmin support in Australia this morning. They highlighted that the hrm run is indeed incompatible with the edge 520. Still can't believe this, as both use ant+ protocol. Anyway, they referred me to website info on compatibility for the hrm run sensor, where compatible devices listed do mot include edge computers. However, when you look up specs for the edge 520, this incompatibility issue is not highlighted or clear. I asked that this be rectified if possible. Judging from this forum I was not the only person to be caught out on this.
I too experienced the same issue on my first ride this past weekend with my 520. It was a century and I rode with my Fenix 3 as well. Both devices registered the regular drops to 63. I opened a case with Garmin to which I have yet to receive a response. I went by the compatibility discussed at this link which shows the 520 has the ability to display heart rate data from the HRM-RUN:
https://support.garmin.com/support/searchSupport/case.faces?caseId=%7B11b42280-4f30-11e4-ef05-000000000000%7D
I was told by support weeks ago that an update was coming soon. I guess I understated just how "soon" that would actually be.
I contacted support right after I received my 520 and they were nice enough to send me a standard HRM strap as I had a century ride that weekend (or following, cant remember when I called). I now have a tri this Sunday but it looks like I will have to use the standard strap and not HRM Run for the race.
Good luck with that Magnus. I've learned my lesson with Garmin. Not one device has been released that was actually ready for use and now reading that Garmin's own device doesn't read their HR Belt right blows the roof of the house. I only use the HRM-Run Belt as all other Garmin belts do not work. After wearing them for a few rides they bend and the sensors don't have contact to your skin anymore and send faulty data...totally crappy. There is nothing more to say. Before they fix the HRM-Run Belt issue, a new device will be on the market. That's customer service..
Software update fixes compatibility with hrm run sensor
I downloaded software update 3.0 for edge 520 on Sunday 4th October and it fixed the connectivity issues with hrm run. I no longer see drops to 63 bpm thankfully. Now just have a spare sensor i guess, as i bought a premium strap to overcome the initial incompatibility.
