Or is it the case that most ANT-FS clients also implement an ANT+ profile (it's a sport watch or something) and we first look for broadcast messages from the device using the standard ANT+ network key and RF frequency (57) then send an ANT-FS link request and request the client to change RF frequencies to avoid interference with other devices? (Basically follow section 8 from the ANT-FS Technical Specification)
After some more digging on this forum it looks like the standard RF frequency might be 50? Or is that just the frequency that Garmin uses?
The next issue/wonkyness I'm running into is that the ANT-FS spec states that the client shall broadcast their beacon on every channel period. My Garmin Forerunner 910xt though seems to be configured for the fastest channel period of 4096 but it only broadcasts 16 beacons in a row then sleeps for a few seconds. The sleeping causes my ant slave device to report a bunch of EVENT_RX_FAIL_0x02 messages then eventually fall back into search mode. Not sure yet if that's necessarily a problem because it does seem to pick the client right back up the next time it broadcasts it's beacon. My concern is that as I implement more of the ANT-FS stack the failure is going to cause some channel state that I need to be lost.
