-
Notifications
You must be signed in to change notification settings - Fork 30
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
Evolution - bind/clone issue #11
Comments
I wonder if this is related, I have an XM+ that I can't bind to. I flashed it with the FCC(International) D8 mode firmware and at the point where the bind occurs(green LED on and red LED flashing to acknowledge successful bind) both LED just illuminate and stay on, bind unsuccessful.. I have had this same behaviour with LBT and International rx firmware incompatibilities.. I can bind to my frsky beecore just fine! |
Oh..... That could explain it. I only have the international version. |
I should have an R-XSR in the post today with international FW on it I will do some testing with LBT-EU FW today and report back if I get the time.. |
@fishpepper, can you confirm if the Evolution code will work with the international firmware? Assume you are using the EU FW in Germany? Thanks |
I just got the r-xsr receiver with FCC FW this would not bind so I blew the LBT FW and got exactly the same result, no bind.. I fear the issue is deeper than just frsky protocol flavours.. My Taranis is running International FW and binds to my Beecore whoop fine as does this Openground based Evolution, my Taranis also binds to the International FW R-XSR but Openground on the Evolution won't... *shrugs.. |
Did you try with one of the older D8 only receivers? |
No I didn't, I realise now that you stated somewhere OpenGround was for D8 Rx's. Doh! However there is a D8 version f/w for the XM+ which I also had this same issue binding with.. Is D16 compatibility a huge hassle to implement? I see the whole micro market expanding and Rx's like the R-XSR / XM+ being a common place component. |
Someone is working on the implementation for it (recall that I saw it in a different thread) |
@fishpepper, I recompiled the latest master and tested binding and TXClone again.
Unfortunately I still have the same issue:
Bind mode: Put the RX into bind mode (2 solid LED's), as soon as I hit bind on the TX one RX led starts blinking as it should indicating that it receives the bind packets. However upon restart of both TX and RX, the RX simply blinks indicating no connection.
TX Clone: I tried that next. Put the Evolution in Clone TX mode, powered my taranis up and hit bind. The evolution started with the autocalibration etc and finished with "please switch off now".
After powering it back up the RX still could not connect (powering the taranis up makes it connect instantly to the taranis).
Any ideas on what I'm doing wrong? I assume that the TX module connections are fine given it can send and receive (at least looks like that from the tests above). Could there be a HW connection issue to the module which would not show up during bind but only in transmit operation?
Also you recommended to check the hoptable and place a while(1); after the debug print with the hop table for now. => can you point me at the right place for that? I checked the src but could not find the obvious place for the hoptable debug.
Thanks !
The text was updated successfully, but these errors were encountered: