-
-
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
65 cyplus #77
Conversation
Wonderful ! I will test it right now, I incidentally needed to do a little bit of sport 😁 |
So ! After about half an hour of testing, here is my experience :
|
Just had a 10 min try just using the Fortius GUI and seems to work well thanks without any errors appearing in the console. I will try a more extensive test with Zwift after work this evening... |
I will take a look at the Target-rest; that was not the intention! |
Testing with CYCPLUS dongle on Raspberry PI. FortiusANT.2020-05-07 16-59-49.log First one reconnected immediatelafter calibration, three times. |
I think having the software reconnect for whatever reason is a 'good thing' because disconnects may happen and it saves having to restart FortiusANT manually. But IMHO we're expending resources to bodge something which is totally broken with these particular CYCPLUS dongles. The dongles just don't support continuous scanning. The CYCPLUS engineer has admitted they messed up and they've changed the hardware. See https://tacxfaqx.com/knowledge-base/cycplus-ant-stick/
Apparently from February 2020 on they've fixed it but I bought my two dongles mid April so I can only presume I got old stock. I imagine many will still get old stock for some time. And of course we can work around this in FortiusANT but we can't in Zwift or other closed source apps so if you're using two dongles, one is not going to work. My two dongles went back for a refund today. |
Hi I have added the detach_kernel_driver for Linux Note that, after reconnecting all channels must be reset as well. Please verify, so that I can merge the software. |
Hi all @ElDonad @mattipee @TrevorHunter @aegisdesign @martingeraghty @aegisdesign @iainhay Is this the max we can do for CYCPLUS? |
Yeah, I think this is the most we can do, considering these devices are broken... I had however no problem the Zwift side, at least no visible one, but at this point I think I'm going to try getting a working one from Cycplus ^^ In the meantime however, I see no more thing we can do to support these dongle... Apparently the stability of the connection varies between people, and yes the dongle doesn't crash if not paired. Anyway, thank you very much for the hard work, see you maybe on Zwift ! |
@ElDonad @mattipee @TrevorHunter @aegisdesign @martingeraghty @aegisdesign @iainhay
Based upon the investigations done by Elie and Matthew, combined with the invaluable lessons I learned from Matthew last night, error-recovery is implemeted for unwilling dongles.
At first, CYCPLUS dongles don't like the ResetDongle() command, other than at session-startup. So it is disabled.
Secondly, the dongle goes "offline" and must be reconnected. This is what FortiusANT now does: after an error, the dongle is found again and all channels are paired again. So it required some work.
In my situation (I have no CYCPLUS dongle) I can remove the dongle while running and pluggin in (even another one) and FortiusANT and ExplorANT continue to run.
So my request to you is to test this from the https://github.com/WouterJD/FortiusANT/tree/65-CYPLUS branch.
If results are positive, I will promote to the master.