Problems with Ant+ connectivity

I’m with you on that
aso if you read the test reports on the FCC website you’ll see the effective power output for ANT+ and BLE have both increased from 40 to 60 (cant remember the actual units used now)

this antenna change will will improve things I’m pretty sure

Hi all,
After my F5S upgraded to the 7.60 Firmware I must say that dropouts are pretty much gone for me.
I have tested it while running (with Stryd PM) and cycling (with Team Zwatt PM).
While running I didn't have anything to compare it with, but it seemed all OK now w/o any dropouts (I anyway did not experience too many dropouts with Stryd before).
While cycling I had my Edge1000 also recording and the numbers were roughly the same (roughly because I experienced that the Edge was recording at 1 sec intervals and the F5S was recording at "smart" intervals). Previously I experienced huge dropouts every few minutes on the F5S, but it seems to be fixed now.
This weekend I will try it out again with 1sec recording interval on both decives and will report back to you.

Does anyone else also experience improvements since the 7.60 upgrade?

I've actually got some short dropouts from the RD pod now too, but this only really happens to noticeable extent when using along with Stryd paired both as footpod and power meter. Even though the dropouts last maybe 1-2sec there's quite many of them, especially beginning of the run, yet large parts of the run towards end are totally drop out free.

When Stryd was only paired as footpod to provide pace I didn't have dropouts.

This doesn't actually matter for me as when I'm using Stryd for power I don't really need the RD Pod. I only bought it to test Garmins running power and to keep my options open.

Still does seem that even though my F5 is probably one of the better ones out there, it does have its limits.

I sometimes use the watch to broadcast wrist HR instead of using strap when cycling indoors and the app I use (connected with Garmin ANT+ stick on a Win10 tablet) clearly shows lower signal strength for HR than other sensors, dropping to 50-60% and sometimes even below where as other sensors show steady 80-90% signal.

Here again seems the signal is weaker in the beginning of the activity. Wonder why is that?

I downloaded the latest Beta and without wanting to jinx myself the dropouts are pretty much non existent for two consecutive runs. I hope this continues.

i saw first improvement with 7.00 FW, since FW 7.1 i have almost no dropouts. (with my first F5 i had 50% dropouts, with second and starting with FW 6.00 cca 15-20%)

I'm currently on firmware 7.60 third watch... Fenix 5... Fenix 5X and back to Fenix 5... I have dropouts on speed, HR and watt/cadence.

rickj2903 Sounds interesting that the beta version seems to work. I'll have try tomorrow!

Well I can confirm my dropouts are just as bad with genuine Garmin sensors ????

spot which graph is from my watch and which from the pc running Zwift (both from the same sensor)

Had a chat with Garmin earlier and still no news on when the revised hardware will be available
ciq.forums.garmin.com/.../1303479.png

I took a chance today and bought a stryd to use with the 5, even if it could fail. Yahoo: I have no visible dropouts. I used it together with a HRM RUN which also didn't have any dropouts (or at least no easily detectable even if I zoom)

Question to you that have issues:
Are you running in urban area where there are many Wifi accesspoints (near houses/apartments)? ANT are using the same frequency and one idea why some people tend to have lot of issues might be related to where they actually are training and the noise-level of the radiochannel.

Interesting. I have zero drop-outs with my stryd which I've now been using for over a month. First use was in a remote area, but right now I'm in a city environment with at least part of the track very much in a built-up area - and I have zero dropouts. In fact, pace, distance and lap pace tracking have improved massively since I use the footpod for distance and pace as opposed to GPS which I think suffers far more from buildings and tree cover than Garmin or others want to admit or make known.

I think I might be suffering from this issue with my new Fenix 5S. For example, see the attached image.

Jogging with a Garmin foot pod on the treadmill; completely steady state, I saw the pace all over the place according to the watch during the workout, and afterwards I can see that the stride length basically seems to be the problem.

It seems to be alternating between two completely different values, so for the steady cadence the implied pace is completely different. Is this possibly due to the foot pod connectivity fading in and out? I have the RD pod too and that seems to be locked in OK.
ciq.forums.garmin.com/.../1304613.png