This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

First ride. HR drops to specially 63. (HRM-RUN)

Former Member
Former Member
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?
  • Seems that Garmin has some clean up to do ;-)

    Edit:
    Just took a ride with my old Edge 510 HR transmitter but with the new HR belt (from 920XT). No issues on HR here. So it's related to HRM run transmitter solely.
  • Is anyone else noticing the HR drops on other devices after pairing with the 520? I get the same drops on my fenix3 now. I've changed the battery on my transmitter but still see the drops during my workouts.
  • Is anyone else noticing the HR drops on other devices after pairing with the 520? I get the same drops on my fenix3 now. I've changed the battery on my transmitter but still see the drops during my workouts.


    No, I don't see the drops on my F3 with the HRM-Run or the Edge520 with the normal HRM now.
  • Is anyone else noticing the HR drops on other devices after pairing with the 520? I get the same drops on my fenix3 now. I've changed the battery on my transmitter but still see the drops during my workouts.


    No issues on 920XT with HRM run belt
  • I'm also having problems with my HRM from Wahoo. The 520 won't pair correctly with the Wahoo Tickr. If it does pair it looses connection after 5 seconds. I'm 100% sure the problem isn't the Wahoo Tickr since it worked flawlessly with my 510 and it still works perfectly with other ANT+ or bluetooth devices. I deleted the HRM sensor and now it won't even recognize the Tickr anymore. Has anyone else had similar problems?


    I got my Edge 520 today and have exactly the same problem with my Tickr. My Tickr works perfectly with 510, Vivoactive, iPhone etc but doesn't want to know about the Edge 520. The Edge 520 works fine with the Garmin HR strap I own. Maybe a firmware update will fix this soon?
  • Former Member
    0 Former Member over 9 years ago
    I got my Edge 520 today and have exactly the same problem with my Tickr. My Tickr works perfectly with 510, Vivoactive, iPhone etc but doesn't want to know about the Edge 520. The Edge 520 works fine with the Garmin HR strap I own. Maybe a firmware update will fix this soon?

    Good to know that I'm not the only one and that my device is faulty. I hope Garmin will acknowledge the problem and issue a fix shortly since I don't have the Garmin HRM and currently I cannot use any heartrate monitoring.
  • Confirmed with support the issue is due to the 520 trying to pickup the running dynamics from the HRM-Run. A ix is coming but no eta available. All other HR straps should work without issue.

    I did some additional testing with my fenix3 and found that my strapped worked fine until I turned on the 520. Once I turned it on it causes some kind of interference as I notice the drop to 63 bpm on the fenix as well. As soon as I turn it (520) off the drops stop.


    For those with only one HR strap (such as myself), here's hoping the update is out soon.
  • My email from garmin

    Dear Me

    Thank you for contacting Garmin Europe.

    I apologize for the confusion caused.

    Please be advised the the Edge 520 is not compatible with the HRM-Run as this Heart Rate Monitor is specifically for running watches. That is why it works perfectly with your Forerunner 620.

    Please find the links for the compatible Heart Rate Monitors :

    https://buy.garmin.com/en-GB/GB/shop-by-accesories/fitness-sensors/heart-rate-monitor/prod10996_010-10997-00.html
    https://buy.garmin.com/en-GB/GB/shop-by-accesories/fitness-sensors/soft-strap-premium-heart-rate-monitor/prod15490_010-10997-07.html

    If there is anything else I can help you with then please let me know.


    It's not really good enough - especially for bike/run sessions or duatholon. Atm either lose running dynamics or lose heart rate on the bike. I guess the former is preferable but hopefully be a SW update soon to fix.
  • Wow - that is one of the most disappointing customer service responses I have ever seen. Clearly the 520 has a bug where it misparses the battery level message as a pulse message. Why won't garmin just fix the bug?

    Dear Me

    Thank you for contacting Garmin Europe.

    I apologize for the confusion caused.

    Please be advised the the Edge 520 is not compatible with the HRM-Run as this Heart Rate Monitor is specifically for running watches. That is why it works perfectly with your Forerunner 620.

    Please find the links for the compatible Heart Rate Monitors :

    https://buy.garmin.com/en-GB/GB/shop-by-accesories/fitness-sensors/heart-rate-monitor/prod10996_010-10997-00.html
    https://buy.garmin.com/en-GB/GB/shop-by-accesories/fitness-sensors/soft-strap-premium-heart-rate-monitor/prod15490_010-10997-07.html

    If there is anything else I can help you with then please let me know.


    It's not really good enough - especially for bike/run sessions or duatholon. Atm either lose running dynamics or lose heart rate on the bike. I guess the former is preferable but hopefully be a SW update soon to fix.
  • @punkgeek - totally agree!

    What a total cop out from Garmin. I have a Fenix 3 with HRM-RUN bundle and an Edge 510 as well. I use my Fenix for swim/run training, but use my Edge 510 out front for most of my cycling training. I only have the one HRM-RUN strap that I use with both devices. It works just fine with my Edge 510, never an issue.

    So in response to Garmin... "the HRM-Run as this Heart Rate Monitor is specifically for running watches" why does it then work perfectly fine with your existing cycling computers?!

    This is a firmware issue. Copy the code from the 510 that "ignores" the run data coming out of the HRM-RUN sensor.

    Wow - that is one of the most disappointing customer service responses I have ever seen. Clearly the 520 has a bug where it misparses the battery level message as a pulse message. Why won't garmin just fix the bug?