Hi all.

As a christmas gift i was given a Furibee X215 which has a frsky xm+ rx. And also a flysky FS-i6 tx. I cant get the drone to bind with the radio. After a lot of googling and searching ive hit a brick wall and am now hugely confused due to reading to many different things.

I think the easiest thing is to buy a different rx that will work out of the box with the frsky rx.

So id like to know what my options are. Is a different radio the answer? If so what cheap radios are compatible? Is a cheap one worthwhile or should i bite the bullet and get a more expensive one so i am futureproofed. Such as a taranis x9-D which would let me update the rx.

Im stumped as to the best option! But id prefer not to take my rx out of the drone and do soldering/updating etc, I just want it all to work.

Im a bit of a noob! So please be gentle. Thanks in advance.

Andy.

You can't use Frsky RX with Flysky TX. Either switch RX or TX.

Q7X or X9D plus are good radio. X9D plus is what most pro fly with. Both will update your RX without problem.

Or a FlySky RX like this for $4.99..! FrSky make the better radios and receivers though.

Be aware that if you have not flashed benb0jangles firmware your FS-i6 you will only be able to use the native PPM protocol, and therefore not the iBUS digital protocol that is an option with newer FlySky RX.

Thank you both for the replies. I got myself a Taranis 9x-d plus and bound it yesterday evening so all good for that step. The new issue i have now is that my throttle, yaw etc didn't control my drone in the correct way.

I loaded up betaflight and connected to my drone and in the radio section, if i throttle up (left stick) the yaw slider moves. I managed to chane it by selecting a diferent option in the dropdown list. But my drone is still unresponsive in terms of the motors spinning.

Only the led's flash different colours on the back when i move the controls. I followed a set of videos to setup the taranis before binding to the quad. It setup switxces for arming, disarming, changing the flight mode etc so i wondered if having these setup would stop my drone working. Ive tried flicking all the switches and levers but im getting nothing.

Any ideas? Many thanks.

Andy.

What betaflight firmware are you using? If 3.2 or later, go to CLI type Status
Post results.

Hi Vodoo614, thanks.

I'm pretty sure out of the box it was 3.2

Thi's will be tonights job then! I will let you know later as unfortunately I am at work now.

You setup all your switches in Taranis, but do you setup the mode tabs in configurator for arming?

I haven't done anything in the betaflight except change the Channel Map to JR / Spektrum / Graupner which made my throttle ect map correctly. I was too scared to fiddle with too much!

I will take a look at Betaflight properly and do the status on CLI and get back to you.

Don't worry about CLI and status.

You need to setup switch arming. That is in mode tab. Plenty of video tutorials. If you setup everything and you still can't arm. Then post your status.

Just FYI, when you are connected to the PC via USB to BetaFlight, if you do not have your battery connected the motors won't spin, there isn't enough amperage (or voltage for that matter) on the 5v from the USB to power the motors. As long as the sliders are moving with stick inputs in the 'Receiver' tab, you should be good to go..?

Remember do not test your motors with props attached!

Hi peeps.

Just for reference here is the status.


# status
System Uptime: 3050 seconds
Voltage: 0 * 0.1V (0S battery - NOT PRESENT)
CPU Clock=168MHz, GYRO=ICM20689, ACC=ICM20689
Stack size: 2048, Stack address: 0x10010000
I2C Errors: 0, config size: 2026, max available config: 16384
CPU:6%, cycle time: 128, GYRO rate: 7812, RX rate: 111, System rate: 9
Arming disable flags: CLI

I presume this is all good? Back to my problem and thanks you I have fixed it. I found out how to set my modes to the relevant switches and it was the arm mode that sorted it all out. I haven't put the props on my quad at all yet!! I have a strange excited but apprehensive feel about doing it!

Further to this I have spend some hours reading a lot of the betaflight help documentation and watching videos on you tube. Particularly from Project Blue Falcon. His LED guide was superb so I've got some nice flashing LED's for turning, throttling and arming/disarming.

One last question, my drone has Betaflight 3.2.2 installed. Should I update it to 3.3.3? Would this give me any benefits at all?

Next step is to get this bad-boy flying!

Thank you both for your help.

Great. Arm disable flag does not show anything that would prevent you from arming.

Unless you are running F. Port., the is no benefit to 3.3.3.

I can relate to the apprehension. Just have to crack that nut.