Related
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 over 7 years ago
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
  • 0 over 7 years ago
    I was thinking a little deeper to this and my solution is software duct tape. If Garmin could add logic to check the current heart rate vs the previously recorded and look for a major variation. (i.e. 80 vs 140). If it detects this, simply keep logging the previously known good HR to the .fit file and keep this on the screen. Wait 5 -10 seconds for the sensorhub to recover and then show the latest HR number and repeat the variation check. Also, if it detects this, disable the sensor reconnect messages or simply keep them disabled after the first 1-2 minutes of the activty start. The biggest problem with this issue is all the HR dips to 80 through-out the activity and the annoying sensor reconnect messages. This throws off the average HR and zones too.
  • 0 over 7 years ago
    I just received my 3rd VA3 replacement from Garmin last Monday April 16, but sad to say that all the issues i experienced with the previous 2 VA3's are still in my current watch these are the HR dropouts, Ant+ disconnection (im using a Garmin footpod) and Bluetooth disconnection (Iphone 7 plus).. this dropouts/disconnection goes all together and occurs like every 15 or 20 minutes while doing an activity. HR drops to 70-80 then slowly goes up. not really sure if a true fix is coming, because the 3.5 update has nothing to do with this long time VA3 problem.


    You are confirming that this problem is not not just big, it is design flow. I.e. every device has it. The fact that not every owner complains is because we are (external sensor users) simply small group. Not that many people who have speed/cadence sensors - do not have bike computer and even less people run with external pod and no external hear rate.

    Well, too bad. Looks like we are stuck here, since no software and not even hardware fix exists (besides buying completely different watch).
  • 0 over 7 years ago
    I've done two runs since I started using a chest strap and I didn't get a single sensor drop, whereas I've been getting between 1 and 5+ of them before that in the 3 weeks I've had the watch.
  • 0 over 7 years ago
    I've done two runs since I started using a chest strap and I didn't get a single sensor drop, whereas I've been getting between 1 and 5+ of them before that in the 3 weeks I've had the watch.


    That is the whole point. With external HR watch works more or less okay - drops are there, but rare. Besides once drop occurs - heart rate comes back instant when connection restored.
  • 0 over 7 years ago
    Yesterday I recorded a ride directly on the watch (not using HR broadcast). Sensor Hub was crashing at similar intervals. I do however have ANT+ speed and cadence on the bike though I think the batteries are flat.

    Sensor Hub Reset, v580
    04/21/18
    01:47:03
    5832,237821322
    5832,237821544
    5832,237821778
    5885,237822010
    5832,237822044

    Sensor Hub Reset, v580
    04/21/18
    01:51:41
    5832,238100169
    6756,238100266
    5885,238100269
    5832,238100453
    5832,238100670

    Sensor Hub Reset, v580
    04/21/18
    02:00:09
    5832,238608228
    6756,238608266
    5885,238608268
    5832,238608528
    5832,238608727

    Sensor Hub Reset, v580
    04/21/18
    02:11:29
    5832,239288924
    5832,239289128
    5885,239289268
    5832,239289324
    5832,239289629

    Sensor Hub Reset, v580
    04/21/18
    02:31:45
    5832,240504015
    6756,240504266
    5832,240504268
    5885,240504268
    5832,240504569

    Sensor Hub Reset, v580
    04/21/18
    02:51:51
    5832,241708222
    6756,241708266
    5885,241708268
    5832,241708485
    5832,241708721

    Sensor Hub Reset, v580
    04/21/18
    02:51:55
    5832,241708222
    6756,241708266
    5885,241708268
    5832,241708485
    5832,241708721

    Sensor Hub Reset, v580
    04/21/18
    03:00:14
    5832,242212782
    5832,242213036
    6756,242213265
    5832,242213267
    5885,242213269

    Sensor Hub Reset, v580
    04/21/18
    03:05:41
    6756,242540266
    5885,242540268
    5832,242540428
    5832,242540724
    5832,242540926

    Sensor Hub Reset, v580
    04/21/18
    03:13:24
    5832,243001925
    5832,243002137
    6756,243002266
    5885,243002268
    5832,243002426

    Sensor Hub Reset, v580
    04/21/18
    03:13:28
    5832,243001925
    5832,243002137
    6756,243002266
    5885,243002268
    5832,243002426

    Sensor Hub Reset, v580
    04/21/18
    03:22:50
    5832,243568518
    5832,243568763
    5832,243569009
    5832,243569267
    5885,243569269

    Sensor Hub Reset, v580
    04/21/18
    03:26:10
    5832,243768429
    5832,243768630
    5832,243768913
    5832,243769130
    5885,243769268

  • 0 over 7 years ago
    You are confirming that this problem is not not just big, it is design flow. I.e. every device has it. The fact that not every owner complains is because we are (external sensor users) simply small group. Not that many people who have speed/cadence sensors - do not have bike computer and even less people run with external pod and no external hear rate.

    Well, too bad. Looks like we are stuck here, since no software and not even hardware fix exists (besides buying completely different watch).


    The fact that the VA3 included this features as its selling point like the wrist based HR (which eliminates the strap) and the capability of adding extra Ant+ sensors, these features should have work as it should be. but maybe ur right this is a design flow that Garmin wont be able to fix.
  • 0 over 7 years ago
    Do you guys think that the GPS spikes problem is related to these dropouts? It was not the case before, but after the last updates (sensor hub, iirc), now I have at least a GPS spike for every long ride. So frustrating.
  • 0 over 7 years ago
    UPDATE: As of today the HR dropout and Ant+/Bluetooth disconnection still an issue and now, another problem update the "weather data is not available" even if watch is connected to phone, and synced it successfully but still no weather data is shown, i did all the possible troubleshooting (15 sec reset and re-pair the watch) but still an issue... Complete disappointment.
  • Former Member
    0 Former Member over 7 years ago
    I picked up a VA3 this week, on every ride so far (all around an hour long) I've had at least 3 instances of the HR not recording.
    It's going back to Amazon.
  • 0 over 7 years ago
    I picked up a VA3 this week, on every ride so far (all around an hour long) I've had at least 3 instances of the HR not recording.
    It's going back to Amazon.


    as you can see - it is not a news here. My advice - if you do not want disappointment to grow - do not exchange for the same (i.e. vivoactive 3) - it also will not work. Garmin is perfectly aware. Go get something else. People saying 645 works fine. Yet it costs fine too.