Problems with Ant+ connectivity

My speed/cadence sensor which a Giant ride sense connects but once riding it instantly disconnects. The sensor connects perfectly to my edge 500 which I ride with too so I know it's not the sensor playing up. I bought the Fenix 5 black sapphire on Friday and have done 2 rides with the same results. I've removed the sensor from the watch , changed the battery but it still does the same thing. All my other ant+ sensors connect to the watch perfectly and stay connected. I have the hrm-run strap, a Garmin foot pod , Tempe and all stay connected except for the Giant ride sense. It seems as though the distance from the sensor to my left wrist is too far. Any thoughts?

When I got my Fenix 5x with software 2.40 I paired my Stages Power meter via Bluetooth which worked quite well. In the meantime I'm on Beta 2.95. The first week on Beta 2.95 the sensor still worked almost flawlessly. However since a few days I had problems to connect with the sensor and I removed the sensor from the watch and tried to pair it again. Now the only option I get is to pair the sensor via ANT+ which leads to unacceptable continuous drop outs. The connection via Bluetooth is not offered anymore. Is there a specific procedure or trick to add sensors via Bluetooth? Maybe Bluetooth pairing is a problem with Beta 2.95. Did anybody add Bluetooth sensors with Beta 2.95? Thanks for your comments.

Tempe

I've just bought a Garmin Tempe to go with my F5 sapphire and it is disconnected more than it is connected. It seems to be okay when the watch screen is showing the temperature readout but as soon as the watch reverts to the watch face (showing the time) then it loses connectivity to the Tempe. Is this an issue with connectivity, as being discussed in this thread? or is it the way that the Tempe pod works? I haven't used it for an activity yet, could that be another factor?

I've just bought a Garmin Tempe to go with my F5 sapphire and it is disconnected more than it is connected. It seems to be okay when the watch screen is showing the temperature readout but as soon as the watch reverts to the watch face (showing the time) then it loses connectivity to the Tempe. Is this an issue with connectivity, as being discussed in this thread? or is it the way that the Tempe pod works? I haven't used it for an activity yet, could that be another factor?

That is working as intended - the Tempe is only queried when it's being actively used. Since the Tempe only sends out data once every minute, it can take some time to show a result in the temperature widget. Once you record an activity, you get temperature data every minute.

That is working as intended - the Tempe is only queried when it's being actively used. Since the Tempe only sends out data once every minute, it can take some time to show a result in the temperature widget. Once you record an activity, you get temperature data every minute.

Thanks for clarifying that, I should have guessed that would be the case but in my rush to play with my new toy I wasn't thinking it through.

Thanks again.

Thanks for clarifying that, I should have guessed that would be the case but in my rush to play with my new toy I wasn't thinking it through.

I know that feeling all too well...;)

That is working as intended - the Tempe is only queried when it's being actively used. Since the Tempe only sends out data once every minute, it can take some time to show a result in the temperature widget. Once you record an activity, you get temperature data every minute.

I agree it's the expected behaviour, but I'm going to nitpick your explanation if I may :)

The Tempe sends data every two seconds, alternating between two different messages, see this thread for lengthy details.
Most sensors send data four times a second, and it tends to take watches eight times as long to synchronise with the Tempe transmission timing as a result.
The Tempe only updates the temperature once a minute, which is why people think it transmits once a minute, but it actually transmits the same pair of messages 15 times during that minute.

I agree it's the expected behaviour, but I'm going to nitpick your explanation if I may :)

The Tempe sends data every two seconds, alternating between two different messages, see this thread for lengthy details.
Most sensors send data four times a second, and it tends to take watches eight times as long to synchronise with the Tempe transmission timing as a result.
The Tempe only updates the temperature once a minute, which is why people think it transmits once a minute, but it actually transmits the same pair of messages 15 times during that minute.

Thanks for the clarification! :)

Pacar blue

Had a chat with the hotline here in Switzerland regarding weak ANT connectivity. Apparently Garmin is aware of ANT problems and they mentioned to wait for a SW update...

Interestingly, the guy on the hotline mentioned, that they are not aware of any GPS and Pace accuracy issues :confused:. I told him to check this forum with more than 600 entries in the "GPS accuracy" thread...

The latest beta (3.11) supposedly has doubled the range of BLE, although I have no information either way about ANT+.

The latest beta (3.11) supposedly has doubled the range of BLE, although I have no information either way about ANT+.

No improvements for me with beta 3.11. Still massive dropouts. I will return my f5 and get a 935. I have somehow the feeling , that the F5 just has the same entry than the f3 or the 620. I just want a watch which is working, and don't want to worry.