Hello everyone
I have a strange problem , and cannot figure out if it's a bug on my side , in ANT DLLs (c# / .Net), or in the sensors device profile.
I can succesfully start a channel in "background scanning" mode to detect ANT sensors around.
I can successfully connect and retrieve data from several kind of sensors, including HR with Running Dynamics profile. (Both HR and Running dynamics channels are working as expected)
But, I noticed a problem :
If I previously did a background scan in my program , then I'll always get a "Fail" return code when I send the 0x74 data page to the HR/Rundyn sensor to start a Running Dynamics session. Even if the "HR" channel is running fine and transmitting data.
It doesn't matter if the sensor was active or not during the scan, in both cases (sensor started and detected during the scan, sensor not started during the scan) I'll always have the "Fail" return code when sending datapage 0x74.
The "scan " channel has already been closed and disposed when I try to send messages to the HR/Rundyn sensor in a different channel.
I also tried sending the "close Running dynamics" message (0x75) , with same results.
If I restart my program (which releases the ANT device), then I can connect and send messages to the HR/Rundyn sensor correctly.
And If I do the following:
-Start program, pair with HR/Rundyn belt => working ok
- Unpair the bet, release channels
-Start backgroudn scan => the scan works but the HR/Rundyn belt won't be detected
-Stop and release background scan
-Pair again the HR/Rundyn belt => still working correctly
It seems to me there is an uncompatibility between scanning and running dynamics, If the scanning sees the belt first then the pairing won't be succesfull, if the pairing sees the belt first then the scanning won't see it.
I observed this problem with a Garmin Belt, and with a SimulANT sensor.
I cannot reproduce it with SimulAnt as a "display", because I did not find a way to start a "background scan" using this software.
This problem doesn't appear with other kind of devices, for instance I can successfully send commands to a FE-C device after having seen it during a scan.
Anyone have any idea of what could be happening ?
Thanks
