Devo 7e doesn't bind with Spektrum Satellite

Hi all

I try to bind my Devo 7e with a Spektrum Satellite. On the Satellite i see a DSM2 sign. Here's what i did:
-I power on the Satellite and it flashes rapidly
-After pressing "bind" on the Devo, the Satellite LED turns off and flashes then at a slower speed
-Then, the Satellite LED turns off again. After that, it should turn on and remain steady, but it never does.

I tried several combinations in Cleanflight (SPEKTRUM1024 / SPEKTRUM2048 with different "spektrum_sat_bind" parameters), with exactly the same behaviour. On the Devo i tried DSM2 and DSMX. Nothing worked. Reinstalling Deviation on the Devo (according to this ) didn't work.

Has anyone an idea how I can solve this??
-Which protocol (1024/2048) and which spektrum_sat_bind parameter on Cleanflight?
-Which protocol on the Devo (DSM2/DSMX)?
-How can I do further investigation if it doesn't work?

I don't even know how to begin troubleshooting, or if the problem is on the Devo or the Satellite side...

I hope you can give me a hint on this.
donato

In my experience, the most common binding issue can be solved by clearing the Fixed ID in the Model Setup screen. Once you bind and you have a solid light, you can add a fixed ID.

I'm not an expert, but I have a grandkid so I have to act like one... YMMV! I have an OrangeRX RX111N satellite I just set up on Cleanflight 1.3. According to my reading, since I want DSMX, i used Spektrum2048; for DSM2 use Spektrum1024... so make that change to my notes below:

In my notes, I used this procedure for an F3Evo brushed controller:
Alternatively you can use the CLI and choose SPEK2048 (note the difference... it took me a while to catch that!)
To get the bind to happen through Cleanflight I found a really good tutorial. :
Let us know how it goes, and please correct anything I may have mis-stated!

Hey Deal57, thank you for your reply, you made my day..!

The Fixed ID was the problem, i didn't know that this value can cause problems . After changing thi ID to "none", binding was possible with the following values:

In Cleanflight:

• UART3 set to RX_SERIAL
• On the Receiver screen set to RX_Serial and SPEKTRUM1024 (for DSM2)
• CLI: set spektrum_sat_bind=7

On the Devo7e:

• DSM2
• Erase Fixed ID ("None")

Additional info:
I also tried to bind the satellite with DSMX (with SPEKTRUM2048, spektrum_sat_bind=8 or 9, and DSMX on the Devo), but that didn't work for me.


Thank you very much..!

i can confirm that with nightly builds i can use fixed ids on all my 5 sats, lemon orange and banggood without problem
the choice of fixed id is related on different settings of each model, so i can turn on a model but it wont bind if for mistake i forgot to choose right one.
its one of cons of x9r pro with dsmx module for example
even in 2048 with
set spektrum_sat_bind=9
and after bind
set spektrum_sat_bind=0

Thank you for your reply. I installed the latest 5.0.0 (stable) release. You mean it would be better to install the nightly? And it is stable enough?

@vlad_vy, what do you mean with "Deviation v5.0.0 build with latest protocols"?

I did not understand all you wrote. How can I get a 5.0.0 with latest protocols? Do I have to build it myself?

Ah, ok, everything clear now.. большое спасибо

Last question:
Can you tell me whats the difference between devo7e and devo7e-256 zip-files?