-
-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ANT dongle not disconnected properly, then reported "No (free) ANT-dongle found" #203
Comments
First reported by @RichardE-UK. I have this issue now and then myself; to be investigated and suggestions welcome. |
@switchabl do you have suggestions how to properly close the ANTdongle so that it does not remain connected? |
@WouterJD Normally that should happen automatically (but I think I've had this issue a couple of times myself). Maybe calling |
I've been testing a Tacx Fortius using Windows and Dynastream Ant dongle today and have come across the same error report. FortiusANT worked initially but is now reporting "No (free) ANT-dongle found" despite not opening a CTP and rebooting PC. I've used Task Manager to close any obvious processes but with no success. I wanted to let you know @WouterJD to provide another data point. |
@MeanHat @switchabl The "only" way to reset is to remove the dongle and re-insert. |
@switchabl I have added:
and will see whether this helps. |
The additional "cleanup" code does not change the behaviour. |
THis happens and no additional suggestions received. Closed |
You just had to make sure that each of the Apps had fully disconnected from the dongle and there were no "orphaned" processes hanging about using Task Manager if required
I tried running Bkool, RouvyAR and Zwift at this point but (of course) they couldn't see the brake unit as I only had the one Ant+ dongle. The second dongle turned up this morning and I have just successfully run pairing of the brake unit with all three Apps. It is the case that swapping between the Apps can sometimes leave orphaned processes, and I needed to "end task" on a few occassions to release the new Ant+ dongle if the App had been closed, but had some components still running in the background.
The text was updated successfully, but these errors were encountered: