Binding Issues with OrangeRX R615X

Ok so Im new at this so the answer might be very obvious. Im working on my first quad build and bought an OrangeRX R615x. Im trying to get it to bind with my 7e. Im running 4.0.1 as well as an additional module installed and working perfectly for my Syma quads. Im following bind instructions from here :

and my lights are all blinking just like in his video, even resting at a steady on light, except my transmitter never fully connects, it just sits on the "Binding Model, Press ENT to stop, 0 seconds left"

as it just stays on this screen, the RX stays the steady on light just like in the video when is supposed to be connected.

Anyone have any advice or thoughts? very frustrating

There's a known bug that causes the box to not vanish when after things bind. Just hit ENT or EXT, and see if you can control the aircraft.

I get that all the time, a button press doesn't fix it for me, I have to shut everything down and then power it back up and re-bind. Sometimes 3 or 4 times. Once you get the 3-beep tone (from the Tx) you're bound.


What's strange is the bind light on the rx comes on, the model thinks it's bound and stops trying but the devo still displays "binding to ...", just try a few times till you get the bind confirmation toneout from the tx and be good.

Does moving the sticks exit the bind dialog?

Use your own fixed ID. Not the 123456......Then there is no request for bind or something else.
The RX615 binds within the same second the devo is switched on.

Edit:
I am using DSMX, so there is no slow flashing.....

Cereal_Killer wrote: I get that all the time, a button press doesn't fix it for me, I have to shut everything down and then power it back up and re-bind. Sometimes 3 or 4 times. Once you get the 3-beep tone (from the Tx) you're bound.

What's strange is the bind light on the rx comes on, the model thinks it's bound and stops trying but the devo still displays "binding to ...", just try a few times till you get the bind confirmation toneout from the tx and be good.

I get this behavior on my Proto X, using the hubsan X4 protocol. The quad lights stop blinking, the Tx stays in "binding to..." mode. Buttons exit the box, but the quad doesn't respond. The quad has to be shut off to go back to bind mode, and it won't bind properly unless I turn off the Tx as well.

So possibly this isn't a DSM issue, but somewhere in the bind code.

It slipped my mind but I also get this on my protoX (both of them actually). So to reiterate- both my protoX's and my Orange R615 satellite (multiwii) do this same behavior. The ProtoX's actually do it much more, nearly every time I fly one of them will do it, the Orange however only does it every once in a while, maybe a few times a week total (out of 25-35 power up's in that time).

I'll be able to add more data shortly as I have a CC3D on route (will also be using the R615x satellite). I'll go ahead and try it with the same exact rx unit as I'm getting the issue with on multiwii. If I have the issue there I'll make a new thread about it.