CIQ platform vs watch platform BLE/ANT+ data stream

up...

I am not sure I understand your questions but I will take a shot. Sorry if I miss the mark.
1. I'm sure it is possible that an App or Datafield could interrupt normal ANT data stream flow during an activity. Setting the hi-priority search timeout incorrectly on a generic ANT channel will do this. I'm not sure if watch faces can do this since they don't have generic ANT Channels. I don't know if this would have an effect on BTLE communications though. I suspect it might if the hardware uses the same radio for both BTLE and ANT

It didn't let me make a long post so here's the rest.

2. My understanding is that the CIQ platform uses the same radio as the watchs platform.
3. When there are multiple sources of the same information like Cadence that could come from a Power Meter and from a Cadence sensor, the watch gives priority to one. In the case of cadence, I think it will use the power meter cadence data and ignore cadence sensor cadence data. It will do this the same way for both native data fields and CIQ data fields that acquire the data via getActivityInfo. The only way to get the cadence data from the cadence sensor when both sources are present would be to use a CIQ datafield with a Generic ANT channel. Having 2 sources of Cadence data should not corrupt the FIT file though.

thank you for the reply MoxyRoger :)

DCRainmaker reported Garmin acknowledging Fenix 5/5s ANT+ problems.
My initial quest has been answered by this acknowledgment from Garmin.

QUOTE:
?We are aware that there are reports of ANT+ reception issues, particularly with some specific devices.
Garmin is looking at ways to improve the performance, but there does not appear at this time to be a ?quick fix? software update.
We do anticipate future designs to improve support for identified third-party devices that are not consistently meeting expectations today.?

... continue

...

1.It is good to know that Apps and Datafields also can interfere with ANT data streams during an activity.
Do you have any knowledge this could happen even when a datafield is not set up in a screen, during an activity.
For instance in the earlier mentioned datafield (auxiliary heart rate) and device ID not set up in the datafiled.

... continue

...

2. Noted.

... continue

...

3.You are correct that the combined power/cadence data has priority over the singel cadence data.(my experience also).
How does the watch handle this single cadence data when both power/cadence and cadence sensors are present.
Does it sync with the cadence stream channel and (could) loose processing time or is it ignoring this channel compleet.
Good to know one can log this second channel via CIQ.

The End ;)