<p>Okay, I solved it: I had installed the EU version of OpenTX, but I hadn't flashed the internal module on the transmitter. When I did that it worked flawlessly.</p>

CC BY-SA 4.0
2020-04-15T11:05:24.943Z
2020-04-15T11:05:24.943Z
Hannes Hultergård
<p>Another potential cause for not being able to bind is having a different radio firmware on the receiver vs the transmitter module. I recently ran into this issue with some of my setups. The RX was on 2.X.X firmware, which FrSky enabled some minor attempts at encryption to discourage unauthorized receivers and transmitters.  This firmware is NOT backward compatible with the 1.X.X radio firmware, so if your internal module on your transmitter is not updated to 2.X.X firmwares it WON'T bind. You will need to upgrade your internal radio module to the correct firmware as well. You can <a href="https://www.frsky-rc.com/download/" rel="nofollow noreferrer">find the current 2.X.X firmwares here</a> if needed.  Keep in mind if you upgrade you'll need to upgrade ALL your RXs in all your quads, and you won't be able to go back unless you downgrade ALL your RXs and radio firmware again. </p>

<p>Also, it's worth pointing out that for all their struggles, within a few weeks there was an update available for the open-source multi-protocol modules that allows binding to the 2.X.X firmware RXs. So, in the end, they've caused a lot of inconvenience for users and not accomplished their goals.  Make of that what you will.</p>

CC BY-SA 4.0
2020-04-15T12:45:55.640Z
2020-04-21T03:42:06.110Z
2020-04-21T03:42:06.110Z
QuadMcFly
<p>As well as the previously mentioned hardware and mode issues, some people report that having your transmitter too close to your receiver during binding can cause ‘washout’, which prevents binding as the signal is too ‘intense’ (for lack of a better word) to be understood.</p>

<p>I’d try moving your transmitter 1.5m from your receiver and trying again.</p>

CC BY-SA 4.0
2020-04-15T11:04:10.643Z
2020-04-15T11:04:10.643Z
Drones and Whatnot
<p>I'm trying to bind an r-xsr to a qx7s, but the receiver shows a solid red, green and blue light and won't bind.</p>

<p>I have updated the receiver to version 2.1.0 LBT and the transmitter to the EU version of OpenTX 2.3.7.</p>

<p>Is there a known problem with any of this firmware, or is there another problem?</p>

<transmitter><taranis><receiver>
r-xsr won't bind to qx7s
Hannes Hultergård
# r-xsr won't bind to qx7s

(Asked by: username_0 on 2020-04-15)

I'm trying to bind an r-xsr to a qx7s, but the receiver shows a solid red, green and blue light and won't bind.

I have updated the receiver to version 2.1.0 LBT and the transmitter to the EU version of OpenTX 2.3.7.

Is there a known problem with any of this firmware, or is there another problem?

**Tags:** transmitter, taranis, receiver

---

## 3 answers

### Answer by username_0 on 2020-04-15. Score: 4 | Accepted answer

Okay, I solved it: I had installed the EU version of OpenTX, but I hadn't flashed the internal module on the transmitter. When I did that it worked flawlessly.


---

### Answer by username_1 on 2020-04-15. Score: 3

Another potential cause for not being able to bind is having a different radio firmware on the receiver vs the transmitter module. I recently ran into this issue with some of my setups. The RX was on 2.X.X firmware, which FrSky enabled some minor attempts at encryption to discourage unauthorized receivers and transmitters. This firmware is NOT backward compatible with the 1.X.X radio firmware, so if your internal module on your transmitter is not updated to 2.X.X firmwares it WON'T bind. You will need to upgrade your internal radio module to the correct firmware as well. You can [find the current 2.X.X firmwares here](https://www.frsky-rc.com/download/) if needed. Keep in mind if you upgrade you'll need to upgrade ALL your RXs in all your quads, and you won't be able to go back unless you downgrade ALL your RXs and radio firmware again.

Also, it's worth pointing out that for all their struggles, within a few weeks there was an update available for the open-source multi-protocol modules that allows binding to the 2.X.X firmware RXs. So, in the end, they've caused a lot of inconvenience for users and not accomplished their goals. Make of that what you will.


---

### Answer by username_2 on 2020-04-15. Score: 2

As well as the previously mentioned hardware and mode issues, some people report that having your transmitter too close to your receiver during binding can cause ‘washout’, which prevents binding as the signal is too ‘intense’ (for lack of a better word) to be understood.

I’d try moving your transmitter 1.5m from your receiver and trying again.


---

