Problems with Ant+ connectivity

Hi chatlow,

the first three digits of the SN are representing the model. E.g. 537 is the silver version with blue band, 536 is slate grey with black band, ...
So I think you cannot compare your new with the old device as both are two different types.
I also asked support for serial number break for different models but they said that they don't have it.
Maybe you can check the folder "EVNTLOGS", open the txt-file(s) and check what the oldest date is you can find inside. See my post above yours. But I have no confirmation so far if this is the correct way to identify.

Sorry to keep resurrecting this thread but want to check some potential dropouts. I had 1 message on my replacement F5 sapphire during a ride last week saying HRM connected and then again for my cadence sensor yesterday. Not a huge issue but never had that before and hope it was just a reconnection blip. Having quickly tested in the house ,the connection is solid and only disconnects when I stand > 5 meters away. Bluetooth to my phone is fine up to around 10-15 meters.

Garmin confirmed the new replacement sapphire f5 I have received is from the new production line so it has the improved ant+ module and altitude fix.

Only other thing - with a cadence sensor - is it normal for a unit to be 'not connected' the sensor when not spinning, say when stationary or 30 seconds? Noticed this when seeing that message then going to settings - sensors and seconds after going to that menu is connected again.

Thanks,

Chatting to Garmin again, I was able to confirm serials after 010-01688-00 536132248 should not have the issue.

Hi, mine is 536121xxx and Device ID 3964380xxx. I can't find anything that looks like the first part of the number you're mentioning anywhere (in the watch's About-section, in Garmin Connect Mobile, Garmin Connect Web or Garmin Express). M/N is AA3119-00, FCC ID is A3119-00, IC is 1792A-A311900. Production date looks like 22nd November 2017 from the dates of files/folders on the watch.

I have a Tacx HR belt, a Tacx Ant+ BLE/Ant+ Speed/Cadence sensor, a Garmin Footpod, and they all seem to work flawlessly, with a range of at least 3 to 5 meters before any of them disconnects. Tried the Tacx sensor over both Ant+ and BLE, and BLE range seems to be quite a bit longer, even through a couple of walls (drywall plates). Connection between my Fenix 5 and my Xperia Z5 phone can drop out sometimes, but I tested in the restaurant where I worked and it stayed connected across the whole restaurant, about 15 meters. My apartment, where it disconnects sporadically from time to time, has a multitude of wireless signals, like 20-30 wireless networks from various neighbors, all kinds of wireless gadgets etc. so that could be the reason.

However I just bought a Humon Hex Muscle Oxygen monitor, and it had a Ant+ range of only about 25 centimeters before it disconnected! They sent me a replacement, and the second one has about 80 cm of range, so still useless for any activity where my hand isn't pretty close to my thigh. The Humon Hex is a pretty new product, so I suspect they have a problem with their Ant+ signal strength, but since my serial is before the one mentioned in the quote above, I just wondered if I might have a connection problem in the watch too.

I'm going to get an Edge 520 Plus one of the coming days, so I'll check with that and report back here.

Would be cool if someone from Garmin could come on here and give us some info, but I guess they don't wanna confirm anything in public so that they have to recall 1000s of watches before a certain serial number or production date...


Cheers,
Audun

tip...
when one wants to check for older or newer production version, one has to compare the device_id's
device_id is also found in the garmindevice.xml file on your Garmin device
do not make this device_id public

OnlyTwo,
Can you point me to where I can check my device Id against a production timeline? Im curious as to my F5 saphire's build date.

Sorry to keep resurrecting this thread but want to check some potential dropouts. I had 1 message on my replacement F5 sapphire during a ride last week saying HRM connected and then again for my cadence sensor yesterday. Not a huge issue but never had that before and hope it was just a reconnection blip. Having quickly tested in the house ,the connection is solid and only disconnects when I stand > 5 meters away. Bluetooth to my phone is fine up to around 10-15 meters.

Garmin confirmed the new replacement sapphire f5 I have received is from the new production line so it has the improved ant+ module and altitude fix.

Only other thing - with a cadence sensor - is it normal for a unit to be 'not connected' the sensor when not spinning, say when stationary or 30 seconds? Noticed this when seeing that message then going to settings - sensors and seconds after going to that menu is connected again.

No, that is not normal. I recommend replacing the batteries on your sensors.

Any chance that this gets corrected in firmware or that a general recall is issued?

Until this is done I'm not ever buying a Garmin product again, as I have been swindled into buying a defective product.

This is a hardware issue and can't be corrected via firmware. The "correction" is the new Fenix 5 plus series.
There is no recall and no plan for one from what I've been told.

Any chance that this gets corrected in firmware or that a general recall is issued?

Until this is done I'm not ever buying a Garmin product again, as I have been swindled into buying a defective product.

This is a hardware issue and can't be corrected via firmware. The "correction" is the new Fenix 5 plus series.
There is no recall and no plan for one from what I've been told.

not quite true. Yes, the Fenix 5 Plus series has the issue fixed but Garmin have also fixed the hardware on the original F5 series of watches and replaced their stock with these. I had my F5 sapphire unit RMA'd a over a month ago by them and all seems great. BT gets around 30 ft in range and ant+ for me is fine over 10 feet (using PM, HRM, Spd/Cad)

Best bet is to contact Garmin about it and go from there. Good luck

I've contacted Garmin support several times, and have never gotten that answer. The best I've gotten them to admit is that there are issues with third party sensors, and there are no hardware updates to address them. That was 2 months ago, and I've since given up.