I just bought an eachine QX65 but I can't bind it to my controller.

This is the information:
Radio control: FrSky ACCST Taranis Q X7 international version
Tinywhoop: Eachine QX65 Frsky reciever

What I have tried so far is to unchecked the eu checkbox in order to get the D8 mode available in the radio control but unfortunately it did not bind either.

Should I try to bind it via command line in betaflight?

Do you guys have any idea of what may be happening and what should I do?

Everything you have done so far is logical and should work. You can't bind D8 mode receivers with a CLI command so you have to use the bind button on the FC of the QX65.

The QX65 is listed has being supplied with a Beecore V2.0 FC. There are actually two versions of that FC, a D8 mode one and a D16 mode one. I'm wondering if you actually have the D16 mode one in your QX65. Try binding it in D16 mode if you've not already tried doing that.

I assume you've installed the 170317 version of firmware on the internal XJT module of your QX7?

If binding in D16 mode still doesn't work then please run both the "dump" and "diff all" commands in the Betaflight Configurator CLI tab and copy/paste the results back here.

(24-Oct-2021, 04:45 PM)SnowLeopardFPV Wrote: Everything you have done so far is logical and should work. You can't bind D8 mode receivers with a CLI command so you have to use the bind button on the FC of the QX65.

The QX65 is listed has being supplied with a Beecore V2.0 FC. There are actually two versions of that FC, a D8 mode one and a D16 mode one. I'm wondering if you actually have the D16 mode one in your QX65. Try binding it in D16 mode if you've not already tried doing that.

I assume you've installed the 170317 version of firmware on the internal XJT module of your QX7?

If binding in D16 mode still doesn't work then please run both the "dump" and "diff all" commands in the Betaflight Configurator CLI tab and copy/paste the results back here.

Hi SnowLeopardFPV,
Thank you so much for the response.

"I'm wondering if you actually have the D16 mode one in your QX65. Try binding it in D16 mode if you've not already tried doing that."
I do have D16 mode in the taranis Q x7 and I did try to bind it with it but it doesn't work either.

"I assume you've installed the 170317 version of firmware on the internal XJT module of your QX7?"
Yes the remote control seems to have the XJT_NONEU_170317.frk firmware installed and I don't recall having updating it.

"If binding in D16 mode still doesn't work then please run both the "dump" and "diff all" commands in the Betaflight Configurator CLI tab and copy/paste the results back here."
Here I leave the output of the commands in the files (dump_results.txt & diff_all_results.txt)

All of your Betaflight settings are correct and fine.

What is the binding procedure that you're using?

Do you have another quad with a D8 or D16 receiver that you're able to successfully bind your QX7 with?

(24-Oct-2021, 07:18 PM)SnowLeopardFPV Wrote: All of your Betaflight settings are correct and fine.

What is the binding procedure that you're using?

Do you have another quad with a D8 or D16 receiver that you're able to successfully bind your QX7 with?

I have the (mobula hd 7) but is not working properly it does bind to the radio but when I am trying to fly it, it's not stable and sometimes it lose the binding, that's why I bought two eachine QX 65 thinking it would be easier etc...

About the (modula hd 7) I had a lot of troubles binding it but mainly because I bought it with the wrong receiver.
https://fpvdronepilots.com/threads/mobul...522/page-2


could it be that the problem is related to this one?


It's very strange because on banggood they do say it works with taranis q 7.

What do you recommend me to do? Buy a new remote controller?

(24-Oct-2021, 07:18 PM)SnowLeopardFPV Wrote: All of your Betaflight settings are correct and fine.

What is the binding procedure that you're using?

Do you have another quad with a D8 or D16 receiver that you're able to successfully bind your QX7 with?

Is this the problem I have?
would this module help me to bind easily to any tiny whoop?

https://www.banggood.com/IRangeX-IRX4-LI...rehouse=CN

https://www.banggood.com/FrSky-2_4GHz-XJ...rehouse=CN

You shouldn't need an external module. The ACCST version of the QX7 with the 170317 firmware installed natively supports binding to D8 mode receivers. In addition to D8, the 170317 firmware version includes ACCST D16 1.x.x (not ACCST D16 2.x.x).

I have an X9D+ SE (ACCST version) with the 170317 firmware installed and have bound it to two of my tiny whoops in D8 mode with no problems. Also keep in mind there there is no such thing as EU-LBT or FCC versions of D8 like there is with D16. There is only one global type for D8 mode which means there are less complications to worry about.

At the moment we don't know if the problem is with the receiver in the QX65 or with the internal module in your QX7.

I would try re-flashing the internal XJT module on your QX7 with the 170317 firmware in case there is some corruption in the firmware. I would also re-flash OpenTX 2.3.14 to your transmitter as well for the same reason. When you flash OpenTX, do it with the transmitter completely switched off (just connect a USB cable to it and flash it from OpenTX Companion). When you do it that way, the OpenTX bootloader will also get updated at the same time because I notice you are currently on bootloader version 2.3.0 but OpenTX is on version 2.3.14. Sometimes that version mismatch can cause strange issues, so it is best to keep them in sync.

It might also be worth re-flashing Betaflight 3.2.2 to the FC as well ensuring that the "Full chip erase" option is switched on. If you do that, make sure you save a "diff all" of your current setting first so you can restore the original Betaflight settings again afterwards.

(24-Oct-2021, 11:04 PM)SnowLeopardFPV Wrote: You shouldn't need an external module. The ACCST version of the QX7 with the 170317 firmware installed natively supports binding to D8 mode receivers. In addition to D8, the 170317 firmware version includes ACCST D16 1.x.x (not ACCST D16 2.x.x).

I have an X9D+ SE (ACCST version) with the 170317 firmware installed and have bound it to two of my tiny whoops in D8 mode with no problems. Also keep in mind there there is no such thing as EU-LBT or FCC versions of D8 like there is with D16. There is only one global type for D8 mode which means there are less complications to worry about.

At the moment we don't know if the problem is with the receiver in the QX65 or with the internal module in your QX7.

I would try re-flashing the internal XJT module on your QX7 with the 170317 firmware in case there is some corruption in the firmware. I would also re-flash OpenTX 2.3.14 to your transmitter as well for the same reason. When you flash OpenTX, do it with the transmitter completely switched off (just connect a USB cable to it and flash it from OpenTX Companion). When you do it that way, the OpenTX bootloader will also get updated at the same time because I notice you are currently on bootloader version 2.3.0 but OpenTX is on version 2.3.14. Sometimes that version mismatch can cause strange issues, so it is best to keep them in sync.

It might also be worth re-flashing Betaflight 3.2.2 to the FC as well ensuring that the "Full chip erase" option is switched on. If you do that, make sure you save a "diff all" of your current setting first so you can restore the original Betaflight settings again afterwards.

I will try what you proposed and I let you know.

Thanks for the help.

(24-Oct-2021, 11:04 PM)SnowLeopardFPV Wrote: You shouldn't need an external module. The ACCST version of the QX7 with the 170317 firmware installed natively supports binding to D8 mode receivers. In addition to D8, the 170317 firmware version includes ACCST D16 1.x.x (not ACCST D16 2.x.x).

I have an X9D+ SE (ACCST version) with the 170317 firmware installed and have bound it to two of my tiny whoops in D8 mode with no problems. Also keep in mind there there is no such thing as EU-LBT or FCC versions of D8 like there is with D16. There is only one global type for D8 mode which means there are less complications to worry about.

At the moment we don't know if the problem is with the receiver in the QX65 or with the internal module in your QX7.

I would try re-flashing the internal XJT module on your QX7 with the 170317 firmware in case there is some corruption in the firmware. I would also re-flash OpenTX 2.3.14 to your transmitter as well for the same reason. When you flash OpenTX, do it with the transmitter completely switched off (just connect a USB cable to it and flash it from OpenTX Companion). When you do it that way, the OpenTX bootloader will also get updated at the same time because I notice you are currently on bootloader version 2.3.0 but OpenTX is on version 2.3.14. Sometimes that version mismatch can cause strange issues, so it is best to keep them in sync.

It might also be worth re-flashing Betaflight 3.2.2 to the FC as well ensuring that the "Full chip erase" option is switched on. If you do that, make sure you save a "diff all" of your current setting first so you can restore the original Betaflight settings again afterwards.

Hi SnowLeopardFpv,
I have done some of the things you told me but it still doesn't work.

What I did & what I did not:
I took one of the two QX65 I have and I updated it to the betaflight 4.0.6. Now I just read again your comment and what you wanted me to do is to re-install/re-flash with the same version as the original Betaflight 3.2.2 right? should I give a try?

I have also updated the QX7 with the latest OpenTX version following this tutorial.


I also realize that I did not re-flash the internal XJT module of my QX7, should I do it by downloading it from here and following that tutorial right?
https://www.frsky-rc.com/xjt/
https://blog.dronetrest.com/flashing-fir...a-taranis/


Don't you think I would save myself time and headache by buying the module XJT-lite? or you still think it may not work?

(10-Nov-2021, 11:42 PM)thedroneracingpilot Wrote: What I did & what I did not:
I took one of the two QX65 I have and I updated it to the betaflight 4.0.6. Now I just read again your comment and what you wanted me to do is to re-install/re-flash with the same version as the original Betaflight 3.2.2 right? should I give a try?

Being on a later version of Betaflight that is available for your FC shouldn't make any difference. The receiver should still work any version. All of your Betaflight settings still look correct in that new version.

(10-Nov-2021, 11:42 PM)thedroneracingpilot Wrote: I also realize that I did not re-flash the internal XJT module of my QX7, should I do it by downloading it from here and following that tutorial right?
https://www.frsky-rc.com/xjt/
https://blog.dronetrest.com/flashing-fir...a-taranis/

Yes, I would try (re)flashing the ACCST 1.x.x firmware to the internal XJT module on your QX7. Make sure you click on the DOWNLOAD link in the "History firmware DOWNLOAD (not compatible with v2.x.x)" at the bottom of the Firmware section. That will download the 170317 firmware version which is the one you need. Make sure you flash the NONEU version of the firmware because the QX65 will have an FCC version of the receiver firmware on it.

(10-Nov-2021, 11:42 PM)thedroneracingpilot Wrote: Don't you think I would save myself time and headache by buying the module XJT-lite? or you still think it may not work?

You shouldn't need to do that. The external XJT-Lite module is exactly the same as the XJT module inside your QX7 so if your internal module isn't binding then I don't see how an external module of the same would. It's quite possible that the issue is actually to do with a hardware fault on the receiver in the QX65.

(12-Nov-2021, 12:26 AM)SnowLeopardFPV Wrote: Being on a later version of Betaflight that is available for your FC shouldn't make any difference. The receiver should still work any version. All of your Betaflight settings still look correct in that new version.


Yes, I would try (re)flashing the ACCST 1.x.x firmware to the internal XJT module on your QX7. Make sure you click on the DOWNLOAD link in the "History firmware DOWNLOAD (not compatible with v2.x.x)" at the bottom of the Firmware section. That will download the 170317 firmware version which is the one you need. Make sure you flash the NONEU version of the firmware because the QX65 will have an FCC version of the receiver firmware on it.


You shouldn't need to do that. The external XJT-Lite module is exactly the same as the XJT module inside your QX7 so if your internal module isn't binding then I don't see how an external module of the same would. It's quite possible that the issue is actually to do with a hardware fault on the receiver in the QX65.

Yes, I would try (re)flashing the ACCST 1.x.x firmware to the internal XJT module on your QX7. Make sure you click on the DOWNLOAD link in the "History firmware DOWNLOAD (not compatible with v2.x.x)" at the bottom of the Firmware section. That will download the 170317 firmware version which is the one you need. Make sure you flash the NONEU version of the firmware because the QX65 will have an FCC version of the receiver firmware on it.

I have flashed my taranis Q x7 ACCST with the internal XJT 170317 non-eu and still doesn't work
Any more ideas?


You shouldn't need to do that. The external XJT-Lite module is exactly the same as the XJT module inside your QX7 so if your internal module isn't binding then I don't see how an external module of the same would. It's quite possible that the issue is actually to do with a hardware fault on the receiver in the QX65.

I understand now, you mean that this module XJT-Lite would give me the D8 mode if didn't have it. I guess this module would be for people who bought the taranis q x7 ACCESS right?

(13-Nov-2021, 10:51 PM)thedroneracingpilot Wrote: I have flashed my taranis Q x7 ACCST with the internal XJT 170317 non-eu and still doesn't work
Any more ideas?

Maybe the QX65 has a hardware issue with the receiver. The only way to confirm or rule that out would be to try binding your QX7 to a different quad to see if doing that is successful or not.

(13-Nov-2021, 10:51 PM)thedroneracingpilot Wrote: I understand now, you mean that this module XJT-Lite would give me the D8 mode if didn't have it. I guess this module would be for people who bought the taranis q x7 ACCESS right?

Yes, that would be one reason Another reason that an external XJT module can also be useful is where the internal module is on one region of firmware (i.e. EU-LBT) and the external module is on the other region of firmware (i.e. FCC). Then you can use one of the modules to bind to EU-LBT receivers and the other to bind to FCC receivers, if you have the need for that requirement.