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

HR/ANT+ dropouts may be fixed with Sensor Version 5.8

Former Member
Former Member
There is another topic regarding an upgrade to sensor version 5.8.
I took this upgrade today via Garmin Express.
Later on I did an indoor cycling workout with the Garmin ANT+ speed sensor and using on board HR.
For the first time I did a workout (33 minutes ling) without any dropouts.

For those with this ANT+/HR dropout issue, please take the upgrade and report back.

Hopefully you can have a workout that looks as clean as mine.



ciq.forums.garmin.com/.../1318902.png
  • Former Member
    0 Former Member over 7 years ago
    I did a factory reset today - out of frustration that the heart rate keeps dropping more than hope it would fix the problem - and lo and behold, not a single drop out on my run!! I did 4 activities this weekend including three hikes and one trail run and they all had multiple heart rate drops. This run today, with absolutely nothing other than my reset VA3 - no apps or settings changed - was perfect, tracking my heart rate like it used to. Not sure why, guess I'll slowly start changing things to how I like it and see when my heart rate starts dropping out again.


    Do you have any ANT+ devices connected?
  • This may be old news, but my recent experience now that it's biking weather is that I still had dropouts using cadence/speed sensors and chest HR strap if I maintain wearing the watch. If I strap the VA3 on my handlebar mount I got no dropouts. This may have been coincidence though. When using an external HR monitor, does the oHR stay running on the watch or does it turn off?
  • I hope you are right although some previous posts say differently. I will try again using HR strap instead OHR.
    I think factory reset is worth a try if problem will be the same with strap.
    By the way i newer had any HR strap isues with Edge and i always moisten contacts so i didn't consider bad contact, but problems ocured during crossfit, which is a bit different than riding a bike so this could be possible.


    I had few rides with ANT+ HR strap, instead OHR, (including ANT+ speed and cadence) and I didn't notice sensor reconections (VA3 didn't vibrate nor showed massages about reconections). I don't either recognize HR drops i graphs as I did using OHR (together with ANT+ speed and cadence).
    Also i used OHR, without ANT+ sensors, and results were OK.
    Comparing graphs of Edge 520 with HR strap and OHR VA3 I'm very satisfied with results. Only thing that I don't understand is difference in calories burnt. I had 771 with VA3 and 884 with Edge 520 for a same ride, but this is another topic.
  • We have made good progress on this issue and hope to have a timeline for a permanent resolution very soon. The continued frustration is beyond understandable and I would like to thank everyone for their continued patience while we have investigated this.
  • We have made good progress on this issue and hope to have a timeline for a permanent resolution very soon. The continued frustration is beyond understandable and I would like to thank everyone for their continued patience while we have investigated this.


    Can you confirm that this is the onboard HR monitor drop outs? also (and sorry to threadjack) any word on getting the golf app to work better given the feedback we've given Garmin? get these sorted and I'll be one happy camper :)
  • We have made good progress on this issue and hope to have a timeline for a permanent resolution very soon. The continued frustration is beyond understandable and I would like to thank everyone for their continued patience while we have investigated this.


    Following and waiting...
  • It looks like I am getting sensor resets, I have ANT+ speed and cadence sensors. It didn't really bother me that it kept saying "connecting to speed" every so often until I started getting lots of GPS spikes. I think these issues must be related but I cannot be sure as it is not that easy to see from the connect dashboard, my HR doesn't always appear to drop. Do these who have been getting drops, also get GPS spikes? My old Garmin NEVER had these problems and I'm thinking about returning this back for a refund.
  • We have made good progress on this issue and hope to have a timeline for a permanent resolution very soon. The continued frustration is beyond understandable and I would like to thank everyone for their continued patience while we have investigated this.


    Any updates on the timeline for a permanent resolution?
  • I have recently purchased a VA3. Did so as I hoped it would broadcast HR to my Edge 820, sadly it drops out every 15 to 20 mins. I have a couple of weeks left before I cant return to store for refund. I do hope there is a fix before then. Shame, I have had many Garmin devices, all have been ok up until now :-(
  • It looks like I am getting sensor resets, I have ANT+ speed and cadence sensors. It didn't really bother me that it kept saying "connecting to speed" every so often until I started getting lots of GPS spikes. I think these issues must be related but I cannot be sure as it is not that easy to see from the connect dashboard, my HR doesn't always appear to drop. Do these who have been getting drops, also get GPS spikes? My old Garmin NEVER had these problems and I'm thinking about returning this back for a refund.


    While I really want to believe that there is software/firmware fix for these dropouts - the more I read about it and observe my own unit - the more I feel that it is hardware problems - watch goes through proper hard-reset. Yes, firmware already trying to mask HR reset by setting it not to 0, but 80 (or something around that number) and that will mask drops/resets while you are walking around - they are clearly evident during exercise with elevated heart rate. Same could (or I would say should) be applied to GPS precision, altimeter etc.

    I.e. my point - these resets are happening all the time - it just plenty of users do not notice them - since there is conscious efforts to hide them in firmware.