Greetings
I have an NRF51422 QFAAEO running S210 Soft Device version 3.0.
I have written a Bootloader application that uses Ant-FS as the upload mechanism. During testing we noticed a strange behavior reproducible across multiple hosts / client combinations that we cannot explain. Hopefully you guys can explain if this is bug or feature.
We are using the Ant-FS reference Host project for development. When I run this application, It reports itself as "SW Version: AML1.300, Library version: AKX0.309 ". We are using Ant USB sticks of 3 different manufacture so don't believe that is a factor.
On the host application, when I select "Options" and then select the "Ant Channel" tab, I have a group of options labeled "RF Frequency" with text box fields for "Search Frequency" and "Connect Frequency" as well as a check box labeled "Random Connect Frequency". The value of these options plays a deterministic role in whether the host can successfully upload to the client.
If the checkbox is unchecked and the search frequency is the same as the connect frequency (the default if it has never been changed), our upload test of uploading a 42KB bin file in bursts of 1KB fails roughly 90% of the time.
If those two frequencies are far apart, for example 55 and 99, the exact same test succeeds 95% of the time. If I bring the two frequencies closer and closer together, the failure rate gets proportionately higher.
Examining the logs from the host for the failed attempts shows the client is simply not responding to multiple Ant-FS messages from the host.
Why would sharing a frequency between the "connect" and "search" fields cause interference? There are no other Ant devices running when we conduct these tests and the range of the client to host is just a few inches.
Is this bug or feature?
I am cross posting this to the "This Is Ant" forums since it is asking about their provided software. Link to same thread on Ant Dev Forums.
David
