I’ve been flying a DJI spark for some time and thought I’d get into FPV. To start I grabbed myself a FatShark, TaranisQ 7s and a Meteor65.
However, for the life of me I can’t get anything to bind with the Meteor65. I’ve updated the firmware, purchased an external module for the receiver, there are conflicting videos all over the net so keen to have a chat or meet with someone who can help.
No worries my man, where in the world are you based? We hold regular meet ups and you’d be more than welcome to attend. There’s a few of us that meet up on a regular basis around the Midlands area
Joy. Manged it once, maybe twice, and just when I thought I’d got the hang of it, completely failed.
The key issue, is having the same firmware version in the TX and RX, and given that there’s two “current” version levels and each of those has an EU and rest-of-World version, there’s plenty to get wrong.
The worst of it is, I don’t think you can easily find what firmware is actually on your devices, so you’re basically stuck with picking one, flashing everything and hoping it works.
I was extremely resistant, but it didn’t take long for me to swap to Crossfire.
Where did your Meteor65 come from? If the answer is China, it is very likely that the FrSky RX is the FCC version and if it’s a recent model, it’s also likely that it’s ACCST 2, which isn’t compatible with OpenTX/multi-format transmitters (haven’t looked at your TX module yet)
EBay, I did order a LBT drone and RX. I bought the external module to get past the ACCST issue without flashing the RX… at least that’s what my internet research pointed me towards
Well, if everything’s LGBT you should be laughing.
Seriously though, it looks like there’s a lot of dip switch settings on the TX that change the receiver compatibility and could still stop you from getting connected.
If you are using the external module to get around the lack od D8 protocol on the 7Xs you need to enable this in screen one of the modelsetup menu, you’ll also need to disable the internal module.
With the external module option set to XJT you then need to select the D8 protocol. This protocol is not region specific so you don’t need to worry about EU LBT and non-EU.
In Betaflight, with your Meteor connected, go to the receiver tab and ensure the receiver option is set to “SPI Support” and the protocol is “FrSky D8.”.
Next go into the CLI tab and on the command line type “bind_rx” and hit return.
This will put the built in SPI receiver into bind mode.
Now you can activate the bind option for your module from the first screen of your model setup and all being well you should now be bound.
Disconnect your quad from the USB and reconnect and hopefully your radio will announce “Telemetry Recovered.”
firstly thanks for helping out here. I managed to miss that article but covered everything it says, which is why I’m running out of ideas. It’s also the reason I ordered the Expansion module to get around the new protocol that isn’t open source.
This is what I went through with the 2nd hand Nazgul I got on eBay that had an XM+ on it. I already had quad with XM+ bound to my controller, so I thought I was making a sensible choice.
But I could not get them damn thing to bind. Every indication was that it was working. Flashed with different firmwares several times and all seemed to go okay. Just wouldn’t play ball.
So I eventually thought life was to short, bought a TBS Crossfire starter bundle and had both quads transferred and up and running in probably about an hour.