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

It would be great to know if this continues and if anyone has an ANT+ turbo trainer (like the Tacx Neo) whether that improves that as well. If it does I might consider re-buying the VA3! As stated in other threads I also had problems on the treadmill using just the internal gyro and oHRM but I'm wondeirng if that has to do with the ANT+ on the turbo trainer being on as it used to sporadically vibrate to tell me it had found the speed/cadence sensor!

Thanks brontide, it would be great to hear. I understand the limitations regarding power but for me that's secondary. Zwift displays that for me on the PC and I could always use my Edge as well if I wanted it recorded but sometimes I just want to record the basics and keep it on Connect. Anyway, method aside, I'd still like it to work as well as my original VA which wasn't the case with the VA3 until now maybe.....

33+ minutes this morning with a strap+tacx santori smart with no reconnects. This is progress. Just be aware that garmin does not have combined FirstBeat metrics, yet, it's on the roadmap so your readings from the Edge or other garmin device doesn't necessarily impact things like you vo2max score on the VA3.

I have this version and did a 50min bike trainer ride this morning with a ANT+ cadence sensor. Experienced sensor reconnect multiple times and that seemed to happen at the same time as the HR reading on the watch dropped back to 80(seems to be a reset baseline?).. so for me there still seems to be some sort of issue.

I have this version and did a 50min bike trainer ride this morning with a ANT+ cadence sensor. Experienced sensor reconnect multiple times and that seemed to happen at the same time as the HR reading on the watch dropped back to 80(seems to be a reset baseline?).. so for me there still seems to be some sort of issue.

I'll do anther workout tonight and report back. My hope was maybe a bit premature.

It is definitely not fixed. Tonight's workout, On Board HR/ANT+ speed, 2 HR/Speed dropouts.

It seems to have something to do with the on board HR. It does not seem to happen when using a HR strap as Brontide tested. But who knows for sure.



ciq.forums.garmin.com/.../1319361.png

Sorry to say but I'm still seeing the same thing. Maybe not as bad but the drops are still happening. When they happen its the same thing, HR reading goes to 80 and the sensor eventually reconnects and vibrates the watch. (eventually HR goes up to where it needs to be). Battery seems a little bit better 20% for ~1:25 minute activity.. vs ~20% for an hour. I bet whatever is causing the HR to drop to 80 is most likely chewing up battery at the same time. For a comparison it happened 3 times on an 1:25 minute ride (sensor 5.80) vs ~8 times on a 1:30 minute bike (sensor 5.50)

Oh man! I was hopeful for a minute! Was going to give it a last chance tomorrow.

Personally I wouldn't throw in the towel just as yet. Garmin seems to be making progress with it. I'm not happy they are there but love the VA3 enough to deal with these quirks until they get fixed. Also, at least my ride map appears accurate (no teleporting to other areas). And no, I don't work for Garmin.

Evidence from the sensor error log in the Garmin folder (SNS_ERR.TXT)
16 Sensor errors on 3/5 on version 5.50 vs 5 sensor errors on 3/7 on version 5.80 (This is what they look like).

Sensor Hub Reset, v580
03/07/18
23:34:01
6756,41581295
5885,41581923
6756,41582295
5885,41582923
6756,41583294